Content deleted Content added
Wendyzinoa (talk | contribs) Industrial lifecycle integration |
Wendyzinoa (talk | contribs) No edit summary |
||
Line 17:
The horizontal scheme can be misleading, however, if it is thought that the cost of intermediate data transformation or the cost of shifting responsibility over business logic can be avoided.<ref name="Integ"/>
'''Industrial lifecycle integration''' is a system integration process that considers four categories or stages of integration: initial system implementation, engineering and design, project services, and operations.<ref>{{Cite web|title=The Value of Data-Centric Execution Architecture in System Integration Frameworks for Industrial Energy Assets|url=https://www.vistaprojects.com/system-integration/|url-status=live|website=Vista Projects Limited}}</ref> This approach incorporates the requirements of each lifecycle stage of the industrial asset when integrating systems and subsystems. The key output is a standardized data architecture that can function throughout the life the of the asset.
A '''common data format''' is an integration method to avoid every adapter having to [[data conversion|convert data]] to/from every other applications' formats, [[Enterprise application integration]] (EAI) systems usually stipulate an application-independent (or common) data format.<ref>{{Citation|title=Aircraft/Store Common Interface Control Document Format Standard|publisher=SAE International|doi=10.4271/as5609a}}</ref> The EAI system usually provides a data transformation service as well to help convert between application-specific and common formats. This is done in two steps: the adapter converts information from the application's format to the bus' common format. Then, semantic transformations are applied on this (converting zip codes to city names, splitting/merging objects from one application into objects in the other applications, and so on).
| |||