AUTOMATED_DEBRIS_MANAGEMENT_SYSTEM.pdf

PDF 62 KB Posted

Attached to
Advanced Contract Initiative (ACI) Regional Contracts for Debris Management Services (RCDMS) DRAFT PWS
Solicitation number
W912EK18R0022
Issued by

About this file

This document provides a draft performance work statement (PWS) for a regional contracts for debris management services solicitation and outlines requirements for an automated debris management system. The PWS seeks emergency debris removal services across multiple states. Contractors must provide an automated system to register hauling vehicles and equipment, generate load tickets electronically, and consolidate data for billing and reporting. The system requires capabilities such as truck certification with images and volumes, electronic ticket generation with location and time details, and real-time statistics on debris removal amounts and completion percentages. It must also integrate with GPS and GIS technologies to track haul routes and support auditing of contractor invoices, government documentation, and applicant payments. The draft PWS requests industry feedback through a ProjNet bidder inquiry process by July 19, 2018 to inform the final solicitation.

Automated Debris Management System (ADMS)

View the file

Other files

File Type Posted
2018_ACI_Debris_DRAFT_PWS.pdf PDF

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

AUTOMATED DEBRIS MANAGEMENT SYSTEM (ADMS)

(Pronounced Adams)

The purpose of this section is to provide specifications for an automated debris management system to be utilized in disaster debris management missions tasked under the Debris ACI Contract(s). The Government shall be provided access to the Government approved ADMS. The ADMS must meet the following performance characteristics:

a. Truck certification is used to register debris hauling vehicles and equipment. At a minimum, the following must be included:

• A means of electronically registering debris contractor vehicles and equipment

• Link electronic registration to digital images

• Identify mission/contract number

• Generate unique ID’s for contractor vehicles and equipment

• Utilize uniform measurements e.g. feet and inches to calculate vehicle volume

• Capture driver’s and certification team member’s unique identification numbers

• Capability to recertify vehicles and record in an audit table

• Certification data must be associated to authorized system user

• Reject vehicles which are not associated with current mission/contract

• Capture vehicle audit records

• Create a printed certification record

• Provide administrative reporting capabilities

b. The ticket/tower applications must incorporate system operator credentials. At a minimum, this should include:

• Ticket/tower monitor electronic registration

• Generate unique ID’s for registrants

• Link designated ticket/tower personnel roles to a specific mission

• The ability to edit ticket/tower personnel roles i.e., create, update and delete

• Store ticket/tower personnel contact information relative to the mission

• Track and Manage ticket/tower personnel role and status

• Reject invalid ticket/tower personnel credentials

c. The system must generate an electronic load ticket at the point of debris loading into the transport container. Any method of ticket generation (, smart card, RFID, or other methods) is acceptable, provided ticket issue is controlled. At a minimum, the system must produce a load ticket data record including the following characteristics:

• Position of loading point

• Date and time of ticket initiation

• Date and time of ticket completion

• Truck identification

• Mission/Contract number

• Ticket initiator personnel credentials

• Acknowledge successful data capture

• Record digital images of debris, location, and / or other images selected by user.

• Records Right of Entry or work order number if applicable

d. Completed Right-of-Way (ROW), ROE and Per-Unit point of origin transactions must be received at the approved disposal site. At a minimum, the disposal site management application must provide the capability to:

• Identify site configuration data such as, but not limited to, name, location, debris type, etc. at the beginning of each work day

• Display certification data and photo for ticket/tower personnel to perform a field audit of truck/trailer to assure they matches certification and placard number

• Designate debris type

• Record debris volume (based on unit of measure for the contract task order)

• Create load data record in internal storage

• Continuously calculate and present real-time disposal site statistics

• provide electronic load ticket receipts for backup and auditing purposes

• Store data locally and transmit transaction data as quickly as possible based on communication availability

• Associate ticket/tower personnel credentials with each received load

e. Other Miscellaneous requirements

• Minimal elements of the traditional debris load ticket (debris type, load call, and ROE number) are entered

• Uses Global Positioning System (GPS) & Geographic Information System (GIS) technologies to automatically determine the most direct haul route from loading site to disposal site and records mileage

• Evaluation of daily event status, production information, and performance information using web-based reporting, off the shelf software, and GIS tools

• Coordination of contractor invoices, FEMA documentation and applicant payment processes enabled through an integrated database management system

f. Perform administrative functions, verify vehicle audit information, display real-time collection volumes, and review ticket/tower personnel GPS audit logs. At a minimum, the field administrative applications must provide the capability to:

• Change ticket/tower personnel identification badge roles and responsibilities

• Review total CY counter value

• Audit vehicle certification data

• Validate/Invalidate equipment and personnel

• Reinitiate security sequence for ticket/tower personnel

• In tabular format, display the results of ticket/tower GPS audit files by limiting access to the internet data

g. Tower Site Monitor

• The tower/site monitor will be stationed in the inspection tower and estimate the quantity of debris contained in the truck or trailer in Cubic Yards (CY). Each truck or trailer will have the measured hauling capacity in CY recorded on the side of the truck or trailer. That number should be validated with the quantity state in the appropriate location on the upper portion of the load ticket

• The tower/site monitor will record the name and the arrival time of the truck and confirm the type of debris in the truck.

• The tower/site monitor will record the estimated volume of debris contained within the bed of the truck or trailer in CY, under “Unloading Information” on the load ticket. The monitor must print sign his/her name in the designated block of the load ticket.

• The tower/site monitor will enter load ticket information into the approved ADMS database.

• Load tickets are controlled forms and cannot be lost since they are used to verify the invoices submitted by the contractor to the Government.

• The Government QA and/or COR will verify the load quantity before permitting any truck to proceed from the tower entrance to the dumping location.

• The tower/site monitor will document the truck is emptied and verify the departure time of the truck on the load ticket.

• This information shall be provided on a daily basis to the COR.

h. Provide specified data established by the KO. Data may include but is not limited to:

• Debris Hauled by Waste Stream (Daily and Accumulative)

• Percentage complete per Pass

• Debris Reduced (Daily and Accumulative)

• Debris Loads (Daily and Accumulative)

• Number of Crews

i. Transactional data must be summarized, validated, presented and audited to provide an overall status of mission performance. The Data Consolidation applications must facilitate billing, error reporting, performance tracking and graphical data preparation. At a minimum, the Data Consolidation tools must provide the capability to:

• Accept transactional data sets from multiple debris location systems

• Recognize multiple mission/applicant configurations

• Grant access to authorized authenticated users or processes

• Contain a master record of:

- Roles and responsibilities

- Ticket/tower personnel credentials and other data

- Certification credentials and other data

- Mission data

- Applicant data

- Geospatial data

* Street centerlines

* County outlines

* Population and demographic

* Elevation

* Wetlands delineation

* Historic and Environmentally Sensitive areas

* Debris work zones

* Parcel data

* Land use

* FEMA flood zones

• Thematic mapping techniques to distinguish different data by color and/or symbol

• Identify data attributes for a single point of data

• Select one or many points of data

• Calculate operational efficiency statistics such as:

- Trip turnaround time

- Trip distance to disposal site (straight line projection)

- Average container fill percentage

- Average tower manager load call

- Load call trend data e.g., by tower managers, contractor, subcontractor, driver, etc.

• Multiple data selections generate tabular data reports

• Filter mechanisms to highlight geospatial data

• Role based security

• Prevent distributed data from being reprocessed for billing purposes

• Identify billing data sets based on parameters such as:

- Time/Date

- Contractor/Subcontractor

- Debris type

- Debris disposal method (haul-in, reduction, open burn, incineration, haul-out, leave in place, etc.)

- Haul distance

• Prevent modification to original data by unauthorized or unauthenticated users

• Insert audit records for modifications to original data by authorized, authenticated users

(Pronounced Adams)

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