Theater Deployable Communications Contractor Logisitics Support PWS.pdf

PDF 661 KB Posted

Attached to
Request for Information - Theater Deployable Communications Contractor Logistics Support
Solicitation number
Not on record
Issued by

About this file

This document is a Performance Work Statement (PWS) for the Theater Deployable Communications (TDC) Contractor Logistics Support (CLS) contract. The overall objective is to obtain comprehensive sustainment and support services for the United States Air Force (USAF) TDC equipment to ensure reliable operations. Key requirements include:

The contractor shall provide global sustainment services such as depot-level logistical support, systems configuration, technical and engineering support, help desk functions, equipment repair, warranty management, and program management. The contractor must maintain an inventory management system, process purchase requests, and manage shipments and warehousing. The contractor is responsible for obsolescence management and diminishing manufacturing sources over the contract period. Key performance thresholds are defined for system availability, mean time to restore function, and inventory accuracy. The contract includes a 60-day transition period and requires the contractor to develop and execute a detailed Transition Plan.

The related federal contract opportunity is a Request for Information (RFI) from the USAF Air Force Lifecycle Management Center seeking market information to support the procurement of TDC Contractor Logistics Support.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ATTACHMENT 1

Performance Work Statement (PWS) for Theater Deployable Communications (TDC)

Contractor Logistic Support (CLS)

8 Mar 2024

Prepared by:

Base Infrastructure Branch (AFLCMC/HNIB) C3I Infrastructure Division (AFLCMC/HNI)

AF Life Cycle Management Center (AFLCMC) Hanscom AFB, MA

Distribution Statement A: Approved for public release: distribution is unlimited..

DOCUMENT CHANGE RECORD

This table is used to record revisions to this document. For each revision, record the Date, Editor, document Version (same as version number on the cover), and a summary of changes.

Version Date Summary of Changes Editor

Performance Work Statement (PWS) -iii

CLS PWS Table of Contents

1. BACKGROUND

2. SCOPE

3. Progam Management

3.1. Personnel Management

3.1.1. Work Day Period of Performance

3.1.2. Travel

3.2. Security

3.2.1. OPSEC

3.2.2. Security Clearances

3.2.3. DoD Identification / Common Access Cards (CAC)

3.2.4. Foreign Ownership, Control, or Influence (FOCI)

3.3. Financial Management

3.3.1. Other Direct Costs (ODC)

3.4. Meetings and Communication

3.4.1. Program Management Review Meetings

3.4.2. Periodic Meetings

3.5. Data Management

3.6. Configuration management

3.6.1. Equipment or Software Updates/Enhancements

3.7. Logistics Management

3.7.1. Defense Property Accounting System (DPAS)

3.7.2. Procurements

3.7.2.1. Department of Defense (DoD) Item Unique Item Identification (IUID)

3.7.2.2. Procurement Pre-Approval Requirements

3.7.2.3. Refurbished Equipment

3.7.3. Shipments

3.7.3.1. System availability-

3.7.3.2. Mean Time To Restore Function (MTTRF)

3.7.3.3. Packaging, Handling, Storage and Transportation (PHS&T)

3.7.3.4. International Standards for Phytosanitary Measures (ISPM NO. 15) Requirements

3.7.3.5. Electrostatic Material (When Applicable)

3.7.3.6. Hazardous Materials (When Applicable)

3.7.3.7. Green Procurement Program (GPP)

3.7.4. OEM Product Support

iv

3.7.5. Warranty Management

3.7.6. OEM Training

3.7.7. Help Desk Support

3.7.8. Program Protection

3.7.8.1. Program Protection Plan (PPP)

3.7.8.2. Program Protection Implementation Plan (PPIP)

3.7.8.3. Suspected or Confirmed Counterfeit Products Reporting Procedures

3.7.8.3.1. Contractor Notification Procedures:

3.7.8.3.2. Subcontractor Notification Procedures:

3.8. Government Furnished PROPERTY (GFP)

3.8.1. Warehouse GFP Inventory

4. Obsolescence Risk Management and Diminishing Manufacturing Sources and Materiel Shortages (DMSMS) Program

4.1. DMSMS Responsibilities

4.2. Ozone Depleting Substances (ODS)

5. Warehouse Management and Operations

5.1. IUID/inventory Requirement

5.2. Safety Requirements

6. Contract Transition

6.1. Transition Phase In

6.2. Transition Plan

6.3. Transition of Government Furnished Property (GFP)

6.4. Transition Phase-In Status Reporting

6.5. Transition Phase-Out

7. Performance assesment

8. Service Delivery Summary

Acronym List v

This Page Intentionally Left Blank

For

Enterprise IT & Cyber Infrastructure Division (AFLCMC/HNIB)

TDC CLS

1. BACKGROUND

The Theater Deployable Communications (TDC) equipment is a Commercial Off the shelf (COTS) and Government off the shelf (GOTS) based system that provide telecommunications, network and satellite communications in ruggedized deployable packages.

TDC is a modular, scalable family of communications packages (voice, data, intra-site transmission, etc.), satellite communications (SATCOM) terminals, and network management packages tailored to meet various Air Force mission needs.

The TDC packages consist of Integrated Communications Access Packages (ICAP), SATCOM Terminals, and the Network Control Center – Deployed (NCC-D). This equipment is combined to provide voice and data networking services at deployed locations.

2. SCOPE

The overall objective of the requirement detailed in this document is to obtain contractor comprehensive sustainment and support services for the United States Air Force (USAF) TDC equipment and ensure reliable operations for all TDC systems (identified in TDC Equipment Government Furnished Property (GFP)) covered under this contract.

The contractor shall provide comprehensive contractor support in providing global sustainment services for the USAF TDC Program. These services include, but are not limited, to depot level logistical support in equipment sourcing, replacement, and inventory, systems configuration, including technical and engineering support to sites requesting TDC assistance, and program management.

The contractor shall provide TDC equipment support consisting of help desk functions, failure diagnostics, equipment functional testing, equipment repair, material purchasing, spares analysis, shipping and receiving services, inventory management, equipment warranty management, costs management and troubleshooting techniques.

3. PROGAM MANAGEMENT

The contractor shall provide management covering the performance of all objectives covered in this document during the entire contract period of performance.

3.1. PERSONNEL MANAGEMENT

The contractor shall provide project oversight/management as necessary to track, manage, and report on the cost, schedule, and performance status of this effort. The contractor shall appoint a Program Manager (PM) with sufficient corporate authority to direct, execute and control all elements of this contract.

3.1.1. Work Day Period of Performance

Services provided shall be on a Work Day Period of Performance (WDPP) Monday through Friday, excluding federal holidays. Contractor personnel shall be required to support the user during the WDPP.

In specific circumstances, the contractor may be required to provide support during extended hours to perform mission essential tasks. Additionally, the contractor may be required to perform Outside of the WDPP (OWDPP) to support exercises or crisis situations as directed and approved by USAF the Procurement Contracting Officer (PCO) Core hours for contractor support of TDC requirements shall be from 0700 to 1700 hours local time zone, Monday through Friday, excluding federal holidays. Support shall be provided during core hours.

3.1.2. Travel

Travel for this effort, shall be cost reimbursable and shall comply with FAR 31.205-46.

The Contractor shall notify the Government Program Office at least five (5) days in advance of any travel, and ensure the request is approved in writing prior to travel.

3.2. SECURITY

The Contractor shall comply with all requirements of this PWS in accordance with the security provisions established in the Cyberspace Operations Security Classification Guide (included as Government Furnished Information (GFI)) and the DD Form 254, DoD Contract Security Classification Specification. The Contractor shall flow down the security requirments to subcontractors as applicable.

3.2.1. OPSEC

The contractor shall apply Operations Security (OPSEC) in their management of the TDC CLS program IAW DOD Directive 5205.02E and AFI 10-701 Operations Security, and the program’s Critical Information List. The Contractor shall provide OPSEC and Cybersecurity (CS) training as part of its overall training requirements for protecting controlled unclassified information (CUI), activities, and operations during the course of the contract. The Contractor shall flow down all OPSEC requirements to subcontractors that handle Critical Information (CI).

3.2.2. Security Clearances

The Contractor shall ensure all personnel on this contract have a valid SECRET security clearance.

Personnel Security:

The Contractor shall ensure applicable Contractor personnel have security clearances at the appropriate level for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and/or CUI and classified items.

3.2.3. DoD Identification / Common Access Cards (CAC)

Contractor personnel shall be required to follow facility security procedures and policies including protection of classified information or material (if required), facility security, and attending required security/safety briefings provided by the contractor. Contractor shall provide and update, as required, a listing by name of all personnel hired to perform duties under this contract. The contractor shall, through sponsorship by the Government, get a Common Access Card (CAC) for employees requiring access to Government databases. Contractor shall purchase required CAC readers. Government shall supply necessary software for CAC readers.

Contractor shall turn in any CACs to the Government when an employee terminates his/her employment with the company. All contractor personnel shall be briefed on an annual basis on facility and equipment security along with reporting procedures. (CDRL A004)

The Contractor Shall immediately report a lost or stolen CAC as directed by local Governmnet policy. The Contractor shall notiy the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list withn 5 busnisses days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require access. The Contractor shall return an expired CAC within five business days after expiration date. The Contractor shall return any and all CACs withing five business days after the completion/termination of the contract as directed by Government policy.

The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical accessto facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a listof contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Contractor Verification System (CVS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)]

The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy. The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return all CACs within five business days after completion/termination of the contract as directed by local Government policy.

3.2.4. Foreign Ownership, Control, or Influence (FOCI)

Foreign participation is excluded at the Prime and Subcontractor level, unless authorized through a current approved National Interest Determination.

The Contractor shall disclose any FOCI for the purpose of initial or continued facility clearance eligibility. A Standard Form 328 Certificate Pertaining to Foreign Interests shall be submitted to the Government cognizant security office specified in DD Form 254.

3.2.5. Secuirty Incidents and Violations

The Contrtactor shall notify the Government Contracting Activity and the Government Secuirty Manager within 48 hours of any incident involving the actual or suspected compromise/loss of classified information to enable the Government to conduct immediate assesments of potential impact pending formal inquiry/investigation. Actual or suspected compromise of Covered Defense Infromation will be reported IAW DFARS Clause 252.204-7012.

3.2.6. Controlled Unclasisfied Information (CUI)

The contractor shall comply with DoDI 5200.48_DAFI16-1403, Controlled Unclassified Information, DoDM 5200.01, Vol 1_AFMAN16-1404, Vol 1, Air Force Information Security Program, and DoDM 5400.07_AFMAN33-302 Air Force Manual, DoD Freedom of Information Act (FOIA) Program. The contractor shall monitor CUI aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information.

The Contractor shall distribute controlled unclassified information IAW DoD Instruction 3200.14, Principles and Operational Parameters of the DoD Scientific and Technical Information Program, and DoD Instruction 2040.02, International Transfer of Technology, Articles, and Services. The Contractor shall properly mark all such documents IAW DoD Instruction 5230.24, Distribution Statements on Technical Documents. Technical documents not subject to distribution are defined in DoD Instruction 5230.24, DoD Directive 5230.25, and DoD Manual 5010.12-M, Procedures for the Acquisition and Management of Technical Data.

Protection of Information Controlled Unclassified Information (CUI) [Required if Contractor requires access to CUI] Controlled Unclassified Information is any information that law, regulation, or government wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under Executive Order 13526, Classified National Security Information, December 29, 2009, or any predecessor or successor order, or the Atomic Energy Act of 1954, as amended.

The National Archives and Records Administration (NARA) CUI Registry (http://www.archives.gov/cui/registry/category-list.html) identifies approved CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI.

The contractor shall comply with DoDI 5200.48_DAFI16-1403, Controlled Unclassified Information, and DAFMAN 16-1404 Vol 1-3 Air Force Information Security Program. The contractor will consult the applicable security classification guide to monitor CUI aggregation for potentially generating classified information by compilation.

The Contractor shall comply with DoDM 5400.07/Air Force Manual 33‑302, DoD Freedom of Information Act (FOIA) Program, requirements.

Protection of CUI and unclassified DoD information not approved for public release on non-DoD Information Systems will be protected IAW DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information. Unless specific categories of CUI require more stringent controls, non-DoD Information Systems must be protected using the guidelines set forth in NIST Special Publication 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations.

Covered Defense Information [Required for all solicitations and contracts, including solicitations and contracts using FAR part 12 procedures for the acquisition of commercial items]

The Contractor shall comply with DFARS 252.204-7012 Safeguard Covered Defense Information and Cyber Incident Reporting (Dec 2019) This subpart applies to contracts and subcontracts requiring contractors and subcontractors to safeguard covered defense information that resides in or transits through covered contractor information systems by applying specified network security controls. It also requires reporting of cyber incidents. The subpart does not abrogate any existing contractor physical, personnel, or general administrative security operations governing the protection of unclassified DoD information, nor does it impact requirements of the National Industrial Security Program.

3.3. FINANCIAL MANAGEMENT

The contractor shall provide all financial management support for the following areas: all Repair Actions, Purchase Orders, Invoice Expenditures, and Government Invoicing.

The Contractor shall track each cost to ensure that the funded ceiling is not exceeded. In Accordance With (IAW) FAR 52.232-20, the Contractor shall notify the PCO, via a contracts letter, when the limitation of cost threshold has been met (i.e., a specific Cost CLIN is expected to reach a 75% expenditure status within the next 60 days). The Contractor shall include an estimated date when the CLIN will reach 100% expenditure. The Contractor shall provide this financial summary for the current PoP CLINs in the Monthly Status Report. (CDRL A003)

3.3.1. Other Direct Costs (ODC)

The Contractor shall use the appropriate ODC CLIN for all procurements and shipments within this contract.

The Contractor shall not exceed the ODC funding limits set by the Government in the Contract Line Item Number (CLIN) structure.

The contractor shall create an electronic Maintenance Service Report for every failed piece of equipment and/or every support action that occurs, in which Government funds must be expended.

All Material Support Requests (MSR) for repairs/spares purchase of equipment shall be turned into the Contracting Officer Representative (COR) for approval. Once MSRs are approved by the COR, the contractor shall process repair/purchase procurement actions within five (5) duty days.

These records shall be available for Government access, review and approval on a web-enabled information management system. (CDRL A008)

3.4. MEETINGS AND COMMUNICATION

The Contractor shall initiate, organize, and participate in meetings, to include but not limited to the meetings listed below, whenever necessary to accomplish the tasks of this Contract or in support of reporting requirements of the Government. The Contractor shall keep the PMO informed of relevant plans or changes, disseminate knowledge of tasks to be done, and provide situational awareness. All action items taken at meetings shall be tracked by the Contractor and documented in the Monthly Report. (CDRL A003)

3.4.1. Program Management Review Meetings

The contractor shall hold a Post Award kick–off meeting for the contract. Program Management Reviews (PMRs) shall be held quarterly unless deemed not required by QAP/COR during the basic year of the contract and in each of the follow- on years exercised.

Reviews shall provide overall project status and shall be presented at a date and time coordinated with and approved by the Government. The Contractor shall submit briefing slides/agenda to the Government in accordance with the CDRL in advance of the event. The contractor shall record and distribute meeting minutes for all official meetings / telecons which pertain to the performance of this contract. (CDRL A001) (CDRL A002)

3.4.2. Periodic Meetings

The QAP/COR may perform audits, with the support of the contractor, of randomly selected equipment based on the inventory listing review of the incident Report (IR) for accuracy and review of the MSR log for accuracy. Meeting minutes shall be provided by the Contractor.

(CDRL A002) (CDRL A007)

3.5. DATA MANAGEMENT

The Contractor shall provide an organized, online Integrated Digital Environment (IDE) to host all data generated or otherwise relevant in the performance of the contract. Examples of these would include but not be limited to; reports, technical studies and analysis, lessons learned, management plans, policies, processes, procedures, meeting minutes and attendee lists, trip reports, conference agendas, PMR slides, billing information, technical documentation, control plan (i.e. corrosion control), preventative maintenance inspection procedures, and all other program supporting documentation. The Government will not mandate the format of this information.

The Contractor shall ensure data hosted on the IDE is free of computer viruses and malware. The Contractor shall provide key personnel from the PMO with unrestricted read/download 24/7/365 electronic access utilizing unique user names and passwords in accordance with AFI 33-200 and AFSSI 8520 and the capability to download this data from the repository throughout the contract period of performance. The Contractor shall inform the PMO of all scheduled maintenance outages. The Contractor shall provide Data Accession Lists (DAL) to Government PMO personnel, listing the contents of the IDE for this contract. (CDRL A013)

The Contractor shall provide all Contract Data Requirement List (CDRL) data IAW the PWS, CDRL Exhibits, and referenced GFI. The Contractor shall manage the control, status accounting, and distribution of CDRL items. The Contractor shall submit all CDRL deliverables IAW CDRL Exhibit DD Form 1423s.

The contractor shall use a report format, which is approved by the Government, for all equipment outages (hardware and software) accountable to this contract. The data maintained in the report of incident reports (IR LOG) shall be updated daily as changes occur. Data format must be standardized, and consistent. An archive of closed actions shall be maintained. The contractor shall be responsible for maintaining accurate information in the database. (CDRL A006)

3.6. CONFIGURATION MANAGEMENT

Contractor shall notify the COR of any configuration changes made to TDC equipment by the field units prior to accomplishing any repair actions. Contractor shall provide Configuration Management Plan NLT 30 business days After Receipt of Contract. Prior to any implementation, the Government must concur with any proposed changes or updates to the systems that impact the Government. Where specifically required elsewhere in this contract, regular audits and updates of the specifically designated systems will be established between the Government and the contractor to ensure the systems are kept fully operational. Government concurrence shall be provided by the

PCO. (CDRL A005)

3.6.1. Equipment or Software Updates/Enhancements

In accordance with established Government performance parameters, the contractor shall recommend updates/enhancements to equipment that has been identified as critical to extend its life or to ensure more reliable operations. This notification shall include evaluations performed on equipment that may no longer be supportable by either repair or replacement. Configuration approval for any modifications and purchase of equipment shall be obtained from the designated PCO in accordance with procedures established in this contract.

3.7. LOGISTICS MANAGEMENT

The contractor shall provide all logistic support functions to maintain equipment and software accountable to this contract in a centralized location. The equipment shall be kept in good working condition and serviceable. The equipment shall meet all requirements as necessary to be fielded as operational replacements for the user. The contractor shall perform Preventive Maintenance Inspections (PMI’s) and base the frequency on OEM’s recommendations and the Government’s operational requirements. The contractor shall acquire and manage all parts and materials necessary to support the actions required under this contract. This includes, but is not limited to, the following types of support: (CDRL A009)

• Inventory management

• Stock, store and issue functions

• Shipping and receiving functions

• Help Desk functions, troubleshooting, diagnosis and equipment repairs

• Ordering, tracking and expediting purchases

• Track failure rates, repair times, spares analysis and trend analysis

• OEM warranty management

The Contractor shall maintain visibility and accountability of Government assets provided as Government Furnished Property (GFP) or purchased by the Contractor to be used in the performance of this contract. The Contractor shall ship, track, manage and report on these assets as required. The Contractor shall include in the Monthly Status Report details on the failure rates, repair times, spares analysis and trend analysis of assets requiring repair. The Contractor shall make all reasonable attempts to minimize costs associated with asset control and shipment, while meeting obligations to maintain the TDC system IAW this contract. (CDRL A003)

Contractor shall be responsible for all inventory required for the performance of the contract as identified in TDC Equipment GFP, TDC GFE Tools and Computer Equipment listed with the RFP.

Trend / failure rate analysis, number of failures per number of systems in total inventory when failure rate is greater than 5% in a reporting period. reported Monthly/quarterly/yearly.

In addition to >5% in reporting period, provide top 5 failure rates in reporting period regardless of

%. (CDRL A011)

3.7.1. Defense Property Accounting System (DPAS)

Contractor shall act as the inventory control point (source of supply) and must report all transactions according to AFI 23-101. The AF has selected the Defense Property Accountability System (DPAS) as the Accountable Property System of Record (APSR) for this AF initiative allowing the AF to financially account for this materiel and meet the DoD Financial Improvement and Audit Readiness (FIAR) requirements.

Contractor shall provide property accountability / control of contractor managed and possessed Air Force owned property (inclusive of materiel and equipment) through implementation of standard and integrated AF logistics and contractor processes (from receipt / acceptance through issue / disposition) IAW DoDM 4140.01, DoDI 5000.64.

Contractor shall establish and maintain accountable inventory records for government furnished property (GFP), within a government accountable property system of record (APSR), that reflects current quantity, status, location, condition and authorizing contract while establishing an audit trail to update and track end-to-end logistics and financial transactions.

3.7.2. Procurements

The contractor shall purchase materials, in direct support of the equipment covered under this contract, by obtaining prior approval from the PCO/COR via a Material Support Request (MSR). Materials necessary to support this contract include the following:

a. Direct repair materials - Materials necessary to perform repairs to maintain system operations and functionality.

b. Operational support materials - Materials necessary to support mission requirements.

These materials may include, but are not limited to, bench stock, consumable-type materials, replacement spares, PMO ITF equipment, Field Change Orders (FCOs) and USAF Time Compliance Technical Orders (TCTOs).

c. Enhancement materials - Materials/components deemed necessary to support systems in the case of vanishing vendor analysis, loss of source of repair capability, or items that provide additional approved capability in support of the Contractor Logistic Support (CLS) facility.

d. Title to Replacement Hardware: Title, license, or any affected “rights to use” (RTU) to any replacement hardware provided by the contractor shall pass to the government upon site acceptance of the hardware.

Any items purchased during the Period of Performance (POP) shall be added/updated to the applicable baseline items listed in TDC Equipment GFP, TDC GFE Tools and Computer Equipment GFE and shall be identified as Government owned.

For any items purchase during this contract the contractor shall ensure the manufacturer has provided an Item Unique Identification (IUID) label to the equipment as required by Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.211-7003. Contractor shall maintain IUID labels on all equipment and containers having IUID labels that arrive at the warehouse.

3.7.2.1. Department of Defense (DoD) Item Unique Item Identification (IUID)

The Contractor shall provide DoD IUID Item Unique Identification (IUID) for:

• Delivered items that are greater than $5,000 (Government’s Unit Acquisition Cost)

• Delivered items that are less than $5,000 (Government’s Unit Acquisition Cost) that is serialized with the exception of the equipment types listed in Table 1, Equipment Exempt from IUID

Voice Over Internet Protocol (VOIP) Phones Plain Old Telephone Systems (POTS) Phones Server internal Interface Cards [i.e. Network Interface cards (NIC), Serial Interface (SI)] Disk Drives Consumables (e.g., rack Uninterruptable Power Supply (UPS) batteries) Power Supplies Racks and Accessories Cables Antennas Rack mounted Power Distribution Units (PDUs) Tools Test Equipment Monitors Keyboards Fans Power Over Ethernet Injectors (POEs) Signal Converters

Table 1.0 – Equipment Exempt from IUID

The Contractor shall ensure that the IUID be accomplished by the Original Equipment Manufacturer (OEM) marking each qualifying item with a permanent 2-dimensional Data Matrix EC200 symbol. The Item Unique Identification (IUID) label in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.211-7008 and the requirements contained in the most recent version of Department of Defense Standard Practice, Identification Marking of U. S. Military Property, MIL-STD-130N.

The symbol shall be square and can range from 0.25 inch per side, up to 1.5 inches per side which is assembled and shall comply with the syntax formats of International Organization for Standardization/International Electro technical Commission (ISO/IEC) 15434, Transfer Syntax for High Capacity Automatic Data Capture Media. The data matrix shall be encoded with the OEM Commercial And Government Entity (CAGE) code, part number, and the item's serial number, in that order. The marking shall also include the same information in human readable format.

DoD requires that the concatenated IUID not exceed 50 characters in length. DoD also prohibits the use of dashes and slashes as separators between component parts in a single data element that is formed from component parts. The label shall be applied to the equipment prior to shipment.

EXAMPLE:

OEM CAGE 1U2R7

Orig. Part No. 1P1234

Serial No. S786950

If the Contractor acquires by subcontract, any item(s) for which unique item identification is required, the Contractor shall include the above paragraph in the applicable subcontract(s).

3.7.2.2. Procurement Pre-Approval Requirements

The Contractor shall obtain pre-approval per Section 3.7.1.

3.7.2.3. Refurbished Equipment

Should the Contractor find it necessary to provide refurbished equipment for hardware support actions, the equipment shall be provided “as-new” and the Contractor shall provide service and support to the refurbished equipment as if it were provided new from the OEM. If the Contractor chooses to purchase refurbished equipment, the Contractor shall obtain approval from the PCO/COR prior to the purchase. The Contractor shall provide the audit trail in the monthly report of where the equipment has been previously used and in what country the equipment refurbishment was performed unless the PCO waives this requirement. Refurbished equipment without an audit trail shall not be used on the AF system/networks unless approved by the PCO/COR. Refurbished equipment without an audit trail shall not be capable of storing any data or embedded coding (i.e.

batteries, power supplies, etc.). The Contractor shall comply with Section 3.7.1.1 IUID requirements. (CDRL A003)

3.7.3. Shipments

Shipping for this effort, shall be cost reimbursable. Shipping includes to/from units and OEM facilities. The contractor shall provide a spreadsheet of the shipping logs (incoming and outgoing) via electronic format on a daily basis. This log shall be cumulative on a monthly basis.

Replacement equipment will be shipped as required by the COR to maintain at least a 95% operational availability rate. (CDRL A007) The Contractor shall ensure that shipment of any equipment for an incident resolution conforms to the shipping method requirements included in Table 2.0.

Shipping Requirements

CONUS Shipping Requirement 2 Business Days

OCONUS Shipping Requirement 2-4 Business Days

Table 2.0 – Shipping Timelines

3.7.3.1. System availability-

Where the system must be ready for operation all the time and Not Mission Capable (NMC) is defined as the time from notification of failed part to replacement arrival at the unit location.

MC = Mission Capable any time an IR is not open for a system (i.e. NCC-D Flex, Medium SATCOM, ICAP Module)

NMC = An open IR for a failed part

System availability of at least 95%

𝑨𝑨𝑶𝑶 =

𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻 𝑴𝑴𝑴𝑴 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯

(𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻 𝑴𝑴𝑴𝑴 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯 + 𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻 𝑵𝑵𝑴𝑴𝑴𝑴 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯)

3.7.3.2. Mean Time To Restore Function (MTTRF)

The Mean Time To Restore Function (MTTRF) for a fielded system shall not exceed 7 calendar days. MTTRF is the average elapsed time, as a result of a failure, required to restore a system to full operating status (providing a spare does not need to be purchased). MTTRF includes administrative and logistics delay times associated with restoring function following a failure.

MTTRF is defined as follows:

𝑀𝑀𝑀𝑀𝑀𝑀𝑀𝑀𝑀𝑀 =

𝑁𝑁𝑀𝑀𝑁𝑁𝑁𝑁 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻

𝑁𝑁𝑀𝑀𝑁𝑁𝑁𝑁 𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐸𝐻𝐻

Not mission capable unscheduled (NMCU) refers to those times when the system is not mission capable because of unscheduled maintenance and associated delays.

Government delays due to IRs referred to the government do not count towards the 7 days.

3.7.3.3. Packaging, Handling, Storage and Transportation (PHS&T) The contractor shall be responsible for the preservation, packaging and transporting of all GFE and replacement spares to be delivered under the terms of this contract. The contractor shall comply with MIL-STD-2073-1E, DoD Standard Practice for Military Packaging. Packaging requirements are identified on the AFMC Form 158, Packaging Requirements. All "markings and labeling" of shipments shall conform to MIL-STD 129R, DoD Standard Practice Military Marking for Shipment and Storage. Shipments of classified/sensitive material or equipment shall be handled, transported, transmitted and protected IAW the National Industrial Security Program Operating Manual, DoD 5220.22M.

The contractor shall ensure items can be shipped by the appropriate mode of transportation.

All items shipped by the Defense Transportation System shall be governed by DoD 4500.9-R, Defense Transportation Regulation. Transportation requirements shall be listed on DD Form 1653, Transportation Data for Solicitations. The contractor shall provide transportation data for new items or for modified items IAW FAR 52.247-53.

The contractor shall identify and manage any items requiring special handling and/or movement which may include hazardous, oversize/outsize, items requiring demilitarization or precious metals. The contractor shall ensure shipped items are protected from the hazards of handling equipment and shall be transportable IAW MIL-STD-1366E, Interface Standard for Transportability Criteria.

3.7.3.4. International Standards for Phytosanitary Measures (ISPM NO. 15)

Requirements The contractor shall use the wood packaging material regulation for international trade which describes phytosanitary (including treatments) that have been approved for wood packaging material and provides for the approval of new or revised treatments. Use the latest revision of (ISPM No. 15), and the following statement complies with the United Nations-implemented restrictions on wood packaging material (WPM). "This requirement is specifically concerned with invasive species such as pinewood nematode. WPM is defined as wood pallets, skids, load boards, pallet collars, wooden boxes, reels, dunnage, crates, frames, and cleats. The statement below cites the requirements in detail and covers lumber for building containers and pallets used for deliveries resulting in worldwide shipments (direct vendor deliveries, Air Logistics complex (ALC), Container Consolidation Points (CCP), Aerial Ports, Water Ports, or other DoD installations.

3.7.3.5. Electrostatic Material (When Applicable)

The Contractor shall apply provisions of MIL-STD-1686, (current revision) when identifying all solid state devices and modules containing diodes, translators, integrated circuits and/or other microelectronic components sensitive to electrostatic forces. All such items shall be packaged IAW ASTM D3951 using electrostatic free barrier materials and shall clearly bear "Electrostatic Sensitive Device" labels IAW MIL-STD 129, Department of Defense Standard Practice Military Marking for Shipment and Storage.

3.7.3.6. Hazardous Materials (When Applicable)

The contractor shall ensure Hazardous shipments comply with International Civil Aviation Organization (ICAO), U.S. Code of Federal Regulations (CFR) Title 49, International Air Transport Association (IATA) Dangerous Goods Regulation, International Maritime Dangerous

Goods Code (IMDG, Annex 1), and AFMAN24-204_IP, Preparing Hazardous Materials for Military Air Shipments. Packaging shall meet "DOT specification or a United Nation (UN) specification " manufactured in accordance with 49 CFR, Part 178 and the final packages assembled IAW 49 CFR, Parts 100-185 as applicable. A Competent Authority Approval (CAA) shall be acquired from the responsible Associate Administrator or other designated Department official to perform a function requiring prior consent under the Hazardous Material Regulation (HMR). Packages(s) shall be marked IAW MIL-STD-129, DoD Standard Practice, Military Marking for Shipment and Storage. The contractor "shall" affix a completed DD Form 1574, Serviceable Tag-Materiel or DD Form 1574-1, Serviceable Label- Materiel to each unit pack or intermediate container and prime outer container(s). The tag or label will indicate the condition(s) of the materiel and to identify the individual article or contents, bundle, container to which they are securely attached. If a symbol is used to represent the manufacturer or the approval agency certifying compliance with 49 CFR 178, subparts L and M, the symbol must be registered with the U.S. Department of Transportation. A copy of the Contractor's Test Report and signed certification that the package configuration meets both CFR and UN requirements shall be made available to the procuring contract office, as required, prior to acceptance or shipment of any portion of the product IAW Contract Data Requirements List (CDRL) (Reference AFMC Form 158). Safety Data Sheets (SDS) are required for known hazardous items and applicable items shown in FED-STD-313, Tables I and II. The SDS shall have any applicable identification number, such as National Stock Number or Special Item Number. A copy of the SDS shall be mailed or e-mailed no later than "FIVE" days prior to contractual delivery of items.

3.7.3.7. Green Procurement Program (GPP)

GPP is a mandatory federal acquisition program that focuses on the purchase and use of environmentally preferable products and services. GPP requirements apply to all acquisitions using appropriated funds, including services, and new requirements. IAW FAR 23.404(b), the GPP requires 100% of EPA designated product purchases that are included in the Comprehensive Procurement Guidelines (CPG) list that contains recovered materials, unless the contractor cannot acquire the item:

1. competitively within a reasonable timeframe,

2. meeting reasonable performance standards, or

3. at a reasonable price.

The prime contractor is responsible for ensuring that all subcontractors comply with this requirement.

3.7.4. OEM Product Support

When a service issue is escalated to an OEM help desk, the Contractor shall continue to actively provide oversight, tracking and reporting on the status of the ticket and act as the user’s advocate.

Contractor shall provide status of all outages via the IR Log to the COR on a weekly basis. (CDRL A006).

3.7.5. Warranty Management

The contractor shall administer and enforce all commercial warranties offered by manufacturers and or distributors for parts used in the maintenance effort. The contractor shall be responsible for administration of warranties on Government-owned parts and equipment, including software, accountable under this contract. The Government will provide all available relevant warranty information to the contractor at contract award.

3.7.6. OEM Training

The Contractor shall procure OEM or third party training material or classes for Government personnel as directed by the PCO/COR.

3.7.7. Help Desk Support

Support actions: The contractor shall initiate response to an Incident Report (IR/trouble ticket) for failed items at a unit’s location upon receipt of the IR. This IR will contain the following information, at a minimum:

• The IR Number, a unique identifying number

• The unit information, address, point of contact, phone numbers and email address

• The failed part name, part number, serial number and Module or kit name.

Module or Kit name being the primary sub system that the failed part belongs to.

• Description of the problem, symptoms, details of the issue, in addition to troubleshooting actions taken.

The contractor shall record this information in an accountable database for tracking purposes and contact the unit to obtain any additional information required. Once satisfied that the correct part has been identified as failed, a replacement shall be processed for shipment to the unit. Details of this database are in paragraph 3.5

The Contractor shall provide support for TDC related tickets to include all equipment that is upgraded throughout the duration of this requirement. The Contractor shall provide a centralized, service desk with a toll free number that Users can call for assistance.

The Contractor’s Help Desk shall:

The contractor shall maintain and staff a helpdesk in support of TDC. The purpose of the helpdesk is to provide the fielded systems with technical support on an as needed basis and to assist users in troubleshooting, repairing and returning their system to full mission capability, including shipping spare parts when necessary. (CDRL A006)

Once the field contacts the TDC CLS Contractor’s helpdesk, the helpdesk will attempt to troubleshoot with the on-site Government maintainer. Troubleshooting may identify a failed component or software issue, requiring the TDC CLS Contractor to refer the Governmnet maintainer to the incident Report process or the PMO to provide the appropriate software assistance. It is not expected that the TDC CLS Contractor will need to travel to perform troubleshooting or repair/replacement, since the on-site maintainer would perform the removal/replacement of the component.

• Be able to diagnose and resolve hardware, and operational issues related to TDC equipment.

• Contractor shall be experienced in managing trouble tickets to OEM Help Desk or engineering support. OEM and Sub contractor support shall be on an as-needed basis including incidents requiring hardware covered under a manufacturer’s warranty or software support.

When the contractor requires additional engineering support for both hardware and software the TDC Program Office at Hanscom AFB shall be contacted to provide next level support.

During core hours, site requested maintenance shall be supported by technically proficient respondents not more than 30 minutes after the support request is initially received. All Incident Reports (IR) received after core hours shall be responded to the next duty day.

Outside the Continental United States (OCONUS) Locations: Unit must be contacted daily via email until contact is made. A second contact attempt shall be made by phone to OCONUS units whose duty day overlaps the contractor’s core hours. If contact is not accomplished after 3 days, the COR must be notified the next duty day.

3.7.8. Program Protection

3.7.8.1. Program Protection Plan (PPP)

The PPP will be provided as GFI. The PPP gives additional security requirements above the National Industrial Security Program Operating Manual (NISPOM).

3.7.8.2. Program Protection Implementation Plan (PPIP)

The Contractor shall prepare and deliver a PPIP. The PPIP shall identify implemented protection requirements upon subcontractors (if any) that will be providing, protecting, and accessing Critical Program Information (CPI) or Critical Components. It shall describe the Contractor’s assessment process of security practices of subcontractors or suppliers as appropriate and continually monitor their compliance with protection measures. It shall describe implementation of Supply Chain Risk Management to achieve Trusted Systems and Networks (TSN) per DoD 5200.44. It shall describe information assurance best practices including as appropriate to subcontractors. It shall describe counterfeit prevention processes and requirement for all levels of subcontractors. It shall require contractor and subcontractor reports of suspected or confirmed counterfeit items are entered into the Government-Industry Data Exchange Program (GIDEP) system. (CDRL A012)

3.7.8.3. Suspected or Confirmed Counterfeit Products Reporting Procedures The Contractor shall quarantine all suspect products pending further direction from the Government. The Contractor shall provide a statement, with problem description, justifying why this is considered suspect and how it was detected. If the supplier is not the OEM, the Contractor shall NOT notify the supplier that the items are suspected as being counterfeit items. However, consultation with the OEM is authorized. The Contractor shall make certain the Line Replacement Units (LRUs) and all members of the lot procured for use on this contract are stored in correct environmental controls.

The Contractor shall make certain the original documentation is secured as evidence and maintain any and all documentation associated with the LRU to include, but not be limited to:

• LRU information such as part identifying number, lot date code, manufacturer information and originator/point of contact information

• Any information reflecting LRU procurement/acquisition traceability (e.g. A copy of the purchase order, any and all correspondence between the buyer and the supplier to include: e-mails, records of phone conversations and paper letters of correspondence)

• LRU documentation from the purported original manufacturer, distributors and suppliers (certificate of compliance and certificate of conformance)

• All visual examination and physical analysis/testing results and the technical data package showing that the LRUs passed the required screening and qualification tests

• List of OEM products affected

3.7.8.3.1. Contractor Notification Procedures:

The Contractor shall, within 2 business days of discovery or lower-level notification, notify the PCO, COR, and the Government PM of all suspect items identified via e-mail and a formal contracts letter.

3.7.8.3.2. Subcontractor Notification Procedures:

The Contractor shall ensure all subcontractor(s), within 2 business days of discovery or lower-level notification; notify its customer, that is the next link toward the Prime Contractor.

Notification shall be passed up the customer chain until reaching the Prime Contractor.

3.8. GOVERNMENT FURNISHED PROPERTY (GFP)

The Government will provide GFP for the administration of this contract.

The following information shall be provided by the Government as GFP:

a. TDC Spares Equipment GFP

b. TDC Tools and Computer Equipment GFP

The Government will make every effort to provide the Contractor all existing GFE/GFP identified in the attached list of Government Furnished Equipment and Property. However, the Government reserves the right not to provide GFE/GFP, due to non-availability. In all circumstances where GFP/GFE is provided directly, the contractor shall comply with FAR Clause 52.245-1

The Contractor shall coordinate the request for and the delivery of all GFE/GFP through the PMO.

The PMO will determine the most cost effective method of all shipments for GFE/GFP using a DD Form 1149 or equivalent documentation evidencing all items transferred or on temporary loan.

A complete and detailed inventory shall be accomplished by the Contractor of all Government Furnished Equipment/Property using the latest version of the GFP Spreadsheet provided as GFI in accordance with the Exhibit A Instructions. (CDRL A009)

This process shall be completed IAW FAR 52.245-1. The Contractor shall submit the report in structured order so that the spreadsheet can be sorted and/or filtered. The Contractor shall submit the report electronically in Microsoft Excel. The GFP Report cannot be scanned or faxed.

Information provided must be extractable.

The Government Furnished Property Report should include all header fields from SGFP data Input Spreadsheet which provided the initial list of GFP:

The Government reserves the right to conduct a physical inventory of all GFE/GFP annually as well as 30 workdays prior to the end of the contract.

The PCO will approve the replacement of GFE/GFP, if required

The Contractor shall maintain up-to-date records of all GFE/GFP. The Contractor shall conduct annual inventories of GFE/GFP or as requested by COR, and provide the resulting list to the COR.

All custody exchanges shall be approved by the COR and documented in accordance with the terms of the contract.

If at any time, there is a discrepancy, it shall be reported immediately to the COR after the discovery of lost, damaged, or destroyed GFE/GFP. The Contractor shall investigate and submit a report of shortage, loss, damage, or destruction of GFE/GFP to the PCO and COR within two working days after the discovery. The Contractor shall report the specific property affected, including national stock number (NSN) or other identifying codes and nomenclature; the circumstances surrounding the loss, damage, or destruction; the estimated cost of alleviating the problem, if required; and the expected impact on provision of Contractor services, if any. The Contractor shall not remove GFE/GFP from the installation or other supported areas without written approval from the PCO or designated Government representatives. DFARS 252.245-7002 “Reporting Loss of Government Property” provides additional guidance with respect to loss of Government property.

The Contractor shall, at the end of the contract follow disposition instructions provided by the Government and subsequently delivered to or otherwise made available to the Contractor for use under the contract.

3.8.1. Warehouse GFP Inventory

The contractor shall use an inventory database to identify equipment (hardware and software) accountable to this contract.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .