Attachment 1 - Draft Statement of Work.pdf

Solicitation Number: PR 82-4009-24 Attachment (1)

Date: 03/27/2024

Statement of Work Spacecraft Engineering, Software, Research and Development Services Version 1

Contents 1 Introduction

1.1 Scope

2 Performance Requirements

2.1 Spacecraft and Payload Integration and Test (I&T)

2.1.1 Ground Integration and Test Software

2.1.2 Mission Simulation

2.1.3 Integration and Test Ground Support Equipment

2.2 Real-Time Embedded Software

2.2.1 Embedded Software Life Cycle Expertise

2.2.2 Embedded Software Engineering Tools

2.2.3 Embedded Platforms for Flight Software

2.2.4 Embedded Software System Skill Set

2.2.5 Software System Engineering Contributions to System Design

2.2.6 Flight Software Engineering Contributions to Mission Operations

2.3 Other Software

2.3.1 Infrastructure Support

2.3.2 Utilization of Third-party and Open Source Software

2.3.4 FPGA Software

2.4 Program Support

2.4.1 Software Project Management

2.4.2 Technical Writing

2.4.3 Software Quality Assurance

3 Special Requirements

3.1 Security

4 Acronyms

Statement of Work (SOW) Spacecraft Engineering, Software, Research and Development Services

1 Introduction The Naval Center for Space Technology (NCST), located at the U.S. Naval Research Laboratory (NRL) in Washington, DC, is the designated lead laboratory for Navy space programs. NCST has the mission to “preserve and enhance a strong space technology base and provide expert capabilities in the development and acquisition of space systems which support Naval missions.”

NCST has the primary responsibility to develop space systems, spacecraft payloads, tactical communications, and aerospace systems, and to actively pursue emerging technologies in an effort to advance space, tactical, and aerospace system development.

The NCST defines system requirements based on overall mission objectives, develops alternative system architectures, designs and develops systems and subsystems, and implements technologies to achieve optimized operational systems.

The NCST has several on-going advanced science and technology space programs at various states of the development process. These programs are developed and tested at NRL and many use the Blossom Point Tracking Facility (BPTF) as the ground systems responsible for flight operations.

Over the past 25 years the NCST has developed, enhanced, and maintained a collection of software used for design, development, test, launch, and mission operations of DoD space assets. This software is constantly being enhanced to provide state of the art solutions to space applications. The core suite of software components are used in all aspects of the spacecraft or component life-cycle.

1.1 Scope

NCST develops spacecraft for DoD, NASA, and numerous other Government agency customers.

These efforts have resulted in successful satellite operations in low, medium, highly elliptical, and geosynchronous orbits. The ability of the center to rapidly produce cost effective and reliable spacecraft and components is directly related to the experience of the engineering team and the ability to apply and modify development techniques, software procedures, processors, and other hardware components to accomplish new requirements. A vast collection of reusable and application specific software components, test procedures, operating system modifications, and other software has been collected and organized. This collection requires continued new development, enhancement, maintenance, test, and configuration management as required by new programs.

Efforts of the tasks delineated in Section 2, Performance Requirements, below will be conducted in coordination with Principal Investigator (PI) led research teams that may include Government scientists and other Contractors. The quality and timeliness of the provider's contribution to the work will be evaluated in terms of its impact on the success of the overall project.

This Statement of Work (SOW) defines the technical and managerial tasks required to design, develop, test, maintain, enhance, and provide configuration control for all software modules related to spacecraft and space component development/test and system operations. This includes:

1) Spacecraft and Payload Integration and Test

2) Real-time Embedded Software

3) Other software

4) Program Support

2 Performance Requirements The following section specifies the Performance Objectives and Performance Elements for the contract.

2.1 Spacecraft and Payload Integration and Test (I&T)

NCST is often the system integrator for spaceflight and prototype components and systems developed in-house or by government and industry partners. Depending on program requirements, NCST will be responsible for assembly, verification, validation, integration, test, and/or acceptance of hardware and software component(s) of a higher level assembly (HLA) (ie payload, subsystem, system, spacecraft, or space vehicle). At the next level of integration, NCST will assemble, integrate, and test the HLA. Testing varietals include, but are not limited to health checks, functional, performance, qualification, lifetime, compatibility, EMI/EMC, vibration/acoustic, thermal balance, thermal cycle, thermal vacuum. These test campaigns will vary in rigor and duration depending on customer requirements.

In order to support the wide range of possible test campaigns, NCST requires a robust software capability to command, control, and assess the unit under test at all levels of integration. This is accomplished with a combination of COTS, GOTS, and mission unique software (MUS). The COTS/GOTS solutions generally fall into two categories for I&T: Command and Control (C2) and Real Time Operating System (RTOS). Legacy systems use Neptune for C2 and VxWorks for RTOS. The contractor shall have expertise with VxWorks, and the design, development, testing, and maintenance of MUS within the Neptune environment. For future programs, the contractor will assist the government in assessing the right C2 and RTOS tools for the job. Other COTS/GOTS components should be evaluated for use, applicability, and cost at government direction. The contractor shall have expertise in other COTS/GOTS solutions for C2 and RTOS.

The contractor shall provide engineering and operations support for spacecraft and payload Integration and Test (I&T). The contractor shall provide I&T architecture used in the design and development of command and telemetry processing, testing of hardware specific interfaces, and test procedure development from box to system to complete spacecraft/component acceptance testing. The contractor shall utilize C2 software and the test system specific device control and status libraries to develop systems that satisfy the requirements of full spacecraft development, acceptance testing and pre/post launch processing and analysis. The requirements for Spacecraft and Payload Integration and Test are separated into three sections: a) Ground Integration and Test Software; b) Mission Simulation Software and c) Integration and Test Ground Support Equipment.

2.1.1 Ground Integration and Test Software

The contractor shall provide software engineering and hardware integration expertise in support of the spacecraft and payload development, integration and test efforts. The contractor shall use common hardware and software components to support Command, Telemetry & Data Handling (CT&DH), Flight Software, Payload and Spacecraft development, integration & test activities. The contractor shall develop the ground integration and test software such that it will integrate effectively and efficiently into the C2 software based operational ground system to support flight and mission operations. The existing I&T ground software code base represents a C2 software application layer that shall be reused and/or adapted to future spacecraft and payload development efforts. The contractor shall continue the growth and adaptation of the existing reusable code bases to new space missions. The contractor shall provide command formatting, command transmission, telemetry acquisition, telemetry decommutation, telemetry analysis, embedded memory & log handling, Ground Support Equipment (GSE) control/monitoring, Simulation control/monitoring, time synchronization control/monitoring, and automated test control in support of the I&T Ground Software system deployments.

2.1.1.1 The contractor shall design, develop, test, and deploy spacecraft related integration and test ground software components. The contractor shall generate the following specifications and documentation: system design review presentations, software development plan, software requirements, interface requirements, interface definitions, detailed design, technical notes, unit test results, test plan, test descriptions, test results and user guides. The contractor shall tailor the development approach and documentation requirements to be commensurate with sponsor, NCST, budget, schedule and risk constraints. The contractor shall apply the techniques and design approaches necessary to maximize the application of existing software components, maximize the potential for future reuse, expand the functionality of the existing code base to support new requirements, incorporate generic and non-proprietary ground I&T software components & concepts from other organizations, and adhere to existing and emerging interface standards. NCST recognizes the criticality and costs associated with component and system level test efforts. The contractor shall provide incremental improvements in test coverage and test automation while reducing cost and schedule by continuously evaluating the test approach, technique and tools.

2.1.1.2 The contractor shall design, develop, and deploy automated test procedures using the scripting language provided by the C2 software. The contractor shall generate the following specifications and documentation: test plans, test descriptions, anomaly reporting and test results.

The automated test procedures shall be used to space flight qualify for the CT&DH, Flight Software, Spacecraft and Payload. Furthermore the automated test procedures may be used for space flight qualification of other spacecraft avionic components. The development of the test plans, test descriptions and automated test procedure require a high degree of insight into the spacecraft HW subsystems, spacecraft SW subsystems, GSE, Simulation SW, and I&T Ground SW. The contractor shall refine the UUT test plan and test description working with the Unit Under Test (UUT) engineers. The contractor shall develop and deploy the UUT automated test procedures and exercise these procedures as part of the space flight qualification of the UUT.

2.1.1.3 The contractor shall provide support to transition C2 and test software to operational environment for mission operations. The contractor shall reduce mission operations development cost and risk by using proven techniques using common software and procedures for I&T and migrating the source to the C2 software ground station.

2.1.2 Mission Simulation

The contractor shall support the Mission Simulation Software. The NCST approach is to use a common simulation software approach to support the CT&DH, Flight Software, Payload and Spacecraft development, integration and test activities. Furthermore, the NCST approach is to develop the Mission Simulation software such that it will provide a high fidelity spacecraft simulation capability when used in HWIL configurations. The existing mission simulation software code base is comprised of an embedded component and a supporting C2 application layer component. These components shall be reused and/or adapted to future spacecraft and payload development efforts. The contractor shall support the growth and adaptation of the existing reusable simulation code bases to current and new space missions. In support of Mission Simulation Software system deployments, the contractor shall provide hardware interface protocols, interface testing, spacecraft component modeling, spacecraft dynamics modeling, orbit modeling, sensor field of view modeling, time synchronization, propulsion system modeling, thermal modeling, mechanism modeling, and electrical power system modeling.

2.1.2.1 The contractor shall support the design, development and deployment of the Mission Simulation software components. The contractor shall support the generation of the following specifications and documentation: system design review presentations, software development plan, software requirements, interface requirements, interface definitions, detailed design, technical notes, unit test results, test plan, test descriptions, test results and user guides. The contractor shall tailor the development approach and documentation requirements to be commensurate with sponsor, NCST, budget, schedule and risk constraints. The contractor shall apply the techniques and design approaches necessary to maximize the application of existing software components, maximize the potential for future reuse, expand the functionality of the existing code base to support new requirements, incorporate generic and non-proprietary simulation and modeling software components & concepts from other organizations, and adhere to existing and emerging interface standards.

2.1.3 Integration and Test Ground Support Equipment

The contractor shall assist in the specification of the I&T Ground Support Equipment (GSE). The contractor shall facilitate the specification, design, development, test and deployment of GSE embedded software. The contractor shall use a common hardware and software design for the development, integration & test of the CT&DH, Flight Software, Payload, and Spacecraft. The contractor shall provide support for existing NCST I&T GSE, which contain common and reusable components used for stimulation and/or monitoring of all UUT interfaces. The GSE capabilities in conjunction with I&T ground and simulation software provide an environment in which all interfaces can be exercised in a flight equivalent fashion. The contractor shall configure the GSE and associated software support modules and provide the functionality required for fully automated design and production testing. The contractor shall use the GSE HW and related software components designed to provide a high fidelity spacecraft simulation capability when used in conjunction with hardware in the loop (HWIL) configuration. The contractor shall continue the growth and adaptation of the existing GSE hardware and software architecture to support new

NCST spacecraft subsystem and system level testing. The contractor shall evaluate spacecraft system and subsystem test requirements and use this evaluation to develop GSE hardware interface and software specifications.

2.1.3.1 The contractor shall design, develop, test, and deploy embedded GSE software. The contractor shall modify, enhance, and create device specific interfaces for real time data collection and GSE control by understanding the internals of the real time operating systems (RTOS). The contractor shall configure the ROTS based GSE, the C2 software based test system, the application specific interfaces, and the spacecraft hardware unit under test for performance, environmental, and acceptance testing. The contractor shall design, develop, and configure management of automated procedures that are used during integration and test in order to use proven and tested sequences during launch and mission operations. The contractor shall modify the software source code and automated procedures to replace the GSE interfaces and simulation practices with real time operational data in order to create operational procedures.

2.1.3.2 The contractor shall generate the following specifications and documentation: system design review presentations, software development plan, software requirements, interface requirements, interface definitions, detailed design, technical notes, unit test results, test plan, test descriptions, test results and user guides. The contractor shall tailor the development approach and documentation requirements to be commensurate with sponsor, NCST, budget, schedule and risk constraints. The contractor shall apply the techniques and design approaches necessary to maximize the application of existing software components, maximize the potential for future reuse, expand the functionality of the existing code base to support new requirements, incorporate generic and non-proprietary embedded GSE software components & concepts from other organizations, and adhere to existing and emerging interface standards.

2.2 Real-Time Embedded Software

2.2.1 Embedded Software Life Cycle Expertise

The contractor shall design, develop, test, verify and deploy a wide range of real-time embedded software components. The contractor shall develop flight software components for both the spacecraft bus and application specific payloads and experiments. The contractor shall develop mission specific real-time embedded software for control applications like robotics, guidance and navigation, thermal regulation, machine-vision, and machine-learning. As dictated by the program manager, the contractor shall generate software specifications and documentation to include but not limited to: system design review presentations, software development plans, software configuration management plans, software requirement specifications, interface requirements, interface definitions, detailed software design and architecture technical data packages, unit test results, test plans, test descriptions, test results and user guides. The contractor shall be prepared to tailor the development approach and documentation requirements to be commensurate with sponsor, NCST, budget, schedule and risk constraints.

2.2.1.1 The contractor shall adhere to software development standards, practices, policies, and guidelines established by NCST program management or NCST software development section leads. All decisions for embedded and flight software code development, management and distribution must have coordinated approval with NCST program management or NCST software development section leads.

2.2.2 Embedded Software Engineering Tools

The contractor shall utilize the existing NCST tool sets that comprise the infrastructure used over the full flight software development life cycle. These tools encompass requirements tracking, interface definition, modeling, simulation, auto-code generation, auto document generation, operating systems, integrated development environments, computer aided software engineering, compilers, configuration management, problem tracking, unit test tool sets, static code analysis tools, runtime code analysis tools, performance monitoring tools, test requirement tracking, test result tracking and Programmable Read Only Memory (PROM)/Electrically Erasable Programmable Read Only Memory (EEPROM) programming techniques. Embedded software support often requires the tight integration with Field-Programmable Gate Array (FPGAs). The contractor shall provide expertise in FPGA software interfacing. In addition to providing expertise required to adequately utilize the existing tools sets, the contractor shall support NCST in expanding the role of automated tools and providing the means to integrate these tools into the NCST software development process.

Tool sets will include but are not limited to:

Databases: Microsoft Access, MySQL, NoSQL Code Analysis Tools: Lint, Wind River tools, Clang Analyze, Klocwork CASE: UML Modeling CM: CVS, SVN, Git Problem Tracking: MantisBT, JIRA, GitLab Document Generation: Microsoft Word, ADOBE PDF Requirements Tracking: JAMA Test Tracking: JAMA and Atlassian tools Automated Testing: Jenkins, Continuous Integration & Testing, CMake/CTest, Python test automation Operating Systems: Windows, VxWorks, Realtime and COTS Linux variants including Red Hat and Ubuntu.

Compilers/Languages: GNU GCC, LLVM/Clang, C, C++03 and earlier, C++11 and greater (modern C++), Java, Python, CMake, Makefile, shell scripting, GDB, LLDB, PPC/Arm/x86 Assembly

Modeling and Simulation: Matlab/Simulink, game engines (e.g. Unreal Engine) IDEs: Visual Studio, Wind River VxWorks

These tools encompass requirements tracking, interface definition, modeling, simulation, auto-code generation, auto document generation, operating systems, integrated development environments, computer aided software engineering, compilers, configuration management, problem tracking, unit test tool sets, static code analysis tools, runtime code analysis tools, performance monitoring tools, test requirement tracking, test result tracking and PROM/EEPROM programming techniques.

2.2.3 Embedded Platforms for Flight Software

To support the Flight Software embedded subsystems, the contractor must show extensive experience with radiation hardened embedded processors, memory constrained systems, processor bandwidth constrained systems, I/O constrained systems, embedded operating systems, command reception & processing, telemetry acquisition & reporting, diagnostics, spacecraft avionics and payload interfaces, memory and log management, redundant systems, fault detection isolation and recovery algorithms, spacecraft subsystem closed loop control, attitude determination & control algorithms, guidance & navigation algorithms, spacecraft autonomy and onboard data reduction & analysis.

The contractor shall develop and maintain software components compatible with embedded processors including but not limited to Zync, Raspberry PI, Atmel microcontrollers, 8051 microcontrollers and PowerPC, Arm, and x86 based processors. The contractor shall apply the techniques and design approaches necessary to maximize the application of existing software components, maximize the potential for future reuse, expand the functionality of the existing code base to support new requirements, incorporate generic and non-proprietary flight components and concepts from other organizations and adhere to existing and emerging interface standards.

The requirements, complexity and performance of flight software components are highly dependent on the embedded hardware architecture and hardware interfaces. The contractor shall provide digital hardware design, FPGA capabilities and digital interface protocols to the extent that the contractor can coordinate with digital hardware designers to develop a balanced approach that will help minimize overall system complexity and cost. The specification of the design, development and implementation of the embedded software systems shall require expertise in the area of fault tolerant control systems with emphasis on attitude control, fault tolerance and safety compliance.

2.2.4 Embedded Software System Skill Set

The contractor shall provide the following skill set:

• Embedded software system design and documentation

• Embedded software development environments

• Embedded software problem tracking, CM and release engineering

• Embedded real-time and near real-time operating systems

• Operating system integration with embedded processors

• Embedded device drivers

• Interrupt service routines

• Exception processing

• Diagnostic tool sets compatible with operating systems, embedded applications, embedded hardware and test sets

• Performance monitoring and performance improvement techniques

• Built-in-tests

• Software and hardware redundancy techniques

• Standardized inter-task and inter-processor communication techniques

• Resource management (memory, logs, parameter tables, configuration tables, priorities, locks, task control)

• Telemetry acquisition, reporting, and logging

• Command acceptance, distribution, disposition, and logging

• Closed loop control in support of spacecraft or payload power, guidance, navigation, attitude control, thermal, mechanical, propulsion, ordnance, robotic and radio frequency subsystems

• Time knowledge and maintenance algorithms

• Payload data interface and data handling techniques

• Hardware protection techniques

• Fault detection, isolation, and recovery techniques

• Autonomous Tasking

• Auto-code generation

• Embedded hardware integration

• Embedded hardware testing

• Embedded software test planning and test execution

• Embedded hardware test planning and test execution

• System on a chip software development

• Development and deployment of machine learning models on embedded targets

• Algorithm development for highly parallelized vector and graphics processing units

2.2.5 Software System Engineering Contributions to System Design

The contractor shall provide technical proposals; flight component software requirements and design; interface control descriptions and documentation; liaison meetings between hardware and structural engineering personnel; test system requirements and design; and spacecraft avionics requirements and design. The contractor shall provide engineering and development support for system, subsystem and component level prototyping and path-finding tasks.

2.2.6 Flight Software Engineering Contributions to Mission Operations

The contractor shall support spacecraft flight operations from final acceptance testing to launch through mission operations. The contractor shall support development of nominal mission and anomaly resolution procedures, and implementation of automated ground and flight based procedures. The contractor shall provide operational scenario test development for flight hardware, flight software, ground station compatibility and training. The contractor shall provide support to the flight operations team during launch and mission operations as required for the mission or when determined necessary by the COR.

2.3 Other Software

The contractor shall provide computer system administration and communication system development. These capabilities include: server configuration and maintenance; workstation configuration and maintenance; relational database design, configuration and maintenance;

configuration management; error tracking, reporting, resolution, and documentation; and communication network design, development, administration, and trouble-shooting. The contractor shall provide software expertise and experience with real-time embedded systems, reconfigurable computers as well as Windows and Linux-based workstations.

2.3.1 Infrastructure Support

The contractor shall provide System Administration for all related computer operating systems used in performance of the preceding requirements. The NCST spacecraft and payload software and hardware development efforts require a highly reliable and high capacity server and with an integrated network of workstations. This environment must conform to Navy, NRL and NCST computational security constraints while supporting both a stable production environment and dynamic R&D environment. The contractor shall specify the hardware and network requirements for the NCST spacecraft and payload development support environment. The contractor shall design, implement, test and maintain the server and workstation system services and administration.

2.3.1.1 The contractor shall provide Database Design and Administration for all related components used in the performance of the preceding requirements. The NCST spacecraft and payload software development efforts utilize a SQL based schema for the definition of the internal software communication protocol and messages, and the space/ground protocol and messages.

The SQL database is used to capture the protocols, packet formats, fields and field constraint definitions of the embedded flight software internal and external interfaces. This information is used to automatically generate source code for flight software data structures, ground software data structures, ground software data handling procedures, ground software interface specification and interface control documents. The contractor shall provide the software engineering expertise, database design expertise and database administration expertise to continue the growth and adaptation of the existing Spacecraft interface database to existing and new space missions.

2.3.1.2 The contractor shall provide Configuration Management and Defect Tracking for all software, procedures, documentation, plans, and other components used in the performance of the preceding requirements. The NCST spacecraft and payload software development efforts rely heavily on a disciplined configuration management and defect tracking approach. The configuration management and problem reporting approach supports multiple programs utilizing an extensive common code base and mission unique processing. The contractor shall maintain and improve the existing approach and implementation of the NCST configuration management and defect tracking systems.

The contractor shall provide the following components as they apply to the NCST, the subcontractors, and the other government customers:

1) Operating Systems – in depth experience with the application and system internals of :

Unix, Linux, Wintel, VxWorks

2) Programming Languages – proven development and operational experience with: C, C++, Python, Java, assembly languages

3) Embedded Processor Architectures – expert software development, device control, and system operations of: PowerPC, R3000, 8051, I960, MIPS 3081

4) COTS Tools – expertise with operational and administrative uses of: MS Access, Jira, Jama, GitLab, SQL, Mongo

5) Networking – complete understanding and proven operational systems built using:

MultiSite/MultiVendor routing and service distribution

2.3.2 Utilization of Third-party and Open Source Software

The contractor shall develop a process for evaluating the risk and licensing restrictions associated with the use of third-party software, including open source, for all embedded software development. The process shall include an evaluation with respect to host, development, test and target hardware platforms. Additionally, the process shall define methods to qualify the third-party source code, define the configuration and version management of third-party source in the software development plan, and define a plan to handle the third-party software dependency life cycle.

2.3.4 FPGA Software

The contractor may provide expertise with FPGA design and development processes. The contractor may have experience with integration of systems that include FPGAs and designing the FPGA software alongside other system software. The contractor may design and develop FPGA interfaces for other software and document these interfaces.

2.4 Program Support

2.4.1 Software Project Management

The contractor shall provide software project management, including: technical oversight;

development of schedules; development of budgets; resource planning; and development of software project planning documents and deliverables. The contractor shall provide flight software and embedded project management throughout the entire lifecycle of software projects, including the proposal phase; planning; design; development; integration; test; delivery; and post-delivery support activities, such as training, field-testing and mission support).

2.4.2 Technical Writing

The contractor shall provide technical writing support, including: explaining scientific and technical ideas in simple language; working with engineers to establish technical specifications;

prepare technical documentation; and follow document development life cycle.

2.4.3 Software Quality Assurance

The contractor shall provide Software Quality Assurance (SQA) support, including: monitoring the software development process, management of software requirement and tracking changes to requirements. The contractor shall define and develop the SQA process to conduct audits of the code, build, and documentation to assure adherence to the project standards. The contractor shall work with project mission assurance to provide oversight and verification of adherence to the SQA plan.

3 Special Requirements This section describes the special requirements for this effort. The following sub-sections provide details of various considerations on this effort.

3.1 Security

Contractor personnel performing any function designated as a component of the Cyber Security Work Force (CSWF), and/or having privileged user access to NRL information systems will require background investigations as specified in SECNAV M-5510.30. System Administrators with privileged access may work in the computing, network and/or enclave environments.

System Administrators with privileged access shall meet the training and certification requirements for IAT level I at the computing environment (CE), IAT level II at the network environment (NE), and IAT level III for the enclave environment as specified in SECNAV M-

5239.2. A submitted DoD Tier 5 Investigation is required for all System Administrators with privileged access serving in these positions. A completed NACLC investigation and a submitted

Tier 5 Investigation are required for all contractor personnel performing CSWF duties. Personnel performing CSWF, IA, or IT duties must be identified as such on all badge and visit request submissions.

Contractors issued a DoD interim secret security clearance may ONLY work on unclassified tasks in accordance with this contract SOW. No classified access will be authorized. Unclassified CSWF, IA, IT or any positon that requires privilege access are NOT authorized with a DoD issued interim secret clearance.

The contractor require access to TS/SCI systems in order to design, develop, and implement Software Defined System for TS/SCI and communications applications. This will require access to NATO information and COMSEC controls to participate in field demonstration, installations, and algorithm development as required.

All contractors (including subcontractors) identified in the Statement of Work shall supplement their current security practices by requiring any personnel involved in executing the contract to complete Operations Security (OPSEC) training via DCSA through their CDSE site:

https://securityawareness.usalearning.gov/opsec/index.htm; and follow any OPSEC guidance that may pertain to the project.

Contractor personnel assigned to this contract who require Top Secret/SCI access must have a favorably adjudicated DoD Tier 5 investigation; a final Top Secret security clearance, with eligibility of SCI prior to submission. Contractor personnel assigned to this contract who require Top Secret access must have a favorably adjudicated DoD Tier 5 investigation; a final Top Secret security clearance prior to submission. Contractor personnel, who require access to Secret information, must have a favorably completed Tier 3 investigation and a final Secret clearance prior to submission.

Contract Facility Security Officers (FSOs), and/or NRL CORs, are required to report immediately to Code 1230 any derogatory information regarding a contractor holding an interim Secret clearance, either on- or off-site. FSOs and NRL CORs shall also notify Code 1230 when a contractor’s interim or final clearance has been declined or revoked.

For Contractors working on unclassified task orders and performing at the locations listed in block 8, a favorably completed suitability determination and a submitted T3 investigation is required prior to the start of work. Individual installation access restrictions may apply.

4 Acronyms BPTF: Blossom Point Tracking Facility

CLIN: Contract Line Item Number

CMP: Contractors Management Plan

CSWF: Cybersecurity Workforce

COR: Contracting Officer Representative

COTS: Commercial Off The Shelf

CT&DH: Command, Telemetry & Data Handling

DRA: Data Reduction and Analysis

EEPROM: Electrically Erasable Programmable Read Only Memory

FEP: Front End Processor

FPGA: Field-Programmable Gate Array

GSE: Ground Support Equipment

GSEC: Ground System Equipment Control

HDL: Hardware Description Language

HWIL: Hardware in the loop

I&T: Integration and Test

ICD: Intelligence Community Directive

KO: Contracting Officer

MUS: Mission Unique Software

NACLC: National Agency Check with Local Agency Check and Credit Check

NCST: Naval Center for Space Technology

NRL: Naval Research Laboratory

PI: Principal Investigator

OCI: Organizational Conflict of Interest

PM: Program Manager

PROM: Programmable Read Only Memory

RCGS: Responsive Command Generation System

R&D: Research and Development

REM: Resource Equipment Management

ROSC: Requirements for On-site Contractors

RTS: Remote Tracking Station

SATCOM: Satellite Communications

TGD: Task Group Definition

UST_EXT: Upper Stage Extension task generation

UUT: Unit Under Test

IA: Information Assurance

VM: Virtual machine

SCI: Special Compartmentalized Information

4 Acronyms