Optibus

S-091-V1-EN This article explains the Schedule format and defines all the fields used in it. You can upload a schedule into Optibus using this format, or export an existing one from Optibus in this format:

The following are options for event types:

Pre_trip – fixed time for the driver and vehicle before the start of a duty

Post_trip – fixed time for the driver and vehicle after the end of a duty

depot_pull_out – non-service trip from the depot

depot_pull_in – non-service trip to the depot

deadhead – non-service trip between two service trips

sign_in\sign_off – fixed time for the driver before the start\end of a duty

split – specifies a split break (unpaid break\compensated break)

- Pre_trip – fixed time for the driver and vehicle before the start of a duty
- Post_trip – fixed time for the driver and vehicle after the end of a duty
- depot_pull_out – non-service trip from the depot
- depot_pull_in – non-service trip to the depot
- deadhead – non-service trip between two service trips
- standby – a paid break
- service_trip 
- sign_in\sign_off – fixed time for the driver before the start\end of a duty
- split – specifies a split break (unpaid break\compensated break)

Excel schedule format

Optibus.com

Academy

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Field Name	Explanation	Required	Comments
Duty id	Unique duty identifier	For duty schedule/full schedule
Vehicle Block Id	Unique vehicle block identifier	Yes
Event Type	Specifies the event type	Yes
Description	General description of the event	Yes	For Layover - you will see the defined break name as in the preferences. For Taxis - in/out representing to and from the depot and to/from represents a taxi to a changeover, split or break.
Trip Id	Unique identifier for service trips	Only for service trips
Route Id	A unique route id (route catalog number, direction and alternative)	Only for service trips
Sign	Route sign number	Only for service trips
Direction	The direction the trip is headed for	Only for service trips
Alternative	The alternative describes a different pattern under the same route sign	Yes	(0 if not relevant)
Day Offset	1 if after midnight, 0 if not	Yes
Start Time	Departure time of event	Yes
End Time	Arrival time of event	Yes
Boarding Time	(0 if not relevant/available. Do not include for non-service trips)	Yes
Origin Stop Id	Origin station identifier of an event	Yes
Origin Stop Name	Origin station name of an event	No
Destination Stop Id	Destination station identifier of an event	Yes
Destination Stop Name	Destination station name of an event	No
Required Vehicle Type	Vehicle type identifier for the vehicle type the trip requires	No
Actual Vehicle Type	The actual vehicle type identifier that performs the trip in the schedule	Yes	Must be a vehicle type that appeared as allowed vehicle type for this trip in the dataset
Distance	The length of the event	No	Preferred to be included, must match value in dataset
First Stop Name	Not needed	No
Last Stop Name	Not needed	No
Overlap		No
Days	The event the day is valid on	Yes	Concatenation of operational days; 1 for Sunday, 2 for Monday and so on.
Pref Group	The allocation of the event to the pref group from the preference configuration	No
Service Groups	The combination of days of the week the service is relevant for	No	Concatenation of operational days; 1 for Sunday, 2 for Monday and so on.