Wiki page content

ID@URI

ID@URI was initially devised by the DIALOG research project of the Helsinki University of Technology as a universal identifier format for identifying and linking tangible objects ("things") to their information sources on the Internet (the "Internet of Things").

Intelligent Products

Several propositions for how to define and classify intelligent products have been made in the past. This definition is based on the survey article on Intelligent Products by Meyer et al. (2009).

GUPI

GUPI is an acronym for 'Globally Unique Product Identifier'.

Device Interoperability Layer

The PROMISE Device Interoperability Layer provides the mechanism by which devices can be automatically discovered by the PROMISE Data Services (middleware) layer.

Application Specific PEID

The Application Specific PEID extends the PROMISE Core PEID by a PEID-specific interface. Access to data is not limited to key-content compositions, but the Application Specific PEID may provide a semantic method interface to read or write portions of the content of the PEID.

PROMISE Core PAC

The PROMISE Core PAC (Core PEID Access Container) is a functional representation of a collection of PROMISE Core PEIDs. The Core PAC provides networking functionality to communicate with the backend via the PROMISE Data Services (middleware) layer.

PROMISE Core PEID

The PROMISE Core PEID is an identification, data collection and storage system that is, at least partially, attached to a product to provide lifecycle monitoring and management. Note that the Core PEID does not provide information to the backend directly.

PROMISE PEID Grouping

Five PEID groups have been defined, which include all PEID types which can be found in the PROMISE demonstrators, and will be just as applicable to other future application scenarios. The evolution of these groups is described below. The five groups are defined as follows:

Type 0 PEID: Identifier-only PEID.

Device Controller

A PROMISE Device Controller (DC) provides the interface function between components that can support the PROMISE Messaging Interface (PMI) and those which cannot. One example would be when dealing with “simple” PEIDs that do not have any significant processing power (see PROMISE PEID Grouping for the list of PEID capabilities).

Closed Loop Lifecycle Management (CL2M)

Closed Loop Lifecycle Management (CL2M) is a natural development and extension of PLM (Product Lifecycle Management).

Syndicate content

New!

John Stark on cl2m.com!

 

Read his newsletter online.