The SUTI standard is a set of documents. The documents and its relations are described in one of these documents – Document relations. Most of these documents are open while Use Cases and SUTI attributes are exclusive to its members. The standard have developed a set of asynchronous XML-messages that can be exchanged between a client and a provider.
The Client is supposed to have access to the travel demands from customers and passengers in its own system. To fulfill these demands the client has contracted one or several Providers.
The Provider have access to vehicles and drivers that will actually perform these travels.
In the demand responsive environment there are many different types of applications for how this can be achieved. SUTI has solutions for them by using different types of standardized messages. All these types of applications has general descriptions in a document called Use Cases.
The Client is encouraged to describe its application in a Self Declaration. As from 2016 SUTI has also set guidelines for how to do such a Self Declaration.
Developing and maintaining the Standard
The developing and maintaining is driven by its members demands. The Technical Committee receives cases from its members. The cases can be either simple attribute cases or bigger projects. In order to start work for bigger projects the Technical Committee needs approval from the board.
The Board will also set the different priorities to projects if there are concurrent needs.
For minor issues, like SUTI-attributes, the Technical Committee may decide promptly. Bigger issues will be part of a remittal process which in most cases also includes presentation in at least one SUTI seminar.
The Board finally decides on a new version of the standard. New versions of SUTI are since a few year ago limited to a yearly version. Thus there is a SUTI 2015 version decided after yearly member meeting in March 2015.