CM-048-V2-EN
The Project Configurations screen is where you set your project’s metadata. Metadata holds crucial information about how your service operates. That can be information for regulatory bodies, duty types and pay for payroll integrations, and other data.
Besides Project Configurations, metadata can also be configured in other places throughout the platform:
The Route tab
The Timetable tab
The Rostering module
In this article, we will go over the metadata setup process in Project Configurations, and provide an overview of the categories of metadata that you can work with.
How to use
While in the Projects view, right-click on the project you want to configure (or hover over the project and click the three dots button to the right) and select Configuration.
You will see a window with a Metadata tab on the left, listing all the categories you can configure. Choose a category, click on it, and click +Add New.
Every metadata instance you create needs a name - you can define it at the top. Then, fill out the rest of the fields required for the category and click Save.
The created instance will show up in a table view. You can create as many instances as needed for your operation.
You can sort the instances in the table by clicking on the column you want to sort them by:
The columns can also be moved left and right. To do so, just click and hold on a column name and drag it to the place in the table that you prefer:
You can choose to hide or show some columns in this view using the Display data drop-down. Click on it and uncheck the boxes next to columns you’d like to hide:
Once done with the configuration, click Save in the Project Configuration window.
Metadata categories
Below you will find a table listing the metadata you can configure in your project. Where available, the names will contain links to relevant articles.
Name | Description | Used in |
This category lets you define different organizations that your buses service and their working and non-working days. | Ticketer | |
In this category you can list all the days in the year that require special services. This can include bank and public holidays. This will later be used with service IDs in the Planning product. | Ticketer | |
Operation Type | Here you can set if a service ID applies to school days, holidays or all days. It is also applied on a service ID level in Planning. This is later used in the Timetable report. | |
Pay Grade | If there are multiple pay grades between different roster groups, they can be defined here and then applied to each group in Rostering. | |
Designation Code | Used in Grampian exports. | |
Pay Value Code | This code is used in Grampian exports. It allows for more granular payment configuration than the Optibus base. It must be defined here then duplicated with a time definition. | |
Job Analysis Code | Assigns a default value for duties without their own job analysis code. If the code is the same as the pay value code, keep the job analysis code blank. | |
Employee Type | An employee type code is used in Grampian exports. It needs to be defined here and then assigned to each roster group in Rostering preferences. | |
Tendered | These codes are used on a trip and stop level in the timeplan. These are required to reclaim money from the Local Authorities and Government for the subsidized routes or portions of trips. | |
Depot Code | All depot codes must be added here to be included and usable across exports. | |
Operator | This metadata category is used for TXC reports and is sometimes checked by third parties. Your organization’s contact details, National Operator Code and various license details should be added here. | |
Registration | Generally, bus operators are required to register their services with the government and the local authorities. |