Versar, Inc. - Armed Services Board of Contract Appeals
Versar, Inc. - Armed Services Board of Contract Appeals
Versar, Inc. - Armed Services Board of Contract Appeals
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
& ..2221£2£ 2<br />
· Ft. Stewart through the LonWorks protocol. <strong>Versar</strong> did not consult. with Ft. Stewart.<br />
(R4, tab 1 at 22; trw 2/38-42,45, 65-66, 68,178-79, 181, 6/101-02, 140)<br />
20. PSC commented upon C/Tech' s submittal that Andover did not interface, and<br />
was not completely compatible, with Ft. Stewart's system. <strong>Versar</strong>'s 23 August 2006 RFI<br />
.No. 15 responded that its system was compatible with Siemens and complied with<br />
specification requirements to use LonWorks technology as the communication protocol<br />
and LonMark standard network variable types and any specification deviation could have<br />
cost or schedule impacts. (R4, tab 124 at 2344-45; trw 6/140)<br />
21. On 23 August 2006, a Siemens senior sales engineer informed Mr. Nickel:<br />
Andover is correct ...that our system carl support Lon<br />
as specified. However specification item J, states the<br />
[Pinckney] system shall interface and communicate to the<br />
Siemens system at Fort Stewart. The engineer followed the<br />
[C]orps open protocol specification for your project.<br />
[H]owever the school system is not administered from the<br />
[C]orps specification. The school systems at Fort<br />
Stewart...are not LON as specified by school administration.<br />
[They] are Siemens BACnet for the front end and RS-485 for<br />
the building systems all on the campus network. LON cannot<br />
interface to any <strong>of</strong>our existing systems [without] Andover<br />
providing a BACnet panel at [Pinckney] and both companies<br />
providing labor to program and unbundled points which is<br />
costly[.] ...Andover assumed the systems at Fort Stewart were<br />
LON based on this specification and they are not. To fully<br />
meet the specification Andover should have performed [ an]<br />
analysis <strong>of</strong>the systems at Fort Stewart based on item J[.]<br />
(R4, tab 200 at 3012) On 22 September 2006 Richard Habrukowich, <strong>Versar</strong>'s project<br />
manager (tr. 1/259), asked the CO for a specification amendment or written direction that<br />
<strong>Versar</strong> use the Siemens control exclusivelr (R4, tab 200 at 3010,3015). An AFCEE<br />
employee inf<strong>of</strong>fi1ed Mr. Habrukowich and the CO that Siemens could communicate with<br />
LonMark ifan interface device were used but he suggested they "make sure that Siemens<br />
provides the interface to BacNet in lieu <strong>of</strong>the LonMark System and inform the engineer<br />
<strong>of</strong>your decision to clarify the specification" (R4, tab 150 at 2575).<br />
22. On 25 October 2006, Robert Rollo, PSC's prin.cipal, wrote to CO Brown that a<br />
change directive should issue to engage Siemens and that "[t]he customer understands<br />
that this will be an additive cost contract mod and is fully prepared for this change" (R4,<br />
18