MSOC Data Requirements Description Sheets (DRDs).pdf

ATTACHMENT J-17

DATA REQUIREMENTS DESCRIPTION SHEETS

1. DRD Title

MSOC Work Breakdown Structure (WBS) and Dictionary

2. Date of current version

04/06/17

3. DRL line item no.

DRD-MSOC-0001

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

To organize the tasks to be accomplished in this contract in a service-oriented structure. The MSOC WBS 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.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional)

Attachment J-1, Glossary

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

SOW 2.1

Attachment J-21

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: 1

b. Scope: The WBS shall encompass all the services required to achieve all the requirements of this contract. The WBS 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.

c. Content: The WBS shall graphically depict the WBS tree. The dictionary shall contain a concise description of contract tasks to be performed and products to be delivered, subdivided by WBS element. A WBS element may represent an identifiable product, a set of data, a service, a task, or a budget function. The structure shall be at the RFP WBS level (See Attachment J-21 for mapping to the SOW) with additional levels as required by the Contractor. Lower levels of detail, which the Contractor uses for its own management purposes to validate information reported to NASA, shall be compatible with NASA requirements and be accessible by NASA. The relationship between theWBS and the Contractor's internal organizations and processes shall also be provided.

The WBS shall map to the Flight Operations Directorate (FOD) WBS.

d. Format: The WBS tree is to be in organization chart format and the associated WBS narrative (WBS dictionary) in text form, arranged as depicted by the WBS tree. Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be the Contractor’s format.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial – Due with proposal

ii. Final – Due at contract start

iii. Approval – Contract start + 90 calendar days.

iv. Frequency – As required.

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

DRD-MSOC-0001 (Page 1 of 1)

DRD-MSOC-0002 (Page 1 of 2)

Management Plan

2. Date of current version

06/29/16

3. DRL line item no.

DRD-MSOC-0002

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

The Management Plan will provide a comprehensive plan that integrates all aspects of the WBS to successfully accomplish the contract requirements.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

SOW 2.0, 2.2.1

DRD-MSOC-0001

DRD-MSOC-0017

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: 1

b. Scope: The Management Plan shall describe the basis for the Contractor’s management approach, organization, and systems for accomplishing and managing all services and functions described in the WBS. The plan shall be comprehensive in nature and integrate all management systems of the prime, any subcontractors, any significant vendors, including Small and Small Disadvantaged businesses and any teaming or partnering arrangements, and associate contractor agreements (ACAs).

c. Content: The Contractor shall address the following elements as a minimum:

1) Schedule

a. Describe adherence to established and fluctuating schedules.

b. Describe the tools utilized to evaluate and track schedules.

2) Budget

a. Describe how individual program/activity/project budgets will be tracked and maintained.

b. Describe tools utilized to maintain the budget.

c. Describe the process for indirect cost management.

3) Organizational Structure

a. Provide charts and descriptions of the organizational structure, showing connections with any corporate organizations and subcontractors. Describe each organization and its function.

This chart should correspond with the MSOC Work Breakdown Structure (WBS) and Dictionary (DRD-MSOC-0001).

b. Describe the internal and external organizational structure to explain roles and responsibilities, and lines of communication to NASA, subcontractors, parent corporations and other organizations.

c. Describe the communication channels, lines of authority (including the line of succession if the Program Manager is unavailable), reporting relationships and responsibilities of all organizational elements. Include in this discussion any subcontractors or team members to illustrate their relationship within the structure or between the organizational elements and any other subcontractors or team members.

d. Describe in detail the degree of local autonomy, any relationship to a parent organization, and any decisions and approvals that will be made outside the local organization.

DRD-MSOC-0002 (Page 2 of 2)

e. Describe the reporting responsibilities of the Program Manager to corporate management and the relationship between the Program Manager and the prime’s corporate management, as well as the management of any subcontractors or team members.

f. Describe plans and approaches that will be used for subcontractor administration.

g. Describe any teaming relationships and prime contractor to subcontractor arrangements, a description of the nature and extent of work to be performed, roles and responsibilities, addressing how management and control policies will be implemented, and how work will be scheduled, controlled, reported, and reviewed.

h. Describe methods of communication with other contractors as listed in Attachment H-10 Associate Contractor Agreement for MSOC Activities.

4) Approach to Work

a. Describe the approach for managing the baseline work as well as IDIQ delivery orders and LOE task orders. Provide specific details of how each work element in the WBS will be integrated across the contract.

b. Describe with rationale the technical metrics to be collected during the performance of this contract.

c. Describe the approach to support NASA and affiliated organizations regarding technical and schedule information.

d. Describe the strategy for cross-training and flex utilization ofpersonnel.

5) Management

a. Describe the efficient and aggressively cost effective management approach withinthe organizational structure.

b. Describe the distribution and roles of management to ensure effective accomplishment of the MSOC effort.

c. Describe the approach to maintain the appropriate percentages of work distributed tosmall businesses and the various small disadvantaged businesses throughout the life of the contract.

d. Format: Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be the Contractor’s format.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial – Due with proposal.

ii. Final – Receipt of Government updates + 30 calendar days.

iii. Approval – Final submission + 90calendar days.

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

DRD-MSOC-3 (Page 1 of 1)

Risk Management Plan

2. Date of current version

06/08/16

3. DRL line item no.

DRD-MSOC-0003

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

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

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional)

FOD Risk Management Plan CA-WI-18 Rev D

Latest version

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

SOW 2.11

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: 1

b. Scope: The risk management plan defines the Contractor’s method to accomplish proactive end-to-end risk analysis management and abatement, throughout the contract duration. Risk management includes risk: identification, analysis, handling, mitigation, tracking, controlling, and risk communication.

c. Content: Present a structured, integrated risk management and abatement implementation approach that correlates with the proposed integrated architecture evolution. The plan will address the risk sources, magnitude and mitigation, and actions directed toward its elimination or reduction to an acceptable level. The plan will take into account technical, programmatic, supportability, cost, and schedule concerns for the solution implementation, and it will take into consideration impacts due to external influences, e.g., major schedule delays, NASA funding cuts, and mission set adds/deletes.

The plan will specify how the risks are documented, communicated, and reported to the Contractor and NASA management.

d. Format: Electronic format of all submissions will be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation will be the Contractor’s format.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial – Contract Start + 15 calendar days.

ii. Final – Receipt of Government updates + 15 calendar days.

iii. Approval – Final submission + 15 calendar days.

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

DRD-MSOC-4 (Page 1 of 1)

Contract Configuration Management Plan

2. Date of current version

06/08/16

3. DRL line item no.

DRD-MSOC-0004

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

To describe the Contractor's method for accomplishing the configuration management of the contract.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

SOW 2.13.4

8. Preparation Information (Include complete instructions for document preparation)

a. Data type: 1

b. Scope: The plan will describe the Contractor’s management approach and planned implementation methods for accomplishing the Configuration Management (CM) of thecontract.

c. Content: The plan will describe the Contractor’s CM organization, policies, procedures, implementation approach, and control systems that are to be used to ensure proper contract CM activities.

d. Format: Electronic format of all submissions will be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation will be the Contractor’s format.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial – Contract award + 2 business days.

ii. Final – Contract start.

iii. Approval – Contract start + 30 calendar days.

DRD-MSOC-5 (Page 1 of 2)

Phase-In Plan

2. Date of current version

07/05/16

3. DRL line item no.

DRD-MSOC-0005

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

To describe the Contractor’s planned approach for MSOC phase-in.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

DRD-MSOC-0018

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: Type 1

b. Scope: A Phase-In Plan shall be prepared which describes the Contractor’s approach for the transition of responsibility from the Incumbent Contractor during the 61-day transition period. The Plan must address the Contractor’s approach to assume responsibilities by contract start.

c. Content: The Contractor is expected to meet full performance requirements from the start date of the base contract period. Prior to performance of services ordered by the Government under this contract, the Contractor shall accomplish all tasks required to begin work ordered under this contract.

The Offeror shall submit a Phase-in Plan which shall detail the proposed implementation processes and strategies for effecting a smooth transition. The plan shall contain, at a minimum, detailed rationale, schedule, and specific approach to successfully complete each item described below.

Address the following items:

(i) Describe in detail the plan for maintaining continuous and efficient operations. Describe how you will work with incumbent Contractors and NASA, including resources and interfaces expected from each to ensure an effective transition and continuousservice.

(ii) Provide a phase-in schedule to accomplish all proposed phase-in steps/milestones and the personnel responsible for those steps/milestones. Describe your approach for how you will implement the schedule. Describe your approach for informing NASA of milestone status, progress and issues, including a regular reporting schedule to NASA and proposed metrics to demonstrate contract transition progress

(iii) Provide details for initial staffing and training of personnel, including the incumbent personnel capture plan. This response shall include plans to provide personnel with the required critical skills and necessary certifications to meet the MSOC start up staffing requirements ensuring uninterrupted critical mission operations services with qualified/certified personnel.

(iv) Address the office space that is required for phase-in, beyond what is to be provided bythe

Government, if any.

(v) Describe approach for ensuring completion of badging requirements and personnel security clearances to ensure employees are cleared for access to JSC and its associated facilities, as required, prior to start of the contract.

(vi) Describe how an inventory will be performed with the Incumbent Contractor of all records/documents that will be transitioned. Records/Document transition shall be completed at contract start. The schedule shall include notification to the organizations 30 days prior to the initial start of an inventory. Individuals who will be performing inventories shall be identified.

DRD-MSOC-5 (Page 2 of 2)

(vii) Describe your approach to identifying requirements for Contractor applications or systems connectivity or integration with JSC. Describe your approach to identifyand describe the risks and mitigations associated with any requirements for Contractor application or system connectivity or integration with JSC.

(viii) Address property control transfer, including schedule and milestones for completing 100% inventory including but not limited to Government Furnished Property and Installation Accountable Government Property. The schedule shall include notification to the organizations 30 days prior to the initial start of any inventory. Individuals who will be performing inventories shall be identified. Property shall include:

1. Hardware/Software control transfer

2. Documentation control transfer (including any classifieddocumentation)

3. Facilities responsibility transfer

(ix) Identify the risks associated with your plan and ways to mitigate those risks.

(x) Describe your approach for ensuring incorporation of the following into any contractor or government provided management tools and processes to ensure business andconfiguration management capabilities are ready to implement on day one of contract start:

(a) Existing Technical Configuration Management items (e.g. AR’s, CR’s, IR’s, PR’s, SR’s, and Ops Note data)

(b) Existing Contract Management items (e.g. Delivery Orders, Task Orders,Metrics)

(xi) Describe your approach for developing the FY18 Technical Operating Plan (Tech Plan) per the requirements of DRD-MSOC-0018. The submittal of the actual FY18 Tech Plan will be per the timeline defined in DRD-MSOC-0018.

d. Format: Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be the Contractor’s format.

e. Distribution: The Contractor shall submit their proposed plan with the initial proposal. If updates are warranted, submit the Plan to the Contracting Officer and the Contracting Officer’s Representative per the format designated by the Contracting Officer.

f. Submission:

i. Initial: Due with proposal

ii. Final: Contract award + 5 calendar days

iii. Approval: Contract award + 10 calendar days

iv. Updates: As required. Submit revisions for Government approval after any major change in phase-in approach.

g. Maintenance: The Contractor mayrevise the Plan at any time or at the direction of the Contracting Officer. Revisions to the Plan are subject to Contracting Officer review. Changes shall be incorporated as required by change page or complete reissue.

DRD-MSOC-6 (Page 1 of 2)

Phase-Out Plan

2. Date of current version

06/08/16

3. DRL line item no.

DRD-MSOC-0006

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

To describe the Contractor’s planned approach for MSOC Phase-Out.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

SOW 2.0

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: Type 1

b. Scope: A Phase-Out Plan shall be prepared which describes the Incumbent Contractor’s approach for the transition of responsibility from the Incumbent Contractor to the Follow-On Contractor during the Follow-On Contractor’s Phase-In period. The Plan must address the Incumbent Contractor’s approach to transfer responsibilities by end of contract. Final Phase-Out Plan Government approval prior to Follow-On Contractor Phase-In period start.

c. Content: The Incumbent Contractor is expected to meet full SOW performance requirements while performing the Phase-Out activities until end of contract.

The Incumbent Contractor shall submit a Phase-Out Plan which shall detail the proposed implementation processes and strategies for effecting a smooth transition. The plan shall contain, at a minimum, detailed rationale, notional milestones, and specific approach to successfully complete each item described below.

Address the following items:

(i) Describe in detail the plan for maintaining continuous and efficient operations. Describe how the Incumbent Contractor will work with the Follow-On Contractor and NASA, including resources and interfaces expected for each to ensure an effective transition andcontinuous service.

(ii) Provide a Phase-Out steps/milestones and the personnel responsible for those steps/milestones. Describe the approach for informing NASA of milestone status, progress and issues, including a regular reporting schedule to NASA and proposed metrics to demonstrate contract transition progress.

(iii) Describe how the Incumbent Contractor will transition the support of provided Mission

Systems capabilities to the Follow-On Contractor by the end of the contract, as applicable.

(iv) Describe how the Incumbent Contractor will transition utilization of MSOC facilities to the Follow-On Contractor by the end of the contract, asapplicable.

(v) Describe how an inventory will be performed with the Follow-On Contractor of all records/documents that will be transitioned. Records/Document transition shall be completed before end of contract. The schedule shall include notification to the organizations 30 days prior to the initial start of an inventory. Individuals who will be performing inventories shall be identified.

DRD-MSOC-6 (Page 2 of 2)

(vi) Address property control transfer, including schedule and milestones for completing 100% inventory including but not limited to Government Furnished Property and Installation Accountable Government Property. The schedule shall include notification to the organizations 30 days prior to the initial start of any inventory. Individuals who will be performing inventories shall be identified. Property shallinclude:

1. Hardware/Software control transfer

2. Warranty/Service Agreement control transfer

3. Documentation control transfer (including any classifieddocumentation)

4. Mission Systems responsibility transfer

(vii) Identify the risks associated with your plan and ways to mitigate those risks.

(viii) Describe your approach for transition of the following to the Follow-On Contractor prior to end of contract:

1. Existing and In-Work Technical Configuration Management items (e.g. CR’s, IR’s, PR’s, Drawings and Ops Note data)

2. Existing Contract Management items (e.g., Metrics)

d. Format: Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be the Contractor’s format.

e. Distribution: The Contractor shall submit their proposed plan upon NASA request. The plan shall be distributed to the Contracting Officer and the Contracting Officer’s Representative per the format designated by the Contracting Officer.

i. Plan Initial – Due Contract End minus 6 Months

ii. Plan Final – Receipt of Government updates + 15 calendar days

iii. Plan Approval – Receipt of Final + 10 calendar days.

iv. Updates: As required. Submit revisions for Government approval after any major change in

Phase-Out approach.

g. Maintenance: The Contractor mayrevise the Plan at any time or at the direction of the Contracting Officer. Revisions to the Plan are subject to Contracting Officer review. Changes shall be incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTIONSHEETS

DRD-MSOC-7 (Page 1 of 4)

Technical Metrics Plan and Reports

2. Date of current version

04/06/2017

3. DRL line item no.

DRD-MSOC-0007

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

The Technical Metrics Plan shall define measures and measurement methodologies to assess the Contractor’s schedule and technical performance relative to key system and process attributes for each Mission System. The Technical Metrics Reports shall document the results of the planned technical measures using the established measurement methodologies over the applicable period of time. Technical Metrics and Reports shall be provided at NASA project integration and status meetings, and as requested by NASA.

5. DRD Category: (check one)

X Technical Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

SOW 2.3, 3.1.6, 3.1.7,

3.1.9, 3.2.1.9, 3.2.2.9, 3.2.3.9, 3.2.4.9, 3.2.5.9

DRD-MSOC-0012

DRD-MSOC-0042

DRD-MSOC-0043

a. NPR 7123.1, NASA Systems Engineering Processes and Requirements

b. NASA/SP-2007-6105, NASA Systems EngineeringHandbook

c. JSC-63756, Flight Operations Directorate (FOD) Software

Management Plan (SMP)

Latest versions

8. Preparation Information (Include complete instructions for document preparation)

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

b. Scope: The Technical Metrics Plan shall identify the systems and processes to be measured, describe the measures to be recorded, summarize the measurement methodologies, and explain the reports and measurement assessment rationale. This information shall collectively constitute the Contractor’s integrated measurement system for assessing and responding to schedule, and technical performance relative to key system and process attributes. The scope of measurement shall include all products, services, and processes specified in the Statement of Work (SOW) regardless of the performing organization, (e.g. prime, subcontractor). The Technical Metrics Reports shall provide the values of the measures specified in the Technical Metrics Plan relative to prescribed thresholds for response. Additionally, the Technical Metrics Reports shall summarize any trends, notable values, and variances in the measurementdata.

c. Content: The Technical Metrics Plan shalldescribe:

i. The contractor’s comprehensive approach to gathering all metrics data and utilizing it to assess and respond to safety, schedule and technical performance relative to key system, process and operational attributes. The scope of measurement shall include all products, services, and processes specified in the Statement of Work (SOW) regardless of the performing organization, (e.g. prime, subcontractor).

ii. All key technical metrics that the Contractor will use to manage safety, schedule and technical performance on the Contract, what each will be used to assess and a brief rationale for that choice. The planned measures shall also include the technical metrics defined in the Statement of Work (SOW) for assessment against the thresholds established uniquely for each Mission System.

iii. The contractor’s approach to accepting metrics data from the previous contract. For previous metrics data that is common to the current contract, describe how the data will be incorporated into a continuous set of metrics data (representing the old data and new data generated on the current contract). For previous metrics data that is not common to the current contract, describe

DRD-MSOC-0007 (Page 2 of 4) how the data will be preserved for future use and how it will be made accessible to the Government.

iv. In addition to the contractor-determined metrics data identified in response to the above descriptions, the contractor shall provide metrics data needed by the Government to perform the Government’s management, oversight and planning functions. Appendix A describes the Government’s metrics data requirements, frequency and desired reporting formats. Contractors are encouraged to propose alternate, innovative ways to generate the tables/formats. The data shall be provided in Microsoft Excel unless an alternate method/tool is agreed-to with the Government.

Technical Metrics Reports shall be provided per Mission System and shall include, but not be limited to, the data identified in Appendix A as well as the following:

i. Change Request (CR) status

ii. System/subsystem availability

iii. System/subsystem utilization

iv. System/subsystem performance

v. Problem Report (PR) and Incident Report (IR) status bysystem/subsystem,

vi. Operations Notes status by system/subsystem,

vii. Personnel Certification Status (for all positions requiring acertification)

viii. Process Integrity Metrics, (format and content defined by theGovernment)

ix. Status Reports, as defined by the Government.

d. Format: Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be the Contractor’s format.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Technical Metrics Plan:

1. Initial – Due at contract award + 2 business days.

2. Final – Due at contract start.

3. Approval – Due at contract start + 30 calendar days.

4. Frequency – As required, annually at a minimum.

ii. Technical Metrics Reports:

1. Initial – Due 10 calendar days following close of the first month after approval of the Plan.

2. Final – Due at Contract completion.

3. Approval – N/A.

4. Frequency – third Thursday of each month.

g. Maintenance:

i. Technical Metrics Plan – Revisions shall be incorporated bychange page or complete reissue

ii. Technical Metrics Report – N/A

DRD-MSOC-0007 (Page 3 of 4)

Appendix A

SVMF-unique metrics data for NASA’s use

Report 1: Summary utilization metrics – by events

A table and graphic that shall provide, at a minimum, a continuous view of event (training events and evaluations) data described below. The data shall be pulled from the Government provided training management system. This metric shall be provided monthly.

Cumulative Minimum

<Insert Data Month 1>> <Insert Data Month 2>> <Insert Data Month 3>> <cont>

Maximum

Maximum

Actuals

Actuals

SVMF Resource Utilization of Nominal

Report 2: Summary utilization metrics – Mockups

A table and graphic that shall provide, at a minimum, the mockup usage by hours. The data shall be pulled from the Government provided training management system. This metric shall be provided monthly.

SVMF Mockup Usage Month Total FUR Hours Crew Hours Non Crew Hours SU/TD Hours

Report 3: Summary utilization metrics -- SVMF Tours

A table and graphic that shall provide, at a minimum, the number of tours conducted in the SVMF. The data shall be pulled from the Government provided tour calendar and facility sign-in sheet. This metric shall be provided monthly.

Month

Total

Media

Other

PAO

Floor

Report 4: Test Readiness Reviews (TRRs) and Safety Reviews (SRs) Conducted

A table that shall provide a continuous view of these metrics from contract start through contract end to facilitate trend analysis. All data shall be specified in number of SRs or TRRs conducted, unless otherwise indicated. Data shall be provided quarterly.

Report 5: Customer Satisfaction

A table and graphic that shall present the data contained in the Government provided SVMF Training Evaluation Form NASA can use to monitor Customer Satisfaction. Include any ratings, scores and

DRD-MSOC-0007 (Page 4 of 4) complaints received. As a minimum, this table shall provide a view of these metrics each month from contract start through contract end to facilitate trend analysis. Format is at contractor discretion, unless otherwise requested by NASA.

Report 6: Deviations, Waivers and Exceptions A table (like the example below) that shall provide, at a minimum, the number of Deviations, Waivers, and Exceptions generated on a monthly basis.

Description Waiver

No.

Deviation

No.

Exception1 N o Date presented to

NASA

Approved/ Disapproved

& date

Comments

Totals Notes:

1 Exceptions” are defined as any agreed-to variance from an approved process or procedure that is not addressed as a formal waiver or deviation.

Report 7: Number of Maintenance Activities

A table (like the example below) that shall provide, at a minimum, the description and findings of all maintenance activities on a monthly basis.

Title & Description of the maintenance activity Date

Performed Findings, Comments

DRD-MSOC-0008 (Page 1 of 3)

Government Property Management Plan (PMP)

2. Date of current version

08/04/16

3. DRL line item no.

DRD-MSOC-0008

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

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

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional)

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

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

SOW 2.14.1

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: 1

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

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.

c. Content:

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, andaudits

(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

DRD-MSOC-0008 (Page 2 of 3)

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 theGovernment)

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 andthe 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 specifythe 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 trainingcourses.

(c) Specify the level of professional property management certification obtained bythe 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.

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

e. Distribution:

DRD-MSOC-0008 (Page 3 of 3)

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

ii. Final – Due 30 days after contract award.

iii. Approval –

iv. Frequency –

g. Maintenance: Changes to the PMP shall be incorporated by change pages or complete reissue after coordination with the GPA.

DRD-MSOC-9 (Page 1 of 1)

Small Business Subcontracting Plan and Reports

2. Date of current version

06/08/2016

3. DRL line item no.

DRD-MSOC-0009

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

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

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional)

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, Individual Subcontracting Reports

Latest version

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

SOW 2.2.1

8. Preparation Information (Include complete instructions for document preparation)

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: Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be the Contractor’s format;

reporting shall be in compliance with NFS 1852.219-75.

e. Distribution: Per Contracting Officer Letter.

f. Submission:

i. Subcontracting Plan:

1. Initial – Due with proposal.

2. Approval – By contract start.

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 NFS1852.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 an electronic 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.

http://www.esrs.gov/

DRD-MSOC-10 (Page 1 of 1)

Information Technology (IT) Capital Planning and Investment Control (CPIC)

2. Date of current version

07/05/16

3. DRL line item no.

DRD-MSOC-0010

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

To document the Contractor’s compliance with Federal and NASA IT CPIC Planning and Reporting regulations and requirements.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional)

a. Clinger-Cohen Act

b. Office of Management and Budget (OMB) Circular A-130

c. OMB Circular A-11

Latest versions

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

SOW 2.1.4, 3.1.1.1

8. Preparation Information (Include complete instructions for document preparation)

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

b. Scope: Information Technology (as defined in the Clinger-Cohen Act) is subject to certain scrutiny and reporting requirements as set forth in Legislative actions, Executive and Agency mandates, and directives. The Office of Management and Budget (OMB) Circular A-130 establishes the foundation for CPIC. OMB Circular A-11 establishes the guidelines and requirements for reporting to the Executive Branch. Any additional reporting requirements associated with the CPIC data collection and reporting process will be covered by this DRD.

c. Content: In conformation with CPIC process, the contractor shall participate in data collection and reporting efforts. The contractor shall furnish the data needed for NASA to comply with OMB Circular A-11 (This requirement is completed through the monthly 533 reportingdocument).

Annually, the Contractor shall submit its Fiscal Year (FY) spending plans for review, and approval prior, to the beginning of the FY. Format, reporting processes, and procedures will be provided annually, based on the JSC and Agency requirements.

Examples of documentation, formats, processes, procedures, and structures can be provided upon request. However, all formats, processes, procedures, and structures are subject to changes.

d. Format: Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be the Contractor’s format.

e. Distribution: Per Contracting Office’s letter.

f. Submission:

i. Plan Initial – Contract Start

ii. Plan Final – Receipt of Government updates + 15 calendar days

iii. Plan Approval – Contract Start + 30 calendar days.

iv. Plan Frequency – As required, by the referenceddocumentation.

v. Report Frequency – Annually, as directed by COR

DRD-MSOC-11 (Page 1 of 1)

Emergency Preparedness and Disaster Recovery Plan

2. Date of current version

04/06/17

3. DRL line item no.

DRD-MSOC-0011

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

To describe the Contractor's approach for emergency preparedness and disaster recovery for all facilities in this SOW.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional)

a. NPD 8710.1, Emergency ManagementProgram

b. JPR1040.4, JSC Emergency Preparedness Plan

c. NPR 2810.1, Security of Information Technology

d. Office of Management and Budget (OMB) Circular A-130

e. NPD 2810.1, NASA Information Security Policy

f. Homeland Security Presidential Directive/HSPD-12 Subject: Policy for a Common Identification Standard for Federal Employees and Contractors

Latest versions

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

SOW 2.6.1

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: 1

b. Scope: The Emergency Preparedness and Disaster Recovery Plan describe theContractor's approach for emergency preparedness and disaster recovery.

c. Content: Content shall include thefollowing:

i. A risk analysis of all facilities/systems,

ii. Identification of specific equipment/facilities that require backup or alternate sites,

iii. Identification of backup strategies,

iv. Emergency response plans,

v. Backup facility/alternate sites operating plans.

d. Format: Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be the Contractor’s format.

e. Distribution: Per Contracting Officer’s letter.

f. Submission:

i. Initial – Contract start + 15 calendar days.

ii. Final – Receipt of Government updates + 15 calendardays.

iii. Approval – Final submission + 60 calendar days.

iv. Frequency – Annually, no later than May 1st of each calendar year.

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

DRD-MSOC-12 (Page 1 of 3)

Status Reports and Reviews

2. Date of current version

10/22/19

3. DRL line item no.

DRD-MSOC-0012

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

To provide NASA insight into the status of the Mission Systems elements and to provide insight into the performance of the MSOC Contractor.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

SOW 2.1, 2.13.3, 3.1.9,

3.2.1.9, 3.2.2.9, 3.2.3.9, 3.2.4.9, and 3.2.6.9

DRD-MSOC-0007

a. JSC-63756, Flight Operations Directorate (FOD) Software Management Plan (SMP)

b. CD-UWI-0013, Mission Systems Division GovernancePlan

c. NASA-STD-8739.8, Software Assurance Standard, Section6.7, Software Assurance Status Reporting

Latest version

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: 2

b. Scope: This DRD establishes the reporting for the activity, performance, and utilization of the Mission Systems elements. This DRD will also identify the Contractor’s progress and accomplishments.

c. Content:

i. Status Reports and Reviews: Include overall technical, administrative progress, and status of significant activities relating to the accomplishments of the contractual objectives. Risks to the accomplishment of contractual objectives shall also be identified. These reports and reviews also include performance and utilization data of major systems. Health and safety incidents, mishaps, and close calls are included as well.

ii. Activity Reports: Include significant accomplishments, high level run reports for simulations, tests, problems encountered, quality assurance results, corrective actions, and significant facility problems or mishaps.

iii. Metrics Reports: Produced in accordance with DRD-MSOC-0007, Technical Metrics Planand Reports. Reports are of sufficient detail to permit understanding and evaluation of progress made. Supporting data in the form of charts, graphs, etc. shall be included, asappropriate.

iv. Program Manager Status Reviews (PMSRs): A monthly review to document accomplishments, changes in plans, problems being worked, and proposed solutions for projects and other work.

The discussion of plans, progress, and problems include variance analysis, reporting cause, impact, and corrective action. Technical issues are covered in terms of performance goals (metrics), exit criteria, schedule progress and/or cost impact. The review includes current status and year-end estimate and covers upcoming major events.

v. Surveillance Reports: Include a description of the surveillance methodology for internal and supplier surveillance, internal and supplier surveillance performed in the evaluation period, internal and supplier surveillance findings, internal and supplier corrective action requests issued, and plans for improvement.

vi. Post Project Summary Reports: Produced for projects where the Government requests a Detailed Pre Project Estimate. Report will provide the variance between the identified project’s initial, detailed estimated cost and the project’s final cost; the variance between the project’s scheduled release to operations (RTO) and the actual RTO; and a summary of the project’s technical verification highlighting any issues. The Report will also include an explanation for the above variances and issues.

DRD-MSOC-0012 (Page 2 of 3)

vii. Status Reports and meetings include, but are not limited to:

1. Daily reports and morning standups:

a. FOD status teleconferences

b. Daily Operations Meeting (DOM)

c. SVMF daily status reports

d. SVMF morning standups

2. Weekly or as required reports:

a. Weekly activity reports

b. FOD Flight Operations and Integration Group (FOIG) meetings

c. FOD Product Integration Board (MPIB) meetings

d. FOD integrated scheduling meetings

e. Facility Control Boards (CBs) and other CD governing boards and panels as defined by

CD-UWI-0013, Mission Systems Division Governance Plan

f. CD and Contractor management status meetings

g. Delivery schedules

h. Work plans

3. Monthly reports:

a. Program Manager Status Reviews (PMSRs)

b. Progress reports

c. Delivery schedules

d. Work plans

e. DRD status reports

f. Security reports

g. QA reports

h. SQA monthly report (in accordance with NASA-STD-8739.8, Software Assurance

Standard, Section 6.7, Software Assurance Status Reporting)

i. Surveillance reports

4. Quarterly reports:

a. Process Integrity Metrics Review (PIMR)

b. Technical Cost and Schedule Reviews (TCSRs)

5. Reports and meetings due with special frequency:

a. FOD Flight Readiness Reviews (FRRs) – per flight and increment

b. Post Project Summary Reports

6. Reviews and meetings:

a. PMSR – monthly

b. Operating plan review – as required

c. Project Integration Meetings – as required

d. Critical Path Review (CPR) – as required

e. PPBE review – as required

d. Format: Electronic format of all submissions shall be compatible with IRD provided desktop standard applications. Organizational format of the supporting documentation shall be determined by mutual agreement between the Contractor and the TMR.

e. Distribution: Per Contracting Officer’s letter.

DRD-MSOC-0012 (Page 3 of 3)

i. Initial – Due at the end of the first applicable reporting period after contract start.

ii. Final – Due at the end of the final applicable reporting period.

iii. Approval – N/A.

iv. Frequency – Due on the last day of the applicable period for status reports covering one week or less. Due no later than 20 business days following close of the applicable period for all status reports covering periods of time greater than one week. Other frequencies are acceptable with mutual agreement of the Contractor and the TMR.

DRD-MSOC-0013 (Page 1 of 3)

Reprocurement Data Package

2. Date of current version

06/30/16

3. DRL line item no.

DRD-MSOC-0013

RFP/Contract No.

(Procurement completes)

NNJ16100117R

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

Provide content and format requirements for delivery to NASA of all analytical models, tools, supporting documentation, equipment, data items and resource/cost information used to perform future reprocurement activities. In the event of a competitive solicitation for a follow-on effort, NASA may provide non-proprietary historical information such as average composite direct labor rates and approximate seniority profiles of incumbent personnel to all interested parties in order to increase the probability of realistic pricing. Data contained in Paragraph 8.c.i, “Labor Resources”, Paragraph 8.c.ii, “Nonlabor Resources”, and Paragraph 8.c.iii may be marked “Lockheed Martin Proprietary Data” and “Competition Sensitive”. The Government does not intend to disclose any contractor proprietary information. Data contained in Paragraph 8.c.iv, “Technical and Process Information” may be disclosed to competing offerors in the future.

5. DRD Category: (check one)

Technical X Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

8. Preparation Information (Include complete instructions for document preparation)

a. Data Type: 2

b. Scope: Analytical models, unique tools, supporting documentation, equipment, and resource/cost information shall be submitted in accordance with this Data Requirements Description (DRD).

c. Content: A data package shall be submitted containing…