T-0073_QA_8-31-16_J3_Response_31AUG16.docx

Question 1: The notice on FedBizOps states that the deadline for questions is 4:00 p.m. ET on Tuesday, 6 September 2016. This is also the proposal due date and time. Please clarify.

Answer 1: The proposal due date will be changed to Friday, 9 September at 2:00 p.m. ET.

Question 2: The notice on FedBizOps states that the offeror’s submission must include “Completed and signed Standard Form (SF) 1449, page 1”. We cannot find an SF 1449 anywhere within the solicitation documents posted?

Answer 2: An SF 1449 was not posted. This requirement will be removed.

Question 3: The notice on FedBizOps states that the offeror must provide a “Completed pricing schedule”. We cannot locate a section B to the solicitation or any other pricing schedule. Can the government please clarify the pricing response requirements?

Answer 3: This reference will be removed. The government did not generate a pricing schedule. Refer to FBO announcement “Clause 252.204-7011 ALTERNATIVE LINE ITEM STRUCTURE - Contractor must submit their firm fixed priced proposal with an alternative line item structure that conforms to their practices to ensure the resulting contract structure is economically and administratively advantageous to the Government and the Contractor. The Virginia Army National Guard will not entertain a labor hour or time and material type contract except for specific line items for short-duration/quick reaction type requirements.” In other words, the government is not dictating the pricing schedule; the contractor is free to propose the line item structure that supports their proposal and is sustainable for payment through the life of the contract.

Question 4: Can you elaborate on the current interoperability (“incompatible with GEE”, Paragraph 1.5 Background) issues the current VANG COP has with external systems and data sources?

Answer 4: The VANG does not currently have an interactive COP that communicates with external systems. Previously, VDOT has attempted to share data with VANG to display on the VANG COP. However, VDOTs data was stored on a hard drive and due to DOD/VANG security policies external hard drives cannot be connected to DOD systems. Therefore, the data could not be uploaded. The VANG JOC is not using GEE due to the cost of the license. VANG JOC is using a free version of Google Earth.

Question 5: Are there translation issues with items such as location (e.g. problems with latitude and longitude), etc?

Answer 5: The VANG does not currently have an interactive COP. There are no known issues that would hinder translation. VANG JOC products are Microsoft Office based sent via NIPR email.

Question 6: What are the issues with trying to send data from the VANG COP to their federal and state partners?

Answer 6: The VANG does not currently have a shared COP. Data is pulled from various public sites and Powerpoint products are developed to merge/display the data. Currently, in order to share data from the VANG COP it must be transferred to disk and hand delivered to state partners to display via WebEOC (mapper). There is no seamless and efficient way to display VANG data (dynamic and static layers) to federal and state partners. Current constraints on sending and sharing data include Network Security, Network Access availability and various agency specific systems.

Question 7: Is there an incumbent contractor? If so can you please provide the name, contract number, award date, period of performance and award amount of the previous contract?

Answer 7: There is no incumbent contractor. The VANG has not previously had this service or capability.

Question 8: Does the VANG have a preference for a specific GIS viewer implementation?

Answer 8: The VANG does not have a preference for a specific GIS viewer implementation. Currently, Google Earth is being used.

Discussion (9): The solicitation specifies the contractor’s proposal discuss 1) Plan to ensure 99% uptime compliance (paragraph 2.2), 2) Capability limitations that will be experienced based on the network. Proposed INFRASTRUCTURE: Server systems will be hosted by VANG DOIM to run a virtual server that supports Keystone Exchange Core version 1.2 or greater, on Windows Server 2012V2. COP/SSA must be able to run across any network (3G/4G/LTE, WIFI, low bandwidth network, low data rate radios, etc.).

Question 9: Since knowledge of the VANG network specifics, physical architecture, historical availability, network bandwidth upload/download rates etc will provide a clear path for the most suitable solution, can the VANG provide detailed information, network topology diagram regarding the DOIM hosting facility virtualized XchangeCore environment; historical availability/downtime; network bandwidth/latency; I/O connections, load balancer; continuity of operations (COOP) etc in sufficient detail for the contractor to discuss plans to ensure 99% uptime compliance and address the requirement for COP/SSA to run across any network.

Answer 9: G6 will provide the virtual server to support Keystone Exchange core on a Windows Server 2012v2 or greater. VaARNG network maintains a 99.99% uptime. Network topology, COOP, bandwidth etc.are CIL and cannot be provided to the public. The contractor shall ensure 99% uptime of the system they develop outside the government architecture. The contractor would not be held liable for latency issues resulting from network/infrastructure issues outside the contractor’s control.

Discussion (10): Para 2.1.4 COP/SSA must be accessible from within the VANG enclave, as well as externally for those entities not located within the enclave (such as traditional soldiers or soldiers who are traveling on temporary duty). Software and data will be hosted within the VANG enclave or central office Question 10: Can the VANG provide details of the architecture and compute, storage, and network resources available within the VANG enclave or central office?

Answer 10: Network topology, COOP, bandwidth etc.. are CIL and cannot be provided to the public.

Question 11: Can the VANG describe the virtualized environment? Is it employing VMWare, vCenter and vSphere ESXi hypervisor or hyperV? Is it a nested hypervisor install or bare metal?

Answer 11: The VANG does not currently have the benefit of a virtualized environment.

Question 12: Will the VANG consider caching strategies and/or pre-load of GIS data to devices to mitigate low bandwidth latency issues?

Answer 12: The VANG will consider caching strategies and/or pre-load of GIS data.

Question 13: Does the VANG require HSIP LIMDIS to be securely wiped from any remote device after use for security purposes?

Answer 13: The VANG does require HSIP LIMDIS to be securely wiped from any remote device after use for secur6ity purposes.

Question 14: Can the VANG provide detailed information regarding the current status/architecture of the XchangeCore implementation? How many active sharing agreements / connections are in place? Is it a single XchangeCore configuration or a multiple XchangeCore configuration? Can the VANG provide a system level view graphic of the architecture?

Answer 14: There is no existing system in place.

Question 15: Did the VANG transition from the OpenDL LDAP authentication to a Microsoft Active Directory implementation?

Answer 15: Yes Question 16: For compatibility and usability does the VANG envision or prefer a 2D map, or 3D globe viewer?

Answer 16: The VANG prefers a 2D map.

Question 17: With which current government agencies does the VANG COP currently interface?

Answer 17: The VANG does not have an existing interfacing COP. The VANG COP does not regularly interface with any federal or state agencies that are listed in the statement of work. The VANG COP can be manually shared via VANG personnel at the VEOC with their assigned VANG computer (via DCS access). The VANG COP can be shared via DCS for DOD partners. Data is currently gathered and manipulated manually. The VANG is responsible for establishing the sharing agreements with other government agencies; the contractor will not be held accountable for pulling the data otherwise. The VANG feels there is sufficient public information available on the internet to still generate an initial product, e.g. weather, VDOT 511 etc.

Question 18: What is the GIS that "partners have migrated their COPs to an industry standard GIS based system which cannot be easily integrated with the VANG’s current COP"?

Answer 18: Refer to Answer 17.

Discussion: Federal Business Opportunities (FBO) states:

RESPONSE DEADLINES:

a. Questions shall be submitted in writing to susan.e.swanson5.civ@mail.mil not later than 4:00 p.m. ET, Tuesday, 6 September 2016.

b. Offer packages shall be submitted electronically to susan.e.swanson5.civ@mail.mil not later than the date and time specified in block 8 on page 1 of the SF1449 unless otherwise amended via a solicitation amendment (SF30) or directly on the Federal Business Opportunities (https://www.fbo.gov) webpage. Contractor is responsible for monitoring fbo.gov for any changes to the solicitation.

Question 19: Since the only date reference in FBO relates to when Questions are due, do you have a ballpark estimate of when the offer packages will be due?

Answer 19: The proposal due date will be changed to Friday, 9 September at 2:00 p.m. ET.

Question 20: When will the SF1449 be posted on FBO?

Answer 20: An SF 1449 was not posted. This requirement will be removed.

Question 21: Will you entertain any vendor demos to show existing capabilities that align with the requirements?

Answer 21: The contractor may provide links to products pertinent to a demonstration are acceptable. The VANG knows of no existing systems that are capable of providing a 100% solution for the VANG specific requirements. Other systems may serve as a solid platform a vendor can build upon/expand to incorporate the layers the VANG is requesting. The intent of this contract is to develop a customized Virginia National Guard solution.

Question 22: With which current government agencies does the VANG COP currently interface?

Answer 22: The VANG does not have an existing interfacing COP. The VANG COP does not regularly interface with any federal or state agencies that are listed in the statement of work. The VANG COP can be manually shared via VANG personnel at the VEOC with their assigned VANG computer (via DCS access). The VANG COP can be shared via DCS for DOD partners. Data is currently gathered and manipulated manually. The VANG is responsible for establishing the sharing agreements with other government agencies; the contractor will not be held accountable for pulling the data otherwise. The VANG feels there is sufficient public information available on the internet to still generate an initial product, e.g. weather, VDOT 511 etc.

Question 23: Is there an incumbent contractor and if so, who is the contractor and how long have they been supporting the VANG COP initiative?

Answer 23: There is no incumbent contractor. The VANG has not previously had this service or capability.