A reference software architecture for the development of industrial automation high-level applications in the petroleum industry

A classification of software reference architectures: Analyzing their success and effectiveness

“…The INAHL reference architecture [29] is a recently published, classical, facilitation reference architecture designed for multiple organizations in the petroleum industry. It was designed by a research centre in cooperation with one user organization [5].…”

“…Table 6. List of studied reference architectures T G1 C1 C2 C3 D1 D2 D3 D4 LS WRM [18] 1 X X X X X X X X 4 OATH [23] 1 X X X x x X X X 3 OSI RM [31] 1 X X X X X X X X 4 HIF [27] 1 X X X X x X X X 3 CORBA [24] 1 X X X X X X X X 4 FORTIS RSA 2 X X X X X X X X 4 IBM PanDOORA 3 X X X X X X x X 3 WMS RA [17] 3 X X -X x --X 1 INAHL [29] 3 X X x X x X X X 2 MS .NET [20] 3 X X X X X X X X 4 ACHMEA RA [13] 4 X X X X X X X X 4 ABN WAA [12] 4 X X x x X X X X 2 ANSI-SPARC [28] 5 X X X X x X X X 3 ERA [2] 5 X X x X x X X XeSRA [22] 5 X X x X x X X X -AHA [30] 5 X X x X X x X XIn Table 6, we list the values for all reference architectures that we studied. A row in the table shows the type that the reference architecture resembles the most (indicated in the "T" column) and its values for each of the sub-dimensions in our framework.…”

Towards a Cyber-Physical Architecture for Industrial Systems via Real-Time Java Technology

“…Urdaneta et al [15] proposed a reference software model in the context of the petroleum industry. The goal of their research was to satisfy the requirements of Industrial Automation High-Level Applications (IAHLAs) which are…”

The interoperability force in the ERP field

“…In these systems, Urdaneta et al (2007) propose an architecture for the development of IAHLAs (Industrial Automation HighLevel Applications), which should fulfil the following extra-functional design criteria, among others: 1) interoperability: the architecture must be based on the standards supported by multiple vendors so that an organisation can choose between several products (e.g., middleware, databases and operating systems) with no effect on their applications; 2) use of existing systems: the architecture must provide mechanisms that allow the applications to access the existing enterprise information systems in the organisation (e.g., message-oriented middleware, transaction-processing monitors and ERP systems). and Blanc et al (2008) describe challenges for manufacturing execution systems (MES), where the control system (the decisional subsystem) is considered the composition of a high-level management system (such as ERP) and a low-level control system.…”