Flexible PROMISE Component Architecture

A PROMISE application must include at least one of the following components:

Product Embedded Information Device (PEID)

PROMISE PLM addresses unique items (complete product, sub assembly, component, container or individual), rather than the product type which is more the scope of traditional PLM.

 
The PROMISE PEID is a product’s embedded information device, normally more than a simple identification device, which may be either a physical or logical device implementation. It is an example of an Automatic Identification and Data Capture (AIDC) implementation.
 
Promise PLM embraces all AIDC technologies including RFID, barcode, wireless and sensor technologies, plus all kinds of emerging technologies such as biometrics.
 
Depending on the needs of individual applications, the PEID may be as simple as a barcode or passive RFID transponder which only identifies the item. Other items may justify sophisticated on board data processing devices that can be connected to sensors or actuators on the product. These capture lifecycle events or specific conditions that can impact the product such as temperature or pressure.
 
Data on PEIDs may be accessed via the PROMISE middleware layer, PROMISE Data Services.
 
 
PROMISE Data Services
PROMISE Data Services is the name given to the middleware component of the PROMISE architecture that connects together the different systems in a PROMISE infrastructure, and provides the means for gathering and communicating lifecycle data.
 
PROMISE Data Services integrates PEIDs with applications such as PROMISE PDKM and DSS systems and other backend systems. It also enables system to system communication between different PROMISE systems.
 
PROMISE Data Services enables both device management and communication between system components, acting as the networking layer of the PROMISE  architecture and providing controlled and secure access to relevant information.
Product Data Knowledge Management (PDKM)
The PROMISE PDKM is a very important component of a PROMISE application. It aims to systematically integrate and manage data from all lifecycle phases, creating knowledge from information.
 
The ultimate goal is to integrate data throughout the entire lifecycle from different sources, allowing comprehensive analysis of such data. The more detailed insight on products thus obtained enables the enhancement of operational business processes.
 
The PDKM will incorporate data from PEIDs and other software systems, e.g. legacy CAD, CRM and/or SCM systems that are part of a company’s IT infrastructure. If data from these systems is required for generating specific decision support information, will be made available to the PROMISE DSS system.
 
 
Decision Support System (DSS)
The PROMISE DSS utilises data from the PDKM for making decisions related to an individual entity’s, or series of entities’ different life cycles: beginning, middle and end-of-life.
 
PROMISE has developed and also provides guidelines for the development of algorithms for specific industrial applications to provide decision support for predictive maintenance, diagnosis and analysis of use patterns.
 
Up-to-date and accurate lifecycle information can, for example, have significant influence on residual life decisions regarding individual sub-assemblies or components and positively impact the environment through improved and more efficient recycling or refurbishment decisions. By feeding up-to-date lifecycle information back into design (Design for X) and production (adaptive production), modifications can be made which will have an immediate impact.
 
A closely coupled DSS has direct access to the databases of the PDKM, and is thereby able to access and process the large amounts of information stored in the PDKM. A loosely coupled DSS can access the PDKM system via PROMISE Data Services, and, though it does not have same direct access as a closely coupled DSS, it can be located in the field close to the PEIDs for service and maintenance applications or be distributed between different nodes.