APPENDIX_C_CSDR__DD2794_Attachment.xlsx

XLSX spreadsheet 48 KB Posted

Attached to
KC-135 Aero-I SATCOM Replacement Federal contract opportunity
Solicitation number
KC-135_Aero-I
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Tinker Air Force Base

About this file

Written by GovTribe AI ·

This document contains a cost and software data reporting plan template (DD Form 2794) for the KC-135 Aero-I SATCOM replacement program. The template requires reporting at the work breakdown structure (WBS) element level for cost, schedule, and software development data. Reporting is required for integrated program management reports, contract funds status reports, software resources data reports, and earned value management. Data must be reported for program milestones like requirements reviews, design reviews, testing events. Final data delivery is required at contract completion.

A related federal contract opportunity notice seeks sources to replace the KC-135 aircraft's aging Aero-I SATCOM system with an Iridium solution. A market survey is being conducted to identify potential offerors that can qualify production and provide an Iridium system, transceiver, antenna, and associated components for 400 aircraft. An industry day will be held on May 8, 2018 to provide information and accept written questions. Capability statements are requested by April 30, 2018 to assess offeror's production, software, repair, and technical data capabilities. The program aims to begin fielding replacements in fiscal year 2020 through 2022.

From the source

CSDR DD2794

View the file

Other files for this federal contract opportunity

Other files attached to KC-135 Aero-I SATCOM Replacement, newest first.
File Type Posted
UPDATED_5-_Vendor_Questions_and_Government_Responses_04_Nov_19.pdf PDF
UPDATED_4-_Vendor_Questions_and_Government_Responses_29_Oct_19.pdf PDF
UPDATED_3-_Vendor_Questions_and_Government_Responses_10_Oct_19.pdf PDF
UPDATED_2-_Vendor_Questions_and_Government_Response_30_SEP_19.pdf PDF
UPDATED-Vendor_Questions_and_Government_Responses_26_SEP_19.pdf PDF
APPENDIX_A_SOW_REV_A.pdf PDF
ATTACHMENT_3_PRICING_MATRIX_REV_A.xlsx XLSX spreadsheet
FA810519R0005_______0001.pdf PDF
ATTACHMENT_2_Section_M_EVALUATION_FACTORS_REV_A.pdf PDF
Vendor_Questions_and_Government_Responses_10_SEP_19.pdf PDF
EXHIBIT_A_CDRLs.zip ZIP file
FA810519R0005.pdf PDF
ATTACHMENT_1_Section_L_Instructions_to_Offerors.pdf PDF
APPENDIX_A_SOW.pdf PDF
EXHIBIT_A_DIDs.pdf PDF
APPENDIX_C_CSDR_Plan.pdf PDF
APPENDIX_B_SRD.pdf PDF
EXHIBIT_A_CDRLs.pdf PDF
ATTACHMENT_3_PRICING_MATRIX.xlsx XLSX spreadsheet
ATTACHMENT_2_Section_M_EVALUATION_FACTORS.pdf PDF
AERO-I_Additional_Questions_and_Responses.pdf PDF
Synopsis_-_Aero-I.pdf PDF
Aero-I_Pre-Solicitation_Attendee_List-_16_May_2019.pdf PDF
Pre-Solicitation_Q&A's_(Round_2).pdf PDF
ppi_tool.accdb MDB file
Pre-Solicitation_Questions_-_Post_to_FBO_(Updated).pdf PDF
Pre_Solicitation_Conf_-_Aero-I_DRAFT_-_FINAL.pdf PDF
SRD.pdf PDF
Section_L_Pricing.xlsx XLSX spreadsheet
SOW.pdf PDF
CDRLs.pdf PDF
KC135_AERO_I_Contract_CSDR_Plan.xls XLS spreadsheet
Registration_Form.docx DOCX document
Section_L.pdf PDF
FA810519R0005V19.pdf PDF
Section_M.pdf PDF
AERO-I_Industry_Day_Slides.pdf PDF
AERO-I_Replacment_Industry_Day_Registration_Form.pdf PDF
Show all 38

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
Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

DD Form 2794, Pg 1

COST AND SOFTWARE DATA REPORTING/EARNED VALUE MANAGEMENT CO-PLAN Form Approved OMB No. 0704-0188 The public reporting burden for this collection of information is estimated to average 8 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, 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 COMPLETED FORM TO THE ABOVE ORGANIZATION.

1. MAJOR PROGRAMa. NAME:Aero-I SATCOM
b. PHASE/MILESTONEc. PRIME MISSION PRODUCT2. WBS SYSTEM TYPE3. SUBMISSION TYPE4. CURRENT SUBMISSION DATE (YYYYMMDD)5. LAST APPROVED PLAN DATE (YYYYMMDD)
Pre-ABXC-FRPAERO-IElectronic SystemXINITIAL
AXC-LRIPO&SCHANGE
6a. POINT OF CONTACT (POC) NAME AND ADDRESS (Include ZIP Code)6b. TELEPHONE NUMBER (Include Area Code)6c. FAX NUMBER (Include Area Code)6d. E-MAIL ADDRESS
Jacqueline Burns/Bldg 3001 Ste 2AG1/88G, Tinker AFB, OK, 73145405-734-2736
B8. PREPARING ORGANIZATION9a. CONTRACTOR NAME/ADDRESS9b. CONTRACT NUMBER9c. APPROPRIATION10. APPROVED PLAN NUMBER
PROGRAMXCONTRACT (PRIME)i. PERFORMING ORGANIZATIONii. DIVISIONRDT&E
CONTRACT (SUB)TBDXPROCUREMENT
O&M
11. WBS ELEMENT CODE12.
WBS REPORTING ELEMENTS13. REPORTS REQUIRED
(X if applicable)DD 1921-3 (CBDR):DD 1921-1 / 1921-5 EAC:EVM Reporting:
XXX
a. PROGRAM/
CONTRACT/ SUBCONTRACTb. CONTRACT/
SUBCONTRACTa. CWBS
DICTIONARYCCDRg. SRDR
FORMATSh. IPMR

FORMAT 1

b. DD 1921
(CDSR)c. DD 1921-1
(FCHR)d. DD 1921-2
(PCR)e. DD 1921-5
(SFCHR)f. EAC
1.01.0Electronic SystemXXXXXX
1.11.1Prime Mission Product (PMP)XXXXX
1.1.11.1.1PMP Integration, Assembly, Test, and CheckoutXXXXXX
1.1.1.11.1.1.1Integration and AssemblyXXXXX
1.1.1.21.1.1.2Test and CheckoutXXXXX
1.1.1.31.1.1.3Hardware 1 (A Kit)XXX
1.1.1.3.11.1.1.3.1Wiring HarnessXXX
1.1.1.3.21.1.1.3.2Mounting PlateXXX
1.1.1.3.31.1.1.3.3Cabling and Associated ComponentsXXX
1.1.1.41.1.1.4Hardware 2 (B Kit)XXXXX
1.1.1.4.11.1.1.4.1Iridium TranscieverXXXXX
1.1.1.4.21.1.1.4.2Iridium AntennaXXXXX
1.1.21.1.2PMP Software ReleaseXXXXX
1.1.3.11.1.2.1Computer Software Configuration Item (CSCI)XXXX
1.1.41.1.2.2PMP Software Integration, Assembly, Test, and CheckoutXXXXX
1.21.2Integration, Assembly, Test, and CheckoutXXXX
1.2.11.2.1SIL IntegrationXXXXX
1.2.21.2.2Software IntegrationXXXX
1.31.3Systems EngineeringXXXXX
1.3.11.3.1Software Systems EngineeringXXXXXX
1.3.21.3.2SEMP (annex)XXXX
1.3.31.3.3Requirements managementXXXX
1.3.41.3.4Airworthiness manangementXXXX
1.41.4Program ManagementXXXXX
1.4.11.4.1Software Program ManagementXXXXXX
1.4.31.4.2Cybersecurity ManagementXXX
1.4.41.4.3Core Program ManagementXXXX
1.4.41.4.4Other Program ManagementXXXX
1.4.4.11.4.4.1LCSP/LCMP (annex)XXXX
1.4.4.21.4.4.2Integrated Master Plan (IMP)XXXX
1.4.4.31.4.4.3Integrated Master Schedule (IMS)XXXX
1.4.4.41.4.4.4Risk Management Plan (Annex)XXXX
1.4.4.51.4.4.5Product Support ElementsXXXX
1.4.4.5.11.4.4.5.1Group A Kit Number Allocation
1.4.4.5.21.4.4.5.2Group A Kit Delivery Method
1.4.4.5.31.4.4.5.3Group B Kit Number Allocation
1.4.4.5.41.4.4.5.4Group B Kit Delivery Method
1.4.4.61.4.4.6TEMP (Annex)
1.4.51.4.5Cybersecurity Test and EvaluationXX
1.4.5.11.4.5.1Cybersecurity Development TestXX
1.4.5.21.4.5.2Cybersecurity Operational TestXX
1.4.61.4.6Mock-ups/System Integration Labs (SILs)XXXXX
1.4.71.4.7Test and Evaluation SupportXXXXX
1.4.81.4.8Test FacilitiesXXXXX
1.4.8.11.4.8.1TBDXXXXX
DD FORM 2794, AUGUST 2015PREVIOUS EDITION IS OBSOLETE
11. WBS ELEMENT CODE12.
WBS REPORTING ELEMENTS13. REPORTS REQUIRED
(X if applicable)DD 1921-3 (CBDR):DD 1921-1 / 1921-5 EAC:EVM Reporting:
XXX
a. PROGRAM/
CONTRACT/ SUBCONTRACTb. CONTRACT/
SUBCONTRACTa. CWBS
DICTIONARYCCDRg. SRDR
FORMATSh. IPMR

FORMAT 1

b. DD 1921
(CDSR)c. DD 1921-1
(FCHR)d. DD 1921-2
(PCR)e. DD 1921-5
(SFCHR)f. EAC
1.51.5Training
1.5.11.5.1Training Materials
1.5.1.11.5.1.1CBT Trainer
1.5.1.21.5.1.2Training Manuals
1.5.21.5.2Maintenance Training
1.5.31.5.3Weapon System Trainer (SIM) Software
1.61.6DataXXXXX
1.6.1.11.6.1Time Compliance Tech OrderXXXXX
1.6.21.6.2Technical PublicationsXXXXX
1.6.2.11.6.2.1Maintenance Manuals/Tech OrdersXXXXX
1.6.2.21.6.2.2Aircrew ManualsXXXXX
1.6.2.31.6.2.3Commodity Technical OrdersXXX
1.6.31.6.3Engineering DataXXXX
1.6.3.11.6.3.1DrawingsXXXX
1.6.3.21.6.3.2Source DataXXXX
1.6.3.31.6.3.3Airworthiness DataXXXX
1.6.41.6.4Management DataXXXX
1.6.4.11.6.4.1Integrated Program Management Report (IPMR)XXXX
1.6.4.21.6.4.2Contract Funds Status Report (CSR)XXXX
1.6.51.6.5Support DataXXXX
1.6.5.11.6.5.1Ram-C DataXXXX
1.6.5.21.6.5.2Provisioning DataXXXX
1.6.61.6.6Data DepositoryXXXX
1.6.6.11.6.6.1JEDMICSXXXX
DD FORM 2794, AUGUST 2015PREVIOUS EDITION IS OBSOLETE
11. WBS ELEMENT CODE12.
WBS REPORTING ELEMENTS13. REPORTS REQUIRED
(X if applicable)DD 1921-3 (CBDR):DD 1921-1 / 1921-5 EAC:EVM Reporting:
XXX
a. PROGRAM/
CONTRACT/ SUBCONTRACTb. CONTRACT/
SUBCONTRACTa. CWBS
DICTIONARYCCDRg. SRDR
FORMATSh. IPMR

FORMAT 1

b. DD 1921
(CDSR)c. DD 1921-1
(FCHR)d. DD 1921-2
(PCR)e. DD 1921-5
(SFCHR)f. EAC
Subtotal CostXXX
Reporting Contractor G&AXX
Reporting Contractor Undistributed BudgetXX
Reporting Contractor Management ReserveXX
Reporting Contractor FCCMXX
Total CostXXX

Reporting Contractor Profit/Loss or Fee X X

Total Price X X X

DD FORM 2794, AUGUST 2015 PREVIOUS EDITION IS OBSOLETE

DD Form 2794, Pg 2

14. CSDR SUBMISSION DATES
a.
SUBMISSIONb.
FORM(S)c.
EVENTd.
REPORT TYPEe. AS OF DATEf. DUE DATE
(YYYYMMDD)(YYYYMMDD)
1CWBS DictionaryContract Award (plus 12 months)Initial
21921, 1921-1, 1921-2Contract Award (plus 12 months)Initial
3SRDR DevelopmentContract Award (plus 12 months - Total Contract Estimate)Initial
4SRDR DevelopmentStart of each Software ReleaseInitial
51921, 1921-1Start of each Software Release (Coincident with SRDR Initial)Initial
61921, 1921-1System Requirements Review (SRR)Interim
7SRDR DevelopmentSystem Requirements Review (SRR)Interim
81921, 1921-1Preliminary Design Review (PDR)Interim
9SRDR DevelopmentPreliminary Design Review (PDR)Interim
101921, 1921-1Critical Design Review (CDR)Interim
11SRDR DevelopmentCritical Design Review (CDR)Interim
121921, 1921-1, 1921-2First Production Representative Unit DeliveredInterim
131921, 1921-1, 1921-2Annual Report 1...nInterim
14SRDR DevelopmentAnnual Report 1...nInterim
151921, 1921-1End of each Software Release (Coincident with SRDR Final)Interim
16SRDR DevelopmentEnd of each Software ReleaseInterim
17CWBS DictionaryContract CompletionFinal
181921, 1921-1, 1921-2Contract CompletionFinal
19SRDR DevelopmentContract Completion - Total Contract Actuals)Final
20SRDR DevelopmentEvent 90 Days Prior to Production DecisionInterim
211921, 1921-1, 1921-2Event 90 Days Prior to Production DecisionInterim

DD FORM 2794 (PAGE 2), AUGUST 2015 PREVIOUS EDITION IS OBSOLETE

15. REMARKS

CO-PLANNING
a. Integrated Program Management Report (IPMR)
1. IPMR column 13.h reporting requirements shall be updated/annotated at the post-award conference.

2. IPMR elements selected for reporting in column 13.h shall be updated to reflect the PMO’s programmatic risk and reporting visibility needs through contract award.

3. EVM reporting requirements shall be reflected in the contractual IPMR CDRL (DD FORM 1423-1).

4. For information on IPMR policy requirements, refer to DID DI-MGMT-81861A and the IPMR Implementation Guide.

b. EAC Reporting
1. EAC column 13.f reporting requirements shall be updated/annotated at the post-award conference.

2. EAC column 13.f reporting

c. As-of-Date
1. When both an IPMR and CSDR are due in the same month, the data As-Of-Date shall be aligned to reflect the contractor’s accounting month end data.

2. CSDR Due Date need not align with IPMR Due Date.

FAC vs EAC
All references refer to Forecast at Completion (FAC) unless stated otherwise.Although the reporting entity may elect to report the Forecast at Completion (FAC) from its Electronic Industries Alliance (EIA) 748 Compliant Earned Value Management System (EVMS), there is no requirement that the FAC originate from the entity's Estimate At Completion (EAC) or any other derivative within EVMS.
NON-RECURRING/RECURRING DEFINITIONS
Recurring and Non-Recurring Costs required for all levels:
Recurring costs. Repetitive elements of development, investment or sustainment costs that may vary with the quantity being produced or maintained, irrespective of system life cycle phase and appropriation. Recurring cost categories include procurement, and production and maintenance activities; acceptance testing; maintenance and support equipment, training, and data; test articles built to an operational configuration; and certain elements of systems engineering and program management.
Examples of Prime Mission Product activities include repetitive costs incurred when building prototype, test systems, or production units to an operational configuration. Examples of Prime Mission Product Hardware activities include Fabrication and assembly of partial/full prototype, test, or production units whether for customer or contractor use; Raw material, purchased parts, equipment associated with the fabrication and assembly of partial/full prototype or test units whether for customer or contractor use; Touch labor, integration and assembly, installation and check out; Engineering support for production unit fabrication, assembly and check out.
Examples of Prime Mission Product Software activities include Procurement of stand-alone or bundled COTS software licenses used in an operational system and installation and checkout of developed software into production units. Examples of Systems Engineering activities include Sustaining engineering, logistics support, planning, organizing, monitoring and reporting activities, document maintenance. Examples of Program Management activities include programmatic, financial, contractual, schedule, planning, organizing, and monitoring (quality information assurance, configuration management) activities in support of production unit fabrication, assembly and check out; meetings & efforts in support of supplier, manufacturing & production activities.
Nonrecurring costs. Non-repetitive elements of development, investment or sustainment costs that generally do not vary with the quantity being produced or maintained, irrespective of system life cycle phase and the appropriation. Nonrecurring cost categories include product design and development (PD&D) activities, including those for modifications; system test and evaluation (ST&E) including ST&E for modifications; tooling; pre-production or pre-maintenance activities; design and development of support equipment, training, and data; and certain elements of systems engineering and program management.
Examples of Prime Mission Product PD&D activities are: Requirements definition, engineering design, analysis & development; Redesign, rework & retest due to design flaws & first time corrective actions; test articles built for testing purposes only (i.e., units that are not production-representative) such as wind tunnel models, and bench and coupon test articles; structural development, static, fatigue, software, and ballistics testing; stress analysis; flight, ground, or sea testing of system properties; redesign as a result of testing; and retesting efforts; All configuration, quality, and data management efforts supporting release activity for first article configuration, delivery & certification; System safety plan, manuals, tech services, & maintenance manual development in support of first article delivery.
Examples of hardware design and development activities include material, purchased parts and labor associated with engineering models, operational models, bench, lab articles or partially built units (i.e. units that are not production representative), tooling, and ground support equipment for qualification, structural, static, fatigue or stress testing, and refurbishment of test units; and engineering support including manufacturing engineering, quality engineering, and tool engineering for development unit fabrication, assembly & tests.
Examples of software design and development activities include design and development of all software; delivered operational software and software developed to correct deficiencies and add capabilities; Initial integration of COTS and GOTS products into operational configuration; Support for HW-SW integration and test, system level testing; initial integration of COTS and GOTS products into operational configuration; and commercial software licenses for development facilities. System Engineering, Program Management, and Data activities occur throughout the system life cycle and are supportive in nature; as such, these costs take on the characteristics of the underlying activities being performed.
Examples of Systems Engineering activities include installation plans or quality inspection plans; requirements definition, allocation and flow-down; creation of specification and Interface Control Documents (ICDs); design and implementation of system security; top level design trade-offs; analyses, studies, and simulations for system performance and effectiveness, reliability, availability, maintainability or survivability; internal & external design review, IPT coordination & integration meetings; Certification & Control documentation; and supplier selection & coordination. Examples of Program Management activities include programmatic, financial, contractual, schedule, planning, organizing, and monitoring (quality information assurance, configuration management) activities in support of development, design & testing efforts.
Examples of System Test and Evaluation activities include development of test plans/procedures; subsystem and system level test and integration for developmental articles; test equipment in support of development including for static & fatigue testing, test stands, wind tunnel models, stress analysis, ballistics testing, flight, ground or sea testing of system, redesign from testing, retesting; System/Software Integration Laboratory (SIL) development; and analysis to support verification, validation & certification. Examples of Training activity include initial courseware development and simulator development. Examples of Initial Spares and Repair Parts activity include spare parts and material in support of the nonrecurring subsystem/system level articles.
Examples of Support Equipment activity include initial equipment design and test efforts, and test program sets development. Examples of Tooling activity include special test equipment, special tooling, procurement of initial & rate tooling, tool replacement (with the exact same tool) & tool modification (to accommodate product configuration changes). Examples of Operational/Site Activation activity include site planning efforts.
COST ACCOUNTING STANDARDS (CAS) DISCLOSURE STATEMENT DIFFERENCES
Describe significant accounting changes from previous accounting period in the Remarks section of the reports, if applicable.
1921-3 CONTRACTOR BUSINESS DATA REPORT
a. The Contractor Business Data Report is prepared by and for the business entity (e.g., business unit, segment, or site) responsible for submitting the Forward Pricing RateProposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government.
b. Reports are submitted annually at the end of the contractor's fiscal year.
c. Data for Future Years should be reflective of the number of years contained in the most current document, i.e., the FPRP or the FPRA.If the document applies to more than three future years, attach additional future year sheets as required.In the absence of these documents, estimates should be provided for three future years.
** (if required) 1921-2 PROGRESS CURVE REPORT
a. Unit or Lot Reporting: Reporting to be provided by UNIT or LOT.
b. Product Characteristics: 1921-2 must include the WEIGHT and POWER.Note on 1921-2 remarks: CWIPT determines Unit or Lot reporting and product characteristics to be collected for Progress Curve report.DCARC Analyst must update comments as applicable.
FINAL COST REPORT
Submitted when final end item has been delivered and accepted by the government(e.g., as evidenced by a completed DD 250) and 95% or more of total contract costs have been incurred.
SUSTAINMENT
Contractor shall provide the following Quantity information in the Remarks section of the 1921 and 1921-5: number of systems supported by this contract, and number of repairs performed.The Contractor must state the nominal capacity planned for each Delivery Order (e.g., the # of repairs, # of overhauls, # of flight hours, etc.) identified in the plan.This requirement is intended to capture what services are being bought with each effort.
IRAD EFFORT
The contractor should list the major relevant IRAD projects leveraged for this development effort, provide a brief description of the cost of the projects, and provide/attach any more detailed actual cost information at the level available.

DD FORM 2794 (PAGE 2), AUGUST 2015 PREVIOUS EDITION IS OBSOLETE

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