A02 - Performance Work Statement (PWS) 26 Mar 2024.docx

PERFORMANCE WORK STATEMENT

FOR

SATELLITE COMMUNICATIONS (SATCOM) TERMINALS MAINTENANCE SUPPORT (STMS)

27 February 2024

Prepared by:

Commercial Satellite Terminal Program (CSTP) Project Manager, Tactical Network (PM TN)

SFAE-CCC-WTC

Aberdeen Proving Ground, MD 21005

1. SCOPE

The Satellite Communications (SATCOM) Terminals Maintenance Support (STMS) was established in response to a growing need for more information about failures and tracking of Trouble Tickets associated to outages, repairs, and maintenance. The SATCOM Maintenance Center (SMC), located on Aberdeen Proving Ground, Maryland (APG, MD), is 24 hours a day/seven days a week (24/7) facility that provides tracking for all assets, operational or spared worldwide. As well as logistical warehouse support for multiple programs to include, Deployable Ku Earth Terminal (DKET), Secure Internet Protocol Router and Non-classified Internet Protocol Router (SIPR/NIPR) Access Point (SNAP), Micro Very Small Aperture Terminal (mVSAT), Ground to Air Transmit and Receive (GATR), United States Marine Corps (USMC) Very Small Aperture Terminal System (VSATs), Transportable Tactical Command Communications (T2C2), Agile Communication Environment (ACE) program and Inflatable SATCOM Antenna (ISA). The STMS allows for data share amongst programs to identify mean time between failures (MTBF), repair or replacement costs, shipping, configuration management, Item Unique Identification (IUID) implementation and tracking, trend, and fault analysis. The STMS manages and maintains logistical capabilities through logistics personnel support that manage shipping, receiving, tracking, inventorying, maintenance, and the organization of the Continental United States (CONUS) and Outside of Continental United States (OCONUS) warehouses. Additionally, the STMS provides Engineering and Technical support to assist with technical requirements, Trouble Ticketing, and maintaining the SATCOM Terminal Remote Monitoring and Management (STRMM). The STRMM network provides near real time remote access to all Terminals, so the SMC has the visibility needed to provide the support needed to maintain mission success.

2. GENERAL

2.1. Period of Performance

Period of performance will be 8/24/2024-6/23/2029 for a 10-month Base Period, to include a thirty (30) day Transition-in period, and four (4) separate twelve (12) month Option Periods.

2.2. Place of Performance

The SMC operates 24/7 and its primary place of performance is at Aberdeen Proving Ground, MD (APG, MD). The contractor will be required to have permanent personnel stationed in APG, MD that will also be required to provide support at the Edgewood, MD Government facility outdoor storage area.

The Contractor will be required to have permanent Warehouse Manager and Logistician support stationed at Government facilities located at Arifjan, Kuwait, and Ramstein, Germany as identified in paragraph 3.1. The Contractor will be required to have permanent Network Support personnel located at APG, MD, and Shaw AFB, SC; the Shaw AFB personnel will provide support to Qatar, Doha and may travel to any location identified in paragraph 2.2.

The Contractor shall interface electronically or via telephone with Government Department of the Army Civilian (DAC) and Systems Engineering and Technical Assistance (SETA) Logistics personnel located in APG, MD, Ramstein, Germany and Camp Arifjan, Kuwait to access required data. The network hubs for STRMM are located at APG, MD, Shaw Air Force Base, South Carolina, and Qatar, Doha.

The Contractor may be required to travel to a Temporary Duty Station (TDY) to include, but not limited to the following locations: Australia, Bahrain, Djibouti, United Kingdom, Italy, Germany, Guam, Iraq, Japan, Jordan, Korea, Kuwait, Niger, Qatar, and Turkey. Additional locations could be added if the Government requires.

The Contractor will be required to obtain sponsorship services via a “bridge company” in order to perform services in Kuwait. The Contractor will be required to establish a “GmbH” in order to perform services in Germany.

See Attachment 1XX – Level of Effort (LOE) for specific personnel location requirements.

2.3. Work Hours

CONUS operational hours will be a 40-hour work week /to accommodate mission needs. The SMC will operate (7) days a week to include holidays on a 40-hour work week. During training exercises and deployments, the Contractor’s Contract Data Requirement List (CDRL) work hours may extend up to seven (7) days a week, 12 hours a day for a total of 60-hour work weeks. The training exercises and deployments must be approved by the Contracting Officer Representative (COR) in advance.

OCONUS operational hours will be a 40-hour work week for the Germany location and a 60-hour work week is authorized for the Kuwait location. There will be no deviation from these hours.

2.4. Inspection and Acceptance

Inspection and acceptance shall be at the specified destination.

Requiring Activity’s Department of Defense Activity Address Code (DoDAAC) W81LH7

2.5. Quality Assurance Surveillance Plan

The Government shall establish a Quality Assurance Surveillance Plan (QASP) for monitoring, reporting and evaluation of the Contractor’s performance under STMS. The Contractor is tasked to provide a feasibility report and provide the deliverables as indicated in the CDRL per the Department of Defense (DD) Form 1423-1. The Contractor will be evaluated with periodic inspections as to the quality of the output of their work and results will be documented. Included in the Contractor’s contribution in meetings and reviews, the quality of the Contractor’s technical reports, Contractor’s productivity and the overall quality of the technical support provided. The Contractor should be responsive to Government tasking and submit their monthly reports, technical reports as required by the contract. Timely feedback to the Contractor on unacceptable performance will be provided by the Contracting Officer (KO) and documented in writing. Prompt feedback is essential so the Contractor can develop and implement a corrective action plan.

2.6. Security

The Contractor shall have a Government approved SECRET facility clearance and personnel able to obtain and maintain a Secret level security clearance in accordance with (IAW) the DD Form 254 in this contract. The Contractor shall be required to have a Final SECRET facility clearance with SECRET safeguarding capability at the time of bid submission. In performing this effort, the Contractor shall have access to classified information at Government facilities only. Operations Security (OPSEC) requirements will be provided by the Government IAW Army Regulations (AR) 530-1 for this Performance Work Statement (PWS).

2.7. Documents

All the following applicable documents are available upon request.

· MIL-STD-130N Identification Marking of U.S. Military property

· DoD 4140.1R Supply Chain Materiel Management Regulations

· MIL-STD-3018 Parts Management

· AR 530-1, Operational Security (OPSEC)

· DoD 5220.22-M, National Industrial Security Program Operating Manual

· DoD Information Assurance (IA) Regulations, Policies, and Guidelines

· DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT) (29 Dec 20)

· FISMA Act of 2002, Federal Information Security Management Act of 2002

· Army Regulation 25-2, Information Assurance (IA) (4 Apr 19)

· DoDI 8500.01, Cybersecurity (7 Oct 19)

· DoDI 8500.2, Information Assurance (IA) Implementation

· DoDD 8551.01, Ports, Protocols, and Services Management (PPSM)

· DoD 8570.01-M Information Assurance Workforce Improvement Program (10 Nov 15)

· DI-SESS-81253C, Configuration Status Accounting (CSA) Information

· DI-MGMT-80441C, Government Property Inventory Report

· DFARS 252.239.700, Defense Federal Acquisition Regulation Supplement

· AR 25-2, Information Assurance

· AR 525-13, Antiterrorism

· AR 385–10, The Army Safety Program

· DA Pam 385-40, Army Accident Investigations and Reporting

· AR 200-1, Environmental Protection and Enhancement

· AR 11-35, Occupational and Environmental Health Risk Management

· OSHA Pocket Guide, Worker Safety Series – Warehousing

· SATCOM/CSTP SOP Logistics Shipping

· SATCOM/CSTP SOP SATCOM Maintenance

· Certification Standards Army Forces Strategic Command (ARSTRAT) X/Ka-Band Certifications: WGS X/Ka-Band Terminal certification requirements Version 2.0, 20 June 2006.

3. REQUIREMENTS

3.1. STMS Support

The Contractor shall provide the following in support of the STMS, excluding the items identified as Gov’t provided:

PWS 7.2.2

CTR facility, APG, MD and Govt Facility Edgewood, MD, Iraq, Qatar, Djoubiti, UAE, OMAN, Kuwait, Qatar, Bahrain, Jordan, Germany, Italy, South Korea, England, Africa

3.2. Satellite Communications (SATCOM) Maintenance Center (SMC) Facility

The Contractor shall provide a facility for the SMC, which operates 24 hours a day, 7 days a week, 365/366 (leap year) days a year. The Contractor’s SMC facility shall be located on the Aberdeen Proving Grounds (APG), Maryland (MD) Installation. The contractor provided workspace for APG, MD shall include desk space, telephones, internet connectivity and any other items and services necessary to work in an office / warehouse environment in the same building.

The current occupancy would be twelve (12) personnel, but occupancy may change as needed. The facility shall consist of a minimum of 15,000 square feet of combined office and warehouse space and a minimum of 3,000 square feet of outdoor, security fenced area. The warehouse space shall be a minimum of 4,000 sq. ft., the outside fence shall be at least 8ft tall. There shall be a power stub to the outside area for 208/120V, 200A, 60Hz, and 380/220V, 150A, 50Hz, the power can be switchable. The warehouse, office, and outdoor space shall be in/at the same building.

The warehouse space shall include a minimum of one (1) loading dock and a High Bay with minimum measurements of 10ft. wide and 12ft. high to include a ramp to enter High Bay if needed. The High Bay shall be in the same facility as the warehouse space, industrial shelving capable of holding 90 standard pallets, government provided forklift and provide secure, interior storage with access door. The office space shall include a minimum of one (1) secure room for SMC operations to support SIPR and NIPR connectivity, one (1) conference room, one (1) breakroom, two (2) bathroom, six (6) offices, one (1) lab room, Secure server room with racks for computer / server operation and a secure front entrance point. Office Services: regular janitorial and cleaning services, copier access and usage, document shredding, first aid kit management, common area maintenance, and access control system with badge readers at all entry doors, labs, SMC and other sensitive areas and internet wireless and wired internet to all offices.

The Contractor provided conference room shall support unclassified voice and video conferencing capability, and a capability for content display from laptop/tablet devices. The conference room shall support a minimum of fifteen (15) people with a conference room table that supports a minimum of eight (8) people. The VTC capability shall support multi-point calls with up to six (6) end-points. The display for VTC and content presentation shall be supportive of a collaborative environment for up to eight (8) people (minimum 60” display). The Contractor shall also provide suitable space (e.g., cubicle, workstation and office space, desk, chair, lighting, storage/testing space, commercial internet access, etc.) for a Government Project Manager.

Secure Lab room shall include power outlets for use of six (6) 220V power drops and (4) standard size racks at a minimum.

Security and access to the facility shall be controlled by the Contractor and must include, at a minimum, security cameras at the outdoor fenced area and all exterior entry/access points, as well as a badging process required for access to all entry and access points. There shall be a secure access point between the warehouse and office space, as limited access is required to the office space.

The Government will provide NIPR, SIPR, Defense Switched Network (DSN) and Voice over Secret Internet Protocol.

The Contractor shall provide and maintain commercial internet services at this location dedicated solely for Government use. The commercial internet service data rate shall be at a minimum of 250Mbps (with upload speed depending on the internet service provider) with a minimum of four (4) public static IP addresses. The Contractor shall not use this commercial internet service for day-to-day helpdesk operations.

The Contractor shall control access to the facility; however, the Government shall have access to perform the inspection and acceptance of completed work and tasks. The Contractor shall plan for the Government Project Manager to be on site at any point during normal operational hours, Monday through Friday. During real-world contingencies, the Government Project Manager may need to be on-site at any time of day, 7 days a week.

3.3. Transition

The Contractor shall follow the transition plan submitted as part of the proposal and keep the Government fully information of status throughout the transition period. The Transition period will be from date of award to 30 calendar days later.

The Contractor shall provide Tier 1 helpdesk support upon contract award. The Contractor shall provide Tier 2 helpdesk support, if required, within 15 calendar days of contract award.

The Contractor shall install equipment at their SMC location and provide personnel such that within 30 calendar days of award, the entire SMC operation, all support service, and the helpdesk are in full operational performance.

3.4. Training and Documentation

The Contractor shall provide software training for operations of the STMSto use the Monitor & Control (M&C) software, asset tracking, and Trouble Ticketing, as required by the Government. When training and/or documentation is required, the Government will request a rough order of magnitude (ROM) estimate from the Contractor and the resulting agreed upon deliverable cost will be paid for as an ODCs/material.

Software and license requirements referenced in PWS Section 3.4 and subparagraphs will be paid for as an ODC/Material Cost.

The Contractor shall have trained personnel and experience in the following software applications.

3.4.1. Monitor and Control (M&C) and Asset Management

The current M&C Trouble Ticketing, and asset tracking software will be supplied by the Government and used by the various SATCOM Terminals and the STRMM Network to include DKET, SNAP, ISA, and United States Marine Corps (USMC) Very Small Aperture Terminal System (mVSATs). It is also the software used for Trouble Ticketing and Asset management.

Network Engineers, and STRMM Engineers will be required to take the specific software administrative training with the Original Equipment Manufacturer (OEM).

Helpdesk personnel will be required to complete online M&C training and on-site software training.

The Government will sponsor any specific training that is unique to the STRMM network.

3.4.2. Trouble Ticketing

The current Trouble Ticketing software used by the SMC for maintenance support:

to include but not limited to DKET, SNAP, ISA, and USMC mVSAT. Software training will be provided by the Government and the Contractor will be required to ensure all users of software will be familiar with the system and trained with documentation provided.

3.4.3. Documentation

If required to develop new training and logistical documents for a customer based on the equipment being supported to be within scope of this contract. The Contractor shall develop those documents as a deliverable with an approved schedule and cost by the Government. Once documentation is completed, the Contractor shall implement the document requirements as part of the support on this contract.

3.5. (Optional) Software Licenses The Contractor shall provide HUB, Tactical and Strategic software licenses to support M&C and STRMM for new or existing systems requested by the Government. Software licenses referenced in this 3.4 and subparagraphs will be paid for as an ODC/material cost.

3.5.1. Hub Licenses:

Hub Licenses are for Terminals which are considered nodes that have several links (spoke sites) e.g., DKET is one but is not limited to.

3.5.2. Tactical Licenses:

Tactical licenses are for tactical Terminals and are the links at the spoke site of the hub including network enclaves (NIPR, SIPR, etc.) e.g., SIPR/NIPR Access Point (SNAPs) Terminal, Inflatable Satellite Antenna (ISA) are to name a few.

3.5.3. Strategic Licenses:

Strategic licenses are for large, fixed sites e.g., Regional Hub Nodes, Teleports, etc. but are not limited to.

3.5.4. Enterprise Licenses:

Enterprise licenses provide unlimited licenses and service support for all Terminals under the program for one (1) year.

3.6. Trouble Ticketing

The STMS is responsible for all Trouble Ticketing for the Government. The Contractor shall work with anyone the Government designates as responsible for the maintenance of the system that the Trouble Ticket software (TTS) is being open for. Future Trouble Ticketing solutions will run on current M&C platform. The Contractor shall use these software instances to log all maintenance tickets. TTS and/or M&C will be used to identify and track system/component warranties when deemed necessary. Additionally, TTS will be utilized to produce reports for internal and customer use as needed. The Trouble Ticketing will also be used to provide and track system priority statuses. The Contractor shall maintain a warranty report of all items being tracked by the contract IAW CDRL D001.

3.6.1. Priorities

The Contractor shall prioritize all assets, which will dictate shipping, receiving, and tracking based on the following criteria:

· Priority 1 – Outages; Trouble Ticket

· Priority 2 – HAZCONS; Trouble Ticket

· Priority 3 – Items replacements to existing systems; Trouble Ticket

· Government Priority 1-3; set by the Government All other items will then be prioritized by order of importance and approved by the Government.

3.7. Network Management

3.7.1. M&C and Asset Management Integration Support

The Contractor shall provide support to integrate the M&C software to the Asset Management software. The Contractor shall create an interface exchange between the two software packages. The Contractor shall eliminate any data entry duplication into multiple systems. To the extent that there is overlap in the compliance data complement and the host data complement, those elements will be candidates for integration.

3.7.2. DKET Integration Support

The Contractor shall install M&C configurations for any DKET in the CSTP enterprise and provide an Integrated Master Schedule (IMS) IAW CDRL B003.

This is to include ISA and mVSAT Terminals as needed:

· Update topology to match RF flow

· Update resource to use the appropriate translator for Terminal equipment make and model

· Update dashboard views to match configuration and resources of the Terminal

· Update IP addressing and serial addressing of resources

· Verify functionality (test out rules, switches, etc.)

· Package the updated configured system into a zip file that can be copied into a new onsite server

· Site survey to determine connectivity to new or relocation of Terminals being introduced into the network as per CDRL A001

3.7.3. Quarterly Information Assurance Vulnerability Alert (IAVA) Support The Contractor shall provide Cyber Security (IAVA) updates as required every quarter. The Contractor shall follow the guidance in PWS para. 3.7.1 and 3.7.2 in generating those updates.

References: Department of Defense (DoD) Information Assurance (IA) Regulations, Policies, and Guidelines

· DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process (DIACAP)

· FISMA Act of 2002, Federal Information Security Management Act of 2002

· Army Regulation 25-2, Information Assurance (IA)

· DoDD 8500.01E, “Information Assurance,” October 24, 2002

· DoDI 8500.2, Information Assurance (IA) Implementation

· DoDI 8510.01, Information Assurance Certification and Accreditation Process

· DoDD 8551.1, Ports, Protocols, and Services Management (PPSM)

3.8. Cyber Security

The Contractor shall develop a cyber-resilient system by ensuring IAVAs and Security Technical Implementation Guides (STIGs) can be applied individually without the need to re-image the system, and not only update IAVAs or STIGs during new capability updates. Contractor shall comply with all necessary DoD Cyber Security requirements, performing work as specified in this section when required. The Contractor shall provide Transmission Security (TRANSEC) over the satellite communication path/links. The Contractor shall configure satellite infrastructure devices (e.g., Internet Protocol (IP) modems) that directly support the IP protocol suite to comply with DoD Instruction (DoDI) 8551.1, Ports, Protocols, and Services Management (PPSM).

3.8.1. Cybersecurity Documentation Requirements

3.8.1.1. The Contractor shall support Government Cyber Certification and Accreditation (C&A), and Connectivity or Interconnectivity activities as required, including providing C&A documentation, upon request in a format acceptable to DoD Cyber C&A activities.

3.8.1.2. The Contractor shall report all IAVAs, STIGs and Bulletins within a Plan of Actions and Milestones (POA&M) monthly and provide a list outlining which were implemented, those not implemented and why they were not and how they were mitigated if mitigation was required. All non-implemented IAVAs and STIGs shall have Government concurrence. The Contractor shall provide a comprehensive and up to date software scan using current Army Best Business Practices for scanning and remediation every month. This data will be rolled up to the Assistant Secretary of the Army for Acquisition, Logistic and Technology (ASAALT) Cyber and the Procurement Executive Office (PEO) to ensure the basic mission assurance techniques are implemented uniformly with the portfolio.

3.8.1.3. The Contractor shall perform manual scans at least monthly to ensure the system is Federal Information Security Management Act (FISMA) and STIG compliant.

3.8.1.4. The Contractor shall provide updates, Incident Reporting and Vulnerabilities Management.

3.8.2. IAVAs

3.8.2.1. The Contractor shall apply Exploit Category A IAVAs within 14 days of notification through the NETCOM SharePoint site

3.8.2.2. The Contractor shall apply Exploit Category B IAVAs within 14 days, when possible, or within 30 days if a system level POA&M to mitigate is provided.

3.8.2.3. The Contractor shall monitor all update requirements vendor sites, mailing lists, third party sources, vulnerability scans and U.S. Army Cyber Command (ARCYBER) G36 SharePoint site for Information Assurance Vulnerability Messages. The Contractor shall make mitigation, patching, upgrade, or modification recommendations and provide a POA&M for all requirements that cannot be fulfilled on time, in a format approved by the PEO for each update requirement. The Contractor shall treat the POA&M as specified in the system’s Security Classification Guide (SCG) and provide a digital copy to the Government via a method approved by the Government. The Contractor shall provide a comprehensive and up to date software scan using current Army Best Business Practices for scanning and remediation every 30 days.

3.8.3. STIGS

Contractor shall implement STIG no later than (NLT) 30 days from release of a new Defense Information Security Agency STIG. Where an update cannot be technically applied due to system functionality, that STIG item shall be documented in the system POA&M with appropriate mitigations. If an update cannot be applied NLT 30 days, the Contractor shall provide a milestone schedule in the POA&M item for application for Government approval.

3.8.4. Risk Management Framework (RMF) Process

The Contractor shall complete items mandated by RMF and Agent of Certifying Authority (ACA) to include documentation called out in the DoD 8500 and Chairman of the Joint Chief of Staff (CJCS) 6510 series directives, instructions, and manuals. The Contractor shall assist the Warfighter Information Network-Tactical (WIN-T) program office to initiate and plan the Cyber Certification and Accreditation (C&A) leading up to the implementation and validation of assigned Information Assurance (IA) controls.

The Contractor shall implement a Cyber program to ensure that the system meets all DoD IA requirements IAW Army Regulation (AR) 25-2 “Information Assurance”, DoDI 8500.1 “Information Assurance”, DoDI 8500.2 “Information Assurance Implementation”, and DoDI 8510.01.

The Contractor shall support the RMF process for DKET, Micro VSAT, ISA, SNAP SATCOM Terminals. The Contractor proposed implementation shall be compliant with current policies, guidelines, and requirements within DoD governing C&A.

The Contractor shall update the RMF package and the embedded Cyber Test Plan, as required, to reflect relevant changes in the system hardware and software baselines.

3.8.5. Interim Approval to Test (IATT)

The Contractor shall perform software scans prior to any Government witnessed tests, and remediate and/or mitigate all Category 1, 2, and 3 findings.

3.8.6. Authority to Operate (ATO)

The Contractor shall support all IA meetings, reviews, testing and activities to support and enable the Government to obtain and maintain an ATO IAW DoDI 8510.01. The ATO process will occur every three (3) years. The Contractor shall support 3rd party software scans and requirements where the 3rd party is identified by the Government. The Contractor shall support POA&M maintenance.

3.8.7. Federal Information Systems Management Act (FISMA)

The Contractor shall implement and execute the yearly activities associated with satisfying the RMF Annual Review and meeting the reporting requirements of FISMA. The annual review date will be recorded in the System Identification Plan, which will coincide with the date of the signed ATO.

3.9 Satellite Maintenance Center (SMC) Helpdesk Support

The contractor shall report any repairs, shipments, Return Material Authorization (RMAs), property transfers, equipment swaps, or any other action tied to government assets with the ticketing system stated in paragraph 3.6 and all subparagraphs. The systems identified by the government shall coordinate all replacements and repairs through the SMC. The COR will provide oversight and direction to SMC activities. SMC contact information will be provided to the Contractor and or government representative who performs the maintenance of the systems being supported, by the COR, upon task order award. The contractor shall coordinate all actions taken with the system representatives supporting the terminal identified by the COR will be the responsibility of this contract.

3.9.1 Helpdesk

The contractor shall provide helpdesk Tier I and Tier II support. The Tier I support shall field calls 24/7 and report maintenance actions via the ticketing system. The Tier I support shall record via the ticketing system all required actions (shipments, repairs, replacements, maintenance actions, etc) and will support any actions pertaining to maintenance of any system being supported. The Tier I personnel will use the logistical system to determine availability of spares for maintenance actions.

The Tier II support shall be technically knowledgeable about the systems being supported by the SMC. They shall make attempt to provide guidance to system representative to fix issues being reported, as well as to evaluate repair items to ensure a fix action is required. The Tier II personnel will support the CONUS maintenance support of systems identified by the COR. The Tier II personnel will support the Tier I personnel and be available 24/7. The Tier II personnel will use the M&C system provided by the government to view system connected to the network to support maintenance issues.

4. GOVERNMENT FURNISHED PROPERTY

4.1. Government Furnished Property (GFP)

The Government will be providing GFP for use by the Contractor to perform the duties as required. The Contractor shall only use the property for performing work in support of this contract. Modifications or alterations of property are prohibited. The Contractor shall not cannibalize property. In the event property is received by the Contractor in a condition not suitable for its intended use, the Contractor shall immediately notify the COR. The Contractor shall have a process to enable the prompt recognition, investigation, disclosure and reporting of loss of incidental property (meaning unintended, unforeseen or accidental loss, damage, or destruction of Government property that reduces the Government’s expected economic benefits of the property).

Government property that is incidental to the place of performance, when the contract requires contractor personnel to be located on a Government site or installation, and when the property used by the contractor within the location remains accountable to the Government. Incidental property is not covered under FAR Part 45, Government Property. The Contractor is responsible for maintenance and repair costs and conditions by which the contractor could be liable for loss.

4.2. Facilities.

The Contractor shall be responsible for the office space/working space within the facility necessary to accomplish the requirements outlined within this PWS. The Government shall provide the shelving, cages, forklifts, UID printers, test lab equipment and any other specialty items currently required to support the STMS. Computers will be provided to the Contractor personnel by the Government. Common Access Card (CAC) is required for Government computer use.

If the Contractor proposes a facility other than the current incumbent facility, the proposed facility must be “move in ready” on the day of contract award. The incumbent contractor (herein referred to as “the incumbent”) will uninstall all Government Furnished Property (GFP) (PWS 4.0 and subparagraphs) and any other Government-owned software and documentation at the incumbent’s helpdesk location at APG. The Contractor awardee (herein referred to as “the Contractor”) shall ship the items to the Contractor’s new SMC location and reinstall all of the equipment at that location. The Government will be responsible for the cost of shipping. The Government will notify the Contractor when the GFP is available for shipping, and the Government will help facilitate and coordinate this move with the incumbent. The Contractor shall prepare a list of all hardware, software, and documentation removed by the Contractor, which the Government will validate prior to the Contractor shipping the items to the Contractor’s new SMC location.

4.3. Telephone Services.

The Contractor shall be provided telephone services for official use only in carrying out the terms of this contract. Defense System Network (DSN) capable telephone lines will be provided at each Government provided service facility. The dial access capability will be restricted to only that capability required for mission accomplishment, to provide contact between the service facility and other service locations and facilities. This service is provided strictly for the purpose of completing the mission requirements of this contract (e.g., coordinate response to outage, parts/labor support, etc.).

4.4. Internet and Email Access (Official Use Only).

The Contractor shall provide standard commercial Internet services as part of this contract. Any requirements for other than commercial Internet services will be provided by the Government and coordinated with the U.S. Army Signal Network Enterprise Center at Aberdeen Proving Ground (USASNEC-APG). Facilities shall provide capability for SIPR/NIPRnet access. The Government shall provide oversight and assistance with access to SIPR/NIPR capabilities as required.

4.5. Vehicles will be provided to OCONUS personnel only.

Personnel must obtain a local Kuwait country license prior to the Government authorizing vehicles; the Contractor shall be responsible for the sponsor of this license via a “bridge” company of the Contractor’s choosing.

5. ITEM UNIQUE IDENTIFICATION (IUID)

The Contractor shall manage an IUID program for all hardware delivered under this contract to ensure that all equipment meeting the UID criteria is marked, and the applicable data are submitted to the DoD UID Repository.

5.1. UID Marking

The Contractor shall comply IAW Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7003, Item Unique Identification and Valuation to provide UID, IAW DFARS 252.211-7007, Reporting of Government Furnished Property; or DoD recognized unique identification equivalent, for all applicable equipment items and MIL-STD-130N. UID marking shall be IAW the latest version of MIL-STD-130N. UID markings are also required for embedded components, such as subassemblies. Guidance for UID marking of embedded components shall be IAW the latest version of MIL-STD-130N at website http://www.acq.osd.mil/dpap/pdi/uid/.

5.2. UID Data Submission Guidance

The latest UID Data Submission guidance may be found at http://www.acq.osd.mil/dpap/pdi/uid/data_submission_information.html. The Contractor shall submit UID data via the Wide Area Workflow (WAWF) Paperless Contracting Environment per the latest published guidance.

5.3. Asset Tracking Software

The Contractor shall provide asset tracking software used by the STMS that tracks Terminals and components. Asset tracking shall be maintained in a Government approved software database. The Government may request the transition to a Government managed software during the Period of Performance of this effort. The database shall follow MIL-STD-130N and shall be capable of creating all required documents for transfer, transportation, and accountability. The asset tracking software referenced in PWS section 5.3 will be paid for as an ODC/Material Cost.

Asset tracking software will support following forms:

· Department of the Army (DA) 2062

· Department of Defense (DD) 3161

· DD 1149

· DD 250

· DD 1348-1A

· DA 2765-1

6. CONTRACT DATA REQUIREMENT LIST (CDRLs) The following deliverables shall be submitted IAW the CDRLs listed the basic contract:

A001

DI-MISC-82104A

PWS 3.7.1., 3.7.2

Site Survey Report (SSR)

A002

DI-MGMT-80441D

PWS 6.1.4

Monthly Govt Property Inventory Report

A003

DI-MGMT-81804A

PWS 6.1.3

Item Unique Identification (IUID)

B001

DI-MGMT-80368A

PWS 6.1.1

Monthly Status Report

B002

DI-MGMT-81468A

PWS 6.1.1

Contract Funds Status Report (CFSR)

B003

DI-MGMT-81861C

PWS 3.6.2

Integrated Master Schedule (IMS)

D001

DI-SESS-81639B

PWS 3.5

Warranty Performance Report

D002

DI-TMSS-81815

PWS 6.2

Commercial-Off-The-Shelf (COTS) Manuals

S001

DI-SESS-80255B

PWS 6.1.2

Failure Summary and Analysis Report

6.1. Reports

6.1.1. Monthly Status Report

The Contractor shall prepare and deliver monthly status reports IAW CDRL B001 and a separate Contract Funds Status Report IAW CDRL B002. Contractor format is acceptable IAW the cited Data Item Description (DID) IAW MIL-STD-963C, Data Item Descriptions (2014), but shall include activities completed for the month, planned activities for the following month, schedule, any issues or complications, and planned solutions to solve those issues or complications. Electronic copies shall be submitted via email to the COR and the KO. All reports shall be submitted no later than NLT the 15th of each month.

6.1.2. Quarterly Reports Failure Reporting & Corrective Action Systems (FRACAS) The Contractor shall develop procedures for analysis of failures to determine the root cause, and documentation for recording corrective actions taken. The FRACAS shall include uniform failure reporting, failure and trend analysis reports and corrective actions. All hardware/software failures from system level down to the maintenance-worthy piece part shall be subject to these requirements. The Contractor shall notify the Government of any failure impacting safety, cost, schedule, production, supportability, and cost of ownership or interface/performance. All failures, critical and non-critical, shall be reported quarterly to the Government for review. System operational hours (Elapsed Time Meter readings) shall be identified for each failure occurrence and included in the FRACAS data structure. The Contractor shall assess the failure data for the identification of trends (three (3) or more failures of the same root cause) and identify those trends in the monthly status report. The Contractor shall submit to the Government FRACAS reports IAW CDRL S001. Each FRACAS report shall, at a minimum, identify the root cause, and detail the remedial action taken including parts replaced. Each new and open FRACAS report shall be delivered quarterly until closure. Upon closure, a final individual FRACAS report shall be presented in the quarterly reporting requirement. The Government reserves the right to conduct a Failure Review Board (FRB) throughout the contracted period of performance. The Contractor is encouraged to use MIL-HDBK-470A as guidance.

6.1.3. Item Unique Identification (IUID) Marking and Verification Report The Contractor shall prepare and deliver an Item Unique Identification (IUID) Marking and Verification Report IAW CDRL A003 DI-MGMT-81804A The Item Unique Identification (IUID) Marking and Verification Report is a tabular list which provides the data resulting from IUID marking activities such as: physical asset marking, registration, verification, inventory audits, quality audits, and other asset lifecycle activities.

6.1.4. Government Property Inventory Report

The Contractor shall prepare and deliver Quarterly Government Property Inventory reports IAW CDRL A002. Contractor format is acceptable IAW the cited Data Item Description (DID), DI-MGMT-80441D.This report enables the Contractor to periodically provide to the Government an inventory listing of Government Property (i.e., both Government Furnished Property (GFP) and Contractor Acquired Property (CAP)) in the Contractor’s possession (to include Sub-contractors) by contract.

6.2. Standard Operating Procedures (SOPs)

6.2.1. Internal SOPs

The Contractor shall develop logistics Standard Operating Procedures (SOPs) IAW Department of Defense (DoD) Instruction 5000.64 Accountability and Management of DoD Equipment and Other Accountable Property, Federal Acquisition Regulation (FAR) Part 45 Government Property), and Army Regulation (AR) 740-1 Storage and Supply Activity Operations. All Contractor SOPs must be reviewed and approved by the U.S. Government prior to publishing the finalized product and formatted IAW CDRL D002.

The Contractor shall develop a Helpdesk and Trouble Ticketing SOP for the Satellite Communications Terminals Maintenance Center (SMTC) IAW FAR Part 45 Government Property, and the Contractors SOP must be reviewed and approved by the U.S. Government prior to publishing the finalized product. The Hazardous Condition reporting process will be IAW Government directed requirements.

6.3. Parts

The Contractor shall identify parts that need to be replaced or repaired, provide a quote and then action based on approval from the Government. The Contractor shall deliver, and store these parts as needed based on the needs of the mission.

6.3.1. Material

The Contractor shall provide any material necessary to complete the tasks listed above to include spare parts, test equipment, shipping, etc. Prior to procuring any materials over $1,000 the Contractor shall obtain COR approval. The Contractor shall not purchase any materials without direction and approval of the KO that exceeds $2,500 for services or $3,500 for supplies. All purchases exceeding this micro-purchase level threshold will require three quotes. All materials shall have a Purchase Order no later than 30 days from the request to the COR approval.

The Contractor shall notify the COR if the Contractor is unable to purchase materials due to any proprietary restrictions. The Government shall provide the Contractor with any components that the Contract identifies as proprietary as Government Furnished Equipment (GFE). Any components the Contractor identifies as proprietary, the Government will GFE the component. Any item procured will be tracked and identified in the tracking database. The Contractor shall prepare and deliver Monthly Government Property Inventory reports IAW CDRL A002.

6.3.2. Component Replacements

The Contractor shall identify components for replacement that are failed, to include items deemed to be beyond economical repair, 65% of component or subsystem cost, by the COR. IAW DoD 4140.1R (Section 2)

6.3.3. Repairs

The Contractor shall identify components for repair that have faults, to include items failed up to the beyond economic repair threshold determined. If the repair is estimated above 65% of component or subsystem cost, it must be approved by the COR. If a component is determined to be within the threshold for repair (under 65%), the Contractor shall take necessary steps to remedy that component. The Contractor shall contact vendors to obtain quotes to have said component repaired. Quotes shall be presented to the COR for approval. Once a quote is approved by the COR, the Contractor shall work to have the component shipped to and from said vendor to conclude the repair of that component.

6.3.4. Diminishing Manufacturing Sources and Material Shortages (DMSMS) Parts Obsolescence The Contractor shall proactively identify configuration items, including spare parts, subject to DMSMS and parts obsolescence IAW MIL-STD-3018 (Section 6, para 6.4.3). The Contractor shall prepare and provide to the Government a DMSMS Report IAW CDRL A004. The report shall present the screening/forecasting tool and methods applied to determine forecasted risks and present a projection covering a minimum of five (5) years into the life cycle identifying when a DMSMS or parts obsolescence risk may impact the configuration Product Baseline. The probability of risk and recommended risk mitigation action(s) shall be determined and documented in the report for each DMSMS risk. Upon identification of a DMSMS or parts obsolescence risk, the Contractor shall develop and provide in the report recommended action plan(s) to mitigate the risk impact regarding system availability, schedule, and cost. The Contractor shall progressively assess DMSMS and obsolescence and convey this information along with recommended action plans, including alternative sources, parts, materials, and implementation costs to the Government. The Contractor shall deliver source data as part of the DMSMS Report to support Government forecasting of DMSMS risks. Source data shall be to the lowest configuration item indenture as detailed within the configuration management baseline. The Contractor is encouraged to participate in the no-cost GIDEP. The Contractor may visit https://www.gidep.org to initiate participation in the GIDEP. Proactive application of GIDEP is encouraged. The Contractor is encouraged to visit https://www.dau.edu/cop/dmsms/Pages/Default.aspx for further DMSMS guidance.

7. Areas of Support The Contractor may be responsible for providing the below areas of IAW Appendix A, Labor Categories STMS. These labor categories are not all inclusive and required man-year support varies.

7.1. Logistical Support

The Contractor shall provide qualified logistical support personnel capable of working in a military environment and knowledgeable with the DoD polices for all military agencies in relation to logistics. This includes shipping, receiving, tracking, inventorying, maintaining, and organizing warehouses CONUS and OCONUS.

7.1.1. Global Logistics Support

The Global Logistics Support is responsible for the overall accountability, management, and delivery of logistics and field procurement activities in support of CONUS and OCONUS warehouse operations. The Global Logistics will have direct oversight of each warehouse being supported. Fundamental to this role is the ability to remotely manage and mentor the logistical team specialists engaged with country program management teams and take an active role in the preparation and implementation of emergency logistics responses.

· Update, maintain, disseminate, and control the effective implementation of international logistics, warehousing, and procurement procedures across country programs

· Oversee the coordination and movement of equipment between warehouse hubs

· Develop and coordinate the delivery of training modules to employees.

· Develop logistics auditing tools

· Coordinate regular country logistics audits and the development of action plans as needed

7.1.2. Warehouse Support

Responsible for the management of the entire warehouse and the flow of resources between the point of origin and the point of destination to meet shipping requirements. It involves the integration of information flow, material handling, production, packaging, inventory, transportation, warehousing, and often security.

The Contractor shall provide support to a range of commonly used mVSAT SATCOM and baseband systems. The Contractor shall perform the following specific tasks:

· Provide reports as required

· Keep appropriate databases updated to accurately reflect system baselines and perform audits on such database to ensure effectiveness of controls

· Liaise with the customer to ensure requirements are met

· Help develop standards, guidelines, and SOPs for internal logistics processes

· Providing guidance and support in the maintenance of version control of baseline hardware and software documentation

· Maintain Property Accountability for all PdM SATCOMS systems in OCONUS and CONUS IAW ARs 700-142 (Type Classification, Material Release, Fielding and Transfer) and 735-5 (Property Accountability Policies)

· Manage IUID efforts IAW MIL-STD 130N, IAW DFARS 252-211-7003, and IAW DFARS 252-211-7007

7.1.3. Logistic Support

The Contractor shall provide Logisticians who will support all warehouse functions and ensure all assets are accounted for and shipped in an appropriate manner.

The Contractor shall perform the following tasks:

· Enable Maintenance and warranty repair

· Manage equipment spares

· Handle packaging and shipping (inbound and outbound)

· Maintain maintenance action tracking and status update

· Maintain equipment asset tracking and warranty status

· Manage equipment repair turnaround time

· Provide reports as required

· Information Technology Infrastructure Library (ITIL) Change Management.

· Framework and following the direction of Designated Approval Authority (DAA)

· Conduct day-to-day activities of change management process execution

· Enable maintenance and warranty repair

· Request and provide quotes from freight forwarders

· Manage equipment spares

· Handle packaging and shipping (inbound and outbound)

· Maintain maintenance action tracking and status update

· Maintain equipment asset tracking and warranty status

· Manage equipment repair turnaround time

· Operate forklifts up to 10K lbs.

· Generate shipping documentation such as DD 1149, Bill of Ladings (BoLs), and Customs forms

7.1.4. IT Asset Management Software Engineer

The contractor shall provide IT Asset Management Software Engineer who will support the asset management process via the several different software platforms stated in paragraph 5.3

· Analyze the needs of the user

· Design, test and develop the software to meet those needs

· Recommend upgrades for existing systems and programs

· Develop separate elements of a software that work well in the program as a whole

· Create various diagrams, flowcharts and models that illustrate the type of code needed for programmers

· Ensure continued functionality of a program during maintenance and testing of software

· Document each aspect of a system or application as a reference for future upgrades and maintenance

· Revisit the development process to fix bugs or address client or consumer concerns

· Perform daily and long-term operational and strategic management of hardware and software

· Plan, monitor, and record hardware assets and/or software license to make sure they complied with vendor contracts in different software tools

· Apply a continuous improvement approach in enhancing the strategies employed in technology spending, as well as in tracking company assets within the Configuration Management Database (CMDB) throughout their lifecycle

· Ensure effective management of the CMDB and that the content contained is accurate

· Define and enhance scheme for identifying hardware and software-related assets as well as CIs, including versioning and dependencies in the asset management tools, attributes, the Contract management library, and the CMDB

· Manage inventory of CIs and assets, including dependencies and attributes), making sure that modifications, withdrawals, and additions of existing ones are correctly recorded by the teams in charge in the tools to ensure that the vendor contracts are complied with

· Responsible for managing lifecycle of hardware and software models in the DML right from their introduction to their retirement

· Generate and distribute various reports, including compliance reports on current assets and CIs and their status; also perform trend analyses

· Perform verification and audit of DML and CMDB content;…