Task Order 4 PWS for Products Services and Applications.pdf

National Environmental Satellite, Data, and Information Service (NESDIS)

Office of Satellite and Product Operations (OSPO) and

Office of Satellite Ground Services (OSGS)

Draft Products and Applications Task Order 4

Performance Work Statement (PWS)

November 22, 2019

DRAFT OPERATIONS, MAINTENANCE, AND SUSTAINMENT

TASK ORDER 4 PWS - PRODUCTS, SERVICES & APPLICATIONS

1.0 Overview 4

1.1 Products, Applications, and Services Background 4

2.0 Scope 5

2.1 Place of Performance 6

2.2 References 6

3.0 General Requirements 7

3.1 Program Management Support 7

3.2 Monitoring and Customer Support 8

3.2.1 General Requirements 8

3.2.2 OSPO Satellite Product Monitoring and Customer Service Desk 9

3.2.3 Product, Application and Service Monitoring 9

3.2.3.1 Software Product Monitoring 10

3.2.3.2 Data Set Monitoring 10

3.2.3.3 Scientific Monitoring 10

3.2.3.4 Operational/Production Monitoring 10

3.2.3.5 Product Completion Monitoring 11

3.2.3.6 Product Accuracy Monitoring 11

3.2.3.7 Operational/Production Test Monitoring 11

3.2.3.8 Product Distribution Monitoring 11

3.2.3.9 Systems Analysis Support to Operations 11

3.2.3.10 Services Monitoring 12

3.3 Product Support Requirements 12

3.4 Software Maintenance Requirements 13

3.4.1 General Software Maintenance Requirements 13

3.4.1.1 Reactive Software Maintenance 13

3.4.1.2 Routine Software Maintenance 14

3.4.1.3 Adaptive Software Maintenance 14

3.5 Satellite Product Maintenance 15

3.6 Critical Infrastructure Protection (CIP) Support Maintenance Requirements 15

3.7 Satellite Product and Services Transition to Operations 16

3.8 Website Support 18

3.9 Specific Product, Application, and Services Requirements 21

3.9.1 Satellite Analysis Branch (SAB) Support 21

3.9.2 National Ice Center (NIC) Meteorologist/ Synthetic Aperture Radar (SAR) Support/ Satellite Image Processing and Analysis System (SIPAS) 23

3.9.2.1 Operations and Maintenance for NIC’s, SIPAS and IMS Applications 24

3.9.3 Direct Services Branch (DSB) Support 24

3.9.3.1 FTS Operations and Maintenance 28

3.9.4 Satellite Operations Software Maintenance 30

4.0 Performance Requirement Summary 31

Appendix A. Deliverables 33

Appendix B. Acronym Listing 36

Appendix C: Applications that produce L2 products 43

1.0 Overview

The Office of Satellite and Product Operations (OSPO) and the Office of Satellite Ground Services (OSGS) have shared responsibilities in managing legacy satellite ground systems and product processing systems. This document, Task Order 4 Performance Work Statement (PWS) specifies the requirements for Products and Applications Support for the OMS contract.

1.1 Products, Applications, and Services Background

Satellite products include operational OSPO software applications that generate and distribute satellite-derived products and services to NOAA and other users. These products and applications support critical mission systems and customers, so they must be available, secure, and reliable to deliver high quality and timely products. Environments requiring product and application support include: 1) NOAA’s Satellite Operations Control Center (SOCC) and 2) Environmental Satellite Processing Center (ESPC). Services include the geostationary and polar satellite direct broadcasts and rebroadcasts. The contractor’s work requirements associated with these services are described in this PWS.

Operational Application Support

Operational software applications manage the ground system components that command, control and communicate with the mission satellites. This includes network and hardware device drivers and interfaces, antenna tracking software, data ingest, processing to level 1B, and distribution systems.

Tasks associated with operational applications are:

● Maintaining ground station software systems that command and control the mission ground systems.

● Managing the applications that support operational product generation, data distribution, websites to customers, databases, or document management systems.

Operational Product Support

Product Support includes the generation and distribution of satellite-derived products and services to NOAA and other users. Product systems include complete software systems that are required to create products from current, future, and next generation NOAA satellites and non- NOAA satellites. In addition, ESPC software products also include ancillary systems that monitor and archive the data and products. Product system software must meet NESDIS-approved software coding and documentation standards and the OSPO Software Configuration Management (CM) Plan, and are administered by Government configuration management procedures.

● Manual and man-machine mix product generation is governed by standard Satellite Analysis Branch (SAB) and National Ice Center (NIC) operating procedures. These products include:

○ Real-time, operational volcanic ash, tropical storm, precipitation, oil spill/marine debris and/or fire/smoke products.

○ Snow and ice products or Synthetic Aperture Radar (SAR) imagery

○ Satellite product databases supporting products and applications.

Product generation and distribution of Satellite derived products require the following types of support:

● Operational software applications generate and distribute satellite-derived products and services to NOAA and other users.

● Maintenance of products and applications.

● Ensure compliance, reliability, availability, and maintainability of the OSPO operational applications to ingest data, generate, and distribute products.

● Ensure compliance, reliability, availability, and maintainability of the SOCC command and control, data acquisition, and product generation and distribution.

● Provide timely response to telephone or email inquiries requesting support or status updates on specific satellites, products, or services.

● Assist performing user outreach, support Web services, and inform users regarding environmental satellite products and services.

● Provide training.

2.0 Scope

The products and applications support for applicable Government ground systems is listed in Table 1.1-1 and Table 1.1-2. A detailed description of NESDIS systems is provided in OMS IDIQ PWS, Appendix 1, “NESDIS System Boundary General Correspondence to NESDIS Missions/Functions”.

Individual system inventories, drawings, descriptions, interfaces, as well as other reference documents are available in the OMS Document Library.

Table 1.1-1 NESDIS Systems Data and/or Systems Supported

NESDIS Systems Data and/or Systems Supported Data System Access

GOES NOP Legacy Geostationary Operational Environmental Satellites N/O/P Ground System

Y Y

DSCOVR Space Weather Ground System (Deep Space Climate Observatory (DSCOVR)) is an independent ground system that is a part of the GOES NOP system security boundary. It may become a security boundary that contains only

DSCOVR at some future date.)

N N

ESPC Environmental Satellite Processing Center Y Y NJGS NOAA JASON-3 Ground System Y Y

GOES R Series Geostationary Operational Environmental Satellites Ground System

Y Y

JPSS Series Joint Polar Satellite System Ground System Y Y POES Legacy Polar-orbiting Operational

Environmental Satellite Ground System Y Y

DMSP

Non-NOAA

Defense Meteorological Satellite Program (NOAA Operates this DOD Satellite)

Y Y

MSL Mission Support Local Area Network (LAN) Y Y

Table 1.1-2 Non-NESDIS Systems Supported under Task Order 4

Non-NESDIS Systems Supported Data System Access

AWIPS / NCEP Advanced Weather Interactive Processing System 2 (AWIPS2), National Centers for Environmental

Prediction (NCEP) Advanced Weather Interactive Processing System (NAWIPS)

Y N

Space Science and Engineering Center

Cooperative Institute for Meteorological Satellite Studies’ Man computer Interactive Data Access

System (McIDAS)

Y N

2.1 Place of Performance

Work locations for this task order are listed below:

● NOAA Satellite Operations Facility (NSOF) located in Suitland, MD

● NOAA Center for Weather and Climate Prediction (NCWCP) located in College Park, MD

● NASA’s Goddard Space Flight Center located in Greenbelt, MD

● NOAA Wallops Command and Data Acquisition Station (WCDAS) located in Wallops, VA;

● NOAA Fairbanks Command and Data Acquisition Station (FCDAS) located in

Fairbanks, AK;

● NOAA Consolidated Backup Unit (CBU) located in Fairmont, WV

2.2 References

The following reference documents are included in the OMS bidder’s library and apply to this task order:

● GOES-R Series Product Definition and User’s Guide (PUG)

● Joint Polar Satellite System (JPSS) Level 1 Requirements Document Supplement

3.0 General Requirements

The Contractor shall:

● Provide the required subject matter expertise, personnel, material, equipment, services, and facilities to perform and deliver products and applications support for the assigned systems with no interruption of services, at all work locations.

● Provide qualified personnel with professional and technical expertise commensurate with their responsibilities, and any certifications, if required.

3.1 Program Management Support

Program Management for Task Order 4 shall be administered per Task Order 1-Program Management. In addition, the following requirements shall apply to Task Order 4 for Products and Applications.

PWS-TO4-PA01: The Contractor shall provide and maintain a Resource Allocation Report [Deliverable], or any commercial off the shelf [COTS] tool with similar functionality showing tasks, resource management, and a project timeline. This schedule (or timeline) shall be accessible to Government personnel. Any alternative tool other than MS Project shall be approved by the Government, in advance. The schedule will be provided to the Government weekly.

PWS-TO4-PA02: The Contractor shall provide written weekly status reports [Deliverable See Task Order 1) ] and meeting support to include meeting minutes and agendas (Deliverable See Task Order 1) specific to active ongoing product development(s) for the duration of all product implementation tasks. The specific content of the weekly written status report shall be mutually agreed upon, after contract award.

PWS-TO4-PA03: The Contractor shall provide a monthly report to the Government describing new or pending licensing and warranty renewals in the Software License and Maintenance Renewal Management Report [Deliverable]. The Contractor shall provide license compliance validation and tracking services for all customer and COTS software applications used to support product operations.

PWS-TO4-PA04: The Contractor shall document lessons learned, identify risks, and provide mitigation plans as they implement new products [Deliverable].

PWS-TO4-PA05: The Contractor shall produce a Project Plan and Schedule for Products and Applications [Deliverable] for project based activities such as Product System Development and Integration (PSDI) projects, large system refresh, new systems transitioning to operations, or system boundary decommissioning. The Contractor shall provide initial review of the schedule thirty days after contract start followed by weekly updates with monthly reviews.

PWS-TO4-PA06: The Contractor shall provide a Quality Assurance Plan [Deliverable] that documents software development, software modification and test case processing. The software processes shall include at a minimum: completion of a requirements review, test plan [Deliverable], test readiness review, test and integration, test data review, an operational readiness review, and completion of all required documentation prior to a transition to operations. The Contractor shall include recommendations on process improvements to software sustainment, test, and operations.

Configuration Management requirements are specified in the OMS IDIQ PWS, and included under Task Order 1, Program Management PWS.

PWS-TO4-PA07: The contractor shall provide all required configuration management processes and services for products and applications.

PWS-TO4-PA08: The Contractor shall perform management and configuration control for new or modified software following CM procedures.

PWS-TO4-PA09: The Contractor shall provide weekly updates for open CCRs and report progress of CCR closure in the Configuration Change Requests Report (Task Order 1 Section

3.1.1 Configuration and Document Management (PWS-TO1-CM02); Deliverable XX). Perform all required activities to close CCRs per the agreed schedule, and elevate or expedite any activities required to maintain the CCR closure schedule.

3.2 Monitoring and Customer Support

3.2.1 General Requirements

Section 3.2.1 applies to all areas of support for Product and Applications.

PWS-TO4-PA10: The Contractor shall provide expertise in these tools, formats, languages, scripts, and operating systems applicable to products and applications:

● Tools - McIDAS, IDL, GrADS, NCL, GNU, ENVI, Matlab, ESRI ArcGIS

● Formats - netCDF, HDF, BUFR, McIDAS formats, GIS formats

● Languages - Java, SQL, C, C++, HTML, Fortran, XML, JS

● Scripting Languages - BASH, PYTHON, Perl, C-Shell

● Operating Systems - Unix, Linux, Windows

● All COTS software programs that support Products and Applications

PWS-TO4-PA11: The Contractor shall analyze available commercial off-the-shelf software (COTS), open GIS applications, and other NOAA applications to determine the “best fit” to meet the functional requirements. This includes providing documentation describing evaluation criteria, results, gap analysis and risks associated with each application candidate.

PWS-TO4-PA12: The Contractor shall comply with project or product-specific NOAA agreements with other entities, including Memorandum of Understandings (MOU) and Memorandum of Agreements (MOA). The Government will provide these documents to the Contractor within the OMS document library.

PWS-TO4-PA13: The Contractor shall deliver all product documentation in compliance with archive standards, including Federal Geographic Data Committee (FGDC) and International Organization for Standardization (ISO) compliant Metadata.

PWS-TO4-PA14: The Contractor shall assure compliance to ESPC standards of all delivered source code. The delivered code will be placed under configuration management per OSPO CM policies and procedures. Any executables that require re-building shall be extracted from the CM repository, unmodified.

PWS-TO4-PA15: The Contractor shall maintain a database of software in a centralized location, including all applicable software licensing and warranty information. This database shall be synchronized with the Product and Application configuration item (CI) database.

PWS-TO4-PA16: The Contractor shall maintain a current staffing list and update and distribute it on a monthly basis. The staffing list shall contain all employee training, as well as any changes (name, company, hire date and if applicable, departure date) [Deliverable].

PWS-TO4-PA17: The contractor shall meet or exceed overall product availability, not associated with system outages, of .999 averaged over 30 days.

3.2.2 OSPO Satellite Product Monitoring and Customer Service Desk

PWS-TO4-PA18: The Contractor shall provide a customer support desk staffing coverage 24 hours per day x 7 days per week x 365 days per year sufficient to handle the daily call, email, and customer service ticket volume estimates shown in Table 2.2.3-1:

Table 2.2.3-1 Support Volume FY19 Description Daily Average Annual

Calls 20 7300 E-mails 20 7300

Customer Service Tickets (Products)

5 1800

3.2.3 Product, Application and Service Monitoring

PWS-TO4-PA19: The contractor shall follow the product, application or service monitoring SOP and escalate to the appropriate technical point of contact for the following monitoring capabilities:

● Software Product Monitoring

● Data Set Monitoring

● Scientific Monitoring

● Operational/Production Monitoring

● Product Completion Monitoring

● Product Accuracy Monitoring

● Operational/Production Test Monitoring

● Product Distribution Monitoring

● Systems Analysis Support to Operations

● Services Monitoring

PWS-TO4-PA20: The Contractor product lead shall respond to the Product Customer Service Desk within 15 minutes of receipt of a call request.

PWS-TO4-PA21: The Product Customer Service Desk shall acknowledge customer call requests within 2 hours of receipt.

PWS-TO4-PA22: The Contractor shall resolve Product Customer Service Desk help desk tickets within 48 hours.

3.2.3.1 Software Product Monitoring

OSPO application systems monitor: (1) satellite data flows (2) data ingest, calibration and validation, (3) OSPO data processing and production systems, and (4) OSPO data distribution systems. All OSPO product and applications are continuously monitored to assure the accuracy, completion and integrity of content.

3.2.3.2 Data Set Monitoring

PWS-TO4-PA23: The Contractor shall monitor data sets for compliance in proper use, continuous ingest, and timely arrival of auxiliary data (e.g. ground truth data, model data, in situ data) to PDA from external sources.

3.2.3.3 Scientific Monitoring

PWS-TO4-PA24: The Contractor shall perform near real-time statistical data gathering, data quality, and long-term trend analyses to detect data characteristics for the scientific user community.

3.2.3.4 Operational/Production Monitoring

PWS-TO4-PA25: The Contractor shall perform and verify the:

● Execution of daily backup procedures for critical software libraries and files.

● Production of archive data sets and inventory records.

● Compilation of production statistics.

● Archiving of historical data.

● Operational/production processes produce expected products with expected results within expected latency requirements.

3.2.3.5 Product Completion Monitoring

PWS-TO4-PA26: The Contractor shall evaluate adherence to product generation schedules and check proper completion of orbital jobs on a daily, weekly, and/or monthly basis as applicable.

3.2.3.6 Product Accuracy Monitoring

PWS-TO4-PA27: The Contractor shall evaluate accuracy of products and satellite-derived parameters as compared, for example, to ground/sea/atmospheric truth (model data, Family of Services, or radar data) and/or climatology.

PWS-TO4-PA28: The Contractor shall perform analysis and measurements on all software applications to ensure the accuracy of products and satellite-derived parameters.

3.2.3.7 Operational/Production Test Monitoring

PWS-TO4-PA29: The Contractor shall monitor changed software to verify that it executes as expected and shall verify that replacement software meets or exceeds the efficiency and/or accuracy of the original.

3.2.3.8 Product Distribution Monitoring

PWS-TO4-PA30: The Contractor shall maintain statistical information on:

● Product-specific distribution metrics from all distribution servers.

● Visits to all websites by external users, regarding product-specific web analytics and other information useful in evaluating web presence.

PWS-TO4-PA31: Data from servers when operational shall be provided a minimum of 99.9% (of all data provided by data servers when the system is operationally available, averaged over a 30-day period)

3.2.3.9 Systems Analysis Support to Operations

PWS-TO4-PA32: The Contractor shall provide monitoring and job scheduling functions to include:

● Monitor product applications to specified levels. For example, these documents may include Level 1 requirements for the respective systems (e.g. SNPP and JPSS), GOES R Product User guides (e.g. GOES-R), and associated manuals for legacy applications.

● Modify job streams, start or stop application systems, rerun jobs, set-up and support testing, and monitor production utilizing Government-supplied enterprise scheduler system.

● Monitor primary and backup IT systems and product applications to provide continuous 24 hours a day x 7 days a week x 365 days a year operations utilizing Government

Furnished Equipment (GFE), OMS Document Library (when available), or Contractor-developed tool.

● Monitoring and trending of SNPP/JPSS products generated by the NESDIS Interface Data Processors (IDPs) utilizing JPSS Ground System Data Quality Monitor (DQM) Tools.

3.2.3.10 Services Monitoring

PWS-TO4-PA33: The contractor shall provide Product Customer Service Desk and customer support, including escalating and resolving Enterprise Configuration Management Tool (ECMT) help tickets per the ESPC procedure and notify the appropriate Service Manager, for the following:

● National Oceanic and Atmospheric Administration (NOAA) Satellite Information System (NOAASIS) website

● GOES Variable (GVAR)

● GOES Rebroadcast (GRB)

● Low Rate Information Transmission (LRIT) as a contingency

● High Rate Information Transmission/ Emergency Managers Weather Information

Network (HRIT/EMWIN)

● High Rate Picture Transmission (HRPT)

● High Rate Data (HRD)

● Field Terminal Support (FTS)

● Argos DCS

3.3 Product Support Requirements

PWS-TO4-PA34: The Contractor shall perform customer support functions to include:

● Customer service notification (24 hours a day, 7 days a week), issue escalation, initiate appropriate customer response and management notification utilizing established call trees and Standard Operating Procedures.

Note- Initial contacts are to acknowledge only receipt of customer requests and are made on behalf of the Government. The Contractor shall immediately forward each customer service response issue to the designated responsible support individual.

● Generate and review statistics of product and application usage. This includes logging of all customer support events, generating performance metrics (e.g. number of emails, calls and tickets per day, etc.).

● Generate/disseminate a daily customer support event log to include actions, all phone calls, email contacts from the previous day by 7:00 am local time the next day [Deliverable].

● Manage the customer support status log and transaction files.

● Analyze messages in logs for accuracy, relevance, and timeliness.

● Update status pages (with customer support status, news, facts, and warnings)

● Collect and report weekly on product and applications operational metrics [Deliverable].

● Facilitate and provide daily logs and customer support tickets for the daily review.

● Provide training materials [Deliverable], train users, and support personnel utilizing customer support procedures and processes, as well as communicate system changes and notifications.

● Ensure staff proficiency on emergency procedures and the conditions required for supporting emergency situations (e.g. dismissal or Government closure announcements).

● Provide high quality customer support telephone response, assign and track customer support tickets using Government-approved systems.

● Coordinate and forward customer support requests to the designated support individual (e.g. Product Area Lead (PAL)/Government Representative) as they are received.

● Monitor customer support responses to ensure submitted requests reach in-progress state.

● Maintain customer data in the Government-furnished Customer Relation Management

(CRM) database. These activities include: provide status email notifications for all anomalies, outages, and changes to data, products, applications, or services; include users (persons), products, services, satellites, applications, instruments, organizations, and administration

PWS-TO4-PA35: The Contractor shall perform surveys in order to measure customer satisfaction with the Help Desk. The Contractor shall work with the cognizant Government branch to develop and administer the surveys.

3.4 Software Maintenance Requirements

3.4.1 General Software Maintenance Requirements

The following section describes the general support tasks for software maintenance.

PWS-TO4-PA36: The Contractor shall deliver all software in compliance with established NESDIS standards. In the absence of NESDIS standards, the Contractor shall utilize industry best practices. For the case of industry best practices, the Contractor shall provide these to the Government for approval in advance.

PWS-TO4-PA37: The Contractor shall provide analysts with expertise in computer programming, remote sensing, and physical science.

PWS-TO4-PA38: The Contractor shall perform reactive, routine, and adaptive maintenance and database management on a 24 hours a day, 7 days a week basis for all operational ESPC applications.

3.4.1.1 Reactive Software Maintenance

For the contractor’s immediate follow up for return to service of products where an issue has been identified and logged, the following requirements apply:

PWS-TO4-PA39: The Contractor shall resolve, regardless of the hardware platform, all unexpected problems in data acquisition software, command and control, product generation systems software and product distribution software within 48 hours or less of notification.

PWS-TO4-PA40: The Contractor shall begin corrective action within two hours of notification for problems that prevent the operational processing, or where accuracy of the product(s) is significantly degraded of any operational products.

3.4.1.2 Routine Software Maintenance

PWS-TO4-PA41: The Contractor shall provide nominal software maintenance (i.e., monitoring, patching on a daily, weekly, monthly, or quarterly basis as reflected in the maintenance schedule), regardless of the hardware platform, for:

● Operational software used in daily operations.

● Adherence to all NESDIS/OSPO software CM policies and practices.

● Software updates.

● Perform monitoring of outputs to assure data/product integrity, compilation of statistics, backup, recovery, and security procedures.

● Implement approved changes to operational and non-operational software.

● Perform testing, verification to ensure that new and modified software functions as intended, and meets all existing functional and performance specifications.

● Produce, deliver, and document corrections, modifications, adaptations and enhancements of any new product application software for ESPC operational applications [Deliverable].

● Adapt, integrate and maintain COTS third-party software used in the ESPC.

● Utilize all Government-supplied and/or third party source software code, compilers, compiler procedures and off-the-shelf (OTS) tools required to re-create baseline software configurations.

● Routinely maintain, back-up, and support all databases utilized within the ESPC environment. These shall be readily available for operational use.

● Provide maintenance notifications in the daily change log (Deliverable)

3.4.1.3 Adaptive Software Maintenance

PWS-TO4-PA42: The Contractor shall perform adaptive maintenance per Satellite Products and Services Review Board (SPSRB) Software Coding and Documentation Standards.

PWS-TO4-PA43: The Contractor shall provide adaptive software maintenance to any hardware system supporting changes to operational product and application systems software. These tasks include processing environment changes (such as):

● Migration or conversion to a new computer

● System failures

● COOP activities

● Environmental data formats

● Output requirement changes

● Satellite launches

● To account for new satellites, satellite longitudinal and orbital changes and instrument changes

● Update of procedures for hardware and/or system software modifications or updates.

● Provide maintenance notifications in the daily change log (Deliverable previously mentioned)

3.5 Satellite Product Maintenance

Product systems are complete software systems used to create products from current, next generation NOAA satellites, and ancillary systems used to monitor and archive data and products.

Product system software must meet NESDIS-approved software coding and documentation standards. These standards are administered per ESPC Software Configuration Management (CM) procedures.

PWS-TO4-PA44: The contractor shall provide database maintenance support which includes:

● Updating meta tag parameters

● Functional verification of all pages (created or modified)

● Ensuring the quality and integrity of database components and tables

● Ensuring all operations and related reports are completed

● Support for record and field variable updates (including options to add, delete or edit)

● Provide maintenance notifications in the daily change log (Deliverable previously mentioned)

3.6 Critical Infrastructure Protection (CIP) Support Maintenance Requirements

This section contains staffing requirements to cover the activation and operations of all back up facilities in the event of a catastrophic disaster at NSOF or NCWCP.

PWS-TO4-PA45: The Contractor shall participate and assist, as directed, in the annual execution of a continuity of operations (COOP) and disaster recovery exercise.

PWS-TO4-PA46: The Contractor shall provide product monitoring support, maintenance, and customer support during COOP exercises. This includes ensuring products and applications remain in a ready state per COOP and CIP documentation.

PWS-TO4-PA47: Following Government-directed COOP deactivation, the Contractor shall conduct post-COOP debriefings, capture lessons learned (Deliverable same as deliverable previously mentioned), and provide recommendations for business process improvements to the Government.

PWS-TO4-PA48: The Contractor shall provide cross training to personnel to manage and operate the backup sites in the event of loss of primary OSPO support personnel.

PWS-TO4-PA49: The Contractor shall provide and support maintenance activities of the continuity of operations and disaster recovery (COOP/DR) plan and procedures to address the immediate and longer-term needs, to include:

● Determining vulnerability to significant service interruptions for NOAA missions.

● Identifying and analyzing economic, service, public image, and other implications of extended service disruptions.

● Defining preventive measures to minimize the probability and impact of interruptions.

● Defining recovery alternatives and best approaches for providing the capability for backup operations and timely service restoration.

● Determining immediate, intermediate, and extended recovery resource requirements.

3.7 Satellite Product and Services Transition to Operations

Science Algorithm development within NESDIS follows the Satellite Product and Services Review Board (SPSRB) Process. Algorithms and the corresponding Delivered Algorithm Package (DAP) are developed by the Center for Satellite Applications and Research (STAR) with OSPO Product Area Lead (PAL) participation. Services such as GRB and HRIT have components managed by CCBs. The GOES CCB provides oversight for the GRB ground processing. The ground processing for HRIT is under the ESPC CCB. The Service Managers submit CCRs to the CCBs, work with the CORs to ensure successful transition to operations, and coordinate with users.

While Contractor support for algorithm development activities is provided via other contract vehicles, the Government has designated this contract as the receiving vehicle for each DAP.

PWS-TO4-PA50: The contractor shall provide support for these tasks:

● Requirements review with Government personnel at the start of each DAP implementation project.

● Software code review and submit a Code Review Report (Deliverable) .

● Test (including regression testing), and verification of the products

● Operational readiness review.

● Completion of SPSRB documents (System Maintenance Manual, External User Manual and Internal User Manual).

● Promotion of the DAP(s) into the operations environment.

● Establish, maintain, and provide Government access to the ESPC Software Development

Environment.

● The Software Development Environment will include all tools, libraries, software, test data, models/simulators, and documentation used in the implementation of the product.

PWS-TO4-PA51: The Contractor shall plan and manage new implementation efforts to ensure successful implementation of projects per the implementation details within the CCR.

PWS-TO4-PA52: The Contractor shall establish, maintain, and provide Government access to the ESPC Software Development Environment.

PWS-TO4-PA53: The Contractor shall provide support to project management and systems engineering technical reviews.

PWS-TO4-PA54: The Contractor shall support the development and transition of new product applications, enhancements, and systems into the operational environment. This must include a (documented) process, a Government approved checklist, performing system tests, regression tests, and verifying that products meet user requirements as intended.

PWS-TO4-PA55: The Contractor shall work with these parties to plan, integrate, test, and transition to operations all new products, product enhancements, and product applications.

● Government Product Area Leads (PAL)

● Office of Satellite Ground Systems (OSGS)

● OSGS Contractors

● STAR Scientists

● Service Managers

PWS-TO4-PA56: The Contractor shall provide a Capacity and Performance Plan [Deliverable] to the Government to increase ESPC capacity and performance, and to maintain performance margins prior to any DAP implementation. This includes assessments for the new products transition to the current operational systems and infrastructure, as scheduled by the Government.

PWS-TO4-PA57: The Contractor shall review DAPs, and notify the Government when code delivered by STAR, or other collaborators, deviates significantly from ESPC standards. This review will determine whether the DAP requires modifications that will exceed the planned ESPC implementation cost or schedule, or will have negative impacts to system-reliability or compromise system security.

PWS-TO4-PA58: The Contractor shall coordinate with data providers (e.g., NWS, international partners, etc.,) to plan data ingest and product distribution to the NCEI via Comprehensive Large Array-data Stewardship System (CLASS) for archive.

PWS-TO4-PA59: The Contractor shall conduct operational readiness reviews (ORR) as required for products and applications (new products and/or major enhancements) that will be implemented into operations.

PWS-TO4-PA60: The Contractor shall monitor new applications/products for quality and completion, and that all operations and maintenance plans are established.

PWS-TO4-PA61: The Contractor shall coordinate changes to Ground Systems interfaces (e.g.

software, hardware, and firmware updates) with the Government ground system engineers (or their designated alternates).

https://www.ncei.noaa.gov/ http://www.class.noaa.gov/ http://www.class.noaa.gov/

PWS-TO4-PA62: The Contractor shall notify and support the Government ground systems engineers regarding anomalies and/or interfaces and data products pertaining to the systems below and future systems as identified by the Government:

● GOES-R Ground Systems

● JAXA Ground Systems

● NASA Ground Systems

● ESPC

● CNES

● EUMETSAT

3.8 Website Support

OSPO currently manages the following website shown in the table below:

Website Name URL Update Frequency

Number of

Pages

Host Location

Service Areas

NOAASIS https://noaasis.noaa.gov/ Weekly 400+ WOC GVAR,GRB, GOES Product Quality, HRIT, GOES DCS

POES, APT and HRPT, S-NPP and

JPSS, HRD,

Argos DCS, GNC-A, SARSAT

NOAA Satellite Conferences www.satelliteconferences.noa a.gov

Satellite Conference is held every 2 years. Website is updated several times during the year that the conference is held

246 WOC JPSS Instruments, GOES-R

Instruments, ESPC, GVAR,GRB, GOES Product Quality, HRIT, GOES DCS

POES, APT and HRPT, S-NPP and

JPSS, HRD,

Argos DCS, GNC-A, SARSAT

OSPO imagery and product server (and anonymous ftp server) --satepsanone.nesdis.noaa.gov Daily 3950 ESPC General

Subcommittee on disaster reduction www.sdr.gov Monthly 17 WOC General

Global Earth Observation System www.geonetcastamericas.noa a.gov

Monthly 10 WOC General

Current GOES images and animation www.goes.noaa.gov Monthly 200 WOC General

Current satellite images and operational products www.ssd.noaa.gov Monthly ~3880 WOC General

Operational Satellite Products and Services www.ospo.noaa.gov Monthly for

POES, SNPP,

JPSS, and GOES Status and when needed

4522 WOC POES Spacecraft and Instruments, JPSS Spacecraft and Instruments, GOES-R

Spacecraft and Instruments, PWS-TO4-PA63: The Contractor shall provide support and documentation for website support to include:

● Apply and maintain common ‘look and feel’ to OSPO web pages required by OSPO, NESDIS, NOAA, DOC, and OMB.

● Provide layout and graphic design, coding, web design, scripts, programming and site maintenance services for OSPO’s web presence and any redesign efforts.

● Maintain web pages to support the implementation of new products or capabilities including new information or additions to old products, and any changes required by new or modified Government standards.

● Assist OSPO personnel in the conversion of their product output to web offerings including assistance with layout structure, coding conventions, and maintenance.

● Collect web content and create/modify web pages in compliance with standards. The Government will provide content for all OSPO web pages.

● Consolidate common website information, ensuring data accuracy.

● Manage/maintain the Google Sites webpages and associated content and content delivery services and accounts.

● Assist OSPO personnel in providing web coding which complies with current industry best practices for web development and written in W3C validated HTML, using cascading style sheets to separate content from presentation for ease of maintenance and revision.

● Support web server applications including Dreamweaver, Majordomo and photo editing software.

● Provide resources and tools for handling images, animations and documents obtained, developed, maintained and applied to produce digital material for web publication.

● Maintain an interactive website for spacecraft events and spacecraft changes.

● Provide guidance and assistance to OSPO personnel so that future web content can be easily maintained and updated according to OSPO standards.

● Advise the OSPO IT staff regarding IT hardware and system software requirements of

OSPO’s STAR’s web environment.

● Work with the OSPO IT staff to apply web IT security controls as required to aid in meeting IT Security audit reviews.

● Work with the OSPO IT staff to facilitate web IT infrastructure changes as required.

● Implement websites in the NOAA Web Operations Center (WOC).

● In case of absence of federal staff, provide a backup representative for OSPO to the

NESDIS Information Resource Management Advisory Committee (IRMAC) Web Team meetings and activities.

● Develop and apply Web Content Management Plan(s) as required [Deliverable].

● Provide advisory support regarding government web content management policies and security compliance.

● Work with OSPO web content providers to update or implement mobile accessibility requirements for OSPO as necessary.

● Design and code OSPO web pages to follow federal, DOC, NOAA, NESDIS, and OSPO

STAR policies such as the Section 508 Accessibility requirements.

● Assist OSPO in answering actions and data calls in reference to OSPO’s web environment.

● Provide status and statistical reporting to OSPO management and personnel, and NESDIS and other NOAA offices as necessary. Provide quarterly log of inquiries and responses to management (Deliverable); provide monthly report of OSPO website hits [Deliverable].

● Maintain/monitor statistical information of website visits by external users, regarding product-specific web analytics and other information useful in evaluating web presence.

These statistical data sets will be defined by contract start and reported monthly. The Government will review and approve the data.

○ Policy for monitoring is https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2017/m- 17-06.pdf

● Draft responses to web inquiries and provide to the Government representative within two (2) business days upon receipt of inquiry.

● Restore/resolve web issues within 72 hours after identification.

● Provide similar support for future enhancements of OSPO’s web presence.

● Provide capabilities in various Application Programming Interfaces (API) to include

Google and Environmental Systems Research Institute (ESRI).

PWS-TO4-PA64: The Contractor shall maintain the NOAASIS website. Maintenance tasks include:

● Check all the links on a weekly basis and contact the Service Manager if a link does not work. Ensure that links to the OSPO website that display satellite status and service bulletins have the latest information.

● Respond to requests from Service Managers for changes with a schedule estimate within 1 working day.

● Post new information in existing tabs within 5 working days.

● Implement the operational website shall be implemented in the NOAA WOC. For major changes the contractor shall prepare a Beta site and provide access to the Service Managers to review it prior to going live in the WOC.

PWS-TO4-PA65: The Contractor shall operate and maintain the FTS Web Portal which will be hosted in the WOC to ensure the following requirements are met:

● FTS users will be able to browse and select information from the FTS web portal.

Information includes the following:

○ NOAA Global Forecast System and Navy Global Environmental Model gridded data

○ NOAA Global Multisensor Automated Snow/Ice Map (GMASI)

○ Mission Notices and Mission Schedules

○ Ephemeris Data

○ Two Line Element Sets

○ Predicted Post-Maneuver Two Line Element (TLE)s

○ Revolution Numbers

○ Earth Orientation Files

○ HRD Link Monitoring Reports

○ Ephemeral Processing Coefficient Tables

○ GND-PI Files

○ Look Up Tables

○ Visible Infrared Imaging Radiometer Suite (VIIRS) Reflective Solar Bands (RSB)

AutoCal History Auxiliary File

○ CrIS Correction Matrix

○ Algorithm Development Library (ADL) algorithm release packages and enterprise

Algorithms (when available)

○ JPSS Program Documentation from JPSS Management Info System

○ Global Gridded Intermediate Products (GIPs)

○ Additional products per Service Manager’s guidance

● The FTS server shall provide capability for customers to retrieve data via automated scripts

3.9 Specific Product, Application, and Services Requirements

3.9.1 Satellite Analysis Branch (SAB) Support

PWS-TO4-PA66: The Contractor shall provide shift support (including weekends and holidays, when required) to produce multi-disciplinary, interpretive (human-machine mix) products.

Note- The Government estimate for this support is 306 hours per week (average) and the minimum that the Government needs for the Contractor to minimally fulfill the requirement is 270 contact hours per week.

● The Government requires at a minimum:

○ One analyst certified to work independently on at least four SAB product areas.

○ Two analysts certified to work independently on at least three SAB product areas.

○ Three analysts certified to work independently on at least two product areas.

○ Three analysts (defined as personnel who, once trained in SAB, are certified to work independently) on at least one product area.

The Government will provide extensive on the job training, and a certification procedure.

PWS-TO4-PA67: Contractor-supplied analysts shall be (or become) certified on:

● Volcano/Tropical Desk with no more than 3.5 months on the job training

● Marine Pollution Desk with no more than 2.5 months on the job training

● Fire Desk with no more than 2 months on the job training

● Precipitation Desk with no more than 1.5 months on the job training

Note - Government analysts will provide on-the-job training to the Contractor to acquire required skills and expertise to produce real-time, operational volcanic ash, tropical storm, precipitation, oil spill/marine debris and/or fire/smoke products (and other new products, as needed).

PWS-TO4-PA68: The Contractor shall provide programmer analysts with skill sets to use satellite imagery to produce disaster mitigation products, preferably including one or more of the following skills:

● Remote sensing

● Meteorology or Oceanography

● Use of software capable of satellite imagery display (e.g., McIDAS, ENVI, ArcGIS, ERDAS)

● Computer programming (shell scripting - BASH, CSH, KSH – Perl, Python, HTML IDL, ENVI, ArcGIS)

PWS-TO4-PA69: The Contractor shall continue to provide support during emergency situations.

Dismissal or Government closure announcements will not apply to Contractor SAB analysts unless otherwise instructed by the on-site Government representative.

PWS-TO4-PA70: The Contractor shall perform special projects, as directed by the SAB personnel (e.g. support research collaborations, outreach, data analysis, validation, and general scripting enhancing SAB operations). The Government may require up to five Contractors obtaining secret level clearances.

PWS-TO4-PA71: The Contractor shall deploy to the remote COOP site in the event of an activation of the COOP. Government counterparts will also participate.

3.9.2 National Ice Center (NIC) Meteorologist/ Synthetic Aperture Radar (SAR) Support/ Satellite Image Processing and Analysis System (SIPAS)

PWS-TO4-PA72: The Contractor shall provide critical snow and ice products and services eight

(8) hours/day x seven (7) days/week x 365 days/year.

PWS-TO4-PA73: The Contractor shall participate, under the direction of the Government and with Government counterparts, in operations-related activities to the Interactive Multisensor Snow and Ice Mapping System (IMS) Snow and Ice analysis, selected Ice Products, and acquire and provide SAR imagery. Support includes weekends and holidays when required.

Note- the Government estimates this support at 160 hours/week (average one (1) analyst for SAR, and three (3) analysts supporting IMS activities). Government analysts will provide on-the-job training to Contractor analysts supporting the NIC to acquire the skills and experience necessary to produce the snow and ice products, regional and hemispheric ice charts, or acquire SAR imagery.

PWS-TO4-PA74: Contractor analysts shall produce the products in accordance with standard NIC operating procedures and with minimal oversight. The Contractor shall demonstrate product proficiency expertise via on the job training. Product proficiency demonstration shall not exceed the following durations:

● 3 months for snow and ice product for regional and hemispheric ice charts

● 3 months for SAR acquisition

On the job training shall not exceed the following duration

● 18 months of on-the-job training for regional and hemispheric ice charts

PWS-TO4-PA75: The Contractor shall perform routine NIC office tasks (e.g., answering the phone, logging shift items).

PWS-TO4-PA76: The Contractor shall continue to provide support during emergency situations.

Dismissal or Government closure announcements will not apply to Contractor NIC analysts, unless otherwise instructed by the on-site Government representative.

PWS-TO4-PA77: The Contractor shall perform special projects, when requested, under the direction of the Government (e.g. research collaborations, outreach, data analysis, and validation).

PWS-TO4-PA78: The Contractor shall participate in workshops and meetings in support of the NIC mission. The frequency of these events vary and are based on availability of funds.

PWS-TO4-PA79: The Contractor shall deploy to the remote (NIC IMS) COOP site given activation of a COOP event.

3.9.2.1 Operations and Maintenance for NIC’s, SIPAS and IMS Applications

PWS-TO4-PA80: The Contractor shall provide technical support to all applicable NIC systems to include both Satellite Image Processing and Analysis System (SIPAS) and IMS hardware and operating systems, network devices, servers, and workstations.

PWS-TO4-PA81: The Contractor shall establish and maintain a current Systems Inventory listing [Deliverable] containing all SIPAS devices/software in the hardware and software CI database(s).

PWS-TO4-PA82: The Contractor shall provide operations and customer support training to the NIC staff addressing the return to service hardware procedures.

3.9.3 Direct Services Branch (DSB) Support

The Direct Services Branch manages the satellite transmission services that provide operational data, derived products, and support for the worldwide direct readout community who are given free, unrestricted access to the scientific data directly from the NOAA satellites.

PWS-TO4-PA83: The contractor shall provide operations support for the systems related to the following services:

● HRIT/EMWIN

○ HRIT Broadcast Stream Service configurational changes within the PDA Portal

○ HRIT Broadcast subscription modifications, activations and deactivations

○ HRIT Broadcast Stream Virtual Channel allocation, activations and deactivations

○ Dartcom receiving stations configurational changes

● The contractor shall ensure that the following files are received by the FTS software and distributed through the PDA to the FTS software in the WOC within 1 hour of the files being made available:

○ NCEP files for FTS

○ NAVGEM files for FTS

○ NAAPS files for FTS

○ USNO files for FTS

○ GMASI files for FTS

○ Revolution Number Files

○ Other FTS files as defined by the Service Manager

● The contractor shall ensure that the following files are received by the FTS software and distributed through the PDA to the FTS software in the WOC within 1 day of the files being made available:

○ LUTs

○ PCTs

○ HRD Link Monitoring Reports

○ CrIS Correction Matrix Object

○ RSBAutoCal history aux file

○ VIIRS Gridded Snow Ice Cover Rolling IPs

○ VIIRS Global/Rolling 5-km NBAR NDVI Gridded IPs

○ VIIRS Land Surface Albedo Gridded IPs

○ Quarterly Surface Type IPs

○ Quarterly Surface Type/Land Water Mask IPs

○ Master Land Index Tile IPs

○ Other FTS files as defined by the Service Manager

● The contractor shall ensure that the ephemeris data, including TLEs and full ephemeris are received by the FTS software and distributed through the PDA to the FTS software in the WOC in a timely manner, at least 1 hour from the data being made available to the interface and within 1 day of generation.

● The contractor shall upload the current version of the Algorithm Development Library (ADL), RT-STPS software, algorithm release packages, and Direct Broadcast documents and technical specifications (as specified by the Government) and ensure they are available to FTS users within 1 week of them being made available.

● The contractor shall monitor the GNC-A receive stations at NSOF to ensure they are receiving products.

Table 2.Direct Service Monitoring

Service Monitored Operator available Action

NOAASIS

website

Normal working hours

Normal working hours, with a designated operator on call after hours

The contractor shall ensure that the links on the…