15.11.2012 Views

icegov2012 proceedings

icegov2012 proceedings

icegov2012 proceedings

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

service level agreements. The interoperating information systems<br />

desire comprehensive, understandable, and coherent re-adaptation<br />

of business processes.<br />

Judicial aspects of interoperability are sparsely described by many<br />

[3, 8, 22-23, 28, 41, 49] as an important factor affecting the<br />

Sub-layers Description Constructs<br />

Policy<br />

Enterprise<br />

Architecture<br />

Business<br />

Process<br />

Judicial<br />

Governance<br />

Economical<br />

This layer deals with<br />

back-office procedures<br />

and processes between<br />

the interoperating<br />

systems from policy<br />

perspectives for clear,<br />

transparent, and truly<br />

interpretable exchange<br />

of information by<br />

sender as well as<br />

receiver [41, 47].<br />

Enterprise architecture<br />

represents wide-spread<br />

areas of public<br />

organizations that can<br />

be effective to resolve<br />

interoperability<br />

conflicts [40] as a mean<br />

to measure the basic<br />

information.<br />

Business process deals<br />

with the alignment of<br />

business processes and<br />

procedures, valuecreation,<br />

monitoring,<br />

controlling, and long<br />

and short term<br />

agreements.<br />

Judicial layer reflects<br />

the organizational laws<br />

and regulations,<br />

constitutional and legal<br />

restraints, and<br />

organizational safety<br />

and security issues that<br />

affect the interaction of<br />

information systems.<br />

Governance<br />

mechanisms determine<br />

how communication,<br />

responsibilities, and<br />

decision-making<br />

structures are<br />

formalized [26, p.2307].<br />

Economic layer<br />

concerns the issues that<br />

limit the overarching<br />

scope of<br />

interoperability.<br />

1. Context and<br />

demarcation<br />

s<br />

2. Collaboratio<br />

n<br />

3. Policies<br />

4. Standards<br />

5. Formal<br />

communicat<br />

ion<br />

6. Human<br />

resource<br />

Formal<br />

7. Processes<br />

and<br />

procedures<br />

alignment<br />

8. Service level<br />

agreements<br />

9. Laws and<br />

regulations<br />

10. Constitution<br />

al restrains<br />

11. Political<br />

commitment<br />

12. Jurisdictiona<br />

l regulations<br />

13. Change<br />

management<br />

14. Environmen<br />

t and ethics<br />

15. Financial<br />

constraints<br />

overall maturity of interoperability. This sub-layer discusses the<br />

219<br />

law and regulation and constitutional restrains that affect the<br />

maturity of interoperability. Goldkuhl [16, p-4] describes the<br />

judicial interoperability as “congruence between different laws<br />

and regulations”. According to Janssen and Scholl [28] the<br />

governance in public organizations is differentiated by the wellorganized<br />

and cogent interoperation among organizational<br />

mechanisms, as long as these mechanisms guide in the correct<br />

direction.<br />

Table 1 Organizational sub-layers and measurement constructs<br />

Janssen and Joha [26, p-2307] explain that the “governance<br />

mechanisms determine how communication, responsibilities, and<br />

decision-making structures are formalized”. Measures to assess<br />

the maturity of judicial sub-layer of organizational interoperability<br />

include political commitment, jurisdictional regulations, and<br />

change management. Finally, we define the economical sub-layer<br />

of interoperability, which is discussed quite often in literature but<br />

rarely incorporated in maturity models and frameworks. This sublayer<br />

describes the financial issues of organization interoperability<br />

that restricts the overarching purview and affects the maturity e.g.<br />

return on investment. Based on the literature review of<br />

organizational interoperability and interoperability maturity<br />

models and frameworks in Section 2 we derived the sub-layers of<br />

organizational interoperability as discussed in Section 3. In order<br />

to briefly understand the importance and classification of these<br />

sub-layers of organizational interoperability, we will discuss each<br />

measurement construct shown in Table 1 in details.<br />

3.2 Measurement Constructs Organizational<br />

Interoperability<br />

In this subsection the constructs are further detailed and refined to<br />

enable the assessment in real-life situations.<br />

1. Context and demarcation. Interoperability requires clear and<br />

distinctive interoperation between information systems, processes,<br />

organizations, and employees. According to Strang, Linnhoff-<br />

Popien et al. [44, 45], clear and distinctive contextual<br />

interrelationship and specifics help to assess the interoperability<br />

compatibility and substitutability. Although there is an informal<br />

consensus about the context and demarcations of technical<br />

interoperability, the contextual definitions, goals, objectives,<br />

ontologies, and demarcations of organizational interoperability is<br />

hardly discussed in literature. This measure gives a reflection of<br />

the level of to-the-point clearness and distinctiveness of<br />

organizational interoperability [32].<br />

2. Collaboration. Inter and intra-organizational interactive and<br />

willing full working relationship in public organizations [32],<br />

where the shared goals, and roles and responsibilities are<br />

recognized to support organizational interoperability [9].<br />

Although the organizational framework can be distinct in nature,<br />

the collaboration is essential for organizational interoperability.<br />

This measure determines the level of organizational collaboration.<br />

3. Standards. Although policies and standard are two separate<br />

measures, their description and implications are somewhat interrelated.<br />

Standards are necessary for organizational interoperability<br />

as majority of maturity models and frameworks are still<br />

conceptual. In our view, standards are essential to advance<br />

organizational interoperability. They can describe the conceptual<br />

settlements between the concerned interacting quarters in subtle<br />

agreed documented format in consultation with recognized<br />

standardization bodies [52].

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

Saved successfully!

Ooh no, something went wrong!