N0017821R4400 Amendment 10 Conformed Copy.pdf

CODE

(Hour)

PAGE(S)

until 04:00 PM local time 28 Feb 2022

X

A

X B

X C X D

EX

X

G

F 63 - 73

74 - 95

X H 96

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA

FAR (48 CFR) 53.214(c)

DO-A7 1 96

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N00178 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

Electionic Submission Only conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 2

3 - 13

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

14 - 37

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

39 - 40

41 - 42 X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 43 - 52 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 53 - 56 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

57 - 61

PART II - CO NTRACT CLAUSES

NSWCDD 1

ATTN: CARMELL BEARD/024 CARMELL.BEARD@NAVY.MI

HLGREN RD..

DAHLGREN VA 22448 540-653-4706

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

20 Apr 2021

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N0017821R4400

Section A - Solicitation/Contract Form

GENERAL INFORMATION

DESCRIPTION: The Naval Surface Warfare Center Dahlgren Division (NSWCDD), Weapons Control and Integration Department, Asymmetric Systems Division (H10) is the source of this requirement. This acquisition will provide the following services: 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 Radio Only Charlie (ROC), and; e) assist in the development and integration of devices utilizing SBD and GDB enabled modems as well as software defined radios.

PROPOSAL DUE DATE: Proposals are required to be submitted to the Contracting Officer and Contracting

Specialist on or before the date and time specified in Block 9 of Page 1.

CRITICAL DATES: This Solicitation represents the Government's requirements and shall be the governing document. All questions regarding this requirement shall be submitted to the Contract Specialist and Contracting

Officer. The deadline for receipt of questions is 18 February 2022. The anticipated award date is 16 March 2023 Contract performance is currently schedule to begin on 30 March 2023. The proposal validity period shall be through 30 June 2023.

ADVANCE NOTICE/PRE-SOLICITATION CONFERENCE: An Advance Notice/Sources Sought notice, including a draft Statement of Work (SOW), labor qualifications, and Full Time Employees (FTEs), was posted in the Beta SAM on 01 October 2020.

COMPETITION APPROACH: This requirement is a sole source Contract.

INCUMBENT CONTRACTOR: This requirement is a direct follow-on to Cost-Plus-Fixed-Fee (CPFF) Contract

No. N0017817C0001 with Iridium Government Services LLC.

GENERAL INFORMATION: A conformed copy of the Solicitation will be issued with any amendments.

THIS SOLICITATION AND PREVIOUS POSTINGS: Offerors should not rely on information contained in previous postings. This Solicitation represents the Government's requirements and shall be the governing document.

ORGANIZATIONAL CONFLICT OF INTEREST QUESTIONS: Questions relating solely to the Offeror's possible Organizational Conflict of Interest shall be addressed directly to the Contract Specialist and the Contracting Officer listed in Section G-242-H001 Government Contract Administration Points-of Contact and Responsibilities.

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Base Period CPFF

CPFF

Base Period Cost Plus Fixed Fee for Command Control and Communication

Support in accordance with Section C, Statement of Work

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0001AA Labor

Hours

Base Period CPFF Holding CLIN

CPFF

Holding CLIN

FOB: Destination

Base Period ODCs

COST

Base Period ODCs in support of CLIN 0001 for Command Control and

Communication Support in accordance with Section C, Statement of Work.

0002AA Lot Base Period ODC Holding CLIN

COST

0003 Lot Base Period Not Separately Priced

Not Separately Priced Contract Data Requirement List Date Deliverables for the

Base Period IAW Exhibit A, CDRLs.

NET AMT

OPTION Option Year 1 CPFF

CPFF

Option Year 1 Cost Plus Fixed Fee for Command Control and Communication

Support in accordance with Section C, Statement of Work.

0004AA Labor

OPTION Option Year 1 CPFF Holding CLIN

OPTION Option Year 1 ODCs

COST

Option Year 1 ODCs in support of CLIN 0004 for Command Control and

0005AA Lot OPTION Option Year 1 ODC Holding CLIN

COST

0006 Lot OPTION Option Year 1 Not Separately Priced

Not Separately Priced Contract Data Requirement List Data Deliverable for the

Option Year 1 IAW Exhibit A, CDRLs.

OPTION Option Year 2 Cost Plus Fixed Fee

CPFF

Option Year 2 Cost Plus Fixed Fee for Command Control and Communication

0007AA Labor

OPTION Option Year 2 CPFF Holding CLINs

OPTION Option Year 2 ODCs

COST

Option Year 2 ODCs in support of CLIN 0007 for Command Control and

0008AA

Option Year 2 ODC Holding CLIN

COST

0009 Lot OPTION Option Year 2 Not Separately Priced

Option Year 2 IAW Exhibit A, CDRLs.

OPTION Option Year 3 Cost Plus Fixed Fee

CPFF

Option Year 3 Cost Plus Fixed Fee for Command Control and Communication

0010AA Labor

OPTION Option Year 3 CPFF Holding CLIN

OPTION Option Year 3 ODCs

COST

Option Year 3 ODCs in support of CLIN 0010 for Command Control and

0011AA Lot OPTION Option Year 3 ODC Holding CLIN

COST

0012 Lot OPTION Option Year 3 Not Separately Priced

Option Year 3 IAW Exhibit A, CDRLs.

OPTION Option Year 4 Cost Plus Fixed Fee

CPFF

Option Year 4 Cost Plus Fixed Fee for Command Control and Communication

0013AA Labor

OPTION Option Year 4 CPFF Holding CLIN

OPTION Option Year 4 ODCs

COST

Option Year 4 ODCs in support of CLIN 0013 for Command Control and

0014AA Lot OPTION Option Year 4 ODC Holding CLIN

COST

0015 Lot OPTION Option Year 4 Not Separately Priced

Not Separately Priced Data Contract Data Requirement List Deliverable for the

Option Year 4 IAW Exhibit A, CDRLs.

SECTION B NOTES

NOTE 1: LABOR HOURS (HR)

Offerors shall price via each CLIN's holding SLIN.

*Labor hours will be updated to reflect the Level of Effort at time of award.

NOTE 2: OPTION CLAUSE

Option to Extend the Term of the Contract Clause in Section I applies to the Option CLINs.

NOTE 3: OTHER DIRECT COSTS (ODCs)

Any Other Direct Cost (ODC) other than the costs identified in Section C.5 will be limited to those approved at time of award. The estimated ODC costs are located in Section L.4.2.3.

NOTE 4: NOT SEPARATELY PRICED (CLINs 0003)

The price for Not Separately Priced (NSP) Data items shall be included in the price of the corresponding Labor

CLIN(s) (CLINs 0003, 0006, 0009, 0012, 0015) in response to clause L-215-H004, INSTRUCTIONS FOR

PRICING OF CONTRACT DATA REQUIREMENTS LIST (NAVSEA) (OCT 2018).

B.1 TYPE OF ORDER

This Contract is a Level of Effort (term) type order.

Items in the 0001, 0004, 0007, 0010, 0013 series are Cost-Plus-Fixed Fee (CPFF)

Items in the 0002, 0005, 0008, 0011, 0014 series are cost only, excluding fee.

Items in the 0003, 0006, 0009, 0012, 0015 series are Not Separately Priced (NSP) type.

B.2 ADDITIONAL CLINS

Additional CLINs may be unilaterally created by the Contracting Officer during the performance of this Contract to accommodate the multiple types of funds that may be used under this Contract. These modifications will not change the overall Level of Effort, estimated cost or incentive fee of the Contract.

CLAUSES INCORPORATED BY FULL TEXT

B-216-H006 FEE TABLE (NAVSEA) (MAR 2019)

Labor CLIN Labor Hours Cost Per

Hour*

Fee Rate Per

Hour*

Loaded

Hourly Rate

*The Offeror shall divide the proposed fee for each CLIN by the quantity of labor hours indicated to complete the table. Fee is calculated based on cost less FCCOM; if FCCOM is proposed, necessary columns may be added.

In the event of any inconsistency between the above table and the CLIN pricing, the CLIN pricing shall take precedence.

(End of text)

B-231-H001 TRAVEL COSTS (NAVSEA) (OCT 2018)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The travel costs to be reimbursed shall be those costs for which the Contractor has maintained appropriate documentation and which have been determined to be allowable, allocable, and reasonable by the

Procuring Contracting Officer, Administrative Contracting Officer, or their duly authorized representative.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35;

however, Procuring Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the

Contractor's or employee's convenience.

B-232-H005 PAYMENTS OF FEE(S) (LEVEL OF EFFORT)--ALTERNATE I (NAVSEA) (OCT 2018)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts.

(b) The Government shall make payments to the Contractor, subject to and per the clause in this contract entitled "Fixed

Fee" (FAR 52.216-8) or "Incentive Fee", (FAR 52.216-10), as applicable. Such payments shall be submitted by and payable to the Contractor pursuant to the clause of this contract entitled "Allowable Cost and Payment" (FAR 52.216-7), subject to the withholding terms and conditions of the "Fixed Fee" or "Incentive Fee" clause, as applicable. Fee paid per hour shall be based on total fee dollars divided by total hours to be provided. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract.

B-232-H006 LIMITATION OF COST OR LIMITATION OF FUNDS CLARIFICATION (NAVSEA) (OCT 2018)

The clause entitled "Limitation of Cost" (FAR 52.232-20) or "Limitation of Funds" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.

Section C - Descriptions and Specifications

STATEMENT OF WORK

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 Radio Only Charlie (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:

I. SV connection change indication

II. Feeder link usage indication

III. Access congestion indication Distributed Tactical Communications System (DTCS) Broadcast

Control Channel (DBCCH)

IV. Replication conflict indication

V. Theater Net broadcast area change indication

VI. Theater Net invalid UE indication UE access request indication

VII. UE network attach expired indication

VIII. GBC to LS messaging (including Coverage Request, Coverage Response, Satellite Vehicle

Latitude Longitude Altitude (SVLLA) request, and SVLLA response)

UE TRX and Application (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:

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

II. 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.)

III. 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:

I. Undirected Broadcast Max Uplink Power System Parameter Word

II. Directed Broadcast PuCH Location Burst

III. Uplink and Downlink Link Control Word data

IV. Payload Type

V. Control Data

VI. Congestion Indicator

VII. Phase 2 type and Direct Access Tactical Net Request and Link Maintainer Channel Assignment VIII. Registration Attach Request

IX. Net Access Request

X. System Information Frames of the DTCS Broadcast Control Channel (DBCCH)

XI. Net Information Frames of the DBCCH

XII. 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:

I. Change primary and secondary nets

II. Receive listening status unsolicited

III. Receive transmitting status unsolicited

IV. Receive signal strength unsolicited every 5 seconds

V. Receive DBCCH Status Indications (e.g., correlating to GUI Display “X”, “D”, “3” indications.

VI. Force registration

VII. Accept external Global Position System (GPS) data

VIII. Receive radio firmware version IX. Use net flag Push-to-talk (PTT) for data operations

X. 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.4.5 The Contractor shall provide a report when the satellite system is compromised to inform the

Government of when the system was compromised, for what period of time, in what areas, and what service(s) was compromised.

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 Government

Furnished Equipment (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 Government 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 A00A).

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 A00B). 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 Sub-contractors 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 A00B).

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 A00F, CDRL A00G).

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 A00F, CDRL A00G).

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 A00F, CDRL A00G).

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 A00D).

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 A00D, CDRL A00C). 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 A00D).

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 A00D, CDRL A00C).

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 A00D, CDRL A00C). 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

A00E).

C.3.15 Monthly Status Reporting – The Contractor shall submit a monthly status report (CDRL A001).

C.4 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 time of proposal submission.

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 Sub-contractor personnel are not required to have a security clearance.

C.5 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 SOW.

C.5.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 Contracting Officers Representative (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 B.231-H001 Travel Costs.

Representative travel locations include:

Dahlgren, VA

C.5.2 Direct Charge of Materials and Equipment

C.5.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.5.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.5.2.3 and C.5.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.5.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.