Exhibit A - GPNTS Software DD-1423 CDRLs.pdf
PDF 1 MB Posted
- Attached to
- Global Positioning System (GPS)-based Positioning, Navigation, and Timing Service (GPNTS) Software Support Federal contract opportunity
- Solicitation number
- N00039-19-R-0005
About this file
This document outlines a forthcoming solicitation for Global Positioning System (GPS)-based Positioning, Navigation, and Timing Service (GPNTS) software support services. Key details include:
-
The Space and Naval Warfare Systems Command (SPAWARSYSCOM), in support of the Program Executive Office for Command, Control, Communications, Computers, and Intelligence (PEO C4I), Communications and GPS Navigation Program Office (PMW/A 170), intends to release Request For Proposal (RFP) N00039-19-R-0005 in Q1FY19 for GPS-based Positioning, Navigation, and Timing Service (GPNTS) software support.
-
The contract will utilize cost-plus-fixed-fee Contract Line Item Numbers for GPNTS software improvements, maintenance, and engineering services over a potential 10-year period including a base 5-year ordering period and subsequent 3-year and 2-year option periods.
-
The incumbent contractor for GPNTS development is Raytheon Integrated Defense Systems under contract N00039-11-C-0089.
-
The GPNTS software receives, processes, and distributes three-dimensional position, velocity, acceleration, attitude, time and frequency data to shipboard user systems and is designed for backfit and forward fit to various platforms.
-
The Technical Data Package associated with the solicitation is available to authorized DoD contractors through a secured website upon completion of non-disclosure agreements.
View the file
Other files for this federal contract opportunity
Show all 37
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
GPNTS
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A001
2. TITLE OF DATA ITEM
Contractor’s Progress, Status, and Management Report
(CPSMR)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MGMT-80227
5. CONTRACT REFERENCE
SOW 3.1.1
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
9. DIST
STATEMENT
D
10. FREQUENCY
SEE BLK 16
12. DATE OF 1ST SUBMISSION
45 DACA
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION MTHLY Draft
Final Reg Repro
16. REMARKS
BLK A: Contract Line Item No. 0003, 1003, 2003
BLK 4: The Contractor shall deliver the CPSMR in memo format. to include the following information:
• Significant changes/challenges from previous month
• Forecasted challenges for next month
• News risks rated yellow-red and current risks elevated to yellow-red
• Subcontractor status update (significant items)
• A financial summary to include:
o Actuals incurred for the current month and cumulative to date from the Contractor ledger.
Include current funding level Funds Remaining Funds Remaining good through (date) o Cost curves showing actual and projected conditions throughout the contract o Summary of invoices submitted to the Government.
• A summary by CLIN of cost, schedule, and risks for each exercised CPIF CLIN option:
o Current funding level o Funds remaining o PM EAC with supporting narrative o Schedule/delivery projections o Summary of any other risks or issues
• Requests for Government Action
• Summary of significant decisions and accomplishment from Software
Configuration Control Board (SCCB) meetings. Any Contractor reports on minutes or action items as a result of those meetings shall be included as an attachment to the CPSMR, in Contractor format.
BLK 9: Distribution Statement D. Distribution authorized to Department of Defense and U.S.
DoD contractors only for Administrative/Operational use only. Other requests for this document shall be referred to PMW/A 170.
BLKS: 10, 11, 12, 13: The Contractor shall submit forty-five (45) calendar days after contract award and monthly thereafter.
Include a redlined version of the submitted CDRL, indicating all changes made to the document since the original submittal.
All data will be provided in 2010 Microsoft Office format. Email deliverable to the GPNTS COR via Contractor secured email.
PCO 1
Contract Specialist 1
COR 1
ACOR 1
Contract Support 1
15. TOTAL --------- 0 0 0
G. PREPARED BY
See Signature Cover Sheet
H. DATE
I. APPROVED BY
J. DATE
DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page __ of __ Pages
18. ESTIMATED
TOTAL PRICE
17. PRICE
GROUP
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
A002
Funds & Labor Hour Expenditure Report
3. SUBTITLE
Labor Hours Reporting
4. AUTHORITY (Data Acquisition Document No.)
DI-FNCL-81537
5. CONTRACT REFERENCE
SOW 3.1.1.2
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
9. DIST
MTHLY
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
N/A
13. DATE OF SUBSEQUENT
SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK A: Contract Line Item No. 0003, 1003, 2003
BLK 9: Distribution Statement D. Distribution authorized to Department of Defense and U.S.
DoD contractors only for Administrative/Operational use only. Other requests for this document shall be referred to PMW/A 170.
BLKS: 10, 11, 12, 13: The Contractor shall submit forty-five (45) calendar days after contract award and monthly thereafter.
Include a redlined version of the submitted CDRL, indicating all changes made to the document since the original submittal.
All data will be provided in 2010 Microsoft Office format. Email deliverable to the GPNTS COR via Contractor secured email.
PCO 1
Contract Specialist 1
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
A003
Conference Agenda
3. SUBTITLE
SEE BLK 16
4. AUTHORITY (Data Acquisition Document No.)
DI-ADMN-81249B
5. CONTRACT REFERENCE
SEE BLK 16
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
SEE BLK 16
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
N/A
13. DATE OF SUBSEQUENT
SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK A: Contract Line Item No. 0003, 1003, 2003
BLK 5: SOW sections 3.1.1.3, 3.1.1.4, 3.1.2.1, 3.1.2.2, 3.1.2.3, 3.1.2.4, 3.1.2.5, 3.1.2.6, 3.1.2.7.
BLK 3, 10: Conference Agendas will be provided for the following events to include Post Award Conference (PAC), Program Management Reviews (PMRs), Software Design Reviews, Software Requirements Review, Preliminary Design Review (PDR), Critical Design Review (CDR) and Test Readiness Review (TRR).
BLK 9: Distribution Statement D. Distribution authorized to Department of Defense and U.S.
DoD contractors only for Administrative/Operational use only. Other requests for this document shall be referred to PMW/A 170.
BLKS 12, 13: The Contractor shall submit the Conference Agenda thirty (30) days before the meeting, except for the PAC, which can be submitted fourteen (14) days before meeting.
Include a redlined version of the submitted CDRL, indicating all changes made to the document since the original submittal.
All data will be provided in 2010 Microsoft Office format. Email deliverable to the GPNTS COR via Contractor secured email.
PCO 1
Contract Specialist 1
COR 1
(1 Data Item)
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
A004
Presentation Material
3. SUBTITLE
SEE BLK 16
4. AUTHORITY (Data Acquisition Document No.)
DI-ADMN-81373
5. CONTRACT REFERENCE
SEE BLK 16
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
SEE BLK 16
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
N/A
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK A: Contract Line Item No. 0003, 1003, 2003
BLK 5: SOW 3.1.1.3, 3.1.1.4, 3.1.2.1, 3.1.2.2, 3.1.2.3, 3.1.2.4, 3.1.2.5, 3.1.2.6, 3.1.2.7.
BLK 3, 10: Presentation Materials shall be provided for the following events to include Post Award Conference (PAC), Program Management Reviews (PMRs), Software Design Reviews, Software Requirements Review, Preliminary Design Review (PDR), Critical Design Review (CDR) and Test Readiness Reviews (TRRs).
BLK 9: Distribution Statement D. Distribution authorized to Department of Defense and U.S.
DoD contractors only for Administrative/Operational use only. Other requests for this document shall be referred to PMW/A 170.
BLKS 12, 13: The Contractor shall submit the Presentation Materials fourteen (14) days before the meetings, except for the PAC, which can be submitted seven
(7) days before the meeting.
Include a redlined version of the submitted CDRL, indicating all changes made to the document since the original submittal.
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
A005
Report, Record of Meeting / Minutes
3. SUBTITLE
SEE BLK 16
4. AUTHORITY (Data Acquisition Document No.)
DI-ADMN-81505
5. CONTRACT REFERENCE
SEE BLK 16
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
SEE BLK 16
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
N/A
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK A: Contract Line Item No. 0003, 1003, 2003
BLK 5: SOW 3.1.1.3, 3.1.1.4, 3.1.2.1, 3.1.2.2, 3.1.2.3, 3.1.2.4, 3.1.2.5, 3.1.2.6, 3.1.2.7.
BLK 3, 10: Reports, Record of Meeting/Minutes will be submitted after the following Events to include Post Award Conference (PAC), Program Management Reviews (PMRs), Software Design Reviews, Software Requirements Review, Preliminary Design Review (PDR), Critical Design Review (CDR) and Test Readiness Reviews (TRRs).
BLK 9: Distribution Statement D. Distribution authorized to Department of Defense and U.S.
DoD contractors only for Administrative/Operational use only. Other requests for this document shall be referred to PMW/A 170.
BLKS 12, 13: The Contractor shall submit the Report, Record of Meeting/Minutes fourteen
(14) calendar days after completion of the meeting. Include, when possible and as appropriate, line item numbers in all submittals of this CDRL, except for the final submittal, which includes the adjudicated Government comments, as needed.
Include a redlined version of the submitted CDRL, indicating all changes made to the document since the original submittal.
All data will be provided in 2010 Microsoft Office format. Email deliverable to the GPNTS COR via Contractor secured email.
PCO 1
Contract Specialist 1
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
A006
Program Protection Implementation Plan (PPIP)
3. SUBTITLE
Program Protection Implementation Plan (PPIP)
4. AUTHORITY (Data Acquisition Document No.)
DI-MGMT-81826C
5. CONTRACT REFERENCE
SOW 3.1.1.5
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
SEE BLK 16
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
N/A
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK A: Contract Line Item No. 0003, 1003, 2003
BLK 9: Distribution Statement D. Distribution authorized to Department of Defense and U.S.
DoD contractors only for Administrative/Operational use only. Other requests for this document shall be referred to PMW/A 170.
BLK 10, 11, 12, 13, 14: PPIP shall be provided 30 days after receiving countermeasures from the Government as required. The Contractor shall have thirty (30) calendar days to address comments and resubmit.
Include, when possible and as appropriate, line item numbers in all submittals of this CDRL, except for the final submittal, which includes the adjudicated Government comments, as needed.
Include a redlined version of the submitted CDRL, indicating all changes made to the document since the original submittal.
All data will be provided in 2010 Microsoft Office format. Email deliverable to the GPNTS COR via Contractor secured email.
PCO 1
Contract Specialist 1
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
A007
Integrated Program Management Report (IPMR)
Di-MGT-81861A
5. CONTRACT REFERENCE
SOW 3.1.1.6, 3.1.1.7, 3.1.1.8. 3.1.1.11
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
MTHLY
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK A: Contract Line Item No. 0003, 1003, 2003
BLK 4: The Contractor shall deliver a monthly Integrated Program Management Report (IPMR) in accordance with DI-MGMT-81861A requirements except or as modified or defined by the following instructions (paragraph references below are DID references, unless otherwise stated:
General Instructions, IPMR Sections 1 through 3.1 apply. Program defined parameters within sections 1 through 3.1 include:
• Formats 1, 5, 6, 7 are mandatory. Formats 2, 3 and 4 are optional for contract values less than $50M and mandatory for contract values $50M or above in then-year dollars, including all known options.
• 2.1.1.1 All costs in IPMR formats shall be reported in whole dollar units (no decimals) to support XML transmission guidelines.
• The "as of" date on the monthly IPMR submittal will follow the Contractor's accounting period.
Any/all subContractor IPMR data (standalone IPMR reports and/or subContractor data integrated into the prime Contractor’s IPMR) if applicable, shall be submitted along with the Prime Contractor’s monthly IPMR submittal. SubContractor data shall not lag in performance periods. This includes subcontracted support labor.
Format 1, Work Breakdown Structure (Mandatory), (DID Paragraph 3.2 applies) Program defined parameters within 3.2 include:
• 2.2.2/3.2.4.1 Format 1 reporting levels will initially be at Level 3 of the CWBS for management and support activities and Level 4 for discrete work. Reporting levels will be adjusted at no cost to the Government in conjunction with the IBR based on program risk as the program Responsibility Assignment Matrix is reviewed and risk further assessed. Reporting levels will be reviewed by the Government quarterly, or as special interest areas arise. Reporting level changes will be mutually agreed to and documented via email from the COR. Contract modification is NOT necessary to update reporting levels.
• 3.2.4.2 Cost of Money (COM) costs shall be included at the CWBS level in block 8a of the IPMR Format 1 if the vendor’s accounting system allows. Corresponding non-additive COM entries shall also be made in Block 8b of the IPMR Format 1.
• 3.2.4.3 G&A costs shall be included at the CWBS level block in 8a of the IPMR Format 1 if the vendor’s accounting system allows. Corresponding non-additive G&A entries will also be made in Block 8c of the IPMR Format 1.
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
5. CONTRACT REFERENCE
SOW 3.1.1.6, 3.1.1.7, 3.1.1.8. 3.1.1.11
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
MTHLY
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
Format 2, Organizational Breakdown Structure, (Optional for contract values less than $50M, Mandatory for contract values equal to/greater than $50M in then-year dollars) (DID Paragraph 3.3 applies) Program defined parameters within 3.3 include:
• 3.3.1.1 Format 2 IPMR reporting levels will follow the contractor’s internal management structure (OBS) or the Program IPT structure.
• 3.3.1.1.2/3 Format 2 data shall provide standalone visibility for subcontractor efforts as well as material procurement. When Format 2 is optional and tailored out of the IPMR, Format 1 shall contain standalone visibility for subcontract and material procurement
• Cost of Money (COM))/G&A to follow the same methodology as Format 1.
Formats 3 Baseline (Optional for contract values less than $50M, Mandatory for contract values equal to/greater than $50M in then-year dollars). (DID Paragraph 3.4) Program defined parameters within 3.4 include:
• Formats 3 Forecast periods shall be monthly for at least six months, quarterly for at least two quarters, and then semi-annually, or annually to completion. All groupings will be consistent with the Government fiscal year.
• 3.4.1.10 The planned completion date and estimated completion date shall equal the corresponding baseline and forecast completion dates in the IMS, Format 6. Any differences resulting in an OTS shall be reviewed and approved by the Government prior to incorporation into the PMB or the IPMR.
• 3.4.2.2 All changes to the PMB from the prior month will be explained in Format 5 and entered into Format 3, block 6b. Significant changes (+/- 5%) to the PMB in any given month shall be detailed by control account in Block 6.b of the Format 3. All other changes shall be summarized and discussed in Format 5. If the Format 3 is tailored out of the IPMR, all baseline changes shall be discussed in Format 5.
Format 4, Staffing (Optional for contract values less than $50M, Mandatory for contract values equal to/greater than $50M in then-year dollars) All DI-MGMT- 81861A Paragraph 3.5 applies. Program defined parameters within 3.5 include:
• Formats 3 and 4 shall include identical forecast periods.
• 3.5.1 Format 4 shall be reported in hours and equivalent months.
• 3.5.1.4/5 Format 4 columns (4) through (14) Forecast (Non-Cumulative), the staffing forecast shall reflect the same staffing estimate used as the basis for the EAC reported in Column (15) on Format 1. Any significant change in the total number of hours/equivalent months at completion of the contract (i.e., Column 15 Total) shall be explained in Format 5.
Format 5, Management Overview and Variance Analysis (Mandatory), All DI-MGMT- 81861A (Paragraph 3.6 Requirements apply in its entirety). Program defined parameters within 3.6 include:
3.6.1 The Format 5 shall contain a General section which will provide the Government with the following:
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
5. CONTRACT REFERENCE
SOW 3.1.1.6, 3.1.1.7, 3.1.1.8. 3.1.1.11
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
MTHLY
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
• Contract Summary. 3.6.2 This shall be a narrative at a program manager level which will describe the major program issues which have resulted in the contract’s overall cost/schedule status. It shall highlight significant changes since the previous report. This section shall describe and status the corrective actions in place to resolve program issues. This section is intended to be a high-level summary and limited to one page in length. This section shall not refer the reader to the WBS element VAR explanations in lieu of providing summary explanations.
• EAC Analysis 3.6.4 shall be discussed in detail. This section shall include an explanation of the month’s changes to the EAC in Format 1, Column 15. It will also explain the rationale of the creation of the Management Best Case, Worst Case, and Most Likely EAC’s. The rationale for Management EAC formulation shall not be a result of using EVM metrics to calculate EAC’s. Management EAC’s should be adjusted based on program risk and include estimates for looming program events which will impact program cost. This section will explain the assumptions, conditions, methodology, and risk/opportunity incorporation in all 3 management EAC’s. This section will explain the difference between the EAC on Format 1, Column 15 and the Most Likely Management EAC if applicable. It will include an assessment of the IMS status and the impact of schedule to the Most Likely EAC.
This section will also include a table (by Format 1 WBS) of EAC changes by reportable WBS showing the prior EAC as compared to the current report’s EAC.
Explanations of the changes by WBS after a bottoms-up EAC, monthly reviews, significant impacts from re-planning, or burden rate changes shall be documented here.
• UB Analysis 3.6.5 shall explain the components of Undistributed Budget balance changes from month to month. A plan to distribute Undistributed Budget shall also be included in the narrative.
• MR Analysis 3.6.6 shall explain how MR was created in the initial report.
Subsequently changes to MR will be fully explained. A comparison of MR to the program’s Risk Register shall also be included in this section.
• IMS Discussion and analysis shall be included in totality as described in 3.6.7.
Schedule variance narratives shall also identify the significant missed milestones, impact to major milestones, and expected recovery dates.
• The IMS discussion will also include an explanation of the Agile SCRUM Sprints and how they are rolled/tracked in the IMS and then into the IPMR.
• Cost and Schedule analysis by WBS
• 3.6.10.2.1 Thresholds for the program are:
o Current Month Cost: +/- 5% and $50k o Current Month Schedule: +/- 5% and $50k o Cumulative Cost: +/- 10% and $75k o Cumulative Schedule: +/- 10% and $75k o Variance at Completion: +/- 10% and $75k
• 3.6.10.2.2 The thresholds above are initial thresholds and will be reviewed when the Government reviews the Contractor’s Responsibility Assignment Matrix (RAM) in preparation for the IBR. Only at that time, when Control Account dollar values are disclosed, can initial variance thresholds be right-sized for the program. At the IBR, the initial variances may be adjusted based on RAM analysis. The thresholds will be periodically reviewed by the Government and Contractor during the performance of the contract to ensure the analysis is providing proactive insight to the cost and schedule performance on the program.
PCO 1
Contract Specialist 1
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
5. CONTRACT REFERENCE
SOW 3.1.1.6, 3.1.1.7, 3.1.1.8. 3.1.1.11
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
MTHLY
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
Changes to the thresholds will be mutually agreed upon, documented via email from the Government COR and do not represent constructive changes.
• 3.6.10.2.3 Initially, the variance analysis pool will be determined by the Contractor using the government directed thresholds. The 15 reportable WBS variances will be determined based on dollar value, then by program risk. (If one WBS is reportable for cost, schedule, and EAC, it is ONE reportable WBS). If after this selection process, there are not 15 WBS element variances to discuss, the contractor will discuss WBS elements with emerging trends which will soon lead to threshold breach. If after this cycle of selection there are not 15 reportable WBS variances to discuss, the Contractor will so state in the Format 5.
• 3.6.10.2.4 The contractor is not prohibited from providing more analysis as warranted by cost/schedule performance issues, nor is the government prohibited from requiring more than 15 WBS elements to cover emerging trends. Neither situation represents a constructive change and/or additional cost to the Government.
Additional analysis can be requested via email from the Government COR per guidance in DI-MGMT-81861.
• Current Month variances are to be explained separately from cumulative variances, and cost variances are to be explained separately from schedule variances.
Variance at Completion analysis is to be included as defined above.
• Variance explanations for each CWBS element shall address the technical cause, the near-term impact to the reporting element, the impact to other elements and the overall program, and the corrective action plan established to adjudicate the issue.
The corrective action plans are to be updated in each submittal if the variance is reported for more than one month.
Format 6 (Mandatory), All DI-MGMT-81861A (Paragraph 3.7 Requirements apply).
Program defined parameters in 3.7 include:
• The IMS shall be sufficiently detailed such that the network critical path, network near-critical paths, high risk and other significant technical efforts are identified and planned realistically to assure achievability. Network near-critical paths, high risk, and other significant effort IMS reporting requirements will be initially discussed, identified and mutually agreed upon to the maximum extent possible at the Post Award Conference for the purposes of the initial IMS submittal, and finalized/documented as part of the initial Integrated Baseline Review exit criteria/close-out action items.
• The IMS shall employ the same primary numbering system consistent with the CWBS and the resulting Contractor extended CWBS.
• 3.7.1.3.7.8 The Government may reserve fields and/or require the Contractor to use certain fields for specific information. The required reserved fields, at this time, in addition to those in 3.7.1.3.7.3 are EV% Complete, Physical % Complete, Risk #
• The IMS shall employ additional nomenclature and numbering systems that facilitate ready traceability to the Functional/Organizational elements (i.e., IPTs), contract Performance Statement of Work (SOW) paragraphs, and other significant organizational or management elements.
• The IMS shall reflect those retired or mitigated risk planning initiatives (i.e., added schedule or resources above original BOE) and funded risk mitigation activities identified.
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
5. CONTRACT REFERENCE
SOW 3.1.1.6, 3.1.1.7, 3.1.1.8. 3.1.1.11
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
MTHLY
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
• 3.7.1.1.1/2 The Prime IMS shall include the efforts for all activities, including subContractor, supplier and material procurement efforts. Prime Contractors are responsible for flowing down EVMS Requirements, and/or integrating IMS requirements contained in the prime contract to all subContractors when applicable.
The subContractor Format 6 shall be attached to the Prime’s submittal of Format 6.
• 3.7.1.3.6 Schedule Risk Assessments (SRA) shall be submitted as part of the IBR artifact delivery as an attachment to the baselined IMS. The initial submittal shall include a narrative describing the Contractor’s SRA process and how that process is reflected in the IMS. The SRA narrative shall identify and explain the validity of the risk percentages used in the assessment by WBS and for Critical Path Tasks.
Subsequent submissions may be necessary for significant program milestones. An SRA must also accompany the Contractor’s request to initiate OTB/OTS planning or before implementation of significant cost and schedule resets, i.e, Single Point Adjustments. The Government reserves the right to participate in the Contractor’s SRA process, providing input to risk assessments used in the SRA, at no cost to the Government.
• The Contractor shall create a display in Government Fiscal Years as the default schedule view.
• Any/all external dependencies shall be included in the IMS and identified with unique coding/structure to facilitate separate analysis. All external dependencies shall be determined and documented no later than the conclusion of the initial management or baseline review. Any evolutionary changes occurring during the course of the contract that impact external dependencies shall be reflected in the monthly IMS analysis report and incorporated into the IMS as soon as feasible but no later than the next monthly submittal following identification of the change.
• The IMS shall reflect those retired or mitigated risk planning initiatives and funded risk mitigation activities identified and documented in the Contractor’s Risk Management Plan.
• The first submission of the IMS shall include narrative that provides the Basis and Assumptions (B&A) of the IMS. The B&A will support the IMS and provide a schedule for all program milestones and/or IMS events and document all associated programmatic schedule assumptions that were utilized in the development of the baseline plan (i.e., the ground rules and assumptions, historical data, experience on similar efforts, vendor schedules, number of work days per week, number of shifts, etc., used in estimating the task durations shown in the schedule).
• At a minimum, all subsequent monthly IMS submissions shall include a narrative schedule analysis identifying and communicating changes impacting the critical path within the Format 5 or as a standalone document. The schedule narrative shall address progress to date and discuss any significant schedule changes (i.e., any changes to the critical path, the next major milestone, significant logic revisions, programmatic schedule assumption changes, major work-around or recovery plans), as well as variances to the baseline schedule, Format 3, contractual finish date, causes for the variances, potential impacts, and recommended corrective actions.
The monthly IMS narrative shall be included as part of the Format 5 IPMR submission.
Format 7. All DI-MGMT-81861A (Mandatory) (Paragraph 3.8 Requirements apply):
• 3.8.1 Time phased data shall be reported at the Contractor Control Account level.
Format 7 shall be submitted quarterly in accordance with DI-MGMT-81861.
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
5. CONTRACT REFERENCE
SOW 3.1.1.6, 3.1.1.7, 3.1.1.8. 3.1.1.11
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
SEE BLK 16
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK 10-13: The first IPMR submission is due within 12 business days after the end of the second full accounting period following contract award. Thereafter, the IPMR shall be required monthly. The first Format 6 is due 12 business days after the end of the first full accounting period following contract award, thereafter Format 6 shall be submitted monthly in conjunction with the remaining formats in the IPMR. The initial SRA submission shall accompany the IBR artifacts and be run using the baselined IMS.
Subsequent SRA’s may be required in conjunction with program milestones, as agreed to during the post-award conference. All formats shall be submitted to the COR no later than 12 business days following the close of the Contractor's accounting calendar month end.
Final IPMR submission is due when the last deliverable, as defined by the contract, has been achieved.
BLK 14: One copy formatted per DI-MGMT-81861A and one human readable format.
Include a redlined version of the submitted CDRL, indicating all changes made to the document since the original submittal.
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
A008
Integrated Baseline Review (IBR)
5. CONTRACT REFERENCE
SOW 3.1.1.9
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
SEE BLK 16
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK A: Contract Line Item No. 0003, 1003, 2003
BLK 10: At the discretion of the Government, IBRs will be conducted as needed throughout the life of the contract.
BLK 12: The initial IBR shall be conducted as soon as feasible (e.g., as soon as the Performance Measurement Baseline (PMB) is established and documented) but not later than 180 days after contract award or authorization to proceed. Initial IBR planning, preparation and conduct details will be discussed and finalized to the maximum extent possible at the Post-Award Contract Kick-off meeting. Agreement will be reached on:
• IBR approach, CLIN/SOW scope coverage (including subcontractor scope and IBR approach), dates, duration, and preliminary IBR agenda.2. IBR entrance criteria.
DCMA and the PMO IBR Lead/Facilitator will take the lead role in assessing contractor IBR readiness.
• Pre-IBR support requirements including:
- Advance IBR documentation/artifacts submittal requirements and schedule for delivery of artifacts.
- The Contractor shall provide a progress schedule, preferably MSProject of all of the IBR preparation tasks that need to be accomplished to achieve successful review 10 calendar days after the IBR date is set.
- The Contractor shall participate in IBR coordination meetings, frequency to be determined. These meetings will be telecoms to discuss IBR preparation as the Contractor works through the detail planning of the scope of work. It will be used as a forum to coordinate the logistics of the review; discuss the status of the tasks on the IBR Preparation schedule mentioned above; and discuss the artifacts as they are being created so that expectations are met at the review.
- Participation in Government pre-IBR Workshop activities (e.g., vendor may be asked to send 2-3 representatives (e.g., PM, SE Lead, Scheduler) to a Government pre-IBR workshop to provide 2-4 hours of PMB, IMS, IBR artifact and EVMS overview and data traces). This participation is in lieu of discussing the EVMS and processes as an agenda item at the IBR itself.
In situations where the entire work scope is not known in the 180 days, the IBR will be conducted in stages, such as Undefinitized Contract Actions (UCA) and NTE’s. A review of the known work scope will be conducted within the 180-day window with follow-up IBRs scheduled at a later time for the work not yet completed in the context of the entire Performance Measurement Baseline.
Even when the UCA/NTE situations are not applicable, subsequent IBR(s) would be required if the program experiences major changes in requirements via contract modifications, a shift in major milestone events, major changes to the baseline, re-planning, or OTS/OTB. Deliverables shall be formatted ready to print on 8.5 x 11 or 11 x 17 paper. All electronic files submitted for IBR artifacts shall be complete representation of each document, so no manipulation is required by the Government. Providing information which must be manipulated via pivot tables, for instance will result in artifacts being rejected and the IBR date compromised.
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
5. CONTRACT REFERENCE
SOW 3.1.1.9
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
SEE BLK 16
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
8. APP CODE
A
11. AS OF DATE
SEE BLK 16
13. DATE OF SUBSEQUENT
SUBMISSION SEE BLK 16 Draft
Final Reg Repro
16. REMARKS
BLK 10: At the discretion of the Government, IBRs will be conducted as needed throughout the life of the contract.
BLK 12: The initial IBR shall be conducted as soon as feasible (e.g., as soon as the Performance Measurement Baseline (PMB) is established and documented) but not later than 180 days after contract award or authorization to proceed. Initial IBR planning, preparation and conduct details will be discussed and finalized to the maximum extent possible at the Post-Award contract Kick-off meeting. Agreement will be reached on:
• IBR approach, CLIN/SOW scope coverage (including subcontractor scope and IBR approach), dates, duration, and preliminary IBR agenda.2. IBR entrance criteria.
DCMA and the PMO IBR Lead/Facilitator will take the lead role in assessing contractor IBR readiness.
• Pre-IBR support requirements including:
- Advance IBR documentation/artifacts submittal requirements and schedule for delivery of artifacts.
- The Contractor shall provide a progress schedule, preferably MS Project of all of the IBR preparation tasks that need to be accomplished to achieve successful review 10 calendar days after the IBR date is set.
- The Contractor shall participate in IBR coordination meetings, frequency to be determined. These meetings will be telecoms to discuss IBR preparation as the Contractor works through the detail planning of the scope of work. It will be used as a forum to coordinate the logistics of the review; discuss the status of the tasks on the IBR Preparation schedule mentioned above; and discuss the artifacts as they are being created so that expectations are met at the review.
- Participation in Government pre-IBR Workshop activities (e.g., vendor may be asked to send 2-3 representatives (e.g., PM, SE Lead, Scheduler) to a Government pre-IBR workshop to provide 2-4 hours of PMB, IMS, IBR artifact and EVMS overview and data traces). This participation is in lieu of discussing the EVMS and processes as an agenda item at the IBR itself.
In situations where the entire work scope is not known in the 180 days, the IBR will be conducted in stages, such as Undefinitized Contract Actions (UCA) and NTE’s. A review of the known work scope will be conducted within the 180-day window with follow-up IBRs scheduled at a later time for the work not yet completed in the context of the entire Performance Measurement Baseline.
Even when the UCA/NTE situations are not applicable, subsequent IBR(s) would be required if the program experiences major changes in requirements via contract modifications, a shift in major milestone events, major changes to the baseline, re-planning, or OTS/OTB. Deliverables shall be formatted ready to print on 8.5 x 11 or 11 x 17 paper. All electronic files submitted for IBR artifacts shall be complete representation of each document, so no manipulation is required by the Government. Providing information which must be manipulated via pivot tables, for instance will result in artifacts being rejected and the IBR date compromised.
COR 1
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO.
SEE BLK 16
B. EXHIBIT
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER __ __
D. SYSTEM/ITEM
5. CONTRACT REFERENCE
SOW 3.1.1.9
6. REQUIRING OFFICE
PMW/A 170
7. DD 250 REQ
LT
SEE BLK 16
12. DATE OF 1ST SUBMISSION
SEE BLK 16
14. DISTRIBUTION
a.…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .