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

WMATA Real-Time Parking
Information Feasibility Study
Chapter 6: PILOT PROJECT CONCEPT
test at the field device to ensure that it is properly transmitting information to the
central server, and can receive information from the central server.
• Once the central server is properly communicating with the field controller, then
all the internal functionality of the central server must be tested. This begins with
the demonstration of access from other computers at WMATA, and the ability to
review information, upload/download data, and make changes to system
parameters. An independent verification and validation test is critical to this
success.
• A 60 day operational test should be used to verify that the system operates
reliably and can handle archiving of data beyond the current month. This test
would require the use of the local wayfinding signs, but should be performed
before information is made available via the internet. The test should verify data
transmission and check that alarms are addressed as specified. The system
should be able to determine if it is not receiving regular updates from the
detection system and alert WMATA IT staff if its information feed from the
detection system fails.
Transmission to Other Entities
It is recommended that user information systems such as web page, mobile device, and
text message updates first be tested internally by WMATA staff. Subsequent to WMATA
staff verification of correct functionality, the system should then be tested by a limited
number of regular users of the pilot station parking facilities. After a suitable
demonstration period, the system can then be made available to the general public.
• First test transmission to the WMATA web servers Communications must be
established and the new web site developed. This will likely require coordination
between the parking system developer, and the web site developer.
Independent management of this coordination is critical to the success. Once
the new web pages are developed and populated, they should be tested
internally as stated above for at least one month prior to allowing the public
access.
• Communications with RITIS and 511 Virginia Again, this will require coordination
between the parking system developer and the RITIS and 511 Virginia
developers. As both the RITIS and 511 Virginia systems already exist, it should
primarily be the responsibility of the parking system developer to use and
implement the existing data standards. Any proprietary systems should be
discarded or not used for this link. Coordination with the other agencies and their
developers is key to the seamless integration of these systems.
• Coordination with outside vendors (e.g., third party mobile device information
resellers) In this instance, WMATA should adopt its own interface controls and
require the resellers to meet these controls. These systems can be verified by
the third party as to their operations and stability.
By following this process and completing independent verification and validation testing
at each stage, the technical issues related to the development of this system should be
more easily identified and addressed at the appropriate and easiest time to fix. This will
help ensure WMATA takes ownership of a system that best meets their identified needs.
Page 6-28 June 2009