OMS_IDIQ_PWS__Nov_30_2017_DRAFT.docx

DRAFT OMS IDIQ PWS

National Environmental Satellite, Data, and Information Service (NESDIS) Office of Satellite and Product Operations (OSPO) and Office of Satellite Ground Services (OSGS) Draft Operations, Maintenance, and Sustainment (OMS) Indefinite Delivery/Indefinite Quantity (IDIQ) Performance Work Statement (PWS) Nov 30, 2017

Contents

The National Oceanic and Atmospheric Administration’s (NOAA’s) National Environmental Satellite, Data, and Information Service (NESDIS) provides satellite products, services, environmental information, and official assessments of the environment in support of societal and economic decisions. NESDIS satellite ground systems are the infrastructure for generating and distributing these satellite products and services. NESDIS satellite ground systems are entering a new era with the launch of the next-generation geostationary and polar-orbiting satellites. Both the Geostationary Operational Environmental Satellite “R” Series (GOES-R) Program and Joint Polar-orbiting Operational Satellite System (JPSS) Program include new ground systems for NESDIS.

This PWS describes services to operate, maintain, sustain and dispose of existing NESDIS legacy satellite ground systems until these new ground systems and their associated observatory constellations fully transition to operations. The contractor(s) selected shall migrate existing business functions to an enterprise ground architecture and use shared services as they become available for satellite operations.

Within NESDIS, the Office of Satellite and Product Operations (OSPO) and the Office of Satellite Ground Services (OSGS) requires operations, maintenance, sustainment and disposal support to our legacy ground systems. OSPO operates and OSGS maintains and sustains the ground systems covered in this PWS. NESDIS intends to sustain legacy ground systems through preventative maintenance, sparing, and failed component replacement (corrective maintenance) while actively managing performance risk and cost risk as the legacy systems approach retirement and disposal.

The broad scope of this work includes:

· Operational, maintenance, and sustainment support of NESDIS-deployed hardware, firmware, and software ground systems;

· Support of Satellite-to-Ground communications, including radio frequency (RF) and terrestrial communications networks, telemetry over Internet Protocol (IP), and RF antenna systems;

· Systems that support mission scheduling, ground system software/subsystem functions, and satellite command and control;

· Secure data ingest from both NOAA-operated satellite missions and external sources;

· Data Collection System (DCS) satellite services;

· Product generation, storage, monitoring, and distribution systems supporting new and improved satellite products, services, and algorithms;

· Provision of information to the National Centers for Environmental Information (NCEI) for archive and stewardship of these products.

· Program execution and delivery of services using National Institute of Standards and Technology (NIST) security control guidelines.

· Technical Baseline evolution, both Hardware and Software that changes components or adopts new technology.

Figure 1.1-2 illustrates the Federal Information Security Management Act (FISMA) defined systems and covered elements for this Contract.

Figure 1.1-2. NOAA NESDIS FISMA Systems/ Covered Contractual Elements Table 1.1-1 shows the ground systems that are within the scope of this contract. The items listed in Table 1.1-1 may be referred to as “assigned systems” within the body of this PWS.

Table 1.1-1 NESDIS Systems to be Operated, Maintained, and Sustained under this PWS

Table 1.1-2 lists Out-of-Scope Ground Mission Systems that are operated, maintained and sustained external to this contract, but their interfaces with Table 1.1-1 systems are in-scope.

Table 1.1-2 Out-of-Scope Ground Systems that Interface with In-Scope NESDIS Ground Systems

Search and Rescue Satellite aided Tracking System (SARSAT)

Comprehensive Large Array-data Stewardship System (CLASS)

Geostationary Operational Environmental Satellites (GOES) – R Series

Joint Polar Satellite System (JPSS)

Government Resources for Algorithm Verification, Independent Test and Evaluation (GRAVITE)

Table 1.1-3 shows administrative Local Area Network (LAN) systems that are operated, maintained and sustained external to this contract, but their interfaces with the Table 1.1-1 systems are in-scope.

Table1.1-3. Out-of-Scope Program Networks That Interface with In-Scope NESDIS Ground Systems

NOAA Environmental Satellite, Data and Information Service (NESDIS) Local Area Network (LAN), Silver Spring MD

Fairbanks Command and Data Acquisition Station (FCDAS) LAN, Fairbanks, AK

National Climate Data Center (NCDC) LAN, Asheville, NC

National Ocean Data Center (NODC) LAN, Silver Spring, MD

National Geophysical Data Center (NGDC) LAN, Boulder, CO

Center for SaTellite Applications and Research (STAR) LAN, College Park, MD

Wallops Command and Data Acquisition Station (WCDAS) LAN, Wallops Island, VA

A detailed list of NESDIS systems is in Appendix A1. Individual system inventories, drawings, descriptions and interfaces are available in the Bidder’s Library.

1.2 Place of Performance

Figure C.1.1-1 illustrates the NESDIS Ground Enterprise (NGE). Work locations for this contract are:

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

· OSGS Program Offices located in Greenbelt MD and Silver Spring, MD

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

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

· NESDIS Command and Data Acquisition (CDA) Stations located in Wallops VA, Fairbanks AK and Barrow AK

· NESDIS NCEI located in Asheville NC, Boulder CO, and Silver Spring MD

· The NESDIS Consolidated Back-up Unit (CBU) located in Fairmont, WV.

Figure C1.1-1. Representation of NOAA Satellites and Ground Systems

1.3 Activities

This Performance Work Statement (PWS) includes requirements and activities which the Contractor shall perform for NESDIS in the execution of the contract. Activities under this contract will include Operations, Maintenance, and Sustainment. The term “activities” will be used to mean any services or support functions performed by the Contractor and needed to fulfill the Operations, Maintenance or Sustainment requirements of this PWS. A “shall” statement will generally be prefaced by the type or nature of the activity such as, “The Contractor shall perform Maintenance Planning Activities on the Assigned Systems.” The specific activities and assigned systems will be defined in individual Task Orders (TO).

While this is not a development contract, certain development-like activities may be performed as part of sustainment. In addition, Integration and Test activities will be used to verify and validate changes made during both maintenance and sustainment activities. Technical and procedural performance metrics are listed in the Performance Requirements Summary (PRS).

Development activities are performed to create new systems and capabilities in support of NESDIS products and services via hardware, software and networking components, using a process that includes the following development phases:

· Determining system functional and performance requirements

· Designing system features to satisfy baselined requirements

· Documenting business rules and operations processes

· Acquiring hardware, software and communication services

· Writing new and/or modifying existing (including re-purposing) software code

· Installing and verifying the system in test and then operational facilities

· Transitioning the system to operations, including user training

1.4.2 Operations

Operations activities and functions are performed to ensure the efficient and effective command and control of satellites and selected reference climate networks, data acquisition from a spectrum of observing and computational systems, product generation, archive, product distribution and the execution of broadcast services. Operations are often supported on a 24 hours x 7 days x 365 days per year basis with defined remote back-up and contingency capabilities that ensure the high availability and reliability of products and services. NESDIS operations transform satellite and in-situ environmental observations into desired data and information products and related services that either create or deliver value to NOAA and other customers (both internal and external to NOAA).

Core functional areas of NESDIS satellite operations include:

· Support of launch, activation, and evaluation of new satellites

· Monitoring and verification of satellite health and status

· Configuration/commanding of satellites to meet user’s needs

· Detection, identification and assessment of satellite and ground system anomalies

· Managing, monitoring, and configuring associated ground segment elements

· Ensuring a secure operational environment

1.4.3 Maintenance

Maintenance activities are performed to ensure the continued operation of a system that has been formally transitioned to the operational organization where data or information are observed, transmitted, calibrated, processed, or distributed. Maintenance activities ensure that the overall system continues to meet scientific, technical, functional, and performance requirements in addition to availability and reliability requirements and that the appropriate security posture for the particular system is maintained. Types of maintenance include:

· Preventive Maintenance- changes to ground systems or software with the intent to prevent errors, problems or failures before they occur

· Corrective Maintenance- reactive (emergency) and/or routine (planned) fixes that are needed as a result of anomalies such as network and data outages, data format changes, hardware failures, security vulnerabilities and/or software problems

· Science Maintenance- calibration updates and algorithm changes necessary to ensure product quality or correct for unanticipated anomalies or artifacts

· Limited Scope Adaptive Maintenance- product and system modifications that can be performed by operations support personnel, and that maintain current system requirements and the controlled configuration and interfaces In all cases, system testing and regression testing is performed to verify the results of the maintenance action and to ensure that none of the modifications negatively impact the functional performance of the operational baseline system.

1.4.4 Sustainment

Sustainment activities are typically larger scale and preplanned activities performed to develop, modernize, or enhance components. Sustainment activities are conducted to reduce life cycle costs (or provide the best return on the investment), leverage technology advancements and improvements, improve the capability, reliability and robustness of the system, and extend the system life to meet program-life requirements.

Sustainment activities include the modernization (or technology refreshment) of existing hardware and software, and adding new capabilities to meet Government requirements. Sustainment activities may include:

· Developing, integrating, testing and implementing new or improved science algorithm or application capability, or a new sub-component of an existing system;

· Enhancing operations by improving existing system components or capabilities;

· Adding new capabilities to meet NOAA requirements to provide the best return on investments;

· Addressing life cycle issues, including the impacts of aging sensors (calibration adjustments), sensor and spacecraft anomalies, and the impacts of the gain of loss or data sources in order to maintain the highest quality (most accurate) products and services.

1.4.5 Integration and Test

Integration and Test (I&T) activities are performed within the development, sustainment and maintenance functions to bring individually-tested components of a new or modified system together into a subsystem or fully functioning system, and to verify that a particular system component, subsystem, or the system itself meets a set of new or modified requirements or capabilities. Verification methods include testing, demonstration, inspection, trending and analysis.

Test and demonstration are characterized by the detailed collection of data under a tightly controlled set of conditions and component configurations. Activities include:

· Implementing specialized testing environments as needed

· Detecting and resolving errors and anomalies

· Ensuring standards and governance compliance (statutory and policy) and interoperability among hardware and software systems

· Ensuring that hardware and software systems perform as designed, and understanding the impacts upon graceful degradation (e.g. loss of data sources, satellite failures, degraded hardware performance)

· Verifying the data streams, communications infrastructure (and fault detection) and generation of quality products and associated metadata and quality flags I&T activities also apply to non-operational systems supporting science, research & development, and research to operations functions.

The Department of Commerce relies on voluntary standards, both domestic and international, whenever feasible and consistent with law and regulation pursuant to law. Examples of voluntary standards include those provided by the American National Standards Institute (ANSI), the Institute for Electrical and Electronics Engineers Standards Association (IEEE-SA).

2.2 Department of Commerce Specifications

The Contractor shall operate, maintain and sustain a suite of systems already in operations. These systems are of varying levels of age and complexity. Most activities have pre-existing Standard Operating Procedures (SOP) to guide Contractor execution, which the Government will make available.

3. Requirements The Contractor shall:

· Provide subject matter expertise, personnel, material, equipment, services, and facilities necessary to perform and deliver operations, maintenance, and sustainment products and services in order to execute the contract with no interruption of services.

· Perform operations, maintenance, and sustainment activities at all program sites listed in section 1.2. for all systems listed in Table 1.1-1 including interfaces to systems listed in Tables 1.1-2 and 1.1-3.

· Provide personnel that possess professional and technical certifications commensurate with their responsibilities.

3.1 Program Management

PWS-PM01: The Contractor shall provide program/project management services and personnel to manage the contract. The Contractor shall provide and maintain a Program Management Plan [CDRL XX]. PWS-PM02: The Contractor shall provide and maintain a Microsoft (MS) Project-based Integrated Master Schedule (IMS) [CDRL XX]. The IMS shall include monthly Invoice and quarterly Contract Funds Status reporting dates. The initial IMS needs to include linked milestones for all contract transitions and task orders.

PWS-PM03: The Contractor shall provide a contract funds status to the Government quarterly for each task order. [CDRL XX].

PWS-PM04: The Contractor shall invoice the Government monthly under each individual task order.

PWS-PM05: The Contractor shall provide and maintain an annual Spend Plan for Government approval. [CDRL XX]. The Spend Plan shall run from 01 October through 30 September of the following fiscal calendar year and have monthly increments and milestones. The spending in the plan shall be presented in Work Year Equivalents (WYE) for labor and dollars in thousands to one decimal point for material procurements. The Spend Plan shall be updated monthly.

PWS-PM06: The Contractor shall provide to the COR a weekly Work Plan for Monday through Sunday no later than close of business (COB) the previous Friday. [CDRL XX] PWS-PM07: The Contractor shall support the Government use of the System Estimation Tool (SET), which is a cost estimation tool used in collaboration by NCEI. The Government uses a Government Furnished (GF)SET to produce cost estimates for transition of new or improved data products to operations. The SET is used cooperatively with NCEI to accurately cost needed upgrades to processing, storage, transmission and archive. Detailed cost estimates will be developed on a case-by-case basis.

PWS-PM08: The Contractor shall perform Engineering assessments (EA) identified and approved by the COR that include details related to system performance analysis, capacity planning, and cost estimates over the performance period. Deliverables from engineering assessments may result in technical direction letters or contract modifications depending on the scope and magnitude of the request [CDRL XX].

PWS –PM09: The Contractor shall provide and maintain a Staffing Plan [CDRL XX]. The staffing plan shall include an organization chart, and identified roles and responsibilities for positions requiring certifications. The Contractor personnel shall possess professional and technical certifications commensurate with their responsibilities. The Contractor shall provide personnel that qualify under the condition of SUITABILITY ASSESSMENT-ON SITE SERVICE SUPPORT.

PWS-PM10: The Contractor shall provide meeting management services to the Government. These services include scheduling meetings, creating meeting agendas, documenting meeting minutes for all attended meetings, tracking action items, distributing agendas, schedules, minutes and action items and posting them to the Government-designated location [CDRL XX] PWS-PM11: The Contractor shall provide trained staff to support the Government in the use of enterprise tools listed in Table 3.1-1.

The Government will provide to the Contractor’s personnel on-site familiarization with the Government’s implementation of the enterprise tools.

Enterprise Configuration Management Tool (ECMT) [IBM ClearCase / ClearQuest]

Customer Relationship Management (CRM) Solution

Table 3.1-1 Government Furnished Enterprise Tools PWS-PM13: The Contractor shall provide completed travel request forms for non-emergency travel to the COR no less than 14 business days prior to the first day of planned travel.

PWS-PM14: The Contractor shall travel to work sites to support operations, maintenance and sustainment activities in accordance with the Federal Travel Regulations (FTR).

The Government may require additional levels of approval for Government funded travel to attend or support conferences, workshops and meetings. The Contractor should plan on submitting those requests as early as possible.

3.1.1 Systems Engineering Management

PWS-SE01: The Contractor shall provide and maintain a Systems Engineering Management Plan (SEMP). [CDRL XXX]. The SEMP shall describe how the Contractor will apply Systems Engineering tools and principles to the execution of operations, maintenance and sustainment of the assigned systems. The SEMP shall describe the Contractor’s Technical Review Processes. The SEMP shall describe the Contractor’s process improvement efforts.

PWS-SE02: The Contractor shall support the Government’s Engineering Review Board (ERB) by providing an Executive Secretary experienced with the Engineering Review process.

PWS-SE03: The Contractor shall provide Technical Writing Services to the Government. These include text and graphics, formatting, editing, proofreading, printing, faxing, copying and file conversion.

3.1.2 Configuration and Asset Management

The Government performs Configuration Control and Management following the guidelines provided in the NOAA/NESDIS/OSGS 5820.02A Change and Configuration Management Process Document. The Government will provide IBM Rational ClearCase / ClearQuest based Enterprise Configuration Management Tool (ECMT) to track hardware and software configuration items.

PWS-CM01: The Contractor shall assist the Government in operating and maintaining the ECMT.

PWS-CM02: The Contractor shall submit Configuration Change Documentation for all changes made during maintenance and sustainment of Hardware and Software.

The Government will provide a Microsoft SharePoint based document management system.

PWS-CM03: The Contractor shall assist the Government in operating and maintaining the Microsoft SharePoint tool.

PWS-CM04: The Contractor shall manage and maintain the NSOF Library in accordance with the NSOF Library SOP.

PWS-CM05: The Contractor shall provide “Book-Bosses” for all operating procedures, documents, diagrams, data sets, configuration files and technical data packages used in the operations, maintenance and sustainment of assigned systems.

The Book-Boss will track configuration change requests to their assigned materials and make recommendations to the Government for when they should issue a new revision of the materials i.e. “Roll a Rev.”.

PWS-CM06: The Contractor shall submit Document Change Request forms.

Operations, Maintenance and Sustainment Documentations is varied and extensive. It includes operating procedures, documents, diagrams, data sets, configuration files, build forms, network diagrams, operational event logs, data flow diagrams, computer room rack layouts, operations checklists, program descriptions, security audit logs, firewall rules, system descriptions, interface control documents, system security plans, software and hardware inventories, IT security artifacts, Memoranda, maintenance manuals, contractual documentation and technical data packages.

PWS-CM07: The Contractor shall support the Government Configuration Control Board by providing an Executive Secretary experienced with Configuration Control and Management processes.

PWS-CM08: Within TBD days of contract award, the Contractor shall perform a Physical Configuration Audit (PCA) of all Assigned Systems down to the Configuration Item level.

PWS-CM09: Within TBD days of PCA completion, the Contractor shall reconcile the PCA results of all Assigned Systems with existing property management (Sunflower), Information Technology (IT) Security hardware inventories and the Enterprise Technical Architecture Infrastructure Reference Model.

PWS-CM10: Within TBD days of PCA completion, the Contractor shall reconcile the PCA results of all Assigned Systems with existing software license management lists, IT Security software inventories and the Enterprise Technical Architecture Applications Reference Model.

The reconciled hardware and software inventories constitute the Contractor's Configuration Management Baseline (CMB) for Assigned Systems going forward.

PWS-CM11: The Contractor shall maintain the CMB in the ECMT.

PWS-CM12: The Contractor shall reconcile the CMB against monthly security scans of assigned systems. [CDRL XX] PWS-CM13: The Contractor shall reconcile the CMB against the annual property inventory. [CDRL XX] It is likely that a number of discrepancies will exist between the CMB and the Reference Models. Reducing or removing these differences may lead to long-term cost savings and such opportunities should be explored.

PWS-CM14: The Contractor shall recommend to the Government a “Technical Architecture Get-Well Plan” to reduce the number of discrepancies between the CMB and the Infrastructure and Applications Reference Models. [CDRL XX] PWS-CM15: The Contractor shall assist the Government in managing software license agreements.

PWS-CM16: The Contractor shall assist the Government in managing hardware warranty agreements.

3.1.3 Property Management

PWS-CM17: The Contractor shall perform shipping and receiving functions for all equipment, spare parts and items for return to vendors, suppliers and repair facilities.

Shipping and Receiving activities include assembling items, containers, boxes and crates to be shipped and prepare identifying information and shipping instructions; unpack and route items received to appropriate storage areas; and shipment of packages to required locations using Government –provided carrier shipping accounts. A Contractor Property Contact shall be designated to assist in the management of acquiring, inventorying, and disposing of NOAA property assigned to the custodial area.

PWS-CM18: The Contractor shall provide support to the Government for property management.

Property Management support functions include: records maintenance; labeling, and processing documentation related to personal property and/or ensuring personal property use for official purposes only; support to the annual property inventory; identify excess property; assist and records reconciliation of physical inventories; and assist with property recovery for outbound employees.

3.1.4 Quality Assurance Program

PWS-QA01: The Contractor shall provide and maintain a list of voluntary standards with which they comply and their level of compliance or certification. [CDRL XX] PWS-QA02: The Contractor shall provide, maintain and track their performance against a Quality Assurance Plan (QAP). [CDRL XX] The QAP explicitly describes the Contractor processes and measures for subcontractors and vendor accountability in their performance on the contract. The PRS will define technical and process performance measures for the contract activities.

PWS-QA03: The Contractor shall support the Government’s process improvement activities.

The Government will provide a SharePoint-based Action Information Management System (AIMS) for organizing data calls.

PWS-QA04: The Contractor shall support organizational data call requests.

3.1.5 Risk Management

PWS-RM01: The Contractor shall comply with the OSGS Risk, Issue and Opportunity Process Document, OSGS 5820.04A (October 3, 2016).

PWS-RM02: The Contractor shall provide support to the Government in the operation of the Active Risk Manager (ARM) tool.

PWS-RM03: The Contractor shall collaborate with the Government on Risk Management, reporting risk status at Monthly Contract Status Reviews.

3.1.6 Contract Transition

Transition of prior contracts to this contract shall be a key managed activity by the Contractor in coordination with the Government. The Contractor shall achieve a smooth transition of work performance from the incumbent contractor(s) to itself for any designated contracts. This includes transition training with no interruption in services to on-going operational services (e.g. staffing, training, transfer of operations, maintenance and sustainment performance, transfer of inventory and configuration control, administration, security, transfer of all accounts, passwords, permissions and system permissions, communication of expiration dates for licenses and warranties, Book Boss custodianship of all data sets, software scripts, documentation, procedures, and checklists).

PWS-CT01: The Contractor shall provide a contract Phase-in Transition Plan with checklist [CDRL XX].

PWS-CT02: The Contractor shall report Phase-In Transition Status weekly.

Transition of this contract for continued post-contract operations, maintenance, and sustainment shall be a key managed activity by the Contractor in coordination with the Government. The Contractor shall accurately and effectively communicate and transfer all activities to a new contractor at the end of the period of performance with no interruption to operations or services. The Phase-out Transition shall include all activities of the existing contract (e.g. staffing, needs, training, transfer of operations, maintenance and sustainment performance, transfer of inventory and configuration control, administration, security, transfer of all accounts, passwords, permissions and system permissions, communication of expiration dates for licenses and warranties, Book Boss custodianship of all data sets, software scripts, documentation, procedures, and checklists).

PWS-CT03: The Contractor shall deliver a Contract Phase-Out Transition Plan [CDRL XX].

PWS-CT04: The Contractor shall report Phase-Out Transition Status weekly.

3.2 Operations

The Government will provide infrastructure and procedural details to the Contractor sufficient for the safe and effective execution of deployed system activities assigned to the Contractor’s personnel.

PWS-OP01: The Contractor shall perform and support operations activities and functions to ensure the efficient and effective command and control of satellites and selected reference climate networks, data acquisition from a spectrum of observing and computational systems, product generation, archive, product distribution and the execution of broadcast services.

PWS-OP02: The Contractor shall provide operations support on a 24x7x365 basis with defined remote back-up and contingency capabilities, while ensuring the high availability and reliability of products and services.

PWS-OP03: The Contractor shall provide operations support for core functional areas of satellite operations.

Core Functional Areas include:

· Launches and transition to operations activities.

· Monitoring and verification of satellite health and status.

· Configuration/commanding of satellites to meet user’s needs.

· Detection, identification and assessment of satellite and ground system anomalies.

· Managing, monitoring, and configuring the associated ground segment element.

· Ensuring a secure operational environment.

PWS-OP04: The Contractor shall provide daily operational support activities associated with managing a satellite command and control center and product processing environment.

Operational Support Activities include:

· Satellite Launch and Commanding Activities

· Help Desk Services to Operations and Satellite Product Users

· Systems and Product Analysis Support during Operational Anomalies

· Network, Systems, Workstation, Printer and Satellite Hardware Support

· Data Center Infrastructure Management

· Antenna Operations Support

· Network and Security Monitoring

· Continuity of Operations (COOP)

· Operations Training

PWS-OP05: The Contractor shall assist the Government in maintaining the accuracy of SOPs.

PWS-OP06: The Contractor shall assist the Government in maintaining the accuracy of the Operational Systems’ Configuration Files.

3.3 Maintenance

3.3.1 Maintenance Activities

PWS-MN01: The Contractor shall perform maintenance activities on all assigned systems.

PWS-MN02: The Contractor shall provide the resources and labor necessary to successfully complete maintenance tasks.

PWS-MN03 The Contractor shall document changes to the system at the configuration item level in accordance with SOP and Configuration Control processes.

PWS-MN04 The Contractor shall maintain the assigned systems such that they remain compliant with technical, functional, performance, availability, reliability, and security requirements and specifications.

PWS-MN05: The Contractor shall support all required communications methods to the Government to assure prompt continued status (through a variety of means) of systems being maintained.

3.3.1.1 Network & Systems Administration

PWS-MN06: The Contractor shall provide system and network administration maintenance-related activities, including:

1. Perform system and network administration functions

2. System and network patch management

3. Coordination with the Government on system and network maintenance with vendors

4. Updates to the latest releases or versions of system and network operating systems

5. Disaster recovery activities, such as backups, migrations, and dumps of libraries and files

6. Routine status reporting to the COR regarding server and storage usage.

3.3.2 Capacity Planning

PWS-MN07: The Contractor shall conduct performance or capacity management activities.

Performance and Capacity Management activities include:

1. Studies required by the Government

2. Document Capacity Planning and Performance Management procedures that meet processing requirements. This planning shall ensure changes to servers/computers or peripherals do not adversely impact OSPO system operations.

3. Monitor and report of component performance, utilization, and efficiency; ensure system capacity and storage are sufficient to handle current and future operational data volume and processing requirements and meet the metrics

4. Manage component resources (e.g., devices and traffic) to meet defined availability and performance service levels

5. Ensure information management practices and existing IT infrastructure keep pace with each other

6. Component tuning to maintain optimum performance

7. Develop and implement improvement plans

3.3.3 Telecommunications Support

PWS-MN08: The Contractor shall coordinate with telecommunications vendors, customers, partners, leased circuit providers and other mission systems to troubleshoot network problems, outages, or any other issues impacting a service level agreement.

3.3.4 Preventative and Corrective Maintenance

PWS-MN09: The Contractor shall perform preventative and corrective maintenance, modifications, planned and unplanned activities on all systems, and maintain a spares depot for systems listed in Table 1.1-1 at all work locations. This includes the following functions:

1. Provide and maintain a Preventative Maintenance Plan [CDRL XX];

2. Creation and delivery for Government approval work packages (inclusive of material procurements and test plans) [CDRL XX];

3. Quarterly visual inspections of all equipment;

4. Correcting error conditions per a Help Desk ticketing process;

5. Perform preventative maintenance on a quarterly basis; coordinate all maintenance schedules and timelines

6. Identify system components and software within one year of obsolescence;

7. Perform all software maintenance functions, patching and software compliance;

8. Provide IT security maintenance support,

9. Planned and unplanned maintenance,

10. Standard operating procedures

11. Recommend load balancing improvements,

12. Specialized imagery-scheduling program.

13. Maintain all Government databases.

14. Update diagrams of all WAN and LAN data communication connections 15, Maintain current satellite operations ground system equipment within acceptable quality levels

16. Manage/perform spares depot level repairs, and the return of defective equipment to vendor for repair or replacement

3.3.5 Installation, De-installation and Relocation

PWS-M7: The Contractor shall provide all schedules for Government approval, and perform all equipment upgrades, installations, de-installations and relocations within the scheduled allotted times; ensure no equipment is damaged during installations, de-installations, or relocations; and ensure 100% of all installations and relocations comply with building and electrical codes (e.g., National Electrical Code).

PWS-M08: The Contractor shall provide to the authorized Government official for approval a schedule for the implementation of any new hardware installations. The Contractor shall install new hardware after receiving written Government approval.

3.3.6 Web Development Support

PWS-M09: The contractor shall manage and maintain mission and product webpages and associated content and content delivery services and accounts.

3.3.7 Antenna Maintenance Support

PWS-M10: The Contractor shall provide all support to perform maintenance activities on NOAA antenna systems in Appendix X2. Antenna support shall only be provided at NSOF. WCDAS and FCDAS have existing support located onsite.

PWS-M011: The Contractor shall process and implement an Antenna System Maintenance Plan for the 9.1m antenna system, listing daily, weekly, monthly, semi-annual, annual, and any needed inspections necessary [CDRLXX]. The Contractor shall maintain and submit Antenna System Maintenance Records documenting the maintenance tasks performed on the 9.1m antenna systems.

3.4. Sustainment

3.4.1. Obsolescence Prevention and Remediation

PWS-SU01: Within TBD days of PCA completion and annually thereafter, the Contractor shall identify all system hardware components and software within 1 year of obsolescence.

PWS-SU02: The Contractor shall provide and maintain a Preventative Maintenance Plan to replace the obsolete hardware and software identified above. [CDRL XX] The Preventative Maintenance Plan will include Integration, Test and Check-out procedures sufficient to verify and validate post-maintenance system performance.

3.4.2. Sustainment Support

Sustainment activities are part of a 5-year rolling Government plan associated with scheduled technology refresh windows, enterprise convergence and shared services implementations. As part of the Contractor’s Annual Spend Plan development, the Government and Contractor will reconcile the Contractor’s Preventative Maintenance Plan and the Government’s 5-year Sustainment Plan with available funding to determine a prioritized list of sustainment tasks for the coming year.

PWS-SU03: The Contractor shall track sustainment tasks in the IMS using bi-weekly milestones.

Sustainment task plans and procedures shall be in accordance with SOPs and provide a level of detail and verification commensurate with the cost and complexity of the task. The Government will approve scheduled sustainment activities and provide a minimum of one person per shift who is authorized to approve sustainment activities. Sustainment tasks shall not interfere with or compromise mission system operations.

PWS-SU04: The Contractor shall obtain approval of the Contracting Officer’s Representative (COR), Contract Technical Point of Contact (TPOC) or their designated representative immediately prior to commencing sustainment work.

PWS-SU05: The Contractor shall complete Configuration Change Requests to update all affected documentation, drawings and procedures within 24 hours of completing any sustainment activities.

3.4.1 Sustainment Test and Integration

Assigned Systems are software-intensive and will likely require frequent patching and updating for both operational and security purposes. Successful execution of this PWS will require the Contractor to assist the Government in fast and effective patching, integrating, compiling and testing of small to medium software changes of simple to moderate complexity. If large or complex software development is needed, the Government will write a separate task order.

Sustainment integration and testing will take place in specified test environments after all documentation and peer reviews are successfully completed. Testing for changes that provide new program scope shall include an end-to-end test that exercises the customer interface per the Interface Requirements Document (IRD) or Interface Control Document (ICD). System tests shall include testing with customer-provided data in a testing environment that is reflective of the customer’s operational environment. Test plans for new capability shall be approved by the Government in advance.

Upon successful completion of test environment testing and Government receipt and approval of the test results, software changes may be deployed into the deployment environment. After the Government verifies successful installation, deployment testing will follow.

PWS-SU06: The Contractor shall perform software integration in accordance with documented and approved plans after formal software peer review.

PWS-SU07: The Contractor shall permit the Government to observe all software testing.

PWS-SU08: The Contractor shall provide the Government with detailed test plans, test steps, test data sources, and expected outcomes, for review and approval no less than two weeks prior to testing.

PWS-SU09: The Contractor shall coordinate proposed system acceptance test schedules with the Government.

PWS-SU10: The Contractor shall maintain all documentation of test results and daily test logs throughout the release, integration and testing phases.

PWS-SU11: At the successful completion of system testing, the Contractor shall provide all test results and/ documentation to the Government

3.4.2 User Access Sustainment

PWS-SU12: The Contractor shall provide and maintain an interactive website which maintains spacecraft events and spacecraft changes.

PWS-SU13: The Contractor shall support website user access sustainment services.

PWS-SU14: The Contractor shall coordinate with the Government to collect web site system requirements.

PWS-SU15: The Contractor shall provide and maintain a mobile version of the website.

PWS-SU16: The Contractor shall consolidate common website information, ensuring data accuracy.

3.4.3 Training

PWS-SU17: The Contractor shall provide personnel that are trained on and experienced in the activities they support.

PWS-SU18: The Contractor shall assist the Government in identifying training for Government and Contractor personnel that will improve operations, maintenance and sustainment of assigned systems.

PWS-SU19: The Contractor shall provide training to Government personnel on substantive changes made to assigned systems in the course of maintenance and sustainment.

3.5. Information & Cyber Security Support

Information and cyber security services for DOC NOAA systems will be implemented on a separate contract vehicle. The scope of Information and cyber security support for this contract is to support the OSPO IT Security Program by providing scans, patching, hardening, implementing technical security controls, artifacts for security controls assessments, and technical POA&M milestones.

3.5.1 Information and Cyber Security

PWS-ICS01: The Contractor shall coordinate with NOAA/OSPO’s Information and Cyber Security program’s designated point of contact to assist in implementing the required security controls to ensure confidentiality, integrity and availability of the information resources integral to the successful operation of OSPO satellite and product processing systems.

3.5.2 Security Continuous Monitoring and Situation Awareness

PWS-ICS02: Incident Response (IR): The Contractor shall coordinate and report remedial actions in response to IT Security events or incidents to the NOAA Cyber Incident Response Team (N-CIRT) within the required 24-hour period or as specified in the OSPO Incidence Response (IR) Plan.

PWS-ICS03: Incident Response (IR): The Contractor shall coordinate and report remedial actions in response to IT Security events or incidents to the NOAA Cyber Incident Response Team (N-CIRT) within the required 24-hour period or as specified within the OSPO IR plan.

PWS-ICS04: System and Network Monitoring (SI): The Contractor shall complete monitoring activities of Tier 2 system and security logs, and report issues through applicable means.

PWS-ICS05: System and Network Monitoring (SI): The Contractor shall complete monitoring activities of IT systems and security logs, and report issues through applicable means.

PWS-ICS06: Audit and Logging (AU): The Contractor shall review system monitoring logs and complete reports as documented in the System Security Plans. Vulnerability Assessment (RA):

PWS-ICS07: The Contractor shall complete required vulnerability assessment activities, including authenticated monthly and quarterly scans and reporting.

PWS-ICS08: The Contractor shall deliver completed scan reports to NESDIS by the 1st day of each month for monthly vulnerability scans and website scanning and vulnerability scans on the 15th day of the third month of quarterly scans of the fiscal quarter (12/15/YY, 3/15/YY, 6/15/YY, 9/15/YY), or as modified by NESDIS.

PWS-ICS09: The Contractor shall maintain and update scanning plugins for associated vulnerabilities at least monthly.

PWS-ICS10: 4 The Contractor shall maintain and update scanning product and associated vulnerability at least monthly.

PWS-ICS11: The Contractor shall provide qualified individuals to operate NESSUS; the NOAA standard vulnerability scanning tool. In some cases, other scanning tools may be used for specific components.

PWS-ICS12: The Contractor shall implement federal guidelines for CyberScope reporting as directed by DOC, NOAA, NESDIS, or OSPO policy.

PWS-ICS13: The Contractor shall maintain a Scanning Exclusion List of system components excluded from automated vulnerability scanning due to age, mission, or technical considerations; update and publish monthly through the OSPO Configuration Management process.

PWS-ICS14:The Contractor shall assess all components identified on the Scanning Exclusion List for vulnerabilities using other technical means, including manual evaluation and testing; complete assessments as part of scheduled monthly and quarterly vulnerability assessments.

PWS-ICS15:The Contractor shall remediate for vulnerabilities all components identified on the Scanning Exclusion List.

3.5.2.1 Contingency Planning (CP):

PWS-ICS16: The Contractor shall maintain system Disaster Recovery/COOP plans and publish updated plans semi-annually or as established by NOAA policy, and accurately document contingency activities and include in plan updates.

PWS-ICS17: The Contractor shall coordinate with the OSPO IT Security Program to maintain the Contingency Plan Test Plan and Report (CPTPR) documentation and update semi-annually or as required.

PWS-ICS18: The Contractor shall participate in quarterly Contingency Plan training; ensure all staff complete CP training at least semi-annually.

PWS-ICS19: The Contractor shall test the system Contingency Plan annually; test system backup procedures quarterly; and fully document as part of annual Contingency Plan testing.

3.5.2.2 Flaw Remediation (SI)

PWS-ICS20: The Contractor shall identify and report information system vulnerabilities;

PWS-ICS21: The Contractor shall mitigate information system vulnerabilities;

PWS-ICS22: The Contractor shall test software updates related to flaw remediation for effectiveness and potential side effects on all affected OSPO systems before installation;

PWS-ICS23: The Contractor shall maintain and implement DOC, NOAA, or OSPO flaw remediation tools where applicable;

PWS-ICS24: The Contractor shall document in the SSP any component that cannot be patched including reasons such as: due to age, mission, or technical impact.

3.5.2.3 Malicious Code Protection (SI)

PWS-ICS25: The Contractor shall identify and document specific components unable to implement anti-malware protections. If a component cannot implement this control due to age or mission impact, document the technical, operational considerations, mitigation in the SSP, and request risk acceptance through the FIPS 200.

3.5.3 Security Program Management

3. 5.3.1 Security Awareness & Training

PWS-ICS26: All Contractor personnel shall complete all NOAA required Training on schedule, including: No FEAR Act Training, NOAA Safety Awareness Training, NOAA Safety and Environment Awareness Training, NOAA IT Security Awareness Training.

PWS-ICS26: All Contractor staff shall complete required Role-Based Security Training by 30 days before the NOAA required deadline each fiscal year.

3.5.3.2 Security Assessment & Authorization (CA)

3.5.3.2.1 Continuous Monitoring and Assessment & Authorization (A&A):

PWS-ICS27: The Contractor shall support processes that enable OSPO to achieve compliance with Government security mandates and obtain/maintain an Authority to Operate (ATO) for each system.

PWS-ICS28: The Contractor shall submit assigned SCA artifacts on time.

3.5.3.2.2 Plans of Action & Milestones (POA&M) Management:

PWS-ICS29: The Contractor shall manage technical POA&M milestones using OSPO’s Configuration Management program, including automated tools.

3.5.3.2.3 System Interconnection:

PWS-ICS30: The Contractor shall support information requests for all system Interconnection Security Agreements.

3.5.3.2.4 System Security Documentation:

PWS-ICS31: The Contractor shall support information requests for Security Authorization Package for all assigned OSPO systems, including all required documents identified below, and additional information or documentation required by updates to Commerce, NOAA, NESDIS, or OSPO policies and procedures.

3.5.3.3 Security Support for SE and Change & Configuration Management PWS-ICS32: The Contractor shall comply with configuration management requirements per section 3.1.2 of this PWS image1.png image2.png