Draft NOC II DRL_DRDs.docx

Neutral Buoyancy Laboratory (NBL) Operations Contract II (NOCII)

Contract Data Requirements List (CDRL)

And

Data Requirements Descriptions (DRD)

TABLE 1: CONTRACT DATA REQUIREMENTS LIST (CDRL)

Annually by 9/30

Reports - Monthly

DATA TYPE DESCRIPTION

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

Type 1: Written Approval

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. Contractually binding documents will not be implemented nor revised without contractual authorization.

Type 2: Mandatory Submittal

Data submitted to NASA for coordination, information, review, and/or management control.

Type 3: Submittal Upon Request

Data prepared and retained by respondent to be made available to requiring organization upon request.

OPR ORGANIZATIONS

BA – Office of Procurement CA – Flight Operations Directorate (FOD) CA3 – FOD Business Office Chief IA – Information Resources Directorate JB3 – Center Operations Directorate, Property, Supply, and Equipment Branch LA – Office of the Chief Financial Officer NS – JSC Safety and Test Operations Division NT – Quality and Flight Equipment Division

1. DRD Title: Management Plan, Contractor Work Breakdown Structure, and Dictionary

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To provide a comprehensive plan that integrates all aspects of the SOW to accomplish efficient and effective management. To organize the tasks to be accomplished in this contract in a service-oriented structure. The Contractor Work Breakdown Structure CWBS and dictionary shall provide the framework for structuring the program implementation plans, establishing and tracking budgets, preparing schedules, developing work force and material estimates, preparing work authorization documents, and reporting contract performance

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Due with proposal.

Submission Frequency: Each CWBS update or as required

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· SOW 1.0

· SOW 1.1

· SOW 1.3

Applicable Documents: N/A

Scope: The Management Plan shall describe the basis for the Contractor’s management approach, organization, and systems managing all services and functions described in the SOW. It shall provide comprehensive integration of all management systems of the prime, subcontractors, and major vendors. The systems shall include those specifically required by the Statement of Work, as well as those systems and procedures to be set in place by the Contractor. It shall include the CWBS which shall encompass all the services required to achieve all the requirements of this contract. The CWBS shall subdivide the work to be accomplished into elements that serve as the basis for detailed planning and control, and in addition, permit collection of cost and schedule data for each element.

Contents:

The Contractor shall address the following elements:

Remarks: Upon Contract Award, the Contractor’s Contract Management Plan becomes a part of the contract.

Maintenance: Revisions shall be incorporated by complete reissue.

F

1. DRD Title: Configuration Management Plan

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To define and describe the Contractor’s configuration management processes for hardware, software, and documentation.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Contract award + 15 days.

Submission Frequency: As required.

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· SOW 1.10

· SOW 1.16

· SOW 1.16.4

Applicable Documents:

· NPR 7120.5F, NASA Space Flight Program and Project Management Requirements

· NPR 7123.1C, NASA Systems Engineering Processes and Requirements

· ISO 10007, Quality Management Systems – Guidelines for Configuration Management

· JSC-63756, Flight Operations Directorate Software Management Plan

Scope: The Configuration Management Plan defines and describes all Contractor configuration management processes for hardware, software, and documentation.

Contents: The Configuration Management (CM) Plan shall define and describe the processes and methodologies for performing configuration management of hardware, software and documentation. As a minimum, describe the following:

i. The criteria for selecting items that require the application of CM

ii. Contractor processes to perform CM in accordance with the SOW and applicable documents. Ensure that the following are addressed: changes management; tracking approved versions of hardware; software and documentation; managing varying states of maturity; coordinating dependent interfaces.

iii. The specific allocation of responsibilities, accountability, authority, and resources for performing CM. Include any variations that occur during the different lifecycle phases.

iv. The procedures for identifying and removing non-conforming products. (DRD-NOCII-17 defines the Non- conformance Record Template to be utilized by NOCII.)

v. Document support (e.g., word processing, document formatting) and configuration management for all NBL documents (e.g., NASA documents on the CX Master List).

vi. Method of electronic document availability to all JSC users, including a listing of all documentation, and how it will be delivered to NASA, for unrestricted use.

vii. How the quality records will be maintained

viii. How the Contractor will ensure that only approved documentation is utilized to perform user operations in the facilities

ix. A description of the procedure for making changes to the Configuration Management Plan.

Remarks: N/A

Maintenance: Update as required due to configuration management process or procedure changes. Revisions shall be incorporated by complete reissue.

1. DRD Title: Efficiencies and Innovative Techniques

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☒ Administrative ☐

S&MA ☐

10. Description/Use: To provide a comprehensive plan for Efficiencies and Innovative Techniques for improving contract performance with the goals of working more safely, enhancing quality, ensuring user satisfaction, and reducing cost

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Due with proposal.

Submission Frequency: Annually, 30 days prior to the start of every contract year.

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· SOW 1.0

Applicable Documents: N/A

Scope: The Efficiencies and Innovative Techniques Plan shall describe the Contractor’s multi-year approach for improving technical performance, risk reduction and cost for all functions detailed in the SOW and include a detailed description of each planned improvement. Contractor proposed innovations that would significantly enhance operations are to be included and will be considered as a factor during annual reviews.

Contents: The Contractor shall propose efficiencies and innovative techniques that streamline processes, improve technical performance, and/or reduce risk or cost without compromising safety, or mission success.

For each efficiency or innovation proposed through this DRD, the Contractor shall, at a minimum, describe the technical and management approach, risks and risk mitigations, schedule, investment cost by WBS element by fiscal year for each proposed efficiency or innovation, and proposed savings by WBS element. There shall be enough detail for the Government to adequately assess the practicality and return on investment for each suggested improvement. The Government reserves the right to engage the Contractor for more detail and discussion on above proposal.

The Offeror shall provide SOW language and SOW location for each efficiency and innovation proposed under Technical Approach (TA) - Mission Suitability Sub-factor 2, (TA1). Innovations and efficiencies may be incorporated into the SOW after award.

1. DRD Title: External Customers Plan

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To provide a comprehensive plan for maintaining and supporting external customers of the NBL.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Due with proposal.

Submission Frequency: Update after approval of plan + 1 year; afterward as required. Reports monthly.

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· SOW 2.4

Applicable Documents:

· NPD 1050.1 Authority to Enter into a SAA

· Space Act Agreement Guide

Scope: The External Customers Plan (ECP) describes the Contractor’s multi-year approach for supporting and integrating approved external customers for use of the facilities. After approval, the External Customers Plan will become part of the contract as Attachment J-04. Execution of External Customer agreements shall be in accordance with Clause H.8, Non-Government Use of NASA Facilities.

Contents:

The External Customers Plan shall describe the Contractor’s comprehensive plan for supporting and integrating approved (both current and future) external customers of the NBL per the SOW.

The plan shall demonstrate the Contractor’s approach and methods for passing cost savings to FOD as a result of supporting external customers.

The ECP shall describe all processes, data requirements and approval cycles for External Customers, for both external customers brought in by the Contractor via an RSAA and external customers brought in by NASA. The ECP shall follow the table of contents below, supplemented by other relevant data identified by the Contractor:

1. Executive Summary – summarize the plan’s key points and approaches.

2. Infrastructure Development:

a. NBL Capabilities, Constraints, and Policies:

i. Identify and evaluate NBL Facility capabilities not generally available from the commercial market and unique to NASA.

ii. Provide a checklist of all constraints and policies the Customer must meet in order to operate in the NBL.

iii. Provide a process that reviews the potential customer’s requirements against NBL capabilities, constraints, and policies.

iv. Describe plans to resolve issues between customer requirements and NBL schedules, capabilities, constraints, and policies.

(Goal: These checklists and processes will be used to assess potential customers, with the intent that if they satisfy all constraints it makes them eligible to enter into an agreement with the Contractor or NASA)

b. Procedures:

i. Identify and describe procedures for reducing/eliminating conflict between government and non- government work.

ii. Identify and describe any changes the Government needs in its processes, procedures, special terms and conditions that the Government may consider to accommodate external customer needs.

iii. Identify and describe procedures for coordinating user requests for new services within pre-existing commitments to ensure compatibility and fulfillment with existing resources.

iv. Identify and describe procedures for protecting data between companies and potential Organizational Conflicts of Interest.

v. Identify schedules and metrics for staying within the plan.

c. Costs:

i. Describe your plan to assist NASA in updating the price list for use of the NBL. Identify all factors that you will consider in updating the costs (e.g., equipment maintenance and replacement costs).

ii. Describe your approach for determining the cost savings to FOD for each External Customer agreement utilizing accepted accounting practices. Include actual reimbursement to NASA, auditable cost offsets and any other factors deemed appropriate. Propose a format for reporting this data to NASA.

3. Integration Support

i. Describe plans to support both NASA and the customer during agreement development and negotiations.

ii. Describe plans to document the customer’s requirements and how they satisfied all constraints and policies. (This data will be used to demonstrate compatibility between the External Customer’s requirements and NASA’s facilities. It may also be utilized in the formulation of the formal agreement with the customer, as needed).

4. Implementation

i. Describe your approach to implementing and executing the External Customer’s requirements from the point of a signed agreement/commitment through completion of the External Customer activity.

5. Reports:

a. The Contractor shall submit monthly reports summarizing approved external customer operations, satisfaction, Reports shall include, at a minimum:

i. Approved Customers

1. Success in meeting the needs/requirements of all approved external customers

2. Customer and NASA satisfaction with external customer operations

3. Financial report including

· Contract hours and dollar values applicable to NF 533 offset

· Reimbursement payments to NASA

4. Six month outlook of external customer activity

ii. Potential customers, and the associated:

1. Amount of work expected,

2. Anticipated activities,

3. Timeframe/ Length of use,

4. Level and type of support by the Contractor

5. Estimated support of the Contractor

6. Facility equipment and infrastructure required,

7. Additional details not otherwise addressed (e.g., operations, setup, teardown)

6. Other relevant data.

a. SOW Appendix C includes a performance standard for supporting external customers.

b. Other relevant data identified by the Contractor

1. DRD Title: Risk Management Plan

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To describe the Contractor’s implementation approach for performing and reporting risk management, in conformance with the processes that are defined by the Government.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Contract start + 15 days.

Submission Frequency: As required

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· SOW 1.14

Applicable Documents:

· NPR 7120.5F, NASA Space Flight Program and Project Management Requirements

· NPR 8000.4, Risk Management Procedural Requirements

Scope: The Risk Management Plan documents the process that the Contractor will follow to manage risk throughout the duration of the contract and provide government insight to risk management. “Risk” refers to anything that can prevent a team from meeting the contract requirements. All forms of risk shall be managed. These include technical, programmatic, supportability, cost, and schedule risks.

Contents: The Risk Management Plan shall describe the Contractor’s processes to provide management at all levels with 1) a disciplined system for early identification of technical uncertainties, 2) a disciplined assessment of current project status, and 3) key indicators of mission success. The plan shall describe the basis for taking action to control risk and for measuring the effectiveness of that action. As a minimum the plan shall discuss:

i. Risk identification – The process to determine and define all risks.

ii. Risk analysis – The process to convert risk data into decision-making information. This process should include estimating the probability, impact and time frame of the risks, eliminating duplicate risks (including grouping similar risks) and prioritizing risks according to consequences.

iii. Risk planning – The process to develop mitigation options and decide what to do with the risks.

iv. Risk tracking – The process to acquire, compile and report risk status data, including risk indicators and mitigation actions. Appropriate risk metrics shall be identified so that the Government can evaluate the quality of the risk management.

v. Risk control – The process covering decisions to re-plan mitigation, close risks, invoke contingency plans or continue to track risks. The plan shall define responsibilities, typical milestones/reviews, and describe the key risk control activities.

vi. Communications and documentation –These are the means by which the output of the processes is documented and communicated to all team members. It is present in all the above processes.

vii. The plan shall also identify the information to be documented for each risk. For risks having both a high probability and high impact/severity, the plan shall require, as a minimum, the following:

(1) Description of the risk

(2) Primary consequence should the undesirable event occur

(3) Estimate of probability of occurrence and the fidelity of the estimate

(4) Significant cost impacts, given its occurrence

(5) Significant schedule impacts, given its occurrence

(6) Potential mitigation measure not already taken and the cost to implement them

(7) Characterization of the risk as acceptable or unacceptable with rationale.

1. DRD Title: Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan

5. Solicitation No.: (Insert number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The DEIA plan demonstrates the contractor’s commitment to fairness regarding diversity, equity, inclusion, and accessibility. This plan will provide NASA with an understanding of how the contractor plans to recruit, retain, and develop a diverse high performing workforce from underserved communities. The plan shall include measurable performance metrics and objectives. The DEIA plan will be utilized as an assessment tool by the contracting officer to monitor the contractor’s progression in its commitment to diversifying its workforce.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Plan shall be submitted within 30 days after contract award.

Submission Frequency: Update annually

Format: Contractor’s format is acceptable.

Interrelationship:

Applicable Documents: Executive Order 13985, Advancing Racial Equity and Support for Underserved Communities Through the Federal Government

Scope: In support of the Executive Order 13985, Advancing Racial Equity and Support for Underserved Communities Through the Federal Government, NASA is seeking to advance equity or remove barriers for members of underserved communities to access procurement opportunities. Underserved communities refer to populations sharing a particular characteristic, as well as geographic communities, that have been systematically denied a full opportunity to participate in aspects of economic, social, and civic life. Underserved Communities include Black, Latino, Indigenous, Native American, Asian Americans and Pacific Islanders and other persons of color; members of religious minorities; lesbian, gay, bisexual, transgender, and queer (LGBTQ+) persons; persons with disabilities; persons who live in rural areas; and persons otherwise adversely affected by persistent poverty or inequality.

Contents:

The DEIA Plan shall identify qualitative and quantitative approaches utilized to measure progress in the areas of Leadership and Commitment, Diverse Talent, and Culture and Sustainability. The following shall be addressed annually:

Leadership and Commitment – Demonstrate leadership’s commitment and accountability to diversity, equity, and inclusion. Identify quantitative approaches utilized to measure progress of a Diversity and Inclusion program

1. What is the operational status of, and level of resources available to, offices or divisions within the organization that are responsible for advancing civil rights or whose mandates specifically include serving underrepresented or disadvantaged communities?

2. What actions has the organization taken to implement affirmative equity-enhancing policies, regulations, guidance, and approaches to emphasizing equity in policy and rule-making processes?

3. Describe how the organization’s commitment will be communicated internally and externally from leadership to employees and stakeholders.

Diverse Talent – Demonstrate a pursuit of a high performing diverse workforce from underserved communities.

1. Discuss the specific diversity metrics utilized by the organization to measure performance in achieving a diverse workforce and provide the corresponding metrics for the current or most recent organizational reporting period

2. What barriers or opportunities exist to engage subject matter experts from underserved communities in industry and academia? How does the organization plan to overcome those barriers?

3. How will underserved communities be leveraged?

4. Describe recruiting activities, objectives, and outcomes (e.g., number of participants, number interviewed and hired from underserved communities).

Culture & Sustainability – Demonstrate how an inclusive and fair work environment will be cultivated and maintained.

1. Based on the data, what structures and strategies will be used to manage diversity, measure results, refine approaches, and institutionalize a culture of inclusion?

2. Identify actionable opportunities to improve data collection, use, and sharing that would allow for disaggregation, the ability to deliver services more equitably, and better understanding of how programmatic and policy decisions impact underserved communities.

3. Describe other corporate activities that seek to increase support of diversity, equity, and inclusion.

Maintenance: Changes shall be incorporated by complete reissue.

1. DRD Title: Small Business Subcontracting Plan and Reports

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To describe the Contractor's planned approach to Small Business Subcontracting and their reporting against this plan.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Due with Proposal

Submission Frequency:

Plan:

• Plan is due annually by 90 days prior to the anniversary of the contract

• Update at contract start, then updates as required.

• Revisions shall be submitted within 45 days after required changes have been identified.

• Approval prior to contract award.

Reports:

• All reports shall be submitted in accordance with FAR 52.219-9 and NFS 1852.219-75.

• The contractor shall submit semi-annually and at contract completion to the NASA/JSC Contracting Officer Individual Subcontract Report (ISR) and Summary Subcontracting Reporting (SSR), using the electronic version of this data.

• Contractors are required to submit subcontracting data in the Electronic Subcontracting Reporting System (eSRS).

• All contractors are required to register and file both types of subcontracting reports using the eSRS system. The website to register is www.esrs.gov.

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

· All reports shall be submitted in accordance with FAR 52.219-9 and NFS 1852.219-75.

Interrelationship:

· SOW 1.3

· Clause H.6

· Attachment J-01

Applicable Documents:

· FAR 19.702, Statutory requirements

· FAR 52.219-8, Utilization of Small Business Concerns

· FAR 52.219-9, Small Business Subcontracting Plan

· NFS 1852.219-75, Small Business Subcontracting Reporting

Scope: The Small Business Subcontracting Plan shall be in compliance with FAR 52.219-9. The Small Business Subcontracting Reporting shall be in compliance with NFS 1852.219-75.

Contents: The Subcontracting plan must include the approach that the Contractor intends to use in meeting the subcontracting goals. Subcontractors whose bid is part of this proposal should be identified. For each subcontractor, the percentage of the proposal and any small or small business subcategory classification should be identified. For areas of potential future subcontracting, the Contractor should identify the area of work, the percentage of contract that this is expected to encompass, potential subcontractors and their small business or small business subcategory classification. Describe the management approach to subcontracting with small, small disadvantaged businesses, Women-owned small businesses (WOSB), Historically Underutilized Business Zone (HUBZone), Veteran Owned Small Businesses (VOSB), Service Disabled Veteran Owned Small Businesses, and Historically Black Universities,(HBCU) and Minority Serving Institutions (MSIs).

Remarks: The Small Business Plan shall become a part of the contract as Attachment J-01.

1. DRD Title: Phase-In Plan

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To describe the Contractor's planned Phase-In approach.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Due with proposal with exception of item xvii. That shall be provided upon request.

Submission Frequency: One Time

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· DRD-NOCII-26

· DRD-NOCII-31

Applicable Documents:

Scope: The NOC II Phase-In Plan provides plans for the transfer of all anticipated on-going development and operations activities along with supporting logic and rationale. This includes but is not limited to the initial overall staffing strategy/incumbent capture plan and critical skills plans to meet the NOC II start up staffing requirements ensuring uninterrupted operations services with qualified/certified personnel.

Contents:

This Phase-In Plan shall describe the overall plan for transition. At a minimum, it shall address:

i. Schedule with key milestones, and personnel responsible for those milestones

ii. Approach and rationale for implementing the plans, procedures, and processes required for performance of the contract, including property, personnel, facilities, and security,

iii. Approach to transitioning existing external customers to NOC II. This includes the approach for establishing a Reimbursable Space Act Agreement (RSAA) with NASA similar to that held by incumbent.

iv. Approach for retaining critical skills

v. Approach for transferring all existing software licenses and ownership from current contractor to NASA

vi. Metrics used to determine progress for contract transition,

vii. Property control transfer,

viii. Property location moves for GFP in the following locations: N/A

ix. Software control transfer,

x. Documentation control transfer,

xi. Facilities responsibility transfer,

xii. Incorporation of existing CR, DR, TO, and all technical and administrative data (e.g., metrics data from previous years), Data Packages (DRD-NOCII-31) and NBL Databases (DRD-NOCII- 26)

xiii. Mission assurance considerations,

xiv. Security considerations,

xv. Risk mitigation strategy,

xvi. Configuration management considerations.

xvii. Phase-In cost shall be separately identifiable and tracked within an Offeror’s accounting system. The Contracting Officer may request actual cost and hours associated with Phase-In once Phase-In is complete and final indirect rates are established.

1. DRD Title: Government Property Management Plan (PMP)

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To describe the method of administering and controlling Government personal property and submitting proposed property manager qualifications.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

· Initial Submission: Apparent Successful Offeror shall submit within 10 days of Contracting Officer’s request. Supplemental property procedures due 60 days after contract start.

Submission Frequency: One Time and Revisions

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· SOW 1.17.1

Applicable Documents:

· Federal Acquisition Regulation (FAR) 52.245-1 Government Property Clause

Scope: The Government Property Management Plan defines the Contractor's use, maintenance, repair, protection, and preservation of Government personal property. It shall describe the Contractor's approach to receiving, handling, stocking, maintaining, protecting and issuing Government property (equipment and material). The Plan should include interaction and Department/ Office responsibilities. The Contractor shall submit to the delegated Government Property Administrator (GPA) detailed supplemental property procedures, which are separate from the Property Management Plan, no less than 60 days after the contract start date.

The Contractors submitting an initial Property Management Plan as part of their reply to the Request for Proposal in accordance with Contracting Officer direction, will also submit proposed property manager qualifications and experience as specified below.

Contents:

This plan shall reference those policies and procedures which are part of the Contractor's Property Management System and shall include at a minimum, but not limited to, the following functions/outcomes/activities:

1. Property Management

(a) Voluntary consensus standards, industry-leading practices and standards, customary commercial practices

(b) Periodic internal reviews, surveillances, self-assessments, and audits

(c) Written procedures

2. Acquisition of Property

(a) Acquisition authority

(b) Classification of property

3. Receipt of Government Property

(a) Receiving

(b) Identification

4. Records of Government Property

5. Physical Inventory

6. Subcontractor Control

(a) Flow down of property clauses to subcontractors

7. Reports (a) Loss, Theft, Damage, Destruction reports

(b) Physical Inventory reports

(c) Audits and self-assessment reports

(d) Corrective Action reports

8. Relief of Stewardship Responsibility and Liability

(a) Loss, Theft, Damage, Destruction of property

(b) Consumed property

(c) Delivered property

(d) Contractor Inventory Disposal of property

i. In-house screening of excess

ii. Disclosure of excess

(e) Abandonment of Government property (if directed by the Government)

9. Utilizing Government Property

(a) Utilization

(b) Consumption

(c) Movement

(d) Storage

10. Maintenance

(a) Preventive maintenance

(b) Rehabilitation

(c) Calibration

11. Property Closeout

(a) Screening for further use

(b) Final physical inventory

(c) Transfers off the contract

(d) Final NASA Form 1018

12. Reconcile Contractor Records with NASA Financial Property Records [NASA Form 1018 and the Contractor-Held Asset Tracking System (CHATS) if applicable]

13. JSC-Unique Considerations (as they arise or known now)

Management Qualifications/Experience:

1. The Offeror/Contractor shall specify the name and the qualifications of the proposed property manager.

(a) List the Federal agencies or departments supported in managing Government property and the corresponding number of years of experience.

(b) List completed personal property management training courses.

(c) Specify the level of professional property management certification obtained by the proposed property manager.

(d) List professional personal property management organizations in which the proposed property manager has an active current membership.

2. This qualification data shall be a one-time submittal from the Offerors with their initial Property Management Plan (PMP) when the plan is requested by the Contracting Officer. Insert that data as a separate tab after that PMP. This qualification data shall be excluded from the final PMP from the awarded Contractor.

Maintenance: Changes to the PMP shall be incorporated by complete reissue after coordination with the Government PA.

1. DRD Title: Change Control Process and Plan

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: This process plan shall describe the Contractor’s change control process for development, modifications, and sustaining changes to the NBL facility and systems covered in the SOW.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Due with proposal

Submission Frequency: As required

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· SOW 1.16.2

Applicable Documents:

· CX-WI-0036, CX Change Request Process

· JSC-63756, Flight Operations Directorate Software Management Plan

Scope: The NBL will utilize the NASA change control process, described in CX-WI-0036, for NOCII. The Change Control Process Plan (CCPP) shall describe the Contractor’s internal change control processes and how those processes interface with CX-WI-0036.

Contents: The Contractor shall describe its internal change control processes for both Change Requests (CRs) and Task Orders. As a minimum, this plan shall address and describe these areas:

1. Roles, responsibilities and dependencies (e.g., product deliveries). Address the NOCII Contractor, NASA, the change originator and other organizations involved in the change.

2. Processes for change development, including support of requirements development and definition, NASA and Contractor screening, impact assessment, making recommendations related to the change, obtaining NASA and Contractor control board review and approval.

3. Providing quality assurance support and preventing organizational conflicts of interest (OCI) throughout the change development and implementation process

4. Interrelationships between the change control process and other NOCII processes (e.g., discrepancy reporting/management)

5. Processes and methodologies for cost and schedule estimating, including how the Contractor will ensure accuracy in these critical areas.

6. Process for controlling cost and schedule during change implementation. Address management of requirements updates and resulting impacts.

7. Interfacing Contractor change processes with NASA’s existing change control process (CX- WI-0036)

8. Providing change approval status and change implementation status to NASA-authorized personnel; e.g., the change originator.

9. Describe all differences between processes and methods for IDIQ TOs versus core change requests

10. Deliverables; e.g., change control database and metric reports.

1. DRD Title: Maintenance Plan

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☒ Administrative ☐

S&MA ☐

10. Description/Use: This plan will document the Contractor’s approach to for maintenance of NBL mockup and systems.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: Due with proposal; all sections labeled as Part (2) not required with proposal.

Submission Frequency: As required

Format: Contractor discretion, unless otherwise agreed upon between NASA and the Contractor. The electronic format shall be compatible with Microsoft Office.

Interrelationship:

· SOW 1.8

· SOW 2.2

Applicable Documents: N/A

Scope: The Maintenance Plan shall encompass all mockups, systems and equipment at the NBL. The plan describes the process for preventative maintenance, return to print maintenance, equipment replacement and returning the mockup or system to service. The plan also provides the scheduling process to conduct all activities within the plan to minimize impacts to events in the facility.

Contents:

i. Roles and responsibilities: The Contractor shall provide a description of all resources (labor and non-labor) to complete the activities stated in the plan. The Contractor shall provide the organizational structure that will perform the maintenance along with a narrative of their responsibilities.

ii. Preventative maintenance:

Part (1): The Contractor shall describe their approach for conducting preventative maintenance, providing associated rationale.

Part (2): The Contractor shall provide a list of existing, modified or new processes, procedures and documents that will be used to conduct preventative maintenance.

iii. Return to print maintenance:

Part (1): The Contractor shall describe the approach that will be used to conduct return to print maintenance, providing associated rationale.

Part (2): The Contractor shall provide a list of existing, modified or new processes, procedures and documents that will be used for return to print maintenance.

iv. Equipment replacement and critical spares

Part (1): The Contractor shall describe their approach for equipment replacement maintenance, providing associated rationale. The Contractor shall include a cost benefit analysis approach for determining replacement feasibility of general shop equipment (e.g., drill press, lathe, mill).

Part (2): The Contractor shall provide a list of all equipment in mockups or systems that use consumables, replacement components or are themselves required to be replaced during normal operations. This list shall be based on vendor recommendations, failure trends and performance data. The list shall provide the frequency of replacement, estimated cost for time and materials, and if it is not a Commercial Off the Shelf (COTS) item, provide the lead time to procure the item.

The Contractor shall provide a critical spares list. The Contractor shall start with the existing critical spares list and provide justification if they plan to add or remove items from the list.

The Contractor shall provide a list of all operating systems and software used in the facility that are not supported by other FOD entities. Within the list, the Contractor shall provide the schedule for the planned replacement or upgrade of operating systems or software and the estimate for time and materials for replacement per line item.

v. Acceptance and return to service

Part (1): The Contractor shall describe their approach for verification of completed maintenance and equipment return to service, providing associated rationale.

Part (2): The Contractor shall provide a list of existing, modified or new processes, procedures and documents that will be used for maintenance verification and equipment return to service.

vi. Schedule

Part (1): The Contractor shall describe their approach for an annual schedule of mockup and system maintenance, providing associated rationale. The approach shall describe the process for ensuring that scheduled mockup maintenance tasks will not interfere with on- going operations, or with the long range operational schedule. If a conflict is identified, and the maintenance is deemed to be critical, then the plan shall describe the process for communicating that conflict to the users and for resolving any issues.

Part (2): The Contractor shall provide a procedure for scheduling mockup and system maintenance.

1. DRD Title: Reports Required for Logistics

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: 01/20/23

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: These reports are required to determine the effectiveness of the Property Management System and as indicators of the volume of logistics activity.

11. Distribution: All DRDs shall be submitted via the Flight Operations Directorate (FOD) Contract Management System (FCMS) link below:

https://fod1.sp.jsc.nasa.gov/FOD/FCMS/NOC2/SitePages/Home.aspx

Initial Submission: See below

Submission Frequency: See below

Format:

· Forms for data input for the NASA Form 1324 (B.1) and 1489 (B.2) are available through JB3/Contract Property Group section of the JB3 web page under “JSC Data Requirement Descriptions (DRDs)”. http://centerops.jsc.nasa.gov/jb/jb3/

· Other forms shall be completed as specified above or as specified by the Government Property Administrator (PA).

Interrelationship:

· SOW 1.17.1

Applicable Documents: N/A

Scope: The reports at 1, 2, and 3 below are required when Contractor on-site storage of Government property in one location at JSC (JSC campus, Ellington Field, Sonny Carter Test Facility, or White Sands Test Facility) has a total dollar value greater than or equal to $75,000 and is not reported in NASA or the Contractor’s property systems. The reports at 4 and 5 are required in accordance with the directions below.

Contents:

1. NASA Form 1324, Semiannual Report of Personnel Property Management Operations (also called the Semi-annual Report of Personal Property Operations, Data for Semiannual Report of Contractor Supply Operations, or Data Sheet 1324):

This semi-annual report defines the following line item data elements as of March 15 and September 15 of each year:

a. Material Inventory Status

b. Material Acquisition Activity

c. Material Receiving Activity

d. Logistics Personnel Resources Report

Reference: NPR 4100, NASA Materials Inventory Management Manual Due Dates: March 25 and September 25

2. NASA Form 1489, Semiannual Analysis of Inventory Report (also called the Analysis of Physical Inventory Report, Data for Semiannual Report of…