NOTE: The signature page must include at minimum the signatures of the
Cost Engineering Group Supervisor and the Project Manager. Additional
signatures are not required but welcome.

**\[Project Name\]**

**Cost Analysis Data Requirements (CADRe)**

\[Milestone Event or CADRe Plus\]

Revision as of

\[date\]

+---------------------------------+---+---------------------------------+
| Prepared by \*                  |   | Reviewed by:                    |
+---------------------------------+---+---------------------------------+
| Date                            |   | Date                            |
+---------------------------------+---+---------------------------------+
| Reviewed by\*:                  |   | Approved by:                    |
+---------------------------------+---+---------------------------------+
| Date                            |   | Date                            |
+---------------------------------+---+---------------------------------+
| Prepared by:                    |   | Reviewed by:                    |
+---------------------------------+---+---------------------------------+
| Date                            |   | Date                            |
|                                 |   |                                 |
| Cost Engineer                   |   | Project System Engineer         |
+---------------------------------+---+---------------------------------+
|                                 |   |                                 |
+---------------------------------+---+---------------------------------+
| Prepared by                     |   | Reviewed by:                    |
+---------------------------------+---+---------------------------------+
| Date                            |   | Date                            |
|                                 |   |                                 |
| Cost Engineer                   |   | Project Business Manager        |
+---------------------------------+---+---------------------------------+
|                                 |   |                                 |
+---------------------------------+---+---------------------------------+
| Reviewed by:                    |   | Approved by:                    |
+---------------------------------+---+---------------------------------+
| Date                            |   | Date                            |
|                                 |   |                                 |
| Supervisor, Cost Engineering    |   | Project Manager                 |
| Group                           |   |                                 |
+---------------------------------+---+---------------------------------+

\*Customize if signatures are used to sign CADRe

# Part A -- General Descriptive Information

This opening paragraph introduces the reader to the document,
identifying what will be found below in terms of summary. **EXAMPLE**:
\[This section contains overview descriptions of the Mars Exploration
Program, the mission, the flight and ground systems to accomplish the
mission, and how the Phoenix Project that proposes to execute the
mission\]

## A.1 System Description

Summary of the system including goals or brief overview of the success
criteria.

## A.1.1 System Overview & Launch

Summary of the entire system including launch. Diagrams depicting launch
vehicle configuration along with system wide block diagrams are
encouraged. Summarize relevant constraints and or assumptions on launch
and arrival.

## A.1.2 Cruise

Summary of the cruise portion of the mission including significant
dates, maneuvers and operations on board during cruise along with a
diagram depicting the trajectory and cruise stage configuration if
available. Identify levels of redundancy key aspects of the design and
other relevant information specific to this system.

## A.1.3 EDL

Summarize of the entry, descent and landing portion of the mission. This
may be broken out into three sub descriptions if needed. Describe key
moments and operations taken by the EDL system during approach and
landing. Include configuration and process diagrams if available.
Identify levels of redundancy key aspects of the design and other
relevant information specific to this system.

## A.1.4 Surface

Describe surface operations and systems along with configuration
diagrams and block diagrams. Identify levels of redundancy key aspects
of the design and other relevant information specific to this system.

## A.2 Subsystem Description

Intro to the subsystem descriptions. **EXAMPLE \[**MSL features a Cruise
stage, EDL stage and Surface stage each with an array of subsystems
ranging from avionics to thermal. In a few cases these systems are
integrated across all three flight elements. The following section
identifies and briefly explains each subsystem according to the parent
flight element.\]

### A.2.1 Structures Subsystem

Summarize the structural subsystem for each flight element. Identify and
describe key features, interfaces and describe configuration or block
diagrams that are presented. Include descriptions of specific structural
items such as booms, masts, mobility systems. Also discuss assumed
heritage and identify design assumptions, constraints and TRL levels.

### A.2.2 Propulsion Subsystem

Summarize the propulsion subsystem for each flight element where
applicable. Identify and describe key features, interfaces, operations
and describe configuration or block diagrams that are presented. Also
discuss assumed heritage and identify design assumptions, constraints
and TRL levels.

### A.2.3 Thermal Subsystem

Summarize the thermal subsystem for each flight element where
applicable. Identify and describe key features, interfaces, operations
and describe configuration or block diagrams that are presented. Also
discuss assumed heritage and identify design assumptions, constraints
and TRL levels.

### A.2.4 Power Subsystem

Summarize the power subsystem for each flight element where applicable.
Identify and describe key features, interfaces, operations and describe
configuration or block diagrams that are presented. Also discuss assumed
heritage and identify design assumptions, and TRL levels.

### A.2.5 Avionics Subsystem

Summarize the avionics subsystem for each flight element where
applicable. Identify and describe key features, interfaces, operations
and describe configuration or block diagrams that are presented. Also
discuss assumed heritage and identify design assumptions, constraints
and TRL levels.

### A.2.6 Telecom Subsystem

Summarize the telecom subsystem for each flight element where
applicable. Identify and describe key features, interfaces, operations
and describe configuration or block diagrams that are presented. Also
discuss assumed heritage and identify design assumptions, constraints
and TRL levels.

### A.2.7 Attitude Control Subsystem

Summarize the attitude and control subsystem for each flight element
where applicable. Identify and describe key features, interfaces,
operations and describe configuration or block diagrams that are
presented. Also discuss assumed heritage and identify design
assumptions, constraints and TRL levels.

### A.2.8 Software Subsystem

Summarize the software subsystem for each flight element where
applicable. Identify and describe key features, interfaces, operations
and describe configuration or block diagrams that are presented. List
and describe each CSCI in terms of functionality. Also discuss assumed
heritage and identify design assumptions, constraints and TRL levels.

### A.2.9 MOS/GDS Subsystem

Summarize the MOS/GDS subsystem for the flight system. Identify and
describe key features, interfaces, operations and describe configuration
or block diagrams that are presented. Also identify design assumptions
and constraints. List the facilities required for MOS/GDS and identify
how these facilities will be procured, managed and operated.

## A.3 Payload Description

Summarize, in detail, each individual instrument's capability and goal
and provide a detailed account of the operations of the instrument if
complicated. Provide configuration diagrams of individual instruments
and an overall configuration diagram of payload suite relative to the
S/C. Also identify design assumptions and constraints and TRL levels.

## A.4 Project Level Description

### A.4.1 Project Management

Summarize project management in terms of how and who oversight and
project responsibilities are delegated to. Identify how project
management will be structured and describe key rolls and
responsibilities in that structure. Provide an organizational chart if
available. Provide project level schedules and explain as needed.
Provide information pertaining to government and non government
contractors along with additional organizations that may be involved.

### A.4.2 Project Systems Engineering

Summarize the primary responsibilities of the systems engineering effort
on the project and include a reference to the level one requirement and
mission success criteria. Include descriptions of the launch approval
and planetary protection.

### A.4.3 Science Team

Summarize the Science Team responsibilities and identify how the science
team will be structured throughout the duration of the mission. Provide
an organizational chart if available and define each responsibility.

### A.4.4 Mission Assurance

Summarize mission assurance for the project in terms of management along
with verification and validation. Reference other documents if needed.

### A.4.5 Education and Public Outreach

Summarize EPO for the project in terms of management and implementation.
Reference other documents if needed.

### A.4.6 ATLO and Testbeds

Describe the project's ATLO plan. Include flow charts depicting test bed
procedure. Identify and describe the test facilities required by the
project and how they will be used. Identify any other NASA or non NASA
facilities that will be utilized during the ATLO process.

### A.4.7 Risk Assessment

Explain or identify where the Risk Management process for the project
may be found. This should include roles and responsibilities of the risk
management process and a descriptive list of the objectives of the
project risk management process. Include the project's significant risks
as defined by the Project System Engineer and any mitigation efforts for
them. Specifically include the 5x5 risk matrix and the risk mitigation
discussions that support it.

### A.4.8 Acquisition Plan

The acquisition plan describes the contract types, acquisition strategy,
and schedule for system development and procurement. For simplicity a
summary of sub contracts totaling one million dollars or more and their
respective type and schedule should be compiled and placed in the
appendix. Include any known international agreements from Headquarters
Program Executive Program exec or Office of External Relations.

### A.4.9 Government Funded Equipment

For simplicity, a summary of GFE should be tabulated in Part A and
identifiable in Part B of the CADRe.

## A.5 Significant Changes since Previous CADRe Submission

The CADRe is intended to document the evolution of a project,
specifically addressing changes in cost, technical (both hardware and
software) parameters, and schedule changes that impact cost. Summarize
changes made since submission of the previous CADRe. Significant changes
are defined when any of the following changes by ten percent or more:
Total cost, Part B technical parameters (hardware and software),
schedule months, or, if any instruments are added or removed. Where
possible provide detail as to *why* the change(s) occurred.

Note: Special attention should be given to this section when developing
a "CADRe Plus"

(Candidates for CADRe Plus are those projects that launched more than
180 days ago). In the CADRe Plus version, this section will document to
the extent possible all cost, technical, schedule, and programmatic
changes that occurred from SRR to LRD which will provide a comprehensive
historical track of the project. Use the additional templates shown
below to complete the CADRe plus.

![](media/image1.wmf){width="6.874305555555556in"
height="8.629861111111111in"}

![](media/image2.wmf){width="5.99375in" height="2.0479166666666666in"}

\* The following template can be found as the last tab in the CADRe Part
B Excel Spreadsheet

When completing the Workforce Analysis template below use FTE/WYE
instead of simple headcount since FTE/WYE implies a full cost with
overhead.

![](media/image3.wmf){width="5.998611111111111in"
height="4.876388888888889in"}

# Summary of Part B -- Technical Data 

Part B is comprised of an EXCEL workbook broken into worksheets
containing system level, payload, flight elements and software.

Summary tables of the information provided in Part B should be placed in
Part A along with a summary table of tracked changes in technical data
from previous CADRe submittals for the project in question. Examples of
the summary tables are provided in the Part B template. There are two
kinds of tables:

1.  System Summary Table has the total system mass, the individual
    flight element masses, and the subsystem masses.

2.  Key Technical Parameters Table describes the system level parameters
    and any technical parameters associated with components in the
    technical metrics worksheets.

Each of the tables found in the Part B template should be considered as
examples only - as the tech metrics are customized for each project, the
tables will need to be updated accordingly.

# Summary of Part C -- Project WBS and Cost

Part C of the CADRe will be a separate EXCEL Workbook. This must reflect
total cost estimate to date and the estimate for completion for the
project and coincide with the data presented in the system level,
payload, flight element, MOS/GDS and software metric sheets. The
project's WBS and dictionary, as well as details of the recurring and
non-recurring cost must be included in the Part C EXCEL file. Part C
also includes a mapping to the NASA standard WBS. A cost summary table
should be included, detailing at least level 1 cost roll-ups. It may
also be beneficial to include cost subsystem summaries for each flight
element.