NGAM RFP CDRL FINAL 092710.pdf

NEXT GENERATION AEGIS MISSILE

CONCEPT DEFINITION AND PROGRAM

PLANNING (CDPP)

CONTRACT DATA REQUIREMENTS LIST (CDRL)

HQ0147-10-R-0027

27 September 2010

CONTRACT DATA REQUIREMENTS LIST (CDRL)

TABLE OF CONTENTS

1.0 INTRODUCTION

2.0 INSTRUCTIONS FOR INTERPRETING DD FORM 1423

AND RELATED INFORMATION, AND FOR PREPARATION

AND DELIVERY OF DATA

2.1 GENERAL

2.2 Interpretation of the CDRL, DD Form 1423

2.2.1 Block 7 DD 250 Requirements 3

2.2.2 Block 8 Approval Code

2.2.3 Block 9 Distribution Statement 3

2.2.4 Block 10 Frequency

2.2.5 Block 11 As Of Date 5

2.2.6 Block 12/13 Date of First & Subsequent Submissions

2.2.7 Block 14 Distribution

2.2.8 Block 16 Remarks

2.2.9 Distribution Control

2.2.10 Special Markings

2.3 Digital Delivery of Data

3.0 EXHIBITS

A. Exhibit A CDPP Contract Effort

B. Exhibit B Recommended Program Table 11 C. CDRLs 12-45

4.0 One-Time Data Item Descriptions 46-59

1.0 INTRODUCTION

This document provides data submission information to contractors for the basic contract and/or options to be accomplished. Within this document will be found:

Instructions

Contract Data Requirements Lists (CDRLs) with CDRL Index.

One-Time Data Item Descriptions (DIDs) for non standard DIDs

Data Item Descriptions have not been included in this document. Standard DIDs will be furnished upon request. Once a contract begins, changes to this document will be made in the same manner as for any other section of the contract.

2.0 INSTRUCTIONS FOR INTERPRETING DD FORM 1423 AND RELATED

INFORMATION AND FOR PREPARATION AND DELIVERY OF DATA

2.1 GENERAL

The CDRL, DD Form 1423-1 shall be used as the main contractual document which lists the data/information items that are formally deliverable to the Government under the contract to which the CDRL applies. Exceptions may be noted in the Contract Schedule and/or the Contract General Provisions, either of which may require submission of other data. Each

CDRL item has an assigned a data item number (e.g. A001), a DID identifier and a data item title, and in some cases a subtitle. Additionally, the CDRL provides other information such as: frequency of submission of deliverable item, as-of-date, dates or times of first and subsequent submissions, distribution; and, approvals.

Data Item Descriptions, tailored as necessary, provide detailed instructions for preparation of data which is listed on the CDRL. The DIDs are identified by title and assigned data item alpha-numeric codes: e.g., DI-F-6010. In those instances in which a DID has been generated to fit a particular requirement, and the standard DID does not exist or does not supply the appropriate information, it is assigned a unique identifier code (e.g., OT-MRT-20081).

The contractor shall develop a CDRL sequence-to-Performance Work Statement (PWS) index as part of the their proposal This cross reference list will show all the applicable CDRL sequence numbers in the left hand column and, in the right column, indicate where each CDRL sequence numbered item applies in the contract

This CDRL package, as presented in Section 3, is broken into two specific Exhibits for clarification. Exhibit “A” CDRLs are applicable to deliverables associated with the execution of the CDPP contract itself. Exhibit “B” CDRLs are applicable to deliverables associated with recommended developmental program. As an example, there are separate and distinct requirements for the A002 Contract Work Breakdown Structure, which refers to execution of the CDPP, and the B012 Work Breakdown Instruction, which refers to the recommended developmental program.

2.2 INTERPRETATION OF THE CDRL, DD FORM 1423

This data requirements document utilizes the DD 1423-1 version. The blocks are essentially self-explanatory and are delineated on the DD Form 1423-1. Additionally, instructions, definitions and codes shown on the DD Form 1423 are contained in DFAR 253.303 AR 700-

51. Further instructions and guidance are provided for Blocks 7, 8, 9, 10, 11, 12, 13, 14, and

16 in the following sections.

2.2.1 Block 7. DD 250 Req – Electronic notification will be used when transmitting the reports or data listed in the CDRL when Block 7 is coded “EN.” This electronic notification fulfills the contractual delivery requirements normally provided by a Letter of Transmittal. The electronic notification via e-mail will be addressed to the requiring office shown in CDRL Block 6 and Block 14a copy addressees. The electronic notification will reference the CDRL sequence number(s) of the report or data and advise that the report or data required by the CDRL has been sent to the electronic data warehouse. For data requirements which have an "A" code in CDRL Block 8, the electronic notification will contain a request for formal approval from the Government and the reports or data sent to the electronic data warehouse will be labeled “Draft” in its filename. Upon receipt of Government approval of the CDRL report or data, an electronic distribution shall be made to the Block 6 and Block 14a addressees advising an “Approved” report or data has been sent to the electronic data warehouse with the file name inc luding “Approved.” For Block 7 codes other than EN, the acceptance will be by DD 250 action as defined in DOD 5010.12-M, and

DFAR Supplement Appendix F

2.2.2 Block 8. APP Code A - When "A" is placed in Block 8, Government approval of the submitted data is required; distribution of the approved data will be deferred pending receipt of approval and/or comments to the submitted draft. The Government’s and contractor's responsibilities for timely processing of such submitted data is identified in

Block 16 by the expression "APPROVAL: GXX/CYY" (numbers are inserted in place of XX and YY which represent numbers of calendar days). For example “APPROVAL: G04/C03” is interpreted as follows: "Government response (approval/disapproval/comments /technical direction) will be provided within 4 calendar days of receipt of the data from the contractor;

the contractor will update or revise the data (reflecting the Government's comments) and resubmit within 3 calendar days of receipt of the Government's response. When an "N/A" appears in Block 8, draft data are not required before submittal of final data.

2.2.3 Block 9. Distribution Statement – Distribution code “D” applies to all CDRL deliverables, which restricts dissemination to DOD and DOD contractors only.

2.2.4 Block 10. Frequency - The frequency of data submittal. Entries in this Block are explained in Table 1, “Data Submittal Frequency Codes”. If the data are of a recurring type, it is to be submitted at the end of the reporting period established in this Block unless otherwise indicated in Block 16 or Block 13.

TABLE 1. BLOCK 10 DATA SUBMITTAL FREQUENCY CODES

CODE FREQUENCY

ANNLY

Annually

ASGEN*

As generated

ASREQ*

As required

BI-MO

Every two months

BI-WE

Every two weeks

CP/RQ

Change pages as required

DAILY

Daily

DFDEL

Deferred delivery (See DFARS 252.227-7026)

MTHLY

Monthly

ONE/P

One Preliminary

ONE/R

One time with revisions

OTIME

One time (Does not include draft submissions)

QTRLY

Quarterly

R/ASR*

Revisions as required

SEMIA

Every six months

WEEKLY

Weekly

XTIME*

Multiple separate submittals (2TIME, 3TIME, etc.)

(Does not include draft submissions). Requirement is fully described in Block 16. Used in lieu of other codes where such are inadequate to define requirement, or used in addition to other codes requiring amplification in Block 16.

*SEE BLOCK 16*

Specific instructions will be found in Block 16 for this item.

2.2.5 Block 11. As of Date – This is the date for cutting off collection of the data. If the data are to be submitted multiple times, a numeral will be entered in this block to indicate the number of calendar days prior to the end of the reporting period, which was established in Block 10, that data collection will be cut off. For example “15” would place the “as of” date for the data at 15 days before the end of the month, quarter, or year, depending on the frequency established in Block 10; a “0” would place the “as of” date at the end of each month, quarter, etc. If the data are submitted only once, the “as of” date will be as follows: year/month/day (e.g., “10/03/01”).

2.2.6 Blocks 12 and 13. Date of First Submission – This is the due date for initial data submission. This is normally date the data are delivered electronically and is entered as year/month/day (e.g., “10/03/01”) or keyed to a specific event or milestone, using a code from Table 2, “Data Submission Codes”.

NOTE: No classified dates are cited in the CDRL.

TABLE 2. BLOCK 12 and 13 DATA SUBMISSION CODES

CODE FREQUENCY

ASGEN

As generated

ASREQ*

As required

DFDEL*

Deferred delivery

XMAC**

Months after contract award

XDAC**

Days after contract award

XDACM**

Days after contract modification

XDADO**

Days after delivery order

XDARP**

Days after reporting period

XDARC**

Days after receipt of comments

XDATC**

Days after test completion

XDPTT**

Days prior to test

NLT

No later than

EOC

End of contract

EOM

End of month

EOQ

End of quarter

*SEE BLOCK 16

Specific instructions will be found in Block 16 for this item.

** The “X” is assigned a value indicating the number of time units; e.g., 2MAC is 2 Months after contract award.

2.2.7 Block 14. Distribution Addressee Code List - This section specifies the physical mailing addresses (if required) and electronic notification addresses for the

Block 14.a addressee codes listed on the CDRLs.

DTIC Email: Notification address to be supplied at time of award

Mailing Address:

Defense Technical Information Center

Cameron Station Alexandria, VA 22314

DCMA Email: Notification address to be supplied at time of award

DCMA Office for Contractors Facility Address to be supplied at time of award

MDA/DVM Email: Notification address to be supplied at time of award

Missile Defense Agency Next Generation Aegis Missile - Program Manager

ATTN: MDA/DVM

Ms. Kari Anderson Bldg. 5222, Martin Road

Redstone Arsenal, AL 35898

MDA/DACV Email: Notification address to be supplied at time of award

Missile Defense Agency

Next Generation Aegis Missile – Contracting Officer

ATTN: MDA/DACV

NGAM Contracting Officer

MDA/DVM/PM&I

Missile Defense Agency

Next Generation Aegis Missile - Program Management and Integration

(Email notification address to be supplied at time of award)

ATTN: MDA/DVM/PM&I

2.2.8 Block 16. "Remarks" - This block is used to modify the DID preparation instructions. Block 16 also provides a place for specific instructions relating to:

report frequency, as of date, time of first submission, and time of subsequent submissions.

2.2.9 Distribution Control – Modifications to the distribution of any contract report in any stage of development or completion is prohibited without the approval of the Contracting Officer.

2.2.10 Special Markings

Disclaimer Statement - A conspicuous disclaimer statement shall be contained on the cover of all reports as follows:

"The views, opinions, and/or findings contained in this report are those of the author(s) and should not be construed as an official Missile Defense Agency position, policy, or decision unless so designated by other documentation."

Distribution Statement – All material will be marked “Reproduction requires approval of originator or higher DOD Authority. Further dissemination only as directed by MDA/DVM or higher DOD Authority. Request for this document must be referred to: (to be supplied at contract award).”

Warning – All material will be marked “This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or Executive Order 12470. Violation of these export laws is subject to severe criminal penalties." "Destruction Notice - All material will be marked as follows: For classified documents, “Follow the procedures in DOD 5200.22M, Industrial Security

Manual, Section II-19 or DOD 5200.1-R, Information Security Program Regulation, Chapter IX. For unclassified, limited documents, “Destroy by any methods that will prevent disclosure of contents or reconstruction of the document." “Pre-Decisional Material

- All material will be marked “Pre-Decisional, Exemption (b) (5).”

For Official Use Only. – All material will be marked “For Official Use Only”

2.3 Digital Delivery of Data and Electronic Data Warehouse

The contractor shall establish and maintain throughout the duration of this contract a secure password-protected, web-based data warehouse for the electronic delivery of all unclassified data delivered under this contract. A list of authorized personnel for access to the data warehouse will be provided by the Government. Upon electronic delivery of data to the data warehouse, the contractor shall notify by electronic notification in lieu of transmittal letter, all CDRL Block 6 and 14 addresses of such delivery.

SECTION 3.0

CONTRACT DATA REQUIREMENTS

INDEX LIST

Exhibit A – CDPP Contract Effort

DATA ITEM NO. TITLE OF DATA ITEM DID or Reference Document

A001 Management Plan DI-MGMT-80004A

A002

Contract Work Breakdown Structure (WBS) and Dictionary DI-MGMT-81334C

A003 Integrated Master Schedule – Key Events N/A

A004 Cost Performance Report (EVMS Included) DI-MGMT-81466A

A005 Contract Funds Status Report DI-MGMT-81468

A006 Monthly Status Report DI-MGMT-80368A

A007 Agenda DI-ADMN-81249A

A008 Report Record of Meetings and Minutes DI-ADMN-81505

A009 Presentation Material DI-ADMN-81373

A010 Contract Summary Report DI-ADMN-80447A

A011

MAP and PMAP Requirements Applicability

Matrix OT-MAP-090721

A012

Performance Report on Small Business

Utilization DI-MGMT-81642

A013 Test Plan DI-NDTI-80566A

A014 Test Report - Quick Look DI-MISC-80652

A015 Test Report - Final DI-MISC-80652

A016

Scientific and Technical Reports -

Performance Analysis Predictions DI-MISC-80711A

A017 Analysis Modeling and Simulation Plan DI-IPSC-81427A

Exhibit B – Recommended Program

B001 Concept Tec Concept Technical Parameters for Analysis Interceptor Data Template & Data

Requirements NGAM

B002

Operational Concept Definition - Concept

Functional and Physical Architecture / Allocations DI-IPSC-81430A

B003 Risk Management Plan DI-MGMT-81808

B004 Critical Program Technologies DI-RELI-80685

B005

System/Subsystem Specification - Draft Missile System Specification DI-IPSC-81431A

B006 Performance Models and Simulations DI-MSSM-81751

B007

MAP and PMAP Requirements Applicability Matrix OT-MAP-090721

B008

Failure and Summary Analysis Report -

Failure Modes, Effects and Criticality Analysis (FMECA) Report DI-RELI-80255

B009

Draft Concept Cost Analysis Requirements Description CARD MDA Handbook V.6

B010

IMS and IMP - Development and Production

Integrated Master Schedule and Integrated

Master Plan

DI-MGMT-81650

B011

WBS - Development and Production Work

Breakdown Structure with Dictionary DI-MGMT-81334C

B012

Product Development, Production, and

Operating & Support Cost Estimates DI-FNCL-80166C

B013 Integrated Logistics Support DI-ILSS-80095 smithdon Typewritten Text

SECTION 4.0

One-Time (OT) Data Item Descriptions

Section 4.0 Data Reference Data Items

B001 Concept Technical Parameters for Analysis Interceptor Data Template

B001 Concept Technical Parameters for Analysis Data Requirements NGAM

A011 / B007

Map and PMAP Requirements Applicability

Matrix OT-MAP-090721

B009

Draft Concept Cost Analysis Requirements Description GFI List

DATA ITEM DESCRIPTION Form Approved

OMB NO. 0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including t he 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 inf ormation, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate f or Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503.

1. TITLE

Interceptor Data Template

2. IDENTIFICATION NUMBER

XX-XXX-XXXXX

3. DESCRIPTION/PURPOSE

4. APPROVAL DATE

(YYMMDD)

5. OFFICE OF PRIMARY RESPONSIBILITY (OPR)

6a. DTIC APPLICABLE 6b. GIDEP APPLICABLE

7. APPLICATION/INTERRELATIONSHIP

7. Th is DID provides a list of the data items required to support the configuration of Contractor interceptor designs in the

Government Simulation tool.

8. APPROVAL LIMITATION

9a. APPLICABLE FORMS

9b. AMSC NUMBER

10. PREPARATION INSTRUCTIONS

Metric Data

Baseline Predicted

Nominal Mass

Estimated Mass with MGA Applied

Component (kg)

MGA

(kg)

Missile 10.0 11.5

Payload 10.0 11.5

KV Weight w/ Cover 10.0 15.00% 11.5

Sensor

Optics Cover

Guidance Electronics (IMU + avionics)

Battery(s)

Wiring Harness

DACS Inert

DACS fuel

Data link, TM, ant

Structure/Misc hardware

Misc Hardware

Ballast

Guidance Unit 0.0 0.0

Mount Plate 15%

Cover

KV relay

Component (kg)

MGA

(kg)

Misc Hardware

Separation Assy

Nosecone 0.0 0.0

Nosecone Assy (deployed) 15%

Nosecone shroud

Nosecone deployment system

Aft shroud Assy

Aft shroud

Misc Hardware

Deployment System

Third Stage 0.0 0.0

3rd Stage Burn out Mass 15%

Rocket Motor Assy 0.0 0.0

Rocket Motor Inerts 0.0 0.0

Case + Internal Insulation

Cable Raceway(s)

Igniter + ISD

Nozzle Assy

TVC Components (battery+brackets + cabling

External Insulation

Misc motor hardware (o-rings, nut plates ..)

Nozzle Shroud

ACS

Aero Surfaces

Harnesses

Stage Separation Assy (3rd Stage to Payload)

Misc stage hardware

Total Expelled Weight 0.0 0.0

Propellant

Expelled Insulation

Second Stage 0.0 0.0

2nd Stage Burn out Mass 15%

Rocket Motor Assy 0.0 0.0

Rocket Motor Inerts 0.0 0.0

Case + Internal Insulation

Cable Raceway(s)

Component (kg)

MGA

(kg)

External Insulation

Misc motor hardware (o-rings, nut plates ..)

Nozzle Shroud

ACS

Aero Surfaces

Harnesses

Stage Separation Assy (2nd Stage to 3rd Stage)

Stage Separation Assy (1st Stage to 2nd Stage)

Misc stage hardware

Total Expelled Weight 0.0 0.0

Propellant Mass

Expelled Insulation

First Stage 0.0 0.0

1st Stage Burn out Mass 15%

Rocket Motor Assy 0.0 0.0

Rocket Motor Inerts 0.0 0.0

Case + Internal Insulation

Cable Raceway(s)

Igniter + ISD

Nozzle Assy

TVC Components (battery+brackets + cabling

External Insulation

Misc motor hardware (o-rings, nut plates ..)

Nozzle Shroud

ACS

Aero Surfaces

Harnesses

Stage Separation Assy (1st Stage to 2nd Stage)

Canister Restraint Hardware

Misc stage hardware

Total Expelled Weight 0.0 0.0

Propellant

Expelled Insulation

11. DISTRIBUTION STATEMENT

Public reporting burden for this collection of information is estimated to average 110 hours per response, including t he 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 inf ormation, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate f or Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503.

1. TITLE

Interceptor Data Requirements NGAM

2. IDENTIFICATION NUMBER

XX-XXX-XXXXX

3. DESCRIPTION/PURPOSE

7. Th is DID provides a list of the data items required to support the configuration of Contractor interceptor designs in the

Government Simulation tool.

Overview

• Parameters units/formats

– All parameters in SI units

• Angles in degrees

– Definition of random variab les

• Uniform: minimum and maximum values

• Gaussian: mean and 3-sigma values

– All positions/orientations defined with respect to Body Reference Frame (BRF)

• X-axis along centerline and out the nose with Y-Z axis defined fo r a right handed system – origin to be defined by contractor

– Table Formats – see Appendix

Propulsion:

For each stage,

• Motor wet & dry mass (include expendable inerts)

• Expendable propellant mass

• Nozzle exit area

• Nozzle location(s) in BRF

• Nozzle alignment uncertainty

• Motor Type

– Solid

• Complete “Ballistics Data” tab in “Interceptor Data Template” spreadsheet

• Minimum/maximum burn time across operating temperature range

• Total Impulse uncertainty

– Liquid

• Nominal thrust level

• Thrust bias and repeatability uncertainties

• Specific impulse

• Control System Type

– Thrust Vector Control

• Nozzle 2 nd order response characteristics

• Nozzle deflection and deflection rate limits

– Reaction Control System

• Nozzle locations in BRF

• Thrust level(s)

• Propellant mass

• Specific impulse

Aerodynamics:

For each aerodynamic configuration,

• Aero reference area

• Aero reference length

• Moment reference point location in BRF

• Force/moment coefficient tables

– For axi-symmetric airframe, 2-d imensional tables as a function of Mach and Total angle-of-attack

– For non-axi-symmetric airframe, 3-dimensional tables required – independent variables may be:

• Mach, Total angle-of-attack, Aerodynamic Roll Angle – f(M, aT, f)

• Mach, Pitch angle-of-attack, Yaw angle-of-attack – f(M, a, b)

– CA (axial force coefficient) – Power on and Power off tables – includes all drag terms except skin frict ion

– CN (normal force coefficient)

– CY (side force coefficient) – not required for axi-symmetric airframe

– Cl (rolling moment coefficient)

– Cm (pitching moment coefficient)

– Cn (yawing moment coefficient) – not required fo r axi-symmetric airframe

– For configurations that include aerodynamic control surfaces

• Definition of fin configuration

• Incremental aero tables

– Define increments to each aero coefficient for deflect ion of each fin

– 4-dimensional tables – f(M, aT, f, di) or f(M, a, b, di)

• Additional tables

– CSF (skin friction coefficient) – 2-dimensional table – function of Mach and Altitude

– Cmq, Cnr, Clp, etc. (rate damping coefficients) – 1-d imensional table – function of Mach

• Uncertainty of each coefficient

• Complete “Physical Descript ion” tab in “Interceptor Data Template” spreadsheet

Mass Properties:

• Complete “Mass Props Details” tab in “Interceptor Data Template” spreadsheet, defining component masses and mass growth allowances

• Provide vehicle mass properties table for each configuration, defining center-of-grav ity vector and inertia tensor as a function of interceptor mass

– Configurat ions

• 1 st

Stage Burn

• 2 nd

Stage Burn

• 3 rd

Stage Burn with Nosecone

• 3 rd

Stage Burn without Nosecone

• KV

– Table format – 10 co lumn format

• Column 1 – Total vehicle mass – row 1 = burnout mass, row N = ignit ion mass - kg

• Columns 2-4 – Center-of-grav ity position in BRF (x,y,z) – meters

• Columns 5-7 – Moment of inert ia (Ixx, Iyy, Izz) – kg-m

• Columns 8-10 – Product of inert ia (Ixy , Ixz, Iyz) – kg-m

IMU / Navigation:

Provide characteristics of each IMU (Guidance Sect ion and/or KV)

Location in BRF

Gyro response characteristics

- Natural frequency, damping ratio, dynamic range

Gyro Error model

- Bias, scale factor, non-orthogonality, random walk, etc.

- Accelerometer response characteristics

- Natural frequency, damping ratio, dynamic range

Accelerometer Error model

- Bias, scale factor, non-orthogonality, random walk, etc.

Description of GPS aid ing

KV:

DACS

• Propellant Mass

• For each nozzle,

– Location and orientation in BRF

– Alignment error

– For liquid DACS,

• Force level, specific impulse, minimum on-time, on/off delay, response characteristics, repeatability

– For solid DACS,

• Description of throttling (o r sustain/divert pulse) functionality and relat ionship of thrust level and specific impulse to throttle level (or sustain/divert thrust)

• Turn down ratio

• Valve response characteristics

Seeker

• Field-of-v iew

• IFOV

• NEI

• Update interval

• Measurement noise

• Processing delay Separation Dynamics

• Description of separation mechanism, tip-off rates, and separation DV

Boost Flyout Model:

• Description of flyout/engagement constraints, i.e., min stage separation altitudes, maximum staging dynamic pressure and angle-of-attack, maximum lateral/axial g-loads, dynamic pressure for nosecone separation, min imum p lanned intercept altitude, minimum planned endgame time, etc.

• General description of guidance modes, i.e., hold vertical (launch-xx seconds), pitchover (xx-xx seconds), etc.

• Autopilot block d iagram/algorithm with gain schedules of sufficient detail to replicate in government model

• Flyout fan to support verificat ion of government model

– To include nominal time histories of ground range, altitude, velocity, flight path angle, pitch angle, angle -of-attack, mass, delivered thrust, body rates, body-frame acceleration vector (no gravity), CG location (body coordinates)

• Timing/update interval of flight algorithms

Midcourse and Endgame Model:

• Description of Midcourse and Endgame Sequencing/Events

• Description of track filter, guidance, and autopilot algorithms – to include

– Guidance modes & criteria for sequencing

• Guidance commands in response to midcourse IFTUs

• Endgame guidance

• Criteria for terminal aimpoint shift

– Description and block d iagram of DACS throttling/firing logic

• Timing/update interval of flight algorithms

Public reporting burden for this collection of information is estimated to average 110 hours per response, including t he 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 inf ormation, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate f or Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503.

1. TITLE

MAP and On Time Delivery Metrics

2. IDENTIFICATION NUMBER

OT-MAP-090721

3. DESCRIPTION/PURPOSE

MAP Core Metrics provide uniform quality performance data on hardware and software performance for major MDA programs.

7.1 This DID contains the format and content preparation instructions for the data products generated by specific task requirements delineated in the contract.

7.2 This DID may be used on any type contract where a vehicle fo r control and processing of specific quality metrics is neede d.

Format

A sample filled-in reporting tool is attached as Appendix A. This tool is used for automated data entry into the MAP and MARC databases and changes to the tool are not authorized without prior written approval of MDA/QS.

Content

Each of the MAP Metrics has mult iple primary data elements which generate one or more overall results describing the performance of specific tasks. MAP hardware metric 3.1.3.1.6 and software metric 3.1.3.1.8.d are no longer required. The reporting tool contains Hardware and Software specific versions of MAP Metric 3.1.3.1.4 and an On Time Delivery fo rm for reporting crit ical item deliveries monthly.

Each metric requires the entry of common data in the heading. These include:

Date: Month and Year being reported

Program: MDA designation of the reporting organization

Component: Optional entry fo r data specific to a component of an MDA Program, e.g., THAAD Missile, GMD IMU, etc. Each component should be entered on a separate page.

Subcomponent: Optional entry for data specific to a subcomponent of a listed component. Each subcomponent should be entered on a separate page.

Hardware/Software: For all MAP metrics listed in this DID, select Hardware o r Software, as applicable, from the drop down menu.

Build: Optional entry for data specific to only one unit of a completely specified Program, Component or Subcomponent.

Contractor: Enter the Contractor responsible for the data being reported from the drop -down menu.

MAP Metric 3.1.3.1.1 Nonconformance Report Summary

NC Summaries will be prepared monthly fo r electronic delivery to MDA/QS using the on-line reporting tool.

Definitions applicable to the NC Reporting Process:

Nonconformance or Deficiency - Any deviation from a requirement specified in released engineering or manufacturin g documentation or contract requirements.

NC Closure – No further action is required to eliminate the reported deviation.

Preventive Action - Actions taken to prevent recurrence of the reported defect and/or to screen defects which may have occurred in similar material.

Correct ive Action - Actions taken to correct the documented defect

Rework – Actions taken to bring a defective item into full compliance with all applicable requirements.

Repair – Actions taken to return a defective item to useable condition, but not necessarily into full compliance with all applicable requirements.

NC form instructions.

Nonconformance reports are required for any observed deviation from requirements contained in released engineering and manufacturing documentation. Supplier formats may be used as long as the following min imum data is available on each NC report:

o Document number o Date in itiated o Part number of deficient part and highest level assembly affected o Description of deficiency, including a reference to the applicable requirement o Disposition information, including Preliminary Material Review Board, Material Review Board and Failure

Review Board actions taken to determine and implement required preventive and corrective action.

o Closure information, includ ing Rework and Repair (standard and non-standard) instructions, Return to Vendor, Scrap, and Use As Is decisions

Specific data required to complete the reporting tool for this metric include:

Total NCs reported as Open (pending action) during the previous reporting period

Number of New NCs opened during the reporting period

Number of NCs closed by PMRB action, MRB act ion and FRB act ion during reporting period

Number of open NCs pending closure by PMRB, MRB and FRB at end of reporting period

Number of open NCs in 30 day increments (0-30, 31-60, 61-90 and >90 days) at the end of the reporting period

Total number of open NCs at the end of the reporting period (This metric is calculated twice in the form. Both totals should match.)

The first NC Summary Report will treat legacy informat ion as new data and a starting position will be included in the Comments block fo r this first NC Report Summary only

MAP Metric 3.1.3.1.2 Waivers and Deviations

Type I waivers or deviat ions are defined as those affecting performance, durability, interchangeability, systems interface, health or safety. All others are Type II waivers or deviations.

The specific data required to complete the reporting tool for this metric includes:

Total count of Type I waivers submitted to the MDA PCB for approval during reporting period

Total count of Type I waivers approved by the MDA PCB during reporting period

Average cycle time fo r approval of Type I Waivers during reporting period

Total count of Type II waivers submitted during reporting period

Total count of Type II waivers approved during reporting period

Total count of Type I deviations submitted to the MDA CCB for approval during reporting period

Total count of Type I deviations approved by the MDA PCB during report ing period

Average cycle time fo r approval of Type I Deviations during reporting period

Total count of Type II deviations submitted during reporting period

Total count of Type II deviations approved during reporting period

MAP Metric 3.1.3.1.3 Change Requests

Class I and II Change Requests are defined in MAP paragraph 3.10.3.1.2.

The specific data required to complete the reporting tool for this metric includes:

Total count of Class I Change Requests submitted to the MDA PCB during reporting period

Total count of Class I Change Requests approved by the MDA PCB during reporting period

Average Cycle time fo r Class I Change Request approvals during reporting period

Total count of Class II Change Requests submitted during reporting period

Total count of Class II Change Requests approved during reporting period

Average Cycle time fo r Class II Change Request approvals during reporting period

MAP Metric 3.1.3.1.4a Hardware Design Escapes

Design escapes include failures and defects found through analysis attributed to design.

The specific data required to complete the reporting tool for this metric includes:

Number of design escapes detected during the reporting period

Location design escape was located – Supplier facility and level of assembly, inspection or test

Disposition of design escape (Corrective and Preventive Action)

MAP Software Metric 3.1.3.1.4 b Software Design Escapes

The specific data required to complete the reporting tool for this metric include:

Current Phase - selected from the drop-down menu

Number of software requirements

Development Completed? Select Yes or No from the drop-down menu.

Percentage of design escapes detected in-phase

For each completed or partially completed phase listed on the form, enter the number of defects found during th e phase which originated during the phase. Also enter the number of defects detected which were determined by analysis to have originated in any earlier phase.

All other data for this metric on this form is automatically calculated. Enter any comments app licable to this metric in the supplied space.

MAP Metric 3.1.3.1.5 Foreign Object Elimination

Foreign Object Damage and Debris (FOD) incidents are to be reported monthly.

Total number of FOD related incidents (damage and debris)

Total number of FOD related incidents resulting in scrap, rework, or repair

MAP Metric 3.1.3.1.7 Program Quality Staffing

The number of planned quality personnel during the reporting period

The number of on-board quality personnel during the reporting period

MAP Software Metric 3.1.3.1.8a Earned Value Work Performed (Schedule Performance Index (SPI)) and MAP

Software Metric 3.1.3.1.8 b Earned Value Costs (Cost Performance Index (CPI))

The specific data required to complete the reporting tool for this metric include:

Work Breakdown Structure (W BS) Number for each active software component during the reporting period

Budgeted Cost of Work Performed (BCWP)

Budgeted Cost of Work Scheduled (BCWS)

Actual Cost of Work Performed (ACWP)

MAP Software Metric 3.1.3.1.8 c Staffing Adequacy (SA )

Actual number of staff through the end of the reporting period

Planned number o f staff through the end of the reporting period

Number of staff categorized by seniority who have left the software team during the reporting period

MAP Software Metric 3.1.3.1.8 e Software Requirements Index (SRI)

The current phase of the program selected from the drop-down menu

For the selected phase only o Number of Requirements Allocated to Software o New Requirements o Modified Requirements o Deleted Requirements o Slipped Requirements o Total requirements (N+M+D+S) in Prev ious Reporting Period

MAP Software Metric 3.1.3.1.8 f Software Test Coverage

Software tests scheduled through the end of the reporting period

Software tests completed through the end of the reporting period

Software tests passed through the end of the reporting period

Number of software requirements covered by tests during reporting period

MAP Software Metric 3.1.3.1.8 g Source Lines of Code (S LOC)

Current Life Cycle Phase selected from the drop-down menu

Estimated number of source lines of code to be delivered at completion

Actual number of source lines of code developed during reporting period

MAP Software Metric 3.1.3.1.8 h Defect History

Number of defects opened in the developed software during the reported period by criticality (Category 1, 2, 3 and 4&5)

Number of defects closed in the developed software during the reported period by criticality (Category 1, 2, 3 and 4&5)

MAP Software Metric 3.1.3.1.8 i Defect Density

Cumulat ive number of defects discovered by criticality (Category 1, 2, 3 and 4&5)

Source Lines of Code developed to date

On Time Delivery Metric

a. Definit ions.

Critical Items are identified by each Program's Critical Item List, IMS and/or Line of balance report. Critical Items may include hardware, software, CDRL items or any combination.

Scheduled Delivery Date is the Program Need Date at the beginning of the reporting month for each crit ical item to be delivered during that month. For the purpose of this report, scheduled delivery dates do not change during the month.

On time, or early, delivery is defined as on, or before, the existing Program Need Date at the beginning of each month.

On time, or early, only applies to critical item deliveries scheduled at the start of the reporting month.

b. Form instructions.

For each unique combination of Supplier, Location, and Program with scheduled critical item deliveries in a month use one row of the input form. Mult iple crit ical item deliveries from the same Supplier/Location/Program combination may be combined on one row. Enter data for Tier 1, 2 and 3 suppliers only. Data may optionally be reported at the

Component level.

Complete Supplier field in accordance with standard Supplier Road Map nomenclature. Refer to https://portal.mda.mil/portal/directory/(qs)_safety,_quality,_and_mission_assurance/supplier_road_map

Unscheduled critical item deliveries are not to be included in the current report. If a critical item is delivered before its scheduled need date, it may no longer qualify as a crit ical item. If it remains on the critical list after delivery for some reason, it may be counted as on time during the scheduled month, but not during the delivered month.

If a delivery is late to the Program Need Date, but received during the current month, it is the Program's option to count it as on time, or late depending on the Program's impact assessment of the late delivery. Any planned delivery rescheduled to a new month, will be counted as late during the current month.

Appendix A is available at:

https://portal.mda.mil/portal/server.pt/gateway/PTARGS_0_148935_387_315_4397_43/communitylist/code/download.asp?ID=16033&commID=315

Questions about the required content for the reporting tool should be addressed to MDA/QS

DD Form 1664, APR 89 Previous editions are obsolete Page 5 of 5 https://portal.mda.mil/portal/directory/(qs)_safety,_quality,_and_mission_assurance/supplier_road_map https://portal.mda.mil/portal/server.pt/gateway/PTARGS_0_148935_387_315_4397_43/communitylist/code/download.asp?ID=16033&commID=315