Task 9-8 Mission Operations Support to JPSS FP.pdf
PDF 790 KB Posted
- Solicitation number
- 80GSFC21R0046-elibrary
View the file
Other files
Show all 21
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Omnibus Multidiscipline Engineering Services II
(OMES-II)
All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions
Task Order Statement of Work (SOW)
Date: 5/7/2021 Task Name: Mission Operations Support to JPSS Flight Project Task No. / Mod: 9/8 Task Monitor (TM): Redacted Contract number: NNG17CR69C Contract SOW Reference:
Subtask 1: Function 3 B Subtask 2: Function 3 B Subtask 3: Function 3 C, 3F, 4A, 4B Subtask 4: Function 3 C, 3F, 4A, 4B
Subtask 5: Function 4B Subtask 6: Function 4B Subtask 7: Function 4A, 4B
I. Scope
Background –
The Joint Polar Satellite System (JPSS) Flight Project (FP) Flight Readiness Group performs design, implementation of the operations concept and the post launch operations of the JPSS satellites for all JPSS missions (S-NPP and JPSS-1/2/3/4) through handover to OSPO at ~L+90 days on behalf of the JPSS Flight Project. JPSS Flight Readiness Engineering Support specified within this task provides technical engineering support to the JPSS Flight Project Flight Readiness Manager across all of these elements.
a. Summary of work – Support the mission operations readiness needs for S-NPP, JPSS-1 and
JPSS-2
b. Required skills/knowledge - Mixed skill-set of personnel that has knowledge in spacecraft operations of the various subsystems and instrument operations. Personnel also needed that have experience in ground system design/development/testing and testing with the flight vehicle.
All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions
II. Period of Performance
POP defined for each of the following subtasks
III. Subtask Description
Subtask 1: J1 Spacecraft Mission Operations Systems Support
Subtask requirements and period of performance have ended but numbering is retained in
SOW.
Subtask 2: J2 Spacecraft Mission Operations Systems Support
Provide Mission Operations System Engineering support to the JPSS Flight Project particularly in the area of integrated observatory level testing involving the Common Ground System, including but not limited to the following: - Integration and Test (I&T) for Spacecraft bus subsystems and instrument - Satellite environmental test planning, conduct, and verification - Spacecraft external interface testing - Evaluation of spacecraft operations products (DB, ops products, commissioning) - Evaluation of spacecraft deliverables and givers - Evaluation of spacecraft contract requirement compliance - Spacecraft and observatory special studies / trades - Spacecraft discrepancy and anomaly investigations/resolution - Risk management and waiver review - Spacecraft technical telecons, special topic meetings, TIMS and Monthly Status reviews.
Recurring Travel is required in Support of Activity approximately 1 trip every 3 months for 2 personnel. Travel is to be Pre-Approved by Project. Travel Locations shall include, but not be limited to, following locations: 1. Satellite Provider (Gilbert, AZ) (3 days) 2. Instrument Provider (assume Azusa, CA for costing) (3 days) Trip Reports in Contractor Format required within seven (7) days of completion of trip.
Duration: 12 months
Subtask 3: J1 Mission Operations Support Team (MOST)
SOW.
Subtask 4: J2 Mission Operations Support Team (MOST)
Provide team management, system engineering, and discipline engineering support to the JPSS-2 Mission Operations Support Team (MOST) including but not limited to the following:
• Provide JPSS-2 spacecraft, instrument and orbital analysis expertise as members of the integrated MOST. This task will provide support in the areas of spacecraft (bus subsystem) analysts, instrument analysts, and orbital analysts.
• Provide cognizance S-NPP/JPSS-1 Legacy/Lessons Learned and JPSS engineering developing support for spacecraft subsystems supporting operations including the communication, power, thermal, instruments, CD&H, FSW, propulsion, and Guidance, Navigation, and Control subsystems.
• Support mission planning and ongoing operation and anomaly support for the JPSS satellites. Specifically, work collaboratively with spacecraft and instrument vendors as appropriate and other JPSS/S-NPP OSPO and MOT personnel to identify the necessary activities to continue on-orbit operations of the S-NPP and JPSS-1 Satellite
• Develop and maintain procedures for nominal operation of the JPSS-2 satellite, as well as for anomaly response. Specifically, work collaboratively with spacecraft and instrument vendors and other JPSS/S-NPP OSPO and MOT personnel to develop, refine, verify, and update (as needed) nominal, operations procedures for the JPSS-2 spacecraft and instrument suite. These include Recommended Operating Procedures (ROPs) and Standard Operating Procedures (SOPs).
• Develop and maintain procedures to include Command Procedures, Ground System Operating Procedures, Telemetry Display Pages, plot development, test and on-orbit scripts, Contingency Operations Procedures, and Post-Launch Test (PLT) plans and scripts.
• Develop JPSS-2 Training Plans. Support the development and maintenance of training materials and provide general training on the JPSS-2 spacecraft and instruments.
Consider options for exposure to similar designed missions (S-NPP, JPSS-1, other GSFC missions)‘shoulder to shoulder’ operational training and best methods for incorporating similar missions Lessons Learned into the Training approach.
• Support spacecraft and Ground System Testing: Participate in planning and conducting JPSS Joint Compatibility Tests (JCTs) to send commands and process telemetry, including developing the test plan, generating and validating test scripts, configuring the Ground System, and execution/direction of the test. Support in regression testing and validating changes. Coordinate use of ground system resources. Perform Telemetry and Command Database Validation.
• Participate in, support, and coordinate/Lead where needed, Operations Reviews and Working Groups. Includes but is not limited to support of: Mission Operations Working Groups, Mission Operations Reviews, Flight Operations Review, Simulator Working Group Reviews, Operational Readiness Reviews, External Independent Readiness Review, Network Operations Working Groups, End-to-End Working Groups, PLT Working Groups, and ROP working groups.
• Plan and conduct mission simulations, rehearsals and training. • Conduct around-the-clock engineering and mission operations services during launch and early operations and check-out through transition to OSPO (~L+90 days). Provide engineering services in conducting data analysis and trending.
• Provide support during calibration/validation and routine operations and science testing.
Certain elements of this subtask will not be planned/executed during this period of performance of this mod due to the current phase of the JPSS-2 spacecraft development, availability of the JPSS-2 unique simulators and the readiness of the JPSS-2 unique changes to the Common Ground System (CGS). All elements have been retained in this mod such that the contractor understands the full scope of the JPSS-2 MOST and this subtask.
Recurring Travel is required in Support of Activity approximately 1 trip per 3 months for 3 individuals. Travel is to be Pre-Approved by Project. Travel Locations shall include, but not be limited to, following locations: 1. Satellite Provider (Gilbert, AZ) (3 days) 2. Trips to Instrument Provider (assume Azusa, CA for costing) (3 days) Trip Reports in Contractor Format required within seven (7) days of completion of trip.
Duration: 12 months Subtask 5: J1 LEO&A Planning Support
SOW.
Subtask 6: J2 LEO&A Planning Support Coordinate and support the development of a post-launch activation, check-out, and validation plan. The plan shall include both spacecraft and instrument activities as well as cover the entire overall schedule for the 90-day JPSS-2 Commissioning Phase.
Majority of the element of this subtask will not be planned/executed during this period of performance of this mod due to the current phase of the JPSS-2 spacecraft development, availability of the JPSS-2 unique simulators and the readiness of the JPSS-2 unique changes to the Common Ground System (CGS). The contractor shall support documentation and disposition of the lessons learned from the JPSS-1 campaign for incorporation into the JPSS-2 campaign. All elements have been retained in this mod such that the contractor understands the full scope of the JPSS-2 MOST and this subtask.
Subtask 7: FSW Working Group Support
Define, formally baseline, and maintain process documentation (FUDP) describing how flight software updates and table updates are initiated, vetted, implemented, validated, and approved across the various configuration engineering/control boards on the JPSS Ground and Flight Projects.
Conduct regular Flight Software Working Group (FSWWG) to bring together all government and supplier stakeholders to propose and vet technical solutions to resolve on-orbit anomalies or implement and validate new functionality in the flight software and/or related operational products (stored sequences, ground operations procedures, etc.). Tie FSWWG activities to the formal processes for on-orbit software updates, and to the various configuration engineering/control boards and discrepancy/anomaly review boards on the JPSS Ground and Flight Projects.
Monthly Deliverable Report
The contractor shall provide no later than the 10th working day following the close of the contractor’s monthly accounting period a 533M for each individual subtask and a summary 533M at the total task level. If it is not possible to provide the individual 533M at the subtask level, the contractor shall provide on the 10th working day following the close of the contractor’s monthly accounting period a break out of hours and costs by subtasks to the Contract Resource Analyst, Contracting Officer, and the Task Monitor. The report shall include current period hours and costs, cumulative to date hours and costs, and cumulative costs with a one-month cost plan. When needed, the contractor shall make adjustments to the
The contractor shall manage schedule, cost, and technical risk through monitoring and reporting of progress and performance metrics, identifying issues well in advance of negative consequences, recommending corrective action to the TM, and implementing corrective actions with the compliance of the TM.
e. Performance Metrics
The work performed for this task will be evaluated by the TM based on the technical merit.
The TM shall develop detailed performance metrics that shall reflect the contractor’s performance in meeting research analysis, specific mission requirements, deliverables and delivery schedule, and the contractor’s cost. Technical evaluation of the task performance is a subjective combination of performance metrics, technical quality of deliverables, cost control, significant events, innovations and meeting requirements set forth in the SOW.
f. Government Furnished Facilities, Equipment, Software and Other Resources
The Government will provide account and passwords to government-furnished workstations where existing versions of various relevant software packages shall be maintained. It shall be the contractor’s responsibility to complete any GSFC required security-related training courses.
The contractor shall provide Systems Administration service and support equipment required for both onsite & offsite contractor functions
g. Quality Assurance Requirements (See Clause I.1 1852.216-80 TASK ORDERING PROCEDURE (d) (4) and QA plan)
The contractor shall comply with the JPSS Project’s Quality Assurance Plan, attached to this task order.
The contractor providing technical services shall comply with all CMMI Level 2 processes established for the Project and deliverable products. Applicable requirements include, but not limited to:
1. NPR 7120.5D NASA Space Flight Program and Project Management Requirements cost reporting in accordance with the WBS. The contractor, including subcontractors, shall be available to attend monthly status meetings.
The contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly meeting via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports.
Monthly Subtask Report Spreadsheet
The contractor shall provide a break out of hours and costs by close of business on the 15th of each month to the Contract Officer, Contract Resource Analyst, and the Task Monitor. The report spreadsheet shall include current period hours, costs, cumulative-to-date hours and costs, and cumulative costs with a one-month cost plan. When needed, the contractor shall make adjustments to the distribution of costs, layout of the report and change reportable elements as specified by the Task Monitor and/or the Contract Resource Analyst.
IX. Security Requirements
The contractor shall comply with Information Technology Security procedures and requirements as defined by NPR 2810.1A in the performance of this task. In addition, the contractor shall comply with all applicable federal rules and regulations and agency directives.
The Contractor shall adhere to project requirements regarding ITAR related information, as controlled by the ITAR, 22 CFR 120-130, by the U.S. Department of State. Any transfer of controlled information to a foreign person or entity requires an export license issued by the U.S.
Department of State or an ITAR exemption to the license requirement prior to the export or transfer.
X. Safety
The OMES-II Safety/Mission Assurance Officer shall:
• Ensure all contractor personnel understand their safety responsibilities and follow safe practices for all lab and office operations.
• Ensure branch training requirements for contractor employees are implemented.
• Attend safety related training applicable to the operations under their area of responsibility.
The contractor personnel shall:
• Follow safety requirements when performing any task, keeping their workplace in a safe manner.
• Attend all required training, set forth by the OMES-II Safety/Mission Assurance Officer, ensuring certifications are current.
XI. Data Rights This SOW shall adhere to the following Data Rights clause, as stated in this contract: “the default Data Rights clause under this contract is FAR 52.227-14 RIGHTS IN DATA-GENERAL as modified by NASA FAR Supplement 1852.227-14-Alternate II and Alternate III and GSFC 52.227-90. Any exceptions to this clause will be covered by FAR 52.227-17 RIGHTS IN DATA-SPECIAL WORKS as modified by NASA FAR Supplement 1852.227-17, and, if applicable, GSFC 52-227.93.”
XII. Applicable Documents
In the performance of this task, the contractor shall comply with the following documents:
a. NPR 7150.2A/B NASA Software Engineering Requirements
b. GPR/GPD 7150 Goddard Software Engineering Requirements
c. GSFC STD-1000 Goddard Space Flight Center Rules for the Design, Development, and Operation of Flight Systems (GOLD Rules)
XIII. References
File details come from the government source that posted it. Updated .