CDRL A002 - IPMDAR.pdf

PDF 97 KB Posted

Attached to
Tunner Aircraft Cargo Loader (ACL) Bridge Federal contract opportunity
Solicitation number
FA8534-24-R-0011
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Robins Air Force Base

About this file

This document is a Contract Data Requirements List (CDRL) that specifies the monthly Integrated Program Management Data and Analysis Report (IPMDAR) required for a federal contract opportunity related to the Tunner Aircraft Cargo Loader.

The CDRL details the format, content, and submission requirements for the IPMDAR, including the Contract Performance Dataset, Schedule, and Performance Narrative Report. It provides specific guidance on variance analysis thresholds, staffing changes, and baseline changes that must be addressed in the IPMDAR deliverables. The CDRL also outlines the review and approval process, with the government having 45 days to approve/disapprove submissions. The related federal contract opportunity is for a 5-year, Fixed Price Incentive Firm Target/Firm Fixed Price Indefinite Delivery/Requirements-type contract to provide overhaul, PPU overhaul, and unscheduled depot-level maintenance of the Tunner Aircraft Cargo Loader. The solicitation is anticipated to be released on or around May 20, 2024, with a sole source bridge contract to be awarded to Leonardo DRS.

View the file

Other files for this federal contract opportunity

Other files attached to Tunner Aircraft Cargo Loader (ACL) Bridge, newest first.
File Type Posted
CDRL A009 - Accident Report.pdf PDF
CDRL A004 - Conference Minutes.pdf PDF
Atch_9Pricing_Instructions Final.docx DOCX document
CDRL A008 - IUID.pdf PDF
CDRL A003 - CFSR.pdf PDF
CDRL A001 - CWBS.pdf PDF
Atch 6. Tunner OH Incentives.docx DOCX document
Attachment 5- Tunner OH GFP. Final.xlsx XLSX spreadsheet
Atch 2- FD2060-24-31655 Tunner OH Bridge QASP_COR Final.pdf PDF
Atch 1-Tunner OH PWS Final (005).docx DOCX document
FA8534-24-R-0011 Final.pdf PDF
CDRL A010 - QAPP.pdf PDF
Atch_8-Cost_Proposal_Adequacy_Structure.pdf PDF
CDRL A007 - OIM.pdf PDF
CDRL A005 - CASR.pdf PDF
Atch 7 - Tunner Registration Number Final.docx DOCX document
Atch 4 Safety Appendix Final.docx DOCX document
CDRL A006 - Test Report.pdf PDF
FA8534-24-R-0011 Draft 11 July 2024.pdf PDF
Atch_2-QASP.pdf PDF
Atch_9-Cost_Proposal_Adequacy_Structure.pdf PDF
Atch_4-Safety_Appendix.docx DOCX document
Atch_10-Pricing_Instructions.pdf PDF
Atch_6-Tunner_TSSA_Determination.docx DOCX document
Atch_5-Tunner_GFP.xlsx XLSX spreadsheet
Atch_8-Tunner_Registration_Numbers.docx DOCX document
Atch_7-Provisions_for_ROK.docx DOCX document
Atch_3-TDP.pdf PDF
Show all 28

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

G. PREPARED BY

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

16. REMARKS

C. CATEGORY:

TDP ________ TM _______ OTHER

Form Approved OMB No. 0704-0188

15. TOTAL

A. CONTRACT LINE ITEM NO. B. EXHIBIT

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

H. DATE J. DATEI. APPROVED BY

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 Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 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 address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

DIST

22202-4302.

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page of Pages

0003/1003/2003/3003/4003 A/B/C/D/E X

Tunner Loader

A/B/C/D/E002 Integrated Program Management Data and Analysis Report (IPMDAR)

DI-MGMT-81861B/T SEE BLK 16 AFLCMC/WNZ

LT

N/A C

MONTHLY

N/A

SEE BLK 16

SEE BLK 16

EVM-CR 0 1 0

0 0

Block 4: The Contractor shall provide monthly IPMDARs per DID DI-MGMT-81861B except as modified per the following:

Contract Performance Dataset (CPD), Schedule (Native Schedule File and Schedule Data set (SD)) and Performance Narrative Report (Executive Summary and Detailed Analysis) Instructions:

A.) 1.2.1. Contract Performance Dataset (CPD). The CPD shall be submitted in dollars as part of the original JavaScript Object Notation (JSON) submission.

Subcontractors with IPMDAR flow down may submit dollars as part of the original Prime submission and provide a separate JSON file with both dollars and hours file directly to the Government to protect data sensitivities related to rates.

B.) 1.5. Data Repository and 1.6 Electronic Submission and File Formats: Data in accordance with the applicable DOD approved File Format Specifications (FFS) and Data Exchange Instructions (DEI) is to include all structures and units to at least the control account.

C.) Subcontractor Integration: Data for Subcontractors with an IPMDAR DID flow down requirement shall be integrated with the Prime’s IPMDAR CDRL delivery.

Schedule:

D.)Reserved

E.) ‘2.4.2.20. Data Dictionary for Native Schedule File’: The first monthly analysis narrative submission for the Native Schedule shall include the ‘Schedule Assumptions’ and ‘Data Dictionary’. Any change, post-first submission, to the ‘Schedule Assumptions’ or ‘Data Dictionary’ requires re-submittal of the information with the affected IPMDAR deliverable.

F.) ‘2.4.2.21. Schedule Risk Assessment (SRA) - Reporting Frequency’:

Additionally, an SRA can be performed outside of routine scheduled occurrences, at the request of the Government, particularly when the schedule is a significant issue for the Government due to operational requirements, funding limitations, or when scheduling is considered a major risk element to the acquisition effort.

N/A

NSP

BRANTLEY.KYLE.AN

DREW.1545276115

Digitally signed by

BRANTLEY.KYLE.ANDREW.154527611

Date: 2024.02.07 10:22:25 -05'00'

07 Feb 2024 GRIEPENBURG.DE

IDRE.H.1289435464

Digitally signed by

GRIEPENBURG.DEIDRE.H.1289435

Date: 2024.02.16 09:06:08 -05'00'

20240216

1 3

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

0003/1003/2003/3003/4003 A/B/C/D/E X

Tunner Loader

Block4 “Authority” (continued):

Performance Narrative Report – Detailed Analysis – Variance Analysis:

G.) 2.5.3.4 Variance Analysis Selection. Variance analysis shall be presented using ‘dollars’ as the basis.

H.) General: If there are no changes to the reportable element problem analysis, expected impacts, or corrective action status, the contractor may specify “no changes since the last reported analysis” and reference the IPMDAR date when the narrative was reported.

I.) a.) 2.5.3.4.2 Government Specified Variance Analysis Thresholds’. Control account variances that exceed the category thresholds identified below are selected and reported:

b.) Pool of Reportable Variances for each CLIN are determined by the following thresholds:

1) Overhaul; Monthly -10% and $40K; Cumulative -10% and $60K; VAC-10% and $75K%

J) 2.5.2.4.3 Specific Number of Control Account Variances. The contractor shall report all variances that exceed the specified thresholds in 2.5.3.4.2Percentages determined using reporting level BCWS and BCWP as the base (denominator)

Variance thresholds shall be reviewed periodically to ensure the threshold levels are commensurate with the changing program risks and may be adjusted by contract modification with no change in contract price.

Performance Narrative Report – Detailed Analysis

2.5.3 Detailed Analysis

Table 2.1 - Detailed Analysis Table – Required Elements: provide explanations in the Performance Narrative Report Detailed Analysis in accordance with IPMDAR DID with the additional following definitions:

K.) Baseline Changes: Ensure that the following are covered in the Performance Narrative Report Detailed Analysis for baseline changes:

1) Significant Performance Measurement Baseline (PMB) differences (absolute dollar values exceeding +/- 10%) as compared to the previous IPMDAR reported PMB shall be explained in the Performance Narrative Report Detailed Analysis

Table 2.2 - Detailed Analysis Table – Tailorable Elements: provide explanations in the Performance Narrative Report Detailed Analysis in accordance with IPMDAR DID with the additional following definitions:

M.) Staffing Changes: ‘Major changes’ to staffing are defined as a change of +/- 10% or greater in the reported organizational level staffing as compared to the previous IPMDAR submittal.

Blk 5: OH PWS 4.5.1, 4.5.1.1.2

Blk 7: Letter of transmittal (LT) only; no DD250 required. For each deliverable, the Contractor shall transmit the CDRL deliverable by an electronically LT to the Contracting Officer’s Representative (COR) via email and other agreed upon media. The LT shall provide the following elements: Transmittal Statement, Contractor's Name, LT Tracking Number, Contract Number, CDRL Data Item Number, and Deliverable Description.

Blk 8: When there is "N/A" in block 8, the Government still has the inherent right to disapprove the data item deliverable. The Government shall have 45 days after receipt of Contractor's submission to approve/disapprove the submission; if approval/disapproval is not received within 45 days of receipt, approval shall be automatic. The Contractor shall have 15 days to respond with a revised submittal for any Government disapprovals.

3 3

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

0003/1003/2003/3003/4003 A/B/C/D/E X

Tunner Loader

Blk 9: Distribution is authorized to U.S. Govt agencies and their contractors (administrative or operational use). Other requests for this document shall be referred to AFLCMC/WNZ.

Blks 11-13: Each month of the calendar represents a reporting period. The first report is due by the 25th of the month immediately following the second full month after contract award. Subsequent reports are due by the 25th of each month following the first submission with no breaks in reporting, and shall address the reporting period immediately preceding the report delivery.

Blk 14: All IPMDAR files must be electronically submitted to the EVM Central Repository (EVM-CR). The EVM-CR can be located through the AAP website (https://www.acq.osd.mil/asda/ae/ada/ipm/index.html).

3 3

File details come from the government source that posted it. Updated .