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 ... s that do not have any significant processing power (see PROMISE PEID Grouping for the list of PEID capabilities). In such a ...

Wiki page - potted1 - 4 Feb 2011 - 3:18pm - 0 comments - 0 attachments

The PROMISE architecture identifies the PROMISE Messaging Interface (PMI) as the solution to the requirement for a generalized interface. Thus, the PROMISE Messaging Interface (PMI) is the common communication interface between ...

Wiki page - potted1 - 4 Feb 2011 - 3:15pm - 0 comments - 0 attachments

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 communicating and ...

Wiki page - potted1 - 4 Feb 2011 - 3:13pm - 0 comments - 0 attachments

PROMISE Architecture Series The purpose of the PROMISE architecture is to provide a secure infrastructure for the exchange and ... available to the beginning-of-life phase, (BOL) The PROMISE architecture defines standards, interfaces and components. These allow ...

Wiki page - potted1 - 9 Nov 2009 - 12:20pm - 0 comments - 5 attachments

The Application Specific PEID extends the PROMISE Core PEID by a PEID -specific interface. Access to data is not ... how they are configured. This is entirely irrelevant to PROMISE Data Services , but reader configuration is important in practice. The ...

Wiki page - potted1 - 4 Feb 2011 - 3:17pm - 0 comments - 0 attachments

... which include all PEID types which can be found in the PROMISE demonstrators, and will be just as applicable to other future ... for these, but for some it might be simpler to embed the PROMISE Data Services (middleware) connectivity. Type 4 PEID : ...

Wiki page - potted1 - 4 Feb 2011 - 3:11pm - 0 comments - 0 attachments

The PROMISE Device Interoperability Layer provides the mechanism by which devices can be automatically discovered by the PROMISE Data Services (middleware) layer. It supports the description of the ... Layer must support a service-oriented view of the PROMISE Core PAC , i.e. the Core PAC displays its functionalities in a ...

Wiki page - potted1 - 4 Feb 2011 - 3:17pm - 0 comments - 0 attachments

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

Wiki page - potted1 - 4 Nov 2009 - 9:52am - 0 comments - 0 attachments

The PROMISE DSS utilises data from the PDKM in order to make decisions ... A loosely coupled DSS can access the PDKM system via PROMISE Data Services , and, though it does not have same direct access as a ... or be distributed between different nodes. PROMISE has developed, and also provides guidelines for the development of ...

Wiki page - potted1 - 3 Feb 2011 - 5:02pm - 0 comments - 0 attachments

The PROMISE PDKM is an extremely important component of a PROMISE application. Its purpose is to systematically integrate and manage data ... support information, it can be made available to the PROMISE Decision Support System . The ultimate goal of the PDKM is to ...

Wiki page - potted1 - 4 Feb 2011 - 3:09pm - 0 comments - 0 attachments