J4_SOW_v2.3-TC.pdf

April 18, 2016 Attachment J4 – Statement of Work Version 2.3

NESDIS Office of Satellite Ground Services Systems Engineering and Technical Support (SETS)

Contract Statement of Work Requirements Document

Version 2.3 April 18, 2016

U.S. Department of Commerce (DOC)

National Oceanic and Atmospheric Administration (NOAA)

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

CHANGE RECORD

DOCUMENT TITLE: OSGS Systems Engineering and Technical Support (SETS) Contract Statement of Work Requirements Document

VERSION DATE PAGES AFFECTED DESCRIPTION

1.0 30 Oct 15 All Final

1.1 29 Feb 16 Remove Section 2.8.3

2.0 3 Mar 16 All Update

2.1 28 Mar 16 Edit Section 2.4.1

Section 2.8.1 renumbered 2.9 Section 2.8.2 renumbered 2.10

Re-insert Section 2.8.3, renumber as 2.11

2.2 7 Apr 16 Pg. 13 Edit Section 2.4.2.2, second paragraph

2.3 18 Apr 16 All Use active versus passive tense

Capitalize Government and Contractor

The document version number identifies whether the document is a working copy, final, revision, or update, defined as follows:

• Working copy or Draft: a document not yet finalized or ready for distribution; sometimes called a draft. Use 0.1A, 0.1B, etc. for unpublished documents.

• Final: the first definitive edition of the document. The final is always identified as Version 1.0.

• Revision: an edition with minor changes from the previous edition, defined as changes affecting fewer than one-third of the pages in the document. The version numbers for revisions 1.1 through 1.9, 2.1 through 2.9, and so forth. After nine revisions, any other changes to the document are considered an update. A revision in draft, i.e. before being re-baselined, should be numbered as 1.1A, 1.1B, etc.

• Update: an edition with major changes from the previous edition, defined as changes affecting more than one-third of the pages in the document. The version number for an update is always a whole number (Version 2.0, 3.0, 4.0, and so forth).

Table of Contents

1 INTRODUCTION

1.1 Terms and Definitions

1.2 Scope

1.3 Period of Performance

1.4 Government Furnished Property (GFP)

2 SYSTEM ENGINEERING AND TECHNICAL SUPPORT REQUIREMENTS

2.1 Program and Project Management

2.1.1 Business Management

2.1.1.1 Contract and Cost Management

2.1.1.2 Project Information Technology Management and Access

2.1.1.3 Travel

2.1.1.4 IT SECURITY REQUIREMENTS

2.1.1.5 Contract Transition

2.1.2 Configuration Management

2.1.3 Risk Management

2.1.4 Subcontract Management

2.2 Technical Management Planning

2.2.1 System Engineering Management Planning

2.2.2 Technical Cost and Schedule Analysis

2.2.3 Financial and Cost Estimation Analysis

2.2.4 Safety and Mission Assurance

2.2.5 NESDIS Independent Review Team (IRT) Support

2.3 Information Resource Management & Engineering

2.3.1 Computer Resource Management

2.3.2 Software Acquisition Capability Assessment

2.3.3 Information Resource Management Advisory Committee (IRMAC)

2.3.4 Software Engineering

2.3.5 System Integration and Test

2.3.6 Independent Verification and Validation (IV&V)

2.4 Systems Engineering

2.4.1 Pre-Formulation and Formulation Services: Candidate, Preliminary Analysis, and

Systems Definition Studies

2.4.2 System Concept Design, Analysis, Economic, and Trade Studies

2.4.2.1 Systems Concept Design

2.4.2.2 System Concept Analysis

2.4.2.3 System Concept Economic Analysis and Trade Studies

2.4.3 System Requirements/Functional Analysis

2.4.3.1 Requirements Analysis

2.4.3.2 Requirements Traceability

2.4.3.3 Criticality Analysis

2.4.3.4 Functional Analsyis/Allocation

2.4.3.5 Performance Analysis/Allocation

2.4.4 System Architecture Evolution Planning

2.4.4.1 Systems Concept Planning

2.4.5 System Engineering Standards

2.5 Special Studies

2.6 User Systems Liaison

2.7 Transition to Operations

2.7.1 Sustainment

2.8 IT Security

2.9 Ground System Sustaining Engineering

2.10 Continuity of Operation Program Support

2.11 Radio Frequency Support

3 DELIVERABLES

3.1 Reporting

3.1.1 Progress Reports

3.1.2 Financial Reports

3.1.3 Contract Closeout Report

1 INTRODUCTION

This Statement of Work (SOW) details the analysis and system engineering activities to be performed by the Contractor in support of the National Environmental Satellite, Data, and Information Service (NESDIS) of the National Oceanic and Atmospheric Administration (NOAA). The primary places of performance for the Contract are the Geostationary Operational Environmental Satellite R Series (GOES-R) Program Office at the NASA Goddard Space Flight Center in Greenbelt, MD; the Joint Polar Satellite System (JPSS) Program Office facility in Greenbelt, MD; the Office of Systems Architecture and Advanced Planning (OSAAP), Office of Satellite Ground Services (OSGS) and Office of Projects, Planning and Analysis (OPPA).

Program offices are located in Silver Spring, MD; and the NOAA Satellite Operations Facility (NSOF) located in Suitland and Silver Spring, MD. A limited number of Contractor staff may also be based at the European Organization for the Exploration of Meteorological Satellites (EUMETSAT) Headquarters facility in Darmstadt, Germany. The place of performance for the specific Work Assignments (See e.g., Sections C2, F5, F6, and G11) will be outlined in the NOAA/NESDIS office Work Assignment Statements of Work.

NESDIS is responsible for the procurement of new flight and ground systems and the modification of existing systems needed to operate the satellites, and to collect, process, distribute, and store satellite data for the nation’s civilian environmental satellite (spacecraft and sensor) program. These systems include computers, communications, Radio Frequency (RF) equipment and the associated hardware and software, as well as build, maintain and upgrade the physical infrastructure (e.g., facilities) supporting the satellite missions. NESDIS is also responsible for performing similar work on cooperative missions with other United States Government agencies, foreign governments, and organizations. NESDIS is responsible for the IT architecture and security of their computer systems processing environmental data, and supporting both operational and administrative functions.

The NESDIS organizations are responsible for program level management activities for these satellite missions. Government managers are responsible for the entire environmental satellite program or for portions thereof, including coordinating activities within the various NOAA/NESDIS organizations and with NOAA’s National and International partners. NESDIS is also responsible for planning for future satellites, instruments and products, and annual satellite program budgets.

1.1 Terms and Definitions

The following terms and definitions are used throughout this Statement of Work (SOW).

The term “shall” designates a required activity or specification.

The terms “Government” and “Government personnel” means federal Government employees.

The term “Government representatives” means federal Government employees and its support Contractors.

1.2 Scope

This Statement of Work (SOW) details the System Engineering and Technical Support activities to be performed by the Contractor in support of the National Environmental Satellite, Data, and

Information Service (NESDIS) of the National Oceanic and Atmospheric Administration

(NOAA).

The activities defined herein describe the Contractor’s responsibilities, on a Work Assignment basis, for providing adequate resources to assist the Government in overseeing work to design, analyze, validate, develop, fabricate, assemble, integrate, checkout, test, evaluate, verify, deliver, transition, document, and support operations, maintenance and sustainment of the NESDIS ground systems and their interfaces.

1.3 Period of Performance

See Section F2 of the Contract.

1.4 Government Furnished Property (GFP)

See Section G4 of the Contract.

2 SYSTEM ENGINEERING AND TECHNICAL

SUPPORT REQUIREMENTS

The Contractor shall provide all management and engineering services, personnel, materials, and equipment, not otherwise furnished by the Government.

2.1 Program and Project Management

The Contractor shall establish a management structure responsible for overall program control as well as individual project controls for each Work Assignment.

The Contractor shall designate an on-site Program Manager to coordinate day-to-day activities and to act as the technical interface with the Government's Contracting Officer's Representative (COR). The Program Manager and Government COR will be co-located.

The Program Manager shall have sufficient corporate authority to assure that the contract cost, schedule and technical requirements are fully met.

Additional Project Management details may be provided for the Work Assignments.

2.1.1 Business Management

2.1.1.1 Contract and Cost Management

The Contractor shall perform the contract and cost management activities necessary to execute the contract.

The Contractor shall manage project finances.

2.1.1.2 Project Information Technology Management and Access

The Contractor shall use Government furnished information technology resources to access Government networks.

2.1.1.3 Travel

The Contractor shall travel to various CONUS and OCONUS locations during the performance of this contract. See also, Section F4.

2.1.1.4 IT SECURITY REQUIREMENTS

The Contractor shall comply with the IT Security requirements of the Department of Commerce as outlined in Commerce Acquisition Regulation (CAR) 1352.239-72, Security Requirements For Information Technology Resources (April 2010), except that development of a Security Accreditation Package in accordance with CAR 1352.239-72, section (i) is not required.

The Contractor shall comply with NOAA security requirements regarding access to Government facilities and follow NOAA NESDIS/Finance Office policies and procedures.

The Contractor must also comply with DOC and NOAA IT Security Policies, which includes completion of annual IT Security Awareness training. Contractor’s staff will also be required to sign a NOAA Non-Disclosure Agreement prior to obtaining system access.

In addition, personnel shall be screened in accordance with the requirements for Moderate Risk contracts as specified by CAM 1337.70 section 2.2; specifically, in accordance with CAR 1352.237-70, Security Processing Requirements—High or Moderate Risk Contracts (April 2010). Any access by contract personnel who are Foreign Nationals shall be in accordance with the requirements of CAR 1352.237-73, Foreign National Visitor and Guest Access to Departmental Resources (APR 2010). See also, Section I of the Contract.

Contractor will provide the NOAA points of contact the names of Contractor staff assigned so that the NOAA staff has sufficient time to process requests for NOAA badges, and network access prior to Contractor’s staff starting work at NOAA and/or NASA locations. For any subsequent staffing changes, the Contractor, at minimum, will provide five (5) working days written notice of requests for Contractor staff to be provided NOAA badges and access to network systems.

2.1.1.5 Contract Transition

The Contractor shall provide resources to conduct an orderly transition of engineering knowledge, processes, documentation, and tools to the Government or to a successor Contractor, beginning three (3) months prior to the end of the period of performance of the contract.

2.1.2 Configuration Management

The Contractor shall use the Government furnished Configuration Management tools in support of activities outlined within this SOW and any Work Assignments.

The Contractor shall oversee and perform Configuration Management activities across the NESDIS ground enterprise.

The Contractor shall support the Government’s Configuration Control processes including providing technical inputs regarding actions coming before the Engineering Review Boards (ERBs) and CCBs (Configuration Control Board).

2.1.3 Risk Management

The Contractor shall oversee and perform risk management activities for the NESDIS ground enterprise.

The Contractor shall support the Government’s risk management process including providing technical inputs for Risk Management Boards (RMB).

2.1.4 Subcontract Management

The Contractor shall be responsible for all performance, including the technical, cost, and schedule performance, of all subcontractors.

The Contractor shall provide technical and management oversight and status reporting for all subcontract activities.

The Contractor shall ensure requirements from this SOW and applicable documents are flowed down to the subcontractors.

2.2 Technical Management Planning

2.2.1 System Engineering Management Planning

The Contractor shall assist the Government in developing and maintaining Program Plans, Project Plans and System Engineering Plans (SEP).

The Contractor shall support the Government in developing schedules.

The Contractor shall support the Government in developing Technical Performance Measures

(TPM).

The Contractor shall support the Government in developing Cost Estimates.

The Contractor shall support the Government in executing management and engineering reviews.

The Contractor shall support the Government in executing NESDIS Strategic Planning.

The Contractor shall support the Government in the development of procedures for, and in the development of, work breakdown structures and work planning and definition of systems.

The Contractor shall support the Government in developing and implementing procedures on the formulation of contract technical package requirements and assist in the technical documentation to guide each program’s System Contractors in meeting the Government’s requirements.

The Contractor shall support the Government in meeting facilitation, management briefing development, process improvement and status reporting.

2.2.2 Technical Cost and Schedule Analysis

The Contractor shall support the Government in defining program requirements and their associated program budgets.

The Contractor shall support the evaluation of prime Contractor quotations for contract modifications and change proposals.

The Contractor shall review prime Contractor’s Cost and Schedule Status Reports to assess cost and schedule performance.

The Contractor shall support the Government on the analysis and reporting of Earned Value (EV) for NESDIS Development, Modernization, and Enhancement (DME) Projects.

2.2.3 Financial and Cost Estimation Analysis

The Contractor shall support the Government with Financial and Cost Estimation Analysis including independent cost estimates, independent financial analysis support to IT acquisitions and proposed contract modifications, and alternatives analysis, life cycle cost estimates (LCCE), multi-year PAC planning, and total cost of ownership (TCO) analysis, Construction Work In Progress (CWIP), OMB 300 and budgeting.

2.2.4 Safety and Mission Assurance

The Contractor shall support the Government in the performance of Safety and Mission Assurance activities.

The Contractor shall support the Government during the anomaly and incident review process.

2.2.5 NESDIS Independent Review Team (IRT) Support

The Contractor shall support the Government in conducting independent reviews of NESDIS space and ground systems.

The Contractor shall support the Government in the executive secretariat and administrative activities for the IRT.

2.3 Information Resource Management & Engineering

2.3.1 Computer Resource Management

The Contractor shall support the Government in developing procedures and standards for computer resource management.

The Contractor shall support the Government in computer resource management verification activities.

The Contractor shall support the Government in developing Government computer resource management plans and programs.

The Contractor shall support the development of requirements analysis packages and related material to support Information Resource Management (IRM).

2.3.2 Software Acquisition Capability Assessment

The Contractor shall support the Government in software acquisition.

2.3.3 Information Resource Management Advisory Committee (IRMAC) The Contractor shall support the Government in recommending system technical standards (e.g., Technical Reference Model), establishing IT goals and objectives, outlining IT strategies, and conveyance of such information to OSGS management for awareness and planning purposes.

2.3.4 Software Engineering

The Contractor shall support the Government in developing software engineering procedures.

The Contractor shall support the Government in the planning and requirements definition aspects of software engineering.

The Contractor shall support Government software acquisition activities including:

a) Develop and review software development plans, schedule activities, and requirements definition.

b) Review formal software deliverables of the satellite ground system development Contractors, such as software design, database design documents and software requirements specifications, and supplier processes.

c) Review and recommend existing and emerging software engineering methods, techniques, and software tools.

d) Develop procedures and tailor or recommend standards for software engineering in support of the development of satellite ground systems, such as review of CDRLs.

e) Evaluate the effectiveness of the satellite ground systems development Contractor’s applications of computer languages and programming support environments and provide recommendations to achieve soundness and completeness for the Government.

f) Evaluate software development methodologies (adaptive vs. predictive) based on project complexity, potential for requirements changes, and schedule/cost constraints, and provide an adaptive/predictive software development tradeoff including associated risks for all ground system projects.

g) Develop and tailor software metrics, and analyze software development efforts using these metrics for the design and development of satellite ground systems.

h) Evaluate and prepare software size and development cost estimates and life-cycle size and cost estimates.

i) Review and evaluate satellite ground systems development Contractor’s software designs, including design for maintainability, extensibility, modularity, and scalability, and assess whether the software can support long term missions and is consistent with emerging enterprise concepts.

j) Determine degree of independence of the various subsystems of the development Contractor’s design, i.e., how loosely or tightly coupled are the software components and how do changes in one component impact other components.

k) Evaluate documented operational requirements of software performance parameters and system configurations, including support to mission operations testing team.

l) Evaluate and review satellite ground systems development Contractors’ software life-cycle support plans and documentation.

2.3.5 System Integration and Test

The Contractor shall support the Government in hardware and software Integration and Testing activities.

The Contractor shall support the Government in Quality Assurance and review of test reporting.

The Contractor shall support the Government in defining functional capabilities as requested to support testing of calibration/validation and product assessment needs.

The Contractor shall support the Government in reviewing and evaluating interface requirements, controls and integration.

The Contractor shall support the Government in monitoring and evaluating the development Contractors’ and subcontractors’ integration and test activities.

2.3.6 Independent Verification and Validation (IV&V)

The Contractor shall support the Government by performing independent verification and validation activities.

The Contractor shall support the Government in the evaluation for acceptance of deployed capabilities.

2.4 Systems Engineering

2.4.1 Pre-Formulation and Formulation Services: Candidate, Preliminary Analysis, and

Systems Definition Studies

The Contractor shall support the Government by providing engineering services for mission concept development that integrate the aspects of flight systems, ground systems, and instrument systems.

The Contractor shall support the Government by developing a Concept of Operations (CONOPS) reflecting mission objectives, measurement concepts, and instrument concepts, as well as identifying various communications interfaces required in the end-to-end flow of information from the point of data acquisition to the data consumer organizations.

The Contractor shall support the Government by providing pre-formulation and formulation phase study inputs for spacecraft, instruments, and ground systems.

The Contractor shall support the Government in formulating a preliminary analysis of alternatives for high-level hardware and software design concepts, including relative cost and schedule estimates based on design alternatives, and identification and assessment of high-risk elements in designs.

The Contractor shall support the Government identification of interface requirements for pre-launch, launch, on-orbit servicing, or retrieval of flight hardware.

The Contractor shall support the Government by defining interface engineering and management requirements.

The Contractor shall support the Government by preparing requirements and specification packages that conform to applicable standards defined within Work Assignments.

The Contractor shall support the preparation of mission systems and operations documentation.

The Contractor shall support the Government by providing System Engineering and Analysis services to NESDIS for environmental satellite ground systems, instruments, spacecraft or other related mission activities.

The Contractor shall support the Government in Information Technology (IT) architecture analysis and conceptual design activities, strategic planning and development activities, physical and IT security evaluation and recommendations, contingency planning, facility upgrade planning, and performing special studies as directed by NESDIS.

The Contractor shall support the Government in developing and evaluating NOAA-wide observing requirements, allocating requirements to satellite and other remote sensing and in-situ observing programs, and planning for new spacecraft and instruments and the associated ground and communications systems. These include the satellites flown by NOAA/ NESDIS as well as cooperative missions flown by other agencies and foreign governments.

The Contractor shall support the Government in planning for the launch, checkout, and operations of spacecraft for the current and future series of environmental satellites, including the associated ground and communications systems.

The Contractor shall support the Government in pre- and post-launch calibration activities to ensure satellite instrument performance, operations, and accuracy requirements are met.

The Contractor shall work with instrument project engineers and vendors to establish and oversee contractor executed test procedures, integration with the spacecraft, radiometric calibration, instrument interfaces, engineering, and instrument operation procedures.

The Contractor shall support the Government by performing assessment of end-to-end instrument performance, from raw measurement to Level 1b product data and Level 2 products.

The Contractor shall support the Government for technical oversight of instrument data processing algorithm development, including implementation by the ground system (transition to operations).

The Contractor shall furnish the necessary labor and materials to perform all Contract requirements. All deliverables required by this Contract shall be in a Government-approved Contractor format unless otherwise specified by each Work Assignment.

All deliverables (Plans, Reports, Schedules, and Spreadsheets) shall be provided in both hard copy and electronic format as directed by the Government. Both the formal hard copies and the electronic copy of the deliverable shall be submitted by the due date.

2.4.2 System Concept Design, Analysis, Economic, and Trade Studies

2.4.2.1 Systems Concept Design

The Contractor shall support the Government in the system conceptual design phase to determine feasibility and define product and process solutions in terms of design requirements that satisfy the functional architecture and integrate the physical architecture.

The Contractor shall support the Government by providing a robust, integrated system boundary document including: configuration items, physical interfaces, and system elements for each logical set of functional and performance requirements of the functional architecture.

The Contractor shall support the Government by developing alternatives and preferred system product and process solutions to provide the basis for the specification tree, work breakdown structure, and progressive definition of specifications and configuration baselines.

2.4.2.2 System Concept Analysis

The Contractor shall support the Government in system concept analysis to satisfy operational requirements and program objectives, and to provide a rigorous quantitative basis for performance, functional and design requirements.

The Contractor shall support the Government in the use of models, simulations, and prototypes to refine systems concepts, and seek user feedback leading to competitive acquisitions or the fielding of critical operational elements, where appropriate.

The Contractor shall support the Government in evaluation, assessment, and development of Contractor-supplied engineering models or prototype models against the Contractor’s own benchmark models.

The Contractor shall support the Government by conducting independent analyses and tests, such as performance analyses and the testing of hardware and software, to verify the adequacy of the development Contractors' assumptions, predictions and designs.

2.4.2.3 System Concept Economic Analysis and Trade Studies

The System analysis may take the form of either trade studies or system economic analysis.

The Contractor shall support the Government in conducting trade studies. Specifically the Contractor shall conduct requirements trade studies, allocation trade studies, and design trade studies to establish performance and functional specifications and establish optimum system configuration.

The Contractor shall support the Government in conducting system economic analysis to aid in decision-making.

The Contractor shall support the Government in assessing the circumstances and intended purpose of an economic analysis and recommend an appropriate approach, including the selection of any models.

The Contractor shall support the Government by performing functional economic analysis to evaluate improvements of administrative and operational processes.

2.4.3 System Requirements/Functional Analysis

2.4.3.1 Requirements Analysis

The Contractor shall support the Government in conducting requirements analysis.

The Contractor shall support the Government in the analysis of user needs, objectives, and requirements in the context of user missions, utilization environments, and identified system characteristics.

The Contractor shall support the Government by determining functional, performance and other technical requirements for each primary function of the system.

The Contractor shall support the Government by reviewing and updating prior analyses to refine mission and environment definitions to support system definition.

2.4.3.2 Requirements Traceability

The Contractor shall support the Government in conducting requirements traceability.

The Contractor shall support the Government to ensure that the traceability analysis includes tracking the allocated design requirements through the Work Breakdown Structure between the system level and the lowest level of assembly.

The Contractor shall support the Government by analyzing requirements documentation to determine the impact of changes to requirements at any level of the systems engineering documentation process.

The Contractor shall support the Government by examining requirements documentation to ascertain that the rationale for a given change can be reviewed without the need to reconstruct the analysis process.

The Contractor shall support the Government using manual and/or automated tools, such as the Dynamic Object Oriented Requirements System (DOORS), to assist in this function.

2.4.3.3 Criticality Analysis

The Contractor shall support the Government in conducting criticality analyses of program requirements.

The Contractor shall assist the Government to ensure that criticality analysis is used to chart the probability of failure modes in NOAA satellite missions against the severity of consequences, allowing for remedial effort to be directed as required.

2.4.3.4 Functional Analysis/Allocation

The Contractor shall support the Government to perform iterative functional analysis with allocation to the level of detail specified by the Government to support required system process and product design efforts.

2.4.3.5 Performance Analysis/Allocation

The Contractor shall support the Government in establishing and allocating performance requirements for each functional requirement and system interface.

2.4.4 System Architecture Evolution Planning

The Contractor shall support the Government in developing, analyzing, and validating system architectures and interfaces.

The Contractor shall provide high-level architectural analysis that addresses information flows and system functions.

The Contractor shall support the Government by providing lower level architecture analysis that addresses structure and interfaces for individual or closely related systems.

The Contractor shall support the Government by identifying and describing any shortcomings and inconsistencies.

The Contractor shall support the Government by recommending alternatives for any shortcomings identified by the Contractor or the Government.

The Contractor shall support the Government by developing and maintaining a top-level Systems Architecture Plan for all programs managed by the Government and the programs with which they interface for the purpose of defining information flow, functional capabilities and interfaces.

The Contractor shall analyze the effectiveness of evolving system architectures in meeting mission needs and operational requirements.

The Contractor shall support the Government to recommend technical standards and programmatic approaches to efficiently achieve future objective integrated architectures. This includes defining target enterprise architecture across NESDIS systems and developing roadmaps to reach the target from the baseline architecture in incremental steps, as driven by the infusion of new and enhanced mission systems and capabilities into the evolving architecture framework.

The Contractor shall support the Government by performing technical studies to identify system performance and capacity needs for the future. Such studies could include the impacts and potential impacts of pending legislation and local issues on operational systems.

The Contractor shall support the Government by assessing unfulfilled requirements and shortfalls in existing or planned systems and plan for eliminating these gaps through productivity and/or preplanned product improvements.

2.4.4.1 Systems Concept Planning

The Contractor shall support the Government in system concept planning to satisfy overall program objectives. The Contractor shall:

a) Develop acquisition program baselines reflecting top-level characteristic thresholds and goals for performance, schedule, and cost.

b) Develop test and evaluation (T&E) master plans that describe: the system, minimum acceptable performance requirements, critical technical parameters, the integrated test program schedule and management, developmental and operational T&E outlines, and T&E resource requirements.

c) Develop Integrated Logistic Support plans incorporating maintenance and support concepts, facilities, manpower and training assessments.

d) Develop Program and Project Plans addressing such topics as execution status, existing system shortfalls, alternatives assessed and results (including cooperative opportunities), most promising alternative and rationale, acquisition processes and schedule, cost drivers and major trade-offs, risk assessment and reduction/control (i.e., in the areas of technology, design and engineering, support, environmental impact, cost and schedule), and affordability in the context of long-range modernization and investment plans.

2.4.5 System Engineering Standards

The Contractor shall support the Government by developing policy, tailoring and selecting standards and procedures for system engineering in such areas as: reliability and maintainability; risk management; human factors; system safety; test and evaluation;

transportability; integrated logistics support; productivity; and quality assurance/control.

2.5 Special Studies

These one-of-a-kind analytical studies may require access to proprietary or highly-sensitive agency information that would compromise the information and potentially provide competitive advantage if divulged to a for-profit Contractor.

These special studies may be used for planning purposes by the Government and may include, but are not limited to, cross-agency analyses and considerations of private/public partnerships that would cross organizational boundaries.

The Contractor shall support and/or conduct special studies for the Government, which the Contractor has no conflict of interest either through subsequent competitive bidding or through proprietary interest in any particular solution.

The Contractor shall provide a plan to the Government describing its conflict-free business practices and methods of ensuring compliance.

2.6 User Systems Liaison

The Contractor shall support the Government by providing engineering and system engineering support services and working directly with NOAA product data users to ensure that end user needs are met by NESDIS satellite systems.

These efforts shall include coordinating with users regarding data product preferences, formats, latencies and other data requirements; network connectivity and data transmission protocols;

developing Interconnection Security Agreements, Interface Requirements and Interface Control Documents; developing user testing procedures; participating in inter-office and program technical interchange meetings/forums.

The Contractor shall apply extensive knowledge of meteorological remote sensing, communications approaches, and data production to interpret user needs.

The Contractor shall assist the Government in the acquisition of ancillary data from external elements for use in satellite product generation. The Contractor shall assist in refining product distribution requirements and analyze distribution architecture to ensure satellite data delivery mechanisms meet user needs.

2.7 Transition to Operations

The Contractor shall provide technical support for the planning and transition to operations, including training, documentation, and process development.

The Contractor shall support the Government for the planning, definition, and implementation of the transition, mission and data operations, and sustainment activities including participation in mission and data operations engineering roles and execution of the mission and data operations efforts, from pre-launch planning through post-launch operations.

The Contractor shall support the Government by developing and coordinating schedules, training and education materials for product users, operators, engineers, and support personnel.

The Contractor shall support the Government by preparing artifacts and materials to support multiple system readiness reviews leading to launch and post-launch acceptance reviews.

The Contractor shall work with Flight and Ground Projects, Program, Government technical support teams, and development Contractor teams to ensure that end user needs are met by the satellite mission system.

2.7.1 Sustainment

The Contractor shall support the Government in integrated logistics support planning

The Contractor shall support the Government in developing sustainment and sparing plans

The Contractor shall support the Government in developing and maintaining operational and service level agreements.

2.8 IT Security

The Contractor shall support the Government by providing technical support to the design, implementation, and evaluation of all phases of mission security and information assurance solutions for NESDIS satellite missions.

The Contractor shall support the Government by performing security assessments, developing system requirements, and preparing security plans, risk assessments, and developer security test and evaluation (developer ST&E) reports based on NIST, Department of Commerce, NASA, and Department of Homeland Security standards for information technology (IT) systems.

The Contractor shall support the Government with implementing standards, guidance, and policies for the mission system. The Contractor shall support continuous monitoring of all information security, including activities associated with the acquisition and development efforts.

The Contractor shall support the Government in planning and executing Assessment and Authorization work performed by the NESDIS OCIO-S, including activities to achieve and maintain Authority to Operate, such as gathering evidence to demonstrate control implementation and compliance.

2.9 Ground System Sustaining Engineering

Sustaining engineering consists of a combination of systems engineering and product support life-cycle management strategies to ensure that the specified sustainment metric outcomes are met for the life of the program, such as satisfying Reliability, Maintainability and Availability (RMA) measures as additional satellite input data or functional requirements are levied upon the ground system.

The Contractor shall support the Government by providing independent technical, cost and cost/benefit analyses for all sustaining engineering work being conducted by ground system development Contractors, including complete replacement systems as well as upgrades of existing systems to provide enhanced performance and functional capabilities.

As part of the process, the Contractor shall participate in the required SDLC gate reviews and provide feedback to the Government on the viability of the development Contractor’s designs, cost, and schedule.

The Contractor shall work closely with both the development Contractor and OSPO personnel in developing integration & test, verification & validation, and transition to operations plans, and ensure deconflicting of schedules based on OSPO operational priorities during the execution of these plans.

2.10 Continuity of Operation Program Support

The Contractor shall support the Government by performing the following:

a) Developing pertinent documents (standard operating procedures, etc.) required to effectively execute contingency operations including communications, logistics and other related NESDIS primary mission essential areas;

b) Analyzing contingency/ continuity plans for current operational and future satellite ground and administrative support systems; and

c) Assisting with exercising/evaluating activities associated with approved operational contingency/continuity plans.

2.11 Radio Frequency Support

The Contractor shall support the Government by performing the following:

a) Conducting analyses as required for NOAA/NESDIS with the Development, Modernization and Enhancement (DME) of new and existing Geostationary Earth Orbit (GEO), Medium Earth Orbit (MEO) and/or Low Earth Orbit (LEO) Satellite Program Radio Frequency (RF) systems;

b) Evaluating current and emerging RF systems and technologies for use with current and future GEO, MEO and LEO satellite missions (including NOAA partner and cooperative missions);

c) Developing link analyses, interference analyses and anomaly resolution studies as required;

d) Creating, collecting and generating data and reports of findings as required; and

e) Assisting NOAA/NESDIS staff with preparation for (and participating when required) in technical meetings and discussions with partners, cooperative organizations and agencies; e.g., NASA, DOD, EUMETSAT, JAXA, KSAT and CNES.

3 DELIVERABLES

The Contractor shall provide specific and unique required deliverables, including reports, meeting minutes, trip reports and documentation of the work performed as called for within this SOW, the Work Assignments, and the Contract. Work Assignments may specify a different deliverable requirement in order to expedite the delivery of written documentation. Absent any deviation cited in the Work Assignment, the requirement set forth herein shall apply.

3.1 Reporting

All reports will be delivered electronically in the Contractor’s format in a Microsoft Office readable file.

3.1.1 Progress Reports

See Section G3.

3.1.2 Financial Reports

See Section G12.1.2.

3.1.3 Contract Closeout Report

See Section G12.1.3. Report Specification Matrix