N00024-18-R-5200_Question-Comments_12.13.17.xlsx
XLSX spreadsheet 21 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. NAVSEA is continuing to review the questions received and intends to post additional responses when they are available. Follow up questions may be submitted using the question/comment template previously provided in this notice (please be sure to indicate clearly which response to which the follow up question pertains).
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 |
| December 13, 2017 |
| Item No. | FBO Response Date | Source Document | Page Number | Section/Paragraph | Question/Comment | Proposed Action/Change | Government Response |
| 1 | 12/13/17 | Draft Solicitation Sections B, C, F | pg. 1 and 133 | Section B; item 0002 and Section C para 3.3.2 | Will the government provide a list of the GFP that is to be managed? | Provide a list of GFP. | A full list of GFP will be provided as an attachment to the formal solicitation. |
| 2 | 12/13/17 | Draft Solicitation Sections B, C, F | pg. 6 - 8 and pg. 126. | Section B; items 0017 - 0024 and Section C para 3.2.2. | Will sample tasks be included as part of the RFP? | Clarify how these CLINs will be evaluated in the RFP. | Sample tasks will not be included in the RFP. Sections L and M will provide guidance on proposal submission and CLIN evaluation. |
| 3 | 12/13/17 | Draft Solicitation Sections B, C, F | pg. 9 - 10 and pg. 126 | Section B; items 0025 - 0032 and Section C para 3.2.3. | What is the level of effort associated with these ad hoc deliveries? | Clarify level of effort. | The Government will define the number of hours under level-of-effort CLINs that Offerors must propose as part of the formal solicitation. After contract award, the specific level-of-effort required under the referenced line items will be specified in Technical Instructions issued by the Government. |
| 4 | 12/13/17 | Draft Solicitation Sections B, C, F | pg. 65 - 66 | Section C, para 2.2 | Are the referenced NAVSEA and PEO IWS documents available to bidders? | Provide documents. | NAVSEA and PEO IWS documents are available to bidders in the CEC Bidder's Library.Please refer to the FBO notice for instructions on accessing the Library. If a document is believed to be missing, please advise. |
| 5 | 12/13/17 | Draft Solicitation Sections B, C, F | pg. 90 | Section C, para 3.1.4.7 and 3.1.4.8 | CDRL A048 is labeled "TEMPEST Control Plan" in paragraph 3.1.4.7 and "Spectrum Certification Spectral Characteristics Data" in paragraph 3.1.4.8. | Clarify CDRLs. | This is a typographical error; CDRLs will be correctly numbered in the formal solicitation. |
| 6 | 12/13/17 | Draft Solicitation Sections B, C, F | pg. 91 and 92 | Section C, para 3.1.4.14 and 3.1.5.1 | CDRL A050 is labeled "Installation Control Drawings" in paragraph 3.1.4.14 and "Test Plans/Test Procedures, Master Test Plan" in paragraph 3.1.5.1. | Clarify CDRLs. | This is a typographical error; CDRLs will be correctly numbered in the formal solicitation. |
| 7 | 12/13/17 | Draft Solicitation Sections B, C, F | pg. 92 | Section C, para 3.1.5.1.3 | CDRL A052 is listed twice - once as "Test/Inspection Report" and a second time as "Test Plans/Test Procedures, Formal Qualification Test (FQT)" | Clarify CDRLs. | This is a typographical error; CDRLs will be correctly numbered in the formal solicitation. |
| 8 | 12/13/17 | Draft Solicitation Sections B, C, F | pg. 93 and 94 | Section C, para 3.1.6.1 and 3.1.6.2 | Para 3.1.6.1 shows CDRL A054 as "QAPP" and para 3.1.6.2 shows CDRL A055 as "QAPP". Subsequent CDRLs are miss-numbered. | Clarify CDRLs. | This is a typographical error; CDRLs will be correctly numbered in the formal solicitation. |
| 9 | 12/13/17 | Draft Solicitation Section C | Pg. 80 | 3.1.1.1 | Section C lists Program Manager and Technical Director. Will the Government be specifying minimum qualifications for these positions? Will these be the only key personnel identified by the Government? | Recommend that Government allow Industry to select key personnel consistent with their technical approach. | Minimum qualifications of the key personnel will be identified in the formal solicitation. Section C contains a full list of key personnel required by the Government. |
| 10 | 12/13/17 | Draft Solicitation Section F | Pg. 157 | General | Will the Government be providing details of schedule requirements? Is there a master program schedule available for major program milestones? | Recommend that the Government provide detailed program schedule with milestones. | Schedules are are available to bidders in the CEC Bidder's Library and will be updated for the formal solicitation. Please refer to the FBO notice for instructions on accessing the Library. If a document is believed to be missing, please advise. |
| 11 | 12/13/17 | Draft Solicitation Section C | Pg. 68 | 3 | Section C does not list GFE/GFI explicitly including Government equipment that may need to be placed at contractor facilities. Will these be provided separately? | Recommend detailed listing of GFE and GFI. | A full list of GFP/GFE/GFI will be provided as an attachment to the formal solicitation. |
| 12 | 12/13/17 | Draft Solicitation Section C | General | General | Will the Government define specific CEC product deliveries (e.g., expected releases, maintenance frequency, etc.)? | Recommend that the Government provide system delivery and other key milestones for all contractors to have a common basis for bidding. | Schedules are are available to bidders in the CEC Bidder's Library and will be updated for the formal solicitation. Please refer to the FBO notice for instructions on accessing the Library. If a document is believed to be missing, please advise. |
| 13 | 12/13/17 | Draft Solicitation Section C | General | General | Integration of the CEC system with E2-D Advanced Hawkeye - this integration effort is mentioned in the FBO notice but not in Section B or C. Is this to be accomplished as part of Advanced Studies for NAVAIR? | Recommend clarification on the extent of integration needed. | The Government anticipates that the E2-D integration will be completed under Advanced Studies and/or Future Software Capability Enhancements and Hardware Technology Refresh LOE Tasks. |
| 14 | 12/13/17 | Draft Solicitation Section C | Pg. 7 | CLIN 0016 | Completion of Zumwalt Class wholeness - Per FBO announcement, the contemplated contract may include support for Zumwalt class. Section C does not seem to provide any specifics or work scope (other than identification of Advanced Studies - Zumwalt). Without the LOE details, it is not clear what type of work or labor categories will be needed. | Recommend additional detail on scope. | The Government anticipates that the Zumwalt integration will be completed under Advanced Studies and/or Future Software Capability Enhancements and Hardware Technology Refresh LOE Tasks. |
| 15 | 12/13/17 | Draft Solicitation Section C | Pg. 7 | General | CLIN Structure - The provided CLIN and Section C structure seems to be very complex and requires common elements to be addressed in multiple locations making the process of generating basis of estimates very involved and potentially making the Government evaluation onerous. For example, CLIN 0001 references C.3.3.1 and then under the fourth level of indentation (3.3.1.1), it references 3rd level Section C tasks (3.1.1, 3.1.2, etc.) | Recommend that the Government consider a simplified CLIN structure for ease of estimating and evaluation. | The Government will take the recommendation under advisement for the development of the formal solicitation. |
| 16 | 12/13/17 | Draft Solicitation Section C | Pg. 8 | General | Due to the complex scope provided in Section C, technical approach and compliance in the technical proposal for all scope sections may be cumbersome for contractors to develop and for the Government to evaluate. | Recommend that the Government consider focused technical approach evaluations, e.g. with the use of sample tasks or for narrow scope areas. Recommend providing draft Sections L and M to potential offerors prior to solicitation for their review and comment. | The Government has posted a draft version of Section L of the solicitation to FBO and will take the other recommendations under advisement for the development of the formal solicitation. |
| 17 | 12/13/17 | Draft Solicitation Section B | Pg. 13 | CLINS 0001 - 0008 | In order to assess the appropriateness of CPIF CLINs, it would be helpful to understand the details of the incentive criteria anticipated by the Government. | Recommend Government provide the details of the incentive fee plan, including incentives, evaluation criteria, etc. | The Government does not currently anticipate any incentive criteria beyond the standard cost incentive for CPIF line items. |
| 18 | 12/13/17 | Draft Solicitation Section C | Pg. 96 | 3.1.7.1 and 3.1.7.2 | CDRL A056 and CDRL A057 are both called out as SUPPLIER’S CONFIGURATION MANAGEMENT PLAN. | Clarify CDRL numbering. | This is a typographical error; CDRLs will be correctly numbered in the formal solicitation. |
| 19 | 12/13/17 | Draft Solicitation Section C | Pg. 110 | 3.1.9.1 and 3.1.9.2 | CDRL A079 and CDRL A080 are both called out as CDRL A079 – RELIABILITY AND MAINTAINABILITY (R&M) PROGRAM PLAN. |
Similarly, there are other duplicate numbering instances:
CDRL A095 – OPERATIONS SECURITY (OPSEC) PLAN, SYSTEMS SECURITY MANAGEMENT PLAN (SSMP)
CDRL A096– COUNTERFEIT PREVENTION PLAN
CDRL A097 – OPERATIONS SECURITY (OPSEC) PLAN, SYSTEMS SECURITY MANAGEMENT PLAN (SSMP)
| CDRL A098 – COUNTERFEIT PREVENTION PLAN | Clarify CDRL numbering. | This is a typographical error; CDRLs will be correctly numbered in the formal solicitation. | ||
| 20 | 12/13/17 | Draft Solicitation Section C | Page 90 |
Page 143 Paragraph 3.1.4.8 Paragraph 3.3.7.1.2
| Paragraph 3.3.7.2.2 | Many CDRLs are called out in section 3.1 (common tasks) and again in section 3.3 (completion tasks). For example, CDRL A042 Tempest Test Plan is called out in paragraph 3.1.4.8 (common tasks) and again in paragraphs 3.3.7.1.2 and 3.3.7.2.2 (completion tasks). This appears to be a duplication of effort if the CDRL is quoted in both the common tasks and completion tasks. | Clarify how the CDRLs and work activities in the common tasks are to be allocated to the completion tasks. | CDRLs and associated delivery dates will be clarified in the formal solicitation. | |||
| 21 | 12/13/17 | Draft Solicitation Section C | Pg. 70 | 3.1.1.5.1 and .2 | Section C requires offerors to implement EVMS for both completion and LOE tasks. |
a) Since LOE tasks generally do not have schedule details in the Integrated Master Schedule (IMS) (similar to completion tasks), does the Government still want to impose EVMS requirements for LOE tasks?
| b) If so, will offerors have the flexibility to scale down the EVMS implementation effort appropriate for LOE tasks. | Recommend that Government provide additional detail on EVMS requirements as related to LOE tasks or provide language allowing offerors to appropriately tailor implementation of EVMS. | The Government intends to impose EVMS requirements on specific LOE tasks. The EVMS requirements, if any, will be described in the Technical Instruction for each LOE task. The Government anticipates including EVMS requirements on any software developments or system tech refresh/obsolescence updates efforts executed under TIs. | ||||
| 22 | 12/13/17 | Draft Solicitation Section C | Pg. 70 | 3.1.1.5.2 | “For LOE Tasks, the Contractor shall utilize the EVMS established in Section C, paragraph 3.1.1.5.1, as directed by each approved TI.” |
a) Can the Government describe what typical requirements may be anticipated in a TI for LOE tasks?
| b) Will there be specifics on the extent to which EVMS needs to be applied? | Recommend that the Government provide additional clarification on TIs. | The Government intends to impose EVMS requirements on specific LOE tasks. The EVMS requirements, if any, will be described in the Technical Instruction for each LOE task. The Government anticipates including EVMS requirements on any software developments or system tech refresh/obsolescence updates efforts executed under TIs. | ||||
| 23 | 12/13/17 | Draft Solicitation Section B | Pg. 1 | General | CLIN structure: |
a) Is the Government’s intent that offerors manage each CLIN independently?
b) Assuming that all CLINs will be executed simultaneously, will offerors have the flexibility to manage costs across CLINs?
c) Or are their color of money restrictions for how each CLIN’s budget should be managed? Recommend additional detail and clarification of CLIN structure and Government’s expectations for management. a) Each CLIN stands on its own as an independent line item. The Government expects that Offerors manage CLINs in a manner that promotes maximum efficiency while conforming with contract requirements.
b) Unless otherwise stated in the contract, the Government does not guarantee that any option CLINs will be exercised. Offerors must manage CLINs in accordance with the contract requirements.
c) The Government will ensure that the contract CLIN structure supports the expected funding profile.
| 24 | 12/13/17 | Draft Solicitation Section B | Pg. 1 | General | Will configuration change notices (CCNs) be included in the bidder's library? | Recommend including | Some ECPs and SCNs are included in the CEC Bidder's Library for informational purposes. All ECPs and SCNs related to currently in-service platforms will be provided to the successful Offeror following contract award. |
| 25 | 12/13/17 | Draft Solicitation Section B | Pg. 1 | General | What is the anticipated schedule for the draft and final RFP release? | Provide schedule estimates | The Government released the draft solicitation on October 17, 2017. The formal solicitation will be issued no earlier than calendar year 2018. |
| 26 | 12/13/17 | Draft Solicitation Section B | Pg. 1 | General | Will the Network Architecture Document be included in the bidder's library? | Include in the bidder's library | The Government intends to include the Network Architecture Document in the CEC Bidder's Library with the release of the formal solicitation. |
| 27 | 12/13/17 | Draft Solicitation Section B | Pg. 1 | General | Will the current System Threat Assessment Report (STAR) be included in the bidder's library? | Include in the bidder's library | The Government does not currently anticipate including the System Threat Assessment Report in the CEC Bidder's Library. |
| 28 | 12/13/17 | Draft Solicitation Section B | Pg. 1 | General | Will waivers and deviations be included in the bidder's library? | Include in the bidder's library | Some waivers and deviations are included in the CEC Bidder's Library. All waivers and deviations related to currently in-service platforms will be provided to the successful Offeror following contract award. |
| 29 | 12/13/17 | Draft Solicitation | 65 | 1.0 | The second sentence of the first paragraph references a Technical Data Package which outlines the required software baselines that need to be supported for this solicitation. When will the TDP be available for use in determining the needed support? | Request TDP be provided. | The TDP was provided as part of the CEC Bidder's Library. It will be updated as necessary for the release of the formal solicitation. |
| 30 | 12/13/17 | Draft Solicitation | 69 | 3.1.1.3 | The paragraph states "The Contractor shall provide CEC program support by coordinating with other organizations (including PEO IWS 1, 2, 4, 7, 9, 10, 11, Warfare Centers, Prime Contractors and their Subcontractors) involved in the development, verification, support, maintenance, production, and training for CEC software and hardware and organizations (or their cognizant prime contractors) developing or having interfaces with CEC systems." However training is not indicated as part of the scope in paragraph 3.1 and development of an Operational Security (OPSEC) Training Manual in paragraph 3.1.8.17. Is training a provision to be provided by the Contractor as Design Agent? | Please clarify if training is within the scope of this contract. | Section C, paragraphs 3.1.8.22 and 3.1.8.23 detail the training requirements. |
| 31 | 12/13/17 | Draft Solicitation | 85 | 3.1.3.17 | This paragraph requires the specific use of the CEC Wrap-Around Simulation Program. Will the contractors have access to that program in order to identify the depth of Modeling & Simulation required to use the CEC WASP in execution of all tests? | Please clarify | A WASP user's guide was provided in the CEC Bidder's Library. The Government does not anticipate providing the WASP until after contract award. |
| 32 | 12/13/17 | Draft Solicitation | 88 | 3.1.4.5 | This paragraph requires "The Contractor shall maintain and update the overall hardware configuration baseline." Has such a baseline been established to date and will that baseline be available as part of the bidder's library? | Provide requested data in bidder's library | A hardware baseline exists. Several versions of the hardware have been included in the CEC Bidder's Library. |
| 33 | 12/13/17 | Draft Solicitation | Is the government going to provide bidders access to the most recent delivery of CEC source code as part of the bidder's library? | Provide requested data in bidder's library | The CEC Bidder's Library contains source code and build files. A more recent build will be provided in the Bidder's Library with the formal solicitation. | ||
| 34 | 12/13/17 | Draft Solicitation | 75 | 3.1.1.11.3 | This section states "For LOE tasks, the requirements of Section C, paragraphs 3.1.1.11.1 and 3.1.1.11.1.1 through 3.1.1.11.1.6 apply as directed by each approved TI". Sections 3.1.1.11.1.1 through 3.1.1.11.1.6 do not exist. | Recommend correction to SOW. | This is a typographical error; paragraph references will be corrected in the formal solicitation. |
| 35 | 12/13/17 | Draft Solicitation | 81 | 3.1.2.15 | This paragraph states "The Engineering Notebook shall be made available to the Government in near-real time to facilitate understanding of the decisions made in the development process." Can the government clarify what near-real time constitutes in this context? | Please clarify the meaning of "near-real time". | The delivery timeframe for this CDRL will be provided in Exhibit A of the formal solicitation. |
| 36 | 12/13/17 | Draft Solicitation | 84 | 3.1.3.11 | Will the Virtual Development Environment store or provide access to any classified data? | Please clarify if there will be a separate classified VDE required by the government. | The VDE must support both classified and unclassified development. |
| 37 | 12/13/17 | Draft Solicitation | various | various | There are significant references to government plans and data throughout the RFP, which the contractor believes should be part of the bidders library. Since the initial tranche of data will be provided by disk, is there a mechanism for bidder's library updates during the RFP period? | Please clarify | The Government intends to update the CEC Bidder's Library with additional documents to support the formal solicitation. |
| 38 | 12/13/17 | Draft Solicitation | Pg. 1 | Section B | For the Completion CLINs, the Share Ratio Above Target and the Share Ratio Below Target are not identified. | Please provide the Share Ratio Above Target and Share Ratio Below Target for the Completion CLINs in the Final RFP package. | The incentive parameters of CPIF CLINs will be included in the formal solicitation. |
| 39 | 12/13/17 | Draft Solicitation | Pg. 71 | 3.1.1.8.2 | Paragraph 3.1.1.8.2 covers Rolling Wave Planning yet the IBR is referenced in the third sentence of the Paragraph; this appears to be copy/paste error from Paragraph 3.1.1.8.1. | Recommend deletion of the third sentence in Paragraph 3.1.1.8.2 as demonstrated below: |
| "As TIs are executed and LOE tasks are planned, the Contractor shall work with the Government team to conduct Rolling Wave Planning events for the purpose of evaluating the risks inherent in adding work to the contract’s planned PMB. Rolling Wave Planning events are dependent on execution of TIs, but may be held every six (6) months. The IBR shall verify that the Contractor is using a reliable PMB which includes the entire scope of the new effort, is consistent with contract schedule requirements, and has adequate resources assigned. The prime Contractor shall lead the subcontractor Rolling Wave Planning events, with active participation by the Government." | The Government has revised the referenced section to read as follows: "The Rolling Wave Planning events shall verify that the Contractor is using a reliable PMB which includes the entire scope of the new effort, is consistent with contract schedule requirements, and has adequate resources assigned." Note that this language is not final and is subject to change in the formal solicitation. The Government invites comments regarding the updated language. | |||||
| 40 | 12/13/17 | Draft Solicitation | Pg. 126 | 3.2.1.1 | ||
| Paragraph 3.2.1.1. discusses the scope for FRACAS and FRB, however 3.2.1 is for Advanced Studies work. | Please move 3.2.1.1 to the Post-Delivery Support Paragraph as 3.2.4.4. | This paragraph will be moved to 3.2.4.4 in the formal solicitation. | ||||
| 41 | 12/13/17 | Draft Solicitation | Multiple | Section B | The Pre-Solicitation notice states that the contemplated contract will include integration of the CEC system with the AEGIS Advanced Capability Build 20 (ACB20), integration of the CEC system with SSDS ACB20, and integration of the CEC system with E2-D Advanced Hawkeye. While the Draft RFP contains a Completion CLIN (0001) for integration of the CEC System with AEGIS ACB20, there is not a Completion CLIN for integration of the CEC system with SSDS ACB20 or integration of the CEC system with E2-D Advanced Hawkeye. Additionally, the Draft RFP includes multiple LOE CLINs for Zumwalt activities, USMC capabilities, and FMS customer platforms while the Pre-Solicitation notice states that the contemplated contract will include Completion of Zumwalt Class wholeness, testing of the CEC system with United States Marine Corps capabilities and integration of the CEC system with FMS customer platforms. |
| Accordingly, the only major Completion task identified in the Draft RFP (CLIN 0001 AEGIS ACB20) does not reflect what it takes to ensure end-to-end performance of the CEC system, including interoperability, testing, and engagement. This represents a significant risk to the Government’s CEC Program in its entirety since the CEC Program execution cannot be evaluated against only integration of the CEC System with AEGIS ACB20. | Recommend incorporation of Completion CLINs for integration of the CEC with SSDS ACB20 and E2-D Advanced Hawkeye. Additionally, recommend changing the LOE CLINs for Zumwalt Class Wholeness and USMC efforts to Completion CLINs. | |||||
| Completion CLINs require well defined entrance and exit criteria. The Government welcomes industry feedback on the level of definition required to support completion tasking and whether the documentation available for the referenced CEC requirements meets the standards. | ||||||
| 42 | 12/13/17 | Draft Solicitation | Multiple | Section C | There are instances throughout the Draft SOW where the same CDRL number contains multiple titles or where the same CDRL title contains a different number. Examples are below: |
CDRL A031
Section 3.3.3.1 : SOFTWARE TRANSITION PLAN (STRP) Section 3.1.4.3: Engineering Drawings
CDRL A032:
Section 3.1.4.4: Engineering Drawings Section 3.1.4.5: Technical Data Package
CDRL A033:
Section 3.1.4.6: Technical Data Package
| Section 3.1.4.7: ELECTROMAGNETIC ENVIRONMENTAL EFFECTS (E3) INTEGRATION AND ANALAYSIS REPORT (E31AR), EMC PROGRAM PLAN (EMCPP) | It is recommended that the Final SOW address the inconsistencies between CDRL Number/Title and Titles/CDRL Number. | The Government will correct CDRL numbering in the formal solicitation. | ||||||
| 43 | 12/13/17 | Draft Solicitation | All | All | While the Draft RFP contains Completion scope, it does not reflect the complexities of the total technical requirements, including compliance with the CEC System Specification and all other requirements of the CEC system for integration and fielding of the CEC. On recent relevant proposals, such as AEGIS CSEA and SSDS CSEA, sample problems were used across the board to evaluate technical competency. If sample problems are not included, the Government will be unable to accurately assess an Offeror’s competency to meet CEC emergent needs. | Recommend that the Final RFP include Completion criteria and sample problems requiring Offerors to sufficiently detail and clearly demonstrate how its technical solution integrates with all platforms in the CEC network, including legacy fielded systems, and future capabilities to maintain a single integrated air picture. | A sample problem will be included in Sections L and M of the formal solicitation. | |
| 44 | 12/13/17 | Draft Solicitation | All | All | Currently the Draft RFP does not contain clearance requirements for Key Personnel at time of award. | Recommend that the Final RFP include a requirement for Key Personnel such as the Principal Program Manager, Deputy Program Manager, Chief Engineer, and Chief Architect to have Top Secret clearances at time of award. | Minimum qualifications of the key personnel will be identified in Section L of the formal solicitation. | |
| 45 | 12/13/17 | Draft Solicitation Section C | General | General | Will the Government be including sample technical tasks as part of the evaluation criteria? Will these sample tasks be awardable? | Recommend that the Government provide details of sample tasks. Recommend Sections L and M include priced sample tasks that enable evaluation of technical understanding and cost realism for specific anticipated work. | A sample problem will be included in Sections L and M of the formal solicitation. | |
| 46 | 12/13/17 | Draft Solicitation Section B-C-F | pg. 4 - 6 and pg. 126. | Section B; items 0009 - 0016. Section C para 3.2.1. | Will sample tasks be included as part of the RFP? | Clarify how these CLINs will be evaluated in the RFP. | The Government does not anticipate including sample tasks as part of the evaluation. Sections L and M of the formal solicitation will provide guidance on proposal submission and evaluation criteria. | |
| 47 | 12/13/17 | Draft Solicitation Section B-C-F | pg. 10 - 12 and pg. 127 | Section B; items 0033 - 0040 and Section C para 3.2.4. | What is the level of effort associated with these post delivery activities. | Clarify level of effort. | The Government will define the number of hours under level-of-effort CLINs that Offerors must propose as part of the formal solicitation. After contract award, the specific level-of-effort required under the referenced line items will be specified in Technical Instructions issued by the Government. |
File details come from the government source that posted it.