CALIFORNIA PATH PROGRAM
INSTITUTE OF TRANSPORTATION STUDIES
UNIVERSITY OF CALIFORNIA, BERKELEY
This work was performed as part of the California PATH Program of
the University of California, in cooperation with the State of California
Business, Transportation, and Housing Agency, Department of Trans-portation,
and the United States Department Transportation, Federal
Highway Administration.
The contents of this report reflect the views of the authors who are
responsible for the facts and the accuracy of the data presented herein.
The contents do not necessarily reflect the official views or policies of
the State of California. This report does not constitute a standard, spec-ification,
or regulation.
ISSN 1055- 1417
July 2009
EDAPTS Test Deployment :
System Installation and Technical
Review Report
California PATH Working Paper
UCB- ITS- PWP- 2009- 8
CALIFORNIA PARTNERS FOR ADVANCED TRANSIT AND HIGHWAYS
Xudong Jia, Ryan Beasley, Jeff Gerfen,
Neil Hockaday, Bruce Chapman
Report for Task Order 6403
Task Order 6403
Cal Poly Pomona
EDAPTS Test Deployment
System Installation and
Technical Review Report
Version 5.0
Prepared by
Xudong Jia, Ph. D., P. E
Ryan Beasley
California State Polytechnic University, Pomona
Jeff Gerfen
Neil Hockaday
California Polytechnic State University, San Luis Obispo
And
Bruce Chapman
California Department of Transportation
Under PATH Contract TO 6403
June 8, 2009
ii
Abstract
The California Department of Transportation ( Caltrans) and the Federal Transit
Administration ( FTA) embarked on a research program entitled “ Efficient Deployment of
Advanced Public Transportation Systems” ( EDAPTS) in the late 1990’ s. The Bronco
Express EDAPTS Stage 5 Deployment Demonstration project at California State
Polytechnic University, Pomona ( Cal Poly Pomona) is an integral part of this program. Its
objective is to go through the procurement and deployment process of a low cost Intelligent
Transportation Systems ( ITS) solution to determine if the EDAPTS concepts are optimized
for small transit agencies and if they can be successfully transitioned to the commercial
marketplace.
This report documents the installation, verification, and validation steps associated with the
Bronco Express EDAPTS Demonstration project. It identifies and summarizes procedures
that are effective in installing and testing a lower- cost ITS system and provides a practical
methodology for verifying and validating small transit ITS systems. It also documents
outcomes of the installed system in compliance with the user needs and the performance
specifications as requested in the Bronco Express EDAPTS RFP.
Keywords: EDAPTS, System Engineering, System Verification, System Validation,
Intelligent Transportation Systems
iii
iv
Executive Summary
The California Department of Transportation ( Caltrans) and the Federal Transit
Administration ( FTA) embarked on a research program entitled “ Efficient Deployment of
Advanced Public Transportation Systems” ( EDAPTS) in the late 1990’ s. The Bronco
Express EDAPTS Stage 5 Deployment Demonstration project at California State
Polytechnic University, Pomona ( Cal Poly Pomona) is an integral part of this program. Its
objective is to go through the procurement and deployment process of a low cost Intelligent
Transportation Systems ( ITS) solution to determine if the EDAPTS concepts are optimized
for small transit agencies and if they can be successfully transitioned to the commercial
marketplace.
This report documents the installation, verification, and validation steps associated with the
Bronco Express EDAPTS Demonstration project. It identifies and summarizes procedures
that are effective in installing and testing a lower- cost ITS system and provides a practical
methodology for verifying and validating small transit ITS systems. It also documents
outcomes of the installed system in compliance with the user needs and the performance
specifications as requested in the Bronco Express EDAPTS Request for Proposal ( RFP).
The installation, system verification and validation processes for the Bronco Express
EDAPTS System demonstrated a number of critical system deployment activities in using a
modified version of the Federal Highway Administration ( FHWA) Systems Engineering “ V-model”
( see Figure E- 1). The selected system supplier was not required ( nor paid) to
complete the detailed design, software and hardware development, and unit/ device testing
steps called for by this approach, but rather delivered Commercial Off- the- Shelf ( COTS)
software and hardware products.
The system supplier acted as a system integrator to integrate all the COTS products for the
Bronco Express EDAPTS system. Using the Bronco Express Operations Guidelines ( or the
“ Concept of Operations”), high- level design documents and system requirements as
guidelines, the system supplier, in coordination with the research team and Cal Poly Pomona
Parking and Transportation Services ( PTS), procured and installed the EDAPTS system.
The procurement and installation process consisted of ( 1) web service establishment, ( 2)
vehicle on- board subsystem installation and integration, ( 3) solar- powered roadside
information display sign installation and integration, and ( 4) system testing.
v
vi
Figure E- 1 Modified FHWA Systems Engineering V Model
( Source: Systems Engineering for Intelligent Transportation Systems, US DOT, 2007)
Please note that items in blue were completed as part of the procurement, system verification, and validation
processes while the items in gray were not.
Since no solar- powered roadside information display signs meeting the Bronco Express
EDAPTS system requirements and specifications were commercially available at the time of
contract award, the system supplier could not install the signs at the same time as the AVL,
APC, and MDT subsystems were installed. The supplier had to design, build, test, and
deliver its own solar- powered sign product to Bronco Express separately from the rest of the
installation and integration process. Cal Poly Pomona facilities personnel then installed the
signs at the designated sites around campus.
The research team, observing the Bronco Express EDAPTS System installation process and
working with the system supplier, developed the system verification plan, the validation plan
and their associated test procedures. Using these test plans and procedures, the research
team verified the installed subsystems and functionality against those required in the RFP,
those provided in the system supplier’s proposal, and those described in the Bronco Express
EDAPTS Operations Guidelines.
vii
viii
The system verification process demonstrated the following findings:
a.) The installed EDAPTS system largely met all performance specifications, although it
felled short in some key areas. Generally, these failures were in areas originally specified
by the EDAPTS RFP, but were not promised by the system supplier.
b.) The system as a whole met the capacity and support requirements set out in the
specification, supporting far larger quantities of elements such as vehicles, drivers, stops,
and routes than those set forth in the EDAPTS RFP.
c.) The system met all applicable state and Federal standards, including Department of
Transportation ( DOT) requirements for vehicle onboard components and Federal
Communications Commission ( FCC) licensing requirements for wireless data
communications devices.
d.) One of the primary deficiencies was the lack of schedule adherence capability throughout
the system, as it had no concept of fixed- route scheduling. It also did not conform to the
EDAPTS Data- Formatting Standard at any level of the system, detracting from the open-format
ideal of EDAPTS and complicating the possibility of part- interchangeability and
the modification or addition of new features in the future by the university or another
system supplier.
The system validation process demonstrated the following findings:
1) The installed system met the user needs and operational requirements described in sixteen
of twenty seven operational scenarios.
2) The installed system failed ten operational scenarios. The majority of the failures were in
scenarios related to functionality of the MDT devices. For example, the MDT ( 1) did not
display the stop where the driver would begin the route, ( 2) did not start displaying the
time in a large digital format once the driver started driving and ( 3) did not display the
current arriving at a stop.
3) One of the twenty seven scenarios was not tested due to the fact that the Bronco Express
EDAPTS system provided a service that substituted the service described in the testing
scenario.
ix
x
The system verification and validation demonstrated in this project proved to be very
effective in determining how well the installed EDAPTS system met the system functional
requirements and the operational characteristics and user needs described in the EDAPTS
RFP. The processes and test procedures developed by the team ensured that the verification
and validation tests are repeatable and well documented.
xi
xii
TABLE OF CONTENTS
1. Introduction ............................................................................................................................ 1
2. EDAPTS Research Program Overview .................................................................................... 2
3. Project Methodology .............................................................................................................. 3
4. Bronco Express EDAPTS System Installation ......................................................................... 6
4.1 Web Service Establishment ................................................................................................. 6
4.2 Vehicle On‐ Board Subsystem Installation and Integration ................................................. 7
4.3 Solar‐ Powered Roadside Information Display Installation and Integration ...................... 10
4.4 System Testing ................................................................................................................... 12
4.5 Bronco Express EDAPTS System Ribbon Cutting Ceremony ............................................. 15
5. Overview of the Installed Bronco Express EDAPTS System ................................................. 16
5.1 Bronco Express Vehicle On‐ Board Equipment/ Vehicle‐ to‐ Central Site Wireless
Communication System .................................................................................................... 17
5.2 Bronco Express Dispatch Clients ....................................................................................... 18
5.3 Bronco Express Public Client ............................................................................................. 21
5.4 Solar‐ Powered Signs/ Sign‐ to‐ Central Site Wireless Communications System ................. 23
6. Bronco Express EDAPTS System Evaluation ......................................................................... 24
6.1 System Verification Plan and Testing ................................................................................ 24
6.2 System Validation Plan and Testing ................................................................................... 29
7. Conclusions .......................................................................................................................... 45
8. References ............................................................................................................................ 46
9. Appendicies .......................................................................................................................... 47
Appendix A Structural Design of Sign Posts and Site Layout Design of Sign Foundations
Appendix B Summary of System Verification Findings
Appendix C Completed System Verification Worksheets
Appendix D Questionnaire to System Supplier
Appendix E Bronco Express EDAPTS System Validation Plan and Results
xiii
xiv
1
1. INTRODUCTION
The Bronco Express Efficient Deployment of Advanced Public Transportation Systems ( EDAPTS)
Demonstration project at California State Polytechnic University, Pomona ( Cal Poly Pomona) is
currently seeking to determine if the EDAPTS concepts for procuring low cost Intelligent
Transportation Systems ( ITS) are optimized for small transit agencies and if they can be
successfully transitioned to the commercial marketplace. This research project, hereafter
referred to as the “ Bronco Express EDAPTS Demonstration”, is sponsored by Caltrans and the
Federal Transit Administration ( FTA) and seeks to update to current practice the original
EDAPTS research done by California Polytechnic State University, San Luis Obispo ( Cal Poly San
Luis Obispo). This report documents the procurement, installation, verification, and validation
steps associated with the Bronco Express EDAPTS Stage 5 Deployment Demonstration.
This report identifies and summarizes procedures that are effective in installing and testing a
lower‐ cost ITS system and provides a practical methodology for verifying and validating small
transit ITS systems. It is the second of three reports documenting the Bronco Express EDAPTS
Demonstration. The first report, entitled “ Cal Poly Pomona EDAPTS Test Deployment
Procurement Documentation Package” ( Jia and Gerfen, 2008), outlined the procurement of the
Bronco Express EDAPTS system. The next and final report in this sequence will collect and
summarize all previous reports in this project and provide insights, recommendations and
lessons learned during the Bronco Express EDAPTS Demonstration.
2. EDAPTS RESEARCH PROGRAM OVERVIEW
The EDAPTS research approach promotes innovative communications approaches, open source
designs, solar powered real‐ time arrival signs, and innovative data links to help small transit
provider access useful ITS solutions. It also promotes the acquisition of commercial off‐ the‐shelf
( COTS) equipment/ software. The approach focuses on providing improved transit services
and safety for passengers, decreasing driver work load and providing improved operations data
to management; and doing this at a cost level that small transit properties can afford. The
EDAPTS research goal is to demonstrate the viability of lower‐ cost implementations of transit
ITS technologies; where the concepts, designs and performance expectations are tightly
focused and tailored specifically to small transit system needs.
The Bronco Express EDAPTS Demonstration is built upon the results of prior research efforts.
Additional research, outside this demonstration effort, looked at the cost benefit of the EDAPTS
approach in day‐ to‐ day operations and developed performance specifications specifically
focused on small transit procurement of EDAPTS compliant solutions ( Jia et al, 2007; Gerfen et
al, 2007).
2
3. PROJECT METHODOLOGY
Cal Poly Pomona and Cal Poly San Luis Obispo researchers solicited participation from Bronco
Express stakeholders who would be affected or would benefit from the deployment of an
EDAPTS ITS system at Cal Poly Pomona. These representatives formed the Bronco Express
EDAPTS Advisory Panel and it had representation from the university, transit provider, transit
operator, security, campus parking, drivers and student body.
Using the Advisory Panel as an active resource, the research team developed a clear
understanding of the needs, the problems, and the envisioned solutions. This was documented
in the Bronco Express EDAPTS Operations Guidelines ( Jia and Gerfen, 2007) and formed the
basis for the Bronco Express procurement effort. To mimic a typical small transit agency
procurement process, procurement was done using a Request for Proposal ( RFP) process
through the Cal Poly Pomona’s Procurement Office.
The RFP was released, advertised, and awarded to the system supplier with the best value bid,
where cost was a significant factor in bid evaluation. The selected solution included automatic
vehicle location ( AVL), automatic passenger counters ( APC), solar‐ powered roadside
information display ( RID) signs at four bus stops and mobile data terminals ( MDTs) on all
Bronco Express Buses.
Following installation and system testing by the vendor, the research team completed the final
subsystem verification, system verification, and system validation steps to determine how close
the installed system came to meeting desired RFP functionality and specifications.
This project utilizes a modified version of the Federal Highway Administration ( FHWA) Systems
Engineering “ V‐ model” ( see Figure 1 below) as a guide to facilitate a systematic and efficient
procurement process.
3
Figure 1 Modified FHWA Systems Engineering V Model
( Source: Systems Engineering for Intelligent Transportation Systems, US DOT, 2007)
Please note that items in blue were completed as part of the procurement, system verification, and
validation processes while the items in gray were not.
The V‐ model is modified in that the selected system supplier was not required ( nor paid) to
complete the detailed design, software and hardware development, and unit/ device testing
steps called for by this approach, but rather delivered Commercial Off‐ the‐ Shelf ( COTS)
software and hardware products. Aspects of the V‐ model, which this deployment project
adhered to, included development of the Bronco Express Operations Guidelines ( i. e. “ Concept
of Operations”), definition of high‐ level design documents and development of system
requirements. These documents were then used as source material to help define and conduct
system verification and validation for the Bronco Express EDAPTS System.
The procurement process for the Bronco Express EDAPTS System demonstrated a number of
critical system procurement activities in using the modified V‐ model as a framework. These
activities included active participation of the stakeholders throughout the process, identification
of the highest priority systems and subsystems in the high‐ level design step, selection of
relevant performance specifications for the desired system and subsystems, and selection of a
qualified system supplier for the integration and installation of the system.
Once the RFP system supplier selection phase was completed, the Bronco Express EDAPTS
Demonstration moved into its installation stage. The winning system supplier, in coordination
with the research team and Cal Poly Pomona Parking and Transportation Services ( PTS),
installed the first elements of the Bronco Express EDAPTS System, the on‐ board equipment, on
April 29, 2008. On January 8, 2009 the final elements of the system, the solar‐ powered dynamic
roadside information display signs, were installed. The system then entered the acceptance
verification and validation phase of the research demonstration.
4
By observing the Bronco Express EDAPTS System installation process and working with system
supplier, the research team developed an understanding of the operational functions and
features of the installed system. This understanding was used to develop the system
verification plan, the validation plan and their associated test procedures. The purpose of these
test plans and procedures was to verify the installed subsystems and functionality against the
requirements of the RFP and the system supplier’s proposal. The plans and test procedures also
validate the user needs and performance measures against the Bronco Express EDAPTS
Operations Guidelines. A detailed description of the Bronco Express EDAPTS System
installation, verification and validation processes is provided in later sections.
5
4. BRONCO EXPRESS EDAPTS SYSTEM INSTALLATION
This Section covers the four phases of the Installation and Test period: ( 1) Web Service
Establishment, ( 2) Vehicle On‐ Board Subsystem Installation and Integration, ( 3) Solar‐ Powered
Roadside Information Display Installation and Integration, and ( 4) System Testing.
The Bronco Express EDAPTS System installation was done by both system supplier and Cal Poly
Pomona personnel. These groups installed all the subsystems, components and software
functions provided in the system supplier’s proposal. During this process, the system supplier
identified, acquired and tested the required COTS hardware and software components before
the components were integrated into the Bronco Express EDAPTS System.
Since no solar‐ powered roadside information display signs meeting the Bronco Express EDAPTS
system requirements and specifications were commercially available at the time of contract
award, the system supplier could not install the signs at the same time as the AVL, APC, and
MDT subsystems were installed. The supplier had to design, build, test, and deliver its own
solar‐ powered sign product to Bronco Express separately from the rest of the installation and
integration process. Cal Poly Pomona facilities personnel then installed the signs at the
designated sites around campus.
4.1 Web Service Establishment
The Bronco Express EDAPTS System installation effort provided a unique opportunity to
evaluate the integration of small transit ITS solutions under the ITS Services Business Model.
Before the Bronco Express EDAPTS System was installed, the successful system supplier had
already supplied similar web‐ based transit services on a monthly‐ fee basis to its existing clients.
These services included the use of AVL technologies, wireless data communications
technologies, data base management systems, and dedicated web services that showed real
time locations of buses, predicted bus arrival times, and provided specialized bus operational
information. This real‐ time tracking technology reported bus locations to a Web‐ based server
with a delay of not more than 10 seconds, and bus locations and related operational data
( speed, heading, door status, ignition state, and boarding and alighting passengers) were stored
in databases and used to predict the arrival of buses at each stop for each service route.
Predicted bus arrival times and other statistical summaries of bus operations were provided to
customers through web portals.
The system supplier provides the Bronco Express EDAPTS System service with two web portals.
One, http:// www. broncoshuttle. com, enables the public to access bus location and status. The
other is a private website and allows the EDAPTS research team and PTS to manage the Bronco
Express EDAPTS System remotely. This web site is password‐ protected, allowing only
authorized individuals to access the site and manage the Bronco Express EDAPTS System.
6
4.2 Vehicle On‐ Board Subsystem Installation and Integration
The vehicle on‐ board subsystem consists of the AVL, APC, and MDT components.
AVL Procurement and Installation
Eight AVL units, each consisting of a Global Positioning Satellite ( GPS) receiver system and a data
modem, were procured as COTS products for the Bronco Express EDAPTS System. Each AVL unit
was configured to interface with other in‐ vehicle components including the APC and MDT units.
The AVL units use Global System for Mobile ( GSM) communications links and General Packet
Radio Service ( GPRS) technologies to provide mobile data communication services for the
Bronco Express EDAPTS System.
The system supplier installed the first AVL unit on a Cal Poly Pomona bus on April 29, 2008.
During the installation, the supplier placed the unit on the backside of the driver seat, out of the
way of daily operations. Figure 2 shows a typical installation of the AVL unit on a Bronco
Express bus.
Figure 2 AVL Unit Installed on Bronco Express Shuttle Bus
7
After the first AVL unit was mechanically and electrically mounted in the bus, the system
supplier configured the device to communicate with the rest of the system. The AVL unit
functioned properly, detecting the location of the bus and transmitting the location information
to the remote Web server. The system supplier, working with the PTS driver, tested the unit and
the system by verifying the following functional requirements.
1) The unit reported geographic position to the server and back through each of the two
web portals within one minute of vehicle start.
2) The unit reported position every 6 seconds at low speeds and every 10‐ 15 seconds at
medium and high speeds.
3) The unit acknowledged operation to the server once per minute when it is turned on.
• The unit reported door open and door close events to the server reliably.
4) The unit automatically assigned itself to the route it is currently serving.
5) The system accurately predicted bus arrival time at bus stops.
The system supplier started installing the remaining AVL units on the remaining seven buses
after PTS operated the first AVL equipped bus for several days and verified the unit functioned
as indicated by the supplier. The installation required approximately two weeks to complete
and was planned to not interfere with Bronco Express operation.
APC Procurement and Installation
The supplier, working with PTS and the research team, selected infrared‐ based APCs over
mechanical pressure APCs for the Bronco Express EDAPTS System. These APCs are specifically
designed for transit use to collect passenger boarding and alighting counts. They then pass the
counts on to the AVL unit for transmission back to the server. The door sensors are overhead‐mounted,
directionally sensitive, two‐ beam systems that are only activated when a hard‐ wired
“ door open” signal is active.
PTS and the supplier determined the door configurations and measured dimensions of all the
buses to determine the number of APCs and their configuration required for the Bronco Express
EDAPTS System. This indicated that a single one‐ door APC device and seven two‐ door APC
devices were needed for coverage of the eight buses.
The supplier procured the necessary APC devices and installed them six weeks after the AVL
units were successfully installed. Initially, AVL units and APC devices were to be installed at the
same time in order to save overall installation time; however, the procurement delay time for
APC devices was longer than that for AVL units and the installations had to be completed
separately. The APC installation was completed over a four‐ day period, beginning on June 23,
2008. Figure 3 shows a typical APC installation on a Bronco Express shuttle bus.
Following APC installation, the supplier conducted a set of tests on each bus to verify proper
APC operation. Supplier personnel, working with PTS drivers, tested the device and the EDAPTS
system by verifying the following functional requirements.
8
• Door open and close events were reliably reported.
• People boarding the bus, including those entering quickly or those entering in close
proximity were counted accurately.
• People exiting the bus, including those that exit quickly or left in close proximity to each
other were accurately counted.
• Proper communication between the APC and the AVL unit was established and
maintained.
Figure 3 Automatic Passenger Counter Installed on Bronco Express Shuttle Bus
MDT Procurement, Unit Testing, and Installation
The system supplier worked with PTS to select an appropriate MDT device from the available
COTS products based on the indicated functionality contained in the Bronco Express EDAPTS
Operations Guidelines. This selection considered factors such as cost, ruggedness and
reliability. The procured MDT devices have a bright Thin Film Transistor ( TFT) graphic Liquid
Crystal Display ( LCD) and use the Windows ® CE operating system.
Due to mechanical mounting challenges, the system supplier used various MDT mounting
schemes to properly position the MDT devices on buses. All MDT installations were completed
by October 17, 2008. The installed MDTs were placed within the reach of drivers, but not in the
way of driver normal activities. Figure 4 shows a typical installation of the Mobile Data Terminal
on a Bronco Express shuttle bus.
9
Figure 4 Mobile Data Terminal Installed on Bronco Express Shuttle Bus
4.3 Solar‐ Powered Roadside Information Display Installation and Integration
The roadside information displays present " live" data to waiting passengers at specific stops by
showing the estimated arrival time of all buses serving that particular stop. While these signs
typically display arrival time information, they may also display other messages such as public
service announcements or system status information.
The Roadside Information Display subsystem used for the Bronco Express EDAPTS System
consists of a display, a mounting post, and a post foundation. The post supports the sign and
must provide a safe, secure mounting under local environmental conditions, including wind and
earthquake events. The foundation is poured concrete with an appropriate mounting receptacle
to which the post is secured.
− Solar‐ Powered Sign
To respond to the Cal Poly Pomona’s green initiative, Bronco Express requested solar‐ powered
signs in the RFP. However, commercially produced solar‐ powered signs that met the Bronco
Express EDAPTS system requirements and specifications, and also met the Americans with
Disabilities Act ( ADA) guidelines and requirements, were not commercially available at the time
of the procurement. The system supplier decided to work with PTS and the research team to
develop and design a solar‐ powered sign for installation at Cal Poly Pomona.
The system supplier reviewed the roadside information display performance requirements in
the Bronco Express EDAPTS RFP and presented the prototype to the research team and the
Advisory Panel members on June 24, 2008. Since the prototype did not fully consider the ADA
guidelines and requirements, the panel rejected it and asked the supplier to provide a new ADA
compliant prototype design for evaluation.
The system supplier continued working with the research team and Advisory Panel to establish a
better understanding of the performance requirements that needed to be met in the new sign
10
prototype. The new design considered the input of several team discussions, reviews of ADA
guidelines, and the requirements described in the RFP, Section 5081. This design used
information contained in the ADA Accessibility Guidelines for Buildings and Facilities ( ADAAG)
( http:// www. access‐ board. gov/ adaag/). The understanding developed during this design
process helped the supplier in its solar‐ powered sign prototype design effort.
The supplier presented its new solar‐ powered sign prototype to the research team and
Advisory Panel members on December 4, 2008. The prototype sign was temporarily integrated
into the Bronco Express EDAPTS system and tested with respect to the functionality described
in the RFP. The research team and the Advisory Panel members accepted the prototype sign
design and asked the system supplier to manufacture four production‐ quality signs for the
Bronco Express EDAPTS System. Final versions of the solar‐ powered sign were delivered to Cal
Poly Pomona on December 28, 2008 for installation at the sites identified in the RFP. The final
product operates over cellular networks, accommodates both sight‐ challenged and hearing‐challenged
passengers, and has the following features:
• Entirely solar‐ powered, making connection to a commercial line AC
source unnecessary.
• Mounts on a 6‐ inch steel pole, approximately 8 feet above ground.
• Uses a solar panel typically mounted on top of the pole, which is typically
out of reach to vandals.
• Has an estimated 6‐ 7 day run time with no sunlight on solar panels
• ADA compliant, using 3‐ inch characters in the “ one‐ line” mode or 2‐ inch
characters in the “ two‐ line” mode.
• ADA compliant, using a text‐ to‐ speech engine in the sign to announce
expected bus arrival times when passengers press the pole‐ mounted
button.
− Sign Post and Foundation
1 Section 508 refers to Section 508 of the Rehabilitation Act. In 1998, Congress amended the
Rehabilitation Act to require Federal agencies to make their electronic and information technology
accessible to people with disabilities.
Section 508 was enacted to eliminate barriers in information technology, to make available new
opportunities for people with disabilities, and to encourage development of technologies that will help
achieve these goals. The law applies to all Federal agencies when they develop, procure, maintain, or
use electronic and information technology. Under Section 508 ( 29 U. S. C. § 794d), Federal agencies must
give disabled employees and members of the public access to information that is comparable to the
access available to others.
Meeting Section 508 requirements is also the policy of the California State University to make
information technology resources and services accessible to all CSU students, faculty, staff and the
general public regardless of disability.
11
Once the sign design was accepted by the research team and the Advisory Panel members, the
Cal Poly Pomona Facilities Department personnel worked with the system supplier to establish
structural and dimensional specifications for sign posts and foundations. Procedures were also
developed for installing the signs on campus property.
The Facilities Department personnel, along with the research team and PTS, conducted an
investigation of the four designated sites and evaluated the sites from the view of passenger
demand, solar coverage, utilities, ADA accessibility, soil conditions, and adjacent surroundings
of the bus stops at the sites. After the investigation, the Facilities personnel identified the
following site design criteria:
• Solar energy from a sign mounted solar panel could not be utilized at the Building 94
bus stop site due to large trees in the stop area. The sign’s solar panel needed to be
moved to the roof of an adjacent building. A 50‐ ft cable run was needed to allow
running a low voltage wire bundle to connect the remotely located solar panel to the
sign at the bus stop site.
• Sidewalks at two sites ( Building 94 and CLA Building) had to be reconstructed in order to
install the solar‐ powered signs. The new sidewalks had to be ADA compliant.
• Concrete pads were needed at the sites of University Village and Parking Lot B. The new
pads provided an area for people to stand while waiting for buses.
• All sign posts had to be painted to meet the University color standards.
• All sign posts had to be high enough to provide a vertical clearance of 8 ft above the
ground for signs.
• All sign posts required a solid concrete foundation to securely hold the pole and sustain
the sign weight ( approximately 200 pounds) during environment stress conditions.
− Sign Installation
After establishment and definition of the sign post design criteria, the Cal Poly Pomona
Facilities Department did the detailed structural design of signposts and developed a sign
installation plan for the four solar‐ powered signs. Facilities Department personnel started the
actual installation of signs on December 27, 2008 and completed the installation on January 7,
2009. Figures 5 and 6 show the signs installed at the Building 94 and the University Village sites.
Appendix A provides the detailed structural design of sign posts and the site layout design of
sign foundations.
4.4 System Testing
After completion of sign installation, the system supplier did a one‐ day on‐ site system test. The
supplier, working with PTS personnel, checked the communications and data flows from APCs,
MDTs, and AVLs to the supplier’s Data Center where the system software and databases reside.
They also verified the web services provided by the two web portals and inspected the
12
messages displayed on the solar‐ powered signs. Through this system test, the supplier ensured
that the installed system performed to meet the requirements described in its proposal. The
“ real‐ time” bus arrival information displayed on the four solar signs was verified to match the
time estimates provided by the system software. Figure 7 shows system supplier personnel
checking the wireless connection from the sign to the EDAPTS system server.
Since this on‐ site system test was a manufacturers’ bid compliance test, it did not verify if the
installed system had fully met all the functions originally described in the EDAPTS RFP. Also it
did not validate if the installed system met the total operational requirements envisioned by
the University. To accomplish this, a comprehensive system verification and validation was
performed by Cal Poly Pomona and Bronco Express. Section 6 describes the system verification
and validation plans and the test procedures. It also provides detailed results of the system
test.
Figure 5 Solar‐ Powered Sign at the Building 94 Bus Stop
13
Figure 6 Solar‐ Powered Sign at the University Village Bus Stop
Figure 7 System Testing
14
4.5 Bronco Express EDAPTS System Ribbon Cutting Ceremony
Following the successful installation of roadside information display signs and the testing of the
Bronco Express EDAPTS System, Cal Poly Pomona hosted a ribbon cutting ceremony on January
8, 2009 ( see Figure 8).
This ceremony marked the opening day of using the Bronco Express EDAPTS System as an
integral part of the University shuttle bus service system. The ceremony provided marketing
opportunities to promote the use of the system. Reporters from Cal Poly Pomona’s newspaper,
PolyCentric, wrote and published an article to introduce the Bronco Express EDAPTS System to
students, faculty, and staff of Cal Poly Pomona. Reporters from the local newspaper, San
Gabriel Valley Tribune, also wrote and published an article entitled “ Cal Poly Pomona develops
small transit system for mass use” to describe the Bronco Express EDAPTS System. The Inland
Empire Daily Bulletin considered the use of solar energy as an innovative green ITS solution,
providing excellent benefits to everyone in the Cal Poly Pomona community.
Figure 8 The Solar‐ Powered Sign Is Officially Unveiled at the Bronco Express EDAPTS
Inauguration Ceremony
15
5. OVERVIEW OF THE INSTALLED BRONCO EXPRESS EDAPTS SYSTEM
The Bronco Express EDAPTS System utilizes a service‐ based business model. The system supplier
operates and maintains the system for Cal Poly Pomona through a comprehensive service
agreement. This service agreement provides all aspects of maintenance and operations,
including all recurring and non‐ recurring costs required for continued day‐ to‐ day operation of
the system.
System components are connected to the system supplier’s data center, which is located at the
system supplier’s main facility in Los Angeles, California. The data center houses the Bronco
Express system server, receiving and analyzing vehicle location and passenger loading
information from all buses, and transmitting the data back in various formats to all system
elements located on the Cal Poly campus and to the web clients.
Table 1 shows how the Bronco Express System components as they appear in the EDAPTS RFP,
the supplier’s proposal, and in the final installed system. Figure 9 shows a graphical overview of
the installed system.
Table 1 System Components in the EDAPTS RFP, System Supplier’s Proposal, and
Installed System
EDAPTS Components
Requested
in RFP
Pledged in
System
supplier’s
Proposal
Implemented
1
Provide 8 sets on onboard
equipment, including AVL, MDT,
emergency button, automatic
passenger counter, wireless
communications
Yes Yes Yes
2
Vehicle‐ to‐ central site wireless
communications system
Yes Yes Yes
3 Central Site Server Software Yes Yes Yes
4
Transit Management Dispatch Client
Software
Yes Yes Yes
5
Provide 4 dynamic messaging signs
with wireless communications at bus
stops
Yes Yes Yes
6
Dynamic messaging sign wireless
communications system
Yes Yes Yes
16
Figure 9 Installed Bronco Express EDAPTS System
5.1 Bronco Express Vehicle On‐ Board Equipment/ Vehicle‐ to‐ Central Site Wireless
Communication System
Vehicle on‐ board subsystems were installed in all eight Bronco Express shuttle buses,
including buses owned by Cal Poly Pomona and those owned by Laidlaw. The equipment
installed consists of an AVL Modem, a Mobile Data Terminal ( MDT), and an Automatic
Passenger Counter ( APC).
Mobile Data Terminals
The MDT provides the system interface to drivers, and allows:
• Drivers to log on to the Bronco Express EDAPTS System using Bronco Express
employee ID and route number
• Drivers and dispatchers to send text‐ based messages to each other
• Drivers to declare an on‐ board emergency that sends a notification to the dispatch
clients
• Fuel percentage readings to be entered at the end of a driver’s shift
• Drivers to log out of the Bronco Express EDAPTS System
• Administrative functions to be accessed
17
Automatic Passenger Counting
The APC, installed above the doors on each Bronco Express bus, collects boarding and alighting
passenger information and transmits the information to the AVL unit. The AVL unit then
assembles and sends the passenger information to the data center. The passenger information
is time stamped and linked to the bus stop where the boarding and alighting events occurred.
Automatic Vehicle Location/ Wireless Communications System
The AVL unit installed on Bronco Express buses assembles information from MDTs, APCs, and
engine diagnostics and transmits the collected information to the data center through a cellular
data network.
5.2 Bronco Express Dispatch Clients
Bronco Express Dispatch Clients are a web‐ based application that can only be accessed by the
PTS manager and dispatchers using web browsers such as Firefox and Internet Explorer. These
portals use password protected interfaces to limit access to the Central Site Software and the
Transit Management Dispatch Client Software. Figure 10 shows the main screen presented by a
dispatch client, which includes a fleet status table, a map‐ based display on the upper‐ right part
of the window, and a listing of vehicle emergencies in the lower‐ right part of the window.
System Map
The system map shown in Figure 10 is a sample screen shot of the website. The Bronco Express
Dispatch Client provides operational information such as vehicle location, passenger loading,
speed, and direction in real‐ time for each vehicle in the fleet. This information is updated and
refreshed once every seven seconds. PTS managers and dispatchers using the system map can
visually see the location of all the Bronco Express buses, the passenger loading ( in terms of
percentage vehicle capacity used), the routes the buses are serving, and the speed of each bus.
Using the system map, PTS managers and dispatchers can also playback the exact positions of
buses serving a route in previous days or months. This vehicle history display function shows
the position, speed, time and direction of a specific bus during a specified time interval and
date. The vehicle history output also displays passenger‐ loading information at each stop
during the report period.
Fleet Status
The Fleet Status table as shown in Figure 10 provides information about bus number, ignition
status, speed and direction, and minutes since last position received for each bus. The buses on
the Fleet Status table can be sorted by name, ignition status, or last date and time of position
18
19
check in. They can also be grouped based upon vehicle type, ownership, or other desired
characteristics determined during system configuration.
Route & Driver Management
The Dispatch Client provides a set of tools for managing drivers and routes within the Bronco
Express system. Using these tools, PTS managers and dispatchers can modify the name and
color of a route in the display, change the name of a stop, delete a stop or path for a route, add
a new stop or path, and edit the name of a stop.
The Dispatch Client provides bus assignment and schedule assignment functions, allowing
buses to be automatically assigned to a route and schedules to be linked to a specific route. It
provides a driver assignment function to allow drivers to be assigned to their buses and routes.
The schedules can be assigned in either time intervals or using specific stop times. Currently the
Bronco Express does not utilize the schedule assignment function.
Arrival Prediction
Bus arrival prediction is one of the functions of the Transit Management Dispatch Client
Software. The installed system uses the Bronco Express Dispatch Clients to display arrival
predictions to the PTS manager and/ or dispatchers. These arrival predictions are provided to
the public through web portals, via mobile phones, ADA‐ compliant shelter signs, and call‐ in
phone systems.
Emergency and incident Repsonses
The Dispatch Client allows dispatchers to be alerted when a bus goes outside of a specified
perimeter area or over a set speed threshold. These alerts are stored in a log and emailed to
desiginated dispatchers. The Dispatch Client also sends out emergency alert mesesages via
email to desiginated individuals ( i. e. PTS managers and dispatchers) when an emegercy button
on a MDT is activated.
Reports
The Dispatch Client provides PTS managers and dispatchers with a set of operational reports.
One of the reporting functions is to view information related to the status of a bus at each stop
it makes. Information provided includes: stop name, arrival time, departure time, time
between previous and current departures, time since the bus was last at a stop, time between
previous departure time and the current departure time, and number of passengers that
boarded and exited the bus at the stop.
The Dispatch Client can summarize passenger information for each stop on a hourly, daily, or
monthly basis or on a custom, dispatcher specified period. The passenger information is
provided in Microsoft Excel tables and charts.
Figure 10 Bronco Express Dispatch Interface
20
5.3 Bronco Express Public Client
The Bronco Express public client is a web‐ based application that can be accessed by the public
using Web browsers such as Firefox and Internet Explorer. It uses a simplified and sanitized
non‐ password protected interface similar to the Transit Management Dispatch Client Software,
both of which are served with data from the supplier’s data center. The public client is not able
to access any of the system management functions provided to the dispatch and administrative
users.
Figure 11 shows the main screen presented by a public client ( see
http:// www. broncoshuttle. com), which includes a map‐ based display on the upper‐ right area
and a list of user options for announcement and available service routes on the upper‐ left area.
Users can visually see buses moving on the Google‐ based map, and get expected bus arrival
time when they move their mouse cursor over stop icons. They can also obtain vehicle loading
information by moving their mouse cursor over bus icons.
21
Figure 11 Bronco Express Public Client
22
5.4 Solar‐ Powered Signs/ Sign‐ to‐ Central Site Wireless Communications System
The four solar‐ powered roadside information displays provide expected bus arrival time via a
visible electronic sign array and an audible announcement detailing upcoming bus arrival
time( s) at the stop. The signs visually show expected bus arrival time through a LED display.
Pressing a push button on the signpost initiates an audible announcement of the expected bus
arrival time. The button used is robust and able to withstand the rigors of daily use by riders. It
is similar to the ones used to call for a WALK mode at signalized pedestrian crosswalks ( see
Figure 12).
Figure 12 Audible announcement push button on the Signpost
23
6. BRONCO EXPRESS EDAPTS SYSTEM EVALUATION
Following installation and supplier’s verification of the basic functionality, the research team
started the research evaluation process. The purpose of the evaluation is to determine if the
installed system is compliant with the user needs and the performance specifications as
requested in the Bronco Express EDAPTS RFP.
The evaluation involves two types of testing: system verification and system validation. The
system verification compares the performance metrics of the installed Bronco Express EDAPTS
System to those described in the RFP. The system validation checks if all the user needs and
requirements described in the RFP and Bronco Express EDAPTS Operations Guidelines are being
met by the installed system.
The research team developed both a system verification plan and a system validation plan.
Using the verification and the validation plans, the team worked with PTS and the system
supplier to determine if all the EDAPTS performance objectives are being met by the installed
system.
It is important to note that a failure of the installed system is defined as an instance that the
system does not meet a particular validation or verification criteria as described in this
document. However, a failure does not automatically indicate that the delivered system is non‐compliant
to the contractual agreement between Bronco Express and the selected system
supplier. It may simply indicate that a performance‐ for‐ cost tradeoff was made at some point
in the procurement process and the failure is the logical outcome of that tradeoff.
6.1 System Verification Plan and Testing
The Bronco Express system verification required an evaluation of the implementation of the
features selected for procurement. These features, documented in the Test Deployment EDAPTS
System Requirements and Performance Specification along with their associated metrics of
performance, were an important part of the EDAPTS RFP. Each feature and metric were tested
and rated as being compliant, non‐ compliant, or not applicable. This process provided the
EDAPTS project with a set of verification results that along with the Validation testing assisted in
the identification of several issues in the operational system, providing the research team with
data to make recommendations for system improvement.
24
System Verification Plan
Due to the large number of features and metrics requiring verification, a System Verification
Plan was created to assist researchers with the task. Metrics were categorized and grouped by
the type of verification that was required:
1. Inspection
2. Testing
3. System supplier certification
4. System supplier‐ provided licensing
Metrics verified by inspection were generally required a true or false response to the testing of
conformance. Metrics verified by testing were generally more involved, and hence required a
test plan to determine their conformance. The conformance of metrics verified by system
supplier certification or system supplier‐ provided licensing was established based on materials
provided by the system supplier. The Verification Plan further broke these categories into
general areas of verification such as on‐ board or roadside requirements to permit the research
team to evaluate related metrics more quickly during the verification process.
To further assist with evaluation, test worksheets were created for each metric requiring
inspection or verification. Each worksheet contained the identifier, title of the requirement, the
specified requirements for the metric, and the verification methods specified by the
performance specification generated during the operational requirements phase of the project
( see Figure 13). Each worksheet also contained a verification procedure providing further detail
for verifying the metric, and sections to be completed by the verifier of the metric. These
written sections as shown in Figure 13 included ( 1) the detailed steps taken while verifying the
metric, ( 2) a comments section on verification, ( 3) an indication as to whether the verification
requirements were met or not, and ( 4) a signoff field with date of completion.
While the use of worksheet for each metric created a sizable testing document, it simplified
verification evaluation by confining all information for each metric to a single page. This
method allowed for division of labor during verification allowing all materials for a specific
metric to be kept with the tester, and then easily reintegrated back into the testing document
once verification was complete.
A summary of verification findings is provided in Appendix B, while the completed verification
worksheets are included in Appendix C.
25
1.2.4 power_ switch_ MDT
EDAPTS Specification Identifier 2.2.4.1
Metric Requirement
The MDT shall have an accessible power switch in the driver’s
compartment
Verification Method
Verify in system design document or specifications. Inspect
deliverables to ensure compliance.
1
Verification Procedure
Review design documents provided by Syncromatics. Inspect
the installed system
Implementation:
Comments:
Verification Requirements Met YES 􀂉 NO 􀂉
Signature: Date:
Figure 13 Example Verification worksheet prior to use.
26
System Verification Testing
Verification of the Bronco Express EDAPTS system proceeded using the System Verification
Plan, with testing performed and documented by the research team. Each metric was
evaluated using the verification method and the procedure specified in the System Verification
Plan. The research team conducted 129 field metric verifications of the installed EDAPTS
system. The remaining 137 metrics were verified using a questionnaire sent to the system
supplier to address the System supplier Certification and System supplier‐ provided Licensing
sections of the Verification Plan. The questionnaire is provided in Appendix D.
System Verification Findings
The data recorded from the system verification worksheets were analyzed, detailing where
project needs were met and where deficiencies were identified. Overall, many of the
requirements laid out in the EDAPTS Performance Specification were met by the system
supplier.
1. Documentation standards such as readability, style, and formatting were well
met. Initially user manuals were not provided as set forth in the specifications, but were
later supplied by the system supplier. A higher‐ level system manual including theory of
operation and maintenance instructions was not provided. While the troubleshooting
sections included in some of the user manuals were thorough and complete, not all
manuals included a troubleshooting section.
2. Parts manufactured for both the roadside and vehicle onboard systems
largely met all requirements, including part edge trueness, corrosion resistance, mounting‐hole
tolerance, and part commonality.
3. Vehicle Onboard components functioned reliably, providing consistent
location updates to the system and users. However, very few parts bore manufacture
nameplates, and some installed cables lacked both the necessary label markers and cable
abrasion methods required under the specification. The locations of installed components
were well laid out, and did not impede driver view of the road or regular operations.
Despite all of this, the MDT offered only minimal functionality, providing emergency
functionality and messaging capabilities. Most of the required driver feedback functionality
was not implemented.
4. Roadside components also functioned reliably, providing clear minutes‐ until‐arrival
information to riders utilizing both visual and audible methods. The displays and
their posts and foundations were solidly constructed, and met the requirements for
weather and vandal resistance. ADA requirements for message display and clarity were also
met. While the signs function admirably, they do not meet the required level of fourteen
27
days of solar autonomy, nor do they recharge from a fifty percent battery capacity level
within the specified time duration.
Accuracy of the predicted arrival information was found to be questionable at times.
Extensive testing and documentation of this core function was made during both the
verification and validation phases of the evaluation to better understand the reasons for
this inaccuracy and assist the system supplier in resolving the issue. The inaccuracy could be
related to the supplier’s algorithm used for predicting bus arrival time and the lack of traffic
information on the bus routes.
5. The ATRMS client provided most of the features necessary to manage the
fleet, including both map‐ based and tabular vehicle tracking displays. It also provided
useful reports to the user, detailing both stop arrival times and passenger loading
information. As with the rest of the system it did not provide schedule adherence support,
a key RFP function required for operations. It also did not provide management or
diagnostic functionality for either the onboard or roadside hardware. This functionality is
less critical in a service‐ based system, but is still required as part of the original
specification. The ability to broadcast public‐ service or banner‐ type messages on the
roadside display signs was also missing from the client.
6. The central software and associated data store also provides most of the
required functionality and supports most of the specified features such as data store
management and backup, requirements related to capacity, security, and uptime, as well as
response times for both data traversal through the software and to user queries. It does
not provide open access to the data store nor the necessary documentation necessary for
doing so.
The system as a whole met the capacity and support requirements set out in the specification,
supporting far larger quantities of elements such as vehicles, drivers, stops, and routes than
those set forth in the EDAPTS RFP. The system also meets all applicable state and Federal
standards, including Department of Transportation ( DOT) requirements for vehicle onboard
components and Federal Communications Commission ( FCC) licensing requirements for
wireless data communications devices.
One of the primary deficiencies is the lack of schedule adherence capability throughout the
system, as it has no concept of fixed‐ route scheduling. It also does not conform to the EDAPTS
Data‐ Formatting Standard at any level of the system, detracting from the open‐ format ideal of
EDAPTS and complicating the possibility of part‐ interchangeability and the modification or
addition of new features in the future by the university or another system supplier.
28
6.2 System Validation Plan and Testing
The Bronco Express system validation required a comprehensive evaluation of the functionality
described in each operational scenario ( contained in the Bronco Express Operations Guidelines).
Each operational scenario was tested live on the installed system to determine if the installed
system provided the described system features and functions. All scenarios were tested and
rated as either having full compliance, non‐ compliance, partial compliance, or not applicable. A
partial compliance rating in a scenario indicates that the system met some, but not all objectives
within that specific scenario. Using this process, the team discovered some issues and
shortcomings of the installed system, and established a mechanism for monitoring system
performance and developing recommendations for system improvements. The results of this
effort provided the EDAPTS project with a set of validation findings that were beneficial to
Bronco Express and potentially to other small transit agencies desiring to deploy their own
EDAPTS system.
System Validation Plan
The validation of each operational scenario began with a detailed review of each scenario,
identifying key elements, such as the specific conditions of the situation encountered, the user
needs to be addressed, and the desired functional criteria to be validated. Please see the
following sample operational scenario to help clarify the process used ( see Figure 14). The
important key elements to be addressed are underlined to bring attention to them.
Upon identification of all key aspects of a scenario, the research team then articulated all
operational characteristics or user needs associated with this operational scenario in an easy to
understand format. The characteristics gleaned from the below scenario are listed as follows:
• The system shall provide a bus schedule.
• The Bronco Express Automatic Transit Arrival Sign provides bus information
for all routes, such as arrival times and “ out of service” announcement.
• The system shall constantly update the shuttle arrival times on the Bronco
Express Automatic Transit Arrival Sign at least every 7 seconds.
• Promotional material describing the Bronco Express EDAPTS System shall be
provided to users ( i. e. student, faculty and visitors using the shuttle service).
29
SAMPLE OPERATIONAL SCENARIO ( EDAPTS Operations Description Section 4.1.1):
A professor walks up to a bus stop at 15 minutes before the hour to get a ride to
his class. He knows that buses serving Routes A, B, and C pass through this stop,
however he would like to catch Route B. He is not too concerned about being late
to his class, since he knows the Route B bus is scheduled to arrive at the stop 12
minutes before the hour and will drop him off at his lecture destination at 3
minutes before the hour. This would allow him to be in his class by 1 minute
after the hour and ready to teach at 10 minutes after.
The Bronco Express Automatic Transit Arrival Sign installed at the bus stop
provides him with information for all routes by successively displaying the
following messages:
“ Rt A here in 10 minutes”
“ Rt B here in 4 minutes”
“ Rt C OUT OF SERVICE”
Each message is displayed for approximately 7 seconds, then the pattern repeats.
The professor notes Route B is running a minute late, but feels comfortable since
the information displayed on the Bronco Express EDAPTS bus sign has
demonstrated itself to be accurate. He also notes that Route C is not running and
wonders if it is because the bus has had a mechanical failure or the driver is on
break. He knows these are the most probable explanations because he read the
promotional material distributed via email and in the CPP campus newspaper,
Poly Post, when the new EDAPTS system was installed.
The Route B bus arrives as predicted at 11 minutes before the hour, the professor
boards and the bus departs. The bus ends up gaining a little time on the way to
his destination and arrives on schedule at 3 minutes before the hour.
The professor gets off the bus, walks to his classroom, and is on time.
Figure 14 Sample Operational Scenario for Validation Plan Development
Keeping these operational characteristics in mind, the research team then developed specific
test steps and carried out those steps to validate the scenario. See the sample validation steps
in the sample below.
30
Operational Scenario Validation Steps
1. Create a data collection sheet ( or map) that chronicles and details the professor’s
( tester’s) experience including his arrival at the initial bus stop, wait for the bus, ride
on the bus, arrival at the last bus stop and walk to his final destination.
2. Take the planned validation trip, noting all times on the data collection sheet.
3. Record data and observations, including any special factors and impressions.
Required observations are:
1. Did the system provide a bus schedule?
2. Did the Bronco Express Automatic Transit Arrival Sign provide bus
information for all routes?
3. Did the shuttle arrival times on the Bronco Express Automatic Transit
Arrival Sign update every 7 seconds?
4. Was promotional material for EDAPTS system provided?
The research team developed the overall System Validation Plan by creating an individual
validation plan for each operational scenario included in the Bronco Express EDAPTS Operations
Guidelines. This System Validation Plan is organized by the following sections, and can be found
in Appendix E.
1. Riding the Bronco Express Shuttles
2. Driving the Bronco Express Shuttles
3. Dispatching Drivers and Vehicles
4. Managing Bronco Express Services
5. Laidlaw Management Tasks
6. Maintaining the EDAPTS System
System Validation Testing
Validation of the Bronco Express EDAPTS system commenced using the System Validation Plan.
These test activities were carried out and documented by the research team. The resulting
data, including any system performance measures addressed, were recorded in the validation
data worksheets.
The system validation involved two distinct types of activities: ( 1) direct observation of the
operational performance aspects of the installed system and ( 2) a questionnaire survey to the
31
32
system supplier. The research team conducted nineteen individual validation tests in the direct
observation and measurement activity, including some statistical analyses of system
performance measures. The survey activity utilized a questionnaire sent to the system supplier
requesting responses to several technical and logistics based questions. This survey was
developed by the research team and addressed eight sets of operational scenarios, primarily
related to maintenance and troubleshooting issues associated with operation of the installed
system.
System Validation Results
The data resulting from the system validation was recorded, analyzed, and a validation report
was prepared showing where needs were met and where deficiencies were identified. The
validation report is provided in Appendix E.
Table 2 shows a summary of the validation results. The validation test concluded that the
installed system met the user needs and operational requirements described in sixteen
operational scenarios. The installed system failed ten operational scenarios. The majority of the
failures were in scenarios related to functionality of the MDT devices. The following table
summarizes the results for each of the twenty seven validation tests.
Table 2 Summary of Validation Test
RIDING THE BRONCO EXPRESS SHUTTLES
Operational Scenario Notes
3.1.12 CPP professor walks
up to a bus stop to
catch a bus
Pass / Fail / Not Validated
This scenario was successfully validated. Posing as a professor, the test observer felt very
comfortable arriving at a stop and trusting the estimated arrival time displayed by the sign.
The Bronco Express roadside information display was very valuable and helpful, keeping the
observer informed as to when the desired bus was going to arrive. Because the Bronco
Express system does not have a published schedule with exact stop times, the complete
validation of this scenario was not possible. However, the installed EDAPTS system did provide
expected bus arrival times to riders as envisioned.
3.1.2 CPP Student in the
library needing to
catch a bus
Pass / Fail / Not Validated
This scenario was successfully validated. The web‐ services provided by the Bronco Express
EDAPTS System are very effective in providing estimated bus arrival times. The website is very
easy to navigate through and provides significant information on bus operations. It shows
estimated arrival time, bus direction, bus passenger loads and the exact location of the bus on
its route. The location of the bus is updated approximately every 7 seconds. The website also
provides bus status ( i. e. “ out of service”, “ on route”). The estimated bus arrival time
information displayed on the sign agrees with the information provided on the website.
3.1.3 CPP Student with a
cell phone needing to
catch a bus ( Possible
future feature)
Pass / Fail / Not Validated
This scenario was not tested. The Bronco Express system does not provide a voicemail service.
2 3.1.1 refers to the Section 3.1.1 scenario in the System Validation Plan.
33
Table 2 Summary of Validation Test ( Cont’d)
RIDING THE BRONCO EXPRESS SHUTTLES
Operational Scenario Notes
3.1.3A CPP Student with a
cell phone needing to
catch a bus
Pass / Fail / Not Validated
This scenario was successfully validated. The text messaging feature provided a very easy way
to find out the bus arrival time for any stop. The transaction time was faster than what was
envisioned in the scenario and the estimated arrival time was accurate. Each bus stop had its
own identification number which allowed only one text message to be sent in order to receive
the bus arrival time.
3.1.4 CPP Student with a
web‐ enabled cell
phone needing to
catch a bus3 ( Possible
future feature )
Pass / Fail / Not Validated
This scenario was successfully validated. The features provided by the website when accessed
via a web‐ enabled phone are similar to the website features described in Section 3.1.2 of the
Validation Plan. The mobile friendly website provides useful information including shuttle
arrival time and a live map. This provided information makes it easy for anyone with a web‐enabled
phone to find the status of a shuttle.
The small format sign described in the original scenario was not procured by Cal Poly Pomona
and could not be tested.
Table 2 Summary of Validation Test ( Cont’d)
3 This scenario, different from Section 3.1.3 scenario, can access to the public website ( http:// www. broncoshuttle. com) of the
Bronco Express EDAPTS System.
34
DRIVING THE BRONCO EXPRESS SHUTTLES
Operational Scenario Notes
3.2.1 Cal Poly or Laidlaw
driver starting the
day’s work
Pass / Fail / Not Validated
This scenario was not successfully validated. The power‐ up procedures of the MDT are different than
envisioned. In the envisioned scenario, the MDT power depends on the ignition switch position, such
that when the ignition is turned on, the MDT powers up. In the installed system, this is only true if the
bus battery switch has been left in the “ ON” position, and this is not the normal end of service situation.
If the driver turns the battery switch to the “ OFF” position, the MDT does not have power and will not
power up by simply turning the ignition switch to the “ ON” position. When the driver then turns the
battery switch to the “ ON” position and turns on the bus ignition switch, the driver is also required to
press a MDT button to power up the MDT. In this scenario test, the MDT had not been powered up since
the last time the battery switch had been changed from the “ OFF” position to the “ ON” position,
preventing automatic power‐ up of the MDT.
In addition, instead of the asking the driver to select his name and verify his personal ID number the MDT
asked the driver to enter his personal ID number and verify his name. Although the login feature
described in this scenario was a bit different, the login feature provided by the MDT did allow the driver
to login to the MDT. Similarly, instead of the driver selected a route from a list of routes the driver was
required to enter the route and then confirm it.
During the login process the MDT did not prompt the driver to enter the vehicle’s odometer reading as
envisioned in the scenario. After the driver logged into the MDT, nothing else really happened on the
MDT. The MDT did not display the stop where the driver would begin the route, did not start displaying
the time in a large digital format and did not remove all other information when the driver reached a
specified speed. In addition, the MDT went into a “ power‐ save” mode after approximately one and a half
minutes of inactivity. When the driver arrived at a stop the MDT did not indicate that the bus had arrived
at the stop nor did it indicate and countdown a scheduled time to depart from the stop.
Table 2 Summary of Validation Test ( Cont’d)
35
DRIVING THE BRONCO EXPRESS SHUTTLES
Operational Scenario Notes
3.2.2 Cal Poly or Laidlaw driver
changing shift
Pass / Fail / Not Validated
This scenario was conditionally validated. The MDT function did not provide a “ Driver
Shift Change” function, but it did provide log‐ in and log‐ out functions that could be used a
similar way. The relieved driver can use the log‐ out function to sign out of the MDT and
the relief driver can use the log‐ in function to sign into the MDT. Instead of prompting the
relieved driver to input an odometer reading before logging out, the MDT prompted the
driver to input a fuel percentage reading. After the relieved driver signed out, the relief
driver was able to log‐ in from the main menu. Instead of selecting his name, the MDT
required the relief driver to enter his Personal ID Number and confirm his name.
Information relating to the shift change transaction might have been collected, stored and
transmitted to the central site, but reports are not available to confirm this.
3.2.3 Cal Poly or Laidlaw driver
logout
Pass / Fail / Not Validated
This scenario was not successfully validated. Many features in this scenario were not
available. For instance, the MDT does not determine the end of the driver’s day. Also, the
MDT does not record deadhead4 miles. The driver is able to log‐ out using the MDT and is
prompted for a fuel percentage level, but not an odometer reading as envisioned.
Information relating to the log‐ out transaction might have been collected, stored and
transmitted to the central site, but reports are not available to confirm this.
3.2.4 Cal Poly or Laidlaw driver
on route and picking up
passengers
Pass / Fail / Not Validated
This scenario was not successfully validated. This scenario failed its validation test
because none of the features are available. The MDT does not display the current time
after arriving at a stop. A “ CPP Rider” button is not available and the MDT does not show
the time of day while the vehicle is in motion.
Table 2 Summary of Validation Test ( Cont’d)
4 Deadhead refers to a bus that transports no passengers during a trip.
36
DRIVING THE BRONCO EXPRESS SHUTTLES
Operational Scenario Notes
3.2.5 Cal Poly or Laidlaw driver
on route and picking up
passengers with automatic
passenger counter ( APC)
( POSSIBLE FUTURE
FEATURE)
Pass / Fail / Not Validated
This scenario was not successfully validated. Although the buses are equipped with fully
functional APCs the other features described in this scenario depend on the MDT and are
not available. The MDT does not display APC passenger counts and there is not a “ Riders
On Board” counter available.
37
Table 2 Summary of Validation Test ( Cont’d)
DRIVING THE BRONCO EXPRESS SHUTTLES
Operational Scenario Notes
3.2.6 Dangerous situation on
bus
Pass / Fail / Not Validated
This scenario was not successfully validated. The emergency button is not installed in the
envisioned location ( i. e. below the driver’s left thigh) nor is it in an alternate area that is
out of sight of passengers when pressed/ activated. Once the button is pressed, the
emergency message is sent as required, but it does not require the button to be held for
more than 1.5 seconds.
When the emergency button is pressed while the MDT is in a “ power‐ save” mode, the
emergency message is sent and the MDT is taken out of its “ power‐ save” mode. When
the emergency button is pressed, it immediately alerts the Cal Poly Pomona dispatcher
but not the First Transit dispatcher. This is because the First Transit dispatcher has not
been given access to the dispatch console functions. Should First Transit be given
“ dispatcher” access, this function would be available to them as well.
The Cal Poly Pomona dispatcher is not alerted audibly and the on‐ screen visual alert itself
is not as envisioned; the console does not flash and the emergency alert message looks
the same as any other message sent from the MDT. When the emergency button is
pressed the bus is not automatically put in a “ GPS Tracking Mode”, although bus updates
frequency meets the envisioned rate. Buses can manually be put in a “ tracking mode”
during which the system map zooms in on the bus and follows its every move. The
dispatch console is not locked out of its normal functions during the emergency
notification process and the system never prompts the dispatcher to ask a coded question
as envisioned.
Observers Note: A few of these issues and failures might be more related to Bronco
Express/ PTS operational process limitations than with installed hardware/ software issues.
38
Table 2 Summary of Validation Test ( Cont’d)
DRIVING THE BRONCO EXPRESS SHUTTLES
Operational Scenario Notes
3.2.7 Going on break
Pass / Fail / Not Validated
This scenario was not successfully validated. None of the envisioned MDT features were
available. The MDT does not indicate the driver’s scheduled arrival time at each stop as
they arrive at the stop. The MDT does not know when the driver’s break is and does not
countdown the break time. The vehicle does not have an on vehicle electronic route sign
that they can change to show “ on‐ break” status and the MDT does not report arrivals and
stops.
3.2.8 Fueling
Pass / Fail / Not Validated
This scenario was not successfully validated. The MDT does not provide a fueling
function. A driver is not prompted to enter a gallon amount or odometer reading during
the fueling process. The number of gallons and odometer readings is not recorded by the
MDT. The system does record fuel percentage readings at the end of a driver’s shift ( if
entered by the driver), but this was not what was envisioned in this scenario.
39
Table 2 Summary of Validation Test ( Cont’d)
DISPATCHING DRIVERS AND VEHICLES
Operational Scenario Notes
3.3.1 Dispatchers at work
Pass / Fail / Not Validated
This scenario was successfully validated. The dispatcher console shows a system map to
monitor real‐ time bus locations. The console has a system table that summarizes the fleet
status. It is similar in appearance, but not exactly the same as the one described in the
scenario. The system map updates bus location every seven seconds, more frequently
than the once‐ per‐ minute envisioned. The fleet status information is updated every
minute. The dispatcher is able to easily monitor the real‐ time bus location using the
dispatcher console.
3.3.2 Dispatchers know where
vehicles are
Pass / Fail / Not Validated
This scenario was successfully validated. The test observer noted only one minor problem.
Dispatchers are not able to see a name change in the fleet status table because the table
itself does not provide a section for drivers’ names. However, Cal Poly Pomona dispatchers
are able to communicate with the drivers via a dedicated radio channel and First Transit
dispatchers are able to communicate with the drivers using mobile phones. The
dispatchers are able to monitor the buses at all times using the system map. The drivers
are able to log‐ in and log‐ out of the MDT.
3.3.3 Dispatch bus with serious
mechanical failure
Pass / Fail / Not Validated
This scenario was not successfully validated. This is primarily because of MDT and console
functions that are not provided. Neither the drivers nor the dispatchers are able to change
the status of the buses on the fleet status table. The dispatcher’ console also does not
have an “ Incident Clearance Report” button.
40
Table 2 Summary of Validation Test ( Cont’d)
MANAGING BRONCO EXPRESS SERVICE
Operational Scenario Notes
3.4.1 Using passenger loading
reports to optimize
vehicle size
Pass / Fail / Not Validated
This scenario was successfully validated. The reports provided by the system are very
helpful. A Bronco Express manager is able to view reports showing daily, monthly, and
yearly passenger loading reports for all routes.
3.4.2 Using schedule adherence
reports to adjust schedule
( Potential future feature)
Pass / Fail / Not Validated
This scenario was not successfully validated. Although the system provides managers and
administrative assistants with a Schedule and Schedule Adjust section, it does not have a
function to adjust schedules based on the actual travel times experienced. Also, the
system does not recommend a new bus schedule based on the statistical patterns derived
from the actual travel time of buses on a specific route.
41
Table 2 Summary of Validation Test ( Cont’d)
LAIDLAW MANAGEMENT TASKS
Operational Scenario Notes
3.5.1 Providing the monthly
report to Cal Poly
Pass / Fail / Not Validated
This scenario was successfully validated. A Bronco Express manager is able to generate a
monthly report showing the passenger boarding of each stop. The report shows passenger
loading for any time period specified. Reports are broken down to show the loading
information for every stop in a drivers shift. The report shows the total number of
passengers for each stop and route. Some minor problems exist in that the manager is not
able to select the output report file type, the generated report is always given in Excel
format only, and no “ button” function is available to print the report.
42
Table 2 Summary of Validation Test ( Cont’d)
MAINTAINING THE EDAPTS SYSTEM
Operational Scenario Notes
3.6.1 Schedule and route
updates
Pass / Fail / Not Validated
This scenario was successfully validated. The system provided many features for creating,
modifying and deleting route schedules. If a route is added to a stop the signs will
automatically recognize the new route. The system does not include a “ button” to
automatically deploy the schedule to all MDTs and real- time bus arrival signs as
envisioned. MDTs do not incorporate support for route schedule information such as this.
3.6.2 Addition of new stops on
a route
Pass / Fail / Not Validated
This scenario was successfully validated. The MDT does not report GPS coordinates to the
driver, but GPS coordinates are not required to add stops to a route. The addition of new
stops on a route is a simple “ click- n- add” process based only on the map display graphic.
3.6.3 On‐ board Hardware
Maintenance
Pass / Fail / Not Validated
This scenario was successfully validated. The MDT is physically easy to remove and
reinstall. An MDT user manual is provided that showed all MDT wiring. However, the
manual does not provide testing procedures to ensure that the MDT is working properly.
Given the simplicity of the MDT, these procedures may not be strictly necessary, though
they were envisioned. First Transit dispatchers aren’t able to communicate with technicians
through radios but Cal Poly Pomona dispatchers are.
3.6.4 Dispatch Console
Maintenance
Pass / Fail / Not Validated
This scenario was successfully validated. The dispatch console uses a web interface;
consequently there is no need to install software for the dispatch console to work properly.
If the dispatch console fails to work properly, Cal Poly Pomona personnel report the
problem to the system supplier, who then affects repair. Once the system supplier fixes the
problem, the PTS can determine if all EDAPTS dispatching functions are working properly
using the Track Website User Manual provided by the system supplier.
43
44
Table 2 Summary of Validation Test ( Cont’d)
MAINTAINING THE EDAPTS SYSTEM
Operational Scenario Notes
3.6.5 Vehicle to central dispatch
communication link fails
Pass / Fail / Not Validated
This scenario was conditionally validated. The manuals provided by the system supplier
do not provide troubleshooting guidelines or system diagnostic tools related to this scenario.
Since this is envisioned as a system wide failure, Cal Poly Pomona simply needs to contact
the system supplier who then affects repair.
3.6.6 On‐ board equipment fails
Pass / Fail / Not Validated
This scenario was not successfully validated. Although the driver is able to send messages
to the dispatcher via the MDT and the system supplier provides RMA ( Return Merchandise
Authorization) paperwork, the MDT does not indicate a failure in the APC and the APC’s
power could not be cycled by the driver.
3.6.7 Transit sign fails
Pass / Fail / Not Validated
This scenario was successfully validated. Although the sign does not display an “ Out Of
Service” message, it does announce an “ Out Of Service” message ( audibly) that provides an
error code to be given to the system supplier. Timestamps are recorded for the last time a
device was reported to the servers, and more detailed failure logs are kept on the devices as
well.
3.6.8 Computer console or
server fails
Pass / Fail / Not Validated
This scenario was successfully validated. The dispatch console does display warning
messages at the bottom left corner of the screen when an error occurs. If a problem occurs
with the dispatch console, Cal Poly Pomona is only responsible for contacting the system
supplier. The system supplier is responsible for updating the dispatch services and fixing
any problems like the one envisioned in this scenario.
7. CONCLUSIONS
The Bronco Express EDAPTS System, as installed and operated at the Cal Poly Pomona campus,
consists of eight sets of vehicle on‐ board subsystems ( including AVL units, APCs, and MDTs), four
solar‐ powered signs, and two web sites. This system is designed to provide a low‐ cost ITS
solution for operational needs identified by the Parking and Transportation Services of Cal Poly
Pomona.
The EDAPTS research team, observing the Bronco Express EDAPTS System installation process
and working with system supplier and PTS personnel, developed the system verification plan,
the validation plan and associated test procedures. Using these test plans and procedures, the
research team verified the installed subsystems and functionality against those required in the
RFP, those provided in the system supplier’s proposal and those described in the Bronco
Express EDAPTS Operations Guidelines.
System verification was a process of inspecting, testing, and investigating EDAPTS system
performance against the EDAPTS specifications set forth in the EDAPTS RFP. The verification
used a methodical approach derived from the detailed and hierarchically organized EDAPTS
performance specification utilized. The research team concluded that the installed EDAPTS
system largely meets all performance specifications, although it fell short in some key areas.
Generally, these failures were in areas originally specified by the EDAPTS RFP, but were not
promised by the system supplier.
The data from the system validation was recorded, analyzed, and documented in the validation
report. The validation test concluded that the installed system met overall user needs and
operational requirements. However, the installed system did fail ten operational scenarios and
the majority of the failures were in scenarios related to functionality of the MDT. For example,
the MDT ( 1) did not display the stop where the driver would begin the route, ( 2) did not start
displaying the time in a large digital format once the driver started driving and ( 3) did not
display the current arriving at a stop. The system supplier is aware of the MDT limitations and is
planning to upgrade the MDT features for the installed EDAPTS system through the service
agreement.
The system verification and validation demonstrated in this project proved to be very effective
in determining how well the installed EDAPTS system met the system functional requirements
and the operational characteristics and user needs described in the EDAPTS RFP. The processes
and test procedures developed by the team ensured that the verification and validation tests
are repeatable and well documented.
45
8. REFERENCES
• Xudong Jia and Jeff Gerfen. “ Bronco Express EDAPTS System Procurement
Documentation Package.” Technical Report, California PATH and Caltrans, 2008.
• Xudong Jia, Edward Sullivan, Cornelius Nuworsoo, and Neil Hockaday. “ EDAPTS
Cost/ Benefit Evaluation.” Technical Report, California PATH and Caltrans, 2007.
• Jeff Gerfen, Neil Hockaday. “ Development of Performance‐ Based Specifications for
Efficient Deployment of Advanced Public Transportation Systems ( EDAPTS), Technical
Report, California PATH and Caltrans, 2007.
• Xudong Jia, Jeff Gerfen, Neil Hockaday. “ Task Order 6403: Cal Poly Pomona EDAPTS Test
Deployment Operations Description, Version 6.0.”, Technical Report, California PATH and
Caltrans, 2007.
• US Department of Transportation. “ System Engineering for Intelligent Transportation
Systems: An Introduction for Transportation Professionals.” January 2007.
46
47
9. APPENDICIES
Appendix A Structural Design of Sign Posts and Site Layout Design of Sign
Foundations
Appendix B Summary of System Verification Findings
Appendix C Completed System Verification Worksheets
Appendix D Questionnaire to System Supplier
Appendix E Bronco Express EDAPTS System Validation Plan and Results
Implemented !
and ! Verified
1 . 1 . 1 . 1
A l l ! d o c u m e n t s ! s h a l l ! b e ! p r e s e n t e d ! c l e a r l y ! a n d ! c o n c i s e l y , ! a n d
r e f l e c t ! w r i t i n g ! o f ! a t ! l e a s t ! a ! 1 2 t h ! g r a d e ! l e v e l .
Yes
1 . 1 . 1 . 2
A l l ! d o c u m e n t s ! s h a l l ! b e ! c l e a r l y ! u n d e r s t a n d a b l e ! b y ! a u d i e n c e s
w i t h ! 1 2 t h ! g r a d e ! r e a d i n g ! c o m p r e h e n s i o n ! l e v e l .
Yes
1 . 1 . 1 . 3
A l l ! d o c u m e n t s ! s h a l l ! c o n f o r m ! t o ! t h e ! M I L " S T D " 9 6 2 D ! d o c u m e n t a t i o n ! s t a n d a r d , !
s e c t i o n ! 4 . 7 ! f o r ! c l a r i t y .
Yes
1 . 1 . 1 . 4
A l l ! d o c u m e n t s ! s h a l l ! c o n f o r m ! t o ! t h e ! U . S . ! G o v e r n m e n t ! P r i n t i n g ! O f f i c e ! S t y l e ! M a n u a l !
f o r ! s t y l e ! a n d ! g r a m m a r .
Yes
1 . 1 . 1 . 5
A l l ! c a b l e s ! a n d ! w i r e s ! o n ! w i r i n g ! d i a g r a m s ! s h a l l ! u t i l i z e ! u n i q u e ! i d e n t i f i e r s ! w h i c h !
m a t c h ! p h y s i c a l ! l a b e l s ! o n ! c a b l e s .
No
1 . 1 . 1 . 6
A l l ! w i r i n g ! d i a g r a m ! i n t e r " p a g e ! c o n n e c t i o n s ! s h a l l ! b e ! c l e a r l y ! m a r k e d ! a t ! t h e ! l e f t ! o r !
r i g h t ! h a n d ! s i d e ! o f ! t h e ! p a g e ! w i t h ! t h e ! w i r e ! o r ! c a b l e ' s ! u n i q u e ! i d e n t i f i e r .
n/ a
1 . 1 . 1 . 9
T h e ! S y s t e m ! M a n u a l ! s h a l l ! i n c l u d e ! a ! T h e o r y ! o f ! O p e r a t i o n ! o u t l i n i n g ! t h e ! o p e r a t i o n ! o f !
t h e ! s y s t e m ! a n d ! h o w ! i t ! f u n c t i o n s .
No
1 . 1 . 1 . 1 0
T h e ! S y s t e m ! M a n u a l ! s h a l l ! b e ! c o m p r e h e n s i v e ! a n d ! c o v e r ! a l l ! s y s t e m " o p e r a t i o n !
s c e n a r i o s ! i n ! c l e a r ! s t e p " b y " s t e p ! d e t a i l s .
No
1 . 1 . 1 . 1 1
T h e ! S y s t e m ! M a n u a l ! s h a l l ! i n c l u d e ! c l e a r ! s t e p " b y " s t e p ! i n s t r u c t i o n s ! f o r !
t r o u b l e s h o o t i n g ! a n y ! p o t e n t i a l ! s y s t e m ! p r o b l e m s .
No
1 . 1 . 1 . 1 2
T h e ! S y s t e m ! M a n u a l ! s h a l l ! i n c l u d e ! c l e a r ! s t e p " b y " s t e p ! i n s t r u c t i o n s ! f o r ! i n s t a l l i n g ! t h e !
E D A P T S ! s y s t e m .
No
1 . 1 . 1 . 1 3
T h e ! S y s t e m ! M a n u a l ! s h a l l ! i n c l u d e ! c l e a r ! s t e p " b y " s t e p ! i n s t r u c t i o n s ! f o r ! a l l ! n e c e s s a r y !
r o u t i n e ! o r ! s c h e d u l e d ! m a i n t e n a n c e ! p r o c e d u r e s .
No
1 . 1 . 1 . 1 4
T h e ! U s e r ! M a n u a l ! s h a l l ! b e ! c o m p r e h e n s i v e ! a n d ! c o v e r ! a l l ! u s e r ! o p e r a t i o n
s c e n a r i o s ! i n ! c l e a r ! s t e p " b y " s t e p ! d e t a i l .
Yes
1 . 1 . 1 . 1 5
T h e ! U s e r ! M a n u a l ! s h a l l ! i n c l u d e ! c l e a r ! s t e p " b y " s t e p ! i n s t r u c t i o n s ! f o r ! t r o u b l e s h o o t i n g !
c o m m o n ! p o t e n t i a l ! p r o b l e m s .
No
1 . 1 . 3 . 1
A l l ! d e v i c e s ! d i s p l a y i n g ! i n f o r m a t i o n ! t o ! o r ! r e q u i r i n g ! i n f o r m a t i o n ! f r o m ! a ! u s e r ! s h a l l ! b e !
e a s y ! t o ! u s e ! a n d ! d i s p l a y ! c l e a r ! o p e r a t i o n a l ! u s a g e ! i n s t r u c t i o n s ! t o ! t h e ! u s e r .
Yes
1 . 1 . 5 . 4
A l l ! p a r t s ! h a v i n g ! t h e ! s a m e ! m a n u f a c t u r e r ’ s ! p a r t ! n u m b e r ! a r e ! f u n c t i o n a l l y ! a n d !
p h y s i c a l l y ! i n t e r c h a n g e a b l e .
Yes
EDAPTS ! Specification
Cal ! Poly ! Pomona ! Deployment ! Feature ! Verification
1. ! ! Inspection
1.1 ! ! General ! Requirements
1
Implemented !
and ! Verified
EDAPTS ! Specification
1 . 1 . 5 . 1
A n y ! n o n " r a d i u s e d ! e x t e r n a l ! p a r t ! e d g e s ! s h a l l ! b e ! s m o o t h , ! s t r a i g h t ,
a n d ! t r u e .
Yes
1 . 1 . 5 . 2 A l l ! i n s t a l l e d ! p h y s i c a l ! p a r t s ! s h a l l ! h a v e ! s m o o t h e d ! ( r a d i u s e d ! / ! n o n " s h a r p ) ! c o r n e r s . Yes
1 . 1 . 5 . 3
A l l ! p h y s i c a l ! p a r t s ! s h a l l ! b e ! m a n u f a c t u r e d ! t o ! w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r !
s p e c i f i e d ! d i m e n s i o n s .
Yes
1 . 1 . 5 . 8
A l l ! i n s t a l l e d ! c a b l e s ! s h a l l ! u t i l i z e ! c a b l e ! c l a m p s , ! s p l i t ! l o o m , ! c a b l e
r a c e w a y s , ! o r ! o t h e r ! s i m i l a r ! m e t h o d s ! t o ! m i n i m i z e ! c a b l e ! a b r a s i o n ! a l o n g ! t h e ! l e n g t h ! o f !
t h e ! c a b l e .
No
1 . 1 . 8 . 1
A l l ! i n s t a l l e d ! p a r t s ! s h a l l ! b e a r ! a ! m a n u f a c t u r e r ' s ! n a m e p l a t e ! o r
s t i c k e r , ! c o n t a i n i n g ! t h e ! m a n u f a c t u r e r ' s ! n a m e , ! p r o d u c t ! p a r t ! n u m b e r ! a n d ! r e v i s i o n ! a s !
a p p l i c a b l e , ! a n d ! s e r i a l ! n u m b e r .
No
1 . 1 . 8 . 2
A l l ! f i e l d " i n s t a l l e d ! i n t e r f a c e ! w i r e s ! a n d ! c a b l e s ! s h a l l ! u s e ! s u i t a b l e ! g u a g e , ! s h i e l d i n g , !
a n d ! c o l o r ! f o r ! t h e ! a p p l i c a t i o n ! i n ! c o n f o r m a n c e ! w i t h ! a p p l i c a b l e ! S A E ! a n d ! s t a t e ! a n d !
f e d e r a l ! D O T ! s t a n d a r d s .
Yes
1 . 1 . 8 . 3
A l l ! i n s t a l l e d ! i n t e r c o n n e c t ! c a b l e s ! s h a l l ! b e a r ! a ! c a b l e ! m a r k e r ! a t ! s i x ! i n c h e s ! f r o m ! e a c h !
e n d ! o f ! t h e ! c a b l e , ! a n d ! a t ! r e g u l a r ! i n t e r v a l s ! a l o n g ! t h e ! c a b l e .
No
1 . 1 . 8 . 5
A l l ! e q u i p m e n t ! a n d ! a c c e s s o r i e s ! s h a l l ! b e ! a ! p r o d u c t ! o f ! g o o d ! w o r k m a n s h i p ! a n d ! s h a l l !
b e ! f r e e ! f r o m ! a n y ! d e f e c t s ! t h a t ! w i l l ! a f f e c t ! t h e i r ! a p p e a r a n c e ! o r ! s e r v i c e a b i l i t y . !
Yes
1 . 1 . 1 . 7 A l l ! w i r i n g ! d i a g r a m s ! s h a l l ! r e f l e c t ! i n d i v i d u a l ! s i g n a l ! l e v e l s ! f o r ! m u l t i " c o n d u c t o r ! c a b l e s . No
1 . 1 . 1 . 8
S y s t e m ! w i r i n g ! d i a g r a m s ! s h a l l ! i n d i c a t e ! a l l ! i n d i v i d u a l ! c o n d u c t o r s / s i g n a l s ! b y ! u n i q u e !
i d e n t i f i e r .
No
1 . 1 . 4 . 2
T h e ! t r a n s i t ! p r o p e r t y ! s h a l l ! h a v e ! t h e ! a b i l i t y ! t o ! s e l f " m a i n t a i n ! a l l ! s y s t e m ! E l e m e n t s ! d u e !
t o ! t h e ! a v a i l a b i l i t y ! o f ! s p a r e ! p a r t s ! a n d ! t h e ! c a p a b i l i t y ! t o ! r e t a i n ! a ! s u p p l y ! o f ! s p a r e s .
n/ a
1 . 1 . 8 . 8
I n ! c a s e ! o f ! c o n f l i c t ! b e t w e e n ! r e g u l a t o r y ! b o d y , ! c l a s s i f i c a t i o n ! a n d ! i n t e r n a t i o n a l !
r e g u l a t i o n s ! a n d ! r e q u i r e m e n t s , ! a n d ! t h i s ! s p e c i f i c a t i o n , ! t h e ! m o r e ! s t r i n g e n t !
r e q u i r e m e n t ! s h a l l ! t a k e ! p r e c e d e n c e .
Yes
1 . 1 . 8 . 1 2
I f ! e x t e n s i o n ! o f ! a n ! E D A P T S ! p r o t o c o l ! i s ! d e e m e d ! n e c e s s a r y , ! i t ! s h a l l ! b e ! d o n e ! i n ! a !
m a n n e r ! t h a t ! d o e s ! n o t ! i n t e r f e r e ! o r ! b r e a k ! c o m p a t i l b i l i t y ! w i t h ! e x i s t i n g ! d a t a !
e l e m e n t s , ! a n d ! s h a l l ! n o t ! d u p l i c a t e ! o r ! o t h e r w i s e ! r e p e a t ! e x i s t i n g ! f u n c t i o n a l i t y .
No
1 . 1 . 8 . 1 3
A l l ! v e n d o r " d e v e l o p e d ! s o f t w a r e ! s h a l l ! b e ! w r i t t e n ! i n ! a n ! i n d u s t r y ! s t a n d a r d , ! h i g h ! l e v e l , !
n o n " p r o p r i e t a r y ! l a n g u a g e .
Yes
1 . 1 . 8 . 6
A l l ! i n s t a l l e d ! e q u i p m e n t ! s h a l l ! s h a r e ! C o m p o n e n t " l e v e l ! p a r t ! c o m m o n a l i t y , ! a l l o w i n g !
f o r ! e a s e ! o f ! s w a p p a g e ! o r ! r e p l a c e m e n t ! w i t h ! m i n i m a l ! r e c o n f i g u r a t i o n .
Yes
2
Implemented !
and ! Verified
EDAPTS ! Specification
1 . 1 . 8 . 7
A l l ! u s e r ! o r ! m a i n t e n a c e ! a c c e s s i b l e ! h a r d w a r e ! ( i n c l u d i n g ! m o u n t i n g ! h a r d w a r e ) ! s h a l l !
s h a r e ! C o m p o n e n t " l e v e l ! p a r t ! c o m m o n a l i t y , ! a n d ! a l s o ! a t ! t h e ! s y s t e m " w i d e ! l e v e l !
w h e r e ! p o s s i b l e .
Yes
1 . 1 . 4 . 1 A l l ! s y s t e m ! e l e m e n t s ! s h a l l ! b e ! i n s t a l l a b l e ! b y ! q u a l i f i e d ! t r a n s i t ! p r o p e r t y ! p e r s o n n e l . Yes
2 . 1 . 3 . 1
A l l ! O n " B o a r d ! S y s t e m ! e l e m e n t ! m o u n t i n g ! h o l e ! p a t t e r n s ! s h a l l ! b e ! m a n u f a c t u r e d ! t o !
w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r ! s p e c i f i e d ! d i m e n s i o n s .
n/ a
2 . 1 . 3 . 2
A l l ! O n " B o a r d ! S y s t e m ! e l e m e n t ! m o u n t i n g ! h o l e ! d i m e n s i o n s ! s h a l l ! b e ! m a n u f a c t u r e d ! t o !
w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r ! s p e c i f i e d ! d i m e n s i o n s .
n/ a
2 . 1 . 4 . 1
A l l ! p o w e r ! c o n n e c t i o n s ! s h a l l ! b e ! f u s e d ! o r ! c i r c u i t ! b r e a k e r ! p r o t e c t e d ! a t ! t h e ! s o u r c e !
c o n n e c t i o n .
Yes
2 . 2 . 4 . 7
T h e ! M D T ! s h a l l ! r e c e i v e ! A P C ! b o a r d i n g ! a n d ! a l i g h t i n g ! d a t a ! f r o m ! t h e ! A P C , ! d i s p l a y ! a !
c u m u l a t i v e ! c o u n t ! t o ! t h e ! d r i v e r , ! a s s o c i a t e ! t h i s ! d a t a ! w i t h ! s t o p s ! d u r i n g ! t h e ! d a y , ! a n d !
i n c o r p o r a t e ! t h e ! d a t a ! i n t o ! t h e ! s t o p ! r e c o r d ! t r a n s m i t t e d ! t o ! t h e ! c e n t r a l ! s i t e ! f o r ! e a c h !
s t o p .
Yes
2 . 5 . 1 3 . 1
D o c u m e n t a t i o n ! d e t a i l i n g ! t h e ! c o m p l e t e ! p h y s i c a l , ! e l e c t r i c a l , ! a n d ! m e s s a g i n g !
r e q u i r e m e n t s ! f o r ! t h e ! i n t e r f a c e ! b e t w e e n ! t h e ! M D T ! a n d ! t h e ! a u t o m a t i c ! p a s s e n g e r !
c o u n t e r ! s h a l l ! b e ! p r o v i d e d ! b y ! t h e ! v e n d o r ! u p o n ! d e l i v e r y . !
Yes
2 . 5 . 1 4 . 2 T h e ! A P C ! u n i t ! s h a l l ! c o u n t ! b o a r d i n g s ! a n d ! a l i g h t i n g s ! a n d ! p r o v i d e ! d a t a ! t o ! t h e ! M D T . No
3 . 1 . 2 . 1
A l l ! O n " B o a r d ! C o m m u n i c a t i o n s ! e l e m e n t ! m o u n t i n g ! h o l e ! p a t t e r n s ! s h a l l ! b e !
m a n u f a c t u r e d ! t o ! w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r ! s p e c i f i e d ! d i m e n s i o n s .
n/ a
3 . 1 . 2 . 2
A l l ! O n " B o a r d ! C o m m u n i c a t i o n s ! e l e m e n t ! m o u n t i n g ! h o l e ! d i m e n s i o n s ! s h a l l ! b e !
m a n u f a c t u r e d ! t o ! w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r ! s p e c i f i e d ! d i m e n s i o n s .
n/ a
3 . 1 . 3 . 1 A l l ! p o w e r ! c o n n e c t i o n s ! s h a l l ! b e ! f u s e d ! o r ! b r e a k e r e d ! a t ! t h e ! s o u r c e ! c o n n e c t i o n . Yes
2 . 4 . 1 1 . 1
D o c u m e n t a t i o n ! d e t a i l i n g ! t h e ! c o m p l e t e ! p h y s i c a l , ! e l e c t r i c a l , ! a n d ! m e s s a g i n g !
r e q u i r e m e n t s ! f o r ! t h e ! i n t e r f a c e ! b e t w e e n ! t h e ! M D T ! w i r e l e s s ! d a t a " c o m m u n i c a t i o n s !
s y s t e m ! d r i v e r ! a n d ! t h e ! o n " b o a r d ! w i r e l e s s ! d a t a ! i n t e r f a c e ! s h a l l ! b e ! p r o v i d e d ! b y ! t h e !
v e n d o r ! u p o n ! d e l i v e r y .
No
2 . 5 . 1 4 . 1 T h e ! A P C ! s h a l l ! b e ! a b l e ! t o ! h a v e ! c o l l e c t e d ! d a t a ! r e t r i e v e d ! r e m o t e l y . Yes
2 . 6 . 1 6 . 1
D o c u m e n t a t i o n ! d e t a i l i n g ! t h e ! c o m p l e t e ! p h y s i c a l , ! e l e c t r i c a l , ! a n d ! m e s s a g i n g !
r e q u i r e m e n t s ! f o r ! t h e ! i n t e r f a c e ! b e t w e e n ! t h e ! M D T ! a n d ! t h e ! e m e r g e n c y ! a c t u a t o r !
s h a l l ! b e ! p r o v i d e d ! b y ! t h e ! v e n d o r ! u p o n ! d e l i v e r y .
No
1.2 ! ! On " Board ! Requirements
3
Implemented !
and ! Verified
EDAPTS ! Specification
4 . 1 . 2 . 1
A l l ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! e l e m e n t ! m o u n t i n g ! h o l e ! p a t t e r n s ! s h a l l ! b e !
m a n u f a c t u r e d ! t o ! w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r ! s p e c i f i e d ! d i m e n s i o n s .
Yes
4 . 1 . 2 . 2
A l l ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! e l e m e n t ! m o u n t i n g ! h o l e ! d i m e n s i o n s ! s h a l l ! b e !
m a n u f a c t u r e d ! t o ! w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r ! s p e c i f i e d ! d i m e n s i o n s .
Yes
5 . 1 . 2 . 1
A l l ! R o a d s i d e ! C o m m u n i c a t i o n s ! e l e m e n t ! m o u n t i n g ! h o l e ! p a t t e r n s ! s h a l l ! b e !
m a n u f a c t u r e d ! t o ! w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r ! s p e c i f i e d ! d i m e n s i o n s .
n/ a
5 . 2 . 2 . 2
A l l ! R o a d s i d e ! C o m m u n i c a t i o n s ! e l e m e n t ! m o u n t i n g ! h o l e ! d i m e n s i o n s ! s h a l l ! b e !
m a n u f a c t u r e d ! t o ! w i t h i n ! t h e ! g i v e n ! t o l e r a n c e ! o f ! t h e i r ! s p e c i f i e d ! d i m e n s i o n s .
n/ a
4 . 3 . 8 . 1
R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! p o s t ! s h a l l ! m e e t ! a p p l i c a b l e ! s t a t e ! a n d ! f e d e r a l ! D O T !
s t a n d a r d s ! f o r ! c r a s h ! s a f e t y .
Yes
4 . 4 . 9 . 1
R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! f o u n d a t i o n s ! a n d ! p o s t s ! s h a l l ! c o m p l y ! w i t h ! t h e !
U n i f o r m ! B u i l d i n g ! C o d e ! w i t h ! r e g a r d ! t o ! w i n d ! r e s i s t a n c e .
Yes
4 . 4 . 9 . 2
R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! f o u n d a t i o n s ! a n d ! p o s t s ! s h a l l ! b e ! e a r t h q u a q e ! r e s i s t a n t !
w h e n ! i n s t a l l e d ! i n ! e a r t h q u a k e " p r o n e ! a r e a s .
Yes
8 . 1 . 3 . 2
T h e ! C e n t r a l ! S i t e ! S o f t w a r e ! s h a l l ! p r o v i d e ! s e l f " t e s t ! d i a g n o s t i c s ! t o ! a i d ! i n ! f a u l t !
i s o l a t i o n .
No
8 . 5 . 1 0 . 1
D o c u m e n t a t i o n ! d e t a i l i n g ! t h e ! c o m p l e t e ! p h y s i c a l , ! e l e c t r i c a l , ! a n d ! m e s s a g i n g !
r e q u i r e m e n t s ! f o r ! t h e ! i n t e r f a c e ! b e t w e e n ! t h e ! C S S ! v e h i c l e ! c o m m u n i c a t i o n s ! s y s t e m !
d r i v e r ! a n d ! t h e ! c e n t r a l ! s i t e ! w i r e l e s s ! d a t a ! i n t e r f a c e ! s h a l l ! b e ! p r o v i d e d ! b y ! t h e ! v e n d o r !
u p o n ! d e l i v e r y .
No
6 . 7 . 1 1 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! t r a c k ! t r a n s i t ! v e h i c l e s ! v i a ! m a p "
b a s e d ! a n d ! t a b u l a r ! d i s p l a y .
Yes
6 . 8 . 1 3 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! t r a c k ! t r a n s i t ! v e h i c l e ! s c h e d u l e !
a d h e r e n c e ! i n f o r m a t i o n ! a n d ! d i s p l a y ! i t ! t o ! t h e ! u s e r .
No
6 . 9 . 1 6 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! t r a c k
t r a n s i t ! v e h i c l e ! l o a d i n g ! i n f o r m a t i o n ! a n d ! d i s p l a y ! i t ! t o ! t h e ! u s e r .
Yes
6 . 1 0 . 1 8 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! c o m p i l e ! a n d ! p r e s e n t ! r i d e r s h i p !
r e p o r t s ! f o r ! t h e ! u s e r .
Yes
6 . 1 1 . 2 0 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! c o m p i l e ! a n d ! p r e s e n t ! s c h e d u l e !
a d h e r e n c e ! r e p o r t s ! f o r ! t h e ! u s e r .
No
6 . 1 2 . 2 3 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! a l l o w ! t h e ! u s e r ! t o ! a d m i n i s t e r ! a l l !
s y s t e m ! u s e r s ! a n d ! t h e i r ! p e r m i s s i o n s .
Yes
1.4 ! ! Central ! Software ! Requirements
1.3 ! ! Roadside ! Requirements
4
Implemented !
and ! Verified
EDAPTS ! Specification
1 . 1 . 7 . 2
M a y d a y ! m e s s a g e s ! i n i t i a t e d ! b y ! t h e ! d r i v e r ! s h a l l ! b e ! r e c e i v e d ! w i t h ! t h e ! s p e c i f i e d !
p e r c e n t ! r e l i a b i l i t y .
Yes
1 . 1 . 6 . 1
R a w ! p a s s e n g e r ! f a r e ! o r ! p a s s ! i d e n t i f i c a t i o n ! n u m b e r s ! o r ! s t r i n g s ! t h a t ! d i r e c t l y ! i d e n t i f y !
a ! s p e c i f i c ! r i d e r ! m a y ! n o t ! b e ! s t o r e d ! a n y w h e r e ! i n ! t h e ! E D A P T S ! s y s t e m ! o r ! t r a n s m i t t e d !
a c r o s s ! a n y ! E D A P T S ! c o m m u n i c a t i o n s ! l i n k . ! A n y ! o b s f u c a t i o n ! m e t h o d ! o f ! t h e s e !
n u m b e r s ! m u s t ! b e ! o n e " w a y ! a n d ! n o n " r e v e r s i b l e , ! p r e v e n t i n g ! t h e ! t r a n s f o r m a t i o n !
b a c k ! t o ! a ! r a w ! I D ! n u m b e r ! o r ! s t r i n g .
n/ a
1 . 1 . 8 . 4
N u l l ! v a l u e s ! s h a l l ! b e ! u s e d ! w h e n ! i n i t i a l i z i n g ! o r ! c r e a t i n g ! a n y ! d a t a ! o r ! d a t a ! t y p e s , ! o r !
r e c o r d i n g ! a n ! o u t " o f " r a n g e ! v a l u e .
No
2 . 1 . 1 . 1
O n " b o a r d ! d e v i c e s ! s h a l l ! n o t ! i m p e d e ! d r i v e r ' s ! v i e w ! o f ! t h e ! r o a d , ! n o r m a l ! d r i v e r !
o p e r a t i o n s , ! m o v e m e n t ! i n ! t h e ! d r i v e r ' s ! o r ! p a s s e n g e r ! c o m p a r t m e n t s , ! n o r ! e n t r y ! o r !
e g r e s s ! f r o m ! t h e ! v e h i c l e .
Yes
2 . 1 . 2 . 1
T h e ! m a x i m u m ! a m o u n t ! o f ! t i m e ! r e q u i r e d ! t o ! r e m o v e ! a n d ! r e p l a c e ! a n ! O n " B o a r d !
s y s t e m ! e l e m e n t .
n/ a
2 . 1 . 2 . 2 T h e ! O n " B o a r d ! s y s t e m s ! s h a l l ! p r o v i d e d ! s e l f " t e s t ! d i a g n o s t i c s ! t o ! a i d ! i n ! f a u l t ! i s o l a t i o n . No
2 . 2 . 2 . 1
T h e ! m a x i m u m ! a m o u n t ! o f ! t i m e ! t h e ! M D T ! s h a l l ! t a k e ! t o ! r e s p o n d ! t o ! d r i v e r ! o r !
p a s s e n g e r ! i n p u t ! f o r ! n o r m a l ! ( n o n " e m e r g e n c y ) ! o p e r a t i o n s .
Yes
2 . 2 . 2 . 9
T h e ! M o b i l e ! D a t a ! T e r m i n a l ! s h a l l ! b e ! c a p a b l e ! o f ! v a l i d a t i n g , ! l o g g i n g , ! a n d ! f o r w a r d i n g !
t o ! t h e ! c e n t r a l ! s i t e ! t h e ! s p e c i f i e d ! n u m b e r ! o f ! v e h i c l e ! l o c a t i o n ! a n d ! s t a t u s ! p e r ! m i n u t e .
Yes
2 . 2 . 4 . 2
T h e ! M D T ! s h a l l ! h a v e ! a ! l a r g e ! f o r m a t ! c l o c k ! t o ! d i s p l a y ! t i m e ! t o ! t h e ! d r i v e r ! w h e n ! t h e !
c o a c h ! i s ! i n ! m o t i o n
No
2 . 2 . 4 . 3 T h e ! M D T ! s h a l l ! d i s p l a y ! b u s ! s t o p ! n a m e ! t o ! t h e ! d r i v e r ! u p o n ! a r r i v a l ! a t ! a ! s t o p . No
2 . 2 . 4 . 4
T h e ! M D T ! s h a l l ! d i s p l a y ! b u s ! s t o p ! a r r i v a l ! s c h e d u l e ! a d h e r e n c e ! i n f o r m a t i o n ! t o ! t h e !
d r i v e r ! w h e n ! a t ! a ! s t o p .
No
2 . 2 . 4 . 5
T h e ! M D T ! s h a l l ! d i s p l a y ! c o u n t d o w n ! u n t i l ! d e p a r t u r e ! i n ! m i n u t e s ! t o ! a ! d r i v e r ! w h i l e ! a t ! a !
s t o p ! o r ! o n ! b r e a k .
No
2 . 2 . 4 . 1 1
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! d e t e c t ! a r r i v a l s ! a n d ! d e p a r t u r e s ! f r o m ! s t o p s , !
w h e n ! a t ! a ! s t o p , ! a n d ! w h e n ! b e t w e e n ! s t o p s ! b a s e d ! o n ! t h e ! t r a n s i t ! s c h e d u l e ! a n d !
m a s t e r ! s t o p ! l i s t .
No
2 . 2 . 4 . 1 5
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! l o g ! b o a r d i n g ! a n d ! a l i g h t i n g ! d a t a ! f o r ! r e t r e i v a l !
a n d ! p o s t ! p r o c e s s i n g .
Yes
2.1 ! ! General ! Requirements
2. ! ! Verification ! & ! Testing
2.2 ! ! On " Board ! Requirements
5
Implemented !
and ! Verified
EDAPTS ! Specification
2 . 2 . 4 . 1 6
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! b e ! r e m o t e l y ! a d m i n i s t e r e d ! f r o m ! t h e ! c e n t r a l !
s i t e .
Yes
2 . 2 . 4 . 1 7
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! l o g ! s t o p ! d e p a r t u r e ! a n d ! a r r i v a l ! d a t a ! f o r !
r e t r e i v a l ! a n d ! p o s t ! p r o c e s s i n g .
Yes
2 . 2 . 4 . 1 8
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! d e c l a r e ! o n " b o a r d ! e m e r g e n c i e s ! t o ! c e n t r a l !
d i s p a t c h ! a n d ! t h e n ! s e n d ! r e g u l a r ! p o s i t i o n ! u p d a t e s ! t o ! t h e ! c e n t r a l ! s i t e .
Yes
2 . 2 . 4 . 1 9
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! s u r v e y ! r o u t e ! s t o p s ! f o r ! l a t i t u d e , ! l o n g i t u d e , !
a n d ! d i r e c t i o n ! ( h e a d i n g ) .
No
2 . 2 . 4 . 2 0
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! c o m m u n i c a t e ! w i t h ! t h e
c e n t r a l ! s i t e ! t o ! s u p p o r t ! a d m i n i s t r a t i v e ! f u n c t i o n s ! s u c h ! a s ! s o f t w a r e ! u p d a t e s , !
s c h e d u l e ! d o w n l o a d s , ! a n d ! r e t r i e v a l ! o f ! d a t a ! l o g g e d ! o n ! t h e ! M D T .
Yes
2 . 2 . 4 . 2 1
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! p e r f o r m ! a ! c o m p r e h e n s i v e ! s e l f " t e s t ! u p o n !
p o w e r ! u p .
No
2 . 2 . 4 . 2 2
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! l o g ! b o a r d i n g ! a n d ! a l i g h t i n g ! d a t a ! f o r ! r e t r e i v a l !
a n d ! p o s t ! p r o c e s s i n g .
No
2 . 2 . 5 . 1
T h e ! M D T ! c o n t r o l s ! a n d ! i n t e r f a c e ! s h a l l ! b e ! e a s i l y ! o p e r a b l e ! b y ! t h e ! d r i v e r ! w i t h o u t !
r e q u i r i n g ! a ! s i g n i f i c a n t ! s h i f t ! f r o m ! d r i v i n g ! p o s i t i o n .
Yes
2 . 2 . 5 . 2
T h e ! M D T ! d i s p l a y ! s h a l l ! b e ! c l e a r l y ! r e a d a b l e ! b y ! t h e ! d r i v e r ! f r o m ! i t s ! i n s t a l l a t i o n !
l o c a t i o n ! a s ! h e ! o r ! s h e ! c o n d u c t s ! n o r m a l ! o p e r a t i o n s . ! T h e ! M D T ! d i s p l a y ! s h a l l ! m a i n t a i n !
c l e a r ! r e a d a b i l i t y ! u n d e r ! b o t h ! d a y ! a n d ! n i g h t " t i m e ! c o n d i t i o n s .
Yes
2 . 2 . 5 . 4
T h e ! M D T ! s h a l l ! p r o v i d e ! a ! s i m p l e , ! e a s y ! t o ! u s e , ! u n c l u t t e r e d ! i n t e r f a c e ! t o ! t h e ! d r i v e r . !
A l l ! c o m m o n l y ! u s e d ! a c t i o n s ! s u c h ! a s ! l o g " i n , ! l o g " o u t , ! a n d ! r o u t e " c h a n g e ! s h a l l ! b e ! e a s i l y !
a c c e s i b l e ! a n d ! p r o v i d e ! i n t e g r a t e d ! s t e p " b y " s t e p ! i n s t r u c t i o n s . ! B u t t o n s ! a n d ! s c r e e n !
c o n t r o l s ! s h a l l ! b e ! e a s i l y ! u s e d ! a n d ! a c t i v a t e d .
Yes
2 . 2 . 5 . 5
T h e ! M D T ! s h a l l ! r e q u i r e ! m i n i m a l ! i n t e r a c t i o n ! b y ! t h e ! d r i v e r ! a s ! d u r i n g ! n o r m a l ! d r i v e r !
o p e r a t i o n s .
Yes
2 . 2 . 7 . 1
T h e ! M D T ! s h a l l ! d e t e c t ! s t o p s ! w i t h ! t h e ! s p e c i f i e d ! p e r c e n t ! r e l i a b i l i t y ! w h e n ! G P S ! i s !
a v a i l a b l e .
No
2 . 2 . 8 . 1
T h e ! M o b i l e ! D a t a ! T e r m i n a l ! s h a l l ! d e t e c t ! w h e n ! t h e ! v e h i c l e ! i s ! i n ! m o t i o n , ! a n d ! s h a l l !
b l a n k ! i t s ! s c r e e n ! t o ! p r e v e n t ! d r i v e r ! d i s t r a c t i o n . ! D i s p l a y ! o f ! t h e ! t i m e ! i n ! l a r g e !
c h a r a c t e r s ! i s ! a c c e p t a b l e .
Yes
2 . 2 . 9 . 2
T i m e ! e s t i m a t e s ! s h a l l ! b e ! a c c u r a t e ! w i t h i n ! t h e ! s p e c i f i e d ! n u m b e r
o f ! s e c o n d s .
Yes
6
Implemented !
and ! Verified
EDAPTS ! Specification
2 . 6 . 1 7 . 1
T h e ! E m e r g e n c y ! A c t u a t o r ! s h a l l ! b e ! o p e r a b l e ! f r o m ! t h e ! d r i v e r ' s ! p o s i t i o n , ! a n d ! s h a l l !
a b l e ! t o ! u n o b t r u s i v e l y ! a c t i v a t e d ! i n ! t h e ! e v e n t ! o f ! a n ! e m e r g e n c y . ! T h e ! a c t u a t o r ! s h a l l !
b e ! r e s i s t a n t ! t o ! a c c i d e n t a l ! a c t i v a t i o n ! d u e ! t o ! n o r m a l ! m o v e m e n t ! i n ! t h e ! d r i v e r ' s !
c o m p a r t m e n t .
No
2 . 6 . 1 9 . 1 T h e ! e m e r g e n c y ! a c t u a t o r ! s h a l l ! n o t ! a l l o w ! f a l s e ! s i g n a l i n g ! o f ! a n ! e m e r g e n c y . No
3 . 1 . 1 . 1
O n " B o a r d ! S y s t e m ! e l e m e n t s ! s h a l l ! b e ! a b l e ! t o ! b e ! r e m o v e d ! a n d ! r e p l a c e d ! w i t h i n ! t h e !
s p e c i f i e d ! a m o u n t ! o f ! t i m e .
Yes
3 . 1 . 1 . 2
T h e ! O n " B o a r d ! W i r e l e s s ! C o m m u n i c a t i o n s ! s y s t e m ! s h a l l ! p r o v i d e ! s e l f " t e s t ! d i a g n o s t i c s !
t o ! a i d ! i n ! f a u l t ! i s o l a t i o n .
Yes
9 . 2 . 2 . 1
L a t i t u d e ! a n d ! l o n g i t u d e ! e s t i m a t e s ! s h a l l ! b e ! a c c u r a t e ! t o ! w i t h i n ! t h e ! s p e c i f i e d ! n u m b e r !
o f ! m i n u t e s .
Yes
2 . 2 . 4 . 1 2
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! p r o m p t ! a ! d r i v e r ! f o r ! t h e i r ! I D ! n u m b e r ! u p o n !
l o g i n , ! a n d ! t h e n ! a s s o c i a t e ! t h e ! I D ! n u m b e r ! w i t h ! a n ! I D ! n u m b e r ! / ! n a m e ! c r o s s !
r e f e r e n c e ! i n ! t h e
M D T .
Yes
2 . 2 . 4 . 1 3 T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! p r o m p t ! a ! d r i v e r ! f o r ! r o u t e ! n u m b e r ! u p o n ! l o g i n . Yes
2 . 2 . 4 . 1 4
T h e ! M D T ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! p r o m p t ! t h e ! d r i v e r ! f o r ! a ! r o u t e ! n u m b e r ! d u r i n g !
a ! r o u t e ! c h a n g e ! d u r i n g ! t h e ! d a y .
Yes
2 . 2 . 5 . 3
A l l ! s o u n d s , ! t o n e s , ! o r ! o t h e r ! a u d i b l e ! f e e d b a c k ! g e n e r a t e d ! b y ! t h e ! M D T ! s h a l l ! b e ! o f !
s u f f i c i e n t ! v o l u m e ! t o ! b e ! a u d i b l e ! i n ! t h e ! d r i v e r ' s ! c o m p a r t m e n t ! a b o v e ! b a c k g r o u n d !
v e h i c l e ! n o i s e .
No
3 . 1 . 3 . 3
M i n i m u m ! p e r i o d ! o f ! a u t o n o m o u s ! o p e r a t i o n ! r e q u i r e d ! t o ! s u p p o r t ! e m e r g e n c y !
f u n c t i o n a l i t y ! i n ! t h e ! e v e n t ! o f ! a ! p o w e r ! l o s s .
Yes
4 . 1 . 1 . 1
R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! e l e m e n t s ! s h a l l ! b e ! a b l e ! t o ! b e ! r e m o v e d ! a n d ! r e p l a c e d !
w i t h i n ! t h e ! s p e c i f i e d ! a m o u n t ! o f ! t i m e .
n/ a
4 . 1 . 1 . 2
T h e ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! s h a l l ! p r o v i d e d ! s e l f " t e s t ! d i a g n o s t i c s ! t o ! a i d ! i n !
f a u l t ! i s o l a t i o n .
No
4 . 2 . 3 . 2
T h e ! D y n a m i c ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! s h a l l ! b e ! c a p a b l e ! o f ! r e c e i v i n g ! a n d ! t h e n !
d i s p l a y i n g ! b a n n e r ! m e s s a g e s ! u p ! t o ! t h e ! g i v e n ! c h a r a c t e r ! l i m i t .
No
4 . 2 . 3 . 4
T h e ! D y n a m i c ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! p r e s e n t !
m i n u t e s ! u n t i l ! a r r i v a l ! f o r ! b u s e s ! a r r i v i n g ! a t ! a ! s t o p ! b a s e d ! o n ! r e a l " t i m e ! b u s ! t r a j e c t o r y .
Yes
4 . 2 . 3 . 5
T h e ! D y n a m i c ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! i n d i c a t e !
w h e n ! i t ! i s ! o u t ! o f ! s e r v i c e ! t o ! p a s s e n g e r s ! w a i t i n g ! a t ! a ! s t o p .
Yes
2.3 ! ! Roadside ! Requirements
7
Implemented !
and ! Verified
EDAPTS ! Specification
4 . 2 . 3 . 6
T h e ! D y n a m i c ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! s h a l l ! b e ! c a p a b l e ! o f ! s u p p o r t i n g ! t h e !
o p t i o n a l ! d i s s e m i n a t i o n ! o f ! i n f o r m a t i o n ! t o ! r i d e r s ! w i t h ! h e a r i n g ! a n d ! s i g h t ! d i s a b i l i t i e s !
i n ! a c c o r d a n c e ! w i t h ! t h e ! A m e r i c a n s ! w i t h ! D i s a b i l i t i e s ! A c t ! ( A D A ) .
Yes
4 . 2 . 7 . 1
E s t i m a t e d ! m i n u t e s ! u n t i l ! a r r i v a l ! s h a l l ! b e ! a c c u r a t e ! t o ! w i t h i n ! t h e ! s p e c i f i e d ! n u m b e r ! o f !
s e c o n d s .
No
5 . 1 . 1 . 1
R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! e l e m e n t s ! s h a l l ! b e ! a b l e ! t o ! b e ! r e m o v e d ! a n d ! r e p l a c e d !
w i t h i n ! t h e ! s p e c i f i e d ! a m o u n t ! o f ! t i m e .
n/ a
5 . 2 . 1 . 1
M a x i m u m ! t i m e ! f o r ! v e h i c l e " u p d a t e ! m e s s a g e s ! s e n t ! f r o m ! t h e ! C S S ! t o ! b e ! r e c e i v e d ! b y !
t h e ! R I D ! u n d e r ! t y p i c a l ! s y s t e m ! l o a d ! c o n d i t i o n s .
Yes
5 . 2 . 1 . 3
T h e ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! C o m m u n i c a t i o n s ! s y s t e m ! s h a l l ! h a v e ! a ! s u f f i c i e n t !
t h r o u g h p u t ! r a t e ! t o ! e n s u r e ! t h a t ! a l l ! v e h i c l e s ! i n ! t h e ! f l e e t ! w i t h ! t h e ! s p e c i f i c e d ! u p d a t e !
f r e q u e n c y .
Yes
4 . 2 . 3 . 1
T h e ! R I D ! s h a l l ! b e ! a b l e ! t o ! h a v e ! c o n f i g u r a t i o n ! a n d ! s y s t e m ! s c h e d u l e ! i n f o r m a t i o n !
d o w n l o a d e d ! t o ! i t ! r e m o t e l y ! f r o m ! t h e ! c e n t r a l ! s i t e .
n/ a
4 . 2 . 3 . 3
T h e ! D y n a m i c ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! s h a l l ! b e ! c a p a b l e ! o f ! s t o r i n g ! a n d ! t h e n !
d i s p l a y i n g ! a t ! l e a s t ! t h e ! g i v e n ! n u m b e r ! o f ! i n d i v i d u a l ! p u b l i c ! s e r v i c e ! b a n n e r ! m e s s a g e s .
No
6 . 1 . 1 . 1
T h e ! m a x i m u m ! a m o u n t ! o f ! t i m e ! t h e ! A T R M S ! s h a l l ! t a k e ! t o ! r e s p o n d ! t o ! o p e r a t o r ! i n p u t !
f o r ! v e h i c l e ! t r a c k i n g ! o p e r a t i o n s .
Yes
6 . 1 . 2 . 2
T h e ! c e n t r a l ! s o f t w a r e ! s h a l l ! b e ! c a p a b l e ! o f ! s u p p o r t i n g ! a t ! l e a s t ! t h e ! g i v e n ! n u m b e r ! o f !
s i m u l t a n e o u s ! e m e r g e n c y ! c o n d i t i o n s .
Yes
8 . 8 . 1 8 . 1
T r a v e l e r ! I n f o r m a t i o n ! A P I ! t i m e ! e s t i m a t e s ! s h a l l ! b e ! a c c u r a t e ! w i t h i n ! t h e ! s p e c i f i e d !
n u m b e r ! o f ! s e c o n d s .
No
6 . 1 . 3 . 1 T h e ! A T R M S ! G U I ! s h a l l ! b e ! r e a d a b l e ! b y ! e m p l o y e e s ! o f ! v a r y i n g ! v i s u a l ! c a p a b i l i t i e s . Yes
6 . 1 . 3 . 2 A T R M S ! d i s p l a y ! f o n t s ! s h a l l ! b e ! s c a l a b l e ! f r o m ! s m a l l ! t o ! l a r g e . No
6 . 1 . 4 . 1
M i n i m u m ! p e r i o d ! o f ! a u t o n o m o u s ! o p e r a t i o n ! r e q u i r e d ! t o ! s u p p o r t ! e m e r g e n c y !
f u n c t i o n a l i t y ! i n ! t h e ! e v e n t ! o f ! a ! p o w e r ! l o s s ! s h o u l d ! b e ! 1 ! h o u r .
n/ a
6 . 2 . 1 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! a l l o w ! t h e ! u s e r ! t o ! r e m o t e l y !
a d m i n i s t e r ! t h e ! O n " B o a r d ! S y s t e m s ! a b o a r d ! e a c h ! v e h i c l e .
No
6 . 3 . 3 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! a l l o w ! t h e ! u s e r ! t o ! b u i l d ! a !
s c h e d u l e , ! d i s s e m i n a t e ! i t ! t o ! t h e ! f l e e t , ! a n d ! t r a c k ! t h e ! s c h e d u l e ! v e r s i o n ! o n ! e a c h !
v e h i c l e ! i n ! t h e ! f l e e t .
No
2.5 ! ! Client ! Software ! Requirements
2.4 ! ! Software ! Requirements
8
Implemented !
and ! Verified
EDAPTS ! Specification
6 . 5 . 6 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! r e c e i v e ! v e h i c l e ! e m e r g e n c y !
a l a r m s , ! t r a c k ! v e h i c l e s ! w i t h ! a l a r m s , ! a n d ! l o g ! a c t i o n s ! t a k e n .
Yes
6 . 5 . 6 . 2
T h e ! A T M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! g u i d e ! u s e r s ! t h r o u g h ! t h e ! p r o c e s s ! o f !
c r e a t i n g ! a n ! e m e r g e n c y ! p l a n ! f o r ! h a n d l i n g ! d r i v e r ' s ! e m e r g e n c y ! a l a r m s . ! T h i s ! p l a n !
s h a l l ! i n c l u d e ! p r o c e d u r e s ! f o r ! i n t e r a c t i n g ! w i t h ! l o c a l ! l a w ! e n f o r c e m e n t ! a n d ! f o r m s ! f o r !
d e v e l o p i n g ! a n ! e m e r g e n c y ! c a l l o u t ! l i s t .
No
6 . 5 . 7 . 1 T h e ! A T R M S ! s h a l l ! s o u n d ! a n ! a u d i o ! a l a r m ! o f ! a t ! l e a s t ! t h e ! s p e c i f i e d ! v o l u m e ! a t ! 1 ! m e t e r . No
6 . 5 . 7 . 2
T h e ! A T R M S ! s h a l l ! h a v e ! a ! v i s u a l ! e m e r g e n c y ! i n d i c a t o r ! t h a t ! f l a s h e s ! a n d ! a t t r a c t s ! t h e !
a t t e n t i o n ! o f ! a n y ! e m p l o y e e ! w i t h i n ! t h e ! r o o m ! t h e ! A T R M S ! i s ! i n s t a l l e d ! i n .
No
6 . 6 . 9 . 1
T h e ! A T R M S ! c o n s o l e s ! s h a l l ! h a v e ! t h e ! c a p a b i l i t y ! t o ! a l l o w ! t h e ! u s e r ! t o ! a d m i n i s t e r ! e a c h !
D y n a m i c ! R o a d s i d e ! I n f o r m a t i o n ! D i s p l a y ! i n ! t h e ! s y s t e m , ! i n c l u d i n g ! d o w n l o a d i n g !
s c h e d u l e s ! a n d ! e x e c u t a b l e s , ! o p e r a t i o n a l ! s t a t u s , ! a n d ! t r a c k i n g ! f i l e ! v e r s i o n s ! o n ! e a c h !
s i g n .
No
6 . 8 . 1 5 . 1 T i m e ! e s t i m a t e s ! o n ! t h e ! A T R M S ! d i s p l a y ! s h a l l ! b e ! a c c u r a t e ! t o ! w i t h i n ! 3 0 ! s e c o n d s . Yes
6 . 1 1 . 2 2 . 1
T i m e ! e s t i m a t e s ! i n ! r e p o r t s ! g e n e r a t e d ! b y ! t h e ! A T R M S ! s h a l l ! b e ! a c c u r a t e ! t o ! w i t h i n ! 3 0 !
s e c o n d s .
Yes
7 . 2 . 1 . 1
I f ! u t i l i z i n g ! T C P / I P ! c o m m u n i c a t i o n , ! A T R M S ! c l i e n t s ! s h a l l ! f u n c t i o n ! f r o m ! w i t h i n ! a !
N e t w o r k ! A d d r e s s ! T r a n s l a t i o n ! ( N A T ) ! n e t w o r k .
Yes
7 . 1 . 1 . 1
M i n i m u m ! p e r i o d ! o f ! a u t o n o m o u s ! o p e r a t i o n ! r e q u i r e d ! t o ! s u p p o r t ! e m e r g e n c y !
f u n c t i o n a l i t y ! i n ! t h e ! e v e n t ! o f ! a ! p o w e r ! l o s s ! s h o u l d ! b e ! 1 ! h o u r .
n/ a
7 . 3 . 2 . 1
T h e ! A T R M S ! C o m m u n i c a t i o n s ! S y s t e m ! s h a l l ! m e e t ! o r ! e x c e e d ! a ! 9 9 . 9 9 % ! s u c c e s s f u l !
d e l i v e r y ! p e r c e n t a g e ! r a t e ! f o r ! a l l ! d a t a ! t r a n s p o r t e d ! b e t w e e n ! t h e ! A T R M S ! a n d ! t h e !
A T R M S ! A P I .
Yes
7 . 3 . 2 . 2
M a x i m u m ! t i m e ! f o r ! a ! m e s s a g e ! a n d ! r e s p o n s e ! b e t w e e n ! t h e ! A T R M S ! a n d ! t h e ! C S S !
s h o u l d ! b e ! 3 0 ! s e c o n d s .
Yes
1 . 1 . 7 . 6
A l l ! E D A P T S ! e l e m e n t s ! s h a l l ! b e ! a b l e ! t o ! r e c o v e r ! f r o m ! a ! p o w e r ! l o s s ! a n d ! r e s u m e !
n o r m a l ! o p e r a t i o n s ! w i t h o u t ! r e q u i r i n g ! s p e c i a l i z e d ! t e c h n i c a l ! i n t e r a c t i o n .
Yes
1 . 1 . 2 . 1
T h e ! m i n i m u m ! n u m b e r ! o f ! v e h i c l e s ! s u p p o r t e d ! b y ! t h e ! s y s t e m ! s h a l l ! b e ! t h e ! e i g h t ! p l u s !
5 0 % .
Yes
1 . 1 . 2