PWS Rail ITV RFI DRAFT.pdf

PERFORMANCE WORK STATEMENT

MILITARY SURFACE DEPLOYMENT & DISTRIBUTION COMMAND

DODX RAIL CAR IN TRANSIT VISIBILITY

Rail Car In-Transit Visibility (RITV)

Performance Work Statement (PWS)

For

The Defense Freight Rail Interchange Fleet (DFRIF)

Date Year

Table of Contents

1. BACKGROUND AND SCOPE

2. REMOTE MONITORING DEVICE (RMD) REQUIREMENTS

3. INSTALLATION OF RMDS

4. DATA AND NETWORK SERVICE

5. GENERAL INFORMATION

6. PERFORMANCE

1. BACKGROUND AND SCOPE

1.1 Background

1.1.1 The Surface Deployment and Distribution Command (SDDC) Rail Fleet Management Branch manages the daily operations and maintenance of the Defense Freight Rail Interchange Fleet (DFRIF). The DFRIF consists of roughly 1,700 Department of Defense (DoD) owned chain flat rail cars. SDDC is seeking a modernized technology to allow for advanced real-time information and monitoring of assets beyond the current transportation service providers (rail carriers) car location messages.

1.1.2 SDDC’s Rail Fleet Movement Branch requires real time reporting and tracking of DODX rail cars. Real time tracking will allow for improved ITV, a Real Time Common Operating Picture (COP), data for incident investigations, and shop repairs monitoring. Implementation will also lead to enhanced safety, security, and accountability of the DFRIF and provide units with ITV of equipment moving by rail in the Continental United States (CONUS).

1.2 Scope

The Rail Fleet Management Branch requires rail car tracking devices for approximately 1,700 DODX cars located in the Continental United States (CONUS), installation of the devices on the rail cars, and data service for the devices. The Contractor shall provide data services that can also be incorporated into the current DoD systems for monitoring surface movements.

2. REMOTE MONITORING DEVICE (RMD) REQUIREMENTS

2.1 ITV Transmissions

2.1.1 The contractor shall provide a RMD that can capture and transmit near real time ITV with reporting by way of contractor website and API transmission to the data platform required by SDDC as outlined in paragraph 4.2.

2.1.2 RMDs shall provide reporting data every fifteen (15) minutes while the device is in motion, and every thirty (30) minutes when the device is at rest. RMDs will be programmed with an energy conservation mode to limit battery drain and minimal reporting while at rest for periods greater than 90 minutes. If the RMD is at rest for extended periods (6 hours or greater), the RMD will be in sleep mode and only report when impacted, tampering is detected, or movement begins again.

2.1.3 In addition to location and movement data, the device shall be able to detect and report the following to SDDCs data platform:

a) An impact event of greater than 1.5G force and aft or side to side motion.

b) The load status of the rail car (i.e. loaded or empty) by means of a vertical sensor.

c) A tampering event when a sudden impact greater than 4 G or a constant oscillating movement occurs that indicates an attempt to remove the device by prying.

2.2 Device Specifications

2.2.1 RMDs shall be no larger than 15 inches long, 4 inches wide, and 2 inches thick including any mounting hardware.

2.2.2 The device shall be capable of over-the-air software updates and be mesh network capable. It shall have position accuracy of within 50 feet.

2.2.3 The RMD battery shall have a life of at least 5 years. The battery life shall be monitored by status updates on the contractor webpage or reports generated by the device showing life remaining and any battery malfunctions to include overheat conditions.

2.2.4 RMD assemblies shall conform to the requirements of the Association of American Railroads (AAR) and all Federal HAZMAT/HERO requirements and specifications. Devices shall meet, at a minimum compliance, with the following standards in Table 1 below:

Table 1. MILSTD/HERO Requirements

ISO/IEC 17025:2005€ General Requirements for the Competence of Testing and Calibration Laboratories, 5/15/2005

ANSI C63.4-2003, American National Standard for Methods of Measurement of Radio- Noise Emissions from Low-Voltage Electrical and Electronic Equipment in the Range of 9 kHz to 40 GHz, dated 2003

332438-1TRFWL, Test Report for Intentional Radiator Tests According to FCC Part 15C and Industry Canada Requirements, dated 12/22/2017

47 CFR Part 15, Subpart B, Code of Federal Regulations, Federal Communications Commission (FCC) for Unlicensed Broadcast and Spurious Emissions of Telecommunications Equipment

Air Force Instruction Manual 91-208, Hazards of Electromagnetic Radiation to Ordnance (HE-RO) Certification and Management, dated 5/16/2008

MIL-STD-464, Electromagnetic Environmental Effects Requirements for Systems, Rev. C dated 12/21/2010

NAVSEA OP3565, Electromagnetic Radiation Hazards to Personnel, Fuel, and other Flammable Material, dated 2/1/2003

MIL-HDBK-240, Hazards of Electromagnetic Radiation to Ordnance Test Guide, Rev. A dated 3/10/2011

DoDI 6055.11, Protection of DoD Personnel from Exposure to Radio Frequency Radiation and Military Exempt Lasers, dated 2/21/1995

2.2.5 Contractors shall provide RMDs with the ability to withstand harsh weather and environmental conditions related to rail operations to include temperature operating ranges of -30°F to 180°F and altitudes up to 15,000 feet above sea level.

2.2.6 A mounting device shall be used to mount the RMD to the side of the DODX rail car.

The RMD shall be affixed to the mounting device with hardware to allow removal for servicing and battery replacement.

2.2.7 A label shall be placed onto the RMD or within proximity to identify the RMD as being property of the “United States (U.S.) GOVERMENT" and containing sensitive monitoring instruments. The label shall contain a “WARNING” in large red letters with a description of handling requirements to ensure the RMD is not damaged during loading or unloading operations at installations by MHE, such as forklifts. The contractor’s proposed warning label shall be approved by the SDDC Rail Fleet Management before production and affixing to DODX rail cars.

3. INSTALLATION OF RMDS

3.1 Installation of RMDs on DODX cars shall be the responsibility of the contractor when the service is ordered by the government. The Rail Fleet Management Branch will identify locations where rail cars are aggregated and coordinate installation with the contractor.

3.2 The mounting bracket may attach to the DODX car by being bolted/screwed into place or by the use of epoxy. The RMD shall be mounted on the side of the rail car offering least exposure to damage from material handling equipment (MHE). Refer to Figure 1.

Figure 1. Remote Monitoring Device Location

3.3 Installation Access

3.3.1 The contractor will be required to enter and work on U.S. Government military installations. The contractor is responsible for its employees, to include subcontractors, and will comply with access and control procedures, to include background checks, personal inspections and vehicle inspections as required by the installation.

3.3.2 The contractor is responsible for coordinating installation access requests with the installation where the DODX rail cars are located. These locations could include military installations, (e.g. Fort Bliss, TX, National Training Center (NTC), CA) or ports where SDDC operates (e.g. Charleston, SC or Beaumont, TX).

3.3.3 The contractor shall coordinate safety requirements for locking out tracks with the Installation Transportation Officer (ITO) to ensure work can be performed when installing the RMDs on DODX rail cars.

3.3.4 The contractor is responsible for supplying all safety equipment for its employees engaged in performing work on DODX rail cars. At a minimum the following safety equipment is required when working on military railhead locations: steel toed boots, long sleeve shirt, hard hat, high visibility vest or outerwear, protective eyeglasses, and applicable hearing protection.

3.4 Activation of the Device

3.4.1 The contractor will activate the RMD at time of installation and associate the DODX car number with the RMD installed on the rail car. The activation is also the process of registering the device with cellular and/or satellite networks for tracking purposes.

3.4.2 The contractor will invoice monthly for the data service after tags have been activated.

The government will pay a prorated usage fee for cellular service based on the day activation occurs in the monthly billing cycle.

3.5 Daily Installation Reports

During installation operations, the contractor shall provide a report daily of the devices that were installed and activated on that day. The report will include the rail car number and device number.

3.6 Location of Cars and Installation Timelines

3.6.1 It is the government’s intent that all DODX cars will be equipped with RMD’s within 1 year of the initiation of the contract.

3.6.2 Installation of RMD’s on DODX rail cars will require traveling to many different locations as DODX cars are in constant demand and routed to several military installations and commercial facilities daily. SDDC Rail Fleet Management Branch will coordinate directly with the contractor in identifying locations of concentrated DODX rail cars to facilitate the installation process.

3.6.3 Replacement RMD’s will be installed within 90 days of RMD failure or loss of RMD transmission if the car is in a location where the contractor is able to install.

3.6.4 The contractor may invoice for travel expenses when traveling to locations for device installation. If travel is necessary, the contractor shall invoice travel expenses based on mileage rates and per diem rates as established in the JTR at the time of travel. If it is more beneficial to the government for contractor personnel to fly and rent a car, the contractor shall provide cost information to the CO for approval before travel can be booked.

4. DATA AND NETWORK SERVICE

4.1 Required Data Elements

All RMD’s shall provide the following minimum data elements:

Globally Unique Tag Identifier: example 21234567890123 (14 numeric characters)

Position Coordinates: Latitude: 49.46470 ; Longitude: 17.69983

Battery Capacity Percent Remaining: example 45%.

Transmission type: C (cellular) or S (satellite).

4.2 Data Interfaces

4.2.1 The Contractor shall establish an interface with government systems within 30 days of the start of contract performance.

4.2.2 The Contractor shall comply with the security and interoperability requirements specified for data exchanges between the necessary systems. Existing Interface Requirements Documents and/or Interface Control Documents shall be used as the baseline for data interfaces to Government systems.

4.3 Web Based Access

4.3.1 The contractor shall provide secure account access as requested by the COR. The contractor will establish user accounts within 3 business days of request from the COR. The COR will provide the contractor with necessary information for the contractor to establish new accounts and grant access.

4.3.2 The website will offer the following: interactive map with trip timeline, geofence management with alerts upon enter/exit, asset historical data that can be queried through running reports, information pertaining to RMD dwell, mileage and utilization.

4.3.3 The contractor website shall be capable of producing reports, running queries concerning history files/events, providing alerts via email for selectable events such as entering/exiting defined geofences or impacts and start/stop times.

4.4 Cellular Service

The device shall have broad access to cellular networks, enabling coverage at military installations and ports across the country.

5. GENERAL INFORMATION

5.1 Operations Security (OPSEC).

Information provided during work performance shall only be released to personnel/entities who provide specific services in support of the contract. The contractor shall implement

Impact detection events

Tamper detection events

Event Date Time: 2018-04-25T18:30:21 CST.

Radio & EMC Certification: PTCRB, GCF, CE, FCC, IC appropriate safeguards to mitigate against the release of said information to third parties not participating in work on this contract. In any case where there is uncertainty or ambiguity, regarding OPSEC protocols, the contractor shall consult the COR and/or Contracting Officer for a resolution.

5.2 Damage, Accident, and Loss Reporting.

5.2.1 The contractor shall immediately notify the COR of any incident and/or accident that results in injury or death to any personnel, damage to cargo or property, or hazardous spills or leaks, during or arising from performance under this contract.

5.2.2 The contractor shall submit an accident report within 24 hours with the following information:

• Status of injured personnel

• Pictures of affected equipment

• Training certificates/licenses for personnel involved in incident

5.2.3 Accident Information required from Contractor within 30-Day (or sooner if investigation is complete) Information required from Contractor

• Findings identifying the root cause(s) of the accident

• Corrective actions taken to prevent recurrence

• Follow-on status of any injuries from 24-hour status

• Final incident report from Contractor’s safety representative to COR

5.2.4 The contractor will be liable for any damage they cause to government property during the course of installation operations.

5.3 Contract Management

5.3.1 The Contractor shall provide at a minimum one contract manager and one alternate who shall be responsible for the performance of the work and all coordination with the government. The Contractor shall provide telephone numbers and email addresses for each of the contract managers. The contract manager and alternates shall have full decision-making authority to act for the Contractor on all matters pertaining to the performance of services under this contract.

5.3.2 When installing devices at government directed locations, the contractor shall provide a POC for each installation team that will be accessible by telephone to the COR.

5.3.3 The Contractor shall meet monthly with the COR to discuss verbal reports of contractual problems, actual or anticipated, as identified with a monthly written report reflecting unresolved conditions or negative reports. Written reports or records (meeting minutes) shall be required for any commitments made between the U.S. Government and the Contractor.

5.4 Work Hours

The government will not require the contractor to work outside of normal workday hours under normal circumstances. If the contractor chooses to work overtime, night or weekend hours in support of the contract, the government will not reimburse the contractor for additional labor costs. If the government does require the contractor to work outside of normal hours, any premium hours must be approved by the CO in advance.

5.5 Ordering

5.5.1 When the Rail Fleet Management Branch identifies an installation location and timeline, they will notify the contractor and the Contracting Officer of the number of cars and location.

The Contracting Officer will issue the task order to the contractor.

5.5.2 The task order will include the number of required devices (i.e. the number of cars the government intends to install tags on), the location of the cars, and the timeline for when cars will be positioned at the location. The contractor will be given 14 days’ notice at a minimum.

5.5.3 The government intends to issue task orders for installation of no fewer than 50 rail cars at a time.

5.5.4 When needed, the government may order devices to be shipped to locations where the government or its agent will install the device. The contractor shall ship devices to identified locations within 5 days. The contractor may invoice the cost of shipping.

5.6 Replacement of Malfunctioning Devices

When a device within the required life expectancy malfunctions or no longer works as described in Section 2, the contractor shall ship a replacement at no cost to the government. Replacements will be shipped within 5 days.

5.7 Invoicing

5.7.1 The contractor shall submit invoices by email to the COR and CO for review and approval. Invoices shall include all applicable information IAW FAR 52.212-4(g).

5.7.2 The contractor may include the cost of the tag, installation, shipping and per diem for travel on the same invoice with the data service or may invoice them separately.

5.7.3 Invoices will not be processed for payment until all of the required billing or certifying documentation is received.

6. PERFORMANCE

6.1 Deliverables

The contractor shall deliver data as set forth in the below table. All deliverables shall be submitted electronically via e-mail to the COR, Contracting Officer, and Contract Specialist.

Insert Delivery Table

6.2 Performance Requirements Summary (PRS)

The PRS represents the most important objectives that, when met, will ensure performance under the contract is satisfactory. Although not all PWS requirements are listed in the PRS, the contractor shall comply with all requirements in the PWS.

Performance Objective Performance Measure Performance Standard

Acceptable Quality Level

(AQL)

Rail cars equipped with functioning RMDs as ordered

Percentage of railcars with actively reporting RMDs after contractor installation

100% 99%

Real-time location data accuracy

Percentage of location data points within 50 feet of actual location

99% 95%

Paragraph Deliverable Delivery Schedule

2.1 ITV Transmissions

3.1 Installation of RMDs

3.5 Daily Installation Reports

4.2.1 Data Interface Established

4.3.1 User Accounts Established

4.6 Service Coverage

5.2.2& 5.2.3

Accident Reporting

5.3.1 Contract Manager POC

5.3.2 Installation POC

5.3.3 Monthly Meeting

5.6 Device Delivery

Performance Objective Performance Measure Performance Standard

Acceptable Quality Level

(AQL)

System uptime Percentage of time the contactor system is operational and providing data

99.5% 99%