PWS_MOSSI_II_Draft.pdf

J-1

SECTION J - LIST OF ATTACHMENTS

PART III – List of Documents, Exhibits, and Other Attachments

Attachment Title

J-l Performance Work Statement (PWS)

J-2 Data Procurement Document

J-3 Applicable Regulations, Procedures, and Documents

J-4 Acronyms and Abbreviations

J-5 Organizational Conflict of Interest (OCI) Plan

J-6 Work Breakdown Structure (WBS)

J-7 MOSSI II Performance Evaluation Plan

J-8A Installation Property, Services and Facilities

J-8B List of Installation-Accountable Government Property

J-9 Safety, Health, and Environmental (SHE) Plan

J-10 Wage Determinations

J-11 Contractor Innovations, Approaches, Advance Agreements, and Corporate

Capital Investments

J-12 IDIQ Fully Burdened Labor Rates

J-13 Task Order Summary

J-14 Small Business Subcontracting Plan

J-15 NASA Labor Category Descriptions

J-16 DD254 Department Of Defense Contract Security Classification Specification

J-1-1

ATTACHMENT J-1 PERFORMANCE WORK STATEMENT (PWS)

The Marshall Operations Systems, Services, and Integration (MOSSI II) contract provides the ground systems and operations services necessary to meet the requirements delegated to the

Payload and Mission Operations Division (PMOD) within the Human Exploration Development and Operations (HEDO) Office located at the Marshall Space Flight Center (MSFC). MOSSI II includes institutional (mission support) requirements, resulting from HEDO/PMOD being chartered by, and residing within, the MSFC. MOSSI II also includes programmatic requirements delegated to PMOD by the programs and projects that employ PMOD to satisfy a subset of requirements within their overall portfolio.

The MOSSI II contract scope includes innovations (including commercialization initiatives) and improvements that meet National Aeronautics and Space Administration (NASA) goals and/or result in cost savings and efficiencies.

The MOSSI II contract is a mission services contract. The core component (PWS Sections 1 through 11) includes:

• International Space Station (ISS) payload operations and ground systems

• Space Launch Systems (SLS) o Test, launch, and flight operations o Ground systems to support test, launch, and flight operations

• Near Earth Asteroid (NEA) Scout flight operations and ground systems

• Autonomous Mission Operations (AMO) demonstrations to support crew autonomy

• Delay Tolerant Network (DTN) protocol variants definition, prototyping, and testing

The scope of the MOSSI II contract will be executed with the philosophy of leveraging the common resources and requirements of the multiple programs that PMOD supports in order to provide common designs, facilities, systems and services that will result in efficiencies and cost savings that are beneficial to all PMOD customers. In cases where unique designs, facilities, systems, and/or services are required, the resource requirements associated with those unique requirements will be allocated by the project customer requiring the unique services.

The MOSSI II contract supports all project customer life cycle phases as documented in NASA Procedural Requirements (NPR) 7120.5 “NASA Space Flight Program and Project

Requirements.” Briefly, Phases A through D include the Design, Development, Test and

Evaluation (DDTE) phases that bring new systems and capabilities on-line for use. Phase E is the

Operations phase, that receives new capabilities produced in the earlier phases, and incorporates these new capabilities into the existing repeatable operations products, processes, and procedures.

Phase F, Closeout, may also be applicable during the MOSSI II period of performance per the requirements of PMOD customer programs and projects.

The ground system architecture is in Phase E and any modifications will be managed via the appropriate change process. The Phase E component of MOSSI II is essentially the “Plan, Train, Fly” component of operations, which, for the ISS program, is focused on the mission

J-1-2 preparation, training, and real-time operations conducted on an ISS increment basis. For non-ISS programs, this phase includes operations support for monitoring and/or controlling ascent, checkout, orbit determination, mission operations, de-orbit and descent, landing and post-landing. Phase F would include the decommissioning of launch or flight vehicles. Phase F could include the orderly transfer of PMOD/MOSSI II requirements or content to other business entities, including commercial providers.

In support of the ISS program, the term “mission” refers to the on-orbit operations of the ISS.

Periodic segments of the operations plan are referred to as “increments” and “increment pairs.”

“Increment pairs” represent the semi-annual science planning periods for ISS utilization.

“Increment-specific” refers to products that focus on a single increment, and “flight-specific” refers to products that focus on the unique aspects resulting from a vehicle that visits the ISS. In support of PMOD, the MOSSI II contractor is tasked with providing the operations personnel and capabilities to accomplish operations preparation, planning, and training; as well as execution, post-flight, and post-increment functions of on-orbit payload operations functions for

Payloads, Payload Support Systems (PLSS) and facilities.

Historically, the ISS Payload Operations Integration Function (POIF) refers to the plan/train/fly effort and the Payload Operations Integration Center (POIC) refers to the ISS mission ground systems hosted in the Huntsville Operations Support Center (HOSC). Payload Operations

Integration (POI) is used to refer to the union of these efforts upon the establishment of a Cost

Account Manager (CAM) at MSFC. In some cases, ISS reference material refers to the POIC as the POIF operations activities performed in the POIC. The POIC is designated as an Office of

Management and Budget major Information Technology (IT) Investment.

For the ISS support, PMOD staffs the POIC flight controller positions 24 hours a day, 7 days a week, 365 days a year. PMOD ensures payload safety and facilitates “user access” to ISS resources to maximize science return and enhance mission success. In support of SLS, PMOD provides continuous local and remote access to SLS engineering data. SLS training, simulation and console support is tailored to the needs of the SLS program, primarily focused on launch operations and post-flight data analysis. Operations support for the Near Earth Asteroid (NEA)

Scout project is also tailored to the needs of that mission, driven by specific mission events.

Both the Autonomous Mission Operations (AMO) project and the Delay Tolerant Network

(DTN) project are implemented within the operations support structure of the ISS program.

The Ground System requirements of the MOSSI II contract include the development, maintenance, and operation of the POIC systems, including related outfitting and systems that extend beyond the physical boundaries of the HOSC and MSFC. The HOSC is located in MSFC

Building 4663. Due to heritage, “the HOSC” is used interchangeably for PMOD ground systems, some of which do not reside in Building 4663. Additionally, the HOSC has been designated as an Agency high value asset (HVA), which requires an increased level of risk management and reporting. The memorandum providing information on management of HVAs may be viewed at:

https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2017/m-17-09.pdf

J-1-3

Ground System functions include: sustaining engineering of developed systems for both local and remote locations; operations activity preparation and simulation; mission evaluation activities;

hardware and software maintenance; systems operations and facility outfitting; data collection, processing, distribution, long-term storage and operations and maintenance

(O&M), decommission, transition, and close-out of systems.

Customers are defined as program or projects entities that provide resources to PMOD to implement their requirements. During the MOSSI II period of performance, customers will include NASA programs and projects, and may include non-NASA entities.

Project users are defined as the organizations and/or individuals that utilize the operational systems, services, and capabilities provided by PMOD through the MOSSI II contract.

Geographically, domestic users may reside within the HOSC, within MSFC or other NASA

Centers, and within domestic commercial or educational facilities. International users include formal ISS International Partners (IP) facilities and researchers, international space ventures, and

Payload Developers / researchers.

The MOSSI II contract will include an indefinite-delivery, indefinite-quantity (IDIQ) task ordering component, which will extend the services provided by the core mission component to meet the requirements of any current or future programs or projects that wish to utilize PMOD and the MOSSI II contract.

The MOSSI II contractor is accountable for successful performance of the requirements defined in this PWS. The contractor is responsible for implementing, managing, measuring, integrating, and participating in both internal and external processes necessary for execution of the activities described in this PWS.

PMOD is committed to the continual improvement of its processes, practices, and products. The contractor is expected to embrace this commitment through the execution of the MOSSI II contract.

1.0 Management

1.1 Program Management

The contractor shall:

1.1.1 Prepare, submit, and implement a MOSSI II Management Plan in accordance with Data Requirements Description (DRD) 1641MA-003.

1.1.2 Perform the overall management, planning, coordination, integration, scheduling, and reporting necessary to accomplish contract requirements in accordance with the

PMOD Management Plan, PMOD-MGMT-PLAN-001, and the applicable Program

Implementation Plan (PIP) (e.g., Payload and Mission Operations Division (PMOD) ISS

Payload Operations Integration (POI) Project Implementation Plan (PIP), PMOD-

ISSPIP-PLAN-001).

J-1-4

1.1.3 Provide planning, coordination, integration, and surveillance of the activities necessary to assure disciplined performance of work and timely application of resources for the accomplishment of the functions addressed in this PWS.

1.1.4 Provide a single point of contact with contractual obligation authority to perform all contract functions and activities required. This point of contact shall have access to all contract administration data and information related to contract performance.

1.1.5 Prepare, submit, and present resource, technical, and schedule risk status reports, metrics data, and documentation in accordance with the PMOD Management Plan, DRD

1641MA-006, Performance Management Review, and DRD 1641MA-005, Metrics Plan and Report.

1.1.6 Perform domestic and international travel to complete required assignments per applicable regulations. Travel to attend training classes, provide off-site system support, and participate in analysis at other facilities and in support of other engineering, design, development and test activities at remote sites.

1.1.7 Provide support for outreach and education activities upon request.

1.1.8 Provide and present data (e.g., Rough Order of Magnitude (ROM) estimates) and special reports to discuss and resolve emerging technical and programmatic problems and change in a format and content that complies with the PMOD request.

1.1.9 Obtain and maintain required personnel clearance levels prior to any classified work being performed. The required Facility Security Clearance Level for the Marshall

Operations Systems, Services and Integration (MOSSI II) contract is TS/SCI. The Contractor shall adhere to the requirements outlined in the Government Contracting

Authority issued DD254, Department of Defense Contract Security Classification

Specification, for this contract. The DD254 is incorporated as Attachment J-16, DD254, Department of Defense Contract Security Classification Specification.

1.1.10 Ensure all required Contractor personnel have a national security clearance commensurate with the highest level of classified duties being performed as identified in

Attachment J-15, NASA Labor Category Descriptions.

1.2 Contract Management

The contractor shall:

1.2.1 Prepare and submit an On-Site Employee Location Listing in accordance with

DRD 1641CD-002.

1.2.2 Prepare, submit, and implement an Organizational Conflict of Interest (OCI) Plan in accordance with DRD 1641MA-004.

J-1-5

1.2.3 Comply with the NASA Physical Security procedures in HOSC Access

Procedures, MSFC-PROC-1933, for access to the HOSC which is NASA Mission

Essential Infrastructure.

1.2.4 Prepare and submit Technology Reports in accordance with DRD 1641CD-001.

1.2.5 Prepare and submit a Re-Procurement Data Package in accordance with DRD

1641MA-009

1.3 Business and Financial Management

The contractor shall:

1.3.1 Perform all business and financial management functions necessary to fulfill the requirements of this contract; integrate these functions across all areas of performance;

and provide on-going business analysis and response to requests and inquiries from the

PMOD relating to budget, schedule, manpower, cost plans, and cost performance.

1.3.2 Establish charge codes aligned to the NASA WBS/PWS, as appropriate, to be used in generating reports to the Government (e.g., PMR, PPBE, and schedules). Update as necessary when WBS/PWS changes are made or new projects are added.

1.3.3 Provide a resource tracking system that provides traceability from Level III to

Level V in accordance with the PMOD Mission Operations Configuration Management

(MOCM) Plan, PMOD-MOCM-PLAN-001, and Ground Systems Configuration

Management (GSCM) Plan, PMOD-GSCM-PLAN-001, to support resource tracking and reporting.

1.3.4 Prepare and submit contractor Operating Plan and Program Planning, Budgeting and Execution (PPBE) inputs in accordance with DRD 1641MA-008 to include basis of estimates (BOE) for program/project budget cycles and processes and preparation of inputs for the NASA PPBE process, to include five-year budget projection planning.

1.3.5 Prepare and submit Information Technology (IT) Capital Planning Investment

Control (CPIC) cost accounting reports in accordance with DRD 1641MA-001 and present contractor inputs prior to submittal based on Agency, project, PMOD, and

MSFC deadlines.

1.3.6 Prepare and submit the Financial Management Report (533M) in accordance with

DRD 1641MA-010 and provide cost analysis and assessments for all activities of the

PWS, including any IDIQ task orders.

J-1-7

1.6.1.5 Perform CM functions to include configuration identification, configuration change control management, configuration status accounting, configuration verification, and auditing in accordance with the MOSSI II CM Plan.

1.6.1.6 Maintain existing documents, identified as applicable with contractor update required, in Appendix A, Applicable Documents List, and in accordance with the PMOD Management Plan.

1.6.1.7 Respond and provide inputs to existing documents, identified as applicable with no contractor update required, in Appendix A Applicable

Documents List, and in accordance with the PMOD Management Plan.

1.6.1.8 Maintain software libraries, drawings, test procedures, and operating procedures in accordance with the PMOD GSCM Plan.

1.6.2 Organizational CM (project specific)

The contractor shall:

1.6.2.1 Perform CM in accordance with the PMOD ISS POI PIP.

1.6.2.2 Perform a CM desk function for the receipt, distribution, and response submittal to ISS program Change Requests (CR), Preliminary Interface Revision

Notices (PIRNs), Change Evaluation Forms (CEFs), and Payload Integration

Agreements (PIAs) utilizing ISS systems in accordance with MOCM and GSCM plans.

1.7 Data Management (DM)

PMOD data and deliverables are hosted on multiple websites (i.e., real-time operations, organizational, and programs). Framework and hosting of real-time operations website(s) is a MOSSI II responsibility as required below. The PMOD Organizational website is hosted by the MSFC CIO, while the ISS program website is hosted by the Johnson Space Center

(JSC) Mission And Program Integration Contract (MAPI).

The contractor shall:

1.7.1 Prepare, submit, and implement a PMOD Data Management Plan in accordance with DRD 1641DM-001.

1.7.2 Administer the content of websites and pages, supporting products, documentation, and data, as established by the PMOD Management Plan, PMOD Data

Management Plan, the PMOD ISS POI PIP, and supporting governance, to include:

• PMOD real-time operations website

• PMOD organizational website

J-1-8

• ISS program website

1.7.3 Maintain repositories for PMOD documentation in the following categories:

• PMOD real-time operations documentation

• PMOD organizational documentation

• Project documentation

• Documentation required by Attachment J-2, Data Procurement Document

(DPD)

1.7.4 Develop and maintain websites and pages in accordance with processes defined in the PMOD DM Plan.

1.7.5 Maintain records management in accordance with NASA Policy Directive (NPD)

1440.6, “NASA Records Management,” and NPR 1441.1, “NASA Records Management

Program Requirements.”

1.8 Quality Management

The contractor shall perform quality assurance in accordance with the PMOD-QA-

PLAN-001, PMOD Quality Assurance Plan.

1.9 Administrative/Logistics Support

The contractor shall:

1.9.1 Provide administrative/logistics support for forums identified in the PMOD

Management Plan to include teleconference logistics, agenda planning, recording technical meeting minutes, recording and tracking actions, and posting materials for access.

1.9.2 Provide administrative/logistics support for non-routine meetings, conferences, workshops, technical meetings, and VIP meetings hosted by the PMOD.

1.10 Procurement

The contractor shall:

1.10.1 Procure hardware, maintenance services, software licenses, upgrades, tools, and materials, not otherwise furnished by the Government as listed in Attachment J-8B, List of Installation-Accountable Government Property (IAGP), in accordance with contract requirements and implementation plans and in compliance with applicable Federal

Acquisition Regulations (FAR) and NASA FAR Supplement (NFS) requirements.

The Contractor shall ensure that all license/maintenance agreements entered into in support of this contract contain the following language to ensure the assignment of all

J-1-9 license/maintenance agreements to the Government and/or third-party Contractor at the end of the contract period of performance: “Seller hereby agrees to permit assignment of this license/maintenance agreement, and all rights thereof to NASA/Marshall Space

Flight Center, or to another party that may be selected and assigned at the sole discretion of the Government.”

1.10.2 Identify and report options for efficiencies and potential cost reductions while executing the annual procurement plan.

1.10.3 Identify and report integrated FY procurement plan execution status in accordance with DRD 1641MA-008, and DRD 1641MA-006.

1.10.4 Ensure that procurements of systems and applications associated with one or more of the six covered Electronic and Information Technology (EIT) Accessibility product groups, specified below, comply with the applicable standards in accordance with Section

508 of the Rehabilitation Act of 1973. The applicable Technical Standards (Subpart B) include:

• Software Applications and Operating Systems (1194.21)

• Web-based Intranet and Internet Information and Applications (1194.22)

• Telecommunications Products (1194.23)

• Video or Multimedia Products (1194.24)

• Self-Contained Closed Products (1194.25)

• Desktop and Portable Computers (1194.26)

1.11 Property Management and Coordination

The contractor shall:

1.11.1 Prepare, submit, and implement a Government Property Management Plan in accordance with DRD 1641LS-001.

1.11.2 Coordinate and comply with all NASA property processes, procedures, and regulations to include movement, shipping, receiving, audits and inventories, in accordance with NPR 4200.1, “NASA Equipment Management Procedural

Requirements.”

1.11.3 Prepare and submit a report identifying all property provided by the Government for use by the contractor in the performance of this effort and for which the contractor has been given physical custody in accordance with DRD 1641LS-001.

1.11.4 Perform property management and administration of all property acquired by, or in possession of, the contractor and subcontractors including List of IAGP in accordance with DRD 1641LS-001.

J-1-10

1.11.5 Provide logistics functions, such as packing and preparation, for shipping equipment for relocating equipment to its installation point in accordance with NPR

4200.1.

1.11.6 Coordinate all property management functions with the MSFC property management organization and any appointed Property Administrator (PA).

1.11.7 Initiate transfer of accountability by submitting a MSFC Form 4554, “Transfer and Shipping Document" (or equivalent DD Form 1149), accompanied by a copy of the contractor’s applicable purchasing and receipt document for the property. The Form 4554 shall reference both the contractor’s Subcontract/Purchase Order number and the

Government contract number. For purchases of supplies and materials, this form shall be submitted within 30 calendar days after the end of each calendar-year quarter (i.e., not later than January 30, April 30, July 30, and October 30). For equipment purchases, the

Form 4554 (or equivalent DD Form 1149) shall be submitted within 10 business days after acceptance of each item of equipment by the contractor.

1.11.8 Coordinate movement of property (e.g., materials or equipment) off site with the

Contracting Officer (CO) and the Industrial Property Officer (IPO) in accordance with

NFS 1852.245-71, “Installation-Accountable Government Property.”

1.12 Export Control

The contractor shall:

1.12.1 Maintain an export control program in accordance with NASA Advisory

Implementing Instruction, NAII 2190.1, "NASA Export Control Program Operations

Manual."

1.12.2 Provide export control review and assessment for PMOD documentation and presentations, and provide disposition recommendations to the Government.

1.13 Contract Information Technology (IT) Security

Ground system IT security is managed and addressed separately from contract IT security and is detailed in Section 6.0, Ground Systems Development and Sustaining Engineering.

The contractor shall:

1.13.1 Perform contract IT security management in accordance with DRD

1641MA-003, MOSSI II Management Plan.

1.13.2 Prepare and submit the Information Technology (IT) Security Status Report in accordance with DRD 1641MA-011.

J-1-11

1.14 Safety, Health and Environmental Program

The contractor shall:

1.14.1 Prepare, submit, and implement the On-site Safety, Health, and Environmental

(SHE) Plan in accordance with DRD 1641SA-001.

1.14.2 Prepare and submit On-site Mishap and Safety Statistics Reports in accordance with DRD 1641SA-002.

1.14.3 Prepare and submit the Environmental Compliance Report in accordance with

DRD 1641EE-001, to include the Annual Green Purchasing Report.

1.15 Continuous Improvement, Innovations and Efficiency

NASA recognizes that its industry partners have a wealth of knowledge and experience as it relates to making innovative changes throughout the conduct of program/project life cycles.

Leveraging this experience, NASA expects the contractor to continually monitor for and assess potential areas of improvement.

The contractor shall:

1.15.1 Derive, document, and propose to the relevant PMOD forums recommendations for improvements to operations processes, systems, services, and productivity, considering return on investment in such areas as project management, risk, quality, operations philosophies/processes, mission development, training (e.g., crew, Flight

Control team, Payload Developer teams, and SLS Engineering Support Center

(SESC)), product development, tool capabilities, and mission execution.

1.15.2 Make regular and continual assessment of PMOD and project customer products, processes, systems, and services for efficient and appropriate application toward meeting objectives, staffing, milestones, and cost.

1.15.3 Collect lessons learned during performance of contracted requirements per the

PMOD Management Plan; evaluate and recommend actions for incorporation into products, processes, systems and services; and manage and track actions taken in response to lessons learned to closure, to include the reporting of status and external dependencies.

1.15.4 Make regular and continual assessment of PMOD governance processes and documents and make recommendations to PMOD management for efficient and appropriate application toward improved management practices.

1.15.5 Assemble lessons learned and submit to project customers upon project call (e.g., mission or activity related).

J-1-12

1.15.6 Collect performance feedback from all PMOD customers/users (internal and external) on products, processes, systems, and services. Analyze feedback and recommend prioritization and actions in response to feedback collected to relevant

PMOD forums.

1.15.7 Manage and report the implementation of approved changes to products, processes, systems, and services resulting from collected feedback.

1.15.8 Perform trade studies and benchmarking when approved by the PMOD to continuously seek improved operations processes, systems, services, and productivity.

2.0 Technical Integration

Technical integration includes the leadership and coordination across the MOSSI II contract, the PMOD organization, and the PMOD project customers required to develop end-to-end operations concepts and solutions, to respond to project customer actions, and to represent

PMOD topics in forums. The framework for integration and governance across PMOD is described in the PMOD Management Plan. The charters for the boards, panels, coordination groups, and forums described in the PMOD Management Plan form the basis for vetting, escalation, and coordination of the PMOD position on decisions both internal and external to

PMOD.

2.1 PMOD Internal Action Integration

The contractor shall:

2.1.1 Assess and technically integrate across ground systems, flight systems, technical disciplines, and project customers to identify resource, schedule, safety, and technical impacts for internal PMOD forum actions (to include engineering and other technical change requests).

2.1.2 Assess each PMOD internal action item for resource, schedule, and technical impacts across all elements impacted to include impacts from non-MOSSI II contracts and Government efforts.

2.1.3 Submit proposed responses, track, and represent responses through PMOD forums/processes and other coordination meetings where the responses are reviewed.

2.1.4 Propose reconciliation approaches for conflicting assessments.

2.1.5 Report lack of responses from mandatory assessors to the action or change initiator.

2.1.6 Escalate external decisions that impact PMOD objectives and performance to the appropriate management or forum.

J-1-13

2.1.7 Ensure action and change due dates are met, or that prioritization and delays have

PMOD approval.

2.2 Project Integration

2.2.1 Project Technical Integration

The contractor shall:

2.2.1.1 Collect and document requirements for implementation and integration into operations and ground systems.

2.2.1.2 Provide change package engineering support for project changes initiated by the PMOD.

2.2.1.3 Integrate, in response to project-initiated changes, launch vehicles, ground systems, flight systems, and technical disciplines to identify resource, schedule, safety, and technical impacts to the baseline as specified in the applicable PMOD PIP. Impacts may include other contracts and Government efforts in support of PMOD (e.g., Communications Services Office (CSO), MAPI, and other NASA Centers).

2.2.1.4 Analyze changes, functionally derive requirements, and initiate relevant internal work authorization/change processes for ground systems and operations products.

2.2.1.5 Generate or evaluate complete and comprehensive updates to the ISS capabilities and program-controlled applicable documents identified in the PMOD

ISS POI PIP to support the implementation of end-to-end POI processes and capabilities.

2.2.1.6 Participate in formal Technical Coordination Meetings (TCMs) and technical reviews to define, implement, integrate, and maintain operations concepts, requirements, capabilities, and interfaces.

2.2.2 Project Technical Representation

The contractor shall:

2.2.2.1 Represent PMOD topics and positions in project forums, boards, and meetings per the applicable PMOD PIP.

2.2.2.2 Develop documentation and presentations, vet in accordance with

PMOD governance, and present material, as required.

J-1-15

2.2.4.2 Integrate with ISS Payload Developers in accordance with project milestones and products identified in the SSP 57057, ISS Science, Technology and Exploration (ST&E) Integration Flow.

2.2.4.3 Provide ISS Payload Developer user advocacy via coordination among all organizational (PMOD) and ISS functions to meet mission requirements.

2.2.4.4 Submit non-standard PIA requests for assessment per the PMOD ISS

POI PIP.

2.2.4.5 Attend ISS Payload Developer Technical Interchange Meetings (TIMs) and design reviews, participate in testing, and incorporate findings into operations and training products.

2.2.4.6 Regularly engage with the ISS Payload Developers to share current ISS and organizational (PMOD) operations best practices, concepts, policies, standards, capabilities, limitations, opportunities, improvements, and risks.

2.2.4.7 Perform ISS Payload Developer ground system requirements integration and mission support planning for testing, operational support, and maintenance activities.

2.2.4.8 Analyze ISS Payload Developer requirements to identify candidates for standardization of services that enhance efficiencies and minimize costs.

2.2.4.9 Ensure that all ground system requirements and commitments are analyzed, documented, and supportable.

2.2.4.10 Analyze ISS Payload Developer operations and ground system, mission, and communication requirements and initiate relevant internal work authorization/change processes for ground systems and operations products.

2.3 Government Off-the-Shelf Software

The contractor shall:

2.3.1 Perform requirements definition and operations assessment of tools, software, and databases used in the performance of the contract.

2.3.2 Represent organizational (PMOD) requirement interests to external tool user working groups and advocate prioritization of changes to the supplier.

2.3.3 Propose and advocate changes that benefit the PMOD and project customers/ users.

J-1-17

Flight controllers are SMEs in their discipline and their initial training plan is approved by

NASA. Flight controllers are recommended for certification by the NASA Operations

Director, and maintain proficiency after certification.

Integrated Support Team (IST) personnel are SMEs in their discipline and their initial training plan is approved by NASA. IST personnel are recommended for certification by the contractor, and maintain proficiency after certification.

3.1 Flight Operations Project and Systems Engineering

The contractor shall:

3.1.1 Perform engineering integration across all flight operations, products, tools, systems, and disciplines to execute the mission in accordance with the applicable PMOD

PIP.

3.1.2 Ensure that flight operations capabilities fully support the dynamic mission environment, surge capability, vehicle traffic, timeline execution changes, and manifest changes.

3.1.3 Conduct performance studies recommending changes to eliminate potential operational bottlenecks and resource conflicts to optimize operational processes.

3.1.4 Deliver integrated operations and flight products, in accordance with applicable

PMOD PIP, to meet program milestones.

3.1.5 Develop, coordinate, and implement approved mitigation plans to resolve operations challenges.

3.1.6 Ensure Flight Controllers understand and are knowledgeable of all available information prior to performing console duties.

3.1.7 Upon request, perform human factors and usability assessments for the design and development of displays, operations concepts, processes, and tools for end-users.

3.1.8 Develop and deliver integrated transition plans to support reconfiguration of flight systems and ground systems.

3.1.9 Provide inputs to test requirements, plans, and procedures and conduct

Operational Readiness Tests (ORTs) to verify the operations and ground system capabilities in accordance with Payload Operations Handbook (POH), Volume 1:

Pre/Post Increment Operations (POH Vol 1), POIF-1004.

3.1.10 Develop and integrate the technical response for ISS CEFs in accordance with

POH Volume 1 and with Payload Operations Handbook (POH), Volume 2: Increment

Operations (POH Vol 2), POIF-1004.

J-1-18

3.1.11 Develop and integrate the technical response for product baselining and change requests and assessments in accordance with the PMOD MOCM Plan.

3.1.12 Identify, document, track, and resolve problems associated with payloads, facility-class payloads, payload support systems, data/video systems, and Joint Station

Local Area Network (LAN) encountered during operational, simulation, test, verification and validation support activities in accordance with POH Vol 2.

3.1.13 Support NASA-directed problem resolution teams/forums (e.g., Mission

Evaluation Room (MER), Anomaly Resolution Team (ART), Multilateral Anomaly

Resolution Team (MART), Failure Investigation Team (FIT)) in accordance with the applicable PMOD PIP.

3.2 Mission Safety

The contractor shall:

3.2.1 Ensure organizational (PMOD) products and processes are in compliance with safety requirements in accordance with the applicable PMOD PIP.

3.2.2 Perform independent safety verification and flight safety compliance in accordance with the applicable PMOD PIP.

3.2.3 Represent organizational (PMOD) interests throughout the safety review process.

3.2.4 Prepare, implement, maintain, and deliver safety products in accordance with

POH Vol 1 and POH Vol 2 and the Payload POIC Hazardous Commanding Safety

Hazard Report, MSFC-RPT-3715.

3.3 Generic Operations Products: Rules, Regulations, and Processes

The contractor shall:

3.3.1 Develop, maintain, and deliver ground support products (e.g., console procedures, console handbooks, Standard Operating Procedures (SOP), Operational Interface

Procedures (OIP), systems briefs, schematics, console tools, payload summary sheets) necessary to adequately support real time operations.

3.3.2 Develop, maintain, and deliver operations products in support of mission requirements in accordance with the PMOD Management Plan and the applicable PMOD

PIP.

3.3.3 Integrate inputs from disciplines and Payload Developer teams to develop, document, and deliver flight rules and payload regulations that identify operational constraints and safety related operations restrictions, launch commit criteria, and other operational constraints documentation in accordance with POH Vol 1 and POH Vol 2.

J-1-19

3.3.4 Integrate inputs from disciplines to develop, document, and deliver all volumes of the Operations Handbooks (e.g., payloads, data, flight) in accordance with the applicable

PMOD PIP.

3.3.5 Provide inputs to all applicable project procedures/documents (e.g., OIP, Flight

Console Operations Handbook (FCOH), flight operations handbook) required for conducting operations with other control centers in accordance with the applicable

PMOD PIP.

3.3.6 Develop and validate operations and ground system configurations required to support ground/vehicle interfaces, payloads, facility-class payloads, and payload support systems to execute the mission plan, identify discrepancies, and resolve any issues.

3.4 Payload-Unique Operations Products

The contractor shall:

3.4.1 Review and provide assessments of the Payload Developer teams’ operations concepts, crew displays, and crew procedures to ensure compliance with the PMOD ISS

POI PIP.

3.4.2 Provide support for the development, review, integration, verification, maintenance, and delivery of payload crew procedures (e.g., nominal/malfunction procedures and reference materials), including crew aid enhancements (e.g., photos, videos, and animations), when required.

3.4.3 Provide technical support and input to the Operations Data File (ODF) Control

Board and its splinter International Procedure Viewer working group and Standards working group, in accordance with the PMOD ISS POI PIP.

3.4.4 Develop, verify, validate, and deliver Ground Command Procedures for payloads, facility-class payloads, payload support systems, data/video systems, and Joint Station

LAN in accordance with the PMOD ISS POI PIP.

3.4.5 Utilize the ISS Timeliner software to develop, verify, validate, and deliver automated on-board bundles for payloads, payload support systems, and facility-class payloads in accordance with the PMOD ISS POI PIP.

3.4.6 Develop, verify, validate, maintain, and deliver POIC command and telemetry displays, payload/facility-unique computations, scripts, and exception monitoring for payloads, facility-class payloads, and payload support systems using ground system capabilities.

J-1-20

3.5 Mission Planning

The contractor shall:

3.5.1 Develop, document, and deliver the planning requirements and US Payload

Planning Groundrules and Constraints (Gr&Cs), and integrate the US and IP Gr&Cs that are used in mission timeline development in accordance with POH Vol 1.

3.5.2 Develop, deliver, and maintain increment activity models and integrate all NASA and IP payload resource requirements (ground and flight) for the ISS increment-specific mission plan in accordance with POH Vol 1 and the PMOD ISS POI PIP.

3.5.3 Develop and deliver the On-orbit Operations Summary (OOS), Payload Activity

Requirements Documents (PARD), and Payload Planning Overviews (PPO) in accordance with POH Vol 1.

3.5.4 Provide NASA-directed informal assessments of potential mission plan changes.

3.5.5 Plan, develop, implement, and deliver processes and procedures to perform payload stowage and payload cold stowage integration functions in accordance with POH

Vol 1 and POH Vol 2.

3.5.6 Verify hardware, tools, and materials are available to execute the mission plan.

3.5.7 Provide stowage inputs and develop and deliver stowage products (e.g., stowage notes, pack and pre-pack lists, transfer lists, un-pack lists) as required for use in the mission plan by the flight operations team and ISS crew.

3.5.8 Attend pre-flight payloads, facility-class payloads, and payload support systems reviews as required.

4.0 Training

PMOD training encompasses the tasks, products, and methods utilized to fully prepare the flight controller, support personnel (operations and ground system), instructor, payload developer, project user, and flight crew involved in the preparation and execution of the mission.

4.1 General Organizational (PMOD) Training

The contractor shall develop, document, and maintain lessons, training materials, and training environments to communicate knowledge of organizational (PMOD) projects, systems, tools, and processes.

J-1-21

4.2 Flight operations personnel, Flight Controller, IST, and Instructor Training

The contractor shall:

4.2.1 Perform and document training needs analyses.

4.2.2 Identify and document requirements for training methods/tools to support flight operations and ground system mission needs for approval in accordance with the PMOD

MOCM Plan.

4.2.3 Develop, document, and maintain lessons, training materials, and training environments in accordance with approved training requirements.

4.2.4 Define, implement, and maintain definitions for Laboratory Training Complex

(LTC) requirements and other capability needs of the PMOD in accordance with

Laboratory Training Complex Requirements, PMOD-LTC-RQMT-001.

4.2.5 Support Space Station Training Facility (SSTF) requirements definition, verification and validation testing, and operation for crew and flight controller training preparation and execution.

4.2.6 Develop, implement, and maintain Individual Training Plans (ITP) in accordance with the Payload Ground Support Personnel Training and Certification Plan, POIF-1000.

4.2.7 Execute and/or support training in accordance with the Payload Ground Support

Personnel Training and Certification Plan, Individual Training Plans, and POH Vol 1.

4.2.8 Provide instructor(s) to conduct training.

4.2.9 Define the training configuration needs and support requirements for each training event and coordinate the resources required for delivery.

4.2.10 Ensure Flight Controllers are trained in compliance with the Payload Ground

Support Personnel Training and Certification Plan.

4.2.11 Ensure IST personnel are trained in compliance with the HOSC Console Training and Certification Plan, HOSC-PLAN-209.

4.2.12 Develop, implement, and maintain mockups and software models of payloads and onboard systems in accordance with the PMOD ISS POI PIP.

4.3 Crew Training

The contractor shall:

J-1-23

5.0 Mission Execution

The contractor conducts and is responsible for real-time ISS payload operations. ISS payload operations are led by NASA Payload Operations Directors (PODs) and are executed by Flight

Controllers.

5.1 Safety and Mission Success

The contractor shall perform real-time operations to ensure safety and enable mission success for payloads, payload support systems, and facility-class payloads in accordance with POH

Vol 2.

5.2 Real-Time Flight Control

The contractor shall perform command and control, planning, video and data management, stowage, timeline execution, crew communication, anomaly identification and resolution, safety, and ground system control in accordance with POH Vol 2.

5.3 On-Call Support

The contractor shall, at a minimum, provide a certified on-call safety engineer at all times if not otherwise providing real-time support. During on-call status, the safety engineer shall maintain proximity to the real-time operations site such that on-site support can be provided within two (2) hours of notification.

5.4 Ground System Operational Support

The contractor shall provide ground system operational support in accordance with the

MSFC Ground Systems and Services (MGSS) Requirements Document, MSFC-RQMT-

3589, the PMOD GSCM Plan, Internal Operating Procedures (IOPs), and SOPs.

6.0 Ground Systems Development and Sustaining Engineering

Ground system support includes all mission phases and all life cycle phases. PMOD ground systems are categorized as mission information technology (IT) systems. ISS ground systems include the POIC and the LTC. A majority of the ground system components are located within the HOSC Building 4663 on the MSFC campus. A small number of components are located external to the HOSC, both within and external to MSFC (e.g., MSFC Building 4207, White

Sands Complex, and KSC).

Sustaining Engineering includes development activities such as upgrades and enhancements.

J-1-24

6.1 Project and Systems Engineering

The contractor shall:

6.1.1 Perform engineering integration across all ground system configuration items, including the NASA-developed Telescience Resource Kit (TReK), to ensure the integrity and compatibility of the overall architecture and compliance with existing interface control/definition documents.

6.1.2 Perform sustaining engineering of ground system architecture components identified in Attachment J-8B and in compliance with applicable ground system requirements documents identified in Appendix A, Applicable Documents List and in accordance with the PMOD GSCM Plan.

6.1.3 Develop new ground system requirements specifications and ICDs in accordance with the PMOD GSCM Plan; implement these new ground system capabilities; and perform sustaining engineering of these new ground system capabilities, operations, and associated documentation delivered under this contract.

6.1.4 Develop new and maintain existing systems concepts, system requirements, software requirements, system architectures, hardware and COTS software specifications, network requirements, and interface definitions, to produce and deliver integrated architecture designs in accordance with the PMOD GSCM Plan.

6.1.5 Conduct Level III and Level IV change assessments, engineering acceptance tests, and design reviews in accordance with the PMOD GSCM Plan.

6.1.6 Develop comprehensive system acquisition specifications, investigate vendor solutions, and provide make-or-buy decision options.

6.1.7 Perform systems engineering and analysis of new or changed Consultative

Committee for Space Data Systems (CCSDS) standards, assess compatibility with existing ground systems, and incorporate approved changes into the ground systems.

6.1.8 Prepare, submit, and implement a System Development Plan in accordance with

DRD 1641MA-007.

6.1.9 Conduct system architecture performance studies and recommend changes to eliminate potential system bottlenecks, resource conflicts, and system overloads.

6.1.10 Generate performance analysis of existing architecture, computer, software

(including COTS), networks, video, voice, security, and data storage components to assess compliance with applicable system requirements. Provide capacity/upgrade planning recommendations based on this analysis.

J-1-25

6.1.11 Provide fault isolation, detection, and analysis, and identify corrective changes to the architecture.

6.1.12 Perform, document, and maintain traceability from program requirements through architecture component specification development in accordance with the PMOD GSCM

Plan.

6.1.13 Perform technology assessments, system upgrade analysis and test, concept prototyping, product evaluations, and human/computer interface evaluations.

6.1.14 Ensure that ground system capabilities fully support the dynamic mission environment, surge capability, vehicle traffic, timeline execution changes, and manifest changes.

6.1.15 Ensure end-user and intra-center operational and system support requirements and implementation program commitments are met.

6.1.16 Maintain the Program Requirements Document (PRD)/Database in accordance with KSC-PLN-3445 Support Requirement System Management Plan and Automated

Support Requirements System Handbook (which supersedes JSC-27379 Support

Requirements System Management Plan), to reflect all inter-center project requirements.

6.1.17 Develop and maintain obsolescence plans which proactively identify a replacement approach, including end-of-life designation, replacement cost, and schedule for application code, and third-party hardware/software.

6.1.18 Perform and document demonstrations and inspections to fulfill formal verification requirements managed by the IV&V contractor.

6.1.19 Verify end-to-end configurations that involve remote connections for standard services as defined by the SSP 50305 POIC Generic User Interface Definition Document or the MSFC-ICD-3683, MSFC Ground Systems and Service Interface Control

Document.

6.2 Software Development and Sustaining Engineering

The contractor shall:

6.2.1 Update software as required in accordance with the PMOD GSCM Plan to support upgrades of Commercial and Government Off-The-Shelf (COTS/GOTS) software/hardware, changes to existing requirements, internal and external ICD/Interface

Definition Documents (IDD), and to resolve software defects.

6.2.2 Perform sustaining software engineering of ground system software in compliance with applicable requirements documents identified in Appendix A, Applicable Documents List, and in accordance with the PMOD GSCM Plan.

J-1-27

6.3.4 Perform sustaining engineering of video systems and services in compliance with applicable requirements documents identified in Appendix A, Applicable

Documents List, and in accordance with the PMOD GSCM Plan.

6.3.5 Develop new video system requirements, specifications, and ICDs in accordance with the PMOD GSCM Plan; implement these new capabilities; and perform sustaining engineering of these capabilities, operations, and associated documentation delivered under this contract.

6.4 Voice Services

The agency network contract is responsible for requirements, design, and delivery of voice systems and services which are considered IAGP for the purposes of the MOSSI II contract.

The contractor shall:

6.4.1 Perform systems engineering (as outlined in section 6.1) and integration for the incorporation of IAGP voice systems and services in accordance with MSFC-ICD-3740.

6.4.2 Perform sustaining engineering of voice recording systems and services in compliance with applicable requirements documents identified in Appendix A, Applicable Documents List, and in accordance with the PMOD GSCM Plan.

6.4.3 Develop new voice recording system requirements, specifications, and ICDs in accordance with the PMOD GSCM Plan; implement these new capabilities; and perform sustaining engineering of these capabilities, operations, and associated documentation delivered under this contract.

6.5 Integration of Network Services

The agency network contract is responsible for requirements, design, and delivery of physical network systems and services which are considered IAGP for the purposes of this contract.

The contractor shall:

6.5.1 Perform systems engineering (as outlined in section 6.1) and integration for the incorporation of IAGP network systems and services in accordance with MSFC-ICD-

3740.

6.5.2 Perform sustaining engineering of virtualized network systems and services in compliance with applicable requirements documents identified in Appendix A, Applicable Documents List, and in accordance with the PMOD GSCM Plan.

6.5.3 Develop new virtualized network system requirements, specifications, and ICDs in accordance with the PMOD GSCM Plan; implement these new capabilities; and

J-1-28 perform sustaining engineering of these capabilities, operations, and associated documentation delivered under this contract.

6.6 NASA Information Technology Systems Engineering & Integration

The contractor shall:

6.6.1 Incorporate safeguards and controls in accordance with National Institute of

Standards and Technology (NIST) SP 800-53 and applicable NASA IT security standards to ensure availability, integrity, and confidentiality of information and IT resources utilized in performance of this contract.

6.6.2 Perform systems engineering and integration of applicable NASA agency IT architecture and infrastructure requirements, design and…