Regional Architecture Logo
 

Send Your Comments

E-Mail

Logo

Regional Architecture Banner Architecture Geographic Scope

MCM Vehicle and Equipment Maintenance Management Equipment Package

Description:

This equipment package monitors vehicle and equipment condition, tracks maintenance history, and schedules routine and corrective maintenance.

 

Included in:

City of Akron Highway Maintenance Department
City of Canton Maintenance Dispatch
City of Canton Street Dept Dispatch
City of Cuyahoga Falls Maintenance Dispatch
City of Cuyahoga Falls Traffic Services Dispatch
Municipal Maintenance Dispatch
ODOT District 4 Maintenance Garages
Portage County Maintenance Dispatch
Stark County Maintenance Dispatch
Summit County Maintenance Dispatch

Processes:

9.1.5Schedule M&C Vehicle Maint
9.2.5Provide M&C Center Personnel Interface for Maint
  

User Service Requirements (fully or partially addressed):

8.0MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.1Maintenance and Construction Operations shall provide a Maintenance Vehicle Fleet Management (MVFM) function to schedule and dispatch, monitor and track location, and monitor operational condition and maintenance requirements of public and contracted fleets of maintenance, construction, and specialized service vehicles. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Vehicle Maintenance Crews, Equipment Maintenance Crews, Weather Services Organizations, and Information Service Providers.
8.1.1.2MVFM shall be capable of supporting route scheduling and dispatching of public and contracted fleets of maintenance, construction, and specialized service vehicles.
8.1.1.3MVFM shall be capable of supporting interactive data communications between dispatchers and operators of public and contracted maintenance, construction, and specialized service vehicles.
8.1.1.4MVFM shall be capable of using on-board vehicle sensors to monitor the vehicle diagnostics and operating conditions of public and contracted fleets of maintenance, construction, and specialized service vehicles.
8.1.1.4.1MVFM shall be capable of collecting information on the operating conditions of vehicles, including but not limited to:
8.1.1.4.1(a)System status (e.g. status of brake system, oil pressure, etc.)
8.1.1.4.1(b)Engine temperature
8.1.1.4.1(c)Mileage
8.1.1.4.1(d)Tire wear
8.1.1.4.1(e)Brake wear
8.1.1.4.1(f)Belt wear
8.1.1.4.2MVFM shall be capable of automatically scheduling preventive and corrective vehicle maintenance.
8.1.1.6MVFM shall be capable of providing dispatchers and operators of maintenance, construction, and specialized service vehicles with information regarding potential and actual roadway problems.
8.1.1.6.1MVFM shall provide information to dispatchers and vehicle operators, including but not limited to:
8.1.1.6.1(a)Congestion
8.1.1.6.1(b)Incidents
8.1.1.6.1(c)Roadway restrictions
8.1.2Maintenance and Construction Operations shall provide a Roadway Management (RWM) function to monitor traffic, road surface, and environmental conditions and forecast traffic and road surface conditions to support management of routine and hazardous road condition remediation and to communicate changes in conditions. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Asset Managers, Planning Agencies, and Weather Services Organizations.
8.1.2.1RWM shall support a number of different services, including but not limited to:
8.1.2.1(a)Winter maintenance (plowing, treating, anti-icing, de-icing, etc.)
8.1.2.1(b)Hazard removal (removing trash, animals, etc.)
8.1.2.1(c)Emergency activities (incident response, planning, alternate routing, etc.)
8.1.2.1(d)Routine maintenance activities (cleaning, cutting, etc.)
8.1.2.1(e)Repair activities
8.1.2.1(f)Other weather related activities (fog dispersion, etc.)
8.1.2.9RWM shall monitor, manage, and control remotely located, automated systems, that affect the roadway surface (e.g. de-icing/anti-icing applications).
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 09-16-2004 using Ronald C. Ice and Associates Web Spinner Technology.