Secure Telephony Equipment and Peripherals (STEP)_DRAFT PWS.pdf

CUI

FA2541-24-X-XXXX Page 1 of 19

PERFORMANCE WORK STATEMENT

FOR

ENHANCED MOBILE SATELLITE SERVICES (EMSS)

SECURE TELEPHONY EQUIPMENT AND PERIPHERALS (STEP)

DRAFT

Controlled by: United States Space Force

Controlled by: SSC/CSCO/EMSS/PMO

CUI Categories: PROCURE

Distribution/Dissemination Controls: FEDCON

POC: disa.meade.ie.mbx.emss-cor-team@mail.mil // 301-225-2800 mailto:disa.meade.ie.mbx.emss-cor-team@mail.mil

FA2541-24-X-XXXX Page 2 of 19

1.0 DESCRIPTION OF SERVICES

1.1 General. The United States Space Force (USSF) / Commercial Satellite Communications Office

(CSCO) / Enhanced Mobile Satellite Services (EMSS) / Program Management Office (PMO) provides the Department of Defense (DOD), United States Government (USG), foreign partners and other sponsored with satellite communication services through a dedicated, EMSS-controlled Service Center.

EMSS is a value-added specialization of unique infrastructure and services made available to EMSS

Mission Partners. EMSS is a service, enabled by satellite ground systems, which interface with the commercial Iridium mobile satellite system, consisting of a 66 satellite, a mesh-network Low Earth Orbit constellation. Offered EMSS services currently include Iridium voice -unclassified and classified, one-way paging, Short-Burst Data (SBD) (two-way ackno0wledged data transmission), Global Data

Broadcast (GDB) one-way multicast), and Distributed Tactical Communications System (DTCS), a one-to-many push-to-talk voice and data service. Additionally, the EMSS PMO provides for the sale and provisioning of EMSS devices, 24/7/365 dedicated help-desk support, Field Service Representative support and other services.

The EMSS architecture is comprised of the following three (3) segments: Commercial Space Segment, EMSS Ground Segment, and a Mobile Segment. The Commercial Space Segment is currently comprised of the Iridium commercial product (i.e., satellite infrastructure), while the EMSS Ground and Mobile segments include both commercial elements and non-commercial elements tailored for EMSS customers.

Each segment evolves over time to provide greater capability and additional services.

1.2 Scope. The contractor shall provide comprehensive order fulfillment for all items covered under this contract and placed through the web-based ordering tool used by all DOD and its Mission Partners called Storefront (or specified DOD Marketplace). Comprehensive order support means the contractor shall be capable of receiving and acknowledging automated orders within one (1) business day or less of issuance by the Government; shipping the item within the timeframe requested by the EMSS customer 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; and cooperating with and supporting the EMSS PMO for data collection.

Items covered under this contract support secure voice capability for approved EMSS users. All communications equipment must be certified by Iridium and approved by the EMSS PMO for EMSS use.

All communications equipment must be delivered provisioned to immediately communicate on the EMSS network, (assuming the Subscriber Identity Module (SIM) card was activated previously, and the customer has a 9575A in their possession.) or be eligible for activation in accordance with the order as requested. All cryptographic equipment must be certified by National Security Agency (NSA) and the vendor shall comply with all NSA requirements that pertain to the secure voice devices. The Government reserves the right to add or remove items at any time during the duration of the contract.

The contractor must support a successful working relationship and process with the contracting office, EMSS PMO, and EMSS customer support service contractor to meet EMSS secure voice customer support requirements.

1.3 Background. The ISM2 interoperates with the 9575A, and together these components comprise a

Secure Iridium Subscriber Unit (SISU). The ISM2 fits into an Iridium phone, the 9575A, which is specially designed to house and operate with the ISM2. The architecture and hardware developed in the initial phase was intended to maintain current secure call capabilities utilizing the same cryptographic algorithm used by the 9505A and the original Iridium Secure Module (ISM). The 9575A and ISM2 are

FA2541-24-X-XXXX Page 3 of 19 available for order on Storefront (or specified DOD Marketplace). The efforts under this contract are required to fulfill the orders for the ISM2 devices, repair services and other support services.

2.0 TASK DESCRIPTIONS

The contractor shall furnish the necessary personnel, materials, facilities, and services to provide EMSS throughout the world in accordance with this PWS. The Contractor shall furnish all components, software, services, and compliance requirements for all products delivered under this contract according to the standards applicable to such items. All Intellectual Property (IP) associated with the Contractor’s performance of the tasks in this PWS shall be governed in accordance with (IAW) the terms and conditions of the contract associated with this PWS.

The summary of services and support anticipated under this PWS are contained in the task areas identified below:

• Task 1: Stakeholder Orientation and Project Kickoff

• Task 2: Programmatic Support, Planning, and Reporting

• Task 3: Equipment and Other Procurable Items (CR)

• Task 4: Surge

2.1 Task 1 - Stakeholder Orientation and Project Kickoff

2.1.1. Subtask 1 - Kickoff Meeting. The Contractor shall coordinate with the Government and host a

Project Kickoff Meeting with the Government not later than five (5) calendar days after contract award. It will be held at the Government's facility, Contractor’s facility, virtual or another mutually agreed upon location, and approved by the Government. The date and time will be mutually agreed upon by both parties. The meeting will provide an introduction between the Contractor and Government personnel involved with the contract. The meeting will provide the opportunity to discuss technical, management, and logistic issues; travel authorization; communication process between Government and Contractor;

and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, OFFICE

(SAF/# or AF/#), and key Government personnel provided by the government.

2.1.2. Subtask 2 - Kickoff Meeting Agenda and Presentation. The Contractor shall provide a draft copy of the agenda not later than three (3) days after contract award for review and approval by the COR, prior to finalizing. The Government will provide the Contractor with the number of participants for the kickoff meeting and the Contractor shall provide sufficient copies of the presentation for all government representatives present upon start of the meeting. The Contractor shall provide a Kickoff Meeting

Agenda that will include, but not be limited to, the following:

• Introduction of Personnel

• Review of Organization and Points of Contact

• Overview of Project Tasks

• Schedule, Major Tasks, Milestones (w/dates), and Deliverables

• Communication Plan/Lines of Communication Overview

• Discussion Of Draft Project Management Plan (PMP)

• Travel Notification and Processes

• Government-Furnished Property (GFP)

• Security Requirements (Building Access, Badges, Common Access Cards [CAC])

• Analytical Support Status Accreditation (ASSA) Documentation

• Invoice Procedures

• Monthly Meeting Dates

FA2541-24-X-XXXX Page 4 of 19

• Reporting Requirements (e.g., Monthly Status Report)

• Roles and Responsibilities

• Overview of Transition/Software Transition Out Processes, Timeframes, And Statuses

• Prioritization Of Contractor Activities

• Any Initial Deliverables

• Other Logistic Issues

• Quality Control Plan (QCP)

• Sensitivity And Protection of Information

• Additional Issues of Concern (Leave/Back-Up Support)

2.2. Task 2 - EMSS Programmatic Support, Planning, and Reporting

The contractor shall be required to establish and maintain a working relationship with Iridium LLC, the

EMSS PMO and the customer support service vendor for any clarifying information on provided equipment.

2.2.1. Subtask 1 - Corporate Requirements

a) The contractor shall be an authorized Iridium Value-Added Reseller (“VAR”) in good standing with Iridium and must be capable of providing evidence of this status at any time during the contract’s duration.

b) (b) The contractor must have a demonstrated corporate firewall between all commercial

Iridium business and EMSS business. Evidence of such shall be provided within the Contractor’s

Project Management Plan (PMP) and reaffirmed in writing annually. Please see Article 13(b), “Identification of Potential Conflicts of Interest.”

c) (c) The contractor shall cooperate with all EMSS third-party contractors and support a successful working relationship with the EMSS customer support service contractor.

d) (d) The contractor shall be capable of storing and handling the ISM2, which is a

Communication Security (COMSEC) Controlled Item (CCI), and its associated key material, which will include the handling and storage of keys at the SECRET and TOP SECRET classification levels. The contractor requires a COMSEC account with the ability to procure keying material up to TOP SECRET.

2.2.2. Subtask 2 - Management of Activities, Staffing, Schedule, and Budget. The Contractor shall determine and establish the project organization to provide overall management of the contract work. The

Contractor shall designate key personnel responsible for the cost, schedule, and performance for the contract and shall serve as a primary point-of-contact for both management and technical matters. The contractor shall establish and maintain a working relationship with Iridium LLC, the EMSS PMO and the customer support service vendor for any clarifying information on provided equipment.

The Contractor shall produce a Project Management Plan (PMP) within ten (10) days of contract award.

It shall describe the technical approach, organizational resources, and management controls to be employed to meet cost, schedule, and performance requirements. The PMP shall be reviewed and approved by the Government. Changes to the PMP, as required, shall be implemented annually by mutual agreement between the Government and the Contractor based on evolving requirements throughout the entire life of the contract.

FA2541-24-X-XXXX Page 5 of 19

2.2.3. Subtask 3 - Monthly Status Reporting (MSR) The Contractor shall provide a Monthly Status

Report (MSR). The MSR shall address any major activity, progress and status of the work accomplished during the reporting period including any risk assessment and management reporting. All monthly report data shall be reported for the same reporting period. The convention used should be synchronized across all reported services. Standard convention is as of the first day of the monthly reporting period at

00:00AM UTC through 11:59PM UTC of the last day, which coincides with the first performance day after contract award. The MSR shall include the status of contract deliverables, risks, projected activities, meetings, travel, and other status information pertinent to the execution of the contract. The MSR shall provide a financial review and include the current amount funded, received, obligated, and billed against each CLIN and the estimated burn rate.

(a) Reported activities shall include but are not limited to equipment order status, filled, and shipped orders, other user terminal serial numbers, summary of all repair services, and status of inventory and/or issues related to inventory, delivery fulfillment metrics detailing the date the order was shipped and received. This will become the metric for meeting “Performance

Standards.” The metric formula will be:

Standard delivery: 14 minus (order shipped date – order received date) = Days to fulfill order.

Should the number be less than 0 (indicating that an order took longer than 14 days), this order will be considered as late. Orders more than 30 days old will be considered delinquent and the

EMSS COR and customer shall be briefed on the status of the order and a course of action shall be identified.

The contractor shall promptly notify the EMSS COR and customer of any projected delays (e.g., the order is large and exceeds stock levels). This notification shall explain the reason for the delay and the contractor’s proposed mitigation strategy for addressing and correcting the issue.

(b) The contractor shall provide a Quarterly Trend Analysis Report that examines significant or noteworthy activities and purchasing trends during the reporting period. The report shall further delineate these activities by month.

2.2.4. Subtask 4 - Operations Security (OPSEC) Plan. The Contractor shall develop an Operations

Security (OPSEC) Plan at the start of the contract. The OPSESC Plan shall describe the Contractor’s plan for protecting critical information related to efforts conducted on the contract. The OPSEC Plan shall be reviewed and approved by the Government. The Contractor shall update the OPSEC Plan on an annual basis. Changes to the OPSEC Plan shall be implemented by mutual agreement between the Government and the Contractor based on evolving requirements throughout the entire life of the contract.

2.2.5. Subtask 5 - Risk Management Plan (RMP). The Contractor shall produce a Risk Management

Plan (RMP) at the start of the contract. The RMP shall describe the Contractor’s plan for identification of potential risks as well as outline potential risk mitigation strategies. The RMP shall be reviewed and approved by the Government. The Contractor shall update the RMP as required and include a summary of the current risks and mitigations during the Quarterly In-Progress Review.

2.2.6. Subtask 6 - Quarterly In-Process Review (IPR). The Contractor shall participate in quarterly In-

Progress Reviews (IPR) at a location determined by the EMSS PMO. The Government will provide the format and agenda two weeks prior to the scheduled review. The Contractor shall provide a draft IPR briefing one week prior to the scheduled review. The IPR will represent a cumulative reporting of MSRs as well as planned forecasting for the following quarter.

FA2541-24-X-XXXX Page 6 of 19

2.2.7. Subtask 7 - Semi-Annual and Annual Project Management Review (PMR). The Contractor shall participate in Semi-Annual PMR, conducted at the location determined by the EMSS PMO to address

EMSS services' status and to assess the potential for changes that can reduce costs, improve end-user services, or enhance administrative and management systems. The Contractor shall participate in an

Annual PMR/Technology Interchange Meeting (TIM), conducted at the EMSS Service Center to include the wider operational audience to address EMSS services' status and to assess the potential for changes that can reduce costs, improve end-user services, or enhance administrative and management systems.

The Contractor shall prepare and present analyses and data in briefing format, to support these reviews, which may include such topics as:

The Contractor shall also recommend potential improvements that can be initiated and/or implemented in the coming year. The first semi-annual review shall be conducted six months after contract award. The

Contractor and Government shall jointly prepare an agenda for each review meeting. The Contractor shall prepare and submit semi-annual planning review minutes and presentations for review and approval by the Government.

2.2.8. Subtask 8 - Support to EMSS Life Cycle Sustainment Plan. Upon the request of the Government, the contractor shall provide an Annual Input to EMSS Life Cycle Sustainment Plan (LCSP). This submission is delivered annually, and the date may vary from year to year. This submitted information will document the contractor’s network and service projections for the upcoming 10-year period but may exclude items of sensitivity. The contractor’s input to the EMSS LCSP will be limited to network elements and services the contractor is responsible to support at the EMSS Service Center and the contractor facility.

2.3. Task Area 3 - Equipment

2.3.1. Subtask 1 - General Requirements The contractor shall provide the list of equipment described in

Enclosure 1. The equipment will be purchased by EMSS customers via identified DOD Marketplace and the order forwarded to the contractor. The comments field in the Equipment List (Enclosure 1) contains additional instructions and guidance for a particular item. Enclosure 1 is subject to change over the life of the contract. Items may be added and removed as government requirements change. The cost for any item being added to this contract shall be determined via the Request for Proposal (RFP) process. The

Government does not guarantee any minimum ordering quantities unless otherwise specified in the RFP.

All items on the equipment list shall be included in the MSR.

The contractor shall deliver NSA-approved Type 1 Secure compatible ISM2. Each ISM2 shall be based on commercially available items to the maximum extent practical. The contractor shall work with the

NSA in accomplishing this effort.

2.3.2. Subtask 2 - ISM2 Production The contractor shall maintain a stock of two hundred (200) ISM2 for sale to the Government under this contract. The Government may order the manufacture of quantities of ISM2 in a production configuration for delivery to the Government. All delivered modules shall include appropriate security markings as approved by the Government. The contractor shall inform the

Government when ISM2 inventory falls below 200.

2.3.3. Subtask 3 - ISM2 Certification, Accreditation and Compliance The contractor shall work with the NSA and related Government accreditation agencies to ensure the Government User ISM2 is certified for each phase of Type 1 Secure operation. In support of certification and prior to delivery of any ISM2, the contractor shall document all accreditation activities and results for review and approval by the

FA2541-24-X-XXXX Page 7 of 19

Government. The contractor shall ensure that all compliance requirements for secure equipment are in good order throughout the life of this contract to include the ISM2 Production Tempest Test and Report.

2.3.4. Subtask 4 - Iridium Secure Modules (ISM) The contractor shall maintain a stock of two hundred

(200) Type 1 Secure Modules compatible with the Government User 9575A handset, which is procured under separate cover. The ISM2 is a COMSEC controlled item that must be certified and approved by

NSA. The Contractor shall notify the EMSS PMO COR when ISM inventory falls below 200.

The contractor shall be capable of storing and handling the ISM2, which is a COMSEC Controlled Item

(CCI), and its associated key material, which will include the handling and storage of keys at the

SECRET and TOP SECRET classification levels. The contractor requires a COMSEC account with the ability to procure keying material up to TOP SECRET.

2.3.5. Subtask 5 - User Spares and Accessories The contractor shall offer ISMs and other associated accessories for sale to the Government under this contract. These include such items as ISM fill cables.

The Government may also request the contractor to fabricate in configurations that are non-standard to its commercial offerings.

2.3.6. Subtask 6 - Delivery Schedule: CONUS/OCONUS All shipments must be “Freight on Board –

Destination” or “FOB-Destination.” Under normal conditions, the contractor shall ship equipment within three (3) calendar days after receipt of order (ARO), 14 days ARO otherwise. All deliveries will be via

Contract Line-Item Number (CLIN). To ensure mission requirements are filled, two additional early delivery CLINs are provided; 5-Day or Overnight. Unless requested by the customer, all deliveries will be priced at regular delivery schedule. Equipment shall be delivered as described in the order. In the event delivery times are not met, the Contractor shall notify the EMSS PMO COR and the customer with the reason and the plan of action to resolve the problem. The delay shall also be reported for the appropriate month in the MSR.

Inventory Levels

ISM2 200

ISM 200

Tamper Seals 200

CONUS

Category/CLIN Conditions

Standard Standard Processing will be shipped within 3 days ARO, 14 days ARO otherwise

5-Day 5-day Processing will be shipped within 5 days ARO

Overnight Overnight Processing will be shipped within 24-hours ARO

OCONUS

Category/CLIN Conditions

Standard Standard Processing will be shipped within 7 days ARO, 14 days ARO otherwise

5-Day 5-day Processing will be shipped within 5 days ARO

Overnight Overnight Processing will be shipped within 24-hours ARO

2.4. Task 4 - Warranties

FA2541-24-X-XXXX Page 8 of 19

All items should have a base one (1) standard year warranty. The standard warranty will be included in the price of the item or device. All warranties will begin their coverage period on the date that the contractor ships the item. The contractor shall ensure that the manufacturer’s standard and applicable extended warranties are made available to customers.

2.4.1. Subtask 1 - Extended Warranties. The Government reserves the right to purchase an extended warranty before expiration of the base warranty. The contractor shall offer an out-of-warranty repair option that provides for the correction and repair or replacement of defective items to ensure the full functionality of the equipment. All warranties will live beyond the life of the contract until the warranty’s end date.

2.4.2. Subtask 2 - Repair Services. The contractor shall provide factory repair services for all warrantied items delivered under this contract. Turn-around-times from receipt at the depot repair facility and receipt back at the Government using organization shall be no greater than 20 working days. The contractor shall provide status of equipment repairs and notify the EMSS PMO COR when repair turn-around-times exceed 20 working days. The contractor shall return all repaired equipment on a prepaid freight basis to the designated Government representative. The handling of the secure COMSEC components of the Government User Terminal shall require appropriate security measures. A summary of all repair services provided shall be included in the MSR.

It is expected that testing of the repaired devices will necessitate the use of keys at the SECRET and TOP

SECRET classification levels. The contractor shall require an IT-I level access for the repair of the ISM2 with six (6) billets.

2.5. Task Area 5 – Delivery Orders

The contractor must have a demonstrated capability for receiving and securely storing all information pertaining to EMSS orders as received through the Government’s prescribed ordering processes. The contractor’s records management system shall have an acceptable administrator hierarchy and/or controls to prevent unauthorized access from individuals or entities not permitted to support this contract. The contractor’s record management system shall be subjected to ad-hoc audits by the Government. This database shall be remitted to the Government in electronic form at the conclusion of this contract and no copies of this information are to be retained by the contractor. The contractor is forbidden to share any specific EMSS order record or general EMSS order trends with third parties not authorized by EMSS

(note: Iridium is a third party and is not authorized to receive this information from the Contractor).

The Contracting Office will provide a record of sale to the contractor upon completion of each transaction placed under this contract. This will ensure the records maintained by the contractor are consistent with the records maintained by the Contracting Office. However, the contractor will support a reliable process, defined in collaboration with the Contracting Office and EMSS PMO, that ensures the fulfillment and delivery of provisioned and activated devices (e.g., the Contractor shall deliver provisioned and activated devices when an order specifies for devices to be provisioned and activated).

2.5.1. Subtask 1 – Mission Partner Database. The contractor shall maintain a database of all EMSS secure voice users which shall include the user's agency and/or authorized affiliated entity, address. The

Contractor shall permit the EMSS Service Center Operators, the Contracting Office and EMSS PMO

"Read Only" access to this database during performance. Access shall be to an exported file containing only the user’s agency and/or authorized affiliated entity, address, and unique identifier number. This database shall be updated, at a minimum, weekly. The contractor shall provide this database, in electronic

FA2541-24-X-XXXX Page 9 of 19 format as an Excel spreadsheet, via email as requested, or file transfer service designated by the

Government, at the conclusion of this contract, or upon contract termination, to the KO and the COR.

2.5.2. Subtask 2 – Records Management Upon receipt of delivery orders, the Contractor shall enter applicable order information into its internal accounting system. The contractor shall notify the KO and the COR, regarding status of receipt of orders, shipment, or backorder of any device.

The contractor shall provide user data backup for maintaining and archiving required user information to protect against inadvertent loss of such data from system failures. This process shall include mechanisms to perform regular, periodic back up of user information and account databases. User invoicing will be the responsibility of the KO.

3.0 SERVICE SUMMARY

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items The performance threshold briefly describes the minimum acceptable levels of service required for each requirement and will be assessed on an “Acceptable” or “Unacceptable” basis.

These thresholds are critical to mission success.

Performance Objective

PWS

Para.

Performance

Threshold

Method of

Surveillance

Credentials;

Accreditation;

Certifications

1.D.1.a 100% Accuracy 100% Surveillance

Technology

Compliance

1.D.1.b 100% Accuracy 100% Surveillance

Professional quality deliverables provided in accordance with the delivery schedule.

1.D.1.c Performance occurs with no required re-performance or re-work at least 95% of the time.

Any re-performance or re-work that occurs is minor and is resolved in a satisfactory manner.

Random Sampling

Inventory Levels 1.D.1.e Maintained at standard IAW this PWS; ISM, ISM2 and

Tamper Proof Seals maintained at 200.

Periodic

Surveillance;

Random Sampling

4.0 DELIVERABLES

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the

Contractor. The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change but actual dates may need to be revised depending on actual contract start date.

DELIVERABLE PWS

PARA

DUE DATE DELIVERY

Kickoff Presentation, Agenda/

Draft Format

2.1 Agenda & draft format – 3 Days

After Contract (DAC) award;

presentation - 5

Email COR

Contractor Format

(CF)

FA2541-24-X-XXXX Page 10 of 19

Iridium VAR Certification 2.2 10 business days after contract award

(BDAC). 5 BD after any updates or changes (AUC)

Email COR CF

PMP 2.2 10 BDAC; 5 BD AUC Email COR CF

MSR 2.2 24 hrs after last day of the reporting period

Email COR CF

IPR 2.2 Agenda & draft format: 2 weeks prior; Final: 24 hrs prior IPR; Semi-annually; Annually

Email COR CF

PMR 2.2 5 BDs prior PMR Email COR CF

RMP; OPSEC Plan 2.2 90 DAC; w/in 14 days AUC Email COR CF

LCSP 2.2 Annually, w/in 30 days of Gov request

Email COR CF

Minutes 2.2 24 hrs after conferences/meetings Email COR CF

Quarterly Trends Analysis Report 2.2 5th BD of the next month; Quarterly Email COR CF

Order Records Database

15 BD prior to end of contract

All Certification documents: ISM

Certification and Accreditation

Approval Documentation

2.2 15 BACA; Annually

To be coordinated with NSA and USSF

ISM2 Production Tempest Test

Report

2.3 To be coordinated with NSA and USSF

within 30 BDAC

Inventory Report 2.3 5th BD of the month; Monthly Email COR CF

Mission Partner Database 2.5 5 BD of request during contract; 5 BD of the conclusion or termination of the contract.

SAAR (2875) Required prior individual system access

EPL 5.3 As Required

Trip/Expense & AAR 6.6 20 days prior/ w/in 1 week of trip Email COR CF

Phase-out Plan 6.2 90 days prior to POP expiration Email COR CF

Software Transition Plan (STrP) ANNLY, 60 days after LCSP request Email COR CF

QCP 6.2 Submitted at Kickoff meeting

MECSP 6.3 Submitted at Kickoff meeting

5.0 GOVERNMENT FURNISHED PROPERTY (EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES)

Equipment means a tangible item that is functionally complete for its intended purpose, durable, nonexpendable, and needed for the performance of a contract. Equipment is not intended for sale and does not ordinarily lose its identity or become a component part of another article when put into use.

Equipment does not include material, real property, special test equipment or special tooling.

Government-furnished property means property in the possession of, or directly acquired by, the

Government and subsequently furnished to the Contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, FA2541-24-X-XXXX Page 11 of 19 overhaul, or modification. Government-furnished property also includes contractor-acquired property when the contractor-acquired property is a deliverable under a cost contract when accepted by the

Government for continued use under the contract.

Government property means all property owned or leased by the Government. Government property includes both Government- furnished and Contractor-acquired property. Government property includes material, equipment, special tooling, special test equipment, and real property. Government property does not include intellectual property and software.

Loss of Government property means unintended, unforeseen, or accidental loss, damage or destruction to

Government property that reduces the Government’s expected economic benefits of the property. Loss of

Government property does not include purposeful destructive testing, obsolescence, normal wear and tear or manufacturing defects. Loss of Government property includes, but is not limited to-

▪ Items that cannot be found after a reasonable search,

▪ Theft,

▪ Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition; or

▪ Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair.

Material means property that may be consumed or expended during the performance of a contract, component parts of a higher assembly, or items that lose their individual identity through incorporation into an end item. Material does not include equipment, special tooling, special test equipment or real property.

Property means all tangible property, both real and personal.

Property Administrator means an authorized representative of the Contracting Officer appointed in accordance with agency procedures, responsible for administering the contract requirements and obligations relating to Government property in the possession of a Contractor.

Property records means the records created and maintained by the contractor in support of its stewardship responsibilities for the management of Government property.

Real property See Federal Management Regulation 102-71.20 (41 CFR 102-71.20).

Sensitive property means property potentially dangerous to the public safety or security if stolen, lost, or misplaced, or that shall be subject to exceptional physical security, protection, control, and accountability.

Examples include weapons, ammunition, explosives, controlled substances, radioactive materials, hazardous materials or wastes, or precious metals.

5.1 Government Furnished Property. The Government will furnish, upon request of the contractor, all necessary Government produced documents and technical background information necessary to perform the work described in this PWS. The Government will not, however, provide copies of commercial journals, magazines, textbooks, or other documents available from the private sector.

FA2541-24-X-XXXX Page 12 of 19

When the contractor is on-site, other furnishings such as telephone service, document reproduction, storage space, and computer resources including access to terminals, printers, software data, and internet may be provided upon request.

The EMSS Service Center will make sufficient SMEs available to review documentation, participate in

Technology Interchange Meetings (TIM), provide oversight, and participate in on-site Configuration

Change Order (CCO) execution.

5.2 Use of Government Owned/Leased Vehicle. In performance of this requirement, the contractor may be authorized the use of a Government Owned/Leased Vehicle, if determined to be in the best interest of the government. The CO, COR, or PM who directly administers the use of the vehicle may authorize its use, after ensuring all federal, state, and local regulatory requirements have been met. The usage may not result in any additional price to the subject contract.

5.3 Contractor-acquired Property. The contractor will not be required to acquire any property. For property to be delivered under the contract/TO that must be accounted for IAW DISAI 270-165-8, the following applies: The Contracting Office retains the right to request an EPL to comply with all requirements of DFARS 252.211-7003, Item Identification and Valuation, when applicable. See DARS

252.211-9000, Requirement to Submit an Electronic Product List for additional information.

6. GENERAL INFORMATION

6.1. Scheduling.

6.1.1 Duty Hours. The Contractor shall have access to Government facility five days per week, Monday through Friday, eight hours a day, except when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings, unless otherwise approved. Contractor personnel are expected to conform to customer agency normal operating hours; however, the Contractor may be required access to Government facility outside of duty hours based on the customer agency’s needs. As a baseline, Contractor personnel shall work 8 hours per day, 40 hours per week. Compensatory time arrangements are permissible for temporary spikes in worktime;

but overtime pay is prohibited without COR and CO approval. Federal Holidays shall be observed in accordance with Office of Personnel Management policy.

6.1.2 Core Duty Hours and Base Shutdown/Inclement Weather. Core duty hours are 0800 - 1600, Monday through Friday (excluding federal holidays). The Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules whether due to a base closure or inclement weather. The website for guidance regarding status of performance for work to be performed in the National Capital Region (NCR) is http://www.opm.gov/status/.

6.2. Phase-Out Plan

6.2.1. The Contractor shall provide a Phase-out Plan NLT than ninety (90) calendar days prior to expiration of the Period of Performance contract. The plan shall facilitate the accomplishment of a seamless transition from the incumbent to and incoming Contractor (if applicable). In addition, the

Contractor will continue to accomplish all tasks as outlined in the contract during this period. The

Contractor shall identify how it will coordinate with the incoming Contractor and Government personnel to transfer knowledge regarding the following:

http://www.opm.gov/status/

FA2541-24-X-XXXX Page 13 of 19

• Project management processes

• Points of contact

• Location of technical and project management documentation

• Status of ongoing technical initiatives

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

• Coordination of IT related programs, issues

6.2.2 The Contractor shall also establish and maintain effective communication with the incoming

Contractor and Government personnel for the period of the transition via weekly status meetings.

6.2.3. Current employees under this contract may be interviewed for possible employment by a succeeding Contractor; however, the Contractor will have the first right of refusal. The current

Contractor will release any employee who chooses to be employed by a succeeding Contractor. The current Contract will assist by orienting assigned employees of the succeeding Contractor during the last thirty (30) days of the period of this contract, per direction of the CO. The Government shall make available to such employees existing Government Furnished Property listed under Section V of this PWS.

Items that are not accountable, such as desks, chairs, telephones, and other normal office equipment and office supplies during the orientation period, will only be transferred to the incoming Contractor if items were solely purchased by the current Contractor’s company.

6.2.4. The Software Transition Plan (STrP). The STrP identifies the hardware, software, and other resources needed for life cycle support of deliverable software and describes the developer's plans for transitioning deliverable items to the support agency. The STrP shall be developed when software support concept calls for transition of responsibility from the developer to the Government or a separate support agency. The STrP shall be submitted sixty (60) after the Governments Initial request for LCSP input.

6.3. Quality Control.

6.3.1. Quality Assurance. The Government shall rely on the Contractors’ existing quality assurance system as the method to ensure that the requirements of the contract and performance thresholds are met;

however, the Government reserves the right to monitor and evaluate the quality of services provided and compliance with the contract terms and conditions at any time.

6.3.2. Quality Control Plan (QCP). The Contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations, and best commercial practices. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services with special emphasis placed on those services listed in this PWS. The Contractor’s quality control program is how it assures itself that the work complies with the requirement of the contract.

6.4. Emergency Operations/Mission Essential Personnel.

6.4.1. Contractor Services During Crisis. IAW DFARs 252.237-7023, Continuation of Essential

Contractor Services (d)(1) “Notwithstanding any other clause of this contract, the contractor shall be responsible to perform those services identified as essential contractor services during crisis situations (as directed by the Contracting Officer), in accordance with its Mission-Essential Contractor Services Plan.”

FA2541-24-X-XXXX Page 14 of 19

(MECSP) All services in this PWS have been defined or designated as essential and shall continue contractor services during crisis.

6.4.2 Continuation of Essential Contractor Services. The Contractor shall maintain and update its plan as necessary. The Contractor shall provide all plan updates to the Contracting Officer for approval. (3)

As directed by the Contracting Officer, the Contractor shall participate in training events, exercises, and drills associated with Government efforts to test the effectiveness of continuity of operations procedures and practices.

6.5. Security Instructions (See DD254 for additional security guidelines.)

6.5.1. Physical Security. The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each workday, all Government facilities, equipment, and materials shall be secured by a Government POC. Contractors are not allowed to secure Government facilities, equipment, and materials.

6.5.2. Access Control. The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced, or used by unauthorized persons. Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The

Contractor is not authorized to record lock combinations without written approval by the Government

COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

6.5.3. Pass and Identification Items. The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.

6.5.4. Retrieving Identification Media. The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.

6.5.5. Traffic Laws. The Contractor and its employees shall comply with base traffic regulations.

6.5.6. Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on site or any other military facility.

6.5.7. Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account. Access shall be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances. If it is determined the Contractor is required to access COMSEC information, the necessary training information and courses shall be provided by the COR. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material.

6.5.8. Contractor Identification. All Contractor personnel shall wear the Government always issued

Common Access Card when away from their immediate work area to distinguish themselves from

Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, Contractor personnel shall identify themselves as a contractor to

FA2541-24-X-XXXX Page 15 of 19 avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractors occupying collocated space with their government program customer should identify their workspace area with their name and company affiliation or as a minimum “Contractor” after name.

6.5.9. Drug, Tobacco, and Alcohol Use Policy. The consumption of alcoholic beverages or illegal drugs by contractor personnel, while on duty, is strictly forbidden. Contractor shall immediately remove any employee who is under the influence of alcohol or drugs.

6.6. Travel

6.6.1. Local Travel. Local travel to attend meetings or events may be required at no cost to the

Government. Travel within the National Capital Region commuting vicinity is considered a cost of doing business and shall not be separately reimbursed.

6.6.2. CONUS Travel: Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 10 business days prior to trip.

6.6.3. OCONUS Travel. Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 20 business days prior to trip. Theater Business Clearances shall be obtained, as necessary, prior to travel.

6.6.4. Further guidance for Contractor travel can be found at https://www.defensetravel.dod.mil/site/faqctr.cfm.

6.6.5. Trip Reports. Following each trip, the Contractor shall prepare and deliver Trip/After Action

Reports to the COR IAW AFH 33-337. The trip report shall be completed in accordance with OFFICE

(SAF/# or AF/#) guidance.

6.7. Surge.

The Government may require surge support during the base or any option period, and surge modifications will be within the scope of the contract and provide increased support for the defined task areas of this

PWS. Surge Support over the life of the contract will not exceed 10% of the contractor’s total quoted price for the base and all the option periods, excluding any six-month extension of services, pursuant to

FAR 52.217-8. Anything above 10% will require Government’s approval. All surge support shall occur during the specified hours and locations indicated in the performance work statement (unless other tasks are agreed to by both parties), and exercise flexibility on an as-needed basis for work defined in all tasks.

6.8. Supply Chain Risk Management (SCRM)

This contract and its associated delivery/task orders are subject to the Federal SCRM policies and regulations including the Defense Federal Acquisition Regulation Supplement (DFARS) 252.239-7017

Notice of Supply Chain Risk, DFARS 252.239-7018 Supply Chain Risk, DoD Instruction 5200.44

Protection of Mission Critical Functions to Achieve Trusted Systems and Networks, Section 806 of theFY2011 NDAA Requirements for Information Relating to Supply Chain Risk, and internal DISA

SCRM Processes and Procedures.

https://www.defensetravel.dod.mil/site/faqctr.cfm

FA2541-24-X-XXXX Page 16 of 19

The contractor shall submit a SCRM plan as part of its technical proposal that describes how the contractor will reduce and mitigate Supply Chain Risk using the security controls outlined below (further described in CNSSI 1253, Appendix D and NIST SP 800-53), as applicable to your contract.

Control# HW SW Srvc

SA-12 Supply Chain Protection (SCP) X X X SA-12(1) SCP / Acquisition Strategies / Tools / Methods X X X SA-12(2) SCP / Supplier Reviews X X X SA-12(5) SCP / Limitation of Harm X X X SA-12(7) SCP Assessments Prior to Selection / Acceptance/ Update X X X SA-12(8) SCP / Use of All-Source Intelligence X X X SA-12(9) SCP / Operations Security X X X SA-12(10) SCP / Validate as Genuine and Not Altered X X X SA-12(11) SCP / Penetration Testing / Analysis of Elements, Processes, and Actors X X X SA-12(12) SCP / Inter-Organizational System Components X X X SA-12(13) SCP / Critical Information System Components X X X SA-12(14) SCP / Identity and Traceability X X X SA-12(15) SCP / Process to Address Weaknesses or Deficiencies X X X IR-4(10) Incident Handling / Supply Chain Coordination X X X IR-6(3) SCP / Incident Reporting / Coordination with Supply Chain X X X SA-11 Developer Security Testing and Evaluation X X X SA-14 Criticality Analysis X X X SA-15 Development Process, Standards, and Tools X X X SI-7 Software, Firmware, and Information Integrity X X X CM-4 Security Impact X X X PM-16 Threat Awareness Program X X X

The contractor shall provide an updated SCRM Plan to the COR and Program Manager within five (5) business days whenever there is a change that affects one or more security controls as described in the

Committee on National Security Systems Instructions (CNSSI) 1253 Appendix D (companion publication to National Institute of Standards and Technology (NIST) Special Publication (SP)). At a minimum, the following events will require a SCRM Update: changes in company ownership, changes in senior company leadership, supplier changes, subcontractor changes, and ICT supply chain compromises.

FA2541-24-X-XXXX Page 17 of 19

APPENDIX

DEFINITIONS, ABBREVIATIONS, AND ACRONYMS (as they pertain to this PWS)

Contracting Officer (KO). The duly appointed Government agent authorized to award or administer contracts. The contracting officer is the only person authorized to contractually obligate the Government.

Program Manager (PM). Government civilian responsible for developing accurate government requirements and managing life-cycle activities to ensure that intended outcomes are achieved which are most advantageous to the government.

Project Manager. Contractor employee responsible for managing time, resources, money, and project scope as it pertains to this PWS.

Defective Service. A service output that does not meet the standard of performance specified in the contract for that service.

Government Furnished Property (GFP). Facilities, equipment, tools, supplies, parts, or any other items furnished for the concessionaire's use by the Government. A full list, if applicable, is in Section V.

Performance Threshold. The minimum performance level of a performance objective required by the

Government.

ACRONYMS

ANC - Legacy Access Network Controller

ASIs - Authorized Service Interruptions

EMSS - Enhanced Mobile Satellite Services

CAT - Category

CCB - Configuration Control Board

CCO - Configuration Change Order

CJSCI - Chairman of the Joint Chiefs of Staff Instruction

CMP - Configuration Management Plan

COI - Conflicts of Interest

CONUS - Continental United States

COR - Contracting Officer’s Representative

COTS - Commercial-off-the-shelf

CPARS - Contractor Performance Assessment Report

DIA - Defense Intelligence Agency

DISN - Defense Information systems Network

DGS - Defense Ground Station

DOD - Department of Defense

DODAAC - Department of Defense Activity Address Code

DSS - Defense Security Service

DTCS - Distributed Tactical Communication System

DTCS/GS - Distributed Tactical Communication System-Global Services

ESBD - Enhanced Short Burst Data

ESSG - Network Defense Solutions Steering Group

FSB - Facility Clearance Branch

FA2541-24-X-XXXX Page 18 of 19

FCL - Top Secret Facility Clearance

FLT - Feeder Link Terminals

FOUO - For Official Use Only

FRU - Field Replaceable Unit

FSO - Field Security Operations

HBSS - Host Based Security System

HPA - High Power Amplifiers

GBC - Geographic…