Section_J_Attachment_J-1_Rev._A.docx

RESEARCH, ENGINEERING AND MISSION INTEGRATION

Attachment J-1

Data Requirements List and Data Requirements Descriptions

MISSION AND PROGRAM INTEGRATION CONTRACT

RESEARCH, ENGINEERING AND MISSION INTEGRATION SERVICES

J-A1-29 J-A1-1

DATA REQUIREMENTS LIST (DRL) AND DATA REQUIREMENTS DESCRIPTIONS (DRD)

The following pages set out the documentation requirements of this contract, starting with a DRL, which is an index to the DRDs. Each DRD prescribes the required data product content, schedule, type, and other particulars for specific data submission requirements.

REMIS-CM

CM – Configuration Management

REMIS-EC

EC – Export Control

REMIS-IT

IT - Information Technology

REMIS-MA

MA – Management

REMIS-PC

PC - Program Control and Business Management

REMIS-PM

PM - Program Management

REMIS-PR

PR - Procurement

REMIS-SA

SA-Safety Assurance

REMIS-SI

SI – Systems Integration

Subject to the Rights in Data clause, 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 this contract. The contractor shall furnish data defined by the DRDs listed on the Data Requirements List (DRL) by category of data. 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) regulation or clause, the regulation shall take precedence over the DPD, per FAR 52.215.33. 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 Management Program, and NRRS 1441.1, NASA Records Retention Schedule, as applicable. The contractor shall disposition records and non-records in accordance with NPR 1441.1, which has been approved by NASA and the National Archives and Records Administration (NARA). All questions on records management issues shall be directed through the CO (CO) to the ISS Records Liaison Officer (RLO).

Documents included as applicable documents in this DPD are the issue specified in the Statement of Work, and form a part of the DPD to the extent specified herein. References to documents other than applicable documents in the data requirements of this DPD 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.

DESCRIPTION

This document identifies and defines the requirements and data types for information and data required under this contract.

The Data Requirement Descriptions (DRDs) define, by an individual Data Requirement (DR), the information and data required for each deliverable document.

The data types are used to identify the approval and control required for each DR. The Data Requirements List (DRL) is an index of all the DRs by category.

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 this clause, 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 Officer Representative (COR) shall have approval authority and shall sign the data prior to its release. Contractually binding documents shall 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 would include design solutions, status, and cost/schedule reporting; analyses and test results, handbooks; and other designated lists, reports, etc.

Type 1 submissions shall be marked “TYPE 1 PRELIMINARY pending NASA approval or Type I APPROVED BY NASA, as appropriate." Additional special designations and deviations may be required on specific submissions in accordance with configuration management requirements.

Type 2 submissions shall be marked “TYPE 2 PRELIMINARY - RELEASE TARGET DATE, xx/xx/xx" or "TYPE 2 FINAL - NASA COMMENTS INCLUDED" or “TYPE 2 FINAL DOCUMENT," where NASA comments were not received.

NOTE: Documents submitted under this clause, even though directly (Type 1) or implicitly (Type 2) approved by NASA, shall not take precedence over the specifications as set out in the Statement of Work, Section C.

The contractor shall normally deliver a complete revised Type 1 or Type 2 data requirement with NASA comments incorporated within 45 calendar days of receipt of comments.

Type 3 submissions shall be marked "TYPE 3 DOCUMENT - FOR INFORMATION, SURVEILLANCE, REVIEW, OR MANAGEMENT CONTROL".

NUMBER OF COPIES AND DISTRIBUTION REQUIREMENTS

The contractor shall provide one copy of each DR to the standard distribution list stated in the DRD. Additional distribution shall be made as directed, in writing, by the CO. The number of copies required shall not exceed the limits set forth in NFS 1852.208-81, Restrictions on Printing and Duplicating, without prior CO approval. Data Transmittal Forms shall be used to confirm delivery of electronically resident DR Deliverables.

ELECTRONIC FORMAT

DRDs shall be maintained electronically in the contractor's own format, unless a specified format is defined in the DRD. The Government may define specific DRD data format to support the utilization of this data in the Management Information System.

SUBMISSION INFORMATION

Wherever in the following DRDs under Block 10 "First Submission Date," or block 10 "Frequency of Submission," delivery is specified as at "FRR" or at any other program event, then delivery shall be required at the start or initialization of the event. Similarly when delivery is specified as a discrete amount of time before a program or project event (i.e., FRR minus 60 days) then delivery shall be required that discrete amount of time before the start of the program or project event. In addition, whenever delivery is specified as after an event, (i.e., FRR plus 30 days) delivery should be required after the end of the event.

DATA REQUIREMENTS DESCRIPTION

(Based on JSC-STD-123) 1a. DRD Title:

Configuration Management Plan

1b. Data Type: 1

2. Date of Current Version

3a. DRD No.

REMIS-CM-01

3b. RFP/Contract No.

NNJ17584385R

4. Use (Define need for, intended use of, and/or anticipated results of data) This plan is prepared by the contractor to describe the assignment of responsibility organizationally and the procedures used in accomplishment of the specific configuration management requirements as stated in the SOW and SSP 41170, Configuration Management Requirements.

5. DRD Category __ Technical X Administrative

__ SR&QA

6. References (SOW, Clause, etc.)

SOW 2.3

7. Interrelationships (e.g., with other DRDs)

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

SCOPE: This Configuration Management (CM) plan defines the requirements, responsibilities, and procedures for the CM system pursuant to SSP 41170, Configuration Management Requirements, and as it applies to this contract.

CONTENT: The CM plan shall address, as a minimum, the following:

A. Management Organization, (including reference documents)

1. Reserved

2. Responsibility and authority for CM including roles in configuration control boards and technical reviews.

3. Interfaces between contractor’s CM organization and NASA, subcontractors, and other contractor’s/contracts.

4. Reserved

B. Configuration Identification

1. Selection of Configuration Items (CIs) (Hardware, Computer Software Configuration Items [CSCIs], and firmware).

2. Establishment of the functional, allocated and product baselines for hardware and software

3. Assignment and application of configuration identifiers including serial numbers, part numbers, lot codes, software and firmware identifiers.

C. Configuration Control

1. Establishment of internal configuration and contractual baselines.

2. Implementation of internal and NASA configuration control.

3. Establishment of configuration control boards and processes.

4. Identification of processes to control changes, deviations, and waivers to program baselines.

D. Configuration Status Accounting

1. Hardware/Software Configuration Status Accounting processes and provisions for reports and/or access to Configuration Status Accounting data.

2. Description and methods of processes and tools to provide:

i. Identification of current approved configuration documentation and configuration identifiers associated with each CI.

ii. Status of proposed engineering changes from initiation to implementation.

iii. Waiver/deviation status and processing.

iv. Results of configuration audits; status and disposition of discrepancies.

v. Traceability of changes and confirmation of change incorporation.

vi. Methods of access to information.

3. Retention of historical data.

4. Systems and tools (including data elements).

E. Configuration Verification/Audits

1. Audit conduct, policies, procedures, documentation, access, and support.

2. Processes, plans, schedules for internal CM audits and subcontractor CM audits.

F. Data Management

1. Development, approval, release and submittal of configuration data/documentation (including drawings) in relation to program and contractual events (DRDs, technical reviews, FCA/PCA, Acceptance Reviews, CoFR, etc.).

2. Plan for subcontractor data management deliveries/control access.

3. Establishment and operation of Engineering Release Unit and CM receipt desk.

4. Process for Documentation control (i.e., DCNs).

5. Retention of historical data.

6. Systems and tools.

FORMAT: Electronic, compatible with the Program authorized repository.

9. OPR: ISS Configuration Management Office

10. FIRST SUBMISSION DATE: Thirty (30) calendar days after Task Order award.

Frequency of Submission: After initial approval - Annually Additional Submissions: Updated if major systems or processes are changed

11. MAINTENANCE: Electronic, as required (see additional submissions)

12. COPIES/DISTRIBUTION:

1 electronic copy: Program Authorized Repository Program Authorized Repository Upload Notification: ISS Data Management Program Authorized Repository Upload Notification: CO Program Authorized Repository Upload Notification: CO’s Representative

13. REMARKS: None

1a. DRD Title:

Export Control Plan (ECP)

2. Date of Current Version

3a. DRD No.

REMIS-EC-01

3b. RFP/Contract No.

NNJ17584385R

4. Use (Define need for, intended use of, and/or anticipated results of data)

Document the contractor’s approach for export control.

5. DRD Category __ Technical X_ Administrative

6. References (SOW, Clause, etc.)

FAR, NFS, and Contract Clause H.A.6, SOW 2.4

7. Interrelationships (e.g., with other DRDs)

DRD REMIS-EC-01

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

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.

CONTENT: The contractor shall prepare and submit an Export Control Plan (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.

FORMAT: Electronic, compatible with the Program authorized repository.

9. OPR: ISS Program Export Control Officer

10. FIRST SUBMISSION DATE: Thirty (30) calendar days after Task Order Award.

Frequency Of Submission: Annually Additional Submissions: As Requested

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: CO Program Authorized Repository Upload Notification: CO’s Representative Program Authorized Repository Upload Notification: Center Export Admin.

Program Authorized Repository Upload Notification: ISS Export Control Officer

13. REMARKS: The ECP Plan requires approval of the Center Export Administrator (CEA).

1a. DRD Title:

Information Technology (IT) Security Management Plan

2. Date of Current Version

3a. DRD No.

REMIS-IT-01

3b. RFP/Contract No.

NNJ17584385R

4. Use (Define need for, intended use of, and/or anticipated results of data) To ensure that IT security reporting requirements, IT Training and reporting, and response to potential data breaches are met for all IT systems utilized during work associated with TOs on this contract.

5. DRD Category _X_ Technical __ Administrative

6. References (SOW, Clause, etc.)

NFS 1852.204-76: Security Requirements for Unclassified IT Resources NPR 2810.1(series): Security of Information Technology.

OMB Circular A-130: Management of Federal Information Resources

SOW 2.5

7. Interrelationships (e.g., with other DRDs)

SCOPE: All contracts that purchase, lease, network to, or otherwise utilize Government-funded IT (as defined by the Clinger-Cohen Act of 1996 and referenced by OMB Circular A-130) must comply with NASA IT Security Requirements.

CONTENT:

A. IT SECURITY MANAGEMENT PROGRAM PLAN:

The Contractor shall submit an IT Security Management Program Plan for its unclassified technology information resources. This program plan shall describe the policy, processes, and procedures that will be followed to ensure appropriate security of IT resources that are developed, processed, or used under this contact. The Contractor’s IT Security Management Program Plan shall be compliant with the IT security requirements in accordance with Federal and NASA policies as referenced in OMB Circular A-130 and NPR 2810.1(series).

B. IT SECURITY PLAN:

The Contractor shall have a responsible individual that meets the intent of the NASA Handbook defined Information Systems Security Officer (ISSO) who is responsible for the contractor’s system(s) in accordance with the definitions set forth in NPR 2810.1(series). The IT security plan shall be kept up to date as changes to the baseline configuration of the system occur and shall be documented in the IT Security Plan. Note: An IT Security Plan is specific to a system or group of systems, while an IT Security Management Program Plan is defined as the elements a contractor has outlined to meet the IT Security requirements for interfacing with other contractors and NASA, training requirements and meeting the requirements, reporting of training accomplished in NPR 2810.1(series).

C. INCIDENT RESPONSE

The Contractor shall support Incident Responses. Incident Responses relates to dealing with the potential for and actual damage and distribution of information systems. An “incident” is any adverse event or situation associated with a system that poses a threat to the system’s integrity, availability, or confidentiality. An incident may result in or stem from any one of the following: a failure of security controls; an attempted or actual compromise of information; and/or waste, fraud, abuse, loss, or damage of government property or information.

The IT Security Management Plan shall address the company’s response to incidents and timing of reporting incidents to NASA.

Incident response training shall be accomplished for employees using the NASA SATERN System.

D. IT SECURITY AWARENESS TRAINING:

Employees subject to this contract shall complete the NASA approved IT Security Awareness Training annually in the NASA SATERN system for both the training content and reporting to NASA. By utilizing SATERN for training purposes, the Contractor evidence of periodic IT security awareness training is automatically maintained and reports can be generated for all employees subject on this contract. The contractor shall submit periodic SATERN reports (as required by the CO) detailing the overall status of the annual training program. The annual training program is defined by the CO.

E. IT SECURITY ROLE BASED TRAINING:

Employees subject to this contract shall complete NASA approved IT Security Training annually related to the following Role Based functions:

(Note: Each Offeror is allowed to define the positions that they will utilize based on their corporate best practices to accomplish the functions typically defined by NASA, listed below:)

· IT Security Manager

· Information System Owner (ISO)

· Information Systems Security Officer (ISSO)

· Organizational Computer Security Official – Representative (OCSO-R)

The Contractor shall accomplish periodic IT security training in the NASA SATERN system. The Contractor shall submit SATERN periodic reports (as required by the CO) detailing the overall status of the annual training program. The annual training program is defined by the CO.

F. INFORMATION ON EMPLOYEES IN SENSITIVE POSITIONS/ASSIGNMENTS REPORT:

The Information on Employees is Sensitive. Provide your corporate best practices for this functions and include your philosophy on background checks.

G. IT POINT OF CONTACT:

The contractor shall identify a point of contact that NASA may reach in its attempt to address IT and IT Security issues. The point of contact shall have the authority to ensure appropriate actions occur.

FORMAT: As defined in NPR 2810.1A and the applicable NIST, NITR and ITS-HBK documents specified above. Electronic, compatible with the Program authorized repository.

9. OPR: ISS Information Technology Office

10. FIRST SUBMISSION DATE: With individual Task Order proposals.

Frequency of Submission: As defined in NPR 2810.1A Additional Submissions: As defined in NPR 2810.1A

11. MAINTENANCE: As defined in NPR 2810.1A

12. COPIES/DISTRIBUTION:

1 electronic copy: CO and OCSO

13. REMARKS: None.

1a. DRD Title:

Task Order Plan

1b. Data Type: 3

2. Date of Current Version

3a. DRD No.

REMIS-MA-01

3b. RFP/Contract No.

NNJ17584385R

4. Use (Define need for, intended use of, and/or anticipated results of data) This DRD provides an integrated overview of the Contractor approach to accomplish the work defined in the NASA provided Task Order (TO). The Work Plan provides details on the technical task, proposed resources, and applicable requirements necessary to accomplish the Task Order. It clearly identifies all deliverables and provides a detailed development schedule with associated resource requirements. The work plan shall include the Contractor approach to performance reporting on technical progress, schedule adherence, and budget maintenance and analysis.

5. DRD Category X __ Technical

6. References (SOW, Clause, etc.)

SOW 1.2

7. Interrelationships (e.g., with other DRDs)

SCOPE: This DRD addresses any technical documentation that may be requested by the specific task orders.

CONTENT: The types of documentation include:

Preparation Information:

The following provides the requirements on the content and organization of the Contractor’s Task Order Response (TOR). Where separate detailed planning documents are to be prepared (as defined by the Task Order) on specific management functions, this document should include a summary of their content and a reference to them.

1.0 Technical Approach

1.1 Development Approach – Summary of design and development approach, including proposed design parameters, safety concerns, and key design requirements. Identify your approach to testing and verification, including test standards/margins used. Testing proposed to meet safety and performance requirements. Highlight component, subsystem, and system level testing. Identify potential options for reducing test costs.

1.2 Requirements Baseline – List or reference the requirements levied on the Contractor via the Task Order and discuss how these are flowed down to lower levels by summarizing the requirements allocation process.

1.3 Technology/Risks - Indicate any existing feasibility issues or proof-of-concept issues that must be taken into account in the development requiring additional testing along with any requirements that offer significant technical challenge or risk of failure. Describe the technology assessment, development, management, and acquisition strategies needed to achieve the Task Order objectives. Describe any opportunities for leveraging on-going technology efforts.

1.4 Logistics - Identify where the major project functions, such as hardware build, testing, integration, etc., will take place and describe the facilities, special services, vehicles, systems, and major equipment necessary to satisfy the identified logistic requirements. The spares philosophy with quantity anticipated should also be identified.

1.5 Mission Operations, Training and Data Management - Describe the operations, training, and data management approaches to the extent they are understood at the time including facility, hardware, and software requirements.

1.6 Safety - Define the ground and mission safety requirements of the project. Safety implications related to implementation of the task should be described with any apparent or implied key flight safety issues.

1.7 Product Assurance - Define the project specific product assurance requirements.

2.0 Management Approach

2.1 Management – Document the plan to monitor and control the Task Order requirements, technical design, schedule, and cost to achieve the objectives defined in the Task Order. Monitor and report on cost status and budget analysis in accordance Task Order Response. Evaluate the need for an OCI Mitigation Plan in response to the task order requirements.

2.2 Organization - Identifies key positions on the project and key external interfaces.

2.3 Work Breakdown Structure - Description reflecting the Contractor Work Breakdown Structure (CWBS) for organizing the technical elements and essential support for the TOR; it should be based (primarily) on deliverable hardware/software elements and sub-elements; the level of detail shall be adequate to support the allocation of personnel and costs and to define a logical schedule through design, implementation, delivery and operation phases (as appropriate for the TO). The CWBS structure should relate to line items on the master schedule and to the resources section.

2.4 Risk Management –Identify the risk management process that will be utilized to identify, monitor, and mitigate risks in response to the TOR.

2.5 Acquisition Plan – Identify all major proposed acquisitions in the relation to the CWBS and provide summary information on each. Describe all agreements for collaborative and/or cooperative relationships that support the TO.

2.6 Review Plan – Summarize the approach to conducting reviews for the delivery order content including peer reviews if appropriate. Describe the reporting requirements for reviews to be conducted along with the names, purposes, content and timing of the critical milestone reviews.

2.7 Documentation - Provide a project documentation tree that includes all governing, hardware development, mission integration, and safety documentation. Provide configuration management in accordance with REMIS-CM-01, Configuration Management Plan.

2.8 Schedule - The schedule delivered, as part of the TOP, shall be of sufficient detail to ensure that the technical team reviewing the proposals clearly understands the total approach being proposed by the Offerors.

2. 9 Resources - Specify the funding and personnel requirements needed for execution of the TO against the CWBS. The Cost data shall be provided by Fiscal Year (FY) and linked to the technical approach being proposed with appropriate level of Basis-of-Estimates to substantiate the cost being proposed. Identify any use to be made of other facilities for which another entity will be financially responsible.

2.10 Life-cycle Cost Estimate: For development projects, provide a life-cycle cost estimate at task inception and provide an updated life-cycle cost estimate as updated contractor work plans are developed.

FORMAT: Electronic, compatible with the Program authorized repository.

3. OPR: ISS Configuration Management Office.

4. FIRST SUBMISSION DATE: As specified in the Task Order.

Frequency of Submission: As specified in the Task Order.

Additional Submissions: As specified in the Task Order.

5. MAINTENANCE: Electronic, as required (see additional submissions).

6. COPIES/DISTRIBUTION:

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

7. REMARKS: None

1a. DRD Title:

NF533 Monthly/Quarterly Cost Reporting

1b. Data Type: 3

2. Date of Current Version

3a. DRD No.

REMIS-PC-01

3b. RFP/Contract No.

NNJ17584385R

4. Use (Define need for, intended use of, and/or anticipated results of data) 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 __ Technical X Administrative

__ SR&QA

6. References(SOW, Clause, etc.)

I.B.1, I.C.2

SOW 2.0, NPR 9501.2

7. Interrelationships (e.g., with other DRDs)

8. PREPARATION INFORMATION: Overall instructions and guidance are provided in NPR 9501.2D, NASA Contractor Financial Management Reporting.

SCOPE: The monthly/quarterly report shall provide a report for projecting costs and Work Year Equivalents (WYEs), for evaluating contractors’ actual cost and fee, for the planning, monitoring, and controlling of project and program resources, and for accruing cost.

CONTENT: Instructions for content are in Attachment 1. Content shall also include adding WYEs associated with direct labor and WYEs associated with subcontracts to the list of cost elements in NPR 9501.2D, NASA Contractor Financial Management Reporting. Also added to the cost elements is a separate line for major subcontractor’s costs. Major subcontractors are defined as contracts greater than $5M annually.

FORMAT: REMIS-PC-01 shall be uploaded into EDMS as an Excel file, with the exception of the signature page, which shall be a .pdf format.

In addition to Attachments 1, the following modifications shall be made to the monthly format. A column shall be added in front of section 7a to provide for “Prior Years Costs” (this column shall remain blank until the beginning of FY17). For section 8 add 4 columns to provide for four months of forecast; also under section 8, a column shall be added to provide for “Balance of Current Year (forecast).” and a column shall be added to provide for “Government Fiscal Year Estimate at Complete (forecast).”

The report shall be in three parts:

REMIS-PC-01A shall be an executive summary narrative with variance explanations at each WBS level. Variance explanations shall be required when a +/- 5% and +/- $10,000 variance occurs between the monthly forecasted cost and the actual cost for that month. The computation is (Monthly Forecasted Cost –Monthly Actual Cost/ Monthly Forecasted Cost). The variance explanation shall identify the lowest level WBS contributing to the variance. In addition, variance explanations need to detail what caused the variance (i.e., ISS Program change in direction, unexpected problems, and discrepancy due to a change order.) Also addressed shall be any impact to delivery and, or schedule and the contractor’s plan for resolving the effect of the variance. The forecast plan shall be adjusted to reflect a change in baseline plan. The executive summary shall also explain (listing and amount) any contract value changes and any changes between the types of contract.

REMIS-PC-01B shall be a top level summary listing by contract cost elements (see NPR 9501.2D) including EPs and major subcontractors. The top level summary shall also include a cost rollup at the WBS 1 level.

REMIS-PC-01C shall be by the WBS level in Attachment 2. Detail for rollup and additional contractor requirements also are included in attachment 2. In addition, cost elements reported in REMIS-PC-01A shall be reported in each section of the WBS designated as a rollup.

9. OPR: Resource Analyst

10. FIRST SUBMISSION DATE: NF533M (initial baseline) shall be submitted 30 calendar days after authorization to proceed.

Frequency of Submission: 533M

a. 533M hardcopy due not later than 12 working days following the close of the contractor’s monthly accounting period.

b. 533M EDMS due not later than 10 working days following the close of the contractor’s monthly accounting period.

1. MAINTENANCE: The contractor shall provide a revised NF533M to correct errors when deemed necessary by the Financial Management Division. The revised NF533M shall be delivered prior to closure of the current JSC accounting system for the month. The reports shall be maintained electronically by the contractor

12. COPIES/DISTRIBUTION:

1 electronic copy: Program secure Repository Program Authorized Repository Upload Notification: ISS Data Management Program Authorized Repository Upload Notification: ISS Assessment Office Program Authorized Repository Upload Notification: Resource Analyst Program Authorized Repository Upload Notification: Financial Management Division Program Authorized Repository Upload Notification: CO Program Authorized Repository Upload Notification: CO’s Representative

13. REMARKS: None

NASA Form 533 (NF533) Reports – REMIS-PC-01 Attachment

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 and NF533Q.

Common NF533 Cost Elements

Examples of accrual accounting for common cost elements reported on the NF533 follow:

Equipment and Materials (commercial off the shelf)

Generally reported to NASA when received and accepted by the contractor.

Common NF533 Data Elements

The following NF533 Data Elements shall be included:

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 and Equipment (PP&E) Reporting

(A.) For PP&E items the contractor plans to purchase, fabricate, or modify, the contractor shall obtain, from the JSC Finance Property Office, the NASA Capitalization/Expense determination. This determination shall be obtained by the contractor prior to any cost being incurred for the PP&E purchase/fabrication/modification. This will help ensure appropriate 533 reporting for items identified as capital. The capitalization/expense determination governs the contractor’s cost reporting requirements associated with the PP&E.

The JSC Finance Property Office makes the capitalization/expense determination based on information provided by the NASA Project Manager. The JSC Finance Property Office acquires the information from the NASA Project Manager using the Form NF1739 Capitalization Determination Form (CDF), which is required for each asset valued at, or greater than $500K. The JSC Finance Property Office may utilize a supplemental questionnaire and/or additional communication with the project manager, or their associates, to ensure adequate information is obtained to make the appropriate accounting treatment determination (i.e., to Capitalize or Expense the asset).

(B) For PP&E purchased, fabricated or modified, and determined by the JSC Finance Property Office to be Capital, the contractor shall:

1. Report the costs of each capital asset (i.e., each individual end item deliverable) as a separate reporting category on the NF 533 or other required cost reporting format.

2. Maintain a reporting structure that allows for the contractor’s accumulation and reporting of cost separately for each identified capital asset (i.e., each individual end item deliverable).

(C) For PP&E purchased, fabricated or modified, and determined by the JSC Finance Property Office to be Expensed (Non-Capital), the contractor is not required to report costs at the detail asset level (i.e., as a separate reporting category on the NF 533 or other required cost reporting format).

NF533 Due Dates

The due dates for the NF533M and NF533Q reports are outlined in Chapter 3 of NPR 9501.2E. The following is a summary of the NF533 due date requirements:

The due dates reflect the date the NF533 reports are received by personnel on the distribution list, not the date the reports are generated or mailed by the contractor. It is critical that the NF533 reports are submitted in a timely manner to ensure adequate time for NASA to analyze and record the cost into the NASA accounting system.

An initial NF533 report is required in the NF533Q format to be used as a baseline for the life of the contract. The initial (baseline) NF533Q report shall be submitted by the contractor within 30 days after authorization to proceed has been granted. The initial NF533 requirement cannot be waived. The initial report shall reflect the original contract value detailed by negotiated reporting categories and shall be the original contract baseline plan. In addition to the initial (baseline) report, monthly NF533 reporting shall begin no later than 30 days after the 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 Supplemental Reporting

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

J-A1-43

APPENDIX B. Required Supplemental Reporting

Annual Accounting Calendar: The contractor’s accounting calendar for the contract period of performance shall be provided in electronic format to the LC2 resource analyst, and LF3 Cost Accountant within 10 business days after contract award. Updates to the accounting calendar shall be provided in electronic format to the LC2 resource analyst and LF3 Cost Accountant before the delivery of the subsequent NF533.

Contractor Variance Report: The contractor shall submit variance reports along with the NF533M when NF533M variances meet or exceed +/- 5% for each Reporting Category for the following items:

1. Column 7A current month (actuals) to 8A previous month (estimate)

2. Column 7A current month (actuals) to 7B current month (plan)

Monthly Unfilled Orders: The contractor shall submit a report in conjunction with the delivery of the monthly NF533M if there are Unfilled Orders Outstanding (10). The report shall be broken down by reporting category and include the item description, the originally reported delivery date and costs, updated delivery date and costs, justifications for delays of greater than 30 days, and justifications for changes in costs greater than 5%. The following format shall be used for this report.

Quarterly Estimate Report: If the contractor’s month-end reporting does not align with the last day of the calendar month, the contractor shall provide a supplemental report for each calendar-month ending a government fiscal quarter (December, March, June, and September). The report shall be broken down by reporting category and include the original and adjusted 533M Current Month Estimated Cost and Hours (8a) that reflects the estimated costs and hours accrued through the last day of the calendar month. All estimated costs shall include unfilled orders expected to be delivered during the adjusted period. The following format shall be used for this report.

Annual Economic Impact Assessment: The contractor shall submit answers to the following four questions back to the LC2 resource analyst in conjunction with the delivery of the October NF533M. The answers should be estimates only, as this requirement is not intended to be an extensive exercise. The information provided will be rolled-up to create Center-level estimates, and will not identify any specific contract. This information will not be shared at the contract-level with anyone outside NASA.

1. What was the on-board total headcount for this contract as of September 30th? (Please include in-directs and an estimate for your major subcontractors.)

2. For the total workforce indicated in #1 above, approximately how many worked in the local Clear Lake area, including JSC? (JSC includes JSC proper, Sonny Carter Training Facility, and Ellington Field.)

3. What was the approximate dollar value of goods and services (including labor) purchased in the Houston area under this contract during the prior Government Fiscal Year?

4. What was the approximate dollar value of goods and services (including labor) purchased outside the Houston area but within the State of Texas?

1a. DRD Title:

Small Business Subcontracting Plan and Reports

1b. Data Type: Plan -1 Report – 2

2. Date of Current Version

3a. DRD No.

NNJ17584385R

4. Use (Define need for, intended use of, and/or anticipated results of data)

To describe the Contracator’s planned approach to Small Business Subcontracting and their reporting against this plan.

5. DRD Category

PC

6. References (SOW, Clause, etc.)

a. FAR 19.702, Statutory requirements

b. FAR 52.219-8, Utilization of Small Business Concerns

c. FAR 52.219-9, Small Business Subcontracting Plan

d. NFS 1852.219-75, Small Business Subcontracting Reporting

7. Interrelationships (e.g., with other DRDs)

L.18.4(b)(5)