ATR_VCS_Procurement_-_Answers_to_Site_Visit_Questions_11JUN14.docx

Answers to May 6th Site Visit for Voice Conferencing System Solicitation Number: N00421-14-R-0030

1. How will ATR compare costs between vendors?

Will a pricing test scenario be generated for the RFP?

The Government will arrive at a "best value" decision by doing a trade off analysis of price and non-price factors and by considering other value indicators such as warranty and maintenance availability. As stated in the synopsis-solicitation, the Government will award a contract resulting from this solicitation to the responsible offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The following factors shall be used to evaluate offers: Technical; Past Performance; Price. Technical and Past Performance, when combined, are Significantly more important than Price.

No, a pricing test scenario will not be generated. However, Updated CLINs, CLIN descriptions, and quantities have been provided (CLIN 0001-CLIN 0018). Vendors shall provide unit pricing associated with each CLIN and quantity. Additionally, data shall be provided to backup and show how pricing was determined and arrived at, i.e., GSA schedule, labor assembly, etc.

2. For the pricing exercise will ATR be requesting associated licensing fees for the Core and each room?

All licensing fees must be included. If the license is a one-time cost, include it with CLIN0001 and CLIN0002 (as required). If the licenses are recurring, include them with CLIN0018.

3. How is FAT, Installation, and SAT to be priced within the proposal or pricing exercise?

Factory Acceptance Testing should be included with the equipment cost. System Acceptance Testing should be covered under CLINs0016 and 0017, and Installation should be covered under CLIN0014.

4. How will ATR score the cost difference for a vendor to provide the minimum T requirement vs the optimal O requirements?

If meeting the Objective will incur an added cost, vendors must indicate the cost for both levels of performance (i.e. Cost to meet Threshold = $XX, Cost to meet Objective = $YY)

The Government will award in accordance with FAR part 12 on a best value basis.

The provision at 52.212-2, Evaluation -- Commercial Items (Jan 1999), applies to this acquisition. (a) The Government will award a contract resulting from this solicitation to the responsible offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The following factors shall be used to evaluate offers:

Technical;

Past Performance;

Price.

Technical and Past Performance, when combined, are Significantly more important than Price.

5. The vendor demonstration may require the purchase of equipment or maybe even require equipment to be manufactured.

How much time will a vendor be given to prepare for the demonstration?

Vendor demonstrations are scheduled to take place within the second week of July (7th -11th). The exact date will be assigned, first come, first serve, when the written proposal is received by the government. On the day of the demonstration, each vendor will be given 1 hour to setup, 2 hours each for demonstration, and 1 hour to teardown.

These must be commercial items per the synopsis-solicitation.

6a. Requirement 3.3.2 States ATR will install fiber and/or copper cabling between rooms.

Does vendor wire up in the rooms?

No. ATR will be responsible for wiring the individual rooms.

6b. Does ATR supply network switches within the room or does the vendor?

ATR will be responsible for all networking infrastructure, within and in between rooms.

7. Requirement VCS 2.1.1.3.3 Does this requirement expect a display for each PTT unit on the end instrument or a display for each trigger (2) on the end instrument?

Threshold Requirement= Indication that ANY of the connected PTT triggers are active;

Objective Requirement= Each PTT trigger, for each connected PTT device The specification document has been updated to reflect this change (VCS.2.1.1.3.3 has been modified and renumbered to VCS.2.3.4).

8. Requirement VCS 6.3.1 What is the quantity of T1 interfaces? What do the T1 interfaces Terminate? How will these 4-wire interfaces be included in the pricing example?

The only hard requirement for T1 interfaces are to communicate with our legacy COTS equipment, of which we have 10 that are approximately 66% full. Version 1.0 of the specification was not clear regarding this, and has since been updated.

These T1s are split into DS0s and terminate various 4-wire, and 2-wire COTS devices.

Pricing should include 10 T1 (DS0) interfaces for the legacy gear, plus any T1s necessary to support the new EIs (if any, per vendor design).

The specification has been updated to reflect this clarification

9. Requirement VCS 6.3.3 Are the 4-Wire interfaces physical interfaces or are they DSO's within a T1?

If physical, how many 4-Wire Interfaces are required?

Where do they terminate?

How will these 4-wire interfaces be included in the pricing example?

All of our 4-wire interfaces are DS0s within the T1s, as mentioned in the answer to question #8.

Per VCS 3.0 (updated in version 1.1 of the spec), The number of legacy 4-wire interfaces fit within 10 T1s.

Per the answer to question #8, price out the cost of the individual 4-wire interface, given the quantities listed in the specification.

10. Requirement VCS 6.3.5 -What type of Telco interfaces are required - 2-Wire FXO, Tl, SIP? 2-Wire -What is the quantity of each type of Telco interface - 2-Wire FXO, Tl, SIP?

-Where do the Telco interfaces Terminate - Core only or Core and each room?

-Do the Telco interfaces all terminate at the base PBX?

-How will these 4-wire interfaces be included in the pricing example?

-Per VCS.2.5.1, we will only require connections to Plain-Old-Telephone-Service (POTS) lines. -Quantity 4.

-The termination of these lines depends on the vendor’s architecture, but our current configuration has them terminating at the Core.

-Telco interfaces terminate in a room within the main ATR building -Price out each 2-wire interface, given our quantity requirements

11. Where do the radios terminate and how many terminations are required?

How will the radio interfaces be included in the pricing example?

Does vendor supply the radio interface cables between to radio and the vendors demark?

All of our radios, regardless of physical location, all connect to our central computer room. We have approximately 40 radio connections. Please price out the cost of an individual radio connection, given our quantities. Yes. The vendor is to supply the radio interface cable, as our current cables might not be compatible.

12. Infrastructure: Copper, Fiber, Ethernet Will ATR provide the infrastructure for the backbone and each room location?

Yes

13. There is no mention of a Non-Blocking Voice Conference System. A non-blocking system allows multiple simultaneous talkers on the same conference at the same time.

A blocking system allows only one talker to be active on a conference at a time. All other talkers are denied access until the first talker stops injecting into the conference. Is this a non-blocking voice conference system a requirement?

Yes. Non-blocking was the intended requirement.

The specification document has been updated to reflect this clarification (VCS.2.3).

14. There is no mention of HA or no-single -point of failure. HA or no-single point of failure is defined as a part of a system that, if it fails, will stop the entire system from working. Is this a requirement?

Ex. If servers are utilized and the servers are required for system operation should the servers be provided in an HA (On-Line with Hot Standby) configuration?

The specification has required an availability of 99.97%, and it is incumbent of the vendor to design a system that is able to meet this goal, using redundancy or any other method deemed fit.

The specification document has been updated to reflect this clarification (Sec.2.5).

15. Reference Requirements Document. Para. 3.6 Technical Data Package When shall the contractor deliver the technical data package?

See the individual CDRLs (file attached with RFP) for the required delivery dates for each item.

16. Reference Past Performance Questionnaire Who submits the completed questionnaire to NAWCAD Contracts?

Should the completed questionnaire be submitted by the agency completing the questionnaire, or should the agency forward the completed questionnaire to the bidder for submission to NAWCAD Contracts?

Questionnaires should be submitted by the agency completing the questionnaire.

17. The CDRL file has only odd-numbered pages, please provide complete file with all CDRLs.

Upon closer inspection, you will realize that there are two CDRLs listed on each page.

18. The RFP indicates contract type is IDIQ, FFP for 5 years which doesn't match 2 years for "100% delivered and installed" in Specification 3.7.

The specified 2-year window is the hard timeframe we have to replace our existing equipment. The contract was created as a 5 year IDIQ to provide a vehicle for future expansion, replacement parts, and maintenance delivery orders.

Our existing equipment is defined per the list of equipment found in Section 8.0 of the specification. Note the term “suggested” acknowledges there could be minor variations in vendor architectures, while scoping the size of the required effort.

The CLINs have been restructured to more closely match Section 8.0

19. The RFP lists quantities for various equipment items as CLINs in Requirements - what are these and how do they compare versus different quantities in Specification 8.0 and El quantities by location in Specification 7.0 maps?

The quantities listed under each CLIN represent the maximum ceiling for each item allowed by the contract. The number of actual items ordered by the government will vary as the need arises, and will come as individual delivery orders after contract award.

Per the answer to #18, Section 8.0 lists the quantities for our current equipment that must be replaced within the next 2 years. The equipment list was labeled as “suggested” to allow for some minor variations due to unknown vendor architectures.

The map provided by Specification 7.0 indicates users, not instruments.

20. When will Vendor Demos be scheduled? Based on past experience with these, two hours is a very short timeframe to successfully demonstrate the extensive features in the Specification. Although it will require more time commitment for ATR personnel, four hours is suggested to ensure proper evaluation of this critical step in the final decision process.

With regard to scheduling, see the answer the question #5.

As for the demonstrations, we are confident that we can evaluate systems within a 2 hour window, when coupled with the written proposals. Please keep in mind that this time is allotted for equipment demonstration only, and should NOT include any power point briefs, company information, etc. We are including 1 hour of setup, and 1 hour of teardown on each end of the demonstration, for a total of 4 hours.

In an effort to focus the vendor demonstrations, a list of mandatory requirements to be demonstrated has been listed in the specification.

The specification has been updated to reflect this change (Sec.4.2).

21. The RFP mentions in (b) at bottom of page 3 "options" along with "basic requirement" but provides no definition of either nor can we find similar elsewhere. How are we to interpret what system content to price for "basic" and/or "options" for accurate and consistent price evaluation?

The “basic requirement” is the equipment required to satisfy the Threshold requirements within Section 6.0, with quantities large enough to satisfy Sections 7.0 and 8.0 of the specification. Any additional cost required to meet the Objective level of performance should be indicated as an option. See Question #4.

22. Specification 2.0, Fig 1 shows "Copper/Fiber" for connections from main switch, how many of each to provide?

Figure 1 is a conceptual drawing only meant to highlight that both wired and RF connections are involved. As stated in the specification section 3.3.2, ATR will be responsible for cabling between rooms. The number of connections is dependent on the vendor’s architecture, to meet the required number of communications devices.

23. Specification 3.3, System Installation has a number of undefined requirements, which preclude accurate pricing. What is proposed work schedule to be planned for installation activities "to ensure flight operations are not affected"? What is quantity of Els and Radios to be included in Initial Equipment Installation? Since ATR will be responsible for installation of all equipment after Initial, what quantities of Els, radios or other external interfaces are projected for how many follow-on orders, and how will ATR evaluate installation costs for these?

It is the government’s responsibility to schedule installations as to not interfere with flight schedules, and ensure that once the installation process begins, the winning vendor will have full 9+ hour days, during normal business hours to complete the installation.

The exact number of EIs and radios is to be determined after award. As an estimated figure for planning purposes, we anticipate the need for ~25 EIs, ~4 radio connections and ~1 standard COTS 4-wire PTT unit.

The number and quantities of follow-on orders depends on both vendor and government constraints, to meet the equipment specified by Section 8.0. Delivery orders vary at the government’s discretion, but we anticipate placing quarterly delivery orders.

24. System Verification, 3.4 indicates the need for vendor to perform this function for all "installed increment(s)". It is understood this paragraph applies to the Initial Equipment Installation, but if the follow-on delivery orders only add additional Els or radio interfaces, the need for completely new system verification is minimal and a costly additional requirement.

The level of verification for the initial installation and incremental follow-on installs is not expected to be at the same level of detail. To account for this, the CLIN structure was amended to account for this price difference.

CLIN0016 Initial Testing CLIN0017 Follow-on Testing

If the government determines verification is needed with a delivery order, Follow-on Testing (CLIN0017) will be included along with the equipment order.

It is expected that the vendor should tailor the testing procedures (and cost) to match the item(s) delivered, pending government approval.

The specification document has been updated to reflect this clarification (Sec.3.4).

25. Training, 3.5, shows training for 12 ATR personnel after "completion of system acceptance test". If this means 3.4, System Verification as seems obvious, is this training only required following the major Initial Installation? To train 12 more people after every proposed follow-on delivery order would seem excessive in both cost and ATR personnel time. Perhaps the bidders should simply provide a standalone price for a 12 person training class at ATR instead? In similar vein, this paragraph requires a consultation visit 90 days "after final system acceptance test". When is this visit to take place, after the Initial delivery, after all deliveries, or after only the final delivery?

There is no hard requirement to require a training session with every delivery order. A delivery order for training will be placed by the government when it is required (pending scheduling considerations with the selected vendor). The timing and frequency of the training sessions will be at the government’s discretion, but will most likely follow major delivery orders.

The specification document has been updated to reflect this clarification (Sec.3.5).

26. Specification 6.2.1, VCS 2.1, calls for "tactile" touch screen. Assuming this means an actual "feel" to the user when depressing the touch screen, these designs are not readily available and expensive, so perhaps the more typical visual and audible indications are acceptable alternatives?

VCS 2.1 specifies “…a tactile mechanism for operators to select…”. The key word is select, and does not imply any sort of tactile-feedback mechanism.

Our market research showed solutions other than touchscreens which could meet our requirement, and we did not want to exclude those designs.

27. Specification 6.2.3, VCS 2.3.1.1.1/.2, calls out handset with index and thumb PTTs, with thumb as lockable. However, the Plantronics headsets earlier mentioned in 2.4.2 has only a single PTT. Is there a requirement to deliver some quantity of handsets with dual PTT with this contract? If so, please provide specifics on design and quantities.

The Plantronics handsets model listed in the spec (as well as all of our dual PTT handsets) are single PTT units that has been purchased by our current vendor and then modified to add a second PTT for the index finger.

Yes, there is a requirement to deliver dual PTT for all handsets (see Section 8.0 for qtys) and VCS.2.3.1.x for specifics.

After further consideration, the requirement for LEMO compatibility has been removed.

The specification document has been updated to reflect this change. (VCS.2.1.3).

28. Specification 6.3 describes a number of COTS interfaces, but there is no mention in the bid of quantities of any of them to be supplied with Initial and any follow-on delivery orders. Please provide these to support accurate and consistent price inputs.

Section 6.3 has been updated to reflect the total number of required COTS interfaces.(VCS.3.0)

Please see answer to #23 for the initial delivery order.

29. Specification 6.3.6, VCS 3.6, calls out Motorola URC-200, General Dynamics CM 200, and INTECH COM160 radios. Are the Interface Control Documents for each radio available for evaluation to determine the level of effort needed to support remote radio configuration?

No. Contact the manufacturer to obtain those documents

30. Specification 6.4.3, VCS 4.3, mentions all comm devices to connect via "network" without any definition of the type of connection allowed or preferred here, i.e. analog, digital, IP, etc. Further, looking at the maps in 7.0, there are Els located all over the ATR region, again with no definition of allowed/preferred network connectivity back to the core switches at ATR.

The use of the term “network” was intentionally unspecific, as exact connectivity varies by location. ATR has the ability to change and manage the network configuration. If the vendor equipment is able to communicate via T1, Ethernet (IP), 4-wire, and 2-wire, per VCS.3.x, the need will be met.

31. Specification 7.0, mentions all El locations have "power and network", but doesn't define specifics on either. What are allowed/preferred by ATR for these parameters? This 7.0 paragraph also says that locations where two users would share an El are indicated on the subsequent maps with "*", although no markings like this can be found on the actual maps. Is this an error? Finally, can ATR provide some specific breakout of which of these locations and quantities are foreseen as Initial delivery for sure, and then any likely follow-on delivery order quantity/location?

All locations have 110VAC power, and IP connectivity connected to the main ATR complex.

Unfortunately, the “*” indicating shared users was left out of the released version, as an oversight on our part.

The specification document has been updated to reflect this change.

The expected initial delivery order is specified in Section 3.3.2, and follow-on orders and quantities are dependent on need and funding availability.

Section 8.0 reflects the amount of our current equipment we intend to replace. See questions #18 for more detail.

32. Specification 8.0, Suggested Equipment List, has quantities that do not match to those in RFP Requirements, nor to the maps in 7.0. Please explain how we should interpret all these discrepant requirements to provide a final pricing proposal that will be equivalent for all vendors.

What is required offer validity and what is proposed initial order date and completion for Initial Equipment Delivery?

See Question #19.

Please price your proposals around the list in Section 8.0, and include the price for each item. Note that section 8.0 is only labeled as “suggested” to accommodate unknown vendor architectures, and may need minor revisions. Updated CLINs, CLIN descriptions, and quantities have been provided (CLIN 0001-CLIN 0018). Vendors shall provide unit pricing associated with each CLIN and quantity. Additionally, data shall be provided to backup and show how pricing was determined and arrived at, i.e., GSA schedule, labor assembly, etc.

There is an addendum to the solicitation in which the provision at FAR 52.212-1, Instructions to Offerors – Commercial Items, now states: “The offeror agrees to hold the prices in its offer firm for 120 calendar days from the date specified for receipt of offers.”

The first delivery order will be placed directly after contract award. Delivery date will be specified in the delivery order.

33. Should we provide a complete Representations and Certifications with our proposal, even though these are available from our System for Award Management listing?

No, each offeror shall include a completed copy of the provision at FAR 52.212-3, Atl 1, Offeror Representations and Certifications – Commercial Items (Nov 2013), with its offer.

34. Section 2.1.1

How many of each type of COTS device listed should the system support?

See answer to questions #8 and #9

35. Section 2.2

Must administration functions be accomplished through the central mechanism for administration, or can some administration functions be accomplished at the operator station under an administrator log in?

All admin functions must be available at the administrator consoles. Any admin functions that are also available at the End Instrument must be password-protected from normal End Instrument users.

36. Section 2.2

What privileges should be limited?

Without knowing the individual design implementations, it is hard to set a hard requirement on what privileges should, and should not be limited.

In general, the user shall be restricted from performing all administrative functions, such as adding and removing devices or members from conferences.

37. Section 4.2

Does this include joining RED conferences together?

No, that is not required for the demonstration. See updated specification regarding the requirements which must be addressed as part of the vendor demonstration.

38. Section 6.1

(VCS.1.2) Between which points is communication latency to be measured?

One way, end-to-end, latency. For example: Originating from a user’s headset, through the system, and out a connected UHF/VHF radio. Also: From a user’s headset, through the system, out the earpiece of another headset connected to a physically separate EI.

39. Section 6.2.1

(VCS.2.1.1.2) What information must be displayed on the conference buttons?

See VCS.2.1.1.3.x

40. (VCS.2.1.1.2) Is Finger-on-Glass (FOG) PTT required?

FOG PTT is not a requirement. FOG does NOT circumvent the index and thumb actuated dual PTT requirements per VCS 2.3.1.1.1 and VCS 2.3.1.1.2

41. (VCS.2.1.4) Is there a specific model of hand-mic required? (Also: VCS.2.3.2)

No specific model is required, provided all requirements specified by VCS.2.3.2.x are met

42. Section 6.2.2: (VCS.2.2.2) Is the speaker vendor-provided or is there a specific model of speaker required?

No. Per VCS.2.2.2, the speaker should be internal to the End Instrument, and provided by the vendor.

43. Section 6.2.4: (VCS.2.4.2.2) What type(s) of failure?

Any failure that might jeopardize the separation of multi-level data. The exact implementation is design dependent. The intent of this requirement is to drive the “default state” of either software or hardware to separate RED and BLACK audio. For example, if a relay is employed in the design, the un-energized state must disconnect RED and BLACK, and require power to connect.

44. Section 6.2.6

(VCS.2.6.2) Are display sizes absolute values or minimum values?

Absolute. The threshold and objective values are used to define the range of acceptable screen sizes (10” – 12” diagonal).

45. Section 6.3.1

(VCS.3.1) How many T1 circuits?

Please see answer to question #8.

46. Section 6.3.6

(VCS.3.6) What other types of radio types are required? Is this list complete?

No other radio types are required.

Yes, the list of Threshold and Objective radios are complete. Threshold=Radios we control today, which must be part of our next-gen system. Objective=Radios used at ATR, but not currently under remote control.

47. How many VoIP lines are required and what codecs need to be supported?

The number of VoIP lines depends on the proposed architecture. Per the specification, we require a hybrid system that will interface with our legacy T1s, while allowing all newly procured equipment (EIs) to be all VoIP.

There are no requirements for specified the VoIP codecs, but industry standard codecs are preferred.

48. How many POTS lines need to be supported?

Per VCS.2.5.1, 4 POTS lines

49. Please specify the number of past performance references to be submitted?

There is not a specific number of required Past Performance Questionnaires. Please provide past performance efforts of similar size and scope within the last 3 years, including contract number, organization supported, indication of whether as a prime or subcontractor, contract value, Government point of contact, and a brief description of how the referenced contract relates to the services described in the Requirements Document. Provide past performance information by utilizing the Past Performance Questionnaire provided.

50. The suggested equipment list quantity (Section 8, page 34 of requirements document) differs from quantities listed on the Fed Biz Opps notice requirements for CLINs. Do CLINs supersede the section 8.0 listing?

See Questions #18, #19, #32.

51. What is the anticipated award timeline for this procurement?

It is anticipated that the contract will be awarded in September 2014.

52. Will the radio(s) be GFE for vendor demo?

Yes, a Motorola URC-200 and General Dynamics CM 200 will be available during the demo to facilitate demonstration or audio communication and control.

53. Is the vendor responsible to provide 19” racks for the Core VCS equipment? If so, is there any space limitations?

Yes, the vendor must provide the 19” racks. Although a small footprint is advantageous, there are no space limitations.

54. Who is to supply the Channel Bank equipment? Vendor, or ATR? How many channel banks are required?

ATR will be responsible for purchasing and installing the channel bank equipment. The number depends on vendor design.

55. Is CAT5e or Fiber preferred for EI connection?

In general, the weather hardened EIs are preferred to be CAT5e, while the Desktop and compact EIs are preferred to be fiber.

56. Requirement 3.3.2 – Initial Equipment Installation “…including any support equipment necessary…” Please clarify what is considered support equipment.

Is the vendor responsible for supplying networking switches and routers, channel banks, voice recorders?

“Support equipment” is a general catch-all to specify any other equipment which is needed, per the vendor’s design. The vendor is NOT responsible for supplying channel banks, or network switches/routers

57. Proposal submissions question- Is hand delivery of the proposal possible? If so, who/how would this be done on base?

Postal Mail instructions and address were provided in the Synopsis-Solicitation. Hand delivered proposals will be accepted and submissions must be received at the NAWCAD office cited no later than 2:00 p.m. Eastern Time on June 23, 2014. They can be delivered to NAWCAD Contracts, Attn: Tonya Lakner, Code 2.5.1.11.5, Building 441, Naval Air Systems Command, 21983 Bundy Road, Patuxent River, MD 20670. Note that the proposal due date has been extended from 29 May 2014 until 23 June 2014.

58. For the proposal submission, is there any page limitations or format constraints?

Yes, proposals are being limited to 50 single-sided pages exclusive of the cost section. Include (2) two hard copies and a CD containing the proposal package separating the cost section of the proposal. The proposal document shall be in Microsoft Word and the Cost Section shall be in Excel and must include any formulas to show how final price is computed.

Please note, 50 pages is the maximum page limit, and not the expected size. Updated CLINs, CLIN descriptions, and quantities have been provided (CLIN 0001-CLIN 0018). Vendors shall provide unit pricing associated with each CLIN and quantity. Additionally, data shall be provided to backup and show how pricing was determined and arrived at, i.e., GSA schedule, labor assembly, etc.

59. What specific standard(s) does the current multi-level EI adhere to? Within that standard(s) which sections are applicable to your requirement?

Per VCS.5.1.1, The system shall be certified to the National TEMPEST Standard, NSTISSAM TEMPEST/2-95 (Red/Black Installation Guidance, dated 12 December 1995.

Please note, the previously released spec incorrectly referenced an older standard.

The specification document has been updated to reflect this change (VCS.5.1.1).

60. What specific standard(s) does the new multi-level EI need to adhere to? Within that standard(s) which sections are applicable to your requirements? If existing COTS equipment meets some, but not all of those criteria is NAWCAD willing to certify and/or assist in obtaining such certification?

TEMPEST/2-95, per VCS.5.1.1. Given our timeline, we are only interested in a fully TEMPEST certified, turn-key solution that is certified to handle multi-level security at the time of contract award.

61. Given there are a multitude of options for multi-level separation (chassis housing, fiber over CAT5e, separate touchscreen or PC, etc.) do you have a preferred implementation approach that best meets the needs of the ATR?

It is mandatory that both RED and BLACK core systems are physically separated, and have two independent networks, per VCS.5.1.1. The only multi-level capable device is the EI, which shall take both RED and BLACK inputs from each respective core, and become members of both types of conferences (VCS.2.4.2). Provided this single user device can meet that requirement while adhering to the TEMPEST/2-95 standards the method for achieving it is a “don’t care” for the government. Separate touchscreens (RED only/ BLACK only) will not be an acceptable solution, per VCS.2.4.2.

62. Please provide the type of crypto devices that are currently supported.

There are no crypto devices currently in use. All RED audio is physically separated from BLACK, and is NOT transmitted outside the room.

63. During the site visit, a failure instance was explained to the attendees, wherein the radio changes were considered failure and its effect on the latency was described. Can data and/or details describing other such failure instances be provided?

The “failure instance” described at the site visit was a project-specific issue that occurred outside of our voice communications system. No failure data will be provided.

64. Would NAVAIR consider extending the proposal submission due date by a minimum of two weeks?

The extension will allow adequate time for the bidders to review the questions and answers after they are released and to make the necessary adjustments/revisions to their proposal based on the answers provided.

The proposal due date has been extended. Proposal submissions must be received at the NAWCAD office cited no later than 2:00 p.m. Eastern Time on June 23, 2014.

65. CLIN 0001- Core VCS components, 6 qty.

Is there a known application and configuration for these 6 systems?

Are these 3 red and 3 black systems?

Are any of these systems intended to be deployable configurations?

As answered in Question #18, the CLIN quantities include room for future expansion, and maintenance. fmrCLIN0001 has since been broken out for clarity:

CLIN0001 Core VCS Components: BLACK CLIN0002 Core VCS Components: RED

66. CLIN 0009- Maintenance, 4 qty.

Please clarify what falls into this CLIN for maintenance?

This CLIN is intended for any yearly maintenance agreement costs which may be required.

fmrCLIN0009 has been renumbered to CLIN0018 and renamed “Yearly Maintenance Agreement” to aide in clarity.

67. CLIN 0004-Miscellaneous Equipment, 215 qty.

Please clarify what is to be included in CLIN 0004, “Misc. Equipment” 215 qty.

This CLIN has been removed.

68. CLIN 0002 VCS Admin, 13 qty.

Is the vendor to supply PC’s as part of this CLIN or is it just software?

Yes, the vendor is to supply PCs, hardened per the IA requirements of VCS.5.0.

Note: fmrCLIN0002 has been replaced with CLIN0004 The specification document has been updated to reflect this clarification (Section 8.0).

69. Please confirm that there is no cross-domain requirement for this solicitation. For example, DSWAG, VCPMO, CDSE, etc.

Correct, there is NO requirement for a cross-domain solution.

70. Dual display is listed as optimal for the compact EI. Is the preference to have one red and one black display? Would this be the preferred approach for the desktop EI?

There is NO requirement to separate red and black by display, for either the compact or desktop EIs.

71. What is NAWCAD’s primary purpose in updating the ATR VCS? Is it obsolescence, poor performance, new requirements or a combination? Please elaborate.

In order to promote interoperability and anticipating future test program requirements, we must gain a VoIP and SIP capability. Current system age is a concern, but performance/obsolescence is out of scope for this Q&A.

72. For certain operators that sit in front of an existing PC, would you want to integrate a communications GUI with that PC display in lieu of, or in addition to, a dedicated touchscreen?

No, dedicated touchscreen only.

73. What web browsers and versions are available for the admin GUI?

Per question #68, the vendor is expected to provide PCs, with required software, for administration capabilities.

74. VCS 3.6.4.

Is Ethernet only control an acceptable option?

The Motorola URC-200 can only be controlled via RS-232. If the Ethernet control converts to RS-232 it is an acceptable solution.

The specification document has been updated to reflect this clarification (VCS.3.6.4).

75. Can the threshold button requirements on the touch screen be tabbed?

Yes.

76. Is wireless allowed for the control panel, headset or Push To Talk (PTT)?

Per the security requirements of our environment, wireless communication is not allowed between any system components.

77. What sort of headsets and connectors are used now for the weather hardened EIs? What network connection is used today for these and what is allowed/preferred for new version?

The headset connectors are the same across all (weather hardened, desktop, compact) EIs. Today Network is CAT5 is used today and the preferred connection. The current physical CAT5 on the weather hardened unit is proprietary, not expected to be duplicated by the new system.

78. Similar to the idea behind Specification 2.4, Opportunities for Cost Savings, will you consider alternate design proposals from a bidder if it is believed they will meet the requirements?

Absolutely.

79. There is nothing in the specification to define required system redundancy or reliability. Typical specifications for mission voice switch products have this noted in some way. Suggest at least have each vendor provide their system reliability performance parameters as a valuable evaluation point.

Specific redundancy requirements were not included in the specification, as varying vendor designs require different levels of redundancy. The specification has set an availability figure which the vendor shall design to. As an evaluation point, each vendor shall submit their system’s reliability performance.

The specification document has been updated to reflect this change (Sec.2.5).

80. If operators are sharing an EI, with more than one conference in the “Active” mode with different PTT associations, and they simultaneously select different PTT buttons, i.e. Operator 1 pushes PTT1 and Operator 2 pushes PTT2, which PTT selection has a higher priority to transmit the microphone audio to the circuits associated to the PTT selection?

Both should transmit simultaneously.

The EI should treat all connected PTT triggers as independent, regardless of user. For example, 2 users with 2 PTT triggers equates to 4 potential triggers which can be assigned to any of the available conferences on that EI. When a PTT is triggered, voice is transmitted on the conference it is assigned to, regardless.

81. Specification 6.2.6, VCS 2.3.1.1, a typical “weather hardened” enclosure is designed for wall mounting, how does ATR foresee such an enclosure being “mounted in a rack”? Is this the current configuration?

Assuming the requirement referenced above was intended to be “VCS2.6.11”, the design is entirely up to the vendor. Historically, ATR has mounted these units to a metal plate, which was in turn mounted to a 19” rack. Yes, that is our current configuration.

82. Can and will ATR provide interface specifications for their existing communications equipment, specifically the servers?

See the answer for question 29. There is no requirement to interface with any of our existing servers.

83. Does ATR have the need to interoperate with and interface to the P8 and F18 simulation and training programs, and could these be early candidates for interoperability evaluation?

ATR does have interoperability requirements to work with other facilities, to support all of our customers, including the programs mentioned. We addressed our interoperability needs by specifying VoIP and SIP (VCS.3.2.x).

84. Section 2.0 states: “For all RED/BLACK EIs, measures will be taken to ensure that RED audio is separated from BLACK audio at all times, in accordance with Department of Defense Information Assurance and TEMPEST regulations”. The standard used to confirm RED/BLACK separation is NSTISSAM TEMPEST/2-95 (Red/Black Installation Guidance, dated 12 December 1995. Should VCS.5.1.1 NSTISSAM TEMPEST/1-92, Compromising Emanations Laboratory Test Standard, Electromagnetics dated 15 December 1992 reference be changed to NSTISSAM TEMPEST/2-95 to relate and agree with the Section 2.0 requirement?

Correct. Thank you for bringing this to my attention.

The specification document has been updated to reflect this clarification (VCS.5.1.1).

85. At the site visit, the Government appeared to indicate that a single point of failure in the system is not acceptable, and redundant elements are desirable. Section 3.8 Spares shows an availability requirement of 99.97% for one year. This availability equates to the possibility of a critical system failure- one that brings the entire system down- of 2.6 hours. Will the redundancy aspects of the proposed system be considered as part of the Government’s Technical evaluation? If so, are there any Threshold and Objective requirements?

Redundancy is part of the government’s evaluation. The government has not specified either threshold or objective reliability numbers, as these are COTS systems. The amount of redundancy required is dependent on the proposed design, to meet the specified availability requirement.

Vendors shall include their system’s reliability numbers with their proposal.

The specification document has been updated to reflect this clarification (Sec.2.5).

86. At the site visit, the Government appeared to indicate that while the primary network is migrating from T-1 (TDM) to IP based, there are still a number of TDM-based elements in the Governments network, which require a hybrid system capable of interfacing to both types (IP and TDM) network voice components. Will the hybrid (IP and TDM) ability of the proposed system be considered as part of the Government’s Technical evaluation? If so, does the Government consider the proposed system’s ability to connect and interface with both IP and TDM network equipment without adding additional hardware and associated costs a benefit? Should the costs of any required additional equipment necessary to transition from TDM to IP be included in the bidder proposals? Is there an estimate as to what portion of the solution will be TDM vs. IP at the time of initial installation?

Correct. Per the requirement set, a hybrid system IP and TDM system is an absolute requirement. This allows us to interface with our legacy TDM equipment, while procuring new VoIP End Instruments. If this functionality can be achieved without additional hardware or added costs, the government most definitely would consider this a benefit.

The cost of additional equipment to transition for TDM to IP should NOT be included as part of the bidding proposal.

The preferred breakdown is for all new EIs to be VoIP, but the ability to have TDM EIs does provide flexibility which is advantageous for the government.

87. Written and third party verified highly controlled processes, procedures, and internationally recognized quality standards such as ISO:9001, are generally considered important elements of ensuring consistent Quality in the Technical products and solutions being proposed. Will these aspects of the proposed system be considered as part of the Government’s Technical evaluation?

Absolutely. The Government will arrive at a “best value” decision by doing a trade off analysis of price and non-price factors and by considering other value indicators.

a) No. See answer to question #19. Also, per the update, the Core CLIN has been split (CLIN0001 for BLACK core, CLIN0002 for RED core)

b) See answer to questions #8, and #9

c) Reference Section 8.0

89. In regards to CLIN 0002 (VCS Administration) how many servers are needed and how many Client Software licenses are needed?

Per Section 8.0, we estimate the need to be 2 servers and 8 clients.

Please note that per the answer to question #68, we will be requiring the vendor to supply the PCs in addition to the software licenses.

Note fmrCLIN0002 is now CLIN0004

90. CLIN 0006 (Installation) - Is it correct that the vendor will only be responsible for initial equipment installation, and all subsequent equipment will be installed by the Government? If so, why is there a quantity of eight listed? For the initial installation, what are the individual quantities of each external communication devices (reference Section 2.1.1 COTS Devices) and each End Instrument type to be connected?

Correct. We anticipate needing only one initial installation event, and follow-on tests to verify ATR’s installation efforts.

Note fmrCLIN0006 is now CLIN0014 For the initial installation, see answer to question #23.

91. CLIN 0007 (Training) - Is Training required for the initial installation only (one session), or is training required for subsequent “remaining equipment installation”? What level of service is required for the training “follow-up consultation”?

We anticipate only one training session, with the exact time to be determined after award.

Regarding the follow-up consultation, the level of service will be one technical person on-site for 3 days, who can work with our technicians to administer the system more efficiently, witness system performance, and make any minor system changes as required.

Note fmrCLIN0007 is now CLIN0015

The specification document has been updated to reflect this clarification (Sec.3.5).

92. CLIN 0008 (Testing) - Is it correct to assume the number of days required for on-site initial installation testing and subsequent installation system verification testing may vary? If so, how should the vendor price testing? Is it acceptable to provide an hourly engineering rate, plus travel and expenses rate to and from the site, and a daily per diem rate? Providing information in this format will allow the Government to calculate the cost for any specific trip duration desired.

Yes, testing may vary. The initial installation should be priced to install a full RED and BLACK core, with EIs and COTS connections per the answer to questions #23.

Yes, it is acceptable to provide an hourly engineering rate, plus travel and expenses rate to and from the site, and a daily per diem rate. This is a firm fixed price contract therefore the contractor must provide exact cost of testing derived from their understanding of the system complexity and site installation.

Note fmrCLIN0008 has now been split into CLINs0016 and 0017 to account for initial and follow-on verification. Vendors shall provide unit pricing associated with each CLIN and quantity. Additionally, data shall be provided to backup and show how pricing was determined and arrived at.

93. CLIN 0009 (Maintenance) – Specific vendor requirements for Maintenance is not explained in the Requirements Document. Please describe how this is to be priced.

CLIN 0009 was setup as a placeholder for an annual maintenance contract to cover technical support, maintenance, and cyber security updates to comply with STIGs.

Note fmrCLIN0009 is now CLIN0018, and a description has been added to the CLIN.

94. Will the Government consider allowing clarification questions pertaining to the first round of Government responses be submitted after the Thursday, 4:00 PM cut-off time? This may benefit all parties by ensuring the Government’s responses are more fully understood by the bidders.

Yes, the Government will allow clarification questions. Although it was posted on FedBizOpps that the Question and Answer (Q&A) period was closed and no additional questions would be accepted, the Government has reopened the Q&A period in case more clarification questions are required based on the Government’s response. Questions will be accepted until 2:00 p.m. Eastern Time on Monday, 16 June 2014. Proposals must be received by NAWCAD Contracts office cited no later than 2:00 p.m. Eastern Time on 23 June 2014. Vendor Questions may be sent via e-mail to Tonya Lakner at Tonya.Lakner@navy.mil.

95. For the EIs being provisioned, if they provide the LEMO connectors, what handmics, headsets, and footswitches are to be provisioned with each EI by the vendor?

After further consideration, the requirement for LEMO compatibility has been removed.

The specification document has been updated to reflect this change (VCS.2.3.1).

96. Requirement 4.2 Vendor Demonstrations:

-Will the customer be providing a format and agenda for the two hour equipment demonstrations?

-What types of features, functions, performance items will be expected to be demonstrated?

-How much setup time will be allotted before the two-hour demo?

See Question #20.

The specification has been updated to show the list of requirements which must be demonstrated. The agenda within that 2 hour window is up to the vendor, but it is important to reiterate that the time period is for equipment demonstration, and not for a company briefing, or any other type of activity. 1 hour set-up and 1 hour teardown will be permitted in addition to the 2-hour demonstration.

97. CLIN 0006 – Installation, 6 qty -Can the customer provide more input on how the Level of Effort and the time period at site should be estimated for each installation?

-Note the vendor is only part of this formula

The level of installation effort should include a full BLACK and RED core setup, as well as the initial EI and radio capability as specified by the answer to question #23. Again, per the answer to #90, we anticipate only one vendor-performed installation event.

Note fmrCLIN0006 is now CLIN0014

98. How does FAR Sole Source N00421-14-R-0052 relate to this solicitation?

Unrelated. The referenced procurement is for a portable, deployable unit that is for another group within ATR.

99. Will the pinouts of the specified LEMO connector be supplied?

No. Unfortunately the pinout is proprietary to the manufacturer of our current system, therefore the requirement has been removed. See answer to questions #95.

100. Of the suggested equipment list, what percentage of the EIs are single user vs. multiple user?

Section 7.0 has been updated to show the split between single and multiple users. Please reference the maps in that section.

101. Does the customer consider system redundancy / availability a “value” item for any proposed solutions?

Absolutely.

102. Is the vendor demo part of a larger downselect (short list) process? What is the approximate vendor demo timeline post proposal submission? When can we expect to be notified?

No, per the RFP, the vendor demonstration is considered to be part of the initial proposal package which will be included in the Technical Evaluation.

Regarding notification, see Question #5

103. Requirement 2.4.1 – End Instrument Sharing Can the customer clarify the number and locations of the EI positions that could be shared?

-Note: It appears the “*” markings did not make it on the diagrams in the RFP

Per the answer to Questions #31, the indications were left out of the released version.

The specification document has been updated to reflect this clarification.

104. CLIN 0001 – Core VCS Components, 6 qty How are the “Core VCS Components” to be provisioned?

Can the customer provide system sizing information such as number of: EIs (red/black vs black only), radios, telephones, recorder ports, etc?

See the answer to questions #65, regarding provisioning of cores.

Please refer to Section 8.0 of the spec. for sizing information of the primary system need.

105. CLIN 0005 Spares, 90 qty and Requirements 3.8 Spares Please clarify how CLIN 0005 qty 90 and the provisioning requirements of paragraph 3.8 fit together.

How should a vendor determine the system size and configuration to apply the availability calculations against?

Note fmrCLIN0005 is now CLIN0013 Per the answer to #19,…