APPENDIX A
SAMPLE CONTRACT
SAMPLE CONTRACT
THIS CONTRACT pertains to the procurement of a statewide Next Generation
Advanced Traffic Management System (Next Gen ATMS). This Next Gen ATMS Contract
("Contract") is entered into this ________ day of ___________, 2011, by and between the
Commonwealth of Pennsylvania, acting through the Department of Transportation
("PENNDOT"), and ___________________ (“CONTRACTOR”).
WITNESSETH:
WHEREAS, PENNDOT issued a Request For Proposals for PennDOT’s Next Gen
ATMS, RFP 10R-01 (“RFP”); and
WHEREAS, CONTRACTOR submitted a proposal in response to the RFP; and
WHEREAS, PENNDOT determined that CONTRACTOR’s proposal, was the most
advantageous to the Commonwealth after taking into consideration all of the evaluation factors
set forth in the RFP and selected CONTRACTOR for contract negotiations; and
WHEREAS, PENNDOT and CONTRACTOR have negotiated this Contract as their
final and entire agreement in regard to services provided to design, develop, implement, test,
maintain and support the statewide Next Gen ATMS .
NOW THEREFORE, intending to be legally bound hereby, PENNDOT and
CONTRACTOR agree as follows:
1. CONTRACTOR shall, in accordance with the terms and conditions of this Contract,
provide services to PENNDOT for a fully operational Next Gen ATMS, as more fully
defined in the RFP, which is attached hereto as Exhibit “A” and made part of this
Contract.
2. CONTRACTOR agrees that the services shall be performed during the contract
period of sixty (60) months following PennDOT’s issuance of Notice to Proceed
under this Contract. PennDOT’s Contracting Officer may renew this contract for a
period of twenty-four (24) months, incrementally or in one step. Additionally, the
Commonwealth reserves the right, upon notice to the Contractor, to extend the term
of the Contract for up to three (3) months upon the same terms and conditions. This
will be utilized to prevent a lapse in Contract coverage and only for the time
necessary up to three (3) months, to enter into a new contract. This right to extend
the Contract in no way minimizes PENNDOT’s right to the timely receipt of the
project deliverables as specified in the RFP.
3. PENNDOT shall pay the CONTRACTOR during the existence of this Contract for
work completed in accordance with the terms and conditions of the Contract, the
Appendix A Page 1 of 3
maximum amount of XXXXXXX DOLLARS AND XXXXX CENTS ($_______)
for the time period set forth in #2 above of this Contract.
4. PENNDOT and CONTRACTOR agree to be bound by the Special Contract Terms
and Conditions, which are attached hereto as Exhibit “B” and made part of this
Contract.
5. PENNDOT and CONTRACTOR agree to be bound by the Standard Contract Terms
and Conditions for Services – STD-274, Rev. 12/17/07, which are attached hereto as
Exhibit “C” and made part of this Contract.
6. CONTRACTOR agrees to provide a strategy for Next Gen ATMS as described in its
Technical Submittal, which is attached hereto as Exhibit “D” and made part of this
Contract, at the prices listed in its Cost Submittal, which is attached hereto as Exhibit
“E” and made part of this Contract.
7. CONTRACTOR agrees to meet and maintain the commitments to disadvantaged
businesses made in its Disadvantaged Business Submittal, if applicable.
8. This Contract is comprised of the following documents, which are listed in order of
precedence in the event of a conflict between these documents:
a. The Special Contract Terms and Conditions.
b. Standard Contract Terms and Conditions for Services – SAP, STD-274 Rev.
12/17/07.
c. The CONTRACTOR’s Cost Submittal and any addenda, if applicable.
d. The RFP and any addenda, including all referenced Appendices.
e. The CONTRACTOR’s Technical Submittal and any addenda, if applicable.
[THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK]
Appendix A Page 2 of 3
IN WITNESS WHEREOF, the parties have executed this Contract on the date first above
written.
CONTRACTOR:
BY ___________________________________
NAME
DATE
BY ___________________________________
TITLE
If a Corporation, only the Chairman, President, Vice President, Senior Vice President,
Executive Vice President, Assistant Vice President, Chief Executive Officer or Chief
Operating Officer must sign; if one of these officers is not available, please attach a
resolution. If a sole proprietorship, only the owner must sign; if a partnership, only one
partner needs to sign; if a limited partnership, only a general partner may sign. If a Limited
Liability Company (“LLC”), only one member needs to sign, unless it is a manager-based
LLC, then a manager must sign. If a Municipality, Authority, or other entity, please attach a
resolution.
_______________________________________________________________________________
DO NOT WRITE BELOW THIS LINE--FOR COMMONWEALTH USE ONLY
COMMONWEALTH OF PENNSYLVANIA
DEPARTMENT OF TRANSPORTATION
BY ___________________________________
TITLE
DATE
APPROVED AS TO LEGALITY
AND FORM
BY _________________________________
For Chief Counsel
DATE
BY _________________________________
Deputy General Counsel
DATE
BY _________________________________
Deputy Attorney General
DATE
RECORDED NO. ____________________
SAP NO. ___________________________
SAP COST CENTER _________________
GL ACCOUNT_______________________
AMOUNT __________________________
BY_________________________________
For Comptroller Operations
DATE
Appendix A Page 3 of 3
APPENDIX B
SPECIAL CONTRACT TERMS AND CONDITIONS
SPECIAL CONTRACT TERMS AND CONDITIONS
1.
FEDERALLY FUNDED CONTRACTS
In the event that Federal funding is used to support the work governed by this Contract, the
following provisions apply:
A. Federal Representative
All references to the Federal Representative in this Contract apply. The Federal Highway
Administration (FHWA) is referred to as the Federal Representative.
B. Federal Nondiscrimination Clauses
CONTRACTOR agrees to comply with the Federal Nondiscrimination and Equal
Employment Opportunity Clauses, dated January 1976, which are attached to and made a
part of this Agreement.
C. Certification of Contractor
CONTRACTOR hereby certifies that CONTRACTOR has not employed or retained for a
commission, percentage, brokerage, contingent fee, or other consideration, any firm or
person (other than a bona fide employee working solely for CONTRACTOR) to solicit or
secure this Contract.
CONTRACTOR further certifies that CONTRACTOR has not agreed, as an express or
implied condition for obtaining this Contract, to employ or retain the services of any firm
or person in connection with carrying out this Contract. CONTRACTOR has not paid, or
agreed to pay, to any firm, organization, or person (other than a bona fide employee
working solely for CONTRACTOR) any fee, contribution, donation, or consideration of
any kind for, or in connection with, procuring or carrying out this Contract.
No member or delegate to the Congress of the United States shall be admitted to any
share or part of this Contract or to any benefit arising therefrom.
D. Federal Disadvantaged Business Enterprise Assurance
CONTRACTOR shall not discriminate on the basis of race, color, national origin, or sex
in the performance of this contract. CONTRACTOR shall carry out applicable
requirements of 49 C.F.R. Part 26 in the award and administration of United States
Department of Transportation-assisted contracts. Failure by CONTRACTOR to carry out
these requirements is a material breach of this contract, which may result in the
termination of this contract or such other remedy as PENNDOT deems appropriate. If
CONTRACTOR is providing services or supplies for PENNDOT pursuant to this
contract, it must include this assurance in each subcontract that it signs with a
subcontractor. If CONTRACTOR is a grantee or other recipient of funds from
PENNDOT, it must include this assurance in each contract into which it enters to carry
out the project or activities being funded by this contract.
Page 1 of 19
E. Review Rights
PENNDOT and the Federal Representative, if appropriate, have the right to review and
inspect all project activities at any time. PENNDOT retains the right to conduct security
audits.
2.
OWNERSHIP RIGHTS
(a)
(b)
(c)
Ownership of Properties
(1)
All “Developed Works” shall be owned according to the provisions set
forth in this Section 2.
(2)
All software owned by the Commonwealth or its licensors
(“Commonwealth Software”) as of the Effective Date, shall be and shall
remain the exclusive property of the Commonwealth or its licensors, and
Contractor shall acquire no rights or interests in the Commonwealth
Software or Tools or that of its licensors by virtue of this Contract except
as described in this Section or in another provision set forth in this
Contract. The Contractor shall not use any Commonwealth Software,
Commonwealth Tools or software or tools of its licensors for any purpose
other than for completion of work to be performed under this Contract. In
the use of Commonwealth Software, Commonwealth Tools or software or
tools of its licensors, Contractor will be bound by the confidentiality
provisions of this Contract.
Definitions
(1)
Software—For the purposes of this Contract, the term “software” means a
collection of one or more programs, databases or microprograms fixed in
any tangible medium of expression that comprises a sequence of
instructions (source code) to carry out a process in, or convertible into, a
form executable by an electronic computer (object code).
(2)
Data—For the purposes of this Contract, the term “data” means any
recorded information, regardless of form, the media on which it may be
recorded, or the method of recording.
(3)
Technical Data—For purposes of this Contract, the term “technical data”
means any specific information necessary for the development, production
or use of the Commonwealth Software.
Commonwealth Property—Non-Exclusive, License Grant and Restrictions
During the term of this Contract, Commonwealth grants to Contractor for the
limited purpose of providing the Services covered under this Contract, a limited,
nonexclusive, nontransferable, royalty-free right (subject to the terms of any third
party agreement to which the Commonwealth is a party) to do the following:
Page 2 of 19
(d)
(1)
Obtain access to and use of the Commonwealth Software in accordance
with the terms of this Contract.
(2)
Reproduce the Commonwealth Software for archival purposes or for other
purposes expressly provided for under this Contract.
(3)
Modify the Commonwealth Software consistent with the terms and
conditions of this Contract provided that Contractor agrees to assign to the
Commonwealth, its rights, if any, in any derivative works resulting from
Contractor’s modification of the Commonwealth Software. Contractor
agrees to execute any documents required to evidence this assignment and
to waive any moral rights and rights of attribution provided for in Section
106A of Title 17 of the United States Code, the Copyright Act of 1976.
(4)
Allow the Contractor’s subcontractors approved by the Commonwealth to
obtain access to the Commonwealth Software for the purposes of
complying with the terms and conditions of this Contract; provided,
however, that neither Contractor nor any of its subcontractors may
decompile or reverse engineer, or attempt to decompile or reverse
engineer, any of the Commonwealth Software. Commonwealth hereby
represents that it has the authority to provide the license grant and rights
set forth in this Section.
(5)
To the extent that Contractor uses Commonwealth Software,
Commonwealth Tools or software or tools of its licensor, Contractor
agrees to protect the confidentiality of these works and maintain these
proprietary works with the strictest confidence.
Impact of Third Party Agreements
Subject to the terms of any third party agreement to which the Commonwealth is
a party, (i) the Commonwealth shall, at no cost to Contractor, provide Contractor
with access to the Commonwealth Software in the form in use by Commonwealth
as of the Effective Date of this Contract and, (ii) Contractor, as part of the
Services to be rendered under this Contract, shall compile and, as changes are
made, update a list of all of the Commonwealth Software then in use by
Contractor or any of its subcontractors in connection with Contractor’s
performance of the Services required by this Contract.
(e)
Reservation of Rights
All rights, not expressly granted here to Contractor on a nonexclusive basis,
including the right to grant non-exclusive licenses and other rights are reserved by
the Commonwealth.
Page 3 of 19
(f)
Termination of Commonwealth License Grant
Upon the expiration or termination for any reason of Contractor’s obligation to
provide the Services under this Contract, all rights granted to Contractor in this
Section shall immediately cease. Contractor shall, at no cost to Commonwealth,
deliver to Commonwealth all of the Commonwealth Software and Tools
(including any related source code then in Contractor’s possession or under its
control) in the form in use as of the Effective Date of such expiration or
termination. Within fifteen (15) calendar days after termination, Contractor shall
provide the Commonwealth with a current copy of the list of Commonwealth
Software in use as of the date of such expiration or termination. Concurrently
therewith, Contractor shall destroy or erase all other copies of any of the
Commonwealth Software then in Contractor’s possession or under its control
unless otherwise instructed by Commonwealth, in writing; provided, however,
that Contractor may retain one archival copy of such Commonwealth Software
and Tools, until final resolution of any actively asserted pending disputes between
the Parties, such retention being for the sole purpose of resolving such disputes.
(g)
Effect of License Grant Termination
Consistent with the provisions of this Section, Contractor shall refrain from
manufacturing, copying, marketing, distributing, or use of any Commonwealth
Software or any other work which incorporates the Commonwealth Software.
The obligations of this Section shall survive any termination of this Contract.
(h)
Use of Contractor-Owned Software
All software owned by Contractor (Contractor Software) and tools owned by
Contractor ( collectively “Contractor Tools,” as defined in paragraph (i) below)
prior to the Effective Date of this Contract shall be and shall remain the exclusive
property of Contractor. The Commonwealth shall acquire no rights or interests in
the Contractor Software or the Contractor Tools by virtue of this Contract except
as set forth below (in the form of a license).
(i)
Definition of Contractor Tools
Contractor Tools is defined as any tools, both in object code and source code
form, which Contractor has previously developed, or which Contractor
independently develops or licenses from a third party, excluding any tools that
Contractor creates pursuant to this Contract. Contractor Tools includes but is not
limited to, methodologies, information, concepts, toolbars for maneuvering
between pages, search engines, JAVA applets, and ActiveX controls.
(j)
Required Reports, Records and Inventory of Contractor Tools and Contractor
Software
(1)
Contractor must provide a list of all Contractor Tools and Contractor
Software to be delivered in connection with the deliverables or Developed
Materials prior to commencing any work under the Contract. Contractor
Page 4 of 19
must also provide a list of all other Contractor Tools and Contractor
Software intended to be used by Contractor to provide the services under
this Contract but will not become part of or necessary for the use of the
Developed Materials. All Contractor Tools and Contractor Software
necessary to use deliverables or Developed Materials shall be delivered to
the Commonwealth along with the license set forth in subsection (k).
Contractor may amend these lists from time to time while the Contract is
being carried out or upon its completion. In the event that the Contractor
fails to list a Contractor Tool, but can demonstrate that such tool was
independently developed by Contractor prior to the Contract on which it
was used, Contractor shall nevertheless retain complete ownership of such
Contractor Tool that is necessary to use the deliverables or Developed
Materials, provided that notice is given to the Commonwealth prior to its
use on the Contract. Any Contractor Tools or Contractor Software not
included on the lists will be deemed to have been created under this
Contract.
(k)
(2)
As part of its response to a RFP, the Contractor will provide a list of all
software and tools that are commercially available and which are required
to support the deliverables or Developed Materials.
(3)
During the term of this Contract, Contractor shall maintain at its principal
office books of account and records showing its actions under this
Contract. Upon reasonable notice by Commonwealth, Contractor shall
allow Commonwealth to inspect these records and accounts for purposes
of verifying the accuracy of such accounts and records.
(4)
In the event that Contractor fails to list a Contractor Tool or Contractor
Software, but is able to demonstrate that such tool or software was
independently developed by Contractor prior to the Effective Date of this
Contract, Contractor shall retain complete ownership of such Contractor
Tool or Contractor Software that is necessary to use the deliverables or
Developed Works, provided that notice is given to the Commonwealth
prior to use on the Contract.
Expiration or Termination Non Exclusive License Grant—Non-Commercial
Contractor Tools and Software
Upon the expiration or termination for any reason of Contractor’s obligation to
provide the Services under this Contract, and/or at the request of the
Commonwealth, Contractor shall (i) grant to Commonwealth a paid-up,
nonexclusive, nontransferable license to use, modify, display, prepare derivative
works and sublicense grant to third parties engaged by Commonwealth (by
contract or otherwise) the right to use, modify, and prepare derivative works based
upon all or any portion of the non-commercially available Contractor Software
and the non-commercially available Contractor Tools owned by Contractor and
used by Contractor in connection with the Services, the foregoing rights being
granted to the extent reasonably necessary to facilitate Commonwealth’s or such
Page 5 of 19
third party’s completion of and maintenance of the Services to be provided by
Contractor under this Contract immediately prior to such expiration or termination
and (ii) deliver to Commonwealth the object code version of such noncommercially available Contractor Software and such non-commercially available
Contractor Tools in the form used by Contractor in connection with the Services
immediately prior to such expiration or termination to allow the Commonwealth
to complete and maintain such work. If Commonwealth enters into a contract that
allows for the use of the Contractor Software or Contractor Tools for which a
license is granted under this Section, the Commonwealth will include a provision
in that contract that limits the use of the Contractor Software or Contractor Tools
as delineated in this Section.
(l)
Rules of Usage for Developed Works
(1)
If Developed Works modify, improve, or enhance application software
programs or other materials generally licensed by the Contractor, then
such Developed Works shall be the property of the Contractor, and
Contractor hereby grants Commonwealth and any third party acting on its
behalf, an irrevocable, nonexclusive, worldwide, fully paid-up license (to
include source code and relevant documentation) in perpetuity to use,
modify, execute, reproduce, display, perform, prepare derivative works
from and distribute, within the Commonwealth, of such Developed Works.
For purposes of distribution under the license grant created by this section,
the term “Commonwealth” includes any government agency, department,
instrumentality, division, unit or other office that is part of the
Commonwealth of Pennsylvania, together with the State System of Higher
Education (including any of its universities), any county, borough,
commonwealth, city, municipality, town, township special purpose
district, or other similar type of governmental instrumentality located
within the geographical boundaries of the Commonwealth of
Pennsylvania. If federal funds are used in creation of the Developed
Works, the Commonwealth also includes any other state government as
well as the federal government.
(2)
If Developed Works modify, improve, or enhance application software
or other materials not licensed to the Commonwealth by the Contractor,
then such modifications, improvements and enhancements shall be the
property of the Commonwealth and its licensor.
To the extent
Commonwealth owns the software or other materials, it hereby grants to
Contractor an irrevocable, nonexclusive, worldwide, fully paid-up license
to use, modify, execute, reproduce, display, perform, prepare derivative
works from, and distribute copies of such Developed Works. To the
extent Commonwealth has a license to the software or other materials, and
to the extent that it, in its sole discretion determines it is able to do so the
Commonwealth will grant to Contractor an irrevocable, nonexclusive,
worldwide, fully paid-up license to use, modify, execute, reproduce,
display, perform and distribute copies of such Developed Works.
Page 6 of 19
(m)
(3)
If Developed Works have been funded by Commonwealth, to any extent,
with either Commonwealth or federal funds, and the Developed Works do
not include pre-existing materials generally licensed by the Contractor,
then the Commonwealth shall have all right, title, and interest (including
ownership of copyright and trademark) to such Developed Works and the
Commonwealth hereby grants to Contractor an irrevocable, nonexclusive,
worldwide, fully paid-up license to use, modify, execute, reproduce,
display, perform, prepare derivative works from, and distribute copies of
such Developed Works. The Commonwealth shall exclusively own all
software products first developed under the terms of this contract by the
Contractor, its subcontractors or other third party vendors that are
specifically developed for, engineered and integrated into the Developed
Works.
(4)
When the Developed Work is a report provided by a research company
that was provided under this Contract, but which was not developed
specifically for the Commonwealth under this Contract, the ownership of
the Developed Work will remain with the Contractor, provided, however,
that the Commonwealth has the right to copy and distribute the Developed
Work within the Commonwealth.
Copyright Ownership—Developed Works Developed as Part of the Scope of
Work for the Project, including Developed Works developed by Subcontractors,
are the sole and exclusive property of the Commonwealth and shall be considered
“works made for hire” under the United States Copyright Act of 1976, as
amended, 17 United States Code. In the event that the Developed Works do not
fall within the specifically enumerated works that constitute works made for hire
under the United States copyright law, Contractor agrees to assign and, upon their
authorship or creation, expressly and automatically assigns all copyright interests,
proprietary rights, trade secrets, and other right, title, and interest in and to such
Developed Works to Commonwealth. Contractor further agrees that it will have
its Subcontractors assign, and upon their authorship or creation, expressly and
automatically assign all copyright interest, proprietary rights, trade secrets, and
other right, title, and interest in and to the Developed Works to the
Commonwealth. Commonwealth shall have all rights accorded an owner of
copyright under the United States copyright laws including, but not limited to, the
exclusive right to reproduce the Developed Works in multiple copies, the right to
distribute, copies by sales or other transfers, the right to register all copyrights in
its own name as author in the United States and in foreign countries, the right to
prepare derivative works based upon the Developed Works and the right to
display the Developed Works. The Contractor further agrees that it will include
this requirement in any subcontractor or other agreement with third parties who in
any way participate in the creation or development of Developed Works. Upon
completion or termination of this Contract, Developed Works shall immediately
be delivered by Contractor to the Commonwealth. Contractor warrants that the
Developed Works are original and do not infringe any copyright, patent,
trademark, or other intellectual property right of any third party and are in
conformance with the intellectual property laws of the United States.
Page 7 of 19
(n)
(o)
Patent Ownership
(1)
Contractor and its subcontractors shall retain ownership to patentable
items, patents, processes, inventions or discoveries (collectively, the
Patentable Items) made by the Contractor during the performance of this
Contract. Notwithstanding the foregoing, the Commonwealth shall be
granted a nonexclusive, nontransferable, royalty free license to use or
practice the Patentable Items. Commonwealth may disclose to third
parties any such Patentable Items made by Contractor or any of its
subcontractors under the scope of work for the Project that have been
previously publicly disclosed. Commonwealth understands and agrees
that any third party disclosure will not confer any license to such
Patentable Items.
(2)
Contractor shall not use any computer program, code, or any works
developed by or for Contractor independently of this Contract (“PreExisting Materials”) in the performance of the Services under this
Contract, without the express written consent of the Commonwealth. Any
Pre-Existing Materials used by Contractor for performance of Services
under this Contract without Commonwealth consent shall be deemed to be
Developed Works as that term is used in this Section. In the event that
Commonwealth provides such consent, Contractor shall retain any and all
rights in such Pre-Existing Materials.
Federal Government Interests
It is understood that certain funding under this Contract may be provided by the federal
government. Accordingly, the rights to Developed Works or Patentable Items of
Contractors or subcontractors hereunder will be further subject to government rights as
set forth in 37 C.F.R. Section 401, and other applicable statutes.
(p)
Usage Rights for Know-How and Technical Information
Either Party, in the ordinary course of conducting business, may use any ideas, concepts,
know-how, methodologies, processes, components, technologies, algorithms, designs,
modules or techniques not otherwise covered by this Section relating to the Services
which Contractor or Commonwealth (alone or jointly with the Commonwealth) develops
or learns in connection with Contractor’s provision of Services to Commonwealth under
this Contract.
(q)
Commonwealth Intellectual Property Protection
Contractor acknowledges Commonwealth’s exclusive right, title and interest, including
without limitation copyright and trademark rights, in and to Commonwealth Software,
Commonwealth Tools and the Developed Works developed under the provisions of this
Section, shall not in any way, at any time, directly or indirectly, do or cause to be done
any act or thing contesting or in any way impairing or tending to impair any part of said
Page 8 of 19
right, title, and interest, and shall not use or disclose the Commonwealth Software,
Commonwealth Tools, or the Developed Works without Commonwealth’s written
consent, which consent may be withheld by the Commonwealth for any reason. Further,
Contractor shall not in any manner represent that Contractor has any ownership interest
in the Commonwealth Software, Commonwealth Tools, or the Developed Works. This
provision is a material part of this Section.
(r)
Contractor Intellectual Property Protection
Commonwealth acknowledges that it has no ownership rights in the Contractor Software
or Contractor Tools other than those set forth in this Contract, or as may be otherwise
granted in writing.
(s)
Source Code and Escrow Items Obligations
Simultaneously with delivery of the Developed Works to Commonwealth, Contractor
shall deliver a true, accurate and complete copy of all source codes relating to the
Developed Works. To the extent that the Developed Works include application software
or other materials generally licensed by the Contractor, then the source code shall be
placed in escrow, subject to the terms and conditions of an Escrow Agreement to be
executed by the Parties and an Escrow Agent that is acceptable to the Commonwealth.
(t)
Contractor’s Copyright Notice Obligations
Contractor will affix the following Copyright Notice to the Developed Works developed
under this Section and all accompanying documentation: “Copyright [year] by the
Commonwealth of Pennsylvania. All Rights Reserved.” This notice shall appear on all
tangible versions of the Developed Works delivered under this Contract and any
associated documentation. It shall also be programmed into any and all Developed
Works delivered hereunder so that it appears at the beginning of all visual displays of
such Developed Works.
(u)
Commercial Software
If a product or deliverable under this Contract is commercially available software or
requires commercially available software for use, the Contractor hereby agrees that it will
enter into a software license agreement with the Commonwealth that provides the
Commonwealth (and third parties acting on behalf of the Commonwealth) with, all rights
set forth in the above section labeled “Rules of Usage for Developed Works.”. If the
Contractor is not the licensor of the software, Contractor hereby agrees that it will inform
the licensor of the software that it will be required to enter into a license agreement with
the Commonwealth (which shall also address third parties’ rights, while acting on behalf
of the Commonwealth, to utilize the licensed software).
(v)
Perpetual License Requirement
Page 9 of 19
The Contractor hereby agrees that all COTS software and solutions shall be provided to
the Commonwealth by way of a perpetual, royalty-free license to the e Commonwealth
including, but not limited to, non-expiring usage to current and future versions, as
explained above in subsection (u), Commercial Software.
3.
4.
PUBLICATION RIGHTS AND/OR COPYRIGHTS
(a)
Except as otherwise provided in this Section, the Contractor shall not publish any
of the results of the work without the written permission of the Commonwealth.
The publication shall include the following statement: “The opinions, findings,
and conclusions expressed in this publication are those of the author and not
necessarily those of the Commonwealth of Pennsylvania.” The Contractor shall
not include in the documentation any copyrighted matter, unless the Contractor
provides the Commonwealth with written permission of the copyright owner.
(b)
Except as otherwise provided in Paragraph 5, Confidentiality, the Commonwealth
shall have unrestricted authority to reproduce, distribute, and use any submitted
report or data designed or developed and delivered to the Commonwealth as part
of the performance of the Contract.
(c)
Rights and obligations of the parties under this Section survive the termination of
this Contract.
LIQUIDATED DAMAGES
(a)
Liquidated damages shall apply to this Contract for the deliverables identified
below.
For each calendar day that the work remains incomplete and/or
unacceptable to PennDOT past the Delivery Dates identified in Appendix U,
Project Deliverables Schedule, the sum per day specified in the following table
will be assessed against the appropriate deliverable and deducted from that
deliverable invoice.
Deliverable
Delivery Dates
Liquidated Damages
per Calendar Day
As
established
in
$2,150
E-2: Eastern Region Implementation
Appendix U
As established in $2,150
F-3: Central Region Implementation
Appendix U
G-3: Western Region Implementation As established in $2,150
Appendix U
In the event that the Liquidated Damage amount exceeds the deliverable invoice,
at PennDOT’s discretion, the difference in amounts shall be deducted from
another deliverable invoice or shall be remitted directly to PennDOT upon
PennDOT’s invoicing.
Page 10 of 19
5.
CONFIDENTIALITY
(a)
The Contractor agrees to protect the confidentiality of the Commonwealth’s
confidential information and the Commonwealth will take all reasonably
necessary measures to ensure the confidentiality of the Contractor’s information
that it designates as confidential in accordance with this paragraph. In order for
information to be deemed confidential, the party claiming confidentiality must
designate the information as “confidential” in such a way as to give notice to the
other party (notice may be communicated by describing the information, and the
specifications around its use or disclosure, in the SOW). Neither party may assert
that information owned by the other party is such party’s confidential information.
The parties agree that such confidential information shall not be copied, in whole
or in part, or used or disclosed except when essential for authorized activities
under this Contract and, in the case of disclosure, where the recipient of the
confidential information has agreed to be bound by confidentiality requirements
no less restrictive than those set forth herein. Each copy of such confidential
information shall be marked by the party making the copy with any notices
appearing in the original. Upon termination or cancellation of this Contract or
any license granted hereunder, the receiving party will return to the disclosing
party all copies of the confidential information in the receiving party’s possession,
other than one copy, which may be maintained for archival purposes only, and
which will remain subject to this Contract’s security, privacy, data
retention/destruction and confidentiality provisions (all of which shall survive the
expiration of this Contract). Both parties agree that a material breach of these
requirements may, after failure to cure within the time frame specified in this
Contract, and at the discretion of the non-breaching party, result in termination for
default pursuant to Section 22.c (DEFAULT), in addition to other remedies
available to the non-breaching party.
(b)
Insofar as information is not otherwise protected by law or regulation, the
obligations stated in this Section do not apply to information:
(1)
already known to the recipient at the time of disclosure other than through
the contractual relationship;
(2)
independently generated by the recipient and not derived from the
information supplied by the disclosing party;
(3)
known or available to the public, except where such knowledge or
availability is the result of unauthorized disclosure by the recipient of the
proprietary information;
(4)
disclosed to the recipient without a similar restriction by a third party who
has the right to make such disclosure; or
(5)
required to be disclosed by the recipient by law, regulation, court order, or
other legal process.
Page 11 of 19
There shall be no restriction with respect to the use or disclosure of any ideas,
concepts, know-how, or data processing techniques developed alone or jointly
with the Commonwealth in connection with services provided to the
Commonwealth under this Contract.
Notwithstanding the foregoing, confidential information may be the subject of a
request under the Pennsylvania Right-to-Know Law, 65 P.S. § 67.101 et seq, and
the Contractor shall comply with the Right-to-Know Law Provisions set forth in
the Commonwealth’s STD-274, Standard Terms and Conditions, which is
attached to the Contract as Appendix C.
6.
SERVICE LEVEL AGREEMENT (SLA)
PennDOT expects that the CONTRACTOR will demonstrate a high level of service and
quality control standards. The CONTRACTOR is required to maintain high quality
standards and provide quality assurance in order to meet or exceed the service levels
outlined below. In addition, the CONTRACTOR shall take timely and appropriate action
in response to resources that are not performing to PennDOT expectations.
PennDOT has developed a base Service Level Agreement (SLA) that is set forth herein
for the purpose of measuring CONTRACTOR performance throughout the life of the
Contract, and any renewals.
A monthly meeting will take place with the CONTRACTOR to review the quality of
service provided to PennDOT. Monthly performance reports will be reviewed to enable
PennDOT to evaluate the CONTRACTOR on a variety of performance criteria,
including, but not limited to, the SLA established. If any service deficiencies are
identified across the entire contract, the CONTRACTOR and PennDOT representatives
will determine a corrective action plan to ensure that the level of service improves.
Failure to correct service deficiencies may be considered an event of default under
Paragraph 17, Appendix C, Standard Terms and Conditions (STD-274).
As a part of process improvement, throughout the life of the contract, improvement to
existing SLA’s and\or additional SLA’s are to be presented at the monthly review
meeting. PennDOT recommends that the CONTRACTOR utilize survey tools to
periodically gather customer satisfaction feedback from a randomly selected group of
PennDOT users who utilize the CONTRACTOR service desk.
Changes and\or additions to SLA’s resulting from the process improvement efforts will
be agreed upon by the CONTRACTOR and PennDOT and will be in accordance with
Paragraph 30, Appendix C, Standard Terms and Conditions (STD-274).
(a)
Reporting
The CONTRACTOR shall provide all performance reports, delivered to the Project
Manager on or before the 5th calendar day of each month for the immediate preceding month
to verify the fulfillment of the service level requirements The CONTRACTOR shall
Page 12 of 19
furnish DEPARTMENT with a monthly report on all service request activity in an
electronic format agreed upon by DEPARTMENT and will provide access to all the data
used to generate these reports.
Credits: If any performance report is not delivered to PennDOT’s Project Manager on or
by the 5th calendar day of each month, the CONTRACTOR shall apply credit in the
amount as described below to the full monthly invoice amount for Task I-3, Routine
Maintenance and Support. The credit shall be applied to the monthly service invoice of
the affected month.
Performance Reports
All reports received on or by the 5th calendar day of the month
th
Any report received after the 5 calendar day of the month
(b)
Credits
(per report)
No credits applied
$50 (per day)
System Availability
This metric is established to track system availability from an end users’ perspective.
The intent is to assure system availability at or above 99.9% for 24 hours, 7 days a week,
365 days a year continuous system operation. The goal is to have minimal or no
unplanned outages that impact the end users.
System availability refers to the time the system is functional, accessible and capable of
meeting the contracted performance requirements. The System will be deemed
unavailable if at least one TMC is not able to access ATMS or not able to operate one or
more core ATMS modules (e.g. DMS, HAR, CCTV). If the System is deemed
unavailable for more than one TMC and the issue is not related, then the downtime will
be counted for those TMCs as separate instances; downtime calculation shall include all
downtime from start to finish at each affected TMS and shall be counted as consecutive
downtime.If the System is deemed unavailable for more than one TMC and the issue is
related, then the downtime will be counted as a single instance based on the total
downtime for that particular issue. The system availability metric applies to the
CONTRACTOR provided software for the ATMS solution.
The CONTRACTOR will be responsible for reporting on system availability monthly.
Downtime shall be calculated from the time when the CONTRACTOR determines the
unavailability began to the restoration of availability.
NOTE: PennDOT approved downtime due to planned ATMS system maintenance will
not count towards total system downtime; approved downtime shall be counted as time
the system is available
The calculation for downtime shall be as follows:
(System availability – downtime) / (System availability) * 100
•
System availability = number of minutes a system is fully functional and
accessible based on normal hours of operation (24/7/365) for the reporting
month.
Page 13 of 19
•
Downtime = number of minutes a system is unavailable for the reporting month
(applies only to unplanned outages).
Credits:
If the reported monthly system availability is below 99.9%, the
CONTRACTOR shall apply credit in the amount as described below to the full monthly
invoice amount for Task I-3, Routine Maintenance and Support. The credit shall be
applied to the monthly service invoice of the affected month.
Monthly System Availability Performance
(example: downtime in 30 day month)
99.9 to 100% (0 – 43 mins)
98% to 99.8% (43 mins – 14 hrs, 24 mins)
95% to 97.9% (14 hrs, 24 mins – 36 hrs)
90% to 94.9% (36 – 72 hrs)
75% to 89.9% (72 – 180 hrs)
50% to 74.9% (180 – 360 hrs)
Less than 50% (Greater than 360 hours)
Credits
No credits applied
5%
15%
25%
50%
75%
100%
For example, if the availability was 96% in Month 9, then the CONTRACTOR would apply
15% credit to the Month 9’s invoice for the regular Monthly charge for Task I-3, Routine
Maintenance and Support.
(c)
Service Request Management
The CONTRACTOR shall produce a troubleshooting guide with recommendations for
resolving potential problems that may occur with the software (see Statement of Work,
Task I). This matrix shall include step-by-step recommendations that allow basic users
the ability to resolve problems as quickly as possible. The recommendations will also
indicate what steps the PennDOT staff is expected to take before contacting the
CONTRACTOR for support.
All service requests escalated to the CONTRACTOR for resolution shall be resolved
according to the parameters established within this Section. The resolution time
requirements include travel time.
The hours indicated in the response and resolution timeframes shall be interpreted as
consecutive hours within a 24 hour period, except where specifically noted as business
hours. Business Hours are: Monday - Friday, 8AM - 5PM
The following table explains Severity Levels of service requests. The DEPARTMENT
will determine the severity level assigned to requests.
Severity Matrix
The following are examples of DEPARTMENT determined severity levels:
Severity 1
Severity 2
Severity 3
Severity 4
• Complete or substantial • Multiple users are • An individual line or •
An
informational
loss of service or severe affected by a service port is out of service, or request or a fault that has
Page 14 of 19
Severity Matrix
degradation of the system degradation or out-ofthat makes the system service condition.
unusable.
• Significant loss of
• Inability to use a service or high business
impact.
mission-critical
application.
• Any service that affects
certain
key
officials
(executive personnel).
• Failure of a redundant
system component.
limited features for a no business impact.
small number of users
(one to ten) are not
functioning.
•
Minimal
business
impact, problem may be
bypassed.
• Some loss of service or
other specific
functionality is lost.
• Non Service Affecting
Alarms
Credits:
If any of the Service Request/Response targets are not met, the
CONTRACTOR shall apply credit in the amount as described below to the full monthly
invoice amount for Task I-3, Routine Maintenance and Support. The credit shall be
applied to the monthly service invoice in which the resolution occurred. Time interval for
each service request shall begin from the time notification is received and shall end when
the request is resolved and the system is returned to proper operating condition as
confirmed by PennDOT.
The following table explains the activities, performance standards and credits for all
service requests.
Routine Maintenance
Service Request Management – All Requests
Measure
Performance
Activities
a) Respond to service request:
− Answer the call or call back
to user,
− Confirm Severity,
− Establish Priority
Activities
b) Resolve service request:
− Restore application
service in the event of a
service failure.
− Resolve service requests
with high business impact
(such as urgent data fixes,
special reports, etc.)
− Resolve service requests
with minimal business
Response
Time
Measure
Time to
Resolution
Credit
Within 10 minutes from initial notification
For every 10 minutes past initial notification
All Requests
Performance
Severity 1 = within
2 consecutive hours
from initial
notification
Severity 2 = within
4 consecutive hours
from initial
notification
Severity 3 = within
8 consecutive
Page 15 of 19
$0
$50 (per 10
minute interval)
Credit (Per Request)
Within 2 hours of notification
0%
Every 30 minutes interval past
2 hours
Within 4 hours of notification
.5%
Every 30 minutes interval past
4 hours
Within 8 business hours of
notification
.5%
0%
0%
Routine Maintenance
Service Request Management – All Requests
Activities
Measure
Performance
Credit
impact (such as nonbusiness hours from
Every 1 business hour past 8
.5%
urgent data fixes, noninitial notification
business hours
urgent special reports and
Within 24 business hours of
0%
Severity 4 = within
data extracts, user and
notification
24 consecutive
technical documentation
business hours from Every 1 business hour past 24
.5%
updates, etc.)
initial notification
business hours
All Requests
Activities
Measure
Performance
Credit (Per Request)
Intervals
Updates Provided Hourly
c) Communicate periodic
$0
Hourly updates
status updates during service through
(For severity 1 & 2) For each hourly update missed
$50
request response.
resolution
The table below outlines additional activities applicable only to service requests related
to service failures:
Routine Maintenance
Service Request Management – Service Failures
Activities
d) Complete/Document Root
Cause Analysis (RCA)
(For severity levels 1 and 2)
e) Document additional
corrective action necessary to
prevent future reoccurrence of
the problem (For severity
levels 1 and 2)
f) Submit After-Action
Review report after
completion of corrective
action. (For severity levels 1
and 2)
Measure
Performance
Within 2 business
Time
to
days of service
Completion
failure
Within 5 business
Time
to
days of service
Completion
failure
Time
to Within 10 business
Completion days after corrective
action is complete
Credit (Per Request)
Within 2 business days
$0
For each business day late
$50
Within 5 business days
$0
For each business day late
$50
Within 10 business days
$0
For each business day late
$50
PennDOT reserves the right to require the completion of c through f activities for severity levels 3
and 4 as needed, provided that PennDOT notifies the CONTRACTOR of such intent.
Page 16 of 19
Example Calculations for Response and Resolution Activities for a given month:
(d)
•
Day 3: Department contacts vendor for a severity 1 incident. Vendor returns call in 45
minutes and restores incident within 2 hours 45 minutes from Departments first call to the
vendor.
Calculation:
o Call returned in 45 minutes = $200 Credit
o Severity 1 incident restored in 2 hours, 45 minutes = 1% Credit
•
Day 11: Department contacts vendor for a severity 4 incident. Vendor answers call
immediately. Vendor restores incident within 37 business hours from Departments first
call to the vendor.
Calculation:
o Call answered immediately = $0 Credit
o Severity 4 incident restored in 37 hours, = 6.5% Credit
•
Monthly Report: Department contacts vendor for 20 service requests within a month of
which 15 are severity l or 2. All calls were responded to within 10 minutes. However,
the vendor fails to communicate periodic status updates on 2 of the severity 2 incidents.
Each incident of these took 4 hours to resolve.
Calculation:
o Call answered within 10 minutes = $0 Credit
o Severity 2 incidents restored within 4 hours = 0% Credit
o Periodic status updates not done hourly
2 incidents x 3 hourly updates = 6 hourly updates missed
6 updates missed x $50 = $300 Credit
Miscellaneous
In the event that the Credits exceed the regular monthly charge, at PennDOT’s discretion,
the difference in amounts shall be deducted from the next monthly invoice or shall be
remitted directly to PennDOT after PennDOT’s invoicing.
In the event there is no applicable regular monthly charge, the amount of the credit shall be
remitted directly to PennDOT after PennDOT’s invoicing.
7.
ADDITIONAL WORK
As part of this design, build and implementation project the need for some additional
work not yet anticipated or defined within specified Tasks, but within the Contract scope,
may be identified by PennDOT or the CONTRACTOR. In the event that such additional
work is identified, the CONTRACTOR shall propose the level of effort, any associated
costs and a schedule for completion.
The agreement for inclusion of the additional work, associated costs and completion
schedule, or any such change that results in an increase or decrease in the total value of
the Contract, shall be formalized in writing by an exchange of letter signed only by both
parties, PennDOT’s Office of Chief Counsel and Comptroller Operations.
Page 17 of 19
8.
COMPLIANCE WITH INFORMATION TECHNOLOGY STANDARDS AND
POLICY
CONTRACTOR shall follow the information technology standards and policies issued by
the Governor’s Office of Administration, Office for Information Technology (OA/OIT),
for the Commonwealth enterprise. These standards and policies are contained in the
Information Technology Bulletins (ITB) on the Office of Administration website at:
http://www.portal.state.pa.us/portal/server.pt?open=512&objID=416&PageID=210791&
mode=2.
Page 18 of 19
APPENDIX BB
LIST OF ABBREVIATIONS
APPENDIX BB
List of Abbreviations
AMBER
API
ATMS
ATR
AVL
BBSS
BHSTE
BIO
BPR
CCB
CCTV
CMP
COTS
DMS
EDRS
EMA
FHWA
GATIR
GIS
GUI
HAR
HMI
HOV
ICC
IT
ITB
ITS
KVM
LAN
MDSS
OA/OIT
PennDOT
PM
PSP
PTC
RCRS
RTMC
RWIS
RFP
SLA
SR
TMC
UAT
America’s Missing: Broadcasting Emergency Response
Application Programming Interface
Advanced Traffic Management System
Automatic Traffic Recorder
Automatic Vehicle Location
Bureau of Business Solutions and Services
Bureau of Highway Safety and Traffic Engineering
Bureau of Infrastructure and Operations
Bureau of Planning and Research
Change Control Board
Closed Circuit Television
Configuration Management Plan
Commercial Off The Shelf
Dynamic Message Sign
Emergency Detour Routing System
Emergency Management Agency
Federal Highway Administration
Geospatial Analysis of Threats and Incident Reports
Geographic Information System
Graphical User Interface
Highway Advisory Radio
Human Machine Interface
High Occupancy Vehicle
Incident Command Center
Information Technology
Information Technology Bulletin
Intelligent Transportation System
Keyboard-Video-Monitor
Local Area Network
Maintenance Decision Support System
Office of Administration, Office for Information Technology
Pennsylvania Department of Transportation
Project Manager
Pennsylvania State Police
Pennsylvania Turnpike Commission
Road Condition Reporting System
Regional Traffic Management Center
Roadway Weather Information System
Request for Proposals
Service Level Agreement
State Route
Traffic Management Center
User Acceptance Test
Appendix BB - Page 1 of 1
APPENDIX C
STANDARD CONTRACT TERMS AND
CONDITIONS
http://www.dgsweb.state.pa.us/comod/CurrentForms/STD274_SAP.doc
Appendix C Page 1 of 1
APPENDIX CC
DEPARTMENT SPECIFIC STANDARDS AND
TOOLS AND CURRENT COMPUTING
ENVIRONMENT
Department Specific Standards and Tools
•
Version Control
o IBM Rational ClearCase
•
Enhancement/defect Tracking
o IBM Rational ClearQuest
•
Requirements Management
o IBM Rational RequisitePro
•
Application Test Management
o Rational Test Suite
Rational Test Manager
Rational Manual Tester
Rational Functional Tester
Rational Performance Tester
•
Enterprise Security Management Software
o CA Siteminder
•
Application Help System
o Adobe RoboHelp
•
Message Oriented Middleware Software
o IBM Websphere MQ
•
Java Application Infrastructure
o IBM Websphere
•
Application Programming Languages (using industry standard frameworks)
o Java
o .NET
•
Data Modeling
o ERWIN
•
Reporting
o Crystal Reports
o Business Objects XI
•
Document Management
o IBM FileNet
•
Data Integration Software
o Informatica
•
Service Desk Request Tracking
Appendix CC - Page 1 of 8
o
BMC Remedy
•
Database Management Systems
o IBM DB2, Oracle, M/S SQL Server
•
Desktop Software Standards
o Microsoft Windows XP Pro SP3 (targeting Windows 7 – 64 bit)
o Microsoft Office 2007 SP2
o Microsoft Internet Explorer 6.0 SP3 (targeting IE8)
o Microsoft Visio Viewer 2007 SP2
o Java Runtime 1.4.2_06 (targeting v1.6.0_02)
o Pantagon Viewer (IDM Viewer) 4.0.2
o Corel GIS Active-X Viewer 7.1
o Adobe Acrobat Reader 8.1.3
o McAfee 8.5i w/patch 8
o Winzip 12 Licensed
o Lotus Notes 8.5
o DB2 Run-Time Client v9
o MDAC 2.8
o SAP Gui 7.10
o Adobe Flash Player 10
•
Release Management Methodology
o Release management practices appropriate to ITILv3.
The Information Technology Infrastructure Library (ITIL) is a customizable
framework of good practices designed to promote quality computing services
in the information technology (IT) sector.
Appendix CC - Page 2 of 8
Current Computing Environment
As of 01/2010
1. Host Systems
a. Department of Transportation/Data Power House
i. IBM z10 EC Series Enterprise Server model 2097-604
1. z/OS 1.10 and z/VM 5.4 Operating systems
2. z/OS 2 LPARS: Side 0 – Production Applications, Side 1- Development and
Test
3. z/VM 2 LPARS: LNX02 Production z/Linux guests, LNX01 Pre-prod
z/Linux guests
b. Server Farm
i. Windows-based Application and Database servers
1. Windows 2003 Server
a. Intel x86 Server platform for production environments
b. VMWare 3.5, Update 4 platform for all other environments (typical)
2. Microsoft SQL 2000, SQL 2005 and Oracle
c. Windows 2003 Forest with users in the Commonwealth’s domain (CWOPA), while all other
resources are in the Department of Transportation’s domain (PENNDOT)
2. Network
a. LAN – Ethernet, TCP/IP, 100MB to desktop
b. WAN
i. Core - Frame Relay and ATM moving to MPLS
ii. Remote Sites – T1
iii. Business Partners – up to and including T1
iv. Engineering District Offices – DS3 up to 45Mbs
v. Riverfront Office Complex – 2 x 50Mb Metro Ethernet
vi. Commonwealth Keystone Building – 3 x 100Mb Metro Ethernet
vii. Willow Oak Mainframe Connection – 2 OC3’s
viii. Server Farm (acts as the WAN hub) – 4 OC12’s
Special Note on PennDOT Network and the Traffic Management Centers(TMCs):
Each TMC has a local 100Mb Ethernet LAN. The TMCs are connected to the PENNDOT Server
Farm through dedicated WAN links with varying bandwidth capacities. Smaller TMCs are
connected with 15Mb paths, while larger TMCs are connected with 45Mb paths. In King of
Prussia and potentially at other sites, the TMC LAN traffic traverses a firewall and VPN routers
before routing across the WAN.
All TMCs have ITS field devices with varying connection media. Fiber Optic Network, Point-toPoint Fiber, T-1, Cellular Modem, and POTS are examples of communication technologies
deployed in support of TMC operations. ITS field device can only be operated by the sponsoring
TMC. No other TMC can communicate directly with another TMC s’ ITS filed devices.
The LAN is supported by the PENNDOT Bureau of Infrastructure and Operations (BIO) in
conjunction with TMC staff and local PENNDOT District IT resources. The WAN is supported
and managed by Verizon Business in conjunction with PENNDOT BIO. ITS field device
communications are supported by the installation vendor as prescribed in the respective TMC
maintenance contract.
Appendix CC - Page 3 of 8
PennDOT is currently working on a project to provide better connectivity between the TMC’s.
The purpose of the TMC Connectivity Project is to develop and provide a robust, flexible,
adaptable and scalable network architecture for Traffic Management Center (TMC) connectivity
that will enable interoperability of TMCs across the state, provide TMC operators access to
PennDOT intranet resources, address business partner connections and meet PennDOT’s longterm business and information technology needs. It is anticipated that the TMC connectivity
solution will be in place for the Next Generation ATMS deployment.
3. End-users
a. Desktop PC – IBM Compatible Dual Core 2.4Ghz 160GB HDD, 2GB mem
b. Laptops – Pentium M and above
c. OS - Microsoft Windows XP with SP3
d. Office - Office 2007 with SP2
e. Browser - Microsoft Internet Explorer 6 with SP3
f. Java 1.6.0_02
g. Adobe Reader 9.2.0
h. IDM Viewer 4.0.2
i. IBM Host on Demand (Terminal Emulation)
4. FileNet
a. Image Services
b. Content Services
c. HPII
d. Webservices
e. Capture
f. Desktop
g. eProcess
h. Report Manager
i. MSSQL
j. OS
k. eInput
l. InputAxcel server 5.3
m. FileNet Exporter
n. Dispatcher
5.3
o. IMC
p. Opex
4.1.1 with HotFix 7
5.4
3.3.8
4.0.2 HotFix 6
5.0 HT 3
4.0 HT 1
5.1 patch 7
4.1
2005 with Sp 3
Windows Server 2003 SP2
2.0
5.3.3
5.2
5.2
5. Windows Sandbox Environment
Server Usage
SiteMinder
Hardware
VMWare
Identity Manager
VMWare
Business Partner
Active Directory
POC Rational
ClearCase
POC Rational
License Server
VMWare
VMWare
VMWare
Operating System
Windows 2003 Server
Standard Edition
Windows 2003 Server
Standard Edition
Windows 2003 Server
Standard Edition
Windows 2003 Server
Standard Edition
Windows 2003 Server
No. of Processors
1
Appendix CC - Page 4 of 8
1GB
Memory
1
512MB
1
512MB
1
2GB
1
2GB
Server Usage
POC DB Server
POC Build
Management
POC Test Server
POC WAS Server
POC DB Server
(Oracle)
Extranet Web
Server
Hardware
VMWare
VMWare
Operating System
Windows 2003 Server
Windows 2003 Server
No. of Processors
1
1.
VMWare
VMWare
VMWare
Windows 2003 Server
Suse 9 Linux
Suse 9 Linux
1
1
1
512MB
1GB
1GB
VMWare
Windows 2003 Server
1
2GB
1GB
2GB
Memory
6. Windows Development Environment
Server Usage
Captiva InputAccel
Server
Image Enhancement
and Barcode
Recognition
Dispatcher for IA
Extraction
Dispatcher for IA
Classification
Opex Scanner
Multi-Directory
Watch Module
FileNet – Exporter
Hardware
VMWare
Operating System
Windows 2003
Server
Windows 2003
Server
No. of Processors
1
Memory
2GB
1
2GB
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
1
2GB
1
2GB
1
2GB
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
1
2GB
Web Server with IIS
for eInput/eRouter
Web Server with IIS
for Input
Mangement Console
FileNet Applications
Server
VMWare
1
2GB
1
2GB
IBM Pentium III
1.0 GHz
Windows 2003
Server
1
2GB
EDMS Database
Server – SQL Server
IBM Pentium III
1.4 GHz
Windows 2003
Server
1
2GB
FileNet Report
Manager Server
IBM 3.6 GHz
Xeon HT
Windows 2003
Server
1
1GB
FileNet Image
Services
EDMS Web Server
0 Legacy Integration
Server Usage
EDMS Web Server .centric Integration
SiteMinder Policy
Server
Identity Manager
Server
Informatica Power
Center Advanced
IBM Pentium III
1.0 GHz
IBM Pentium III
1.0 GHz
Hardware
VMWare
Windows 2003
Server
Windows 2003
Server
Operating System
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
1
1GB
1
1 GB
No. of Processors
1
Memory
1GB
1
2 GB
1
1 GB
1
2 GB
VMWare
VMWare
VMWare
VMWare
VMWare
VMWare
VMWare
VMWare
VMWare
Appendix CC - Page 5 of 8
Extranet Web
Server and WAS
Server
Windows UNI
Server
Rational ClearCase
Server
Rational
DB/License Server
7.
VMWare
Windows 2003
Server
1
2 GB
VMWare
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
1
2 GB
1
2 GB
1
2 GB
Operating System
Windows 2003
Server
Windows 2003
Server
No. of Processors
1
Memory
2 GB
1
2 GB
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
1
2 GB
1
2 GB
1
2 GB
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
1
2 GB
1
2 GB
1
2 GB
IBM Pentium III
1.0 GHz
IBM Pentium III
1.4 GHz
IBM Pentium III
1.0 GHz
IBM Pentium III
1.4 GHz
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
1
1GB
1
2GB
1
1GB
1
2GB
IBM Pentium III
1.0 GHz
Windows 2003
Server
1
1 GB
VMWare
Windows 2003
Server
Windows 2003
Server
Operating System
Windows 2003
Server
Windows 2003
Server Enterprise
1
2 GB
1
1 GB
No. of Processors
2
Memory
1GB
4
16 GB
VMWare
VMWare
Windows System Test Environment
Server Usage
Captiva InputAccel
Server
Image Enhancement
and Barcode
Recognition
Dispatcher for IA
Extraction
Dispatcher for IA
Classification
Opex Scanner
Multi-Directory
Watch Module
FileNet – Exporter
Hardware
VMWare
Web Server with IIS
for eInput/eRouter
Web Server with IIS
for Input
Mangement
Console
FileNet IS
Root/Index Server
FileNet IS Library
VMWare
FileNet Report
Manager Server
EDMS Database
Server – MS SQL
Server
EDMS Web Server
Legacy Integration
(Internal)
EDMS Web Server
- .centric Integration
EDMS Web Server
(DMZ)
Server Usage
FileNet HPII Import
Server
Informatica Power
Center Advanced
VMWare
VMWare
VMWare
VMWare
VMWare
VMWare
IBM Xeon HT 3.6
GHz
Hardware
IBM Pentium III
Xeon 700 MHz
IBM Xeon 3.5
GHz
Appendix CC - Page 6 of 8
Extranet Web
Server and WAS
Server
8.
Windows 2003
Server
1
2 GB
No. of Processors
1
Memory
2GB
1
1 GB
1
1GB
No. of Processors
4
Memory
4 GB
2
4 GB
Windows Training / UAT Environment
Server Usage
2 - Extranet Web
Servers and WAS
Servers (Cluster)
SiteMinder Policy
Server
Identity Manager
Server
9.
VMWare
Hardware
VMWare
Operating System
Windows 2003
Server
VMWare
Windows 2003
Server
Windows 2003
Server
VMWare
Windows Production Environment
Server Usage
4 – Captiva
InputAccel Servers
2 – Image
enhancement and
Barcode
Recognition
4 - FileNet –
Exporter Servers
2 – Dispatcher for
IA Extraction
Servers
2 – Dispatcher for
IA Classification
Servers
2 – Opex Scanner
Multi-Directory
Watch Module
Servers
2 – Web Servers
with IIS for
eInput/eRouter
Web Server with IIS
for Input
Management
Console
FileNet IS
Root/Index Server
FileNet IS Library
FileNet Report
Manager Server
EDMS Database
Server – MS SQL
Server
EDMS Partner
Hardware
IBM x3650 Dual
Core Xeon 3.0
GHz
IBM x3650 Dual
Core Xeon 3.0
GHz
Operating System
Windows 2003
Enterprise Server
(Clustered)
Windows 2003
Enterprise Server
IBM X3650 Dual
Core Xeon 3.0
GHz
IBM X3650 Dual
Core Xeon 3.0
GHz
IBM X3650 Dual
Core Xeon 3.0
GHz
IBM X3650 Dual
Core Xeon 3.0
GHz
Windows 2003
Enterprise Server
2
4GB
Windows 2003
Enterprise Server
2
4GB
Windows 2003
Enterprise Server
2
4GB
Windows 2003
Enterprise Server
2
4 GB
IBM X3650 Dual
Core Xeon 3.0
GHz
VMWare
Windows 2003
Enterprise Server
2
4GB
Windows 2003
Server
1
1 GB
IBM Xeon 3.6
GHz
IBM Xeon 3.6
GHz
IBM Pentium 4
3.6 GHz
IBM Xeon 3.6
GHz
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
4
3GB
4
3 GB
4
2 GB
4
3 GB
IBM Xeon 3.6
Windows 2003
2
2 GB
Appendix CC - Page 7 of 8
Import Server
Server Usage
2 - EDMS Web
Servers – Legacy
Integration
(Internal)
2 - EDMS Web
Servers - .centric
Integration
EDMS Web Server
(DMZ)
FileNet HPII Import
Server
SiteMinder Primary
Policy Server
SiteMinder
Secondary Policy
Server
Identity Manager
Server
Mercury
Administration
Server
Mercury Controller
GHz
Hardware
IBM Xeon 3.6
GHz
Server
Operating System
Windows 2003
Server
IBM Xeon 3.6
GHz
No. of Processors
2
Memory
2 GB
Windows 2003
Server
2
2 GB
IBM Xeon 3.6
GHz
IBM Xeon 3.6
GHz
IBM x360 3.0
GHz
IBM x360 3.0
GHz
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
2
2 GB
2
2GB
4
8GB
4
8 GB
IBM x3650 Dual
Core Xeon 3.0
GHz
IBM x-Series
Windows 2003
Server
4
8 GB
Windows 2003
Server
1
2 GB
IBM x- Series
1
1 GB
1
2 GB
1
2 GB
1
2 GB
IBM x360 Xeon
3.6 GHz
IBM x346 3.6
GHz
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
4
16 GB
2
4 GB
IBM x345 Dual
Core 2.6 GHz
Windows 2003
Server
2
2 GB
IBM x346 3.6
GHz
IBM x346 3.6
GHz
Windows 2003
Server
Windows 2003
Server
2
3.5 GB
2
3.5 GB
Mercury File Server
IBM x-Series
Mercury Utility
Server
Mercury Data
Processor
Informatica Power
Center Advanced
2 - Extranet Web
Servers and WAS
ESB Servers
(Cluster)
2 – Windows UNI
Servers (Primary
and backup)
Rational ClearCase
Server
Rational
DB/License Server
IBM x-Series
IBM x-Server
Appendix CC - Page 8 of 8
APPENDIX D
DOMESTIC WORKFORCE UTILIZATION
CERTIFICATION
APPENDIX D
DOMESTIC WORKFORCE UTILIZATION CERTIFICATION (07/24/09)
To the extent permitted by the laws and treaties of the United States, each proposal will be scored for its
commitment to use the domestic workforce in the fulfillment of the contract. Maximum consideration
will be given to those offerors who will perform the contracted direct labor exclusively within the
geographical boundaries of the United States or within the geographical boundaries of a country that is a
party to the World Trade Organization Government Procurement Agreement. Those who propose to
perform a portion of the direct labor outside of the United States and not within the geographical
boundaries of a party to the World Trade Organization Government Procurement Agreement will receive
a correspondingly smaller score for this criterion. In order to be eligible for any consideration for this
criterion, offerors must complete and sign the following certification. This certification will be included
as a contractual obligation when the contract is executed. Failure to complete and sign this certification
will result in no consideration being given to the offeror for this criterion.
I,
______________________[title]
of
____________________________________[name
of
Contractor] a _______________ [place of incorporation] corporation or other legal entity,
(“Contractor”) located at __________________________________________________________
[address], having a Social Security or Federal Identification Number of ________________________, do
hereby certify and represent to the Commonwealth of Pennsylvania ("Commonwealth") (Check one of
the boxes below):
All of the direct labor performed within the scope of services under the contract will be
performed exclusively within the geographical boundaries of the United States or one of the
following countries that is a party to the World Trade Organization Government Procurement
Agreement: Aruba, Austria, Belgium, Bulgaria, Canada, Chinese Taipei, Cyprus, Czech
Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary, Iceland,
Ireland, Israel, Italy, Japan, Korea, Latvia, Liechtenstein, Lithuania, Luxemburg, Malta, the
Netherlands, Norway, Poland, Portugal, Romania, Singapore, Slovak Republic, Slovenia, Spain,
Sweden, Switzerland, and the United Kingdom
OR
________________ percent (_____%) [Contractor must specify the percentage] of the
direct labor performed within the scope of services under the contract will be performed within
the geographical boundaries of the United States or within the geographical boundaries of one of
the countries listed above that is a party to the World Trade Organization Government
Procurement Agreement. Please identify the direct labor performed under the contract that will
be performed outside the United States and not within the geographical boundaries of a party to
the World Trade Organization Government Procurement Agreement and identify the country
where the direct labor will be performed: ____________________________________________
______________________________________________________________________________
[Use additional sheets if necessary]
The Department of General Services [or other purchasing agency] shall treat any misstatement as
fraudulent concealment of the true facts punishable under Section 4904 of the Pennsylvania Crimes Code,
Title 18, of Pa. Consolidated Statutes.
Attest or Witness:
______________________________
Corporate or Legal Entity's Name
_____________________________
Signature/Date
______________________________
Signature/Date
_____________________________
Printed Name/Title
______________________________
Printed Name/Title
Appendix D - 1 of 1
INSTRUCTIONS
Overall
1. Although formulas are imbedded in all sheets of this workbook,
it is the Offeror's responsibility to verify that all amounts are
accurate.
2. Please contact the Issuing Officer with any questions or
concerns.
Itemized Costs-Positions
1. Fill in the "Offeror Name", "Date" and "Completed By" fields at
the top of the page (cells B4, B5 & B6).
2. Fill in only those cells in the "$ per Hour" columns (columns B,
E, H, K & N) that are not highlighted.
3. There are twenty blank position fields available for any position
that you are proposing. All positions being proposed must be
included in order to complete your proposed rate card. For each
position proposed, fill in the data for all five years.
4. The "Profit" field for each postion is to be entered as a
percentage not to exceed 10%.
Itemized Costs- Other
1. Fill in the ATMS COTS package purchase and licensing costs.
2. Fill in the Escrow Agreement costs.
3. Fill in the blended rate for Release Management task.
Rate Card
This sheet is populated by your input on the "Itemized Costs Positions" sheet. No input is required.
Task Costs
1. The "Specified Position" and the "Hourly Rate" fields will
populate from the "Itemized Costs-Positions" sheet and the
"Cost" fields will calculate.
2. For each "Specified Position" fill in the "Company Name" field
and the "Hours" field for each of the five years.
3. Some items will populate from the "Itemized Cost - Other"
sheet. For each of those items fill in the "Company Name" (if
aplicable); no additional input is required.
Planned ITS Integration
Fill in the unit costs for each identified integration item.
"Estimated Quantity" is provided for each line item and the
"Total Costs" fields will calculate.
Summary
This sheet is populated by your input on the "Itemized Costs Positions", "Itemized Costs - Other", "Task Costs", and
"Planned ITS Integration" sheets. No input is required. This
sheet calculates the cost of a resulting contract by using your
rate card multiplied by the hours you propose for the completion
of the tasks. The "Total Cost" for all five years will be used to
determine the Cost Point scores.
APPENDIX F
DISADVANTAGED BUSINESS ENTERPRISE
REQUIREMENTS
DISADVANTAGED BUSINESS ENTERPRISE REQUIREMENTS
1. POLICY
A. The Pennsylvania Department of Transportation (PennDOT) does not discriminate on the
basis of race, color, national origin or sex. It is the policy of PENNDOT and the United
States Department of Transportation that Disadvantaged Business Enterprises (DBEs) be
given the opportunity to participate in the performance of contracts financed, in whole or
in part, with federal funds.
B. The requirements of 49 CFR 26 apply to this contract.
C. Only DBE firms certified by the Pennsylvania Unified Certification Program (PA UCP)
count toward the DBE Goal.
2. DEFINITIONS
A. Disadvantaged Business Enterprise or DBE means a for-profit small business concern:
1) That is at least 51 percent owned by one or more individuals who are both socially
and economically disadvantaged or, in the case of a corporation, in which 51 percent
of the stock is owned by one or more such individuals; and
2) Whose management and daily business operations are controlled by one or more of
the socially and economically disadvantaged individuals who own it.
B. Small business concern means, with respect to firms seeking to participate as DBEs in
DOT-assisted contracts, a small business concern as defined pursuant to section 3 of the
Small Business Act and Small Business Administration regulations implementing it (13
CFR part 121) that also does not exceed the cap on average annual gross receipts
specified in §26.65(b).
C. Socially and economically disadvantaged individual means any individual who is a
citizen (or lawfully admitted permanent resident) of the United States and who is:
1) Any individual who the Department finds to be a socially and economically
disadvantaged individual on a case-by-case basis.
2) Any individual in the following groups, members of which are rebuttably presumed
to be socially and economically disadvantaged:
i) "Black Americans," which includes persons having origins in any of the Black
racial groups of Africa;
ii) "Hispanic Americans," which includes persons of Mexican, Puerto Rican, Cuban,
Dominican, Central or South American, or other Spanish or Portuguese culture or
origin, regardless of race;
iii) "Native Americans," which includes persons who are American Indians, Eskimos,
Aleuts, or Native Hawaiians;
iv) "Asian-Pacific Americans," which includes persons whose origins are from Japan,
China, Taiwan, Korea, Burma (Myanmar), Vietnam, Laos, Cambodia
(Kampuchea), Thailand, Malaysia, Indonesia, the Philippines, Brunei, Samoa,
Guam, the U.S. Trust Territories of the Pacific Islands (Republic of Palau), the
Appendix F - Page 1 of 6
Commonwealth of the Northern Marianas Islands, Macao, Fiji, Tonga, Kirbati,
Juvalu, Nauru, Federated States of Micronesia, or Hong Kong;
v) "Subcontinent Asian Americans," which includes persons whose origins are from
India, Pakistan, Bangladesh, Bhutan, the Maldives Islands, Nepal or Sri Lanka;
vi) Women;
vii) Any additional groups whose members are designated as socially and
economically disadvantaged by the SBA, at such time as the SBA designation
becomes effective.
D. DBE Goal means the amount of DBE participation stated by PennDOT in the Request for
Proposal. This DBE Goal is stated in terms of total project cost and is based on the
project’s potential for subcontracted work and the availability of DBEs to perform such
subcontract work.
E. Certified DBE means those firms certified by the Pennsylvania Unified Certification
Program (PA UCP). Certifying participants in the PA UCP are Allegheny County’s
Department of Minority, Women, and Disadvantaged Business Enterprises; the City of
Philadelphia, Philadelphia International Airport DBE Program Office; the Port Authority
of Allegheny County’s Office of Equal Opportunity; the Southeastern Pennsylvania
Authority’s (SEPTA) DBE Program Office, and PennDOT’s Bureau of Equal
Opportunity. Refer to the PA UCP website at www.paucp.com for a list of certified
DBEs. All firms listed on the website are certified and are eligible to participate as a
DBE on PennDOT’s federally funded projects. A copy of the PA UCP DBE Directory is
available by contacting any of the certifying participants.
For more information regarding the PA UCP or DBE Certification, please contact
PennDOT’s Bureau of Equal Opportunity 717-787-5891 or 1-800-468-4201.
3. FAILURE TO COMPLY WITH DBE REQUIREMENTS
A. Failure of a prime contractor to meet the DBE Goal and failure to provide a verifiable
“good faith effort” in a response to the RFP will result in rejection of the proposal.
Furthermore, if PennDOT does not approve the “good faith effort”, the proposal will be
rejected.
B. Failure by a prime contractor and subcontractors to carry out the DBE requirements
constitutes a breach of contract and may result in termination of the contract or action as
appropriate.
C. Upon completion of the project, PennDOT will review the actual DBE expenditures to
determine compliance with the DBE Goal. If the DBE Goal is not met, written
explanation from the contractor will be reviewed by PennDOT. If the shortfall in meeting
the DBE Goal is determined to be unjustified and unwarranted, PennDOT may impose
sanction as appropriate.
D. Failure to comply with any DBE requirements may result in termination of the contract,
being barred from proposing on PennDOT RFPs for up to three years, or any other
remedy, as PennDOT deems appropriate.
Appendix F - Page 2 of 6
4. PROCEDURES
A. In response to a Request for Proposal, a prime contractor must make a “good faith effort”
to subcontract a portion of the project work to a certified DBEs. This portion should be
equal to or greater than the DBE Goal stated in the Request for Proposal. Efforts to
subcontract work include but are not limited to:
1) Efforts made to solicit through all reasonable and available means (e.g. use of the
DBE Directory, attendance at pre-bid meetings, advertising and/or written notices)
the interest of all certified DBEs who have the capability to perform the work of the
contract. The bidder must provide written notification, at least 15 calendar days prior
to the proposal due date, to allow the DBEs to respond to the solicitation. The bidder
must determine with certainty if the DBEs are interested by taking appropriate steps
to follow up initial solicitations.
2) Efforts made to select portions of the work to be performed by DBEs in order to
increase the likelihood that the DBE Goal will be achieved. This includes, where
appropriate, breaking out contract work items into economically feasible units to
facilitate DBE participation, even when the prime contractor might otherwise prefer
to perform these work items with its own forces.
3) Efforts made to provide interested DBEs with adequate information about the plans,
specifications, and requirements of the contract in a timely manner to assist them in
responding to a solicitation.
4) Efforts made to negotiate in good faith with interested DBEs. It is the bidder's
responsibility to make a portion of the work available to DBE subcontractors and
suppliers and to select those portions of the work or material needs consistent with the
available DBE subcontractors and suppliers, so as to facilitate DBE participation.
Evidence of such negotiation includes the names, addresses, and telephone numbers
of DBEs that were considered; a description of the information provided regarding
the plans and specifications for the work selected for subcontracting; and evidence as
to why additional agreements could not be reached for DBEs to perform the work. A
bidder using good business judgment would consider a number of factors in
negotiating with subcontractors, including DBE subcontractors, and would take a
firm's price and capabilities as well as contract goals into consideration. However, the
fact that there may be some additional costs involved in finding and using DBEs is
not in itself sufficient reason for a bidder's failure to meet the contract DBE Goal, as
long as such costs are reasonable. Also, the ability or desire of a bidder to perform the
work of a contract with its own work force does not relieve the bidder of the
responsibility to make good faith efforts. Bidders are not, however, required to accept
higher quotes from DBEs if the price difference is excessive or unreasonable.
5) Failure to accept DBE as being unqualified without sound reasons based on a
thorough investigation of their capabilities. The contractor's standing within its
industry, membership in specific groups, organizations, or associations and political
or social affiliations (for example union vs. non-union employee status) are not
legitimate causes for the rejection or non-solicitation of bids in the contractor's efforts
to meet the DBE Goal.
6) Efforts to assist interested DBEs in obtaining bonding, lines of credit, or insurance as
required by the recipient or contractor.
Appendix F - Page 3 of 6
7) Efforts to assist interested DBEs in obtaining necessary equipment, supplies,
materials, or related assistance or services.
8) Utilizing the PA UCP DBE Directory of certified firms.
B. The prime contractor is prohibited from requiring any DBE to agree not to provide
subcontracted effort to other proposers.
C. At the proposal presentation stage, once a DBE has agreed to perform work as a
subcontractor, the prime must provide the business name of the DBE with address,
contact person, phone number, PA UCP DBE Certification Number, a detailed narrative
description of the service to be provided by the DBE, and the percent of the proposal’s
cost to be contractually allocated to the DBE in Section II-9 of the technical proposal.
(Do not provide any cost information in the technical proposal.) A letter of intent from
the DBE stating that the DBE has agreed to enter into a subcontract if the prime
contractor is successful should be include in Section II-9 of the technical proposal.
D. If a DBE cannot be located or if the percent of total proposal cost allocated to the DBE is
less than the DBE Goal, the prime contractor must provide a “good faith effort” in
Section II-6 of the technical proposal. The “good faith effort” must explain and
document the effort made by the prime contractor to obtain DBE participation.
Documentation must be verifiable and must include:
1) The names, addresses, phone and fax numbers of DBEs who were contacted, the
dates of initial contact and the follow-up efforts made by the prime contractor;
2) A description of the information provided to the DBE to define the work to be
performed;
3) Documentation of the reasons why any DBE contacted would not agree to participate.
E. If the proposal of the selected contractor contains a “good faith effort” because the
proposal fails to meet the established DBE Goal, PennDOT will review the “good faith
effort” provided by the contractor in the proposal. If the “good faith effort” is deemed to
be satisfactory, the “good faith effort” will be approved. In such a case the contractor
shall continue a “good faith effort” throughout the life of the contact to increase the DBE
participation to meet the contract DBE Goal. If PennDOT cannot accept the “good faith
effort” submitted by the contractor, the proposal will be considered non-responsive and
PennDOT will notify the contractor that the proposal is rejected.
F. Any proposal that does not meet the DBE Goal and does not provide a “good faith effort”
which identified DBEs who were contacted, will be rejected without review of the
technical contents. Use of a DBE certified by others and not by the PA UCP, use of a
DBE whose certification has expired or cannot be confirmed by PennDOT’s Bureau of
Equal Opportunity, or statements that the DBE Goal will be met after a contractor is
awarded a contract are unacceptable and will result in rejection of proposal.
G. The prime contractor must provide PennDOT with draft and executed versions of the
subcontract with the DBE within 90 days from the date of the notice to proceed given on
the prime contract. Failure to provide the executed subcontract will result in a temporary
stop of work on the 91st day of the contract until an acceptable DBE subcontract is
provided to PennDOT. Any time period involved in such a temporary stop of work will
Appendix F - Page 4 of 6
not extend the period of performance of the contract nor be accepted by PENNDOT as a
justification for project time extension.
H. The prime contractor shall include the Disadvantaged Business Enterprise Requirements
in all subcontracts. Subcontractors must conform to the intent of these requirements.
I. If it becomes necessary to replace a DBE subcontractor during the contract, make a
“good faith effort” to re-contract the same or other work with another certified DBE firm.
Such an effort must include:
1) Alert PennDOT immediately and document the problem in writing;
2) Contact available individual qualified DBEs in an effort to re-contract work to fulfill
the DBE Goal stated in the Request for Proposal; and
3) Provide PennDOT with copies of all new DBE subcontracts (and additional “good
faith effort” information) if the original DBE Goal is not met) by the close of business
of the 7th calendar day of PennDOT’s receipt of written notice of the need to replace a
DBE.
J. Inform PennDOT, in writing, of any situation in which payments are not made to the
DBE Subcontractor as required by the subcontract.
K. Keep records necessary for compliance with DBE utilization obligations by indicating:
1) The number of DBE and non-DBE subcontractors and the type of work, materials or
services performed in the project;
2) Efforts to secure DBE firms and individual whenever a subcontractor is contemplated
during a contact;
3) Documentation of all communication to obtain the services of DBEs on a project;
4) The amounts paid to DBEs by invoice period.
L. Upon completion of a DBE’s work, the prime contractor must submit a certification of
the actual amount paid to the DBE. If the actual amount paid is less than the amount of
the subcontract, an explanation is required and subject to the review and action of
PennDOT.
5. COUNTING DBE PARTICIPATION
A. If the contractor submitting the proposal and serving as prime contractor is a certified
DBE, count the dollar amount of the work to be performed by the DBE toward the DBE
Goal.
B. If the materials or supplies are purchased from a DBE supplier performing as regular
dealer, count 60 percent of the cost of the materials or supplies toward DBE Goal. A
regular dealer is a firm that owns, operates, or maintains a store, warehouse, or other
establishment in which the materials, supplies, articles or equipment of the general
character described by the specifications and required under the contract are bought, kept
in stock, and regularly sold or leased to the public in the usual course of business.
Appendix F - Page 5 of 6
C. If the materials or supplies are obtained from a DBE manufacturer, count 100 percent of
the cost of the materials or supplies toward DBE Goal. A manufacturer is a firm that
operates or maintains a factory or establishment that produces, on the premises, the
materials, supplies, articles, or equipment required under the contract and of the general
character described by the specifications.
D. Count toward the DBE Goal 100% of expenditures of DBE services including
professional, technical consultant or managerial services. Count fees or commissions
charged for providing any bonds or insurance specifically required for the performance of
the contract.
E. Any services to be performed by a DBE are required to be project related. The use of
DBEs is in addition to all other equal opportunity requirements of the contract.
Appendix F - Page 6 of 6
APPENDIX G
LOBBYING CERTIFICATION FORM
Lobbying Certification Form
Certification for Contracts, Grants, Loans, and Cooperative Agreements
The undersigned certifies, to the best of his or her knowledge and belief, that:
(1)
No federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned,
to any person for influencing or attempting to influence an officer or employee of any agency, a member of
Congress , an officer or employee of Congress, or an employee of a member of Congress in connection with the
awarding of any federal contract, the making of any federal grant, the making of any federal loan, the entering
into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of any
federal contract, grant, loan, or cooperative agreement.
(2)
If any funds other than federal appropriated funds have been paid or will be paid to any person
for influencing or attempting to influence an officer or employee of any agency, a member of Congress, an
officer or employee of Congress, or an employee of a member of Congress in connection with this federal
contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form-LLL,
"Disclosure of Lobbying Activities," in accordance with its instructions.
(3)
The undersigned shall require that the language of this certification be included in the award
documents for all subawards at all tiers (including subcontracts, subgrants, and contracts under grants, loans,
and cooperative agreements) and that all subrecipients shall certify and disclose accordingly.
This certification is a material representation of fact upon which reliance is placed when this transaction was
made or entered into. Submission of this certification is a prerequisite for making or entering into this
transaction imposed under Section 1352, Title 31, U.S. Code. Any person who fails to file the required
certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for such
failure.
SIGNATURE: _________________________________________________________
TITLE: _______________________________________________________________
DATE: _______________________________________________________________
Enclosure 1 to Management Directive 305.16
Appendix G - Page 1 of 1
APPENDIX H
DISCLOSURE OF LOBBYING ACTIVITIES
Disclosure Of Lobbying Activities
Management Directive 305.16
The link to the updated Disclosure of Lobbying Activities is indicated below. Continue to include
Enclosure 1 to Management Directive 305.16, Lobbying Certification Form.
http://www.whitehouse.gov/omb/grants/grants_forms.html
SF-LLL, Disclosure of Lobbying Activities – as revised in 1996
Appendix H - Page 1 of 1
APPENDIX I
NON-DISCLOSURE AUTHORIZATION
NON-DISCLOSURE AUTHORIZATION
This non-disclosure authorization agreement ("Authorization") is between the
Pennsylvania
Department
of
Transportation
(PennDOT)
and
_____________________________ ("Company"), with a business address at
__________________________________________________________.
I.
RECITALS
A. Company wishes to receive PennDOT District Network Diagrams which
are confidential and proprietary information (hereinafter collectively
"Information") for the sole purpose of preparing a proposal to be submitted in
response to the Request for Proposals Number 10R-01 Next Gen ATMS.
This exchange includes all communication of Information between the parties
in any form whatsoever, including oral, written and machine readable form,
pertaining to the above.
B. Company wishes to receive the Information for the sole purpose of
submitting a proposal in response to RFP 10R-01 Next Gen ATMS.
C. PennDOT is willing to disclose the Information and Company is willing to
receive the Information (as "Receiving Party") subject to the terms and
conditions set forth herein.
Therefore, PennDOT and Company agree, as follows:
1. That the disclosure of Information by PennDOT is in strictest confidence
and thus Company shall:
a. (1) Not disclose to any other person the Information and (2) use at
least the same degree of care to maintain the Information secret as
the Company uses in maintaining as secret its own secret
information;
b. Use the Information only for the above purposes;
c. Restrict disclosure of the Information solely to those employees of
Company having a need to know such Information in order to
accomplish the purpose stated above;
d. Advise each such employee, before he or she receives access to
the Information, of the obligations of Company under this
Authorization, and require each such employee to maintain those
obligations;
e. Return to PennDOT all documentation, copies, notes, diagrams,
computer memory media and other materials containing any portion
of the Information, or confirm to PennDOT, in writing, the
destruction of such materials no later than the date and time
Appendix I Page 1 of 3
identified in the RFP 10R-01, Calendar of Events, as the date and
time the sealed proposals must be received by; and
f. Immediately upon sale of Company or merger of Company with a
third party, return to PennDOT all documentation, copies, notes,
diagrams, computer memory media and other materials containing
any portion of the Information, or confirm to PennDOT, in writing,
the destruction of such materials.
g. Hold the Commonwealth and the PennDOT harmless and
indemnify the Commonwealth and the PennDOT, its officers,
employees or agents harmless against all claims, demands, actions
based upon or arising out of any activities performed under this
document, including but not limited to those alleging infringement of
patents or copyrights or misappropriation of trade secrets, for
damages, costs, or expenses arising, or alleged to have arisen,
from injury, death, property damage or any other cause as a result
of any act or omission of the Company under this authorization.
2. This Authorization imposes no obligation on Company with respect to any
portion of the Information received from PennDOT which (a)(1) was
known to the Company prior to disclosure by PennDOT and (2) as to
which the Company has no obligation not to disclose or use it, (b) is
lawfully obtained by the Company from a third party under no obligation of
confidentiality, (c) is or becomes generally known or available other than
by unauthorized disclosure, (d) is independently developed by the
Company or (e) is generally disclosed by PennDOT to third parties
without any obligation on the third parties.
3. This Agreement imposes no obligation on Company with respect to any
portion of the Information disclosed by PennDOT, unless such portion is
(a) disclosed in a written document or machine readable media marked
"CONFIDENTIAL" at the time of disclosure or (b) disclosed in any other
manner and summarized in a memorandum mailed to the Company within
thirty (30) days of the disclosure. Information disclosed by PennDOT
in a written document or machine readable media and marked
"CONFIDENTIAL" includes, but is not limited to the Network
Diagrams for RFP 0R-01 “Next Gen ATMS.”
4. The Information shall remain the sole property of PennDOT or the
originating agency.
5. In the event of a breach or threatened breach or intended breach of this
Authorization by Company, PennDOT, in addition to any other rights and
remedies available to it at law or in equity, shall be entitled to preliminary
and final injunctions, enjoining and restraining such breach or threatened
breach or intended breach.
Appendix I Page 2 of 3
6. The validity, construction, and performance of this Authorization are
governed by the laws of the Commonwealth of Pennsylvania.
7. The rights and obligations of the parties under this Authorization may not
be sold, assigned or otherwise transferred.
8. __________________ agrees to indemnify, hold harmless and (if
requested) defend PENNDOT, the Commonwealth of Pennsylvania, and
its officers, agents and employees from any and all claims, suits, actions,
judgments and losses accruing or resulting to any and all contractors,
subcontractors, and any other person, institution or organization
furnishing or supplying work, services, materials, or supplies in connection
with the performance of this Agreement, and from any and all claims,
losses, costs, demands, expenses, and actions accruing or resulting to
any person, institution or organization for injury, death, or property
damage caused by the negligence of the _________or its employees in
the performance of this Agreement and against any liability, cost and
expense for violation of proprietary rights or rights of privacy arising out of
the publication, translation, delivery, performance, use or disposition of
the ______________product covered under this Agreement.
This Authorization is binding upon PennDOT and Company, and upon the
directors, officers, employees and agent of each. This Authorization is effective
as of the date of execution and will continue indefinitely, unless terminated by
either party upon written notice.
However, Company's obligations of
confidentiality, indemnification and restrictions on use of the Information
disclosed by PennDOT shall survive termination of this Agreement.
Pennsylvania Department of Transportation
By:
Name:
Title:
Date:
(Company)
By:
Name:
Title:
Date:
Appendix I Page 3 of 3
APPENDIX J
ATMS DEVICE DRIVER MATRIX
APPENDIX J PennDOT Devices / Vendor’s Existing Device Driver Matrix
Instructions:
The PennDOT Devices / Vendor's Existing Device Driver Matrix form contains a list of PennDOT’s existing devices. Please complete
the form by using “Yes” or “No” to indicate whether a new device driver will need to be developed. If the proposed software solution
contains other already developed device drivers for devices that are not listed, please use the Additional Device Driver section to
identify those drivers.
PENNDOT DEVICES
VENDOR'S EXISTING DEVICE DRIVER MATRIX
Device Manufacturer
Model
DMS
ADAPTIVE Micro Systems
ADAPTIVE Micro Systems
ADAPTIVE Micro Systems
ADDCO
ADDCO
American Signal Co.
American Signal Co.
American Signal Co.
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Daktronics
Dambach
AX8120
AX8500
AX8700
AF0-2S2A4-0805H
AF0-2S3A4-0805H
CMS-T330
CMS-T333
Custom Built Walk-In DMS
VF-1000
VF-1420
VF-2000
VF-2020
VF-2040
VF-2320
VF-2400
VF-2420
VP-1300
VP-4000
D318FM
Appendix J - Page 1 of 4
Driver Needs to
Be Developed?
Comments
APPENDIX J PennDOT Devices / Vendor’s Existing Device Driver Matrix
PENNDOT DEVICES
VENDOR'S EXISTING DEVICE DRIVER MATRIX
Device Manufacturer
Dambach
Display Solutions
Display Solutions
Display Solutions
LedStar
Precision Solar Controls
Precision Solar Controls
SES America
SES America
SES America
SES America
SES America
SES America
Wanco
Model
Vario
Sunray Version 3
VMS 3x88
VMS 3x192
VMS-45-3x24
SMC 1000
SMC 2000
M6000
M6130
M6240
M6430
Sylvia
Sylvia 320
WTMMB
HAR
Highway Information Systems
Highway Information Systems
Highway Information Systems
American Signal Co.
Black Max
HiWay Max
Solar Max
T-100
CCTV
ASTI
Bosch
Bosch
EZ CAM
18X EnviroDome
25X EnviroDome
Appendix J - Page 2 of 4
Driver Needs to
Be Developed?
Comments
APPENDIX J PennDOT Devices / Vendor’s Existing Device Driver Matrix
PENNDOT DEVICES
VENDOR'S EXISTING DEVICE DRIVER MATRIX
Device Manufacturer
Bosch
Bosch
Bosch
Bosch
Bosch
Bosh
Bosch
COHU
Cylink
Detection Systems & Engineering
Pelco
Pelco
Vicon Inc.
Vicon Inc.
Vicon Inc.
Vicon Inc.
Model
ENVD2460P
Envirodome LTC 0928/25C
ENVT120P Dome
G3-AUTODOME
LTC 600
LTC 7960
VG4-323-ECSOP
3920 Series
0807-004
DS-5000 Dual Day/Night
Cameras
Spectra III
Spectra IV
S2-CW22
Surveyor 2000
SVFT
VC284-48
Detectors
EIS
EIS
EIS
Econolite
Wavetronix
RTMS G4
RTMS X2
RTMS X3
Autoscope – 706110
SSI 105
Appendix J - Page 3 of 4
Driver Needs to
Be Developed?
Comments
APPENDIX J PennDOT Devices / Vendor’s Existing Device Driver Matrix
Note:
If the proposed software solution contains other already developed device drivers for devices that are not listed, please use the
Additional Device Driver section to identify those drivers
VENDOR'S EXISTING DEVICE DRIVERS – ADDITIONAL DRIVERS
Device Manufacturer
Model
Appendix J - Page 4 of 4
Device Type
(CCTV, DMS,
HAR, etc.)
Comments
APPENDIX K
PROPOSAL COVER SHEET
COMMONWEALTH OF PENNSYLVANIA
PENNSYLVANIA DEPARTMENT OF TRANSPORTATION
RFP 10R-01 Next Gen ATMS
Enclosed in three separately sealed submittals is the proposal of the Offeror identified
below for the above-referenced RFP:
Offeror Information:
Offeror Name
Offeror Mailing Address
Offeror Website
Offeror Contact Person
Contact Person’s Phone Number
Contact Person’s Facsimile Number
Contact Person’s E-Mail Address
Offeror Federal ID Number
Submittals Enclosed and Separately Sealed:
Technical Submittal
Disadvantaged Business Enterprise Submittal
Cost Submittal
Signature
Signature of an official
authorized to bind the Offeror
to the provisions contained in
the Offeror’s proposal:
Printed Name
Title
FAILURE TO COMPLETE, SIGN AND RETURN THIS FORM WITH THE
OFFEROR’S PROPOSAL MAY RESULT IN THE REJECTION OF THE OFFEROR’S
PROPOSAL
Appendix K - Page 1 of 1
APPENDIX L
NETWORK DIAGRAMS
Appendix L, Network Diagrams are secure documents and will be made available upon Offerors’
submission of Appendix I, Non-Disclosure Authorizations.
APPENDIX M
PROPOSED ATMS SOLUTION TECHNICAL SUMMARY
APPENDIX M
Proposed ATMS Solution Technical Summary Matrix
Instructions:
The ATMS Solution Technical Summary Matrix form contains a list of technical summary questions for the proposed solution. Please
complete the form by providing a brief answer to each item as it relates to the proposed ATMS solution.
ATMS TECHNICAL SUMMARY MATRIX
Technical Summary Question
Summary of Proposed System
Comments
1. What is your proposed Vendor
Software (core ATMS package)?
2. If a COTS product is proposed – what is
your software customization approach?
Do you propose to customize inside or
outside of the COTS package?
3. What is the estimated system size
based on categories below:
a) Number of estimated servers?*
b) Number of estimated database
tables?
c) Number of programs?
d) Number of estimated application
services and interfaces?
4. User Interface & Program Languages
5. Operating System
6. Database Type (e.g. MS SQL or Oracle)
7. Middleware
8. Other software
(items not listed under questions 5, 6, and 7)
9. Host Hardware Platform
10. User Roles
11. Support Tools
12. Support Staff Roles
*Please fill out the ATMS Proposed Server Matrix on the next page. Information on the first line is provided as an example.
Appendix M - Page 1 of 2
APPENDIX M
Proposed ATMS Solution Technical Summary Matrix
ATMS Proposed Server Matrix
Processor
Speed
Number of
Processors
Memory
Estimated
Storage
Needed
Operating
System
Purpose (DB,
App, etc)
Server
Quantity
2.9 GHz
4
16GB
500GB
Windows 2008R2
Database
2
Appendix M - Page 2 of 2
APPENDIX O
STATEWIDE ATMS SOFTWARE
CONCEPT OF OPERATIONS
PennDOT Statewide ATMS Software
Concept of Operations
Last Updated: 04/11/11
Version: 5.0
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
TABLE OF CONTENTS
1.0
DOCUMENT HISTORY .................................................................................................. 1
2.0
PURPOSE DOCUMENT ................................................................................................ 2
3.0
SCOPE OF PROJECT ................................................................................................... 2
4.0
REFERENCED DOCUMENTS ....................................................................................... 3
5.0
BACKGROUND.............................................................................................................. 4
6.0
CONCEPT FOR THE PROPOSED SYSTEM ................................................................. 4
6.1
6.2
6.3
6.4
6.5
ENHANCE AND EXPAND EXISTING ATMS SOFTWARE ......................................... 4
MANUFACTURER’S SOFTWARE ............................................................................. 5
NEW CUSTOM ATMS SOFTWARE ........................................................................... 5
COTS SOFTWARE (AS-IS) ........................................................................................ 5
COTS SOFTWARE (PLANNED ENHANCEMENTS) .................................................. 5
7.0
USER-ORIENTED OPERATIONAL DESCRIPTION....................................................... 6
8.0
OPERATIONAL NEEDS ................................................................................................. 6
9.0
SYSTEM OVERVIEW .................................................................................................... 7
10.0
OPERATIONAL ENVIRONMENT ................................................................................... 8
11.0
SUPPORT ENVIRONMENT ........................................................................................... 8
12.0
OPERATIONAL SCENARIOS ........................................................................................ 9
12.1 SUMMARY OF SCENARIOS BY PHASE ..................................................................77
12.1.1
INITIAL DEPLOYMENT .....................................................................................77
FUTURE DEPLOYMENT ...................................................................................78
12.1.2
13.0
SUMMARY OF IMPACTS .............................................................................................79
LIST OF APPENDICES
APPENDIX A: MARKET PACKAGE
i
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
1.0 DOCUMENT HISTORY
This section intentionally left blank.
Appendix O – Page 1 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
2.0 DOCUMENT PURPOSE
The purpose of this document is to describe the Concept of Operations (ConOps) for the
Pennsylvania Department of Transportation (PennDOT) Statewide Advanced Traffic
Management System (ATMS) Software. The ConOps describes how the system will be used
from the operator’s, maintainer’s and manager’s perspectives in both normal and emergency
modes. The ConOps is intended for the stakeholders, to agree on system concepts and use.
This document will be expanded into a functional requirements document, which will describe
the software in much more detail. It is anticipated that these documents will be greatly expanded
into sample user interfaces, test plans and other design documents by the selected vendor.
The following are included in this document:
1. Document History
2. Scope of Project
3. Referenced Documents
4. Background
5. Concept for the Proposed System
6. User-Oriented Operational Description
7. Operational Needs
8. System Overview
9. Operational Environment
10. Support Environment
11. Operational Scenarios
12. Summary of Impacts
3.0 SCOPE OF PROJECT
The ATMS software will enable operators to more efficiently manage surface transportation
while also providing a more effective response to incidents. The ATMS software will allow for
efficient communication between Districts, states and other stakeholders and provide shared
control of all existing and future intelligent transportation system (ITS) devices throughout the
Commonwealth of Pennsylvania.
PennDOT operates six (6) district traffic management centers (TMCs), three (3) regional traffic
management centers (RTMCs) and PennDOT’s Central Office. Each district contains different
equipment and runs separate control software. Currently, each of the facilities functions
independently.
It is the intent that the ATMS software will be designed for full functionality. However, user and
site access may vary. Therefore, TMCs will be able to turn off functionality that they do not
need. Also, the ATMS software will allow for interagency coordination. It is anticipated that
through the use of administration and maintenance, functionality can be tailored to the needs of
different user groups.
Appendix O – Page 2 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
The primary users of the Next Generation ATMS are PennDOT’s TMCs and RTMCs. These
primary stakeholders will have read-write access to the ATMS according to the ATMS User
privileges defined by PennDOT. It is anticipated that the other identified potential stakeholders,
will initially have one-way communication with the ATMS. For example, video feeds may be
shared with the following stakeholders:
1. City of Philadelphia
2. City of Pittsburgh
3. Counties
4. Delaware Department of Transportation
5. Delaware River Joint Toll Bridge Commission (DRJTBC)
6. General Public
7. Information Service Providers
8. Maryland State Highway Administration (MDSHA)
9. Municipalities
10. New Jersey Department of Transportation (NJDOT)
11. New York State Department of Transportation
12. Ohio Department of Transportation
13. Pennsylvania Department of Transportation (PennDOT)
14. Pennsylvania Emergency Management Agency (PEMA)
15. Pennsylvania State Police (PSP)
16. Pennsylvania Turnpike Commission (PTC)
17. Regional Media
18. Special Events
19. Traffic.com
20. TrafficLand
21. Telvent/Inrix (PennDOT 511 System)
22. US Coast Guard
23. West Virginia Department of Transportation
Note: Other toll bridge authorities that interface with Pennsylvania highways (i.e. Delaware River
Port Authority, Burlington County Bridge Commission) were not included in the Regional ITS
Architectures; therefore, they were not included in this draft.
A complete ATMS system consists of a communication network, field devices, hardware and
software. While each of these components is critical to the successful operation, the focus of
this document will be the operational requirements of the ATMS software.
4.0 REFERENCED DOCUMENTS
•
PennDOT Statewide ATMS ITS Architecture (Draft); March 27, 2009
•
Systems Engineering Guidebook for ITS, Version 2.0
•
IEEE STD 1512 Systems Engineering Process
•
National ITS Architecture (http://www.iteris.com/itsarch/)
Appendix O – Page 3 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
•
PennDOT Bureau of Planning & Research
(http://www.dot.state.pa.us/Internet/Bureaus/pdPlanRes.nsf/PlanningAndResearchHome
Page?OpenFrameset)
•
DVRPC Regional Integrated Multi-modal Information Sharing
(http://www.dvrpc.org/transportation/longrange/its/rimis.htm)
•
RCRS = Road Condition Reporting System
(http://www.geodecisions.com/projectdetail.aspx?ProjectID=41102B)
•
PennDOT AVL Study: As-Is To-Be Business Process and Requirements Document
Version 3.01
5.0 BACKGROUND
PennDOT has been at the forefront of Intelligent Transportation Systems (ITS) deployments
since 1990. During this time there have been several deployments of ATMS software packages
and vendor provided software for the command and control of ITS field devices. In the past
PennDOT has used a variety of methods to procure ITS software to control field devices. As a
result, PennDOT currently has several independent and incompatible vendor provided software
and ATMS systems across the Commonwealth.
6.0 CONCEPT FOR THE PROPOSED SYSTEM
A number of alternative concepts were considered before identifying the proposed approach.
The following potential solutions were considered:
1.
2.
3.
4.
5.
Enhance and expand existing PennDOT ATMS software;
Use manufacturer’s software for ITS equipment control;
Develop a new custom ATMS software;
Procure an existing ATMS software package to be used as-is; and
Procure an existing ATMS software package with planned enhancements /
modifications.
6.1 ENHANCE AND EXPAND EXISTING PENNDOT ATMS
SOFTWARE
Some Districts currently use ATMS systems to provide centralized control. The existing ATMS
software was examined and found to be lacking in several key areas. The primary weakness,
which ultimately led to the current decision, was that the software lacked any up to date
documentation. In addition, it was estimated that more than 30 percent of the software would
need to be retooled. Making significant modification to a poorly documented software package
has a low probability of success and is not recommended.
Appendix O – Page 4 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
6.2
MANUFACTURER’S SOFTWARE
Some Districts operate using a number of independent software packages which were provided
by the device manufacturers along with the installation of their ITS equipment. At District 8-0 for
example, they use approximately six (6) to eight (8) separate software packages to control
dynamic message signs (DMS), Highway Advisory Radio (HAR), Video, etc. While this
represents the lowest investment to obtain basic functionality, the complexities of multiple
systems create inefficiencies and limits sharing information between TMCs to verbal
communication. Additionally, operators must be trained on several systems. And, finally, it is
not possible to provide a consistent, automated response to incidents when using disparate
systems.
6.3
NEW CUSTOM ATMS SOFTWARE
Designing and developing a custom ATMS software was strongly considered as an alternative.
A significant positive aspect is that PennDOT could specify the exact software needs and retain
total ownership of the software product. Potential negative aspects of this approach include
extending the implementation schedule (at least six months to one year would be needed just
for design) and significant (twice or more) cost increase. While we recommend that additional
primary research is completed through direct interaction with potential vendors, our secondary
research indicates that there are several fully developed ATMS software packages that could
meet 70 percent or more of the project goals, immediately.
6.4
EXISTING ATMS SOFTWARE PACKAGES (AS-IS)
Several existing ATMS software packages were examined and compared to the Use Case
Scenarios described in this Concept of Operations. While some packages seem to meet many
of the basic needs, it was not clear if any existing ATMS software packages met all of
PennDOT’s goals. Further, our research and experience shows that existing ATMS software
packages do not exist in the pure sense since each installation has unique needs. In our
opinion, existing ATMS software package implies that each installation uses the same software
and that the software can be installed by an end user. Our research indicates that the vast
majorities of ATMS installations have customized software and require significant time by the
vendor on-site to configure the installation.
6.5
EXISTING ATMS SOFTWARE PACKAGE (PLANNED
ENHANCEMENTS)
In reviewing the alternatives, it is our opinion that this option represents both the best value for
PennDOT and the highest probability of success. Our preliminary research indicates that
several vendors have existing ATMS software that appears to meet 70 percent or more of the
requested functionality. This approach has the dual key advantages of both utilizing a product
which is based on a proven solution, and providing the foundation for enhancements to meet
the PennDOT specific requirements. The only pitfall of this approach lies with potential legal
issues surrounding intellectual property (i.e. licenses, ownership, etc). However, due to the
number of states following this approach it is our belief that by involving PennDOT’s legal
department early in the procurement process, this potential issue can be managed.
Appendix O – Page 5 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
7.0 USER-ORIENTED OPERATIONAL DESCRIPTION
PennDOT currently has various ATMS software deployed throughout the Commonwealth. In
general, this software allows operators to perform the following basic tasks:
•
•
•
Track and manage incident and event information;
Advise the public of incidents (VMS, HAR, Internet); and
View current traffic conditions (CCTV, Vehicle Detectors).
Currently, limited information is exchanged between Districts. Typical stakeholders include
traffic operation and maintenance personnel. These personnel typically are computer literate,
but have limited training on both software development and/or network design.
8.0 OPERATIONAL NEEDS
The operational need identified is to provide a traffic management and emergency response
system on a statewide basis. The new system will provide the ability to control all existing and
planned ITS devices. A key element of the new system is the ability to aggregate all the
disparate field data into a central database. This database will be used for the following:
•
•
•
•
•
•
•
•
•
•
•
Provide information to the traveling public via the internet;
Traffic planning purposes;
Support timely dissemination of Amber Alerts;
Facilitate general road closure information gathering and dissemination;
Increase ease and efficiency of traffic and incident management/
Improve co-ordination between districts for the purpose of statewide corridor
management;
Enhance the gathering, quality verification, analysis and distribution of traffic data from
both internal and external sources;
Provide a source of real-time traveler information;
Aid in pro-active planning with regard to future highway projects;
Maximize utilization of ITS devices; and
Increase response automation.
This system will address the following market packages as defined by the National ITS
Architecture:
ARCHIVED DATA MANAGEMENT
AD1: ITS Data Mart
AD2: ITS Data Warehouse
TRAVELER INFORMATION
ATIS01: Broadcast Traveler Information
Appendix O – Page 6 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
ATIS06: Transportation Operations Data Sharing
TRAFFIC MANAGEMENT
ATMS01: Network Surveillance
ATMS02: Traffic Probe Surveillance
ATMS03: Surface Street Control
ATMS04: Freeway Control
ATMS05: HOV Lane Management
ATMS06: Traffic Information Dissemination
ATMS07: Regional Traffic Management
ATMS08: Traffic Incident Management System
ATMS09: Traffic Decision Support and Demand Management
ATMS18: Reversible Lane Management
ATMS19: Speed Monitoring
ATMS21: Roadway Closure Management
VEHICLE SAFETY
AVSS10: Intersection Collision Avoidance
COMMERCIAL VEHICLE OPERATIONS
CVO06: Weigh-In-Motion
EMERGENCY MANAGEMENT
EM04: Roadway Service Patrols
EM05: Transportation Infrastructure Protection
EM06: Wide-Area Alert
EM09: Evacuation and Reentry Management
EM10: Disaster Traveler Information
MAINTENANCE AND CONSTRUCTION MANAGEMENT
MC01: Maintenance and Construction Vehicle and Equipment Tracking
MC02: Maintenance and Construction Vehicle Maintenance
MC03: Road Weather Data Collection
MC04: Weather Information Processing and Distribution
MC05: Roadway Automated Treatment
MC06: Winter Maintenance
MC07: Roadway Maintenance and Construction
MC08: Work Zone Management
MC10: Maintenance and Construction Activity Coordination
9.0 SYSTEM OVERVIEW
The final system will be used by one (1) to 12 people at each District, 365 days per year, 24/7.
Users shall be capable of simultaneously accessing any element of the system that they have
the privilege to access. Some critical elements of this design will include:
•
Detailed system documentation, including a user interface design, database design;
Appendix O – Page 7 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
•
•
•
•
•
•
•
•
•
•
A modular design, based on well defined and open interfaces;
Modules can be installed, removed, activated or deactivated without affecting other
running modules;
The interface between modules shall be well defined and open;
Web Based Operator Interface;
Scalable, expandable design;
Utilize Windows or Linux based hardware;
Adhere to the latest industry standards;
Follow the SIE CMMI model;
Follow the regulations set forth in the Right-to-Know Law Policy effective January 1,
2009; and
Adhere to the rules established by the Information Technology Bulletin (ITB).
10.0 OPERATIONAL ENVIRONMENT
The operational environment of the new system will consist of a central database located at the
Pennsylvania Department of Transportation (PennDOT) Central Office in Harrisburg. The
system will improve statewide coordination by providing a statewide platform to enable the
information flow to and from all Districts. Additionally, a centralized database will improve data
consistency and provide statewide reporting capabilities.
11.0 SUPPORT ENVIRONMENT
It is anticipated that each District will have a technical resource personnel who will receive basic
troubleshooting training on database and computer networks. This will be supplemented by
staff at the Central Office and the selected ATMS integrator, who will assume the primary
support role. Continued maintenance and support is to be provided by the software
development company that designs the statewide ATMS software.
Appendix O – Page 8 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
12.0 OPERATIONAL SCENARIOS
The following 52 operational scenarios were developed to provide some specific userperspectives to the market packages and corresponding operational needs. The scenarios
were developed using standard software engineering use-case templates.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Scenario 1: Administration – Creating and Defining User Groups
Scenario 2: Administration – Adding New Users
Scenario 3: Administration – Editing Users
Scenario 4: Administration – Disabling Users
Scenario 5: Administration – Adding Field Devices
Scenario 6: Administration – Updating Device Information
Scenario 7: Administration – Creating Camera Presets
Scenario 8: Administration – Response Plan Creation
Scenario 9: Administration – Diversion Route Creation
Scenario 10: Administration – TMC Handoff
Scenario 11: Normal Operations
Scenario 12: CCTV Control
Scenario 13: Sharing CCTV within a TMC
Scenario 14: CCTV Control Handoff to another TMC (Removed)
Scenario 15: DMS Message Creation
Scenario 16: DMS Activation
Scenario 17: DMS Handoff to another TMC (Removed)
Scenario 18: DMS sharing within a TMC
Scenario 19: Travel Time – Preset Message Activation
Scenario 20: HAR Message Creation
Scenario 21: HAR Activation
Scenario 22: HAR Handoff to another TMC (Removed)
Scenario 23: HAR sharing within a TMC
Scenario 24: Incident Detection
Scenario 25: Incident Management
Scenario 26: Response Plan Activation
Scenario 27: Maintenance and Construction Vehicle and Equipment Tracking /
Advanced Vehicle Location (AVL)
Scenario 28: Congestion Management (Signal Timing)
Scenario 29: Traffic Report Generation
Scenario 30: Equipment Status Report
Scenario 31: Equipment Failure Alerts
Scenario 32: Performance Reports
Scenario 33: CCTV Blocking
Scenario 34: Locking CCTV Control
Scenario 35: Travel Time – Custom Message Activation
Scenario 36: HAR Beacon Activation
Scenario 37: Service Patrol Vehicle Tracking / Advanced Vehicle Location (AVL)
Scenario 38: Administrative - Ramp Metering Configuration
Appendix O – Page 9 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Scenario 39: HOV Lane Management
Scenario 40: Lane Control Signals
Scenario 41: Variable Speed Limits (Removed)
Scenario 42: Call Log
Scenario 43: Administration – Contact List
Scenario 44: Diversion Route Activation
Scenario 45: Application-Level Operational Vendor Support
Scenario 46: Generation of Preventive Maintenance Schedule for ITS Equipment
Scenario 47: Remote Viewing of Current Equipment Status, Traveler Information
Messages, and Incident Information
Scenario 48: Ramp Metering
Scenario 49: Variable Speed Limit Control (Removed)
Scenario 50: Proactive Stakeholder Notification
Scenario 51: Equipment Diagnostics
Scenario 52: Roadway Weather Information System
Appendix O – Page 10 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 1
Scenario Name:
Administration – Creating and Defining User Groups
Description:
The TMC Administrator has the ability to create user groups
and assign privileges to each user group.
Preconditions:
Normal Course:
•
1.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
A TMC Administrator is logged into the ATMS.
The TMC Administrator creates and defines a new user
group in the ATMS software.
The TMC Administrator goes to the Administrative
section of the ATMS software.
The TMC Administrator selects User Groups.
The “User Group” screen appears. This screen lists the
current user groups and the privileges assigned to each
group. For example, operators can create and edit
incidents, but managers may only be able to view
information.
The TMC Administrator clicks on the Add New button.
The TMC Administrator enters a new user group name.
For each of the major sections of the ATMS software,
the TMC Administrator assigns create, read, edit or
delete privileges to the new user group.
The TMC Administrator clicks on the save button.
The TMC Administrator must confirm the change.
The new user group should appear in the list.
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Initial Deployment
Appendix O – Page 11 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 2
Scenario Name:
Administration – Adding New Users
Description:
The TMC Administrator has the ability to add new users to the
ATMS software.
Preconditions:
Normal Course:
•
2.0:
a.
b.
c.
d.
e.
f.
g.
h.
A TMC Administrator is logged into the ATMS.
The TMC Administrator adds a new user to the ATMS
software.
The TMC Administrator goes to the Administrative
section of the ATMS software.
The TMC Administrator selects the Users.
The “User” screen appears. This screen should display
a list of current users and their user level.
The TMC Administrator clicks on the Add New button.
The TMC Administrator enters the requested data.
The TMC Administrator assigns the new user to a user
group.
The TMC Administrator clicks on the save button.
The TMC Administrator must confirm the change.
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Initial Deployment
Appendix O – Page 12 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 3
Scenario Name:
Administration – Editing Users
Description:
The TMC Administrator has the ability to edit information (e.g.
user name changes, user privileges, etc.) in the ATMS
software.
Preconditions:
•
A TMC Administrator is logged into the ATMS.
Normal Course:
3.0: The TMC Administrator assigns a user to a user group
a. The TMC Administrator goes to the Administrative
section of the ATMS software.
b. The TMC Administrator selects the User section.
c. The “User” screen appears. This screen should
display a list of current users and their user level.
d. The TMC Administrator selects a user.
e. The TMC Administrator selects the update button.
f. The TMC Administrator edits the information about the
selected user, such as name, contact information and
user group.
g. The TMC Administrator clicks on the save button.
h. The TMC Administrator must confirm the change.
Alternative Course:
3.1:
The TMC Administrator edits the user information for
multiple users (branch at step f).
a. The TMC Administrator selects another user to update.
b. Return to step e.
3.2:
The TMC Administrator edits the user privileges of
multiple users simultaneously (branch at step c). Note:
All selected users are being assigned to the same user
group.
a. The TMC Administrator selects multiple users.
b. Return to step e.
Includes:
Market Packages:
Project Phase:
Initial Deployment
Appendix O – Page 13 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 4
Scenario Name:
Administration – Disabling Users
Description:
The TMC Administrator has the ability to disable users from
accessing the ATMS software.
Preconditions:
Normal Course:
•
4.0:
a.
b.
c.
d.
e.
f.
A TMC Administrator is logged into the ATMS.
The TMC Administrator disables a user’s access to the
ATMS software.
The TMC Administrator goes to the Administrative
section of the ATMS software.
The TMC Administrator selects the User section.
The “User” screen appears. This screen should
display a list of current users and their user level.
The TMC Administrator checks the disable box next to
the Operators name.
The TMC Administrator clicks on the save button.
The TMC Administrator must confirm the change.
Alternative Course:
Includes:
Market Packages:
Project Phase:
Initial Deployment
Appendix O – Page 14 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 5
Scenario Name:
Administration – Adding Field Devices
Description:
A user with sufficient privileges adds new equipment to the
ATMS software.
Preconditions:
•
•
Normal Course:
5.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
Alternative Course:
5.1:
a.
b.
c.
d.
A TMC user with sufficient privileges is logged into the
ATMS software.
The new ATMS devices are installed in the field.
A TMC user with sufficient privileges adds a new field
device to the ATMS software and the ATMS Map.
A TMC user with sufficient privileges opens the
equipment section of the ATMS software.
A TMC user with sufficient privileges selects a device
category (CCTV, DMS, HAR, etc.).
A TMC user with sufficient privileges selects a device
type and / or manufacturer.
A TMC user with sufficient privileges enters requested
device information, such as model and serial numbers.
A TMC user with sufficient privileges enters the latitude
and longitude of the device location.
A TMC user with sufficient privileges clicks on the save
button.
A TMC user with sufficient privileges confirms that the
new device should be saved.
A TMC user with sufficient privileges will be asked if the
data should be sent to the map at this time.
A TMC user with sufficient privileges must confirm that
the device should be added to the map. Otherwise, a
TMC user with sufficient privileges can add the device
to the map later.
The device should be displayed on the map. Active and
inactive devices will appear in different colors.
A user with sufficient privileges adds a field device to
the ATMS Map at a later time (alternative at step h).
A TMC user with sufficient privileges enters the latitude
and longitude of the device location, if it was not
previously entered.
A TMC user with sufficient privileges clicks on the Map
button.
A TMC user with sufficient privileges must confirm that
the device should be added to the map. Otherwise, a
TMC user with sufficient privileges can add the device
to the map later.
A TMC user with sufficient privileges clicks on the save
Appendix O – Page 15 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
button.
e. A TMC user with sufficient privileges must confirm the
change.
Includes:
Market Package(s):
ATMS01: Network Surveillance
ATMS07: Regional Traffic Management
Project Phase:
Initial Deployment
Appendix O – Page 16 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 6
Scenario Name:
Administration – Updating Device Information
Description:
Users with administrative security clearance changes
identification and characteristic information regarding any
device. This includes, but is not limited to, device location,
serial number, brand, make, and type of device.
Preconditions:
•
•
Normal Course:
6.0:
a.
b.
c.
d.
e.
f.
g.
The TMC Administrator is logged into the ATMS
software.
The ATMS devices are reporting status information
back to the TMC.
The TMC Administrator changes identification and
characteristic information regarding a device.
The TMC Administrator opens the equipment section
of the ATMS software.
The TMC Administrator selects a device.
The TMC Administrator views the current settings.
The TMC Administrator clicks on the edit button.
The TMC Administrator changes the device
information.
The TMC Administrator clicks on the save button.
The TMC Administrator confirms that the changes
should be saved.
Alternative Course:
Includes:
Market Package(s):
ATMS01: Network Surveillance
ATMS07: Regional Traffic Management
Project Phase:
Initial Deployment
Appendix O – Page 17 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 7
Scenario Name:
Administration – Creating Camera Presets
Description:
From the Administrative screens, the TMC Manager can save
camera presets for each PTZ camera, such that the camera
image displays a location description whenever the camera is
commanded to a preset view.
Preconditions:
•
•
The TMC Manager is logged into the ATMS software.
The CCTV are functioning properly.
Normal Course:
7.0:
a.
b.
c.
Alternative Course:
7.1: Creating Multiple Presets for one camera (at step g).
a. The TMC Manager wants to create more presets for
the selected CCTV.
b. Return to step d.
Creating Camera Presets.
The TMC Manager selects a CCTV camera
The TMC Manager opens the Administrative screen
The TMC Manager goes to the camera preset entry
section.
d. The TMC Manager enters the camera preset
parameters.
e. The TMC Manager types in a location description.
f. The TMC Manager saves the preset settings.
g. The TMC Manager confirms that the preset settings
should be saved.
7.2: Creating Presets for a different camera (at step g).
a. The TMC Manager wants to create presets for a
different camera.
b. Return to step b.
c. Select another CCTV from the CCTV list menu.
Includes:
Market Package(s):
ATMS01: Network Surveillance
Project Phase:
Initial Deployment
Appendix O – Page 18 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 8
Scenario Name:
Administration – Response Plan Creation
Description:
The TMC Administrator creates a response plan that can be
implemented during the management of an incident, a special
event, or traffic congestion conditions. Plans can be developed
based on a location, severity, and upstream distance or they can
be configured by the TMC Administrator.
Preconditions:
Normal Course:
•
8.0:
a.
b.
c.
d.
e.
f.
g.
h.
Alternative Course:
8.1:
a.
b.
c.
d.
e.
8.2:
a.
b.
c.
d.
The TMC Administrator is logged into the ATMS software.
The TMC Administrator selects devices to be activated
as part of the response plan that are based on a
location, severity, and upstream distance.
The TMC Administrator opens the response plan section.
The TMC Administrator selects a link.
The TMC Administrator selects the response plan
upstream distance (i.e. 1, 2, 5, or 10 miles from location).
The devices (DMS and HAR) within the selected range will
be automatically selected.
The TMC Administrator can select additional devices or
remove devices from the list of devices that are to be
activated as part of a response plan when an incident, a
special event, or congested conditions occurs at a
particular location.
The TMC Administrator can select a contact list.
The TMC Administrator can configure diversion routes.
The TMC Administrator saves the response plan into the
response plan library.
The TMC Administrator manually selects devices to be
activated as part of a response plan (alternative at step
a.)
The TMC Administrator selects a link from the ATMS Map.
The TMC Administrator selects Response Plan.
The Response Plan screen appears.
The TMC Administrator can select equipment to be added
to the response plan.
Return to step f.
The TMC Administrator edits a response plan (alternate
at step b).
The TMC Administrator selects a response plan from the
response plan library.
The TMC Administrator adds or removes devices from the
response plan.
The TMC Administrator updates informational messages.
The TMC Administrator saves the updated response plan
Appendix O – Page 19 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
to the library.
Includes:
Market Package(s):
ATMS09: Traffic Decision Support and Demand Management
Project Phase:
Initial Deployment
Appendix O – Page 20 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 9
Scenario Name:
Administration – Diversion Route Creation
Description:
The TMC Administrator creates diversion routes in RCRS that
can be implemented during the management of an incident, a
special event, or congestion conditions.
Preconditions:
Normal Course:
•
9.0:
a.
b.
c.
d.
The TMC Administrator enters a diversion route in
RCRS.
The TMC Administrator creates diversion routes in
RCRS
.
The diversion route created in RCRS is displayed on
the ATMS map.
The list of nearby links should display roadway
information from APRAS. This information would
include roadways limitations, such as capacity (weight
and height restrictions).
Any changes to the diversion route made in RCRS will
be displayed in ATMS.
The diversion route will be removed from ATMS
immediately after the diversion route is removed from
RCRS.
Alternative Course:
a.
Includes:
Market Package(s):
ATMS09: Traffic Decision Support and Demand Management
Project Phase:
Initial Deployment
Appendix O – Page 21 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 10
Scenario Name:
Administration – TMC Handoff
Description:
In some cases it is necessary to transfer control of an entire
District over to another District. For example, some TMCs do not
run 24/7, so transfer of control occurs on a nightly basis. Also,
during an evacuation, a TMC may be closed down; therefore,
control of all of the equipment and incidents owned by that
District may be temporarily transferred to another District.
Additionally, control of individual devices (i.e. DMS and, CCTV)
can be transferred to other Districts.
Preconditions:
•
•
•
The TMC Operator in the primary control District is logged
into the ATMS software.
The TMC Operator in the requesting District is logged into
the ATMS software.
The field equipment is fully functional.
Normal Course:
10.0:
TMC or Equipment Handoff.
a. The requesting TMC Operator views the ATMS map.
b. The requesting TMC Operator selects the TMC or
equipment that he/she wants to take control of.
c. The requesting TMC Operator right-clicks on the TMC or
equipment icon and selects “Request Control.”
d. An instant messaging box will appear on the requesting
TMC Operator’s computer.
e. The requesting TMC Operator enters the reason for the
request.
f. The ATMS software notifies the controlling TMC via an
instant message.
g. The controlling TMC Operator views the notification.
h. The controlling TMC Operator determines if control should
be given to the requesting district.
i. The controlling TMC Operator clicks on the “Release
Control” button that is on the request notification pop-up.
j. Via an instant message, the requesting TMC Operator
receives audio and visual notification that a response was
received.
k. The controlling TMC Operator can take control over the
requested TMC or equipment.
Alternative Course:
10.1:
A TMC Administrator requests control of another TMC
that is unavailable to respond to the request, but put the
software in approval mode (branch at step g.).
a. Since no one is available at the controlling TMC, but the
ATMS software was set to approval mode, the software
will automatically notify the requesting TMC that control is
Appendix O – Page 22 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
handed over.
10.2:
a.
b.
c.
d.
A TMC Administrator requests control of another TMC
that is unavailable to respond to the request, but did not
put the software in approval mode (branch at step
10.1.g.).
Since no one is available at the controlling TMC, the
requesting TMC does not receive a response from the
controlling TMC.
After a brief period of time, the requesting TMC
Administrator will be prompted to verify that control should
be transferred.
The TMC Administrator selects take control without
authorization.
The requesting TMC will gain control over the requested
TMC or equipment.
Includes:
Market Package(s):
ATMS01: Network Surveillance
ATMS06: Traffic Information Dissemination
ATMS07: Regional Traffic Management
Project Phase:
Initial Deployment
Appendix O – Page 23 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 11
Scenario Name:
Normal Operations
Description:
The TMC is in normal daily status. This is the status when no
traffic events are active.
Preconditions:
•
•
•
•
Normal Course:
The TMC Operator is logged into the ATMS.
No planned events and/or unexpected incidents are
occurring in the TMC monitored region.
No Amber Alerts are active.
Field equipment is accurately returning data to the
ATMS.
11.0: The TMC Operator logs into the ATMS software.
a. The TMC Operator opens the ATMS map, which
displays roadway and equipment status for the entire
Commonwealth
b. The TMC Operator zooms into his District.
c. The TMC Operator turns on equipment layers to view
the status of equipment. Active and inactive equipment
will be displayed in different colors.
d. The TMC Operator can also view equipment status as a
list that appears on the ATMS map.
e. The TMC Operator can right-click on equipment to open
a trouble ticket, if necessary.
f. The TMC Operator checks the detectors along the
monitored corridors for the speed, volume and
occupancy data.
g. The TMC Operator uses the CCTV controls to survey
the monitored corridors.
h. The TMC Operator checks the status of the DMS.
Mousing over the DMS displays a tool-tip with the DMS
message that is currently displayed on the DMS.
Alternative Course:
Includes:
Scenario 46: Generation of Preventive Maintenance Schedule
for ITS Equipment
Scenario 47: Remote Viewing of Current Equipment Status,
Traveler Information Messages, and Incident Information
Market Package(s):
Project Phase:
Initial Deployment
Appendix O – Page 24 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 12
Scenario Name:
CCTV Control
Description:
From the ATMS software, the TMC Operator can access and
view available CCTV cameras. The TMC Operator can also
control the PTZ functionality from the workstation.
Preconditions:
•
The TMC Operator is logged into the ATMS software.
Normal Course:
12.0: Using PTZ CCTV Control.
a. The TMC Operator views the ATMS Map.
b. The TMC Operator, mouses over the CCTV to check the
camera status.
c. The TMC Operator right-clicks on an available CCTV to
view the camera image.
d. A CCTV pop-up window with the live camera view is
displayed.
e. Using the PTZ controls on the CCTV pop-up window, the
TMC Operator can zoom and rotate the camera to view
the monitored roadway.
Alternative Course:
12.1: Joystick Control (branch at step a).
a. The TMC Operator uses buttons on a joystick to enter the
camera number of the CCTV to be viewed.
b. Once the CCTV number is entered, the live video is
displayed on the video wall.
c. The TMC Operator uses the joystick to zoom, rotate and
focus the CCTV.
12.2: Activating Preset Views (branch at step c).
a. The TMC Operator right-clicks on a CCTV to select a
preset camera view.
b. The TMC Operator selects the name of the preset view to
be activated.
c. The TMC Operator confirms that the preset view should
be displayed.
d. A CCTV pop-up window with the live camera view is
displayed.
e. When the live video is displayed, the CCTV should be
positioned according to the selected preset parameters.
f. Using the PTZ controls on the CCTV pop-up window, the
TMC Operator can zoom and rotate the camera to change
the view of the monitored roadway.
Includes:
Market Package(s):
ATMS01: Network Surveillance
Project Phase:
Initial Deployment
Appendix O – Page 25 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 13
Scenario Name:
Sharing CCTV within a TMC
Description:
The TMC Operator shares control with another TMC Operator
within the same TMC.
Preconditions:
Normal Course:
•
13.0:
a.
b.
c.
d.
e.
f.
The TMC Operators are logged into the ATMS.
While one TMC Operator is controlling a CCTV, another
TMC Operator working within the same TMC wants to
gain control of the camera.
The TMC Operator views the ATMS Map.
The TMC Operator, mouses over the CCTV to check the
status.
The TMC Operator right-clicks on the device.
A CCTV pop-up window with the live camera view is
displayed.
When the TMC Operator tries to control the camera, he is
alerted that another TMC Operator is using the camera. If
the user has lower user privileges, then the TMC operator
has the option to take control away from the current user.
If both users have the same user privileges then the TMC
Operator who began using the camera first will have
priority.
Using the PTZ controls on the CCTV pop-up window, the
TMC Operator can zoom and rotate the camera to view
the monitored roadway.
Alternative Course:
Includes:
Market Package(s):
ATMS01: Network Surveillance
Project Phase:
Initial Deployment
Appendix O – Page 26 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 14
Scenario Name:
Description:
Preconditions:
Normal Course:
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Scenario 14 (CCTV Control Handoff to Another TMC) from Rev. 1 was removed.
This page was intentionally left blank. While the Scenario has been removed, the Scenario ID
was left as a placeholder.
Appendix O – Page 27 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 15
Scenario Name:
DMS Message Creation
Description:
A DMS Message is created and stored in the message library.
Preconditions:
Normal Course:
•
15.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
Alternative Course:
The TMC Operator is logged into the ATMS software.
A DMS Message is created and stored in the Message
Library.
The TMC Operator opens the DMS subsystem.
The TMC Operator opens the Message Library.
The TMC Operator selects a sign type (portable,
intermediate, full-sized) and manufacturer.
The TMC Operator types in the DMS message text.
The TMC Operator runs a spell check that also checks for
approved abbreviations.
The TMC Operator assigns a priority level to the
message.
The TMC Operator clicks on the Save button.
The TMC Operator selects a folder within the message
library.
The TMC Operator enters a message title.
The TMC Operator confirms that the message should be
saved.
15.1:
A DMS message is created for display on a DMS
(alternative at step a).
a. See Scenario 16 – DMS Message Activation.
15.2:
The created DMS Message doesn’t meet one or more of
the following constraints.
• Allowable set of characters.
• Number of lines of text.
• Number of characters per line.
• Contains a word that is in the forbidden word list
a. The ATMS software identifies the errors.
b. The TMC Operator corrects the identified errors.
c. Return to step g.
15.3: An existing DMS message is edited (branch at step b).
a. The TMC Operator selects a message category from the
DMS Library.
b. The TMC Operator selects a message from the selected
category in the DMS Library.
c. The TMC Operator clicks on the edit button.
d. The TMC Operator revises the DMS Message.
e. Return to step d.
Appendix O – Page 28 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
15.4:
An existing DMS message is edited and saved for a
different sign type (alternative).
a. The TMC Operator selects a DMS.
b. The TMC Operator opens the message library.
c. The TMC Operator selects a message category from the
DMS Library.
d. The TMC Operator selects a message from the selected
category in the DMS Library.
e. The TMC Operator clicks on the edit button.
f. The TMC Operator receives notification that the message
does not meet one or all of the following criteria:
• Allowable set of characters.
• Number of lines of text.
• Number of characters per line.
• Contains a word that is in the forbidden word list
g. The TMC Operator revises the DMS Message and/or
changes fonts to make the message compatible with the
selected sign.
Return to step e.
Includes:
Market Package(s):
ATMS06: Traffic Information Dissemination
Project Phase:
Initial Deployment
Appendix O – Page 29 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 16
Scenario Name:
DMS Activation
Description:
A DMS message is activated on a DMS.
Preconditions:
•
•
•
The TMC Operator is logged into the ATMS software.
The DMS are communicating with the ATMS software.
The DMS are fully functional.
Normal Course:
16.0:
a.
b.
c.
d.
e.
Alternative Course:
16.1: A DMS message is created for display on a DMS (alternative
at step a).
a. The TMC Operator right-clicks on a DMS icon from the ATMS
Map.
b. The TMC Operator selects create message.
c. The DMS message entry screen appears.
d. The TMC Operator types in a message.
e. The TMC Operator can save the message to the message
library.
f. Return to step e.
A DMS Message is activated from the Message Library.
The TMC Operator opens the DMS subsystem.
The TMC Operator opens the Message Library.
The TMC Operator selects a message.
The TMC Operator selects a DMS.
The ATMS alerts the TMC Operator if the selected message
will not be properly displayed on a selected DMS. The TMC
Operator can then edit the selected message.
f. The TMC Operator clicks on the Activate button.
g. The TMC Operator confirms that the message should be sent
to the DMS.
h. The ATMS shall send the message to the sign. If a
communication failure occurs, the ATMS will attempt to send
the message for the number of times that have been
configured by an Administrative user.
i. The ATMS software will notify the operator of the transmission
status (i.e. successfully activated or activation failure).
16.2: Using the ATMS Map, a DMS message is activated
(alternative at step a).
a. The TMC Operator right-clicks on a DMS icon from the ATMS
Map.
b. The TMC Operator selects activate message.
c. The DMS message library appears.
d. The TMC Operator selects a message. (If the TMC Operator
is activating a high priority message it will overwrite the low
priority message. Once the high priority message expires, the
Appendix O – Page 30 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
low priority message will be reactivated.)
e. Return to step e.
16.3: A message is sent to multiple signs simultaneously (branch at
step d).
a. The TMC Operator selects multiple DMS.
b. Return to step e.
16.4: A message is sent a DMS using a message schedule
(alternative at step b.).
a. The TMC Operator selects message scheduling.
b. The TMC Operator selects a DMS.
c. The TMC Operator selects a message from the Message
Library.
d. The TMC Operator enters the time and day that the message
should be sent to the DMS.
e. The TMC Operator verifies the messages priority.
f. The TMC Operator enters the message duration.
g. The TMC Operator clicks on the Activate button.
h. When the schedule is triggered the TMC Operator must
confirm that the scheduled DMS message should be
activated.
i. Return to step g.
Includes:
Market Package(s):
ATMS06: Traffic Information Dissemination
Project Phase:
Initial Deployment
Appendix O – Page 31 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 17
Scenario Name:
Description:
Preconditions:
Normal Course:
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Scenario 17 (DMS Handoff to another TMC) from Rev. 1 was removed.
This page was intentionally left blank. While the Scenario has been removed, the Scenario ID
was left as a placeholder.
Appendix O – Page 32 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 18
Scenario Name:
DMS sharing within a TMC
Description:
Control of a DMS within a TMC is based on user levels as well as
message priority. For example, if an Administrator activates a
high priority message, a TMC Operator cannot overwrite that
message without the Administrator’s approval.
Preconditions:
Normal Course:
•
•
•
The DMS are fully functional.
The DMS are communicating with the ATMS software.
Multiple TMC Operators within one District are logged into
the ATMS software.
18.0:
Using the ATMS Map, a TMC Operator tries to activate a
message on a DMS that is running a high priority
message.
The TMC Operator right-clicks on a DMS icon from the
ATMS Map.
The TMC Operator selects activate message.
The DMS message library appears.
The TMC Operator selects a message from the message
library.
The TMC Operator will receive an alert notifying the TMC
Operator that a high priority message is currently
activated.
If the TMC Operator wants to cancel the action, he should
click on the Cancel button.
If the TMC Operator wants to continue to send the
message, he should click on the continue button.
The software will require administrative approval to
proceed any further.
The TMC Administrator approves the message.
The message is sent to the DMS.
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
Alternative Course:
18.1:
a.
b.
c.
d.
e.
18.2:
Using the DMS portion of the software, a TMC Operator
tries to activate a message on a DMS that is running a
high priority message (branch at step a).
The TMC Operator opens the DMS portion of the ATMS
software.
The TMC Operator selects a DMS.
The TMC Operator selects an available message.
The TMC Operator selects activate.
Return to step e.
Using the ATMS Map, a TMC Operator tries to activate a
higher priority message on a DMS that is running a lower
priority message (branch at step e).
Appendix O – Page 33 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
a. The TMC Operator confirms the activation.
b. Return to step j.
18.3:
a.
b.
c.
d.
e.
f.
Using the DMS portion of the software, a TMC Operator
tries to activate a higher priority message on a DMS that
is running a lower priority message (branch at step a).
The TMC Operator opens the DMS portion of the ATMS
software.
The TMC Operator selects a DMS.
The TMC Operator selects an available message.
The TMC Operator selects activate.
The TMC Operator confirms the activation.
Return to step j.
Includes:
Market Package(s):
Project Phase:
Initial Deployment
Appendix O – Page 34 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 19
Scenario Name:
Travel Time – Preset Message Activation
Description:
A TMC Operator activates a travel time message on a DMS.
Preconditions:
•
•
•
•
Normal Course:
The DMS are fully functional.
The DMS are communicating with the ATMS software.
Travel time information is being transmitted to the ATMS
software.
Travel time links have been configured in the ATMS
software.
19.0: A TMC Operator activates a travel time message.
a. The TMC Operator opens the Travel Time subsystem.
b. The ATMS Travel Time subsystem, which when opened
should display all travel time DMS, links and generated
times
c. The TMC Operator selects a DMS.
d. The TMC operator selects a preset travel time message
library.
e. Since PennDOT collects travel time data from multiple
sources, the data from each source should be compared
and a level of confidence should be assigned to each
source. The TMC Operator can select between several
travel time calculation methods (weighted average, highest
confidence level) to be used for travel time postings
f. The TMC Operator clicks on view message.
g. The ATMS software displays the message(s) that will be
sent to the sign(s).
h. Whenever travel time messages are displayed, a %
confidence will be displayed on the map as well. This
value will indicate the percentage of supporting field
equipment that is functioning correctly.
i. If necessary, the TMC Operator can edit the message.
j. The TMC Operator clicks on the Activate button.
k. The travel time message(s) is activated on the selected
DMS.
Alternative Course:
Includes:
Scenario 30: Equipment Status Report
Market Packages:
ATMS06: Traffic Information Dissemination
Project Phase:
Initial Deployment
Appendix O – Page 35 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 20
Scenario Name:
HAR Message Creation
Description:
An HAR Message is created and stored in the message library.
Preconditions:
Normal Course:
•
20.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
Alternative Course:
The TMC Operator is logged into the ATMS software.
An HAR Message is created and stored in the Message
Library.
The TMC Operator opens the HAR subsystem.
The TMC Operator opens the HAR Message Library.
The TMC Operator types in the HAR message text.
The TMC Operator assigns a priority level to the
message.
The TMC Operator records the HAR message.
The TMC Operator clicks on the listen to message
button.
The TMC Operator clicks on the Save button.
The TMC Operator enters a message title.
The TMC Operator confirms that the message should
be saved.
20.1:
A HAR message is created for playing on an HAR
(alternative at step a).
a. See Scenario 19 – Message Activation.
20.2:
The created HAR Message doesn’t meet one or more of
the following constraints (at step e).
Contains a word that is in the forbidden word list
a. Return to step c.
20.3: An existing HAR message is edited (branch at step b).
a. The TMC Operator selects a message from the HAR
Library.
b. The TMC Operator clicks on the edit button.
c. The TMC Operator revises the HAR Message.
d. Return to step e.
Includes:
Market Package(s):
ATMS06: Traffic Information Dissemination
Project Phase:
Initial Deployment
Appendix O – Page 36 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 21
Scenario Name:
HAR Activation
Description:
An HAR message is activated on an HAR.
Preconditions:
Normal Course:
•
•
•
21.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
Alternative Course:
21.1:
a.
b.
c.
d.
e.
21.2:
a.
b.
c.
d.
e.
The TMC Operator is logged into the ATMS software.
The HAR are communicating with the ATMS software.
The HAR are fully functional.
An HAR Message is activated from the Message
Library.
The TMC Operator opens the HAR subsystem.
The TMC Operator opens the Message Library.
The TMC Operator selects a message.
The TMC Operator clicks on the listen to message
button.
The TMC Operator selects an HAR.
The ATMS software provides the HAR status including
transmitter status and wattage.
The TMC Operator clicks on the Activate button.
The TMC Operator confirms that the message should be
sent to the HAR.
The ATMS software will notify the operator of the
transmission status (i.e. successfully activated or
activation failure).
The TMC Operator selects the HAR.
The TMC Operator selects listen to current play list.
The TMC Operator verifies that the selected message
was sent to the HAR.
An HAR message is created for display on an HAR
(alternative at step a).
The TMC Operator right-clicks on an HAR icon from the
ATMS Map.
The TMC Operator selects create message.
The HAR message entry screen appears.
The TMC Operator types in a message.
Return to step e.
Using the ATMS Map, an HAR message is activated
(alternative at step a).
The TMC Operator right-clicks on an HAR icon from the
ATMS Map.
The TMC Operator selects activate message.
The HAR message library appears.
The TMC Operator selects a message.
Return to step e.
Appendix O – Page 37 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
21.3:
A message is sent to multiple HAR simultaneously (at
step d).
a. The TMC Operator selects multiple HAR.
b. Return to step e.
Includes:
Market Package(s):
ATMS06: Traffic Information Dissemination
Project Phase:
Initial Deployment
Appendix O – Page 38 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 22
Scenario Name:
Description:
Preconditions:
Normal Course:
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Scenario 22 (HAR Handoff to another TMC) from Rev. 1 was removed.
This page was intentionally left blank. While the Scenario has been removed, the Scenario ID
was left as a placeholder.
Appendix O – Page 39 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 23
Scenario Name:
HAR sharing within a TMC
Description:
Control of an HAR within a TMC is based on user levels as well
as message priority. For example, if an Administrator activates
a high priority message, a TMC Operator cannot overwrite that
message without the Administrator’s approval.
Preconditions:
Normal Course:
•
•
•
23.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
Alternative Course:
23.1:
a.
b.
c.
d.
e.
23.2:
The HAR are fully functional.
The HAR are communicating with the ATMS software.
Multiple TMC Operators within one district are logged
into the ATMS software.
Using the ATMS Map, a TMC Operator tries to activate a
message on an HAR that is running a high priority
message.
The TMC Operator right-clicks on an HAR icon from the
ATMS Map.
The TMC Operator selects activate message.
The HAR message library appears.
The TMC Operator selects a message from the
message library.
The TMC Operator will receive an alert notifying the
TMC Operator that a high priority message is currently
activated.
If the TMC Operator wants to cancel the action, he
should click on the Cancel button.
If the TMC Operator wants to continue to send the
message, he should click on the continue button.
The software will require administrative approval to
proceed any further.
The TMC Operator must confirm that the message
should be sent.
The message is sent to the HAR.
Using the HAR portion of the software, a TMC Operator
tries to activate a message on an HAR that is running a
high priority message (branch at step a).
The TMC Operator opens the HAR portion of the ATMS
software.
The TMC Operator selects an HAR.
The TMC Operator selects an available message.
The TMC Operator selects activate.
Return to step e.
Using the ATMS Map, a TMC Operator tries to activate a
higher priority message on an HAR that is running a
Appendix O – Page 40 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
lower priority message (branch at step e).
a. The TMC Operator confirms the activation.
b. Return to step j.
23.3:
a.
b.
c.
d.
e.
f.
Using the HAR portion of the software, a TMC Operator
tries to activate a higher priority message on an HAR
that is running a lower priority message (branch at step
a).
The TMC Operator opens the HAR portion of the ATMS
software.
The TMC Operator selects an HAR.
The TMC Operator selects an available message.
The TMC Operator selects activate.
The TMC Operator confirms the activation.
Return to step j.
Includes:
Market Package(s):
ATMS06: Traffic Information Dissemination
Project Phase:
Initial Deployment
Appendix O – Page 41 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 24
Scenario Name:
Incident Detection
Description:
The ATMS software shall process data in real-time, providing
roadway congestion information for the data algorithm to evaluate
vehicle detector data and determine the presence of an incident;
the ATMS should detect and alert the TMC Operator of a
potential incident. The incident management will be linked to the
INRIX System.
Preconditions:
Normal Course:
•
•
24.0:
a.
b.
c.
d.
e.
f.
g.
Alternative Course:
The TMC Operator is logged into the ATMS software.
The ATMS software is receiving detector data.
The ATMS software alerts the TMC Operator of a
potential incident.
The ATMS software detects a potential incident.
The ATMS software alerts the TMC Operator of a
potential incident.
The TMC Operator checks the ATMS software map to see
the color of the links around the location of the potential
incident.
The TMC Operator checks the detector data (speed,
volume and occupancy) for the location of the potential
incident.
When a sensor is triggered by a potential incident, the
CCTV best suited to view the triggered sensor will
automatically pan to the triggered sensor and/ or the video
feed will automatically be sent to the video wall, so that
the operator can verify that an incident occurred.
The TMC Operator opens an incident report.
The TMC Operator shares the incident information with
the police.
24.1:
The TMC Operator detects an incident from the ATMS
Software Map (alternative at step a).
a. The TMC Operator views the ATMS Software Map.
b. The TMC Operator looks for links that appear red, which
indicate that traffic flow is slow.
c. Return to step d.
24.2: The TMC Operator detects an incident from the CCTV.
a. The TMC Operator scans through the current CCTV
images.
b. The TMC Operator notices a disruption in traffic.
c. The TMC Operator checks the ATMS map to see the
color of the links around the location.
d. The TMC Operator checks the detector data (speed,
Appendix O – Page 42 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
volume and occupancy) for the location of the potential
incident.
e. The TMC Operator opens and incident report.
Includes:
Market Package(s):
ATMS04: Freeway Control
Project Phase:
Initial Deployment
Appendix O – Page 43 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 25
Scenario Name:
Incident Management
Description:
The TMC Operator tracks and manages an incident.
Preconditions:
•
•
Normal Course:
The TMC Administrator is logged into the ATMS
software.
An incident has been detected and confirmed.
25.0: An incident is managed by the TMC Operator.
a. The TMC Operator uses the incident management
component of the ATMS software.
b. The TMC Operator creates a new incident report.
c. The TMC Operator clicks on a button which will load the
entered incident data from the RCRS system.
d. The TMC Operator coordinates a response with
emergency management, maintenance and construction
management and other incident response personnel.
e. If necessary, the TMC Operator either activates a
response plan or activates individual DMS to alert the
traveling public of traffic delays and/or diversionary
routes.
f. If necessary, the TMC Operator activates a diversion
route.
g. The TMC Operator periodically uses the CCTV cameras
to check the status of the event.
h. The TMC Operator updates the incident data as
necessary.
i. The TMC Operator closes the incident report when the
incident is cleared.
Alternative Course:
Includes:
Market Package(s):
ATMS08: Traffic Incident Management System
Project Phase:
Initial Deployment
Appendix O – Page 44 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 26
Scenario Name:
Response Plan Activation
Description:
An incident is detected and the TMC Operator activates a
response plan.
Preconditions:
•
•
•
Normal Course:
26.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
Alternative Course:
The TMC Operator is logged into the ATMS software.
The TMC Administrator created and saved response
plans into the response plan library.
The equipment is functioning correctly.
An incident is detected and the TMC Operator activates a
response plan.
The TMC Operator receives a notification from the Road
Condition Reporting System to modify a road status.
The TMC Operator opens an incident report
The TMC Operator opens the response plan section.
The TMC Operator selects a response plan to be
activated.
The TMC Operator follows the response plan messages.
The TMC Operator activates suggested messages on the
recommended DMS and HAR.
When prompted, the TMC Operator confirms that the
messages should be activated.
The TMC Operator accesses data from the Emergency
Detour Routing System (EDRS).
The TMC Operator updates devices as recommended by
the response plan.
The TMC Operator continues to track the incident.
The TMC Operator cancels the response plan.
The TMC Operator closes the incident.
26.1:
The TMC Operator removes devices from the response
plan (branch at step e).
a. When the TMC Operator views the devices to be
activated as part of the response plan, he chooses not to
activate one or several devices that are part of the plan.
b. Return to step g.
26.2:
The TMC Operator searches text from the response plan
library (at step d).
a. The TMC Operator searches the response plan library for
key text.
b. Return to step d.
26.3:
The TMC Operator cancels the response plan (after step
g).
Appendix O – Page 45 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
a. From the Response Plan section, the TMC Operator
selects cancel response plan.
b. All activated devices should return to the previous state.
c. The TMC Operator must accept any changes that are
made to the devices.
26.4:
The TMC Operator skips steps in the response plan
(branch at step e).
a. While following the response plan messages, the TMC
Operator clicks on the skip button to skip the current step.
b. The TMC Operator can skip multiple steps.
c. Return to step g.
Includes:
Market Package(s):
ATMS09: Traffic Decision Support and Demand Management
Project Phase:
Initial Deployment
Appendix O – Page 46 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 27
Scenario Name:
Maintenance and Construction Vehicle and Equipment Tracking /
Advanced Vehicle Location (AVL)
Description:
The ATMS software should track real-time data from
Maintenance and Construction vehicles. This information
includes, at a minimum, vehicle identifier, GPS coordinates, and
the time of day that the data was collected. The collected data
can be used to coordinate the dispatch construction and
maintenance vehicles with the County Maintenance Offices for
the event. Possible uses include maintenance vehicles and
emergency vehicles. The AVL system should like to the rest of
the ATMS.
Preconditions:
•
•
•
Normal Course:
27.0:
a.
b.
c.
d.
e.
The TMC Operator is logged into the ATMS software.
The Construction and Maintenance vehicles have active
AVL sensors.
RWIS are reporting data to the TMC.
During a weather related event (i.e. snow) the TMC
Operator can track and coordinate construction,
maintenance, and emergency vehicles.
The RWIS data is reaching a defined threshold (i.e.
pavement temperature approaching 32ºF) and alerts the
TMC Operator.
The TMC Operator opens Construction and Maintenance
section of the ATMS.
The TMC Operator searches the location of construction /
maintenance vehicles.
The TMC Operator can use this information to coordinate
the dispatch Construction and Maintenance vehicles with
County Maintenance Offices.
The TMC Operator can periodically check the real-time
location of a vehicle.
Alternative Course:
Includes:
Market Package(s):
MC01: Maintenance and Construction Vehicle and Equipment
Tracking
MC04: Weather Information Processing and Distribution
MC06: Winter Maintenance
Project Phase:
Future Deployment
Appendix O – Page 47 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 28
Scenario Name:
Congestion Management (Signal Timing)
Description:
The TMC Operator tracks and manages congested highway
conditions.
Preconditions:
Normal Course:
•
•
28.0:
a.
b.
c.
d.
e.
Alternative Course:
28.1:
a.
b.
c.
d.
e.
f.
The TMC Operator is logged into the ATMS software.
Field data is being reported to the ATMS software.
The TMC Operator uses a response plan to alleviate
congestion.
The ATMS software alerts the TMC Operator that traffic is
flowing slowly.
The TMC Operator uses the CCTV to view the location
where traffic is flowing slowly.
The TMC Operator sees that congestion is building up,
but there is no incident.
The TMC Operator activates a response plan.
The TMC Operator monitors the congestion until it is
alleviated.
The TMC Operator uses signal timing to alleviate
congestion (branch at step d.).
The TMC Operator accesses the signal timing library.
The TMC Operator selects a signal timing plan.
The TMC Operator views the signal timing plan.
The TMC Operator activates the signal timing plan.
The ATMS software will notify the TMC Operator when
the plan is successfully activated.
Return to step e.
Includes:
Market Package(s):
ATMS03: Surface Street Control
ATMS04: Freeway Control
ATMS08: Traffic Incident Management System
Project Phase:
Future Deployment
Appendix O – Page 48 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 29
Scenario Name:
Traffic Report Generation
Description:
The TMC Operator generates a traffic report from the ATMS
software.
Preconditions:
Normal Course:
•
•
29.0:
a.
b.
c.
d.
e.
Alternative Course:
The TMC Operator is logged into the ATMS software.
Field data is being reported to the ATMS software.
The TMC Operator generates a traffic report. Anticipated
traffic reports include: Congestion Frequency Profile,
Historic Information by segment or corridor, Urban
Congestion Report, Highway Performance Reports. (See
PennDOT Statewide ATMS Software System
Requirements Appendix B: Sample Graphic
Representations Of The Recommended Performance
Metrics).
The TMC Operator opens the report section of the ATMS.
The TMC Operator selects the type of traffic report to be
generated.
The TMC Operator selects the criteria for the report
generation (i.e. time of day, day of week, roadway
segments, etc.).
The TMC Operator clicks on the generate report button.
The TMC Operator can view the report.
29.1: The TMC Operator saves a traffic report (after step d.).
a. The TMC Operator clicks on the save file button.
b. The TMC Operator enters a file name and selects a file
type.
c. The TMC Operator confirms that the report should be
saved.
Includes:
Market Package(s):
AD1: ITS Data Mart
AD2: ITS Data Warehouse
Project Phase:
Initial Deployment
Appendix O – Page 49 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 30
Scenario Name:
Equipment Status Report
Description:
The TMC Operator views ITS equipment status through the ATMS
software. Possible report types include:
• Percent Uptime
• Device Type
• Detailed History (1 Device)
• Metric on foundational traffic flow data
Preconditions:
Normal Course:
•
•
30.0:
a.
b.
c.
d.
e.
f.
Alternative Course:
30.1:
a.
b.
c.
d.
30.2:
a.
b.
c.
d.
e.
The TMC Operator is logged into the ATMS software.
ITS device data is being reported to the ATMS software.
The TMC Operator generates an equipment status
report.
The TMC Operator opens the Reports section of the ATMS
software.
The TMC Operator selects equipment reports.
The TMC Operator selects the type of equipment report.
The TMC Operator enters the search criteria for the report.
The TMC Operator clicks generate report.
The TMC Operator views the equipment report.
The TMC Operator views equipment status on the map
GUI.
The TMC Operator opens the ATMS Software Map.
The TMC Operator turns on the equipment status layers.
The TMC Operator views the status of the ITS devices on
the map.
An equipment failure report will be automatically generated
when a piece of equipment fails.
The TMC Operator views equipment data in a table style
list (alternative at step a.).
The TMC Operator opens the equipment section of the
ATMS software.
The TMC Operator selects equipment status.
The TMC Operator selects a device type.
The equipment status is displayed in a table style list.
An equipment failure report will be automatically generated
when a piece of equipment fails.
Includes:
Appendix O – Page 50 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Market Package(s):
AD1: ITS Data Mart
AD2: ITS Data Warehouse
Project Phase:
Initial Deployment
Appendix O – Page 51 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 31
Scenario Name:
Equipment Failure Alerts
Description:
The ATMS alerts the TMC Operator of an equipment failure,
such as a failed pixel in a DMS or a loss of communication with
a detector.
Preconditions:
Normal Course:
•
•
•
31.0:
a.
b.
c.
d.
e.
Alternative Course:
31.1:
a.
b.
c.
d.
e.
31.2:
a.
b.
c.
d.
The TMC Operator is logged into the ATMS software.
ITS device data is being reported to the ATMS software.
An ITS device failure is detected.
The ATMS software alerts the TMC operator of a
device failure from the map.
The TMC Operator opens the ATMS Software Map.
The TMC Operator turns on the equipment status
layers.
The TMC Operator views the status of the ITS devices
on the map.
The failed device blinks in red.
An equipment failure report is automatically generated
by the ATMS software.
The ATMS software alerts the TMC Operator of a
device failure from another section of the software.
The TMC Operator is actively using the ATMS software.
A bar at the bottom of the screen blinks red and
displays text saying, “Equipment Failure.”
The TMC Operator mouses over the bar to see more
information about the device failure.
The TMC Operator clicks on the alert toolbar to launch
the equipment management portion of the ATMS
software.
An equipment failure report is automatically generated
by the ATMS software.
The ATMS software alerts the TMC Operator of a
device failure from the map when devices are not being
displayed (branch at step b).
The TMC Operator opens the ATMS Software Map, but
the device layer is not displayed.
A bar at the bottom of the screen blinks red and
displays text saying, “Equipment Failure.”
The TMC Operator mouses over the bar to see more
information about the device failure.
Return to step c. or 31.1.d.
Includes:
Appendix O – Page 52 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Market Package(s):
ATMS07: Regional Traffic Management
Project Phase:
Initial Deployment
Appendix O – Page 53 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 32
Scenario Name:
Performance Reports
Description:
The TMC Operator can generate Performance Measures reports
from the ATMS software based on historical and real-time data.
Some of the information in the performance measures reports will
include travel time index, peak travel index, number of incidents
by type, overall performance index, incident response timeline,
etc. Additional reports will be available to provide information
such as logging TMC actions, length of time for activating
different stages (e.g. incident open, verified, response plan
activated, incident closed) and call logs. (See PennDOT
Statewide ATMS Software System Requirements Appendix B:
Sample Graphic Representations Of The Recommended
Performance Metrics).
Preconditions:
Normal Course:
•
•
32.0:
a.
b.
c.
d.
e.
Alternative Course:
The TMC Operator is logged into the ATMS software.
ITS field data is being reported to the ATMS software.
The TMC Operator generates a performance measure
report.
The TMC Operator opens the report section of the ATMS
software.
The TMC Operator selects the type of performance
reports.
The TMC Operator selects the report criteria.
The TMC Operator clicks on the generate report button.
The TMC Operator can view the report.
32.1:
The TMC Operator saves a performance report (after step
d.).
a. The TMC Operator clicks on the save file button.
b. The TMC Operator enters a file name and selects a file
type.
c. The TMC Operator confirms that the report should be
saved.
Includes:
Market Package(s):
AD1: ITS Data Mart
AD2: ITS Data Warehouse
Project Phase:
Initial Deployment
Appendix O – Page 54 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 33
Scenario Name:
CCTV Blocking
Description:
A TMC Operator with sufficient privileges can block CCTV
camera images so that they cannot be viewed by outside
sources, such as other TMCs, the Internet, and media.
Preconditions:
•
•
A TMC Operator with sufficient privileges is logged into
the ATMS software.
CCTV are functioning properly.
Normal Course:
33.0:
Blocking one CCTV.
a. A TMC Operator with sufficient privileges opens a
CCTV.
b. A TMC Operator with sufficient privileges selects Block
CCTV.
c. A TMC Operator with sufficient privileges saves the
changes.
d. A TMC Operator with sufficient privileges confirms that
the selected CCTV should be blocked.
Alternative Course:
33.1: Blocking CCTV Images (alternative at step a.).
a. A TMC Operator with sufficient privileges opens the
Administrative screen.
b. A TMC Operator with sufficient privileges selects CCTV
Blocking.
c. A list of available CCTV appears.
d. A TMC Operator with sufficient privileges selects the
CCTV to be blocked.
e. Return to step d.
33.2:
Blocking one CCTV from the Map (alternative at step
a.).
a. A TMC Operator with sufficient privileges selects a
CCTV from the ATMS map.
b. A TMC Operator with sufficient privileges selects Block
CCTV.
c. Return to step d.
Includes:
Market Package(s):
ATMS01: Network Surveillance
Project Phase:
Initial Deployment
Appendix O – Page 55 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 34
Scenario Name:
Locking CCTV Control
Description:
The TMC Operator locks control of the CCTV so that no other
user can move the camera.
Preconditions:
Normal Course:
•
34.0:
a.
b.
c.
d.
e.
f.
g.
h.
The TMC Operator is logged into the ATMS software.
If the TMC Operator is controlling a CCTV to view a
critical event, the CCTV control can be locked so that
another user cannot override his control of the camera.
The TMC Operator views the ATMS Map.
The TMC Operator, mouses over the CCTV to check
the status.
The TMC Operator right-clicks on the device.
A CCTV pop-up window with the live camera view is
displayed.
Using the PTZ controls on the CCTV pop-up window,
the TMC Operator can zoom and rotate the camera to
view the monitored roadway.
The TMC Operator clicks on the lock control button.
The TMC Operator confirms that the camera controls
should be locked.
If another TMC Operator tries to take control of the
locked CCTV, he will be notified that control is not
available at this time.
Alternative Course:
Includes:
Market Package(s):
ATMS01: Network Surveillance
Project Phase:
Future Deployment
Appendix O – Page 56 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 35
Scenario Name:
Travel Time – Custom Message Activation
Description:
A TMC Operator activates a custom travel time message on a
DMS.
Preconditions:
•
•
•
•
Normal Course:
35.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
m.
The DMS are fully functional.
The DMS are communicating with the ATMS software.
Travel time information is being transmitted to the ATMS
software.
Travel time links have been configured in the ATMS
software.
A TMC Operator activates a custom travel time
message.
The TMC Operator opens the Travel Time subsystem.
The ATMS travel time subsystem, which when opened
should display all travel time DMS, predefined travel time
scenarios, and links and generated times
The TMC Operator right-clicks on a DMS.
The TMC Operator selects create message.
The TMC Operator types in a custom travel time
message.
The TMC Operator either selects a predefined travel time
scenario or selects the links that are to be included in the
travel time.
The TMC Operator inserts the travel time into the
message. Since PennDOT collects travel time data from
multiple sources, the data from each source should be
compared and a level of confidence should be assigned
to each source. The TMC Operator can select between
several travel time calculation methods (weighted
average, highest confidence level) to be used for travel
time postings
The TMC Operator clicks on view message.
The ATMS software displays the message(s) that will be
sent to the sign(s).
Whenever travel time messages are displayed, a %
confidence will be displayed on the map as well. This
value will indicate the percentage of supporting field
equipment that is functioning correctly.
If necessary, the TMC Operator can edit the message.
The TMC Operator clicks on the Activate button.
The travel time message(s) is activated on the selected
DMS.
Alternative Course:
Appendix O – Page 57 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Includes:
Market Package(s):
ATMS06: Traffic Information Dissemination
Project Phase:
Initial Deployment
Appendix O – Page 58 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 36
Scenario Name:
HAR Beacon Activation
Description:
An HAR beacon is activated.
Preconditions:
•
•
•
•
Normal Course:
36.0:
a.
b.
c.
Alternative Course:
36.1:
The TMC Operator is logged into the ATMS software.
The HAR are communicating with the ATMS software.
The HAR are fully functional.
The HAR has functional beacons.
HAR Beacons are activated.
The TMC Operator opens the HAR subsystem.
The TMC Operator selects an HAR.
The TMC Operator clicks on the Activate Beacons
button.
d. The TMC Operator confirms that the beacons should be
activated.
e. The ATMS software will notify the operator of the
transmission status (i.e. successfully activated or
activation failure).
Using the ATMS Map, HAR beacons are activated
(alternative at step a.).
a. The TMC Operator right-clicks on an HAR icon from the
ATMS Map.
b. The TMC Operator selects Activate Beacons.
c. Return to step d.
Includes:
Market Package(s):
ATMS06: Traffic Information Dissemination
Project Phase:
Initial Deployment
Appendix O – Page 59 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 37
Scenario Name:
Service Patrol Vehicle Tracking / Advanced Vehicle Location
(AVL)
Description:
The ATMS software should track GPS equipped Service Patrol
vehicles. This information includes, at a minimum, vehicle
identifier, GPS coordinates, and the time of day that the data was
collected. The collected data can be used to coordinate the
dispatch of service patrol vehicles.
Preconditions:
Normal Course:
•
•
37.0:
a.
b.
c.
d.
e.
Alternative Course:
37.1:
a.
b.
c.
d.
e.
The TMC Operator is logged into the ATMS software.
The Service Patrol vehicles have active AVL sensors.
During an event (i.e. incident, weather event,
construction) the TMC Operator can track and coordinate
service patrol vehicles.
The TMC Operator opens the AVL subsystem.
The TMC Operator selects Service Patrol Vehicles.
A list of the service patrol vehicles, vehicle status and
vehicle location is displayed.
The TMC Operator can use this information to coordinate
the dispatch to the location.
The TMC Operator can periodically check the real-time
location of a vehicle.
Using the ATMS Map, the TMC Operator can view the
location of service patrol vehicles (alternative at step a.).
The TMC Operator opens the ATMS map.
The TMC Operator turns on the Service Patrol layer.
Vehicles will be displayed on the map in their last reported
location. Each vehicle will be color-coded based on
vehicle status.
The TMC Operator can mouse over the vehicle to get
more information, such as vehicle name/id and contact
information.
Return to step d.
Includes:
Market Package(s):
EM04: Roadway Service Patrols
Project Phase:
Future Deployment
Scenario ID:
Scenario 38
Appendix O – Page 60 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario Name:
Administrative – Ramp Metering Configuration
Description:
The TMC Administrator can configure ramp metering settings,
such as thresholds for changing ramp metering.
Preconditions:
•
•
•
•
•
Normal Course:
38.0:
a.
b.
c.
d.
The TMC Operator is logged into the ATMS software.
Ramp meters are installed in the field
The Ramp Metering Software is communicating with the
ATMS.
Ramp meters and Ramp Meter Supervisory Software
are fully functional
Ramp meters are reporting data back to the TMC
The TMC Operator is able to turn on / off ramp metering
for a corridor.
The TMC Administrator opens the ATMS map.
The TMC Administrator turns on the ramp metering
layer.
The TMC Administrator turns on / off ramp metering for
a corridor.
The TMC Administrator confirms that the changes.
Alternative Course:
Includes:
Scenario 39: HOV Lane Management
Scenario 48: Ramp Metering Control
Market Packages:
ATMS04: Freeway Control
Project Phase:
Future Deployment
Appendix O – Page 61 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 39
Scenario Name:
HOV Lane Management
Description:
The TMC Operator can activate and edit established HOV
Lane Management plans. While HOV lane activation plans will
be pre-established, the TMC Operator can edit and activate
HOV lane plans as necessary.
• The TMC Operator is logged into the ATMS software.
• Ramp meters are fully functional.
• Lane Use Signals are fully functional.
• HOV Lane Use Signals are fully functional.
Preconditions:
Normal Course:
39.0: The TMC Operator activates the HOV lane plan.
a. Prior to the time the HOV Lane should be activated, the
TMC Operator will receive a pop-up reminder that the
HOV lane will be activated.
b. The TMC Operator must close the HOV lane to traffic.
c. Once the TMC Operator receives notification that the
lane is cleared, the TMC Operator can activate the
HOV lane.
d. The TMC Operator confirms that the HOV Lane plan
should be activated.
Alternative Course:
39.1 The TMC Operator edits the HOV lane plan.
a. Prior to the time the HOV Lane should be activated, the
TMC Operator will receive a pop-up reminder that the
HOV lane will be activated.
b. The TMC Operator must close the HOV lane to traffic.
c. Once the TMC Operator receives notification that the
lane is cleared, the TMC Operator can activate the HOV
lane.
d. The TMC Operator confirms that the HOV Lane plan
should be activated.
Includes:
Market Packages:
ATMS04: Freeway Control
ATMS05: HOV Lane Management
ATMS18: Reversible Lane Management
Project Phase:
Initial Deployment
Appendix O – Page 62 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 40
Scenario Name:
Lane Control Signals
Description:
The TMC Operator changes the lane control signals.
Preconditions:
Normal Course:
•
•
The TMC Operator is logged into the ATMS Software.
The Lane Control Signals are functioning properly.
40.0: The TMC Operator uses lane control signals to change
the traffic pattern.
a. The TMC Operator selects a link on the ATMS Map.
b. The TMC Operator opens the current lane control signal
status.
c. The TMC Operator selects new configuration
d. The TMC Operator clicks on the activate button.
e. The TMC Operator confirms that the changes should be
made.
Alternative Course:
Includes:
Market Packages:
ATMS04: Freeway Control
Project Phase:
Future Deployment
Appendix O – Page 63 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 41
Scenario Name:
Description:
Preconditions:
Normal Course:
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Scenario 41 (Variable Speed Limits) from Rev. 2 was removed.
This page was intentionally left blank. While the Scenario has been removed, the Scenario ID
was left as a placeholder.
Appendix O – Page 64 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 42
Scenario Name:
Call Log
Description:
The TMC Operator saves information into the call log.
Preconditions:
Normal Course:
•
The TMC Operator is logged into the ATMS Software.
42.0 The TMC Operator enters information into the call log.
a. The TMC Operator clicks on the new call button.
b. The TMC Operator enters basic call information (i.e.
name, number, date and time)
c. The TMC Operator enters free form text.
d. The TMC Operator clicks on the save button.
e. The TMC Operator confirms that the information should
be saved.
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Initial Deployment
Appendix O – Page 65 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 43
Scenario Name:
Administration – Contact List
Description:
The TMC Administrator creates / edits a contact list that is based
on the incident severity.
Preconditions:
Normal Course:
•
The TMC Administrator is logged into the ATMS Software.
43.0:
The TMC Administrator creates a list of contacts for each
severity level.
The TMC Administrator opens the Administrative screens.
The TMC Administrator selects contact list.
The TMC Administrator adds or edits contacts / contact
information to the list of people who must be notified.
The TMC Operator clicks on the save button.
The TMC Operator confirms that the information should
be saved.
a.
b.
c.
d.
e.
Alternative Course:
Includes:
Market Packages:
Project Phase:
Initial Deployment
Appendix O – Page 66 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 44
Scenario Name:
Diversion Route Activation
Description:
Pre-established diversion routes are saved in the diversion route
library and can be activated as needed. Also, in the event that a
custom diversion route is needed, the TMC Operator can update
the diversion plan.
Preconditions:
Normal Course:
•
44.0:
a.
b.
c.
d.
e.
Alternative Course:
The TMC Operator is logged into the ATMS software.
The TMC Operator can activate pre-established diversion
routes from the library.
The TMC Operator opens the diversion route subsystem.
The TMC Operator selects a location from which traffic
needs to be diverted.
The TMC Operator selects a diversion route.
The TMC Operator clicks on the activate button.
The TMC Operator confirms that the diversion route
should be activated. .
44.1:
The TMC Operator activates a custom diversion route.
(branch at step c.).
a. Field personnel notify the TMC Operator that the
predefined diversion route cannot be implemented;
therefore, the field personnel inform the TMC Operator of
the new diversion route.
b. Using the TMC Map, the TMC Operator modifies the
diversion route based on the information received from the
field personnel.
c. Return to step d.
Includes:
Market Package(s):
Project Phase:
ATMS01: Network Surveillance
Initial Deployment
Appendix O – Page 67 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 45
Scenario Name:
Application-Level Operational Vendor Support
Description:
The ATMS software will provide access to an application level
operational vendor support website, which will allow the users to
report software errors to the vendor. This website will track
reported errors and resolutions.
Preconditions:
Normal Course:
•
•
The TMC Operator is logged into the ATMS Software.
The TMC Operator has access to the Internet.
45.0: The TMC Operator detects and reports a software error.
a. The TMC Operator receives an error message from the
ATMS software.
b. The TMC Operator captures the screenshot.
c. The TMC Operator accesses the vendor supported
website.
d. The TMC Operator enters a software error report and
attaches the screenshot.
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Initial Deployment
Appendix O – Page 68 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 46
Scenario Name:
Generation of Preventive Maintenance Schedule for ITS
Equipment
Description:
The TMC Operator can create preventive maintenance schedule
for ITS equipment that is tracked by the ATMS software. For
example, the TMC Operator can create a schedule VMS pixel
tests on a weekly basis. If a schedule is created, TMC Operators
will receive a reminder that a preventive maintenance activity is
scheduled
Preconditions:
•
•
•
Normal Course:
46.0:
a.
b.
c.
d.
e.
f.
g.
h.
i.
Alternative Course:
The TMC Operator is logged into the ATMS software.
ITS equipment information is entered into the ATMS
software.
ITS equipment is communicating with the ATMS software
The TMC operator creates a preventive maintenance
schedule for ITS equipment by accessing equipment
from the ATMS map.
The TMC Operator opens the ATMS map.
The TMC Operator selects a device from the map.
The TMC Operator selects schedule preventive
maintenance.
When the preventive maintenance screen appears,
information about the selected device (i.e. device type,
manufacture, location, etc.) will already populate the
screen.
The TMC Operator should select the type of preventive
maintenance activity that should be performed.
The TMC Operator should select the frequency for which
the preventive maintenance activity will be performed (i.e.
every day, every 7 days, or every 30 days, etc.)
The TMC Operator should schedule a date on which the
first preventive maintenance activity should occur.
The TMC Operator should save the entry.
The TMC operator will confirm that the entry should be
saved.
46.1
The TMC operator creates a preventive maintenance
schedule for ITS equipment by accessing the equipment
subsystem (Alternative at step a.)
a. The TMC Operator opens the equipment subsystem of
the ATMS software.
b. The TMC Operator selects preventive maintenance.
c. When the preventive maintenance screen appears, the
TMC operator selects the device information (i.e. device
type, manufacturer, model number, location, etc.)
Appendix O – Page 69 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
d. Return to step e.
46.2
a.
b.
c.
d.
Includes:
The TMC operator edits a preventive maintenance
schedule for ITS equipment by accessing the equipment
subsystem (Alternative at 46.1 step b.)
The TMC operator selects a device for which preventive
maintenance activities should be edited.
The TMC updates the equipment information or schedule
on the preventive maintenance screen.
The TMC Operator can log and track maintenance
activities as they occur.
Return to step h.
Scenario 11 (Normal Operations)
Market Package(s):
Project Phase:
Initial Deployment
Appendix O – Page 70 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 47
Scenario Name:
Remote Viewing of Current Equipment Status, Traveler
Information Messages, and Incident Information
Description:
Other stakeholders can remotely review equipment status,
current traveler information messages and current incident
information from the ATMS map.
Preconditions:
•
•
Normal Course:
47.0:
a.
b.
c.
d.
e.
f.
g.
h.
ITS equipment information is entered into the ATMS
software.
ITS equipment is communicating with the e software
The stakeholder reviews equipment status, traveler
information messages, and current incident information
by opening the ATMS map remotely.
The stakeholder uses the Internet to open the ATMS
map.
The ITS equipment will be displayed on the map. The
equipment status (i.e. OK, disabled, communication error)
will be identified by a color code.
The stakeholder can view information, such as current
speeds, travel times, event details, or the current
message that is displayed on a DMS or HAR.
Current speeds will be displayed as various colors (such
as red, yellow, and green).
DMS messages will be displayed in the map view upon
accessing the ATMS map.
HAR messages will be viewable when mousing over the
HAR device that is active.
Current incidents and events will be displayed on the
ATMS map.
The stakeholder can mouse over the incident/event icon
to get more information.
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Initial Deployment
Appendix O – Page 71 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 48
Scenario Name:
Ramp Metering
Description:
The TMC Operator can manage ramp meters.
Preconditions:
•
•
•
•
Normal Course:
The TMC Operator is logged into the ATMS software.
Ramp meters are installed in the field
Ramp meters and ramp meter supervisory software are
fully functional
Ramp meters are reporting data back to the TMC
48.0: The Operator is able to turn on / off ramp meters.
a. Based on triggered traffic threshold levels, the ATMS
system will alert the TMC Operator of a recommended
ramp metering control plan. For example, when the traffic
backs up on the ramp, the TMC Operator will be advised
that ramp meters should be turned off.
b. The TMC Operator uses the activate button to implement
the activation of the recommended ramp metering plan.
c. The TMC Operator can turn on/off ramp metering by
corridor.
d. The TMC Operator must confirm that the plan should be
activated.
Alternative Course:
Includes:
Market Packages:
ATMS04: Freeway Control
Project Phase:
Future Deployment
Appendix O – Page 72 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 49
Scenario Name:
Description:
Preconditions:
Normal Course:
Alternative Course:
Includes:
Market Package(s):
Project Phase:
Scenario 49 (Variable Speed Limit Control) was removed.
This page was intentionally left blank. While the Scenario has been removed, the Scenario ID
was left as a placeholder.
Appendix O – Page 73 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 50
Scenario Name:
Proactive Stakeholder Notification
Description:
The ATMS will send e-mail notifications to stakeholders who have
subscribed to the notification service.
Preconditions:
Normal Course:
•
Stakeholders subscribe to receive e-mail notifications
about selected locations.
50.0: ATMS sends an e-mail notification to stakeholders who
subscribed to the notification service.
a. Using the Internet stakeholders sign up to received e-mail
notifications about traffic events that occur in a specified
location(s).
b. The TMC Operator enters event information into the
ATMS.
c. The notification message should be sent to subscribers.
d. The subscribers will receive a notification about the
current event.
Alternative Course:
Includes:
Market Packages:
ATIS01: Broadcast Traveler Information
Project Phase:
Initial Deployment
Appendix O – Page 74 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 51
Scenario Name:
Equipment Diagnostics
Description:
The TMC Operator can run equipment diagnostic tests to see the
current status of specified equipment types or locations. The
TMC Operator can also update the status if necessary.
Preconditions:
Normal Course:
•
•
•
The TMC Operator is logged into the ATMS.
All field equipment is fully functional.
All field equipment is reporting data back to the ATMS.
51.0: The TMC Operator runs equipment diagnostics based on
equipment location or equipment type.
a. The TMC Operator opens the equipment diagnostic
segment of the ATMS.
b. The TMC operator chooses to run the equipment
diagnostic based on a location (e.g. District) or equipment
type (e.g. DMS, CCTV or HAR).
c. The TMC Operator runs the diagnostic tests.
d. Once the diagnostics are completed, a screen will display
the current status of each piece of equipment.
e. The TMC Operator can edit the status (e.g. OK to Out-ofService), if necessary.
f. The TMC Operator can print or save the diagnostic report.
Alternative Course:
Includes:
Market Packages:
Project Phase:
Initial Deployment
Appendix O – Page 75 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
Scenario ID:
Scenario 52
Scenario Name:
Roadway Weather Information System
Description:
The TMC Operator can view data collected by the Roadway
Weather Information System (RWIS) readers and the TMC
Operator can use the collected information to issue general
traveler advisories or issue location specific warnings to drivers.
Preconditions:
Normal Course:
•
•
•
The TMC Operator is logged into the ATMS.
All RWIS readers are fully functional.
All RWIS readers are reporting data back to the ATMS.
52.0: The TMC Operator views data collected by the RWIS.
a. The TMC Operator opens the ATMS map and turns on
the RWIS layer.
b. The TMC Operator can mouse over a RWIS reader to get
current information.
c. The TMC Operator can use DMS and HAR to notify the
travelers of hazards traveler conditions.
Alternative Course:
Includes:
Scenario 16 (DMS Activation)
Scenario 21 (HAR Activation)
Market Packages:
MC03: Road Weather Data Collection
MC04: Weather Information Processing and Distribution
Project Phase:
Future Deployment
Appendix O – Page 76 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
12.1 SUMMARY OF SCENARIOS BY PHASE
12.1.1
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
INITIAL DEPLOYMENT
Scenario 1: Administration – Creating and Defining User Groups
Scenario 2: Administration – Adding New Users
Scenario 3: Administration – Editing Users
Scenario 4: Administration – Disabling Users
Scenario 5: Administration – Adding Field Devices
Scenario 6: Administration – Updating Device Information
Scenario 7: Administration – Creating Camera Presets
Scenario 8: Administration – Response Plan Creation
Scenario 9: Administration – Diversion Route Creation
Scenario 10: Administration – TMC Handoff
Scenario 11: Normal Operations
Scenario 12: CCTV Control
Scenario 13: Sharing CCTV within a TMC
Scenario 15: DMS Message Creation
Scenario 16: DMS Activation
Scenario 18: DMS sharing within a TMC
Scenario 19: Travel Time – Preset Message Activation
Scenario 20: HAR Message Creation
Scenario 21: HAR Activation
Scenario 23: HAR sharing within a TMC
Scenario 24: Incident Detection
Scenario 25: Incident Management
Scenario 26: Response Plan Activation
Scenario 29: Traffic Report Generation
Scenario 30: Equipment Status Report
Scenario 31: Equipment Failure Alerts
Scenario 32: Performance Reports
Scenario 33: CCTV Blocking
Scenario 35: Travel Time – Custom Message Activation
Scenario 36: HAR Beacon Activation
Scenario 39: HOV Lane Management
Scenario 42: Call Log
Scenario 43: Administration – Contact List
Scenario 44: Diversion Route Activation
Scenario 45: Application-Level Operational Vendor Support
Scenario 46: Generation of Preventive Maintenance Schedule for ITS Equipment
Scenario 47: Remote Viewing of Current Equipment Status, Traveler Information
Messages, and Incident Information
Scenario 50: Proactive Stakeholder Notification
Scenario 51: Equipment Diagnostics
Appendix O – Page 77 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
12.1.2
•
•
•
•
•
•
•
•
FUTURE DEPLOYMENT
Scenario 27: Maintenance and Construction Vehicle and Equipment Tracking /
Advanced Vehicle Location (AVL)
Scenario 28: Congestion Management (Signal Timing)
Scenario 34: Locking CCTV Control
Scenario 37: Service Patrol Vehicle Tracking / Advanced Vehicle Location (AVL)
Scenario 38: Administrative - Ramp Metering Configuration
Scenario 40: Lane Control Signals
Scenario 48: Ramp Metering
Scenario 52: Roadway Weather Information System
Appendix O – Page 78 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
13.0 SUMMARY OF IMPACTS
The transition from existing software to the new ATMS software will have to be managed very
carefully. It is anticipated that a single District (preferably one with newer equipment and limited
or no current ATMS software) will be selected as the pilot location. Concurrently with the
development of the software, the system inventory will need to be verified and hardware
elements evaluated. In some cases, it may be more cost effective to abandon or upgrade older
elements, rather than develop new custom software to address these devices.
It is also recommended that system metrics are put in place now, so as to baseline the current
performance prior to installing the ATMS software. In this way, trends can be developed
showing the system performance both before and after the new ATMS software has been
installed.
Appendix O – Page 79 of 88
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
APPENDIX A: MARKET PACKAGES
The following descriptions for the market packages to be addressed in the Statewide ATMS
Software are from the National ITS Architecture.
ARCHIVED DATA MANAGEMENT
AD1: ITS Data Mart - This market package provides a focused archive that houses data
collected and owned by a single agency, district, private sector provider, research institution, or
other organization. This focused archive typically includes data covering a single transportation
mode and one jurisdiction that is collected from an operational data store and archived for future
use. It provides the basic data quality, data privacy, and meta data management common to all
ITS archives and provides general query and report access to archive data users.
AD2: ITS Data Warehouse - This market package includes all the data collection and
management capabilities provided by the ITS Data Mart, and adds the functionality and
interface definitions that allow collection of data from multiple agencies and data sources
spanning across modal and jurisdictional boundaries. It performs the additional transformations
and provides the additional meta data management features that are necessary so that all this
data can be managed in a single repository with consistent formats. The potential for large
volumes of varied data suggests additional on-line analysis and data mining features that are
also included in this market package in addition to the basic query and reporting user access
features offered by the ITS Data Mart.
TRAVELER INFORMATION
ATIS01: Broadcast Traveler Information - This market package collects traffic conditions,
advisories, general public transportation, toll and parking information, incident information,
roadway maintenance and construction information, air quality and weather information, and
broadcasts the information to travelers using technologies such as FM subcarrier, satellite radio,
cellular data broadcasts, and Internet web casts. The information may be provided directly to
travelers or provided to merchants and other traveler service providers so that they can better
inform their customers of travel conditions. Different from the market package ATMS6 - Traffic
Information Dissemination, which provides localized HAR and DMS information capabilities,
ATIS1 provides a wide area digital broadcast service. Successful deployment of this market
package relies on availability of real-time traveler information from roadway instrumentation,
probe vehicles or other sources.
ATIS06: Transportation Operations Data Sharing - This market package makes real-time
transportation operations data available to transportation system operators. The Information
Service Provider collects, processes, and stores current information on traffic and travel
conditions and other information about the current state of the transportation network and
makes this information available to transportation system operators, facilitating the exchange of
qualified, real-time information between agencies. Using the provided information, transportation
system operators can manage their individual systems based on an overall view of the regional
transportation system. The regional transportation operations data resource represented by the
Information Service Provider may be implemented as a web application that provides a webConcept of Operations
(Appendix a)
Appendix O page 80
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
based access to system operators, an enterprise database that provides a network interface to
remote center applications, or any implementation that supports regional sharing of real-time
transportation operations data.
TRAFFIC MANAGEMENT
ATMS01: Network Surveillance - This market package includes traffic detectors, other
surveillance equipment, the supporting field equipment, and fixed-point to fixed-point
communications to transmit the collected data back to the Traffic Management Subsystem. The
derived data can be used locally such as when traffic detectors are connected directly to a
signal control system or remotely (e.g., when a CCTV system sends data back to the Traffic
Management Subsystem). The data generated by this market package enables traffic managers
to monitor traffic and road conditions, identify and verify incidents, detect faults in indicator
operations, and collect census data for traffic strategy development and long range planning.
The collected data can also be analyzed and made available to users and the Information
Service Provider Subsystem.
ATMS02: Traffic Probe Surveillance - This market package provides an alternative approach for
surveillance of the roadway network. Two general implementation paths are supported by this
market package: 1) wide-area wireless communications between the vehicle and center is used
to communicate vehicle operational information and status directly to the center, and 2)
dedicated short range communications between passing vehicles and the roadside is used to
provide equivalent information to the center. The first approach leverages wide area
communications equipment that may already be in the vehicle to support personal safety and
advanced traveler information services. The second approach utilizes vehicle equipment that
supports toll collection, in-vehicle signing, and other short range communications applications
identified within the architecture. The market package enables transportation operators and
traveler information providers to monitor road conditions, identify incidents, analyze and reduce
the collected data, and make it available to users and private information providers. It requires
one of the communications options identified above, on-board equipment, data reduction
software, and fixed-point to fixed-point links between centers to share the collected information.
Both “Opt out” and “Opt in” strategies are available to ensure the user has the ability to turn off
the probe functions to ensure individual privacy. Due to the large volume of data collected by
probes, data reduction techniques are required, such as the ability to identify and filter out-ofbounds or extreme data reports.
ATMS03: Surface Street Control - This market package provides the central control and
monitoring equipment, communication links, and the signal control equipment that support local
surface street control and/or arterial traffic management. A range of traffic signal control
systems are represented by this market package ranging from fixed-schedule control systems to
fully traffic responsive systems that dynamically adjust control plans and strategies based on
current traffic conditions and priority requests. This market package is generally an intrajurisdictional package that does not rely on real-time communications between separate control
systems to achieve area-wide traffic signal coordination. Systems that achieve coordination
across jurisdictions by using a common time base or other strategies that do not require real
time coordination would be represented by this package. This market package is consistent with
typical urban traffic signal control systems.
Concept of Operations
(Appendix a)
Appendix O page 81
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
ATMS04: Freeway Control - This market package provides central monitoring and control,
communications, and field equipment that support freeway management. It supports a range of
freeway management control strategies including ramp metering, interchange metering,
mainline lane controls, mainline metering, and other strategies including variable speed
controls. This package incorporates the instrumentation included in the Network Surveillance
Market Package to support freeway monitoring and adaptive strategies as an option.
This market package also includes the capability to utilize surveillance information for detection
of incidents. Typically, the processing would be performed at a traffic management center;
however, developments might allow for point detection with roadway equipment. For example, a
CCTV might include the capability to detect an incident based upon image changes.
Additionally, this market package allows general advisory and traffic control information to be
provided to the driver while en route.
ATMS05: HOV Lane Management - This market package manages HOV lanes by coordinating
freeway ramp meters and connector signals with HOV lane usage signals. Preferential
treatment is given to HOV lanes using special bypasses, reserved lanes, and exclusive rightsof-way that may vary by time of day. Vehicle occupancy detectors may be installed to verify
HOV compliance and to notify enforcement agencies of violations.
ATMS06: Traffic Information Dissemination - This market package provides driver information
using roadway equipment such as dynamic message signs or highway advisory radio. A wide
range of information can be disseminated including traffic and road conditions, closure and
detour information, incident information, and emergency alerts and driver advisories. This
package provides information to drivers at specific equipped locations on the road network.
Careful placement of the roadway equipment provides the information at points in the network
where the drivers have recourse and can tailor their routes to account for the new information.
This package also covers the equipment and interfaces that provide traffic information from a
traffic management center to the media (for instance via a direct tie-in between a traffic
management center and radio or television station computer systems), Transit Management,
Emergency Management, and Information Service Providers. A link to the Maintenance and
Construction Management subsystem allows real time information on road/bridge closures due
to maintenance and construction activities to be disseminated.
ATMS07: Regional Traffic Management - This market package provides for the sharing of traffic
information and control among traffic management centers to support regional traffic
management strategies. Regional traffic management strategies that are supported include
coordinated signal control in a metropolitan area and coordination between freeway operations
and arterial signal control within a corridor. This market package advances the Surface Street
Control and Freeway Control Market Packages by adding the communications links and
integrated control strategies that enable integrated interjurisdictional traffic management. The
nature of optimization and extent of information and control sharing is determined through
working arrangements between jurisdictions. This package relies principally on roadside
instrumentation supported by the Surface Street Control and Freeway Control Market Packages
and adds hardware, software, and fixed-point to fixed-point communications capabilities to
implement traffic management strategies that are coordinated between allied traffic
management centers. Several levels of coordination are supported from sharing of information
through sharing of control between traffic management centers.
Concept of Operations
(Appendix a)
Appendix O page 82
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
ATMS08: Traffic Incident Management System - This market package manages both
unexpected incidents and planned events so that the impact to the transportation network and
traveler safety is minimized. The market package includes incident detection capabilities
through roadside surveillance devices (e.g. CCTV) and through regional coordination with other
traffic management, maintenance and construction management and emergency management
centers as well as rail operations and event promoters. Information from these diverse sources
is collected and correlated by this market package to detect and verify incidents and implement
an appropriate response. This market package supports traffic operations personnel in
developing an appropriate response in coordination with emergency management, maintenance
and construction management, and other incident response personnel to confirmed incidents.
The response may include traffic control strategy modifications or resource coordination
between center subsystems. Incident response also includes presentation of information to
affected travelers using the Traffic Information Dissemination market package and
dissemination of incident information to travelers through the Broadcast Traveler Information or
Interactive Traveler Information market packages. The roadside equipment used to detect and
verify incidents also allows the operator to monitor incident status as the response unfolds. The
coordination with emergency management might be through a CAD system or through other
communication with emergency field personnel. The coordination can also extend to tow trucks
and other allied response agencies and field service personnel.
ATMS09: Traffic Decision Support and Demand Management - This market package
recommends courses of action to traffic operations personnel based on an assessment of
current and forecast road network performance. Recommendations may include predefined
incident response plans and regional surface street and freeway control strategies that correct
network imbalances. Where applicable, this market package also recommends transit, parking,
and toll strategies to influence traveler route and mode choices to support travel demand
management (TDM) programs and policies managing both traffic and the environment. TDM
recommendations are coordinated with transit, parking, and toll administration centers to
support regional implementation of TDM strategies. Incident response and congestion
management recommendations are implemented by the local traffic management center and
coordinated with other regional centers by other market packages (see ATMS07-Regional
Traffic Management and ATMS08-Traffic Incident Management). All recommendations are
based on historical evaluation, real-time assessment, and forecast of the roadway network
performance based on predicted travel demand patterns. Traffic data is collected from sensors
and surveillance equipment, other traffic management centers. Forecasted traffic loads are
derived from historical data and route plans supplied by the Information Service Provider
Subsystem. This market package also collects air quality, parking availability, transit usage, and
vehicle occupancy data to support TDM, where applicable.
ATMS18: Reversible Lane Management - This market package provides for the management of
reversible lane facilities. In addition to standard surveillance capabilities, this market package
includes sensory functions that detect wrong-way vehicles and other special surveillance
capabilities that mitigate safety hazards associated with reversible lanes. The package includes
the field equipment, physical lane access controls, and associated control electronics that
manage and control these special lanes. This market package also includes the equipment
used to electronically reconfigure intersections and manage right-of-way to address dynamic
demand changes and special events.
Concept of Operations
(Appendix a)
Appendix O page 83
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
ATMS19: Speed Monitoring - This market package monitors the speeds of vehicles traveling
through a roadway system. If the speed is determine to be excessive, roadside equipment can
suggest a safe driving speed. Environmental conditions may be monitored and factored into the
safe speed advisories that are provided to the motorist. This service can also support
notifications to an enforcement agency to enforce the speed limit on a roadway system.
ATMS21: Roadway Closure Management - This market package closes roadways to vehicular
traffic when driving conditions are unsafe, maintenance must be performed, and other scenarios
where access to the roadway must be prohibited. The market package includes automatic or
remotely controlled gates or barriers that control access to roadway segments including ramps
and traffic lanes. Remote control systems allow the gates to be controlled from a central location
or from a vehicle at the gate/barrier location, improving system efficiency and reducing
personnel exposure to unsafe conditions during severe weather and other situations where
roads must be closed. Surveillance systems allow operating personnel to visually verify the safe
activation of the closure system and driver information systems (e.g., DMS) provide closure
information to motorists in the vicinity of the closure. The equipment managed by this market
package includes the control and monitoring systems, the field devices (e.g., gates, warning
lights, DMS, CCTV cameras) at the closure location(s), and the information systems that notify
other systems of a closure. This market package covers general road closure applications;
specific closure systems that are used at railroad grade crossings, drawbridges, reversible
lanes, etc. are covered by other ATMS market packages.
VEHICLE SAFETY
AVSS10: Intersection Collision Avoidance - This market package will determine the probability
of an intersection collision and provide timely warnings to approaching vehicles so that
avoidance actions can be taken. This market package builds on the Intersection Safety Warning
field and in-vehicle equipment and adds equipment in the vehicle that can take control of the
vehicle to avoid intersection violations and potential collisions. The same sensors and
communications equipment in the roadway infrastructure are used to assess vehicle locations
and speeds near an intersection. This information is determined and communicated to the
approaching vehicle using a short range communications system. The vehicle uses this
information to develop control actions which alter the vehicle’s speed and steering control and
potentially activate its pre-crash safety system.
COMMERCIAL VEHICLE OPERATIONS
CVO06: Weigh-In-Motion - This market package provides for high speed weigh-in-motion with
or without Automated Vehicle Identification (AVI) capabilities. This market package provides the
roadside equipment that could be used as a stand-alone system or to augment the Electronic
Clearance (CVO03) market package.
EMERGENCY MANAGEMENT
EM04: Roadway Service Patrols - This market package supports roadway service patrol
vehicles that monitor roads that aid motorists, offering rapid response to minor incidents (flat
tire, accidents, out of gas) to minimize disruption to the traffic stream. If problems are detected,
the roadway service patrol vehicles will provide assistance to the motorist (e.g., push a vehicle
to the shoulder or median). The market package monitors service patrol vehicle locations and
Concept of Operations
(Appendix a)
Appendix O page 84
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
supports vehicle dispatch to identified incident locations. Incident information collected by the
service patrol is shared with traffic, maintenance and construction, and traveler information
systems.
EM05: Transportation Infrastructure Protection - This market package includes the monitoring of
transportation infrastructure (e.g., bridges, tunnels and management centers) for potential
threats using sensors and surveillance equipment and barrier and safeguard systems to control
access, preclude an incident, and mitigate the impact of an incident if it occurs. Threats can
result from acts of nature (e.g., hurricanes, earthquakes), terrorist attacks or other incidents
causing damage to the infrastructure (e.g., stray barge hitting a bridge support). Infrastructure
may be monitored with acoustic, environmental threat (such as nuclear, biological, chemical,
and explosives), infrastructure condition and integrity, motion and object sensors and video and
audio surveillance equipment. Data from such sensors and surveillance equipment may be
processed in the field or sent to a center for processing. The data enables operators at the
center to detect and verify threats. When a threat is detected, agencies are notified. Detected
threats or advisories received from other agencies result in an increased level of system
preparedness. In response to threats, barrier and safeguard systems may be activated by
Traffic Management Subsystems to deter an incident, control access to an area or mitigate the
impact of an incident. Barrier systems include gates, barriers and other automated and remotely
controlled systems that manage entry to transportation infrastructure. Safeguard systems
include blast shields, exhaust systems and other automated and remotely controlled systems
that mitigate impact of an incident.
EM06: Wide-Area Alert - This market package uses ITS driver and traveler information systems
to alert the public in emergency situations such as child abductions, severe weather events, civil
emergencies, and other situations that pose a threat to life and property. The alert includes
information and instructions for transportation system operators and the traveling public,
improving public safety and enlisting the public’s help in some scenarios. The ITS technologies
will supplement and support other emergency and homeland security alert systems such as the
Emergency Alert System (EAS). When an emergency situation is reported and verified and the
terms and conditions for system activation are satisfied, a designated agency broadcasts
emergency information to traffic agencies, transit agencies, information service providers, toll
operators, and others that operate ITS systems. The ITS systems, in turn, provide the alert
information to transportation system operators and the traveling public using ITS technologies
such as dynamic message signs, highway advisory radios, in-vehicle displays, transit displays,
511 traveler information systems, and traveler information web sites.
EM09: Evacuation and Reentry Management - This market package supports evacuation of the
general public from a disaster area and manages subsequent reentry to the disaster area. The
market package addresses evacuations for all types of disasters, including disasters like
hurricanes that are anticipated and occur slowly, allowing a well-planned orderly evacuation, as
well as disasters like terrorist acts that occur rapidly, without warning, and allow little or no time
for preparation or public warning.
This market package supports coordination of evacuation plans among the federal, state, and
local transportation, emergency, and law enforcement agencies that may be involved in a largescale evacuation. All affected jurisdictions (e.g., states and counties) at the evacuation origin,
evacuation destination, and along the evacuation route are informed of the plan. Information is
shared with traffic management agencies to implement special traffic control strategies and to
Concept of Operations
(Appendix a)
Appendix O page 85
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
control evacuation traffic, including traffic on local streets and arterials as well as the major
evacuation routes. Reversible lanes, shoulder use, closures, special signal control strategies,
and other special strategies may be implemented to maximize capacity along the evacuation
routes. Transit resources play an important role in an evacuation, removing many people from
an evacuated area while making efficient use of limited capacity. Additional shared transit
resources may be added and managed in evacuation scenarios. Resource requirements are
forecast based on the evacuation plans, and the necessary resources are located, shared
between agencies if necessary, and deployed at the right locations at the appropriate times.
Evacuations are also supported by EM10, the "Disaster Traveler Information" market package,
which keeps the public informed during evacuations. See that market package for more
information.
EM10: Disaster Traveler Information - This market package uses ITS to provide disaster-related
traveler information to the general public, including evacuation and reentry information and other
information concerning the operation of the transportation system during a disaster. This market
package collects information from multiple sources including traffic, transit, public safety,
emergency management, shelter provider, and travel service provider organizations. The
collected information is processed and the public is provided with real-time disaster and
evacuation information using ITS traveler information systems.
A disaster will stress the surface transportation system since it may damage transportation
facilities at the same time that it places unique demands on these facilities to support public
evacuation and provide access for emergency responders. Similarly, a disaster may interrupt or
degrade the operation of many traveler information systems at the same time that safety-critical
information must be provided to the traveling public. This market package keeps the public
informed in these scenarios, using all available means to provide information about the disaster
area including damage to the transportation system, detours and closures in effect, special
traffic restrictions and allowances, special transit schedules, and real-time information on traffic
conditions and transit system performance in and around the disaster.
This market package also provides emergency information to assist the public with evacuations
when necessary. Information on mandatory and voluntary evacuation zones, evacuation times,
and instructions are provided. Available evacuation routes and destinations and current and
anticipated travel conditions along those routes are provided so evacuees are prepared and
know their destination and preferred evacuation route. Information on available transit services
and traveler services (shelters, medical services, hotels, restaurants, gas stations, etc.) is also
provided. In addition to general evacuation information, this market package provides specific
evacuation trip planning information that is tailored for the evacuee based on origin, selected
destination, and evacuee-specified evacuation requirements and route parameters.
This market package augments the ATIS market packages that provide traveler information on
a day-to-day basis for the surface transportation system. This market package provides focus
on the special requirements for traveler information dissemination in disaster situations.
MAINTENANCE AND CONSTRUCTION MANAGEMENT
MC01: Maintenance and Construction Vehicle and Equipment Tracking - This market package
will track the location of maintenance and construction vehicles and other equipment to
Concept of Operations
(Appendix a)
Appendix O page 86
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
ascertain the progress of their activities. These activities can include ensuring the correct roads
are being plowed and work activity is being performed at the correct locations.
MC02: Maintenance and Construction Vehicle Maintenance - This market package performs
vehicle maintenance scheduling and manages both routine and corrective maintenance
activities on vehicles and other maintenance and construction equipment. It includes on-board
sensors capable of automatically performing diagnostics for maintenance and construction
vehicles, and the systems that collect this diagnostic information and use it to schedule and
manage vehicle maintenance.
MC03: Road Weather Data Collection - This market package collects current road and weather
conditions using data collected from environmental sensors deployed on and about the roadway
(or guideway in the case of transit related rail systems). In addition to fixed sensor stations at
the roadside, sensing of the roadway environment can also occur from sensor systems located
on Maintenance and Construction Vehicles. The collected environmental data is used by the
Weather Information Processing and Distribution Market Package to process the information
and make decisions on operations. The collected environmental data may be aggregated,
combined with data attributes and sent to meteorological systems for data qualification and
further data consolidation. The market package may also request and receive qualified data
sets from meteorological systems.
MC04: Weather Information Processing and Distribution - This market package processes and
distributes the environmental information collected from the Road Weather Data Collection
market package. This market package uses the environmental data to detect environmental
hazards such as icy road conditions, high winds, dense fog, etc. so system operators and
decision support systems can make decision on corrective actions to take. The continuing
updates of road condition information and current temperatures can be used by system
operators to more effectively deploy road maintenance resources, issue general traveler
advisories, issue location specific warnings to drivers using the Traffic Information
Dissemination market package, and aid operators in scheduling work activity.
MC05: Roadway Automated Treatment - This market package automatically treats a roadway
section based on environmental or atmospheric conditions. Treatments include fog dispersion,
anti-icing chemicals, etc. The market package includes the environmental sensors that detect
adverse conditions, the automated treatment system itself, and driver information systems (e.g.,
dynamic message signs) that warn drivers when the treatment system is activated.
MC06: Winter Maintenance - This market package supports winter road maintenance including
snow plow operations, roadway treatments (e.g., salt spraying and other anti-icing material
applications), and other snow and ice control activities. This package monitors environmental
conditions and weather forecasts and uses the information to schedule winter maintenance
activities, determine the appropriate snow and ice control response, and track and manage
response operations.
MC07: Roadway Maintenance and Construction - This market package supports numerous
services for scheduled and unscheduled maintenance and construction on a roadway system or
right-of-way. Maintenance services would include landscape maintenance, hazard removal
(roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass
cutting), and repair and maintenance of both ITS and non-ITS equipment on the roadway (e.g.,
Concept of Operations
(Appendix a)
Appendix O page 87
PennDOT Statewide ATMS Software Concept of Operations, Rev. 5
signs, traffic controllers, traffic detectors, dynamic message signs, traffic signals, CCTV, etc.).
Environmental conditions information is also received from various weather sources to aid in
scheduling maintenance and construction activities.
MC08: Work Zone Management - This market package manages work zones, controlling traffic
in areas of the roadway where maintenance, construction, and utility work activities are
underway. Traffic conditions are monitored using CCTV cameras and controlled using dynamic
message signs (DMS), Highway Advisory Radio (HAR), gates and barriers. Work zone
information is coordinated with other groups (e.g., ISP, traffic management, other maintenance
and construction centers). Work zone speeds and delays are provided to the motorist prior to
the work zones. This market package provides control of field equipment in all maintenance and
construction areas, including fixed, portable, and truck-mounted devices supporting both
stationary and mobile work zones.
MC10: Maintenance and Construction Activity Coordination - This market package supports the
dissemination of maintenance and construction activity to centers that can utilize it as part of
their operations, or to the Information Service Providers who can provide the information to
travelers.
Concept of Operations
(Appendix a)
Appendix O page 88
APPENDIX P
STATEWIDE ATMS SOFTWARE
SYSTEM REQUIREMENTS
PennDOT Statewide ATMS
Software System Requirements
Last Updated: 04/08/11
Version: 7.3
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
TABLE OF CONTENTS
1.0
DOCUMENT HISTORY .................................................................................................. 1
2.0
PURPOSE OF THE DOCUMENT .................................................................................. 2
3.0
SCOPE OF PROJECT ................................................................................................... 2
4.0
REFERENCED DOCUMENTS ....................................................................................... 4
5.0
BACKGROUND.............................................................................................................. 4
6.0
CONCEPT FOR THE PROPOSED SYSTEM ................................................................. 4
6.1.
6.2
6.3
6.4
6.5
ENHANCE AND EXPAND EXISTING PENNDOT ATMS SOFTWARE................... 5
MANUFACTURER’S SOFTWARE.......................................................................... 5
NEW CUSTOM ATMS SOFTWARE ....................................................................... 5
EXISTING ATMS SOFTWARE PACKAGES (AS-IS) .............................................. 5
EXISTING ATMS SOFTWARE PACKAGE (PLANNED ENHANCEMENTS) .......... 6
7.0
USER-ORIENTED OPERATIONAL DESCRIPTION....................................................... 6
8.0
SYSTEM OVERVIEW .................................................................................................... 7
9.0
OPERATIONAL ENVIRONMENT ................................................................................... 7
10.0
SUPPORT ENVIRONMENT ........................................................................................... 7
11.0
REQUIREMENTS .......................................................................................................... 8
11.1
HIGH LEVEL BUSINESS REQUIREMENTS .......................................................... 8
11.1.1.
Detail Level Business Requirements ..............................................................11
11.2
SYSTEM REQUIREMENTS ..................................................................................13
11.2.1
PERFORMANCE REQUIREMENTS..................................................................13
11.2.2
INTERFACE REQUIREMENTS .........................................................................16
11.2.3
HMI REQUIREMENTS.......................................................................................19
11.2.4
DATA REQUIREMENTS....................................................................................21
11.2.5
ENABLING REQUIREMENTS ...........................................................................22
11.2.6
FUNCTIONAL REQUIREMENTS ......................................................................25
11.3
PERFORMANCE MEASURES ..............................................................................37
12.0
VERIFICATION METHODS...........................................................................................37
13.0
SUPPORTING DOCUMENTATION ..............................................................................39
14.0
TRACEABILITY MATRIX...............................................................................................39
i
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
LIST OF APPENDICES
APPENDIX A: GLOSSARY
APPENDIX B: SAMPLE GRAPHIC REPRESENTATIONS OF THE RECOMMENDED
PERFORMANCE METRICS
APPENDIX C: ATMS FLOW DIAGRAM
i
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
1.0 DOCUMENT HISTORY
This section has been intentionally left blank.
Appendix P – page 1 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
PURPOSE OF THE DOCUMENT
The purpose of this document is to describe the Functional Requirements for the Pennsylvania
Department of Transportation (PennDOT) Statewide Advanced Traffic Management System
(ATMS) Software.
The Stakeholders have identified specific requirements and tasks that an ATMS software must
be able to perform for PennDOT. The purpose of this document is to describe the functionality
necessary to perform the required tasks as a guide for future verification and testing. The
document includes both functional and system requirements. The functional requirements detail
the particular behaviors that the ATMS software shall perform; whereas the system
requirements include performance, interface, HMI, data and enabling requirements that are
crucial to developing an ATMS software that is compatible with PennDOT standards.
Therefore, at a minimum, all of the requirements listed within this document need to be
incorporated into a successful ATMS package.
The following are included in this document:
1. Document History
2. Scope of Project
3. Referenced Documents
4. Background
5. Concept for the Proposed System
6. User-Oriented Operational Description
7. System Overview
8. Operational Environment
9. Support Environment
10. Requirements
11. Verification Methods
12. Supporting Documentation
13. Traceability Matrix
2.0 SCOPE OF PROJECT
The ATMS software will enable operators to more efficiently manage surface transportation
while also providing a more effective response to incidents. The ATMS software will allow for
efficient communication between Districts, states and other stakeholders and provide shared
control of all existing and future intelligent transportation system (ITS) devices throughout the
Commonwealth of Pennsylvania.
PennDOT operates six (6) district traffic management centers (TMCs), three (3) regional traffic
management centers (RTMCs) and PennDOT’s Central Office. Each district contains different
equipment and runs separate control software. Currently, each of the facilities functions
independently.
Appendix P – page 2 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
It is the intent that the ATMS software will be designed for full functionality. However, user and
site access may vary. Therefore, TMCs will be able to turn off functionality that they do not
need. Also, the ATMS software will allow for interagency coordination. It is anticipated that
through the use of administration and maintenance, functionality can be tailored to the needs of
different user groups.
The primary users of the Next Generation ATMS are PennDOT’s TMCs and RTMCs. These
primary stakeholders will have read-write access to the ATMS according to the ATMS User
privileges defined by PennDOT. It is anticipated that the other identified potential stakeholders,
will initially have one-way communication with the ATMS. For example, video feeds may be
shared with the following stakeholders:
1. City of Philadelphia
2. City of Pittsburgh
3. Counties
4. Delaware Department of Transportation
5. Delaware River Joint Toll Bridge Commission (DRJTBC)
6. General Public
7. Information Service Providers
8. Maryland State Highway Administration (MDSHA)
9. Municipalities
10. New Jersey Department of Transportation (NJDOT)
11. New York State Department of Transportation
12. Ohio Department of Transportation
13. Pennsylvania Department of Transportation (PennDOT)
14. Pennsylvania Emergency Management Agency (PEMA)
15. Pennsylvania State Police (PSP)
16. Pennsylvania Turnpike Commission (PTC)
17. Regional Media
18. Special Events
19. Traffic.com
20. TrafficLand
21. Telvent/Inrix (PennDOT 511 System)
22. US Coast Guard
23. West Virginia Department of Transportation
Note: Other toll bridge authorities that interface with Pennsylvania highways (i.e. Delaware River
Port Authority, Burlington County Bridge Commission) were not included in the Regional ITS
Architectures; therefore, they were not included in this draft.
A complete ATMS system consists of a communication network, field devices, hardware and
software. While each of these components is critical to the successful operation, the focus of
this document will be the operational requirements of the ATMS software.
Appendix P – page 3 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
3.0 REFERENCED DOCUMENTS
•
PennDOT Statewide ATMS ITS Architecture, Rev. 1; April 9, 2010
•
PennDOT Statewide ATMS Software Concept of Operations, Rev. 4; October 15, 2010
•
•
Systems Engineering Guidebook for ITS, Version 2.0
IEEE STD 1512 Systems Engineering Process
•
National ITS Architecture (http://www.iteris.com/itsarch/)
•
PennDOT Bureau of Planning & Research
(http://www.dot.state.pa.us/Internet/Bureaus/pdPlanRes.nsf/PlanningAndResearchHome
Page?OpenFrameset)
•
DVRPC Regional Integrated Multi-modal Information Sharing
(http://www.dvrpc.org/transportation/longrange/its/rimis.htm)
•
RCRS = Road Condition Reporting System
(http://www.geodecisions.com/projectdetail.aspx?ProjectID=41102B)
•
PennDOT AVL Study: As-Is To-Be Business Process and Requirements Document
Version 3.01
•
US Department of Transportation, Federal Highway Administration Office of Highway
Policy Information, Traffic Monitoring Guide; May 1, 2001
4.0 BACKGROUND
PennDOT has been at the forefront of Intelligent Transportation Systems (ITS) deployments
since 1990. During this time there have been several deployments of ATMS software packages
and vendor provided software for the command and control of ITS field devices. In the past
PennDOT has used a variety of methods to procure ITS software to control field devices. As a
result, PennDOT currently has several independent and incompatible vendor provided software
and ATMS systems across the Commonwealth.
5.0 CONCEPT FOR THE PROPOSED SYSTEM
A number of alternative concepts were considered before identifying the proposed approach.
The following potential solutions were considered:
1. Enhance and expand existing PennDOT ATMS software;
2. Use manufacturer’s software for ITS equipment control;
Appendix P – page 4 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
3. Develop a new custom ATMS software;
4. Procure an existing ATMS software package to be used as-is; and
5. Procure an existing ATMS software package with planned enhancements /
modifications.
5.1. ENHANCE AND EXPAND EXISTING PENNDOT ATMS
SOFTWARE
Some Districts currently use ATMS systems to provide centralized control. The existing ATMS
software was examined and found to be lacking in several key areas. The primary weakness,
which ultimately led to the current decision, was that the software lacked any up to date
documentation. In addition, it was estimated that more than 30 percent of the software would
need to be retooled. Making significant modification to a poorly documented software package
has a low probability of success and is not recommended.
6.2
MANUFACTURER’S SOFTWARE
Some Districts operate using a number of independent software packages which were provided
by the device manufacturers along with the installation of their ITS equipment. At District 8-0 for
example, they use approximately six (6) to eight (8) separate software packages to control
dynamic message signs (DMS), Highway Advisory Radio (HAR), Video, etc. While this
represents the lowest investment to obtain basic functionality, the complexities of multiple
systems create inefficiencies and limits sharing information between TMCs to verbal
communication. Additionally, operators must be trained on several systems. And, finally, it is
not possible to provide a consistent, automated response to incidents when using disparate
systems.
6.3
NEW CUSTOM ATMS SOFTWARE
Designing and developing a custom ATMS software was strongly considered as an alternative.
A significant positive aspect is that PennDOT could specify the exact software needs and retain
total ownership of the software product. Potential negative aspects of this approach include
extending the implementation schedule (at least six months to one year would be needed just
for design) and significant (twice or more) cost increase. While we recommend that additional
primary research is completed through direct interaction with potential vendors, our secondary
research indicates that there are several fully developed ATMS software packages that could
meet 70 percent or more of the project goals, immediately.
6.4
EXISTING ATMS SOFTWARE PACKAGES (AS-IS)
Several existing ATMS software packages were examined and compared to the Use Case
Scenarios described in this Concept of Operations. While some packages seem to meet many
of the basic needs, it was not clear if any existing ATMS software packages met all of
PennDOT’s goals. Further, our research and experience shows that existing ATMS software
packages do not exist in the pure sense since each installation has unique needs. In our
opinion, existing ATMS software package implies that each installation uses the same software
Appendix P – page 5 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
and that the software can be installed by an end user. Our research indicates that the vast
majorities of ATMS installations have customized software and require significant time by the
vendor on-site to configure the installation.
6.5
EXISTING ATMS SOFTWARE PACKAGE (PLANNED
ENHANCEMENTS)
In reviewing the alternatives, it is our opinion that this option represents both the best value for
PennDOT and the highest probability of success. Our preliminary research indicates that
several vendors have existing ATMS software that appears to meet 70 percent or more of the
requested functionality. This approach has the dual key advantages of both utilizing a product
which is based on a proven solution, and providing the foundation for enhancements to meet
the PennDOT specific requirements. The only pitfall of this approach lies with potential legal
issues surrounding intellectual property (i.e. licenses, ownership, etc). However, due to the
number of states following this approach it is our belief that by involving PennDOT’s legal
department early in the procurement process, this potential issue can be managed.
6.0 USER-ORIENTED OPERATIONAL DESCRIPTION
PennDOT currently has various ATMS software deployed throughout the Commonwealth. In
general, this software allows operators to perform the following basic tasks:
•
•
•
Track and manage incident and event information;
Advise the public of incidents (VMS, HAR, Internet); and
View current traffic conditions (CCTV, Vehicle Detectors).
Currently, limited information is exchanged between Districts. Typical stakeholders include
traffic operation and maintenance personnel. These personnel typically are computer literate,
but have limited training on both software development and/or network design.
Additional information is available in the Concept of Operations document referenced above.
Appendix P – page 6 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
7.0 SYSTEM OVERVIEW
The final system will be used by one (1) to twelve (12) people at each District, 365 days per
year, 24/7. Users shall be capable of simultaneously accessing any element of the system that
they have the privilege to access. Some critical elements of this design will include:
•
•
•
•
•
•
•
•
•
•
•
Detailed system documentation, including a user interface design, database design;
A modular design, based on well defined and open interfaces;
Modules can be installed, removed, activated or deactivated without affecting other
running modules;
The interface between modules shall be well defined and open;
Web Based Operator Interface;
Scalable, expandable design;
Utilize Windows or Linux based hardware;
Adhere to the latest industry standards;
Follow the SIE CMMI model;
Follow the regulations set forth in the Right-to-Know Law Policy effective January 1,
2009; and
Adhere to the rules established by the Information Technology Bulletin (ITB).
8.0 OPERATIONAL ENVIRONMENT
The operational environment of the new system will consist of a central database located at the
Pennsylvania Department of Transportation (PennDOT) Central Office in Harrisburg. The
system will improve statewide coordination by providing a statewide platform to enable the
information flow to and from all Districts. Additionally, a centralized database will improve data
consistency and provide statewide reporting capabilities.
9.0 SUPPORT ENVIRONMENT
It is anticipated that each District will have technical resource personnel who will receive basic
troubleshooting training on database and computer networks. This will be supplemented by
staff at the Central Office. The selected Contractor will assume the primary support role for the
custom application, where Central Office will assist with general hardware and software repairs.
Continued maintenance and support is to be provided by the Contractor software development
company that designs the statewide ATMS software.
Appendix P – page 7 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
10.0 REQUIREMENTS
11.1 HIGH LEVEL BUSINESS REQUIREMENTS
The business requirements were developed as part of the systems engineering process for the
Statewide ATMS ITS Architecture. The business requirements describe in business terms what
must be delivered or accomplished to provide value. The scenarios developed and agreed
upon during the Concept of Operations (Rev. 4 dated October 15, 2010) were used to develop
the business requirements, and the traceability from the scenario number to the business
requirement is shown in the table below. Additionally, each business requirement is mapped to
project Goals and Objectives in the Traceability Matrix (Appendix X of the RFP).
Since this document focuses on needs that were identified as fundamental to the
implementation of ATMS software, the business requirements are focused on the initial
deployment (I) or Phase 1-3 project activities and are deemed necessary. The future
deployment (F) activities will be part of Phase 4 of the project.
ID
BR01
TITLE
Reliable
BR02
Detect Traffic
Issues
BR03
Response
BR04
BR05
Statewide
Coordination
Interoperable
BUSINESS REQUIREMENT
DESCRIPTION
The ATMS software shall be
designed to run 24 hours a day, 7
days a week, 365 days a year.
Utilizing real time vehicle detector
and vehicle probe data, the
ATMS software shall
automatically alert operators of
potential traffic problems quickly.
CCTV will be used to verify
potential traffic problems. Alerts
may include but not be limited to
audible, visual and text/email.
PennDOT needs to provide
consistent and planned
responses to planned and
unplanned events.
PennDOT needs a Statewide
platform which will provide the
means for information to flow to
and from all Districts.
PennDOT must be able to
transfer control of TMCs and
equipment between Districts and
other stakeholders identified as
redundant locations, such as
PennDOT Central Office.
Appendix P – page 8 of 40
CONOPS
SCENARIO
Phases
Criticality
and
Priority
11
I
Crucial,
High
7, 8, 11, 12,
24, 48
I and F
Crucial,
High
8, 9, 15, 16,
20, 21, 25,
26, 43
I and F
Crucial,
High
8, 13, 16,
21, 24, 25,
26, 33, 34,
43
I and F
Crucial,
High
5, 10, 14,
17, 22
I
Crucial,
High
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
ID
BR06
BR07
BR08
TITLE
Secure
Real-time Data
Incidents
BR09
Administration
BR10
Traffic Planning
BR11
Information to
the Public
BR12
Information to
Partners
BR13
User Interface
BUSINESS REQUIREMENT
DESCRIPTION
The ATMS software shall provide
secure access for all approved
users and stakeholders.
PennDOT must be able to collect,
maintain and display real-time
data from field devices and
external sources.
PennDOT must be able to
manage incident activities from
detection to resolution.
PennDOT must have the ability to
administer and maintain the
system. This includes adding
new devices, troubleshooting the
system, system backups,
archiving data, purging data, and
user and user group
maintenance.
PennDOT shall be able to easily
access and utilize all collected,
stored and archived traffic data
for traffic planning purposes (e.g.
developing diversion routes and
response plans).
PennDOT must be able to
disseminate traffic information,
including travel times, to the
traveling public via 511, HAR and
VMS.
PennDOT needs to provide
partners with accurate real-time
information to improve incident
response and coordination.
Information shall meet current ITS
standards (NTCIP, TMDD and
C2C) and any additional ITS
standards that are established by
PennDOT’s Intelligent
Transportation Program.
Traffic and equipment conditions
will be viewable and controllable
via a GIS map. Other
alternatives, such as tables and
tree views, shall be provided.
Appendix P – page 9 of 40
CONOPS
SCENARIO
Phases
Criticality
and
Priority
1, 2, 3, 4, 47
I
Crucial,
High
11, 19, 27,
30, 37, 52
I and F
Crucial,
High
7, 8, 11, 12,
15, 16, 20,
21, 24, 36
I
Crucial,
High
1, 2, 3, 4
I
Crucial,
High
8, 9, 11
I and F
Crucial,
High
8, 15, 16,
18, 19, 20,
21, 26, 36,
48, 52
I and F
Crucial,
High
11, 16, 21,
36, 37
I and F
Crucial,
High
11, 16, 21,
24, 27, 36,
37, 46, 50
I and F
Crucial,
High
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
ID
BR14
BR15
BR16
BR17
BR18
TITLE
Performance
Measures
Asset
Management
Maximize
Existing
Software
ITB
Video Sharing
BR19
Robust
Solution
BR20
Configuration
Management
BUSINESS REQUIREMENT
DESCRIPTION
PennDOT must be able to utilize
collected data to generate
measurable performance metrics
and reports. All data, excluding
video, must be stored indefinitely.
PennDOT shall be able to view
current and historical status of
field devices (CCTV, HAR, VMS,
detectors, etc.). In addition, a
trouble ticket system,
maintenance log, preventative
maintenance system and a
maintenance contractor tracking
system shall be provided.
PennDOT must be able to use the
ATMS to interface with
PennDOT’s existing software
systems, including, but not limited
to the Road Condition Reporting
System (RCRS), HOV, Signal
System, Emergency Pre-Emption,
Transmit, High Winds, Anti-Icing,
Truck Rollover, Ramp Meters,
Pump Station Monitoring, Queue
Detection, INRIX, GATIR (or
current AVL solution), and the
Platinum (HAR) Software.
The ATMS must be compliant
with all of PennDOT’s ITBs, SOPs
and ITS policies and guidelines.
The ATMS software solution shall
be capable of presenting video
available through PennDOT’s
video sharing solution.
The ATMS software solution shall
be secure, scalable, reliable,
available (24x7), redundant,
flexible, easy to maintain and
provide interoperability.
The ATMS Contractor shall
employ a thorough Configuration
Management process and
provide District-level specifics in
terms of configuration and
recovery procedures and
Appendix P – page 10 of 40
CONOPS
SCENARIO
Phases
Criticality
and
Priority
11, 24
I
Crucial,
High
15, 16
I and F
Crucial,
High
11, 25, 26,
27, 37, 52
I and F
Crucial,
High
All
I and F
Crucial,
High
7, 10, 11,
12, 13, 24,
25, 28, 33,
34,
I and F
Crucial,
High
All
I and F
Crucial,
High
All
I
Crucial,
High
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
ID
BUSINESS REQUIREMENT
DESCRIPTION
TITLE
CONOPS
SCENARIO
Phases
Criticality
and
Priority
All
I
Crucial,
High
All
I
Crucial,
High
processes.
BR21
BR22
10.1.1.
Change
Management
Deployment
Management
The ATMS Contractor shall
employ a rigorous Change
Management process. This
process shall address project
change control related, but not
limited to, requirements,
schedule, and resources,
covering the entire change
management life-cycle.
The ATMS Contractor shall
provide deployment deliverable(s)
which address Concept of
Operations traceability,
requirements traceability,
scheduling, testing, rollback
procedures, and user acceptance
of the system.
Detail Level Business Requirements
This section defines the business terms relevant to the solution. Business terms should include
definitions of data elements important to the business whether they are provided on a form used by the
business or entered into a system, names of other organizations that are important to the business area,
names of systems and other equipment used by the staff, and other relevant terms.
Business Terms Glossary
REQ. ID
(from High
Level table)
BUSINESS
TERM
ALL Business
Requirements
ACRONYM OR
ABBREVIATION
DEFINITION
Acronyms and
Abbreviations
All Acronyms and abbreviations used within the
High Level Business Requirements are
Documented in Appendix A: Glossary.
BR02
Operator
Primary handler who monitors real-time traffic
condition and status, and manages dispatch of
and communication with Service Patrol vehicles,
rd
main point of contact for traffic updates to 3
Parties
BR04, BR05
District
11 unique PennDOT Engineering Districts, each
containing multiple counties.
BR07
Real time data
Data that is no more than 5 seconds old from
the time that the ATMS solution receives the
Appendix P – page 11 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
data.
BR11
511
Statewide phone and web-based traveler
information system.
BR12
Intelligent
Transportation
Use of electronics, communications or
information processing to improve the efficiency
or safety of highway surface transportation.
BR12
Intelligent
Transportation
Program
Department wide Program which provides
communication and collaboration between
Intelligent Transportation projects.
BR03, BR04,
BR05, BR07,
BR08, BR10,
BR11, BR14,
BR16
PennDOT
The operators and managers whose duties are
involved with maintenance, incident response,
traffic management, and the IT support staff
supporting them.
BR12
(Business)
Partners
All potential outside partners / business
partners, including but not limited to Media
Partners, MPOs/RPOs, etc.
BR16
Signal System
A signal system can be defined as either a 5
traffic signal system connected together or 1
system having 5 traffic signals connected
Appendix P – page 12 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2 SYSTEM REQUIREMENTS
Within the subsequent tables each system requirement is mapped to the business requirements
from the preceding section. Therefore each system requirement inherently is mapped to
Concept of Operations scenarios as per the Traceability Matrix (Appendix P of the RFP).
11.2.1
PERFORMANCE REQUIREMENTS
The performance requirements include specific details about how well the ATMS software
should perform. For example, usability, system availability, and reliability are considered
performance requirements.
The following performance requirements are considered the minimum criteria that an ATMS
software must meet in order to sufficiently satisfy the needs of PennDOT:
Appendix P – page 13 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
PERFORMANCE REQUIREMENT DESCRIPTION
Real-time is defined as data that is no more than 5 seconds old from
the time that the ATMS solution receives the data. The ATMS
software shall display data in real-time.
PR
BR
PR01
BR07
PR02
BR17, BR18
The ATMS software shall support display of streaming video at 21 to
150 kilobits/second.
PR03
BR07, BR15
The ATMS software shall process and display ITS field device status
in real-time.
PR04
PR05
BR14, BR15
BR07, BR15
PR06
BR07, BR15
PR07
BR14, BR07,
BR11,
PR08
PR09
BR01, BR08
BR07, BR19
PR10
BR02,
BR07
PR11
BR07
The ATMS software shall screen data transmitted from field sensor
devices to verify its accuracy. Should data fall outside of the
acceptable range, the ATMS software shall alert the user and log the
alarm.
The ATMS software shall be capable of polling (i.e. issuing a remote
request for information) the current status of any ITS field device. The
time from when an ITS device issues the response to the ATMS
displaying that information on the user's workstation shall be less than
5 seconds.
The ATMS software shall be able to receive an unsolicited
communication from any device containing notification of a malfunction
involving that device. (i.e. SNMP trap from DMS)
The ATMS software shall process detection data in real-time, providing
roadway congestion information for data distribution.
The ATMS software shall be designed and configured to support a
continuous operation. Continuous is defined as to support a 24 hours
a day, 7 days a week, 365 days a year. There shall be no scheduled
downtime.
The ATMS software shall be capable of maintaining the performance
level described with following number of devices:
- 2,000 CCTV
- 2,000 DMS
- 2,000 Vehicle detector stations
- 600 Ramp Meters
- 6,500 Signal Systems (covering over 13,000 signals)
(Numbers reflect no less than 100% growth over the next 5 years from
the current installed base.)
The ATMS software map will display updates in less than 1 second to
user commands (regardless of the zoom, pan, etc.).
The ATMS software shall not create additional lag time to sending or
receiving data from the field devices (i.e. CCTV and DMS).
Appendix P – page 14 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
PR
BR
PR12
BR07, BR11,
BR15
PR13
PR14
BR01, BR19,
BR22
BR01, BR19,
BR22
PR15
BR15
PR16
BR01
PERFORMANCE REQUIREMENT DESCRIPTION
The ATMS software shall be capable of receiving communication and
issuing commands to all field devices in the system, regardless of
device manufacturer.
The ATMS software solution must not be taken offline during
scheduled maintenance and must be designed as a redundant system
that can have upgrades, OS changes, etc. implemented first on one
portion of the platform and then the other, without the application going
offline.
The ATMS software solution must not undergo non-critical
maintenance during a major winter event or traffic management
incident. A documented process for obtaining PennDOT clearance to
perform non-critical maintenance prior to start must be provided by the
Contractor.
The ATMS shall be capable of communicating with devices regardless
of the communication medium. For example, the same manufacturer’s
DMS may use dial-up in one district, serial communication in another,
and TCP/IP at another.
The ATMS shall be designed and configured to work with the Systems
Center Operations Manager (SCOM) to monitor system performance.
Examples of monitoring include but are not limited to: CCTV camera
feed connectivity, ATMS specific Windows service(s), DMS
connectivity, log file(s) and any other piece of ATMS deemed essential
to the continuous operation of ATMS.
Appendix P – page 15 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.2
INTERFACE REQUIREMENTS
The interface requirements detail how the ATMS software should interact with other PennDOT
systems, such as RCRS and the AVL system.
The following interface requirements represent the minimum conditions that the ATMS software
must meet in order to sufficiently satisfy the needs of PennDOT:
IR
BR
IR01
BR10,
BR11,
BR15, BR16
IR02
BR02,
BR04,
BR07, BR17
IR03
BR02,
BR04,
BR07, BR16
IR04
IR05
IR06
BR16
BR16
BR05
INTERFACE REQUIREMENT DESCRIPTION
The ATMS shall provide the ability to share data communicated from
ITS field devices with other PennDOT software systems that require
such data for purposes of congestion management, incident
management, asset management, emergency management, or other
valid applications. This data includes current / historic data and
operational status of all devices.
The import/export feature shall accept/transmit data in a traffic
management data dictionary (TMDD) compliant format, or some other
open standard which must meet PennDOT approval.
Data received from external sources shall be available to the operator to
be integrated with traffic volume and speed data collected from other
PennDOT vehicle detection systems.
Individual steps in a response plan shall have the ability to access preplanned route data from RCRS, and potentially other data systems, to
provide information or instruction to the operator. Pre-planned routes
will be imported for Phase 1.
RCRS will be the primary means to enter incident data. ATMS software
will display incident locations on map and suggest response plans to
operators based on incident location, duration and severity.
Any user with proper privileges on the PennDOT network will have
access to complete functionality including the control of all equipment
and the ability to print any report from data in the ATMS software.
The ATMS software shall be able to receive all available status and data
from all capable field devices listed in the attached PennDOT ITS
Equipment Inventory (Appendix J of the RFP).
IR07
BR15
IR08
BR02,
BR04,
BR07, BR17
IR09
BR05, BR09
BR15
The ATMS software shall provide the administrator with the ability to
make configuration changes to support equipment changes.
IR10
BR11, BR16
The ATMS software shall provide DMS information to the 511 system.
DMS information shall include:
• DMS ID
The data retrieved from the field device in response to a current status
request will comply with relevant NTCIP data definition and format
standards, to the extent that the device is capable.
Appendix P – page 16 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
IR
BR
IR11
BR16
IR12
BR16
INTERFACE REQUIREMENT DESCRIPTION
• Message
• Message Activation Time
• Message Deactivation Time
• Message Priority Level
The ATMS software shall be capable of receiving detector and probe
data from PennDOT’s real-time traffic detector partners (such as INRIX
and traffic.com).
The ATMS software shall receive status information (Active, Off, or
Error), at a minimum, from the following systems:
• Traffic Signal Systems (Districts 2-0 & 9-0)
• Truck Roll Over System (District 12-0)
• Truck Runaway System (District 9-0)
• Low Visibility (District 9-0)
• High Winds Detection System (District 9-0)
• HOV / Gate Control (District 11-0)
The ATMS software will allow for one-way communication with these
systems. The ATMS software will receive basic alerts and monitoring
information that will be displayed on the ATMS software map.
IR13
BR16
IR14
BR16
IR15
BR16
The ATMS software shall retain existing Highway Advisory Radio (HAR)
and Beacon Control functionality currently available through the
Platinum Software. Full control/viewing capabilities of all aspects of the
existing HAR module must be replaced or integrated into the Statewide
ATMS System.
The ATMS software shall receive pre-planned route data from RCRS.
The ATMS software shall display the detour information as a layer on
the Map.
The ATMS software shall allow for future integration of any or all of the
following systems:
• APRAS (Automated Permit Routing/ Analysis System)
• ATR
• Bluetooth Travel Time
• CAD – 911 (Computer Aided Dispatch)
• IDRum (Interactive Detour Route and Mapping)
• RIMIS (Regional Integrated Multimodal Information Sharing)
• STIP (Standalone Count Station)
• WIM (Weight in Motion)
• I-83 Queue Detection System
• Emergency Pre-emption
• CAVC (Continuous Automated Vehicle Classification)
• Ramp Meters
• MDSS (Maintenance Decision Support System)
• RWIS (Roadway Weather Information System)
• AVL (Automatic Vehicle Location)
• Pump Station Monitoring System
• Anti-Icing System
• Crash Avoidance System
Appendix P – page 17 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
IR
BR
INTERFACE REQUIREMENT DESCRIPTION
IR16
BR16
The ATMS software shall be capable of sending messages via pagers,
phones and e-mail.
IR17
BR16
IR18
BR16
IR19
BR09
The ATMS software shall retain existing HOV module functionality. Full
control/viewing capabilities of all aspects of the existing HOV module
must be replaced or integrated into the Statewide ATMS System. This
includes, but is not limited to, opening/closing of the gates, changing the
HOV sign status, changing Lane Control Sign status, and detecting
wrong way vehicles.
(Note: currently HOV module communicates with the administration and
alarm subsystems in existing District 11 ATMS).
The ATMS software shall provide access to the HOV module from all
workstations at the RTMC (the module should be accessible from the
same workstations that access the new Statewide ATMS solution).
The system will interface with CA SiteMinder tool suite to leverage
CWOPA credentials for user authentication, authorization and user
administration.
Appendix P – page 18 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.3
HMI REQUIREMENTS
The HMI requirements describe how the Human Machine Interface (HMI) should respond and
interact with the Operator.
The following HMI requirements represent the minimum conditions that the ATMS software
must meet in order to sufficiently satisfy the needs of PennDOT:
HR
HR01
BR
BR13
HR02
BR13
HR03
BR14,
BR15
HR04
BR13
HMI REQUIREMENT DESCRIPTION
At a minimum the following data elements shall be separate layers on the
ATMS software user map interface:
- State Routes,
- Local Routes,
- Road Classification,
- Equipment Status,
- Active RCRS Events selectable by event status as unique layers,
- Planned Events,
- Each equipment type shall have a separate layer,
- PennDOT Snow Routes
- 511 Routes
- Road Condition reporting emergency routes
Each layer can be turned on or off by the operator.
The ATMS software map shall have icons positioned to indicate the
location of each field device. The device icons should look like the
respective devices as per PennDOT preference, or another visual
differentiation approved by PennDOT.
The ATMS software shall provide an interface for the user to list inventory
of all available field devices. User can filter the list based on the device
type, sub-type or corridor.
The ATMS software shall allow a user to activate control of a device by
selecting it on the user interface. The complete device details shall also
be displayed.
The ATMS software shall provide four equipment status types: standby
(outlined in green), active (solid green), warning (solid yellow), and out of
service (solid red).
HR05
BR07,
BR13
HR06
BR13
Standby = device is functioning by not currently being used
Active = device is operating normally
Warning = device is usable but has limited functionality and will require
TMC staff field investigation and possibly maintenance contractor
response. (a CCTV with video up but
no zoom or pan/tilt functions; a DMS with a pixel error)
Out of Service = device is currently off-line, not usable and has a
plan/needs a plan in place for resolving the issue
The ATMS software shall allow the operators to configure the color of
incident and device icons.
Appendix P – page 19 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
HR
HR07
HR08
BR
BR13
BR13
HR09
BR13
HR10
BR13
HR11
BR16
HR12
BR02,
BR05,
BR13
HR13
BR04,
BR05,
BR13
HR14
BR13,
BR16
HR15
BR06,
BR13
HR16
BR13
HR17
BR09
HR18
BR02,
BR07
HMI REQUIREMENT DESCRIPTION
The ATMS software shall display the active incident information, CCTV
snapshots and DMS and HAR messages by hovering over a device or
displaying all active DMS, HAR and CCTV.
The ATMS software map shall provide an optional layer based on the
standard PennDOT type 10 map which can be turned on or off by the
operator.
The roadway network shown on the ATMS software map shall be based
on PennDOTs roadway management system (RMS) used for all
PennDOT Geographical Information System (GIS) applications (ie.
RCRS roadway network).
The ATMS software map shall be based on Geographical Information
System (GIS) Technology. The map shall include mile markers and exit
numbers/names as a selectable layer.
The ATMS software shall facilitate displaying information from connected
systems. For example, the APRAS system will allow the user to view
roadway limitations like capacity (weight and height restrictions).
The ATMS software shall support dynamic scaling of all objects (menus,
text etc.) on Web page based on the screen resolution. The target is
1024 x 768.
The ATMS software shall provide a method for taking control / handoffs
of all TMCs equipment (DMS, CCTV & HAR) and open incidents / events.
For example, the ATMS shall allow the handoff of one, multiple or all
cameras in a District to another District. In addition, the ATMS software
shall support the transfer of all TMC functions to another TMC.
The ATMS software shall display all active events (RCRS data) on the
map. The ATMS software shall generate alerts of upcoming planned
events that have been entered into the RCRS system.
The ATMS software screens shall display the login name of the user who
is currently logged into the system.
The ATMS software shall display and provide access to Orthophotography.
All routine administrative tasks shall be accomplished using the ATMS
software user interface (i.e., no direct manipulation of the database,
configuration files, etc). System administrative tasks include, but are not
limited to, the addition of new ITS devices (where a device driver already
exists) and user group configuration.
Using data from vehicle detector and vehicle probe data sources, the
ATMS software shall display traffic speeds based on defined thresholds.
The speeds shall be displayed in various colors based on the defined
thresholds (i.e., green, yellow, red)
Appendix P – page 20 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.4
DATA REQUIREMENTS
The data requirements identify data elements and define the system.
The following data requirements represent the minimum conditions that the ATMS software
must meet in order to sufficiently satisfy the needs of PennDOT:
DR
BR
DR01
BR07, BR14,
BR17
DR02
BR02, BR14,
BR17
DR03
BR07, BR14,
BR17
DR04
BR07, BR14,
BR17
DR05
BR07, BR14,
BR17
DR06
BR14, BR17
DATA REQUIREMENT DESCRIPTION
The ATMS software shall have a database in which collected data and
system activity is automatically tracked and recorded.
The ATMS software shall recognize and record in the activity log all
proprietary warnings, alarms, and status transmissions from each
device.
The ATMS shall support an industry standard relational database
management system (RDMS), unless proven that a proposed
proprietary database is robust enough and meets the actual
functionality as documented within these requirements.
The ATMS software shall support importing and exporting of system
data. For example, data can be exported to Excel.
The ATMS software shall store data collected in a relational database
that can be accessed and queried to develop custom reports.
The ATMS software shall provide users the capability to export edited
vehicle classification data from detectors that are equipped for vehicle
detection. The edited vehicle classification data shall be in the format
specified in the Traffic Monitoring Guide (May 2001) representing the
13 vehicle classifications recommended by the FHWA.
The ATMS software shall record user entry and exits, and denial or
authorization of access to services. The ATMS shall log all user
activities.
DR07
BR14, BR17
DR08
BR14, BR17
Passwords, if stored within the ATMS software, are not in clear text,
but encrypted.
DR09
BR07, BR10,
BR14, BR16,
BR17
The ATMS software shall collect current and historical road
information from the sources listed in the interface section. This
information shall be used by the operator to more effectively manage
incidents and congestion.
DR10
DR11
BR03, BR14
BR09
The ATMS software shall allow for the collection and storage of
maintenance and construction information for use by operations
personnel or data archives in the region.
Error and log messages generated and stored by the ATMS software
solution are in clear plain text. For example, stored in a human
readable format and shall not use any cryptic information, i.e. instead
of “Error Code #N” state “Database Error”.
Appendix P – page 21 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
DR
DR12
BR
BR06, BR09
DR13
BR09
DR14
BR10, BR14
DR15
BR09
DR16
BR06, BR17
DR17
BR17
DR18
BR06, BR17
The ATMS software shall allow multiple people to work on the
application without adversely affecting one another. It provides the
ability to control who does what to a site by restricting capabilities
based on individual's roles.
The ATMS software shall have the ability to backup, purge and
restore the database and virtual system images in an automated
manner.
The ATMS software shall have the ability to store historical ITS
information for future analysis and reporting.
The ATMS software shall have multiple stages of archiving. A local
archive shall retain information for a user defined period of time, no
greater than 2 months. A permanent archive shall retain data in an
external network for a user-defined period of time.
The ATMS software shall use PennDOT authentication and as a user
store (CWOPA). The ATMS software shall utilize LDAP and/or
Siteminder for authentication.
The ATMS software solution shall be capable of transmitting
information, data and requests securely using 128 bit or 256 bit SSL
to department or external resources as required.
The ATMS software shall require a single user sign-on (support
LDAP) for the complete management of incidents and field devices.
The ATMS software shall be capable of assigning each user to a user
group or access level. An Administrator shall be capable of selecting
the access levels and functionality available to each user.
DR19
11.2.5
DATA REQUIREMENT DESCRIPTION
ENABLING REQUIREMENTS
The enabling requirements describe the means to operate the system.
The following data requirements represent the minimum conditions that the ATMS software
must meet in order to sufficiently satisfy the needs of PennDOT:
ER
BR
ER01
BR05, BR09,
BR12, BR17
ER02
BR05, BR09,
BR17
ER03
BR09, BR19
ENABLING REQUIREMENT DESCRIPTION
The ATMS software shall expose data (input and output) through Web
Services.
The ATMS software shall be modular and expose data (input and
output) through well defined API.
The ATMS software shall allow for the development of extensions to
the product using Java, C# or VB.NET.
Appendix P – page 22 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
ER
BR
ER04
BR07, BR17
ER05
BR17
ER06
ER07
BR17
BR09, BR17
ENABLING REQUIREMENT DESCRIPTION
The ATMS software shall be configured for 99.999% uptime.
All ATMS software components shall be cluster-able across multiple
servers.
The ATMS software shall support load-balanced Web farms for
maximum scalability and availability using any industry standard
software or a hardware-based load balancing technology. The ATMS
software needs to work with multiple web servers in a load balanced
manner. The ATMS software should not require Sticky sessions.
The ATMS software shall allow for the selective turn-on / turn-off
facilities (page, application, or data source level). The ATMS software
shall provide the ability to take application components offline without
affecting the server or requiring the shutdown of a node in the cluster.
The ATMS software shall provide automated restart and recovery
(application resiliency).
The ATMS software shall provide monitoring and logging capabilities
that can be configured to alert Operations of the operational status of
the application component.
ER08
BR17
ER09
BR17
The ATMS software shall work seamlessly with industry standard
clustering solutions for database high availability.
ER10
BR17
The ATMS software shall log system and portlet activity including
detailed bandwidth usage reports.
ER11
ER12
ER13
BR17
BR17
BR17, BR19
The ATMS software shall allow for all server software to run as a
service or component (i.e., does not require someone to log in at the
console and start up the application manually).
The ATMS software shall be able to start ATMS components in any
order (if a component is started or restarted, related systems will wait
rather than fail).
The ATMS software shall provide the ability to scale hardware
through direct support for multiple CPUs within the same physical
server.
The ATMS software shall provide the ability to deploy new
functionality and content into the production environment but still only
accessible to test users.
ER14
BR17
ER15
BR09, BR20,
BR22
The ATMS software shall allow the Commonwealth to be able to roll
back to previous states of the functionality (versions), once a version,
upgrade, patch or fix is deployed to production.
ER16
BR17, BR22
The ATMS software shall provide tools that can be published to
staging servers for testing prior to production.
Appendix P – page 23 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
ER
BR
ER17
BR17
ENABLING REQUIREMENT DESCRIPTION
The ATMS software shall provide tools that can be published to
multiple servers for site mirroring and replication.
ER18
BR09, BR17
The ATMS software shall allow for an open API to support automation
for deployment and configuration of product components.
ER19
BR17
The ATMS software shall be capable of being executed in a
virtualized deployment environment (e.g. VMWare).
ER20
BR09
ER21
BR09, BR19
ER22
BR09
ER23
BR17
ER24
BR17
The ATMS software shall provide the ability to support multiple
administrators across the Commonwealth (minimum of 20 concurrent
administrators.) This includes multiple logins per District to account
for shift changes and back up resources.
The ATMS Contractor shall work with the Department to establish and
shall follow disaster recovery procedures to have the application
restored again as soon as possible.
The ATMS software shall provide an automated process to
reload/recover the ATMS application code and related databases.
The ATMS software shall be a client / server architecture
implementing a thin-client, web-based user interface. No custom
software shall be required to be installed on operator workstations.
The ATMS software will support anti-virus software and be configured
to receive operating system security updates.
The ATMS software solution shall be compatible with existing
PennDOT servers, or
ER25
ER26
BR19
BR19
The Contractor shall provide a transition plan if the Contractor makes
recommendations of server changes, or total replacement of current
architecture.
The ATMS software shall provide the ability to support 100
simultaneous users. This includes multiple logins per District to
account for shift changes and back up resources.
Appendix P – page 24 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.6
FUNCTIONAL REQUIREMENTS
The functional requirements describe the tasks that the ATMS software must perform to provide
PennDOT with the functionality needed to perform daily routines. Functionality is identified by
the major ATMS software components.
11.2.6.1 Vehicle Detectors
FDC
BR
FDC01
BR02, BR13
FDC02
FDC03
FDC04
FDC05
FDC06
FDC07
FDC08
BR07,
BR10, BR12,
BR13, BR14
BR02, BR13
BR13
BR02
BR02, BR08
BR02
BR02
FUNCTIONAL REQUIREMENTS – VEHICLE
DETECTORS
The ATMS software shall have the ability to display
the alarm nature and location on a GIS based map
application.
The ATMS software shall receive the current data
transmission from each vehicle detector at regular
time intervals. The ATMS software shall also receive
vehicle probe data and other traffic data sources as
they become available.
The ATMS software shall maintain ranges of average
traffic speed to indicate four (4) levels of traffic flow:
Free Flowing, Slow, Congested and no information.
The ATMS software shall represent each vehicle
detector as a link on a GIS map which is color-coded
to indicate the traffic flow.
The ATMS software shall employ an algorithm to
evaluate vehicle detector data and determine the
presence of a potential incident.
Upon positive detection, the ATMS software shall
activate an alarm to alert the operator. Potential
incidents shall remain in a separate list and will not be
assigned as an incident until after positive
confirmation by an operator.
When a potential incident notification is triggered,
several selectable user actions within the ATMS
software shall be activated including aiming the
nearest CCTV camera in the direction of the sensor
that signaled the incident or moving video of the
nearest camera onto the video wall. The ATMS
software shall provide a mechanism to turn these
features on or off.
The ATMS software solution vehicle data shall include
volume, speed, classification and occupancy,
depending on the capabilities of the source element.
Appendix P – page 25 of 40
SCENARIO
24
11
11
11
11
24
24
11
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
FDC
BR
FDC09
BR07, BR16
FDC10
BR07, BR10
FUNCTIONAL REQUIREMENTS – VEHICLE
DETECTORS
The ATMS software shall integrate the data from all
sources listed under interface requirements to
compute and display current traffic conditions.
The ATMS software shall compare the real-time traffic
speed to the historic average traffic speed for that
time of day, day of week, day of month, holidays and
special events.
Appendix P – page 26 of 40
SCENARIO
11
11
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.6.2 CCTV
FCC
BR
FCC01
BR02,
BR08
FCC02
BR02,
BR08
FCC03
BR02,
BR08
FCC04
BR02,
BR08, BR18
FCC05
BR02,
BR08, BR18
FCC06
FCC07
BR02,
BR08
BR02,
BR08
FCC08
BR04, BR05
FCC09
BR04, BR05,
BR18
FCC10
BR02
FUNCTIONAL REQUIREMENTS - CCTV
The ATMS software shall allow Administrators to save
camera presets for each PTZ camera including a
location description. A preset camera position shall
consist of a pan angle, tilt angle, zoom setting, focus
setting and a title that is superimposed on the image.
The ATMS software shall allow at least 25 preset
camera positions for any Pan-Tilt-Zoom (PTZ)
camera.
The ATMS software shall support screen titles for at
least 16 zones for each PTZ camera, such that the
camera image displays the zone name whenever the
camera is aimed anywhere in the zone, unless the
camera has been commanded to a preset view.
The ATMS software shall be capable of accessing the
video stream of a camera from a designated video
distribution system where the ATMS software is
installed.
The ATMS software shall provide the user the ability
to select any camera view to be displayed on any
monitor controlled by the user’s video switch.
The ATMS software shall allow an authorized user to
control the camera by adjusting the camera’s pan, tilt,
zoom, presets, iris and focus controls in the current
view via joystick or keyboard, including but not limited
to joystick keyboard and virtual joystick/mouse control
The ATMS software shall provide an authorized user
the ability to create and edit video tours, consisting of
a sequence of feeds from various cameras, using
preset pan-tilt-zoom settings for each camera in the
sequence.
The ATMS software shall allow Operators to share
control of CCTV within a TMC. Share of control will
be based on a specified time-out period as well as
user level. A user with higher user privileges can
assume control from a user with lower privileges.
The ATMS software shall allow Operators to access
the designated video distribution system and block
video from view of selected outside sources.
When a potential incident notification is triggered, the
ATMS software solution shall aim the nearest CCTV
Appendix P – page 27 of 40
SCENARIO
7
7
7
12
12
12
12
13
33
24
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
FCC
BR
FUNCTIONAL REQUIREMENTS - CCTV
camera in the direction of sensor that signaled the
incident. The ATMS software shall provide a
mechanism to turn this feature on or off.
SCENARIO
11.2.6.3 Incident Management
FIM
BR
FIM01
BR03, BR10,
BR16
FIM02
FIM03
FIM04
FIM05
FIM06
FIM07
BR14
BR14
BR03
BR16
BR03
BR03, BR04
FUNCTIONAL REQUIREMENTS –
INCIDENT MANAGEMENT
The ATMS software shall allow Administrators to
utilize diversion routes from RCRS that are locationbased. Each route shall be color-coded based on the
location and direction as defined by PennDOT. By
selecting links and/or roadways that will be used as a
diversion route.
The ATMS software congestion metric computed shall
include, but not necessarily be limited to: Roadways
Congestion Index (RCI) (as defined by the Texas
Transportation Institute), Travel time, Travel time
index, Planning time index, Buffer index, Incident
Duration, and Segment delay.
The ATMS software congestion metric reporting shall
be available at the following levels: Segments,
Interstate/Freeway/State Road, Municipality, County,
District, and Statewide.
Where sufficient data is available, the ATMS software
shall classify delay time according to current RCRS
nomenclature.
The ATMS software shall display RCRS incident and
condition information in the ATMS software and on the
ATMS Map.
The ATMS software shall notify the operator when
pre-planned detour routes are compromised by
routine maintenance or other activities.
The ATMS software shall allow Administrators to
create and manage a contact list and schedule.
Based on working and non-working shift, available
personnel will be displayed.
Appendix P – page 28 of 40
SCENARIO
9
24
24
25
11
28
43
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.6.4 Response Plans
FRP
BR
FRP01
BR03,
BR04, BR08,
FRP02
FRP03
FRP04
BR03, BR10
BR03, BR08
BR03, BR08,
BR11
FRP05
BR03
FRP06
BR03
FRP07
BR03
FRP08
BR03
FRP09
BR03
FRP10
BR03, BR08
FUNCTIONAL REQUIREMENTS –
RESPONSE PLANS
The ATMS software shall allow for center-based
capability to formulate an incident response that takes
into account the incident duration, total road and lane
closures.
The ATMS software shall enable the user to define
“response plans” that utilize any combination of
devices and order of activation to automatically
respond to an incident or any event.
The ATMS software response plans shall consist of a
pre-programmed sequence of suggested Operator
actions devised as a standard response to a particular
type of event.
Individual steps in the ATMS software response plans
shall have the ability to activate specific roadside
devices automatically (after operator approval), such
as posting a pre-defined message to a DMS.
Some individual steps in the ATMS software response
plans shall be informational – for example, instructing
the operator to contact State Police.
The ATMS software shall allow a user to create, edit,
and save a library of response plans.
The ATMS software library shall be searchable by title
text and any other information associated with the
response plan.
The ATMS software users shall have the ability to
deactivate the response plan and restore the system
to its previous state.
The ATMS software users shall have the ability to skip
any step in the response plan.
The ATMS software user shall be able to activate a
response plan in 2 ways: as an action in response to
managing an active incident (icon in incident entry
form) or by selecting a link and requesting a new
response plan based on location.
Appendix P – page 29 of 40
SCENARIO
8
8
8, 26
8, 16, 26
8, 26
8, 26
26
26
26
8
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
FRP
BR
FRP11
BR03, BR08,
BR11, BR14
FUNCTIONAL REQUIREMENTS –
RESPONSE PLANS
The ATMS software actions available for use in a
response plan shall include: activation of roadside
devices (i.e. - posting a predefined message to a
DMS), Providing information or instruction to an
operator's screen (i.e. - instructing the operator to
contact the State Police), activation of a diversion
route, sending an e-mail, fax, text message, or page,
Issuing a command to the Road Closure Reporting
System to modify a road status, Generation of a predefined report.
The ATMS software shall allow Administrative users to
create existing or configure new response plans,
which shall be configured by: Location, Severity,
Upstream Distance, and Individual devices.
SCENARIO
26
FRP12
BR03, BR10
FRP13
BR03
The ATMS software shall prompt the operator to
confirm the automatic cancellation of associated
equipment activation when incident is closed.
26
FRP14
BR03
All devices in the ATMS response plans shall be
displayed, selectable and configurable by an
authorized user.
26
FRP15
BR03, BR08
FRP16
BR03, BR08
The ATMS software vendor must provide functional
details of the proposed software, documenting if the
solution is an intelligent engine generating statistically
driven responses, and not solely a protocol based
response.
The ATMS software shall provide optional response
plans for areas that may not have predefined
responses.
Appendix P – page 30 of 40
8
26
26
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.6.5 DMS
FDM
BR
FDM01
BR11
FDM02
FDM03
BR03, BR11
BR03, BR17
FUNCTIONAL REQUIREMENTS – DMS
The ATMS software shall provide the user the
capability to create a message for display on a DMS.
The ATMS software shall enforce the same
constraints on the user’s message that exist for the
selected DMS regarding: allowable set of characters,
number of lines of text, number of characters per line
and fonts.
The ATMS software shall maintain a list of forbidden
words. The ATMS software shall prevent a message
containing any word on the forbidden list from being
posted on any DMS device. The ATMS software shall
provide a facility for an authorized user to modify the
list of forbidden words.
The ATMS software shall provide the user the
capability to create, edit and save messages in a
message library.
SCENARIO
15
15, 16
15
FDM04
BR03
FDM05
BR03, BR11
When prompted by the user, the ATMS software shall
activate the message on the selected DMS device(s).
16
FDM06
BR03, BR11
The ATMS software shall allow the user to specify any
number of DMS devices to receive a given message.
16
FDM07
FDM08
FDM09
FDM10
BR03, BR11
BR03, BR11
BR11, BR15
BR11, BR14
FDM11
BR11
FDM12
BR03, BR11,
BR13
The ATMS software shall provide the user the
capability to remove a message from one or more
DMS.
The ATMS software shall confirm that the proposed
message, specified by the user, has been properly
posted to the DMS device(s) selected by the user.
The ATMS software shall allow the user to perform
remote maintenance, such as pixel tests, to check for
outages of individual pixels.
The ATMS software shall maintain a history of all
DMS messages that have been activated along with
the user name and time when it was activated.
The ATMS software shall provide the user the
capability to manually control the brightness of a DMS
device display.
Messages posted on a DMS shall appear on the
ATMS software graphical user interface along with the
icon representing the device. A mouse over function
will provide message information and an accurate
Appendix P – page 31 of 40
15, 16
16
16
19
19
19
16
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
FDM
BR
FDM13
BR11, BR13
FDM14
BR11
FDM15
FDM16
FDM17
FDM18
FDM19
FDM20
BR11, BR17
BR07, BR11
BR09
BR09, BR11
BR11
BR11
FUNCTIONAL REQUIREMENTS – DMS
representation of the current message.
The ATMS software shall provide the user the ability
to access the DMS from a map, table or tree view type
list.
The ATMS software shall allow Operators to blank
(command) a DMS.
This ATMS software management functionality shall
support the ability to prioritize and schedule
messages.
The ATMS software shall be capable of automatically
updating messages based on data such as Travel
Time or Detector Speed.
The ATMS software shall allow a user with
Administrative privileges to configure the number of
times that the ATMS software will attempt to resend a
message to a DMS if there is a communication failure.
If a communication failure occurs when sending a
message to a DMS, the ATMS software will attempt to
resend the message for the number of times that have
been configured by an Administrative user.
The ATMS software will notify the user if a message
was not successfully posted to the selected DMS(s)
within a specified number of attempts to post the
message.
Some PennDOT Districts use over 44 different DMS
with different fonts and configurations; therefore, the
ATMS software shall allow for an efficient method of
creating, editing and activating messages to multiple
sign types. For example, the ATMS software shall
allow the operator to edit and reactivate a message
that is displayed on any PennDOT DMS.
Appendix P – page 32 of 40
SCENARIO
16
16
15, 16
19
16
16
16
16
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.6.6 HAR
FHR
BR
FHR01
BR03, BR08
FHR02
BR03, BR11,
BR17
FHR03
BR11
FHR04
BR11
FUNCTIONAL REQUIREMENTS - HAR
The ATMS software shall retain existing Highway
Advisory Radio (HAR) and Beacon Control
functionality currently available through the Platinum
Software. Full control/viewing capabilities of all
aspects of the existing HAR module must be replaced
or integrated into the Statewide ATMS System.
The management functionality provided by the ATMS
software shall support the ability to: Predefine and
store messages, select and activate predefined
messages, activate operator entered messages,
prioritize and schedule messages, verify current
status.
The ATMS software shall allow the user to specify any
number of HAR devices to receive a given message.
The ATMS software shall provide the user the
capability to remove a message from one or more
HAR.
The ATMS software shall confirm that the proposed
message, specified by the user, has been properly
posted to the HAR device(s) selected by the user.
SCENARIO
20, 21
20, 21
21
21
FHR05
BR11
FHR06
BR11
The ATMS system shall allow the user to listen to the
message being broadcast by a given HAR.
21
FHR07
BR05
The ATMS software shall allow Operators to share
HAR control within a TMC.
23
FHR08
BR11
The ATMS software shall allow Operators to
activate/deactivate HAR Beacons individually or as a
group.
Appendix P – page 33 of 40
21
26
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.2.6.7 AVL
FAV
BR
FAV01
BR13, BR16
FAV02
BR16
FAV03
BR07
FAV04
BR07, BR13,
BR16
FAV05
BR13
FUNCTIONAL REQUIREMENTS - AVL
The vehicle location data displayed on the ATMS
software map shall consist of, at a minimum, vehicle
type, vehicle identifier, GPS coordinates, and the time
of day that the data was collected. Data can be
filtered by the ATMS operator based on vehicle type
or identifier.
The ATMS software shall allow Operators to view
winter road maintenance vehicles.
SCENARIO
27, 37
27
The ATMS software shall allow Operators to view
Service Patrol Vehicles.
37
The ATMS software shall display vehicle location data
real-time.
27, 37
The ATMS software shall not store historical vehicle
location data within the ATMS software database.
27, 37
11.2.6.8 TRAFFIC SIGNAL TIMING
FST
BR
FST01
BR16
FST02
BR16
FST03
BR16
FST04
BR16
FST05
BR13
FUNCTIONAL REQUIREMENTS – TRAFFIC
SIGNAL TIMING
The ATMS software shall allow operators to manage
HOV lanes. This includes remotely controlling traffic
signal controllers to implement traffic management
strategies at signalized intersections based on traffic
conditions, incidents, emergency vehicle preemptions,
pedestrian crossings, etc.
The ATMS software shall allow Operators to view the
status of Traffic Signal Timing systems.
The ATMS software shall allow the user to select from
a library of pre-set timing plans from the signal
software or return to normal operation.
The ATMS software shall confirm that any commands
specified by the user have been properly accepted by
the specified signal control system.
Signal plans that are active in the ATMS software
shall be represented on the graphical user interface.
Appendix P – page 34 of 40
SCENARIO
28, 39, 40
28
28
28
28
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
FST
BR
FST06
BR
FUNCTIONAL REQUIREMENTS – TRAFFIC
SIGNAL TIMING
The ATMS software shall support users’ management
of signals within at a minimum the following three (3)
categories of functionality:
1. Full Functionality (viewing and changing traffic
signal timings)
2. Traffic Signal Monitoring (monitoring and
viewing the operation to ensure that the signal
is operating correctly)
3. Adaptive Control (monitoring and viewing
existing traffic signal adaptive control software
and algorithms)
SCENARIO
11.2.6.9 EQUIPMENT ADMINISTRATION / STATUS
FEA
BR
FEA01
BR15
FEA02
BR09, BR15
FEA03
BR09, BR15
FEA04
FEA05
FEA06
BR09, BR15
BR15
BR15
FUNCTIONAL REQUIREMENTS - EQUIPMENT
ADMINISTRATION / STATUS
The ATMS software shall provide users the capability
to generate a list of equipment and their status (e.g.
successful or not successful) and equipment health
for a selected date or date range. This can be user
activated or scheduled, and must be confirmed by the
user.
The ATMS software solution shall provide a complete
Web GUI for administration with online help. Agency
administrators can then manage all aspects of the
solution from their Web browsers.
The ATMS software shall allow Administrators to add
or edit field devices’ information in the system and the
ATMS software map via the user interface.
The ATMS software shall provide the ability to adjust
system parameters, which include but are not limited
to Traffic (including travel time) thresholds that
triggers incident detection, geographic boundary of
incidents, incident types.
The ATMS software shall allow for monitoring and
remote diagnostics of field equipment - detect failures,
issue problem reports, and track the repair or
replacement of the failed equipment.
The ATMS software database shall at a minimum
store the itemized currently installed device inventory
including name, manufacturer, make, model, device
age, location, installation date, etc.
Appendix P – page 35 of 40
SCENARIO
30
1, 2, 3, 4, 5,
6, 7, 8, 9, 10,
43
5, 6
5, 6
31, 47
30, 46
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
FEA
BR
FEA07
BR15
FEA08
FEA09
BR15
BR15
FUNCTIONAL REQUIREMENTS - EQUIPMENT
ADMINISTRATION / STATUS
The ATMS software shall allow users to run reports on
average device life, devices under warranty, devices
under contractor maintenance period, etc.
The ATMS software shall allow users to edit
maintenance related data fields to reflect real time
change in maintenance service.
The ATMS software shall include asset management
and an equipment trouble ticketing systems. The
Offeror shall consider integrating existing PennDOT
systems, such as Remedy and SAP.
SCENARIO
30, 46
6, 46
6, 30, 31, 51
11.2.6.10 TRAVEL TIME
FTT
BR
FTT01
BR10, BR11
FTT02
FTT03
BR11
BR12
FTT04
BR07, BR10,
BR16
FTT05
BR02, BR10
FUNCTIONAL REQUIREMENTS - TRAVEL TIME
The ATMS software shall have the ability to use
PennDOT detectors, other outside sources, vehicle
probe data, and other data sources as they become
available to compute a current estimated travel time
between any pair of interchanges or devices as
selected by the user.
The ATMS software shall automatically update the
current estimated travel time on any DMS that are
displaying travel time messages.
The ATMS software shall automatically update the
current estimated travel times that are sent to outside
partners.
The ATMS software shall compute the current length
(distance) of congested traffic on a given route from a
user-specified point, based on vehicle speed and/or
occupancy data.
The ATMS software shall alert operators if travel times
exceed a specified threshold.
Appendix P – page 36 of 40
SCENARIO
19, 35
19, 35
19, 35
19, 35
19, 35
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
11.3 PERFORMANCE MEASURES
PMR
PMR01
PMR02
PMR03
PMR04
BR
BR14
BR14
BR14
BR14, BR15
PMR05
BR14
PMR06
BR14
PMR07
PMR08
BR14
BR08
PMR09
BR09
PMR10
BR14
PERFORMANCE MEASURES
The ATMS software shall support extensive reporting capabilities.
Sample reports have been assembled in Appendix B: Sample
Graphic Representations Of The Recommended Performance
Metrics.
Contractor shall provide an additional twelve (12) reports which will be
jointly designed with PennDOT as per the RFP requirements.
Contractor shall develop report mock ups showing data mapping, logic
and levels, (user authorization and drill down levels if applicable), for
each report.
The ATMS software shall provide the capability to filter data and
generate reports by selecting and prioritizing any combination of data
elements. For example, incident reports can be generated by date,
time of day, road, district, etc.
In addition to traffic related reports, the ATMS system shall be capable
of generating system health reports (i.e. communication status, device
status, equipment uptime).
The ATMS system shall track actions and record operator information
for all key events. These user logs shall be available to system
managers.
The ATMS system will also track automatic functions and errors and
store this information in event logs, which shall be accessible to user.
The ATMS software must provide PennDOT with the ability to create
custom reports using industry standard tools (i.e. Crystal Reports or
SQL Server Reporting Services.)
The ATMS software shall timestamp and store all equipment
activations, communications, notifications and other actions taken at
all times.
The ATMS software logs must be stored in a human readable format
and shall not use any cryptic information, i.e. instead of “Error Code
#N” state “Database Error”.
Contractor shall provide use of existing canned reports, including
schedulable reports, if applicable.
11.0 VERIFICATION METHODS
Appendix P – page 37 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
For each requirement, one of the following methods of verification will be identified:
•
All functional requirements (11.2.6) and HMI requirements (11.2.3) shall be validated
using the demonstration methodology. The contractor shall supply all test plans and
scripts, which shall be executed by PennDOT during User Acceptance and Regional
Acceptance testing. The results shall be compared to the expected outcome and the test
will be evaluated accordingly. PennDOT reserves the right to perform Ad-Hoc testing
and to bring in a third party to conduct the testing for PennDOT.
•
Enabling, Performance, Interface and Data Requirements may require indirect testing
using the analyze methodology. Those elements shall be demonstrated to meet the
requirements indirectly through a logical conclusion or mathematical analysis of a result.
E.g. Algorithms for congestion: the designer may need to show that the requirement is
met through the analysis of count and occupancy calculations in software or firmware.
Appendix P – page 38 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
12.0 SUPPORTING DOCUMENTATION
Supporting documentation (i.e. sample reports) is included in Appendix B.
13.0 TRACEABILITY MATRIX
The traceability matrix is included in Appendix X of the RFP.
Appendix P – page 39 of 40
PennDOT Statewide ATMS Software System Requirements, Rev. 7.2
APPENDIX A: GLOSSARY
APRAS
ATMS
ATR
AVL
BPR
C2C
CAD-911
CAVC
CCTV
CMMI
ConOps
COTS
CWOPA
DMS
DRJTBC
DVRPC
FHWA
GATIR
GIS
GPS
GUI
HAR
HMI
HOV
IDRum
ITB
ITS
LDAP
MDSHA
NJDOT
NTCIP
PEMA
PennDOT
PSP
PTC
PTZ
RAID
RCRS
RCI
RIMIS
RWIS
SEI
SNMP
SOP
SSL
Automated Permit Routing/ Analysis System
Advanced Traffic Management System
Automatic Traffic Recorder
Automatic Vehicle Locator
PennDOT’s Bureau of Planning & Research
Center-to-Center
Computer Aided Dispatch
Continuous Automated Vehicle Classification
Closed Circuit Television
Capability Maturity Model Integration
Concept of Operations
Commercial off the Shelf
Commonwealth of Pennsylvania Account
Dynamic Message Signs
Delaware River Joint Toll Bridge Commission
Delaware Valley Regional Planning Commission
Federal Highway Administration
Geospatial Analysis of Threats and Incident Reports
Geographical Information System
Global Positioning System
Graphical User Interface
Highway Advisory Radio
Human Machine Interface
High Occupancy Vehicle
Interactive Detour Route and Mapping
Information Technology Bulletin
Intelligent Transportation System
Lightweight Directory Access Protocol
Maryland State Highway Authority
New Jersey Department of Transportation
National Transportation Communications for ITS Protocol
Pennsylvania Emergency Management Agency
Pennsylvania Department of Transportation
Pennsylvania State Police
Pennsylvania Turnpike Commission
Pan-Tilt-Zoom
Redundant Array of Inexpensive Drives
Road Condition Reporting System
Roadways Congestion Index
Regional Integrated Multimodal Information Sharing
Roadway Weather Information System
Software Engineering Institute
Simple Network Management Protocol
Standard Operating Procedures
Secure Socket Layer
Software System Requirements
(Appendix a)
Appendix P-a1
PennDOT Statewide ATMS Software System Requirements, Rev. 7.2
STIP
TMC
TMDD
VMS
WIM
Standalone Count Station
Traffic Management Center
Traffic Management Data Dictionary
Variable Message Signs
Weight in Motion
Software System Requirements
(Appendix a)
Appendix P-a2
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b3
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b4
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b5
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b6
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b7
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b8
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
MEASURES
WHAT THEY TELL YOU
Level 1
Level 2
Level 3
Overall Reliability
• Travel
• Upper
Management
e.g., buffer index
conditions
are unreliable
• What’s
• Public
e.g., vehicle-hours
Special
Events
Weath
• What aspects of
•
Traffic
Control
Inciden
Base
Capaci
DemandVariabilit
Activities,
Procedures, and
operations,
management,
and construction
R l ti
MidManagement
Operators
•
Delay by Source
causing
unreliable
travel
Work
USED BY
• Operators
• Field
… for incidents …
INCIDENT TIMELINE
Inciden
t
Incident
Recorded into
CAD
Incident
Verified
6:35
6:42
6:47
Personnel
Dispatched
and Actions
6:49
Responder
s Arrive to
S
Incident
Cleared and
A ti
Return to
Normal
C diti
6:50-7:00
7:15
8:26
1
2
3
4
Detection
Time
Verificati
on Time
Dispatc
h Time
Response
Time
1
Software System Requirements
(Appendix b)
Appendix P-b9
5
Clearance
Time
6
Time to
Normal
C diti
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Number of Trips (in Thousands)
100
Travel Time at
FFS = 14.2 minutes
90
95th percentile = 23.5 minutes
Mean = 18.9 minutes
80
Reliability Metrics
70
60
50
40
30
TTI
=
1.370
BI
=
0.233
Percent Trips On-Time =
52%
PTI
=
1.655
Skew Stat
=
1.712
Misery Index
=
0.481
20
10
0
14
16
TTI = 1.37
18
20
22
BI = 0.233
24
26
28
30
Travel Time (in Minutes)
Event Characteristics
Capacity Loss
Incident Rate
=
141.3
Crash Rate
=
99.7
Percent hours with precip. =
4.7%
Percent hours with frozen =
0.2%
Percent hours with fog
=
1.5%
Work Zone Types
=
(none)
Avg Incident Duration
=
27.6 min
Avrg Work Zone Duration =
0.0 min
Software System Requirements
(Appendix b)
Cong. Source
Lane-Hrs Shoulder-Hrs
Incident
31.0
20.3
Work Zone
0.0
0.0
Section Characteristics
AVMT
=
766.5M
Average No. Lanes
=
3.8
Average AADT/C
=
11.9
Critical AADT/C
=
14.1
Percent Trucks
=
9%
Pct Days with Demand
> (mean + 10%)
=
6.3%
Appendix P-b10
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b11
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b12
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Software System Requirements
(Appendix b)
Appendix P-b13
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
Traffic Profile
SR
General Purpose Lanes
1997 Weekday
West bound
East bound
NE 60th
14 th
40
B’vue.
92n
84th
52
Lk.
Montlake
Ar
bo
re
tu
5
0
2
4
6
A
8 1
1 2
Tim
4
6
P
8 1
Uncongested, near
speed
Software System Requirements
(Appendix b)
1
0
Restricted movement
but near speed
Appendix P-b14
2
4
6
A
More heavily congested,
45 - 55
8 1
1 2
Tim
4
6
P
8 1
Extremely congested,
unstable
1
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
S. I-5 Congestion Frequency Profile: GP Lanes, 2004 Thursday
166
Southbound
166
Nor thbound
164
164
90
Spokane St.
162
162
160
160
5
158
158
Boeing
Access Rd.
156
156
599
MP
MP
154
154
518
405
152
152
S 200th St
150
150
516
148
148
S 272nd St
146
146
N
144
0
2
4
6 8 10 12 2
AM
Time
4
6 8
PM
144
0
10 12
2
4
6 8 10 12 2
AM
Time
4
6 8 10 12
PM
Congested Thursdays per year
0 - 20%
20 - 40%
Software System Requirements
(Appendix b)
40 - 60%
Appendix P-b15
60 - 80%
80 - 100%
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
ATMS - PHASE 2
High
Winds
Detection
MC04 – Weather
Information
Processing and
Distribution
Anti-Icing
MC05 – Roadway
Automated
Treatment
ATIS01 Broadcast
Traveler
Information
EMERGENCY
MANAGEMENT
PHASE 1
PennDOT ATMS
AD2 – ITS Data
Warehouse
ATMS
Database
TRAFFIC MANAGEMENT
ATMS 08: Traffic
Incident
Management
System
ATMS03 - Surface
Street Control
Signal
Control
Systems
ATMS04 Freeway Control
Ramp
Meters
Variable
Speed
Controls
ATMS09 –
Decision Support
and Demand
Management
AVSS10 –
Intersection
Collision
Avoidance
CVO06 – WeightIn-Motion
EM09 –
Evacuation and
Reentry
Management
ATMS02 - Traffic
Probe
Surveillance
MC10 –
Maintenance and
Construction
Activity
Coordination
ATMS05 – HOV
Lane Management
MC08 – Work
Zone Management
MC07 – Roadway
Maintenance and
Construction
Reporting /
Performance
Measures
ATMS07 –
Regional Traffic
Management
ATMS21 –
Roadway Closure
Management
EM06 – Wide
Area Alert
ARCHIVED DATA
MANAGEMENT
511 &
Ready
Notify
MC03 – Road
Weather Data
Collection
EM04 – Roadway
Service Patrols
AD1 – ITS Data
Mart
TRAVELER
INFORMATION
Outside
Partners
(2 Way)
EM10 – Disaster
Traveler
Information
EM05 –
Transportation
Infrastructure
Protection
MAINTENANCE AND CONSTRUCTION MANAGEMENT
ATIS06 Transportation
Operations and
Data Sharing
MC02 –
Maintenance
and Const.
Vehicle
Maintenance
ATMS18 Reversible Lane
Management
MC06 – Winter
Maintenance
MC01 – Maint.,
Construction
Vehicle, Equip.
Tracking
ATMS06 – Traffic
Information
Dissemination
ATMS 19 – Speed
Monitoring
ATMS01 - Network
Surveillance
HAR
DMS
Media
CCTV
Detectors
Market Package Diagram
Working Draft
Software System Requirements
(Appendix c)
Appendix P -c1
3/22/2010
PennDOT Statewide ATMS Software System Requirements, Rev. 7.3
High
Winds
Detection
Anti-Icing
Asset
Management
Databaset
High Winds
Alert
Status and Control
of Roadway
Automated
Treatment
Incident Management
Maintenance and Construction
Activity Coordination
511 &
Ready
Notify
Transportation
Operations and
Data Sharing
Broadcast
Traveler
Information
PHASE 1
TRAVELER
INFORMATION
Outside
Partners
(2 Way)
ARCHIVED DATA MANAGEMENT
INCIDENT, MAINTENANCE, AND CONSTRUCTION
MANAGEMENT
PennDOT ATMS Database
Reporting /
Performance
Measures
TRAFFIC MANAGEMENT
Network Surveillance
Incident Detection
EZPass
Detectors
Video Management
CCTV
Video Wall
Traffic Information Dissemination
Speed Monitoring
Lane
Signals
HAR
Media
DMS
Video
Recorders
Functional Area Diagram
Working Draft
Software System Requirements
(Appendix c)
Appendix P -c2
10/26/2010
APPENDIX Q
ITS EQUIPMENT
APPENDIX Q
ITS EQUIPMENT INVENTORY
APPENDIX Q
ITS EQUIMENT INVENTORY
Table 1: Quantities of ITS Field Equipment
As of 2011-01-21
Quantities of ITS Field Equipment
ITS Device
District 1-0
District 2-0
District 3-0
District 4-0
District 5-0
District 6-0
District 8-0
District 9-0
Permanent CCTV
Portable CCTV
Permanent DMS
Portable DMS *
Permanent HAR
Portable HAR
Microwave Detectors
Video Detectors
0
1
9
1
4
0
0
0
30
0
23
3
21
0
0
0
0
0
1
5
0
0
0
0
22
4
7
45
10
0
0
0
34
0
5
29
9
6
0
0
222
0
61
22
0
0
90
12
56
0
36
15
15
0
0
0
41
0
34
0
2
0
0
0
District 10-0 District 11-0 District 12-0
0
0
32
0
13
0
0
0
148
0
26
0
10
0
140
0
0
0
2
12
4
0
0
0
Total
553
5
236
132
88
6
230
12
* Portable DMS include all semi-permanent DMS.
The chart above is a listing of the quantities of ITS equipment by PennDOT Engineering District.
A detailed listing of each device including information such as, exact location, manufacturer, model, software, etc. is available on the device tabs.
Appendix Q Page 1 of 2
APPENDIX Q
ITS EQUIMENT INVENTORY
Table 2: Summary of ITS Software
As of 2011-01-21
Summary of ITS Software
Device Type
Software
CCTV
ATMS
Broadware Video Server
DIVAR
Philips/Bosch GUI version 2.43
VIDSYS VidShield 6.1
DMS
AMSIG EASYHOST
AMSIG NET
ATMS
DAMBAUCH VMS SOFTWARE
DYNAC
INTELLIGENT CONTROL
MERCURE
MESSENGER
NTCIP VMS CENTRAL
PSC SMC 1000-2000 BASESTATION
PSC SMC 2000 BASESTATION
PSC STDFULL BASESTATION
SOLAR MESSAGE CENTER
VANGUARD
Wanco
HAR
DR2000 Platinum
A detailed listing of each device including information such as, exact location, manufacturer, model, software, etc. is available on the device tabs.
Appendix Q Page 2 of 2
PennDOT Existing DMS
Statewide_ID
District_ID
STATUS
TYPE
SUB-TYPE
STRUCTURE
DISTRICT
Descriptive Location
MILEMARKER
Next Exit
COUNTY
STATE ROUTE
SEGMENT
OFFSET
District 1-0
DMS-01-001
DMS-01-002
DMS-01-003
DMS-01-004
DMS-01-005
DMS-01-006
DMS-01-007
DMS-01-008
DMS-01-013
DMS-01-014
DMS-01-015
DMS-01-016
152NB
1EB
46WB
176NB
181SB
16EB
24WB
33WB
200
210
42E
45E
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
SEMI-PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
CONCRETE PAD
OVERHEAD
OVERHEAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
01
01
01
01
01
01
01
01
01
01
01
01
Milepost 152 Northbound (Seg. 1520/Off. 990)
Milepost 1 Eastbound (Seg 0010/Off. 212)
Milepost 45 Westbound (Seg. 455/Off. 122)
I-79 NB at I-90
I-79 SB at I-90
I-90 EB at I-79
I-90 WB at I-79
I-90 WB at PA 290
Milepost 16 Eastbound (Seg. 164/Off. 1307)
Milepost 20 Westbound (Seg. 201/Off. 200)
Emlenton Exit
St. Petersburg-Emlenton Exit
152.0
001.0
045.0
175.2
180.9
016.5
023.6
033.7
016.0
020.0
042.0
045.0
154
3
45
178
178
18
22
32
19
19
42
45
CRAWFORD
ERIE
ERIE
ERIE
ERIE
ERIE
ERIE
ERIE
MERCER
MERCER
VENANGO
VENANGO
0079
0090
0090
0079
0079
0090
0090
0090
0080
0080
0080
0080
1520
0010
0461
1750
1805
0160
0235
0335
0164
0195
0380
0420
0990
0212
0098
0800
2240
2657
0492
1122
1594
2063
2335
0750
DMS 3
DMS 4
DMS 5
DMS 6
DMS 7
DMS 8
DMS 10
DMS 13
DMS 14
DMS 15
DMS 17
DMS 18
DMS 19
DMS 20
DMS 21
DMS 22
DMS 23
DMS 26
DMS 27
DMS 28
DMS 29
DMS 30
SP1
SP2
SP3
97W
DMS 37
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
PERMANENT
PERMANENT
CENTERMOUNT
OVERHEAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CENTERMOUNT
CENTERMOUNT
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
Northbound 1.5 miles before Port Matilda Exit on I-99
SR 0322 Eastbound 1 mile after Reese Hollow Exit
Northbound 1.5 miles before Port Matilda Exit on I-99
SR 0322 Eastbound 1 mile after Reese Hollow Exit
I-99 Southbound Near Fox Hollow Road (State College)
SR 3014 Westbound at Valley Vista Intersection
SR 0322 Eastbound near Branch Road
I-80 Eastbound 4.5 miles before Exit 158
I-80 Eastbound 2 miles after Exit 158
I -80 Westbound 2 miles before Exit 158
SR 0322 Eastbound near Reedsville
SR 0022 Westbound near Port Royal Exit
SR 0322 Westbound before Branch Road
I-80 Milepost 183 Eastbound
SR 0322 Westbound at bottom of Seven Mountains
SR 0219 Northbound before SR 0770 Intersection, SR 0219-D09 Job
SR 0219 Southbound before SR 0346 Intersection, SR 0219-D09 Job
I-80 Eastbound 2 miles before Exit 101, I-80-B28 Job
I-80 Westbound 5 miles before Exit 101, I-80-B28 Job
I-80 Eastbound 5 miles before Exit 111, I-80-B28 Job
I-80 Westbound 4.5 miles before Exit 111, I-80-B28 Job
I-80 Eastbound 2 miles before Exit 120, I-80-B28 Job
SR 0022 Westbound located in median
SR 0022 Eastbound located off right shoulder behind Jersey Barrier
SR 0322 Eastbound near Reedsville
DuBois- Brockway Exit - Belongs to Dist. 10-0
I-80 Eastbound 1 mile past Exit 111, I-80-B28 Job
059.5
072.5
61
61
74
70
71
079.5
153.5
160.0
156.0
80
158
158
158
183.0
185
099.0
106.0
105.5
115.5
117.0
101
101
111
111
120
099.0
111.5
97
120
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
MIFFLIN
JUNIATA
CENTRE
CLINTON
CENTRE
MCKEAN
MCKEAN
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
MIFFLIN
MIFFLIN
MIFFLIN
CLEARFIELD
CLEARFIELD
0099
0322
0099
3014
0099
0322
0099
0080
0080
0080
0322
0022
0322
0080
0322
0219
0219
0080
0080
0080
0080
0080
0022
0022
0322
0080
0080
0594
0230
0725
0021
0724
0538
0804
1534
1580
1591
0200
0191
0537
1824
0801
0460
0594
0984
1061
1054
1161
1174
0523
0422
0210
0985
1114
1435
2390
1145
3025
0780
2150
0175
1605
0865
0570
0950
2240
1200
2640
0315
1600
0386
2550
1510
0930
0680
1580
1150
1370
1360
2490
0050
094-3520
096-3520
SEMI-PERMANENT
SEMI-PERMANENT
PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
CONCRETE PAD
CONCRETE PAD
CENTERMOUNT
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
03
03
03
03
03
03
Milepost 246 Westbound (Seg. 2471/Off. 0092)
Milepost 216 Eastbound (Seg. 2164/Off.1342)
Westbound between Exits 215 and 212 (Seg. 2131/Off. 2)
I-80 EB, west of Mile Run exit (Segment 1954/Off. 0992)
Milepost 201 Westbound (Seg. 2001/Off. 1098)
Milepost 195 Westbound (Seg. 1955/Off. 0115)
246.0
216.0
944-3520
825-3520
826-3520
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
COLUMBIA
MONTOUR
NORTHUMBERLAND
UNION
UNION
UNION
0080
0080
0080
0080
0080
0080
2471
2164
2131
1954
2001
1955
0037
1342
0002
0992
1098
0115
3
4
5
7
8
9
10
15
18
19
20
22
23
24
26
27
31
33
36
37
40
43
44
51
53
54
63
66
68
69
70
71
72
73
OH 103
OH 104
OH 105
OH 106
OH 107
OH 108
OH 109
W01
W02
W05
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
SEMI-PERMANENT
SEMI-PERMANENT
PORTABLE
PORTABLE
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
PORTABLE
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
PORTABLE
SEMI-PERMANENT
PORTABLE
PORTABLE
SEMI-PERMANENT
PORTABLE
SEMI-PERMANENT
PORTABLE
PORTABLE
SEMI-PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
CONCRETE PAD
CONCRETE PAD
TRAILER
TRAILER
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
TRAILER
TRAILER
TRAILER
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
TRAILER
CONCRETE PAD
TRAILER
TRAILER
CONCRETE PAD
TRAILER
CONCRETE PAD
TRAILER
TRAILER
CONCRETE PAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
CONCRETE PAD
TRAILER
TRAILER
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
Rt. 6 Westbound just before 81N on ramp in gore
Northbound right side
South bound right side behind guide rail
Southbound right side
Northbound right side before bridge
Southbound right side
Southbound right side after off ramp
Northbound right side behind guide rail
Southbound right side behide guide rail
Northbound right side behind guide rail
Rt. 309 Right side
Southbound center median on rocks
Eastbound right side end of guide rail
Northbound right side
Southbound right side
Eastbound right side behind guide rail
Westbound Left should
next to Overhead 101
Southbound right side behind guide rail
Southbound Median behind guide rail
Northbound right side behind guide rail
Southbound right side
Southbound right side behind barrier
Northbound right side
Northbound right side behind guide rail
Northbound right side behind guide rail
Northbound in median
Northbound right side behind guide rail
Northbound right side
Southbound right side behind guide rail
Eastbound right side
Southbound, I-81 right side
Eastbound right side
Northbound behind concrete barrier
Northbound Amsig Overhead
Westbound Amsig overhead
Westbound Amsig overhead
Northbound Amsig overhead
Westbound East of Marshwood Road Exit
Southbound Daumbach overhead
Westbound PA/NY State Line
I-84 EB right side behind guiderail
I-84 EB right side after off ramp
I-84 WB right side
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LACKAWANNA
LACKAWANNA
LACKAWANNA
LUZERNE
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LUZERNE
LACKAWANNA
LACKAWANNA
LUZERNE
LACKAWANNA
LUZERNE
LACKAWANNA
SUSQUEHANNA
LUZERNE
LACKAWANNA
LUZERNE
LUZERNE
LACKAWANNA
LACKAWANNA
LACKAWANNA
SUSQUEHANNA
PIKE
WAYNE
PIKE
PIKE
6006
0011
0081
0081
0309
0309
0309
0081
0081
0081
0309
0081
0080
0081
0029
0084
0084
0081
0081
0081
0081
0081
0081
0081
0081
0081
0081
0081
0081
0081
3022
0081
0080
0081
0081
0080
0084
0380
0006
0081
0084
0084
0084
0084
0251
0252
1811
1835
0628
0651
0627
1780
1665
1394
0480
1695
2504
1654
0041
0020
0021
1955
1611
2045
1890
1911
1881
1920
1624
1794
2034
1724
2004
1731
0010
2141
2590
1850
1490
2645
0101
0174
0325
2315
0541
0134
0300
0305
1060
2112
0233
0746
2893
2462
3322
2090
1065
1795
1520
2403
2027
2090
1083
2492
1784
1014
1482
1924
1689
0043
2196
2112
2344
1943
1858
2302
1541
2371
1140
1460
0211
1541
2133
0145
2118
1900
1533
0383
0323
1985
1985
0436
District 2-0
DMS-02-003
DMS-02-004
DMS-02-005
DMS-02-006
DMS-02-007
DMS-02-008
DMS-02-010
DMS-02-013
DMS-02-014
DMS-02-015
DMS-02-017
DMS-02-018
DMS-02-019
DMS-02-020
DMS-02-021
DMS-02-022
DMS-02-023
DMS-02-026
DMS-02-027
DMS-02-028
DMS-02-029
DMS-02-030
DMS-02-033
DMS-02-034
DMS-02-035
DMS-02-036
DMS-02-040
072.5
District 3-0
DMS-03-001
DMS-03-002
DMS-03-003
DMS-03-048
DMS-03-049
DMS-03-050
212
199
201.0
195.0
District 4-0
DMS-04-002
DMS-04-007
DMS-04-008
DMS-04-009
DMS-04-010
DMS-04-011
DMS-04-012
DMS-04-016
DMS-04-019
DMS-04-020
DMS-04-021
DMS-04-022
DMS-04-023
DMS-04-024
DMS-04-025
DMS-04-026
DMS-04-028
DMS-04-030
DMS-04-031
DMS-04-032
DMS-04-034
DMS-04-035
DMS-04-036
DMS-04-037
DMS-04-038
DMS-04-039
DMS-04-041
DMS-04-044
DMS-04-046
DMS-04-047
DMS-04-048
DMS-04-049
DMS-04-050
DMS-04-051
DMS-04-061
DMS-04-062
DMS-04-063
DMS-04-064
DMS-04-065
DMS-04-066
DMS-04-067
DMS-04-068
DMS-04-069
DMS-04-070
181.0
183.7
178.4
166.7
139.8
169.9
250.8
165.9
2.4
2.3
195.7
161.3
204.9
189.3
191.0
188.4
192.4
162.8
179.8
203.8
172.9
200.8
173.5
214.3
259.0
185.3
149.4
264.5
10.4
017.8
003.3
231.6
054.1
013.8
30.4
30.5
180
182
4
5
1
180
168
141
168
256
168
2
1
1
194
159
202
190
190
187
194
164
182
206
175
201
170
I-81SB
211
260
187
151A-B
262
8
20
2
230
46
17
34
34
DMS-04-071
DMS-04-072
DMS-04-083
DMS-04-088
DMS-04-090
DMS-04-091
DMS-04-092
W03
W04
65
W06
29
W07
W08
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
TRAILER
TRAILER
CONCRETE PAD
TRAILER
CONCRETE PAD
TRAILER
TRAILER
04
04
04
04
04
04
04
I-84 EB right side dehind guide rail
84 WB right side behind guide rail
Southbound right side behind guide rail
I-84 WB right side
Southbound right side on top of barrier
SR 115 NB before truck pull over
SR115 SB
41.3
037.2
157.5
023.7
185.7
46
34
155
20
184
CMS No.1
CMS No.2
CMS No.3
CMS No.4
CMS No.5
CMS No.7
CMS No.9
CMS No.10
CMS No.11
CMS No.12
CMS No.14
CMS No.15
CMS No.16
CMS No.17
CMS No.18
CMS No.20
CMS No.21
CMS No.22
CMS No.23
CMS No.24
CMS No.25
VMS No.1
VMS No.2
VMS No.3
VMS No.4
64
D-78W-9
CMS No. 29
CMS No. 27
CMS No. 30
CMS No. 28
VMS No.5
CMS No. 31
CMS No. 32
SP-403
CMS No. 26
CMS No. 33
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PERMANENT
PERMANENT
PERMANENT
PERMANENT
SEMI-PERMANENT
PERMANENT
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PERMANENT
PORTABLE
PORTABLE
SEMI-PERMANENT
PORTABLE
PORTABLE
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
CONCRETE PAD
TRAILER
TRAILER
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
CONCRETE PAD
OVERHEAD
TRAILER
TRAILER
TRAILER
TRAILER
OVERHEAD
TRAILER
TRAILER
CONCRETE PAD
TRAILER
TRAILER
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
Milepost 316.6 Eastbound (Seg. 90/Off. 947)
Milepost 54.2 Westbound (Seg. 541/Off. 1285)
Milepost 63.6 Eastbound (Seg. 634/Off. 469)
Milepost 50.4 Eastbound (Seg. 500/Off. 1924)
Milepost 319.3 Eastbound (Seg. 140/Off. 456)
Milepost 55.2 Westbound (Seg. 551/Off. 1031)
Milepost 67.6 Westbound (Seg. 90/Off. 947)
PA Turnpike Exit onto US 22 (Approximation)
US 22 Milepost 323.2 Westbound
US 22 Milepost 323.8 Eastbound
I-78 Milepost 50.5 Westbound
Milepost 42.9 I-78 Westbound
I-81 NB MM 98.7
Milepost 21.6 I-78 Westbound
PA 33 NB Milepost 3.7
I-81 Milepost 139.50 Southbound (Seg 1391/Off 2640
Milepost 27 I-78 Eastbound
Milepost 42.3 I-78 Eastbound
I-81 Milepost 122.1 Northbound (Seg 1220/Off 175)
Milepost 27.1 I-78 Westbound
PA 309 Northbound near I-78 Inter. (Seg. 80/Off. 676)
Milepost 47.9 I-78 Eastbound (Seg. 474/Off. 2000)
Milepost 333.6 US 22 Westbound (Seg. 171/Off. 2000)
Milepost 72.8 I-78 Westbound (Seg. 725/Off. 1339)
Milepost 7.9 PA 33 Southbound (Seg. 91/Off. 283)
Westbound (Seg. 2761/ Off. 0410)
I-78 MM 9.5
Milepost 290.6 I-80 EB prior to I-380
Milepost 310.5 I-80 WB just after Toll Booth
Milepost 7.2 I-380 SB prior to Rt.940
I-80 WB at MM 299.9
Milepost 9.7 I-78 Eastbound
Milepost 124 I-81 Southbound (Seg. 1245/Off. 110)
I-78 EB Milepost 67.5
US 422 EB EAST OF RIVER BRIDGE ROAD
I-78 EB After PA 501 Bethel Exit 13 Before Grimes Exit 15 MM 14.4
Milepost 326.1 US 22 Westbound (Seg. 11/Off. 1022)
316.6
054.2
063.6
050.4
319.3
055.2
067.6
PA 309
53
67
51
15th Street
54
67
PA TNPK Toll Booth
Fullerton Avenue
Airport Road
Exit 49
40
Exit 100
Exit 19
US 22
138
29
45
124
23
I-78 Exit 60
49
PA 33
71
PA 248
274
10
293
309
3
299
10
124
Exit 71
P095S_02
P01BN_03
P01BS_04
P413N_05
P413S_06
P476N_07
AMSIG Portable
P013S_08
P013N_09
P095S_11
P095S_12
P095N_13
P206
P301
P302
P303
P422E_17
D095N_01
D095N_02
D095S_03
D095S_04
D095N_07
D095N_08
D095S_09
D095N_10
D095S_11
D095N_12
D095S_13
D095S_14
D095N_15
D202N_01
D202N_02
D202N_03
D030E_05
D422E_01
D422E_02
D063E_01
D076W_01
D076W_03
D076W_09
D076E_05
D076E_02
D476N_01
D476S_02
D100N_01
D100N_03
D100N_04
D100S_05
D202S_04
D202S_05
D202S_06
D202N_07
D202S_08
D202N_09
D202N_10
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
CENTERMOUNT
CENTERMOUNT
OVERHEAD
CENTERMOUNT
OVERHEAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
OVERHEAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
OVERHEAD
CENTERMOUNT
OVERHEAD
OVERHEAD
OVERHEAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
I-95 SB after US Rt. 1
Business Rt. 1 SB at I-95 NB
Business Rt. 1 NB at I-95 SB
PA 413 NB before I-95
PA 413 SB before I-95
I-95 NB RAMP TO NB I-476
I-476 NB AT MILE MARKER 10.6
PA 13 SB at PA 63
PA 13 NB at PA 63
I-95 SB MEDIAN AT ISLAND AVENUE
I-95 SB AT PACKER AVENUE
I-95 NB NORTH OF COLUMBUS
US 202 SB AT BRANDYWINE ROAD
PA 309 NB AT CHELTENHAM MALL
PA TURNPIKE BEFORE FT. WASH. TOLLS
PA 309 SB After North Wales Rd.
US 422 EB BEFORE PA 29
I-95 NB NORTH OF PA 420
I-95 NB NORTH OF AIRPORT EXIT 10
I-95 SB NORTH OF ALLEGHENY AVENUE
I-95 SB SOUTH OF BETSY ROSS BRIDGE
I-95 NB AFTER GIRARD OFF-RAMP
I-95 NB BEFORE COTTMAN AVE. EXIT 30
I-95 SB AT LEVICK ST.
I-95 NB AT ASHBURNER ST.
I-95 SB SOUTH OF ASHBURNER ST.
I-95 NB BEFORE GRANT AVENUE
I-95 SB NEAR ACADEMY RD.
I-95 SB AFTER WOODHAVEN RD.
I-95 NB BEFORE STREET RD.
US 202 (MEDIAN) SOUTH OF RT 252
US 202 NB NORTH OF NORTH VALLEY RD
US 202 NB NORTH OF RT 401
US RT 30 EB BEFORE PA 100
US 422 EB BEFORE PA 363
US 422 EB AFTER PA 29
PA 63 EB BEFORE KNIGHTS RD
I-76 WB BEFORE US 202
I-76 WB BEFORE CONSHOHOCKEN
I-76 WB NEAR UNIVERSITY AVE.
I-76 EB NEAR MONTGOMERY DR EXIT 341
I-76 EB BEFORE GULPH MILLS
I-476 NB AT MILE MARKER 13.9
I-476SB AFTER RIDGE PIKE ONRAMP
PA 100NB ON RAMP PAST BUSINESS RT. 100
PA 100 NB SOUTH OF SHIP ROAD
PA 100 NB AFTER KIRKLAND AVENUE
PA 100 SB SOUTH OF PA 113
US 202S south/North Valley Rd
US 202N north/PA 401
US 202S north/Church Rd
US 202N south/King Rd
US 202 south/PA 100
US 202S north/PA 322
US 202N north/Matlack St
PIKE
PIKE
LUZERNE
PIKE
LACKAWANNA
LUZERNE
LUZERNE
0084
0084
0081
0084
0081
0115
0115
0410
0371
1575
0235
1855
0250
0281
1541
0558
0081
1420
1056
0195
0825
0022
0078
0078
0078
0022
0078
0078
0022
0022
0022
0078
0078
0081
0078
0033
0081
0078
0078
0081
0078
0309
0078
0022
0078
0033
0080
0078
0080
0080
0380
0080
0078
0081
0078
0422
0078
0022
0090
0541
0634
0500
0140
0551
0675
0947
1285
0469
1924
0456
1031
0550
0984
0921
1391
2640
1220
0175
0080
0474
0171
0725
0091
2761
0676
2000
2000
1339
0283
0170
2904
3105
0071
2995
0000
0355
0500
2300
1245
0110
0011
1022
0104
0697
0200
0550
0304
1900
0335
0351
0113
2490
0310
0392
0091
0675
0032
2523
3465
0939
0181
0523
District 5-0
DMS-05-001
DMS-05-002
DMS-05-003
DMS-05-004
DMS-05-005
DMS-05-007
DMS-05-009
DMS-05-010
DMS-05-011
DMS-05-012
DMS-05-014
DMS-05-015
DMS-05-016
DMS-05-017
DMS-05-018
DMS-05-020
DMS-05-021
DMS-05-022
DMS-05-023
DMS-05-024
DMS-05-025
DMS-05-026
DMS-05-027
DMS-05-028
DMS-05-029
DMS-05-030
DMS-05-031
DMS-05-044
DMS-05-045
DMS-05-047
DMS-05-114
DMS-05-115
DMS-05-116
DMS-05-117
DMS-05-118
DMS-05-121
DMS-05-122
323.2
323.8
50.5
042.9
98.7
21.6
3.7
139.5
027.0
042.3
122.1
027.1
047.9
333.6
072.8
007.9
276.0
009.5
290.6
310.5
007.2
299.9
009.7
124.0
067.5
014.4
326.1
LEHIGH
LEHIGH
NORTHAMPTON
LEHIGH
LEHIGH
LEHIGH
NORTHAMPTON
LEHIGH
LEHIGH
LEHIGH
LEHIGH
BERKS
SCHUYLKILL
BERKS
NORTHAMPTON
SCHUYLKILL
BERKS
BERKS
SCHUYLKILL
BERKS
LEHIGH
LEHIGH
NORTHAMPTON
NORTHAMPTON
NORTHAMPTON
CARBON
BERKS
MONROE
MONROE
MONROE
MONROE
BERKS
SCHUYLKILL
NORTHAMPTON
BERKS
15
BERKS
Schoenersville Road NORTHAMPTON
District 6-0
DMS-06-002
DMS-06-003
DMS-06-004
DMS-06-005
DMS-06-006
DMS-06-007
DMS-06-008
DMS-06-009
DMS-06-010
DMS-06-012
DMS-06-013
DMS-06-014
DMS-06-016
DMS-06-017
DMS-06-018
DMS-06-019
DMS-06-020
DMS-06-021
DMS-06-022
DMS-06-023
DMS-06-024
DMS-06-025
DMS-06-026
DMS-06-027
DMS-06-028
DMS-06-029
DMS-06-030
DMS-06-031
DMS-06-032
DMS-06-033
DMS-06-034
DMS-06-035
DMS-06-036
DMS-06-037
DMS-06-038
DMS-06-039
DMS-06-040
DMS-06-041
DMS-06-042
DMS-06-043
DMS-06-044
DMS-06-045
DMS-06-046
DMS-06-047
DMS-06-048
DMS-06-049
DMS-06-050
DMS-06-051
DMS-06-052
DMS-06-053
DMS-06-054
DMS-06-055
DMS-06-056
DMS-06-057
DMS-06-058
010.6
020.1
22
334.8
013.9
N/A
N/A
N/A
N/A
N/A
N/A
N/A
BUCKS
BUCKS
BUCKS
BUCKS
BUCKS
DELAWARE
DELAWARE
BUCKS
BUCKS
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
DELAWARE
DELAWARE
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
BUCKS
BUCKS
BUCKS
CHESTER
CHESTER
CHESTER
CHESTER
MONTGOMERY
MONTGOMERY
PHILADELPHIA
MONTGOMERY
MONTGOMERY
PHILADELPHIA
PHILADELPHIA
MONTGOMERY
DELAWARE
MONTGOMERY
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
0095
2037
2037
0413
0413
8025
0476
0013
0013
0095
0095
0095
0202
0309
0076
0309
0422
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0202
0202
0202
0030
0422
0422
0063
0076
0076
0076
0076
0076
0476
0476
0100
0100
0100
0100
0202
0202
0202
0202
0202
0202
0202
DMS-06-059
DMS-06-060
DMS-06-061
DMS-06-062
DMS-06-063
DMS-06-064
DMS-06-065
DMS-06-066
DMS-06-067
DMS-06-072
DMS-06-073
DMS-06-077
DMS-06-078
DMS-06-079
DMS-06-080
DMS-06-081
DMS-06-100
DMS-06-101
DMS-06-102
DMS-06-104
DMS-06-213
DMS-06-214
DMS-06-215
DMS-06-216
DMS-06-217
DMS-06-218
DMS-06-219
D202S_11
D030W_03
D030W_04
D030E_06
D076E_04
D076E_06
D076W_07
D0001S_50
D0001S_51
D309N_08
D309S_07
D309S_03
D309N_02
D309N_01
D309S_09
D076E_08
P001N_14
P30BW_15
P30BE_16
P095N_18
D291E_01
D030E_01
D030E_02
D202N_12
D023E_01
D023E_03
D023S_02
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CANTILEVER
CANTILEVER
OVERHEAD
OVERHEAD
CANTILEVER
CENTERMOUNT
CENTERMOUNT
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CANTILEVER
CANTILEVER
CENTERMOUNT
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
US 202S south/Plesant Grove Rd
US 30W west/Ship Rd
US 30W west/Whitford Rd
US 30E east/PA 113
I-76 EB MM 334.8
I-76 EB MM 342.8
I-76 WB MM 343.9
US 1 SB before Fox Street
US 1 SB at 2nd Street
PA 309 NB before Stump Road
PA 309 / Hartman Road SB
PA 309 SB before Church Road
PA 309 NB after Church Road
PA 309 Northbound at Willow Grove Ave
PA 309 SB After North Wales Rd.
I-76 EB MM 346.3
RT. 1 NB BEFORE PA 52
US 30 WB APPROACHING US 202
BUSINESS RT. 30 EB BEFORE MOSCOW ROAD
I-95 NB SOUTH OF BLUE BALL AVENUE
I-76 EB at base of Platt Bridge (near 26th Street)
US 30 EB at Valley Creek Corporate Center
US 30 EB East of Ship Road
US 202N north of PA 491
PA 23 EB before William Street
PA 23 EB before Hollow Road
Fayette St. SB before PA 23
D-81N-40
D-81N-58
D-81S-63
D-22E-MID
D-11S-TP
D-22W-CF
D-283N-2
D-83S-46
D-83S-42
D-83N-41
D-15N-114
D-581E-3
D-322W-PH
D-283W-HM
D-81N-1
D-81N-12
D-81S-23
D-81S-40
D-81N-63
D-81N-67
D-81S-68
D-81S-71
D-83N-48
D-83S-48
D-22E-FS
D-22W-FS
D-83N-37
D-83N-40
D-81N-83
D-81S-90
V-81S-75
V-283N-1
V-83N-43
V-22E-FRT
V-81N-55
V-581W-4
V-15N-Wes
V-83N-34
V-15S-EN
V-83S-39
V-22E-NPT
V-83S-24
V-83N-16
V-30W-24
D-581E-6
D-15S-234
D-15N-M.D.
D-30W-15
V-83N-1
D-83N-31
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
SEMI-PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
SEMI-PERMANENT
PERMANENT
CENTERMOUNT
OVERHEAD
OVERHEAD
CENTERMOUNT
CENTERMOUNT
OVERHEAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
OVERHEAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
CONCRETE PAD
OVERHEAD
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
OVERHEAD
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
MP 40
I-81 MM 58
Milepost 62.5 Southbound
US 22/322 at Midway exit
US 11/15 at Trading Post
US 22/322 at Clark's Ferry Bridge
I-283 at Exit 2
I-83 at MM 46
I-83 at Exit 42
I-83 at Exit 40B
US 15 at PA 114 Inter. Northbound
PA 581, MILEPOST 3.6
US 322 at PennHar Exit
PA 283 at Htown/Mtown exits
I-81 at Exit 1
I-81 AT MP 12.3
I-81 MM 23.5
I-81 MM 40
Milepost 63.5 Northbound I-81
Milepost 67.1 Northbound I-81
Milepost 68.4 Southbound I-81
Milepost 71.7 Southbound I-81
Milepost 48.6 Northbound I-83
Milepost 48.6 Southbound I-83
US 22 E. Farm Show
US 22 W. Farm Show
Milepost 36.9 Northbound I-83
Milepost 39.7 Northbound I-83
Milepost 83.8 Northbound I-81
Milepost 90.3 Southbound I-81
Milepost 74.8 Southbound I-81
Milepost 0.7 Northbound I-283
Milepost 43.1 Northbound I-83
Front St. Exit Eastbound US 22/322
Milepost 55.2 Northbound I-81
Milepost 4.1 Westbound PA 581
Wesley Dr. Inter. Northbound US 15
Milepost 34.1 Northbound I-83
Enola Inter. Southbound US 11/15
Milepost 39 Southbound I-83
US 22/322 at Newport Exit
I-83 at Emigsville Exit
I-83 at Queen St Exit
US 30 at Shoe House Rd
Milepost 6.7 Eastbound PA 581
US 15 South at Weirmans Mill Road overpass
US 15 North at Boyle Road overpass
US 30 West prior to US 15 Interchange
I-83 North at MD. Line
I-83 North Mile Marker 31.4. Prior to Exit 32 Newberrytown, PA 382
DMS # 1
DMS # 2
DMS # 3
DMS # 4
DMS # 5
DMS # 6
DMS # 7
DMS # 8
DMS # 9
DMS # 10
DMS # 11
DMS # 12
DMS # 13
DMS # 14
DMS # 15
DMS # 16
DMS # 18
DMS # 19
DMS # 20
DMS # 21
DMS # 22
DMS # 23
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
Old US Route 220, northbound; near Inlows Restaurant south of S.R. 0022 and S.R. 3013 Intersection, rightside
US 22 (Third Ave) State Farms Ins., located on the left side. Map site no. 2
PA 764 : Veeder Root, on left side
PA 764 Overpass: Crosskeys, rightside
T-406 Overpass Ritchey's Tree Farm
US 22 Third Ave. Overpass DMS#6
On ramp to US 22 WB Campground
I-99 at 12th St. North of 17th St.
I-70 WB; approximately .4 Mile East of Breezewood US 30, Breezewood Westbound
I-99 SB North of PA 764 Pinecroft Interchange
I-99 Northbound North of PA764 Pinecroft Interchange
East of PA 453 Intersection - Waterstreet; Leftside
East of Gallitzin/Tunnel Hill Intersection, rightside.
West of the Cresson/Summit Interchange
US 30 Sidling Hill, Rightside
US22 WB East of the Mundy's Corner PA 271 Interchange
Approximately 1/4 mile north of PA45 Intersection and 1 mile north of US22 (Waterstreet) Intersection.
Located near "Old Bedford Village" historical site.
On-Ramp "C" to I-99 from Business US 220 (SR 4009) & Pennsylvania Turnpike
I-99 SB @ Country Ridge Rd (T-494) Overpass
West of Business Rte US 220 (SR 4009) Walmart Distribution Center
Approximately 1 Mile North of the PA 56/I-99 Cessna Interchange at the Old US Rte 220 (SR 4009) Underpass.
334.8
342.8
343.9
346.3
N/A
CHESTER
N/A
CHESTER
N/A
CHESTER
N/A
CHESTER
N/A
MONTGOMERY
N/A
PHILADELPHIA
N/A
PHILADELPHIA
N/A
PHILADELPHIA
N/A
PHILADELPHIA
N/A
MONTGOMERY
N/A
MONTGOMERY
Church Rd/PA 73
MONTGOMERY
PA Turnpike Collector MONTGOMERY
Willow Grove Ave.
MONTGOMERY
N/A
MONTGOMERY
N/A
PHILADELPHIA
DELAWARE
CHESTER
CHESTER
DELAWARE
PHILADELPHIA
CHESTER
CHESTER
CHESTER
MONTGOMERY
MONTGOMERY
MONTGOMERY
0202
0030
0030
0030
0076
0076
0076
0001
0001
0309
0309
0309
0309
0309
0309
0076
0001
0030
3070
0095
0291
0030
0030
0202
0023
0023
0023
44
59
59
Watts
22/322
PA 147
2
46
42
40B
PA Turnpike
5
I-83
Hummelstown
1
14
20
37
65
69
67
70
50
48
Cam. St.
I-81
38
40B
85
90
72
2
44A
PA 39
57
3
Slate Hill
35
I-81
39A
Newport
24
16
Kruetz Crk.
7
Heidlersburg
Bus. US 15
US 15
4
32
CUMBERLAND
CUMBERLAND
CUMBERLAND
PERRY
PERRY
DAUPHIN
DAUPHIN
DAUPHIN
CUMBERLAND
CUMBERLAND
CUMBERLAND
CUMBERLAND
DAUPHIN
DAUPHIN
FRANKLIN
FRANKLIN
FRANKLIN
CUMBERLAND
CUMBERLAND
DAUPHIN
DAUPHIN
DAUPHIN
DAUPHIN
DAUPHIN
DAUPHIN
DAUPHIN
YORK
CUMBERLAND
LEBANON
LEBANON
DAUPHIN
DAUPHIN
DAUPHIN
DAUPHIN
CUMBERLAND
CUMBERLAND
CUMBERLAND
YORK
CUMBERLAND
YORK
PERRY
YORK
YORK
YORK
CUMBERLAND
ADAMS
ADAMS
ADAMS
YORK
YORK
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BEDFORD
BLAIR
BLAIR
HUNTINGDON
BLAIR
CAMBRIA
FULTON
CAMBRIA
HUNTINGDON
BEDFORD
BEDFORD
BEDFORD
BEDFORD
BEDFORD
3344
3424
3435
0131
0181
0290
0291
0171
0170
0261
0311
3460
2000
1300
2400
0000
0000
2015
1042
1950
1950
0729
4076
1300
0004
1975
0081
0081
0081
0022
0011
0022
0283
0083
0083
0083
0015
0581
0322
0300
0081
0081
0081
0081
0081
0081
0081
0081
0083
0083
0022
0022
0083
0083
0081
0081
0081
0283
0083
0022
0081
0581
0015
0083
0011
0083
0022
0083
0083
0030
0581
0015
0015
0030
0083
0083
0400
0538
0020
0451
0417
0404
0060
0070
0612
2144
1349
0675
0390
0939
0002
0110
0235
0401
0630
0664
0681
0715
0484
0485
0954
1464
0745
0364
0396
0834
0911
0741
0002
0430
2238
0250
1436
1247
1899
2840
0633
0550
0081
0120
0340
0991
0385
1045
0403
2355
0105
3013
0022
0764
0022
0022
0099
8004
0099
0070
0099
0099
0022
0022
0022
0030
0022
0453
0220
8007
0099
0056
0099
0250
0210
0030
0161
0150
0270
0250
0335
1471
0391
0390
0090
0011
0380
0100
0111
0030
0470
0750
0011
0301
0035
0105
0380
0225
2890
0365
0675
1650
0305
2191
1965
2155
1360
1060
3320
1540
0990
0225
1205
0520
2475
0700
2715
District 8-0
DMS-08-001
DMS-08-002
DMS-08-003
DMS-08-004
DMS-08-005
DMS-08-006
DMS-08-007
DMS-08-008
DMS-08-009
DMS-08-010
DMS-08-011
DMS-08-012
DMS-08-013
DMS-08-014
DMS-08-015
DMS-08-016
DMS-08-017
DMS-08-018
DMS-08-019
DMS-08-020
DMS-08-021
DMS-08-022
DMS-08-023
DMS-08-024
DMS-08-025
DMS-08-026
DMS-08-027
DMS-08-028
DMS-08-029
DMS-08-030
DMS-08-031
DMS-08-032
DMS-08-033
DMS-08-034
DMS-08-035
DMS-08-036
DMS-08-037
DMS-08-038
DMS-08-039
DMS-08-041
DMS-08-042
DMS-08-043
DMS-08-044
DMS-08-045
DMS-08-046
DMS-08-047
DMS-08-048
DMS-08-049
DMS-08-054
DMS-08-077
040.0
058.0
062.5
002.4
046.0
003.6
001.0
012.3
023.5
040.0
063.5
067.1
068.4
071.7
048.6
048.6
036.9
039.7
083.8
090.3
074.8
000.7
043.1
055.2
004.1
034.1
039.0
016.0
006.7
001.0
031.4
2640
2450
2260
1170
0897
0460
1912
District 9-0
DMS-09-001
DMS-09-002
DMS-09-003
DMS-09-004
DMS-09-005
DMS-09-006
DMS-09-007
DMS-09-008
DMS-09-009
DMS-09-010
DMS-09-011
DMS-09-012
DMS-09-013
DMS-09-014
DMS-09-015
DMS-09-016
DMS-09-018
DMS-09-019
DMS-09-020
DMS-09-021
DMS-09-022
DMS-09-023
DMS-09-024
DMS-09-025
DMS-09-026
DMS-09-027
DMS-09-028
DMS-09-029
DMS-09-030
DMS-09-031
DMS-09-032
DMS-09-033
DMS-09-034
DMS-09-035
DMS # 24
DMS # 25
DMS # 26
DMS # 27
DMS # 28
DMS # 29
DMS # 30
DMS # 31
DMS # 32
DMS # 33
DMS # 34
DMS # 35
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CANTILEVER
CANTILEVER
CANTILEVER
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
09
09
09
09
09
09
09
09
09
09
09
09
SR 0219 SB North of the Galleria Interchange
SR 0219 SB South of Galleria Interchange and North of the PA 56 West Expressway
SR 0219 NB @ SR 3006 (Eisenhower Blvd) Overpass
SR 3016 (Scalp Avenue) West of US 219 Interchange
SR 0056 (Scalp Ave) East of University Park T-701
SR 0056 EB West of the Walters Avenue Underpass
US 30 Eastbound, approximately 250' West of the SR 1011 (E. Graceville Rd) Intersection
US 30 Westbound, approximately 440 feet East of the Bedford/Fulton County Line
I-70 WB; approximately .6 Mile East of Everett US 30 West Exit, Breezewood Westbound, TURNPIKE OWNED.
SR 0070 EB @ I - 76 Turnpike Overpass
SR 0022 (William Penn Hwy) West of US 219 Interchange
SR 0022 (William Penn Hwy) East of Mini-Mall Rd
DMS-42W
DMS-45W
DMS-53E
DMS-53W
DMS-60E
DMS-60W
DMS-62E
DMS-62W
DMS-64E
DMS-64W
DMS-70E
DMS-70W
DMS-73E
DMS-73W
DMS-78E
DMS-78W
DMS-81E
DMS-81W
DMS-86E
DMS-86W
DMS-90E
DMS-90W
DMS-97E
DMS # 17
DMS-42E
DMS-45E
DMS-97W
DMS-130
DMS-140
DMS-150
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
CENTERMOUNT
OVERHEAD
CENTERMOUNT
CENTERMOUNT
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
Emlenton Exit
St. Petersburg-Emlenton Exit
Knox Exit
Knox Exit
Shippenville Exit
Shippenville Exit
Clarion Exit
Clarion Exit
Clarion - New New Bethlehem Exit
Clarion - New Bethlehem Exit
Strattanville Exit
Strattanville Exit
Corsica Exit
Corsica Exit
Brookville-Sigel Exit
Brookville-Sigel Exit
Hazen Exit
Hazen Exit
Reynoldsville Exit
Reynoldsville Exit
DuBois Jeffeson County Airport Exit
DuBois Jeffeson County Airport Exit
DuBois- Brockway Exit
approximately 1/2 mile west of the Indiana/Cambria County Line.
Emlenton Exit
St. Petersburg-Emlenton Exit
DuBois- Brockway Exit
Exit 78 Southbound (Seg. 811/Off. 1690)
Exit 96 Northbound (Seg. 930/Off. 2470)
Exit 99 Southbound (Seg. 1025/Off. 0000)
044.5
049.5
049.5
056.0
056.0
062.5
060.0
063.5
062.0
067.5
068.5
071.0
071.0
076.5
075.5
079.5
078.5
083.5
081.0
089.5
089.5
091.5
094.0
42
45
53
53
60
60
62
62
64
64
70
70
73
73
78
78
81
81
86
86
90
90
97
38.0
42.0
98.0
081.5
093.0
102.5
42
45
97
78
96
99
10
20
21
30
31
40
50
60
70
80
90
110
111
112
120
220
79
89
115
116
225
8
113
300
6
320
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
OVERHEAD
CENTERMOUNT
CENTERMOUNT
OVERHEAD
CENTERMOUNT
OVERHEAD
OVERHEAD
CENTERMOUNT
OVERHEAD
CENTERMOUNT
OVERHEAD
CENTERMOUNT
CENTERMOUNT
OVERHEAD
CENTERMOUNT
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
Carnegie Busway
Carnegie -Greentree VMS
Carnegie OB
Greentree Hill - Middle
Greentree OB
10th Street
Bates Street
Saline St VMS
Edgewood
Greensburg Pike
Penn Hills
Bridgeville
Bridgeville North
Collier Ave
Warrendale
Union Ave
Greensburg Pike Outbound
Rodi Rd
Red Mud Hollow
Wexford
Mt Nebo Rd
Settlers Cabin, 22/30 (Future 0376)
Forest Grove
Chestnut St
Montour Run (Future 0376)
Millvale
064.9
066.2
066.2
067.7
067.7
071.0
072.5
073.6
077.1
078.3
080.7
100
105
5
6
7
8
9
10
11
12
13
14
15
16
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PORTABLE
OVERHEAD
OVERHEAD
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
TRAILER
12
12
12
12
12
12
12
12
12
12
12
12
12
12
I-70 EB, West of I-79 North Junction, South Strabane Twp
I-79 SB, South of Meadowlands, South Strabane Twp
I-70 WB at WV State Line, Donegal Twp
I-70 WB, West of I-79 North Junction, South Strabane Twp
I-70 EB, East of I-79 South Junction
I-79 SB at Allegheny County Line, Cecil Twp
I-70 WB, East of PA Toll 43, Fallowfield Twp
I-79 NB, North of I-70 North Junction, South Strabane Twp
I-79 SB, South of I-70 South Junction, Amwell Twp
I-79 NB, South of I-70 South Junction, Amwell Twp
I-70 EB at Belle Vernon Exit, Rostraver Twp
I-70 EB, West of PA 31, South Huntingdon Twp
I-70 WB at New Stanton Interchange, Borough of New Stanton
I-79 NB at Mount Morris Interchange, Perry Twp
CAMBRIA
CAMBRIA
CAMBRIA
CAMBRIA
CAMBRIA
CAMBRIA
BEDFORD
FULTON
BEDFORD
BEDFORD
CAMBRIA
CAMBRIA
0219
0219
0219
3016
0056
0056
0030
0030
0070
0070
0022
0022
0121
0091
0020
0140
0301
0240
0650
0010
1491
1474
0150
0181
1840
1510
2900
0635
0850
1730
0125
0365
0500
2660
0650
2250
CLARION
CLARION
CLARION
CLARION
CLARION
CLARION
CLARION
CLARION
CLARION
CLARION
CLARION
CLARION
CLARION
JEFFERSON
JEFFERSON
JEFFERSON
JEFFERSON
JEFFERSON
JEFFERSON
JEFFERSON
JEFFERSON
JEFFERSON
JEFFERSON
INDIANA
VENANGO
VENANGO
CLEARFIELD
BUTLER
BUTLER
BUTLER
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0022
0080
0080
0080
0079
0079
0079
0445
0494
0494
0560
0560
0621
0600
0635
0620
0671
0684
0710
0710
0761
0754
0791
0784
0831
0810
0895
0891
0915
0940
0402
0380
0420
0985
0811
0930
1025
2003
0000
0000
0944
0944
0385
1375
0557
0280
3114
0000
2535
2535
0400
2174
0565
2389
1050
2389
2052
2040
1939
2180
0950
2335
0750
2490
1690
2470
0000
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
0279
0279
0279
0279
0279
0376
0376
0376
0376
0376
0376
0079
0079
0079
0079
0279
0376
0376
0079
0079
0279
0022
0079
0028
0060
0028
0010
0024
0025
0034
0035
0010
0025
0035
0071
0085
0105
0510
0530
0554
0744
0131
0903
0000
0000
2095
2095
0570
0000
1108
1583
2370
1165
0905
1380
0454
0200
1000
WASHINGTON
WASHINGTON
WASHINGTON
WASHINGTON
WASHINGTON
WASHINGTON
WASHINGTON
WASHINGTON
WASHINGTON
WASHINGTON
WESTMORELAND
WESTMORELAND
WESTMORELAND
GREENE
0070
0079
0070
0070
0070
0079
0070
0079
0079
0079
0070
0070
0070
0079
0170
0401
0002
0165
0210
0491
0381
0378
0305
0310
0404
0494
0565
0004
0380
0938
1795
1756
1964
2261
1498
2000
1200
1100
0675
1415
2023
0000
District 10-0
DMS-10-004
DMS-10-005
DMS-10-006
DMS-10-007
DMS-10-008
DMS-10-009
DMS-10-010
DMS-10-011
DMS-10-012
DMS-10-013
DMS-10-014
DMS-10-015
DMS-10-016
DMS-10-017
DMS-10-018
DMS-10-019
DMS-10-020
DMS-10-021
DMS-10-022
DMS-10-023
DMS-10-024
DMS-10-025
DMS-10-026
DMS-10-027
DMS-10-028
DMS-10-029
DMS-10-030
DMS-10-031
DMS-10-032
DMS-10-033
District 11-0
DMS-11-001
DMS-11-002
DMS-11-003
DMS-11-004
DMS-11-005
DMS-11-006
DMS-11-007
DMS-11-008
DMS-11-009
DMS-11-010
DMS-11-011
DMS-11-012
DMS-11-013
DMS-11-014
DMS-11-015
DMS-11-016
DMS-11-017
DMS-11-018
DMS-11-020
DMS-11-021
DMS-11-022
DMS-11-024
DMS-11-025
DMS-11-026
DMS-11-027
DMS-11-028
051.2
053.3
055.6
074.6
007.0
078.3
080.7
069.3
072.7
010.0
061.6
062.2
058.8
District 12-0
DMS-12-001
DMS-12-002
DMS-12-005
DMS-12-006
DMS-12-007
DMS-12-008
DMS-12-009
DMS-12-010
DMS-12-011
DMS-12-012
DMS-12-013
DMS-12-014
DMS-12-015
DMS-12-016
017.0
040.0
004.5
017.5
020.0
049.0
037.0
038.0
030.5
031.0
041.0
049.0
056.0
001.0
6
17
25
48
37
40
30
33
42
51
54
1
PennDOT Existing HAR
Statewide_ID
District_ID
STATE ROUTE
SEGMENT
OFFSET
LATITUDE_DD
LONGITUDE_DD
Manufacturer
Model
POWER
COMMUNICATIONS
Broadcast
Install Date
Radius (Miles)
Software
District 1-0
HAR-01-001
HAR-01-002
HAR-01-003
HAR-01-004
HAR-01-005
Saegertown
Ohio
I-79/I-90
New York
HAR-42
0079
0090
0090
0090
0038
1534
0020
0220
0455
0010
2400
2000
1300
2100
1025
41.71700
41.94290
42.03603
42.24750
41.17494
-80.19500
-80.47600
-80.11329
-79.76880
-79.73841
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Black Max
Black Max
Black Max
Black Max
Black Max
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
POTS
POTS
POTS
POTS
POTS
5
5
5
5
4
Nov-03
Mar-06
Nov-03
Jan-07
Aug-07
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
HAR 2
HAR 3
HAR 4
HAR 5
HAR 7
HAR 8
HAR 9
HAR 97
HAR 101
HAR 111
HAR 120
HAR 123
HAR 133
HAR 147
HAR 158
HAR 173
HAR 178
HAR 185
HAR 192
HAR 106
0322
0099
0099
0099
0022
0022
0219
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0080
0690
0744
0820
0502
0191
0580
0964
1021
1105
1191
1224
1345
1460
1584
1725
1781
1860
1900
1054
0146
0000
1940
2365
1550
0160
0475
0981
2359
1722
0262
1575
2113
0407
0548
1319
0000
1923
2155
40.81150
40.81660
40.82870
40.89660
40.60410
40.57440
41.97720
41.14500
41.12450
41.09870
41.04020
41.02230
40.98080
41.02040
40.95460
41.03070
41.06040
41.05290
41.06300
41.12166
-78.07540
-77.93980
-77.84030
-77.73640
-77.58400
-77.36820
-78.62620
-78.78850
-78.68840
-78.52580
-78.39860
-78.35110
-78.13420
-77.94900
-77.75150
-77.52660
-77.43160
-77.29750
-77.21550
-78.61760
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Solar Max
Solar Max
Solar Max
Solar Max
Solar Max
Solar Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
HiWay Max
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/SOLAR
BATTERY/SOLAR
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
BATTERY/ELECTRIC
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
Feb-06
Feb-06
Dec-06
Dec-06
Dec-06
Dec-06
Jan-10
Aug-00
Aug-00
Aug-00
Aug-00
Aug-00
Aug-00
Aug-00
Aug-00
Aug-00
Aug-00
Aug-00
Aug-00
Dec-10
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
SITE 1
SITE 2
SITE 3
SITE 4
SITE 5
SITE 6
SITE 7
SITE 8
SITE 9
SITE10A
0080
0081
0081
0081
0315
0006
0380
0084
I476
0084
2590
1664
1424
1591
0160
0255
0191
0081
1774
2407
1837
0600
2513
0694
2693
2303
0531
2255
41.04390
41.22770
40.94280
41.14672
41.31064
41.42124
41.31360
41.40726
41.48250
41.35910
-76.01960
-75.87110
-76.02420
-75.96426
-75.75884
-75.60272
-75.54740
-75.50445
-75.69380
-74.70997
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
PC-900/PT-1000
PC-900/PT-1000
PC-900/PT-1000
PT-1000
PT-1000
PT-1000
PC-900/PT-1000
PT-1000
PC-900/PT-1000
PC-900/PT-1000
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
2
2
2
2
2
2
2
2
2
2
Jan-01
Jan-01
Jan-01
Jan-01
Jan-01
Jan-01
Jan-01
Jan-01
Jan-01
Nov-08
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
HAR "A"
HAR "B"
HAR "C"
HAR "D"
HAR "E"
HAR "F"
HAR "G"
HAR "H"
HAR No. 1
HAR No. 2
HAR No. 3
HAR No. 4
HAR 78 EXIT 16
HAR 78 EXIT 29
HAR 78 EXIT 40
Haml
40.36018
-75.28680
0078
0022
0078
0022
0495
0010
0604
0160
0900
0300
0645
0400
40.57979
40.65048
40.55488
40.68310
-75.62540
-75.40973
-75.42893
-75.28725
0022
0078
0078
0078
0078
0078
0078
0078
0160
0401
0351
0225
0165
1575
2450
0100
2550
2000
40.61959
40.57809
40.56757
40.51599
40.47780
40.4865
40.5574
40.5776
-75.49913
-75.79869
-75.96656
-76.11947
-76.29389
-76.2451
-75.9981
-75.7984
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
DR1500AM
Solar Max DR1500AM
DR1500AM
DR1500AM
DR1500AM
DR1500AM
Solar Max DR1500AM
DR1500AM
Solar Max DR1500AM
Solar Max DR1500AM
Solar Max DR1500AM
Solar Max DR1500AM
Highway Max DR 1500AM
Highway Max DR 1500AM
Highway Max DR 1500AM
ELECTRIC
BATTERY/SOLAR
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
BATTERY/SOLAR
ELECTRIC
BATTERY/SOLAR
BATTERY/SOLAR
BATTERY/SOLAR
BATTERY/SOLAR
ELECTRIC
ELECTRIC
ELECTRIC
POTS
CELLULAR
POTS
POTS
POTS
POTS
CELLULAR
POTS
CELLULAR
CELLULAR
CELLULAR
CELLULAR
CELLULAR
CELLULAR
CELLULAR
5
6
6
6
6
5
6
5
5
5
5
6
6
6
Jan-00
Jan-99
Jan-99
Jan-02
Jan-99
Jan-99
Jan-99
Jan-04
Jan-07
Jan-07
Jan-07
Jan-07
Nov-10
Nov-10
Nov-10
H-83-48
H-581-3
H-81-63
H-81-42
H-81-52
H-322-147
H-81-78
H-81-89
H-283-HM
H-83-37
H-15-114
H-81-7
H-81-16
H-81-24
H-83-22
3020
0581
0081
0081
0081
0022
0081
0081
0300
0083
0015
0081
0081
0081
0083
0071
0061
0634
0415
0825
0135
40.27890
40.23670
40.30940
40.16633
40.23467
40.39567
40.37750
40.42450
40.21382
40.18968
40.17705
39.80683
39.92870
40.01562
39.99295
-76.81830
-76.97470
-76.94360
-77.27583
-77.12792
-77.00717
-76.67400
-76.52083
-76.70832
-76.84532
-76.98675
-77.70367
-77.63560
-77.53343
-76.73462
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
Black Max Model DRTXM3 AM
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
7
7
6
6
6
6
6
6
6
6
6
6
6
6
6
Dec-99
Dec-99
Dec-99
Jun-08
Jun-08
Jun-08
Jun-08
Jun-08
Jun-08
Jun-08
Jun-08
Jun-08
Jun-08
Jun-08
May-10
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
HAR 01
HAR 03
HAR 1
PTC-O&M
PTC-O&M
0022
0219
0350
0070
0099
0161
0070
0030
2865
0220
1668
40.44130
40.27997
40.71600
39.99726
40.05713
-78.43550
-78.84808
-78.17570
-78.23702
-78.51904
Highway Information Systems
Highway Information Systems
Highway Information Systems
DR2000
DR2000
DR2000
ELECTRIC
ELECTRIC
BATTERY/ELECTRIC
POTS
CELLULAR
T-1
POTS
POTS
Jan-01
Jul-08
Feb-06
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
HAR-1
HAR-42
0228
0038
0011
0010
1030
1025
40.68524
41.17494
-80.09741
-79.73841
Highway Information Systems
Highway Information Systems
Black Max
Black Max
ELECTRIC
BATTERY/ELECTRIC
POTS
POTS
Jan-00
Aug-07
DR2000 Platinum
DR2000 Platinum
District 2-0
HAR-02-001
HAR-02-002
HAR-02-003
HAR-02-004
HAR-02-006
HAR-02-007
HAR-02-008
HAR-02-010
HAR-02-011
HAR-02-012
HAR-02-013
HAR-02-014
HAR-02-015
HAR-02-016
HAR-02-017
HAR-02-018
HAR-02-019
HAR-02-020
HAR-02-021
HAR-02-023
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
District 3-0
District 4-0
HAR-04-001
HAR-04-002
HAR-04-003
HAR-04-004
HAR-04-005
HAR-04-006
HAR-04-007
HAR-04-008
HAR-04-009
HAR-04-011
District 5-0
HAR-05-001
HAR-05-002
HAR-05-003
HAR-05-004
HAR-05-005
HAR-05-006
HAR-05-007
HAR-05-008
HAR-05-009
HAR-05-010
HAR-05-011
HAR-05-012
HAR-05-013
HAR-05-014
HAR-05-015
District 8-0
HAR-08-001
HAR-08-002
HAR-08-003
HAR-08-004
HAR-08-005
HAR-08-006
HAR-08-007
HAR-08-008
HAR-08-009
HAR-08-010
HAR-08-011
HAR-08-012
HAR-08-013
HAR-08-014
HAR-08-026
District 9-0
HAR-09-001
HAR-09-002
HAR-09-003
HAR-09-901
HAR-09-902
District 10-0
HAR-10-001
HAR-10-002
3
4
HAR-10-003
HAR-10-004
HAR-10-005
HAR-10-006
HAR-10-007
HAR-10-008
HAR-10-009
HAR-10-010
HAR-10-011
HAR-10-012
HAR-45
HAR-53
HAR-60
HAR-64
HAR-70
HAR-73
HAR-78
HAR-81
HAR-86
HAR-90
0478
3007
0066
0066
0322
0949
0036
0028
0830
0080
10
20
30
40
60
70
80
71
32
11
0060
0279
0279
0376
0079
0079
0279
0079
0028
0060
50
90
42
43
0070
0070
0079
0070
0050
0080
0330
0310
0520
0022
0720
0240
0020
0895
0791
1456
0000
0615
0210
2300
0780
0485
2000
2173
0015
0054
1100
3600
0521
0660
0120
2530
2225
1250
41.18268
41.17943
41.19677
41.17581
41.18285
41.18620
41.17142
41.16764
41.15919
41.15254
-79.67542
-79.54022
-79.42542
-79.34718
-79.24458
-79.19794
-79.09602
-79.04582
-78.82451
-78.90942
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
POTS
40.47081
40.41239
40.43709
40.44135
40.35531
40.52227
40.50729
40.61471
40.47856
40.44738
-80.22247
-80.07709
-80.01325
-79.82674
-80.11880
-80.13115
-80.03544
-80.09555
-79.96749
-80.16532
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
Black Max
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
POTS
FIBER
FIBER
FIBER
POTS
POTS
FIBER
FIBER
POTS
FIBER
40.18405
40.14015
39.79206
40.11621
-80.22773
-79.84501
-80.07700
-80.44483
Highway Information Systems
Highway Information Systems
Highway Information Systems
Highway Information Systems
Black Max
Black Max
Black Max
Black Max
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
POTS
POTS
POTS
POTS
4
6
6
4
4
4
3
3
4
4
Aug-07
Aug-07
Aug-07
Aug-07
Aug-07
Aug-07
Aug-07
Aug-07
Aug-07
Aug-07
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
Oct-01
Dec-98
Dec-98
Oct-01
Dec-97
Oct-00
Oct-00
Jan-08
Jul-08
Oct-08
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
District 11-0
HAR-11-001
HAR-11-002
HAR-11-003
HAR-11-004
HAR-11-005
HAR-11-006
HAR-11-007
HAR-11-008
HAR-11-009
HAR-11-010
3
District 12-0
HAR-12-001
HAR-12-002
HAR-12-003
HAR-12-004
0184
0420
0054
0044
0760
2895
0000
1505
2
2
2
2
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
DR2000 Platinum
PennDOT Existing CCTV
Statewide_ID
District_ID
STATUS
TYPE
STRUCTURE
POLE HEIGHT (in
feet)
DISTRICT
Descriptive Location
MILEMARKER
EXIT NUMBER
COUNTY
STATE
ROUTE
SEGMENT
OFFSET
LATITUDE_DD
LONGITUDE_DD
Manufacturer
Model
POWER
COMMUNICATIONS
Install Date
Software
District 1-0
EXISTING
PORTABLE
OTHER
CCTV 2
CCTV 3
CCTV 4
CCTV 6
CCTV 9
CCTV 10
CCTV 13
CCTV 14
CCTV 11
CCTV 15
CCTV 16
CCTV 17
CCTV 18
CCTV 19
CCTV 20
CCTV 21
CCTV 22
CCTV 23
CCTV 24
CCTV 25
CCTV 26
CCTV 27
CCTV 28
CCTV 30
CCTV 31
CCTV 34
CCTV 35
CCTV 36
CCTV 50
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
Camera 1
Camera 2
Camera 3
Camera 4
Camera 5
Camera 6
Camera 7
Camera 8
Camera 1Portable
Camera 2 Portable
Camera 3 Portable
Camera 4 Portable
Camera 9
Camera 20
Camera 10
Camera 11
Camera 12
Camera 13
Camera 14
Camera 15
Camera 16
Camera 21
Camera 22
Camera 19
Camera 18
Camera 17
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PORTABLE
PORTABLE
PORTABLE
PORTABLE
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
CCTV No.1
CCTV No.2
CCTV No.3
CCTV No.4
CCTV No.5
CCTV No.6
CCTV No.8
CCTV No.9
CCTV No.10
CCTV No.11
CCTV No.12
CCTV No.13
CCTV No.14
CCTV No.15
CCTV No.16
CCTV No.17
CCTV No.18
CCTV No.19
CCTV No.20
CCTV No.21
CCTV No.22
CCTV No.23
CCTV No.24
CCTV No. 29
CCTV No. 28
CCTV No. 27
CCTV No. 26
CCTV No. 25
CCTV No. 30
CCTV No. 31
CCTV No. 32
CCTV No. 33
CCTV No. 34
CCTV No. 35
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
CM 1
CM 2
CM 3
CM 4
CM 5
CM 6
CM 7
CM 8
CM 9
CM 10
CM 11
CM 12
CM 4700
CM 4710
CM 4711
CM 4712
CM 4713
CM 4721
CM 4722
CM 4723
CM 4724
CM 4725
CM 4726
CM 4727
CM 4728
CM 4729
CM 4731
CM 180
CM 181
CM 182
CM 183
CM 184
CM 185
CM 186
CM 187
CM 188
CM 189
CM 191
CM 201
CM 202
CM 203
CM 204
CM 205
CM 206
CM 207
CM 208
CM 209
CM 210
CM 211
CM 212
CM 213
CM 214
CM 215
CM 216
CM 217
CM 218
CM 219
CM 220
CM 221
CM 222
CM 223
CM 224
CM 225
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
CAM-01-011
01
I-90 AT PA 97 EXIT 27 INTERCHANGE
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
SR 0322 ByPass Westbound, Port Matilda
I-99 Northbound, Near Scotia Road, Greys Woods
I-99 Northbound, Near Park Avenue
I-99 Northbound at Weaver Hill
I-80 Eastbound at Milesburg
I-80 Westbound at Milesburg
SR 0322 Westbound near Branch Road, at Advance Warning DMS
SR 0022 Bypass, at Electric Avenue
I-99 at Port Matilda
SR 0022 Westbound at Westbound end of Narrows
SR 0022 Westbound at Eastbound end of Narrows
SR 0219 & SR 4002, Bradford
SR 0219 & SR 4015, Bradford
SR 0219 & SR 346 West Bradford
SR 0219 & Mill St.
SR 0219 & SR 46
SR 0219 & SR 346 Foster Brook
SR 0219 & SR T-369
SR 0150 & SR 0026, State College
SR 0219, Liberty Boulevard, DuBois
SR 0255, Shaffer Ave., DuBois
I-80 Exit 97 (I-80 / US 219 Interchange), I-80-B28 Job
I-80 Exit 101 (I-80 / PA 255 Interchange), I-80-B28 Job
I-80 Exit 111 (I-80 WB), I-80-B28 Job
I-80 Exit 120 (I-80 / PA 879 Interchange), I-80-B28 Job
SR 0322 / SR 0153, SR 0153-N23 Job
SR 0322 / SR 0879, SR 0153-N23 Job
SR 0322 / SR 0970, SR 0153-N23 Job
SR 0150 & SR 2015, Mill Hall
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
OTHER
OTHER
OTHER
OTHER
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
50
50
50
50
50
50
50
50
30
30
30
30
50
50
50
50
50
50
50
50
50
50
50
50
50
50
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
50
50
40
70
70
50
50
70
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
70
70
70
70
70
70
70
70
70
70
70
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
POLE
OTHER
POLE
POLE
POLE
OTHER
POLE
OTHER
POLE
OTHER
OTHER
POLE
POLE
POLE
POLE
OTHER
OTHER
POLE
OTHER
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
50
027.0
27
074.0
082.0
158.0
158.0
74
81
158
158
061.0
61
ERIE
0090
0264
2449
42.04111
-80.02245
ASTI
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
CENTRE
MIFFLIN
CENTRE
MIFFLIN
JUNIATA
MCKEAN
MCKEAN
MCKEAN
MCKEAN
MCKEAN
MCKEAN
MCKEAN
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLEARFIELD
CLINTON
0322
I-99
I-99
I-99
0080
0080
0322
0322
I-99
0022
0022
0219
0219
0219
0219
0219
0219
0219
0150
0219
0255
0080
0080
0080
0080
0322
0879
0322
0150
0251
0690
0740
0820
1570
1575
0537
0270
0610
0613
0063
0492
0540
0550
0560
0570
0580
0594
0012
0870
0040
0964
1010
1111
1195
0430
0310
0560
0152
0640
0146
2640
1880
1720
1120
2828
0700
2470
0575
1240
0340
0080
0400
0600
0000
0100
1135
0165
2930
0150
0330
0315
2420
0720
0360
1060
2740
0380
40.81152
40.81767
40.82867
40.89655
40.95588
40.95608
40.79620
40.61560
40.80393
40.58018
-78.07475
-77.93973
-77.84030
-77.73637
-77.77533
-77.76720
-77.82116
-77.57620
-78.06375
-77.53855
40.61156
41.92952
41.95307
41.95830
41.96427
41.96843
41.97802
41.99627
40.82946
41.12688
41.12245
41.14678
41.12956
41.09858
41.03959
41.02645
41.02392
41.00010
41.11410
-77.44722
-78.64877
-78.64610
-78.64243
-78.63857
-78.62970
-78.62585
-78.62043
-77.80514
-78.75511
-78.72905
-78.78988
-78.70846
-78.52572
-78.39835
-78.43828
-78.41625
-78.34763
-77.48130
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
BATTERY/SOLAR
WIRELESS
Dec-10
LTC 7960/60-20XPM
ENVD2460P
ENVD2460P
ENVD2460P
ENVD2460P
ENVD2460P
ENVD2460P
ENVD2460P
ENVD2460P
ENVD2460P
ENVD2460P
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
ENVD2460P
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
VG4-323-ECSOP
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
BATTERY / ELECTRIC
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
Feb-06
Feb-06
Dec-06
Dec-06
Dec-06
Dec-06
Jun-07
Oct-06
Feb-08
Dec-06
Dec-07
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-08
Feb-09
Feb-09
Oct-09
Oct-09
Oct-09
Oct-09
Feb-10
Feb-10
Feb-10
Oct-10
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
DIVAR
District 2-0
CAM-02-001
CAM-02-002
CAM-02-003
CAM-02-004
CAM-02-005
CAM-02-006
CAM-02-007
CAM-02-008
CAM-02-012
CAM-02-014
CAM-02-015
CAM-02-016
CAM-02-017
CAM-02-018
CAM-02-019
CAM-02-020
CAM-02-021
CAM-02-022
CAM-02-023
CAM-02-024
CAM-02-025
CAM-02-026
CAM-02-027
CAM-02-029
CAM-02-030
CAM-02-033
CAM-02-034
CAM-02-035
CAM-02-049
097.0
101.0
110.0
120.0
97
101
111
120
I-80 & Rt 93 Drum, Pa Luzerne Co. 80 WB
Junction of I-80 and I-81 80 EB
Exit 164 (SR0029) on I-81 SB
Exit 168 on I-81 Highland Blvd. 81 NB
Exit 175 on I-81 Near Park and Ride 81 NB
Camera located in Stockpile 14 on SR315 NB
I-81 Exit 182 Davis St./Montage MTn. 81 NB side
I-81/I-84/Rt 6 Junction left side of 81 SB ramp from Rt. 6
SR 435 WB at I-380 gore area, segment 310/1309
I-81SB,MM 195 at Turnpike ramp
I-81 NB MM 189.1 Right Shoulder
81 NB, north of Exit 182 on concrete pad
I-81 @ Exit 184, River Street
380/84, Split I-84 EB on Left side
I-380 / SR 307 Interchange – Exit 20 380 NB side
I-84, Exit 8 Mt. Cobb
I-81 @ RT 0093, Exit 145
I-80 @ PA 0309,Exit 262 i-80 EB
I-81 Nuangola Rest Area (SB) - MM 158 (approx. 1 mile South of closest
I-81 Dorrance Rest Area (NB) – MM 156 (~ 1 mile North of closest exit)
I-84 at 6/209 Matamoras Interchange I-84 EB
I-81, US 11, Rt. 6 Business Interchange
I-81 @ Exit 206, PA 374 In median
I-81 at 848 Interchange Exit 219 I-81 NB
I-81 at Great Bend Welcome Center – Exit 230 I-81 SB
I-84 / SR 739 Interchange – Exit 34 I-84 EB
256.0
259.6
164.3
168.3
174.9
175.0
181.9
187.0
001.8
193.7
189.1
183.2
184.3
023.0
019.5
008.4
145.7
262.6
158.0
156.0
053.2
191.2
206.2
219.4
231.8
034.3
256
168
164
168
175
175
182
187
2
194
178
184
185
24
20
8
145
262
155
159
53
191
211
219
230
34
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LUZERNE
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LACKAWANNA
LUZERNE
LUZERNE
LUZERNE
LUZERNE
PIKE
LACKAWANNA
SUSQUEHANNA
SUSQUEHANNA
SUSQUEHANNA
PIKE
0080
0080
0081
0081
0081
0315
0081
0081
0084
0081
0081
0081
0081
0380
0380
0084
0081
0080
0081
0081
0084
0081
0081
0081
0081
0084
2555
2594
1641
1680
1744
0160
1814
1870
0015
1935
1890
1830
1840
0040
0194
0081
1455
2624
1575
1560
0530
1911
2060
2190
2315
0340
2388
0528
1362
1626
2048
2323
2133
1943
1606
1045
0464
1457
1605
0163
0126
2303
0727
0612
2462
0052
1140
1437
1478
2027
1291
1858
41.02643
41.04510
41.20173
41.23465
41.30424
41.31057
41.37101
41.42241
41.40108
41.48259
41.43993
41.38228
41.39323
41.37334
41.31361
41.40722
40.98095
41.05364
41.13005
41.10128
41.35767
41.45686
41.65151
41.82390
41.98397
41.35756
-76.07906
-76.01438
-75.90618
-75.84689
-75.76702
-75.75953
-75.68315
-75.60638
-75.58590
-75.68063
-75.62872
-75.66402
-75.65078
-75.57137
-75.54637
-75.50430
-76.03627
-75.95931
-75.96322
-75.96086
-74.71267
-75.65984
-75.65799
-75.68027
-75.74769
-75.05612
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Cylink
ASTI
ASTI
ASTI
ASTI
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
0807-004
EZ CAM
EZ CAM
EZ CAM
EZ CAM
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
G3-AUTODOME
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
BATTERY/SOLAR
BATTERY/SOLAR
BATTERY/SOLAR
BATTERY/SOLAR
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
T-1
T-1
T-1
T-1
T-1
T-1
T-1
OTHER
CELLULAR
CELLULAR
CELLULAR
CELLULAR
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
Jan-08
Jan-08
Jan-08
Jan-00
Jan-08
Jan-08
Jan-00
Jan-00
Jan-07
Jan-07
Jan-07
Jan-07
Jan-08
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
At US 22 MacArthur Road/7th Street Rt.145 NE Quad
At I-78 Exit 49 Rt.100 NW Quad
At US 22 Airport Road Rt.987 SE Quad
At Rt.512 NW Quad
At Cedar Crest NE Quad
At Fullerton Ave SE Quad
At Schoenersville Rd. SE Quad
At Rt.191 SW Quad
At Rt.309 SW Quad
PA 33 at US 22 Interchange
At 15th St. SW Quad
At RT.309/Tilghman St.NW Quad
At I-78 Exit 55 Cedar Crest NE Quad
At I-78 Exit 60 Rt.309/Rt.145 SE Quad
At I-78 Exit 51 US 22/I-78 Split
At I-78 Exit 54 Rt.222 SW Quad
PA 33 SB At PA 248 NW Quad
At I-78 Exit 75 Morgan Hill SW Quad
At I-78 Exit 71 Rt.33 NW Quad
At US 22 2nd and Bushkill Streets
At I-78 Exit 67 Rt.412 SW Quad
At I-78 Exit 57 Lehigh St. SW Quad
At Rt.222 and Rt.100 SE Quad
At I-78 Exit 40 Rt.737 NW Quad
At I-78 Exit 35 Rt.143 NW Quad
At I-78 Exit 29 Rt.61 NE Quad
At I-78 Exit 19 Rt.183 SW Quad
At I-78 Exit 10 Rt.645 NW Quad
At I-81 Exit 107 Rt.209 NW Quad
At I-81 Exit 119 HighRidge Dr. SE Quad
At I-81 Exit 124 Rt.61 South Median
At I-80 Exit 277 Rt.940/Turnpike NE Quad
At I-80 Exit 309 Rt.209 NE Quad
At I-380 Exit 3 Rt.940 NE Quad
321.5
049.7
324.4
327.3
318.6
322.2
325.7
329.8
317.0
004.1
320.4
PA 145/MacArthurLEHIGH
Rd
49
LEHIGH
Airport Rd
LEHIGH
PA 512
NORTHAMPTON
Cedar Crest
LEHIGH
Fullerton Ave
LEHIGH
Schoenersville NORTHAMPTON
PA 191
NORTHAMPTON
PA 309
LEHIGH
PA 33/US 22
NORTHAMPTON
15th St
LEHIGH
Tilghman St
LEHIGH
55
LEHIGH
60
LEHIGH
US 22/I-78 Split LEHIGH
54
LEHIGH
PA 248
NORTHAMPTON
75
NORTHAMPTON
71
NORTHAMPTON
2nd Street
NORTHAMPTON
67
NORTHAMPTON
57
LEHIGH
PA 100
LEHIGH
40
BERKS
35
BERKS
29
BERKS
19
BERKS
10
BERKS
107
SCHUYLKILL
119
SCHUYLKILL
124
SCHUYLKILL
277
CARBON
309
MONROE
3
MONROE
0022
0078
0022
0022
0022
0022
0022
0022
0022
0033
0022
0309
0078
0078
0022
0078
0033
0078
0078
0022
0078
0078
0222
0078
0078
0078
0078
0078
0081
0081
0081
0080
0080
0380
0180
0494
0240
0040
0130
0190
0010
0100
0090
0017
0160
0240
0554
0604
0062
0544
0071
0750
0710
0250
0664
0574
0132
2810
1300
0050
2170
0025
3300
0075
0450
3770
2450
1820
0025
1500
0090
0380
0700
0270
1089
1725
2555
0150
0650
1700
40.62668
40.58000
40.64322
40.66273
40.60976
40.63081
40.64983
40.67836
40.59966
40.68314
40.61850
40.59007
40.56790
40.55459
40.58953
40.57232
40.71778
40.67007
40.63836
40.69443
40.59624
40.56437
40.55883
40.57760
40.57740
40.55740
40.49940
40.46650
40.62020
40.73500
40.77310
41.06680
40.99870
41.10620
-75.48280
-75.62498
-75.43159
-75.38435
-75.53161
-75.47001
-75.41038
-75.34261
-75.56030
-75.28912
-75.50123
-75.55428
-75.51862
-75.43006
-75.58876
-75.54014
-75.28840
-75.21402
-75.27311
-75.20752
-75.34055
-75.48507
-75.60850
-75.79840
-75.89030
-75.99810
-76.18560
-76.34030
-76.43850
-76.30620
-76.22470
-75.70170
-75.15440
-75.39750
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ENVT120P Dome
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
Jan-04
Jan-04
Jan-04
Jan-04
Jan-05
Jan-06
Jan-06
Jan-06
Jan-05
Jan-04
Jan-05
Jan-08
Jan-06
Jan-04
Jan-05
Jan-04
Jan-09
Jan-06
Jan-04
Jan-08
Jan-05
Jan-08
Jan-07
Oct-10
Oct-10
Oct-10
Oct-10
Oct-10
Oct-10
Oct-10
Oct-10
Oct-10
Oct-10
Oct-10
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
Philips/Bosch GUI version 2.43
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
I-95 SB @ ISLAND AVE/ PIA
I-95 SB @ ENTERPRISE / BARTRAM
I-95 SB @ BROAD ST
I-95 NB @ WWB /PACKER AVE
I-95 SB @ PACKER /FRONT
I-95 SB @ TASKER /REED
I-95 NB @ WASHINGTON / COLUMBUS
I-95 NB @ VINE EXP / BF BRIDGE
I-95 NB @ RACE ST
I-95 SB @ VINE / CALLOWHILL
I-95 SB @ GIRARD AVE
I-95 SB @ ARAMINGO / GIRARD
I-95 NB RAMP TO NB I-476
I-476 NB north of Rt. 1 (mm 5.9)
I-476 NB at Reed Rd (mm 6.8)
I-476 NB at mm 7.4
I-476 NB at Lawrence Rd (mm 8.1)
Rt. 30 Ramp to I-476 SB
I-476 at Rt. 30 (mm 13.2 - median)
I-476 SB at mm 13.9
I-476 SB before County Line Rd. (mm 14.4)
I-476 NB 1 mile before I-76
I-476 NB at I-76
I-476 SB at Schuylkill River Bridge (mm 16.7)
I-476 NB near mm 17
I-476 SB south of Ridge Pike (mm 18.5)
I-476 NB north of Ridge Pike (mm 19.1)
US RT 100 NB AT PHOENIXVILLE PIKE
US RT 100 NB BEFORE KIRKLAND AVE
US RT 100 SB AFTER BOOT ROAD
US RT 100 SB BEFORE PA 100 BUSINESS
US RT 100 NB BEFORE MOUNTAIN VIEW DR
US RT 100 NB AT LINCOLN HIGHWAY
US RT 100 NB AT SUNRISE BLVD.
US RT 100 NB BEFORE SHIP RD.
US RT 100 NB AT WORTHINGTON RD
US RT 100 SB AFTER PA 113
US RT 100 NB AT PA TURNPIKE
US 202 SB @ HENDERSON RD
US 202 NB @ ALLENDALE RD
US 202 NB @ I-76
US 202 SB @ PA 422
US 202 NB @ WEST VALLEY RD
US 202 SB @ PA 252
US 202 NB NORTH OF PA 252
US 202 NB NORTH OF CHESTERBROOK
US 202 SB @ HOWELLVILLE RD
US 202 NB NORTH OF NORTH VALLEY RD
US 202 SB NORTH OF CEDAR HOLLOW RD
US 202 NB @ PA 29
US 202 NB NORTH OF MILL RD
US 202 SB @ CHURCH RD
US 202 NB SOUTH OF PA 401
US 202 SB @ US 30
US 202 SOUTH OF KING RD
US 202 NB AT MORSTEIN RD
US 202 NB AT BOOT RD
US 202 SB SOUTH OF SR 100
US 202 SB NORTH OF SR 322
US 202 NB NORTH OF PAOLI PIKE
US 202 NB SOUTH OF WEST CHESTER PIKE
US 202 NB NORTH OF WESTTOWN ROAD
US 202 NB SOUTH OF WEST CHESTER LINE
12
15
17
19
19
20
20
22
22
22
23
23
7
N/A
N/A
N/A
N/A
13
N/A
N/A
N/A
N/A
16
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0476
0476
0476
0476
8039
0476
0476
0476
0476
0476
0476
0476
0476
0476
0100
0100
0100
0100
0100
0100
0100
0100
0100
0100
0100
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
0202
39.89313
39.88720
39.89937
39.90733
39.91020
39.92792
39.93837
39.95302
39.95590
39.95855
39.96708
39.97355
39.86698
39.94522
39.95378
39.96300
39.97279
40.03603
40.03858
40.04597
40.05177
40.05721
40.06373
40.07530
40.08280
40.09461
40.10004
39.99608
40.00290
40.00770
40.01257
40.01718
40.02800
40.03852
40.04652
40.05498
40.05650
40.07117
40.09325
40.08770
40.08325
40.08015
40.07325
40.07180
40.06778
40.06553
40.06428
40.05790
40.05613
40.05147
40.05080
40.05178
40.04340
40.02988
40.02182
40.01142
40.00532
39.99187
39.98113
39.97282
39.96720
39.95948
39.95048
-75.23458
-75.21500
-75.17575
-75.14932
-75.14937
-75.14675
-75.14375
-75.14108
-75.14083
-75.14098
-75.13422
-75.12032
-75.34357
-75.34865
-75.33762
-75.33373
-75.33959
-75.35932
-75.35317
-75.34928
-75.34445
-75.33123
-75.32145
-75.32208
-75.31125
-75.30490
-75.29169
-75.59392
-75.59950
-75.61283
-75.61643
-75.62133
-75.62777
-75.63200
-75.63347
-75.64132
-75.65695
-75.68015
-75.36775
-75.38345
-75.39425
-75.40702
-75.42742
-75.44137
-75.45197
-75.46017
-75.47262
-75.48595
-75.50038
-75.53303
-75.54668
-75.56160
-75.57032
-75.58787
-75.58765
-75.58117
-75.58240
-75.58903
-75.58887
-75.58350
-75.58150
-75.57972
-75.58187
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
LTC 600 Digital Color Cameras
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
Jan-92
Jan-92
Jan-92
Jan-92
Jan-92
Jan-92
Jan-92
Jan-92
Jan-92
Jan-92
Jan-92
Jan-92
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
District 3-0
District 4-0
CAM-04-001
CAM-04-002
CAM-04-003
CAM-04-004
CAM-04-005
CAM-04-006
CAM-04-007
CAM-04-008
CAM-04-009
CAM-04-010
CAM-04-011
CAM-04-012
CAM-04-013
CAM-04-014
CAM-04-015
CAM-04-016
CAM-04-017
CAM-04-018
CAM-04-019
CAM-04-020
CAM-04-021
CAM-04-022
CAM-04-023
CAM-04-026
CAM-04-027
CAM-04-028
Jan-09
Jan-09
District 5-0
CAM-05-001
CAM-05-002
CAM-05-003
CAM-05-004
CAM-05-005
CAM-05-006
CAM-05-008
CAM-05-009
CAM-05-010
CAM-05-011
CAM-05-012
CAM-05-013
CAM-05-014
CAM-05-015
CAM-05-016
CAM-05-017
CAM-05-018
CAM-05-019
CAM-05-020
CAM-05-021
CAM-05-022
CAM-05-023
CAM-05-024
CAM-05-034
CAM-05-035
CAM-05-036
CAM-05-037
CAM-05-038
CAM-05-039
CAM-05-040
CAM-05-041
CAM-05-042
CAM-05-043
CAM-05-044
055.8
060.5
315.3
054.6
006.4
075.4
071.4
337.7
066.5
057.6
District 6-0
CAM-06-001
CAM-06-002
CAM-06-003
CAM-06-004
CAM-06-005
CAM-06-006
CAM-06-007
CAM-06-008
CAM-06-009
CAM-06-010
CAM-06-011
CAM-06-012
CAM-06-013
CAM-06-014
CAM-06-015
CAM-06-016
CAM-06-017
CAM-06-018
CAM-06-019
CAM-06-020
CAM-06-021
CAM-06-022
CAM-06-023
CAM-06-024
CAM-06-025
CAM-06-026
CAM-06-027
CAM-06-028
CAM-06-029
CAM-06-030
CAM-06-031
CAM-06-032
CAM-06-033
CAM-06-034
CAM-06-035
CAM-06-036
CAM-06-037
CAM-06-039
CAM-06-040
CAM-06-041
CAM-06-042
CAM-06-043
CAM-06-044
CAM-06-045
CAM-06-046
CAM-06-047
CAM-06-048
CAM-06-049
CAM-06-050
CAM-06-051
CAM-06-052
CAM-06-053
CAM-06-054
CAM-06-055
CAM-06-056
CAM-06-057
CAM-06-058
CAM-06-059
CAM-06-060
CAM-06-061
CAM-06-062
CAM-06-063
CAM-06-064
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
005.9
006.8
007.4
008.1
013.0
013.2
013.9
014.4
015.0
016.0
016.7
017.0
018.5
019.1
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
DELAWARE
DELAWARE
DELAWARE
DELAWARE
DELAWARE
DELAWARE
DELAWARE
DELAWARE
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
MONTGOMERY
MONTGOMERY
MONTGOMERY
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CAM-06-065
CAM-06-066
CAM-06-067
CAM-06-068
CAM-06-069
CAM-06-070
CAM-06-071
CAM-06-072
CAM-06-073
CAM-06-074
CAM-06-075
CAM-06-076
CAM-06-077
CAM-06-078
CAM-06-079
CAM-06-080
CAM-06-081
CAM-06-082
CAM-06-083
CAM-06-084
CAM-06-085
CAM-06-086
CAM-06-087
CAM-06-088
CAM-06-089
CAM-06-090
CAM-06-091
CAM-06-092
CAM-06-093
CAM-06-094
CAM-06-095
CAM-06-096
CAM-06-097
CAM-06-098
CAM-06-099
CAM-06-100
CAM-06-101
CAM-06-102
CAM-06-103
CAM-06-104
CAM-06-105
CAM-06-106
CAM-06-107
CAM-06-108
CAM-06-109
CAM-06-110
CAM-06-111
CAM-06-112
CAM-06-113
CAM-06-114
CAM-06-115
CAM-06-116
CAM-06-117
CAM-06-118
CAM-06-119
CAM-06-120
CAM-06-121
CAM-06-122
CAM-06-123
CAM-06-124
CAM-06-125
CAM-06-126
CAM-06-127
CAM-06-128
CAM-06-129
CAM-06-130
CAM-06-131
CAM-06-132
CAM-06-133
CAM-06-134
CAM-06-157
CAM-06-158
CAM-06-159
CAM-06-160
CAM-06-161
CAM-06-163
CAM-06-171
CAM-06-172
CAM-06-173
CAM-06-174
CAM-06-175
CAM-06-176
CAM-06-177
CAM-06-178
CAM-06-179
CAM-06-180
CAM-06-181
CAM-06-182
CAM-06-183
CAM-06-184
CAM-06-185
CAM-06-186
CAM-06-187
CAM-06-188
CAM-06-189
CAM-06-190
CAM-06-191
CAM-06-192
CAM-06-193
CAM-06-194
CAM-06-195
CAM-06-196
CAM-06-197
CAM-06-198
CAM-06-199
CAM-06-200
CAM-06-201
CAM-06-202
CAM-06-203
CAM-06-204
CAM-06-205
CAM-06-206
CAM-06-207
CAM-06-208
CAM-06-209
CAM-06-210
CAM-06-211
CAM-06-212
CAM-06-213
CAM-06-214
CAM-06-215
CAM-06-216
CAM-06-217
CAM-06-218
CAM-06-219
CAM-06-220
CAM-06-223
CAM-06-224
CAM-06-225
CAM-06-244
CAM-06-245
CAM-06-246
CAM-06-247
CAM-06-248
CAM-06-249
CAM-06-250
CAM-06-251
CAM-06-252
CAM-06-253
CAM-06-254
CAM-06-458
CAM-06-459
CAM-06-460
CAM-06-461
CAM-06-462
CAM-06-463
CAM-06-464
CAM-06-465
CAM-06-466
CAM-06-467
CAM-06-468
CAM-06-469
CAM-06-470
CAM-06-471
CAM-06-472
CAM-06-473
CAM-06-474
CAM-06-475
CAM-06-476
CM 226
CM 227
CM 228
CM 229
CM 230
CM 231
CM 271
CM 272
CM 273
CM 274
CM 371
CM 372
CM 373
CM 374
CM 375
CM 376
CM 377
CM 3901
CM 3907
CM 3911
CM 3915
CM 401
CM 402
CM 403
CM 404
CM 405
CM 406
CM 407
CM 408
CM 409
CM 410
CM 4701
CM 4702
CM 4707
CM 4709
CM 630
CM 671
CM 672
CM 673
CM 674
CM 675
CM 676
CM 677
CM 678
CM 679
CM 701
CM 702
CM 703
CM 704
CM 705
CM 706
CM 707
CM 708
CM 709
CM 939
CM 940
CM 941
CM 942
CM 943
CM 944
CM 945
CM 946
CM 947
CM 948
CM 949
CM 950
CM 951
CM 952
CM 953
CM 954
CM 3902
CM 3903
CM 3904
CM 3905
CM 3906
CM 3908
CM 3916
CM 3917
CM 3918
CM 3919
CM 3920
CM 3921
CM 4703
CM 4704
CM 4705
CM 4706
CM 710
CM 711
CM 712
CM 713
CM 714
CM 715
CM 716
CM 717
CM 718
CM 719
CM 720
CM 721
CM 722
CM 723
CM 724
CM 725
CM 726
CM 727
CM 728
CM 729
CM 730
CM 731
CM 732
CM 733
CM 734
CM 735
CM 736
CM 737
CM 738
CM 739
CM 740
CM 741
CM 742
CM101
CM102
CM103
CM104
CM105
CM106
CM107
CM2911
CM2912
CM2913
CM2914
CM 4708
CM 4714
CM 4715
CM 4716
CM 4717
CM 4718
CM 4719
CM 4720
CM 4730
CM 4732
CM 179
CM 2301
CM 2302
CM 2303
CM 3071
CM 3072
CM 1101
CM 1102
CM 1103
CM 1104
CM 1105
CM 1106
CM 1107
CM 1108
CM 1109
CM 1110
CM 1111
CM 1112
CM 1113
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
C-322-147
C-322-225
C-83-39
C-83-41
C-81-65
C-81-67
C-81-66
C-81-70
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
POLE
POLE
POLE
OTHER
POLE
OTHER
POLE
POLE
POLE
OTHER
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
06
US 202 NB AT BUSINESS RT. 322
US 202 NEAR SKILES BLVD (MEDIAN)
US 202 SB AT PA 926
US 202 SOUTH OF GREEN TREE RD
US 202 SB AT WATKINS
US 202 SB AT U.S. RT. 1
PA 422 EB / US 202 NB RAMP TO 76E (RAMP L)
PA 422 EB / US 202 NB RAMP TO 76E (RAMP L MERGE TO I-76 EB )
PA 422 EB / US 202 NB RAMP TO 76E (RAMP L)
US 202 SB @ HOME DEPOT
US RT 30 EB AT SR 100
US RT 30 EB AFTER CLOVER MILL RD
US RT 30 WB AT BUSINESS RT 30
US RT 30 WB AFTER WHITFORD RD
US RT 30 WB AFTER PA 113
US RT 30 WB AT PA 322
US RT 30 EB AFTER PA 340
PA 309 NB @ EASTON RD
PA 309 NB @ PA TURNPIKE
PA 309 NB @ SUSQUEHANNA RD
PA 309 NB @ BETHLEHEM PIKE
US 422 EB AT PA TURNPIKE
US 422 WB AT PA 23
US 422 WB AT PA 363
US 422 WB AFTER PA 363
US 422 EB AT PAWLINGS RD
US 422 EB AFTER PERKIOMEN CREEK
US 422 WB AT EGYPT RD (OAKS)
US 422 EB AT INDIAN HEAD RD
US 422 WB AT CIDER MILL RD
US 422 WB BEFORE PA 29
MacDade Blvd Ramp to NB I-476
I-476 SB at MacDade Blvd.
I-476 SB at Baltimore Pike
I-476 SB at US Rt. 1
PA 63 WB (WOODHAVEN RD) @ MILLBOOK RD
I-676 WB @ 24TH ST
I-676 EB @ BEN FRANKLIN PKWY
I-676 WB @ 20TH ST
I-676 WB @ 18TH ST
I-676 EB @ 16TH ST
I-676 EB @ BROAD ST
I-676 WB @ 11TH ST
I-676 EB @ 8TH ST
I-676 EB @ 3RD ST
I-76 EB WEST OF CROTON RD
I-76 EB @ WEADLEY RD
I-76 WB WEST OF GYPSY RD
I-76 EB @ GULPH MILS
I-76 WB @ MP 330.6
I-76 EB WEST OF MATSON FORD RD
I-76 WB @ MP 332
I-76 EB @ MP 332.6
I-76 WB @ CONSHOHOCKEN CURVE
I-95 NB @ INDIANA ST
I-95 NB @ CASTOR AVE
I-95 SB @ BETSY ROSS BRIDGE
I-95 NB @ WAKELING ST
I-95 NB @ VAN KIRK ST
I-95 SB @ DISSTON ST
I-95 NB NORTH OF COTTMAN AVE
I-95 SB @ PENNY PACKER
I-95 NB SOUTH of the AMTRAK BRIDGE
I-95 SB @ ACADEMY RD
I-95 NB @CONVENT ST
I-95 SB @ MILL RD
I-95 NB @ TENNIS AVE
I-95 NB RAMP TO WOODHAVEN RD (PA 63)
I-95 SB @ WOODHAVEN RD
I-95 NB @ STATION AVE
PA 309 NB @ Waverly Rd Sta 2+975
PA 309 NB @ Sta 4+257
PA 309 SB @ Paper Mill Rd Sta 5+291
PA 309 SB @ PA 73 Church Rd Sta 6+700
PA 309 SB @ Camphill Rd Sta 7+865
PA 309 NB South of Highland Avenue
PA 309 SB @ English Village Drive Near Traffic Signal Sta 18+355
PA 309 SB Just North of Hartman Road Sta 19+503
PA 309 NB @ Stump Road Column Extension to Sign Str. Sta 20+345
PA 309 NB @ Dekalb Pike/Upper State Road Sta 21+550
PA 309 NB Just South of North Wales Road Sta 22+155
PA 309 NB @ Five Points Intersection Jiffy Lube Sta 22+988
I-476 NB @ north of Bullens Lane
I-476 SB @ north of PA 320
I-476 SB @ South of Septa Railroad
I-476 NB @ South of Plush Mill Road sign structure
I-76 WB at I-476 Interchange
I-76 WB east of Conshy curve
I-76 EB west of Waverly Rd
I-76 EB east of Waverly Rd
I-76 EB west of Gladwyne
I-76 WB @ Gladwyne
I-76 WB east of Gladwyne
I-76 WB west of Belmont
I-76 EB @ Belmont Ave
I-76 WB east of Belmont Ave
I-76 WB @ City Ave
I-76 EB @ City Ave
I-76 EB @ US 1
I-76 WB 76 ramp to US 1
I-76 WB west of Montgomery Dr.
I-76 EB @ Montgomery Dr.
I-76 EB east of Montgomery Dr.
I-76 EB west of Girard Ave.
I-76EB @ Girard Ave.
I-76 WB east of Girard Ave.
I-76 EB west of Spring Garden
I-76 WB @ Spring Garden St.
I-76 EB ramp to I-676
I-76 WB east of I-676
I-76 WB @ 30th Street
I-76 WB west of South Street
I-76 EB east of South Street
I-76 EB @ University
I-76 EB east of Grays Ferry
I-76 EB @ Vare Ave
I-76 EB ramp to Passyunk Ave.
I-76 EB to 26th St.
26th St. to I-76 WB
US 1 NB South of Henry Avenue
US 1 SB at Fox Street
US 1 at Wissahickon Avenue
US 1 NB Roberts/Berkeley
US 1 NB at 17th Street
US 1 SB at Broad Street
US 1 Median South of 9th Street
EB PA 291 E of 76
26th St. and Penrose Ave.
WB Platt Brdg. Midspan
WB PA 291 @ I-95
I-476 NB @ North of Beatty Road
I-476 SB @ West Chester Pike
I-476 NB @ North of West Chester Pike
I-476 SB @ South of Marple Road
I-476 SB @ South of Darby Road
I-476 [email protected] South of Bryn Mawr Avenue
I-476 NB @ North of Clyde Road
I-476 SB @ South of Sproul Road
I-476 SB @ Ridge Pike
I-476 SB On ramp from Germantown Pike
US 1 @ Creek Road
PA 23 & Fayette Street
PA 23 & Hollow Road
City Avenue & PA 23
Lincoln Hwy. & 1st Avenue (Coatesville)
Lincoln Hwy. & 7th Avenue (Coatesville)
Torresdale Ave. & Harbison Ave.
Torresdale Ave. & Robbins Ave.
Torresdale Ave. & Levick St.
Torresdale Ave. and Princeton Avenue
Torresdale Ave. & Cottman Ave.
Torresdale Ave. & Rhawn St.
Torresdale Ave. & Ashburner St.
Torresdale Ave. & Linden Ave.
State Rd. at Princeton Ave.
State Rd. at Cottman Ave.
Aramingo Ave. & Tacony St.
Harbison Ave. & Sanger St.
I-95 Girard Avenue offramp
08
08
08
08
08
08
08
08
US 22/322 at Clark's Ferry Bridge
US 22/322 at PA 225
I-83 AT PA 114
I-83 AT PA 581
I-81 AT US 11 / US 15
I-81 AT US 22 / US 322
I-81 AT EXIT 66
I-81 AT I-83
001.0
001.0
003.0
330.6
332.0
332.6
333.9
334.3
335.1
336.0
336.6
336.7
337.3
338.0
338.7
339.6
339.9
340.1
341.0
341.4
341.8
342.1
342.5
342.8
343.1
343.4
343.0
344.3
344.6
344.8
345.2
345.5
345.8
346.5
346.9
347.4
347.4
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
1
1
3
5
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
330
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
32
N/A
N/A
N/A
N/A
35
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
331
N/A
N/A
N/A
N/A
336
N/A
N/A
338
N/A
339
339
340
340
N/A
341
N/A
N/A
342
N/A
N/A
343
N/A
N/A
344
N/A
N/A
346
N/A
347
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
9
N/A
N/A
N/A
N/A
N/A
N/A
18
19
0202
0202
0202
0202
0202
0202
3202
3202
3202
0202
0030
0030
0030
0030
0030
0030
0030
0309
0309
0309
0309
0422
0422
0422
0422
0422
0422
0422
0422
0422
0422
8025
0476
0476
0476
0063
0676
0676
0676
0676
0676
0676
0676
0676
0676
0076
0076
0076
0076
0076
0076
0076
0076
0076
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0095
0309
0309
0309
0309
0309
0309
0309
0309
0309
0309
0309
0309
0476
0476
0476
0476
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
0076
3003
3019
3019
0001
0001
0001
0001
0001
0001
0001
3003
0291
0291
0291
0476
0476
0476
0476
0476
0476
0476
0476
0476
0476
0001
0023
0023
0023
0082
0082
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0080
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
CHESTER
CHESTER
CHESTER
CHESTER
DELAWARE
DELAWARE
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
CHESTER
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
CHESTER
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
DELAWARE
DELAWARE
DELAWARE
DELAWARE
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
BUCKS
BUCKS
BUCKS
BUCKS
BUCKS
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
DELAWARE
DELAWARE
DELAWARE
DELAWARE
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
MONTGOMERY
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
DELAWARE
DELAWARE
DELAWARE
DELAWARE
DELAWARE
DELAWARE
DELAWARE
DELAWARE
MONTGOMERY
MONTGOMERY
DELAWARE
MONTGOMERY
MONTGOMERY
MONTGOMERY
CHESTER
CHESTER
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
PHILADELPHIA
DAUPHIN
DAUPHIN
YORK
CUMBERLAND
CUMBERLAND
DAUPHIN
DAUPHIN
DAUPHIN
0147
0022
0083
0083
0081
0081
0081
0081
1421
2705
39
41
65
67
66
70
0235
1200
0080
0100
0111
0131
0141
0160
0271
0291
0300
0310
0310
0340
0004
0015
0025
0024
3315
3335
3340
3350
3354
3365
3365
3371
3374
3385
3391
3394
3400
3401
3411
3414
3420
3424
3424
3431
3430
3435
3440
3445
3445
3451
3450
3454
3454
3464
0031
0090
0090
0100
0111
0110
0120
0140
0141
0150
0020
0091
0061
0061
0040
0085
0090
0091
0101
0105
0110
0121
0185
1821
1729
0988
0299
0844
1578
1962
0557
0164
2272
4348
0000
2630
0759
0171
2161
1935
0472
0225
2273
0075
0974
2450
2450
2450
-75.31126
-75.26319
-75.22623
-75.82388
-75.81085
-75.06846
-75.05357
-75.05162
-75.03877
-75.03499
-75.02506
-75.01526
-74.99972
-75.03527
-75.03149
-75.07241
-75.07241
-75.12287
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Bosch
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Detection Systems & Engineering
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
LTC 600 Digital Color Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
DS-5000 Dual Day/Night Cameras
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
Envirodome LTC 0928/25C
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-07
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jan-06
Jun-05
Jan-09
Jan-99
Jan-98
Jan-98
Jan-98
Jan-98
Jan-98
Jan-98
Jan-98
Jan-98
Jan-98
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
Jan-04
May-99
May-99
Jan-04
May-99
May-99
May-99
May-99
May-99
May-99
May-99
May-99
Jan-99
Jan-99
Jan-99
Jan-99
Jan-99
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Oct-08
Jan-08
Jan-08
Jan-08
Jan-08
Jan-08
Jan-08
Jan-08
Jan-10
Jan-10
Jan-10
Jan-08
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-09
Jan-08
Jan-08
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
Broadware Video Server
-77.00830
-76.95005
-76.87617
-76.89545
-76.92238
-76.88023
-76.88816
-76.83501
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
Dec-07
Dec-07
Aug-04
Aug-04
Apr-08
Apr-08
Apr-08
Apr-08
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
39.94056
39.93038
39.91955
39.91118
39.89145
39.88117
40.07852
40.08030
40.08142
40.08313
40.02052
40.01298
40.01818
40.02072
40.01927
40.01347
40.00983
40.08793
40.13340
40.16118
40.19592
40.09032
40.10143
40.11305
40.11593
40.11417
40.12430
40.13475
40.14778
40.15048
40.15680
39.87583
39.87678
39.91260
39.93610
40.08092
39.95998
39.95902
39.95905
39.95878
39.95813
39.95768
39.95728
39.95690
39.95697
40.07903
40.07622
40.07357
40.06947
40.06760
40.06417
40.06663
40.06803
40.07200
39.98013
39.98853
39.99730
40.00758
40.01252
40.02217
40.02942
40.03527
40.04103
40.04823
40.05112
40.05857
40.06415
40.06800
40.07062
40.07407
40.09355
40.10025
40.10200
40.11325
40.12352
40.14008
40.20895
40.21835
40.22572
40.23552
40.23970
40.24767
39.88325
39.89155
39.90293
39.90810
40.06547
40.06964
40.06439
40.05303
40.04479
40.03750
40.03688
40.03172
40.02529
40.01999
40.01154
40.00975
40.00597
40.00509
39.99517
39.98753
39.98325
39.97823
39.97664
39.97445
39.96941
39.96406
39.96040
39.95572
39.95376
39.94879
39.94474
39.94355
39.93511
39.92908
39.92313
39.92163
39.92159
40.01156
40.01455
40.01761
40.01826
40.02035
40.01980
40.02097
39.91521
39.90579
39.89780
39.89219
39.92977
39.97795
39.98397
39.98834
39.99585
40.00659
40.01564
40.02878
40.09849
40.10677
-75.59045
-75.58555
-75.57695
-75.57103
-75.55535
-75.54712
-75.40563
-75.39832
-75.39148
-75.39735
-75.62432
-75.64793
-75.66953
-75.68593
-75.69978
-75.72438
-75.73567
-75.16595
-75.20118
-75.20125
-75.22307
-75.41520
-75.41850
-75.42002
-75.43110
-75.45488
-75.45108
-75.44677
-75.46035
-75.45990
-75.47000
-75.34892
-75.35165
-75.36242
-75.36464
-74.96567
-75.17848
-75.17245
-75.17112
-75.16873
-75.16537
-75.16175
-75.15727
-75.15257
-75.14490
-75.37812
-75.36148
-75.34780
-75.34303
-75.33738
-75.32948
-75.31248
-75.30072
-75.28695
-75.10527
-75.08810
-75.08227
-75.07263
-75.05878
-75.03885
-75.02193
-75.01843
-75.00452
-74.99980
-74.98915
-74.98172
-74.96970
-74.96120
-74.96108
-74.94883
-75.17076
-75.18587
-75.19441
-75.20135
-75.20499
-75.20155
-75.22500
-75.22993
-75.23415
-75.24003
-75.24263
-75.24384
-75.35224
-75.35945
-75.36416
-75.36205
-75.31826
-75.27993
-75.27685
-75.26580
-75.25725
-75.24749
-75.24620
-75.23906
-75.22906
-75.21901
-75.20921
-75.20779
-75.19753
-75.19533
-75.19778
-75.20768
-75.20817
-75.20235
-75.19708
-75.19412
-75.19229
-75.18443
-75.18176
-75.18062
-75.18141
-75.18526
-75.19136
-75.19258
-75.19991
-75.19721
-75.19164
-75.19033
-75.19058
-75.18243
-75.17828
-75.17236
-75.16860
-75.15374
-75.14889
-75.14019
-75.19185
-75.19400
-75.21165
-75.22419
-75.36253
-75.34091
-75.33826
-75.34330
-75.34778
-75.35455
-75.35732
-75.36372
-75.30001
-75.28865
40.06895
40.03098
40.00129
39.98316
39.98512
40.01338
40.02051
40.02152
40.02816
40.03011
40.03525
40.04032
40.05037
40.02392
40.02566
40.00805
40.01686
39.97332
40.39622
40.37083
40.20698
40.23916
40.31813
40.30225
40.30765
40.30787
District 8-0
CAM-08-001
CAM-08-002
CAM-08-003
CAM-08-004
CAM-08-005
CAM-08-006
CAM-08-007
CAM-08-008
70
55
40
70
55
55
55
55
038.8
041.2
064.8
067.0
066.4
070.1
CAM-08-009
CAM-08-010
CAM-08-011
CAM-08-012
CAM-08-013
CAM-08-014
CAM-08-015
CAM-08-016
CAM-08-017
CAM-08-018
CAM-08-019
CAM-08-020
CAM-08-021
CAM-08-022
CAM-08-023
CAM-08-024
CAM-08-025
CAM-08-026
CAM-08-027
CAM-08-028
CAM-08-029
CAM-08-030
CAM-08-031
CAM-08-032
CAM-08-033
CAM-08-034
CAM-08-035
CAM-08-036
CAM-08-037
CAM-08-038
CAM-08-039
CAM-08-040
CAM-08-041
CAM-08-042
CAM-08-043
CAM-08-044
CAM-08-045
CAM-08-046
CAM-08-049
CAM-08-050
CAM-08-056
CAM-08-057
CAM-08-074
CAM-08-076
CAM-08-078
CAM-08-096
CAM-08-106
CAM-08-107
C-81-72
C-81-77
C-81-80
C-81-89
C-581-6
C-83-50
C-83-48
C-83-46
C-83-45
C-83-43
C-83-42
C-283-2
C-283-1
C-81-49
C-81-52
C-81-57
C-81-59
C-83-47
C-83-44
C-15-ZIMM
C-581-5
C-581-4
C-581-3
C-81-61
C-81-1
C-81-3
C-81-5
C-81-10
C-81-14
C-81-16
C-81-17
C-81-20
C-81-24
C-81-29
C-15-30
C-30-N.S.RD.
C-30-WEST ST.
C-BR15-97
C-81-45
C-81-47
C-81-74
C-81-79 NB REST
C-83-21
C-83-24
C-83-31
C-322-39
C-30-283
C-30-501
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE
POLE
POLE
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
55
55
55
55
55
55
55
55
55
55
55
55
55
55
55
55
70
55
55
55
70
55
55
55
55
55
55
55
55
55
55
55
55
55
70
25
25
25
55
55
55
55
55
55
55
55
55
55
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
I-81 AT EXIT 72
I-81 AT PA 39
I-81 AT PA 743
I-81 AT I-78
PA 581 MM 6.4
I-83 AT US 22 E / US 22 W
I-83 AT EXT 48
I-83 AT I-283 / US 322 E
I-83 AT EXIT 45
I-83 AT EXIT 44A
I-83 AT EXIT 42
I-283 AT PA 441
I-283 AT PA 230 / PA 283
I-81 AT PA 641
I-81 AT US 11 N / US 11 S
I-81 AT PA 114
I-81 AT PA 581
I-83 AT US 322 E
I-83 AT EXIT 44B
US 15 at Zimmerman Dr. (New Interchange)
PA 581 at Exit 5
PA 581 MM 4.4
PA 581 at Exit 3
I-81 AT PA 944
I-81 AT PA 163
I-81 AT US 11
I-81 AT PA 16
I-81 AT PA 914
I-81 AT PA 316
I-81 AT US 30
I-81 AT EXIT 17
I-81 AT PA 997
I-81 AT PA 696
I-81 AT PA 174
US 15 at US 30
US 30 at Natural Springs Road
US 30 at West Street
Baltimore Street at Steinwehr Ave.
I-81 AT COLLEGE ST.
I-81 AT PA 34
I-81 MM 74
I-81 NORTH REST AREA
I-83 AT US 30 INTERCHANGE
I-83 AT PA 238 INTERCHANGE
I-83 MM 30
US 22/322 AT LINGLESTOWN RD. EXIT
US 30 AT PA 283 EXIT
US 30 AT PA 501 EXIT
CCTV #01
CCTV #02
CCTV #03
CCTV #04
CCTV #05
CCTV #06
CCTV #07
CCTV #08
CCTV #09
CCTV #10
CCTV #11
CCTV #12
CCTV #13
CCTV #14
CCTV #15
CCTV #16
CCTV #17
CCTV #18
CCTV #19
CCTV #20
CCTV #21
CCTV #22
CCTV #23
CCTV #24
CCTV #25
CCTV #26
CCTV #27
CCTV #28
CCTV #29
CCTV #30
CCTV #31
CCTV #32
CCTV #33
CCTV #34
CCTV #35
CCTV #36
CCTV #37
CCTV #38
CCTV #39
CCTV #40
CCTV #41
CCTV #42
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE W/ CLD
POLE
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
I-99 & SR 0350 @ Bald Eagle
SR 1009 Frankstown Rd. at I-99
I-99 SB at SR 0036 Logan Blvd. Overpass
I-99 SB at SR 8015 Ramp "D" Plank Rd.
SR 8004 Ramp N at I-99 SB Crosskeys
SR 0022 WB at SR 0764 Crosskeys Interchange
SR 4010 17th St. at SR 1001 Valley View
SR 4010 17th St. at SR 1001 Pleasant Valley
SR 4010 17th St. at SR 0764 Sixth Ave.
SR 4009 8th St. at SR 4013 Chestnut Ave.
Logan Blvd at Convention Ctr. Blvd.
Convention Ctr. Blvd at Conv. Ctr. Dr.
SR 1001 at SR 1009 Frankstown Rd.
SR 0036 at Southey Ave. Logan Blvd.
Plank Rd. at SR 9900 Convention Ctr. Blvd.
Plank Rd. at SR 1002 Meadows Intersection
Plank Rd. at SR 0022 Wye Switches
17TH Street West of Margaret Ave. Intersection
SR4013 (Chestnut Ave) & SR4017 (Juniata Gap Rd)
SR4013 (Chestnut Ave) & SR4015 (Fourth St) Intersection
SR4013 (Chestnut Ave.) & N. Second St.
I-99 SB at SR 4010 17th St. Interchange
PA 453 Intersection - Waterstreet
S.R. 0764 (Seventh Ave) & Seventh St. Intersection
S.R. 0764 (Sixth Ave) & Eighth Street Intersection
US22 Overpass - Interchange.
Cresson/Summit
Interchange
Gallitzin/Tunnelhill
CCTV
is located in Cambria Co. but the
S.R. is a Blair Co. route.
US 22 & SR 2013 (Wilmore Rd & Center Ave) Candlelight Intersection
SR 3041 Interchange. East of the Indiana/Cambria County Line
PA 453 North of PA 45 Intersection and approximately one (1) mile north of
On-Ramp "C" to I-99 from Business Rte US 220 (SR 4009)
SR4003 (Logan Blvd) & SR0764 (Sixth Ave)
SR 3031 (Galleria Drive) @ SR 0219 (SB Underpass)
SR 0056 @ SR 0219 (SR 8005 Ramp) Interchange
SR 0219 NB @ SR 0756 (Elton Road) Intersection
SR 0219 @ SR 0056 (Scalp Avenue) Intersection
US 30 @ SR 2029 (East Mattie Rd) Intersection
US 30 @ I-70 (SR 9102 Ramp) Intersection
US 30 @ I-76 Turnpike Off - Ramp
US 22 (William Penn Hwy) @ SR 3032 (Mini Mall Rd)
US 22 (William Penn Hwy) @ US 219 Interchange
US 30 Sidling Hill
55
60
65
70
75
80
85
90
95
100
105
110
115
120
125
130
135
140
145
150
155
160
165
170
175
180
185
190
195
200
205
210
215
220
225
230
235
240
245
300
305
315
320
325
330
335
340
345
350
370
375
380
385
390
395
400
405
410
550
555
560
565
570
575
580
585
590
595
856
858
804
806
820
821
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
OTHER
POLE
POLE
POLE
OTHER
OTHER
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
30
50
50
50
15
15
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
Robinson Town Center
Ikea
US22-30/SR60 Interchange
Settlers Cabin EB Off-Ramp
Settlers Cabin
Settlers Cabin EB On-Ramp
Bishops Corner Interchange
Campbells Run
US-22/I-279 SB On Ramp
I-279 Pittsburgh Interchange
Rosslyn Farms Interchange
Carnegie Interchange
Greentree Interchange
Greentree Hill - Top
Greentree Hill - Middle
Banksville Interchange
Fort Pitt Garage
PNC Park - HOV
Lacock Street - HOV
Anderson Street - HOV
North Canal Street - HOV
East Street - HOV
Tripoli Street - HOV
Veteran's Bridge - HOV
Bedford Avenue - HOV
St Boniface - HOV
Hazlett Street - HOV
Venture Street - HOV
Evergreen Road - HOV
McKnight Road - HOV
Perrysville - HOV
I-279 SB On-Ramp - HOV
HOV Park-N-Ride
Jacks Run
Bellevue Road
Union Ave South
Union Ave North
Ben Avon Heights Road
Camp Horne Road
Commonwealth Place
Fort Pitt Blvd
Grant Street
County Jail
2nd Avenue
Brady Street
Bates Street
Swinburne Street
Saline Street
Beechwood Blvd
Commercial Street
Swissvale
Edgewood
Brinton Road
Forest Hills
Wilkinsburg
Greensburg Pike
Churchill Interchange
Penn Hills Interchange
Bridgeville North
Chartiers Creek
Prestley Rd
Kirwin Hts Interchange
Thoms Run Rd
Collier Ave
Carnegie South
Carnegie
Ewing Road
Pittsburgh Int South
West End Bridge South
West End Bridge North
Crane Avenue
South Liberty Interchange
Ft PittTunnel Inbound CP2
Ft PittTunnel Outbound CP2
071.8
077.0
080.0
089.0
006.4
050.0
048.0
046.1
045.0
043.4
042.0
002.0
000.5
049.0
052.0
057.0
059.0
046.9
044.0
72
77
80
89
005.0
004.4
003.0
061.0
001.0
003.0
005.0
010.0
014.0
016.0
017.0
020.0
024.0
029.0
5
4
3
61
1
3
5
10
14
16
17
20
24
29
045.0
047.0
074.5
079.0
021.0
024.0
030.0
45
47A
50
48
46
45
44A
42
2
1
49
52
57
59
47
44B
21
24
DAUPHIN
DAUPHIN
DAUPHIN
LEBANON
CUMBERLAND
DAUPHIN
DAUPHIN
DAUPHIN
DAUPHIN
DAUPHIN
CUMBERLAND
DAUPHIN
DAUPHIN
CUMBERLAND
CUMBERLAND
CUMBERLAND
CUMBERLAND
DAUPHIN
DAUPHIN
CUMBERLAND
CUMBERLAND
CUMBERLAND
CUMBERLAND
CUMBERLAND
FRANKLIN
FRANKLIN
FRANKLIN
FRANKLIN
FRANKLIN
FRANKLIN
FRANKLIN
FRANKLIN
FRANKLIN
CUMBERLAND
ADAMS
ADAMS
ADAMS
ADAMS
CUMBERLAND
CUMBERLAND
DAUPHIN
DAUPHIN
YORK
YORK
YORK
DAUPHIN
LANCASTER
LANCASTER
0081
0081
0081
0081
0581
0083
0083
0083
0083
0083
0083
0283
0283
0081
0081
0081
0081
0083
0083
0015
0015
0581
0581
0081
0081
0081
0081
0081
0081
0081
0081
0081
0081
0081
0030
0030
0030
3001
0081
0081
0081
0081
0083
0083
0083
0022
0030
0030
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
BLAIR
HUNTINGDON
BLAIR
BLAIR
CAMBRIA
BLAIR
CAMBRIA
CAMBRIA
HUNTINGDON
BEDFORD
BLAIR
CAMBRIA
CAMBRIA
CAMBRIA
CAMBRIA
BEDFORD
BEDFORD
BEDFORD
CAMBRIA
CAMBRIA
FULTON
0099
1009
0099
0099
8004
0022
4010
4010
4010
4009
0036
B004
1001
0036
1001
1001
1001
4010
4013
4013
4013
0099
0022
4013
4013
2014
4001
0022
0022
0453
8007
4003
3031
0056
0219
0219
0030
0030
0030
0022
0022
0030
0514
0070
0311
0305
0500
0161
0040
0035
0021
0021
0321
0010
0110
0360
0050
0020
0010
0020
0030
0021
0041
0325
0078
0020
0011
0170
0020
0211
0042
0030
0750
0030
0010
0270
0070
0040
0650
0662
0680
0180
0170
0100
0570
1710
0720
0165
0140
3020
0150
0150
2825
2475
0375
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
0376
0376
0376
0376
0376
0376
0376
0376
0376
0079
0376
0376
0376
0376
0376
0376
0376
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0591
0595
0601
0600
0604
0614
0614
0624
0631
0581
0641
0654
0671
0675
0680
0684
0685
2218
2258
0039
2288
2590
0329
2485
0400
0612
0535
2217
1365
0742
0001
1299
0762
1867
0279
0279
0279
0279
0279
0279
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0376
0079
0079
0079
0079
0079
0079
0079
0079
0079
0079
0019
0019
0051
8151
0279
0279
0120
0125
0131
0134
0141
0141
0003
0003
0004
0004
0015
0020
0025
0030
0035
0045
0054
0060
0071
0070
0074
0085
0091
0095
0104
0530
0535
0540
0540
0550
0554
0554
0560
0564
0570
0281
0281
0401
0010
0054
0055
1040
1565
1566
0720
0650
2971
0732
2114
0575
2102
1385
0200
1860
1808
2700
0127
0500
2600
1150
2760
1190
0315
0400
1800
1500
0700
0000
0000
2000
0300
0250
2100
1900
2300
2400
0000
1665
1000
0450
0100
0100
40.32465
40.35269
40.37995
40.42518
40.23506
40.29684
40.27892
40.25371
40.25810
40.25464
40.24480
40.24211
40.21938
40.19849
40.23478
40.26939
40.27568
40.26149
40.25705
40.22105
40.23213
40.23373
40.24434
40.28888
39.72330
39.75785
39.78381
39.85482
39.90997
39.92864
39.94334
39.96400
40.01580
40.06060
39.84643
39.83971
39.83075
39.82427
40.18686
40.18789
40.33293
40.37014
39.98377
40.02068
40.11143
40.32202
40.07095
40.06850
-76.79749
-76.72021
-76.66019
-76.52125
-76.91403
-76.82532
-76.81942
-76.81412
-76.83570
-76.86492
-76.88332
-76.80543
-76.78742
-77.15854
-77.12800
-77.04451
-77.00159
-76.81461
-76.85607
-76.93664
-76.93203
-76.95911
-76.98240
-76.98163
-77.72937
-77.72658
-77.71456
-77.68653
-77.64815
-77.63576
-77.62026
-77.57800
-77.53328
-77.47970
-77.19608
-77.20943
-77.23677
-77.23096
-77.21161
-77.19097
-76.75782
-76.68459
-76.73029
-76.74263
-76.78453
-76.88495
-76.32724
-76.30561
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
COHU
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 23X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
3920 Series, I-Dome 35X Zoom
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Apr-08
Jun-08
Apr-08
Apr-08
May-08
May-08
May-08
Jun-08
Jun-08
May-08
May-08
May-08
May-08
May-08
May-08
Jun-08
Jun-08
Jun-08
Jul-08
Jun-08
May-08
May-08
Apr-09
Apr-09
Apr-09
Apr-09
Jan-10
Jan-10
Jan-10
May-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
Jan-10
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
VIDSYS VidShield 6.1
40.71108
40.47948
40.47093
40.46567
40.44150
40.44125
40.49915
40.50025
40.50810
40.51892
40.45792
40.45418
40.48200
40.47837
40.45227
40.43727
40.42792
40.51167
40.52939
40.52231
40.53331
40.49395
40.57134
40.51728
40.51628
40.45700
40.46703
40.47758
40.43470
40.58517
40.05648
40.49028
40.30144
40.29461
40.27997
40.27316
39.99917
39.99922
39.99916
40.46762
40.46377
40.01616
-78.18872
-78.39478
-78.39912
-78.40815
-78.42683
-78.43503
-78.39025
-78.39130
-78.39988
-78.39735
-78.39508
-78.40343
-78.40158
-78.40337
-78.40930
-78.41205
-78.41762
-78.40547
-78.38919
-78.39492
-78.38608
-78.38367
-78.13870
-78.39319
-78.39278
-78.56698
-78.54320
-78.72422
-78.91185
-78.14583
-78.51140
-78.41367
-78.83333
-78.84147
-78.84808
-78.85916
-78.24069
-78.23844
-78.23336
-78.75817
-78.76392
-78.13425
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
Bosch
ENVD2460P
LTC 7960/60-20xpm
LTC 7960/60-20xpm
LTC 7960/60-20xpm
LTC 7960/60-20xpm
LTC 7960/60-20xpm
LTC 7960/60-20xpm
LTC 7960/60-20xpm
18X EnviroDome
LTC 7960/60-20xpm
LTC 7960/60-20xpm
LTC 7960/60-20xpm
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
LTC 7960/60-20xpm
LTC 7960/60-20xpm
25X EnviroDome
25X EnviroDome
LTC 7960/60-20xpm
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
25X EnviroDome
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
BATTERY/ELECTRIC
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
POTS
FIBER
FIBER
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
T-1
Feb-08
Jul-01
Jul-01
Jul-01
Jul-01
Jul-01
Jul-01
Jul-01
Jul-01
Jul-01
Jul-01
Jul-01
Apr-03
Apr-03
Apr-03
Apr-03
Apr-03
Jan-02
Jul-01
Jun-04
Jun-04
Jul-01
Jan-03
Oct-05
Oct-05
Jan-06
Jan-06
Apr-05
Feb-07
Jul-06
Sep-07
Sep-07
May-08
May-08
May-08
May-08
Jan-09
Jan-09
Jan-09
Sep-09
Sep-09
Sep-04
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
40.45229
40.45017
40.44715
40.44332
40.43863
40.43386
40.43084
40.42542
40.42514
40.42294
40.42041
40.41031
40.42072
40.42109
40.42293
40.42862
40.43067
40.44778
40.44877
40.44984
40.45054
40.45259
40.45642
40.44620
40.44262
40.46084
40.47394
40.48296
40.49377
40.49529
40.50020
40.50403
40.50712
40.50708
40.50774
40.51396
40.51910
40.52000
40.52442
40.43934
40.43769
40.43517
40.43388
40.43473
40.43609
40.43191
40.42717
40.42939
40.42912
40.42531
40.42616
40.43033
40.42933
40.43215
40.43888
40.44418
40.44422
40.44197
40.36400
40.36932
40.37229
40.37382
40.38172
40.38848
40.39326
40.39903
40.40717
40.41412
40.44421
40.44911
40.41612
40.41418
40.432332
40.432927
-80.17276
-80.16782
-80.16575
-80.16106
-80.15259
-80.14325
-80.13714
-80.12397
-80.11552
-80.10590
-80.09230
-80.07201
-80.04896
-80.04211
-80.03030
-80.02977
-80.02711
-80.00750
-80.00686
-79.99966
-79.99784
-79.99686
-79.99811
-79.99034
-79.99089
-79.99919
-80.00556
-80.00740
-80.01123
-80.01333
-80.02381
-80.02852
-80.03122
-80.03493
-80.04465
-80.05205
-80.05443
-80.06309
-80.07019
-80.00769
-80.00166
-79.99916
-79.99395
-79.98727
-79.97391
-79.95909
-79.95264
-79.94135
-79.93123
-79.90887
-79.89372
-79.88215
-79.87643
-79.87118
-79.86231
-79.85405
-79.84102
-79.82325
-80.11875
-80.11879
-80.11053
-80.10389
-80.09646
-80.09646
-80.10068
-80.10515
-80.10738
-80.10473
-80.02787
-80.02532
-80.01441
-80.00934
-80.023374
-80.022737
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
COHU
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
S2-CW22
S2-CW22
S2-CW22
S2-CW22
VC284-48
VC284-48
VC284-48
S2-CW22
S2-CW22
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
VC284-48
VC284-48
VC284-48
VC284-48
3920 Series
VC284-48
VC284-48
VC284-48
VC284-48
VC284-48
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Spectra III
Spectra III
Spectra III
Spectra III
Spectra III
Spectra III
Spectra III
Spectra III
Spectra III
Spectra III
VC284-48
VC284-48
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
Jan-02
Jan-02
Jan-02
Jan-02
Jan-02
Jan-02
Feb-02
Feb-02
Feb-02
Feb-02
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Nov-02
Nov-02
Nov-02
Nov-02
Nov-02
Nov-02
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Dec-98
Nov-00
Nov-00
Nov-00
Nov-00
Nov-00
Nov-00
Nov-00
Nov-00
Nov-00
1-Aug-06
1-Aug-06
1-Aug-06
1-Aug-06
1-Aug-06
1-Aug-06
1-Aug-06
1-Aug-06
1-Aug-06
1-Aug-06
Dec-98
Dec-98
Oct-03
Oct-03
Oct-03
Oct-03
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
District 9-0
CAM-09-001
CAM-09-002
CAM-09-003
CAM-09-004
CAM-09-005
CAM-09-006
CAM-09-007
CAM-09-008
CAM-09-009
CAM-09-010
CAM-09-011
CAM-09-012
CAM-09-013
CAM-09-014
CAM-09-015
CAM-09-016
CAM-09-017
CAM-09-018
CAM-09-019
CAM-09-020
CAM-09-021
CAM-09-022
CAM-09-023
CAM-09-024
CAM-09-025
CAM-09-026
CAM-09-027
CAM-09-028
CAM-09-029
CAM-09-030
CAM-09-031
CAM-09-032
CAM-09-033
CAM-09-034
CAM-09-035
CAM-09-036
CAM-09-037
CAM-09-038
CAM-09-039
CAM-09-040
CAM-09-041
CAM-09-042
52
32
31
28
33
1
0100
0075
0200
1825
0000
0625
3075
1150
1575
2250
0050
0050
0050
0000
0000
1130
0000
0100
0250
0050
1300
0675
0160
3735
2000
0100
0065
0910
1775
0865
District 10-0
District 11-0
CAM-11-001
CAM-11-002
CAM-11-003
CAM-11-004
CAM-11-005
CAM-11-006
CAM-11-007
CAM-11-008
CAM-11-009
CAM-11-010
CAM-11-011
CAM-11-012
CAM-11-013
CAM-11-014
CAM-11-015
CAM-11-016
CAM-11-017
CAM-11-018
CAM-11-019
CAM-11-020
CAM-11-021
CAM-11-022
CAM-11-023
CAM-11-024
CAM-11-025
CAM-11-026
CAM-11-027
CAM-11-028
CAM-11-029
CAM-11-030
CAM-11-031
CAM-11-032
CAM-11-033
CAM-11-034
CAM-11-035
CAM-11-036
CAM-11-037
CAM-11-038
CAM-11-039
CAM-11-040
CAM-11-041
CAM-11-042
CAM-11-043
CAM-11-044
CAM-11-045
CAM-11-046
CAM-11-047
CAM-11-048
CAM-11-049
CAM-11-050
CAM-11-051
CAM-11-052
CAM-11-053
CAM-11-054
CAM-11-055
CAM-11-056
CAM-11-057
CAM-11-058
CAM-11-059
CAM-11-060
CAM-11-061
CAM-11-062
CAM-11-063
CAM-11-064
CAM-11-065
CAM-11-066
CAM-11-067
CAM-11-068
CAM-11-069
CAM-11-070
CAM-11-071
CAM-11-072
CAM-11-073
CAM-11-074
059.5
060.0
060.1
060.5
061.0
061.6
062.0
062.6
063.2
058.1
064.4
065.8
067.2
067.5
068.3
068.7
068.9
000.7
001.1
001.2
001.4
001.6
000.6
000.3
002.0
002.9
003.6
004.4
004.5
005.2
005.5
006.0
006.5
007.1
007.4
007.9
008.4
070.0
070.3
070.6
070.9
071.7
071.9
072.9
073.3
073.9
074.4
075.6
076.4
077.1
077.4
077.8
078.4
079.0
079.8
080.7
054.5
055.0
055.5
056.0
056.5
057.0
057.5
058.0
058.5
059.0
069.0
069.0
59B
CAM-11-075
CAM-11-076
CAM-11-077
CAM-11-078
CAM-11-079
CAM-11-080
CAM-11-081
CAM-11-082
CAM-11-083
CAM-11-084
CAM-11-085
CAM-11-086
CAM-11-087
CAM-11-088
CAM-11-089
CAM-11-090
CAM-11-091
CAM-11-092
CAM-11-093
CAM-11-094
CAM-11-095
CAM-11-096
CAM-11-097
CAM-11-098
CAM-11-099
CAM-11-100
CAM-11-101
CAM-11-102
CAM-11-103
CAM-11-104
CAM-11-105
CAM-11-106
CAM-11-107
CAM-11-108
CAM-11-109
CAM-11-110
CAM-11-111
CAM-11-112
CAM-11-113
CAM-11-114
CAM-11-115
CAM-11-116
CAM-11-117
CAM-11-118
CAM-11-119
CAM-11-120
CAM-11-121
CAM-11-122
CAM-11-123
CAM-11-124
CAM-11-125
CAM-11-126
CAM-11-127
CAM-11-128
CAM-11-129
CAM-11-130
CAM-11-131
CAM-11-132
CAM-11-133
CAM-11-134
CAM-11-135
CAM-11-136
CAM-11-137
CAM-11-138
CAM-11-139
CAM-11-140
CAM-11-141
CAM-11-142
CAM-11-143
CAM-11-144
CAM-11-145
CAM-11-146
CAM-11-147
CAM-11-148
District 12-0
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
250
255
260
408
415
420
425
430
435
440
319
660
665
265
270
612
620
625
630
635
640
645
650
655
159
161
670
675
680
685
690
695
700
705
710
50
99
101
600
605
615
610
846
848
850
852
854
950
952
954
956
958
840
842
960
962
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
EXISTING
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
PERMANENT
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
OTHER
POLE
OTHER
POLE
POLE
POLE
POLE
POLE
OTHER
POLE
POLE
POLE
POLE
OTHER
OTHER
POLE
OTHER
OTHER
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
POLE
OTHER
POLE
POLE
POLE
POLE
POLE
POLE
POLE
OTHER
OTHER
POLE
POLE
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
30
45
50
50
50
50
50
50
50
50
30
50
30
50
50
50
50
50
30
50
50
50
50
30
30
50
30
30
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
50
30
50
50
50
50
50
50
50
20
25
50
50
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
Ft PittTunnel Inbound CP3
Ft PittTunnel Outbound CP3
Ft PittTunnel Inbound CP4
Ft PittTunnel Outbound CP4
Ft PittTunnel Inbound CP5
Ft PittTunnel Outbound CP5
Ft PittTunnel Inbound CP6
Ft PittTunnel Outbound CP6
Ft PittTunnel Inbound CP7
Ft PittTunnel Upper Portal
Ft Pitt Bridge Lower #13
Ft Pitt Bridge Lower #14
Ft Pitt Bridge Lower #15
Ft Pitt Bridge Lower #16
Ft Pitt Bridge Lower #17
Ft Pitt Bridge Lower #18
Point State Park #19
Ft PittTunnel Lower Portal
Weiss Ln
Mt Nebo Rd
Montgomery Rd
Rodi Rd
McCully Dr
Thompson Run Rd
Laurel Dr
Old William Penn
Haymaker Dr
I-376/SR 22
SR 3069, Liberty Tunnel-North Portal Liberty
Kilbuck St
Duff Rd
McAleer Rd
Pittsburgh Split
Clever Rd
S-Bend NB Entrance
3rd Bend SB
1st Bend NB
2nd Bend NB
3rd Bend NB
Coraopolis Int
Neville Island Br
Deer Run Road
279/28
East Ohio St
Glenfield Rd
Mt Nebo Int
Red Mud Hollow - South
Red Mud Hollow - North
Magee Rd Ext
Nicholson Rd
Rochester Rd
Wedgewood Dr
Wexford Int
Montour Run
Pittsburgh Int West
Pittsburgh Int East
Pittsburgh Int North
W. Harbison Rd
Forest Grove Rd
Crafton
Wabash St
Lowe St
Alexander St
Stuben St
South Main St
St Nicholas Church
Gardner St
31st St
Croft St
40th St
Ft Duquesne Blvd
I-279/SR 65 Interchange
Ohio St
Etna
069.2
069.2
069.3
069.3
069.4
069.4
069.5
069.5
069.7
069.7
069.9
069.8
069.9
069.9
069.9
070.0
000.2
069.7
009.4
010.3
011.5
080.5
081.9
082.4
083.1
083.7
084.2
084.7
066.5
067.0
012.3
013.0
061.1
062.0
062.7
063.0
063.5
064.0
064.5
065.5
066.0
067.5
068.0
070.0
070.5
071.0
071.5
072.0
072.5
073.0
058.6
063.5
064.0
060.0
060.5
061.5
061.1
000.3
000.4
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
ALLEGHENY
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
Allegheny
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0279
0376
0376
0376
0376
0376
0376
0376
3069
0079
0079
0279
0279
0079
0079
0079
0079
0079
0079
0079
0079
0079
0279
0028
0079
0079
0079
0079
0079
0079
0079
0079
0079
0376
0376
0376
0079
0079
0079
0079
0019
0019
0019
H278
0019
0028
0028
0028
0028
0028
0279
0279
0028
0028
0054
0055
0054
0055
0054
0055
0054
0055
0054
0054
0061
0061
0061
0061
0061
0061
0060
0055
0074
0021
0040
0700
0700
1400
1400
2100
2100
2700
2700
3400
0000
0405
0655
0805
0955
1105
1255
2200
0005
40.433352
40.433503
40.433951
40.434197
40.435139
40.435401
40.435943
40.436809
40.437287
40.43765
40.43808
40.43836
40.43867
40.43899
40.43930
40.43971
40.44216
40.43757
40.53860
40.55054
40.56573
40.441898
40.44183
40.443557
40.444726
40.442211
40.438466
40.430146
40.43015
40.52825
40.53586
40.57541
40.58645
40.46513
40.48783
40.49311
40.49332
40.50012
40.50179
40.50496
40.51390
40.52216
40.45254
40.45423
40.54678
40.55238
40.56303
40.56876
40.57872
40.58304
40.58895
40.59696
40.61091
40.45759
40.42385
40.42244
40.42828
40.43326
40.48016
40.45071
40.43118
40.43434
40.43922
40.44358
40.44221
40.45858
40.46471
40.46992
40.47441
40.47861
40.44333
40.44552
40.47846
40.494698
-80.021441
-80.021652
-80.020405
-80.020309
-80.018168
-80.017991
-80.01664
-80.015343
-80.01412
-80.01394
-80.01281
-80.01225
-80.01165
-80.01107
-80.01048
-80.00986
-80.00872
-80.01384
-80.07972
-80.08672
-80.08994
-79.805491
-79.794795
-79.781846
-79.7686
-79.762282
-79.757466
-79.998737
-79.99874
-80.12940
-80.12447
-80.09309
-80.09936
-80.11193
-80.12414
-80.12675
-80.12501
-80.12133
-80.12878
-80.13782
-80.13436
-80.13132
-79.99670
-79.99505
-80.12194
-80.11743
-80.11407
-80.11601
-80.11698
-80.10514
-80.09902
-80.09359
-80.09506
-80.18804
-80.10865
-80.10026
-80.10607
-80.10991
-80.12143
-80.11080
-80.02692
-80.03025
-80.03283
-80.03058
-80.03019
-79.98596
-79.97981
-79.97573
-79.97109
-79.96741
-80.00903
-80.00971
-79.96775
-79.941533
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Vicon
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Pelco
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Vicon
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Surveyor 2000
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Surveyor 2000
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra III
Spectra III
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
Spectra IV
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
SVFT
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
ELECTRIC
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
FIBER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Oct-03
Jan-09
Jan-09
Jan-09
Apr-10
Apr-10
Apr-10
Apr-10
Apr-10
Apr-10
Apr-10
1-Feb-08
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
4/1/2008
4/1/2008
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
1/1/2009
3/1/2009
3/1/2009
3/1/2009
6/15/2009
6/15/2009
3/1/2009
3/1/2009
3/22/2010
3/22/2010
3/22/2010
3/22/2010
3/22/2010
9/1/2010
9/1/2010
9/1/2010
9/1/2010
9/1/2010
4/2/2010
4/2/2010
9/1/2010
9/1/2010
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
ATMS
PennDOT Existing Detectors
Detector Type
Detector ID
SR
Location Name
Direction
Latitude - GIS
Longitude - GIS Manufacturer
Model
Number
Status
District 6-0
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
DA 1 NB
DA 1 SB
DA 2 NB
DA 2 SB
DA 3 NB
DA 3 SB
DA 4 NB
DA 4 SB
DA 5 SB
DA 5 NB
DA 6 SB
DA 6 NB
DA 7 NB
DA 7 SB
DA 8 NB
DA 8 SB
DA 9 SB
DA 9 NB
DA 10 NB
DA 10 SB
DA 12
DA 13 NB & SB
DA 14 NB & SB
DA 15 NB
DA 15 SB
DA 16
DA 101 NB & SB
DA 102
DA 104 SB
DA 104 NB
DA 105
DA 111
DA 112
DA 301
DA-2 US30WB
DA 305 EB
DA 306
DA 310
Microwave Detector
DA 311
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
DA 302 EB & WB
DA 314
DA 312
DA 309
DA 313
DA 315
DA 316
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
I-95
100
100
100
100
100
100
100
30
30
30
30
30
I-95 NB before Allegheny Avenue
I-95 NB after Allegheny Avenue
I-95 NB before Castor Avenue
I-95 NB after Castor Avenue
I-95 at Bridge Street Ramps
I-95 at Bridge Street Ramps
I-95 NB at Bridge St.
I-95 SB at Bridge St.
I-95 SB north of Bridge St.
I-95 NB north of Bridge St.
I-95 SB at top of Cottman Ave. Onramp
I-95 NB before Cottman Ave. Offramp
I-95 NB North of Cottman Ave.
I-95 SB North of Cottman Ave.
I-95 NB 1 mile before Academy Road
I-95 SB near VMS 11
I-95 SB at bottom of Academy Rd. Onramp
I-95 NB before Academy Road Offramp
I-95 NB North of Academy Road
I-95 SB North of Academy Road
I-95 NB & SB before Grant Avenue
I-95 NB just after Tennis Ave. Overpass
I-95 SB just before Woodhaven Rd. Overpass
I-95 NB after Station Ave near CM-954
I-95 SB before Station Ave near CM-954
I-95 near Street Road
PA 100 NB AT PHOENIXVILLE PIKE
PA 100 NB BEFORE KIRKLAND AVENUE
PA 100 SB BEFORE BOOT ROAD
PA 100 NB BEFORE POTTSTOWN PIKE OVERPASS
PA 100 NB AT BOOT ROAD ONRAMP
PA 100 NB BEFORE PA TURNPIKE
PA 100 SB BEFORE PA TURNPIKE
US 30 EB AFTER PA 340
US 30 WB BEFORE PA 100 OFFRAMP
US 30 EB BEFORE PA 113 OFFRAMP
US 30 EB AFTER PA 113
US 30 EB BEFORE PA 100 OFFRAMP
NB
SB
NB
SB
NB
SB
NB
SB
SB
NB
SB
NB
NB
SB
NB
SB
SB
NB
NB
DA 10 SB
DA 12
NB & SB
NB & SB
NB
SB
NB & SB
NB
SB
NB
NB
NB
SB
EB
WB
EB
EB
EB
N39 58.796
N39 58.796
N39 59.327
N39 59.327
N39 59.882
N39 59.882
N40 00.439
N40 00.439
N40 00.738
N40 00.738
N40 01.340
N40 01.319
N40 01.738
N40 01.738
N40 02.125
N40 02.116
N40 02.624
N40 02.549
N40 02.988
N40 02.988
N40 03.619
N40 03.827
N40 04.229
N40 04.444
N40 04.444
N40 05.504
N39 59.767
N40 00.198
N40 00.646
N40 00.630
N40 00.439
N40 03.664
N40 03.947
N40 00.588
N40 01.704
N40 01.142
N40 01.17
N40 00.781
W75 06.337
W75 06.337
W75 05.271
W75 05.271
W75 04.864
W75 04.864
W75 04.349
W75 04.349
W75 03.547
W75 03.547
W75 02.301
W75 02.296
W75 01.382
W75 01.382
W75 01.033
W75 01.107
W75 00.187
W75 00.191
W74 59.664
W74 59.664
W74 58.727
W74 58.241
W74 57.654
W74 56.930
W74 56.930
W74 55.280
W75 35.638
W75 35.983
W75 36.922
W75 36.898
W75 04.349
W75 40.028
W75 40.406
W75 44.146
W75 35.715
W75 41.983
W75 41.238
W75 39.043
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
30
US 30 WB WEST OF S. WHITFORD ROAD
WB
N40 00.840
W75 38.592
EIS
RTMS
Existing
30
30
30
30
30
30
30
US 30 EB AT US 322 OFFRAMP AND ONRAMP
US 30 WB BEFORE PA 100 OFFRAMP
US 30 WB AFTER PA 100 ONRAMP
US 30 WB BEFORE US 30 (BUSINESS) OFFRAMP
US 30 EB AT PA 100
US RT 30 EB AFTER CLOVER MILL RD
US 30 EB BEFORE US 202
EB & WB
WB
WB
WB
EB
EB
EB
N40 00.714
N40 01.393
N40 01.069
N40 00.953
N40 01.220
N40 00.779
N40 01.660
W75 43.602
W75 36.818
W75 37.985
W75 39.587
W75 37.495
W75 38.876
W75 35.704
EIS
EIS
EIS
EIS
EIS
EIS
EIS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
Existing
Existing
Existing
Existing
Existing
Existing
Existing
PennDOT Existing Detectors
Detector Type
Detector ID
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
Model
Number
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
-75.28695
EIS
RTMS
Existing
pending
pending
pending
pending
pending
pending
pending
pending
pending
pending
pending
pending
EIS
EIS
EIS
EIS
EIS
EIS
RTMS
RTMS
RTMS
RTMS
RTMS
RTMS
Existing
Existing
Existing
Existing
Existing
Existing
EB & WB
EB & WB
pending
pending
pending
pending
EIS
EIS
RTMS
RTMS
Existing
Existing
EB & WB
EB & WB
pending
pending
pending
pending
EIS
EIS
RTMS
RTMS
Existing
Existing
SR
Location Name
Direction
Latitude - GIS
Longitude - GIS Manufacturer
US 30 EB OFFRAMP TO US 202
US 30 WB AFTER US 30 (BUSINESS) ONRAMP
US 30 WB AT PA 113 ONRAMP
US 30 WB BEFORE US 322 OFFRAMP (1 MILE)
US 202 SB BEFORE MATLACK STREET
US 202 NB BEFORE WESTTOWN OFFRAMP
US 202 SB BEFORE WESTTOWN ROAD
US 202 NB NORTH OF WESTTOWN RD
US 202 SB AT PA 3 OFFRAMP
US 202 NB AT PA 3
US 202 SB AT PAOLI PIKE
US 202 NB AT PAOLI PIKE
202 SB AT PA 100
US 202 NB BEFORE BOOT ROAD
US 202 NB AT BOOT ROAD
US 202 NB NORTH OF BOOT ROAD
US 202 NB BEFORE US 30
US 202 SB BEFORE BOOT ROAD
US 202 SB AT US 30
I-76 WB at PA 23 exit (same pole as CM-707) WB
I-76 EB @ MM 332.6 (same pole as CM-708) EB
I-76 WB west of Consh, Curve (same pole as CM-709)
WB
I-76 WB east of Consh. Curve (on sign structure with CM711)
I-76 EB east of Waverly Rd (same pole as CM-713) EB
I-76 EB east of Waverly Rd. (freestanding pole) EB
I-76 EB west of Gladwyne (freestanding pole) EB
I-76 WB @ Gladwyne (same pole as CM-715) WB
I-76 EB @ Belmont Ave. (same pole as CM-718) EB
EB
WB
WB
WB
SB
NB
SB
NB
SB
NB
SB
NB
NB & SB
NB & SB
NB & SB
NB & SB
NB
NB & SB
NB & SB
EB & WB
EB & WB
N40 01.830
N40 01.204
N40 01.157
N40 01.010
N39 57.129
N39 57.136
N39 57.559
N39 57.565
N39 57.985
N39 58.002
N39 58.349
N39 58.368
N39 59.473
N39 59.879
N40 00.293
N40 00.739
N40 01.120
N40 01.536
N40 01.906
40.06663
40.06803
W75 35.161
W75 40.754
W75 41.987
W75 42.617
W75 34.902
W75 34.883
W75 34.786
W75 34.782
W75 34.894
W75 34.881
W75 35.018
W75 35.010
W75 35.355
W75 35.154
W75 34.959
W75 34.901
W75 35.123
W75 35.362
W75 35.186
-75.31248
-75.30072
EB & WB
40.07200
EB & WB
EB & WB
EB & WB
EB & WB
EB & WB
EB & WB
Status
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
DA 317
DA 307
DA 305 WB
DA 303
DA205SB
DA205NB
DA206SB
DA206NB
DA207SB
DA207NB
DA208SB
DA208NB
DA210 NB&SB
DA211 NB&SB
DA212 NB&SB
DA213 NB&SB
DA214
DA215NB&SB
DA216 NB&SB
DA701 EB & WB
DA702 EB & WB
30
30
30
30
202
202
202
202
202
202
202
202
202
202
202
202
202
202
202
I-76
I-76
Microwave Detector
DA703 EB & WB
I-76
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
DA704 EB & WB
DA705 EB & WB
DA706 EB & WB
DA707 EB & WB
DA708 EB & WB
DA709 EB & WB
I-76
I-76
I-76
I-76
I-76
I-76
Microwave Detector
Microwave Detector
DA710 EB & WB
DA717 EB & WB
I-76
I-76
Microwave Detector
Microwave Detector
DA720 EB & WB
DA721 EB & WB
I-76
I-76
I-76 WB east of Belmont Ave. (same pole as CM-719) WB
I-76 EB @ US 1 (same pole as CM-722) EB
I-76 WB west of Montgomery Dr, (same pole as CM-724)
WB
I-76 EB @ Montgomery Dr. (same pole as CM-725) EB
Microwave Detector
DA723 EB & WB
I-76
I-76 EB west of Girard Ave. (same pole as CM-727) EB
EB & WB
pending
pending
EIS
RTMS
Existing
Microwave Detector
Microwave Detector
DA724 EB & WB
DA726 EB & WB
I-76
I-76
EB & WB
EB & WB
pending
pending
pending
pending
EIS
EIS
RTMS
RTMS
Existing
Existing
Microwave Detector
DA727 WB
I-76
WB
pending
pending
EIS
RTMS
Existing
Microwave Detector
Microwave Detector
DA727 EB
DA731 EB & WB
I-76
I-76
I-76 WB east of Girard Ave. (same pole as CM-729) WB
I-76 EB ramp to I-676 (same pole as CM-732) EB
I-76 WB @ 30th Street (from graphics but can't be seen)
WB
I-76 EB @ South St. (on sign structure opposite CM-735)
EB
I-76 EB @ Vare Ave. (on same pole as CM-739) EB
EB
EB & WB
pending
pending
pending
pending
EIS
EIS
RTMS
RTMS
Existing
Existing
Microwave Detector
DA50 NB & SB
1
US 1 NB south of Henry Ave. (same pole as CM-101) NB
NB & SB
pending
pending
EIS
RTMS
Existing
PennDOT Existing Detectors
EIS
Model
Number
RTMS
Existing
pending
EIS
RTMS
Existing
pending
pending
pending
pending
EIS
EIS
RTMS
RTMS
Existing
Existing
pending
pending
EIS
Existing
SB
N40 04.654
W75 24.644
Econolite
US 202 NB AT OLD EAGLE SCHOOL RD
NB
N40 04.654
W75 24.644
Econolite
202
US 202 SB AT END OF SWEDESFORD RD ONRAMP
SB
N40 04.525
W75 25.200
Econolite
VIDS 4
202
US 202 NB AT MILE MARKER 24.2
NB
N40 04.517
W75 25.099
Econolite
Video Detector
VIDS 5
202
US 202 SB AT MILE MARKER 23.8
SB
N40 04.380
W75 25.818
Econolite
Video Detector
VIDS 6
202
US 202 NB AT MILE MARKER 23.8
NB
N40 04.300
W75 26.339
Econolite
Video Detector
VIDS 7
202
US 202 NB AFTER VALLEY FORGE RD OFFRAMP
NB
N40 04.304
W75 26.375
Econolite
Video Detector
VIDS 8
202
SB
N40 04.304
W75 26.375
Econolite
Video Detector
VIDS 9
202
NB
N40 04.188
W75 26.869
Econolite
Video Detector
VIDS 10
202
US 202 SB BEFORE VALLEY FORGE RD ONRAMP
US 202 NB SIGN STRUCTURE BETWEEN MM 22.7 &
22.8
US 202 SB SIGN STRUCTURE BETWEEN MM 22.7 &
22.8
SB
N40 04.188
W75 26.869
Econolite
Video Detector
VIDS 11
202
US 202 SB ON PA 252 OVERPASS
SB
N40 03.982
W75 27.438
Econolite
Video Detector
VIDS 12
202
US 202 NB ON PA 252 OVERPASS
NB
N40 03.969
W75 27.407
Econolite
RTMS
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
Autoscope
706110
65
376
376
376
376
376
376
376
79
79
79
79
19
McKees Rocks Br North
Rodi Rd
McCully Dr
Thompson Run Rd
Laurel Dr
Old William Penn
Haymaker Dr
I-376/SR 22
Wexford Int
Crafton Int
S-Bend NB Entrance
Neville Island Bridge
Wabash St
SB
EB
EB
EB
WB
WB
WB
EB
SB
SB
NB
NB
NB
40.478691
40.440377
40.441898
40.441830
40.443557
40.444726
40.442211
40.438466
40.610914
40.450714
40.487805
40.513893
40.431263
-80.043135
-79.831527
-79.805491
-79.794795
-79.781846
-79.768600
-79.762282
-79.757466
-80.095283
-80.110975
-80.124226
-80.134305
-80.026788
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
Detector Type
Detector ID
SR
Location Name
Direction
Microwave Detector
DA51 NB & SB
1
US 1 SB @ Fox St. (same pole as CM-102) SB
NB & SB
pending
pending
Microwave Detector
DA52 NB &SB
1
US 1 SB @ Wissahicken Ave. (same pole as CM-103) SB NB & SB
pending
Microwave Detector
Microwave Detector
DA53 NB & SB
DA54 NB & SB
1
1
Microwave Detector
DA56 NB & SB
1
Video Detector
VIDS 1
202
US 202 SB AT OLD EAGLE SCHOOL ROAD
Video Detector
VIDS 2
202
Video Detector
VIDS 3
Video Detector
US 1 SB @ Roberts/Berkley Ave. (freestanding pole
across from CM-104, looks like 1 detector for NB & SB) SB NB & SB
US 1 NB @ 17th Street (same pole as CM-105) NB
NB & SB
US 1 in the median south of 9th Street (same pole as CM107)
NB & SB
Latitude - GIS
Longitude - GIS Manufacturer
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
District 11-0
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
866
408
415
420
425
430
435
440
710
610
620
650
846
RTMS G4
RTMS G4
RTMS G4
RTMS G4
RTMS G4
RTMS G4
RTMS G4
RTMS X3
RTMS G4
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
PennDOT Existing Detectors
Detector Type
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Detector ID
SR
848
850
852
854
55
60
65
70
75
80
85
90
95
100
105
107
110
111
115
120
125
130
132
146
147
150
160
161
168
169
180
181
185
186
190
191
200
205
220
225
230
235
240
245
310
315
321
325
19
19
19
376
376
376
376
376
376
376
376
376
79
376
376
376
376
376
376
376
376
376
6279
6279
6279
6279
6279
6579
6579
6279
6279
6279
6279
6279
6279
6279
6279
279
279
279
279
279
279
376
376
376
376
Location Name
Lowe St
Alexander St
South Main St
Stuben St
Robinson Town Center
Ikea
US22-30/SR60 Interchange
Settlers Cabin EB Off-Ramp
Settlers Cabin
Settlers Cabin EB On-Ramp
Bishops Corner Interchange
Campbells Run
US-22/I-279 SB On Ramp
I-279 Pittsburgh Interchange
Rosslyn Farms Interchange
Carnegie Busway
Carnegie Interchange
VMS 20
Greentree Interchange
Greentree Hill Top
Greentree Hill Middle
Banksville Interchange NB
Banksville Interchange SB
Sandusky St - NB
Sandusky St - SB
Anderson St
East St- NB
East St- SB
Veterans Bridge - NB
Veterans Bridge - SB
St Boniface - NB
St Boniface - SB
Hazlett St - NB
Hazlett St - SB
Venture St - NB
Venture St - SB
McKnight Road
Perrysville
Jack's Run
Bellevue Road
Union Ave South
Union Ave North
Ben Avon Hts Rd
Camp Horne Rd
Fort Pitt Blvd
Grant Street
10th Street Bridge
2nd Avenue
Direction
NB
SB
SB
NB
EB
WB
WB
EB
EB
EB
EB
EB
WB
NB
SB
NB
NB
NB
SB
SB
NB
NB
SB
NB
SB
SB
NB
SB
NB
SB
NB
SB
NB
SB
NB
SB
NB
SB
NB
SB
SB
NB
SB
SB
WB
EB
EB
WB
Latitude - GIS
40.434402
40.439218
40.442208
40.443533
40.4522886
40.4501700
40.4471450
40.4433177
40.4386328
40.4338577
40.4308422
40.4254173
40.4251375
40.4229405
40.4204126
40.4162917
40.4103101
40.4136839
40.4207168
40.4210864
40.4229323
40.4286208
40.4286208
40.4494045
40.4494045
40.4498373
40.4525927
40.4525927
40.4490474
40.4489473
40.4608440
40.4608440
40.4739382
40.4739382
40.4826786
40.4826786
40.4952933
40.5002027
40.5070818
40.5077405
40.5139643
40.5190986
40.5200039
40.5244161
40.4376946
40.4351725
40.4339945
40.4347274
Longitude - GIS Manufacturer
-80.030193
-80.032931
-80.030182
-80.030552
-80.1727643
-80.1678237
-80.1657530
-80.1610565
-80.1525914
-80.1432466
-80.1371365
-80.1239749
-80.1155179
-80.1058995
-80.0923030
-80.0857427
-80.0720098
-80.0640141
-80.0489589
-80.0421059
-80.0302961
-80.0297677
-80.0297677
-80.0032621
-80.0032621
-79.9996599
-79.9968570
-79.9968570
-79.9925842
-79.9927398
-79.9991932
-79.9991932
-80.0055608
-80.0055608
-80.0072452
-80.0072452
-80.0133338
-80.0238052
-80.0349310
-80.0446513
-80.0520542
-80.0544279
-80.0630941
-80.0701886
-80.0016555
-79.9991637
-79.9866083
-79.9872735
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
Model
Number
RTMS G4
RTMS G4
RTMS G4
RTMS G4
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
PennDOT Existing Detectors
Detector Type
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Detector ID
SR
330
332
335
340
345
350
370
375
380
385
390
395
400
405
407
410
804
806
50
99
101
250
255
260
265
270
550
555
556
560
565
570
575
580
585
586
590
595
600
605
612
615
625
630
635
640
645
655
376
376
376
376
376
376
376
376
376
376
376
376
376
376
376
376
51
51
376
376
376
279
279
279
279
279
79
79
79
79
79
79
79
79
79
79
79
79
79
79
79
79
79
79
79
79
79
79
Location Name
Brady Street EB
Brady Street WB
Bates Street
Swinburne Street
Saline Street
Beechwood Blvd
Commercial Street
Swissvale
Edgewood
Brinton Road
Forest Hills
Wilkinsburg
Greensburg Pike
Churchill Interchange
Buss 22 - Monroeville
Penn Hills Interchange
Crane Avenue
Liberty Interchange
Montour Run
Pittsburgh Int West
Pittsburgh Int East
Weiss Lane
Mt Nebo Road
Montgomery Rd
McAleer Rd
Pittsburgh Split
Bridgeville North
Chartiers Creek NB
Chartiers Creek SB
Prestley Rd
Kirwin Hts Interchange
Thoms Run Rd
Collier Ave
Carnegie South
Carnegie NB
Carnegie SB
Ewing Road
Pittsburgh Int South
Pittsburgh Int North
W Harbison Rd
Clever Rd
Forest Grove Rd
3rd Bend SB
1st Bend NB
2nd Bend NB
3rd Bend NB
Coraopolis Int
Deer Run Road NB
Direction
EB
EB
WB
EB
WB
EB
EB
EB
WB
EB
EB
WB
EB
WB
EB
EB
SB
SB
EB
EB
WB
SB
SB
SB
NB
SB
NB
NB
SB
NB
NB
NB
NB
NB
NB
SB
NB
NB
NB
SB
NB
SB
SB
NB
NB
NB
NB
NB
Latitude - GIS
40.4360871
40.4360871
40.4319120
40.4271671
40.4293885
40.4291170
40.4253050
40.4261605
40.4303257
40.4293293
40.4321509
40.4388798
40.4441832
40.4442240
40.4439832
40.4419663
40.4161212
40.4141842
40.457536
40.423498
40.422607
40.538722
40.550538
40.565721
40.575370
40.586460
40.363998
40.369319
40.369319
40.372291
40.373823
40.381718
40.388484
40.393255
40.399028
40.399028
40.407167
40.414122
40.428304
40.433204
40.465134
40.480143
40.493151
40.493377
40.500264
40.501791
40.504972
40.522092
Longitude - GIS Manufacturer
-79.9739053
-79.9739053
-79.9590915
-79.9526408
-79.9413514
-79.9312314
-79.9088698
-79.8937180
-79.8821470
-79.8764258
-79.8711848
-79.8623120
-79.8540460
-79.8410180
-79.8411408
-79.8232483
-80.0144067
-80.0093373
-80.188130
-80.108799
-80.100209
-80.079473
-80.086629
-80.090033
-80.093175
-80.099527
-80.11875
-80.118793
-80.118793
-80.110533
-80.103885
-80.096462
-80.096462
-80.100679
-80.105154
-80.105154
-80.107378
-80.104731
-80.105887
-80.110141
-80.111776
-80.121473
-80.126863
-80.125141
-80.120923
-80.128781
-80.137959
-80.131154
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
Model
Number
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X2
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
PennDOT Existing Detectors
Detector Type
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Microwave Detector
Detector ID
SR
656
660
665
670
675
680
685
690
700
705
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
950
952
954
956
958
960
79
79
79
79
79
79
79
79
79
79
279
279
279
279
279
376
376
376
376
279
279
279
279
279
376
28
28
28
28
28
Location Name
Deer Run Road SB
Kilbuck St
Duff Rd
Glenfield Rd
Mt Nebo Int
Red Mud Hollow - South
Red Mud Hollow - North
Magee Rd Ext
Rochester Rd
Wedgewood Dr
Ramp B Fort Pitt Bridge
Fort Pitt Bridge - Ramp A
Fort Pitt Bridge - Outbound
Fort Pitt Bridge - Outbound RT
Fort Pitt Bridge - Outbound LT
Ramp N Fort Pitt Bridge
On-Ramp Fort Pitt Bridge
On-Ramp Fort Pitt Bridge
Stanwix On-Ramp to I-376WB
Ramp D Ft Duquesne Br
Ramp D Ft Duquesne Blvd
Liberty Off-Ramp Fort Pitt Br
Liberty On-Ramp - Fort Pitt Br
Blvd Alllies - Off-Ramp
Grant St Off Ramp I-376EB
St Nicholas Church
Gardner St
31st St Bridge
Croft St
40th St Bridge
Ohio St
Direction
Latitude - GIS
Longitude - GIS Manufacturer
NB
NB
NB
SB
NB
NB
SB
SB
SB
NB
NB
SB
NB
SB
SB
EB
WB
WB
WB
SB
NB
NB
SB
NB
EB
NB
40.522092
40.528130
40.535805
40.546813
40.552305
40.563024
40.568734
40.578766
40.589013
40.596946
40.4380755
40.4381592
40.4375692
40.4377060
40.4376692
40.4395351
40.4395269
40.4394881
40.4391819
40.4411968
40.4413335
40.4406619
40.4406701
40.4404088
40.4360279
40.458561
-80.131154
-80.129205
-80.124195
-80.122234
-80.117158
-80.113954
-80.116088
-80.117083
-80.099141
-80.093426
-80.0141519
-80.0138193
-80.0135940
-80.0136289
-80.0136101
-80.0097316
-80.0089189
-80.0089377
-80.0080204
-80.0090074
-80.0092434
-80.0073471
-80.0078997
-80.0078058
-80.0001776
-79.985944
NB
SB
NB
NB
40.464594
40.469962
40.474508
40.478655
-79.979531
-79.975801
-79.971254
-79.967459
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
EIS
Wavetronix
Wavetronix
Wavetronix
Wavetronix
Wavetronix
Wavetronix
Model
Number
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
RTMS X3
SSI 105
SSI 105
SSI 105
SSI 105
SSI 105
SSI 105
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
APPENDIX R
LIST OF UPCOMING INTEGRATION PROJECTS
Appendix R
List of Upcoming Integration Projects
As of 2011-01-10
STATUS
District
408
24
244
County
SR
Sec
Let Date (Estimated)
Actual Let Date
CCTV
HAR
DMS
DEVICE TOTALS
143
283
RTMS
VIDS
201
82
tag readers
Bluetooth
IN PROGRESS
Construction
1
Erie
79
PHA
9/23/2010
9/23/2010
4
3
9
Construction
1
Erie
79
PHA
9/23/2010
9/23/2010
11
0
0
Construction
2
Clearfield
80
B28
5/7/2008
1
6
Construction
2
Clearfield
153
N23
11/13/2008
11/13/2008
Construction
2
Clinton
150
314
9/3/2009
9/3/2009
1
Construction
2
Elk
219
N24
10/15/2009
10/15/2009
0
0
1
Construction
2
Centre
3014
N11
5/13/2010
5/13/2010
7
0
2
Construction
5
Berks
78
WIT
5/21/2009
5/21/2009
5
3
3
Construction
5
Schuylkill
81
WIT
5/21/2009
5/21/2009
6
Construction
5
Berks
176
02S
4/15/2010
4/15/2010
Construction
5
Berks
176
02S
4/15/2010
4/15/2010
1
1
3
Programmed
6
Philadelphia
76
ITS
12/21/2006
12/21/2006
44
0
10
26
Construction
6
Montgomery
309
104
2/9/2007
21
0
9
42
Construction
6
Montgomery
476
RES
12/20/2007
0
0
5
Construction
6
Philadelphia
95
CP1
1/8/2009
1/8/2009
12
0
3
24
Construction
6
Bucks
95
ITB
5/21/2009
5/21/2009
17
0
10
39
Construction
6
Delaware
95
ITC
6/4/2009
6/4/2009
1
14
Construction
6
Delaware
95
ITC
6/4/2009
6/4/2009
Construction
6
Philadelphia
95
GR0
7/2/2009
Construction
6
Bucks
95
ITF
7/16/2009
7/16/2009
Construction
6
Montgomery
476
RDC
7/30/2009
7/30/2009
Construction
6
Montgomery
76
RMP
8/27/2009
Construction
6
Montgomery
202
65N
12/17/2009
12/17/2009
4
Construction
8
Cumberland
81
19
2/20/2009
2/20/2009
1
Construction
8
Lancaster
30
0
11/3/2009
11
Construction
8
York
83
0
11/3/2009
13
Appendix R
1
4
18
0
11
1
0
0
29
15
39
1
54
21
30
25
26
39
26
21
3
2
2
Page 1 of 3
Appendix R
List of Upcoming Integration Projects
As of 2011-01-10
408
24
244
CCTV
HAR
DMS
STATUS
District
County
SR
Sec
Let Date (Estimated)
Actual Let Date
Construction
10
Allegheny
19
0
2/25/2010
2/25/2010
Construction
11
Allegheny
79
0
10/1/2009
10/1/2009
Construction
11
Allegheny,
Beaver, butler,
Washington
19
0
2/25/2010
2/25/2010
Construction
11
Allegheny
28
A10
6/10/2010
6/10/2010
Construction
12
Washington /
Westlmoreland
6/17/2010
6/17/2010
4
1
6
Construction
12
Washington /
Westlmoreland
6/17/2010
6/17/2010
17
0
2
260
9
108
70
0
Projects
IN PROGRESS TOTALS
SFY SUBTOTAL
DEVICE TOTALS
143
283
201
82
RTMS
VIDS
tag readers
Bluetooth
94
203
139
0
3
32
6
1
SFY 2010/2011
Programmed
1
Erie
97627
PCT
12/16/2010
Programmed
2
Centre
350
N02
11/4/2010
0
1
1
Programmed
3
109
6/23/2011
1
1
4
3
Northumberlan
d
Columbia
80
Planned
6/23/2011
1
1
4
Programmed
6
Philadelphia
95
GR1
1/21/2011
22
0
17
10
20
27
Programmed
6
Montgomery
202
7IT
2/17/2011
21
0
9
12
1
17
Programmed
6
Philadelphia
95
CP2
6/9/2011
3
0
7
7
2
2
18
Programmed
9
Bedford
99
09T
4/21/2011
2
Programmed
11
Allegheny
579
A05
6/9/2011
7
24
23
62
80
Projects
SFY 2010/2011 TOTALS
9/23/2010
3
1
50
3
46
SFY 2011/2012
Programmed
4
Lackawanna
81
218
8/4/2011
Programmed
4
Luzerne
81
ITS
11/10/2011
Programmed
4
Luzerne
81
ITS
11/10/2011
Programmed
4
Luzerne
81
0
2/9/2012
Programmed
5
Carbon
80
0
10/15/2011
Programmed
5
Monroe
80
0
10/15/2011
2
Programmed
6
Chester
202
320
7/1/2011
1
Planned
6
Montgomery
202
520
7/14/2011
3
Programmed
6
Montgomery
9101
ITS
3/1/2012
11
Appendix R
2
1
2
1
3
8
1
3
1
3
40
0
22
2
2
4
6
Page 2 of 3
Appendix R
List of Upcoming Integration Projects
As of 2011-01-10
SR
Sec
Let Date (Estimated)
95
GR2
6/7/2012
various
various
7/1/2011
063
2/9/2012
24
244
CCTV
HAR
DMS
RTMS
20
0
11
STATUS
District
County
Programmed
6
Philadelphia
Planned
8
Franklin
Programmed
8
York
83
Planned
10
Indiana,
Westmoreland
22, 119
11/3/2011
Planned
10
Butler
79
4/5/2012
Planned
10
Butler, Clarion,
Jefferson
79, 80
4/5/2012
3
Programmed
11
Allegheny
376
12/15/2011
8
A35
Projects
Actual Let Date
DEVICE TOTALS
143
283
408
201
82
VIDS
tag readers
Bluetooth
2
22
2
20
42
30
24
20
5
11
SFY 2011/2012 TOTALS
5
8
63
7
49
SFY 2012/2013
Programmed
2
Centre
80
ITS
4/1/2013
1
1
2
Programmed
2
Centre
80
ITS
4/1/2013
6
1
14
Planned
2
Centre
220
J10 P2
4/1/2013
4
0
1
3
6
0
10
Planned
2
Centre
322
J10 P3
4/1/2013
0
Programmed
5
Berks
222
0
12/5/2012
5
Programmed
6
Montgomery
422
ITS
7/12/2012
18
Programmed
6
Philadelphia
76
PCC
12/6/2012
1
Programmed
8
Cumberland
81
0
10/1/2012
Planned
10
Clarion,
Jefferson
80
10/4/2012
Planned
10
Clarion,
Jefferson
80
3/7/2013
Projects
4
15
1
26
3
SFY 2012/2013 TOTALS
35
5
41
0
26
15
0
CCTV
HAR
DMS
RTMS
VDS
tag readers
Bluetooth
201
82
TOTALS
STATUS
District
PROJECTS
Appendix R
County
SR
Sec
Let Date (Estimated)
TOTALS
Actual Let Date
TOTAL
408
24
244
143
283
Page 3 of 3
APPENDIX S
AS-IS DISTRICT SYSTEMS AND DEVICES
This appendix provides a high level overview of the existing ITS software and
devices (by manufacturer) currently used in each of the PennDOT Engineering
Districts. The Selected Offeror is expected to provide a software solution that will
integrate all PennDOT ITS devices* into a single Next Generation ATMS system.
*The Ramp Meters in District 6 are not included into the initial system deployment phases of this project
(please refer to Appendix N Phasing Plan).
AS-IS District Systems and Devices
District 1 TMC
System Module
DMS
HAR
Software
Vanguard
DR2000 Platinum
As of 2011-02-08
Device
Manufacturer
Daktronics
HIS
District 2 TMC
AS-IS District Systems and Devices
As of 2011-02-08
System Module
Software
Device
Manufacturer
CCTV
ATMS
Bosch
Intelligent
Control
Adaptive
Microsystems
PSC SMC 10002000
PSC
Messenger
FDS/SES America
Vanguard
Daktronics
DR2000 Platinum
HIS
DMS
HAR
AS-IS District Systems and Devices
District 3
System Module
DMS
As of 2011-02-08
Software
Device
Manufacturer
NTCIP VMS
Central
Display Solutions
PSC SMC 10002000
PSC
AS-IS District Systems and Devices
System Module
Software
As of 2011-02-08
Device
Manufacturer
Bosch
DIVAR
CCTV
Cylink
e-airlink
District 4 TMC
ASTI
Dambauch VMS
DMS
PSC SMC 10002000
Dambauch
STDFULL
PSC
AMSIG Easyhost
AMSIG
NET
WANCO
WANCO
HAR
DR2000 Platinum
HIS
District 5 TMC
AS-IS District Systems and Devices
As of 2011-02-08
Device
Manufacturer
System Module
Software
CCTV
Phillips/Bosch
GUI version 2.43
Bosch
Vanguard
Daktronics
PSC SMC 10002000
DMS
PSC
STDFULL
AMSIG Easyhost
AMSIG
NET
HAR
DR2000 Platinum
HIS
AS-IS District Systems and Devices
System Module
Software
As of 2011-02-08
Device
Manufacturer
Phillips
District 6 RTMC
CCTV
Incident
detection
DYNAC /
Allegiant Joystick
Keyboard
DYNAC
AMSIG Easyhost
Bosch
DS&E
RTMS
(Radar Detectors)
VIDS
(Video Detectors)
AMSIG
Display Solutions
DMS
DYNAC
Dambach
Daktronics
Travel Times
Ramp Meters
FDS/SES America
Transmit
EIS
Transcore
Toll tag readers
District 8 RTMC
AS-IS District Systems and Devices
As of 2011-02-08
Device
Manufacturer
System Module
Software
CCTV
VIDSYS Vidshield
6.1
BOSCH
Vanguard
Daktronics
PSC SMC 10002000
PSC
Mercure
FDS/SES America
AMSIG EasyHost
AMSIG
DR2000 Platinum
HIS
DMS
HAR
COHU
AS-IS District Systems and Devices
System Module
Software
As of 2011-02-08
Device
Manufacturer
Phillips
CCTV
ATMS
District 9 TMC
Bosch
FDS/SES America
DMS
ATMS
Adaptive Micro
Systems
HAR
DR2000 Platinum
HIS
AS-IS District Systems and Devices
District 10 TMC
System Module
As of 2011-02-08
Software
Device
Manufacturer
Vanguard
Daktronics
Intelligent
Control
ADDCO
DR2000 Platinum
HIS
DMS
HAR
AS-IS District Systems and Devices
System Module
Software
As of 2011-02-08
Device
Manufacturer
Vicon
District 11 RTMC
CCTV
ATMS
Pelco
Cohu
Daktronics
DMS
ATMS
Display Solutions
LEDStar
Travel Times
ATMS
EIS
Wavetronix
Microwave
HAR
DR2000 Platinum
HIS
AS-IS District Systems and Devices
System Module
As of 2011-02-08
Software
Device
Manufacturer
ATMS
Display Solutions
Vanguard
Daktronics
DR2000 Platinum
HIS
District 12
DMS
HAR
APPENDIX T
VENDOR SOFTWARE CAPABILITIES MATRIX
APPENDIX T
PENNDOT REQUIREMENTS /
VENDOR'S EXISTING SOFTWARE CAPABILITIES MATRIX
Module
Number of PennDOT
Requirements
DMS
20
CCTV
10
HAR
9
Travel Time module
5
Incident response plan
16
Incident detection/alarm module/vehicle detectors
13
HMI - Regional operations requirements
17
Administration
20
Asset Management
5
Data warehouse
18
Performance measures
13
Interfaces
11
RCRS Interface (includes EDRS)
1
INRIX/ Probe data
1
HOV module
2
Interface to 511
1
AVL Interface
5
Traffic signal systems
6
MDSS / RWIS Interface
0
Queue detection (D5)
0
Interface to RIMIS (D6)
0
Ramp meter interface
0
Number of
Requirements met "Out
of the Box"
Requirements Not Met "Out of the Box*
*Please use the requirements numbers in the System Requirements to identify the requirements that are not met "Out of the Box".
Appendix T Page 1 of 23
APPENDIX T
INSTRUCTIONS FOR
PENNDOT REQUIREMENTS /
VENDOR'S EXISTING SOFTWARE CAPABILITIES MATRIX
Using the codes below, indicate the software’s ability to meet each of the listed requirements. PennDOT has established response
codes that shall be used:
OB - requirement fully met “out of the box”, requiring no change to base source code or configuration
CO - requirement fully met through configuration, requiring no change to base source code
DT - requirement fully met using proposed development tools to extend functional Capabilities, allowing upgrades and full
product support
CU - customization required to fully meet requirement, requiring changes to base source code
TP - requires integration with a third party solution
NA - not available - software does Not address requirement
FR - not available at present, but will be in a future release
Offeror shall use only one (1) code per requirement. Any requirement that is responded to in any other way will be treated as an “NA”
response. Any response that exceeds the software’s capability or is contradicted by other information in the proposal will also be
considered an “NA” response.
Offeror shall provide comments for any “CU”, “TP”, “NA” or “FR” response. Additional comments relative to a requirements group as a
whole can be included in the space provided.
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
DMS
FDM01 Create a message for display on a DMS.
Enforce the same constraints on the user’s message that exist for
FDM02 the selected DMS regarding: allowable set of characters, number of
lines of text, number of characters per line and fonts.
Maintain a list of forbidden words. The ATMS software shall prevent
a message containing any word on the forbidden list from being
FDM03
posted on any DMS device. The ATMS software shall provide a
facility for an authorized user to modify the list of forbidden words.
FDM04 Create, edit and save messages in a message library.
FDM05 Activate the message on the selected DMS device(s).
Allow the user to specify any number of DMS devices to receive a
FDM06
given message.
Provide the user the capability to remove a message from one or
FDM07
more DMS.
FDM08
Confirm that the proposed message, specified by the user, has
been properly posted to the DMS device(s) selected by the user.
FDM09
Allow the user to perform remote maintenance, such as pixel tests,
to check for outages of individual pixels.
FDM10
Maintain a history of all DMS messages that have been activated
along with the user name and time when it was activated.
FDM11 Manual control of the brightness of a DMS device display.
Messages posted on a DMS shall appear on the ATMS software
graphical user interface along with the icon representing the device.
FDM12
A mouse over function will provide message information and an
accurate representation of the current message.
The ATMS software shall provide the user the ability to access the
DMS from a map, table or tree view type list.
FDM14 Allow users to blank (command) a DMS.
FDM15 Functionality to prioritize and schedule messages.
FDM13
Appendix T Page 1 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
FDM16
FDM17
FDM18
FDM19
FDM20
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
Automatically update messages based on data such as Travel Time
or Detector Speed.
Allow a user with Administrative privileges to configure the number
of times that the ATMS software will attempt to resend a message
to a DMS if there is a communication failure.
If a communication failure occurs when sending a message to a
DMS, the ATMS software will attempt to resend the message for the
number of times that have been configured by an Administrative
user.
Notify the user if a message was not successfully posted to the
selected DMS(s) within a specified number of attempts to post the
message.
Provide an efficient method of creating, editing and activating
messages to multiple sign types.
CCTV
FCC01
The ATMS software shall allow Administrators to save camera
presets for each PTZ camera including a location description. A
preset camera position shall consist of a pan angle, tilt angle, zoom
setting, focus setting and a title that is superimposed on the image.
FCC02
The ATMS software shall allow at least 25 preset camera positions
for any Pan-Tilt-Zoom (PTZ) camera.
FCC03
The ATMS software shall support screen titles for at least 16 zones
for each PTZ camera, such that the camera image displays the
zone name whenever the camera is aimed anywhere in the zone,
unless the camera has been commanded to a preset view.
FCC04
FCC05
The ATMS software shall be capable of accessing the video stream
of a camera from a designated video distribution system where the
ATMS software is installed.
The ATMS software shall provide the user the ability to select any
camera view to be displayed on any monitor controlled by the user’s
video switch.
Appendix T Page 2 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
FCC06
FCC07
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
The ATMS software shall allow an authorized user to control the
camera by adjusting the camera’s pan, tilt, zoom, presets, iris and
focus controls in the current view via joystick or keyboard, including
but not limited to joystick keyboard and virtual joystick/mouse
control
The ATMS software shall provide an authorized user the ability to
create and edit video tours, consisting of a sequence of feeds from
various cameras, using preset pan-tilt-zoom settings for each
camera in the sequence.
FCC08
The ATMS software shall allow Operators to share control of CCTV
within a TMC. Share of control will be based on a specified time-out
period as well as user level. A user with higher user privileges can
assume control from a user with lower privileges.
FCC09
The ATMS software shall allow Operators to access the designated
video distribution system and block video from view of selected
outside sources.
FCC10
When a potential incident notification is triggered, the ATMS
software solution shall aim the nearest CCTV camera in the
direction of sensor that signaled the incident. The ATMS software
shall provide a mechanism to turn this feature on or off.
HAR
FHR01
The ATMS software shall provide the ability to manage Highway
Advisory Radios (HAR) and HAR beacons through the Platinum
Software.
FHR02
The management functionality provided by the ATMS software shall
support the ability to: Predefine and store messages, select and
activate predefined messages, activate operator entered messages,
prioritize and schedule messages, verify current status.
FHR03
FHR04
The ATMS software shall allow the user to specify any number of
HAR devices to receive a given message.
The ATMS software shall provide the user the capability to remove
a message from one or more HAR.
Appendix T Page 3 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
FHR05
FHR06
FHR07
FHR08
IR13
Comments
The ATMS software shall confirm that the proposed message,
specified by the user, has been properly posted to the HAR
device(s) selected by the user.
The ATMS system shall allow the user to listen to the message
being broadcast by a given HAR.
The ATMS software shall allow Operators to share HAR control
within a TMC.
The ATMS software shall allow Operators to activate/deactivate
HAR Beacons individually or as a group.
The ATMS software shall allow PennDOT to maintain functionality
through the existing Platinum Software for the control of Highway
Advisory Radio (HAR) and Beacon Control.
Travel Time Module
FTT01
FTT02
FTT03
FTT04
FTT05
The ATMS software shall have the ability to use PennDOT
detectors, other outside sources (i.e. traffic.com), vehicle probe
data (i.e. INRIX), and other data sources as they become available
to compute a current estimated travel time between any pair of
interchanges or devices as selected by the user.
The ATMS software shall automatically update the current
estimated travel time on any DMS that are displaying travel time
messages.
The ATMS software shall automatically update the current
estimated travel times that are sent to outside partners.
The ATMS software shall compute the current length (distance) of
congested traffic on a given route from a user-specified point,
based on vehicle speed and/or occupancy data.
The ATMS software shall alert operators if travel times exceed a
specified threshold.
Incident Response Plans
FRP01
FRP02
The ATMS software shall allow for center-based capability to
formulate an incident response that takes into account the incident
duration, total road and lane closures.
The ATMS software shall enable the user to define “response
plans” that utilize any combination of devices and order of activation
to automatically respond to an incident or any event.
Appendix T Page 4 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
FRP03
FRP04
FRP05
FRP06
FRP07
FRP08
FRP09
FRP10
FRP11
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
The ATMS software response plans shall consist of a preprogrammed sequence of suggested Operator actions devised as a
standard response to a particular type of event.
Individual steps in the ATMS software response plans shall have
the ability to activate specific roadside devices automatically (after
operator approval), such as posting a pre-defined message to a
DMS.
Some individual steps in the ATMS software response plans shall
be informational – for example, instructing the operator to contact
State Police.
The ATMS software shall allow a user to create, edit, and save a
library of response plans.
The ATMS software library shall be searchable by title text and any
other information associated with the response plan.
The ATMS software users shall have the ability to deactivate the
response plan and restore the system to its previous state.
The ATMS software users shall have the ability to skip any step in
the response plan.
The ATMS software user shall be able to activate a response plan
in 2 ways: as an action in response to managing an active incident
(icon in incident entry form) or by selecting a link and requesting a
new response plan based on location.
The ATMS software actions available for use in a response plan
shall include: activation of roadside devices (i.e. - posting a
predefined message to a DMS), Providing information or instruction
to an operator's screen (i.e. - instructing the operator to contact the
State Police), activation of a diversion route, sending an e-mail, fax,
text message, or page, Issuing a command to the Road Closure
Reporting System to modify a road status, Generation of a predefined report.
FRP12
The ATMS software shall allow Administrative users to create
existing or configure new response plans, which shall be configured
by: Location, Severity, Upstream Distance, and Individual devices.
FRP13
The ATMS software shall prompt the operator to confirm the
automatic cancellation of associated equipment activation when
incident is closed.
Appendix T Page 5 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
FRP14
FRP15
FRP16
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
All devices in the ATMS response plans shall be displayed,
selectable and configurable by an authorized user.
The ATMS software vendor must provide functional details of the
proposed software, documenting if the solution is an intelligent
engine generating statistically driven responses, and not solely a
protocol based response.
The ATMS software shall provide optional response plans for areas
that may not have predefined responses.
Incident Detection/Alarm Module/Vehicle Detectors
BR08
PR04
IR03
FDC01
FDC02
FDC03
PennDOT must be able to manage incident activities from detection
to resolution.
The ATMS software shall screen data transmitted from field sensor
devices to verify its accuracy. Should data fall outside of the
acceptable range, the ATMS software shall alert the user and log
the alarm.
Data received from external sources shall be available to the
operator to be integrated with traffic volume and speed data
collected from other PennDOT vehicle detection systems
The ATMS software shall have the ability to display the alarm nature
and location on a GIS based map application.
The ATMS software shall receive the current data transmission
from each vehicle detector at regular time intervals. The ATMS
software shall also receive vehicle probe data (i.e. INRIX) and other
traffic data sources as they become available.
The ATMS software shall maintain ranges of average traffic speed
to indicate four (4) levels of traffic flow: Free Flowing, Slow,
Congested and no information.
FDC04
The ATMS software shall represent each vehicle detector as a link
on a GIS map which is color-coded to indicate the traffic flow.
FDC05
The ATMS software shall employ an algorithm to evaluate vehicle
detector data and determine the presence of a potential incident.
Appendix T Page 6 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
FDC06
Upon positive detection, the ATMS software shall activate an alarm
to alert the operator. Potential incidents shall remain in a separate
list and will not be assigned as an incident until after positive
confirmation by an operator.
FDC07
When a potential incident notification is triggered, several selectable
user actions within the ATMS software shall be activated including
aiming the nearest CCTV camera in the direction of the sensor that
signaled the incident or moving video of the nearest camera onto
the video wall. The ATMS software shall provide a mechanism to
turn these features on or off.
FDC08
FDC09
FDC10
Comments
The ATMS software solution vehicle data shall include volume,
speed, classification and occupancy, depending on the capabilities
of the source element.
The ATMS software shall integrate the data from all sources listed
under interface requirements to compute and display current traffic
conditions.
The ATMS software shall compare the real-time traffic speed to the
historic average traffic speed for that time of day, day of week, day
of month, holidays and special events.
HMI - Regional Operations Requirements
Appendix T Page 7 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
HR01
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
At a minimum the following data elements shall be separate layers
on the ATMS software user map interface:
- State Routes,
- Local Routes,
- Road Classification,
- Equipment Status,
- Active RCRS Events selectable by event status as unique layers,
- Planned Events,
- Each equipment type shall have a separate layer,
- PennDOT Snow Routes
- 511 Routes
- Road Condition reporting emergency routes
Each layer can be turned on or off by the operator.
HR02
HR03
HR04
The ATMS software map shall have icons positioned to indicate the
location of each field device. The device icons should look like the
respective devices as per PennDOT preference, or another visual
differentiation approved by PennDOT.
The ATMS software shall provide an interface for the user to list
inventory of all available field devices. User can filter the list based
on the device type, sub-type or corridor.
The ATMS software shall allow a user to activate control of a device
by selecting it on the user interface. The complete device details
shall also be displayed.
Appendix T Page 8 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
The ATMS software shall provide four equipment status types:
standby (outlined in green), active (solid green), warning (solid
yellow), and out of service (solid red).
HR05
Standby = device is functioning by not currently being used
Active = device is operating normally
Warning = device is usable but has limited functionality and will
require TMC staff field investigation and possibly maintenance
contractor response. (a CCTV with video up but
no zoom or pan/tilt functions; a DMS with a pixel error)
Out of Service = device is currently off-line, not usable and has a
plan/needs a plan in place for resolving the issue
HR06
The ATMS software shall allow the operators to configure the color
of incident and device icons.
HR07
The ATMS software shall display the active incident information,
CCTV snapshots and DMS and HAR messages by hovering over a
device or displaying all active DMS, HAR and CCTV.
HR08
HR09
HR10
HR11
HR12
The ATMS software map shall provide an optional layer based on
the standard PennDOT type 10 map which can be turned on or off
by the operator.
The roadway network shown on the ATMS software map shall be
based on PennDOTs roadway management system (RMS) used for
all PennDOT Geographical Information System (GIS) applications
(ie. RCRS roadway network).
The ATMS software map shall be based on Geographical
Information System (GIS) Technology. The map shall include mile
markers and exit numbers/names as a selectable layer.
The ATMS software shall facilitate displaying information from
connected systems. For example, the APRAS system will allow the
user to view roadway limitations like capacity (weight and height
restrictions).
The ATMS software shall support dynamic scaling of all objects
(menus, text etc.) on Web page based on the screen resolution.
The target is 1024 x 768.
Appendix T Page 9 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
HR13
The ATMS software shall provide a method for taking control /
handoffs all TMCs equipment (DMS, CCTV & HAR) and open
incidents / events. For example, the ATMS shall allow the handoff
of one, multiple or all cameras in a District to another District. In
addition, the ATMS software shall support the transfer of all TMC
functions to another TMC.
HR14
The ATMS software shall display all active incidents (RCRS data)
on the map. The ATMS software shall generate alerts of upcoming
planned events that have been entered into the RCRS system.
HR15
HR16
HR18
Comments
The ATMS software screens shall display the login name of the
user who is currently logged into the system.
The ATMS software shall display and provide access to Orthophotography.
Using data from vehicle detector and vehicle probe data sources,
the ATMS software shall display traffic speeds based on defined
thresholds. The speeds shall be displayed in various colors based
on the defined thresholds (i.e., green, yellow, red).
Administration
BR09
PennDOT must have the ability to administer and maintain the
system. This includes adding new devices, troubleshooting the
system, system backups, archiving data, purging data, and user
and user group maintenance.
FEA02
The ATMS software solution shall provide a complete Web GUI for
administration with online help. Agency administrators can then
manage all aspects of the solution from their Web browsers.
FEA03
FEA04
The ATMS software shall allow Administrators to add or edit field
devices’ information in the system and the ATMS software map via
the user interface.
The ATMS software shall provide the ability to adjust system
parameters, which include but are not limited to Traffic (including
travel time) thresholds that triggers incident detection, geographic
boundary of incidents, incident types.
Appendix T Page 10 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
PR01
PR02
PR03
PR05
PR06
PR07
PR08
PR09
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
Real-time is defined as data that is no more than 5 seconds old
from the time that the ATMS solution receives the data. The ATMS
software shall display data in real-time.
The ATMS software shall support display of streaming video at 21
to 150 kilobits/second.
The ATMS software shall process and display ITS field device
status in real-time.
The ATMS software shall be capable of polling (i.e. issuing a
remote request for information) the current status of any ITS field
device. The time from when an ITS device issues the response to
the ATMS displaying that information on the user's workstation shall
be less than 5 seconds.
The ATMS software shall be able to receive an unsolicited
communication from any device containing notification of a
malfunction involving that device. (i.e. SNMP trap from DMS)
The ATMS software shall process detection data in real-time,
providing roadway congestion information for data distribution.
The ATMS software shall be designed and configured to support a
continuous operation. Continuous is defined as to support a 24
hours a day, 7 days a week, 365 days a year. There shall be no
scheduled downtime.
The ATMS software shall be capable of maintaining the
performance level described with following number of devices:
- 2,000 CCTV
- 2,000 DMS
- 2,000 Vehicle detector stations
- 600 Ramp Meters
- 6,500 Signal Systems (covering over 13,000 signals)
(Numbers reflect no less than 100% growth over the next 5 years
from the current installed base.)
PR10
The ATMS software map will display updates in less than 1 second
to user commands (regardless of the zoom, pan, etc.).
PR11
The ATMS software should not create additional lag time to sending
or receiving data from the field devices (i.e. CCTV and DMS).
Appendix T Page 11 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
PR12
PR13
PR14
Comments
The ATMS software shall be capable of receiving communication
and issuing commands to all field devices in the system, regardless
of device manufacturer.
The ATMS software solution must not be taken offline during
scheduled maintenance and must be designed as a redundant
system that can have upgrades, OS changes, etc. implemented first
on one portion of the platform and then the other, without the
application going offline.
The ATMS software solution must not undergo non-critical
maintenance during a major winter event or traffic management
incident. A documented process for obtaining PennDOT clearance
to perform non-critical maintenance prior to start must be provided
by the Contractor.
PR16
The ATMS shall be designed and configured to work with the
Systems Center Operations Manager (SCOM) to monitor system
performance. Examples of monitoring include but are not limited to:
CCTV camera feed connectivity, ATMS specific Windows
service(s), DMS connectivity, log file(s) and any other piece of
ATMS deemed essential to the continuous operation of ATMS.
IR09
The ATMS software shall provide the administrator with the ability to
make configuration changes to support equipment changes.
HR17
All routine administrative tasks shall be accomplished using the
ATMS software user interface (i.e., no direct manipulation of the
database, configuration files, etc). System administrative tasks
include, but are not limited to, the addition of new ITS devices
(where a device driver already exists) and user group configuration.
Asset Management
FEA01
The ATMS software shall provide users the capability to generate a
list of equipment and their status (e.g. successful or not successful)
and equipment health for a selected date or date range. This can
be user activated or scheduled, and must be confirmed by the user
Appendix T Page 12 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
FEA05
The ATMS software shall allow for monitoring and remote
diagnostics of field equipment - detect failures, issue problem
reports, and track the repair or replacement of the failed equipment.
FEA06
The ATMS software database shall at a minimum store the itemized
currently installed device inventory including name, manufacturer,
make, model, device age, location, installation date, etc.
FEA07
The ATMS software shall allow users to run reports on average
device life, devices under warranty, devices under contractor
maintenance period, etc.
FEA08
The ATMS software shall allow users to edit maintenance related
data fields to reflect real time change in maintenance service.
Comments
Data Warehouse
DR01
DR02
DR03
DR04
DR05
DR06
The ATMS software shall have a database in which collected data
and system activity is automatically tracked and recorded.
The ATMS software shall recognize and record in the activity log all
proprietary warnings, alarms, and status transmissions from each
device.
The ATMS shall support an industry standard relational database
management system (RDMS), unless proven that a proposed
proprietary database is robust enough and meets the actual
functionality as documented within these requirements.
The ATMS software shall support importing and exporting of system
data. For example, data can be exported to Excel.
The ATMS software shall store data collected in a relational
database that can be accessed and queried to develop custom
reports.
The ATMS software shall provide users the capability to export
edited vehicle classification data from detectors that are equipped
for vehicle detection. The edited vehicle classification data shall be
in the format specified in the Traffic Monitoring Guide (May 2001)
representing the 13 vehicle classifications recommended by the
FHWA.
Appendix T Page 13 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
DR07
DR08
DR09
DR10
DR11
DR12
DR13
DR14
DR15
DR16
DR17
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
The ATMS software shall record user entry and exits, and denial or
authorization of access to services. The ATMS shall log all user
activities.
Passwords, if stored within the ATMS software, are not in clear text,
but encrypted.
The ATMS software shall collect current and historical road
information from the sources listed in the interface section. This
information shall be used by the operator to more effectively
manage incidents and congestion.
The ATMS software shall allow for the collection and storage of
maintenance and construction information for use by operations
personnel or data archives in the region.
Error and log messages generated and stored by the ATMS
software solution are in clear plain text. For example, stored in a
human readable format and shall not use any cryptic information,
i.e. instead of “Error Code #N” state “Database Error”.
The ATMS software shall allow multiple people to work on the
application without adversely affecting one another. It provides the
ability to control who does what to a site by restricting capabilities
based on individual's roles.
The ATMS software shall have the ability to backup, purge and
restore the database and virtual system images in an automated
manner.
The ATMS software shall have the ability to store historical ITS
information for future analysis and reporting.
The ATMS software shall have multiple stages of archiving. A local
archive shall retain information for a user defined period of time, no
greater than 2 months. A permanent archive shall retain data in an
external network for a user-defined period of time.
The ATMS software shall use PennDOT authentication and as a
user store (CWOPA). The ATMS software shall utilize LDAP and/or
Siteminder for authentication.
The ATMS software solution shall be capable of transmitting
information, data and requests securely using 128 bit or 256 bit SSL
to department or external resources as required.
Appendix T Page 14 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
DR18
Comments
The ATMS software shall require a single user sign-on (support
LDAP) for the complete management of incidents and field devices.
Performance Measures
IR06
ER10
FIM03
PMR01
PMR02
PMR03
PMR04
PMR05
PMR06
Any user with proper privileges on the PennDOT network will have
access to complete functionality including the control of all
equipment and the ability to print any report from data in the ATMS
software.
The ATMS software shall log system and portlet activity including
detailed bandwidth usage reports.
The ATMS software congestion metric reporting shall be available
at the following levels: Segments, Interstate/Freeway/State Road,
Municipality, County, District, and Statewide.
The ATMS software shall support extensive reporting capabilities.
Sample reports have been assembled in Appendix B: Sample
Graphic Representations Of The Recommended Performance
Metrics.
Contractor shall provide an additional twelve (12) reports which will
be jointly designed with PennDOT as per the RFP requirements.
Contractor shall develop report mock ups showing data mapping,
logic and levels, (user authorization and drill down levels if
applicable), for each report.
The ATMS software shall provide the capability to filter data and
generate reports by selecting and prioritizing any combination of
data elements. For example, incident reports can be generated by
date, time of day, road, district, etc.
In addition to traffic related reports, the ATMS system shall be
capable of generating system health reports (i.e. communication
status, device status, equipment uptime).
The ATMS system shall track actions and record operator
information for all key events. These user logs shall be available to
system managers.
The ATMS system will also track automatic functions and errors
and store this information in event logs, which shall be accessible to
user.
Appendix T Page 15 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
Comments
The ATMS software must provide PennDOT with the ability to
PMR07 create custom reports using industry standard tools (i.e. Crystal
Reports or SQL Server Reporting Services.)
The ATMS software shall timestamp and store all equipment
PMR09 activations, communications, notifications and other actions taken at
all times.
The ATMS software logs must be stored in a human readable
PMR10 format and shall not use any cryptic information, i.e. instead of
“Error Code #N” state “Database Error”.
Contractor shall provide use of existing canned reports, including
PMR11
schedulable reports, if applicable.
Interfaces
IR01
The ATMS shall provide the ability to share data communicated
from ITS field devices with other PennDOT software systems that
require such data for purposes of congestion management, incident
management, asset management, emergency management, or
other valid applications. This data includes current / historic data
and operational status of all devices.
IR02
The import/export feature shall accept/transmit data in a traffic
management data dictionary (TMDD) compliant format, or some
other open standard which must meet PennDOT approval.
IR03
IR04
IR05
Data received from external sources shall be available to the
operator to be integrated with traffic volume and speed data
collected from other PennDOT vehicle detection systems.
Individual steps in a response plan shall have the ability to access
pre-planned route data from RCRS, and potentially other data
systems, to provide information or instruction to the operator. Preplanned routes will be imported for Phase 1.
RCRS will be the primary means to enter incident data. ATMS
software will display incident locations on map and suggest
response plans to operators based on incident location, duration
and severity.
Appendix T Page 16 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
IR07
IR08
IR12
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
The ATMS software shall be able to receive all available status and
data from all capable field devices listed in the attached PennDOT
ITS Equipment Inventory (Appendix J of the RFP).
The data retrieved from the field device in response to a current
status request will comply with relevant NTCIP data definition and
format standards, to the extent that the device is capable.
The ATMS software shall receive status information (Active, Off, or
Error), at a minimum, from the following systems:
• Traffic Signal Systems (Districts 2-0 & 9-0)
• Truck Roll Over System (District 12-0)
• Truck Runaway System (District 9-0)
• Low Visibility (District 9-0)
• High Winds Detection System (District 9-0)
• HOV / Gate Control (District 11-0)
The ATMS software will allow for one-way communication with
these systems. The ATMS software will receive basic alerts and
monitoring information that will be displayed on the ATMS software
map.
Appendix T Page 17 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
IR15
IR16
IR19
Comments
The ATMS software shall allow for future integration of any or all of
the following systems:
• APRAS (Automated Permit Routing/ Analysis System)
• ATR
• Bluetooth Travel Time
• CAD – 911 (Computer Aided Dispatch)
• IDRum (Interactive Detour Route and Mapping)
• RIMIS (Regional Integrated Multimodal Information Sharing)
• STIP (Standalone Count Station)
• WIM (Weight in Motion)
• I-83 Queue Detection System
• Emergency Pre-emption
• CAVC (Continuous Automated Vehicle Classification)
• Ramp Meters
• MDSS (Maintenance Decision Support System)
• RWIS (Roadway Weather Information System)
• AVL (Automatic Vehicle Location)
• Pump Station Monitoring System
• Anti-Icing System
• Crash Avoidance System
The ATMS software shall be capable of sending messages via
pagers, phones and e-mail.
The system will interface with CA SiteMinder tool suite to leverage
CWOPA credentials for user authentication, authorization and user
administration.
RCRS Interface
IR14
The ATMS software shall receive pre-planned route data from
RCRS. The ATMS software shall display the detour information as
a layer on the Map.
Appendix T Page 18 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
Comments
INRIX/ Probe Data
IR11
The ATMS software shall be capable of receiving detector and
probe data from PennDOT’s real-time traffic detector partners (such
as INRIX and traffic.com). Where available, INRIX data will be the
primary source of vehicle probe data.
HOV Module
IR17
IR18
The ATMS software shall retain existing HOV module functionality.
Full control/viewing capabilities of all aspects of the existing HOV
module must be replaced or integrated into the Statewide ATMS
System. This includes, but is not limited to, opening/closing of the
gates, changing the HOV sign status, changing Lane Control Sign
status, and detecting wrong way vehicles.
(Note: currently HOV module communicates with the administration
and alarm subsystems in existing District 11 ATMS).
The ATMS software shall provide access to the HOV module from
all workstations at the RTMC (the module should be accessible
from the same workstations that access the new Statewide ATMS
solution).
Interface to 511
IR10
The ATMS software shall provide DMS information to the 511
system. DMS information shall include:
• DMS ID
• Message
• Message Activation Time
• Message Deactivation Time
• Message Priority Level
AVL Interface
Appendix T Page 19 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
ID
FAV01
FAV02
FAV03
Comments
The vehicle location data displayed on the ATMS software map
shall consist of, at a minimum, vehicle type, vehicle identifier, GPS
coordinates, and the time of day that the data was collected. Data
can be filtered by the ATMS operator based on vehicle type or
identifier.
The ATMS software shall allow Operators to view winter road
maintenance vehicles.
The ATMS software shall allow Operators to view Service Patrol
Vehicles.
FAV04
The ATMS software shall display vehicle location data real-time.
FAV05
The ATMS software shall not store historical vehicle location data
within the ATMS software database.
Traffic Signal Systems
FST01
FST02
FST03
FST04
FST05
The ATMS software shall allow operators to manage HOV lanes.
This includes remotely controlling traffic signal controllers to
implement traffic management strategies at signalized intersections
based on traffic conditions, incidents, emergency vehicle
preemptions, pedestrian crossings, etc.
The ATMS software shall allow Operators to view the status of
Traffic Signal Timing systems.
The ATMS software shall allow the user to select from a library of
pre-set timing plans from the signal software or return to normal
operation.
The ATMS software shall confirm that any commands specified by
the user have been properly accepted by the specified signal control
system.
Signal plans that are active in the ATMS software shall be
represented on the graphical user interface.
Appendix T Page 20 of 23
APPENDIX T
PENNDOT
REQUIREMENTS
/
PennDOT
Requirements /
Existing
Software Capabilities
Matrix MATRIX
VENDOR'SVendor's
EXISTING
SOFTWARE
CAPABILITIES
ID
FST06
Please refer to instructions sheet for guidance on filling out the matrix below.
Existing Software
Requirements
Capabilities*
Comments
The ATMS software shall support users’ management of signals
within at a minimum the following three (3) categories of
functionality:
1. Full Functionality (viewing and changing traffic signal timings)
2. Traffic Signal Monitoring (monitoring and viewing the operation to
ensure that the signal is operating correctly)
3. Adaptive Control (monitoring and viewing existing traffic signal
adaptive control software and algorithms)
Appendix T Page 21 of 23
APPENDIX U
Project Deliverables Schedule
Offerors must provide all delivery dates below in accordance with their proposed solution. Upon PennDOT acceptance and approval, the delivery
dates in this schedule will become the official Project Deliverables Scheduled Due Dates, by whichPennDOT will expect full completion of each
identified Task and any related subtasks. Liquidated damages will be enforced in accordance with Appendix B Paragraph 4.
Offerors will provide delivery dates based on the assumption that an executed Contract and Notice To Proceed are in place by December 1, 2011.
Upon mutual consent, PennDOT and the Selected Offeror may change any of the delivery dates below in accordance with Appendix C Paragraph
30, Changes.
Deliverables
A-1: ATMS Project Management Plan
B-1: Existing Conditions Reports
B-2: Business Requirements
B-3: Detailed Business System Design
C-1: User Interface Design
C-2: Detailed Software Design Document
C-3: Network Topology Report
D-1: Procurement Plan
D-2: Statewide Implementation Plan
D-3: Statewide Test Plan
D-4: Statewide Training Plan
D-5: Knowledge Transfer Plan
D-6: Software License for ATMS COTS Package
E-1: Eastern Region Pre-Implementation Planning
E-2: Eastern Region Implementation
E-3: Eastern Region Knowledge Transfer
F-1: Central Region Specific Element Design
F-2: Central Region Pre-Implementation Planning
F-3: Central Region Implementation
F-4: Central Region Knowledge Transfer
G-1: Western Region Specific Element Design
G-2: Western Region Pre-Implementation Planning
G-3: Western Region Implementation
G4: Western Region Knowledge Transfer
H-1: Standard Statewide ATMS Integration Specification Documents
H-2: Planned DMS Integration
H-3: Planned DMS Integration with Travel Time
H-4: Planned CCTV Camera Integration
H-5: Planned HAR Integration
H-6: Planned Radar / Microwave Vehicle Detector Integration
H-7: Planned Integration of Bluetooth Vehicle Detector Travel Time Links
H-8: Planned Integration of TRANSMIT Travel Time Links
H-9: Planned Video Detector Integration
I-1: User and Support Documentation
I-2: Software Deficiency (Bug) Tracking
I-3: Routine Maintenance and Support
I-4: Release Management (blended rate)
I-5: Escrow Agreement
I-6.1: Turnover Plan
I-6.2: Service Turnover
Delivery Date
Comments
Due no later than 15 days from NTP
Reports due no later than 60 days from NTP
Due no Later than 20 months from NTP
Due no Later than 30 months from NTP
Due no Later than 40 months from NTP
As Needed
As Needed
As Needed
As Needed
As Needed
As Needed
As Needed
As Needed
H-2 through H-9 shall be completed as necessary
throughout the contract term. As PennDOT and
the Sected Offeror identify devices that require
integration, a completion schedule for each
integration shall be mutually agreed to and
documented by letter signed by both parties.
APPENDIX V
DELIVERABLE REVIEW AND APPROVAL
PROCESS
DELIVERABLE REVIEW AND APPROVAL PROCESS
The term “deliverable” refers to any and all tasks as indicated on Appendix E, Cost Submittal.
Deliverables may include shop drawings, reports, samples, test reports, and other information
that may be required for quality control and as required by the Contract Documents.
All deliverables must be submitted and accepted on or before the scheduled deliverable date. All
deliverables must be error free with regard to spelling, grammar, source data and calculations.
Approval of deliverables shall not relieve the Contractor of responsibility for any errors or
omissions in such drawings, nor from responsibility for complying with the requirements of this
Contract.
For all written deliverables, the Contractor shall provide a high level outline of the proposed
contents of the deliverable to make sure the deliverable meets PennDOT expectations. The
outline shall be submitted to PennDOT Project Manager electronically via e-mail. PennDOT
reserves 5 working days to review each submitted outline. Upon review, the result shall be
provided in email indicating one of the following:
a.
“No Exceptions Taken”
With this indication, the Contractor can proceed with work.
b.
“Amend and Resubmit”
With this indication, the procedure shall be:
i. Make the changes noted on the marked return.
ii. Send revised outline to PennDOT Project Manager for review.
iii. Repeat revisions and submissions until marked “No Exception Taken.”
PennDOT will indicate whether the Contractor can proceed with work not
indicated for revision in the outline.
c.
“Rejected”
With this indication, the procedure shall be:
i. Review the outline in conjunction with the Contract Documents and transmit
new outline.
ii. Repeat resubmissions until marked “No Exceptions Taken”.
Do NOT proceed with any fabrication of the work indicated in the outline.
Some deliverables will require formal presentations to PennDOT staff. The Contractor shall plan
to conduct the presentations in a timely manner and allow PennDOT the time to adequately
review the deliverables before final approval, following such presentations. Please refer to
timeframes identified in the deliverable review process below.
The Contractor shall provide electronic versions of all documentation. Where appropriate, a table
of contents, an index, and keywords shall be available for information searching. PennDOT does
Appendix V Page-1 of 3
not require printed documentation except in a case where the Contractor requests and PennDOT
agrees to accept a printed rather than an electronic document.
All deliverables shall contain a cover sheet with the following information:
• The Company’s name;
• Contract number and description;
• Name and address of Contractor;
• Name of preparer of the document;
• Page number, sheet number of detail number and revision numbers;
• Description of deliverable; and
• Signature by Contractor certifying the deliverable was reviewed.
All deliverables shall be numbered sequentially with the Contractor maintaining responsibility
for a deliverable log.
The deliverable submission and review process will consist of the following steps:
•
The Contractor will submit all written deliverables through email whenever possible. For
deliverables that are not written documents, an email indicating the deliverable is
complete will be required. The email shall contain all information as outlined in the
cover sheet above. PennDOT may request hardcopy of the deliverable upon receipt of
the electronic version. The Contractor is responsible to ensure PennDOT has received
the deliverable notifications.
•
PennDOT reserves 15 working days to review each submitted deliverable. Upon review,
the result shall be provided in email indicating one of the following:
d.
“No Exceptions Taken”
With this indication, the Contractor can proceed with work.
e.
“Amend and Resubmit”
With this indication, the procedure shall be:
iv. Make the changes noted on the marked return.
v. Send revised deliverable to PennDOT for review in accordance with initial
submission procedures.
vi. Repeat revisions and submissions until marked “No Exception Taken.”
PennDOT will indicate whether the Contractor can proceed with work not
indicated for revision in the deliverable.
Appendix V Page-2 of 3
f.
“Rejected”
With this indication, the procedure shall be:
iii. Review the deliverable in conjunction with the Contract Documents and
transmit new deliverables.
iv. Repeat resubmissions until marked “No Exceptions Taken”.
Do NOT proceed with any fabrication of the work indicated in the deliverable.
The review of deliverables by PennDOT is for general conformance with the design
concept and Contract Documents. Markings or comments shall not be construed as
relieving the Contractor from compliance with the Contract Documents, nor departures
there from. The Contractor remains responsible for complying with the requirements of
the Contract, for details and accuracy, and completing the work in a timely manner.
Appendix V Page-3 of 3
APPENDIX X
TRACEABILITY MATRIX
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Scenario 52
Scenario 51
Scenario 50
Scenario 48
Scenario 47
Scenario 46
Scenario 45
Scenario 44
Scenario 43
Scenario 42
Scenario 40
Scenario 39
Scenario 38
Scenario 37
Scenario 36
Scenario 35
Scenario 34
Scenario 33
Scenario 32
Scenario 31
Scenario 30
Scenario 28
Scenario 27
Scenario 26
Scenario 25
Scenario 24
Scenario 23
Scenario 21
Scenario 20
Scenario 19
Scenario 18
Scenario 16
Scenario 15
Scenario 13
Scenario 12
Scenario 11
Scenario 10
Scenario 9
Scenario 8
Scenario 7
Scenario 6
Scenario 5
Scenario 4
Scenario 3
Scenario 29
AD 1
AD 2
ATIS 1
ATIS 2
ATMS 1
ATMS 2
ATMS 3
ATMS 4
ATMS 5
ATMS 6
ATMS 7
ATMS 8
ATMS 9
ATMS 18
ATMS 19
ATMS 21
AVSS 10
CVO 6
EM 4
EM 5
EM 6
EM 9
EM 10
MC 1
MC 2
MC 3
MC 4
MC 5
MC 6
MC 7
MC 8
MC 10
BR01
BR02
BR03
BR04
BR05
Scenario 2
Scenario 1
APPENDIX X - TRACEABILITY MATRIX
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Appendix X
Page 1 of 2
Scenario 3
Scenario 4
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Scenario 52
Scenario 51
Scenario 50
Scenario 48
Scenario 47
Scenario 46
Scenario 45
Scenario 44
Scenario 43
Scenario 42
Scenario 40
Scenario 39
Scenario 38
Scenario 37
Scenario 36
Scenario 35
Scenario 34
Scenario 33
Scenario 32
Scenario 31
Scenario 30
Scenario 29
Scenario 28
Scenario 27
Scenario 26
Scenario 25
Scenario 24
Scenario 23
Scenario 21
Scenario 20
Scenario 19
Scenario 18
Scenario 16
Scenario 15
Scenario 13
Scenario 12
Scenario 11
Scenario 10
Scenario 9
Scenario 8
Scenario 7
Scenario 6
Scenario 5
Scenario 2
BR06
BR07
BR08
BR09
BR10
BR11
BR12
BR13
BR14
BR15
BR16
BR17
BR18
BR19
BR20
BR21
BR22
Scenario 1
APPENDIX X - TRACEABILITY MATRIX
X
X
X
X
X
Appendix X
Page 2 of 2
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Scenario 52
Scenario 51
Scenario 50
Scenario 48
Scenario 47
Scenario 46
Scenario 45
Scenario 44
Scenario 43
Scenario 42
Scenario 40
Scenario 39
Scenario 38
Scenario 37
Scenario 36
Scenario 35
Scenario 34
Scenario 33
Scenario 32
Scenario 31
Scenario 30
Scenario 29
Scenario 28
Scenario 27
Scenario 26
Scenario 25
Scenario 24
Scenario 23
Scenario 21
Scenario 20
Scenario 19
Scenario 18
Scenario 16
Scenario 15
Scenario 13
Scenario 12
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Scenario 11
X
X
X
Scenario 10
X
Scenario 9
Scenario 8
Scenario 6
Scenario 5
Scenario 4
Scenario 3
Scenario 7
BR01
BR02
BR03
BR04
BR05
BR06
BR07
BR08
BR09
BR10
BR11
BR12
BR13
BR14
BR15
BR16
BR17
BR18
BR19
BR20
BR21
BR22
Scenario 2
Scenario 1
APPENDIX - X TRACEABILITY MATRIX
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
7
X
X
X
X
7
X
X
X
X
7
X
X
X
X
7
X
X
X
X
6
X
X
X
X
5
X
X
X
X
X
X
8
X
X
X
X
X
X
11
X
X
X
X
7
X
X
X
X
X
X
7
X
X
X
X
X
X
X
15
X
X
X
X
X
X
8
X
X
X
X
X
X
7
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
9
X
X
X
X
12
X
X
X
X
6
X
X
X
X
7
X
X
X
X
8
X
X
X
X
11
X
X
X
X
6
X
X X
X X
X X
X X
X X
X X
12 10
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
5
X
X
X
X
9
X
X
X
X
9
X
X
X
X
5
X
X
X
X
5
X
X
X
X
5
X
X
X
X
5
X
X
X
X
7
X
X
X
X
5
X
X
X
X
5
X
X
X
X
6
X
X
X
X
6
X
X
X
X
7
X
X
X
X
6
X
X
X
X
5
X
X
X
X
8
X
X
X
X
X
X
X
X
X
9
X
X
X
X
8
X
X
X
X
X
X
6
X
X
X
X
X
X
X
X
5
X
X
X
X
6
X
X
X
X
5
X
X
X
X
5
X
X
X
X
X
X
8
X
X
X
X
X
X
8
X
X
X
X
1
6
9
10
7
5
6
10
4
3
11
5
9
2
2
6
47
10
47
47
47
47
PennDOT Statewide ATMS Software Functional Requirements, Appendix X
Page 1
APPENDIX Y
INTERFACE DESCRIPTIONS
APPENDIX Y – Interface Descriptions
Road Closure Reporting System
The Road Condition Reporting System (RCRS) tracks the conditions of roads throughout the
Commonwealth and soon will also contain PennDOT’s pre-planned detour route information.
The incident and condition information within RCRS are to be interfaced/integrated as part of
the Next Gen Advanced Traffic Management System (ATMS). In addition, operators must
have the ability to access RCRS directly from their Next Gen ATMS application to update
RCRS data.
Vehicle Probe Data
PennDOT is currently using INRIX for real-time traffic data, traffic flow information, and travel
times for key routes on nearly 800 miles of Pennsylvania roadways in the Harrisburg, Scranton,
Allentown, Pittsburgh, and Philadelphia metropolitan areas available at www.511pa.com.
The INRIX data, including traffic data, traffic flow information, and travel times will be
interfaced/integrated with the Next Gen ATMS application.
Regional Integrated Multi-Modal Information Sharing
Regional Integrated Multi-Modal Information Sharing (RIMIS) Project is a web based
information exchange network connecting highway operation centers, transit control centers, and
911 call centers in the Delaware Valley. RIMIS will enable agencies to receive messages about
incidents, construction and maintenance activity, and special events that impact highways and
transit. Further information is available from the Delaware Valley Regional Planning
Commission and their website at: http://www.dvrpc.org/Operations/RIMIS.htm.
An interface with RIMIS will be developed through the Next Gen ATMS application to share
traffic data and incident information with key PennDOT partners in Southeastern
Pennsylvania.
District 11-0 High Occupancy Vehicle (HOV) Module
The District 11-0 HOV runs along the I-279 just north of the City of Pittsburgh. The opening
and closing of the HOV is facilitated in conjunction with the Western Regional Traffic
Management Center (WRTMC) and the 11-0 Tunnel Maintainers. Full control for opening and
closing of the HOV is maintained with the existing District 11-0 ATMS software.
Full control/viewing capabilities of all aspects of the existing HOV module must be replaced
or integrated into the Next Gen ATMS. The TMC Operations staff must maintain full control
of all functionality that exists within the WRTMC. This includes, but is not limited to,
opening/closing of the gates, changing the HOV sign status, changing Lane Control Sign
status, and detecting wrong way vehicles.
I-83 Queue Detection System
The Queue Detection System is an Automated Real-time Messaging System (I-83 ARMS) built
off of Transdyn’s software. Using three side fire radar vehicle detectors (RVD), this system can
detect when there is slow or stopped traffic along a two mile stretch of Interstate 83 NB prior to
Appendix Y
Page 1 of 2
the PA 581 split. The software can post configured messages based on the RVD speed readings
on two message boards to warn motorists of current traffic conditions approaching the split. The
system also stores speed and count data for three months and can be downloaded to an excel
spreadsheet. One of the most important features is the alarms that the system will generate when
there is a change in traffic conditions. Even though the system is automated, the alarms prompt
the operator to look for accidents or other issues that may need to be addressed to clear the lanes
and get traffic flowing again.
An interface with I-83 Queue Detection System will need to be developed through the Next
Gen ATMS application to continue to utilize I-83 Queue Detection System functionality and to
incorporate the data and alarms from this system into Next Gen ATMS.
Appendix Y
Page 2 of 2
APPENDIX Z
ATMS RCRS SYSTEM
REQUIREMENTS DOCUMENT
Information Systems Governance
Appendix Z
Next Gen ATMS RCRS Requirements
System Requirements Specification
Version V2.03
BAS Work Order 8, Task 3
Deliverable ID 3.1.4.3
ATMS RCRS System Requirements Document
Appendix Z
Page 1 of 21
Revision History
Below is a document history log which includes each change that was made to this document, which team member
made the change, and the date of the change. The first final version of the document is version 1.0. Subsequent
updates to the document will be numbered v1.1, v1.2, v1.3, etc. Any significant changes (i.e. the addition of a new
section or the removal of an existing section) will be numbered v2.0, v3.0, etc.
Date
Version
08/09/2010
.01
Description
Initial draft submitted to PEMT for review
and comment
08/23/2010
1.0
Approved Initial Version
08/24/2010
2.01
08/31/2010
2.02
11/30/2010
2.03
PEMT Approved System Requirements
Included additional mapping of RCRS
System Requirements to RCRS Business
Requirements
Removed references to EDRS. Added
detour route requirements. Aligned
Appendix B with revised ATMS
requirements.
Author
Bob Schroeder
(Business Analyst)
Bob Schroeder
(Business Analyst)
Bob Schroeder
(Business Analyst)
Bob Schroeder
(Business Analyst)
Michael Pack (Business
Lead)
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
Table of Contents
1.
2.
3.
Introduction
4
1.1
1.2
1.3
1.4
1.5
4
4
4
4
5
Purpose
Scope
Acronyms, and Abbreviations
References
Overview
Overall Description
5
2.1
2.2
5
5
Constraints
Assumptions
Requirements
3.1
3.2
3.3
3.4
3.5
6
HIGH LEVEL BUSINESS REQUIREMENTS
3.1.1 Detail Level Business Requirements
SYSTEM REQUIREMENTS
3.2.1 Performance Requirements
3.2.2 Interface Requirements
3.2.3 Data Requirements
3.2.4 Reporting Requirements
3.2.5 Security Requirements
3.2.6 Hardware Requirements
3.2.7 Software Requirements
Licensing Requirements
Legal, Copyright, and Other Notices
Applicable Standards
6
7
8
8
9
12
12
13
13
14
14
14
14
4.
Supporting Information
14
5.
Detailed Change Tracking Log
15
APPENDIX A: ACRONYMS
16
APPENDIX B: Related ATMS Requirements
18
APPENDIX C: Sample RCRS Inquiry Screen
19
APPENDIX D: Basic Incident Timeline
20
Appendix Z
Page 3 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
Business and System Requirements Specification
1. Introduction
The Road Condition Reporting System (RCRS) tracks the conditions of roads throughout the
Commonwealth. The event, condition, and detour information within RCRS are to be
interfaced/integrated as part of the Next Gen Advanced Traffic Management System (ATMS). In addition,
Next Gen ATMS operators must have the ability to access RCRS directly from their Next Gen ATMS
workstation and update RCRS data.
1.1 Purpose
The purpose of version 2.01 of this document is to document the System Requirements for the
integration of the Pennsylvania Department of Transportation (PennDOT) Road Condition Reporting
System (RCRS) with the Next Gen Statewide Advanced Traffic Management System (ATMS) Software.
The Stakeholders have identified that the Road Condition Reporting System (RCRS) must be integrated
into the Next Gen Advanced Traffic Management System (ATMS) Software. The purpose of this
document is to document the system requirements to accomplish the business needs driving this
integration. System requirements contained in this document will also serve as a guide for future
verification and testing.
1.2 Scope
The ATMS software will enable operators to more efficiently manage surface transportation while also
providing a more effective response to incidents. The RCRS software will be a primary source of traffic
events to be input into the ATMS software.
The scope of this document is to define the business and system requirements needed to support the
interaction between the RCRS and ATMS software. The business and system requirements in this
document will be used to further define business and system requirements for the Next Gen ATMS RFP.
1.3 Acronyms, and Abbreviations
A list of appropriate Acronyms and abbreviations can be found in Appendix A of this document.
1.4 References
Next Gen ATMS SYSTEM REQS REV5.0
PennDOT 062310 FINAL
http://www.portal.state.pa.us/portal/server.pt/gateway/
PTARGS_32_0_232_0_1_47/http;/collaboration.state.pa.us;11930/collab/do/do
cument/overview?projID=284729&documentID=348284
Next gen ATMS RCRS Requirements Scope
Brainstorming – Responses
http://www.portal.state.pa.us/portal/server.pt/gateway/
PTARGS_32_0_232_0_1_47/http;/collaboration.state.pa.us;11930/collab/do/do
cument/overview?projID=284729&documentID=355077
2010-07-09 ATMS RCRS Next Gen
Requirements Meeting Minutes
http://www.portal.state.pa.us/portal/server.pt/gateway/
PTARGS_32_0_232_0_1_47/http;/collaboration.state.pa.us;11930/collab/do/do
cument/overview?projID=284729&documentID=362685
2010-07-15 ATMS RCRS Next Gen
http://www.portal.state.pa.us/portal/server.pt/gateway/
Appendix Z
Page 4 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
Requirements Meeting Minutes
PTARGS_32_0_232_0_1_47/http;/collaboration.state.pa.us;11930/collab/do/do
cument/overview?projID=284729&documentID=362686
RCRS Schema within the GIS Data
Dictionary Version 002.002.000
http://164.156.155.62/Data_Dictionary/main.htm
Next gen ATMS RCRS SR Interview
Document 2010-07-20 – Final
http://www.portal.state.pa.us/portal/server.pt/gateway/
PTARGS_32_0_232_0_1_47/http;/collaboration.state.pa.us;11930/collab/do/do
cument/overview?projID=284729&documentID=365547
High Level Incident Timeline
Appendix D.
1.5 Overview
This document is organized into the following sections:
•
•
•
Overall Description – high level description of how the requirements contained in this document are
presented. This section also includes the constraints and assumptions the business analyst operated
under while documenting the requirements.
Requirements – High level business and system requirements describing how the RCRS software will
interface with the ATMS software
Supporting Information - system documents, interview notes and manuals that assist in the creation
of this document.
2. Overall Description
The requirements contained in this document describe PennDOT’s needs as related to integrating the
Road Condition Reporting System (RCRS) functions with the Next Gen Advanced Traffic Management
System software (ATMS) to maximize existing software functionality. This should include:
•
•
•
•
•
Using the existing RCRS screens
Using the existing RCRS maps or create an ATMS map layer displaying RCRS event data as a layer
over the ATMS map
Administration of the RCRS software can be invoked from within the ATMS software
Access to the RCRS software is limited by the authorized security level of the ATMS operator
The business and system requirements are presented in a table layout with the following
columns:
o ID – Unique identifier for the requirement
o Title – Brief title of the requirement
o Requirement Description – Sentence describing what must be fulfilled in order to
achieve compliance
o Criticality/Importance – Indication of the necessity of the requirement
2.1 Constraints
This document will contain high level business and system requirements which will be used in the creation
of the Next Gen ATMS software.
2.2 Assumptions
This document has been created under the following assumptions:
•
•
•
Requirements are at a high level
PennDOT has provided all necessary resources to create complete requirements
Documents provided for reference are the latest version
Appendix Z
Page 5 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
•
Version:
V2.03
Date: 11/30/2010
Requirements statements were elicited and documented without funding, technical difficulty or
time constraints
3. Requirements
This document focuses on needs that were identified as fundamental to the implementation and initial
deployment of the Next Gen ATMS software. The business requirements contained in this document are
1
focused on the initial deployment (Phase I ) activities and are deemed necessary and were developed to
support specific requirements listed in the Next Gen ATMS Software Systems Requirements. A detailed
list of the Next Gen ATMS related requirements can be found in Appendix B. RCRS is considered the only
source of event data for the ATMS system, therefore, all the associated requirements have been
considered crucial with a high priority.
3.1 HIGH LEVEL BUSINESS REQUIREMENTS
Since the RCRS software is considered the only source of event data for the ATMS system, all the
associated requirements have been considered crucial with a high priority.
ID
TITLE
BUSINESS REQUIREMENT DESCRIPTION
The ATMS software shall have access to
the RCRS software 24 hours a day, 7 days
a week, and 365 days a year.
Criticality
and Priority
Crucial,
High
RCRS-BR01
Reliable
RCRS-BR02
Access
The ATMS software shall access RCRS
directly.
Crucial,
High
RCRS-BR03
Logon
The ATMS software shall provide an icon
(or menu selection) for the operator to
access the entire RCRS system based on
their RCRS authorization level.
Crucial,
High
RCRS-BR04
Display
The ATMS software shall display RCRS
data through the use of predefined and
approved icons.
Crucial,
High
RCRS-BR05
Data
Modification
The ATMS software shall allow the ATMS
operator to update RCRS events directly
if RCRS edit is selected from ATMS.
Crucial,
High
RCRS-BR06
Data Display
(Icon
Maintenance)
The ATMS software shall provide for easy
maintenance of the above icons to allow
for additional causes and statuses.
Crucial,
High
1
(Updated Phase/Rollout discussions and decisions for the ATMS Software are pending at this time.)
Appendix Z
Page 6 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
Version:
V2.03
Date: 11/30/2010
ATMS RCRS System Requirements Specification Document
3.1.1 Detail Level Business Requirements
This section defines the business terms relevant to the solution. Business terms should include definitions
of data elements important to the business whether they are provided on a form used by the business or
entered into a system, names of other organizations that are important to the business area, names of
systems and other equipment used by the staff, and other relevant terms.
REQ. ID
(from High
Level table)
BUSINESS TERM
ALL Business
Requirements
RCRS-BR03
ACRONYM OR
ABBREVIATION
DEFINITION
Acronyms and
Abbreviations
All Acronyms and abbreviations used within the
High Level Business Requirements are
Documented in Appendix A.
Operator
Primary handler who monitors real-time traffic
condition and status, and manages dispatch of
and communication with Service Patrol vehicles,
rd
main point of contact for traffic updates to 3
Parties
Incident
As defined by FHWAs traffic incident
management handbook, an Incident is “any nonrecurring event that causes a reduction of
roadway capacity or an abnormal increase in
demand.”
RCRS-BR05
Event
Any combination of cause and status options in
RCRS
RCRS-BR06
Cause
RCRS-BR06
Status
The reason initiating an event. RCRS has
predetermined causes for events.
The impact the event Cause has on the roadway
network. RCRS has predetermined status for
events.
RCRS-BR07
Detour
A route around a planned area of prohibited or
reduced access, such as a construction site or
road closure
Appendix Z
Page 7 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
3.2 SYSTEM REQUIREMENTS
3.2.1 Performance Requirements
The performance requirements include specific details about how well the ATMS software should
perform. For example, usability, system availability, and reliability are considered performance
requirements.
The following performance requirements are considered the minimum criteria that the ATMS software
must meet in order to sufficiently satisfy the needs of PennDOT:
ID
PERFORMANCE REQUIREMENT DESCRIPTION
Criticality
and Priority
BR
TITLE
RCRS-P01
RCRS-BR01
Availability
The ATMS software shall allow for the RCRS system to be
available 24/7 except when RCRS is unavailable for routine
daily refreshes and scheduled outages.
Crucial,
High
RCRS-P02
RCRS-BR01,
RCRS-BR05
Data Refresh
(Regular Cycle)
The ATMS software shall refresh data from RCRS every one
minute.
Crucial,
High
RCRS-P03
RCRS-BR01
Data Refresh
(After RCRS Update)
RCRS-P04
RCRS-BR01,
RCRS-BR02,
RCRS-BR04
Data Refresh
(Icon Updates)
RCRS-P05
RCRS-BR01,
RCRS-BR04
Data Capacity
RCRS-P05.1
RCRS-BR01,
RCRS-BR04
Data Capacity
(Total Events)
RCRS-P05.2
RCRS-BR01,
RCRS-BR04,
RCRS-BR05
Data Capacity
(Total Users)
RCRS-P05.3
RCRS-BR01,
RCRS-BR04,
RCRS-BR05
Data Capacity
(Concurrent Users)
The ATMS software shall refresh data from RCRS within 5
seconds after an ATMS operator has updated an event in
RCRS.
The ATMS software shall update the appropriate icons in
ATMS after RCRS is updated. This is to be done without
regenerating of the entire map.
The ATMS software shall have the capability to store in
excess of 500MB of DB storage for RCRS data with room for
expansion.
The ATMS software shall have the capacity to accommodate
at least 1800 RCRS events per day.
The ATMS software shall have the capacity to accommodate
at least 1800 RCRS administrative level users.
The ATMS software shall have the capacity to accommodate
at least 100 concurrent RCRS users.
Appendix Z
Page 8 of 20
Crucial,
High
Crucial,
High
Crucial,
High
Crucial,
High
Crucial,
High
Crucial,
High
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
+
3.2.2 Interface Requirements
The interface requirements detail how the Next Gen ATMS software should interact with the RCRS
system. The following interface requirements represent the minimum conditions that the ATMS software
must meet in order to sufficiently satisfy the needs of PennDOT:
ID
RCRS-I01
RCRS-I01.1
BR
TITLE
RCRS-BR04,
RCRS-BR06
Data Display
(Icons)
RCRS-BR04
Data Display
(Icon – Causes)
INTERFACE REQUIREMENT DESCRIPTION
The ATMS software shall display RCRS event data using easily
identifiable icons indicating RCRS cause and status.
The ATMS software shall use icons that reflect the cause of
each RCRS event.
Criticality
and Priority
Crucial,
High
Crucial,
High
The ATMS software shall provide icon(s) that can easily
identify the following causes by group with the ability to add
causes as needed:
RCRS-I01.11
RCRS-I01.2
RCRS-I01.21
RCRS-BR04,
RCRS-BR06
Data Display
(Icon – Cause list)
RCRS-BR04
Data Display
(Icon – Status)
RCRS-BR04,
RCRS-BR06
Data Display
(Icon – Cause list)
ACCIDENT
BRIDGE OUTAGE
BRIDGE PRECAUTION
DEBRIS ON ROADWAY
DISABLED VEHICLE
DOWNED TREE
DOWNED UTILITY
FLOODING
ACCIDENT(Multi-vehicle)–More than one vehicle
involved
OTHER
ROADWORK
SLOW VEHICLE
SPECIAL EVENT
VEHICLE FIRE
WINTER WEATHER
The ATMS software shall use icons that reflect the status of
each RCRS event.
The ATMS software shall provide icon(s) that can easily
identify the following statuses with the ability to add statuses
as needed:
CLOSED: All lanes closed
LANE RESTRICTION: One or more
lanes restricted
SHOULDER CLOSED:
Shoulder closed / lanes open
RAMP CLOSURE: Interstate/Traffic Route
RAMP RESTRICTION: Interstate/Traffic Route
SPEED RESTRICTION
COMMERCIAL VEHICLE RESTRICTION
TRAFFIC DISRUPTION
NO ENTRY ACCESS
Appendix Z
Page 9 of 20
Crucial,
High
Crucial,
High
Crucial,
High
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
ID
RCRS-I02
RCRS-I02.1
BR
RCRS-BR04,
RCRS-BR06
RCRS-BR04,
RCRS-BR06
RCRS-I02.2
RCRS-BR02,
RCRS-BR04
RCRS-I02.3
RCRS-BR04
RCRS-I02.31
RCRS-BR04
RCRS-I02.32
RCRS-BR04
RCRS-I02.33
RCRS-BR04
RCRS-I03
RCRS-BR02,
RCRS-BR05
RCRS-I03.1
RCRS-BR05
RCRS-I03.2
RCRS-BR05
TITLE
Data Display
Event Screen
(Icon - Hover)
Data Display
Event Screen
(RCRS Event Detail
Display Only)
Data Display
Event Screen
(RCRS Event Detail display only)
Data Display
Map Screen
(RCRS Event Detour display only)
Data Display
Map Screen
(RCRS Event Detour display only)
Data Display
Map Screen
(RCRS Event Detour display only)
Data Display
Map Screen
(RCRS Event Detour display only)
Data Update
Event Screen
(RCRS Event Detail
Update)
Data Update
Event Screen
(RCRS Event Detail
Update)
Data Update
Event Screen
(Prohibit)
Version:
V2.03
Date: 11/30/2010
INTERFACE REQUIREMENT DESCRIPTION
Criticality
and Priority
The ATMS software shall display basic event information
when the operator hovers the cursor over an event icon to
include at minimum the following data:
RCRS ID #
Route
Direction
County
Cause
Status
Event Beginning Date/Time
Expected Date/Time to Open
Event Contact Person
Event Contact Number
Crucial,
High
The ATMS software shall display event detail information
when the operator clicks on an event icon.
Crucial,
High
The ATMS software shall generate a screen that will display
the information shown on the RCRS screen in Appendix C.
Crucial,
High
The ATMS software shall have the capability of displaying all
preplanned detour routes stored in RCRS.
Crucial,
High
The ATMS software shall have the capability of displaying all
active Event Detours. The Detours may either be preplanned
or user defined for that particular event.
Crucial,
High
The ATMS user shall be able to toggle detour layers on or off.
Crucial,
High
The ATMS software shall display detours using the same
colors depicted in RCRS.
Crucial,
High
The ATMS software shall provide an edit button on the detail
screen to allow the operator to update the RCRS event
information in RCRS.
Crucial,
High
The ATMS software shall only provide RCRS edit capability if
the operator has update capability in RCRS.
Crucial,
High
The ATMS software shall not provide RCRS edit capability if
the operator does not have update capability in RCRS.
Crucial,
High
Appendix Z
Page 10 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
ID
RCRS-I03.3
RCRS-I03.4
RCRS-I03.5
Version:
V2.03
Date: 11/30/2010
TITLE
RCRS-BR05
Data Update
Event Screen
(RCRS Event Detail –
ATMS Update)
The ATMS software will return the operator to the ATMS
system after the RCRS event has been updated.
Crucial,
High
Data Update
Event Screen
(RCRS Event Detail –
ATMS Update)
The ATMS software shall pull updated event data from the
RCRS system in real-time after the event data has been
updated.
Crucial,
High
Data Update
Event Screen
(RCRS Event Detail –
ATMS Update)
The ATMS software shall pull and display to the operator an
appropriate Incident Response Plan (IRP) if one exists.
Crucial,
High
RCRS-BR01,
RCRC-BR02,
RCRS-BR04,
RCRS-BR05
RCRS-BR01,
RCRC-BR02,
RCRS-BR04,
RCRS-BR07
INTERFACE REQUIREMENT DESCRIPTION
Criticality
and Priority
BR
Appendix Z
Page 11 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
3.2.3 Data Requirements
Data requirements reflect how the data should be loaded, transferred, stored, secured and retrieved.
When available, the data requirements also identify data elements and define the system.
The following data requirements represent the minimum conditions that the Next Gen ATMS software
must meet in order to sufficiently support the Next Gen ATMS users’ use of the RCRS system.
ID
BR
RCRS-DR01
RCRS-DR01.1
RCRS-DR02
RCRS-BR01,
RCRS-BR02
RCRS-BR01,
RCRS-BR02,
RCRS-BR05
RCRS-BR01,
RCRS-BR02,
RCRS-BR07
TITLE
Data Pull
The ATMS software shall pull data from RCRS to ATMS only;
data transfer from ATMS to RCRS is not required.
Data Read Only
The ATMS software shall pull data from the RCRS system in
read mode only.
Data Retrieval
The ATMS software shall have the ability to retrieve data
stored in an Oracle data base.
RCRS-DR03
RCRS-BR01,
RCRS-BR05
Data Entry
RCRS-DR04
RCRS-BR01,
RCRS-BR05
Data Maintenance
RCRS-DR05
RCRS-BR04,
RCRS-BR07
DATA REQUIREMENT DESCRIPTION
Data Types
The ATMS software shall automatically navigate directly to
the appropriate RCRS event edit screen for data input if
event edit is selected from ATMS.
The ATMS software shall provide the ability to update RCRS
data by accessing the RCRS Event Edit screen.
The ATMS software shall have the capability to use the
results of the PennDOT Linear Line Referencing System.
Criticality
and Priority
Crucial,
High
Crucial,
High
Crucial,
High
Crucial,
High
Crucial,
High
Crucial,
High
3.2.4 Reporting Requirements
ID
RCRS-R01
BR
RCRS-BR01,
RCRS-BR02
TITLE
Report Storage
REPORTING REQUIREMENT DESCRIPTION
The ATMS software shall have the ability to store reports that
contain RCRS data that has been copied to the Next Gen
ATMS data base for future retrieval.
Appendix Z
Page 12 of 20
Criticality
and Priority
Crucial,
High
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
3.2.5 Security Requirements
ID
BR
TITLE
RCRS-S01
RCRS-BR01,
RCRS-BR03,
RCRS-BR05
Credential Validation
RCRS-S02
RCRS-BR01,
RCRS-BR03,
RCRS-BR05
RCRS-S03
RCRS-S03.1
RCRS-S03.2
RCRS-S03.3
RCRS-S03.4
RCRS-S04
RCRS-BR01,
RCRS-BR03,
RCRS-BR05
RCRS-BR01,
RCRS-BR03,
RCRS-BR05
RCRS-BR01,
RCRS-BR03,
RCRS-BR05
RCRS-BR01,
RCRS-BR03,
RCRS-BR05
RCRS-BR01,
RCRS-BR03,
RCRS-BR05
RCRS-BR02,
RCRS-BR03,
RCRS-BR05
SECURITY REQUIREMENT DESCRIPTION
Criticality
and Priority
The ATMS software shall allow logon credentials to be
validated by LDAP (Active Directory).
Crucial,
High
System Logon
The ATMS software shall be accessible through existing
CWOPA logons. A single CWOPA logon will validate access
credentials to both ATMS and RCRS with the appropriate
RCRS capabilities.
Crucial,
High
System Logon
(Standards)
The ATMS software shall follow all the established CWOPA
logon standards:
Crucial,
High
System Logon
(Password Format)
System Logon
(Password Attempts)
System Logon
(Password Expiration)
Session Timeouts
Logon Capability
Upper/lower case letters, numbers, symbols
Crucial,
High
5 Consecutive attempts
Crucial,
High
To coincide with Active Directory password
parameters
Crucial,
High
Pre-determined system time out
Crucial,
High
The ATMS software shall support the various levels of RCRS
administrative roles.
Crucial,
High
3.2.6 Hardware Requirements
ID
RCRS-HW01
RCRS-HW02
RCRS-HW03
BR
RCRS-BR01,
RCRS-BR02,
RCRS-BR03,
RCRS-BR04,
RCRS-BR07
RCRS-BR01,
RCRS-BR02,
RCRS-BR03,
RCRS-BR04,
RCRS-BR05
RCRS-BR01,
RCRS-BR02,
RCRS-BR03,
RCRS-BR04
TITLE
HARDWARE REQUIREMENT DESCRIPTION
Criticality
and Priority
Oracle Database
Server
The ATMS software shall have the ability to retrieve data
from an Oracle database Server.
Crucial,
High
Web Servers
The ATMS software shall have the ability to interact with the
PennDOT web server.
Crucial,
High
Clustered Servers
The ATMS software shall have the ability to interact with the
PennDOT clustered servers when needed.
Crucial,
High
Appendix Z
Page 13 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
Version:
V2.03
Date: 11/30/2010
ATMS RCRS System Requirements Specification Document
ID
BR
RCRS-HW04
RCRS-BR01,
RCRS-BR02,
RCRS-BR03,
RCRS-BR04,
RCRS-BR05
TITLE
Hardware Mirroring
HARDWARE REQUIREMENT DESCRIPTION
The ATMS software shall have the ability to support Oracle
RAC and Oracle Golden Gate.
Criticality
and Priority
Crucial,
High
3.2.7 Software Requirements
ID
RCRS-SW01
RCRS-SW02
RCRS-SW03
RCRS-SW04
BR
RCRS-BR01,
RCRS-BR02,
RCRS-BR03,
RCRS-BR04,
RCRS-BR05,
RCRS-BR06,
RCRS-BR07
RCRS-BR01,
RCRS-BR02,
RCRS-BR04
RCRS-BR01,
RCRS-BR02,
RCRS-BR04
RCRS-BR01,
RCRS-BR02,
RCRS-BR03,
RCRS-BR05,
RCRS-BR07
SOFTWARE
REQUIREMENT DESCRIPTION
TITLE
Criticality
and Priority
Web Browser
The ATMS software shall be compatible with the latest
version of Internet Explorer that can fully support all the
RCRS software operation. At the time of this publication that
version is IE6.
Crucial,
High
SVG Viewer
The ATMS software shall support SVG Viewer where required
for mapping purposes.
Crucial,
High
FLASH
The ATMS software shall support the FLASH software where
required for mapping purposes.
Crucial,
High
API
The ATMS software shall provide interfaces and APIs where
required to access the RCRS software.
Crucial,
High
3.3 Licensing Requirements
These will be handled in the Next Gen ATMS RFP.
3.4 Legal, Copyright, and Other Notices
These will be handled in the Next Gen ATMS RFP.
3.5 Applicable Standards
These will be handled in the Next Gen ATMS RFP.
4. Supporting Information
The following Documents may be helpful in understanding the RCRS function and the creation of this
document.
RCRS User’s Manual (Version 006.000.XXX)
rev04.02.10
P:\penndot shared\RCRS\RCRS User’s Manuals\RCRS user’s
Manual(Version 006.000.XXX) rev04.02.10.pdf
Statewide ATMS Software Concepts of
Operations, Rev.3
http://www.portal.state.pa.us/portal/server.pt/gateway/PTARG
S_32_0_232_0_1_47/http;/collaboration.state.pa.us;11930/collab/do/documen
t/overview?projID=284729&documentID=316247
Appendix Z
Page 14 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
5. Detailed Change Tracking Log
The chart below lists the specific changes that were made to the document beginning with Version 2.02.
The chart includes the change number, section and page in which the change was made, the date the
change was made, description of the change, and the version number of the document in which the
change was made.
#
SECTION
PG
CHANGE
DATE
CHANGE DESCRIPTION
VERSION
08/24/2010
PEMT Approved System Requirement Document
2.01
1
Performance
Requirements
8
08/31/2010
Added RCRS-BR05 to requirements:
RCRS-P02, RCRS-P05.2, RCRS-P05.3,
2.02
2
Data Requirements
11
08/31/2010
Added RCRS-BR07 to requirements:
RCRS-DR02, RCRS-DR05
2.02
3
Hardware
Requirements
12
08/31/2010
Added RCRS-BR07 to requirement RCRS-HW01
Added RCRS-BR05 to requirement RCRS-HW02
2.02
Appendix Z
Page 15 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
APPENDIX A: ACRONYMS
24x7
Twenty Four Hours of Operation, Seven Days a Week
AHS
Automated Highway System
ANSI
American National Standards Institute
ARMS
Automatic Real-Time Messaging
ATIS
Advanced Traveler Information System
ATMS
Advanced Traffic Management System
ATR
Automatic Traffic Recorders
AVL
Automatic Vehicle Location
BHSTE
Bureau of Highway Safety and Traffic Engineering
BOMO
Bureau of Maintenance and Operations
BPR
Bureau of Planning and Research
CBSP
Capital Beltway Service Patrol
CCTV
Closed Circuit Television
CDC
Consolidated Dispatch Centers
DARC
Data Radio Channel
DMS
Dynamic Message Signs
DOT
Department of Transportation
DSRC
Designated Short Range Communication
EMA
Emergency Management Agency
FHWA
Federal Highway Administration
GIS
Geographic Information System
GPS
Global Positioning System
HAR
Highway Advisory Radio
HAT
Highway Advisory Telephone System
HAZMAT
Hazardous Materials
HOV
High Occupancy Vehicle
IM
Incident Management
IIMS
Incident Information Management System
IMMS
Incident Management Message Sets
IRP
Incident Response Plan
ITS
Intelligent Transportation System
m.p.
Milepost
PEIRS
Pennsylvania Emergency Incident Reporting System
PEMA
Pennsylvania Emergency Management Agency
PennDOT
Pennsylvania Department of Transportation
PSP
Pennsylvania State Police
RTMC
Regional Traffic Management Center
RWIS
Road Weather Information System
Appendix Z
Page 16 of 20
Version:
V2.03
Date: 11/30/2010
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
TMC
Traffic Management Center
Appendix Z
Page 17 of 20
Version:
V2.03
Date: 11/30/2010
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
APPENDIX B: Related ATMS Requirements
Business Requirements
BR03
PennDOT needs to provide consistent and planned responses to planned and unplanned events
BR04
PennDOT needs a statewide platform which will provide the means for information to flow to and
from all Districts
Real-time Data
Maximize Existing Software
BR07
BR16
Performance Requirements
PR01
Real-time is defined as data that is no more than 5 seconds old from the time that an RCRS entry is
created. The ATMS software shall display data in real-time. (pull + display = 5 seconds)
Interface Requirements
IR04
IR05
IR14
Individual steps in a response plan shall have the ability to access pre-planned route data from
RCRS, and potentially other data systems, to provide information or instruction to the operator.
Pre-planned routes will be imported for Phase 1
RCRS will be the primary means to enter incident data. ATMS software will display incident
locations on map and suggest response plans to operators based on incident location, duration and
severity
The ATMS software shall receive pre-planned route data from RCRS. The ATMS software shall
display the detour information as a layer on the Map
HMI Requirements
HR14
The ATMS software shall display all active incidents (RCRS data) on the map. The ATMS software
shall generate alerts of upcoming planned events that have been entered into the RCRS system
Incident Management
FIM01
FIM04
FIM05
The ATMS software shall allow Administrators to utilize diversion routes from RCRS that are
location-based. Each route shall be color-coded based on the location and direction as defined by
PennDOT. By selecting links and/or roadways that will be used as a diversion route.
Where sufficient data is available, the ATMS software shall classify delay time according to current
RCRS nomenclature
The ATMS software shall display RCRS incident and condition information in the ATMS software
and on the ATMS Map
Response Plans
FRP11
The ATMS software actions available for use in a response plan shall include: activation of roadside
devices (i.e. - posting a predefined message to a DMS), Providing information or instruction to an
operator's screen (i.e. - instructing the operator to contact the State Police), activation of a
diversion route, sending an e-mail, fax, text message, or page, Issuing a command to the Road
Closure Reporting System to modify a road status, Generation of a pre-defined report
Appendix Z
Page 18 of 20
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
APPENDIX C: Sample RCRS Inquiry Screen
Appendix Z
Page 19 of 20
Version:
V2.03
Date: 11/30/2010
BAS Work Order 8 Task 3 Deliverable 3.1.4.3
ATMS RCRS System Requirements Specification Document
Version:
V2.03
Date: 11/30/2010
APPENDIX D: Basic Incident Timeline
The diagram below give a high level description of the flow of an incident through the current RCRS system. It is
intended to help understand the initiation, processing and termination of traffic events as they are currently
handled in the Commonwealth. Please keep in mind, this is a high level diagram and there is considerable
underlying detail that support these processes.
RCRS Basic Incident Flow
Incident
Occurs
TMC Operator Verifies incident:
• Visually from TMC Monitoring device
• Notification from a trusted source
TMC Operator verifies incident is closed
• Visually from TMC Monitoring device
• Notification from a trusted source
Incident
reported
Closed
INCIDENT TIMELINE
Operator Manages Incident:
• Enters incident into TMC log
• Enters incident into RCRS
• Checks IRP for ITS devices to activate
• Activates appropriate ITS devices
• Monitors activity and updates
systems as event changes until incident
closed
Incident detected / reported by:
•
•
•
•
•
•
•
•
•
PennDOT Personnel
PennDOT CCTV cameras
PSP trooper at scene
Other states
PSP Watch Center (email)
County 911
TMC Email Account
Media
Other
Appendix Z
Page 20 of 20
Operator closes Incident:
• Closes incident in RCRS
• Deactivates ITS devices
• Captures activity in TMC Log
• Closes incident
APPENDIX AA
FORM OS-501
CONFIRMATION OF SERVICES
OS-501 (3-10)
CONFIRMATION OF SERVICE
www.dot.state.pa.us
Date Service Rendered: ________________________________ Contractor Name:_ ____________________________________ Phone: _ ____________________________________________ PURCHASE ORDER #_________________________________ SAP Vendor Number: _ ________________________________
Address (1):_________________________________________ Address (2): _________________________________________
State:______________
Zip Code:_ ____________________ (Reference line items on purchase order that match the services that were performed.)
Item #
Description / Product ID
Contractor Signature:_________________________________ Quantity
U.O.M.
Unit Price
Item Total
$0.00
$0.00
$0.00
$0.00
$0.00
$0.00
Total:
$0.00
Date:_ _____________
PENNDOT USE ONLY
I certify the services represented by the confirmation of service form above were received satisfactorily. Therefore, I approve payment be made.
Project Manager Signature
Date (mm/dd/yyyy)
I certify that I have entered a Goods Receipt in SAP for this service. (Goods Receipts should be entered within 48 hours per Management
Directive 310.31)
SRM/R3 Receiver Signature
Date (mm/dd/yyyy)
APPENDIX N
PHASING PLAN
NEXT GEN ATMS PROPOSED PHASING
Proposed phasing:
Module/Item
DMS
Travel Time module
CCTV
HAR
RCRS Interface
Vehicle Probe data
Incident response plan
Incident detection/alarm module/vehicle detectors
Queue detection
HMI - Regional operations requirements
Administration
Asset Management
Data warehouse
Performance measures
HOV module
Interface to RIMIS (D6)
Ramp meter interface
Interface to 511
AVL Interface
Traffic signal systems
MDSS / RWIS Interface
Planned enhancements
PA Turnpike Commission Deployment
Phase 1:
D4, D5, D6, CO
Phase 2:
D2, D3, D8, D9
Phase 3:
D1, D10, D11, D12
x
x
x
x
x
x
x
x
x
x
x
x
Phase 4:
Planned
Enhancements
Phase 5:
PA Turnpike
Commission
Statewide data integrated in Phase 1
Statewide data integrated in Phase 1
x
x
x
x
x
x
x
x
Statewide map and access to available data in Phase 1
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Notes:
1. Modules/items are listed in no particular order.
2. The Next Generation ATMS system will be deployed statewide in Phases 1 through 3.
3. The Department reserves the right to request enhancements, currently identified as Phase 4, to be completed in earlier phases of this contract.
4. Specific tasks for Phase 5 will be established in accordance with Appendix B, Special Terms and Conditions, Paragraph 7, Additional Work
Next Gen ATMS RFP
Appendix N Page 1 of 1
* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project
advertisement
© 2021