Attachment G - Software Functionality Attestation.pdf

Attachment G: Software Functionality Attestation

The below list includes the minimum requirements for a routing software to be considered viable for Portland Public Schools’ needs. By signing below you are attesting that your proposed product meets these minimum requirements.

Street Network Map: Provide a current, routable map including block addressing, lanes, directions, alternate street names, city/zip/state data, and speeds.

Regional Inclusion: Incorporate maps for five Oregon counties and two Washington counties.

Customization Protection: Protect District-initiated changes or customizations in the street network map when accepting new imported map information.

Network Segment Flagging: The ability to encode network segment based on a segment property (ie roads that cannot be traveled on during a snow storm or are maintained by)

Simultaneous Editing: Support multiple users editing the route network map, stops, or schools simultaneously based on user rights.

Independent Modifications: Allow users to add or modify streets and house numbers without vendor assistance.

Multiple Route Datasets: Ability to activate/deactivate multiple route and student datasets and utilize a single map for multiple scenarios.

Scenario Planning: Manage planning changes as scenarios applied at the record level for students, stops, runs, and routes.

History Management: Manage and report on the history of students, stops, runs, and routes.

Vehicle Restrictions: Encode travel restrictions based on vehicle type (e.g., restricting large vehicles while allowing small ones).

Hazardous Road Segments: Encode street segments as walking hazards to automatically prevent student stop assignments across them.

Road Network Walking Restriction Data: Based on the district’s walk restriction criteria, define network properties and combinations of properties that restrict walking on network segments.

Loading Zones: Ability to manage multiple user-defined loading points at each school site. Ability to calculate different distances for walk zones etc. based on defined loading point.

Student Information System (SIS) Integration: Establish unattended/automated data integration through an integration platform from any District SIS. Support near-real-time bi-directional data exchange, including uploading transportation eligibility back to the

SIS.

Data update: Ability to lock student data cells from upload based on automatic or user defined criteria or contingencies.

Multiple Addresses: Manage a single student record with multiple addresses (AM pick-up, PM drop-off, mailing) and varied weekly attendance schedules.

Flexible Tiering capabilities: Enable the creation of tiered "runs" within bus routes.

These runs should be capable of being modified independently and reallocated to alternative routes as required.

Manual Adjustments: Allow for manual changes to stop times and travel times between stops and total route time that are optionally preserved during re-calculations.

Solver Capabilities: Enforce right-side pick-up/drop-off without intervention and describe the override process for restricted areas.

Effective Dates: Support specific initiation and termination dates for route, stop, and student changes.

Public Lookup: Provide web-based lookup for locating bus stops based on GT eligibility, school boundaries, and address information.

Daily Dispatch Changes: Allow dispatchers to make daily changes to driver/asset assignments with appropriate hardware/software integration.

Vehicle Asset Data: Manage asset records (active/inactive), track park outs, and store vehicle details (capacity, wheelchair spots, car seats).

Report Generation: Create user-defined reports and attributes without vendor intervention, with a full report engine accessible to the District.

GIS System Data Import: Support user-initiated import of tabular spreadsheet or spatial

(GIS) data to update system properties and records for all data types.

Manual Data Modification: Support manual modification of data fields within the system. Including road network fields and stop times.

Direct System Integration: Support seamless, automated data exchanges between the routing system and external third-party systems (e.g., GIS, mapping, fleet management).

The vendor must ensure these systems communicate directly without manual intervention or oversight by District staff.

Technical Support: Provide technical support as needed during working hours.

Implementation Specialist: Assign a dedicated implementation team

Date _____________

Signature ____________________________

Name___________________________________

(Please Print)

Company Name ______________________