05_of_19_DRFP_Att_J.1-B_Data_Procurement_Document.docx

DRAFT Request for Proposals 05 of 19 – DRFP Att J.1-B Data Procurement Document

NNC16ZMX004R

NNC16ZMX004R

CONTRACT/RFP

EXHIBIT NUMBER

J.1-B

ATTACHMENT NUMBER

Space Launch System (SLS) Universal Stage Adapter (USA)

PROJECT/SYSTEM

DATA PROCUREMENT DOCUMENT

TBD

CONTRACTOR

DATE

National Aeronautics and Space Administration

DRAFT Request for Proposals 05 of 19 – DRFP Att J.1-B Data Procurement Document

J-2-1

National Aeronautics and Space Administration

DOCUMENT CHANGE LOG

DATA PROCUREMENT DOCUMENT

NO. ISSUE

XXX XXX

XXX

SUPERSEDING:

PAGE:

Contents

INTRODUCTION

Scope Subject to the Rights in Data clause, 52.227-14 Rights in Data-General (MAY 2014), this Data Procurement Document (DPD) sets forth the data requirements in each Data Requirements Description (DRD) and shall govern that data required by the DPD for the contract. The Contractor shall furnish data defined by the DRDs listed on the Data Requirements List (DRL) by category of data, attached hereto, and made a part of this DPD. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this DPD. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) clause, that clause shall take precedence over the DPD, consistent with clause FAR 52.215-8 Order of Precedence—Uniform Contract Format (OCT 1997).

DPD Description This DPD consists of a Document Change Log, an Introduction, a Statement of General Requirements, DPD maintenance procedures, a DRL, and the DRDs.

General Requirements The general requirements, as specified in paragraph 2.0 of this DPD, prescribe those requirements applicable to the preparation, maintenance, and delivery of data that are better defined in aggregate than in the individual DRDs.

Data Requirements List (DRL) Throughout the performance of the contract, the DRL provides a listing of the data requirements of the DPD.

Data Requirements Descriptions (DRDs) Each data requirement listed on the DRL is given complete definition by a DRD. The DRD prescribes content, format, maintenance instructions, and submittal requirements.

Document Change Log (DCL) The Document Change Log chronologically records all revision actions that pertain to the DPD.

DPD Maintenance Procedures Maintenance procedures define the detailed methods to be employed in maintaining the DPD. Detailed maintenance procedures are specified in Section 3.0 of this DPD.

Data Types for Contractual Efforts The types of data and their contractually applicable requirements for approval and delivery are:

STATEMENT OF GENERAL REQUIREMENTS

Applicable/Reference Documents Documents included as applicable documents in this DPD are the issue specified in the Applicable Documents List found in Attachment J.1-C. The Applicable Documents List is to be maintained by the Contractor as specified in DRD USA-007, Configuration and Data Management Plan. Applicable documents listed in Item 12.2 of a DRD are applicable only to the preparation of the deliverable documentation described by that DRD.

References to documents other than applicable documents in the data requirements of this DPD may sometimes be utilized, and shall be indicated in Item 10, Remarks, of the DRD. These do not constitute a contractual obligation on the Contractor. They are to be used only as a possible example or to provide related information to assist the Contractor in developing a response to that particular data requirement.

Subcontractor Data Requirements Where a Subcontractor is performing any part of the work related to a Data Requirement, the Contractor shall ensure these DRDs are levied on the applicable Subcontractor. The Contractor shall integrate and provide Subcontractor data into the applicable Data Requirement. NASA shall have the right to inspect individual Subcontractor data. Subcontractor integration is the responsibility of the Prime Contractor and is addressed in the Contractor’s Project Management Plan.

Document Format

1. All documents may be in Contractor format except when directed otherwise in the DRD, contract clause, or referenced requirement.

1. All documents, unless otherwise noted within the specific DRD, shall be submitted in electronic format using standard Microsoft Office software (Word, Excel, and PowerPoint).

1. In addition to the electronic submittal, one hardcopy package of specific data deliverables shall be delivered to the NASA Contracting Officer for the Government contract file upon request. If a hardcopy package is requested, it shall consist of the Contractor’s Transmittal Memo and one copy of the data deliverable.

1. Contractor may consolidate related DRDs, if approved by NASA.

Data Restrictions and Markings

1. All data produced under this contract shall be in accordance with FAR 52.227-14 Rights in Data-General (MAY 2014). The Contractor shall determine the data restriction that applies to each data deliverable and mark the data restriction on the data coversheet, or indicate the data restriction in the data transmittal package if the data format precludes identification of data restriction directly in the data. The Contractor shall make a determination for each individual data deliverable item, and shall not apply a default or blanket data restriction marking to all data deliverables (e.g., “data may be export restricted”). If NASA does not agree with the Contractor applied data restriction, the NASA Contracting Officer shall return the data to the Contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the “data rights” clause(s) contained in the contract.

The Contractor shall consider the following data restriction categories, as a minimum, and utilize specified marking statements.

If data delivered under this contract is subject to the International Traffic in Arms Regulations (ITAR), the data shall contain an “ITAR Notice” as follows:

International Traffic in Arms Regulations (ITAR) Notice This document contains information which falls under the purview of the U.S. Munitions List (USML), as defined in the International Traffic in Arms Regulations (ITAR), 22 CFR 120-130, and is export controlled. It shall not be transferred to foreign nationals, in the U.S. or abroad, without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exemption is obtained/available from the United States Department of State. Violations of these regulations are punishable by fine, imprisonment, or both.

If data delivered under this contract is subject to the Export Administration Regulations (EAR), the data shall contain the “EAR Notice” as follows:

Export Administration Regulations (EAR) Notice This document contains information within the purview of the Export Administration Regulations (EAR), 15 CFR 730-774, and is export controlled. It may not be transferred to foreign nationals in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exception is obtained/available from the Bureau of Industry and Security, United States Department of Commerce. Violations of these regulations are punishable by fine, imprisonment, or both.

Transmittal

1. Data shall be transmitted to NASA via the Integrated Collaborative Environment (ICE)/Windchill, hardcopy, or other mechanism agreed to by the Contracting Officer, COR, and Project representatives who are responsible to receive, index, and store the data deliverables.

Each data transmittal package shall include:

Transmittal memorandum that specifies the meta-data below for each data transmittal:

Contract number Data Requirements Description (DRD) number DRD data type (specified in Item 3 on the DRD) Submission date or milestone being satisfied Document number and revision Document title File names of all files being delivered; multiple files per document must be clearly related to the document Distribution (as defined by the Contracting Officer’s letter) Requested response date Printable electronic files or hardcopy data.

Document Identification Type 1 and 2 documents published by the Contractor and submitted in response to the data requirements of this DPD shall be identified within an organized identification numbering system prescribed to NASA by the Contractor and, if applicable, as approved by NASA. This number, change legend, date, and title constitute the minimum identification of the specific document and shall appear on the cover and title page. The contract number shall also appear on the cover and title page as separate markings. The originator and organization shall be included on the title page. The document number, change legend, and date shall appear on each page of the document. In the front matter of each document, identify the DPD number and applicable DRD number(s) required for document preparation. Successive issues or revisions of documents shall be identified in the same manner as the basic issue and shall have appropriate change identification. Drawings and ECPs are excluded from the marking provisions of this paragraph. All Type 1 documentation, excluding configuration management requirements, will be marked “PRELIMINARY PENDING NASA APPROVAL,” and once approved shall be reissued with “APPROVED BY NASA” and the date and approval authority annotated on the cover.

Reference to Other Documents and Data Deliverables in Data Submittals All referenced documents shall be made readily available to the cognizant NASA organization upon request. The Contractor should make sure that the references are available to NASA in a manner which does not incur delays in the use of the response document. Reference may be made, within one data submittal, to other data submittals delivered in response to this DPD in those cases where the data required by one DRD may have been delivered by the Contractor in response to another DRD. The reference to previously-submitted data shall include the applicable DRD number, data submittal version date, and location within the referenced document.

Maintenance of Type 1 Document Submittals

1. Revisions of Type 1 documentation may be accomplished either by individual page revision or by a complete reissue of the document, with the exception of drawings (which shall be revised in accordance with contract configuration management requirements).

1. Individual page revisions shall be made as deemed necessary by the Contractor or as directed by the Contracting Officer.

1. A Type 1 document shall be completely reissued when, in the opinion of the Contractor and/or NASA, the document has been revised to the extent that it is unusable in its present state, or when directed by the Contracting Officer. When complete reissues are made, the entire contents of the document shall be brought up to date and shall incorporate revised pages. All revisions shall be recorded. A revision log shall identify complete reissues except for periodic reports and documents which are complete within themselves as final.

1. Changes of a minor nature to correct obvious typing errors, misspelled words, etc., shall only be made when a technical change is made, unless the accuracy of the document is affected.

1. All revised pages shall be identified by a revision symbol and a new date. Each document shall contain a log of revised pages that will identify the revision status of each page with the revision symbol. This list shall follow the table of contents in each document. The line or lines revised on a given page shall be designated by the use of vertical line in the margin of the page, and the change authority shall be indicated adjacent to the change.

1. Contractor Type 1 documents shall not be submitted containing pen and ink markups which correct, add to, or change the text, unless schedule problems exist and approval is obtained in writing from the Contracting Officer. Such markups, however, shall not exceed 20 percent of the page content and shall be acceptable provided that the reproduced copies are legible. In addition, hand-drawn schematics, block diagrams, data curves, and similar charts may be used in original reports in lieu of formally prepared art work, as long as legibility of copies is not impaired. Acceptability will be determined by the Contracting Officer.

DPD Maintenance Procedures NASA Initiated Change New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion of the DPD shall be appended. The Contractor shall notify the Contracting Officer in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision to DPD is appended. In such cases, the Contractor shall submit the requested changes to NASA for approval. See paragraph 3.3 for change procedures.

Contractor-Initiated Change Contractor-proposed data requirements or proposed changes to existing requirements shall be submitted to NASA for approval.

DPD Change Procedures

1. Changes to a contractual issue of this DPD shall be identified by NASA on the Document Change Log.

1. The date of the DPD shall be entered under the “as of” block of the Document Change Log. The date that was in the “as of” block shall be entered in the “Superseding” block.

1. The Document Change Log entitled “Incorporated Revisions” shall be changed to indicate the modification number, portions affected, and remarks. All changes to the DPD/DRDs shall be identified in the “Remarks” column.

1. The Document Change Log entitled “Outstanding Revisions” is changed periodically to indicate outstanding Change Orders and Contracting Officer notification letters.

DPD Reissues

1. When conditions warrant, the DPD shall be re-issued by NASA for each contract modification that affects the DPD and shall supersede the existing DPD in its entirety. Re-issues shall be issued by contractual direction.

1. All revision dates shall remain in the Date Revised block on all DRDs. The issue symbol, which shall commence with “A” and progress through “Z,” shall be entered in the DPD identification block of each DRD page of the DPD.

DATA REQUIREMENTS LIST

DRD

no.

Data Requirement Title

B = Baseline U = Update F = Final M = Monthly Q = Quarterly A = Annually Notes

2.1

Draft after selection, but prior to award Final 60 days after ATP

533M: Monthly 533Q: Quarterly

Formats 1, 3-6: Monthly Format 7: Annually Preliminary IMS with Proposal Full IPMR starting after second accounting period.

Monthly

2.3 B

F

Update at DCR

Risk reports: Quarterly

All reviews. See DRD for details.

Initial 5 days after event;

Final 30 days after event

Update compliance data deliveries as agreed upon by SPIE Verification Working Group and Verification Compliance Summary.

Preliminary at each Acceptance Review;

Final with delivery of each CI

Preliminary 30 days prior to TRR; Final with TRR data package

F

Release 30 days after test.

Deliver 5 days after identifying need for deviation or waiver

F

F

Monthly

F

As data is generated

As needed

Baseline CDR+6 months

Upon receipt or identification of ALERT issue

Baseline Ground Hazard Analysis 30 prior to first use

FMEA

U

FMEA

P

CIL

B

FMEA

B

CIL

After Baseline, update as required

-90d;

B

Update as required

Update as needed to support SLS Block 1B DAC cycle.

Update with ADP

CDR + 6mo. - 75% OMRS Tool

DATA REQUIREMENTS DESCRIPTION (DRD) USA-001

To provide an overall description of the processes and methods planned for accomplishing the Contract Statement of Work and for overall coordination of contract management activities. The PMP also describes the structure and environment within which the contract and subcontract management operates.

Parent SOW Paragraph(s): 1.1.1 Referenced from SOW Paragraph(s): 2.1

The Project Management Plan provides the basic planning document which describes the Contractor’s overall plan for performing the contracted scope of work.

The Project Management Plan shall provide a description of the Contractor’s management concepts, practices, approaches, plans, and schedules necessary for accomplishing (managing and controlling) the tasks described in the Statement of Work. The PMP shall present those management systems to be utilized to define and delegate task assignments and shall define the roles and organizational relationships of the Contractor, Subcontractors, and Government. The PMP shall cover all aspects of contract and subcontract management for the contract. The PMP shall provide information giving the Government insight into staffing, organizational structure, approaches and processes used to manage activities across the contract.

1. Descriptions of the management approaches used to accomplish and monitor contractual tasks.

1. Description of roles and responsibilities of the contract’s key personnel

1. Contractor Systems Engineering Management Plan (SEMP), processes, and tools to implement the technical effort and document the overall technical approach, maintain integrity between NASA requirements to the Contractor verification plans, and to transition the products through the lifecycle; including, at a minimum:

Describe the overall lifecycle Describe the Contractor’s system engineering process, including flowdown to subcontracts.

Describe the trade study methodology.

Describe the scope, approach, methods, and procedures of the system used to implement the management of requirements and verification tracking.

Describe how requirements are validated, and updated requirements reviewed and approved by the Project Office.

Describe the evaluation and decision-making process to be used by the Contractor when resolving technical questions.

Provide implementation planning to include a description of how the Contractor will manage the training required for end-users.

Provide implementation planning for encapsulation and stacking at KSC.

Describe the process for analyzing and defining USA requirements as part of their functional derivation, definition, and allocation of Contractor CEI spec requirements.

Management approach to routinely review and address cost, schedule, technical progress, concerns, and issues.

Description of performance reporting to NASA in preparation for major milestone reviews.

Communication Plan, including but not limited to a description of the overall interaction policy and approach, key interaction milestones, flexibility and adaptability of interactions, the process for continuous improvement and incorporations of lessons learned, and determination and implementation of cause and corrective actions.

Approach to interfaces with the Government, other Contractors, and/or other entities that are necessary and pertinent to the accomplishment of contractual tasks, including such things as data, analyses, equipment, software deliverables, schedules, interfaces, and other technical/managerial interactions.

Approach to the establishment and management of subcontracts.

Description of facility usage in support of the contract.

Performance Assessment Plan including, at a minimum:

Definition of performance assessment metrics that will be used to communicate to NASA the progress of the Contractor’s efforts against the project baseline plan.

Description of management systems and processes used to implement the plan including the developing, timely gathering, compiling, maintaining, auditing, analyzing, reporting, and providing management review of performance metrics.

Description of the Technical Performance Parameters (TPPs) selected for monitoring during the design and development.

Financial baseline plan, which includes cost-sharing approach and project reserves, and financial performance reporting plan.

Schedule performance reporting plans which includes schedule reserves.

DATA REQUIREMENTS DESCRIPTION (DRD) USA-002

To establish a product-oriented framework for reporting program cost, schedule, and technical performance. To provide a basis for uniform planning, reporting status, program visibility, and assignment of responsibilities.

Parent SOW Paragraph(s): 1.1.1

The CWBS establishes a product-oriented logical subdivision of hardware, software, services, facilities, etc., that make up the total project scope of work. The CWBS Dictionary provides a narrative description of the tasks and effort to be performed in each CWBS element.

1. CWBS—A logical, hierarchical display of the subdivision of all project work to be completed. The WBS shall include the approved element title and element number.

CWBS Dictionary—The CWBS dictionary shall describe and document the work content of every CWBS element and relevant efforts associated with each element (e.g., design, development, manufacturing). The CWBS dictionary shall be arranged in the same order as the contract CWBS. The CWBS dictionary shall include the following for each CWBS element:

CWBS element title.

CWBS element code.

CWBS element content description (including quantities, relevant associated work, and contract end items where applicable).

CWBS Index.

SOW paragraph number.

Specification (number and title) associated with the CWBS element (if applicable).

Contract line item associated with the CWBS element.

Date, revision number, revision authorization and approved changes.

Contract Identification Number.

Budget and reporting number (i.e., Charge Code).

DATA REQUIREMENTS DESCRIPTION (DRD) USA-003

To provide a description of the Contractor’s and major subcontractor’s methods, policies, and procedures utilized in complying with the requirements of NASA Federal Acquisition Regulation Supplement NFS 1852.234-1, Notice of Earned Value Management System, NFS 1852.234-2, Earned Value Management System, and the guidelines in American National Standards Institute/Electronic Industries Alliance Standard (ANSI/EIA-748), Earned Value Management Systems.

Parent SOW Paragraph(s): 1.1.2

The Earned Value Management System Description shall provide a description of the system and the Contractor's comprehensive plan for complying with the requirements in NFS 1852.234-1, NFS 1852.234-2, and ANSI/EIA-748.

12.2 APPLICABLE DOCUMENTS:

NFS 1852.234-1, Notice of Earned Value Management System NFS 1852.234-2, Earned Value Management System ANSI/EIA-748, Earned Value Management Systems

DATA REQUIREMENTS DESCRIPTION (DRD) USA-004

7. DESCRIPTION/USE:

Parent SOW Paragraph(s): 1.1.2 DRD USA-002, Contract WBS and WBS Dictionary, DRD USA-003, Earned Value Management Description, DRD USA-005, Integrated Project Management Report; and contract provisions. NPR 9501.2E, NASA Contractor Financial Management Reporting. GRC 52.242-96, NASA Contractor Financial Reporting – Supplemental Requirements (NOV 2012)

The Financial Management Report (533M and 533Q) provides data on accumulated costs and funding projections for management of the contract.

1. 533Q Quarterly Report shall include actual cost and cost projections at the total contract level. The initial 533Q report shall reflect the original contract value detailed by negotiated reporting categories and serve as the original baseline plan.

1. 533M Monthly Report shall include actual cost and cost projections at the total contract level.

A summary level page reflecting cumulative total contract cost since inception shall be included. Reconciliation between the 533M/533Q and the Integrated Project Management Report (DRD USA-005) shall be submitted as an attachment to the 533M/533Q Report.

DATA REQUIREMENTS DESCRIPTION (DRD) USA-005

The IPMR is the primary means of communicating project cost and schedule information between the prime Contractor and the Government. It consists of seven formats that provide project managers information to: (1) integrate cost and schedule performance data with technical performance measures, (2) identify the magnitude and impact of actual and potential problem areas causing significant cost and schedule variances, (3) forecast schedule completions, and (4) provide valid, timely project status information to higher management.

1. Format 1 defines cost and schedule performance data by product oriented Work Breakdown Structure.

1. Format 3 defines changes to the Performance Measurement Baseline (PMB).

1. Format 4 defines staffing forecasts.

1. Format 5 is a narrative report used to provide the required analysis of data contained in Formats 1-4 and 6.

1. Format 6 defines and contains the Contractor’s Integrated Master Schedule (IMS).

1. Format 7 defines the time-phased historical & forecast cost submission.

To ensure an integrated approach to risk management, the information within the data provided by this IPMR DRD shall be integrated with the following DRDs: USA-002, Contract WBS and WBS Dictionary, USA-001, Project Management Plan, USA-009, Risk Management Plan and Risk Management Reports, and USA-004, Financial Management Report (533M and 533Q). The Financial Management Reports shall include reconciliation between the Monthly Contractor Financial Management Report/Quarterly Contractor Financial Management Report (533M/533Q) and the IPMR, which shall be submitted as an attachment to the 533M/533Q reports and also included in Format 5 of the IPMR.

Parent SOW Paragraph(s): 1.1.2

The IPMR is the primary means of communicating cost and schedule performance and project health information between the Contractor and NASA.

12.2 APPLICABLE DOCUMENTS:

Data Item Description, Integrated Program Management Report, DI-MGMT-81861, available at the following web site: www.acq.osd.mil/evm.

12.3 CONTENTS:

All IPMR Formats 1, 3, 4, 5, 6, and 7 are required. The IPMR shall include all data pertaining to all authorized contract work, including both priced and unpriced effort that has been authorized at a not-to-exceed amount in accordance with the Contracting Officer's direction. The Contractor shall provide monthly IPMRs per DI-MGMT-81861 except as modified in this section.

FORMAT 1 INSTRUCTIONS: Provide reporting at level 3 for Project Management, Systems Engineering, Safety and Mission Assurance, Instrumentation and Electrical, and Operations and Ground Support. Provide reporting at level 4 for Structural Systems, Payload Environmental Control, Mechanical Systems, and Assembly, Integration and Testing. Include G&A and COM. .

FORMAT 3 INSTRUCTIONS: Significant differences (absolute values exceeding ±5%) between the PMB at the beginning and end of each specified period shall be explained in Format 5. Use quarterly periods for Block 6, columns (10) through (11), yearly periods for columns (12) through (13), and the remainder of the contract for column (14).

FORMAT 4 INSTRUCTIONS: Significant changes that require explanations in Format 5 are those that change the absolute value of the projected total staff-months at completion of any organizational or functional category by more than ±5%. Use quarterly periods for Block 5, columns (10) through (11), yearly periods for columns (12) through (13), and the remainder of the contract for column (14).

FORMAT 5 INSTRUCTIONS: The reporting level identified above is the level where variance reporting thresholds are applied. Variance analysis shall be required for:

1. Three largest current cost variances exceeding ± $50K or ± 5%

1. Three largest current schedule variances exceeding ± $50K or ± 5%

1. Three largest cumulative cost variances exceeding ± $100K and ± 10%

1. Three largest cumulative schedule variances exceeding ± $100K and ± 10%

1. Three largest variances at completion exceeding ± $250K and other cost and schedule variances or technical performance issues that are causing or are likely to cause significant schedule delays or cost overruns.

The required narrative explanations and variance thresholds will be reviewed periodically, and may be adjusted by contract modification with no change in contract price. All reportable WBS variance narratives shall adequately address the root cause of the variance; adequately discuss any schedule variance in terms of float and impact to the project critical path, if any, and quantitatively explain the causes that account for at least 70% of the variance exceeding the threshold. If there are no changes to the reportable element problem analysis, expected impacts, or corrective action status, then specify “no changes since the last reported analysis” and reference the IPMR date when the narrative was initially reported.

Schedule Analysis (See Format 6 Instructions below). Include the results of the Schedule Risk Assessment (SRA) when performed. Critical and driving path analysis should also include identification and analysis of the primary critical path and all near (secondary) critical paths whose total slack (float) values are within 10 working days or less of the primary critical path. The analysis shall be submitted in a waterfall format and organized in a manner such that the path with the least amount of slack is delineated first and followed by each successive path according to total slack values. When driving path analysis is desired, the specified project milestones and/or major project events are to be identified for Contractor reporting. NOTE: If driving paths are identified through the use of assigned task constraints (limited or fixed start/finish dates) within the IMS, then it should be removed from the IMS after identification/explanation of driving path is complete. Constraints that are left within the IMS unnecessarily will hinder or prevent accurate project critical path identification and analysis. Provide the results of the monthly schedule health analysis as discussed in Format 6 instructions.

Reconciliation between the Financial Management Report (533M/533Q)and the IPMR (Formats 1, 3, and4) shall be included.

In some cases, additional variance analysis is required to cover emerging trends. In this case, the supplier will be required to report additional variances for a time period of 6 months or less.

FORMAT 6 INSTRUCTIONS: The IMS shall include all discrete work at a minimum. Subcontractors with EVMS flowdown shall be included with sufficient detail to develop a realistic critical path. The prime and subcontractor (if any) data shall be consistent, statused monthly, and based on the same cutoff date to enable a realistic critical path.

Summary Master Schedule: The schedule shall include a top level Gantt chart summary arranged by WBS and that reflects all contract and controlled milestones, major program/project phases (i.e. design, fabrication, integration, assembly, test, etc.) and all end-item deliveries. It shall reflect, either by manual creation or by automated summarization, a vertically integrated rollup of intermediate and detailed schedule data.

Detailed Schedules: The detailed schedules shall contain vertical and horizontal integration at the task/milestone level of detail (vice the work package/planning package level) to provide better definition in task sequence and greater accuracy in critical identification.

IMS Fields: Additional IMS fields required in the schedule are WBS, Level of Effort identification, responsible organization, and planning package identification. A field identifying critical path is not required.

Relationships/Dependencies: All discrete tasks/milestones except for the start and end of the contract or for interim receipt and delivery events to/from external entities shall have at least one predecessor and successor.

Level of Effort (LOE) in the Schedule: If LOE tasks are excluded from the schedule, the Contractor must clearly document in an appropriate location how the cost and schedule for LOE effort is being planned and performance is being measured.

Schedule Margin: If schedule margin is included in the IMS, it must be as a defined task and clearly labeled as “Schedule Margin” or contingency. The number of schedule margin tasks should be minimal with most of the margin duration placed as the last task before the ending contract event or the end item delivery. Other acceptable locations for placing smaller amounts of schedule margin are prior to high level project milestones, such as PDR, CDR, System I&T Complete, etc.

In addition to the native IMS file, the Contractor will provide the IMS discussion and analysis as required in Format 5 (Section 3.6.7 of the IPMR DID) to include the results of the Contractor’s internal health analysis. This analysis shall include counts for the following schedule assessment indicators: 1) the total number of tasks, milestones and non-detail (e.g., summary, hammock, rollup, etc.) activities contained in the schedule, 2) the number of completed tasks and milestones, 3) the number of tasks and milestones to be completed, 4) the number of tasks and milestones that have no predecessor and/or no successor relationships, 5) the total number of tasks and milestones that have a total float (slack) value greater than 25% of the remaining duration of the total program/project schedule, 6) the total number of non-detail (e.g., summary, hammock, rollup, etc.) activities that have assigned predecessor or successor logical relationships, 7) the total number of tasks and milestones that have constraint (forced or fixed) dates.

FORMAT 7 INSTRUCTIONS: Format 7 is required at the same level at Format 1 reporting.

SUBCONTRACTOR REPORTS: All subcontractor IPMR formats must be included with the primes’ IPMR or reported directly to NASA.

DATA REQUIREMENTS DESCRIPTION (DRD) USA-006

To establish activity reporting for the Contractor’s progress and accomplishments. The Management Review packages support the monthly and quarterly management reviews of costs, schedule, and technical performance. The format provides a standardized approach for review materials.

DRD USA-001, Project Management Plan

Contract Status Reports and Management Review data packages document the integrated management reviews of the cost, schedule, and technical performance on the contract. There are two types of reviews: monthly and quarterly. These packages must be reconcilable with Financial Management Report 533 reporting and the Integrated Project Management Report.

NOTE: See DRD USA-001, Project Management Plan Performance Assessment Plan requirements, including metrics.

The Contract Status Reports shall consist of the following, at a…