feasibility study of real time parking information at ... - WMATA.com

WMATA Real-Time Parking
Information Feasibility Study
Central Server
Chapter 6: PILOT PROJECT CONCEPT
The central server is the main communications hub for the parking system. It will be
responsible for maintaining the archive and interfacing with the central WMATA staff.
For this reason, its application user interface is critical – it must be easy to use and
complete. The central server will take the information from the local server, reformat it,
and publish it to the outside world. This includes creating web pages or information,
sending information to VDOT, and interfacing with other third party vendors. Over the
long term, the central system will need to be able to interface with several different
systems simultaneously.
The type of computer and operating system for the central server can be more rigidly
defined. It will need to work within the greater WMATA WAN and will be maintained by
WMATA staff. This should not be a problem for any vendor to supply a more custom
system at the local controller, while the central system is a more traditional office
environment system.
Requirements and Procurement Method
The goals, objectives, and functional requirements were addressed in Chapter 4. In that
chapter, requirements were matched to goals and objectives. For the system
requirements, the requirements now need to be logically matched to actual field
components, including systems and subsystems. Two tables demonstrating that all
requirements are matched to objectives and that each objective corresponds to a
requirement are included in the Technical Memorandum.
Not all of the final objectives will be addressed in the pilot study. The intent of a pilot
study is to test the technologies and the operations of the system to see if this
application is warranted at other locations throughout the WMATA system. The pilot
system should be installed with the intention of expanding the system to other stations,
but must stand alone first.
A full system design is still required before the system can be built. This can be
procured using either a design-bid-build or a design-build approach. Under a designbid-build
procurement, a designer would be hired by WMATA to design the system and
assemble contract-ready procurement documents. The system would then be put out to
bid. A contractor would be hired, and either the designer or another consultant would
likely serve as a systems manager, ensuring the contractor is meeting all requirements.
In a design-build procurement, a consultant will still need to assemble and complete
these requirements into a design-build procurement package. The procurement
package in this case will be conceptual and include specific functional requirements, with
certain minimums that must be met to ensure the contractor meets all of the needs of
WMATA. Again, the designer (or another consultant) would likely serve as a systems
manager ensuring all requirements are met. In either procurement method, it is
important that WMATA obtain design engineering and systems manager support to
ensure all needs and desires are met. Though not an absolute requirement, the design
engineer and the systems manager ideally should be the same firm. The first step in
implementation should be to obtain this critical support.
Page 6-17 June 2009