The Strategy Manager component of Osprey provides a suite of tools allowing operators to define strategies that monitor the road network and implement responses that will respond to adverse traffic conditions and improve traffic flow. Configuration of the Strategy Manager uses a simple to use, wizard-driven facility, avoiding the necessity for the operator to have detailed programming knowledge or to remember complex syntaxes.
A strategy is comprised of a rule, a response and a schedule. The rule defines a situation on the road network. The response defines the actions to be taken when the rule holds true. The schedule defines when the strategy is active and should respond to a situation.
Implementation of a strategy response can be set-up to run automatically (without operator intervention) or to require operator authorisation to proceed. This facility is sometimes useful if the strategy is of high importance and the consequences of implementing the response will result in a major impact.
Strategies are defined and monitored through the Osprey GUI.
Inputs which can currently be used to trigger strategies include:
- Manual request
- Incidents and planned/unplanned Events
- Congestion and flow levels
- Journey time for key routes
- Car park status and occupancy
- Event count, type, severity and lanes effected
- Equipment status
- Fault status
- Diversion route status
Strategy response actions include:
- Operator alerts, which indicate to the operator that particular network conditions have occurred and some action should be considered
- VMS setting, allowing the system to override current VMS settings and alert the public to ongoing issues
- Issuing of commands to connected native systems such as UTC, allowing the system to directly invoke actions on these systems as part of a co-ordinated response
- Issuing of emails and text (SMS) messages to pre-defined recipients
- Responses can include multiple actions of each type to provide a comprehensive response. When the response action is complete (usually signified by the strategy condition being cleared) a series of stop responses are taken to reverse the actions taken.
Further strategy configuration allows for persistence of conditions to exist before triggering a response, fixed time responses and a “log-only” feature, allowing strategies to be tested prior to live implementation. Osprey logs full details of the activity, triggering and running of strategies which can then be analysed.