Task 36-8 JPSS Flight Gravite Server Support.pdf
PDF 611 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: June 29, 2021 Task Name: JPSS Flight Gravite Server Support Task No. / Mod: 36/8 Task Monitor (TM): Redacted Contract number: NNG17CR69C Contract SOW Reference: Function 3 - Implementation Phase Services/Sub Section/ E.
MULTIDISCIPLINARY ANALYSES SERVICES
CHANGE SUMMARY: Modified POP
I. Scope
a. Background – The JPSS Flight Project, Code 472, is responsible for the management of the Suomi
National Polar Project (S-NPP) technical support, and post launch support. JPSS Flight Project management responsibilities include the design, development, manufacturing, integration and test, verification and documentation of the JPSS flight systems. The Project monitors the launch vehicle acquisition by KSC and provides payload launch integration support.
b. Summary of work – The JPSS Flight Project, Code 472, has a requirement to provide to the JPSS Science Team pre-launch satellite data collected throughout the Integration and Test (I&T) campaign at the spacecraft vendor facility. This data will be collected at the spacecraft vendor facility and transferred to the NSOF GRAVITE system. For the J2 mission, NOAA is providing the data transport connection through the N-Wave network. The data set consists of Science Mission Data (SMD) and High Rate Data (HRD) from the spacecraft captured by the spacecraft vendor RF Ground Support Equipment (GSE). The JPSS Project requires a data system that can ingest data from the spacecraft vendor GSE, process the data into output products required by each instrument using the GSFC Direct Readout Lab (DRL) Real-Time Spacecraft Telemetry Processing Software (RT-STPS), and transfer the resulting files to GRAVITE through the N-wave network.
1. Participate in program status meetings, telecons, peer reviews, and major project reviews for spacecraft, instruments, launch vehicle, mission operations system, and science data system.
2. Support with requirements definition, flow-down, validation and verification;
3. Prepare/Review project documentation and submit comments and recommendations
4. Prepare and present technical information for technical meetings / reviews / briefings;
5. Participate in instrument, spacecraft and observatory testing and anomaly resolution activities, as required.
6. Analyze configuration, design, and procedural changes submitted to the Project change control boards;
a. Required skills/knowledge –data systems and Direct Readout Lab skills.
II. Period of Performance The period during which the work for this task shall be performed is from task award thru June 30, 2022.
III. Subtask Description – no subtasks required 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 distribution of costs, layout of the report and change reportable elements as specified by the Task Monitor and/or the Contract Resource Analyst.
IV. Deliverables/Schedules/Milestones (See Contract sections B.1 and C.3)
1 Performance Reports & Status Reports Monthly 2 End-of-task Report End of task
V. Management Approach
a. Staff Allocation, Expertise, and Skill Mix
The contractor shall staff this work item with the appropriate skill mix and staffing level for the work.
b. Configuration Management
Systems and documents will be covered under the JPSS Program Configuration Management Procedure (470-00012).
c. Facilities
Gilbert, AZ (PMR) 2 People – 4 Days
8 Times
Gilbert, AZ (QSR) 3 People – 4 Days
2 Times
VII. Work Location
This work shall be performed primarily on-site at the Goddard Space Flight Center and/or via telework from employee location, but the contractor may be required to perform some work at the contractor’s facility.
VIII. Reporting Requirements
a. Monthly Status & Progress Reports
IX. The contractor shall generate a status report monthly for the TM. The report shall be posted electronically by close-of-business to a folder on JPSS eRooms designated by the TM. The report shall include, as a minimum, a summary of the months’ highlights/accomplishments/problems encountered, milestones/schedule/deliverables, risks and customer meetings. The report shall also include a forecast of planned out-of-office time for work travel, vacation, etc.
The contractor shall provide monthly technical and schedule progress reporting to adequately describe the activities of the contractor team to the TM. The contractor shall provide monthly cost reporting in accordance with the WBS. The contractor, including subcontractors, shall be available to attend monthly status meetings.
The contractor shall support the TM in the preparation of status reviews as needed. 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.
X. 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.
There will not be any handling of classified data.
XI. Safety 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.
XII. 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.”
XIII. Applicable Documents
1. NPR 7120.5E, “NASA Space Flight Program and Project Management Requirements”
2. NASA SP-2007-6105 Rev1, NASA Systems Engineering Handbook December 2007
XIV. References
File details come from the government source that posted it. Updated .