Q&A_Response_Package_-_Batch_4.pdf
PDF 90 KB Posted
- Solicitation number
- N00024-17-R-5216
About this file
Q&A Response Package - Batch 4
View the file
Other files
Show all 26
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DATE
QUESTION
NO. RFP REFERENCE/DISCUSSION (if necessary) QUESTION ANSWER
8/16/2017 4‐001 L.1.3 states "In accordance with DFARS 252.234‐7003, included in Section I of RFP, Offers shall submit the DD
Form 1921, Cost Data Summary Report, and DD Form
1921‐1, Functional Cost‐Hour Report.
DFARS 252.234‐7003 states that this solicitation should include "The Government‐approved cost and software data reporting (CSDR) plan for the contract, DD Form 2794". DD Form 2794 has not been included with this RFP. Please provide the DD
Form 2794 in order for the offers to complete the
DD Form 1921 and DD Form 1921‐1 appropriately.
RFP Amendment 2 removed DFARS 252.234‐
8/16/2017 4‐002 Attachment J‐11 tab 2e (WBS) states "Link each cell containing rates to appropriate cells in Worksheet 2f".
Is it the government's intent to have rates displayed in the spreadsheet or link rates in the excel formula ?
Rates shall be displayed in the spreadsheet and linked to worksheet 2f.
8/16/2017 4‐003 Attachment J‐11 tab 2e (WBS) has a column for "Cost
Element".
Is it the government's intent to have a row for each of the offeror's Cost Elements for each WBS?
The Offeror shall tailor the WBS worksheet depending upon the cost elements proposed.
8/16/2017 4‐004 SOW 4.1.7: Once the Contractor has successfully completed all FQT events, the Government shall perform formal Development Testing (DT) on the software at NUWC Newport, RI for submarine platform
ECDIS configurations and at NSWC PD for surface platform ECDIS configurations. Once the Government
Facilities DT is completed and all required SCCB identified SPIRs are corrected, Shipboard DT will be conducted in‐port and underway on selected U.S. Navy platforms to further validate each software builds.
Commander, Operational Test and Evaluation Force
(COTF) will be conducting independent Operational Test
(OT) of the software once the Government DT is successfully completed. The Contractor shall provide personnel to witness government testing at the labs and on the ships.
Personnel should have the required tools and documentation to be able to troubleshoot and document issues found for continuation of test events and to expedite SPIR resolution. For IMS purposes the
Contractor should assume 90 days for the IWS Land‐ based DT which includes a 30 day period to correct priority SPIRs. The Contractor should assume 30 days for IWS At‐Sea DT followed by 30 days for COTF OT.
Is the government Developmental Testing (DT) and
Operational Test (OT) to be conducted within the
24 month Period of Performance for CLIN 0001?
Yes
8/16/2017 4‐005 Section E, HQ E‐2‐0015 and SOW 4.1.4 Section E, references HQ E‐2‐0015 QUALITY
MANAGEMENT SYSTEM REQUIREMENTS (NAVSEA)
(APR 2017); Whereas SOW 4.1.4 references
QUALITY MANAGEMENT SYSTEM REQUIREMENTS
(NAVSEA)(SEP2009).
Is the Section E reference the correct date and
SOW 4.1.4 requires amending?
HQ E‐2‐0015 QUALITY MANAGEMENT
SYSTEM REQUIREMENTS (NAVSEA) (APR
2017) is the correct reference. SOW 4.1.4 was updated in Amendment 2.
8/16/2017 4‐006 L.3.1 Solicitation Response Requirements; the proposal deliverable CDRL Plans of L.4.2 2) Subfactors 2 thru 7
The Government has clearly stated the requirement from previous Q&A responses for 5‐ page plans for all but the SDP, where the page limitation was raised to 30. Additionally, the
Government has removed the word "Draft" from the submittal description, implying near complete plans and that the CDRL/DID is for guidance.
Since normally these plans are typically is excess of
50 pages each and in the case of the SDP upwards of 200 pages, single‐spaced, can the government provide their insight into the executable use of these significantly reduced‐sized plans?
Can the Government provided guidance of how the plans will be evaluated?
Section L.4.2 was revised to remove the expectation that the plans were to be submitted as a draft in accordance with the applicable CDRL. Section M.2.1 provides the guidance on how the plans will be evaluated.
Navy ECDIS Software Solicitation N00024‐17‐R‐5216 Questions
8/16/2017 4‐007 ECDIS SRD Rev 1.0 with Change 1, App J The hardware in the SRD (J3) describes a minimum
5th generation Intel i5 and a minimum Intel
Graphics Media Accelerator 4000. The 5th generation i5 does not support a 4000 series
Graphics media accelerator. Can the Navy please provide the correct target hardware? In addition, the 5th generation i5 has a wide variation in performance (# of cores, clock speeds, etc.). Can the Navy identify the target CPU(s) to ensure software will be compatible with hardware?
SRD Appendix J are minimum requirements for hardware. Paragraph J.3.2.1.1 states
"The processor will by default have the Intel
Graphics Media Accelerator 4000 or higher."
Where it is identified (as in this case), the offeror can design for a higher accelerator that is compatible with the other hardware components requirements and the offeror's software. Where the requirement is not specified, the offeror can specify those requirements that are compatible with the software design.
8/16/2017 4‐008 ECDIS SRD Rev 1.0 with Change 1, App J The hardware in the SRD (J3) describes an unknown graphics card. Can the Navy please provide the target graphics card(s) that the software is required to support?
SRD Appendix J are minimum requirements for hardware. Where the hardware requirement is unknown or not specified the offeror can specify the requirement based on the software design.
File details come from the government source that posted it. Updated .