OMS_Task_Order_1_PWS_for_Program_Management_-Draft_03-07-2018.pdf

DRAFT OPERATIONS, MAINTENANCE, AND SUSTAINMENT

TASK ORDER 01 PWS - PROGRAM MANAGEMENT

Source Selection Information – See FAR 2.101 and 3.104-4 1

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) Task Order 01

Performance Work Statement (PWS)

March 7, 2018

Source Selection Information – See FAR 2.101 and 3.104-4 2

Table of Contents

1.0 Overview 3

2.0 Scope 3

2.1 Program Management 3

2.1.1 Systems Engineering Management 6

2.1.2 Configuration and Asset Management 6

2.1.3 Property Management 8

2.1.4 Quality Assurance 8

2.1.5 Risk Management 9

2.1.6 Training 9

2.1.7 Cyber Security Program Management 9

2.2 Contract Transition 10

Source Selection Information – See FAR 2.101 and 3.104-4 3

1.0 Overview

The Office of Satellite and Product Operations (OSPO) and the Office of Satellite Ground Services (OSGS) have shared responsibilities in managing satellite ground systems and product processing systems. OSPO operates and OSGS maintains and sustains these ground systems.

This Task Order 01 performance work statement (PWS) specifies the program management requirements for managing the ground systems support functions.

2.0 Scope

This Task Order 01 PWS specifies the Program Management requirements to support the operations, maintenance, and sustainment of all the NESDIS ground segments within the OMS contract including: project management, schedule, deliveries, financial operations and cost management, staffing management, configuration management, systems engineering support, asset management and related inventories and audits, purchasing and hardware/software license management, quality management, risk management, training requirements, and contract transition management.

The work locations for this task order include:

● 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

2.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 Contract Program Management Plan [CDRL] to address each task order.

PWS-PM02: The Contractor shall provide and maintain a monthly Integrated Master Schedule (IMS) [CDRL]. The IMS shall include all deliverables and monthly Invoice and quarterly Contract Funds Status reporting dates. The initial IMS must include linked milestones for all contract transitions and task orders, and external dependencies.

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

Source Selection Information – See FAR 2.101 and 3.104-4 4

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]. The Spend Plan shall run from 01 October through 30 September of the following fiscal 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 purchases. The Spend Plan shall be updated monthly.

PWS-PM06: The Contractor shall provide a weekly work Plan covering Monday through Sunday for each task order no later than close of business (COB) the previous Friday. [CDRL]

PWS-PM07: The Contractor shall support the Government use of the OSPO Enterprise Configuration Management Tool (ECMT) to estimate work hours. The Government uses ECMT to monitor work hours for operations, maintenance, and sustainment support. ECMT is used cooperatively to accurately estimate work hours needed for helpdesk tickets, work requests, and configuration changes.

PWS-PM08: The Contractor shall perform Engineering assessments (EA) [CDRL] 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.

PWS -PM09: The Contractor shall provide and maintain monthly a contract Staffing Plan [CDRL]. 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.

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.

Source Selection Information – See FAR 2.101 and 3.104-4 5

Function / Guidance Tool(s) [Vendor/Basis]

Requirements Management / OSGS 5820.03A Requirements Management

Process

Dynamic Object Oriented Requirements System (DOORS) [IBM Rational]

Risk Management / OSGS 5820.04A Risk, Issue and Opportunity Management

Process Document

Active Risk Manager (ARM) [Sword – ActiveRisk]

Asset Management & Configuration Control / OSGS 5820.02A Change and

Configuration Management Process Document

Sunflower Systems Enterprise Configuration Management Tool

(ECMT) [IBM ClearCase / ClearQuest]

Enterprise Help Desk Enterprise Scheduler System Customer Relationship Management

(CRM) Solution

Table 3.1-1 Government Furnished Enterprise Tools

PWS-PM12: 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-PM13: 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.

PWS-PM-14: The Contractor shall provide metrics, track, and report the status of all program deliverables for all task orders. In addition to any specified content requirements for deliverables, the content for all Task Order deliverables shall be mutually agreed. Contractor format is acceptable where not explicitly stated.

PWS-PM-15: The Contractor shall provide reports submitted to the CO and COR, in electronic format. The Contractor shall work with numerous file formats, including Microsoft Office® (.doc, .xls, .ppt, .mpp. .pdf, VISIO, and XML). The frequency of submission of program deliverables will be specified in each task order.

Source Selection Information – See FAR 2.101 and 3.104-4 6

2.1.1 Systems Engineering Management

PWS-SE01: The Contractor shall provide an initial Systems Engineering Management Plan (SEMP) [CDRL] with the proposal response, and maintain it as required. The SEMP shall describe how the Contractor will apply Systems Engineering tools (SET) and principles to the execution of operations, maintenance and sustainment of the assigned systems, as well as technical review processes, and 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.

2.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 a IBM Rational ClearCase / ClearQuest based Enterprise Configuration Management Tool (ECMT) to track hardware and software configuration items (CI).

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 operations, 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 all assigned systems.

Source Selection Information – See FAR 2.101 and 3.104-4 7

The Book-Boss will track configuration change requests (CCR) 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 documentation 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 30 days of Task Order award, the Contractor shall perform a Physical Configuration Audit (PCA) of all Assigned Systems down to the CI level.

PWS-CM09: Within 60 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 60 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 and the enterprise configuration management tool of the assigned systems. [CDRL XX]

PWS-CM13: The Contractor shall reconcile the CMB against the annual property inventory.

[CDRL]

Source Selection Information – See FAR 2.101 and 3.104-4 8

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 provide a Technical Architecture Get-Well Plan to the Government no later than 90 days after contract start. This plan shall document any recommended approach to reduce the number of discrepancies between the CMB and the Infrastructure and Applications Reference Models. [CDRL]

PWS-CM15: The Contractor shall support the Government in managing software license agreements.

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

2.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. The designated Contractor Property Contact provides assistance in the management of acquiring, determining inventory, and disposing of NOAA property assigned to the custodial area.

PWS-CM18: The Contractor shall perform the functions of a NOAA Property Contact.

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 record reconciliation of physical inventories; and assist with property recovery for outbound employees. [NOAA Property _Bulletin_001_FY2016]

2.1.4 Quality Assurance

PWS-QA01: The Contractor shall provide and maintain a list of voluntary standards with which they comply and the level of compliance or certification. [CDRL]

PWS-QA02: The Contractor shall provide their methods and processes in a Quality Assurance Plan (QAP) [CDRL]. The QAP shall be delivered as part of the proposal response. The QAP

Source Selection Information – See FAR 2.101 and 3.104-4 9 explicitly describes Contractor processes, as well as measures for subcontractors/vendor accountability in their performance on the contract.

PWS-QA03 The Contractor shall maintain and track contract performance, and metrics per as part of the monthly program management review.

PWS-QA04: 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-QA05: The Contractor shall support organizational data call requests.

2.1.5 Risk Management

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

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

PWS-RM03: The Contractor shall collaborate with the Government on Risk Management activities and report risk status at Monthly Contract Reviews.

2.1.6 Training

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

PWS-TR02: 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-TR03: The Contractor shall provide training to Government personnel on substantive changes made to assigned systems in the course of operations, maintenance, and sustainment.

2.1.7 Cyber Security Program Management

2.1.7.1 Cyber Security Awareness & Training

PWS-ICS01: All Contractor personnel shall complete all NOAA required training, including, but not limited to: No FEAR Act Training, NOAA Safety Awareness Training, NOAA Safety and Environment Awareness Training, NOAA IT Security Awareness Training.

Source Selection Information – See FAR 2.101 and 3.104-4 10

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

2.1.7.2 Cyber Security Assessment & Authorization

2.1.7.2.1 Continuous Monitoring and Assessment & Authorization (A&A)

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

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

2.1.7.2.2 Plans of Action & Milestones (POA&M) Management

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

2.1.7.2.3 System Interconnection

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

PWS-ICS06: The Contractor shall review and implement connections IAW Interface Control Documents (ICD) and report any discrepancies or needed changes to the Government.

2.1.7.2.4 System Security Documentation

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

2.1.7.3 Security Support for Systems Engineering and Change & Configuration Management

PWS-ICS08: The Contractor shall comply with configuration management requirements per section 3.1.2 of this PWS.

2.2 Contract Transition

The transition of an expiring contracts scope to the OMS contract is a programmatic activity managed by the Contractor and incumbent contractor, in coordination with the

Source Selection Information – See FAR 2.101 and 3.104-4 11

Government. The Contractor shall accurately and effectively communicate and transfer all activities to the new contractor(s) at the end of the period of performance.

PWS-CT01: The Contractor shall achieve a smooth transition of work performance from the incumbent contractor(s) to itself for any assigned system. The Contractor shall manage the transition with no interruption in ongoing services. Typical ongoing activities in transition include:

● Staffing

● Training

● Transfer of operations, inventory, and assets transfer of accounts, passwords, and permissions

● Monitoring of maintenance and sustainment activities

● Configuration control, administration, Book Boss custodianship of data sets, software scripts, documentation, procedures, and checklists

● IT Security activities

● Hardware and software license management, and warranty activity

PWS-CT02: The Contractor shall provide a contract Phase-in Transition Plan with checklist. The initial shall be submitted with the proposal response, and a final 30 days after award. [CDRL].

PWS-CT03: The Contractor shall report Phase-In Transition status weekly.

PWS-CT04: The Contractor shall deliver a Contract Phase-Out Transition Plan [CDRL] outline one year prior to the end of the contract. This plan shall include all existing contract activities including

● Staffing

● Training

● Transfer of operations, inventory, and assets transfer of accounts, passwords, and permissions

● Monitoring of maintenance and sustainment activities

● Configuration control, administration, Book Boss custodianship of data sets, software scripts, documentation, procedures, and checklists

● IT Security activities

● Hardware and software license management, and warranty activity