A conceptualization of complexity in IS-driven organizational transformations

Organizational transformations reliant on successful ICT system developments (continue to) fail to deliver projected benefits even when contemporary governance models are applied rigorously. Modifications to traditional program, project and systems development management methods have produced little material improvement to successful transformation as they are unable to routinely address the complexity and uncertainty of dynamic alignment of IS investments and innovation. Complexity theory provides insight into why this phenomenon occurs and is used to develop a conceptualization of complexity in IS-driven organizational transformations. This research-in-progress aims to identify complexity formulations relevant to organizational transformation. Political/power based influences, interrelated business rules, socio-technical innovation, impacts on stakeholders and emergent behaviors are commonly considered as characterizing complexity while the proposed conceptualization accommodates these as connectivity, irreducibility, entropy and/or information gain in hierarchically approximation and scaling, number of states in a finite automata and/or dimension of attractor, and information and/or variety.

How to guarantee compliance between workflows and product lifecycles?

Product Lifecycle Management (PLM) systems are widely used in the manufacturing industry. A core feature of such systems is to provide support for versioning of product data. As workflow functionality is increasingly used in PLM systems, the possibility emerges that the versioning transitions for product objects as encapsulated in process models do not comply with the valid version control policies mandated in the objects’ actual lifecycles. In this paper we propose a solution to tackle the (non-)compliance issues between processes and object version control policies. We formally define the notion of compliance between these two artifacts in product lifecycle management and then develop a compliance checking method which employs a well-established workflow analysis technique. This forms the basis of a tool which offers automated support to the proposed approach. By applying the approach to a collection of real-life specifications in a main PLM system, we demonstrate the practical applicability of our solution to the field.

Improving business through people and process

Recent information systems development using agile project management has yielded a 50% reduction in effort, together with significant improvements in organisational skills, productivity, quality and business satisfaction.

Detecting approximate clones in business process model repositories

Empirical evidence shows that repositories of business process models used in industrial practice contain significant amounts of duplication. This duplication arises for example when the repository covers multiple variants of the same processes or due to copy-pasting. Previous work has addressed the problem of efficiently retrieving exact clones that can be refactored into shared subprocess models. This article studies the broader problem of approximate clone detection in process models. The article proposes techniques for detecting clusters of approximate clones based on two well-known clustering algorithms: DBSCAN and Hi- erarchical Agglomerative Clustering (HAC). The article also defines a measure of standardizability of an approximate clone cluster, meaning the potential benefit of replacing the approximate clones with a single standardized subprocess. Experiments show that both techniques, in conjunction with the proposed standardizability measure, accurately retrieve clusters of approximate clones that originate from copy-pasting followed by independent modifications to the copied fragments. Additional experiments show that both techniques produce clusters that match those produced by human subjects and that are perceived to be standardizable.

Fast and accurate business process drift detection

Business processes are prone to continuous and unexpected changes. Process workers may start executing a process differently in order to adjust to changes in workload, season, guidelines or regulations for example. Early detection of business process changes based on their event logs – also known as business process drift detection – enables analysts to identify and act upon changes that may otherwise affect process performance. Previous methods for business process drift detection are based on an exploration of a potentially large feature space and in some cases they require users to manually identify the specific features that characterize the drift. Depending on the explored feature set, these methods may miss certain types of changes. This paper proposes a fully automated and statistically grounded method for detecting process drift. The core idea is to perform statistical tests over the distributions of runs observed in two consecutive time windows. By adaptively sizing the window, the method strikes a trade-off between classification accuracy and drift detection delay. A validation on synthetic and real-life logs shows that the method accurately detects typical change patterns and scales up to the extent it is applicable for online drift detection.

The Global Protection of Personal Health Data

The workshop is an activity of the IMIA Working Group ‘Security in Health Information Systems’ (SiHIS). It is focused to the growing global problem: how to protect personal health data in today’s global eHealth and digital health environment. It will review available trust building mechanisms, security measures and privacy policies. Technology alone does not solve this complex problem and current protection policies and legislation are considered woefully inadequate. Among other trust building tools, certification and accreditation mechanisms are dis-cussed in detail and the workshop will determine their acceptance and quality. The need for further research and international collective action are discussed. This workshop provides an opportunity to address a critical growing problem and make pragmatic proposals for sustainable and effective solutions for global eHealth and digital health.

A methodology for extracting legal norms from regulatory documents

We present a methodology to extract legal norms from regulatory documents for their formalisation and later compliance checking. The need for the methodology is motivated from the shortcomings of existing approaches where the rule type and process aspects relevant to the rules are largely overlook. The methodology incorporates the well–known IF. . . THEN structure extended with the process aspect and rule type, and guides how to properly extract the conditions and logical structure of the legal rules for reasoning and modelling of obligations for compliance checking.

QUT’s research data storage solutions: A launchpad for research journeys

This poster presents key features of how QUT’s integrated research data storage and management services work with researchers through their own individual or team research life cycle. By understanding the characteristics of research data, and the long-term need to store this data, QUT has provided resources and tools that support QUT’s goal of being a research intensive institute. Key to successful delivery and operation has been the focus upon researchers’ individual needs and the collaboration between providers, in particular, Information Technology Services, High Performance Computing and Research Support, and QUT Library. QUT’s Research Data Storage service provides all QUT researchers (staff and Higher Degree Research students (HDRs)) with a secure data repository throughout the research data lifecycle. Three distinct storage areas provide for raw research data to be acquired, project data to be worked on, and published data to be archived. Since the service was launched in late 2014, it has provided research project teams from all QUT faculties with acquisition, working or archival data space. Feedback indicates that the storage suits the unique needs of researchers and their data. As part of the workflow to establish storage space for researchers, Research Support Specialists and Research Data Librarians consult with researchers and HDRs to identify data storage requirements for projects and individual researchers, and to select and implement the most suitable data storage services and facilities. While research can be a journey into the unknown[1], a plan can help navigate through the uncertainty. Intertwined in the storage provision is QUT’s Research Data Management Planning tool. Launched in March 2015, it has already attracted 273 QUT staff and 352 HDR student registrations, and over 620 plans have been created (2/10/2015). Developed in collaboration with Office of Research Ethics and Integrity (OREI), uptake of the plan has exceeded expectations.

Using conceptual tool for intuitive interaction to design intuitive website for SME in India : A case study

Statistical reports of SMEs Internet usage from various countries indicate a steady growth. However, deeper investigation of SME’s e-commerce adoption and usage reveals that a number of SMEs fail to realize the full potential of e-commerce. Factors such as lack of tools and models in Information Systems and Information Technology for SMEs, and lack of technical expertise and specialized knowledge within and outside the SME have the most effect. This study aims to address the two important factors in two steps. First, introduce the conceptual tool for intuitive interaction. Second, explain the implementation process of the conceptual tool with the help of a case study. The subject chosen for the case study is a real estate SME from India. The design and development process of the website for the real estate SME was captured in this case study and the duration of the study was four months. Results indicated specific benefits for web designers and SME business owners. Results also indicated that the conceptual tool is easy to use without the need for technical expertise and specialized knowledge.

Heila-tietojärjestelmäprojekti ja sen ongelmat : Tutkimus Helsingin yliopiston henkilöstöhallinnon tietojärjestelmän kehitys- ja käyttöönottotyöstä asiakkaan näkökulmasta

Tutkimuksen tehtävänä oli selvittää Helsingin yliopiston Heila-tietojärjestelmän kehitysprojektin kulkua vuosina 1994-1999. Toisena tutkimustehtävänä oli selvittää minkälaisia ongelmia projektissa oli esiintynyt. Tutkimuksen aineisto oli projektin dokumentaatio, jossa pääaineistona olivat projektin johto- ja projektiryhmien kokouspöytäkirjat, tilanneraportit ja muut määrämuotoiset projektidokumentit. Lisäksi käytettävissä oli muuta aineistoa, kuten Heila-projektia käsitteleviä sähköpostiviestejä ja yleisönosaston kirjoituksia. Tutkimuksessa aineistoa kuvattiin kertomuksellisesti, projektin tapahtumat kirjattiin kertomukseksi kronologisessa järjestyksessä. Aineistoa analysoitiin toisen tutkimustehtävän mukaisesti sisällön analyysillä, ja tästä tuloksena oli projektin ongelmien luokittelu. Lopuksi tarkasteltiin projektin etenemiskertomuksen ja ongelmien luokittelun suhdetta. Kohteena ollut projekti viivästyi aikataulustaan kaikissa vaiheissa: toteutus- ja käyttöönotot viivästyivät useita kuukausia. Projektissa ilmeni resurssipulaa, välillä toimittajan ja välillä asiakkaan eli Helsingin yliopiston puolella. Lisäksi ohjelman sisältöalue oli niin monimutkainen, että se aiheutti vaikeuksia toteutuksessa ja käytössä. Järjestelmän suorituskyky ei vastannut sovittua, käyttöönottojen jälkeen jopa yksinkertainen tallennustoiminto saattoi kestää useita minuutteja, eikä normaaleja työtoimintoja saatu hoidettua. Helsingin yliopisto teki useita kirjallisia huomautuksia ja korvausvaatimuksia toimittajalle. Ongelmat jakautuivat toimintatapoihin liittyviin ongelmiin ja teknisiin ongelmiin. Toimintatapoihin liittyvät ongelmat sisälsivät käyttäjien huomiointiin ja projektin läpivientiin liittyviä ongelmia. Tekniset ongelmat jakautuivat kolmeen alakategoriaan: suorituskyvyn ongelmat, ohjelman ominaisuuksiin liittyvät ongelmat sekä yhteyksiin liittyvät ongelmat. Kukin alakategoria jakautui luokkiin. Projektin etenemistä arvioitiin suhteessa sen toteuttamista ohjanneeseen Helsingin yliopiston yhteistyöprojektien laatuohjeeseen, sekä Niemen (1993) malliin tietojärjestelmäprojektien läpiviennistä. Ongelmien luokittelua verrattiin Niemen (1993) arvioon projektien ongelmista. Projektin onnistumista arvioitiin Saarisen ja Sääksjärven (1992) projektin onnistumisen teorian avulla. Tulosten perusteella on mahdollista tarkastella muita projekteja, ja ongelmaluokitusten perusteella havaita potentiaaliset ongelmat. Siten voidaan parantaa työskentelyolosuhteita ja onnistumisen edellytyksiä tietojärjestelmäprojekteissa. Avainsanat: Tietojärjestelmät, projektityö, ongelmat Keywords: Information systems, project work, problems