It can be pronounced either as it is spelled in individual letters P E I D (which is quite a mouthful) or more simply as the English word 'pied'.
The concept of the PEID was first seen in the EU PROMISE project. The primary purpose of the Product Embedded INFORMATION Device (PEID) is to be the link between a product/article/machine/component and its electronic representation in an information system.
As a minimum, it is responsible for uniquely identifying a product or component of a product. In the case of a very simple product, or even a complex product having a requirement for a very high level of security or confidentiality, the PEID may contain only the GUPI (Globally Unique Product ID) of the product.
More commonly, the PEID also provides a means to collect information from the product/component and its environment, either directly or via reference to a backend system. This information may remain on the PEID throughout the lifetime of the product to which it applies. In most cases, some or all of that information may also be transferred to one or more back-end systems. Individual application requirements will determine whether information should be kept only on the PEID, only in the back-end systems, or a combination of both.
As the PEID may not be connected to the backend system all the time, it may provide means of local information storage, until the information can be relayed to the backend system at a later point in time.
The communication with the backend system can either be directly from the PEID or via a PEID reader (Device Controller). This depends to a large extent on the computing power and facilities of the hardware upon which the specific PEID implementation is based.
PEIDs are based on available sensor and communication technologies. They are attached to or are an integral part of various types of products, ranging from small electronic articles to larger items like cars or other heavy vehicles.
Their main task is to sense, capture and save data about the use and maintenance of associated products. If a PEID does not have sufficient computation capacity for implementing the PMI, then it can join the network through a proxy device, such as a DC.
PEID devices can be grouped according to their amount of embedded computing power and network connectivity. The type 4 PEID group is for devices which can support an embedded PMI implementation (or at least a partial PMI implementation). For all other PEID groups, the node consists of the PEID itself and a Device Controller (DC). A highly flexible DC implementation uses the PROMISE Core PAC (Core PEID Access Container) interface that exploits the Universal Plug-and-Play (UPnP) protocol.
See PROMISE PEID Grouping for the list of PEID groups and their capabilities.