N00024-18-R-5200_Question-Comments_4.18.18.xlsx
XLSX spreadsheet 16 KB Posted
- Solicitation number
- N0002418R5200
About this file
This package contains an Excel spreadsheet that provides responses to questions received from industry in connection with this procurement.
View the file
Other files
Show all 36
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
Template
| Solicitation N00024-18-R-5200 |
| Cooperative Engagement Capability Design Agent/Engineering Services |
| Government Responses to Questions and Comments From Industry |
| April 18, 2018 |
| Item No. | FBO Response Date | Source Document | Page Number | Section/Paragraph | Question/Comment | Proposed Action/Change | Government Response |
| 1 | 4/18/18 | Draft RFP | Pg. 136 | Section C 3.3.2.4 | Does the Government intend to include a transition plan requirement as part of the proposal? Since there is a significant amount of legacy work that is ongoing, how will the Government provide transition of existing software, hardware, and software development and maintenance artifacts to the incoming contractor? |
| Additionally, there are requirements for various facilities and infrastructure - are these required to be in place at the time of award or will the Government consider a transition period. For example, Section 3.1.3.9 requires an Integrated Computer-Aided Software Engineering (ICASE) SDE, 3.1.3.11 requires a Virtual Development Environment, and Section 3.3.2 requires the contractor provide a training classroom. As another example, Section 3.3.2.4 allows the on-site Government Office Space to be made available within sixty days of contractor award versus immediately upon award. | Recommend inclusion of a 60- to 90-day transition plan including identification of details of software and hardware infrastructure turnover such that non-incumbent contractors have a fair opportunity to bid and provide contract support. | The formal solicitation will require Offerors to propose a transition plan. To aid offerors in the development of a proposal, the Government intends to provide information about the transition period and schedule in the Bidder's Library. | ||||||
| 2 | 4/18/18 | Draft RFP | Pg. 1 | General | Which, if any, Government owned assets currently at the incumbent's facility can be transferred/leveraged during program execution? | Provide a list of Government owned assets currently at the incumbent's site that can be leveraged during program execution | The formal solicitation will include a GFP attachment that describes the assets available and the associated transition dates and phases. | |
| 3 | 4/18/18 | Draft RFP | 81 | Section C 3.1.3.1.1 | This paragraph states "The Contractor shall use formal procedures to provide software size, cost, and schedule estimation." Can the government clarify what procedures are acceptable? | Please clarify what software estimation tools are specified, or if bidder has flexibility to choose the tool set used. | The Government anticipates allowing Offerors to proposed the tool set used. The proposed tools must meet the requirements of the solicitation. | |
| 4 | 4/18/18 | Draft RFP | 73 | Section C 3.1.1.11.2 | This paragraph indicates that transition strategies will be discussed at the post-awardee kickoff meeting. Will the incumbent be required to bid equivalent transition costs? | Please clarify | The solicitation does not include a separate line item for transition efforts. All Offerors must propose applicable transition costs in the pricing for the appropriate line items containing transition efforts. All Offerors will propose pricing for the same set of line items. | |
| 5 | 4/18/18 | Draft RFP | Pg. 118 | 3.1.14 | This paragraph states that "The Contractor shall also implement the cybersecurity requirements documented within PEOIWSINST 5239.1, PEO IWS Surface Navy Combat System Cybersecurity, Enclosure 1 - PEO IWS Enclave Cybersecurity Requirements and ensure all aspects of DoD and Navy specific cybersecurity policies and processes are followed." however it is unclear which requirements apply to the Completion Scope. For example, it is unclear which requirements apply to the CEC ACB-20 Completion scope under CLIN 0001 (i.e. all, only the ELC requirements, or some other subset). | Please provide PEOIWSINST 5239.1, Enclosure 1 requirements that are allocated to CEC for ACB-20 Completion scope in the Bidder's Library. | The Government will provide PEOIWSINST 5239.1, Enclosure 1 in the Bidder's Library accompanying the formal solicitation. | |
| 6 | 4/18/18 | Draft RFP | Pg. 86 | Section C 3.1.3.25 | This Paragraph requires the Contractor to deliver Computer Software Product including " . . .fully paid, transferrable licenses. . .". What are the licenses that need to be purchased and delivered with the Computer Software Product for both the Completion and LOE Tasks? | Recommend the Final RFP contain a list of all licenses that need to be purchased, delivered, and maintained for the Completion and LOE tasks. | The contractor is required to provide any licenses necessary for the Government to take ownership of delivered software. Offerors bear the responsibility of determining which licenses are necessary to fulfill this requirement. | |
| 7 | 4/18/18 | General | NA | NA | Can the Government provide both forecast average and historical levels of effort by CLIN? | Provide requested data. | The Government does not anticipate providing the requested information. However, the formal solicitation will include a notional skill mix for LOE line items that Offerors must use. | |
| 8 | 4/18/18 | Draft RFP, Section L | pg. 7 | Volume I: Factor 1 - Technical Approach | "The Government intends for Volume I to be a targeted discussion of the Offeror’s proposed approach to performing each of the CLINs." |
| What is the Government's expectation for approach to perform each CLIN? Also, these instructions do not seem to be consistent with the remaining Volume I instructions which are targeted at specific topics, such as software development approach, system engineering process, etc.? Discussing each CLIN and associated technical approach will take up a lot of pages due to the large number of CLINs specified by the Government. | Recommend that this requirement be removed or further clarified with appropriate page allocation to discuss each CLIN. If the Government does intend to retain this requirement, please provide detailed instructions on the expected content for approach to performing each CLIN while removing any duplication with the requested approach for Volume Elements. | The formal solicitation will clarify these requirements. The Government does not intend for Offerors to discuss each CLIN individually, but the Offeror should address and explain any differences in approach across CLINs. | ||||||
| 9 | 4/18/18 | Draft RFP, Section L | pg. 9 | Transition Plan and Startup | What is the transition period anticipated by the Government? For a complex program, transition periods can vary between 60 and 120 days to allow non-incumbents a fair opportunity to ramp up support and staffing. | Recommend that the Government provide adequate transition period to allow non-incumbents to bid. | The formal solicitation will require offerors to propose a transition plan. To aid offerors in the development of a proposal, the Government intends to provide information about the transition period and schedule in the Bidder's Library. | |
| 10 | 4/18/18 | Draft RFP Section C | NA | 3.1.8.1 | Can the Government provide a description of the "existing logistics support resources" referenced in the first bullet | Provide a description. | The language in the formal solicitation has been updated to more clearly define the requirement. Examples of support resource documentation include, but are not limited to: TDPs, Allowance Parts List, and IETMs. | |
| 11 | 4/18/18 | Draft RFP Section C | NA | 3.3.1.3.1 | Can the SDP-S Tech Refresh Data Package be provided as GFI? | Provide as GFI | The SDP-S Tech Refresh Data Package cannot be provided as GFI for the formal solicitation; the formal solicitation Bidder's Library will contain alternative technical data to support development of a proposal. | |
| 12 | 4/18/18 | Draft RFP, Section L | pg. 15 | Facility | "The Offeror shall describe any Government facilities that will be required to meet any SOW requirements. " | |||
| Will the Government specify what the facilities are? | Specify government facilities current used for this effort. | The Government intends to provide in the formal solicitation a listing of Government-furnished facilities required to accomplish the contract requirements. | ||||||
| 13 | 4/18/18 | Draft RFP, Section L | pg. 9 | System Engineering Process | Section L states "The Offeror shall demonstrate its understanding of what will be required to support the Integrated Product Teams (IPT) and Working Groups (WG) defined in the Section C, paragraph 3.1.1.11.3, Integrated Product and Process Development (IPPD), and its subparagraphs." How may IPTs and WGs are there? How frequent do they meet? | Clarify the number of IPTs and WGs. Clarify meeting frequency. | The requested information is contained in the SEP, which is available in the Bidder's Library. | |
| 14 | 4/18/18 | Draft RFP | NA | NA | During Industry Day, the Government presented future CEC technology development paths. These are not included in the current Draft RFP, Section C. Draft RFP Section L does not provide guidance to describe our capabilities in future technology areas. | Please provide guidance as to how the government will evaluate the contractor's ability to address future capabilities needs. Request the government develop several sample tasks that address these new technology developments for CEC. | The actual development of the referenced capabilities is outside of the scope of this contract. These capabilities will be developed initially on a separate contract and delivered to the Government at TRL 6 for maturation and integration at some point in the future. The maturation and integration efforts may occur under this contract. | |
| 15 | 4/18/18 | Draft Section L | Pages 13-15 | Management Approach | Volume III: Factor 3 - Management Approach lists 12 elements for offerors to describe, but the order in which they are listed does not appear to topically group the elements. This may result in proposal responses that jump around from organization-related to schedule-related back to organizational then on to schedule again and then risk as offerors follow the sequence presented in draft Section L. Going back and forth between topics may make it more difficult to follow related threads through responses and thus more difficult to evaluate offerors' information. | We suggest the following order to create a better topical flow for reading and evaluating the Elements in the Management Approach volume: |
- Program Management
- Program Organization
- Organizational Structure
- Interfacing with Government and Other Stakeholders
- Contract-wide Staffing Plan
- Subcontractor Management / Small Business -- Small Business Subcontracting Plan (as attachment to specified volume)
- Contract-wide Integrated Master Schedule (IMS)
- Contract-wide Contract Work Breakdown Structure (CWBS)
- Performance, Cost, Schedule and Risk
- Risk Management
- Quality Assurance
| - Facility | The Government will take the recommendation under advisement for the development of the formal solicitation. | |||||
| 16 | 4/18/18 | Section L | Page 7 | Volume I: Factor 1 - Technical Approach. First paragraph. | The first sentence of the Technical Volume paragraph of Section L states: "The Government intends for Volume I to be a targeted discussion of the Offeror’s proposed approach to performing each of the CLINs. " |
This indicates that the Government intends to evaluate an Offerer's technical competencies by CLIN; however, the first paragraph does not provide a specific "shall" statement to direct such a structured format.
Recommend adding a second sentence in the first paragraph under Volume I: Factor 1 - Technical Approach, such that the beginning of the paragraph reads as follows:
"The Government intends for Volume I to be a targeted discussion of the Offeror’s proposed approach to performing each of the CLINs. Accordingly, the Offeror shall provide its technical approach for each of the CLINs followed by its approach for each of the items under the ELEMENTS section below."
| Also recommend the four "must be" references in the first paragraph be revised to "shall be". | The formal solicitation will clarify these requirements. The Government does not intend for Offerors to discuss each CLIN individually, but the Offeror should address and explain any differences in approach across CLINs. | |||||||
| 17 | 4/18/18 | Bidder's Library | N/A | N/A | Is our assumption that the software on the classified disk is a small subset of the entire CEC code base correct? | N/A | Yes, the data provided is a subset of the entire CEC code base. | |
| 18 | 4/18/18 | Classified Bidder's Library / AEGIS ACB20 Naval Capabilities Document Requirements Compliance Matrix ; | ||||||
| Unclassified Bidder's Library / Security Classification Guide | N/A | N/A | The unclassified bidders library contains a Security Classification Guide (CEC_SCG_13 OPNAVINST S5513.3B) dated 5/1/2008. This SCG is silent on Cybersecurity topics. The classified bidders library contains an AEGIS ACB20 Naval Capabilities Document (NCD) Requirements Compliance Matrix containing cybersecurity information. This Matrix is marked secret but offers no classification guidance for specific cybersecurity information. | Provide an updated SCG containing marking guidance for Cybersecurity topics. | The CEC_SCG_13 OPNAVINST S5513.3B provided in the Bidder's Library is the most recent version of the SCG. |
File details come from the government source that posted it.