15.11.2012 Views

icegov2012 proceedings

icegov2012 proceedings

icegov2012 proceedings

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Heterogeneous Enterprise Networks and their Applications<br />

(ATHENA) comprises of five levels i.e. performed, modeled,<br />

integrated, interoperable, and optimizing. ATHENA intended to<br />

assess the interoperability in enterprise domain using EIMM. The<br />

model specifically focuses on both organizational as well<br />

technical aspects of interoperability in enterprise domain [3, 18].<br />

Though the maturity models are developed by different individual<br />

researchers [9, 46], national [11], and international [22, 34]<br />

organizations; none of these models or frameworks discuss<br />

measures to assess the organizational aspects of interoperability.<br />

The stages, levels, and layers are sequentially numbered without<br />

any further guideline about the measurements method or the<br />

measures themselves. Literature reviews of interoperability<br />

maturity models and frameworks suggests that the maturity of<br />

technical interoperability is somewhat achievable due the<br />

established standards and policies, but the aspects of<br />

organizational interoperability e.g. policies, business processes,<br />

financial, and governance are important and need to be addresses<br />

carefully. In other words, some of the organizational aspects are<br />

often described as the barrier of interoperability adoption and<br />

implementation [1, 12, 41].<br />

3. MEASUREMENT APPROACH<br />

Literature review of maturity models and frameworks discussed in<br />

Section 2 gives insight about the importance of organizational<br />

aspects of interoperability, but does not provide sufficient<br />

guideline to measure organizational interoperability. The maturity<br />

models describe interoperability levels in a linear fashion, whereas<br />

these levels are implemented on top of each other in practice.<br />

Although some authors [e.g. 50] argue that the successful<br />

implementation of technical, syntactical, and semantic<br />

interoperability is necessary for organizational interoperability,<br />

whereas others [e.g. 28, 32] suggest that both organizational as<br />

well technical interoperability can be implemented on top of each<br />

other. This paper proposes a two layered measurement instrument<br />

where each layer can be implemented on top of each other.<br />

Organization Layer<br />

• Policy<br />

• Enterprise architecture<br />

• Business process<br />

• Judicial<br />

• Governance<br />

• Economical<br />

Technical Layer<br />

• Syntactic<br />

• Semantic<br />

• Physical infrastructure<br />

Figure 1 Interoperability Measurement Instrument.<br />

Proposed measurement instrument as shown in Figure 1 is based<br />

on the methodology of architecture layers of interoperability by<br />

[28], whereas the selection of layers based on the socio-technical<br />

design approach. Bostrom and Heinen [6] argue that the success<br />

of the organizations depend socio-technical system (STS), where<br />

social system represents people and structure and technical system<br />

218<br />

represents technology and tasks. Measurement aspects of the<br />

technical and organizational interoperability as shown in Figure 1<br />

are derived based on the literature review interoperability maturity<br />

models and frameworks. Janssen and Scholl [28] describe that the<br />

settlements should be reached among various involved partners to<br />

avoid unwanted situations regarding the quality, compatibility,<br />

and extent of information collaboration and interoperation. The<br />

arrows shown in the Figure 1 from top to bottom and bottom to<br />

top of each layer shows that implementation of interoperability<br />

layers is non-linear, which means that each layer can be<br />

implemented independent of each other. Hence, the<br />

interoperability measurement aspects of each layer are relative,<br />

but can be measured independently.<br />

The explanation of technical sub-layers is already clear and well<br />

defined by many organizations as well as individual authors [e.g.<br />

22-23, 28, 32, 49], whereas the organizational interoperability and<br />

the measurement aspects of its sub-layers are hardly discussed in<br />

literature. Therefore, this paper briefly discusses the measurement<br />

aspects of organizational layer and derives the adequate<br />

measuring and benchmarking constructs for each sub-layer.<br />

3.1 Organizational Layer<br />

Organizational factors (e.g. technology adaption, economic<br />

constraints, openness, and back-office cooperation) and<br />

organizational issues (e.g. collaboration, business process, and<br />

coordination) that impact the performance of information systems<br />

are used to describe interoperability [14, 16-17]. Organizational<br />

layer places the foundation for functional infrastructure of public<br />

organizations for collaboration, exchange, and sharing of<br />

information. Table 1 gives short description of each organizational<br />

sub-layer as depicted in Figure1. Interoperability sub-layers<br />

explained in Table 1 are sparsely described in literature, but there<br />

is hardly any discussion about the measures to assess them.<br />

Tolk, Turnitsa et al. [47] describe that the pragmatic<br />

interoperability can reflect the maximum maturity if the<br />

information sharing by the sender as well receiver is translucent,<br />

clear, and truthfully interpretable. Policy sub-layer analyzes the<br />

maturity of organizational aspects and helps to avoid the adverse<br />

effects by identify the limitations. This layer also envisages<br />

personal, environmental, standardization, and policy aspects to<br />

distinguish the types of communication, and embraces the<br />

information exchange intention of sender [28, 39].<br />

For the public organizations aiming to facilitate citizens and<br />

businesses with seamless service delivery, the enterprise<br />

architecture can perform the essential role and provide guidance to<br />

address organizational issues [19]. Enterprise architecture of a<br />

public organization provides systematic understanding of basic<br />

elements describing existing and anticipated environment [5].<br />

Thus, enterprise architecture is useful to measure the basic<br />

information about organizational elements. Tough enterprise<br />

architecture encapsulates majority of organizational aspects, we<br />

only focus on interoperability related measures. Thus, the sublayer<br />

enterprise architecture is used to measure the basic<br />

information about human resource and formal communication.<br />

Interoperability in public organizations aims to improve the<br />

service provision by advancing the business processes and<br />

procedures for citizens, business, employees [32]. The business<br />

process sub-layer in this context measures the processes and<br />

procedures alignment, whereas the processes and procedures for<br />

information exchange and sharing between the collaborating and<br />

interoperating information systems are often reflected by the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!