OPIR Site Integration Standard (OSIS)_Rev 1 (2).pdf

OPIR SITE INTEGRATION STANDARD

SENSITIVE BUT UNCLASSIFIED

OVERHEAD PERSISTENT INFRARED (OPIR)

SITE INTEGRATION STANDARD (OSIS)

FINAL Rev 1

PREPARED BY:

Space Systems Command, Space Sensing Product Support Delta (SSC/SNP)

1050 E Stewart Ave

Colorado Springs, CO 80914

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense (DoD) and only those United States (US) DoD contractors that support the Overhead Persistent Infrared Systems (OPIR) Program of Record (POR) Enterprise. Reason: Critical Technology. Date of Determination: 7 Dec 98. Requests for any distribution beyond the above limitations must be submitted in writing to SSC/SNP.

SENSITIVE BUT UNCLASSIFIED

ii

OPIR ENTERPRISE

APPROVAL

ANITA J. MCCORVEY, NH-04

Director, Space Systems Command, Space Sensing Product Support Delta (SSC/SNP)

SUBMITTED BY

DAVID S. ELLESTAD, NH-03, USSF

Integration Branch, Sustainment Integration Lead (SSC/SNPDI)

SENSITIVE BUT UNCLASSIFIED

iii

REVISION HISTORY

Date Author Version Description / Summary of Change

5/2023 Steven Meyers Basic Initial Release

03/2024 Patrick Taylor, Bryan Cannady & Bethany Ramirez

Increased Scope of PIK Modified Round Table structure Removal of SIB TIM Increased requirements for SIB Approval Added project screening criteria for OSIS applicability Revised PIK submission guidance Revised PICO routing guidance Added guidance for daily status briefs during project installation Revised Site Survey guidance Added project closeout requirements and explanations

SENSITIVE BUT UNCLASSIFIED

iv

CONTENTS

OVERHEAD PERSISTENT INFRARED (OPIR) SITE INTEGRATION STANDARD (OSIS) ....................... I APPROVAL ................................................................................................................................................................II REVISION HISTORY ............................................................................................................................................. III CONTENTS .............................................................................................................................................................. IV

PART 1 - INTRODUCTION

1.1 PURPOSE AND SCOPE

1.2 TERMS AND DEFINITIONS

1.3 ROLES AND RESPONSIBILITIES

PART 2 - INPUT WORK PRODUCTS

PART 3 - ENTERPRISE SCHEDULING

PART 4 –BASELINE CHANGE ACTIVITIES

4.1 PROJECT SCREENING

4.2 PROJECT INTEGRATION KICKOFF (PIK)

4.3 DOCUMENT PROCESSING

4.3.1 Project Installation and Checkout (PICO) Document

4.3.2 PICO Initial Review

4.3.3 PICO Technical Roundtable Review

4.4 INTEGRATION BOARDS

4.4.1 System Integration Board (SIB)

4.5 REQUIRED BRIEFINGS POST SIB APPROVAL

4.5.1 Inbrief

4.5.2 Daily Status Briefings

4.5.3 Installation Outbrief

4.6 BASELINE CLOSEOUT REQUIREMENTS

4.6.1 Physical Configuration Audit (PCA)

4.6.2 Completed Documents

4.6.3 Equipment List

4.6.4 Drawings

4.6.5 Alternate Drawings

4.6.6 Cyber Approval

4.6.7 Hardware Lead Approval

4.6.8 System Administrator Lead Approval

4.6.9 COMSEC Approval

4.6.10 Training Approval

4.6.11 Spares Approval

4.6.12 Closure Approval

PART 5 - SOFTWARE BASELINE CHANGE ACTIVITIES

PART 6 - NON-OPERATIONAL SYSTEM USAGE ACTIVITIES

6.1 OPIR BASELINE RELEASE (OBR)

6.2 TESTING ACTIVITIES

6.3 MAINTENANCE ACTIVITIES

6.4 ASSET RETURN TO OPERATIONS

PART 7 – PROCESS OPTIMIZATIONS AND SPECIAL CIRCUMSTANCES

7.1 NETWORK UPDATES FOR OUT OF BAND MANAGEMENT (OOBM) AND SBIRS SUPPORT CENTER (SSC)

7.2 NON-SSC/SNP ENTERPRISE SYSTEM CONTROL

7.2.1 Physical Modifications

7.2.2 Logical Modifications

7.3 ALTERNATE DRAWING UPDATE PROCESS

7.4 ADMINISTRATIVE SYSTEM TECHNOLOGY REFRESH

7.5 TEMPORARY MODIFICATIONS

SENSITIVE BUT UNCLASSIFIED

v

7.6 FREEZE BOARDS

7.7 DEVIATIONS AND ADDENDUMS

PART 8 – MCS AND MCSB FACILITY SAFETY REQUIREMENTS

8.1 HAZARDOUS MATERIALS

8.2 EQUIPMENT LAYOUT, REMODELING AND NEW CONSTRUCTION

8.3 EQUIPMENT TIE DOWN

8.4 SUPPORT EQUIPMENT POWER

8.5 SECURITY REQUIREMENT FOR RACK DOORS

PART 9 – MCS AND MCSB SHIPPING AND RECEIVING

9.1 FREIGHT RECEIVING AREA

9.2 EQUIPMENT PASSAGE

PART 10– FACILITIES MODIFICATION GUIDANCE

10.1. MECHANICAL SYSTEM STANDARDS

10.1.1. Power System Characteristics

10.1.2 Grounding Standards

10.1.3 Environmental Controls

10.2 RAISED FLOOR AREA

10.2.1 Raised Floor Tile Penetrations

10.2.2 Raised Floor Tile Removal and Reinstallation

10.3 CABLE CONVEYANCES

10.3.1 Cable Trays

10.3.2 Flexible Metal Conduit

10.3.3 Conduit Junction Boxes

10.3.4 Cable Way/Wire Way, Conduit and Junction Box Labeling

10.3.5 Data Chase

10.3.6 Firewall Integrity

10.3.7 Under-floor Cable Routes

10.3.8 Overhead Cable Routes

10.4 SIGNAL CABLING

10.4.1 Cable Coloring

10.4.2 Cable Terminations

10.4.3 Cable Re-termination

10.4.4 Cable Installation

10.4.5 Cable Labels

10.5 EQUIPMENT INSTALLATION AND REMOVAL

10.5.1 Racks

10.5.2 Equipment Installation

10.5.3 Equipment Labels

10.5.4 Overhead and Above Ceiling Equipment

PART 11 - PROCESS WAIVER REQUESTS

PART 12– REFERENCE DOCUMENTS

PART 13 - ACRONYMS LIST

SENSITIVE BUT UNCLASSIFIED

PART 1 - INTRODUCTION

1.1 Purpose and Scope

Consistent with Air Force Instruction (AFI) 63-101/20-101, Integrated Life Cycle Management is the responsibility of Program Manager and Product Support Manager. The purpose of this document is to codify the modification management process for the System of Record. Modifications are changes to a Program of Record (POR) Overhead Persistent Infrared (OPIR), both Space Based Infrared System (SBIRS) OPIR Battlespace Awareness Center (OBAC) sites including hardware, software (except for major SBIRS Baseline Release updates) and networks to satisfy an approved operational mission requirement. Modifications remove or add capability or function, enhance technical performance or suitability or change the form, fit, function and interface of POR system components (AFI 63-101).

Furthermore, this document codifies the coordinated operational asset scheduling process ensuring Space Delta 4 (DEL 4) authorizes potential changes to mission operations and/or mission-employment driven by approved system-modifications. The specifics of how each type of change is handled is outlined in the various sections of this document. Finally, details related to Mission Control Station (MCS) and MCSB facility requirements are provided to include facility access, grounding standards, cable conveyances, power system characteristics and mechanical systems characteristics. The cable guidance section is applicable to all POR sites.

The OPIR Site Integration Standard (OSIS) documents achieve the follow:

‒ Operational baseline capabilities are preserved ‒ Risks to the mission-operations and the operational weapon-system baseline are minimized and understood by the Government ‒ All planned maintenance and modifications are presented on a single Enterprise Schedule ‒ Verification that configuration documentation has been updated to reflect the system changes ‒ Installation oversight through project closeout

SSC/SNPDI facilitates the following activities:

‒ A consistent Operations (Ops) Integration process is applied across the enterprise ‒ Required approvals are in place and documented ‒ Verification of Security approval (Physical and Cybersecurity) ‒ Facilities modifications are coordinated and completed ‒ All Baseline Change Closeout Requirements are complete

SENSITIVE BUT UNCLASSIFIED

1.2 Terms and Definitions

Term Definitions

Application Software

A program that performs a specific function directly for an end user or, in some cases, for another application.

Configuration Documentation

Documentation that affects the technical baseline. For example

Technical Orders (TOs)

Risk Management Framework (RMF)

Procedures, processes, test plans

Drawings that reflect the change-room layout, rack layout, cable table, physical interconnect diagrams, network interconnect diagrams and spares bill of material (BOM)

Maintenance and warranty information

All operational device configurations

System build information - Operating System (OS)/firmware level, host name, Commercial Off the Shelf listing, serial number, Internet Protocol (IP) address, equipment part number, license information, virtual machine configuration

Port, protocols and services configurations

Single Line Diagrams

Firmware The software that is “built in” to a particular piece of hardware. It can be upgraded or replaced, but it is effectively part of the hardware

Government Point of Contact

(GPOC)

Assigned government personnel responsible for the oversite of Activity Request (AR) and compliance with contractual requirements

Installing Agency

Government agency or development contractor requesting changes to POR sites

Integration Documents

Project Integration Kickoff (PIK) template, Project Installation and Checkout (PICO), Schedule Request (SR), System Integration Board (SIB) Packages and applicable meeting minutes

Logical change Logical changes are all baseline changes that do not include a physical element Examples include network changes, new or modification of Application Software, OS upgrades and adding/changing firmware within the system.

Maintenance Action

All actions required to retain an end item in or restore it to, a specified condition. This includes diagnosis, repair and inspection.

Operating System (OS)

The software that acts as the foundation layer on a computing device

Physical Modification

All changes to the physical baseline to include installation, removal and replacement.

SENSITIVE BUT UNCLASSIFIED

Term Definitions

Program of Record (POR) Site

Mission Control Station (MCS) Mission Control Station – Backup (MCSB) Survivable Mission Control Station (SMCS) Relay Ground Station MCS (RGSM) Relay Ground Station- Backup (RGSB) Survivable Relay Ground Station (SRGS) Relay Ground Station – Highly Elliptical Orbit (HEO) (RGSH) Relay Ground Station –MCS2 (RGSM2) European Relay Station (ERS) Relay Ground Station Europe (RGSE) Relay Ground Station Pacific (RGSP) Relay Ground Station (RGS) systems include work to be done within the RGS rooms as well as the radomes

Responsible Engineer (RE)

Engineer requesting/performing baseline configuration changes.

Roundtable Review (RT)

A meeting held by the Contractor Logistics Support (CLS) Ops Integration Team to review technical documentation with members of the POR Team. This review ensures that all organizations are aware of the effort and impacts associated with it.

Mitigation plans and mission assurance testing should be identified during this process.

SENSITIVE BUT UNCLASSIFIED

1.3 Roles and Responsibilities

Roles Responsibilities

SSC/SNP Director, Space Systems Command, Space Sensing Product Support Delta

Responsible for sustainment of the Remote Sensing System of Systems

SSC/SNPE Chief Engineer

Determines AF Form 1067 applicability based upon AFI 63-101/20-101 guidance and coordination with Headquarters United States Space Force (USSF), when required

SSC/SNPDI Integration Branch Chief

SIB Chair, may be delegated to another government representative

Responsible for day-to-day implementation of the

OSIS

Supervises SSC/SNPDI Team in execution of integration processes

SSC/SNPDI Ops Integration Lead

Oversees the Baseline Modification processes

Coordinates with CLS, SSC/SNPDI Systems Engineering and Integration (SE&I) Team, SSC/SNPDI Facilities Integration Team (FIT) / Schriever Support Team (SST), Hardware (HW) Depot, Product Support Facility (PSF) and other agencies to ensure all applicable processes, instructions and regulations are met

Chair at the SIB in place of SSC/SNPDI Section Chief

Approval authority for out of cycle (OOC) SIB and process deviation requests

Final Closure authority for Activity Requests (ARs)

SENSITIVE BUT UNCLASSIFIED

Roles Responsibilities

SSC/SNPDI Systems Engineering and Integration (SE&I) Team

Develops and maintains integration processes for all applicable Government organizations. Maintains approved knowledge management database (Confluence/Jira) for all projects.

Future Operations: Responsible for receiving new projects and guiding them through the OSIS process through project approval at the SIB. Tasks include:

-Schedules and facilitates all PIK meetings

-Site survey

-Reviews all documents for accuracy

-Participates in Roundtable (RT) Reviews and project coordination meetings, when possible

-Schedules and facilitates the SIB; produces minutes and documents approvals/disapprovals

-Works with GPOC, RE and CLS Integration to ensure that all Integration board requirements are met prior to presentation for approval

Current Operations: Responsible for facilitating closure of projects after approval at the SIB. Tasks include:

-Attends ESG to maintain knowledge of installation timelines

-Receives Daily Status Briefings during project installation

-Works with GPOC, RE and CLS Integration to collect all required documentation and SME concurrence for project closure

SENSITIVE BUT UNCLASSIFIED

Roles Responsibilities

SSC/SNPDI Facilities Integration Team (FIT)

Oversees facilities changes

Provides required and relevant baseline drawings to modification agency

Coordinates facility modifications as necessary for MCS equipment installations

Issues wire/cable numbers for delivered systems and upgrades. Prime contractor maintains wire numbers 1-59,999. Local facilities team issues wire numbers greater than 60,000

Provides or approves MCS cable routing through the cable tray/conduit system upon request

Maintains POR facility drawings in the three-dimensional high-fidelity model and its associated relational databases. This tool is called the Facility and Mission Equipment Management System (FAMEMS). FAMEMS is the primary tool SNP uses for facilities level configuration management

Maintains the Wire/Cable Management System database for delivered cables to include: wire/cable routing through tray segments, elevation changes, wall and floor penetrations, security classification, wire type and wire length

Reviews MCS PICOs

Completes quarterly power audits and equipment level rack connectivity Quality Assurance (QA) inspections

Provides QA inspection/sign-off for modifications as required.

Attends PIKs as necessary

Schriever Support Team (SST)

Provides logistical support for security oversight, administrative logistics, administrative computer and telephone liaison and facility manager duties

Evaluates MCSB cooling and power requirements and provides recommendations to approval authorities

Coordinates required facility changes with base civil engineering squadron

Attends MCSB PIK, RT Reviews and Integration Boards

SENSITIVE BUT UNCLASSIFIED

Roles Responsibilities

Government Point of Contact (GPOC)

Submits required Integration documentation to

SSC/SNPDI

Is involved in all communication and data transfer between the RE and SSC/SNPDI

Will attend or pre-coordinate covering the PIK, Enterprise Scheduling Group (ESG), document review, SIB Meetings

Prepares Operations Acceptance Panel (OAP) briefing charts

Installing Agency Adheres to all actions required by Contract and requirements in this document

Responsible Engineer (RE) Completes all actions required by Contract and requirements in this document

SSC/SNPDC Cybersecurity & Comm Section

Maintains POR Sustainment Security Accreditation packages

Tracks all equipment transfers in and out of POR facilities

Attends PIK, RT Reviews, Integration boards and provides government oversight for ensuring secure methodologies and technologies will be applied on all POR systems

SSC/SNPDM Maintenance/Logistics Section

Maintain Integrated Product Support Elements

Attends PIK, RT Reviews, Integration boards and provides government oversight for ensuring Logistical fidelity

Enterprise Scheduling Group (ESG)

Coordinates all segment schedule inputs to a single baseline schedule

Must work within established constraints

Verifies system performance from agreed to baseline is not compromised or decremented

Attends all OSIS related meetings as applicable

Maintains database of SRs

Contractor Logistics Support (CLS) Integration

Attends all OSIS related meetings as applicable

Facilitates RT reviews, project coordination meetings and Project Inbriefs

Coordinates with CLS to attend appropriate meetings

SENSITIVE BUT UNCLASSIFIED

Roles Responsibilities

DEL 4 S4/6 (Mission Sustainment and Integration)

Facilitate/support USSF OAP Briefings as required with HHQ and other stakeholders

Participate in Handover Approval Board (HAB) as required

Facilitate Mission Transfer Approval Board (MTAB) as required

Participates in Transitions Integrated Product Teams (IPTs)

Serves as local SSC liaison between program office and test team

Facilitates/coordinates Operations Approval Sub Board (OASB), Standard Change Form (SCFs), Air Force (AF) Form 1067s, Version Content Notification/Version Content Request (VCN/VCR) processes and assigns Universal Control Number (UCN) to approved SCFs and other system modification processes

Chairs Problem Report Working Group (PRWG)/Operational Assessment Review Board (OARB) and informs DEL 4 S4/6S of critical Problem Reports (PRs)

Participates in Government Deficiency Review Board (GDRB) as stakeholder and briefs DEL 4 Directors of Operations (DOs) and DEL 4 Commander of critical information if needed

Integrates various units across DEL 4 for system upgrades

DEL 4 S4/6O

Execute Chief of Maintenance (CoM) functions and maintenance assurance missions

Stakeholder at the SIB

Submits Schedule Requests (SRs) for external stakeholders without Enterprise Collaboration System (ECS) access

DEL 4 S4/6E

Responsible for final SR management/creating Daily Activity Schedule (DAS)

Responsible for memo-routing and approval

Coordinates usage of all operational on-orbit POR assets

Confirms Ops Impacts related to POR on-orbit assets

Develops Ops mitigation plans, coordinates with training/crews

460 Civil Engineering Squadron (460 CES) - Buckley Space Force Base

Adheres to the OSIS and site-specific standards for power/cooling and facilities related efforts/support

Attends PIK, brief projects to SIB

Facilitates submittal of applicable AF Form 332-Base Civil Engineer Work Request

SENSITIVE BUT UNCLASSIFIED

Roles Responsibilities

50 CES - Schriever Space Force Base

Adheres to the OSIS and site-specific standards for power/cooling and facilities related efforts/support

Attends PIK, brief projects to SIB

Facilitates submittal of applicable AF Form 332-Base Civil Engineer Work Request

Government Test Organization (GTO)

Reviews test plan to determine compliance with Test and Engineering Management Plan (TEMP)

Coordinates integrated testing between the contractor, developmental test organization and the operational test organization where appropriate

Special Security Representative (SSR)

Maintains all Emission Security and Sensitive Compartmental Information Facility (SCIF) accreditations

Tracks all equipment transfers in and out of POR facilities

Crew Commander

Commands the Ops floor. When required, exercises authority to stop any approved activity to mitigate risk and/or impact to operations

Delegate for DO approval

Execution/asset release authority

PART 2 - INPUT WORK PRODUCTS

The Project Installation and Checkout (PICO) and all chart submittal templates are content controlled.

Any modifications to PICO template must be approved by SSC/SNPDI prior to use.

Required Product Conditions

Enterprise Schedule This schedule captures all planned maintenance, modifications and non-operational system usage activities. The schedule is based upon submitted SRs.

Schedule Request (SR)

A DAS Schedule Request (SR) is the sole method for projects to get onto the Enterprise Schedule. Additionally, SRs must be approved by the appropriate authorities to be added to the DAS and authorized for execution following SIB approval, if required

Project Integration Kickoff (PIK) Template

This template is required for all baseline changes

The PIK charts provide an overview of the project as well as detailed information needed during the meeting

Project Installation and Checkout (PICO)

Required for all baseline changes unless specifically waived by SSC/SNPDI or other sections of this document.

System Integration Board SIB Template

This template is required for all baseline changes

The charts provide an overview of the project as well as detailed information needed to determine approval/disapproval

SENSITIVE BUT UNCLASSIFIED

Required Product Conditions

Pre/Post Installation Checklist

This checklist is used during the Inbrief to ensure that the RE has final documents, Network Control Board (NCB) configurations, approved drawings, CLS support required, etc. prior to beginning a baseline change

PART 3 - ENTERPRISE SCHEDULING

The Enterprise Schedule is managed by the Enterprise Scheduling Group (ESG). This schedule captures all planned maintenance, modifications and non-operational system usage activities. Systems Engineering and Integration Team (SEIT) is responsible for administrating the enterprise schedule in support of the government co-chairs. They will maintain the scheduling database, de-conflict efforts and provide a schedule for review twice weekly.

The ESG is held twice a week with OOC boards held as required. The objectives of this board are to work as a team to schedule activities to be completed at a POR site; screen Schedule Requests (SRs) to ensure compliance within ESG constraints and discuss project details to determine if deconfliction is possible.

SRs are located on the Enterprise Collaboration System (ECS). The SR must be submitted per ESG submission timeline requirements. All SRs submitted after the prescribed deadline will be discussed at the following ESG unless there is a critical operational or programmatic need.

The Requestor or a representative that has a solid technical understanding of the effort must be in attendance, either in person or via ECS Voice Over Internet Protocol (VOIP) or the SR will not be discussed. If time permits, the ESG will also review projects with a significant Ops impact that fall within the Line Number window to begin the de-confliction process and submission of Line Numbers for Higher Headquarters (HHQ) approval.

Any SRs that present a conflict that cannot be resolved within the ESG constraints will be elevated to the Senior Program Leadership. Government oversight requirements will be discussed and until confirmed, SR will not be reviewed for approval, which may require the SR be brought back when requirements are met.

The ESG is chaired by 2 SWS and includes key stakeholders designated by the ESG chair. After each SR is discussed, the Chairs will be asked for approval to put the SR into the signature cycle or force approved on the spot. Detailed minutes will be sent via unclassified e-mail and High-Level minutes can be provided as requested on ECS. The final SR approval will occur after SIB approval for all baseline change activities. Decisions of this board can be appealed. This meeting is open to all to attend. An ECS Live Meeting and ECS call-in will be available. The Enterprise Schedule will be presented at the SIB, to include approved and in process SRs.

PART 4 –BASELINE CHANGE ACTIVITIES

All baseline change activities are coordinated and scheduled through SSC/SNPDI. All proposed changes, unless specifically excluded in this document, will be brought to a Project Integration Kickoff (PIK) for determination of process applicability. It is SSC/SNPDI responsibility to ensure all processes, board approvals and security approvals are in place before SIB approval. The ESG ensures that the effort has been de-conflicted with other previously approved activities and that all HHQ approvals are in place.

SENSITIVE BUT UNCLASSIFIED

The process notionally has a 30-government working day timeline; however, the only “hard stop” actions built into the process are the approval boards that are on a set schedule. Once a schedule is determined all dates are No Later Than (NLT) and if a step in the process is ready earlier than what is scheduled, the next step can begin effectively shortening the schedule. Below is a synopsis of the process steps and the planned time to complete:

Step Actions Days

Project Integration Kickoff

RE Completes Chart Package

GPOC Approves and Submits

SSC/SNPDI SE&I Schedules and Facilitates

Start of Process

Document Preparation RE Completes PICO

GPOC Approves and Submits 10 Days (notional)

Document Review SSC/SNPDI SE&I Performs

RE Completes Updates (as Required)

2 Days (minimum) to

5 Days (maximum)

Technical Roundtable Review

CLS Integration Schedules and Facilitates

RE Completes Updates (as Required)

CLS Integration Finalizes

5 Days (maximum)

Signatures

SSC/SNPDI formats

RE Signs

CLS / Site Lead Signs

SSC/SNPDI Signs

5 Days (maximum)

ESG

RE Completes SR

ESG Approves Prior to SIB

SIB

RE Completes Chart Package

GPOC Approves and Submits

SSC/SNPDI SE&I Schedules and Facilitates

4 Days (hard scheduled meeting date and time)

Execution Approved

Outbrief

RE Completes Project Execution

RE Completes Chart Package

SSC/SNPDI SE&I Schedules and Facilitates

~30 days post SIB (notional)

Closeout

RE Completes Requirements

GPOC Approves Closure

SSC/SNPDI Finalizes Closure

SSC/SNPDI SE&I Archives Deliverables

~30 days post Outbrief (notional)

4.1 Project Screening

Upon receipt of a project the SEIT will review the PIK charts for scope and impact to the SBIRS Baseline and operations to determine OSIS applicability. If the project does not have an impact to the baseline or operations, the project will be off-ramped and archived on the SNPDI Confluence and JIRA pages under closed projects for record. If there is an uncertainty as to the impact of the project, the project will be brought to PIK for additional screening. The SNPDI Ops Integration Lead is the decision authority for any of these actions.

SENSITIVE BUT UNCLASSIFIED

4.2 Project Integration Kickoff (PIK)

All proposed changes, unless specifically excluded in this document, will be brought to a PIK for determination of OSIS process applicability. The purpose of the PIK is to understand the scope and impacts of a project to ensure the successful integration of a baseline change and determine project OSIS applicability and requirements.

If multiple related packages are submitted, the PIKs for the efforts may be either separately scheduled based upon the priority established by the GPOC or a single PIK may be scheduled to review all related projects. PIKs will be scheduled on Mondays and Wednesdays between 0930 and 1130 MST. The cut off for Monday PIKs is Thursday at 1200. The cut off for Wednesday is Monday at 1200 MST. Scheduling outside of these windows is authorized by the SSC/SNPDI Ops Integration lead. Attendees include but are not limited to: SSC/SNPDI, GPOC, RE, DEL 4 CoM, CLS Leads, CLS Integration, CLS Hardware (HW), CLS Network, CLS System Administration (SA), SSC/SNPDC Cyber Security, site Special Security Officer (SSO), SSC/SNPDI Facilities Integration Team (FIT) and Schriever Support Team (SST). To assist in maximum participation, the PIK is facilitated via an unclassified on-line meeting. REs will make every attempt to keep their briefing unclassified. If this proves not possible a classified meeting will be coordinated.

Installation agencies not associated with SSC/SNP that request an AR will have an SSC/SNP GPOC assigned. SSC/SNP will monitor the effort for sustainment concerns and have concurrence for project closeout.

A standard presentation is completed by the RE and must be approved by the GPOC prior to scheduling a PIK meeting. The presentation will be briefed at the PIK by the RE. Specific Instructions for filling out the PIK template are included in the template. GPOCs are encouraged to submit requests for PIK as soon as all information is available, and charts are complete; however, the PIK meeting will be scheduled not less than 30 government working days prior to project execution. For projects that have significant operational impacts requiring downtime and a line number, the RE will submit a SR to the ESG before project execution to provide time for SpOC to approve the line number. Status of the line number request should be included in the PIK presentation. RE’s will align the titles of their projects going through the OSIS process with their SR’s to the ESG to enable consistent and reliable tracking of projects through the lifecycle.

Projects requiring physical changes to Contiguous United States (CONUS) POR sites will have a site survey scheduled to determine equipment placement, cable routing, power and Heating, Ventilation and Air Conditioning (HVAC) concerns. Network, cyber and software modifications do not require a site survey. If it is determined that new racks are to be installed, a DEL 4 designated official must approve the location. It is preferable to have this survey prior to the PIK; however, it can occur either before or after the PIK. Site surveys must have the following POCs in attendance: SNPDI POC, RE, HW personnel, Facilities and Technical Director (for all installs/de-installs).

For Outside Contiguous United States (OCONUS) efforts the on-site Maintainers will review the package and determine if proposed locations are available and if the rack drawings provided reflect the installed rack content. All personnel traveling to RGSE or RGSP must comply with the SSC/SNP Implementation of the current HOST nomination requirements and procedures.

Coordination actions are completed by the RE. During the PIK there is discussion on what items need coordination before project approval. These coordination items are captured in the PIK Minutes. PIK

SENSITIVE BUT UNCLASSIFIED

minutes are distributed to all parties upon completion of the PIK. All project data is subsequently captured and maintained on the project’s Confluence and Jira pages, as well as archived for Integration team’s discretion.

Projects that have not received SIB approval within six months of project kickoff will be required to restart the integration process from the beginning. If the project was originally brought to PIK in a previous calendar year, the project will be assigned a new Activity Request number and the associated confluence page will be moved to the current year. Exceptions to this process will require a waiver request at the approval of the Ops Integration Lead.

4.3 Document Processing

Documentation for a project is vital to successful baseline integration. The required document is completed by the RE, approved by the GPOC, reviewed by SSC/SNPDI and the Community to ensure technical accuracy. Once Final, the documentation is signed by the RE, the CLS management team and the SSC/SNPDI Ops Integration Lead.

4.3.1 Project Installation and Checkout (PICO) Document

The PICO fully captures and documents the entire scope of the project being performed. The PICO documents all steps being performed, equipment, software, modifications (physical and logical), personnel, locations among other material details of the project.

The purpose of the PICO is to:

Provide all stakeholders with a written and detailed record of the project for review, discussion, and approval at the Roundtable. After the Roundtable, the signed PICO serves as the major milestone in the projects authorization to proceed.

Document all changes being performed on the OPIR Baseline.

Collect the data required to fully coordinate a modification to the Baseline and defines planned sustainment following closeout.

Serve as a physical record of project performance using initialized perform and confirm signature blocks adjacent to each step of the process.

Provide a physical record of project performance to the Subject Matter Experts (SME’s) that are assigned to project validation.

Provide a physical record of project performance to SSC/SNPDI for verification of performance and close-out authorization.

Serve as an enduring physical record of the project’s existence for future reference.

For physical installations a separate PICO will be required for each site at which the modifications will be completed. Logical changes for multiple sites can be combined if all changes are executed from a single site. The PICO must be returned to SSC/SNPDI with all installation and verification steps signed-off before a project will be granted close-out authorization.

The PICO captures the following information:

An overview of the project Support required from CLS, FIT, SST or other agencies Training to be delivered as part of the project

SENSITIVE BUT UNCLASSIFIED

Network changes and approvals Software changes and approvals Step by step instructions on how changes will be made and verified Step by step plan on how mission operations will be restored if negatively impacted Full listing of risks to equipment and operations Full list of all equipment, material, and fixtures to be removed or installed A detailed cable table showing type of cabling and connectors and all connection points A list of drawings or interface documents that require updating Network diagrams, room and rack depictions of areas that will be modified Validation signature blocks for independent SME’s (Cyber, System Administrator, etc.)

Complete listing of actions needed to closeout the AR

During project execution, the steps in this document are to be checked off as completed to serve as a record of completion. If, during the completion of the PICO, the RE determines that deviations to the plan are required work must stop. The PICO template includes guidance to be followed in this situation.

Following Post installation, the PICO showing all steps complete must be provided to SSC/SNPDI SE&I for archival as part of project closeout.

Specific Instructions for filling out the PICO are included in the template. The PICO template is locked to maintain formatting but may be modified to accommodate varying implementation strategies in coordination with SSC/SNPDI SE&I. RE and SSC/SNPDI SE&I will work together to complete template modifications. All elements of the PICO plan are required, therefore, altering or deleting content is not permitted by the RE once the Signed PICO is published. Sections that are not applicable to the installation effort may be marked NA and will be deleted prior to approval and signature.

4.3.2 PICO Initial Review

Once the PICO approved by the GPOC has been received, it will be reviewed by SSC/SNPDI SE&I and subsequently routed to CLS Ops Integration to verify the content is accurate and complete. This review is not for technical accuracy, but to ensure all required tabs are complete and cross-referenced (i.e., if a network device is to be changed, device is listed for change, steps to make the change and verify the change are included and risks associated with the change are identified). If during this review the reviewing team finds incomplete content the review will stop, and the document(s) will be returned to the GPOC/RE for rework. The reviewing team requires a minimum of two business days to conduct their initial review, but will not take more than five business days. Once the content is verified accurate and complete, SSC/SNPDI SE&I will schedule the Technical Round Table.

4.3.3 PICO Technical Roundtable Review

The Technical Round Table is a multi-site peer review chaired by the SSC/SNPDI Ops Integration Lead and facilitated by SSC/SNPDI SE&I. It serves as a pre-requisite for SIB presentation to request approval and is conducted as needed on Tuesdays and Thursdays. The Technical Round Table objective is for the community to ensure accuracy and completeness of the PICO while assessing any risk or potential operational impacts in performing the activity and to determine the best way to mitigate any identified risks or potential operational impacts. The community must issue concurrence before the activity can be presented to the SIB to be approved for implementation.

When notified that the CLS Ops Integration initial review is complete, the SSC/SNPDI SE&I will schedule a Roundtable (RT) Review with appropriate Subject Matter Experts (SMEs) to ensure the PICO is technically accurate and complete. SSC/SNPDI SE&I records minutes during the Roundtable Review

SENSITIVE BUT UNCLASSIFIED

and provides them to the RE for PICO updates. The RE must answer questions and/or incorporate the comments derived from the review into the document. Minor changes to the document can be updated during the meeting. Any major updates must be completed by the RE and resubmitted to SSC/SNPDI SE&I for review. The Government Ops Integration Lead will determine minor versus major changes and if it necessary for SSC/SNPDI SE&I to schedule a follow-up review. SSC/SNPDI will format the Final PICO, insert the appropriate signature blocks and route the documents for approval signatures. Projects that have not submitted SIB charts for approval within three months of the Round Table will be required to return the project to Round Table to re-familiarize the stakeholders.

4.4 Integration Boards

The purpose of Integration Boards is to provide Government oversight and final installation approval authority for all activities conducted within POR sites. The process will ensure all potential risks have been identified, minimized and communicated to all stakeholders prior to implementation.

4.4.1 System Integration Board (SIB)

The SIB presides over modifications to OPIR operational ground segments. The SIB, in conjunction with the ESG, is the final milestone and approval authority to proceed with all modifications to the ground baseline. The SIB is chaired by SSC/SNPDI, who authorizes ground modifications to proceed with the concurrence of the stakeholders. The SIB is held Tuesday and Thursday per week as required; however, an out of cycle (OOC) SIB can be scheduled with approval of SSC/SNPDI Chair.

The SIB does not preside over operational maintenance actions including diagnosis, repair and inspection.

These actions are under the purview of the ESG.

All Integration Board packages will be updated by the GPOC/Requestor with all SIB action items complete NLT noon the day prior to the SIB. Packages will not be presented to the SIB with outstanding action items unless completion is imminent.

SSC/SNPDI will verify that the following coordination for project execution has been completed or scheduled as required:

‒ Enterprise Scheduling Group Approved ‒ Dedicated CLS, Site, Other Organization Support ‒ CLS Inbrief ‒ Cyber Security ‒ Incoming Equipment Form ‒ OPIR Battlespace Awareness Cell (OBAC) / Tools, Application and Processing (TAP) Lab ‒ Training ‒ Drawings Approved ‒ PICO Signed ‒ Engineering Integrations Work ‒ Network Control Board

SSC/SNPDI SE&I facilitates the SIB. This team will produce the SIB presentation and distribute the day before the SIB. A GPOC is required for each effort that is presented to the SIB and must be present during the board. The GPOC and/or RE presents details of the activity under review, install plan, possible risks, mission assurance testing and mission restoration plans. Based on the information presented, the Board, consisting of the SSC/SNPDI Ops Integration Lead, GPOC, and Government Stakeholders

SENSITIVE BUT UNCLASSIFIED

identified in the PIK determine if the activity may proceed as requested. Issues identified by the taken as action items that must be completed prior to returning to the Board. The Project must be Board approved before proceeding with the activity.

To assist in maximum participation, the SIB is facilitated via an unclassified on-line meeting. REs will make every attempt to keep their briefing unclassified. If this proves not possible a classified meeting will be coordinated.

4.5 Required Briefings post SIB Approval

4.5.1 Inbrief

An inbrief is held for all baseline changes typically the day of or the day before the scheduled start date.

CLS Ops Integration facilitates this meeting. RE must pre-coordinate inbrief prior and may not start project until inbrief has been completed and Problem Report (PR) opened if applicable. Participants include the RE and the GPOC, Site Manager, Deputy Site Manager or Site Chief Ops Engineer, FIT, SST, CLS Leads and any other individuals identified in the PICO to provide support may be invited. The Pre/Post Installation Checklist is reviewed, to include site rules of engagement during the inbrief.

4.5.2 Daily Status Briefings

Daily status briefings are required for any activity that spans across several days to completion. The RE or Requestor will provide an end of day status report each day of the effort to both the CLS and SSC/SNPDI. We request the report will includes tasks completed, any issues identified and the plan for the next day Activity Request number (AR #), actions completed in the last 24 hours, planned actions for the 24 hours, planned actions not completed, issues identified and areas in need of assistance.

4.5.3 Installation Outbrief

The RE will attend the SIB to provide an installation Outbrief. The Outbrief template will be completed and presented at the SIB once all PICO actions are complete. The RE will identify problems encountered and any open issues. The items required for closeout will be presented for awareness of what remains to be done. Finally, the community will be permitted to ask questions or voice concerns with project completion and readiness for closeout.

4.6 Baseline Closeout Requirements

Baseline Closeout Requirements are reviewed during the PIK to determine which items apply to the effort. The GPOC/RE works with SSC/SNPDI, CLS Ops Integration, Cyber and CLS Leads to complete each item. Objective evidence is required for each item and will be filed as part of project closeout.

4.6.1 Physical Configuration Audit (PCA)

The Physical Configuration Audit (PCA) is a quality assurance/quality check (QA/QC) of physical modifications to POR sites as directed in the PICO. This is a requirement upon completion of the installation if directed in the PIK. If the installing agency does not have an internal QA, the FIT will provide the QA. The PCA documentation will be sent to the SEIT as part of closeout requirements upon completion of the QA.

SENSITIVE BUT UNCLASSIFIED

4.6.2 Completed Documents

A completed PICO includes all CLS lead and Crew Commander signatures pertaining to the scope of the project as determined in the PIK. The document must show all modification steps complete including step by step verification from CLS and TTO leads if applicable.

4.6.3 Equipment List

A list within the PICO of all equipment coming in/out of the MCS/MCSB. This should align with the in/out form required for submission to the SSR except for serial numbers.

4.6.4 Drawings

Updated drawings are required for any physical or logical modifications to existing baseline drawings.

These will be reviewed by the Hardware Control Board for approval prior to submission to SNPDI. These drawings are separate from floor plans, cable routes and network drawings. Logical changes diagrams and/or drawings will be reviewed by the Network Control Board for approval prior to submission to

SNPDI.

4.6.5 Alternate Drawings

Alternate drawings are required for any physical or logical modifications to existing baseline drawings when the project engineering is not approved by the Boulder Hardware Control Board. These drawings are coordinated through the CLS Hardware Depot drawing team. These are separate from floor plans, cable routes and network drawings.

4.6.6 Cyber Approval

The assigned Cyber lead determined in the PIK has signed off on PICO or has given concurrence that work was completed as directed. This is required when any level of Security Impact Assessment (SIA) is present.

4.6.7 Hardware Lead Approval

The assigned Hardware lead determined in the PIK has signed off on PICO or has given concurrence that work was completed as directed. This is required when any hardware modification is present.

Concurrence by email is acceptable, to which this and the date it was given will be documented.

4.6.8 System Administrator Lead Approval

The assigned System Administrator lead determined in the PIK has signed off on PICO or has given concurrence that work was completed as directed. This is required when any software modification is present.

SENSITIVE BUT UNCLASSIFIED

4.6.9 COMSEC Approval

The assigned COMSEC lead determined in the PIK has signed off on PICO or has given concurrence that work was completed as directed. This is required when any COMSEC modification is present.

4.6.10 Training Approval

The assigned lead determined in the PIK has signed off on PICO or has given concurrence that training was completed as directed. This is approval is required when training is given to operators or maintainers.

The approval for training is assigned from the audience the training pertains to.

4.6.11 Spares Approval

The assigned lead determined in the PIK has signed off on PICO or has given concurrence that spares are provided if required in the scope of the project.

4.6.12 Closure Approval

Projects will be closed by SSC/SNPDI Ops Integration Lead with written concurrence of project GPOC once all tasks are completed. If the RE or GPOC on record are no longer associated with the project, a memorandum for record will be signed by SNPDI Government lead as an overcome by events (OBE) circumstance. All data is archived following closure.

PART 5 - SOFTWARE BASELINE CHANGE ACTIVITIES

All additions, removals, modifications, patches, etc. to Operating Systems, Firmware and Application Software are subject to this document, unless specifically excluded. If during the PIK it is determined that the change activity has been fully vetted by HHQ and SSC/SNPDC and poses minimal risk to the system approval may be relinquished to the ESG and SSC/SNPDC. SSC/SNPDC will track the change and perform closeout.

PART 6 - NON-OPERATIONAL SYSTEM USAGE ACTIVITIES

Non-operational system usage activities are requests to utilize system resources with no change to form, fit, function or interface. Approval for these activities is controlled by the ESG and no PIK is required.

This includes maintenance activities such Preventive Maintenance Inspection (PMI) and usage activities for development, training, etc. The requestor will submit a SR and attend the ESG to request the time and resources required to complete the activity.

6.1 OPIR Baseline Release (OBR)

The formation of content, implementation and testing of OPIR Baseline Releases are vetted and tracked by a separate process and do not require a PIK.

6.2 Testing Activities

Baseline activities may require additional test actions to validate functionality. The associated test plan coordination for these activities falls outside the scope of the OSIS and will be managed by the designated

SENSITIVE BUT UNCLASSIFIED

Government Test Organization (GTO). Planned testing will be briefed at the PIK; included in the Project Installation and Checkout (PICO); and be briefed to the System Integration Board (SIB). Testing schedule will be approved by the ESG.

External test activities involve connectivity to other users or use POR operational assets such as End-to- End (E2E) testing and utilizing an RGS for uplink/downlink testing. For E2E testing, the operations crew commander retains responsibility for the POR mission and must be coordinated with. The crew commander serves as oversight of the POR mission and the military liaison as required. For testing that utilizes RGS, the RGS Safing procedures can be used as requested by the site maintainers. A test plan, test objective worksheet or Air Force procedure for the external test activity must be identified in the SR.

6.3 Maintenance Activities

Maintenance activities include normal PMIs, break-fix actions, Level 1s, part replacements, etc. Planned maintenance activities should follow the ESG process and submit a SR to de-conflict asset usage.

Unscheduled maintenance should be briefed to the ESG if possible and de-conflicted real-time as necessary. System modifications shall not be implemented as maintenance activities.

6.4 Asset Return to Operations

Following a maintenance or usage activity, the assets are returned to operations. Usage activities do not include modifications (changes to form, fit, function or interface) to the system and do not require regression testing upon return to operations. Operational crews and CLS should perform normal checkout activities upon asset return.

PART 7 – PROCESS OPTIMIZATIONS AND SPECIAL CIRCUMSTANCES

7.1 Network updates for Out of Band Management (OOBM) and SBIRS Support Center (SSC)

The POR network is separated in that certain devices provide capabilities to perform the operational mission and other devices provide capabilities that support the operational mission. The devices that support the operational mission are OOBM and SSC. Since these devices cannot directly impact the performance of the operational mission, a more streamlined approach, determined during the PIK may be applied. These efforts will not contain any physical elements to include cable changes.

7.2 Non-SSC/SNP Enterprise System Control

To achieve the purposes of the OSIS it is necessary to apply controls regarding all physical changes within POR sites. These controls are necessary since the facility (space, power, cooling, cable tray, etc.)

must be managed appropriately to prevent unintended operational impacts irrespective of controlling authority.

7.2.1 Physical Modifications

Physical installation of or modifications to all current or future systems installed within POR site that are managed and maintained by external organizations will fall under the purview of the OSIS and will require a PIK to determine impacts and OSIS applicability.

SENSITIVE BUT UNCLASSIFIED

7.2.2 Logical Modifications

Logical changes within these systems that do not interface with the POR are controlled by the external organization and are outside the OSIS process. Systems where logical only changes are not managed by the OSIS include, but are not limited to:, Defense Red Switch Network (DRSN), Secure Terminal Equipment (STE), (Air Force) Satellite Control Network ((AF)SCN), Lockheed Martin Internet (LMI), Northrop Grumman Internet (NGI), National Geospatial-Intelligence Agency (NGA) Net, Secure Internet Protocol Router/Non-Secure Internet Protocol Router (SIPR/NIPR), Joint Worldwide Intelligence Communication System (JWICS), Host VOIP, Government Wide Area Network (GWAN), Ballistic Missile Defense System (BMDS) Overhead Persistent Infrared Architecture (BOA), Command and Control, Battle Management and Communications C2BMC, SBIRS Auxiliary Support Center (SASC)…