NOC DRDs.pdf

ATTACHMENT J-10

DATA REQUIREMENTS SHEETS

DRD-NOC-01 (Page 1 of 2)

DRD-NOC-02 (Page 1 of 1)

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Configuration Management Plan 6/27/16 DRD-NOC-02 80JSC017C0001

4. Use: 5. DRD Category:

To define and describe the Contractor’s configuration management processes for hardware, software, and documentation.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

a. NPR 7120.5D, NASA Space Flight Program and Project Management

Requirements

b. NPR 7123.1A, NASA Systems Engineering Processes and Requirements

c. ISO 10007, Quality Management Systems – Guidelines for Configuration

Management

d. JSC-63756, Flight Operations Directorate Software Management Plan

SOW 1.10, 1.16, 1.16.4

8. Preparation Information:

a. Data Type: 1

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

c. Content: 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 configuration management 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 Configuration Management. Include any variations that occur during the different lifecycle phases.

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

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.

d. Format: Contractor discretion.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial: Contract award + 15 days.

ii. Final: Contract award + 25 days.

iii. Approval: Contract award + 55 days

v. Frequency: As required.

g. Maintenance: Update as required due to configuration management process or procedure changes.

Revisions shall be incorporated by a complete reissue of the document..

DRD-NOC-03 (Page 1 of 1)

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Continuous Improvement and Innovation Plan 6/27/16 DRD-NOC-03 80JSC017C0001

4. Use: 5. DRD Category:

To provide a comprehensive plan for improving contract performance with the goals of working more safely, enhancing quality, ensuring user satisfaction, and reducing cost.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

SOW 1.0

8. Preparation Information:

a. Data Type: 1

b. Scope: The Continuous Improvement and Innovation 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

c. Content: Describe the comprehensive approach to identifying candidates, vetting candidates, obtaining approval for the candidate and implementing the resulting improvement. Describe how the Contractor monitors continuous improvements to ensure no adverse impacts to contract performance. Describe how the contractor captures and reports innovative proposals.

For each improvement and innovation listed, the Contractor shall, as a minimum, describe technical approach, risk reduction, schedule, investment cost by fiscal year for each WBS element (for each labor category and non-labor), and proposed savings for each WBS element. There shall be enough detail for the Government to adequately assess the practicality and payback for each suggested improvement.

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.

d. Format: Contractor’s electronic format is acceptable.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial: Due with proposal.

ii. Final: Contract start + 30 days.

iii. Approval: Contract start + 120 days.

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

g. Maintenance: Revisions shall be incorporated by a complete reissue of the document.

DRD-NOC-04 (Page 2 of 3)

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 comprehensive checklist of all constraints and policies the Customer must meet in order to operate in the NBL.

iii. Provide a comprehensive 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 screen/vet 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 attract more external customers.

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.

iii. Provide your definition of a “completed” or “booked” External Customer agreement Discuss your method of calculating the totals in Table 1, including when you would consider that an External Customer event should be included.

3. Recruiting:

i. Identifying Potential Customers: Describe plans for identifying potential customers, both initially and long-term.

ii. Identify and provide preliminary estimates of the types of customers they expect to recruit, along with the anticipated usage levels/timeframes and external revenue by fiscal year.

4. Marketing the NBL:

i. Describe plans for marketing the NBL to potential customers, and the estimated costs.

5. 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).

6. Implementation

DRD-NOC-04 (Page 3 of 3)

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.

7. Reports and Statuses:

The Contractor shall provide informal statuses on on-going external customer activities at regularly scheduled External Customer Office Tag-Ups.

The Contractor shall provide formal status of external customer activities at regularly scheduled TCSR and QMRs.

Examples of status and report contents includes:

Contacts made and potential customers Anticipated work and schedules Level of support required or anticipated Duration of activity Facility equipment and infrastructure required Progress towards targets Adherence to metrics

8. Other relevant data.

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

Table 1 cost savings goals provide by the Contractor will be used as the minimum requirement and standard of excellence.

b. Other relevant data identified by the Contractor

d. Format: Contractor’s electronic format is acceptable for reports. Utilize the format provided herein for the plan itself.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial: Due with proposal.

ii. Final: Contract start + 40 days.

iii. Approval: Contract start + 135 days.

iv. Frequency: Update after approval of plan + 1 year; afterward as required.

DRD-NOC-05 (Page 1 of 2)

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Risk Managament Plan 6/27/16 DRD-NOC-

80JSC017C0001

4. Use: 5. DRD Category:

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

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

NPR 7120.5D, NASA Space Flight Program and Project Management Requirements NPR 8000.4, Risk Management Procedural Requirements SOW 1.14

8. Preparation Information:

a. Data Type: 1

b. 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.

c. Content: 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 –This is the means by which the output of the processes is documented and communicated to all team members. It is present in all of 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

DRD-NOC-05 (Page 2 of 2)

(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.

d. Format: Contractor’s electronic format is acceptable.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial: Contract start + 15 days.

ii. Final: Contract start + 45 days.

iii. Approval: Contract start + 60 days.

iv. Frequency: As required.

DRD-NOC-06 (Page 1 of 1)

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Fiscal Year (FY) Operating Plan and Planning, Programming, Budgeting, and Execution (PPBE)

6/28/16 DRD-NOC-06 80JSC017C0001

4. Use: 5. DRD Category:

The Contractor shall provide a separate annual FY Operating Plan and PPBE addressing all of the services under this contract.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

NPR 7120.5D, NASA Space Flight Program and Project Management Requirements

SOW 1.1, 1.18

8. Preparation Information:

a. Data Type: Op Plan – 1,

b. Scope: The FY Operating Plan will include a detailed analysis of the content and cost for the future Government Fiscal Year(s). The Plan will contain a multi-year forecast as specified by requesting letter.

c. Content: The FY Operating Plan shall include estimates of the resources required to perform the specified services of the contract. Estimates shall be provided by CWBS and shall include labor in WYE and $, material in $, and total contract total price in $. WYE, labor hour, and $ estimates shall also be provided by source of funding, such as ISS, MPCV, etc. A plan summary shall be provided which compares the total resources estimated by funding source to specified funding marks, and to the negotiated contract value.

The FY Operating Plan shall include estimates by month. Technical work content to be achieved within the plan shall be described by list of tasks to be performed under Core Projects. The Contractor shall provide and maintain a master integrated facility schedule which identifies all projects and internal and external project dependencies.

d. Format: Electronic copy and hardcopy, as specified by NASA. Electronic copy shall be provided in Microsoft Excel unless otherwise agreed-to with NASA.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial: FY Op Plan: Contract start + 30 days

ii. Final: FY Op Plan: Contract start + 50 days

iii. Approval: FY Op Plan: Contract start + 75 days;

iv. Frequency: FY Op Plan: 60 days prior to the end of FY

DRD-NOC-07 (Page 1 of 1)

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Small Business Subcontracting Plan and Reports

10/24/16 DRD-NOC-

80JSC017C0001

4. Use: 5. DRD Category:

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

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

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

SOW 1.3

Clause H.6 Attachment J-01

8. Preparation Information:

a. Data Type: Plan – 1, Report – 2

b. 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.

c. Content: 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 8(a), Women-owned, HUBZoned, Veteran owned, and Service disabled veteran owned companies and HBCU/MIs.

d. Format: Contractor format is acceptable for the plan; reporting shall be in compliance with

NFS 1852.219-75.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Subcontracting Plan:

1. Initial – Due with proposal.

2. Approval – Prior to contract award.

3. Frequency – Subcontracting Plan to be updated in accordance with FAR 19.702.

ii. Reports:

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

2. In lieu of submitting a paper copy of the SF 294 and SF 295 Subcontracting Report for

Individual Contracts. The Contractor shall submit semi-annually and at contract completion to the NASA/JSC Contracting Officer electronically version of this data.

3. Contractors are required to submit subcontracting data in the Electronic Subcontracting Reporting System (eSRS) which has replaced the paper Standard Form 294 and SF 295 Summary Subcontracting Reports.

4. 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.

DRD-NOC-08 (Page 1 of 1)

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Phase-In Plan 7/20/16 DRD-NOC-08 80JSC017C0001

4. Use: 5. DRD Category:

To describe the Contractor's planned Phase-In approach. Technical

Administrative

SR&QA

6. References: 7. Interrelationships:

8. Preparation Information:

a. Data Type: 1

b. Scope: The NOC Phase-In Plan provides plans for the transfer of all anticipated on-going development and operations activities along with supporting logic and rationale.

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

i. Schedule with key 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

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, DO, and all technical and administrative data (e.g., metrics data from previous years), Data Packages (DRD-NOC-31) and NBL Databases (DRD-NOC- 26)

xiii. Mission assurance considerations,

xiv. Security considerations,

xv. Risk mitigation strategy,

xvi. Configuration management considerations.

d. Format: Contractor discretion, unless otherwise agreed upon between NASA and the Contractor.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial: Due with proposal.

ii. Final: Contract award + 5 calendar days.

iii. Approval: Contract award + 10 calendar days.

DRD-NOC-09 (Page 1 of 3)

8. Preparation Information (Include complete instructions for document preparation) 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, within 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

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Government Property Management Plan (PMP) 12/06/2016 DRD-NOC-09 80JSC017C0001

4. Use: 5. DRD Category:

To describe the method of administering and controlling Government personal property and submitting proposed property manager qualifications.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

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

DRD-NOC-09 (Page 2 of 3)

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)

Format The Contractor’s format is acceptable.

Distribution of the Property Management Plan

1. Initial - The Offeror(s)/Contractors will be notified by the Contracting Officer when the PMP submittal is due.

2. Final - Due 30 days after contract award.

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

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.

DRD-NOC-10 (Page 1 of 1)

8. Preparation Information:

a. Data Type: 1

b. Scope: The NBL will utilize the NASA change control process, described in CX-WI-006, for NOC.

The Change Control Process Plan (CCPP) shall describe the Contractor’s internal change control processes and how those processes interface with CX-WI-006.

c. Content: 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:

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

ii 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.

iii Providing quality assurance support and preventing organizational conflicts of interest (OCI) throughout the change development and implementation process iv Interrelationships between the change control process and other NOC processes (e.g., discrepancy reporting/management) v Processes and methodologies for cost and schedule estimating, including how the Contractor will ensure accuracy in these critical areas.

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

vii Interfacing Contractor change processes with NASA’s existing change control process (CX-

WI-006)

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

ix Describe all differences between processes and methods for IDIQ DOs versus core change requests x Deliverables; e.g., change control database and metric reports.

d. Format: Hardcopy and electronic format; JSC web domain accessible.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial: Due with proposal.

ii. Final: Contract award + 15 days.

iii. Approval: Contract award + 45 days.

iv. Frequency: As required.

g. Maintenance: Revisions shall be incorporated by a complete reissue of the document.

DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Change Control Process and Plan 06/28/16 DRD-NOC-10 80JSC017C0001

4. Use: 5. DRD Category:

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.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

a. CX-WI-006, CX Change Request Process

b. JSC-63756, Flight Operations Directorate Software Management Plan SOW 1.16.2

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Maintenance Plan 11/01/16 DRD-NOC-

80JSC017C0001

4. Use: 5. DRD Category:

This plan will document the Contractor’s approach to maintenance of NBL mockups and systems.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

SOW 1.18, 2.2

8. Preparation Information:

a. Data Type: 1

b. 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.

c. Content:

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.

d. Format: Contractor discretion, unless otherwise agreed upon between NASA and the Contractor.

e. Distribution: Per Contracting Officer’s Letter.

f. Submission:

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

ii. Final: Contract award + 35 calendar days

iii. Approval: Contract award + 55 calendar days

iv. Frequency: As required

DRD-NOC-12 (Page 1 of 2)

1. DRD Title 2. Date of current

3. DRL Line Item No.

RFP/Contract No.

Reports Required for Logistics 11/23/15 DRD-NOC-12 80JSC017C0001

4. Use: 5. DRD Category:

These reports are required to determine the effectiveness of the Property Management System and as indicators of the volume of logistics activity.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

SOW 1.17.1

8. Preparation Information

A. SCOPE:

The reports at B.1, B.2, and B.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, 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 B.4 and B.5 are required in accordance with the directions below.

B. CONTENT:

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 Inventory Activity

c. Material Acquisition Activity

d. Material Receiving Activity

e. 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 Analysis of Fixed Inventory Assets, or Data Sheet 1489):

a. This semi-annual report defines the following monetary data elements as of March 15 and September 15 of each year.

b. Starting Price: Price of Receipts, Price of Issues, Ending Price

Note: This will be reported by each Object Class Code stocked in the storeroom.

Separate reports are required for Stores, Programs and Standby stock (see the JSC Stocks Stock Catalog prefaces for a detailed explanation of these codes).

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

3. NASA Form 1619, Physical Inventory of Materials Annual Report:

This annual report identifies the sampling inventory actions completed by the Contractor. This report contains the following data by Object Class Code (see the JSC Stores Stock Catalog preface for a detailed explanation of these codes.)

a. Line items and dollar value of items inventoried.

b. Number of line items with variance.

DRD-NOC-12 (Page 2 of 2)

c. Dollar value of discrepant items, including overage, shortage, and gross discrepancies.

d. Identify whether inventory items are stores, program, or standby stock, and also identify the staff hours and dollar value expended in accomplishing and reconciling the inventory.

e. A brief explanation of cause, of discrepancies, and actions to minimize the chance for recurrence.

Due Date: September 25 Note: Contractor-Acquired Material (CAM) and Government Furnished Material are to be inventoried and reported together for the purposes of this report.

4. Quarterly Report of Contractor-Acquired Material (CAM) and Low Dollar Equipment:

This report will consist of a transfer document (DD Form 1149) that identifies CAM and non-taggable equipment under $100,000 unit cost purchased and received by the Contractor for on-site use that bypass JSC Central Receiving. This Quarterly Report consists of property delivered to Center accountability for the following:

a. Items bought for and delivered for direct consumption on site, bypassing on-site storerooms.

b. Items delivered to on-site storeroom(s) not for immediate consumption/use.

Quarterly Reports are DD1149’s submitted by the Contractor to the Government Property Administrator on a quarterly basis to obtain JSC approval for shipments made during the previous quarter that bypassed JSC Central Receiving.

The Quarterly Report DD1149 will consist of the following:

a. One summary DD1149 annotated with the total number of line items and total value of the items delivered to JSC during the previous three months. That DD1149 shall have the necessary approval signature blocks to affect transfer of accountability to JSC.

b. A list of the Contractor individual DD1149 voucher numbers from the previous quarter used to deliver the property to JSC.

c. Copies of the individual DD1149s on the list reflecting a JSC recipient signature and signature date.

The Quarterly Report summary DD1149 will transfer accountability of these assets to JSC and may also be accompanied by requisitions, issue documents, engineering work orders (if flight material destined for a bond room), or any other similar form approved for use by the Government Property Administrator.

Due Date: 15 working days after the end of the Quarter/Fiscal Year The Quarterly Reporting process shall be added to the Contractor’s property control procedures and/or plan and approved by the cognizant Government Property Administrator.

5. Annual Report of Exchange/Sale:

a. As defined by the Government Property Administrator (PA).

Due Date: 15 days after the end of each Government Fiscal Year if required by the Government

PA.

C. FORMAT:

1. 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/

2. Other forms shall be completed as specified above or as specified by the Government PA.

D. MAINTENANCE:

Changes or corrections to the reports above or this DRD shall be coordinated with the cognizant

Government Property Administrator.

E. DISTRIBUTION:

All reports shall be provided to the cognizant Government Property Administrator.

F. APPLICABLE DOCUMENTS:

N/A

DRD-NOC-13 (Page 1 of 1)

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Quality Plan and Reports 09/02/16 DRD-NOC-

80JSC017C0001

4. Use: 5. DRD Category:

The Quality Plan is used to document the specific details of the Contractor’s Quality Management System (QMS) related to this contact.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

a. ANSI/ISO/ASQC

SOW 1.13

8. Preparation Information:

a. Data Type: 2

b. Scope: A contract specific Quality Plan shall be prepared which identifies activities performed both on-site and off-site of JSC to ensure the quality of products and services.

c. Content: The quality plan shall address each element of the ANSI/ISO/ASQC standard demonstrating the Contractors understanding, implementation, methods, procedures, and controls required to fulfill the contract requirements.

d. Format: Quality Plan format shall match the elements of the ANSI/ISO/ASQC standard.

e. Distribution: JF5/JSC Property Administrator.

f. Submission: Per Contracting Officer’s letter.

i. Initial: Contract start + 30 days.

ii. Final: Contract start + 60 days.

iii. Approval: Contract start + 90 days.

iv. Frequency: Annually.

g. Maintenance: Revisions shall be incorporated by change page or complete reissue.

DRD-NOC-14 (Page 1 of 11)

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Safety and Health Plan 07/16 (replaces 07/14 version)

DRD-NOC-14 80JSC017C0001

4. Use: 5. DRD Category:

Establishes Safety and Health Plan for Contractors providing support to JSC organizations The Office of Primary Responsibility for this DRD is the JSC Safety and Test Operations Division. Any modifications to this DRD require approval from the Chief, Safety and Test Operations Division.

Technical Administrative

SR&QA

6. References: 7. Interrelationships:

OSHA CSP 03-01-003, Voluntary Protection Program (VPP): Policies and Procedures Manual JPR 1700.1, JSC Safety and Health Handbook JSC 17773, Preparing Hazard Analysis for JSC Ground Operations JPR 1040.4, JSC Emergency Preparedness Plan NPR 8621, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping JPR 2310.1, JSC Organizational Learning Program

SOW 1.11

8. Preparation Information:

Frequency of Submission. Initial submission with the proposal. Upon NASA approval, the Contractor’s Safety and Health Plan become a Contractual Requirement.

Distribution: Send copies to each of the following:

Contracting Officer (1 electronic copy)

Contracting Officer’s Representative (1 electronic copy)

NS/Safety and Test Operations Division (1 electronic copy)

JSC Occupational Health Office (1 electronic copy)

JSC Emergency Preparedness Office (1 electronic copy)

Revisions to the Plan: Review the plan annually or as directed by the CO. Update the plan to meet the latest OSHA, JSC, and VPP requirements. Provide a copy of the updated plan with the changes highlighted to the distribution list above at the start of each Contract year. If no changes are required after the annual review, notify the individuals in the distribution list in writing to that affect.

Other Deliverables: The plan must include instructions for submitting the deliverables in Table 1 below to the Government and represent contractual commitments by the Contractor to provide this information.

Include copies to the Contracting Officer and Contracting Officer’s Representative.

DRD-NOC-14 (Page 2 of 11)

Deliverable Frequency DRD ¶ Comments Identity of key safety and health personnel:

Company Physician/Occupational Injury/illness case manager Designated Safety Official Safety Representative Building Fire Wardens (Roster)

Within 15 days of contract start and updated with changes

1.5 Include in plan or

attachment to plan

Safety and Health Self Evaluation Report

Yearly by Jan. 30 1.8 Send to Safety and Test Operations Division

Roster of Terminated Employees Yearly, 30 days after the end of the contract year

1.9.1 Send to the Occupational

Health Branch

Material Safety Data Sheets (MSDS)/Safety Data Sheets (SDS)

When you introduce a new hazardous material

1.9.2 Send to the Occupational

Health Branch See JPR 1700.1, Chapters

9.1 & 9.2

Hazardous Materials Inventory Yearly or when quantities or locations change significantly. Some products require quarterly updates

1.9.3 Send to the Occupational

Health Branch See JPR 1700.1, Chapter 9.2

Data on workplace industrial hygiene exposures

15 days after receiving results

2.1.1 Send to the Occupational

Health Branch Only required if corporate industrial hygiene resource are used.

Inventory of Hazardous Operations 30 days after contract start and updated as necessary

2.3 Send to Safety and Test

Operations Division

Inspection results entered in Building Inspection Tracking System (BITS)

10 working days after completing inspection

2.4

On-site close calls forwarded to JSC close call tracking system

Within 3 working days of receipt

2.6 Send to Safety and Test

Operations Division Required only for Contractor close call systems

DRD-NOC-14 (Page 3 of 11)

Deliverable Frequency DRD ¶ Comments Mishap reporting Immediate and follow-up as required in JPR 1700.1

2.7.1 See Chapter 2.6 of JPR

1700.1 Lessons Learned Report Enter data into the JSC

LLDB or NASA LLIS:

Within 30 days of a triggering event;

Within 30 days of a program milestone, mishap investigation, or hazard or other engineering analysis / evaluation is completed;

or 30 days before end of contract evaluation period or 45 days before end of contract, whichever is applicable.

2.7.1.7 Database entry with 1

electronic copy to the Contracting Officer’s Representative (COR)

JSC Form 288, “Statistical Information - Contractor Safety and Health Program”

Monthly by the 10th of the month

2.7.2. a Send to JSC-Safety- Report-Submittals <JSC- Safety-Report- Submittals@mail.nasa.gov

OSHA logs Yearly by Feb 15 and within 30 days of contract end

2.7.2.b Send to Safety and Test Operations Division OSHA 300 & 300A with names removed. Equivalent forms from Contractor database are acceptable.

Hazards recorded in JSC Hazard Abatement Tracking System (HATS)

Within 5 working days of discovery

3.1, 3.11

Applies to hazards not corrected within 30 days

Interim and Final Abatement Plans Within 5 working days of discovery

3.11.2 Updates for hazards

entered into HATS

List of hazardous operations and processes

Submit with the plan and update as needed

3.3

Table 1, Safety and Health Deliverables

Format:

1. Cover page - to include as a minimum, blocks for the signatures of Contractor's project manager and designated safety official; NASA COR; JSC Safety and Test Operations Division: JSC Occupational Health Branch: and the NASA Contracting Officer. Other signatures may be required at the discretion of the Government. Once approved by NASA, signatures will be collected and the plan placed on the contract.

2. Table of Contents. See content below.

3. Body of plan - as required. Contractor’s format is acceptable but should be aligned with the elements of the content below.

4. The Contractor is part of a larger program – the NASA safety program – which has other contracted employees, civil servants, and other third parties that must be protected from any hazard in the workplace wherever they arise. This includes the following:

a. Hazards associated with work done on contractual tasks.

b. Hazards that arise from non-contractual operations in the vicinity of Contractor’s workers.

DRD-NOC-14 (Page 4 of 11)

c. Hazards that arise from contractual operations which may affect the safety and health of individuals and assets outside this contract.

5. The plan will clearly identify those resources to be provided by the Contractor and proposed resources to be provided by the Government. The Contractor will make this review and supporting rationale available to the Government as part of this plan. It can be documented as a checklist or outline, inserted directly in the body of the plan, or in any format developed by the Contractor that clearly conveys the results of this review including the basis for any underlying assumptions. For further information, see the LIST OF INSTALLATION PROVIDED FACILITIES AND SERVICES provided in this RFP.

6. The plan must cover the prime Contractor and all subcontractors.

Details: Address the following items in your plan:

MANAGEMENT LEADERSHIP AND EMPLOYEE PARTICIPATION

Management and employees work together as a team to provide a safe and healthful workplace.

Management and employee synergies often must work together across contractual lines.

1.1 Policy: Provide the Contractor’s safety and health compliance policy statement with the plan.

Compare the Contractor’s policy statement with those of NASA and OSHA and discuss any differences.

1.2 Goals and Objectives. Describe your approach to the following:

1.2.1 Specific annual safety and health goals and objectives to be met. Include innovative employee input systems and management approaches that produce a measurable rate of improvement in employee participation. These goals and objectives may or may not be quantifiable. Explain how you will evaluate your accomplishment of these goals and objectives.

1.2.2 Methods to be used, if any, to improve on the Days Away Case Rate (DACR), the Total Recordable Injury Rate (TRIR), and the total Days Away plus Restricted Duty plus Job Transfer (DART).

1.3 Management Leadership. Describe how management will demonstrate its commitment to safety and health compliance through visible management activities and fulfill its line management responsibilities for safety and health. Describe specific processes and techniques for implementation in all Contract and subcontract activities and products. Include a statement from the project manager or designated safety official indicating that the plan will be implemented as approved and that the project manager will take personal responsibility for its implementation.

1.4 Employee Involvement. Describe procedures to promote, implement, and sustain employee (non-supervisory) involvement in safety and health compliance program development, implementation and decision-making from all areas of the contract.

1.5 Assignment of Responsibility. Describe line and staff responsibilities for safety and health program implementation. Identify any other personnel or organizations that provide safety services or exercises any form of control or assurance in these areas. As a minimum, the plan will identify the following:

1.5.1 Safety Representative - identify by title, the individual who will be responsive to Center-wide safety, health and fire protection concerns and goals, and who will participate in various joint meetings, forums, and other activities related to the JSC Safety and Health program.

1.5.2 Company Physician/Occupational Injury/illness case manager - identify a point of contact who is responsible for the transfer or receipt of company medical data and who will be the primary contact for the company in the event any employee suffers a work related injury or illness by name, address, and telephone number to the JSC Clinic, mail code SD32. This will facilitate communication of medical data to Contractor management. Promptly notify the JSC Clinic of any changes that occur in the point of contact.

1.5.3 Building Fire Wardens - provide a roster of fire wardens at the start of each Contract year (their names, telephone numbers and pagers, and mail codes). Contractor fire wardens facilitate the JSC fire safety program, including coordination of related issues with NASA facility managers and emergency planning and response officials and their representatives. Fire wardens will be trained per JPR 1700.1.

Update the Roster by letter to the JSC Safety and Test Operations Division, mail code NS2, with copies to

DRD-NOC-14 (Page 5 of 11) the Contracting Officer and the COR. Provide the initial letter to the Government not later than 15 days after contract start.

1.5.4 Designated Safety and Health Official - identify by title the official(s) responsible for implementation of this plan and all formal contacts with regulatory agencies and with NASA.

1.6 Provision of Authority. Describe your approach to maintain consistency of this plan throughout the life of the contract with applicable NASA and JSC requirements and contractual direction as well as applicable Federal, State, and Local regulations.

1.7 Accountability. Describe procedures for ensuring that management and employees will be held accountable for implementing their tasks in a safe, healthful, and environmentally compliant manner.

1.8 Safety and Health Program Self Evaluation. Describe your approach to safety and health program evaluation.