`
A Joint Standard of AASHTO, ITE, and NEMA
NTCIP 1404:2000
v01.02
Transit Communications
Interface Profiles
part of the National Transportation
Communications for ITS Protocol
Standard on Scheduling /
Runcutting (SCH) Objects
December 1, 2000
Also referenced as TCIP-SCH
Published by
American Association of State Highway and Transportation Officials (AASHTO)
444 North Capitol Street, N.W., Suite 249
Washington, D.C. 20001
Institute of Transportation Engineers (ITE)
1099 14th Street, N.W., Suite 300 West
Washington, D.C. 20005-3438
National Electrical Manufacturers Association (NEMA)
1300 North 17th Street, Suite 1847
Rosslyn, Virginia 22209-3801

Copyright 2001 AASHTO / ITE / NEMA. All rights reserved.
 Copyright 2001 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of
Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights,
including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display
are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the
Berne Convention, and the International and Pan American Copyright Conventions. Except for the electronic data dictionary or
script, do not copy without written permission of either AASHTO, ITE, or NEMA.
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page i
ACKNOWLEDGEMENTS
This publication was prepared by the Institute of Transportation Engineers’ (ITE) TCIP Project Team, and
was reviewed and recommended by the Joint Committee on the NTCIP. The Joint Committee is
organized under a Memorandum of Understanding among the American Association of State Highway
and Transportation Officials (AASHTO), the ITE, and the National Electrical Manufacturers Association
(NEMA). The Joint Committee on the NTCIP consists of six representatives from each of the standards
organizations, and provides guidance for NTCIP development.
In February 1997, the TCIP Technical Working Group organized subgroups to standardize the business
area data interface objects. The TCIP TWG formed the Scheduling / Runcutting / Spatial Representation
Subgroup to standardize the Scheduling / Runcutting data interface objects, that resulted in this
document.
At the time this document was prepared, the following individuals were active members of the TCIP
Technical Working Group’s Scheduling / Runcutting Subgroup:
























Isaac K. Takyi, TCIP TWG Chair, New York City Transit Authority
Julie Corman, co-Chair; King County Metro (Seattle)
Dan Overgaard, co-Chair; King County Metro (Seattle)
Nancy Neuerburg; King County Metro (Seattle)
Bob Antonisse; Orbital Sciences Corporation
Paul Comeaux; VIA Metropolitan Transit (San Antonio)
Oscar Franzese; ORNL-Center for Transportation Analysis
Nigel Hamer; GIRO
Shirley Hsiao; Orange County Transportation Authority
Greg Lind; Southern Ohio Regional Transportation Authority
Peggy Morrow; Orbital Sciences Corporation
Jeff Martin; San Diego Association of Governments
Mark Miller; Trapeze Software, Inc.
Brad Nelson; Cubic Corporation (Automated Revenue Collection Group)
Jeff Orton; Utah Transit Authority
David Phillips; Chicago Transit Authority
Jim Sims; Southern California Association of Governments
Jim Sterling; GIS/Trans, Ltd.
Craig Telmer; Trapeze Software, Inc.
Byron Wilson; Utah Transit Authority
Carol Yates; TMS/E-Systems
Paula Okunief, TCIP Project Technical Manager; Cambridge Systematics & ARINC, Inc.
Karen Levine; Cambridge Systematics
Eva Lerner Lam, TCIP Project Director; Palisades Consulting Group, Inc.
In addition to the many volunteer efforts, recognition is also given to those organizations that supported
the efforts of the TCIP Technical Working Group and subgroups by providing comments and funding for
the document, including:


Federal Highway Administration
Federal Transit Administration
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page ii
FOREWORD
This document uses only metric units.
This document is an NTCIP Device Data Dictionary Standard. Device Data Dictionary Standards provide
definitions of data elements for use within NTCIP and TCIP systems.
The TCIP family of standards addresses Advanced Public Transportation Systems (APTS) data interfaces
and related automated transit tools and data. The standards also address the business requirements of
the APTS data interfaces. In some cases, specialized terms were needed to define general classes of
information. For example, different business areas needed to define data elements related to time, date
and footnotes. Special data types were developed so that these data concepts were consistent across
business areas, while specific needs were met. These data types are defined in this document.
For more information about NTCIP standards, visit the NTCIP Web site at http://www.ntcip.org. For a
hardcopy summary of NTCIP information, contact the NTCIP Coordinator at the address below.
In preparation of this NTCIP document, input of users and other interested parties was sought and
evaluated. Inquires, comments, and proposed or recommended revisions should be submitted to:
NTCIP Coordinator
National Electrical Manufacturers Association
1300 North 17th Street, Suite 1847
Rosslyn, Virginia 22209-3801
fax: (703) 841-3331
e-mail: ntcip@nema.org
Approvals
This document was separately balloted and approved by AASHTO, ITE, and NEMA after recommendation
by the Joint Committee on the NTCIP. Each organization has approved this standard, as the following
standard type, as of the date:
AASHTO – Standard Specification; July 1999
ITE – Software Standard; October 1999
NEMA – Suggested Standard for Future Design; February 2000
History
From 1997 to 1999, this document was referenced as ITE ST-ITS-TCIP-SCH and/or NEMA TS 3.TCIPSCH. However, to provide an organized numbering scheme for the NTCIP documents, this document is
now referenced as NTCIP 1404. The technical specification of NTCIP 1404 is identical to the former
reference, except as noted in the development history below:
TCIP draft specifications version 0.1. In September 1997, distributed for public review.
TCIP-SCH version 1.0, February 20, 1998. Accepted as a Recommended Standard. Changed to
version 1.1, July 31, 1998. Revisions included: former section numbers 2.1, 2.3, 4.3, 5.1, and
5.2.
NTCIP 1404 version 97.01.01, July 31, 1998. Approved by AASHTO in July 1999, approved by
ITE in October 1999, and approved by NEMA in February 2000.
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page iii
NTCIP 1404 v01.02, December 1, 2000. Prepared for printing: incremented version number and
updated date; added and revised front matter; updated references to NTCIP and NEMA document
numbers in References Clauses; updated references to ITE document numbers; revised section
numbering; inserted introduction text in Section on Requirements; deleted Annex A Comment
Form; and inserted introduction text in Annex on the ASN.1 Script.
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page iv
INTRODUCTION
The purpose of this document is to define the Scheduling/Runcutting objects that are supported by the
Transit Communications Interface Profiles (TCIP). TCIP serves as the “transit” component of the National
Transportation Communication for ITS Protocol effort.
There are two annexes to this document.
This document defines requirements that are applicable to all NTCIP and TCIP environments and also
contains optional and conditional clauses that are applicable to specific environments for which they are
intended.
The following keywords apply to this document: AASHTO, ITE, NEMA, NTCIP, TCIP, Scheduling,
Runcutting.
In 1992, the NEMA 3-TS Transportation Management Systems and Associated Control Devices Section
began the effort to develop the NTCIP. Under the guidance of the Federal Highway Administration’s
NTCIP Steering Group, the NEMA effort was expanded to include the development of communications
standards for all transportation field devices that could be used in an Intelligent Transportation Systems
(ITS) network.
In September 1996, an agreement was executed among AASHTO, ITE, and NEMA to jointly develop,
approve, and maintain the NTCIP standards.
In 1997, the ITE, in cooperation with the American Public Transit Association (APTA), the U.S. DOT’s
Federal Transit Administration, and the U.S. DOT’s FHWA, began development of the TCIP. The TCIP
Technical Working Group was accepted as a subdivision of the Joint Committee on the NTCIP.
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page v
If you are not willing to abide by the following distribution notice, return these materials immediately.
Joint AASHTO, ITE, and NEMA
NTCIP and TCIP Data Dictionary and ASN.1 Script
DISTRIBUTION NOTICE
To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of
a Data Dictionary and ASN.1 Script (“DD”), AASHTO / ITE / NEMA extends the following permissions:
(i) you may make and/or distribute unlimited copies (including derivative works) of the DD, including
copies for commercial distribution, provided that each copy you make and/or distribute contains this
Notice;
(ii) use of the DD is restricted in that the syntax field may be modified only to reflect a more restrictive
subrange or enumerated values;
(iii) the description field may be modified but only to the extent that: (a) only those bit values or
enumerated values that are supported are listed; and (b) the more restrictive subrange is expressed.
These materials are delivered “AS IS” without any warranties as to their use or performance.
AASHTO / ITE / NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR
RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO / ITE / NEMA AND THEIR
SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF
THIRD PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN
NO EVENT WILL AASHTO, ITE, OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY
THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL, OR SPECIAL
DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR
REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA
REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or
jurisdictions do not allow the exclusion or limitation of incidental, consequential, or special damages, or the
exclusion of implied warranties, so the above limitations may not apply to you.
Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or
NEMA and you, your company, or your products and services.
Disclaimer
The standards or guidelines presented in an NTCIP document are considered technically sound at the
time they are approved for publication. They are not a substitute for a product seller’s or user’s own
judgment with respect to the particular product discussed, and AASHTO, ITE, or NEMA does not
undertake to guaranty the performance of any individual manufacturer’s products by virtue of this standard
or guide. Thus, AASHTO, ITE, and NEMA expressly disclaim any responsibility for damages arising from
the use, application, or reliance by others on the information contained in these standards or guidelines by
others.
NTCIP is a trademark of AASHTO / ITE / NEMA.
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page vi
CONTENTS
SECTION 1 GENERAL .............................................................................................................................. 1-1
1.1
Scope.......................................................................................................................................... 1-1
1.2
References ................................................................................................................................. 1-1
1.2.1 Normative References........................................................................................................... 1-1
1.2.2 Informative References ......................................................................................................... 1-2
1.2.3 Contact Information ............................................................................................................... 1-2
SECTION 2 TERMINOLOGY..................................................................................................................... 2-1
2.1
Definitions ................................................................................................................................... 2-1
2.2
Abbreviations .............................................................................................................................. 2-2
2.3
Acronyms .................................................................................................................................... 2-2
SECTION 3 BASIC CONCEPTS ............................................................................................................... 3-1
3.1
Scheduling/Runcutting (SCH) Business Area Domain ............................................................... 3-1
3.2
Components and Data Flows ..................................................................................................... 3-1
3.2.1 Inputs ..................................................................................................................................... 3-1
3.2.2 Outputs .................................................................................................................................. 3-4
3.3
Classification Scheme ................................................................................................................ 3-6
3.3.1 National Architecture Classification Scheme......................................................................... 3-6
3.3.2 TCIP Classification Tree........................................................................................................ 3-6
3.4
Naming Conventions .................................................................................................................. 3-6
SECTION 4 REQUIREMENTS .................................................................................................................. 4-1
4.1
Scheduling/Runcutting Data Dictionary ...................................................................................... 4-1
4.2
Message Objects ...................................................................................................................... 4-66
SECTION 5 CONFORMANCE REQUIREMENTS..................................................................................... 5-1
5.1
Level One Conformance ............................................................................................................. 5-1
5.2
Level Two Conformance ............................................................................................................. 5-1
ANNEX A DATA ELEMENT/MESSAGE USE CROSS REFERENCE TABLE ..........................................A-1
ANNEX B ASN.1 SCRIPT INFORMATIVE ANNEX ...................................................................................B-1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 1-1
Section 1
GENERAL
1.1
SCOPE
The scheduling domain covers the data needs of the functions related to scheduling and runcutting. This
includes all input data needed to develop the master schedule, trip sheet, run guides, paddles, inventory
files, and other supplemental information. It also includes output data for several systems and information
services: transit garage management, control system, on-board, information/transit customer information
systems, incident and traffic management, paratransit, roadside devices and operating performance
history databases.
The scheduling/runcutting business area provides information on schedules and transit infrastructure to
the Information Service Provider (ISP), Traffic Management (TMC), Remote Traveler Support (RTS),
Intermodal Transportation Service Provider, Planning Subsystem (PS), Transit Vehicle Subsystem
(TRVS), and Other Transit Management System (Other TRM). It receives information from the TMC,
TRVS, Other TRM, Parking Management System (PMS), Intermodal Transportation Service Provider, and
PS.
1.2
REFERENCES
For approved amendments, contact:
NTCIP Coordinator
National Electrical Manufacturers Association
1300 North 17th Street, Suite 1847
Rosslyn, Virginia 22209-3801
fax: (703) 841-3331
e-mail: ntcip@nema.org
For draft revisions or amendments to this document, which may be under consideration by the relevant
TCIP Working Group, and for recommended amendments of the NTCIP Joint Committee, visit the World
Wide Web at http://www.ntcip.org or http://www.ite.org.
A copy of the database containing the TCIP data elements and messages for each of the business areas
is available. To download a copy of the TCIP database, follow the instructions on either the NTCIP or ITE
Websites.
Two types of references are cited in this section. Normative references contain provisions that apply
when implementing this standard. Informative references contain rules and guidelines that may provide a
more detailed understanding of the data, interface, format, profiles, or application of this standard. At the
time of publication, the editions indicated were valid. All standards are subject to revision, and parties to
agreements based on this standard are encouraged to investigate the possibility of applying the most
recent editions of the standard listed below.
1.2.1
Normative References
NTCIP 1400, formerly referenced as ST-ITS-TCIP-FRAME, Transit Communications Interface Profile
Framework, Institute of Transportation Engineers, Version 1.1, April 30, 1998.
NTCIP 1401, formerly referenced as ST-ITS-TCIP-CPT, Transit Communications Interface Profile
Standard on Common Public Transportation Objects, Version 1.1, Institute of Transportation Engineers,
July 31, 1998.
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 1-2
NTCIP 1405, formerly referenced as ST-ITS-TCIP-SP, Transit Communications Interface Profile Standard
on Spatial Representation (SP) Objects, Institute of Transportation Engineers, Version 1.1, July 31, 1998.
NTCIP 1407, formerly referenced as ST-ITS-TCIP-CC, Transit Communications Interface Profile,
Standard on Control Center Objects, Version 1.0, Institute of Transportation Engineers, September 1998.
ISO/IEC 8824:1994, Abstract Syntax Notation One (ASN.1), (ITU-T X.380-X.390, July 1994).
1.2.2
Informative References
Draft IEEE P1489/D0.0.7, Draft Standard for Data Dictionaries for Intelligent Transportation Systems,
Version 0.0.7, October 9, 1997.
Draft IEEE P1488/D0.0.6, Draft Standard for Message Set Template for Intelligent Transportation
Systems, Version 0.0.6, October 17, 1997
The National Architecture for ITS, U.S. Department of Transportation Joint Program Office, January 1997.
1.2.3
Contact Information
Members of the ISO maintain registers of currently valid ISO/IEC International Standards. For the USA,
the members of ISO are the American National Standards Institute (ANSI), which may be contacted at:
ANSI
11 West 42nd Street, 13th Floor
New York, New York 10036
(212) 642-4900
www.ansi.org
The Institute of Electronic and Electrical Engineers (IEEE) develops and maintains the IEEE Standard for
Data Dictionary and Message Set Template for Intelligent Transportation Systems. These draft standards
may be obtained from IEEE at:
Institute of Electronics and Electrical Engineers
445 Hoes Lane, P.O. Box 1331
Piscataway, NJ 08855-1331
(732) 981-0060
www.ieee.org/ieeestore
The Intelligent Transportation Society of America (ITSA) distributes documents developed by the U.S.
DOT Joint Program Office (JPO) on ITS. The National ITS Architecture may be obtained from ITSA at:
Intelligent Transportation Society of America
400 Virginia Avenue, S.W.
Suite 800
Washington, DC 20024-2730
(202) 484-4584
(800) 374-8472
www.itsa.org/public/archdocs/national.html
or from Odetics at:
www.odetics.com/itsarch/
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 2-1
Section 2
TERMINOLOGY
For the purposes of this document and to standardize the terminology in the transit industry, the following
definitions, abbreviations, acronyms, conventions, and notations used in this document apply to this
document.
2.1
DEFINITIONS
Stop Point
Block
Block Group
Driver Activation
Event
Master Schedule
Master Schedule Header
Operator Assignment
Organizational Unit
Pattern
Piece of Work
Public Transit Vehicle
Roster
Route
Run
Schedule Time
Time Point
Transfer Cluster
Trip
Trip Time Point
Vehicle Assignment
© 2001 AASHTO / ITE / NEMA
Description of a point where transit customers board or alight from a
transit vehicle in revenue service.
See Vehicle Assignment.
A grouping of blocks based on some common characteristics such as
use common corridor, terminus location, or route direction name.
A specific request for a driver to take an action. This request is a type of
event.
An action that is activated at a specified time, location, or both.
Examples of events include: announcements, changes to route and
schedule adherence requirements, changes to variable message signs,
request for a driver to take some action, notification of a change of a fare
or radio zone, and notification of a change in operator (relief driver).
A table that includes all the time points and trips on a route. Contained
within the route description is the Master Schedule Header information.
Sequence of time point identifiers and/or their names used to define the
order of time points for all the patterns. This field is used to build
timetables, for exterior signs, etc.
The daily pieces of work assigned to a transit employee.
A division or group within a transit agency, for example, Operations,
Communications, South Garage.
One of multiple outer route segments served by a single transit route.
A task or series of tasks that, when carried out, provide the basic
components or building blocks of transit service delivery.
Vehicles owned, leased, or subcontracted by a public transit agency to
support service provision.
Daily operator assignments grouped into weekly assignment packages.
A collection of patterns in revenue service.
See Operator Assignment.
The time used to define a schedule day. A schedule day spans 48 hours
in seconds [–43,2000, 129,599]; the day extends from noon the day
before the schedule day until noon the following day.
A geographic location that a transit agency uses to schedule transit
service and monitor adherence to the service schedule. It is a point at
which time is assigned to create trips.
A collection of stop points wherein transfer between routes is valid and
possible.
A one-way movement of a transit vehicle in revenue service between two
points.
A specific time assigned to a timepoint on a trip.
The work of a vehicle from the time it leaves the vehicle base until its
next return.
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 2-2
2.2
ABBREVIATIONS
ID
No
Msg
Hrs
Max
Min
Avg
Pt
Identification
Number
Message
Hours
Maximum
Minimum
Average
Point
2.3
ACRONYMS
VIN
Vehicle Identification Number
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 3-1
Section 3
BASIC CONCEPTS
3.1
SCHEDULING/RUNCUTTING (SCH) BUSINESS AREA DOMAIN
The Scheduling domain covers the data flow into and out of the scheduling and runcutting processes.
The components and data flows are described in the section following.
3.2
COMPONENTS AND DATA FLOWS
3.2.1
Inputs
3.2.1.1
Service Planning
The Service Planning component aggregates existing system, system performance, demographics, rules
and policies, and multimodal coordination information. Although almost all the functions are manually
performed, many of the service planning task outputs are stored in digital form – either in a database
management system or geographic information system (GIS).
Moreover, even policies and procedures – that is, service policy, labor rules, and federal regulations – can
be coded as rules in a knowledge-based expert system decision support tool. These rules may be
specified as messages, although, the scheduling/runcutting messages do not explicitly define messages
of this sort.
3.2.1.2
New and Updated Routes
Most scheduling parameters are associated with specific routes. Particularly for service planning
functions, route alignments are generated to meet customer needs, federal regulations, policy
considerations, existing multimodal facility coordination, and roadway constraints. For this reason, routes,
lines, and patterns may be defined in a number of ways. These definitions may be linked to a digital base
map (including geography and topology) using geocoding techniques or to files (representing topologic
networks only). Both representations are supported by the data elements defined in NTCIP 1405,
formerly referenced as ST-ITS-TCIP-SP.
The spatial network definitions may be specified by listing the points (e.g., control points, access points,
time points), segments (e.g., time point intervals, links), or both points and lines along a route. Spatial
classes supporting these definitions may be found in the route class as defined in NTCIP 1405, formerly
referenced as ST-ITS-TCIP-SP.
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 3-2
Figure 3.1 Transit Scheduling Data Flow
Po licies And Rules
Public Forum s
Complaints,
Petitions,
Comm ents,
Calls, Drives
Customer
Inputs
Bo ard
Po licy
Ridership
Dem ands
Contractual
Obligations/
Labor Rules
Service
Po licy
Other Transit
Agencies
Dem ographics
Scheduling / Runcutting Component
Operating
Performance
Histo ry (DB)
- On-tim e
Performance
Routing (New And
Changes To Patterns)
Span of
Service
Service Planning
Tim e
Transfer
Headways
Po ints
Vehicle
Ty pe
Platform And
Layover
Requirem ents
Scheduling Sy stem
Existing Ro utes &
Facility Invento ry
Route
Description
Vehicle
Invento ry
Systems
Tim e
Tables
Bus Stop
Schedules
Street
Superviso r
Assig nment
Vehicle
Assig nment
Remote
Info rm ation
Devices
Travel
Itinerary
Planning
Operator
Assig nment
AVL/CAD
Info rm ation
Service
Providers
Operating
Performance
Histo ry
Do Not Copy Without Written Permission
Runcutter
Blo ck er
Service Information
(Static)
Actual
Operations
CADD/AVL
Trip
Builder
APC
© 2001 AASHTO / ITE / NEMA
Roadside
Systems
(Signal Priority)
Traffic
Managem ent
Center
Em ergency
Managem ent
Center
Paratransit
Reservatio ns
& Dispatch
NTCIP 1404 v01.02
Page 3-3
3.2.1.3
Span of Service
The scheduling component also needs to know the interval during which the transit agency provides
service by service type. For example, regular service may be provided between 6:00 a.m. and 11:00 p.m.
while express service may only be scheduled during the morning and evening peak periods.
3.2.1.4
Headways
Service frequency depends on the time interval, or headway, between trips operating in the same direction
on a route. The headway of trips for each route-direction may be based on load (maximum load point) or
policy considerations. Headways are defined on a per route-direction basis for various periods during the
span of service. Headways may also be defined for contiguous segments shared by multiple routes.
3.2.1.5
Time-Transfer Points
The time transfer process typically starts with the definition of selected origins and destinations to be
connected via inter-route transfer, maximum allowable passenger waiting times, allowances for minimum
expected en-route delays, maximum allowable connection hold times, specified connection locations, and
schedule transfer opportunities. In actual practice, connections between transit routes may either be
unidirectional or bi-directional, and may be published in public timetables (for connections between fixed
route services), planned on a daily basis (for paratransit operations), or generated in real-time (in
response to emergency situations). With the exception of real time connections generated in response to
emergency situations, connections are usually planned between pairs of trips on specific routes, patterns
or groups of trips, as in the case of “pulsed” service where transit vehicles may periodically converge on a
major transit location or locations).
3.2.1.6
Transit Vehicle Inventory
Transit vehicle characteristics vary by size, capacity, and accessibility. Transit agencies maintain an
inventory of vehicles available for service. These inventories may contain information about the age,
model, and make of the vehicles, their seating and standing capacities, and their maximum operating
speeds. The inventories may also contain information on any special characteristics of a bus such as if
the vehicle is lift-equipped, articulated, has a bike rack, etc. All of this information is important to
scheduling because selected routes may require certain vehicle capacity or other specific characteristics.
Scheduling staff need to know how many vehicles of a given category are available that they can assign to
blocks.
3.2.1.7
Operator Work Requirements
Operator work requirements reflect labor agreements and transit policy considerations. These
considerations include platform and layover time and locations, operator paid work time, reporting times,
and relief locations and policies.
3.2.1.8
Operating Performance History
Operating performance history is a core set of data collected and used by many groups within a transit
agency. It may be in one or more databases managed by the transit property. The History contains
information on actual performance of transit service (detailed by stop and route), actual operator work,
actual vehicle work (revenue miles and total miles), and vehicle mechanical performance. It may contain
information on ridership, revenues, fare transactions, schedule adherence, route adherence, operator
message transactions, running times, wait times, and more.
3.2.1.9
Automatic Passenger Counter
Automatic passenger counters (APC) collect information on passengers boarding and alighting a transit
vehicle. APCs collect valuable ridership data to the scheduling component. APCs provide passenger
loads by routes, segments, or stop points along a route to aid transit planners in determining the level of
service required to meet demand.
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 3-4
3.2.1.10 Farebox Data
Electronic fareboxes may provide useful boarding statistics, usage by ridership classification, fare media
type, and origin-destination data that can be used to fine tune ridership demand (especially when a transit
system uses a distance-based fare structure). With the advent of multimode-multiuse smart cards, this
analysis can be refined to assess customer level usage and preferences.
3.2.1.11 Existing Routes, Trips and Other Transit Facilities
Existing route and trip descriptions may contain more information than New and Updated Routes. Not
only do existing routes include information about the path and geometry, comfort stations, and other
landmarks, but they are associated with timetables and performance information. Timetables or master
schedules include all the trip, pattern, and block group information. Performance information may include
operational costs, ridership (by route or stop point/route), revenue, running times, passenger wait times,
and other performance data. Moreover, other data sets may exist that capture control point, layover, pullin/pull-out, comfort station, and transfer point/cluster locations, and park & ride, terminal, and other transit
facilities along a route. Inventory management systems may store information on time points, bus stops,
transit facilities, and assets that are input into the scheduling system.
3.2.1.12 Vehicle Inventory
The vehicle inventory contains information on revenue and non-revenue transit vehicles. This database
provides information to Scheduling on the availability of vehicles for operator and supervisor scheduling.
3.2.2
Outputs
3.2.2.1
Systems/Operation Information
The scheduling data drives major systems and operations of the transit agency. Primarily, assignments of
operators, street supervisors, and vehicles are matched to vehicle (block) and operator (run) assignment
manifests. Moreover, these manifests are the basis for forming the daily operating schedules. The same
block and run manifests or subsets of the manifests are transferred to external agencies or roadside
devices to monitor scheduled trips.
3.2.2.2
Operator, Vehicle, and Street Supervisor Assignments (Transit Garage Management/
Operations)
The operator and street supervisor assignment functions manage the assignment of pieces of work to
operators and supervisors. This function occurs three to four times per year prior to a schedule change.
Operator and supervisor assignments include extra board pick lists.
3.2.2.3
Central Dispatch/Control Center (Including computer-aided dispatch Workstation)
Staff at the central control center can dispatch, monitor, and respond to on-road requests from transit
vehicles in service using an integrated system of AVL technology, computer-aided dispatch systems, and
scheduling software.
3.2.2.4
Traffic Management Center
Traffic management centers will find transit operating schedules useful in predicting regularly occurring
transit vehicle volumes or transit vehicle-related slowdowns.
3.2.2.5
Roadside Systems
Roadside systems such as signal prioritization systems may require data from the scheduling component
so that they can anticipate the frequency that transit vehicles will request priority, or validate a need for
priority. Only block and trip data – associated with routes that traverse the signal system – are required
for transfer.
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 3-5
3.2.2.6
On-board Systems
There are several advanced technology systems on transit vehicles that require inputs from the
scheduling component. These include the on-board components of the AVL system, electronic fareboxes,
and electronic headsigns, annunciators, and variable message signs.
3.2.2.7
Automatic Vehicle Location
AVL systems require information on timepoint times for each run associated with a block; the on-board
AVL system checks the vehicle’s actual location against the scheduled location. This information is used
to determine schedule adherence. In some cases, route adherence calculations are performed on board
the vehicle. When this occurs, the pattern path and geometry is required (that includes start and end
points and the shape points in-between).
3.2.2.8
Farebox
The farebox needs to know which route the vehicle is on (and if possible at which stop it is) when it
registers each fare. This can be complicated if one block serves more than one route. Block data usually
includes a destination identifier that can be used by the farebox to the identify the vehicle’s actual route at
any given time. The farebox may also need to know at which timepoint and/or stop point fares are
collected or in what fare zone the vehicle is located. Therefore, scheduling software needs to be able to
provide the farebox with destination identifier data, timepoints, and (if possible) stop locations.
3.2.2.9
Headsign, Annunciator, and Variable Message Sign (On-Board)
These types of on-board devices identify a route, pattern, or next stop, or describe the route (e.g., “Alewife
via Harvard Square”) or pattern. The information may be based on an ordered list of stops per trip or
pattern (with associated trigger point locations and digital message – either text or synthesized voice) or
on a series of time point intervals. These segment include activation point locations with an associated
digital message on the next stop point, all stop points, and patterns.
Based on real-time location data from the AVL, an activation point alerts the electronic headsign to access
the Route or Pattern identifier (schRouteDirectionName) from the Block message. When Stop Point
locations and identifiers are available from the scheduling output, annunciators and variable message
signs can use these data items in conjunction with AVL data to determine which message to trigger at any
given time and location along a transit service Block. For all the applications, the key piece of information
is derived from the Block level information.
3.2.2.10 Operating Performance History
Schedule data contribute to the core data set collected in the operating performance history. Transit
agencies rely on recorded data about their systems to report to the Federal Transit Administration (which
compiles the National Transit Database), as well as for a variety of performance measures specific to
individual agencies. These data track level of service. Output from the scheduling data can be combined
with data from other (real-time) system information or aggregated to provide performance information to
assess levels of service.
3.2.2.11 Service Information
One significant barrier that standardized interfaces overcome is the difficulty of inserting scheduling
information into traveler information systems. Standardization makes such input seamless. Three outlets
for this type of information are: remote information devices within the transit system, transit customer
information system/trip itinerary planning systems, and information service providers that supply transit
information to customers via such outlets as computer on-line services or automated telephone services.
The information can be packaged in different ways.
There are some computer systems that do not directly require scheduling component outputs, but do rely
on information derived from such outputs. Because of this relationship, it is important to consider these
systems’ data needs as well. Two such systems are the incident management system and the paratransit
reservations and dispatching system.
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 3-6
3.2.2.12 Incident Management
When an incident occurs on a transit vehicle, the location of that vehicle is of vital importance. Therefore,
the emergency response team needs access to the location information that the AVL provides. Along with
this information, it may be important to know who the driver is, what route the vehicle is on, if the vehicle is
on-route or not, identification of the vehicle, and the type of vehicle it is. Most of this information comes
from dispatch (Transit Garage Management/Operations), yet the format is similar to block, run, and roster
data elements.
3.2.2.13 Paratransit Reservations and Dispatch
The paratransit reservations and dispatching system requires information from the trip itinerary planning
system because, increasingly, transit agencies are trying to “mainline” paratransit passengers to the
extent possible to save costs. Therefore, data items such as whether a scheduled transit vehicle is
wheelchair accessible need to be accommodated within the scheduling component. Also, paratransit
reservations and dispatch systems can rely on fixed-route trip itinerary planning software to determine if
the paratransit passenger can use fixed-route service for all or part of his/her trip to get to his/her
appointment on time.
3.3
CLASSIFICATION SCHEME
3.3.1
National Architecture Classification Scheme
This business area falls into one first level category in the National Architecture Classification as described
in the Framework document and the IEEE P1489 Annex A. Scheduling and Runcutting is associated with
the Level 1 category System Management, the Level 2 category Transit Management, and the Level 3
category Schedules and Runcutting.
3.3.2
TCIP Classification Tree
The TCIP classification scheme assigns one node to each message as well as a single node for each
business area’s data dictionary. Any messages embedded in other messages are assigned branch
nodes from the node of the message in which they are embedded. Figure 4.2 illustrates the TCIP
Classification Tree for Scheduling/Runcutting.
3.4
NAMING CONVENTIONS
The Scheduling/Runcutting business area uses the Object Tree as a classification hierarchy, as well as for
its naming conventions.
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 3-7
Figure 4.2 TCIP Classification Scheme for SCH
Figure 3.2 Classification Scheme
Scheduling an d Runcutting (SCH)
2
schdd
sch 1
schP attern
sch 7
schBlock Group
sch 2
schRoute
sch 9
schRoster
sch 8
schT imePo in tInterval
sch 13
schActiv ateAn no uncemen t
sch 18
schE vent
sch 3
schT imeT ableVersion
sch 14
schActiv ateDriver
sch 19
© 2001 AASHTO / ITE / NEMA
schM asterSchedule
sch 4
schRun
sch 10
schT rip
sch 15
schActiv ateFareZ on e
sch 20
schM asterScheduleHdr
sch 5
schRun ningT imePeriod
sch 11
schT ripT imePo int
sch 16
schNo te
sch 6
schT imePo in t
sch 12
schVeh icleAssign
sch 17
schActiv ateSign Chan ge
sch 21
schP ieceOfWo rk
sch 22
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 3-8
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-1
Section 4
REQUIREMENTS
This section defines those data dictionary elements that are expected to be used by Scheduling /
Runcutting implementations of business objects. The objects are described in terms of the IEEE 1489.
The objects are presented in the order of their appearance on the SCH classification tree.
4.1
SCHEDULING/RUNCUTTING DATA DICTIONARY
Descriptive Name:
SCH_ActivationID_nbr
Descriptive Name of Context:
ITS
Definition:
Identifiers for a variety of automatic actions, including: sign change, annunciation, new
fare set/zone, driver message, signal pre-emption point, etc.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 1
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-ActivationID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-2
Descriptive Name:
SCH_ActivationType_cd
Descriptive Name of Context:
ITS
Definition:
The type of activation event.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 2
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-ActivationType
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
1 Announcement trigger
2 Route adherence override
3 Sign change
4 Driver message trigger/paddle (relief point)
5 Fare zone
6 Radio zone
7 Relief trigger
8 Begin Layover
9 End Layover
10 Begin Trip
11 End Trip
12 Begin Deadhead
13 End Deadhead
14-149 Reserved
150-245 Local use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-3
Descriptive Name:
SCH_ActivationTypeDescription_txt /UCS
Descriptive Name of Context:
ITS
Definition:
Description of an unassigned activation type (SchActivationType)
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
SchActivationType
Relationship Type:
description of
Remarks:
External Name:
schdd 3
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-ActivationTypeDescription
Value Domain:
UCS
Data Type:
FOOTNOTE
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
Internal Layout Minimum Size:
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-4
Descriptive Name:
SCH_AnnouncementDuration_tm / SI-time
Descriptive Name of Context:
ITS
Definition:
The length of time of an automated audio or visual (via dynamic message sign)
announcement. If the duration is longer than the amount of time required to make the
announcement, the announcement is repeated.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 4
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-AnnouncementDuration
Value Domain:
IEEE/ASTM SI 10-1997 - time
Data Type:
DURTIME
Representation Classification Term:
time
Valid Value Range:
Valid Value List:
Valid Value Rule:
The units are in seconds.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-5
Descriptive Name:
SCH_AnnouncementID_nbr
Descriptive Name of Context:
ITS
Definition:
An identification number for each unique announcement within an transit agency.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 5
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-AnnouncementID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-6
Descriptive Name:
SCH_AnnouncementLocationID_nbr
Descriptive Name of Context:
ITS
Definition:
The functional address that identifies the device that receives the announcement. This
may refer to a vehicle annunciator, station annunciator, or other audio-facility. This data
element is user-defined.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 6
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-AnnouncementLocationID
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-7
Descriptive Name:
SCH_BlockDesignator_txt /UCS
Descriptive Name of Context:
ITS
Definition:
An alpha-numeric identifier used to associate a sequence of trips to a transit vehicle.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 7
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-BlockDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
Internal Layout Minimum Size:
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-8
Descriptive Name:
SCH_BlockGroupName_txt/UCS
Descriptive Name of Context:
ITS
Definition:
The name given to a block group.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 8
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-BlockGroupName
Value Domain:
UCS
Data Type:
NAME
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
Internal Layout Minimum Size:
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-9
Descriptive Name:
SCH_BlockID_nbr
Descriptive Name of Context:
ITS
Definition:
A unique identifier within a day type that is used to associate a sequence of trips to a
transit vehicle.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 9
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-BlockID
Value Domain:
Data Type:
IDENL
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-10
Descriptive Name:
SCH_BlockName_txt/UCS
Descriptive Name of Context:
ITS
Definition:
The name of the block. For legacy systems the block name often identifies the major
route served by the block and the pull out sequence.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Line
Related Data Concept:
Relationship Type:
Remarks:
This is not necessarily equivalent to SCH-BlockDesignator.
External Name:
schdd 10
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-BlockName
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
8
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-11
Descriptive Name:
SCH_DayType_cd
Descriptive Name of Context:
ITS
Definition:
A type of day characterized by one or more properties that affect public transport
operation.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 11
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-DayType
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
1 Sunday
2 Monday
3 Tuesday
4 Wednesday
5 Thursday
6 Friday
7 Saturday
8 Holiday
9 Weekday
10 Weekend
11 Weekday, school closed
12-149 Reserved
150-245 Local use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-12
Descriptive Name:
SCH_DayTypeDescription_txt/UCS
Descriptive Name of Context:
ITS
Definition:
Description of the type of day that affects revenue service, as characterized by a transit
agency .
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
schDayType
Relationship Type:
description of
Remarks:
External Name:
schdd 12
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-DayTypeDescription
Value Domain:
UCS
Data Type:
FOOTNOTE
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
256
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-13
Descriptive Name:
SCH_NoteDesignator_txt /UCS
Descriptive Name of Context:
ITS
Definition:
Alpha-numeric designator for a SchNoteMsg
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 13
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-NoteDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
Internal Layout Minimum Size:
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-14
Descriptive Name:
SCH_NoteID_nbr
Descriptive Name of Context:
ITS
Definition:
A unique identifier for a note.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 14
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-NoteID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-15
Descriptive Name:
SCH_NoteMsg_txt UCS
Descriptive Name of Context:
ITS
Definition:
A remark or comment related to a message or transit object.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 15
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-NoteMsg
Value Domain:
UCS
Data Type:
MEMSHORT
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
2048
Internal Layout Minimum Size:
1
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-16
Descriptive Name:
SCH_OperatingTimeType_cd
Descriptive Name of Context:
ITS
Definition:
A numeric value indicating the type of operating time.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 16
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-OperatingTimeType
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
1. Deadhead Time- Bus travel time in non-revenue bus travel time to or from the garage
and a terminus point where revenue services begins or ends; or within a vehicle
assignment from the end of one revenue service segment to the beginning of another.
2. Dwell Time - Time scheduled for loading passengers or waiting for them to transfer at
a stop point.
3. Layover Time - Scheduled rest and recovery, usually at a terminal.
4. Make Up Time - Payment for time in order that the total paid time for an operator
assignment is equal to a minimum daily or weekly guarantee.
5. Overtime - Identifies the amount of scheduled time paid beyond the daily guarantee or
actually operated beyond the scheduled time.
6. PullIn Time - Deadhead running time allowed a transit vehicle to arrive at the
VehicleBase after the final access or time point in the vehicle assignment.
7. PullOut Time - Deadhead running time allowed a transit vehicle to depart the
VehicleBase prior to arriving at the first time point in the vehicle assignment.
8. Spread Time - Total elapsed time between the first report time and the final turn-in
time of an operator’s assignment.
9. Travel Time - A period of time allocated to an operator during which (s)he must travel
from one piece of work to another.
10. TurnInAllowance - Paid time for the operator to report to the dispatcher at the
conclusion of a run.
11. Report Time - Paid time for the operator to prepare for the start of a run or a piece of
work.
12. Platform Time - Time when the operator is scheduled to drive the transit vehicle,
including layover time.
13. Break Time - Time when the operator is scheduled to have a rest.
14. Meal Break Time - Time when the operator is scheduled to have a rest (for a meal).
15-149. Reserved
150-245. Local Use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-17
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-18
Descriptive Name:
SCH_OperatorDesignator_txt /UCS
Descriptive Name of Context:
ITS
Definition:
An alpha-numeric identifier of the transit staff who operates a vehicle.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 17
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-OperatorDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
Internal Layout Minimum Size:
8
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-19
Descriptive Name:
SCH_PassengerKilometers_qty / SI-length
Descriptive Name of Context:
ITS
Definition:
A measure of service utilization that represents the cumulative sum of the distances
ridden by all passengers. It is normally calculated by summation of the passenger load
multiplied by the distance between two transit stop points. For example, ten passengers
riding in a transit vehicle for two kilometers equals 20 passenger kilometers, the value of
the object is 20.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 18
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-PassengerKilometers
Value Domain:
IEEE/ASTM SI 10-1997 Length (km)
Data Type:
ULONG
Representation Classification Term:
quantity
Valid Value Range:
Valid Value List:
Valid Value Rule:
Units are in kilometers.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-20
Descriptive Name:
SCH_PatternDesignator_txt /UCS
Descriptive Name of Context:
ITS
Definition:
An alpha-numeric identifier for a defined sequence of points, events, and activation
events along a route.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 19
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-PatternDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
8
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-21
Descriptive Name:
SCH_PatternID_nbr
Descriptive Name of Context:
ITS
Definition:
A unique identifier assigned by a transit agency for a defined sequence of points, events,
and activation events along a variation of a route.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 20
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-PatternID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-22
Descriptive Name:
SCH_PatternName_txt /UCS
Descriptive Name of Context:
ITS
Definition:
The name for a defined sequence of points and events along a variation of a route that
represents a physical path traversed by a transit vehicle in a network.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 21
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-PatternName
Value Domain:
Data Type:
NAME
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
30
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-23
Descriptive Name:
SCH_PayType_cd
Descriptive Name of Context:
ITS
Definition:
The pay factor that identifies the amount of money paid for each hour of service.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 22
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-PayType
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
1. Platform Time
2. Working Time
3. Spread
4. Spread Bonus
5. Overtime
6. Overtime Bonus
7. Paid Meal break
8. Other Paid Break
9. Paid Travel
10. Sign-on time
11. Sign-off time
12. Early Shift Bonus
13. Evening Shift Bonus
14. Night Shift Bonus
15-149 Reserved
150-245 Local use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-24
Descriptive Name:
SCH_PullinTime_tm /SI-time
Descriptive Name of Context:
ITS
Definition:
The time at which a transit vehicle arrives at its storage facility (vehicle base) after
deadheading from the last time point of its scheduled revenue service.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 23
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-PullinTime
Value Domain:
IEEE/ASTM SI 10-1997 time
Data Type:
SCHTIME
Representation Classification Term:
time
Valid Value Range:
Valid Value List:
Valid Value Rule:
Units are in seconds.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-25
Descriptive Name:
SCH_PulloutTime_tm /SI
Descriptive Name of Context:
ITS
Definition:
The time at which a vehicle pulls out of its storage facility (vehicle base) in order to arrive
at the first timepoint of its scheduled revenue service.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 24
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-PulloutTime
Value Domain:
IEEE/ASTM SI 10-1997 time
Data Type:
SCHTIME
Representation Classification Term:
time
Valid Value Range:
Valid Value List:
Valid Value Rule:
Units are in seconds.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-26
Descriptive Name:
SCH_RosterDesignator_txt / UCS
Descriptive Name of Context:
ITS
Definition:
An alpha-numeric index assigned by a transit agency to a roster.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 26
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RosterDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
UTF8String (SIZE (1..8))
Internal Layout Maximum Size:
Internal Layout Minimum Size:
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-27
Descriptive Name:
SCH_RosterID_nbr
Descriptive Name of Context:
ITS
Definition:
An unique number assigned by a transit agency to a weekly assignment.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 27
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RosterID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-28
Descriptive Name:
SCH_RouteDesignator_txt /UCS
Descriptive Name of Context:
ITS
Definition:
An alpha-numeric identifier of a collection of patterns in a revenue service.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 28
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RouteDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
8
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-29
Descriptive Name:
SCH_RouteDirectionID_nbr
Descriptive Name of Context:
ITS
Definition:
A unique identifier for a route direction.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 29
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RouteDirectionID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-30
Descriptive Name:
SCH_RouteDirectionName_cd
Descriptive Name of Context:
ITS
Definition:
A name that describes the direction of a route.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 30
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RouteDirectionName
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
1N
2 S
3 E
4W
5 SW
6 SE
7 NW
8 NE
9 Inbound
10 Outbound
11 Circular
12 Destination
13 Clockwise
14 Counter-Clockwise
15 (defined by name)
15-149 Reserved
150-245 Local use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-31
Descriptive Name:
SCH_RouteID_nbr
Descriptive Name of Context:
ITS
Definition:
Identifies a collection of patterns in a revenue service.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 31
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RouteID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-32
Descriptive Name:
SCH_RouteName_txt /UCS
Descriptive Name of Context:
ITS
Definition:
Names a collection of patterns in a revenue service.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 32
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RouteName
Value Domain:
UCS
Data Type:
NAME
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
30
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-33
Descriptive Name:
SCH_RunDesignator_txt /UCS
Descriptive Name of Context:
ITS
Definition:
The alpha-numeric designator of the run.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 33
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RunDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
8
Internal Layout Minimum Size:
1
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-34
Descriptive Name:
SCH_RunID_nbr
Descriptive Name of Context:
ITS
Definition:
Identifies the piece of work for an operator on a given day type or within a particular
schedule.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 34
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RunID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-35
Descriptive Name:
SCH_RunningSpeed_rt /SI - velocity
Descriptive Name of Context:
ITS
Definition:
The average speed maintained between terminals.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 35
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RunningSpeed
Value Domain:
IEEE/ASTM SI 10-1997 (k/h)
Data Type:
INTEGER
Representation Classification Term:
rate
Valid Value Range:
The valid range is 0 - 500 kph.
Valid Value List:
Valid Value Rule:
The speed is measured in kilometers per hour (kph).
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-36
Descriptive Name:
SCH_RunningTimeActual_tm /SI-time
Descriptive Name of Context:
ITS
Definition:
The actual time (based on real-time observations) for a transit vehicle in revenue service
to travel between two time points.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 36
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RunningTimeActual
Value Domain:
IEEE/ASTM SI 10-1997 time
Data Type:
DURTIME
Representation Classification Term:
time
Valid Value Range:
Valid Value List:
Valid Value Rule:
The units are in seconds.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-37
Descriptive Name:
SCH_RunningTimePeriod_txt /UCS
Descriptive Name of Context:
ITS
Definition:
The division of the operating day within a schedule or DayType into various periods for
the purpose of assigning running times that reflect the passenger loads and traffic
conditions prevalent at those times.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 37
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RunningTimePeriod
Value Domain:
UCS
Data Type:
NAME
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
30
Internal Layout Minimum Size:
1
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-38
Descriptive Name:
SCH_RunningTimeSched_tm /SI-time
Descriptive Name of Context:
ITS
Definition:
A time assigned to the movement of a revenue vehicle over a route between time points.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 38
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RunningTimeSched
Value Domain:
IEEE/ASTM SI 10-1997 time
Data Type:
DURTIME
Representation Classification Term:
time
Valid Value Range:
Valid Value List:
Valid Value Rule:
The units are in seconds.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-39
Descriptive Name:
SCH_RunType_cd
Descriptive Name of Context:
ITS
Definition:
Type of operator assignment.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 39
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RunType
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
1 AM Straight
2 Midday Straight
3 PM Straight
4 Straight
5 Cleanup
6 Owl
7 Regular
8 Relief
9 Split
10 Three Piece (including swing)
11 Tripper
12 Two Piece (including swing)
13-149 Reserved
150-245 Local use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-40
Descriptive Name:
SCH_RunTypeDescription _txt /UCS
Descriptive Name of Context:
ITS
Definition:
A description of type of run.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
schRunType
Relationship Type:
description of
Remarks:
External Name:
schdd 40
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-RunTypeDescription
Value Domain:
UCS
Data Type:
FOOTNOTE
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
256
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-41
Descriptive Name:
SCH_ServiceType_cd
Descriptive Name of Context:
ITS
Definition:
Type of transit service provided.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 41
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-ServiceType
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
1 Regular
2 Express
3 Circular
4 Radial
5 Feeder
6 Jitney
7 Limited
8 Non-revenue
9 Unknown
10 Charter Service
11 School Service
12 Special Service
13 Operator Training
14 Maintenance Service
15 No Service
16 Stand-by
17 Extra
18-149 Reserved
150-245 Local use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
Internal Representation Layout:
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-42
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-43
Descriptive Name:
SCH_ServiceTypeDescription_txt /UCS
Descriptive Name of Context:
ITS
Definition:
Description of the service type for SchServiceType.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 42
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-ServiceTypeDescription
Value Domain:
UCS
Data Type:
FOOTNOTE
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
256
Internal Layout Minimum Size:
1
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-44
Descriptive Name:
SCH_SignCodeID_nbr
Descriptive Name of Context:
ITS
Definition:
A unique identifier of a sign code for each unique announcement within an agency, e.g.
interior, exterior, etc.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 43
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-SignCodeID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-45
Descriptive Name:
SCH_SignLocationID_nbr
Descriptive Name of Context:
ITS
Definition:
The functional address for the sign location where a message is to appear. This may
refer to an in-vehicle sign, station sign, or other visualization media.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 44
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-SignLocationID
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-46
Descriptive Name:
SCH_SignText_txt /UCS
Descriptive Name of Context:
ITS
Definition:
The text of a sign.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 45
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-SignText
Value Domain:
UCS
Data Type:
FOOTNOTE
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
256
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-47
Descriptive Name:
SCH_StopPointLength_qty /SI-length
Descriptive Name of Context:
ITS
Definition:
The linear length (in distance) along a curb or parking area.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 46
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-StopPointLength
Value Domain:
IEEE/ASTM SI 10-1997 length (meter)
Data Type:
INTEGER
Representation Classification Term:
quantiy
Valid Value Range:
Valid Value List:
Valid Value Rule:
Units are meters.
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-48
Descriptive Name:
SCH_StopPointSequenceNo_nbr
Descriptive Name of Context:
ITS
Definition:
Identifies the order of stop points along a pattern or route.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 47
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-StopPointSequenceNo
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-49
Descriptive Name:
SCH_TimeBegin_tm /SI time
Descriptive Name of Context:
ITS
Definition:
The beginning time for a sequence of times.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 48
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimeBegin
Value Domain:
IEEE/ASTM SI 10-1997 time (second)
Data Type:
SCHTIME
Representation Classification Term:
time
Valid Value Range:
Valid Value List:
Valid Value Rule:
The units are in seconds.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-50
Descriptive Name:
SCH_TimeEnd_tm /SI-time
Descriptive Name of Context:
ITS
Definition:
The ending time for a sequence of times.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 49
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimeEnd
Value Domain:
IEEE/ASTM SI10-1997 time (second)
Data Type:
SCHTIME
Representation Classification Term:
time
Valid Value Range:
Valid Value List:
Valid Value Rule:
The units are in seconds.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-51
Descriptive Name:
SCH_TimePointDesignator_txt /UCS
Descriptive Name of Context:
ITS
Definition:
An alpha-numeric identifier of a location at which time is measured.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 50
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimePointDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
8
Internal Layout Minimum Size:
1
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-52
Descriptive Name:
SCH_TimePointID_nbr
Descriptive Name of Context:
ITS
Definition:
A number assigned by a transit agency to uniquely identify a location at which time is
measured.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 51
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimePointID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-53
Descriptive Name:
SCH_TimePointIntervalDesignator_txt /UCS
Descriptive Name of Context:
ITS
Definition:
An alpha-numeric identifier of the interval (link) between two time points.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 52
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimePointIntervalDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
8
Internal Layout Minimum Size:
1
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-54
Descriptive Name:
SCH_TimePointIntervalID_nbr
Descriptive Name of Context:
ITS
Definition:
Identifies a unique path between two time points.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 53
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimePointIntervalID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-55
Descriptive Name:
SCH_TimePointName_txt /UCS
Descriptive Name of Context:
ITS
Definition:
The name of a time point.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 54
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimePointName
Value Domain:
UCS
Data Type:
UTF8String
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
UTF8String (SIZE (1..40))
Internal Layout Maximum Size:
Internal Layout Minimum Size:
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-56
Descriptive Name:
SCH_TimePtNameShort_txt /UCS
Descriptive Name of Context:
ITS
Definition:
A short name associated with a time point. This 4-character name supports existing
legacy systems that rely on 4 characters to identify their time points.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 55
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimePtNameShort
Value Domain:
UCS
Data Type:
UTF8String
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
UTF8String (SIZE(1..4))
Internal Layout Maximum Size:
Internal Layout Minimum Size:
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-57
Descriptive Name:
SCH_TimeTableVersionID
Descriptive Name of Context:
ITS
Definition:
A unique number associated with the concepts, messages, and parts of a schedule
including all the messages associated with the scheduling business area.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 56
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimeTableVersionID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-58
Descriptive Name:
SCH_TimeTableVersionName_txt/UCS
Descriptive Name of Context:
ITS
Definition:
Name of a time table, e.g., ‘summer’.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
schTimeTableVersionID
Relationship Type:
description of
Remarks:
External Name:
schdd 57
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TimeTableVersionName
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
8
Internal Layout Minimum Size:
1
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-59
Descriptive Name:
SCH_TripDesignator_txt/UCS
Descriptive Name of Context:
ITS
Definition:
An alpha-numeric identifier of a one way operation of a revenue vehicle between two
terminus points on a route.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 58
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TripDesignator
Value Domain:
UCS
Data Type:
NAME8
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
Internal Layout Minimum Size:
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-60
Descriptive Name:
SCH_TripID_nbr
Descriptive Name of Context:
ITS
Definition:
A number assigned by a transit agency that uniquely identifies a one way operation of a
revenue vehicle between two terminus points on a route.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 59
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TripID
Value Domain:
Data Type:
IDENS
Representation Classification Term:
number
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
65535
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-61
Descriptive Name:
SCH_TripTimePointDescription_txt /UCS
Descriptive Name of Context:
ITS
Definition:
A description associated with an attribute of a trip time point.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
schTripTimePointAttribute
Relationship Type:
description of
Remarks:
External Name:
schdd 60
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TripTimePointDescription
Value Domain:
UCS
Data Type:
FOOTNOTE
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
256
Internal Layout Minimum Size:
1
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-62
Descriptive Name:
SCH_TripTimePtAttribute_cd
Descriptive Name of Context:
ITS
Definition:
Describes the characteristics of a time point in the context of a trip.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 61
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TripTimePtAttribute
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
1 Layover
2 Relief
3 Control
4 Transfer
5 Recovery
6 Pull in
7 Pull out
8 Maximum load point
9 Arrive
10 Depart
11 Schedule Adherence On
12 Schedule Adherence Off
13 Route Adherence On
14 Route Adherence Off
15-149 Reserved
150-245 Local use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-63
Descriptive Name:
SCH_TripTimePtTime_tm /SI - time
Descriptive Name of Context:
ITS
Definition:
The time value associated with a time point for a particular trip.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 62
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TripTimePtTime
Value Domain:
IEEE/ASTM SI 10-1997 time (second)
Data Type:
SCHTIME
Representation Classification Term:
time
Valid Value Range:
Valid Value List:
Valid Value Rule:
The units are in seconds.
Internal Representation Layout:
Internal Layout Maximum Size:
4294967295
Internal Layout Minimum Size:
0
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-64
Descriptive Name:
SCH_TripType_cd
Descriptive Name of Context:
ITS
Definition:
A classification of the one-way movement of a public transportation vehicle between two
points.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
Relationship Type:
Remarks:
External Name:
schdd 63
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
schTripType
Value Domain:
Data Type:
INTEGER
Representation Classification Term:
code
Valid Value Range:
Valid Value List:
0 escape
1 Revenue
2 Pull In (from vehicle base)
3 Pull Out (to vehicle base)
4 Deadhead
5 Extra
6 Standby
7 Garage transfer
8 Road call
9 Road call return
10 Road test
11 Invalid movement
12-149 Reserved
150-245 Local use
246 Null (data is null)
247 Intentionally left blank (not used)
248 Deleted by device (reset to null)
249 Data unavailable
250 Illegal calculation (e.g., divide by zero)
251 Value out of range
252 Device malfunction (no value returned)
253 Data expired (data deleted, no longer available)
254 Data suppressed for security or privacy
255 Unspecified
Valid Value Rule:
If local use codes are used, schTripTypeDescription should be used to describe the type
of trip.
Internal Representation Layout:
Internal Layout Maximum Size:
255
Internal Layout Minimum Size:
0
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-65
Descriptive Name:
SCH_TripTypeDescription_txt /UCS
Descriptive Name of Context:
ITS
Definition:
A description of the trip type.
Formula:
Source:
TCIP Working Group
Class Name:
SCH
Classification_Scheme_Name:
ST-ITS-TCIP-FRAME
Classification Scheme Version:
V 1.1
Keyword:
Related Data Concept:
schTripType
Relationship Type:
description of
Remarks:
External Name:
schdd 64
External Name Usage:
TCIP Tree Identifier
ANS1 Name:
SCH-TripTypeDescription
Value Domain:
UCS
Data Type:
FOOTNOTE
Representation Classification Term:
text
Valid Value Range:
Valid Value List:
Valid Value Rule:
Internal Representation Layout:
Internal Layout Maximum Size:
256
Internal Layout Minimum Size:
1
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-66
4.2
MESSAGE OBJECTS
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchActivateAnnouncement
Message Description:
A message that indicates the requirements for activating an announcement.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
4
Keyword:
Time Stamp:
Message Body:
SchActivateAnnouncement ::= SEQUENCE {
activation-id
SCH-ActivationID,
announce-duration SCH-AnnouncementDuration,
announce-location SCH-AnnouncementLocationID,
announcement
SEQUENCE OF SCH-AnnouncementID
}
Message Object Identifier:
sch 18
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-67
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchActivateDriver
Message Description:
This message indicates the requirements for activating a driver message request.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
2
Keyword:
Time Stamp:
Message Body:
SchActivateDriver ::= SEQUENCE {
activation-id SCH-ActivationID,
note
SCH-NoteID
}
Message Object Identifier:
sch 19
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-68
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchActivateFareZone
Message Description:
This message indicates the requirements for activating a change in fare zone.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
2
Keyword:
Time Stamp:
Message Body:
SchActivateFareZone ::= SEQUENCE {
activation-id SCH-ActivationID,
fare-zone-id CPT-FareZoneID
}
Message Object Identifier:
sch 20
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-69
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchActivateSignChange
Message Description:
A message that indicates the requirements for changing a sign.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
3
Keyword:
Time Stamp:
Message Body:
SchActivateSignChange::= SEQUENCE {
activation-id
SCH-ActivationID,
sign-location
SCH-SignLocationID OPTIONAL,
sign-code-id
SCH-SignCodeID
OPTIONAL
}
Message Object Identifier:
sch 21
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-70
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchBlockGroup
Message Description:
A grouping of blocks based on some common characteristics such as use common
corridor, terminus location, or route direction name.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
5
Keyword:
Time Stamp:
Message Body:
SchBlockGroup ::= SEQUENCE {
block-group-name SCH-BlockGroupName,
block-id
SEQUENCE OF SCH-BlockID,
note
SCH-NoteID OPTIONAL,
mode
CPT-Mode OPTIONAL,
timetable-version
SCH-TimeTableVersionID
}
Message Object Identifier:
sch 2
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-71
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchEvent
Message Description:
A message that activates an event at a specified time, location, or both.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
5
Keyword:
Time Stamp:
Message Body:
SchEvent ::= SEQUENCE {
activation-id
SEQUENCE OF SCH-ActivationID,
time-begin
SCH-TimeBegin OPTIONAL,
point
SpPointclass OPTIONAL,
activation-type
SEQUENCE OF SCH-ActivationType OPTIONAL,
timetable-version SCH-TimeTableVersionID OPTIONAL
}
Message Object Identifier:
sch 3
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-72
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchMasterSchedule
Message Description:
A table that includes all the time points and trips on a route. Contained within the route
description is the Master Schedule Header information.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
6
Keyword:
Time Stamp:
Message Body:
SchMasterSchedule::= SEQUENCE {
activation-date
CPT-ActivationDate,
deactivation-date CPT-DeactivationDate OPTIONAL,
route
SchRoute,
trip
SEQUENCE OF SchTrip,
mode
CPT-Mode
OPTIONAL,
timetable-version SCH-TimeTableVersionID OPTIONAL
}
Message Object Identifier:
sch 4
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-73
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchMasterScheduleHdr
Message Description:
Sequence of time point identifiers and/or their names used to define the order of time
points for all the patterns. This field is used to build timetables, for exterior signs, etc.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
4
Keyword:
Time Stamp:
Message Body:
SchMasterScheduleHdr ::= SEQUENCE {
time-point-id
SEQUENCE OF SCH-TimePointID OPTIONAL,
time-point-name SEQUENCE OF SCH-TimePointName OPTIONAL,
mode
CPT-Mode OPTIONAL,
timetable-version SCH-TimeTableVersionID OPTIONAL
} (WITH COMPONENTS {..., time-point-id PRESENT }|
WITH COMPONENTS {..., time-point-name PRESENT } )
Message Object Identifier:
sch 5
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-74
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchNote
Message Description:
Text that denotes information about a schedule data element or message.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
4
Keyword:
Time Stamp:
Message Body:
SchNote ::= SEQUENCE {
note-id
SCH-NoteID,
note-designator
SCH-NoteDesignator,
note-message
SCH-NoteMsg,
timetable-version SCH-TimeTableVersionID
}
Message Object Identifier:
sch 6
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-75
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchPattern
Message Description:
One of multiple outer route segments served by a single transit route.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
11
Keyword:
Time Stamp:
Message Body:
SchPattern ::= SEQUENCE {
pattern-designator
SCH-PatternDesignator,
pattern-id
SCH-PatternID,
pattern-name
SCH-PatternName
OPTIONAL,
note-id
SCH-NoteID OPTIONAL,
route-direction
SCH-RouteDirectionName OPTIONAL,
route-id
SCH-RouteID,
time-points
SEQUENCE OF SCH-TimePointID,
stop-points
SEQUENCE OF CPT-StopPointID,
triggers
SEQUENCE OF SCH-ActivationID OPTIONAL,
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
Message Object Identifier:
sch 7
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-76
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchPieceOfWork
Message Description:
A piece of work.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
5
Keyword:
Time Stamp:
Message Body:
SchPieceOfWork::= SEQUENCE {
op-time-types
SEQUENCE OF SCH-OperatingTimeType,
time-begin
SCH-TimeBegin,
time-end
SCH-TimeEnd OPTIONAL,
timetable-version SCH-TimeTableVersionID OPTIONAL,
block-id
SEQUENCE OF SCH-BlockID
}
Message Object Identifier:
sch 22
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-77
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchRoster
Message Description:
Daily operator assignments grouped into weekly assignment packages.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
6
Keyword:
Time Stamp:
Message Body:
SchRoster::= SEQUENCE {
roster-id
SCH-RosterID,
roster-designator SCH-RosterDesignator,
runs
SEQUENCE OF SCH-RunID,
days
SEQUENCE OF CPT-DayofWeek,
mode
CPT-Mode
OPTIONAL,
timetable-version SCH-TimeTableVersionID OPTIONAL
}
Message Object Identifier:
sch 8
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-78
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchRoute
Message Description:
A collection of patterns in revenue service.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
10
Keyword:
Time Stamp:
Message Body:
SchRoute ::= SEQUENCE {
route-designator
SCH-RouteDesignator,
route-id
SCH-RouteID,
route-id-short
CC-RouteIDShort OPTIONAL,
route-name
SCH-RouteName OPTIONAL,
note-id
SCH-NoteID OPTIONAL,
patterns
SEQUENCE OF SCH-PatternID,
schedHdr1
SchMasterScheduleHdr OPTIONAL, --first direction
schedHdr2
SchMasterScheduleHdr OPTIONAL, --second direction
mode
CPT-Mode OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL
}
Message Object Identifier:
sch 9
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-79
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchRun
Message Description:
The daily pieces of work assigned to a transit employee.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
9
Keyword:
Time Stamp:
Message Body:
SchRun ::= SEQUENCE {
run-designator
SCH-RunDesignator,
run-id
SCH-RunID,
run-id-short
CC-RunIDShort OPTIONAL,
run-type
SCH-RunType,
day-type
SCH-DayType,
activation
CPT-ActivationDate,
note-id
SCH-NoteID OPTIONAL,
work
SEQUENCE OF SchPieceOfWork,
mode
CPT-Mode OPTIONAL,
timetable-version SCH-TimeTableVersionID OPTIONAL
}
Message Object Identifier:
sch 10
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-80
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1
Message Group ID:
SCH
Message Name:
SchRunningTimePeriod
Message Description:
The division of the operating day within a schedule or DayType into various periods for the
purpose of assigning running times that reflect the passenger loads and traffic conditions
prevalent at those times.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
6
Keyword:
Time Stamp:
Message Body:
SchRunningTimePeriod ::= SEQUENCE {
begin-time SCH-TimeBegin,
end-time
SCH-TimeEnd,
mode
CPT-Mode
OPTIONAL,
timetable-version SCH-TimeTableVersionID OPTIONAL,
day-type
SCH-DayType
OPTIONAL,
date
CPT-CalendarDate OPTIONAL
}
Message Object Identifier:
sch 11
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-81
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchTimePoint
Message Description:
A point at which time is measured to create trips.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
9
Keyword:
Time Stamp:
Message Body:
SchTimePoint ::= SEQUENCE {
timepoint-id
SCH-TimePointID,
timepoint-designator SCH-TimePointDesignator,
point
SpPointclass,
timepoint-name
SCH-TimePointName
OPTIONAL,
timepoint-name-short SCH-TimePtNameShort OPTIONAL,
note-id
SCH-NoteID
OPTIONAL,
stoppoints
SEQUENCE OF CPT-StopPointID OPTIONAL,
mode
CPT-Mode OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
Message Object Identifier:
sch 12
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-82
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchTimePointInterval
Message Description:
The segment between two timepoints.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
7
Keyword:
Time Stamp:
Message Body:
SchTimePointInterval ::= SEQUENCE {
tpi-id
SCH-TimePointIntervalID,
tpi-designator
SCH-TimePointIntervalDesignator,
startPointID
SCH-TimePointID, -- terminus of interval
endPointID
SCH-TimePointID, -- terminus of interval
location
SpRouteclass OPTIONAL, --may default to line class
mode
CPT-Mode OPTIONAL,
timetable-version SCH-TimeTableVersionID
OPTIONAL
}
Message Object Identifier:
sch 13
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-83
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1
Message Group ID:
SCH
Message Name:
SchTimeTableVersion
Message Description:
The version of a time table generated by the scheduling/runcutting module.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
5
Keyword:
Time Stamp:
Message Body:
SchTimeTableVersion ::= SEQUENCE {
timetable-version-id
SCH-TimeTableVersionID,
timetable-version-name SCH-TimeTableVersionName,
activation-date
CPT-ActivationDate
OPTIONAL,
deactivation-date
CPT-DeactivationDate OPTIONAL,
agency-id
CPT-AgencyID
OPTIONAL
}
Message Object Identifier:
sch 14
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-84
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchTrip
Message Description:
A one way movement of a transit vehicle in revenue service between two points.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
13
Keyword:
Time Stamp:
Message Body:
SchTrip::= SEQUENCE {
trip-id
SCH-TripID,
service-type SCH-ServiceType,
day-type
SCH-DayType,
route-id
SCH-RouteID,
patterns
SEQUENCE OF SCH-PatternID OPTIONAL,
run-id
SCH-RunID OPTIONAL,
block-id
SCH-BlockID OPTIONAL,
trip-type
SEQUENCE OF SCH-TripType OPTIONAL,
trip-timepoint-times
SEQUENCE OF SCH-TripTimePtTime,
event
SEQUENCE OF SchEvent OPTIONAL,
note
SCH-NoteID OPTIONAL,
mode
CPT-Mode OPTIONAL,
timetable-version SCH-TimeTableVersionID OPTIONAL
}
Message Object Identifier:
sch 15
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 4-85
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchTripTimePoint
Message Description:
Time at a timepoint on a trip.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
7
Keyword:
Time Stamp:
Message Body:
SchTripTimePoint ::= SEQUENCE {
timepoint-id
SCH-TimePointID
OPTIONAL,
timepoint-designator SCH-TimePointDesignator OPTIONAL,
trip-timepoint-time SCH-TripTimePtTime,
note
SEQUENCE OF SCH-NoteID,
trip-timepoint-attr
SCH-TripTimePtAttribute
OPTIONAL,
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL
} ( WITH COMPONENTS {..., timepoint-id PRESENT} |
WITH COMPONENTS {..., timepoint-designator PRESENT} )
Message Object Identifier:
sch 16
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 4-86
Message Identifier:
TCIP
Message Set ID:
ST-ITS-TCIP-SCH
Message Set Version:
1.1
Message Group ID:
SCH
Message Name:
SchVehicleAssign
Message Description:
The work of a vehicle from the time it leaves the vehicle base (schVehicleBase) until its
next return. Alias: Block.
Meta Data Source:
Direct
Priority:
no priority
Frequency:
Message Length:
15
Keyword:
Time Stamp:
Message Body:
SchVehicleAssign::= SEQUENCE {
block-id
SCH-BlockID,
block-id-short
CC-BlockIDShort OPTIONAL,
block-designator
SCH-BlockDesignator OPTIONAL,
block-name
SCH-BlockName
OPTIONAL,
pullout-time
SCH-PulloutTime
OPTIONAL,
pullin-time
SCH-PullinTime
OPTIONAL,
pullOut-location
SpPointclass OPTIONAL, --refers to the pull-out location
pullIn-location
SpPointclass OPTIONAL, --refers to the pull-in location
day-type
SCH-DayType,
trips
SEQUENCE OF SCH-TripID,
ptv-type
CPT-PTVehicleType OPTIONAL,
agency
CPT-AgencyID
OPTIONAL,
ptv-base
CPT-PTVehicleBaseName OPTIONAL,
organizational-unit CPT-OrganizationalUnitID OPTIONAL,
note
SCH-NoteID
OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
Message Object Identifier:
sch 17
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page 5-1
Section 5
CONFORMANCE REQUIREMENTS
The Scheduling/Runcutting business area supports the first two levels of conformance: Conformance
Levels 1 and 2 as defined in NTCIP 1400, formerly referenced as ST-ITS-TCIP-FRAME, Version 1.1. The
conformance group, in the context of this document, is defined as the collection of SCH and related
objects that are required to support components in the Scheduling/Runcutting area. Level One
conformance requires data elements contained within this document and other documents that support
this business area. Level Two conformance requires the inclusion of all the objects (data elements and
messages) that support the business area messages contained in Section 4.2 of this document.
5.1
LEVEL ONE CONFORMANCE
Data Element Name
Reference*
SCH Data Elements
NTCIP 1404, formerly referenced as ST-ITS-TCIP-SCH,
Section 4.1
CC-RunIDShort
CC-RouteIDShort
NTCIP 1407, formerly referenced as ST-ITS-TCIP-CC,
Section 4.1
CPT Data Elements
NTCIP 1401, formerly referenced as ST-ITS-TCIP-CPT,
Section 4.1
* NTCIP 1404 (ST-ITS-TCIP-SCH) refers to this document. See Section 4.1 for complete listing. NTCIP
1401 (ST-ITS-TCIP-CPT) Section 4.1 refers to the Common Public Transportation Data Elements. NTCIP
1405 (ST-ITS-TCIP-SP) Section 4.1 refers to the Standard on Spatial Representation.
5.2
LEVEL TWO CONFORMANCE
Message Name
Reference*
SCH Messages
NTCIP 1404, formerly referenced as ST-ITS-TCIP-SCH
Section 4.2
SpPointclass
SpAddresspoint
NTCIP 1405, formerly referenced as ST-ITS-TCIP-SP
Section 4.2
* NTCIP 1404 (ST-ITS-TCIP-SCH) refers to this document. See Section 4.2 for complete listing. NTCIP
1405 (ST-ITS-TCIP-SP) Section 4.2 refers to the Standard on Spatial Representation Objects.
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page 5-2
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page A-1
ANNEX A
Data Element/Message Use Cross Reference Table
Data Element
Message(s)
SCH-ActivationID
SchActivateFareZone
SchPattern
SchActivateSignChange
SchActivateDriver
SchActivateAnnouncement
SchEvent
SCH-ActivationType
SchEvent
SCH-AnnouncementDuration
SchActivateAnnouncement
SCH-AnnouncementID
SchActivateAnnouncement
SCH-AnnouncementLocationID
SchActivateAnnouncement
SCH-BlockDesignator
SchVehicleAssign
SCH-BlockGroupName
SchBlockGroup
SCH-BlockID
ImPTVOperatingParam
SchPieceOfWork
SchBlockGroup
SchVehicleAssign
SchTrip
SCH-BlockName
SchVehicleAssign
SCH-DayType
SchVehicleAssign
SchTrip
SchRunningTimePeriod
SchRun
PiPublishedSchedule
SCH-NoteDesignator
SchNote
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page A-2
Data Element
Message(s)
SCH-NoteID
SchActivateDriver
SchRun
SchVehicleAssign
SchBlockGroup
SchNote
SchTrip
SchRoute
SchTimePoint
SchTripTimePoint
SchPattern
SCH-NoteMsg
SchNote
SCH-OperatingTimeType
SchPieceOfWork
SCH-PatternDesignator
SchPattern
SCH-PatternID
SchTrip
SchPattern
SchRoute
SCH-PatternName
SchPattern
SCH-PullinTime
SchVehicleAssign
SCH-PulloutTime
SchVehicleAssign
SCH-RosterDesignator
SchRoster
SCH-RosterID
SchRoster
SCH-RouteDesignator
SchRoute
SCH-RouteDirectionName
PiDynamicSignMessage
PiNearestStopRequest
ImPTVOperatingParam
SchPattern
PiTripLeg
PiNearestStop
PiPublishedSchedule
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page A-3
Data Element
Message(s)
SCH-RouteID
SchRoute
PiNearestStop
SchPattern
PiSchedAdherenceOffSched
SchTrip
PiTripConstraintInclude
PiTripConstraintExclude
PiNearestStopRequest
PiPublishedSchedule
PiSchedAdherenceCountdown
PiSchedAdherenceRange
SCH-RouteName
PiSchedAdherenceCountdown
SchRoute
PiDynamicSignMessage
PiSchedAdherenceOffSched
PiSchedAdherenceRange
SCH-RunDesignator
SchRun
SCH-RunID
ImPTVehicleInvolved
SchRun
SchTrip
ImPTVOperatingParam
SCH-RunType
SchRun
SCH-ServiceType
PiTripConstraintInclude
SchTrip
PiTripConstraintExclude
PiDynamicSignMessage
SCH-SignCodeID
SchActivateSignChange
SCH-SignLocationID
SchActivateSignChange
SCH-TimeBegin
SchRunningTimePeriod
SchEvent
SchPieceOfWork
SCH-TimeEnd
SchRunningTimePeriod
SchPieceOfWork
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page A-4
Data Element
Message(s)
SCH-TimePointDesignator
SchTimePointInterval
SchTimePoint
SchTripTimePoint
SCH-TimePointID
SchTimePointInterval
SchTimePointInterval
SchMasterScheduleHdr
SchPattern
SchTripTimePoint
SchTimePoint
SCH-TimePointIntervalID
SchTimePointInterval
SCH-TimePointName
SchTimePoint
SchMasterScheduleHdr
SCH-TimePointTime
PiPublishedSchedule
SCH-TimePtNameShort
SchTimePoint
SCH-TimeTableVersionID
SchEvent
SchTripTimePoint
SchTimeTableVersion
SchTimePointInterval
SchRunningTimePeriod
SchPattern
SchTrip
SchVehicleAssign
SchRun
SchRoute
SchRoster
SchTimePoint
SchPieceOfWork
SchBlockGroup
SchMasterSchedule
SchNote
SchMasterScheduleHdr
SCH-TimeTableVersionName
SchTimeTableVersion
SCH-TripID
SchVehicleAssign
PiSchedAdherenceCountdown
PiSchedAdherenceOffSched
PiSchedAdherenceRange
SchTrip
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page A-5
Data Element
Message(s)
SCH-TripTimePtAttribute
SchTripTimePoint
SCH-TripTimePtTime
SchTrip
SchTripTimePoint
SCH-TripType
SchTrip
SchEvent
SchTrip
SchMasterScheduleHdr
PiPublishedSchedule
SchRoute
SchRoute
SchPieceOfWork
SchRun
SchRoute
SchMasterSchedule
SchTrip
SchMasterSchedule
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page A-6
Do Not Copy Without Written Permission
© 2001 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-1
ANNEX B
ASN.1 Script Informative Annex
This annex is a script in ASN.1 format for compiling the required SCH business objects.
TCIP-SCHDD
DEFINITIONS
AUTOMATIC TAGS
::= BEGIN
IMPORTS IDENS, IDENL, NAME, NAME8, FOOTNOTE, DURTIME, SCHTIME, MEMSHORT
FROM TCIP-Subtypes
sch, TCIP-CLASS,
CPT-ActivationDate, CPT-AgencyID, CPT-CalendarDate,
CPT-DayofWeek, CPT-DeactivationDate, CPT-FareZoneID,
CPT-Mode, CPT-OrganizationalUnitID, CPT-PTVehicleBaseName,
CPT-PTVehicleType, CPT-StopPointID
FROM TCIP-CPTDD
SpPointclass, SpRouteclass
FROM TCIP-SPDD
CC-BlockIDShort, CC-RouteIDShort, CC-RunIDShort
FROM TCIP-CCDD;
-- OBJECT IDENTIFIER
schdd OBJECT IDENTIFIER ::= {sch 1}
-- DATA DICTIONARY DEFINITIONS
sch-ActivationID-OID OBJECT IDENTIFIER
::= { schdd 1 }
sch-ActivationID TCIP-CLASS
::= {
SCH-ActivationID IDENTIFIED BY sch-ActivationID-OID
WITH DESCRIPTION "Identifiers for a variety of automatic actions, including:
sign change, annunciation, new fare set/zone, driver
message, signal pre-emption point, etc."
}
SCH-ActivationID ::= IDENS
sch-ActivationType-ID OBJECT IDENTIFIER
::= { schdd 2 }
sch-ActivationType TCIP-CLASS
::= {
SCH-ActivationType IDENTIFIED BY sch-ActivationType-ID
WITH DESCRIPTION "The type of activation event."
}
SCH-ActivationType ::= INTEGER {
annTrigger(1),
-- announcement trigger
routeAdhOverride(2),
-- route adherence override
signChange(3),
-- sign change
msgTrigger(4),
-- driver message trigger/paddle (relief point)
fareZone (5),
-- fare zone
radioZone (6),
-- radio zone
reliefTrigger (7), -- relief trigger
beginLayover (8),
-- Begin Layover
endLayover (9),
-- End Layover
beginTrip (10),
-- Begin Trip
endTrip (11),
-- End Trip
beginDeadhead (12),
-- Begin Deadhead
endDeadhead (13),
-- End Deadhead
-- 14-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-2
intentionallyLeftBlank (247),
deletedByDevice
(248),
dataUnavailable
(249),
illegalCalculation
(250),
valueOutOfRange
(251),
deviceMalfunction
(252),
dataExpired
(253),
available)
dataSupressedForSecurityOrPrivacy
unspecified
(255)
} (0..255)
-- (not used)
-- (reset to null)
-- (no value returned)
-- (data deleted, no longer
(254),
sch-ActivationTypeDescription-ID OBJECT IDENTIFIER
::= { schdd 3 }
sch-ActivationTypeDescription TCIP-CLASS ::= {
SCH-ActivationTypeDescription IDENTIFIED BY sch-ActivationTypeDescription-ID
WITH DESCRIPTION "Description of an unassigned activation type
(SchActivationType)."
}
SCH-ActivationTypeDescription ::= FOOTNOTE
sch-AnnouncementDuration-ID OBJECT IDENTIFIER
::= { schdd 4 }
sch-AnnouncementDuration TCIP-CLASS
::= {
SCH-AnnouncementDuration IDENTIFIED BY sch-AnnouncementDuration-ID
WITH DESCRIPTION "The length of time of an automated audio or visual
(via dynamic message sign) announcement. If the duration is longer than the
amount of time required to make the announcement, the announcement is
repeated."
}
SCH-AnnouncementDuration ::= DURTIME
sch-AnnouncementID-OID OBJECT IDENTIFIER
::= { schdd 5 }
sch-AnnouncementID
TCIP-CLASS
::=
{
SCH-AnnouncementID IDENTIFIED BY sch-AnnouncementID-OID
WITH DESCRIPTION "An identification number for each unique announcement
within an transit agency."
}
SCH-AnnouncementID ::= IDENS
sch-AnnouncementLocationID-OID OBJECT IDENTIFIER
::= { schdd 6 }
sch-AnnouncementLocationID
TCIP-CLASS
::=
{
SCH-AnnouncementLocationID IDENTIFIED BY sch-AnnouncementLocationID-OID
WITH DESCRIPTION "The functional address which identifies the device that
receives the announcement. This may refer to a vehicle annunciator, station
annunciator or other audio-facility. This data element is user defined."
}
SCH-AnnouncementLocationID ::= INTEGER (0..255)
sch-BlockDesignator-ID OBJECT IDENTIFIER
::= { schdd 7 }
sch-BlockDesignator
TCIP-CLASS
::=
{
SCH-BlockDesignator IDENTIFIED BY sch-BlockDesignator-ID
WITH DESCRIPTION "An alpha-numeric identifier used to associate a sequence of
trips to a transit vehicle."
}
SCH-BlockDesignator ::= NAME8
sch-BlockGroupName-ID OBJECT IDENTIFIER
::= { schdd 8 }
sch-BlockGroupName
TCIP-CLASS
::=
{
SCH-BlockGroupName IDENTIFIED BY sch-BlockGroupName-ID
WITH DESCRIPTION "The name given to a block group."
}
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-3
SCH-BlockGroupName
::= NAME
sch-BlockID-OID OBJECT IDENTIFIER
::= { schdd 9 }
sch-BlockID
TCIP-CLASS
::=
{
SCH-BlockID IDENTIFIED BY sch-BlockID-OID
WITH DESCRIPTION "A unique identifier within a day type which is used to
associate a sequence of trips to a transit vehicle."
}
SCH-BlockID ::= IDENL
sch-BlockName-ID OBJECT IDENTIFIER
::= { schdd 10 }
sch-BlockName
TCIP-CLASS
::=
{
SCH-BlockName IDENTIFIED BY sch-BlockName-ID
WITH DESCRIPTION "The name of the block. For legacy systems the block name
often identifies the major route served by the block and the pull out
sequence."
}
SCH-BlockName ::= NAME8
sch-DayType-ID OBJECT IDENTIFIER
::= { schdd 11 }
sch-DayType
TCIP-CLASS
::=
{
SCH-DayType IDENTIFIED BY sch-DayType-ID
WITH DESCRIPTION "A type of day characterized by one or more properties which
affect public transport operation."
}
SCH-DayType ::= INTEGER {
sunday (1),
-- Sunday
monday (2),
-- Monday
tuesday (3),
-- Tuesday
wednesday (4),
-- Wednesday
thursday (5),
-- Thursday
friday (6),
-- Friday
saturday (7),
-- Saturday
holiday (8),
-- Holiday
weekday (9),
-- Weekday
weekend (10),
-- Weekend
weekdaySchoolClosed (11), -- Weekday, school closed
-- 12-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
intentionallyLeftBlank (247),
-- (not used)
deletedByDevice
(248),
-- (reset to null)
dataUnavailable
(249),
illegalCalculation
(250),
valueOutOfRange
(251),
deviceMalfunction
(252),
-- (no value returned),
dataExpired
(253),
-- (data deleted, no longer
available),
dataSupressedForSecurityOrPrivacy
(254),
unspecified
(255)
} (0..255)
sch-DayTypeDescription-ID OBJECT IDENTIFIER
::= { schdd 12 }
sch-DayTypeDescription
TCIP-CLASS
::=
{
SCH-DayTypeDescription IDENTIFIED BY sch-DayTypeDescription-ID
WITH DESCRIPTION "Description of the type of day which affects revenue
service, as characterized by a transit agency."
}
SCH-DayTypeDescription ::= FOOTNOTE
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-4
sch-NoteDesignator-ID OBJECT IDENTIFIER
::= { schdd 13 }
sch-NoteDesignator
TCIP-CLASS
::=
{
SCH-NoteDesignator IDENTIFIED BY sch-NoteDesignator-ID
WITH DESCRIPTION "Alpha-numeric designator for a schNoteMsg."
}
SCH-NoteDesignator ::= NAME8
sch-NoteID-OID OBJECT IDENTIFIER
::= { schdd 14 }
sch-NoteID
TCIP-CLASS
::=
{
SCH-NoteID IDENTIFIED BY sch-NoteID-OID
WITH DESCRIPTION "A unique identifier for a note."
}
SCH-NoteID ::= IDENS
sch-NoteMsg-ID OBJECT IDENTIFIER
::= { schdd 15 }
sch-NoteMsg
TCIP-CLASS
::=
{
SCH-NoteMsg IDENTIFIED BY sch-NoteMsg-ID
WITH DESCRIPTION "A remark or comment related to a message or transit
object."
}
SCH-NoteMsg ::= MEMSHORT
sch-OperatingTimeType-ID OBJECT IDENTIFIER
::= { schdd 16 }
sch-OperatingTimeType
TCIP-CLASS
::=
{
SCH-OperatingTimeType IDENTIFIED BY sch-OperatingTimeType-ID
WITH DESCRIPTION "A numeric value indicating the type of operating time."
}
SCH-OperatingTimeType ::= INTEGER {
deadhead(1),
-- Deadhead Time
dwell(2),
-- Dwell Time
layover(3),
-- Layover Time
makeUp (4),
-- Make Up Time
overtime (5),
-- Overtime
pullIn (6),
-- PullIn Time
pullOut (7),
-- PullOut Time
spread (8),
-- Spread Time
travel (9),
-- Travel Time
turnInAllowance (10),
-- TurnInAllowance
report (11),
-- Report Time
platform (12),
-- Platform Time
break (13),
-- Break Time
mealBreak (14),
-- Meal Break Time
-- 15-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
intentionallyLeftBlank (247),
-- (not used)
deletedByDevice
(248),
-- (reset to null)
dataUnavailable
(249),
illegalCalculation
(250),
valueOutOfRange
(251),
deviceMalfunction
(252),
-- (no value returned),
dataExpired
(253),
-- (data deleted, no longer
available),
dataSupressedForSecurityOrPrivacy
(254),
unspecified
(255)
} (0..255)
sch-OperatorDesignator-ID OBJECT IDENTIFIER
::= { schdd 17 }
sch-OperatorDesignator
TCIP-CLASS
::=
{
SCH-OperatorDesignator IDENTIFIED BY sch-OperatorDesignator-ID
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-5
WITH DESCRIPTION "An alpha-numeric identifier of the transit staff who
operates a vehicle."
}
SCH-OperatorDesignator ::= NAME8
sch-PassengerKilometers-ID OBJECT IDENTIFIER
::= { schdd 18 }
sch-PassengerKilometers
TCIP-CLASS
::=
{
SCH-PassengerKilometers IDENTIFIED BY sch-PassengerKilometers-ID
WITH DESCRIPTION "A measure of service utilization which represents the
cumulative sum of the distances ridden by all passengers. It is normally
calculated by summation of the passenger load multiplied by the distance
between two transit stop points. For example, ten passengers riding in a
transit vehicle for two kilometers equals 20 passenger kilometers, the value
of the object is 20."
}
SCH-PassengerKilometers ::= INTEGER (0..4294967295)
sch-PatternDesignator-ID OBJECT IDENTIFIER
::= { schdd 19 }
sch-PatternDesignator
TCIP-CLASS
::=
{
SCH-PatternDesignator IDENTIFIED BY sch-PatternDesignator-ID
WITH DESCRIPTION "An alpha-numeric identifier for a defined sequence of
points, events and activation events along a route."
}
SCH-PatternDesignator ::= NAME8
sch-PatternID-OID OBJECT IDENTIFIER
::= { schdd 20 }
sch-PatternID
TCIP-CLASS
::=
{
SCH-PatternID IDENTIFIED BY sch-PatternID-OID
WITH DESCRIPTION "A unique identifier assigned by a transit agency for a
defined sequence of points, events and activation events along a variation of
a route."
}
SCH-PatternID ::= IDENS
sch-PatternName-ID OBJECT IDENTIFIER
::= { schdd 21 }
sch-PatternName
TCIP-CLASS
::=
{
SCH-PatternName IDENTIFIED BY sch-PatternName-ID
WITH DESCRIPTION "The name for a defined sequence of points and events along
a variation of a route that represents a physical path traversed by a transit
vehicle in a network."
}
SCH-PatternName ::= NAME
sch-PayType-ID OBJECT IDENTIFIER
::= { schdd 22 }
sch-PayType
TCIP-CLASS
::=
{
SCH-PayType IDENTIFIED BY sch-PayType-ID
WITH DESCRIPTION "The pay factor which identifies the amount of money paid
for each hour of service."
}
SCH-PayType ::= INTEGER {
platform (1),
-- Platform Time
working (2),
-- Working Time
spread (3),
-- Spread
spreadBonus (4),
-- Spread Bonus
overtime(5),
-- Overtime
overtimeBonus (6),
-- Overtime Bonus
mealBreakPaid (7),
-- Paid Meal break
otherBreakPaid (8),
-- Other Paid Break
travelPaid (9),
-- Paid Travel
signOn (10),
-- Sign-on time
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-6
signOff (11),
earlyShiftBonus (12),
eveningShiftBonus (13),
nightShiftBonus (14),
-- Sign-off time
-- Early Shift Bonus
-- Evening Shift Bonus
-- Night Shift Bonus
-- 15-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
intentionallyLeftBlank (247),
-- (not used)
deletedByDevice
(248),
-- (reset to null)
dataUnavailable
(249),
illegalCalculation
(250),
valueOutOfRange
(251),
deviceMalfunction
(252),
-- no value returned
dataExpired
(253),
-- data deleted, no longer available
dataSupressedForSecurityOrPrivacy
(254),
unspecified
(255)
} (0..255)
sch-PullinTime-ID OBJECT IDENTIFIER
::= { schdd 23 }
sch-PullinTime
TCIP-CLASS
::=
{
SCH-PullinTime IDENTIFIED BY sch-PullinTime-ID
WITH DESCRIPTION "The time at which a transit vehicle arrives at its storage
facility (vehicle base) after deadheading from the last time point of its
scheduled revenue service."
}
SCH-PullinTime ::= SCHTIME
sch-PulloutTime-ID OBJECT IDENTIFIER
::= { schdd 24 }
sch-PulloutTime
TCIP-CLASS
::=
{
SCH-PulloutTime IDENTIFIED BY sch-PulloutTime-ID
WITH DESCRIPTION "The time at which a vehicle pulls out of its storage
facility (vehicle base) in order to arrive at the first timepoint of its
scheduled revenue service."
}
SCH-PulloutTime ::= SCHTIME
sch-RosterDesignator-ID OBJECT IDENTIFIER
::= { schdd 26 }
sch-RosterDesignator
TCIP-CLASS
::=
{
SCH-RosterDesignator IDENTIFIED BY sch-RosterDesignator-ID
WITH DESCRIPTION "An alpha-numeric index assigned by a transit agency to a
roster."
}
SCH-RosterDesignator ::= NAME8
sch-RosterID-OID OBJECT IDENTIFIER
::= { schdd 27 }
sch-RosterID
TCIP-CLASS
::=
{
SCH-RosterID IDENTIFIED BY sch-RosterID-OID
WITH DESCRIPTION "An unique number assigned by a transit agency to a weekly
assignment."
}
SCH-RosterID ::= IDENS
sch-RouteDesignator-ID OBJECT IDENTIFIER
::= { schdd 28 }
sch-RouteDesignator
TCIP-CLASS
::=
{
SCH-RouteDesignator IDENTIFIED BY sch-RouteDesignator-ID
WITH DESCRIPTION "An alpha-numeric identifier of a collection of patterns in
a revenue service."
}
SCH-RouteDesignator ::= NAME8
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-7
sch-RouteDirectionID-OID OBJECT IDENTIFIER
::= { schdd 29 }
sch-RouteDirectionID
TCIP-CLASS
::=
{
SCH-RouteDirectionID IDENTIFIED BY sch-RouteDirectionID-OID
WITH DESCRIPTION "A unique identifier for a route direction."
}
SCH-RouteDirectionID ::= IDENS
sch-RouteDirectionName-ID OBJECT IDENTIFIER
::= { schdd 30 }
sch-RouteDirectionName
TCIP-CLASS
::=
{
SCH-RouteDirectionName IDENTIFIED BY sch-RouteDirectionName-ID
WITH DESCRIPTION "A name which describes the direction of a route."
}
SCH-RouteDirectionName ::= INTEGER {
north (1),
-- North
south (2),
-- South
east (3),
-- East
west(4),
-- West
sw (5),
-- Southwest
se (6),
-- Southeast
nw (7),
-- Northwest
ne (8),
-- Northeast
in (9),
-- Inbound
out (10),
-- Outbound
circ (11),
-- Circular
dest (12),
-- Destination
clockwise(13),
-- Clockwise
counterClock (14), -- Counter-Clockwise
name (15),
-- defined by name of route
-- 16-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
intentionallyLeftBlank (247),
-- (not used)
deletedByDevice
(248),
-- (reset to null)
dataUnavailable
(249),
illegalCalculation
(250),
valueOutOfRange
(251),
deviceMalfunction
(252),
-- (no value returned),
dataExpired
(253),
-- (data deleted, no longer
available),
dataSupressedForSecurityOrPrivacy
(254),
unspecified
(255)
} (0..255)
sch-RouteID-OID OBJECT IDENTIFIER
::= { schdd 31 }
sch-RouteID
TCIP-CLASS
::=
{
SCH-RouteID IDENTIFIED BY sch-RouteID-OID
WITH DESCRIPTION "Identifies a collection of patterns in a revenue service."
}
SCH-RouteID ::= IDENS
sch-RouteName-ID OBJECT IDENTIFIER
::= { schdd 32 }
sch-RouteName
TCIP-CLASS
::=
{
SCH-RouteName IDENTIFIED BY sch-RouteName-ID
WITH DESCRIPTION "Names a collection of patterns in a revenue service."
}
SCH-RouteName ::= NAME
sch-RunDesignator-ID OBJECT IDENTIFIER
sch-RunDesignator
TCIP-CLASS
::=
© 2001 AASHTO / ITE / NEMA
::=
{
{ schdd 33 }
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-8
SCH-RunDesignator IDENTIFIED BY sch-RunDesignator-ID
WITH DESCRIPTION "The alpha-numeric designator of the run."
}
SCH-RunDesignator ::= NAME8
sch-RunID-OID OBJECT IDENTIFIER
::= { schdd 34 }
sch-RunID
TCIP-CLASS
::=
{
SCH-RunID IDENTIFIED BY sch-RunID-OID
WITH DESCRIPTION "Identifies the piece of work for an operator on a given day
type or within a particular schedule."
}
SCH-RunID ::= IDENS
sch-RunningSpeed-ID OBJECT IDENTIFIER
::= { schdd 35 }
sch-RunningSpeed
TCIP-CLASS
::=
{
SCH-RunningSpeed IDENTIFIED BY sch-RunningSpeed-ID
WITH DESCRIPTION "The average speed maintained between terminals."
}
SCH-RunningSpeed ::= INTEGER (0..65535)
sch-RunningTimeActual-ID OBJECT IDENTIFIER
::= { schdd 36 }
sch-RunningTimeActual
TCIP-CLASS
::=
{
SCH-RunningTimeActual IDENTIFIED BY sch-RunningTimeActual-ID
WITH DESCRIPTION "The actual time (based on real-time observations) for a
transit vehicle in revenue service to travel between two time points."
}
SCH-RunningTimeActual ::= DURTIME
sch-RunningTimePeriod-ID OBJECT IDENTIFIER
::= { schdd 37 }
sch-RunningTimePeriod
TCIP-CLASS
::=
{
SCH-RunningTimePeriod IDENTIFIED BY sch-RunningTimePeriod-ID
WITH DESCRIPTION "The division of the operating day within a schedule or
DayType into various periods for the purpose of assigning running times that
reflect the passenger loads and traffic conditions prevalent at those times."
}
SCH-RunningTimePeriod ::= NAME
sch-RunningTimeSched-ID OBJECT IDENTIFIER
::= { schdd 38 }
sch-RunningTimeSched
TCIP-CLASS
::=
{
SCH-RunningTimeSched IDENTIFIED BY sch-RunningTimeSched-ID
WITH DESCRIPTION "A time assigned to the movement of a revenue vehicle over a
route between time points."
}
SCH-RunningTimeSched ::= DURTIME
sch-RunType-ID OBJECT IDENTIFIER
::= { schdd 39 }
sch-RunType
TCIP-CLASS
::=
{
SCH-RunType IDENTIFIED BY sch-RunType-ID
WITH DESCRIPTION "Type of operator assignment."
}
SCH-RunType ::= INTEGER {
amStraigtht (1), -- AM Straight,
midStraight (2), -- Midday Straight,
pmStraight (3),
-- PM Straight,
straight (4),
-- Straight,
cleanup (5),
-- Cleanup,
owl (6),
-- Owl,
regular (7),
-- Regular,
relief (8),
-- Relief,
split (9),
-- Split,
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-9
threePiece (10),
tripper (11),
twoPiece(12),
-- Three Piece (including swing),
-- Tripper,
-- Two Piece (including swing)
-- 13-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
intentionallyLeftBlank (247),
-- (not used)
deletedByDevice
(248),
-- (reset to null)
dataUnavailable
(249),
illegalCalculation
(250),
valueOutOfRange
(251),
deviceMalfunction
(252),
-- no value returned
dataExpired
(253),
-- data deleted, no longer available
dataSupressedForSecurityOrPrivacy
(254),
unspecified
(255)
} (0..255)
sch-RunTypeDescription-ID OBJECT IDENTIFIER
::= { schdd 40 }
sch-RunTypeDescription
TCIP-CLASS
::=
{
SCH-RunTypeDescription IDENTIFIED BY sch-RunTypeDescription-ID
WITH DESCRIPTION "A description of type of run."
}
SCH-RunTypeDescription ::= FOOTNOTE
sch-ServiceType-ID OBJECT IDENTIFIER
::= { schdd 41 }
sch-ServiceType
TCIP-CLASS
::=
{
SCH-ServiceType IDENTIFIED BY sch-ServiceType-ID
WITH DESCRIPTION "Type of transit service provided."
}
SCH-ServiceType ::= INTEGER {
regular (1),
-- Regular,
express (2),
-- Express,
circular(3),
-- Circular,
radial (4),
-- Radial,
feeder (5),
-- Feeder,
jitney (6),
-- Jitney,
limited (7),
-- Limited,
nonRevenue (8),
-- Non-revenue,
unknown (9),
-- Unknown,
charter (10),
-- Charter Service,
school (11),
-- School Service,
special (12),
-- Special Service,
operatorTraining (13), -- Operator Training,
maintenance (14), -- Maintenance Service,
noService (15),
-- No Service,
standBy (16),
-- Stand-by,
extra (17),
-- Extra,
-- 18-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
intentionallyLeftBlank (247),
-- (not used)
deletedByDevice
(248),
-- (reset to null)
dataUnavailable
(249),
illegalCalculation
(250),
valueOutOfRange
(251),
deviceMalfunction
(252),
-- no value returned
dataExpired
(253),
-- data deleted, no longer
available,
dataSupressedForSecurityOrPrivacy
(254),
unspecified
(255)
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-10
} (0..255)
sch-ServiceTypeDescription-ID OBJECT IDENTIFIER
::= { schdd 42 }
sch-ServiceTypeDescription TCIP-CLASS
::=
{
SCH-ServiceTypeDescription IDENTIFIED BY sch-ServiceTypeDescription-ID
WITH DESCRIPTION "Description of the service type for schServiceType."
}
SCH-ServiceTypeDescription ::= FOOTNOTE
sch-SignCodeID-OID OBJECT IDENTIFIER
::=
{ schdd 43 }
sch-SignCodeID TCIP-CLASS
::=
{
SCH-SignCodeID IDENTIFIED BY sch-SignCodeID-OID
WITH DESCRIPTION "A unique identifier of a sign code for each unique
announcement within an agency, e.g. interior, exterior, etc."
}
SCH-SignCodeID ::= IDENS
sch-SignLocationID-OID OBJECT IDENTIFIER
::=
{ schdd 44 }
sch-SignLocationID TCIP-CLASS
::=
{
SCH-SignLocationID IDENTIFIED BY sch-SignLocationID-OID
WITH DESCRIPTION "The functional address for the sign location where a
message is to appear. This may refer to an in-vehicle sign, station sign or
other visualization media."
}
SCH-SignLocationID ::= INTEGER (0..255)
sch-SignText-ID OBJECT IDENTIFIER
::=
{ schdd 45 }
sch-SignText TCIP-CLASS
::=
{
SCH-SignText IDENTIFIED BY sch-SignText-ID
WITH DESCRIPTION "The text of a sign."
}
SCH-SignText ::= FOOTNOTE
sch-StopPointLength-ID OBJECT IDENTIFIER
::=
{ schdd 46 }
sch-StopPointLength TCIP-CLASS
::=
{
SCH-StopPointLength IDENTIFIED BY sch-StopPointLength-ID
WITH DESCRIPTION "The linear length (in distance) along a curb or parking
area."
}
SCH-StopPointLength ::= INTEGER (0..65535)
sch-StopPointSequenceNo-ID OBJECT IDENTIFIER ::=
{ schdd 47 }
sch-StopPointSequenceNo TCIP-CLASS ::= {
SCH-StopPointSequenceNo IDENTIFIED BY sch-StopPointSequenceNo-ID
WITH DESCRIPTION "Identifies the order of stop points along a pattern or
route."
}
SCH-StopPointSequenceNo ::= INTEGER (0..65535)
sch-TimeBegin-ID OBJECT IDENTIFIER ::=
{ schdd 48 }
sch-TimeBegin TCIP-CLASS
::= {
SCH-TimeBegin IDENTIFIED BY sch-TimeBegin-ID
WITH DESCRIPTION "The beginning time for a sequence of times."
}
SCH-TimeBegin ::= SCHTIME
sch-TimeEnd-ID OBJECT IDENTIFIER
::=
{ schdd 49 }
sch-TimeEnd TCIP-CLASS ::= {
SCH-TimeEnd IDENTIFIED BY sch-TimeEnd-ID
WITH DESCRIPTION "The ending time for a sequence of times."
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-11
}
SCH-TimeEnd
::= SCHTIME
sch-TimePointDesignator-ID OBJECT IDENTIFIER
::=
{ schdd 50 }
sch-TimePointDesignator TCIP-CLASS ::= {
SCH-TimePointDesignator IDENTIFIED BY sch-TimePointDesignator-ID
WITH DESCRIPTION "An alpha-numeric identifier of a location at which time is
measured."
}
SCH-TimePointDesignator ::= NAME8
sch-TimePointID-OID OBJECT IDENTIFIER
::=
{ schdd 51 }
sch-TimePointID TCIP-CLASS
::= {
SCH-TimePointID IDENTIFIED BY sch-TimePointID-OID
WITH DESCRIPTION "A number assigned by a transit agency to uniquely identify
a location at which time is measured."
}
SCH-TimePointID ::= IDENS
sch-TimePointIntervalDesignator-ID OBJECT IDENTIFIER ::=
{ schdd 52 }
sch-TimePointIntervalDesignator TCIP-CLASS
::= {
SCH-TimePointIntervalDesignator IDENTIFIED BY sch-TimePointIntervalDesignatorID
WITH DESCRIPTION "An alpha-numeric identifier of the interval (link) between
two time points."
}
SCH-TimePointIntervalDesignator ::= NAME8
sch-TimePointIntervalID-OID OBJECT IDENTIFIER
::=
{ schdd 53 }
sch-TimePointIntervalID TCIP-CLASS ::= {
SCH-TimePointIntervalID IDENTIFIED BY sch-TimePointIntervalID-OID
WITH DESCRIPTION "Identifies a unique path between two time points."
}
SCH-TimePointIntervalID ::= IDENS
sch-TimePointName-ID OBJECT IDENTIFIER
::=
{ schdd 54 }
sch-TimePointName TCIP-CLASS ::= {
SCH-TimePointName IDENTIFIED BY sch-TimePointName-ID
WITH DESCRIPTION "The name of a time point."
}
SCH-TimePointName ::= UTF8String (SIZE (1..40))
sch-TimePtNameShort-ID OBJECT IDENTIFIER ::=
{ schdd 55 }
sch-TimePtNameShort TCIP-CLASS
::= {
SCH-TimePtNameShort IDENTIFIED BY sch-TimePtNameShort-ID
WITH DESCRIPTION "A short name associated with a time point. This 4character name supports existing legacy systems which rely on 4 characters to
identify their time points."
}
SCH-TimePtNameShort ::= UTF8String (SIZE(1..4))
sch-TimeTableVersionID-OID OBJECT IDENTIFIER
::= { schdd 56 }
sch-TimeTableVersionID
TCIP-CLASS
::=
{
SCH-TimeTableVersionID IDENTIFIED BY sch-TimeTableVersionID-OID
WITH DESCRIPTION "A unique number associated with the concepts, messages and
parts of a schedule including all the messages associated with the scheduling
business area."
}
SCH-TimeTableVersionID ::= IDENS
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-12
sch-TimeTableVersionName-ID OBJECT IDENTIFIER
::= { schdd 57 }
sch-TimeTableVersionName
TCIP-CLASS
::=
{
SCH-TimeTableVersionName IDENTIFIED BY sch-TimeTableVersionName-ID
WITH DESCRIPTION "Name of a time table, e.g., `summer'."
}
SCH-TimeTableVersionName ::= NAME8
sch-TripDesignator-ID OBJECT IDENTIFIER
::= { schdd 58 }
sch-TripDesignator
TCIP-CLASS
::=
{
SCH-TripDesignator IDENTIFIED BY sch-TripDesignator-ID
WITH DESCRIPTION "An alpha-numeric identifier of a one way operation of a
revenue vehicle between two terminus points on a route."
}
SCH-TripDesignator ::= NAME8
sch-TripID-OID OBJECT IDENTIFIER
::= { schdd 59 }
sch-TripID
TCIP-CLASS
::=
{
SCH-TripID IDENTIFIED BY sch-TripID-OID
WITH DESCRIPTION "A number assigned by a transit agency that uniquely
identifies a one way operation of a revenue vehicle between two terminus
points on a route."
}
SCH-TripID ::= IDENS
sch-TripTimePointDescription-ID OBJECT IDENTIFIER
::= { schdd 60 }
sch-TripTimePointDescription TCIP-CLASS
::=
{
SCH-TripTimePointDescription IDENTIFIED BY sch-TripTimePointDescription-ID
WITH DESCRIPTION "A description associated with an attribute of a trip time
point."
}
SCH-TripTimePointDescription ::= FOOTNOTE
sch-TripTimePtAttribute-ID OBJECT IDENTIFIER
::= { schdd 61 }
sch-TripTimePtAttribute
TCIP-CLASS
::=
{
SCH-TripTimePtAttribute IDENTIFIED BY sch-TripTimePtAttribute-ID
WITH DESCRIPTION "Describes the characteristics of a time point in the
context of a trip."
}
SCH-TripTimePtAttribute ::= INTEGER {
layover (1),
-- Layover
relief (2),
-- Relief
control (3),
-- Control
transfer (4),
-- Transfer
recovery (5),
-- Recovery
pullIn (6),
-- Pull in
pullOut (7),
-- Pull out
maxLoadPt (8),
-- Maximum load point
arrive (9),
-- Arrive
depart (10),
-- Depart
schedAdhOn (11), -- Schedule Adherence On
schedAdhOff (12), -- Schedule Adherence Off
rtAdhOn (13),
-- Route Adherence On
rtAdhOff (14),
-- Route Adherence Off
-- 15-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
intentionallyLeftBlank (247),
-- (not used)
deletedByDevice
(248),
-- (reset to null)
dataUnavailable
(249),
illegalCalculation
(250),
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-13
valueOutOfRange
(251),
deviceMalfunction
(252),
dataExpired
(253),
dataSupressedForSecurityOrPrivacy
unspecified
(255)
} (0..255)
-- no value returned
-- data deleted, no longer available
(254),
sch-TripTimePtTime-ID OBJECT IDENTIFIER
::= { schdd 62 }
sch-TripTimePtTime
TCIP-CLASS
::=
{
SCH-TripTimePtTime IDENTIFIED BY sch-TripTimePtTime-ID
WITH DESCRIPTION "The time value associated with a time point for a
particular trip."
}
SCH-TripTimePtTime ::= SCHTIME
sch-TripType-ID OBJECT IDENTIFIER
::= { schdd 63 }
sch-TripType
TCIP-CLASS
::=
{
SCH-TripType IDENTIFIED BY sch-TripType-ID
WITH DESCRIPTION "A classification of the one-way movement of a public
transportation vehicle between two points."
}
SCH-TripType ::= INTEGER {
revenue (1) ,
-- Revenue
pullIn (2),
-- Pull In (from vehicle base)
pullOut (3),
-- Pull Out (to vehicle base)
deadhead (4),
-- Deadhead
extra (5),
-- Extra
standby (6),
-- Standby
garTransfer (7),
-- Garage transfer
roadCall (8),
-- Road call
roadCallReturn (9),
-- Road call return
roadTest (10),
-- Road test
invalidMovement (11),
-- Invalid movement
-- 14-149 reserved
-- 150-245 local use
null
(246),
-- (data is null)
intentionallyLeftBlank (247),
-- (not used)
deletedByDevice
(248),
-- (reset to null)
dataUnavailable
(249),
illegalCalculation
(250),
valueOutOfRange
(251),
deviceMalfunction
(252),
-- no value returned
dataExpired
(253),
-- data deleted, no longer available
dataSupressedForSecurityOrPrivacy
(254),
unspecified
(255)
} (0..255)
sch-TripTypeDescription-ID OBJECT IDENTIFIER
::= { schdd 64 }
sch-TripTypeDescription
TCIP-CLASS
::=
{
SCH-TripTypeDescription IDENTIFIED BY sch-TripTypeDescription-ID
WITH DESCRIPTION "A description of the trip type."
}
SCH-TripTypeDescription ::= FOOTNOTE
-- MESSAGE DEFINITIONS
**
schActivateAnnouncement-ID OBJECT IDENTIFIER ::=
schActivateAnnouncement TCIP-CLASS ::= {
© 2001 AASHTO / ITE / NEMA
{ sch 18
}
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-14
SchActivateAnnouncement IDENTIFIED BY
schActivateAnnouncement-ID
WITH DESCRIPTION
"A message that indicates the requirements for
activating an announcement."
}
SchActivateAnnouncement ::= SEQUENCE {
activation-id
SCH-ActivationID,
announce-duration
SCH-AnnouncementDuration,
announce-location
SCH-AnnouncementLocationID,
announcement
SEQUENCE OF SCH-AnnouncementID
}
schActivateDriver-ID OBJECT IDENTIFIER ::= { sch 19 }
schActivateDriver TCIP-CLASS ::= {
SchActivateDriver IDENTIFIED BY
schActivateDriver-ID
WITH DESCRIPTION
"This message indicates the requirements for
activating a driver message request."
}
SchActivateDriver ::= SEQUENCE {
activation-id SCH-ActivationID,
note
SCH-NoteID
}
schActivateFareZone-ID OBJECT IDENTIFIER ::= { sch 20 }
schActivateFareZone
TCIP-CLASS ::= {
SchActivateFareZone
IDENTIFIED BY
schActivateFareZone-ID
WITH DESCRIPTION
"This message indicates the requirements for
activating a change in fare zone."
}
SchActivateFareZone ::= SEQUENCE {
activation-id SCH-ActivationID,
fare-zone-id
CPT-FareZoneID
}
schActivateSignChange-ID OBJECT IDENTIFIER ::= { sch 21 }
schActivateSignChange
TCIP-CLASS ::= {
SchActivateSignChange
IDENTIFIED BY
schActivateSignChange-ID
WITH DESCRIPTION
"A message that indicates the requirements for
changing a sign."
}
SchActivateSignChange::= SEQUENCE {
activation-id SCH-ActivationID,
sign-location SCH-SignLocationID OPTIONAL,
sign-code-id
SCH-SignCodeID
OPTIONAL
}
schBlockGroup-ID OBJECT IDENTIFIER ::= { sch 2 }
schBlockGroup
TCIP-CLASS ::= {
SchBlockGroup
IDENTIFIED BY
schBlockGroup-ID
WITH DESCRIPTION
"A grouping of blocks based on some common
characteristics such as use common corridor, terminus location or route
direction name."
}
SchBlockGroup ::= SEQUENCE {
block-group-name
SCH-BlockGroupName,
block-id
SEQUENCE OF SCH-BlockID,
note
SCH-NoteID OPTIONAL,
mode
CPT-Mode OPTIONAL,
timetable-version
SCH-TimeTableVersionID
}
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-15
schEvent-ID OBJECT IDENTIFIER ::= { sch 3 }
schEvent
TCIP-CLASS ::= {
SchEvent
IDENTIFIED BY
schEvent-ID
WITH DESCRIPTION
"A message that activates an event at a
specified time, location or both."
}
SchEvent ::= SEQUENCE {
activation-id
SEQUENCE OF SCH-ActivationID,
time-begin
SCH-TimeBegin OPTIONAL,
point
SpPointclass
OPTIONAL,
activation-type
SEQUENCE OF SCH-ActivationType OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL
}
schMasterSchedule-ID OBJECT IDENTIFIER ::= { sch 4 }
schMasterSchedule TCIP-CLASS ::= {
SchMasterSchedule IDENTIFIED BY
schMasterSchedule-ID
WITH DESCRIPTION
"A table that includes all the time points and
trips on a route. Contained within the route description is the Master
Schedule Header information."
}
SchMasterSchedule::= SEQUENCE {
activation-date
CPT-ActivationDate,
deactivation-date
CPT-DeactivationDate
OPTIONAL,
route
SchRoute,
trip
SEQUENCE OF SchTrip,
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL
}
schMasterScheduleHdr-ID OBJECT IDENTIFIER ::= { sch 5 }
schMasterScheduleHdr
TCIP-CLASS ::= {
SchMasterScheduleHdr
IDENTIFIED BY
schMasterScheduleHdr-ID
WITH DESCRIPTION
"Sequence of time point identifiers and/or their
names used to define the order of time points for all the patterns. This
field is used to build timetables, for exterior signs, etc."
}
SchMasterScheduleHdr ::= SEQUENCE {
time-point-id
SEQUENCE OF SCH-TimePointID
OPTIONAL,
time-point-name
SEQUENCE OF SCH-TimePointName OPTIONAL,
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL
} (WITH COMPONENTS {..., time-point-id PRESENT }|
WITH COMPONENTS {..., time-point-name PRESENT } )
schNote-ID OBJECT IDENTIFIER ::= { sch 6 }
schNote
TCIP-CLASS ::= {
SchNote
IDENTIFIED BY
schNote-ID
WITH DESCRIPTION
"Text which denotes information about a schedule
data element or message."
}
SchNote ::= SEQUENCE {
note-id
SCH-NoteID,
note-designator
SCH-NoteDesignator,
note-message
SCH-NoteMsg,
timetable-version
SCH-TimeTableVersionID
}
schPattern-ID OBJECT IDENTIFIER ::=
schPattern TCIP-CLASS ::= {
© 2001 AASHTO / ITE / NEMA
{ sch 7
}
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-16
SchPattern IDENTIFIED BY
schPattern-ID
WITH DESCRIPTION
"One of multiple outer route segments served by
a single transit route."
}
SchPattern ::= SEQUENCE {
pattern-designator
SCH-PatternDesignator,
pattern-id
SCH-PatternID,
pattern-name
SCH-PatternName
OPTIONAL,
note-id
SCH-NoteID
OPTIONAL,
route-direction
SCH-RouteDirectionName OPTIONAL,
route-id
SCH-RouteID,
time-points
SEQUENCE OF SCH-TimePointID,
stop-points
SEQUENCE OF CPT-StopPointID,
triggers
SEQUENCE OF SCH-ActivationID OPTIONAL,
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
schPieceOfWork-ID OBJECT IDENTIFIER ::= { sch 22 }
schPieceOfWork
TCIP-CLASS ::= {
SchPieceOfWork
IDENTIFIED BY
schPieceOfWork-ID
WITH DESCRIPTION
"A piece of work."
}
SchPieceOfWork::= SEQUENCE {
op-time-types SEQUENCE OF SCH-OperatingTimeType,
time-begin
SCH-TimeBegin,
time-end
SCH-TimeEnd
OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL,
block-id
SEQUENCE OF SCH-BlockID
}
schRoster-ID OBJECT IDENTIFIER ::= { sch 8 }
schRoster
TCIP-CLASS ::= {
SchRoster
IDENTIFIED BY
schRoster-ID
WITH DESCRIPTION
"Daily operator assignments grouped into weekly
assignment packages."
}
SchRoster::= SEQUENCE {
roster-id
SCH-RosterID,
roster-designator
SCH-RosterDesignator,
runs
SEQUENCE OF SCH-RunID,
days
SEQUENCE OF CPT-DayofWeek,
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
schRoute-ID OBJECT IDENTIFIER ::= { sch 9 }
schRoute
TCIP-CLASS ::= {
SchRoute
IDENTIFIED BY
schRoute-ID
WITH DESCRIPTION
"A collection of patterns in revenue service."
}
SchRoute ::= SEQUENCE {
route-designator
SCH-RouteDesignator,
route-id
SCH-RouteID,
route-id-short CC-RouteIDShort
OPTIONAL,
route-name
SCH-RouteName OPTIONAL,
note-id
SCH-NoteID OPTIONAL,
patterns
SEQUENCE OF SCH-PatternID,
schedHdr1
SchMasterScheduleHdr OPTIONAL, --first direction
schedHdr2
SchMasterScheduleHdr OPTIONAL, --second direction
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-17
mode
CPT-Mode OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL
}
schRun-ID OBJECT IDENTIFIER ::= { sch 10 }
schRun
TCIP-CLASS ::= {
SchRun
IDENTIFIED BY
schRun-ID
WITH DESCRIPTION
"The daily pieces of work assigned to a transit
employee."
}
SchRun ::= SEQUENCE {
run-designator SCH-RunDesignator,
run-id
SCH-RunID,
run-id-short
CC-RunIDShort
OPTIONAL,
run-type
SCH-RunType,
day-type
SCH-DayType,
activation
CPT-ActivationDate,
note-id
SCH-NoteID
OPTIONAL,
work
SEQUENCE OF SchPieceOfWork,
mode
CPT-Mode OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
schRunningTimePeriod-ID OBJECT IDENTIFIER ::= { sch 11 }
schRunningTimePeriod
TCIP-CLASS ::= {
SchRunningTimePeriod
IDENTIFIED BY
schRunningTimePeriod-ID
WITH DESCRIPTION
"The division of the operating day within a
schedule or DayType into various periods for the purpose of assigning running
times that reflect the passenger loads and traffic conditions prevalent at
those times."
}
SchRunningTimePeriod ::= SEQUENCE {
begin-time
SCH-TimeBegin,
end-time
SCH-TimeEnd,
mode
CPT-Mode
OPTIONAL,
timetable-version SCH-TimeTableVersionID
OPTIONAL,
day-type
SCH-DayType
OPTIONAL,
date
CPT-CalendarDate OPTIONAL
}
schTimePoint-ID OBJECT IDENTIFIER ::= { sch 12 }
schTimePoint
TCIP-CLASS ::= {
SchTimePoint
IDENTIFIED BY
schTimePoint-ID
WITH DESCRIPTION
"A point at which time is measured to create
trips."
}
SchTimePoint ::= SEQUENCE {
timepoint-id
SCH-TimePointID,
timepoint-designator SCH-TimePointDesignator,
point
SpPointclass,
timepoint-name
SCH-TimePointName
OPTIONAL,
timepoint-name-short
SCH-TimePtNameShort
OPTIONAL,
note-id
SCH-NoteID
OPTIONAL,
stoppoints
SEQUENCE OF CPT-StopPointID
OPTIONAL,
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
schTimePointInterval-ID OBJECT IDENTIFIER ::=
schTimePointInterval
TCIP-CLASS ::= {
© 2001 AASHTO / ITE / NEMA
{ sch 13
}
Do Not Copy Without Written Permission
NTCIP 1404 v01.02
Page B-18
SchTimePointInterval
WITH DESCRIPTION
IDENTIFIED BY
schTimePointInterval-ID
"The segment between two timepoints."
}
SchTimePointInterval ::= SEQUENCE {
tpi-id
SCH-TimePointIntervalID,
tpi-designator
SCH-TimePointIntervalDesignator,
startPointID
SCH-TimePointID, -- terminus of interval
endPointID
SCH-TimePointID, -- terminus of interval
location
SpRouteclass OPTIONAL, --may default to line
class
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
schTimeTableVersion-ID OBJECT IDENTIFIER ::= { sch 14 }
schTimeTableVersion
TCIP-CLASS ::= {
SchTimeTableVersion
IDENTIFIED BY
schTimeTableVersion-ID
WITH DESCRIPTION
"The version of a time table generated by the
scheduling/runcutting module."
}
SchTimeTableVersion ::= SEQUENCE {
timetable-version-id
SCH-TimeTableVersionID,
timetable-version-name
SCH-TimeTableVersionName,
activation-date
CPT-ActivationDate
OPTIONAL,
deactivation-date
CPT-DeactivationDate
OPTIONAL,
agency-id
CPT-AgencyID
OPTIONAL
}
schTrip-ID OBJECT IDENTIFIER ::= { sch 15 }
schTrip
TCIP-CLASS ::= {
SchTrip
IDENTIFIED BY
schTrip-ID
WITH DESCRIPTION
"A one way movement of a transit vehicle in revenue
service between two points."
}
SchTrip::= SEQUENCE {
trip-id
SCH-TripID,
service-type
SCH-ServiceType,
day-type
SCH-DayType,
route-id
SCH-RouteID,
patterns
SEQUENCE OF SCH-PatternID
OPTIONAL,
run-id
SCH-RunID
OPTIONAL,
block-id
SCH-BlockID
OPTIONAL,
trip-type
SEQUENCE OF SCH-TripType
OPTIONAL,
trip-timepoint-times SEQUENCE OF SCH-TripTimePtTime,
event
SEQUENCE OF SchEvent OPTIONAL,
note
SCH-NoteID OPTIONAL,
mode
CPT-Mode OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL
}
schTripTimePoint-ID OBJECT IDENTIFIER ::= { sch 16 }
schTripTimePoint TCIP-CLASS ::= {
SchTripTimePoint IDENTIFIED BY
schTripTimePoint-ID
WITH DESCRIPTION
"Time at a timepoint on a trip."
}
SchTripTimePoint ::= SEQUENCE {
timepoint-id
SCH-TimePointID
OPTIONAL, -- Indicative
timepoint-designator SCH-TimePointDesignator
OPTIONAL, -Indicative
trip-timepoint-time SCH-TripTimePtTime,
Do Not Copy Without Written Permission
© 2000 AASHTO / ITE / NEMA
NTCIP 1404 v01.02
Page B-19
note
SEQUENCE OF SCH-NoteID,
trip-timepoint-attr SCH-TripTimePtAttribute
OPTIONAL,
mode
CPT-Mode
OPTIONAL,
timetable-version
SCH-TimeTableVersionID OPTIONAL
} ( WITH COMPONENTS {..., timepoint-id PRESENT} |
WITH COMPONENTS {..., timepoint-designator PRESENT} )
schVehicleAssign-ID OBJECT IDENTIFIER ::= { sch 17 }
schVehicleAssign TCIP-CLASS ::= {
SchVehicleAssign IDENTIFIED BY
schVehicleAssign-ID
WITH DESCRIPTION
"The work of a vehicle from the time it leaves
the vehicle base (SchVehicleBase) until its next return. Alias: Block."
}
SchVehicleAssign::= SEQUENCE {
block-id
SCH-BlockID,
block-id-short
CC-BlockIDShort
OPTIONAL,
block-designator
SCH-BlockDesignator
OPTIONAL,
block-name
SCH-BlockName
OPTIONAL,
pullout-time
SCH-PulloutTime
OPTIONAL,
pullin-time
SCH-PullinTime
OPTIONAL,
pullOut-location SpPointclass OPTIONAL, --refers to the pull-out
location
pullIn-location
SpPointclass OPTIONAL, --refers to the pull-in
location
day-type
SCH-DayType,
trips
SEQUENCE OF SCH-TripID,
ptv-type
CPT-PTVehicleType
OPTIONAL,
agency
CPT-AgencyID
OPTIONAL,
ptv-base
CPT-PTVehicleBaseName
OPTIONAL,
organizational-unit CPT-OrganizationalUnitID
OPTIONAL,
note
SCH-NoteID
OPTIONAL,
timetable-version
SCH-TimeTableVersionID
OPTIONAL
}
END
© 2001 AASHTO / ITE / NEMA
Do Not Copy Without Written Permission