SFREQ-19.0 The DRS shall output total number of routes produced by the DRS on a given system run. Test This has been verified by analyzing the model output. Reference Model Performance section. SFREQ-20.0 The DRS shall output total estimated route time for each route produced by the DRS on a given system run. Test Same verification as SFREQ-19 SFREQ-25.0 The DRS shall take as an input, configurable delivery/pickup times for each delivery/pickup location and use this information in determining total route time. Delivery time is defined as the time it takes for a carrier to exit their vehicle, make delivery of the parcel(s), return to their vehicle and continue on their route. Test Reference Model Output data. Each Route has associating .csv file which specifies cumulative route time for each stop. For the purposes of model testing this variable was set to 2.5 minutes.
Requirement ID Requirement Description Functional Area Priority Traceability/Source The DRS shall provide an interface to allow for initiation of a system run by the front end user and provide the front end user feedback indicating success or failure of initiation. A system run is defined as execution of the DRS for a specified delivery/pickup location set. DRT Interface High Derived based on customer communication (email). The DRS shall accept as input delivery deadlines and service times (time range for delivery) for delivery locations. These times shall be used as input constraints in route formulation and optimization. Core Processing Low USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall interface to USPS databases for the purposes of obtaining parcel delivery location information. Data Management High Derived based on customer communication (email). The DRS shall interface with the USPS AMS to validate delivery/pickup location information. Delivery/Pickup location information shall be validated prior to dynamic route processing. Data Management High Derived based on customer communication (email). The DRS shall accept manual input of delivery/pickup location information and combine or modify delivery/pickup location set prior to route processing. Location information is defined as an address and geocode Data Management High USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives.
The DRS shall interface to the USPS DRT for the purposes of providing access to carrier management administrative functions. DRT Interface Low USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall retain route history and line of travel data for 360 days. Route history and line of travel data shall be in address format and geocoded format. Data Archiving High USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall have the capability to define routes across customized boundaries. Customized boundaries are uniquely defined boundaries based on one or more zip codes, or partial zip codes. DRT Interface Medium USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall accept as an input a maximum and minimum route length constraint. These route length constraints shall be configurable and the DRS shall formulate optimized routes based on the specified route length. Route length is defined in units of hours. Core Processing High USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall output total mileage for each route produced by the DRS on a given system run. Core Processing High USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives.
The DRS shall provide a capability to front end users which allows for the following route attributes to be configurable: Start time End time Last Delivery 15 minute break 30 minute lunch break These configurable attributes shall be factored into dynamic route optimization. DRT Interface Medium USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall factor in historical traffic data where applicable when determining standard and non-standard traffic conditions for route formulation and optimization. Core Processing Low Derived based on system need. The DRS shall allow for road type restrictions to be specified and factored into dynamic route formulation and optimization. Road type restrictions, at a minimum, pertain to the following: One–way streets Toll-Roads Roads restricted to certain vehicle types. HOV restrictions. DRT Interface High USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives.
The DRS shall locate 95% of street addresses presented for dynamic route formulation. This includes address’s, which would be designated on a HCR, rural routes and addresses added within the previous week. Data Mgmt. High USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall provide the capability to add delivery/pickup locations in USPS databases in address format. This functionality shall be implemented as a post-processing step after completion of route formulation and optimization. Data Mgmt. High USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall provide a capability to validate route stop information prior to providing route instructions to carrier. Route Stop information pertains to the following data: Date of delivery Time of delivery Address and/or Latitude/Longitude Type of package Required delivery time (if applicable) Data Mgmt. Medium Derived based on system need. The DRS shall report package volume metrics, for designated delivery area, on demand. Metrics include quantity of parcels input into the system, and quantity of parcels delivered. DRT Interface Medium USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives.
The DRS shall implement an interface which allows front end users to input parcel pickup information including address, geocode and service time if applicable. Core Processing Low USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall take as input and factor the following configurable route attributes into dynamic route formulation and optimization: Start time End time Last Delivery 15 minute break 30 minute lunch break Core Processing Low USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. The DRS shall produce routes, which visit each delivery location specified by the system input (within 400 locations constraint) and return to the starting Delivery Depot. This is defined as a complete tour. Core Processing High Derived based on system need and prototyping. The DRS shall output a sequential list of delivery locations and parcel pickups for each route produced. Delivery locations shall be in geocode format and address format. Core Processing High Derived based on system need and prototyping. The DRS shall format delivery location information for route formulation and optimization processing. Data Management High Derived based on system need and prototyping.
SFREQ-9.0 The DRS shall support scheduling of multiple package pickups for a given delivery/pickup location data set. Medium USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. SFREQ-11.0 The DRS shall provide as output printable Turn directions for each route. Turn-by-Turn directions shall specify directions to and from each delivery location of a route. High USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. SFREQ-14.0 The DRS shall interface to the USPS DRT for the purposes of providing access to carrier management administrative functions. Low USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. SFREQ-16.0 The DRS shall have the capability to define routes across customized boundaries. Customized boundaries are uniquely defined boundaries based on one or more zip codes, or partial zip codes. Medium USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives. SFREQ-21.0 The DRS shall report on demand, fuel usage metrics. Fuel usage metrics shall be based on estimated and actual fuel usage for routes produced by the DRS. Medium USPS Request For Information regarding Dynamic Routing Strategy: Section IV. Objectives.