Task Order 1 PWS for Program Management.pdf

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

Office of Satellite and Product Operations (OSPO) and

Office of Satellite Ground Services (OSGS)

Draft Program Management Task Order 1

Performance Work Statement (PWS)

November 22, 2019

DRAFT OPERATIONS, MAINTENANCE, AND SUSTAINMENT (OMS)

TASK ORDER 1 PWS - PROGRAM MANAGEMENT

Table of Contents

1.0 Overview 3

2.0 Scope 3

2.1 Place of Performance 3

2.2 References 3

3.0 Requirements 4

3.1 Program Management 4

3.1.1 Configuration and Document Management 7

3.1.2 Quality Assurance 9

3.1.3 Risk Management 9

3.1.4 Training 10

3.1.5 Cyber Security Program Management 10

3.1.5.1 Cyber Security Awareness & Training 10

3.1.5.2 Cyber Security Assessment & Authorization 11

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

3.1.5.2.2 Plans of Action & Milestones (POA&M) Management 11

3.1.5.2.3 System Interconnection 11

3.1.5.2.4 System Security Documentation 11

3.1.5.3 Security Support for Systems Engineering and Change & Configuration Management 11

3.1.5.4 Cyber Security Management and Oversight 11

4.0 Contract Transition 12

5.0 Performance Requirements Summary 14

Appendix A. Deliverables 16

Appendix B. Meetings 19

Appendix C. Acronym Listing 22

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. The Task Order 1 Performance Work Statement (PWS) specifies the OMS program management requirements applicable to NESDIS ground systems support functions.

2.0 Scope

The Task Order 1 PWS specifies the Program Management requirements to support operations, maintenance, and sustainment of the assigned NESDIS ground segments within the OMS contract. Program management responsibilities include: project management, conducting program management reporting and review packages, schedule, delivery of products and services, financial operations and cost management, staffing management, configuration management, data management, systems engineering support, asset and property management with related inventories/ audits, purchasing and hardware/software license management, quality management, risk process management, training requirements, and contract transition management.

2.1 Place of Performance

The work locations for Task Order 1 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.2 References

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

● NOAA/NESDIS/OSGS 5820.02A Change and Configuration Management Process Document

● NSOF Library Standard Operating Procedure (SOP)

● NOAA Property _Bulletin_001_FY2016

● OSPO Risk Management Plan

● No FEAR Act Training, NOAA Safety Awareness Training, NOAA Safety and

Environment Awareness Training, and NOAA IT Security Awareness Training.

● Interface Control Documents (ICDs)

● DOC, NOAA, NESDIS, or OSPO policies and Information & Cyber Security Support procedures.

3.0 Requirements

3.1 Program Management

PWS-TO1-PM01: The Contractor shall provide program/project management services, personnel, and various documentation required to execute all requirements set forth in the IDIQ contract and all task orders. The Contractor shall:

● Create and maintain a comprehensive Program Management Plan (PMP) that shall cover programmatic activities for the OMS IDIQ contract and all task orders The initial PMP shall be submitted with the proposal, and the final one shall be submitted (1) month after contract award. Subsequent updates delivery shall be mutually agreed and updated to cover new scope (i.e. new or modified task orders, as required) [Deliverable].

● Develop and submit all programmatic documentation deliverables (see Appendix 1, Deliverables).

● Deliver a monthly Program Review Status Package [Deliverable] containing a detailed technical status, personnel status and updates, financial baseline plan vs. actual and variance report, current ODC status/plan/ forecast, maintenance plan status, table containing all required contract metrics.

● Deliver a monthly Integrated Master Schedule (IMS) [Deliverable].

● Deliver a monthly Consolidated Contract Financial Report [Deliverable].

● Conduct programmatic meetings to provide status of contract activities covering technical, schedule, financial activities, monthly program review, and regularly scheduled status meetings (e.g., tag up meetings, risk management, change control and any other ad hoc special topic or technical interchange meetings, phone calls, and response to data calls (when required) that are requested by the Government program office).

PWS-TO1-PM02: The Contractor shall provide and maintain a monthly Integrated Master Schedule (IMS) to include operations, maintenance and sustainment activities. The IMS shall be submitted with the monthly report and include all deliverables. The IMS is also required to include linked milestones for all contract transitions and task orders, procurement activities (as predecessors to sustainment activities), and all external dependencies such as Critical Weather Days. The IMS shall be included in the monthly program management review status package.

The contractor shall support additional schedule updates, when requested, supporting such activities as estimation of new, or modified activities, and developing impact assessments.

PWS-TO1-PM03: The Contractor shall provide a Contract Funds Status Report to the Government (monthly) for each task order [Deliverable]. The contractor may submit a consolidated contract funds status for the program covering all task orders.

PWS-TO1-PM04: The Contractor shall submit to the Government monthly invoices for each individual task order [Deliverable].

PWS-TO1-PM05: The Contractor shall provide and maintain an annual Spend Plan for Government approval [Deliverable]. 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 place for material purchases. The Spend Plan shall be updated monthly.

PWS-TO1-PM06: The Contractor shall provide a weekly Program Status Report (work status and plan) covering Monday through Sunday for each task order no later than the close of business (COB) the previous Friday [Deliverable].

PWS-TO1-PM07: The Contractor shall support the Government use of the 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-TO1-PM08: The Contractor shall provide and maintain a weekly contract Staffing Plan [Deliverable]. The Staffing Plan shall include a Contractor Organization chart, and identified roles and responsibilities. Updated organizational charts shall be provided when significant personnel or organizational changes to the Contractor’s organization occur, or change. Further, advance notification of 10 days shall be provided in the event of personnel changes. Contractor personnel shall possess the requisite professional and technical certifications, or comparable experience, commensurate with their responsibilities. The Contractor shall provide personnel that qualify under the condition of Suitability Assessment On-Site Service Support.

PWS-TO1-PM09: The Contractor shall maintain a list of all training taken by the Contract staff, relevant to, or required by, work performed on the Contract. The Contractor shall report changes to this as a part of their weekly status briefings. This list shall include at a minimum, the Contract staff members, name, position, training taken, date and the training relevance to the Contract or mandate it fulfills. The Contractor shall also produce and deliver to the Government, an updated list when requested for a data call.

PWS-TO1-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 [Deliverable] and posting any documentation to the Government-designated location. See Appendix B. Meetings for details.

PWS-TO1-PM11: The Contractor shall provide trained staff to support the Government in the use of enterprise tools listed in Table 2.1-1.

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

Table 2.1-1 Government Furnished Enterprise Tools

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]

Property Management Tracking Tool Sunflower Systems

Enterprise Scheduler System Customer Relationship Management

(CRM) Solution

Configuration Control / OSGS 5820.02A Change and Configuration Management

Process Document

Enterprise Configuration Management Tool

(ECMT)

Enterprise Help Desk IBM ClearCase/ClearQuest

Network Monitoring Solarwinds

Asset / Patch Management Altiris / BigFix

Log Management Tripwire / ArcSight

Web Management WebInspect

Vulnerability Management NESSUS

Document Management SharePoint / Google Docs

PWS-TO1-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. Travel must be deemed necessary and authorized by submission and subsequent approval of a travel request by the COR in order to be paid for by the Government.

PWS-TO1-PM13: The Contractor, as required by the COR or CO, shall travel to OMS work sites to support project activities, continuity of operations, and maintenance and sustainment activities and/or meetings/site visits as required by individual task orders. The Contractor shall comply with the following:

● All OMS contract-related travel shall be planned, coordinated, and approved in writing by the COR in advance.

● Travel shall be in accordance with the Federal Travel Regulation.

● The Contractor shall submit travel request forms for non-emergency travel at least 14 business days prior to the first day of planned travel.

● The Contractor shall submit travel costs on its monthly invoices within 30 days of travel.

● Submit any program requested travel for other Government Funded travel (e.g., support conferences, workshops, etc.) per submission processes to obtain any additional levels of Government approval required.

3.1.1 Configuration and Document Management

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

PWS-TO1-CM01: The Contractor shall support the Government daily in operating and maintaining ECMT for all OSPO systems. An ECMT Standard Operating Procedure (SOP) describing the support and processes will be provided in the OMS document library.

PWS-TO1-CM02: The Contractor shall submit Configuration Change Requests (CCRs) with all required documentation for all changes made during operations, maintenance, and sustainment of any hardware or software. The Government will provide a Microsoft SharePoint based document management system for creating or modifying documentation describing the maintenance and operations of hardware or software and provides information in general about hardware or software. The contractor shall provide current metrics on CCRs in the Configuration Change Request Report [Deliverable]. Ninety percent (90%) of CCRs shall have no open problem reports (PRs) at operational readiness review (ORR); any open PRS shall have an approved resolution plan.

PWS-TO1-CM03: The Contractor shall perform and provide Mission Impact Assessments (MIA) [Deliverable] for each CCR with an open problem report, which may include details related to system performance analysis, capacity planning, and cost estimates over the performance period. The MIA may result in technical direction letters or contract modifications depending on the scope and magnitude of the request.

PWS-TO1-CM04: The Contractor shall utilize the Government’s enterprise Microsoft SharePoint tool. Sharepoint will be the enterprise tool for OMS program documentation repository and technical documentation library for all OSPO systems.

PWS-TO1-CM05: The Contractor shall manage and maintain the NSOF Library in accordance with the NSOF Library Standard Operating Procedure (SOP).

PWS-TO1-CM06: The Contractor shall provide one or more Contractor resources as the responsible party for maintaining each, operating procedure, document, diagram, data set, configuration file or technical data package used in the operations, maintenance and sustainment of all assigned systems.

The responsible party 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.

PWS-TO1-CM07: The Contractor shall submit CCR’s for Document Change Requests.

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-TO1-CM08: The Contractor shall support the Government Configuration Control Board by providing an Executive Secretary experienced with Configuration Control and Management processes to create, maintain, and track completion of agendas, minutes, and action items.

PWS-TO1-CM09: The contractor shall maintain (and develop, as required) a comprehensive set of Government-owned contract documentation. The maintenance of this contract documentation shall include the following tasks:

● Provide/report a log of all documents created or modified. The list of modified documentation shall be reported monthly.

● Create or modify contract documentation while maintaining the required government /contract markings.

○ Contractor markings (i.e. corporate identifiers/logos, proprietary, internal use only etc.) are not permitted on OMS contract documentation

○ Contractor markings allowed include company name, address, telephone number, email address and website (on a single page inside the cover of multi-page documents, or on a single slide or frame at the beginning of a multimedia presentation).

● Maintain the current document format.

3.1.2 Quality Assurance

PWS-TO1-QA01: The Contractor shall provide their methods and processes for how they plan to ensure processes are carried out as planned while meeting all contract requirements in a Quality Assurance Plan (QAP) [Deliverable]. The QAP shall be included in the proposal submission and be updated as required. This plan explicitly describes Contractor processes and measures for subcontractor/ vendor performance and deliverables.

PWS-TO1-QA02: The Contractor shall provide a Quality Assurance SOP [Deliverable] within 60 days of the start of the contract and update it annually or as requested by the CO.

PWS-TO1-QA03: The Contractor shall provide, report, and track contract performance metrics as part of the monthly program management review. Metrics shall cover all task orders. Metrics shall be mutually agreed at the start of the contract, and may include modified or new metrics, as required, to accurately reflect contract performance.

PWS-TO1-QA04: The Contractor shall participate in the Government’s process improvement activities.

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

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

3.1.3 Risk Management

PWS-TO1-RM01: The Contractor shall comply with the OSPO Risk Management Plan.

PWS-TO1-RM02: The Contractor shall prepare a Risk Report [Deliverable] listing the Contractor’s view of initial OMS risks for review and consideration by the Government with recommended mitigations as part of its proposal submission. Subsequent updates to be coordinated with the Government monthly.

PWS-TO1-RM03: The Contractor shall support the Government in the risk management activities and maintaining risk related data in the Government-provided risk management tool, Active Risk Manager (ARM).

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

3.1.4 Training

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

PWS-TO1-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-TO1-TR03: The Contractor shall provide training and any corresponding training materials to Government personnel on substantive changes made to assigned systems in the course of the contract.

3.1.5 Cyber Security Program Management

3.1.5.1 Cyber Security Awareness & Training

PWS-TO1-ICS01: 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, and NOAA IT Security Awareness Training.

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

3.1.5.2 Cyber Security Assessment & Authorization

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

PWS-TO1-ICS03: The Contractor shall support security related processes required to be compliant with Government security mandates, and obtain/maintain an Authority to Operate

(ATO) for each system.

PWS-TO1-ICS04: The Contractor shall submit assigned Security Control Assessment (SCA) [Deliverable] artifacts yearly for each assigned system per the agreed schedule.

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

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

3.1.5.2.3 System Interconnection

PWS-TO1-ICS06: The Contractor shall provide data for information requests for all system Interconnection Security Agreements (ISA).

PWS-TO1-ICS07: The Contractor shall review and implement any and all interfaces per system Interface Control Documents (ICDs). Discrepancies or changes shall be reported to the Government for follow up.

3.1.5.2.4 System Security Documentation

PWS-TO1-ICS08: The Contractor shall support information requests for Security Authorization Packages for all assigned OSPO systems, including all required documents, and additional information when updates are made to DOC, NOAA, NESDIS, or OSPO policies, and Information & Cyber Security Support procedures.

3.1.5.3 Security Support for Systems Engineering and Change & Configuration Management

PWS-TO1-ICS09: The Contractor shall comply with configuration management requirements per section 3.5.3.3 of the OMS IDIQ PWS.

3.1.5.4 Cyber Security Management and Oversight

PWS-T01-ICS10: The contractor shall provide management for each OMS Task Order to ensure the Cyber Security requirements specified in the OMS IDIQ PWS are compliant. The details of the responsibilities are specified in the OMS IDIQ PWS Sections 3.5- Information & Cyber Security Support and Appendix B- OMS Information & Cyber Security Support Task Accountability Matrix. The typical tasks for cyber security management and oversight include:

● Perform activities, as coordinated between the OMS contract and OSPO IT Security Compliance Office

● Attend ISSO briefings to be cognizant of IT Security tasks requiring O&M input, to report progress of ongoing IT Security tasks such as vulnerability remediation, POAM activities, and SCA activities

● Maintain current set of required artifacts for auditors for each IT Security boundary and control, and providing artifacts per schedule. Key audits shall be reflected in the OMS schedule.

● Support and manage audit activities, including interviews of O&M personnel during audits

● Lead maintenance activities of IT Security Inventory, and investigate and resolve discrepancies

● Ensure, monitor, and report completion of all IT security required training (including all users and position-specific support positions)

● Support O&M-related readiness and execution of the annual COOP exercises and deployments

● Support disaster recovery activities, ensure routine disaster recovery backups are tested and fully functional in advance to ensure their functionality

● Report status of O&M security activities to the Government

● Perform risk management activities for the OMS contract to the Risk Management Board

● Lead Contractor activities for investigating IT security incidents

4.0 Contract Transition

The transition of an expiring contract’s scope to the OMS contract is a programmatic activity managed by the OMS Contractor and incumbent contractor, in coordination with the Government. The OMS Contractor shall accurately and effectively capture (document), and manage the transition of all activities contained in OMS task orders in a transition plan. A separate transition plan is required for each individual transition to the OMS contract.

PWS-TO1-CT01: The Contractor shall provide a contract Phase-In Transition Plan with a checklist of all required tasks and activities to complete the transition successfully. The initial Phase-in Transition Plan shall be submitted with the proposal response, and a final 30 days after contract award [Deliverable]. The final Phase-in Transition Plan shall consolidate all Task Order Phase-in Transition Plans from Step 1 and Step 2 of the solicitation. For new Task Orders an initial Phase-in Transition Plan shall be submitted at task order proposal response, and the final two weeks after task order start.

PWS-TO1-CT02: The Contractor shall transition work performance from any incumbent contractor(s) to itself for any assigned system within 60 days of assignment. The Contractor shall manage the transition with no interruption in ongoing services. Typical activities occurring 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-TO1-CT03: The Contractor shall document and report verbally the Phase-In Transition status report to the Government PMO weekly and monthly at the OMS program review meeting.

The initial Phase-In Transition Plan should describe how the contractor will transition Task Order 1 from the incumbent contractor(s) to itself with no interruption to ongoing services. The Phase-In Transition Plan shall include a checklist of all required tasks and activities to complete the transition successfully.

The final Phase-in Transition Plan is due after contract award shall consolidate all Task Order (1-

4) Phase-in Transition Plans.

PWS-TO1-CT04: The Contractor shall deliver a Contract Phase-Out Transition Plan (Deliverable) outline one year prior to the end of the contract to the PMO to 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

5.0 Performance Requirements Summary

PWS Section

Performance Objectives

Minimum Acceptable Quality Level (AQL)

Monitoring Method Incentive/Disincentive

Appendix A Deliverables

Contractor shall submit regularly scheduled Task Order deliverables, as scheduled per invoice period

98% submitted on time for each month

Inspection/review of deliverables, except “as required ”deliverables

≥ 98% submitted on time or earlier = to be filled in upon award % CLIN x001 payment

97.9 - 90% submitted on time = to be filled in upon award % CLIN x001 payment

89.9 - 85% submitted on time = to be filled in upon award % CLIN x001 payment

84.9 - 80% submitted on time = to be filled in upon award % CLIN x001 payment

< 80% submitted on time = invoice payment withheld until ≥ 80% of deliverables have been received, then to be filled in upon award % CLIN x001 payment

Appendix A Deliverables

Deliverables are accurate and complete

No missing data or miscalculations

Inspection/review of deliverables

CPARS ratings;

positive/negative Government correspondence

PWS-TO1-PM1,

Submission of contract-related travel documentation (travel requests, travel costs/expenses) for approval

-2 weeks prior to start travel for non-emergency

-within 30 days of travel completion for expenses to be reflected in monthly invoice

Inspection/review of travel approval documents, and invoices

CPARS ratings;

positive/negative Government correspondence

PWS-TO1-CT02,

CT03: Contract Transition In

Successful completion of all contract transition for all task orders;

complete planning documentation (initial/final), checklists, training, and reporting of transition activities per the agreed- to transition schedule

- On time delivery

- Checklist contains all transition elements

- 100% disposition of all transfer elements

-Inspection of transition plan documentation

-Verification required for

1) Contractor attendance of incumbent contractor training

2) Transfer and receipt of critical elements in monthly program review package

-Completed all transfer activities within transition period.

(contractor self-reports metrics in monthly program review package)

- Metrics verifying no lapse in service during transition period (availability)

CPARS ratings;

positive/negative Government correspondence

PWS-TO1-CM02

PWS-TO1-CM06

PWS-TO1-CM07

CM Request shall be closed by due date in the

ECMT

80% of all CM requests are closed without requiring revisions

ECMT monthly closure report

CPARS ratings;

positive/negative Government correspondence

Appendix A. Deliverables All deliverables shall be emailed to the individuals listed in the distribution column of the table below.

Deliverable

ID #

Deliverable Frequency Distribution PWS Reference Section(s)

TBD Program Management Plan

Initial with proposal submission, final one (1) month after contract award. Subsequent updates delivery shall be mutually agreed

CO,COR, PMO

3.1 Program

(PWS-TO1-PM01)

TBD Program Review Status Package

Monthly CO,COR,PM 2.1 Program Management (PWS-

TO1-PM01)

TBD

Integrated Master Schedule

(IMS)

Initial with proposal submission, updates monthly thereafter.

CO,COR, PMO 3.1 Program Management (PWS-

TO1-PM01)

(PWS-TO1-PM02)

TBD

Consolidated Contract Financial Report

Monthly CO,COR, PMO 3.1 Program Management (PWS-

TO1-PM01)

TBD Contract Funds Status Report

Monthly CO, COR, PMO

3.1 Program

(PWS-TO1-PM02)

(PWS-TO1-PM03)

TBD Invoices Monthly CO, COR, PMO

3.1 Program

Management

(PWS-TO1-PM04)

TBD Annual Spend Plan Initial 60 days after award; annually thereafter

CO, COR,

PMO

3.1 Program

Management

(PWS-TO1-PM05)

TBD Meeting minutes, agendas, action item lists, lessons learned, etc.

As required per required meetings established by the Government

Area Leads, PMO

3.1 Program

(PWS-TO1-PM05)

3.3.1.2. Meetings & Data

Call Support

(PWS-TO2-OP07; PWS-

TO2-OP08)

3.1 Program

(PWS-TO4-PA02)

TBD Weekly Program Status Report (work status and plan covering Monday through Sunday for each task order)

Weekly COR, CO, PMO, Operations Manager

3.1 Program

Management

(PWS-TO1-PM06)

TBD Staffing Plan Initial with proposal, final within 5 business days after award, updated monthly thereafter, and upon issuance of new task order(s);

COR, PMO 3.1 Program Management

(PWS-TO1-PM09)

TBD

Configuration Change Requests (CCRs) Report

Weekly

(weekly summary of CCRs and status; included in the Weekly

Program Status Report

Area Leads, PMO

3.1.1 Configuration and

Document Management

(PWS-TO1-CM02)

3.3.5.1 Facilities Change

Configuration Board (CCB) Report

(PWS-TO2-OP20)

3.1.2.1 Software

Sustainment Solutions

(PWS-TO3-SS01)

3.7 Satellite Product and

Services Transition To Operations

(PWS-TO4-PA45)

3.1.1 Configuration and

Document Management

(PWS-TO1-CM02)

TBD Mission Impact Assessments As required COR, PMO 3.1.1 Configuration and Document Management

(PWS-TO1-CM03)

TBD Quality Assurance Plan (QAP) Initial with proposal, updated as required (with the issuance of any new task order)

COR 2.1.3 Quality Assurance

(PWS-TO1-QA01)

TBD

Quality Assurance Standard Operating Procedure (SOP)

60 days after Contract start, updated annually, or requested by CO

CO, COR,

PMO

2.1.3 Quality Assurance

(PWS-TO1-QA02)

TBD

Risk Report

Initial report (Initial contractor risk list and proposed mitigation) with proposal.

Subsequent updates (coordinated w/ Contractor and Government) monthly

COR, PMO 2.1.4 Risk Management

(PWS-TO1-RM02)

(PWS-TO1-RM04)

TBD

Security Control Assessment (SCA) Artifacts

Annually for each assigned system per the agreed schedule

(SCA occurs yearly at a time chosen by NSOF. The artifacts are designated by the security assessors at the time of the assessment)

COR, PMO,

ISSO

2.1.6.2.1 Continuous

Monitoring and Assessment & Authorization (A&A)

(PWS-TO1-ICS04)

TBD Phase-In Transition Plan Initial plan submitted with proposal covering all task orders, Final plan 30 days after contract award

Subsequent plans for new task orders - Initial at task order proposal response, final 2 weeks after task order start

COR, CO 4.0 Contract Transition

(PWS-TO1-CT01)

(PWS-TO1-CT03 )

TBD Phase-Out Transition Plan Due one (1) year prior to the end of contract

COR, CO 4.0 Contract Transition

(PWS-TO1-CT04)

Appendix B. Meetings

Meeting Frequency Medium/Format Submit To Agenda Topics Description

Post Award Conference Once (within 10 days after contract award)

In person COR/CO

The Contractor shall participate in daily Help Desk Meetings

Daily In person COR Help Desk Daily Logs ECMT Ticket Status Change Log and Actions Report

The Help Desk Manager facilitates the Daily Help Desk meetings through providing Daily Logs, Ticket Reports, and Change Log reports for any planned System/ Network updates scheduled within 24 hours that may impact operations

The Contractor shall participate in daily SOCC Ticket Meeting

Daily In person COR Specific SOCC tickets

The Help Desk Manager facilitates the SOCC Ticket review/analysis process for ticket completion and to determine whether additional information or action is appropriate for ticket closure

The Contractor shall participate in daily SOCC Meeting

Daily In person COR SOCC issues, Wallops, Fairbanks, CDA, NSOF, NDE, GOES, POES, Jason 2

(Overview of SOCC and other satellite stations)

The SOCC Branch Chief facilitates this meeting and provides a status of daily/major activities that occur in

SOCC

The Contractor shall participate in weekly OMS Tech Doc Meeting

Weekly In person COR Technical documentation dashboard and outstanding tasks

The QA facilitates this meeting daily to address status on tasks assigned to the technical writers

The Contractor shall participate in weekly CCBs (Configuration Change Board)

Weekly – designated days for ESPC, DMSP, GOES, Polar

In person COR Reviews ECMT Requests

The CM Manager facilitates these CCBs:

To review and disposition ESPC, DMSP,GOES, Polar, and Common ECMT tickets (CCRs, and WRs)

The Contractor shall participate in weekly OMS Weekly Contract Meeting

Weekly In person COR Staffing, Program Management, Operations and Maintenance, System Engineering, Products and Applications, IT Security, POA&Ms and A&As

The Quality Manager facilitates this meeting to provide weekly status on planning for OMS tasks

The Contractor shall participate in weekly ISSO POA&M Status Meetings.

Weekly designated days for

GOES, POES,

ESPC, NJGS

In person COR A&A and POA&Ms

This meeting is held to secure a status of A&A and POA&Ms for systems

The Contractor shall participate in bi-weekly Help Desk Working Group

Bi-weekly

(every two weeks).

In person COR Review :

Procedures and update accordingly

The Help Desk Manager facilitates this meeting with the objective to improving the process and procedures used at the ESPC Help Desk

The Contractor shall participate in monthly ERB (Executive Review Board)

Monthly In person COR TBA by leader The PAL facilitates this meeting on an as-needed basis to resolve issues that cannot be resolved by the CCB.

The ERB shall also be responsible for the re-allocation of resources, establishing division priorities, and actions within the respective Divisions relating to change management and maintaining the operational integrity of the OSPO operating environment.

The Contractor shall participate in quarterly CM Technical Activities Working Group Meeting

Quarterly or as needed

In person COR TBA by leader The PAL facilitates this meeting on an as-needed basis to adjudicate the CM Process Improvements Forms/Pending requests

The Contractor shall participate in bi-weekly CM Tools Working Group

Bi-weekly

(every two weeks)

In person COR ECMT status, tickets, WRs and CCRs

The primary function and responsibility of the Configuration Management Tools Working Group (CMTWG) is managing stakeholder needs and requirements for Change and Configuration Management tools running (ECMT) on the NSOF Mission Support LAN

(NOAA5044).

The Contractor shall participate in monthly SOCC Risk Meeting

Monthly In person COR Open Risks Monthly meeting to review and provide status on all SOCC risks

The Contractor shall participate in Monthly MOD Issues meeting

Monthly In person COR Open Risks Monthly meeting to review and provide status on all Maintenance and Operations Division (MOD) issues

The Contractor shall participate in weekly Inventory Review Board

Weekly In person COR Inventory reviews and approvals

Inventory Improvements

The ESPC Network Engineer facilitates this meeting and reviews the updates on Altiris/ESPC and SOCC HW and SW inventories

Appendix C. Acronym Listing AIMS Action Information Management System

AQL Acceptable Quality Level

ARM Active Risk Manager

ATO Authority to Operate

CCR Configuration Change Request

CI Configuration Item

CO Contracting Officer

COB Close of Business

COR Contracting Officer Representative

CRM Customer Relationship Management

CS Contract Specialist

EA Engineering Assessments

ECMT Enterprise Configuration Management Tool

ERB Engineering Review Board

FAR Federal Acquisition Regulation

FTR Federal Travel Regulations

IAW In Accordance/Agreement With

IBM International Business Machines

ICD Interface Control Document

IDIQ Indefinite Delivery Indefinite Quantity

IMS Integrated Master Schedule

ISA Interconnection Security Agreements

IT Information Technology

MD Maryland

NCWCP NOAA Center for Weather and Climate Prediction

NESDIS National Environmental Satellite, Data, and Information Service

NOAA National Oceanic and Atmospheric Administration

NSOF NOAA Satellite Operations Facility

OMS Operations Maintenance Sustainment

OSGS Office of Satellite Ground Services

OSPO Office of Satellite Product Operations

PCA Physical Configuration Audit

PM Program Manager

PMO Program Management Office

POA&Ms Plan of Action and Milestones

PWS Performance Work Statement

QAP Quality Assurance Plan

SCA Security Control Assessment

SOP Standard Operating Procedure

WYE Work Year Equivalents