Relationships

The table below lists the forms of relationships that comprise the Enterprise View of ARC-IT.

Coordination Name Description
Acquisition Agreement An agreement where one party agrees to provide a system (hardware and or software) to another party, typically in exchange for compensation.
Application Interface Specification The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Application Usage Agreement An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Device Placement and Operations Agreement An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity.
Device Usage Agreement Agreement between the owner of a device and an operator of the device, granting the operator permission to use the device. Specifies who is responsible in the case of device failure and application failure, describes parameters of use including communications provisions, and sets expectations of device and application performance.
Employment Agreement An agreement between an individual and a corporation or government entity, whereupon the individual agrees to provide labor to the corporation/agency, which in turn compensates the employee. Stipulates level of compensation, working conditions, necessary equipment and training and expectations of employee performance.
Equipment Operations Agreement An agreement relating to the use of a specific piece of equipment, where one party agrees to use and/or not tamper with the equipment according to a set of condition.
Expectation of Action An expectation where one party expects another party to take a specific action, typically in response to data or information provided by the first party, but without any formal agreement.
Expectation of Data Provision An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Expectation of Information Provision An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Expectation of Privacy Proxy Services An expectation whereby one party expects to provide data to a second party that proxies that data, provides it to a destination suggested by the first party, and protects the originator's contact information.
Expectation of Roadway Condition Management An expectation whereby one party expects the other to maintain the condition of the roadway environment to a level sufficient for the trusting partner to operate safely.
Expectation of Safety Provision Users of the transportation environment expect that the entities that operate the environment do so in such a way as to preserve and enhance users' safety. This is inherent to current operations, and is an underlying assumption of drivers and pedestrians when accepting information from ITS. This expectation is explicitly noted for connected vehicle applications where this is a new relationship, whereupon the transportation system user expects a transportation service provider to do something (i.e., actuate a system or deliver information) that will protect and/or enhance the user's safety.
Funding Agreement An agreement that documents the funding arragements for ITS projects. At minimum, includes standard funding clauses, detailed scope, services to be performed, and project budgets.
Handshake Agreement An informal agreement typically arrived at in the early stages of a project or regional architecture development. Not suitable for long term operations.
Information Exchange Agreement An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Information Exchange and Action Agreement An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Information Provision Agreement An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Information Provision and Action Agreement An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Installation Agreement An agreement whereupon one party installs a system on behalf of a second party.
Interagency Agreement An agreement between public agencies for operations, services or funding. Documents responsibilities, functions and liability of each party, at minimum.
Interface Description Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator.
Maintenance Data Exchange Agreement An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Master Agreement An agreement that serves as a master agreement for a specific agency, defining how business is done. Includes standard contract and/or legal verbiage. Allows states, cities and other public agencies that do business with the same agencies over and over to have a single agreement that uses smaller agreements (e.g., MOU) to modify or expand the boundaries of the larger agreement to include more specific language.
Memorandum of Understanding An early-stage agreement typically providing minimal detail but demonstrating general consensus. Typically used to expand on an interagency agreement. May also serve as a means to modify a broader Master Funding Agreement, where the master agreement covers various ITS projects and the MOUs specify the scope and differences between the projects.
Operations Agreement An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Presumption of Correct Operation The assumption made by one party that another party operates their device in a similar and correct fashion. Specific to devices in the transportation environment, this assumption is relevant when devices interact, where one party's device receives information from another's. The operator of the device implicitly trusts that the other device is operating according to a similar set of governing rules as its device.
Presumption of Non-Interference The assumption made by one party that another party's device that uses similar resources operates in manner that does not conflict with their device.
Project Blanket Agreement An agreement between all stakeholders involved in a project that covers data provision, information exchange and related actions.
Purchase Agreement An agreement between the current owner of a resource (has the 'owns' role) and a second party to transfer ownership to the second party. The purchase agreement stipulates the rights and responsibilities of all parties with respect to the resource, before and after purchase. It might for example include assignment of liability, define the exchange of capital or other resources, rights to data, re-use and any other consideration or constraint allowed under the law.
Security Credentials License and Usage Agreement An agreement in which a device owner gains access to security credentials, and agrees to protect and use those credentials in accordance with restrictions and safeguards documented in this agreement.
Service Coordination Agreement An agreement between two or more parties that operate similar or geographically adjacent or overlapping services, stipulating coordination, information sharing and other aspects of service provision relevant between these services.
Service Delivery Agreement A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications.
Service Package Blanket Agreement An agreement between all stakeholders involved in a service that covers data provision, information exchange and related actions.
Service Usage Agreement An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Shared Operations Agreement An agreement between any agency involved in the funding, operation, maintenance or right-of-way use of another public or private agency's assets. Documents responsibilities for all activities associated with shared systems being operated and/or maintained. May assign responsibilities and liabilities related to joint contracting and/or procurement activities, define mechanisms for standardizing operating procedures of shared assets, define joint training programs and describe real-time and archived data sharing.
System Maintenance Agreement An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
System Monitoring Agreement An agreement in which a connected vehicle device owner grants permission for another entity to remotely monitor the status of applications and services operating on that device.
System Usage Agreement An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Unspecified Unspecified agreement used as a placeholder for user-defined agreements, to be used in special circumstances with tools (RAD-IT, SET-IT) only.
Vehicle Data Access Agreement An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data.
Vehicle Operating Agreement An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Verification Agreement An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Warranty A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.