TODS Governance ¶

This page outlines the policies, procedures, and structures that guide the collaborative and transparent development of the Transit Operational Data Standard (“TODS”). The TODS is a critical framework enabling effective dispatching and operations management through a standardized data schema. This document is intended for all members of the TODS Community, including the TODS Board of Directors, TODS Managers, TODS Contributors, and TODS Stakeholders. By clearly defining the principles, roles, and policies, we aim to facilitate the efficient, fair, and responsible advancement of the TODS Project.

Principles ¶

The TODS Governance is designed with the following principles in mind:

Merit

Changes should have a clear purpose.
Consequences of a change should be evaluated from the perspective of different affected stakeholder groups.
Changes should be prioritized by the community.

Openness + Transparency

Discussion and decisions about changes should be publicly noticed and accessible.
Change-making process should be straight-forward and easy to follow.
Change proposals should have a reliable timeline for being decided on and incorporated.
Each change (or bundled set of changes) should be identified by assigning a new version number.

Efficiency

Change-making process should be simple for simple changes.
Complex changes should be made with careful consideration.
Streamlined, purpose-driven change management should be applied to maximize stakeholder efficiency.
Changes should be straightforward to incorporate by existing TODS Stakeholders.
Significant changes, especially those which are not backwards compatible with existing datasets, should be limited in number and in frequency in order to limit the number of times existing processes and tools need to be re-engineered.
A significant change merits a new version number.

Definitions ¶

TODS Project ¶

The TODS Project encompasses:

TODS Specification
TODS Tools
TODS Repository
TODS Documentation
TODS Governance

TODS Governance ¶

Who and how decisions are made about the scope and direction of the TODS Project, including but not limited to the approved roles and responsibilities and the following policies:

TODS Change Management and Versioning Policy
TODS Contributor Agreement
TODS Code of Conduct
TODS Use License

TODS Specification ¶

The data schema documented on the TODS Repository and TODS Documentation for the purposes of representing planned transit operations for use is dispatching and operations management software.

TODS Community ¶

The combined members of TODS Board, TODS Manager, TODS Board Coordinator, TODS Contributors and TODS Stakeholders.

TODS Contributor Agreement ¶

Agreement contributors make when contributing to the TODS Project as documented at: CLA.md

TODS Code of Conduct ¶

Agreement for behavior within the TODS Community which must be abided by by all of TODS Board, TODS Contributors and the TODS Manager and its representatives as documented at code-of-conduct.md

TODS Change Management + Versioning Policy ¶

How content of the TODS Specification may be changed and released as an official TODS version.

TODS Documentation ¶

The text and website (and supporting scripts) which describe the TODS Specification and its purpose and usage located on the TODS Repository.

TODS Repository ¶

The version control repository containing the TODS Specification located at: https://github.com/cal-itp/operational-data-standard

TODS Repository Organization ¶

The version control organization which contains the TODS Repository.

To be migrated

The TODS Repository is currently located with the Cal-ITP GitHub organization but will be migrated as part of the process of transitioning management to MobilityData.

TODS Tools ¶

Any scripts or code released within the TODS Repository Organization.

TODS Use License ¶

The TODS Specification is licensed under the Apache License 2.0 (code) and Creative Commons Attribution 4.0 (sample data, specification, and documentation) as defined in LICENSES file in the GitHub repository.

Roles ¶

Responsibility for the governance of the TODS Project is divided among the following roles as defined here and fulfilled by the following individuals as noted:

Role	Who
TODS Board	Joshua Fabian, Massachusetts Bay Transportation Authority (MBTA) Matthias Gruetzner, INIT Guilhem Hammel, Giro Erik Jensen, Chicago Transit Authority (CTA) Jeffrey Kessler, Keolis Commuter Services
TODS Board Coordinator	Scott Frazier
TODS Manager	MobilityData
TODS Program Manager	Cristhian Hellion, MobilityData
TODS Contributors	TBD
TODS Stakeholders	Anyone interested in or could be directly affected by the TODS Project.

TODS Owner ¶

The TODS Project is collectively owned and overseen by the TODS Board of Directors.

TODS Board of Directors ¶

The TODS Board of Directors (“TODS Board”) governs and collectively owns the TODS Project.

The Board MAY select an individual or organization to serve as the TODS Manager to handle the day-to-day management of the TODS Specification and TODS Project.
The TODS Board MUST execute a memorandum of understanding with the TODS Manager (if one is chosen) that outlines the roles, responsibilities, and limitations of the management role.
The TODS Board MAY change the TODS Manager at any time for any reason.
In the event that there is not an active agreement with an TODS Manager the TODS Board MUST assume the TODS Manager responsibilities.
The TODS Board SHOULD ask the TODS Manager to select a new TODS Program Manager if there is continued failure to perform and meet expectations.
TODS Board membership MUST be determined by the Board Composition Policy.
TODS Board decisionmaking should be consistent with the Board Decisionmaking Policy.

TODS Board meetings and actions.

TODS Board Coordinator ¶

Chosen by the TODS Board, this individual is responsible for coordinating the actions and activities of the TODS Board.

The Board Coordinator MUST schedule, agendize and arrange for Board meetings in consultation with the TODS Board Chair and TODS Program Manager.
The Board Coordinator MUST conduct votes by the TODS Board and document results.
The Board Coordinator MUST communicate with the TODS Manager / TODS Program Manager as needed.

TODS Manager ¶

Responsible for the daily management of the TODS Project at the direction of the TODS Board including the:

TODS Change Management Process,
TODS Repository,
TODS Project resource management, and
Internal and external project communications.
The TODS Manager MAY be an individual or organization.
The TODS Manager MUST assign an individual as the TODS Program Manager.
The TODS Manager MUST communicate the name of the TODS Program Manager to the TODS Board in writing and notify the Board of any change in this assignment in writing.
The TODS Manager SHOULD select a new TODS Program Manager if asked to do so by the TODS Board.

TODS Program Manager ¶

Serves as the main contact between the TODS Board and the TODS Manager.

TODS Contributor ¶

Individuals apply to become Contributors by acknowledging and agreeing to the TODS Contributor Agreement and TODS Code of Conduct.

An TODS Contributor MUST abide by the TODS Code of Conduct or face removal.
An TODS Contributor MAY create issues, discussions, and pull requests in the TODS Repository.
An TODS Contributor MAY vote in decisions on changes to the TODS spec and other aspects of TODS.

TODS Stakeholder ¶

Anyone interested in or could be directly affected by the TODS Project. Interested parties may register for the TODS distribution list.

Document History ¶

Initial Version ¶

Initial release of the TODS Governance document.
Establishment of governance principles, roles, policies, and procedures.