HC108424R0008_DMCC IDIQ RFP.pdf

SEE ADDENDUM

(No Collect Calls)

HC108424R0008 17-Apr-2024

b. TELEPHONE NUMBER

618-418-6518

8. OFFER DUE DATE/LOCAL TIME

03:00 PM 17 May 2024

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA X ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

HC10849. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

MELISSA A. WEH

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.X

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

DISA/DITCO-SCOTT-PS84

2300 EAST DRIVE

SCOTT AFB IL 62225

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

1,500

NAICS:

517112

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF114

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

HC108424R0008

Section SF 1449 - CONTINUATION SHEET

PWS FOR RFP

STATEMENT OF WORK

Award/Mod Effective Version Date

Award

Contract Number: To be determined (TBD)

Tracking Number: TBD

Contractor Name: TBD

Follow-on to Previous Contract and

Task Order Number:

47QTCA19D00MV/HC108421A0001

1. Contracting Officer’s Representative (COR). To be completed at award

a. Primary COR.

Name:

Organization:

Department of Defense Activity

Address Code (DODAAC):

Address:

Phone Number:

E-Mail Address:

b. Alternate COR.

Organization:

DODAAC

Address:

2. Title. The Department of Defense (DoD) Mobility Classified Capability (DMCC) Indefinite Delivery

Indefinite Quantity (IDIQ) for Mobile Devices, Hotspots, and Data Service Plans – Domestic, Priority, and

International.

3. Background. The Defense Information Systems Agency Mobility Program Management Office (PMO) has a mission to provide DMCC-Secret (DMCC-S) and DMCC-Top Secret (DMCC-TS) enterprise capabilities and services to enable global mobile communications to support operations for joint warfighters, national level leaders, and coalition partners. This capability is critical to the security of classified communication at the highest levels of the DoD and approved non-DoD as well as in strategic field locations.

In 2013, DISA and the National Security Agency (NSA) piloted a mobility program to provide classified mobile communications. The intent of the classified capability was to incorporate commercial solutions to process and protect classified data as well as provide mobile secure communications capabilities. In a joint effort, the agencies tested and approved the Samsung Galaxy S4 Custom Read Only Memory (CROM) handset for DMCC. The CROM replaced the commercial firmware with a government developed firmware to lock down the device to meet the Commercial Solutions for Classified (CSfC) Mobile Access Capability

Package (MACP) requirements for deployment. Since then, DISA upgraded handsets from the S4 CROM, S7

CROM to the S20 CROM; and upgraded tablets from the Tab S3 CROM to the Tab S7 CROM.

With this new acquisition, DISA now requires the latest approved next generation DMCC devices that are listed on the CSFC Components List. However, these devices will be non-CROM mobile devices that do not require the Government developed CROM firmware. The devices will be locked down using current device and Mobile Device Management controls. This will allow DISA to switch to the latest devices on the CSfC

Components List as they become available to support the customer base.

Currently there are approximately 4.9K active DMCC-S/TS End User Devices (EUDs) worldwide for the

DMCC- S/TS non-Windows devices. DISA will leverage commercial off the shelf mobile devices that meet the NSA CSfC MACP where possible. Additionally, the DMCC non-Windows devices will have dual data-at-rest encryption capability per the Data-at-Rest Capability Package (DAR CP) requirements. These non-

Windows devices must also be listed on the National Information Assurance Partnership (NIAP) Product

Compliant List and subsequently listed on the NSA CSfC Components List under the category “EUD/Mobile

Platform.”

DMCC-S Windows Data-at-Rest (WINDAR-S) EUDs started as a pilot in 2019, which then quickly rolled into semi-production in early 2020 in support of the coronavirus disease pandemic 2019. Currently there are approximately 4.1K active WINDAR-S worldwide. WINDAR-S are not NIAP tested and subsequently are not listed on the CSfC Components list due to NIAP certification issues. No WINDAR-S EUDs currently exist on the CSfC Components list but may in the future.

Current secure communications are via Internet ingress using the DoD Information Network Internet Access

Point (IAP) connected to the Non-Classified Internet Protocol Router Network or the Federated Gateway, both of which can connect to the DMCC-S/TS Virtual Private Networks (VPN). Priority Service selection provides priority data service through the cellular carrier network up until the data is dropped onto the Internet. From there the traffic is best effort to the DoD IAP. Priority Services is only available in the Continental United

States (CONUS).

All communication will traverse via a Retransmission Device (RD), i.e., hotspot, through use of a commercial data service plan for both inside and outside the defined domestic coverage areas. The Government defines domestic coverage as the United States (Alaska and Hawaii included), Puerto Rico, and United States (U.S.)

Virgin Island and all other areas as outside domestic as international roaming coverage.

To address and mitigate evolving cyber security threats as well as meet CSfC MACP requirements, DISA continues to use a hotspot in conjunction with the current and future DMCC EUDs for secure communication.

Currently DISA plans to deploy the initial devices using a WiFi connection to the hotspot in lieu of the required CSfC Ethernet/Ethernet over Universal Service Bus (USB) tethering. Unlike the previous DMCC-

S/TS devices, instead of using WiFi to connect to the hotspot, the current CSfC required connection is

Ethernet or Ethernet over USB since the current DMCC-S devices cannot meet the required CSfC end user device Operating System (OS) virtualization requirements. Thus, a USB-C to Ethernet adapter, Ethernet cable, and USB-C to USB-C male cable will be required. Which of these components required is dependent upon the EUD the hotspot will connect with. Ordering will provide the required items. However, WiFi is still required on the hotspot since it can be used for WiFi offloading of a tethered EUD acting with the hotspot acting as a WiFi client to a WiFi network.

Due to the CSfC Ethernet requirement the IDIQ will also provide the following Ethernet Tethering

Components when needed. Per hotspot order, a USB-C to Ethernet Adapter with 60-Watt Power Delivery

USB-C port needs to be provided. Based on the EUD, one of the following cables will be required. If an

Android EUD, a USB-C Male to USB-C Male cable is required. If a Windows EUD, then CAT6 Ethernet

Cables with dual RJ45 connectors is required. The cable selection will be done during ordering process. Both cables will be 4ft in length.

The current DISA Android and hotspot blanket purchase agreement (BPA) ends on 31 Jan 2025. From the time this IDIQ is awarded, DISA has the potential to replace all 4.9K Android devices and hotspots as well as replace all the current 4.1K+WINDAR-S hotspots. Variations in replacement will occur based on user ordering preferences. The Government’s main priority is to replace all the current deployed hotspots by 31

Jan 2025 before they are deactivated when the current contract expires. The android device replacement process plan is ongoing.

Note that while the Android device and cellular service/hotspot “swap” process is occurring, there will also be new orders occurring.

The contractor will be able to access the orders submitted by the Defense Information Technology Contracting

Organization (DITCO) via the Integrated Defense Enterprise Acquisition System (IDEAS) (reference instructions via FAR DARS Provisions and Clauses).

4. Objectives. The objective of this requirement is to establish a single award ordering vehicle to provide an enterprise offering for secure mobile communications capabilities to the DoD as well as Federal Agency and

Congressional/Executive Mission Partners in accordance with the NSA CSfC MACP and other Government requirements.

5. Scope. The scope of this requirement is to provide DMCC Android and Windows mobile devices, hotspot devices, associated data service plans and Ethernet tethering items. The contractor shall provide a hotspot for use with DMCC-S/TS mobile devices (i.e., Android smartphone and tablet, Windows tablet/2-in-1) that meets the Government’s RD requirements, as well as provide domestic, priority, and international data service plans.

Additionally, the contractor will be required to provide non-Windows and Windows EUDs that meet the requirements. Lastly, the USB-C to Ethernet adapter, as well as the Ethernet and USB-C cables mentioned above with each hotspot order if requested. The adapter and cables requirements are grouped as the “Ethernet

Tethering Components” in the IDIQ. Subsequent task orders, also referred to as Communication Service

Authorizations (CSAs), will be issued identifying the appropriate data service plan required for each DMCC-

S/TS user. All hotspots, EUD devices and Ethernet adapters procured under this IDIQ must be approved by the DISA Authorizing Official (AO). The Government may change solutions throughout the life of the IDIQ as technology and/or CSFC Requirements changes.

The contractor shall provide comprehensive order support for all items covered under this IDIQ contract.

Customer requests for products under this IDIQ will be placed through the web based DISA Storefront portal, or its replacement. DITCO will prepare and issue orders and modifications electronically in IDEAS.

Customer requests for services under this IDIQ will be prepared by DITCO and issued as a delivery order.

DITCO will also prepare and issue modifications ( as applicable) to resulting delivery orders. Comprehensive order support means the contractor shall be capable of the following:

Receiving and acknowledging automated orders within one business day of issuance by the

Government

Shipping the item within the timeframe as defined in the contract and in accordance with applicable Federal law or best practices

Maintaining detailed records on all purchases and shipments

Supporting ordering issues, equipment/product returns and repairs

6 Performance Requirements.

6.1 Hotspot Device Procurement

The offeror shall provide a hotspot device that meets the following specifications. Government may switch to a future comparable hotspot as technology changes via 3rd Generation Partnership Project Releases without the need for a contract modification or price adjustment.

1. The hotspot device must be Wi-Fi 802.11 standard (e.g., a/b/g/n/ac/ax).

2. The hotspot device must be able to connect to a cellular carrier priority services solution or IAP endpoint.

3. The hotspot must support full Dual-Band/Dual-Concurrent Wi-Fi.

4. The hotspot must support unlocked capability to support third party Subscriber Identifier Module (SIM), Nano-SIM, and/or eSIM in addition to the carrier SIM, Nano-SIM and/or eSIM. Both the carrier and 3rd party SIM, Nano-SIM and/or eSIM are not required to be installed simultaneously but be able to be swapped out instead when needed.

5. SIM, Nano-SIM, and/or eSIM configuration needs to be supported both domestically and internationally.

6. The hotspot must support firmware Over the Air updates from the supporting cellular carrier.

7. The hotspot must be able to support as a minimum the following DMCC-S device Local Area Network

(LAN) connection types to the hotspot with associated required supported Wide Area Network (WAN) type connections. Optional additional WAN interfaces provided too:

a. Wi-Fi Access Point LAN (4 VM Virtualized Next Gen WINDAR):

i. Required WAN Connections: (a) Ethernet [RJ-45] (Home/work); (b) Cellular (Inside/outside home & work)

ii. Optional WAN Connection: None

b. Ethernet over USB-C Tethering LAN (Current WINDAR):

i. Required WAN Connections: (a) Ethernet [RJ-45] (Home); (b) Cellular (Inside/outside home & work)

ii. Optional WAN Connection: (a) WiFi Client Point Offloading (Home/work)

c. Ethernet [RJ-45] Tethering LAN (Android Smartphone and Tablet via USB-C to Ethernet RJ-45 adapter):

i. Required WAN Connection: (a) Cellular (Inside/outside home & work)

ii. Optional WAN Connection: (a) WiFi Client Offloading (Home/work)

8. Ethernet:

a. Capable of 1 Gigabits per second (Gbps) via RJ-45 Ethernet LAN connection

b. Capable of 1 Gbps via USB-C/Ethernet LAN connection

c. Capable of 1 Gbps via RJ-45 Ethernet WAN connection

9. If the hotspot is configured as a WiFi access point the following requirements occur:

a. *Must implement Wi-Fi Protected Access 2 (WPA2) Pre-Shared Key (PSK) as a minimum, objective being WPA3 PSK1

b. *PSK must not be displayed on the main liquid-crystal display (LCD) screen except when the configuration menu is being accessed by an authenticated Administrator.

c. *Service Set Identifier (SSID) must not be displayed on the main LCD screen except when the configuration menu is being accessed by an authenticated Administrator.

d. *Media Access Control address of connected devices must not be displayed on the main LCD screen except when the configuration menu is being accessed by an authenticated Administrator.

e. *Wi-Fi Protected Setup must be able to be disabled.

f. *Traffic of multiple EUDs sharing the hotspot must be separated (commonly referred to as Wi-Fi

Privacy Separation or Access Point Isolation).

10. Capable of Internet Protocol version 6 support

11. *Administrator password must not be displayed on the main LCD screen except when the configuration menu is being accessed by an authenticated Administrator.

12. *Hotspot must be administered on the configured LAN side using HTTP. If WAN administration is a capability in the hotspot, then it must be able to be disabled by an authenticated Administrator via a configuration menu.

13. *Hotspot must require authentication with Administrator credentials to make changes to hotspot settings.

14. *Hotspot must not permit connected devices to access files stored on the hotspot.

15. *Hotspot must require Administrator authentication prior to downloading logs or configuration files.

16. *The hotspot must implement a firewall either software or hardware.

17. *The hotspot must strip and replace the Data-Link Layer protocol headers to the device between the hotspot and the connected device which as a minimum must replace the IP and MAC addresses from that

1 Requirements annotated with an “*” are CSfC MACP hotspot requirements. Any that are not met become a CSfC reportable “Deviation” that must be approved by the DISA Authorizing Official (AO) for approval to accept. All others are DISA hotspot requirements.

of the connected device before broadcasting over the selected WAN interface.

18. *The chip providing connectivity on the hotspot external/transport side must be physically separate from the hotspot main processer.

19. *The hotspot must be capable of being managed via wired LAN connection via USB and/or Ethernet

(RJ45).

20. Supported by a minimum 1-year standard warranty upon shipment to the Government. This includes replacement if required free of charge to the Government to include shipping.

21. Support: Hotspot vendor must be committed to providing a minimum of three years of hotspot updates, to include drivers, security patches, etc. per model provided. Updates can be delivered on the cellular interface by the supported cellular carrier.

22. The hotspot device(s) must be tested and obtain DISA AO approval prior to award.

Deliverable: Table 1: Hotspot Device

Table 1: Hotspot Device

SOW

Task#

Deliverable

Title

Format Due Date Distribution/

Copies

Frequency and Remarks

6.1 Hotspot Device Contactor

Format

1. Meet hotspot device requirements per Section 6.1, items 1 through 22.

2. CONUS and OCONUS

Government delivery days as follows for both hotspot only and when the hotspot is included with other EUD kits which have different delivery dates:

a. CSA order with 50 or less Hotspot only kits are 9 and 14 business days to delivery, CONUS and OCONUS respectively, from date of the submitted CSA order.

b. CSA order from 51 to 100 Hotspot only kits are 13 and 18 business days to delivery, CONUS and OCONUS respectively, from date of the submitted CSA order.

c. CSA order for 101 Hotspot or more only kits are 17 and 22 business days to delivery, CONUS and OCONUS respectively, from date of the submitted CSA order.

d. Hotspot devices will be packaged into the appropriate Hotspot and EUD

Kits per Section 6.8.4 Kitting and

Labeling

e. Delivery date per hotspot only kits per Section 6.8.1 Cellular Device

Delivery – Hotspot with/without

Ethernet Tethering Components

Procurement.

f. EUD Delivery date per inclusion into EUD Kits per Section 6.8.2 EUD

Device Delivery – Android End User

N/A As required

Devices and Section 6.8.3 EUD

Device Delivery-Windows End User

Devices.

6.2 Data Plan Procurement

In addition to the procurement of the hotspot devices, DISA requires the procurement of Standard or

Priority data service plans. The data plans shall allow end users to utilize the hotspot device to communicate through their DMCC mobile device. All secure communications will need to traverse through the hotspot device’s data plan or other WAN connection(s) as stipulated in Section 6.1.7.

1. Data Plan Procurement – Standard

The required plans for the DMCC user is dependent upon whether the hotspot will be operating in CONUS or

OCONUS. The data plan shall allow the DMCC customer to select from any combination of the following data plans based on the operating location and mission need. A combination of plans may be required between

Domestic and Global Plans to support TDY travel between CONUS and OCONUS. Users may submit a new order changing their current effective data plan(s) for Domestic Plans and/or Global Plans to another size offering to meet the user’s mission requirement.

a. The Government has identified a need for two data service Domestic Plans for use domestically:

i. 5 Gigabyte (GB)/month data plan

ii. Unlimited/month data plan

b. The Government has identified a need for six data service Global Plans for use globally:

i. Monthly Data Plan offering a minimum of 100 megabyte (MB)

ii. Monthly Data Plan offering a minimum of 300MB

iii. Monthly Data Plan offering a minimum of 800MB

iv. Monthly Data Plan offering a minimum of 1.5GB

v. Monthly Data Plan offering a minimum of 5GB

vi. Monthly Data Plan offering a minimum of 10GB

2. Data Plan Procurement – Priority Service Addition

DISA requires the procurement of priority service data plans for the DMCC Domestic Plans customers per the

Domestic Plans listed in Section 6.2.1.a. Priority Data Service Plans will prioritize the data from the hotspot across the cellular carrier network. Thus, providing for a better service in case of data congestion on the network. Priority data plans currently are not available for DMCC Global Plans customers for plans in Section

6.2.1.b since such international priority service is not available from current cellular carrier international cellular roaming partners. Presently, the contractor must offer the DMCC customer the option of choosing the

Domestic Priority Service Addition as an additive to their choice of Domestic Plans in Section 6.2.1.a. Note if a contract change is made to add/drop a Domestic Plan data service in Section 6.2.1.a, this section will apply to all resulting Domestic Plans listed in Section 6.2.1.a after the contact change has been enacted.

The Government has the capability to support, and the contractor must be able to provide, Priority Service

Addition data getting to the DMCC-S gateways via two different methods:

a. Direct Connection: Priority Service Addition data routed via cellular carrier network using

Multiprotocol Label Switching (MPLS)/Access Point Name (APN) traffic routing to carrier Points of

Presence (PoP) connected directly on the Department of Defense Information Network (DoDIN).

This gives data priority across the cellular carrier’s network directly to the DoDIN. The APN/MPLS configuration will be associated with only one SIM in whatever form factor compatible with the hotspot (e.g. Nano-SIM, eSIM, etc.). The MPLS/APN private network shall be configured as follows: 1) No internet transport; 2) Network traffic precedence; 3) Network traffic segmentation.

b. Internet Connection: Data priority across the cellular carrier network until it is offloaded to the

Internet at which point it becomes Internet best effort data routing. Data is routed across the Internet until accessing the DoDIN via multiple DoD outward facing Internet Access Points (IAP) located at the Defense Enterprise Computing Centers in Texas, Ohio, and Utah.

The MPLS/APN cellular carrier PoP connection to the DoDIN is not mandatory, but available for use if the cellular carrier PoPs currently exist to be exercised in coordination with the Government at no additional expense to the Government since the data IP packet path connections are available. If MPLS/APN private network is not available to be used or not elected for enablement by the Government, then Priority Service

Addition data path routing to DMCC Gateways will be via the Internet to the DoDIN IAPs as noted above and what is currently in use.

Deliverable: Table 2: Data Plan

Table 2: Data Plan

PWS

Task#

Deliverable

Title

Format Due Date Distribution/

Copies

Frequency and

Remarks

6.2 Data Plan

activation / change

/termination information per

Online Tool

(Section 6.4)

Contactor

Format:

Online Tool

(Section 6.4)

Required data plan usage information must be present in the Online Tool (Section

6.4) within or at 10 calendar days after the billing cycle.

Data plan type and activation date information must be visible in the Online tool for the hotspot on or before the scheduled hotspot delivery date as provided in

Section 6.8.1, Section 6.8.2, and Section 6.8.3 for

CONUS and OCONUS number of business days delivery requirement from

CSA order date.

6.3 Cellular Service Coverage

Offeror shall provide a hotspot that is compatible with the frequency bands supported (Transmitted Frequency) and Waveforms/Protocol Stack supported (fourth-generation (4G) and fifth-generation (5G) where available) designated for access for both Domestic (CONUS) and International (OCONUS) coverage. Government understands that the 5G Waveform/Protocol Stack is not broadly deployed in OCONUS today except in select concentrated areas (Japan, South Korea, European (70%), etc.). The overall aim of this task is to cover to the maximum extent possible the various Combatant Command (COCOM) Regions geographical countries around the world using whatever combination of available frequency bands, listed and unlisted, with 4G/5G Waveform

Protocol Stacks to provide adequate bandwidth capacity service to DMCC users.

1. Domestic Coverage-Standard

a. Frequency Bands: At a minimum, the hotspot device shall be compatible with at least four bands from the available International Telecommunication Union (ITU) Region 3 North America bands listing: 1, 2, 3, 4, 5, 7, 12, 13, 14, 17, 25, 26, 28, 29, 30, 41, 46, 48, 66, 71, 77, 79 and FR2. As technology continues to mature and further migrate to 5G and beyond to XG, the frequency bands listing will evolve geographically across CONUS and as such are subject to change without the need of a contract change, just Govt update instead.

b. Waveform/Protocol Stack Support: The 4G Waveform/Protocol Stack needs to support a minimum of four of the selected frequencies in Section 6.3.1.a. The 5G Waveform/Protocol Stack needs to support, where geographically available, a minimum of two of the selected frequency bands in

Section 6.3.1.a. In those geographic regions where the listed frequencies in Section 6.3.1.a are unavailable to support the 5G Waveform/Protocol stack, then unlisted frequency bands can be utilized in place of Section 6.3.1.a. Overall, the 4G and 5G requirement is to provide a minimum of four and two 4G and 5G Waveform/Protocol Stacks respectively across CONUS where geographically available and supported. Either case, the 4G and 5G Waveform/Protocol Stacks, per the overall geographically available frequency bands ultimately selected, are required to meet the bandwidth capacity requirements per Section 6.3.4.a Bandwidth Capacity Domestic Coverage. As technology continues to mature and further migrate to 5G and beyond to XG, the Waveform/Protocol stacks will evolve geographically across CONUS and as such are subject to change without the need of a contract change, just Government update instead.

2. Domestic Coverage-Priority Service

Priority service shall use what frequency band(s) are supported to achieve it but must be as a minimum consist of two 4G Waveform/Protocol Stacks and one 5G Waveform/Protocol Stack compatible with the hotspot. The frequency bands should match those listed in Section 6.3.1 Domestic Coverage-Standard but unlisted bands can be used if listed bands are not available. However, the priority service bandwidth capacity for both the 4G and 5G Waveform/Protocol stacks are required to meet the capacity bandwidth per Section 6.3.4.a Bandwidth Capacity Domestic Coverage.

3. International Coverage

a. Frequency Bands: It is understood that internationally, frequency bands vary from country to country and can vary greatly within different regions of the same country. Therefore, identifying select frequency bands for each COCOM area, which covers multiple countries of all different sizes, is not plausible. Instead, a whole OCONUS approach is required comparable to the CONUS approach. At a minimum, where geographically available, the hotspot device shall be compatible with at least two frequency bands from the available ITU Regions 1, 2, and 3 roaming bands listing: 1, 2, 3, 4, 5, 7, 13, 17, 20, 28, 40, 41, 66, 77, 78.

b. Waveform/Protocol Stack Support: Internationally, the 4G Waveform/Protocol Stack covers 90% of the world’s population and is increasing in density across OCONUS with higher concentration in more developed countries, especially in urban areas. However, unlike the current DMCC BPA, the third-generation (3G) Waveform/Protocol Stack is not a requirement in this PWS due to lack of hotspot original equipment manufacturer (OEM) support in this Waveform/Protocol Stack as carriers repurpose frequencies to 4G/5G Waveform Protocol Stacks.

1) 4G Waveform/Protocol Stack: Across the OCONUS COCOMs, excluding United States Africa

Command (AFRICOM), where frequency bands are geographically available that support the 4G

Waveform/Protocol Stack, at least two of the selected frequency bands from Section 6.3.3.a. shall be provided by the contractor, with three frequency bands provided in higher density population areas, if available. In those COCOMs geographic regions where the frequency bands listed in

Section 6.3.3.a are unavailable to support the 4G Waveform/Protocol stack, then unlisted frequency bands that do support the 4G Waveform/Protocol Stack can be utilized in place of the frequency bands listed in Section 6.3.3.a. Overall, excluding AFRICOM, the 4G requirement is to provide at least two 4G Waveform/Protocol Stack across OCONUS and have three such stacks where geographically available and supported. For AFRICOM, only one 4G Waveform/Protocol

Stack frequency band is required where geographically supported (e.g., major cities), with two

(2) frequency bands supported in higher density population areas if available. Outside those areas where 4G Waveform/Protocol Stack is not available, support is not required. Support will be only available if the hotspot optionally, not required, supports the 3G Waveform/Protocol

Stack.

2) 5G Waveform/Protocol Stack: Across all the OCONUS COCOMs, 5G Waveform/Protocol Stack is not required.

3) Waveform/Protocol Stack Bandwidth Capacity: It is understood, as noted above, that frequency bands will vary widely across the various OCONUS COCOM geographic areas, but the required number of 4G Waveform/Protocol Stacks in those areas remains the same regardless of the frequencies used. Regardless, the 4G Waveform/Protocol Stacks are required to meet the bandwidth capacity requirements per Section 6.3.4.b International Coverage excluding Africa

Command and Section 6.3.4.c International Coverage Africa Command respectively. The 5G

Waveform/Protocol Stack, if provided where geographically available, will be required to meet the same bandwidth capacity requirements provided above for 4G.

4. Bandwidth Capacity

The hotspot device and cellular network should at a minimum provide the following bandwidth transport capacity for the following locations. This excludes any bandwidth throttling caused by the source data network when downloading/ uploading data across the cellular network.

a. Domestic Coverage: 15 megabits per second (Mbps) download and 4 Mbps upload.

b. International Coverage excluding Africa Command: Best effort.

c. International Coverage Africa Command: Best effort.

Deliverable: Table 3: Service Coverage

Table 3: Service Coverage

Task#

Deliverable

Title

Format Due Date Distribution/

Copies

Frequency and

Remarks

6.3 Service

Coverage

Contactor

Format Provided in Request for

Proposal (RFP) response for evaluation

N/A In RFP original response and updates

6.4 Web Services/Online Account Management Tool (Online Tool) & Reports

1. Web Services/Online Account Management Tool (Online Tool): The offeror shall provide the

Government access to their online account management tool to access data usage reports, both aggregated and for each user account, that is updated within 10 days of the bill period end date. The offeror’s tool will allow only specific users to query usage data over a specified period. Query results shall be downloadable and in either a text delimited and/or Microsoft Excel format. The other requirement for the Online Tool is to check to see if a hotspot has an active data plan and what that data plan is, to support troubleshooting during EUD provisioning, and to confirm that a hotspot has active service in case the hotspot is not showing connectivity to the cellular carrier network or data is not being transported during the provisioning process. The hotspot is required to be listed in the

Online Tool by the expected CONUS or OCONUS delivery date of the hotspot to the Government as defined in Section 6.8.1 “Cellular Device Delivery – Hotspot with Ethernet Tethering Components

Procurement”. Hotspot Data usage reporting is not required to be reportable until the defined 10-day reportable time period has elapsed as noted above.

The online tool could be the providing commercial cellular provider tool already operational. The offeror will provide Government Personnel and cleared designated Government Offerors access to the tool within two weeks after contract award as well as a link to tool usage manuals/FAQ and offeror helpdesk chat/telephone number for tool support 24 hours a day, seven days a week. Offeror procedures for requesting access to the tool will be provided within one week after award.

2. Data Submission Quarterly Reports: The offeror will be responsible for submitting a quarterly report which summarizes the following information per table row: Table

4.1 – Data Submission Quarterly Report Items.

Table 4.1: Data Submission Quarterly Report Items

Procurement Instrument Identifier

(PIID) and CSA

PIID as required by the Federal Acquisition Regulation (FAR 4.605) and CSA

2 Data Plan (GBs) Total amount of purchased cellular data

3 Data Usage (GBs) Total amount of used cellular data

4 # of Other Devices Format: # Hotspot devices

The Data Submission Quarterly Reports are to be provided on a quarterly basis on or before the following dates and can be searched online from the contractor/cellular carrier:

a. 1st Quarter – 31 January

b. 2nd Quarter – 30 April

c. 3rd Quarter – 31 July

d. 4th Quarter – 31 October

3. Data Submission: Bi-Weekly Activity Record Report: The offeror will be responsible for submitting an Excel Bi-Weekly activity record report which summarizes and compiles the following information per table row element item:

Table 4.2 – Data Submission B-Weekly Report Items. Note that EUDs are not directly on the mobile carrier cellular network. Thus, the EUD data identified in columns K (EUD Type), L (EUD Model Name) and M (EUD SN#) must be procured via other means then the carrier network so to be added to the report.

Table 4.2: Data Submission Bi-Weekly Report Items

Column Column Header Data Field Description and Conditions

A Account Number Order IDIQ/Commercial Cellular Provider Account number per newly created CSA for new Orders

B Username IDIQ/Commercial Cellular Provider Account name per DITCO assignment.

Each new order is assigned a CSA by DITCO and assigned by

IDIQ/Cellular Provider as the username

C Current Service

Access Number

Hotspot Commercial Phone number

D Original Service Date Activation date of the line

E Price Plan Name Domestic rate plan assigned to the hotspot (Note: Naming convention to be determined at award)

F Add-On Plan Name International rate plan if applicable (Note: Naming convention to be determined at award)

G Hotspot Model Hotspot Model Number (Note: If ordered in lieu of data plan change record posting, then post “N/A” if for data plan change record)

H Hotspot IMEI Hotspot IMEI (Note: Provided for both order and data plan change record)

I Hotspot Serial # Hotspot Serial Number (Note: Provided for both order and data plan change record)

J User defined Label CSA Name

K EUD Type “Smartphone” or “Tablet” (If ordered under the same CSA number, otherwise “N/A” for hotspot only order)

L EUD Model Name OEM device model name (e.g., S23, Tab S9, etc.) [If ordered under the same CSA number, otherwise “N/A” if for hotspot only order]

M EUD SN# OEM EUD designated serial number (If ordered under the same CSA number, otherwise “N/A” if for hotspot only order)

The Data Submission Bi-Weekly Report is due the Monday following the previous Friday that corresponds to the Government Electronic Funds Transfer (EFT) Pay Date per the GSA Payroll calendar (e.g., for 2024;

https://www.gsa.gov/system/files/2024_GSA_Payroll_Calendar.pdf). If the following Monday after the designated GSA EFT Pay Date is a Government Holiday, then the report is due the next day, that being

Tuesday.

Each row in the Excel file is a new CSA order EUD and/or hotspot if both items ordered the same time or change data plan record for that two-week duration. File naming convention follows: “Year-month-date_BPA_2_week_activity_record” (e.g., 2024-01-05_BPA_2_week_activity_record) where the date is the

GSA EFT date. The 1st Excel tab will list the EFT date in same format as file name date and will list the 2 weeks activity record per Table 4.2. The 2nd Excel tab labeled "Contract Year Compilation" will be a running compilation of all the activity record data to date for that year of the contract. A new compilation will occur with each new year of the contract.

4. Data Submission: Weekly Shipping Report: The offeror will be responsible for submitting an Excel weekly activity record report which summarizes and compiles the following shipping information for that week of CSA orders shipped and any shipments that are still outstanding for delivery. Once delivered, the shipment is dropped from the next weekly shipment report once the shipment has been reported delivered in Column I for that week’s shipment report. The contractor shall note delays caused by strikes, foreign custom clearance, natural disasters, severe weather, and conflicts. These delays, to the extent that acceptable justification is provided to the Government, will extend the required delivery date.

However, delays attributable to the contractor or subcontractor(s) will not extend the required delivery date. Such delays shall be identified, verified, and accounted for in the Weekly Shipping report data field

“Delayed Order Update”, Column H, with revised estimated delivery date in Column C. The shipment report will be provided per the format listed in Table 4.3.

Table 4.3: Data Submission Weekly Shipping Items Report

Column Column Header Data Field Description and Conditions

A Account Number Order IDIQ/Commercial Cellular Provider Account number per newly created CSA for new Orders

B Ship date Date the CSA order was shipped

C Schedule arrival date Date the CSA order is scheduled to arrive at destination

D Shipping Carrier Shipping carrier receiving and responsible for destination delivery

E Provisioning Site Name Short name for shipping destination per Table 6.8 for provisioning sites

F Number of shipped items Total number of boxes shipped in the shipping order

G Tracking number(s) Group/individual shipping tracking numbers for all items shipped linked to each individual item if appropriate.

H Delayed Order Update Information on shipment delay such as strikes, foreign custom clearance, natural disasters, severe weather, and conflicts. The scope is to identify the cause, verification proof of the cause, and updated delivery date in Column C.

I Delivered Date Date of actual delivery

Note, as new destination shipping sites are added, site short name and destination addresses will be provided.

The following file naming convention shall be used by the contractor: “Year-month-date_IDIQ_weekly_shipping_record” (e.g., 2024-01-05_IDIQ_weekly_shipping_record) where the date is the carrier pickup date. The 1st Excel tab will list the shipping date in same format as file name date and will list the weekly shipping activity record per Table 4.3. The 2nd Excel tab labeled "Contract Year Compilation" will be a running compilation of all the shipping activity record data to date for that year of the contract. There will only be a single line entry for each shipment and thus be updated as needed until the shipment is delivered. A new compilation will occur with each new year of the contract.

Deliverable Table 4.4: Web Services/Online Account Management Tool (Online Tool) & Reports

Task#

Deliverable

Title

Format Due Date Distribution/

Copies

Frequency and Remarks

6.4.1 Web

Services/Online

Account

Management

Tool (Online

Tool):

Contactor

Format Tool access procedures: 1 week after award.

Tool access: 2 weeks after award

Hotspot active plan service information listed in the

Online Tool by hotspot expected delivery date to

CONUS or OCONUS destinations per Section

6.8.1. Cellular Device

Delivery – Hotspot with

Ethernet Tethering

Components Procurement

N/A Government usage as required.

6.4.2 Data

Submission

Quarterly

Reports

Downloadable in delimited text or MS

Excel format

Quarterly per the following:

a. 1st Quarter – 31 January

b. 2nd Quarter – 30 April

c. 3rd Quarter – 31 July

d. 4th Quarter – 31 October

Standard 1 Soft

Copy* to include the HaCC

DMCC-S

Provisioning

Lead

Quarterly

6.4.3 Data

Submission Bi-

Weekly

Activity Record

Reports

MS Excel format The Monday after the Friday

GSA EFT Pay Date as noted in Section 6.4.3

Standard 1 Soft

Copy* to include the HaCC

DMCC-S

Provisioning

Lead

Bi-weekly

6.4.4 Data

Submission

Weekly

Shipping

Report

MS Excel format Provided every Friday for a consolidated CSA shipment

Standard 1 Soft

Copy* to include the HaCC

DMCC-S

Provisioning

Lead

Weekly

*Standard Distribution: 1 copy of the deliverable to the Contracting Officer, Contract Specialist, Primary COR, and

Alternate COR.

6.5 Customer Service Support Requirement

For technical support, the Government provides Tier 1, 2 and 3 support for DMCC. The required support for the contractor is Tier 4 support only, Manufacturer support, and included in the service cost. This support shall be 24 hours a day, 7 days a week. The offeror shall provide a Tier 4 help desk technical support for the Government.

DMCC users do not contact Tier 4 support directly but submit trouble tickets to DMCC Tier 1 support. Those tickets escalate up through the other Government Tiered support as needed and only Government Tiered support contacts Tier 4 as needed. The contractor helpdesk may consolidate and represent the actual OEM equipment helpdesk for actual technical support and subsequently relay and monitor ticket request as an intermediary service function instead of providing actual OEM level technical expertise. Currently Government Tier 1, 2, and 3

Technical support is CONUS based. However, the contractor is required to provide OCONUS as future

OCONUS DMCC gateways are deployed.

For provisioning, the Government runs operations both in CONUS and OCONUS locations. The same helpdesk will support the ordering and delivery process too as well as any data plan and cellular services issues from

Government CONUS and OCONUS locations. The contractor helpdesk may consolidate and represent the mobile carrier helpdesk for the actual data plan and cellular services support and subsequently relay and monitor ticket request as an intermediary service function instead of providing actual mobile carrier level technical expertise.

The contractor shall assist the Government Technical and Provisioning ticket submitters with timely resolution of the reported problem and maintain contact with the reporting user until final resolution of any identified problems until the reporting user has verified/accepted the resolution. It is the contractor Service Support desk that is also responsible for ensuring the appropriate supporting equipment OEM and/or mobile carrier is engaged and supporting the appropriate trouble ticket to resolution in a timely manner.

For CONUS support the helpdesk shall aid by phone, email, and Internet messaging/chat for live support. The supporting CONUS phone number shall be a toll-free number. For OCONUS Customer service the helpdesk will provide email, along with Internet messaging/chat for live support. For OCONUS, in lieu of internet messaging/chat, live phone service can be used but only at no additional cost to the Government for the phone call. Customers may be queued on the phone and Internet messaging/chat while waiting for live support to connect. Below are required times:

a) Phone/Online message/chat queue Initial response time: 1) Very Important Person (VIP)/Critical: 5 minutes; 2) Non-VIP/General: 15 minutes

b) Once a ticket has been generated it must be delivered to Tier 4/OEM by the following times: 1)

VIP/Critical: 30 minutes; 2) Non-VIP/General: 4 hours.

c) Tier 4 / OEM Tech Support Initial Response Interaction time once ticket generated and received by Tier

4/OEM: 1) VIP/Critical: 20 minutes; 2) Non-VIP/General: 24 hours.

VIP is defined as a Flag Officer, Senior Executive Service, and Honorable customers. Critical is defined as a service outage effecting cellular service, helpdesk, and/or EUDs that are affecting multiple (>10) or all users simultaneously. General defines all other requests.

The offeror will provide a PDF flyer for accessing phone, email, and online customer support for both CONUS and OCONUS on the same flyer with a draft for Government review within 1 week after award.

Final approved list will be within 1 week of Government feedback. Customer Service Support shall be fully operational within 1 week after Government approval.

Deliverable: Table 5: Customer Service Support

Task#

Deliverable

Title

Format Due Date Distribution/

Copies

Frequency and

Remarks

6.5 Customer

Service Support

Contactor

Format Maximum response and queue times capability review is due 1 week after award

Draft online PDF flyer is due 1 week after award

Final version is due 1 week after Government feedback

Fully operational is due 1 week after Government approval

6.6 Smartphone and Non-Windows Tablet EUD Procurement

The below generic requirements are the present EUD baseline and future EUDs will be equal or better than the below requirements as device technology improves. The Government may switch to future comparable EUDs, provided they are listed on the CSfC Components List Category End User Device/Mobile Platform, without the need for a contract modification. The offeror shall provide a smartphone and tablet device that meets the following specifications:

1. Smartphone and Non-Windows EUD CSfC Requirements.

Per PWS Section 6.5.1, CSfC requires the EUD to be listed on the CSfC Components List End User

Device/Mobile Platform Selection document. In order for this subfactor to be rated Acceptable, the

IDIQ Contract Provider will provide devices that are listed on the CSfC Components List per the

Category End User Device/Mobile Platform.

2. Smartphone and Non-Windows Tablet EUD CSfC DAR Requirements:

The EUDs must have CSfC Components list Data-at-Rest capability per the current DAR Capability

Package (CP). The DAR requirement can be deployed per the CSfC Components List as "File

Encryption" and/or "Hardware Full Drive Encryption". The corresponding CSfC Components List

“Selection” document on the CSfC website, delineates the specific and additional NIAP certification requirements for the two types of encryptions needed to be listed on the CSfC Components List. The contractor will provide the appropriate dual layers of encryption on the End Device as proscribed in the prevailing DAR CP using appropriate DAR components from the CSfC Components List. Per the current Android devices used on DMCC, the Government provides the licensing required to activate the Dual DAR capability via our on-premises Premium Knox Platform for Enterprise + Dual DAR licenses servers. This occurs during the Government Android EUD provisioning process. The

Government will continue to purchase the Dual DAR software licensing to include for any new OEM devices used in the future. If the Offeror proposes a different Dual DAR capability for smartphone and Non-Windows tablet EUD, the Offeror needs to inform the Government in their proposal or proposed later after contract award, on the impact of the licensing and hardware/software to implement the Dual DAR capability on the EUD and the DMCC-S gateways network if applicable.

3. Smartphone and Non-Windows Tablet EUD Device Requirements

a. Screen size minimum: a) Smartphone: 6.0 in; b) Tablet: 10 in [Note:

Folding phones full open size corresponds to EUD screen size]

b. Resolution minimum: a) Smartphone: 720 x 1080; b) Tablet: 800 x 1280

c. Storage Memory minimum: 128 GB

d. Processor Memory: 8 GB Minimum

e. Loudspeaker minimum: 2 speakers

f. USB: Minimum of one port of Type-C 3.1 or better

g. Battery capacity device minimum in milli-Amp hours (mAh) shall be the following or better: a) Smartphone: 3,600 mAh; b) Tablet: 7,500 mAh.

Understanding that with the advancements in both battery and mobile device technology, battery mAh capacities may decrease in future devices due to efficiency increases. In doing so the current provided values may no longer be accurate. In that case the Govt will review the requirement and update the requirement so to be in step with technological advancements. This action is at the Government’s sole discretion.

h. Operating System: Non-Windows OS listed on CSfC Components List

i. Sensors: Fingerprint

j. Minimum Charging protocol: PD 3.0

k. Charging minimum wattage (Non-fast): a) Smartphone 5 Watts; b) Tablet:

10 Watts

l. Charging minimum wattage (Fast): a) Smartphone 15 Watts; b) Tablet: 30

Watts

m. Stylus supported, Tablet: Capacitive Stylus Pens, Rubber Tip

n. Keyboard supported, Tablet: Pogo pins

o. Build: Glass front, metal (e.g., Aluminum) Frame, metal (e.g., Aluminum)

Back [Note: Folding phone hinge not specified and may…