CMC3_Attachment J8-DRL_DRD.pdf

Cargo Mission Contract

Data Requirements List (DRL) and Data Requirements Descriptions (DRDs)

Attachment J-8

This page intentionally left blank.

Subject to the Rights in Data clause, these DRDs set forth the data requirements for each deliverable for this contract. The contractor shall furnish data defined by the DRDs by category of data. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within each DRD. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) regulation or clause, the regulation will take precedence over the DRD per FAR 52.215-8, Order of Precedence – Uniform Contract Format.

NASA-Owned/Contractor-Held records shall be managed by the Contractor in accordance with Title 36 of the code of Federal Regulations, Chapter XII B, Records Management, and NPD 1440.6, NASA Records Management Program. The records shall be organized in accordance with the instructions in NPR 1441.1, NASA Records Retention Schedules, as applicable. The contractor shall disposition records and non-records in accordance with NPR 1441.1. All questions on records management issues shall be directed through the Contracting Officer to the ISS Technical Records Liaison Officer.

Documents included as applicable documents in DRDs are the issue specified in the Applicable Document List (ADL) (Contract Attachment J-7) and form a part of the DRD to the extent specified herein. References to documents other than applicable documents in the data requirements of DRDs may sometimes be utilized. 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.

Documentation submitted pursuant to this clause may incorporate references to other current approved documentation, provided the references are adequate and include such identification elements as title, document number, and approval date (where applicable). However, if the pertinent information is of relatively minor size, the contractor shall incorporate the information itself, in lieu of using a reference.

The contractor shall assure that any referenced information is readily available to appropriate users of the submitted document.

DATA TYPES

For the purpose of the DRDs, the following information/documentation types are applicable:

Type 1: That information and documentation which requires NASA approval prior to release.

Approved Type 1 information and documentation shall be controlled, and deviations from or changes to the concepts, techniques, and/or requirements stated therein shall require NASA approval prior to implementation. All work under this contract covered by approved Type 1 documents shall be performed in accordance with those approved documents. The Contracting Officers Representative will have approval authority and will sign the data prior to its release. Contractually binding documents will not be implemented nor revised without contractual authorization.

Type 2: That information and documentation for which NASA reserves a time-limited right to disapprove, in whole or in part. Type 2 data shall be submitted to JSC for review not less than 30 calendar days prior to its release for use or implementation. The contractor shall clearly identify the release target date in the "submitted for review" transmittal. If the contractor has not received any comment prior to the released target date, the document may be released for appropriate use. Any NASA comment received shall be appropriately dispositioned before the document is to be used. Type 2 data may be approved by NASA prior to its submittal.

Type 3: That information and documentation which is provided to NASA for surveillance, information, review, and/or management control. This information does not require formal NASA review and approval. Information in this category includes design solutions, status, cost/schedule reporting; analyses and test results, handbooks; and other designated lists, reports, etc.

NUMBER OF COPIES AND DISTRIBUTION REQUIREMENTS

The contractor shall provide copies of each DR to the standard distribution list stated in the DRD.

Additional distribution shall be made as directed, in writing, by the Contracting Officer. The number of copies required shall not exceed the limits set forth in NFS 1852.208-81, Restrictions on Printing and Duplicating, without prior Contracting Officer approval. Data Transmittal Forms shall be used to confirm delivery of electronically resident DRD deliverables.

ELECTRONIC FORMAT

DRDs shall be maintained electronically in the contractor's own format, unless a specified format is defined in the DRD.

DATA REQUIREMENTS DESCRIPTION

(Based on JSC-STD-123)

1a. DRD Title:

Engineering Drawings and Associated Lists

1b. Data Type: 3

2. Date of Current Version

April 1, 2018

3a. DRD No.

CMC-EN-01

3b. RFP/Contract No.

TBD

4. Use:

Provide the design data used to manufacture, install, verify, operate, and maintain the products of this contract.

5. DRD Category

Technical

6. References

a. SOW 3.2.3, 5.4

7. Interrelationships None

CMC-EN-02

8. PREPARATION INFORMATION: The contractor shall prepare the data delivery as follows:

8A. SCOPE: This DR establishes the content, format, control, delivery requirements and post-delivery maintenance of drawings, schematics, and associated lists prepared by the contractors and/or obtained from subcontractors/vendors for products of this contract. Subcontractor/vendor drawings, describing items classified as minor procurements or limited development items, which were not developed on CAD systems, are exempt from the electronic transmission and database requirements herein.

8B. CONTENT: All released manufacturing, assembly, installation and layout drawings of all hardware developed and/or sustained under this contract, including all components, subassemblies, and assemblies, to include:

• Manufacturing drawings

• Assembly drawings

• Installation drawings

• Layouts

• Schematics

Drawings shall meet the applicable requirements of the following:

• ASME Y14.34, Drawings, Engineering and Associated Lists

• ASME Y14.35, Engineering Drawings and Associated Documents

• ASME Y14.100, Engineering Drawing Practices

• IEEE/ASTM SI 10-2010, American National Standard for Use of the International System of

Units (SI): The Modern Metric System

• SSP 30695, Acceptance Data Package Requirements Specification

8C. FORMAT: Data shall be stored, managed and controlled in electronic format in the VMDB. Note: The

Boeing Vehicle Sustaining Engineering Contract Vehicle Data Integration (VDI) Team has the responsibility for loading, integrating, maintaining and giving users access to data in the VMDB (Reference D684-10090-01, VMDB Data Integration Plan)..

9. OPR: ISS Vehicle Office (Mail Code OB)

10. FIRST SUBMISSION DATE: See “Frequency of Submission”

Frequency Of Submission: (Note: all drawing releases to the VMDB will be made via the Sustaining Engineering Contract) :

• Drawings shall be available for major design reviews with electronic data delivery to the Vehicle Master Data Base (VMDB).

• Drawing delivery shall be provided for each applicable Acceptance Data Packages (ADPs) or ADP updates.

CAGE Codes for drawings on the CMC will not be updated until the drawings are required to be updated for technical reasons.

Government provided drawings housed in the Engineering Drawing Control Center (EDCC) shall be transferred to the VMDB when drawing updates are required.

Additional Submissions: As required to maintain drawings current with As-Built configuration.

11. MAINTENANCE: The document shall be maintained electronically.

Changes and/or updating of drawings and list shall be accomplished in accordance with the Contractor's engineering system and the provisions of the cited applicable documents.

12. COPIES/DISTRIBUTION: 1 e-copy to Program Repository (VMDB) Program

Authorized Repository Upload Notification: ISS Data Management

13. REMARKS: None

Engineering Drawings and Associated Lists for Orion

CMC-EN-01-O

Provide the design data used to manufacture, install, verify, operate, and maintain the products of this contract.

a. SOW 3.2.3, 5.4

7. Interrelationships N/A

8A. SCOPE: This DR establishes the content, format, control, delivery requirements and post-delivery maintenance of drawings, schematics, and associated lists prepared by the contractors and/or obtained from subcontractors/vendors for products of this contract. Subcontractor/vendor drawings, describing items classified as minor procurements or limited development items, which were not developed on CAD systems, are exempt from the electronic transmission and database requirements herein.

8B. CONTENT: All released manufacturing, assembly, installation and layout drawings of all hardware developed and/or sustained under this contract, including all components, subassemblies, and assemblies, to include:

• Manufacturing drawings

• Assembly drawings

• Installation drawings

• Layouts

• Schematics

Drawings shall meet the applicable requirements of the following:

• ASME Y14.34, Drawings, Engineering and Associated Lists

• ASME Y14.35, Engineering Drawings and Associated Documents

• ASME Y14.100, Engineering Drawing Practices

• IEEE/ASTM SI 10-2010, American National Standard for Use of the International System of

Units (SI): The Modern Metric System

• SSP 30695, Acceptance Data Package Requirements Specification

8C. FORMAT: Data shall be stored, managed and controlled in electronic format.

9. OPR: Orion Crew and Service Module Office

10. FIRST SUBMISSION DATE: See “Frequency of Submission”

Frequency Of Submission:

• Drawings shall be available for major design reviews with electronic data delivery to the Engineering Drawing Control Center (EDCC).

• Drawing delivery shall be provided for each applicable Acceptance Data Packages (ADPs) or ADP updates.

CAGE Codes for drawings on the CMC will not be updated until the drawings are required to be updated for technical reasons.

Additional Submissions: As required to maintain drawings current with As-Built

Changes and/or updating of drawings and list shall be accomplished in accordance with the Contractor's engineering system and the provisions of the cited applicable documents.

12. COPIES/DISTRIBUTION: 1 e-copy to Program Repository

Program Authorized Repository Upload Notification: Orion Data Management

ISS Vehicle Engineering Data

CMC-EN-02

4. Use To describe the overall data requirements to be delivered to the Vehicle Master Database (VMDB).

SOW 3.2.3, 5.4

7. Interrelationships DRD CMC-EN-01 and

DRD CMC-SA-05

8. PREPARATION INFORMATION: The contractor shall prepare the data delivery as follows:

8A. SCOPE: This DRD encompasses the capture, sustaining, and configuration management of vehicle engineering data that will reside in the Vehicle Master Database (VMDB) (a Government Furnished Database). This DR is not intended to generate any data not required in the Statement of Work or other DRDs.

8B. CONTENT:

Engineering data for hardware developed and sustained under this contract shall include:

• Resource Data o Mass Properties (weight and center of gravity) o Power and Thermal

• Performance and Characteristics Data o Constraints and Operational Limits, Design Limits, Hardware Characteristics for the operating envelope

• Electromagnetic and Environment Interference

• Parts Selection and Control o Electrical, Electronic, and Electro-mechanic o Component Electrical Power and Thermal Consumption during steady-state, standby, startup, and peak operations 8C. FORMAT: Data shall be stored, managed and controlled in VMDB electronic format.

9. OPR: ISS Vehicle Office (Mail Code OB)

10. FIRST SUBMISSION DATE: Data set and inventory updates - Provide data for new/modified hardware prior to Government acceptance; for sustained hardware, provide data as updated.

Frequency Of Submission: As required to maintain data current.

Additional Submissions: See Frequency of Submission.

11. MAINTENANCE: The DR shall be maintained electronically.

12. COPIES/DISTRIBUTION: 1 e-copy to Program Repository (VMDB or equivalent)

Program Authorized Repository Upload Notification: ISS Data Management Program Authorized Repository Upload Notification: Contracting Officer Program Authorized Repository Upload Notification: Contracting Officer Representative

Cargo Integration Cargo CAD Models for Launch, Return and On-Orbit Configurations

CMC-EN-03

3b. RFP/Contract No.

The CAD models will be used to ensure the integrated assemblies are compatible with ISS visiting vehicles. The CAD models are used to assess clearances for both launch, return and on-orbit operations. The CAD models are also used for ISS vehicle integrated performance, Mission analysis and ISS System analysis.

5. DRD Category

6. References SOW 3.2.4, 5.5 7. Interrelationships : N/A

8A. SCOPE: Develop, deliver, and maintain CAD models for the hardware developed or sustained within the scope of the contract SOW. Models of the hardware shall be delivered to the ISS Vehicle Sustaining Contractor. Best Available, As-Designed (validated) models for planned construction and As-Built (final) models are required.

8B. CONTENT:

CAD models shall be 3-D CAD models of sufficient detail that the external and internal geometry shows an accurate depiction of the hardware. Two levels of fidelity shall be provided:

Exterior CAD Models A low fidelity model is required that shows all hardware external extrusions.

A high fidelity model that shows all hardware external extrusions is required which includes higher fidelity renderings of the following details (not limited to): docking aids, debris shields, cables, cable clamps, brackets, antennas, cameras, lights, targets, vents, handrails, EVA aids, sensors, thrusters, and element-to-element interface geometry. The models shall also include surface features that would prohibit the installation of any Space Visioning System (SVS) target and surface features that would obstruct a camera’s view of the SVS targets. Visible Orbital Replacement Units (ORUs) planned to be replaced on-orbit should be included in the model and partially visible ORUs that require a crewmember to replace should also be modeled as complete entities. Launch and on-orbit configurations are required if the “As-Launched” hardware model is different than the on-orbit model. A description of which files to use for each configuration shall be provided.

Interior CAD Models In general, CAD Models are required for all items that meet any of the following criteria;

however, specifics on when a CAD model is required should be worked with NASA:

• installed in a rack or on a rack front, on a mid-bay panel or in a standoff

• protrude into egress space;

• have power cords

High fidelity CAD models are typically required for hardware with one or more of the following features: internal pressure shell, standoffs, hatches, ports (e.g. O2 Ports, Fireports, etc.), stowage compartments, rack attachments, vents, lights, handrails, racks, seat track, and emergency equipment along with any associated keep out zones. All objects that deploy rotate or otherwise move shall be documented and modeled with location and limit parameters described.

Low fidelity CAD models are typically not required. However, if High fidelity CAD models do not exist for simple box-like structures that are very preliminary in design, a low fidelity CAD model is acceptable and should include dimensions. Attach features for additional details such as vents, lights, and handrails are not specifically required, although models shall be complete with datum information such that additional details can be placed as they become available.

8C. FORMAT:

Exterior CAD Models Models shall be full scale in English (inches) units. Models shall be constructed to nominal dimensions.

Models shall be built with respect to element local coordinate system as defined by SSP 30219, ISS Reference Coordinate Systems Document.

One of the following formats shall be provided: SLA, UG, Pro-E, JT, PT or VRML.

Translation: STEP AP203 neutral file format acceptable only if none of the above formats are available.

Solid Models Only—Models may be un-parameterized “dumb solids” meaning tolerance data, model history, material properties, etc. need not be included.

Model parts shall be individual entities and not fused together. This will allow the CAD team to update the model based on hardware measurements. Assembly structure, part names and part numbers are helpful. However, for controlling file size growth and having redundant geometry, all identical components (i.e., handrails, connectors, etc.) shall be nested in detail/ditto space/assemblies. For example if 20 identical handrails are used, only one detail is required and the rest should be in ditto space/assembly.

Description on movement limits for any articulating items shall be included in the model/drawing.

As-Designed and As-Built (validated and final) models shall be validated to released engineering drawings. Drawings should also be located in the VMDB.

Interior CAD Models Models shall be full scale in English (inches) units. Models shall be constructed to nominal dimensions.

Models shall be built with respect to element local coordinate system as defined by SSP 30219, ISS Reference Coordinate Systems.

Solid models only: Models shall be supplied in UG, Pro-E, SLA, VMRL, JT or PV formats Translation: STEP AP203 neutral file format acceptable only if none of the above formats are available.

Interior models shall be delivered either separate from exterior models, or as a documented assembly such that interior models can easily be separated leaving both interior and exterior features intact. If supplied as separate models, information to associate interior to exterior shall be provided.

Where interior subassemblies are supplied as separate models, sufficient documentation shall be provided to support correct geometrical integration of each subassembly into its larger interior element.

A model tree shall be provided which documents the element model assembly architecture as well as model and subassembly titles.

Supplied configuration data shall include: 1) Identification of the configuration baseline documented source including approved changes incorporated/not-incorporated, and 2) Configuration description data compared with previously delivered versions of the same models.

Model parts shall be individual entities and not fused together.

Models and associated assembly trees and configuration data shall be delivered electronically via File Transfer Protocol (FTP) site or as Compact Discs.

9. OPR: ISS Systems Engineering and Integration Office (Mail Code OM)

10. FIRST SUBMISSION DATE:

Frequency of Submission: External CAD Models

• High fidelity best available CAD model required at L-15 months, Design Review 1 or Preliminary Design Review (electronically accessible).

• High fidelity validated CAD model required at L-11.5 months, Design Review 2 or

Critical Design Review (electronically accessible).

• High fidelity best available payload CAD model “Express” CAD model required at

L-11 months. Integrated As-Designed payload CAD model required at L-10 months.

Note: Express Models: Express Models are not delivered with a Release Model Directory (RMD), not renamed with sub-element numbers, not broken up into <5MB pieces, not checked for accuracy or completeness, revised or maintained, not associated with any cargo or stage condition, and not located with respect to any element or the ISS coordinate system.

• High fidelity final CAD model required at L-9 months or with Acceptance Data Package submittal/update.

Frequency of Submission: Internal CAD models

• High fidelity (if required) best available CAD model required at L-12 months, Design Review 1 or Preliminary Design Review (electronically accessible).

• High fidelity (if required) final CAD model required at L-10 months or with

Acceptance Data Package submittal/update.

For COTS hardware, CAD models are required at increment start minus 10 months or when the procured item is delivered, for items procured after increment start minus 10 months. For COTS hardware which is modified for flight, CAD model is required for delivery with the design modification approval and with COTS (with modification) final delivery

Additional Submissions: As required to reflect changes or updates to the As-Built

11. MAINTENANCE: Changes and/or updating of models shall be accomplished in accordance with the Contractor’s engineering system and contract requirements for the As-Built configuration. Models shall be maintained electronically.

12. COPIES/DISTRIBUTION: 1 e-copy to Program Repository via EDMS workflow Program Authorized Repository Upload Notification: ISS Data Management Program Authorized Repository Upload Notification: Contracting Officer

Representative

Cargo Integration Cargo CAD Models for Launch, Return and On-Orbit Configurations for Orion

CMC-EN-03-O

The CAD models will be used to ensure the integrated assemblies are compatible with Orion. The CAD models are used to assess clearances for both launch, return and on-orbit operations. The CAD models are also used for Orion vehicle integrated performance, mission analysis and system analysis.

5. DRD Category

6. References SOW 3.2.4, 5.5 7. Interrelationships : N/A

8A. SCOPE: Develop, deliver, and maintain CAD models for the hardware developed or sustained within the scope of the contract SOW that are structurally mounted to internal or external Orion vehicle interfaces. Items temp-mounted to IVA interfaces (e.g., Multi-Use Bracket, Flexible Bracket Assembly, or IVA restraints and mobility aids like handrails, etc.), soft bag interfaces (velcro, friction fit, etc), or are hand-held are exempt from this requirement. Models of the hardware shall be delivered to the Orion Vehicle Sustaining Contractor. Best Available, As-Designed (validated) models for planned construction and As-Built (final) models are required. Note: The content described below uses ISS examples.

If Orion requires CAD models in the future, the examples are retained to help guide the models required for Orion unique implementation.

8B. CONTENT:

CAD models shall be 3-D CAD models of sufficient detail that the external and internal geometry shows an accurate depiction of the hardware. Two levels of fidelity shall be provided:

Exterior CAD Models A low fidelity model is required that shows all hardware external extrusions.

A high fidelity model that shows all hardware external extrusions is required which includes higher fidelity renderings of the following details (not limited to): docking aids, debris shields, cables, cable clamps, brackets, antennas, cameras, lights, targets, vents, handrails, EVA aids, sensors, thrusters, and element-to-element interface geometry. The models shall also include surface features that would prohibit the installation of any Space Visioning System (SVS) target and surface features that would obstruct a camera’s view of the SVS targets. Visible Orbital Replacement Units (ORUs) planned to be replaced on-orbit should be included in the model and partially visible ORUs that require a crewmember to replace should also be modeled as complete entities. Launch and on-orbit configurations are required if the “As-Launched” hardware model is different than the on-orbit model. A description of which files to use for each configuration shall be provided.

In general, CAD Models are required for all items that meet any of the following criteria;

however, specifics on when a CAD model is required should be worked with NASA:

• installed in a rack or on a rack front, on a mid-bay panel or in a standoff

• protrude into egress space;

• have power cords

High fidelity CAD models are typically required for hardware with one or more of the following features: internal pressure shell, standoffs, hatches, ports (e.g. O2 Ports, Fireports, etc.), stowage compartments, rack attachments, vents, lights, handrails, racks, seat track, and emergency equipment along with any associated keep out zones. All objects that deploy rotate or otherwise move shall be documented and modeled with location and limit parameters described.

Low fidelity CAD models are typically not required. However, if High fidelity CAD models do not exist for simple box-like structures that are very preliminary in design, a low fidelity CAD model is acceptable and should include dimensions. Attach features for additional details such as vents, lights, and handrails are not specifically required, although models shall be complete with datum information such that additional details can be placed as they become available.

8C. FORMAT:

Exterior CAD Models Models shall be full scale in English (inches) units. Models shall be constructed to nominal dimensions.

Models shall be built with respect to element local coordinate system as defined by SLS-Spec- 048 Cross Program Integrated Coordinate Systems.

One of the following formats shall be provided: SLA, UG, Pro-E, JT, PT or VRML.

Translation: STEP AP203 neutral file format acceptable only if none of the above formats are available.

Solid Models Only—Models may be un-parameterized “dumb solids” meaning tolerance data, model history, material properties, etc. need not be included.

Model parts shall be individual entities and not fused together. This will allow the CAD team to update the model based on hardware measurements. Assembly structure, part names and part numbers are helpful. However, for controlling file size growth and having redundant geometry, all identical components (i.e., handrails, connectors, etc.) shall be nested in detail/ditto space/assemblies. For example if 20 identical handrails are used, only one detail is required and the rest should be in ditto space/assembly.

Description on movement limits for any articulating items shall be included in the model/drawing.

As-Designed and As-Built (validated and final) models shall be validated to released engineering drawings.

Models shall be full scale in English (inches) units. Models shall be constructed to nominal dimensions.

Models shall be built with respect to element local coordinate system as defined by SLS-Spec-048 Cross Program Integrated Coordinate Systems.

Solid models only: Models shall be supplied in UG, Pro-E, SLA, VMRL, JT or PV formats Translation: STEP AP203 neutral file format acceptable only if none of the above formats are available.

Interior models shall be delivered either separate from exterior models, or as a documented assembly such that interior models can easily be separated leaving both interior and exterior features intact. If supplied as separate models, information to associate interior to exterior shall be provided.

Where interior subassemblies are supplied as separate models, sufficient documentation shall be provided to support correct geometrical integration of each subassembly into its larger interior element.

A model tree shall be provided which documents the element model assembly architecture as well as model and subassembly titles.

Supplied configuration data shall include: 1) Identification of the configuration baseline documented source including approved changes incorporated/not-incorporated, and 2) Configuration description data compared with previously delivered versions of the same models.

Model parts shall be individual entities and not fused together.

Models and associated assembly trees and configuration data shall be delivered electronically via File Transfer Protocol (FTP) site or as Compact Discs.

9. OPR: Orion Crew and Service Module Office

10. FIRST SUBMISSION DATE:

Frequency of Submission: External CAD Models

• High fidelity best available CAD model required at L-15 months, Design Review 1 or Preliminary Design Review (electronically accessible).

• High fidelity validated CAD model required at L-11.5 months, Design Review 2 or

Critical Design Review (electronically accessible).

• High fidelity best available payload CAD model “Express” CAD model required at

L-11 months. Integrated As-Designed payload CAD model required at L-10 months.

Note: Express Models: Express Models are not delivered with a Release Model Directory (RMD), not renamed with sub-element numbers, not broken up into <5MB pieces, not checked for accuracy or completeness, revised or maintained, not associated with any cargo or stage condition, and not located with respect to any element or the ISS coordinate system.

• High fidelity final CAD model required at L-9 months or with Acceptance Data Package submittal/update.

Frequency of Submission: Internal CAD models

• High fidelity (if required) best available CAD model required at L-12 months, Design Review 1 or Preliminary Design Review (electronically accessible).

• High fidelity (if required) final CAD model required at L-10 months or with

Acceptance Data Package submittal/update.

For COTS hardware, CAD models are required at increment start minus 10 months or when the procured item is delivered, for items procured after increment start minus 10 months. For COTS hardware which is modified for flight, CAD model is required for delivery with the design modification approval and with COTS (with modification) final delivery

Additional Submissions: As required to reflect changes or updates to the As-Built

11. MAINTENANCE: Changes and/or updating of models shall be accomplished in accordance with the Contractor’s engineering system and contract requirements for the As-Built configuration. Models shall be maintained electronically.

12. COPIES/DISTRIBUTION: 1 e-copy to Program Repository

Program Authorized Repository Upload Notification: Orion Data Management

New Hardware Interim Design Review Deliverables

CMC-EN-04

To support each new hardware design review process, the contractor shall deliver all products per expectation agreement.

5. DRD Category Technical

6. References SOW 5.3 7. Interrelationships : CMC-PM-02

8A. SCOPE: Describes scope of interim design reviews required to be held for Government review of new hardware being developed under the Cargo Mission Contract. Design reviews shall be held per SSP 50287, Hardware and Software Acceptance Process unless otherwise specified in the Statement of Work for the particular hardware project. The data required for all reviews required shall be delivered per this DRD.

8B. CONTENT: Data Requirements per SSP 50287 or SOW.

8C. FORMAT: Electronic, compatible with the Program authorized repository.

9. OPR: ISS Office sponsoring new hardware.

10. FIRST SUBMISSION DATE: Per baselined schedule for hardware project.

Frequency Of Submission: As required to meet requirements and baselined schedule.

Additional Submissions: As required for Delta Reviews.

11. MAINTENANCE: See “Additional Submissions”.

12. COPIES/DISTRIBUTION:

1 electronic copy: Program Authorized Repository Program Authorized Repository Upload Notification: ISS Data Management

New Hardware Interim Design Review Deliverables for Orion

CMC-EN-04-O

To support each new hardware design review process, the contractor shall deliver all products per expectation agreement.

5. DRD Category Technical

6. References SOW 5.3 7. Interrelationships : CMC-PM-02

8A. SCOPE: Describes scope of interim design reviews required to be held for Government review of new hardware being developed under the Cargo Mission Contract. Design reviews shall be held per SSP 50287, Hardware and Software Acceptance Process unless otherwise specified in the Statement of Work for the particular hardware project. The data required for all reviews required shall be delivered per this DRD. Note: CMC design processes are based on SSP 50287 which is acceptable to Orion GEMCB (Government Equipment and Materials Control Board).

8B. CONTENT: Data Requirements per SSP 50287 or SOW.

9. OPR: Orion Office sponsoring new hardware.

10. FIRST SUBMISSION DATE: Per baselined schedule for hardware project.

Frequency Of Submission: As required to meet requirements and baselined schedule.

Additional Submissions: As required for Delta Reviews.

11. MAINTENANCE: See “Additional Submissions”.

Export Control Plan (ECP)

1b. Data Type: 2

CMC-II-01

Document the contractor’s approach for export control.

5. DRD Category Administrative

6. References: SOW 1.8; Clauses H.4; NFS 1852.225-70 7. Interrelationships: N/A

8. PREPARATION INFORMATION: The contractor shall prepare the data delivery as follows:

8A. SCOPE: The plan shall describe all export control activities related to the performance of contract requirements. The plan shall include procedures for issuance of a quarterly report listing all exports affected for the subject contract on behalf of NASA by the contractor during the reporting quarter. The list is to include information describing the item exported, licenses (if acquired), exemptions, license information, transaction status, compliance activities, and records of process completion for license exceptions or exemptions classifications on those exports. Additionally, the plan shall describe the processes used to properly classify and mark data.

8B. CONTENT: The contractor shall prepare and submit an ECP describing the contractor’s planned approach for accomplishing contract functions while adhering to export laws, regulations and directives.

The ECP shall describe the Export Control Log, which shall contain information describing the item exported, licenses (if acquired), exemptions, license information, transaction status, compliance activities, and records of process completion for license exceptions or exemptions classifications on those exports.

8C. FORMAT: Electronic, compatible with the Program authorized repository.

9. OPR: ISS External Integration Office (Mail Code OX)

10. FIRST SUBMISSION DATE: Thirty (30) calendar days after phase-in start.

Frequency of Submission: Annually Additional Submissions: See “Frequency of Submission”

11. MAINTENANCE: The plan shall be reviewed annually to ensure accuracy. Any updates to the plan require a resubmission of the plan.

12. COPIES/DISTRIBUTION: 1 Electronic copy: Program Authorized Repository Program Authorized Repository Upload Notification: ISS Data Management Program Authorized Repository Upload Notification: Contracting Officer Program Authorized Repository Upload Notification: Contracting Officer Representative Program Authorized Repository Upload Notification: Center Export Administrator Program Authorized Repository Upload Notification: ISS Export Control Officer

1a. DRD Title:

Export Control Audit Results

1b. Data Type: 2

2. Date of Current Version

April 1, 2018

3a. DRD No.

CMC-II-02

3b. RFP/Contract No.

TBD

4. Use To provide insight into the Contractor’s Export Control processes

5. DRD

Category Administrative

6. References: SOW 1.8 ; Clause H.4; NFS 1852.225-70 7. Interrelationships: N/A

8. PREPARATION INFORMATION: The contractor shall prepare the data delivery as follows:

8A. SCOPE: Audits shall include a thorough examination of all export control processes (as outlined in the Contractor’s Export Control Plan) associated with this contract, areas for improvement (if any), and corrective action plans for identified areas of improvement.

Affected subcontractors are required to do their own self-audits and report the results of the audit to NASA through the Cargo Mission Contract prime contractor. Prior to audit completion, inclusion on the audit process through informal statuses to the JSC Export Services Team or Center Export Administrator is optional and might prove useful in the success of this effort.

8B. CONTENT:

• Document current audit processes, export control processes audited and audit findings,

• Based on audit findings, the contractor/subcontractor shall include corrective action plans for any processes identified for improvements and notification when the correction of any non-conformances has been completed.

8C. FORMAT: Electronic, compatible with the Program authorized repository

9. OPR: ISS External Integration Office (Mail Code OX)

10. FIRST SUBMISSION DATE: September 30, 2018 Frequency Of Submission: Annually, at the end of each fiscal year Additional Submissions: N/A

11. MAINTENANCE: The document shall be maintained electronically.

12. COPIES/DISTRIBUTION:

1 copy (electronic): Program Authorized Repository Program Authorized Repository Upload Notification: ISS Data Management Program Authorized Repository Upload Notification: ISS Lead Export Control Representative

DATA REQUIREMENTS

DESCRIPTION (Based on JSC-STD-123)

NASA Form (NF) F533 Monthly Cost Reporting

1b. Data Type: 3

2. Date of Current Version

May 31, 2017

3a. DRD No.

CMC-PC-01

3b. RFP/Contract No.

TBD

4. Use Provide summary level cost reporting to the International Space Station Program Office for the evaluation of the contractor’s actual cost and fee for the planning, monitoring, and controlling of project and program resources, and for accruing cost.

5. DRD

Category Administrative

6. References: SOW 1.3.1, 1.4.1, NPR 9501.2E 7. Interrelationships: CMC-PC-02, PM-02, PM-

NASA Form 533 (NF533) Reports The NASA Form 533 (NF533) reports provide data necessary for the following:

1. Projecting costs and hours to ensure that dollar and labor resources realistically support project and program schedules.

2. Evaluating contractors' actual cost and fee data in relation to negotiated contract value, estimated costs, and budget forecast data.

3. Planning, monitoring, and controlling project and program resources.

4. Accruing cost in NASA's accounting system, providing program and functional management information, and resulting in liabilities reflected on the financial statements.

Cost is a financial measurement of resources used in accomplishing a specified purpose, such as performing a service, carrying out an activity, acquiring an asset, or completing a unit of work or project. NASA Procedural Requirements (NPR) 9501.2E entitled “NASA Contractor Financial Management Reporting,” or its most current revision, identifies the cost reporting requirements for a contract. An NF533 format is provided in Appendix A.

NASA is required by law to maintain accrual accounting, which requires cost to be reported in the period in which benefits are received, without regard to time of payment.

The reports (NF533M [Monthly] and NF533Q [Quarterly]) are the official cost documents used at NASA for cost type, price determination, and Fixed Price Incentive contracts. The data contained in the reports must be auditable using Generally Accepted Accounting Principles (GAAP). Supplemental cost reports submitted in addition to the NF533 must be reconcilable to both the NF533M & NF533Q. The NF533Q has been waived for this contract.

Common NF533 Cost Elements

Balance of Contract (8c) Balance of contract for the remaining estimate to complete for each RC (column 8c on NF533)

Government Fiscal Year Estimate at Complete (EAC) (8d)

Actual cumulative cost and hours incurred plus remaining estimated cost and hours for the current Government Fiscal Year (column 8d on NF533)

Contractor Estimate (9a) Contractor estimate for the total estimate to complete entire scope of contract for each RC (column 9a on

NF533)

Contract Value (9b) Contract value based upon contract modifications for each RC (column 9b on NF533)

Unfilled orders outstanding (10) Unfilled orders outstanding at the end of the reporting period for each RC (column 10 on NF533)

Reporting Category level Used by NASA’s accounting system to determine the RC level

Reporting Category Identifier Identifies if the RC is an actual Reporting Category or a Sub- Reporting Category

A Reporting Category (RC) correlates to a task order, delivery order, or Work Breakdown Structure (WBS) and is the level at which cost is reported. Each RC can have Sub- Reporting Category line items (detailed cost elements) that add up to a RC. The Contractor is required to coordinate with the NASA Resource Analyst assigned to the contract in order to establish and maintain the Reporting Categories the contractor shall use to comply with this data requirement.

Column 7b (planned cost incurred/hours worked for the month) and 7d (cumulative planned cost incurred/hours worked) of the NF533M represent the negotiated baseline plan for the contract. There may not be a relationship between the estimates provided in columns 8 of the NF533M to columns 7b and 7d. Columns 7b and 7d represent the legally binding contract negotiated baseline plan plus all authorized changes.

Uncompensated overtime hours worked should be reported on NF533 reports as a separate line item or in the footnotes.

Short and long-term cost estimates, which include all data entered in columns 8 and 9a on the NF533M and NF533Q reports, shall be based on the most current and reliable information available.

Prior period cost adjustments shall be reported in column 7a and 7c of NF533M and column 7a of the NF533Q as soon as identified. In a footnote, the cost adjustment shall be delineated by government fiscal year, discuss the reasons for, the amounts of, and the time period for which the adjustment(s) relate.

Property, Plant & Equipment (PP&E) Reporting

An initial Baseline report is required (in the NF533Q format) to be used as a baseline for the life of the contract. The initial baseline report shall be submitted by the contractor within 30 calendar days after authorization to proceed has been granted. The initial report shall reflect the original contract value detailed by negotiated reporting categories and shall be the original contract baseline plan.

NF 533 M reporting shall begin no later than 10 days following the close of the contractor’s accounting period after initial incurrence of cost.

NF533 Final Submission Upon Contract Completion

Monthly NF533 reporting is no longer required once the contract is physically complete, provided the final cost report includes actual cost only (no estimates or forecasts). The contractor must continue to submit monthly NF533 reports as long as estimates for the following period are included. If the final cost of a contract changes after the submission of the "final" contractor cost report, the contractor must submit a revised NF533 report in the month the cost change is recognized.

Electronic NF533 Flat File Requirement (will only be submitted if requested during the course of the contract) If requested by NASA, the contractor shall submit a Flat File NF533M electronically by the same due date. The data shall be submitted via email using the Government prescribed flat file format (if requested, an example of the Agency Defined File Format layout details will be provided by NASA).

NF533 Report Distribution

• electronic copy: Program Authorized Repository

• Program Authorized Repository Upload Notification: ISS Data Management

• Program Authorized Repository Upload Notification: LF3 Cost Accounting

• Program Authorized Repository Upload Notification: Contracting Officer

• Program Authorized Repository Upload Notification: Contracting Officer Representative

• Program Authorized Repository Upload Notification: ISS Assessment Office

• Program Authorized Repository Upload Notification: ISS Resources Office Program Authorized Repository Upload Notification: Defense Contract Management Agency

A signed summary page in PDF format is to be included with the distribution. If an electronic copy is not signed, a signed hardcopy is required.

NF533 Supplemental Reporting

Supplemental reporting requirements will be submitted during the course of the contract in accordance with direction in Appendix B.

APPENDIX A. NF533 Format & Template

• The report shall be in three parts:

• CMC-PC-01A shall be an executive summary narrative with variance explanations for each WBS level.

• CMC-PC-01B shall be a top level summary listing by contract cost elements (see NPR 9501.2E) including Equivalent Persons and major subcontractors*. The top level summary shall also include a cost rollup at the WBS 1 level.

• CMC-PC-01C reporting levels shall be agreed to at the onset of the contract by

NASA and the contractor. NASA and the contractor will map costs according to the ISS and Orion Work Breakdown Structure (Reference SSP documents 50659-ISS WBS and 50839-ISS Program Operations Description (IPOD) and MPCV 72106 Orion MPCV WBS and Data Dictionary). For example, the ISS Program tracks costs to the second and third level WBS as appropriate.

• *Major Subcontractors are defined as follows:

• For core work (SOW Sections 1,2,3, and 4) – a company that performs 25% or more of the work scope or is 25% or more of the overall cost for the contract regardless of Contract Year spread.

• For discrete work projects (SOW 6 or DIL): Major subcontractor and vendors are those that exceed $1 Million dollars in annual cost to the prime contractor.

Monthly Contractor Financial Management Report NASA form 533M 2. Report for Month Ending:

Approved OMB # 2700-0003 Operating Days:

TO: FROM: 3.CONTRACT VALUE

NASA/Johnson Space a. Cost b. Fee:

Contract Administration $0 $0 Houston Texas 77058

a. TYPE b. CONTRACT NO. AND LATEST DEFINITIZED MODIFICATION NO. 4.Fund Limitation:

1. DESCRIPTION CPAF $0

OF c. SCOPE OF WORK d. AUTH. CONTR. REP. (Signature) DATE CONTRACT a. INVOICE AMTS. BILLED b. TOTAL PYTS. REC'D

$0 $0

7. COST INCURRED/HOURS WORKED 8. ESTIMATED COST/HOURS TO COMPLETE 9. ESTIMATED FINAL

COST/HOURS 10. UNFILLED

ORDERS

OUTSTANDING

6. REPORTING CATEGORY/ PRIOR CURRENT NEXT NEXT NEXT BALANCE GFY CONTRACTOR CONTRACT

COST ELEMENTS GFYs ACTUAL PLAN ACTUAL PLAN ACTUAL PLAN MONTH MONTH MONTH MONTH OF EAC ESTIMATE VALUE

ESTIMATE ESTIMATE ESTIMATE ESTIMATE CONTRACT

7a 7b 7c1 7d1 7c2 7d2 8a 8b 8c 8d 9a 9b

EP 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

DIRECT LABOR HOURS:

DIRECT LABOR HOURS - PRIME 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 DIRECT LAB HOURS - SUBCONTRACTORS 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 TOTAL DIRECT LABOR HOURS 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

DIRECT COST:

DIRECT LABOR COST - PRIME 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 DIRECT LAB COST - SUBCONTRACTORS 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

MINOR SUBCONTRACTORS 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

MATERIAL 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

ODC 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

TOTAL: DIRECT COST 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

INDIRECT COST:

FRINGE 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

OVERHEAD 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

PROCUREMENT BURDEN 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 G&A 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

TOTAL: INDIRECT COST 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

PHASE-IN 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

IDIQ TASK ORDERS

UNDISTRIBUTED BUDGET

MANAGEMENT RESERVE

TOTAL: TOTAL COST 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

FEE EARNED 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

PROVISIONAL FEE 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

POTENTIAL ADD. FEE 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

TOTAL FEE 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

TOTAL: COST PLUS FEE 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

5. BILLING

DURING MONTH GFY CUM TO DATE INCEPTION TO DATE

http://nodis3.gsfc.nasa.gov/npg img/N PR 9501 002E /NF533M.pdf http://nodis3.gsfc.nasa.gov/npg img/N PR 9501 002E /NF533Q.pdf

Administrative

8A. SCOPE: Contains the contractual Work Breakdown Structure (WBS) and WBS

Dictionary.

8B. CONTENT: Contains the contractual WBS and its Dictionary as follows:

The WBS and Dictionary shall indicate the mapping of the contractor WBS to the contract

SOW WBS.

A. WBS: Pressurized cargo processing, Section 4, and sustaining engineering, Section 3, for the Orion Program shall be a separate WBS from ISS cargo processing and sustaining engineering. SOW Section 6 tasks (tasks associated with IDIQ Task Orders and Clause H.13, Underlimit Changes) shall have separate WBS’s than SOW Section 1 – 4. The WBS shall subdivide the total contracted effort into elements that serve as the basis for detailed planning and control of the project, and permit collection of cost and schedule data at element level. These elements include hardware, software, services, tasks, etc. It shall include all subcontracting and major procurement effort at the proper level. It shall be product oriented and structured so that key SOW tasks are at an appropriately high level.

B. WBS Dictionary: The WBS Dictionary shall define the scope and provide narratives that describe the tasks included in each element

8C. FORMAT: Electronic in MS Word, compatible with the Program authorized repository.

The WBS shall be in a chart format showing element relationships. The WBS Dictionary shall be ordered in consonance with the WBS and shall reference each WBS element by its identifier and name.

9. OPR: ISS Program Office (Mail Code OA) – Contracting Officer Representative

10. FIRST SUBMISSION DATE: Draft to be submitted with contract proposal. A final submittal is due 60 calendar days after contract phase-in begins.

Work Breakdown Structure (WBS) and Dictionary

1b. Data Type: 1

2. Date of Current Version 3a. DRD No.

April 1, 2018 CMC-PC-02

Provides framework to define work and to establish financial reporting levels and to correlate schedules.

6. References SOW 1.4.2 7. Interrelationships CMC PC-01, CMC PM-02

Frequency Of Submission: As need to maintain current.

Additional Submissions: See “Frequency of Submission”

11. MAINTENANCE: The plan shall be reviewed annually to ensure accuracy. Any updates to the plan require a resubmission of the plan.

12. COPIES/DISTRIBUTION: 1 electronic copy: Program Authorized Repository

Program Authorized Repository Upload Notification: Contracting Officer

14. REMARKS: None

1a. DRD Title:

Configuration Management Plan

1b. Data Type: 1

2. Date of Current Version

CMC-PC-03

Describes the assignment of responsibility organizationally and the procedures used in…