|
|
|
Risks
|
|
Integrating all
these separately run functions may take more time, care and testing than
might be initially apparent.
|
|
Replacing or
integrating proprietary systems may pose additional difficulties.
|
|
System failure might
take down all functions instead of one which might be the case now. Developing the capability for Core Systems
to back each other up and enable fail-over to maintain the continuity of
operations is one possible mitigation.
|
|
Other
Considerations
|
|
|
|
Owner/Operator
versus Participator
|
|
Transit operator can
add a revenue stream by selling real-time position, trajectory and weather
information collected by its vehicles to data aggregators.
|
|
Can also buy data
where it would help real-time operational management of the fleet.
|
|
Vehicles can be
tracked and managed with data transferred through the secure Core System.
|
|
The Core System
levels the playing field for small transit operators that cannot purchase and
operate all the systems currently employed by large transit operations.
|
|
|
|
By operating a Core
System a transit operator has more flexibility to run custom applications and
apply processing at the data distribution level unique to its
operations. That might enable unique
pricing, route diversion, and incentive programs. It would also guarantee the availability of
the Core.
|
|
|
|
Outstanding
Questions
|
|
Is there a business
model where owning and operating a Core System has a clear advantage to just
participating in a Core System operated by another entity?
|
