ISO/TS 15143-3:2020 土木機械と移動式道路建設機械—職場のデータ交換—パート3：テレマティクスデータ | ページ 6

3.1.1

caution codes referencing number

ISO/IEC symbol registration number as defined in ISO 7000 and referenced in ISO 6405-1 and ISO 6405-2.

Note 1 to entry: Caution codes referencing numbers are returned from the telematics provider (3.1.18) server and refer to standardized symbols representing various conditions present on EMM and mobile road construction machinery.

3.1.2

construction worksite

location of the operation of a fleet of mobile equipment generally identified as construction machines ここで, the machines are used to perform work

3.1.3

customer application

end user (3.1.7) or assigned third-party developer application

3.1.4

data element

instance of data transmitted by the OEM server to the customer application (3.1.3) adhering to the definition of the quantity or condition described by Clause 11 of this document

3.1.5

discoverability

requirement that the data be stored in such a manner that it can be accessed if necessary

3.1.6

endpoint

address or connection point to the provider’s server for a specific API method

Note 1 to entry: Endpoints are associated by a URL.

3.1.7

end user

organization owning or operating the mobile machinery or both

Note 1 to entry: The end user utilizes the telematics data for the purpose of managing the tasks associated with work performed on a construction worksite (3.1.2) .

3.1.8

fault code

set of codes unique to each OEM related to diagnostic trouble codes as defined in SAE J1939-73

Note 1 to entry: Fault codes are defined by the OEM and might not be standardized. The customer application (3.1.3) developer needs to obtain fault code definitions from each OEM.

3.1.9

Internet media-type

two-part identifier for file formats on the Internet

3.1.10

link

element to allow the customer application (3.1.3) to be directed to additional data or resources

3.1.11

make code

alphabetic string representing the OEM of a specific piece of equipment

3.1.12

model

alphanumeric string representing the machine form type and series as defined by the OEM

3.1.13

namespace

set of symbols that are used to organize objects of various kinds, so that these objects may be referred to by name

3.1.14

namespace URL

uniquely named elements and attributes in an XML document

Note 1 to entry: Namespaces (3.1.13) are defined in a W3C recommendation. An XML instance might contain element or attribute names from more than one XML vocabulary.

3.1.15

request

HTTP request to retrieve a complete information set

Note 1 to entry:"Request" can be of one or more HTTP request(s)."

Note 2 to entry: “Request” can be for one or multiple pages.

Note 3 to entry: Fleet snapshot request is a request to retrieve all (or subset) pages for the fleet.

Note 4 to entry: Equipment snapshot request is a request to retrieve all equipment snapshot data.

Note 5 to entry: Time series (3.1.19) request is a request to retrieve all details (or subset) of a piece of equipment.

3.1.16

serial number

alphanumeric string defined by the OEM identifying a specific piece of equipment

Note 1 to entry: The serial number is generally the PIN as defined in ISO 10261.

3.1.17

snapshot time

date and time at which the snapshot of the fleet was created

3.1.18

telematics provider

OEM or third party providing telematics equipment or services

3.1.19

time series

sequence of data points, typically consisting of successive measurements made over a period of time

Note 1 to entry: Examples of a time series would be the geospatial position of a piece of equipment or the set of fault codes (3.1.8) generated by a piece of equipment over a period of time.

3.1.20

version

integer that is used to distinguish different editions of the contract

3.1.21

XML declaration

processing instruction that identifies the document as being XML

Note 1 to entry: All XML documents should begin with an XML declaration, which should be situated at the first position of the first line in the XML.

3.1.22

resource owner

equipment/fleet owner or end-user