Terminology
In order to better understand the various explanations the common ROB-Net terminology is explained in this section. The listing below is ordered alphabetically.
Component - These are the building blocks of the new hierarchical structure ROB-Net uses to express activities, concepts and more. Simple examples are the mileage- and hours read components used to communicate the mileage or hours clocked on a vehicle. More complex examples are the new tire activities with many possible subcomponent combinations: a component for profile depth and tire specifications, a component for a specific surcharge, etcetera.
A component can be identified by its ROB-code, operation code, operation type code, reason code and its parent component. This last property highlights the new hierarchical data structure solution employed by the new 319x ROB-code range: the component relationship to other components are part of its semantic meaning.
Contract - A unique set of rules belonging to a specific object in ROB-Net. These rules describe what type of maintenance, repair, tire or even relief vehicle components are allowed by the lessor owning the specific vehicle the contract belongs to. It is imperative to understand that the contract is the culmination of all the lessor configurations applicable to an object and supplier combination and that the lessor is free to change this ruleset at any time. I.e. a contract might be different for different suppliers depending on specific settings done by the lessor.
Damage Service Request - Used to refer to a request which only contains damage related lines. This term is also known as "schade werkopdracht", or "SWO" in short. No API version currently supports these, only the ROB-Net web application supports these through the button "Schade" on the page "Overzicht aanvragen".
Line - A line, or sometimes fully qualified as service request line, is a special type of component. The special feature is that it is the direct descendant of a service request and is responsible for describing a general planned activity and/or concept related to an object.
Object - A synonym for a lessor owned vehicle. It usually refers to the physical vehicle and the associated contract belonging to it. An object can either be active or inactive. When an object is active it is associated with a single lessor, but when it is inactive multiple lessors may be associated with it. This occurs when object ownership transfers from one lessor to another.
Operation - A two part code: the first is a two digit code indicating the mutation applied, the second is the optional type code used to further specify the meaning of the first code. When the first code is not required the operation is omitted for subcomponents. It is never omitted for lines.
Reason - A two numbered code indicating the reason or cause for the presence of a component. At times this reason is not necessary: for lines this is indicated by a value of 99, whilst for subcomponents this code will be omitted.
Relief Vehicle Request - Used to refer to a request pertaining to the deployment of replacement transport for an object undergoing maintenance or repairs for an extended period of time. This term is also known as "Vervangend Vervoer aanvraag", or "VV" in short. The term used for this type of request in this API is rental vehicle request.
Rental Vehicle - Used to refer to components associated with the deployment of replacement transport for an object undergoing maintenance or repairs for an extended period of time. In the past this used to be a separate type of request, but now it is part of a service request.
Repair and Maintenance - Refers to a subset of components possible in a service request. These, unsurprisingly, contain all general repair and maintenance components from ROB-Net, such as replacing a leaking headlight or changing engine fluids. This term is also known as "Reparatie en Onderhoud", or "RO" in short.
Request - Used to refer to either a service request or a relief vehicle request. A request always belongs to a specific object and a specific lessor.
ROB-code - A four numbered code describing a particular activity or concept that a supplier can apply to an object. Together with a operation- and reason code this formed the predecessor of the new components. For example, the ROB-code 5611 means "fog light". With the operation code 01 "replace" and the reason code 12 "leak" it forms the action of replacing a fog light because it is leaking. This term was previously known as "Activity Code".
Service Level - A set of variables, such as agreements, configured by the supplier and optionally the service level cluster administrator.
Do note that the configured variables are not a binding contract. The supplier is free to submit service requests containing values that are in conflict with the applicable service level (agreement) for the object.
The default service level is a special type of agreement that functions as a set of fallback values, so called "standaardtarieven" and others, for when no agreement is applicable to the current situation.
Service Level Agreement - An agreement between the supplier (group) and lessor covering repair and maintenance rates, tires rates, discounts and more. Agreements may be on the basis of just a supplier and lessor relation or based upon the supplier, object vehicle make (dealership) and lessor.
Service Level Agreement Cluster - A group of suppliers managed by an administrator in order to share their service level agreements (SLAs) configuration. The cluster administrator is a special type of user known as the "Groepsgebruiker Organisatie", "GGO" in short.
Service Request - Used to refer to a request which only contains repair and maintenance and tire related lines. This term is also known as "Werkopdracht aanvraag", or "WO" in short. Since API version 2 it now also supports rental vehicle lines.
Subcomponent - A special type of component which is always a child of another component. A subcomponent is usually used to further specify a particular concept introduced by its parent component.
Tires - Refers to a subset of components possible in a service request. These contain all components related to tires, such as replacing worn tires or swapping tires for a different season. This term is also known as "Banden", or "B" in short.