20200115_PWS -DITTR .pdf

PDF 414 KB Posted

Attached to
DITTR Warranty and Maintenance
Solicitation number
W91151-20-R-0009
Issued by

About this file

This is a sources sought synopsis for a sole source contract to provide remote and on-site hardware/software warranty and maintenance for proprietary equipment installed in the Deployable Integrated Telecommunications Test Range radio frequency threat emitter. The incumbent is TLC Solutions, Inc. Responses are requested to determine if competition is possible and to support a competitive procurement. The requirement includes warranty coverage for equipment located at Fort Huachuca, Arizona in support of the Intelligence Electronic Warfare Test Directorate, United States Army Operational Test Command. The period of performance is one base year with four option years. Responses are due by July 15, 2020 and must include business information and details regarding experience, pricing, and recommendations to improve competition. The NAICS code is 517919 with a size standard of $35 million.

View the file

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

PERFORMANCE WORK STATEMENT (PWS)

United States Army Operational Test Command (USAOTC)

DITTR Warranty/Maintenance Agreement 15 January 2020

TABLE OF CONTENTS

Description

1.0 General

1.1 Description of Services

1.2 Background

1.3 Objectives

1.4. Scope

1.5. Period of Performance

1.6. General Information

1.6.1 Quality Assurance

1.6.2 Recognized Holidays

1.6.3 Hours of Operation

1.6.4 Place of Performance

1.6.5. Type of Contract

1.6.6. Security Requirements

1.6.6.1 Physical Security

1.6.6.2 Contractors Requiring Common Access Card (CAC)

1.6.7 General Training Requirements

1.6.8 Safety

1.6.9 Post Award Conference/Periodic Progress Meetings

1.6.10 Contracting Officer Representative (COR)

1.6.11 Identification of Contractor Employees

1.6.12 Organizational Conflict of Interest

1.6.13 Installation Access

2.0. Definitions and Acronyms

2.1 Definitions

2.2 Acronyms

3.0 Government Furnished Items and Services

3.1. Services

3.2. Equipment

4.0 Contractor Furnished Items and Responsibilities

4.1 General

5.0 Specific Tasks

5.1 Basic Services

5.2 Equipment

5.3 Technical Faults and Queries

5.4 Data Collection Requirements

5.5 Response Times

5.6 Enterprise Contractor Manpower Reporting

6.0 Applicable Publications

PART 1

GENERAL INFORMATION

1. GENERAL: This is a non-personnel services contract to provide warranty coverage of proprietary software and hardware for support of the Intelligence Electronic Warfare Test Directorate (IEWTD), USAOTC’s Deployable Integrated Telecommunication Test Range (DITTR) Radio Frequency (RF) threat emitter.

The Government shall not exercise any supervision or control over the contract service provider performing the services herein.

1.1 DESCRIPTION OF SERVICES/INTRODUCTION: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform warranty services for the Deployable Integrated Telecommunications Test Range (DITTR), a RF threat emitter, as defined in this Performance Work Statement (PWS) except for those items specified as Government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 BACKGROUND: Currently IEWTD, USAOTC operates a multi vehicle RF threat emitter system called DITTR for support in Operational Test missions within ATEC and DOD. This system has been in service for approximately 12 years and needs occasional upgrades, replacements and standard hardware maintenance warranties to stay effective in its continuous support to all Electronic Warfare (EW) DOD missions. The PWS is necessary to provide an extended warranty of all RF threat emitter hardware, software maintenance for those RF components and support for all applicable software updates and license agreements. The support services provided by the test support contractor are critical to mission accomplishment. IEWTD, USAOTC has a statutory mission to conduct independent operational tests for material and equipment prior to full scale production in accordance with 10 U.S. Code Section 2399.

1.3 OBJECTIVES: The major objectives of this requirement is for the contractor to provide a hardware/software warranty to cover the contractor’s proprietary equipment installed in IEWTD, USAOTC’s RF threat emitter (DITTR). This contract is necessary to provide support for ongoing operational test activities and test support for multiple Army and Department of Defense level programs being conducted at IEWTD, USAOTC.

1.4 SCOPE: This hardware and software maintenance and warranty support covers the hardware and software supplied previously by TLC Solutions Inc. and installed in IEWTD’s DITTR RF threat emitter system. (See section 5.2 for precise list of equipment covered by this PWS). Support is primarily supported remotely, however, on-site hardware/software support for up to two weeks per year may be required due to the inability to provide remote support or urgent customer support requirements.

1.5 PERIOD OF PERFORMANCE: The period of performance shall be for one

(1) base year of 12 months and four (4) 12-month option years.

1.6 GENERAL INFORMATION:

1.6.1 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan and the Performance Requirements Summary, TE A. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.2 Recognized Holidays. The following federal holidays are observed by the Government:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.3 Hours of Operation: The Contractor shall perform the services required under this contract between the hours of 0730 and 1600 Monday through Friday and adhere to all federal holidays. During field testing, regardless of the location, duty hours will be adjusted as required to meet test schedules and/or optimum environmental conditions for testing. Specific work hours are based on test mission requirements and will be published in the weekly and daily test schedules, and/or as directed by the Contracting Officer. The Government will coordinate directly with the Contractor for warranty support services based on the level of maintenance needed. Any overtime, if required, will be incorporated into this firm-fixed price contract.

1.6.4 Place of Performance: The work to be performed under this contract will be at the Fort Huachuca, Arizona. Historically, it has been necessary to perform the support updates and maintenance over phone (hotline) or through secured internet connection. If required, the Government will coordinate with the Contractor for on-site support. Communication between the Program Manager and COR for after hour or emergency calls may be required for mission support.

1.6.5 Type of Contract: The Government will award a Firm Fixed Price Contract.

1.6.6 Security Requirements: This system is unclassified and requires only a background check of Contractor personnel.

1.6.6.1 Physical Security: The Contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use.

1.6.6.2. Contractors Requiring Common Access Card (CAC): Before CAC issuance, the contractor employee requires, at a minimum, a favorable adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation IAW Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks onsite or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

Contractors that do not require CAC, but require access to DoD facility or installation: Contractor and all associated subcontractors employees shall comply with adjudication standards and procedures using the National Crime Information Centre Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative), or, at OCONUS locations, IAW status of forces agreements and other theatre regulations.

1.6.7 General Training Requirements: The Contractor is responsible for hiring qualified personnel with required certifications in performance of this contract.

Contractor personnel shall complete the mandatory training referenced in section

1.6.7 and for any required refresher training to support the current assigned mission. Any other training of contractor personnel must be directly related to the current assigned mission and shall be approved in advance by the KO or designated representative for each contractor employee.

1.6.7.1 OPSEC Training. All Contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete four (4) OPSEC classes: OPSEC 1301 Fundamentals, OPSEC Awareness for Military Members, DoD Employees, and Contractors;

Social Media and Operations Security Training; and Social Networking. These shall be completed within fifteen (15) calendar days after contract start date. The Contractor shall submit certificates of completion for each affected Contractor employee and sub-Contractor employee to the COR within fifteen (15) calendar days after completion through e-mail. These courses are available online at the following websites:

https://securityawareness.usalearning.gov/opsec/index.htm -OPSEC 1301 OPSEC Fundamentals (4 Hours) -OPSEC Awareness for Military Members, DoD Employees, and Contractors (45 minutes).

1.6.7.2 Per AR 530-1, Operations Security, new Contractor employees must complete Level I OPSEC training within thirty (30) calendar days of reporting for duty. All Contractor employees must complete annual OPSEC awareness training.

1.6.7.3 Antiterrorism (AT) Level I Training. All Contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, and controlled-access areas shall complete AT Level I awareness training within thirty-(30) calendar days after reporting to duty. The Contractor shall submit certificates of completion for each affected Contractor employee and subcontractor employee, to the COR through e-mail within fifteen (15) calendar days after completion of training for all employees and subcontractor personnel.

AT Level I awareness training is available at the following website: Joint Knowledge Online, http://jko.jten.mil. Training must be completed annually.

1.6.7.4 iWATCH Training. The Contractor and all subcontractor shall brief all employees on the local iWATCH program (training standards provided by the requiring activity antiterrorism officer). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within fifteen (15) calendar days after contract start date and the certificates of completion submitted to the COR through e-mail within fifteen (15) calendar days after completion. New employees shall complete training and submit results to the COR before commencing work under the contract.

1.6.7.5 Threat Awareness and Reporting Program (TARP) Training. Within thirty

(30) calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever applies, or thirty (30) calendar days after employment of new personnel, all Contractor employees, including subcontractor employees, who are employed under the contract, shall complete TARP training within thirty (30) calendar days after reporting to duty IAW AR 381-

12. The Contractor shall submit certificates of completion for each affected Contractor employee and subcontractor employee to the COR within ten (10) calendar days after completion of training. TARP training is available at the Army Learning Management System (ALMS) https://www.ako.alms.army.mil/. Training must have been completed within the last twelve (12) months and maintained yearly thereafter. If training cannot be conducted on the website, the Contractor will coordinate with the local Counter Intelligence (CI) Officer at their assigned location for classroom training and a copy of either the training certificate or the https://securityawareness.usalearning.gov/opsec/index.htm http://jko.jten.mil/ https://www.ako.alms.army.mil/ training attendance roster signed by the CI Officer will be maintained by the Contractor. Verification of the training will be provided to the COR within ten (10) calendar days after completion of the training.

All Contractor employees and associated sub-Contractor employees must complete the DoD Cyber Awareness Challenge training before issuance of network access and annually thereafter. All Contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoD 8570.01, DoD 8570.01-M and AR 25-2 upon hire. In addition to the training, the Contractor shall review, sign and provide a copy of the LAN agreement to the COR and KO prior to receiving a network account. Use https://portal.otc.army.mil/pubs/Miscellaneous Forms/OTC LAN Access User Agreement.pdf for access to OTC LAN and maintain privileged accounts

1.6.7.6 Cybersecurity/IT Training: All contractor employees and associated sub-contractor employees must complete the DoD Cybersecurity awareness training before issuance of network access and annually thereafter. All contractor employees working cybersecurity/IT functions must comply with DoD and Army training requirements in DoD 8140.01, DoD 8570.01-M and AR 25-2 within six months of appointment to Cybersecurity/IT functions.

1.6.7.6.1 Information Assurance Contractor Training and Certification: DoD 8570 requires certifications for compliance, an approved IA certification based on your assigned IAT level and a Computing Environment (CE) certification based on the equipment and software you work with for your primary duties. The specific FAR clause for contractors, which references the requirement, is displayed below along with direct links to the DoD source.

DFARS 252.239-7001 Information Assurance Contractor Training and Certification.

Source Link:

(a) The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01- M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including:

(1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and

(2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.

https://portal.otc.army.mil/pubs/Miscellaneous%20Forms/OTC%20LAN%20Access%20User%20Agreement.pdf https://portal.otc.army.mil/pubs/Miscellaneous%20Forms/OTC%20LAN%20Access%20User%20Agreement.pdf

(b) Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

(c) Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

(d) Contractor personnel shall be IAT Level II certified for access on the DITTR system.

1.6.7.6.2 DoD 8570 IA Baseline Certification Requirement: For the DoD 8570 IA Baseline Certification you must have one of the certifications listed at the link below, based on the IA level your position is assigned.

Source Link:

https://public.cyber.mil/cwmp/dod-approved-8570-baseline-certifications

1.6.8 Safety: Contractor and associated sub-contractors shall provide a safe and healthful work environment for their employees as prescribed in FAR 52.236- 13, 29 CFR Part 1910, pertinent provisions local regulations, policies, and SOPS.

They shall safeguard public and Government personnel, property, and equipment, and avoid interruption of Government operations. The Contractor will report accidents or losses to the Contracting Officer as Specified in relevant regulations and standards. Whenever the Contractor becomes aware of serious or imminent danger to Government, civilian or Contractor personnel, the Contractor shall take immediate corrective action.

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance:

maintain written and oral communications with the Contractor concerning https://public.cyber.mil/cwmp/dod-approved-8570-baseline-certifications technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.11 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.6.12 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart

9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.13 Installation Access: The Contractor shall be responsible for assuring all Contractor personnel authorized to perform work under this contract obtain installation access. The Contractor and all associated sub-contractor employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures IAW OTC Memorandum 190-2. Employees performing services under this contract shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Directorate of Emergency Services, Security Office, or the host nation equivalent.

In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Governments Security Officer may require changes in Contractor security matters or processes. The CAC shall be returned to the COR when the employee no longer performs work for the Contractor under this contract.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. Contractor: A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. Contracting Officer: A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. Contracting Officer’s Representative (COR): An employee of the U.S.

Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.2. ACRONYMS:

Abbreviation Explanation

ACOR Alternate Contracting Officer's Representative

AFARS Army Federal Acquisition Regulation Supplement

AR Army Regulation

ATCTS Army Training & Certification Tracking System

ATEC Army Test and Evaluation Command

ATO Authorization to Operate

AuC Authentication Centre

BSC Base Station Controller

BSM Base Station Management

BSS Base Station Subsystem

BTS Base Transceiver Station

CAC Common Access Card

CDMA Code Division Multiple Access

CE Computing Environment

CFR Code of Federal Regulations

COLT Cell on Light Truck

COR Contracting Officer Representative

COTS Commercial-Off-the-Shelf

DA Department of the Army

DFARS Defense Federal Acquisition Regulation Supplement

DITTR Deployable Integrated Telecommunications Test Range

DMDC Defense Manpower Data Center

DoD Department of Defence

EDGE Enhanced Data Rate for Global Evolution

EVDO Evolution-Data Optimized

FAR Federal Acquisition Regulation

FTP File Transfer Protocol

IAW In accordance with

IEWTD Intelligence Electronic Warfare Test Directorate

GPRS General Packet Radio Service

GSM Global System for Mobile communications

GSN GPRS Support Node

HLR Home Location Register

HSDPA High Speed Downlink Packet Access

IA Information Assurance

IAM Information Assurance Management

IAT Information Assurance Technical

IP Internet Protocol

IPsec Internet Protocol Security

KO Contracting Officer

IT Information Technology

LMT Local Maintenance Terminal

LTE Long Term Evolution

MMS Multimedia Messaging Service

MSC Mobile Switching Centre

NACI National Agency Check with Inquiries

NIST National Institute of Standards and Technology

NSS Network and Switching Subsystem

OMC Operations and Maintenance Centre

OSS Operational Support System

PPS Public Packet Switched Network

PWS Performance Work Statement

RAN Radio Access Network

RF Radio Frequency

RMA Return Materials Authorization

RMT Remote Maintenance Terminal

RTT 1X Advanced for CDMA2000 Voice

SLA Service Level Agreement

SMS Short Messages Service

SMSC Short Message Service Centre

SOP Standard Operating Procedure

SSH Secure Shell

TCP/IP Transmission Control Protocol / Internet Protocol

UMTS Universal Mobile Telecommunications System

USAOTC U.S. Army Operational Test Command

PART 3

GOVERNMENT FURNISHED ITEMS AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES

3.1 Services: The Government will provide all day-to-day maintenance, and in case of a fault situation, the first level of diagnostics. This is to ensure the normal maintenance of the network and resolution of problems that are normal in the life of a network, such as without limitation replacing modules, fixing transmission problems, etc. are completed as per the Government’s normal operating practices. The Government shall designate as its system manager, a Government employee who has been trained and registered on the IEWTD support FTP Site.

3.1.1 Alarm and Event Monitoring: The Government will be responsible to regularly monitor the alarms and events on the networks. The Government will respond accordingly to live alarms on the network and take appropriate steps to alleviate the alarm conditions. Particular attention shall be given to critical alarms and any other alarms, which indicate a service outage.

3.1.2 Traffic Monitoring: It is the Government’s responsibility to monitor traffic on all live nodes within the network and to initiate investigation if any abnormal traffic behavior is noted.

3.1.3 Maintenance of Main Power: It shall remain the sole responsibility of the Government to ensure a reliable regulated source of main power is provided to all nodes and any supporting elements (e.g. network switches) in the network as per the specifications for each product.

3.1.4 Maintenance of Transmission Network: It shall remain the sole responsibility of the Government to maintain the transmission network required to provide communication between the various network elements.

3.1.5 Provision of Remote Access: The government is responsible for remote access to the network elements. Therefore during periods of Internet service outage, all support activities requiring remote access shall be suspended.

3.1.6 System Administration Tasks: The Government shall retain primary responsibility for executing the system administration tasks on the Operational Support System (OSS), Base Station Support System (BSS) and Network Switching Subsystem (NSS) nodes. These tasks include, but are not necessarily limited to, the following:

Weekly Database backups especially for mission critical databases (e.g.

OMC, HLR, AuC, SMSC, PPS)

Weekly backup

Periodic backups of entire system for mission critical nodes (e.g. MSC, BSC, GSN, OMC) so that full restoration is possible within reasonable time frame.

Update and maintain accurate network documentation (including network diagrams) and can be provided to the support contractor upon request.

3.1.7 Preventative Maintenance: The Government will perform preventative maintenance actions are systematically performed to maintain an operating network. The aim of preventive maintenance is to conduct periodic reviews of system performance. All systems shall undergo a system functional test regularly to check for proper operation. This will be accomplished by placing test calls in the selected region. Other preventative maintenance procedures are summarized here:

Cable check

Light Emitting Diode (LED) status check

Fan check

Radio check

Antenna check

3.1.8 Corrective Maintenance: The Government will take corrective maintenance is the set of actions and procedures necessary to return a faulty network to an in service state. These tasks include, but are not necessarily limited to, the following:

Implementation of configuration and parameter changes as advised by the contractor.

Performing software updates, that is, the application of software patches and/or upgrades which have been provided by the contractor. These tasks should be performed under the guidance of the contractor.

Replacement of faulty hardware units as advised by the contractor.

Verification of system performance after any of the above changes.

Maintenance of incident report log book.

3.1.9 Remote Access: The contractor requires direct internet access to the TLC Solutions Inc., supplied equipment in the Government’s network to permit remote fault analysis. The Government will arrange to provide the contractor with remote access using the RMT (see paragraph 3.2) through an IPsec tunnel to IEWTD. IEWTD would also need to supply the contractor with any passwords and user names on the designated servers for the purpose of remote system diagnosis.

3.1.10 Local Maintenance Terminal (LMT): IEWTD must have at its disposal on the network site at least one LMT for trace collection and System configuration. More than one may be required depending on the size of the network (i.e. one for each COLT). The LMT must be operational and have installed and configured an application for remote SSH access (e.g. PuTTY, Team Viewer).

3.2. EQUIPMENT: Remote maintenance Terminal (RMT). The Government shall supply the contractor with a Government owned maintenance terminal (laptop) and router as Government Furnished Property (GFP), TE B to be accessed at the contractor’s primary business location. This will ensure a secure tunnel to the Government’s DITTR system for the contractor to remotely access for trouble shooting purposes in accordance to Government Cybersecurity Standards. The RMT will be maintained in compliance IAW any authorization to operate (ATO) obtained for the DITTR. As such, it will be incumbent on the Contractor to adhere to and implement all required Security Controls for the RMT, including a subset for which compliance responsibility will fall specifically on the Contractor. Primarily, this subset of controls will fall within the Physical and Environmental control family found in NIST Special Publication 800-53 Rev 4, but may include other controls as necessary.

3.2.1 Government Furnished Property (GFP): The Contractor shall develop a Property Management System (PMS) In Accordance With (IAW) FAR Part 45 and FAR 52.245-1. The PMS shall be submitted thirty (30) days after full contract performance and shall detail Contractor activities concerning GFP control in the following areas: Property Management; Acquisition; Receiving;

Identification; Records; Movement; Storage; Physical Inventories; Reports;

Consumption; Utilization; Maintenance; Subcontractor Control; Disposition; and Contract Close-out as pertinent. The Contractor shall establish and maintain an acceptable property management system. Failure to maintain an acceptable property management system, as defined in DFARS 252.245-7003, may result in disapproval of the system by the Contracting Officer and/or withholding of payments.

3.2.2 The contractor shall include within its property management plan, a process for the accountability and management of all GFP. Contractors in possession of classified or Controlled Cryptographic Item (CCI) GFP shall dispose of the classified contractor inventory in accordance with applicable security guides and regulations or as directed by the KO. Contractor GFP identified as inherently dangerous to public health or safety shall not be disposed of unless rendered innocuous or until adequate safeguards are provided.

3.2.3 The contractor shall include within its property management procedure, a process for the accountability and management of Government-owned scrap.

The process shall, at a minimum, provide for the effective and efficient disposition of scrap, including sales to scrap dealers, so as to minimize costs, maximize sales proceeds, and, contain the necessary internal controls for mitigating the improper release of non-scrap property. The contractor may commingle government and contractor-owned scrap and provide routine disposal of scrap, with plant clearance officer concurrence, when determined to be effective and efficient.”

3.2.4 A joint inventory of Government-furnished equipment must be completed within two weeks after the contract effective date. The Contractor shall sign a property listing for all equipment provided by the Government. Items of equipment missing or not in working order shall be recorded and the COR shall be notified in writing. The Contractor and the Government representative shall jointly determine the working order and condition of all equipment and document their findings. Rejection of GFP by the Contractor shall not relieve the Contractor of responsibility in performance of this contract. The Contractor shall not use property provided by the Government for any purpose other than the performance of this contract. The Contractor shall conduct annual inventories and complete required documentation in accordance with DoDI 4161.02.

3.2.5 Pursuant to the property clauses in this contract the Contractor is required to perform a joint Government/Contractor inspection of all GFP. This inspection is intended to establish a mutual agreement as to the condition of GFP provided to the Contractor for use in performance under this contract. In addition, the Contractor is required to conduct an automated annual inspection for all GFP and Contractor Acquired Property (CAP). The annual GFP and CAP inspection shall be completed and annually submitted in a property master report ninety (90) calendar days prior to end of POP in accordance with Contract Data Requirements List (CDRL) A001.

3.2.5.1 CAP will also be Item Unique Identification (IUID) marked and registered IAW DFARS 252.211-7003. Contractors shall be required to identify the Government’s unit acquisition cost for all deliverable end items to which item unique identification applies. If CAP items are subsequently delivered to the Government under terms of the contract, via a contract line item number (CLIN), then the requirements imposed on the contractor for both DFARS 252.211-7003 and 252.211-7007 apply to both GFP and CAP.”

3.2.5.2 Reporting of GFP: The contractor shall update the IUID Registry as transactions occur or as otherwise stated in the Contractor’s property management plan. The Contractor shall annually provide 90 days prior to the end of the POP, a master report of GFP and CAP in accordance with CDRL A001.

3.2.5.3 The contractor must maintain and provide utilization reports to authorized Government personnel as needed. Requirements for use and reporting shall be included as CDRL A001 in this contract.

3.2.6 The Government reserves the right to furnish parts, supplies, materials, and equipment when deemed to be in the best interest of the Government. If determined liable, the Contractor shall be financially responsible for replacement costs of all lost, stolen, or damaged property that is furnished upon contract award or during the duration of the contract.

3.2.7 Management of Government-Furnished Property: The Contractor shall manage GFP in accordance with Parts 45 and 52 of the FAR. The Contractor shall be liable for shortages, loss, damages, or destruction of Government property in accordance with the property clauses in Section I of the contract and the Financial Liability Investigation. Within fifteen (15) calendar days of discovering the item is missing, damaged or destroyed, the Contractor shall appoint a point of contact who is responsible for initiating the Financial Liability Investigation. As soon as the GFP is no longer required, it shall be promptly turned in IAW the approved Property Control Plan.

3.2.8 Final Inventory: At the completion of the contract, the Contractor and Government representative(s), including a Government Property Book representative, shall conduct a joint inventory. The Contractor shall be liable for loss or damage to GFP beyond fair wear and tear.”

3.2.9 The Contractor shall not use property provided by the Government for any purpose other than in the performance of the contract IAW FAR 52.245-9.

Exception being, the allowable personal, and/or non-job related provisions as set forth in current Acceptable Computer Use Policies.

3.2.10 Tagging, Labeling, and Marking of GFP: The Contractor shall tag, label, or mark GFP items identified in the contract as serially-managed items (as required by DFARS 252.245-7001). The Contractor is not required to tag, label, or mark GFP previously tagged, labeled, or marked.

3.2.11 Loss of GFP: The contractor shall report the loss of Government property as required by DFARS 252.245-7002. The Contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation. The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to theft, inadequate storage, lack of physical security, or “Acts of God.” This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this contract.

3.2.12 The contractor shall provide inspection, audits, surveys and requests for information, as necessary. This access includes all site locations and, with the Contractor’s consent, all subcontractor premises. The contractor shall provide to the COR, without prior notice, supporting documentation as needed for Army Audit Readiness and other audits, in accordance with FAR 52.245-1(g).”

PART 4

CONTRACTOR FURNISHED ITEMS

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 GENERAL: The Contractor shall furnish all supplies, equipment, and services required to perform work under this contract that are not listed under Section 3 of this PWS.

PART 5

SPECIFIC TASKS

5. SPECIFIC TASKS:

5.1 BASIC SERVICES: The contractor shall provide services listed in the table below with a description of each of the expected services listed in the subsections below.

Table 1 lists the expected services that shall be provided under the performance work statement.

Services and Deliverables

IEWTD Support FTP Site access Included

IEWTD Information Services Included

Trouble Ticketing service Included

Remote Troubleshooting service Included

Software Maintenance releases Included

Periodic Software Upgrade service Included

Return Materials Authorization (RMA) Service Included

Advance RMA Service see para 5.2.7

Table 1: Expected Services and Deliverables

The Contractor shall provide the Standard Support Service during normal business hours, except those listed as critical faults during mission support times that include the following services:

Provide the Government with access to a hotline and/or email from where they can create trouble tickets.

Provide the Government with access to a support FTP Site where information services are available. (i.e. Technical Notes, Documentation, Manuals, Software Downloads, etc.).

Normal working hour management and maintenance of operational interface with IEWTD.

Technical telephone support with direct access and a one-hour response time. 24x7 for critical faults during IEWTD mission support of operational testing.

Technical telephone support with direct access during normal business hours for all other level of faults as per section 5.3.2.

Track and manage all open IEWTD issues.

Escalation of service affecting issues to other contractor departments (e.g.

R&D) and senior management where necessary.

Provide contractor departments with information to permit efficient management of escalated issues.

Manage and progress work-around solutions for technical issues where possible.

Provide the Government with detailed analysis of status of each action for significant service affecting events, conforming to pre-agreed requirements and template.

Develop and execute agreed upon action plans where necessary.

Participate in conference calls with the Government when necessary to discuss resolution plan for urgent/critical problems.

Implementation of configuration changes and/or parameter changes on IEWTD’s network where approved by the Government.

5.2 EQUIPMENT: This section lists all the equipment covered by this PWS.

Unit / Subsystem Qty Description

MSC CORE (PMN) 1

LOC: COLT 1 Supports GSM/UMTS/LTE w- SMS, MMS, DATA @ 50 Active Subscribers (EDGE, HSPDA, LTE 5x5, 10x10, or 20x20

MIMO)

MSC CORE (Star Solutions)

LOC: COLT 1 Supports CDMA 1xRTT and EVDO w-SMS + DATA @ unlimited subscribers (no MMS support)

MSC CORE (Quortus) 1

LOC: COLT 4 Supports GSM/CDMA/UMTS/LTE w-SMS, MMS, DATA @ 50 Active Subscribers (EDGE, 1xRTT, EVDO, HSPDA, LTE 5x5, 10x10, or 20x20 MIMO)

GSM 900 BSS 3 LOC: COLT 4, 3 Sectors w/2-TRX ea.

GSM 1800 BSS 3 LOC: COLT 4, 3 Sectors w/2-TRX ea.

CDMA 1xRTT BSM 1 LOC: COLT 1

CDMA EVDO BSM 1 LOC: COLT 1

CDMA 1xRTT/EVDO Combined BSM

1 LOC: COLT 4

CDMA 850 1xRTT BSS 8 LOC: COLT 1,2,3, & 4

CDMA 850 EVDO BSS 8 LOC: COLT 1,2,3, & 4

UMTS 900 Node B 8 LOC: COLT 1,2,3 & 4

LTE 2600 eNode B 4 LOC: COLT 1 & 4

Extended warranty for equipment below to start September 1, 2020.

GSM 900 BSS 3 LOC: COLT 1, 3 Sectors w/2-TRX ea.

GSM 1800 BSS 3 LOC: COLT 1, 3 Sectors w/2-TRX ea.

5.2.1 IEWTD Support FTP Site Access: A contractor provided IEWTD Support FTP Site shall be the primary gateway to all contractor support services other than trouble ticketing services. The Government can apply for registration on the support site. Once approved, IEWTD will receive a unique username and password to access the site. The account shall be valid for the duration of the contract. If the Government elects to exercise an option year, the account expiration dates will be extended so it’s not necessary to re-register each year.

5.2.2. IEWTD Information Services: Government Information services shall be available via the support FTP Site. Once logged in, the Government can access product documentation, user manuals, technical notes, white papers, etc. for existing contractor supplied hardware/software.

5.2.3 Trouble Ticketing Service: The contractor shall provide a hotline and/or email service for IEWTD to submit and manage all Government related trouble tickets for the DITTR system. The service should allow for easy escalation of tickets to the appropriate departments such as to development and/or integration engineers where necessary. Full ticket history should be accessible to the Government through this service even after tickets are closed. All Government trouble tickets should be maintained on the contractor’s internal issue tracker database.

5.2.4 Remote Troubleshooting: Most DITTR hardware implements TCP/IP for communication with each other and with the outside world, this enables remote access to most network elements to be maintained by the support contractor.

This will allow support contract engineers to perform advanced troubleshooting of complex network problems remotely. Full firewall protection is also used within the gateway nodes to ensure the Government IT security is not compromised.

Interoperability with the Government firewalls and compliance with the Government Cybersecurity policies referenced in DoDI 8510.01 and DoD Directive 8570.01 & 8140.01 is required.

5.2.5 Software Maintenance Releases: It is expected that the contractor may release software patches or maintenance builds which contain bug fixes and/or minor feature enhancements. Such software maintenance releases shall be included in the PWS. The software builds along with release notes and upgrade procedures are made available via the Software Downloads section of the Government Support FTP Site or directly sent over a Government secure portal.

5.2.6 Return Materials Authorization Service: The contractor shall provide a full RMA service for all hardware warrantied by the contractor. This service should be integrated with the contractor’s Issue Tracker so the Government can track progress of RMA in the same way as any other trouble ticket. For the regular RMA service the Government must ship the faulty item to the contractor where it will be repaired or replaced and sent back to the Government.

5.2.7 Advance RMA Service Availability: The advance RMA service (loaner program) differs from the standard RMA service in that a replacement item could be shipped to the Government before the faulty item is returned to the contractor or repaired by the contractor in case of critical problems that are effecting ongoing missions. This will be a best effort based on availability of hardware on hand at the contractor’s facilities. A charge may apply for advance RMA services provide by the contractor (i.e. shipping, handling, leasing fees).

5.2.8 Software Upgrade Service: The software upgrades along with release notes and upgrade procedures are directly sent over a Government secure portal. Trained contractor engineers will upload the software to the network elements and perform the upgrade remotely.

5.3 Technical Faults and Queries: The Government is responsible for screening all faults and queries to try to identify the source of a problem. In cases where the problem is deemed to be due to a malfunction of the contractor’s equipment/software, a trouble ticket shall be opened through the contractor’s Trouble Ticket hotline or email service detailing the problem. For Critical severity issues this should be immediately followed up with a call to the 24x7 support line.

5.3.1. The Government will submit a separate trouble ticket via the contractor’s Trouble Ticket hotline/email service for each item. Trouble tickets which cover multiple items shall be broken into multiple tickets. If duplicate tickets covering the same problem arise, these shall be closed by the contractor.

5.3.2. On receipt of an official service request, the contractor will allocate a unique case reference number which should then be used on all future correspondence about that issue. A contractor support engineer will analyze the service request and assign the issue to an appropriate support engineer who will then commence investigation of the request.

5.3.3. IEWTD should select the appropriate priority for the issue – i.e. Critical, Major, Medium or Minor (see 5.3.4 for definition of each priority). All non-service affecting issues will be classed as Medium or Minor. Thereafter IEWTD should be able to follow the progress and status of the ticket via email and/or telephonically.

5.3.4. Problem Levels and Service Priority Classification: The Government shall be the primary interface to the End User and will provide First level support to the End User; the contractor will provide Second and Third Level support.

5.3.4.1 Critical and Emergency Faults: An extreme condition which causes a significant service outage with considerable restrictions on End Users or the whole of the system, typically affecting core product functionality, including but not limited to, loss of call-processing, loss of the ability to record call data records and loss of a critical management system during an ongoing IEWTD support mission.

5.3.4.2 Major Faults: This class of problem is service affecting but system retains 70% or more of its service capacity. The system is operable for core functionality, but at a reduced level requiring immediate attention.

5.3.4.3 Medium Faults: Medium faults are conditions that do not notably impact service to End Users but are nonetheless causing significant inconvenience to the Government.

5.3.4.4 Minor Faults: Minor faults are conditions that do not significantly impair the functionality of the system and do not affect service to End User.

5.4 Data Collection Requirements: In many cases, log files or traces from the Government’s network will be required to assist the contractor in troubleshooting a problem. In some cases the contractor may be able to retrieve the required files using the remote access provided by IEWTD. However, in other cases it will be necessary for the Government personnel to capture these traces and attach them to the issue on the Support FTP Site. In such cases, an issue may be placed in the “IEWTD Pending” status while the contractor awaits delivery of these traces from IEWTD.

5.5 Response TImes:

5.5.1 Definitions: The Response Time is the time taken by the contractor personnel to respond to the initial IEWTD call about a problem. This response may take the form of a phone conversation, an email to the Government or an SMS text message.

The Workaround Time is the time taken by the contractor personnel to implement a workaround, which resolves the problem temporarily or at least reduces the severity of the problem to a lower level. The Workaround Time does not include the time taken by the Government in the collection and return of data and materials requested by the contractor and required to troubleshoot the problem.

The Restoration Time is the time taken by the contractor to implement a solution which resolves the problem permanently. The Restoration Time does not include the time taken by the Government in the collection and return of data and materials requested by the contractor and required to troubleshoot the problem.

5.5.2 Response and Restoration Time Schedule: The table below lists the response and restoration times to which the contractor shall be committed as part of this PWS. Restoration times are by their nature extremely difficult to accurately predict as they depend on the time taken to successfully diagnose the cause of a problem which varies greatly depending on the complexity of the problem. Hence restoration times below indicate the time taken to reduce the severity of the problem or to restore the network to pre-existing conditions. This may be achieved by work around solutions and/or by reverting to a previous software release.

The Response Time, Workaround Time and Restoration Time for addressing different problem levels are shown in Table 3. For additional information about problem levels, see section 5.3.4.

Problem Level

Response Time Workaround Time

Restoration Time

Critical Within 60 minutes

Within 8 hours Within 5 business days.

Major Within 4 hours Within 48 hours

Within 10 business days

Medium Within 8 business hours

Within 10 business days

Next scheduled…

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 .