Sources Sought SOW_Draft.pdf

STATEMENT OF WORK

SECTION C – DESCRIPTION/SPECIFICATION/WORK STATEMENT

C.1 BACKGROUND

This Statement of Work (SOW) defines the requirements to supply novel and enhanced Iridium

Command, Control and Communications (C3) Services in support of research, development, test, and experimentation efforts that may be implemented for use in tactical, operational and strategic-level activities. This effort will include enhancements to the existing Asymmetric

Command and Control for Expeditionary Systems and Services (ACCESS) service, as well as new architectures, hybrid architectures, and new services. This effort will also include hardware and software integration with 9523, 9602, and 9603 modems as well as future Software Defined

Radios for services utilizing ACCESS, Iridium Short Burst Data (SBD), and Global Data

Broadcast (GDB), Certus, and other Iridium services.

C.2 SCOPE

The scope outlined in this contract includes tasking to: a) maintain the operations of the

Geographic Broadcast Controller (GBC) and Location Server (LS) located at the Iridium Test

Support Center (TSC), and virtual private network (VPN) to Dahlgren’s Operational Controller

(OC); b) maintain service availability of ACCESS, SBD, Certus, and other Iridium services utilized by the government team issuing this contract; c) develop and refine the Global Data

Broadcast (GDB) Service; d) assist in the future development of new handheld end user devices that operate the ACCESS system and replace the current ROC, and; e) assist in the development and integration of devices utilizing SBD and GDB enabled modems as well as software defined radios. As part of this effort, the Contractor shall evaluate the potential netted and/or broadcast communications architectures and shall recommend a course of action, which may include more than one architectural implementation, or the hybrid implementation(s) of multiple architectures.

Among the improvements and enhancements that will be implemented under the ACCESS and

SBD architectures are the Key Performance Parameters (KPPs): a) global range; b) increased capacity; c) improved service resilience to interference and jamming; d) and awareness and mitigation of network contention or congestion. To design, build, and effectively test and evaluate the efficacy of these system enhancements, ongoing support for component-level and total system testing is required. Additionally, this contract also supports the identification, development, enhancement and implementation of other Iridium-based services, products, and architectures.

C.3 REQUIREMENTS

C.3.1 ACCESS - The Contractor shall provide support to complete tasks needed to meet the requirements leading towards a field usable or operational ready capability. These tasks shall include the following:

C.3.1.1 The Contractor shall continue the design and development of an operationally suitable

User Equipment (UE). Efforts include:

Improving the graphical user interface (GUI) for usability

Achieving ruggedization standards (e.g., applicable elements of MIL-STD 810 G)

Reducing the number of external antennas, increasing maintainability, and increasing the number of receivers from 2 to 3 (as per the recommendation from the relevant analysis of alternatives)

Range Extension Solution (Global Range allowing nets to be established worldwide)

Broadcast Voice

Broadcast Data

Broadcast Position Location Information (PLI)

Broadcast Commands (Ability to send command messages to listeners and receive automatic responses back to the talker)

Decentralized Net Management (Ability to manage [add/delete, enable/disable] nets, handsets and PLI from a location not at the gateway)

User Equipment Reference Design (Includes the design and testing of a transceiver

(TRX) and the design and development of an application board)

ACCESS Handset/Radio (Development, test and transition to manufacturing a ACCESS tactical radio/terminal for ACCESS service)

Real Time User Prioritization With the Space Vehicle (SV) (Ability to center on a user’s acquisition class for implementing a priority and preemption mechanism)

ACCESS Chat (Ability to deliver a real-time chat application among multiple users with improved reliability and user experience)

Managed Net (Ability to use coordinated access techniques to control transmit access to the satellite system)

C.3.1.2 The Contractor shall provide support to develop, integrate, test, and migrate ACCESS hardware (e.g., Geographic Broadcast Controller (GBC), Location Server (LS), and Operational

Controller (OC)) and associated software from the initial development stage to a high availability

(e.g., 99.999%) state in support of Experimentation and Demonstration enablement, field testing and evaluation, operational readiness reviews, and limited operational use cases.

C.3.1.3 The Contractor shall provide hardware integration support in the Government effort to build hardware interfacing with Iridium modems that provide ACCESS service to the end user.

C.3.1.4 The Contractor shall provide software integration support in the Government effort to build end user devices interfacing with Iridium modems that provide ACCESS service to the end user.

C.3.1.5 The Contractor shall provide support in regards to self-certifying and field testing

Government built hardware integrated with Iridium modems.

C.3.1.6 The Contractor shall provide support to review and update the existing System

Functional Specification with new functional revisions.

C.3.1.7 The Contractor shall provide support to review the current Interface Control Documents

(ICDs), complete the implementation of each existing element, specify elements marked with placeholders (e.g., “TBD”), add and implement any additional Government requested elements missing from the ICDs, and generate/implement new ICDs needed for existing and/or future

Government defined subsystems.

Existing ICD elements supporting the following are prioritized for implementation:

Long Application Messaging Service (AMS)

Over-the-Air (OTA) re-keying

Hot Nets, Warm Nets, and Cold Nets (to include Ad Hoc Nets and configurable Net

Persistence)

Managed Nets (to include Net Beacon, latency mitigations for multi-beam and multi-SV nets)

Paging

GBC Indications, including the following specific ICD elements:

o SV connection change indication o Feeder link usage indication o Access congestion indication (DBCCH) o Replication conflict indication o Theater Net broadcast area change indication o Theater Net invalid UE indication UE access request indication o UE network attach expired indication o GBC to LS messaging (including Coverage Request, Coverage Response, SVLLA request, and SVLLA response)

UE TRX and APP board control through the UE Peripheral interface

Major missing elements (to be supported through an existing or to-be-developed ICD) include but are not limited to:

OC ability to query Location Server (LS) solutions (past, present, and future—up to 48 hours in advance)

OC ability to query LS metadata (e.g., date/time of last ephemeris update; date/time of last restart; system loading—% RAM in use, % CPU in use; SV/Beam laydown table(s);

SV/Beam exclusion list; etc.)

Packet collision control and mitigation techniques and solutions (e.g., GBC multiple frame buffer)

Managed Net enablement/support through access to the transport and physical layer messaging protocol of the UE TRX through the UE Application Board and the UE

Peripheral Device interface including the following messages:

o Undirected Broadcast Max Uplink Power System Parameter Word o Directed Broadcast PuCH Location Burst o Uplink and Downlink Link Control Word data

Payload Type

Control Data

Congestion Indicator o Phase 2 type and Direct Access Tactical Net Request and Link Maintainer

Channel Assignment o Registration Attach Request o Net Access Request o System Information Frames of the DTCS Broadcast Control Channel (DBCCH) o Net Information Frames of the DBCCH o Handoff Candidate List Indication

Ability to control UE handset and receive status information through UE Peripheral interface (as an alternative to the UE GUI) including:

o Change primary and secondary nets o Receive listening status unsolicited o Receive transmitting status unsolicited o Receive signal strength unsolicited every 5 seconds o Receive DBCCH Status Indications (e.g., correlating to GUI Display “X”, “D”, “3” indications.

o Force registration o Accept external Global Position System (GPS) data o Receive radio firmware version o Use net flag (PTT) for data operations o Boot while Springboard application is sending messages

Receipt of telemetry data at the OC including real-time noise measurements on a per

Iridium sub-band, SV, panel, and beam basis

C.3.1.8 The Contractor shall support the migration or duplication of the ACCESS subsystems

(hardware/software) from the Iridium Technical Support Center (TSC) Test Facility to more operationally-focused Iridium or Government facilities to include the Enhanced Mobile Satellite

Services (EMSS) Gateway in Hawaii.

C.3.1.9 The Contractor shall provide support to develop, test, integrate, and employ tools and applications for ACCESS Command and Control Monitoring (e.g., health, status, congestion, quality of service), System Management, Billing, Test & Performance Analysis, and

Troubleshooting.

C.3.1.10 The Contractor shall develop, implement, and test hardware and software systems to monitor ACCESS Gateway performance ensuring service reliability requirements are met.

C.3.1.11 The Contractor shall conduct modeling and simulation (M&S) as necessary to validate the ACCESS system architecture and associated performance metrics. The Contractor shall modify or update their existing modeling and simulation tools as necessary to be able to simulate

ACCESS service performance and impact on the system.

C.3.2 Short Burst Data (SBD) Service – SBD is a network transport capability for transmitting and receiving short data messages between equipment and centralized host computer systems.

The short data bursts are typically less than 2 kilobytes per transmission. The contractor shall provide support for the systems engineering process and design of the SBD Service. This support shall include, but not be limited to, the following:

C.3.2.1 The Contractor shall provide support for the development of enhanced SBD. Enhanced

SBD will allow for the encryption of the message header for all SBD messages.

C.3.2.2 The Contractor shall provide support for the development of the SBD Service

Architecture. Elements of the architecture include, but are not limited to Space Vehicles (SVs), Ground Nodes (Iridium Gateway elements and other control elements), and User Equipment.

C.3.2.3 The Contractor shall provide support for the development of a Technical

Implementation Plan. The plan shall, at a minimum, outline the approach to implementing the

SBD System Architecture and maintaining high quality of service (QoS) service in balance with other existing Iridium services

C.3.3 Global Data Broadcast (GDB) Service – GDB is a one-to-many global data broadcast service enabling enterprises to send data to an unlimited number of devices anywhere on Earth whether inside buildings, in-vehicles or aboard aircraft. GDB provides a practical, cost-effective option for transmitting data to a large number of remote devices across a country or continent.

The Contractor shall provide support for the systems engineering process and design of the GDB

Service. This support shall include, but not be limited to, the following:

C.3.3.1 The Contractor shall provide support to conduct analyses of alternatives (i.e., trade studies) needed for planning, designing, developing, and integrating GDB from the legacy satellite constellation and Iridium NEXT (CDRL A004).

C.3.3.2 The Contractor shall provide support for the development of the GDB Service

Architecture. Elements of the architecture include, but are not limited to Space Vehicles (SVs), Ground Nodes (Iridium Gateway elements and other control elements), and User Equipment.

C.3.3.3 The Contractor shall provide support for the development of a Technical

Implementation Plan. The plan shall, at a minimum, outline the approach to implementing the

GDB System Architecture and maintaining high quality of service (QoS) service in balance with other existing Iridium services (CDRL A004).

C.3.4 Iridium-based Services, Products, and Architectures – The Contractor shall support the identification, development, enhancement, and implementation of other Iridium-based services, products, and architectures that may be based upon existing Iridium services, or may

“spin-off” of efforts under development.

C.3.4.1 The Contractor shall provide support to conduct research and analyses for the planning, design, development, and integration of architectures, systems, products, and services with the objective of improving DoD command, control and communications (C3) capabilities in challenging environments and for diverse missions. This effort includes enhancing the existing

ACCESS, SBD, Certus, and GDB systems and services.

C.3.4.2 The Contractor shall provide support with the development of new services, products, and architectures to include hybrid combinations of ACCESS, SBD, Certus, and GDB.

Additionally, completely new services may include: position, navigation and timing (PNT) initiatives; “Iridium-as-sensor” initiatives, and other initiatives not yet formally identified. Such initiatives will augment and support C3 capabilities.

C.3.4.3 The Contractor shall support development, testing, training, experimentation, demonstrations, and other R&D activities and events by making available access to an operational Iridium constellation. This access to the constellation shall be at no fee for purposes of the aforementioned activities.

C.3.4.4 The Contractor shall provide support to plan and execute tests, exercises, and demonstrations of products, services, and architectures developed under the scope of this contract. These activities may be conducted CONUS or OCONUS.

C.3.5 Iridium NEXT - The Contractor shall provide NSWCDD a technical understanding of the Iridium NEXT Satellite Network and Architecture via, but not limited to, access to existing documentation, new documentation, briefs, technical interchange meetings, subject matter experts, and scheduled Iridium events. This understanding shall describe the capabilities, requirements, specifications, services planned, and the implementation schedule of events. This shall include, at a minimum, the Initial Capabilities Document, Functional Capabilities

Document, System Functional Specification, System Requirements Specification, Monthly

Briefing Packages, responses to Government technical questions, or Industry equivalent documents. Additionally, the contractor shall provide access to and awareness of scheduled

NEXT events (briefings, technical reviews, etc.) and R&D, production, and integration facilities on a, at minimum, “not to interfere” basis to NEXT schedule or personnel except by explicit

Iridium arrangement.

C.3.5.1 The Contractor shall conduct an anti-access/area denial (A2/AD) study to analyze the effects of and mitigation strategies to jamming and other common A2/AD techniques on

ACCESS and SBD services through Iridium NEXT in terms of, but not limited to, capacity, throughput, and robustness (CDRL A004). This analysis shall include system modeling and simulation cases, scenarios, and results. The study shall provide:

A direct comparison to the analysis and results previously completed for the Legacy

Constellation

Additional results for both NEXT and the Legacy constellation accounting for system dynamics (e.g. low earth orbit) and their effects on service in the face of A2/AD techniques.

C.3.6 Anti-Access/Area Denial (A2/AD) – The Contractor shall provide support to develop, implement, test, and demonstrate security and resiliency enhancements needed to mitigate the effects of anti-access/area denial (A2/AD) threats to Iridium (e.g., ACCESS, SBD, and GDB) and US Government systems as they support the enhancement of Low Probability of Detection

(PLD) and Low Probability of Interception (PLI) objectives. This shall include the following:

C.3.6.1 The Contractor shall provide support to develop and execute anti-jamming/anti-interference testing of the Iridium system. Such testing shall evaluate both the A2/AD effects due to jamming/interference as well as the effectiveness of implemented mitigation techniques.

C.3.6.2 The Contractor shall provide support to plan and execute exercises and demonstrations of ACCESS, SBD, and GDB.

C.3.6.3 The Contractor shall provide support to plan and conduct ACCESS, and Iridium Certus

UE installations aboard aircraft, ships, and other platforms in support of exercises, demonstrations, and system deployments. This support may include assisting the Government in obtaining the lease of aircraft, surface vessel, and/or ground vehicles for mission test and evaluation during flight operations using aircraft-supplied pods and GFE test equipment (to be decided by the Government).

C.3.6.4 The Contractor shall provide support to develop and implement near and long-term strategies, techniques, and solutions for detecting, locating, identifying, and mitigating congestion and contention (e.g., A2/AD effects due to interference/jamming) on both the Legacy and NEXT constellations. The Contractor shall identify and prioritize solutions that can be implemented without requiring SV modifications. The Contractor shall place an emphasis on solutions enabling multiple steps of the Electromagnetic Interference (EMI) Resolution Process.

C.3.6.5 The Contractor shall provide support to develop and implement solutions and techniques for detecting, locating, identifying, and mitigating A2/AD interference effects on

USG systems. The Contractor shall place an emphasis on solutions enabling the EMI Resolution

Process.

C.3.6.6 The Contractor shall provide modeling, simulation, and analysis support for paragraphs

C.3.6.1 – C.3.6.5.

C.3.7 Technical Support and Information – The Contractor shall provide technical support and information in the areas of:

System Engineering Trade Studies for new products, services, and architectures (CDRL

A004)

Modeling and Simulation (M&S) support in the development and evaluation of new and existing architectures

Testing and Analysis support for new and existing products, services, products, and architectures

Hardware and Software support for products and services that interface with all components of the Iridium system (space vehicles, ground nodes, platforms and user equipment).

C.3.7.1 The Contractor shall develop and support Payload Software for the Iridium Space

Vehicles (both legacy and NEXT), as required for an architecture, system, or service implementation.

C.3.7.2 The Contractor shall develop and support Ground Node Hardware and Software as may be required to execute signal processing, control and management by the Iridium network.

C.3.7.3 The Contractor shall develop and support Hardware and Software for User Equipment

(UEs) or Terminals to include hand-held, man-packable, and multi-platform (ground vehicle, aircraft, unmanned aircraft, and ship-based) installations.

C.3.7.4 The Contractor shall provide Technical Information and Support to preserve and migrate R&D products and services into DoD Programs of Record (where applicable or desired).

This may require collaboration with other DoD Departments or Agencies.

C.3.8 Project Management

C.3.8.1 Technical Interchange Meetings (TIM) - The Contractor shall prepare and present a summary of the projects’ technical status and schedule at regularly scheduled TIMs (CDRL

A002). TIMs shall normally occur once per month. The Contractor shall support the collection and distribution of meeting minutes and action items (CDRL A005). TIMs shall take place at

Government designated locations.

C.3.8.2 Project Management Plan (PMP) - The Contractor shall develop and/or maintain a

PMP for architectures, services, and products developed under this contract (CDRL A006).

C.3.8.3 Risk Management Plan (RMP) - The Contractor shall develop and/or maintain RMPs for architectures, services, and products developed under this contract and hold project risk management meetings that will occur regularly at Government request (CDRL A007). The

Contractor shall support the collection and distribution of meeting minutes and action items

(CDRL A005). The risk management meetings shall take place at Government designated locations.

C.3.8.4 Configuration Management Plan (CMP) - The Contractor shall develop and/or maintain a Configuration Management (CM) program that addresses all new and/or modified hardware, firmware, software, and documentation resulting from this effort. The CM program shall provide configuration identification, configuration control, configuration status accounting, of all new and/or modified trainer hardware, firmware, software, and documentation including

Government furnished property for the duration of the contract. The Contractor shall provide to the Government a configuration management plan (CDRL A008).

C.3.8.5 Interface Control Documentation (ICD) - The Contractor shall develop and/or maintain Interface Control Documentation that identifies all new and/or modified hardware, firmware, and software interfaces. The Contractor shall provide to the Government an interface management plan (CDRL A009).

C.3.9 Systems Engineering

C.3.9.1 System Engineering Plan (SEP) - The Contractor shall develop and/or maintain SEPs to include technical approaches, changes and modifications to the Space Vehicle, Ground System

Components, and UE specifications of system requirements (CDRL A010).

C.3.9.2 System Requirements Management and Review - The Contractor shall develop and/or maintain System Requirements Specifications (SRSs) – Physical, Functional, Performance) Baseline for architectures, services, and products developed under this contract

(CDRL A011). The Contractor shall also conduct periodic System Requirements Reviews

(SRRs) to maintain the established requirements baseline and maintain the Requirements

Traceability Matrix. The Contractor shall provide traceability mappings from the system requirements baseline for each of the requirements allocated to the handset, space vehicle, and ground system support components. After the system requirements baseline and system traceability mapping is established, it will be controlled by the contractor with changes managed through and appropriate Configuration Management system. Risks identified as part of the requirements management process shall include the contractor assessment of ranking and mitigation recommendations.

C.3.9.3 System and Service Feature Roadmap - The Contractor shall develop and/or maintain Functional Capability Documents (FCDs) and White Papers describing current and future services, products, and architectures (CDRL A004).

C.3.9.4 System Engineering and Technical Support for Application Integration - The

Contractor shall provide system engineering and technical support to the customer and other subcontractors for the definition, design, and deployment of the applications utilizing services, products, and architectures developed under this contract.

C.3.9.5 Network Feed Capacity Upgrades - The Contractor shall support studies, modeling and simulations to determine the capacity and the definition and deployment of improvements to ensure data download capacity requirements are properly implemented and meet system requirements (CDRL A004).

C.3.10 Software Development

C.3.10.1 Space Vehicle (SV) Software Development - The Contractor shall develop and deploy

SV payload software to support the requirements for products, services, and architectures developed under this contract. Implementation may include fixes, pokes, or other changes or modifications to existing SV payload software. The Contractor shall provide traceability from the SRS baseline for each of the requirements allocated to the SV component (CDRL A011).

C.3.10.2 UE Transceiver (TRX) Software Development - The Contractor shall develop software baselines for UE TRX applications supporting services, products, and architectures developed under this Contract. The software shall be tested on prototype or production hardware platforms and integrated into the system to support a full end-to-end system qualification to be performed. A reference design and software baseline shall be provided to the Government

(CDRL A015, CDRL A016).

C.3.10.3 UE Application (App) Board Software Development - The Contractor shall develop software baselines for UE App Boards. The software shall be tested on prototype or production hardware platforms and integrated into the system to support a full end-to-end system qualification to be performed. A reference design and software baseline shall be provided to the

Government (CDRL A015, CDRL A016).

C.3.10.4 Ground System Equipment Software Development - The Contractor shall develop a software implementation to support the requirements allocated to the ground systems component of services, products, and architectures developed under this contract. The Contractor shall provide traceability from the SRS baseline for each of the requirements allocated to the ground system component. A reference design and software baseline shall be provided to the

Government (CDRL A015, CDRL A016).

C.3.11 Hardware Development

C.3.11.1 Ground System Hardware Development, Staging, and Roll Out - The Contractor shall define, design, assemble, and integrate necessary ground system elements to satisfy service and architecture requirements. This includes performing operational qualification and validation of ground-based equipment.

C.3.11.2 UE Industrial Design and Transition to MFG - The Contractor shall design, qualify, and transition UE terminals to manufacturing.

C.3.12 System and Product Testing

C.3.12.1 System Test Strategy & System Test Plan - The Contractor shall develop and maintain high-level System Test Strategies to validate that all requirements in the SRD baseline have been met. In addition, the Contractor shall establish and maintain System Test Plans

(CDRL A013).

C.3.12.2 Integration Testing - The Contractor shall perform Integration Testing of services, products, and architectures developed under this contract prior to SV software being uploaded to the constellation, to ensure that it will interoperate with previous and currently developed and functioning services and UE terminals. This testing shall include Regression Testing. The

Contractor shall document the test strategy, test plan, and results of each formal Integration test event (CDRL A013, CDRL A012). The Contractor shall provide test tools for evaluation of

UE, SVs, and any system and subsystem that constitutes components of services, products, and architectures developed under this contract. The Contractor shall provide tools including: those that measure call completion rate; PTT set up time; PTT success rate; PTT duration; time to listen; listen duration; message completion; clarity; net integrity; network load; network latency;

packet loss rate; bit error rate; and any other relevant metrics as identified in any systems engineering document, requirement document, or any other performance referenced throughout the design and implementation. The Contractor shall provide tools to test and verify any algorithm used by services, products, and architectures developed under this contract.

C.3.12.3 System End-to-End Testing - The Contractor shall support and perform end-to-end testing, including all components of services, products, and architectures developed under this contract. A formal test plan shall be developed and results reviewed with the Government

(CDRL A013).

C.3.12.4 SV Soak and Upload Campaign - The Contractor shall perform on over-the-air qualification of the SV payload software and systematically upload all satellites with the qualified software for services, products, and architectures developed under this contract.

C.3.12.5 Information Assurance Certification - The Contractor shall support the process of ensuring the ground system designs are compliant to DoD information assurance requirements.

The Contractor shall implement encryption of channels used for control of Iridium-based services, products, and architectures including net information, UE push-to-talk request, and any other relevant net or radio transaction. The Contractor shall provide engineering services in support to the development of Type-1 Suite-B (Secret and Below) UE terminals.

C.3.12.6 On-Orbit Testing - The Contractor shall perform On-Orbit Testing of services, products, and architectures developed under this contract after the SV payload software is uploaded. The Contractor shall document the test strategy, test plan, and results of each formal

On-Orbit Test event (CDRL A013, CDRL A012).

C.3.12.7 LUE/LTA Testing Support - The Contractor shall support government-led Limited

User Evaluations (LUE) and Limited Technical Assessments (LTA) for services, products, and architectures developed under this contract.

C.3.13 Hardware and Software Certification

C.3.13.1 The Contractor shall perform hardware and software certification with the UE terminals, products, services, products, and architectures developed under this contract. The

Contractor shall document the test strategy and test plan and results of each formal Certification

Test event (CDRL A013, CDRL A012). The Contractor shall perform certification regression tests with any major hardware or software revisions prior to fielding new hardware of software releases. All encryption algorithms will be accredited by the National Institute of Standards and

Technology, the National Security Agency, or any other equivalent agency that can validate the implementation of the encryption algorithm.

C.3.14 Service Delivery Support

C.3.14.1 Service Model Development - The Contractor shall assist the Government in developing an operations model for supporting the entire service deliver supply chain, including service provisioning, capacity management, customer service, and customer billing.

C.3.14.2 End User Support and Troubleshooting - The Contractor shall assist the Government in developing Tool, Techniques, and Procedures (TTPs) for end user support and troubleshooting products, services, products, and architectures developed under this contract.

C.3.14.3 Training - The Contractor shall work with the Government to develop and deliver training materials to support the installation, operation, and maintenance of the UE terminals and ground system components (CDRL A014).

C.3.15 Monthly Status Reporting – The Contractor shall submit a monthly status report

(CDRL A001).

C.5 MANDATORY REQUIREMENTS

The following mandatory requirements shall be maintained throughout the life of this contract.

Requirement 1: Facility Security Clearance

The Contractor’s primary facility for supporting this contract is required to have a facility clearance of TOP SECRET and must be cleared at the SECRET level for storage at the time of contract award.

Requirement 2: Personnel Security Clearances

One prime Contractor individual in the Program Management labor category shall have a TOP

SECRET/SCI security clearance. Other prime Contractor personnel and Subcontractor personnel are not required to have a security clearance.

C.6 OTHER DIRECT COSTS

During the performance of this contract the Contractor will have to travel and procure material and consumables to perform the tasking of the statement of work.

C.6.1 Travel

The Contractor shall be required to travel in performance of this contract. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements and shall be requested of and authorized in advance by the COR in writing or by electronic email. All requests must show the appropriate order number, the number or people traveling, the number of days for the trip, the reason for the travel, an estimated cost (with G&A separate) and any high cost or unusual costs expected. The Contractor is not authorized to perform any travel that is not in conjunction with this effort. All travel shall be conducted in accordance with FAR 31.205-46 Travel Costs.

Representative travel locations include:

Dahlgren, VA

C.6.2 Direct Charge of Materials and Equipment

C.6.2.1 Materials and Equipment Costs

During the performance of this contract, it may be necessary for the Contractor to procure materials or equipment (hereafter referred “materials”) to respond to the mission requirements listed in the Statement of Work (SOW). This contract is issued from a service contract and the procurement of materials of any kind that are not directly related to and necessary for contract performance may be determined to be unallowable costs pursuant to FAR Part 31. The term

“material” includes supplies, parts, equipment, hardware, and Information Technology (IT) resources including hardware, services, and software. Any material provided by the Contractor is subject to the requirements of the FAR, DFARS, and the applicable Department of Navy regulations and instructions. Charges related to material costs may include general and administrative (G&A) expenses, but shall not include fee or profit.

C.6.2.2 Materials List

The materials and equipment contained in the following list are authorized for purchase once the

Contractor has complied with approval requirements as stated in Sections C.6.2.3 and C.6.2.4 below:

Platform Kits and Support Equipment

Software Maintenance Support – Licenses

ABC2 Terminals and Peripherals

OpenPort Terminals and Peripherals

GBC and Location Server Hardware

User Equipment Terminals and Peripherals

Test and Troubleshooting Equipment

Materials not fitting the description listed in this Section may not be purchased and reimbursed as an Other Direct cost to this contract unless mutually agreed to by both the Government and the Contractor and subsequently added to the contract by Contract Modification.

C.6.2.3 Requiring Approvals for ODCs

All purchases of materials, exceeding $3,500 per individual purchase, and all Personal Protective

Equipment (PPE), require COR approval prior to purchase. As well as approval by the COR, prior written approval from the Procuring Contracting Officer (PCO) shall be required for all purchases of materials under the following circumstances:

a) If the Contractor possesses an approved purchasing system, the following applies:

1) A purchase of materials in accordance with what is stated in Section C.5.2.2 above, that is greater than $3,500 and less than or equal to $10,000 per individual purchase may be executed with COR review and written approval. PCO approval is not required.

2) A purchase of materials in accordance with what is stated in Section C.5.2.2 above that exceeds $10,000 per individual purchase may NOT be executed unless the COR reviews the proposed purchase and the Contract Specialist issues an electronic written PCO approval.

b) If the Contractor does not possess an approved purchasing system, the following applies:

1) A purchase of materials in accordance with what is stated in Section C.5.2.2 above that equals

$3,500 or less per individual purchase may be executed with COR review and written approval.

PCO approval is not required.

2) A purchase of materials in accordance with what is stated in Section C.5.2.2 above that exceeds $3,500 per individual purchase may NOT be executed unless the COR reviews the proposed purchase and the Contract Specialist issues an electronic written PCO approval.

c) Separate multiple purchases of amounts valued below those thresholds stated in this section shall not be submitted to circumvent the COR and PCO review and approval procedure. Splitting purchase requirements to defeat purchasing thresholds shall not be approved.

C.5.2.4 Procedure for Obtaining COR/PCO Approval

To obtain COR and/or PCO approval, the Contractor shall:

a. Submit a written request for purchase of materials to the COR (email is acceptable). The COR shall review the request. If it is in accordance with the list above and requires PCO approval, the

COR shall submit the request via the Contract Specialist to the PCO for review and approval.

b. Minimum requirements for a written request for purchase are as follows:

1. Complete description of the material to be purchased

2. Quantity

3. Unit and Total Cost

4. Delivery/ Freight Charges

5. Any associated service charges such as assembly, configuration, packing, etc.

6. An explanation for the need for the material

7. List the competitive quotes received from potential suppliers

8. The basis for the selection of the selected supplier

9. Price reasonableness determination

10. If the procurement is sole sourced to a particular supplier or manufacturer, include the rationale for limiting the procurement to that supplier/manufacturer.

c. Once the COR and/or PCO have reviewed the request, the Government shall notify the

Contractor of the outcome. Issues or details may be discussed with the Contract Specialist acting on behalf of the PCO until a final Government determination is made as to whether to approve, modify, or reject the purchase.

C.6.2.5 Disposition of Material

Upon completion of the period of performance, all materials associated with this contract that were purchased by the Contractor and not depleted during the performance of the contract shall become the property of the Government. The Contractor shall transfer all materials not depleted to the COR. The Contractor’s Monthly Progress Report shall include a complete list of all material purchased to date under the contract.

The Contractor shall deliver all material (end items) to the Government through Building 125, Central Receiving with a DD1149. The DD1149 shall include the following:

1) Dollar Value

2) Purchase Request Number

3) Item Description

4) Serial Number

5) Model Number

6) Quantity

7) Contract Number

8) Technical Point of Contact

9) Assigned Unique Serialized Identification Number

In addition, each deliverable shall have an IUID tag and the corresponding information uploaded into iRAPT (Invoicing, Receipt, Acceptance and Property Transfer).

C.6.2.6 Information Technology (IT) Resources

IT Resources shall not be purchased unless DOD and Navy purchasing procedures have been satisfied and approvals obtained. IT resources include personal computers (PC’s), laptops, printers, software, servers, hubs, routers, phones, fax machines, and any related maintenance, telecommunications, training, or other support services. All IT Resource Other Direct Cost

Purchases require COR and PCO approval regardless of the dollar value associated with the purchase.

C.7 Government Furnished Property

C.7.1 GFP may be issued under this contract.

C.7.2 The Contractor shall maintain and report the inventory of GFP (CDRL A00X) issued under this contract.

C.7.3 The GFP Inventory Log shall identify: Other Plant Equipment (OPE)/Special Test

Equipment (STE), TAG Number (Plant Account Number), Contractor sighting, date sighted, sighted location, disposition, serial number.

C.7.4 The specific format shall be pre-approved by the COR and Contracting Officer prior to the first submission.

C.8 SECURITY

C.8.1 One individual in the Program Management labor category shall have a TOP

SECRET/SCI Security clearance. Other Prime contractor and Subcontractor personnel are not required to have a security clearance. All deliverables associated with this contract are unclassified unless otherwise specified. Access to classified spaces and material and generation of classified material shall be in accordance with the attached DD Form 254. The Department of

Defense Contract Security Classification Specification (DD Form 254) provides the security classification requirements for this contract. The Contractor shall obtain facility and personnel security clearances as required by the Department of Industrial Security Program prior to starting to work on tasks requiring clearances. Access to classified spaces and material and generation of classified material shall be in accordance with the NISPOM and the NSWCDD Command

Security Manual. Some work accomplished under this contract will be classified up to the level of TOP SECRET. The Contractor shall maintain the capability to store information up to and including SECRET. All data generated under this contract shall be classified in accordance with the guidance in the NISPOM and the NSWCDD Command Security Manual. The Contractor must comply with guidelines specified on the DD254. All deliverables associated with this contract will be non-SCI.

C.8.2 Access to Non-SCI intelligence is needed in order to utilize intelligence documents.

There is a requirement for one of the Program Managers to have a TS/SCI clearance on this contract. They must be cleared at the SI/TK/G/HCS level in order to have access to SCIF environments. The individual with SCI clearance will be required to attend intelligence meetings where SIGINT intelligence information will be discussed. Controlled Unclassified Information

(CUI) (formerly For Official Use Only (FOUO) and Personally Identifiable Information (PII)) generated and/or provided under this contract shall be safeguarded and marked as specified in

DODI 5200.48, Controlled Unclassified Information (CUI), March 6, 2020. The contractor will be required to receive classified information at the Secret level at the contractor’s facility.

C.8.3 Facility Clearance: The Contractor shall possess and maintain a TOP SECRET facility clearance as verified within the Industrial Security Facility Database.

C.8.4 Physical Security: The Contractor shall be responsible for safeguarding all Government information or property provided for Contractor use. At the end of each work period, Government information, facilities, equipment and materials shall be secured as specified by the

NISPOM and the NSWCDD Command Security Manual. Secret storage is required at the

Contractor’s facility in order to meet requirements of receiving classified material in accordance with this contract.

C.8.5 Electronic Spillages (ES) are unacceptable and pose a risk to national security. An electronic spillage is defined as classified data placed on an information system (IS), media or hardcopy document possessing insufficient security controls to protect the data at the required classification level, thus posing a risk to national security (e.g., sensitive compartmented information (SCI) onto collateral, Secret onto Unclassified, etc). The Contractor’s performance as it relates to ES will be evaluated by the Government. ES reflects on the overall security posture of NSWCDD and a lack of attention to detail with regard to the handling of classified information of IS security discipline and will be reflected in the Contractor's performance rating.

In the event that a Contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the Government for ES remediation will be charged to the Contractor.

C.8.6 NSWCDD Security will continue to be responsible for the corrective action plan in accordance with the security guidance reflected on the DOD Contract Security Classification

Specification - DD254. NSWCDD Security will identify the Contractor facility and contract number associated with all electronic spillages during the investigation that involve Contractor support. NSWCDD Security will notify the Contracts Division with the Contractor facility name and contract number, incident specifics and associated costs for clean up. The Contracting

Officer will be responsible to work with the Contractor Facility to capture the costs incurred during the spillage clean up. The Contractor is also responsible for taking Information Security

Awareness training annually, via their Facility Security Officer (FSO), as part of the mandatory training requirements. If a spillage occurs additional training will be required to prevent recurrence.

C.8.7 Portable Electronic Devices (PEDs)

C.8.7.1 Non-government and/or personally owned portable electronic devices (PEDs) are prohibited in all NSWCDD buildings with the exception of personally owned cell phones which are authorized for use in spaces up to and including Controlled Access Areas. The Contractor shall ensure the onsite personnel remain compliant with this PED policy. NSWCDD instruction defines PEDs as the following: any electronic device designed to be easily transported, with the capability to store, record, receive or transmit text, images, video, or audio data in any format via any transmission medium. PED’s include, but are not limited to, pagers, laptops, radios, compact discs and cassette players/recorders. In addition, this includes removable storage media such as flash memory, memory sticks, multimedia cards and secure digital cards, micro-drive modules, ZIP drives, ZIP disks, CD-RWs, DVD-RWs, MP3 players, iPADs, digital picture frames, electronic book readers, kindle, nook, cameras, external hard dish drives, and floppy diskettes.

C.8.7.2 Personal Wearable Fitness Devices (PWFDs) marketed primarily as fitness or sleep devices are allowed in all Navy spaces where collateral non-Sensitive Compartmented

Information (SCI), classified information is processed, stored, or discussed up to and including secret. User must ensure PWFD is compliant with all requirements in NAVADMIN 216/15, Cyber Hygiene Authorization to use Personal Wearable Fitness Devices (e.g., FitBit, Jawbone

UP, etc.) in Navy Spaces, dated 14 September 2015 and register PWFD in the NSWCDD Fitness

Device Tracker.

C.8.7.3 PED’s belonging to an external organization shall not be connected to NSWCDD networks or infrastructure without prior approval from the NSWCDD Information Assurance and Compliance Branch. This approval will be granted using the TARIS form and action tracker process.

C.8.7.4 Personally owned hardware or software shall not be connected or introduced to any

NSWCDD hardware, network or information system infrastructure.

C.8.8 Operations Security (OPSEC)

C.8.8.1 All Contractors (including Subcontractors) shall supplement their current security practices by requiring any personnel involved in executing this contract to complete

Government-sponsored and administered Operations Security (OPSEC) training. In addition, all

Contractors should be aware of the Critical Information List (CIL) for the department they are supporting as well as the OPSEC plan for NSWCDD. Upon contract award, all identified

Contractors (including Subcontractors) shall sign a Contractor's conformance statement and submit it to the NSWCDD COR named in block 13 of the attached DD-254 thereby acknowledging that they will meet the requirements of this contract. The COR shall contact their

Department Training Coordinator to schedule key employees to attend the Government-sponsored OPSEC training. The Contractor must immediately notify the Government upon the discovery of any nonconformance with the OPSEC Plan.

C.8.9 Privacy Program Training

C.8.9.1 Privacy Program Training. Privacy training is mandatory for all NSWCDD personnel

(military, civilian, and contractor) and must be completed annually. The Total Workforce

Management System (TWMS) is the official database for workforce training and is the preferred tool for taking and recording privacy act training. All NSWCDD personnel are responsible for ensuring individual annual privacy training requirements are met.

C.8.10 Visits by Foreign Nationals and Foreign Representatives

C.8.10.1 Contract performance may require that the Contractor host, at an off-base location, foreign nationals and/or foreign representatives. A foreign national is a person who is a citizen of a foreign nation, and who is not a citizen of the United States. A foreign representative is a person who represents a foreign interest in dealings with the U.S. Government, either directly or through dealings with a U.S. Government Contractor. A foreign representative may be a United

States citizen.

C.8.10.1.1 A Contractor-hosted visit of a foreign national or foreign representative may be either an “official” visit or an “unofficial” visit. An official visit is a visit where the foreign national or foreign representative is representing a foreign government in an official capacity. An unofficial visit is a visit where the foreign national or foreign representative is not representing a foreign government.

C.8.10.1.2 A visit by a foreign national or a foreign representative may be either “DoD

Sponsored” or “Non-DoD Sponsored”. A DoD Sponsored visit is a visit that is coordinated by a

DoD entity. A Non-DoD Sponsored visit is a visit that does not involve DoD coordination (A visit by either a foreign national or a foreign representative pursuant to performance by the

Contractor under this contract is not considered to be, by itself, a sponsored visit).

C.8.10.2 The Contractor hosting a visit by either a foreign national or a foreign representative is responsible for adherence to Department of Defense and Department of the Navy directives, instructions, regulations, and manuals that govern foreign disclosure. “Foreign Disclosure” is defined as the disclosure of Classified Military Information (CMI) and Controlled Unclassified

Information (CUI) to foreign nationals and/or foreign representatives. Disclosure of such information may be accomplished orally, visually, in writing, or by any other medium.

C.8.10.2.1 Classified Military Information (CMI). This is information that is originated by or for the Department of Defense, or a Military Department, or an entity under its jurisdiction and control, and which requires protection in the interest of national security. Such information is designated as TOP SECRET, SECRET, or CONFIDENTIAL.

C.8.10.2.2 Controlled Unclassified Information (CUI). This is information that requires safeguarding or dissemination controls pursuant to and consistent with applicable law, regulations, and government-wide policies but is not classified under Executive Order 13526 or the Atomic Energy Act as amended.

C.8.10.3 Naval Surface Warfare Center Dahlgren Division (NSWCDD) Foreign National

Visitor and Foreign Disclosure Application process.