Towards a Consistent Service Lifecycle Model in Service Governance

Introducing an SOA in a company brings new challenges for the existing management. Small loosely coupled services allow the Enterprise Architecture to flexibly adapt to existing business processes that themselves depend on changing market environments. SOA, however, introduces a new implicit system complexity. Service Governance approaches address this issue by introducing management processes and techniques, and best practices to cope with the new heterogeneity. Service lifecycle management is one aspect. Existing definitions of service lifecycles vary greatly.. In this paper, we compare existing service lifecycle approaches concerning defined phases and process. In particular, we challenge the purpose of the distinctions made between design time, runtime, and change time. Concluding, we propose a consolidated service lifecycle model for usage in Service Governance

Service Semantics Classification: an Approach Towards Modular Service Ontology

Since service systems are becoming increasingly complex in emerging technology, business, legal and economics environments, service abstractions are necessary to master this complexity. However, the term ‘service’ means different things to different people in different disciplines, which implies that any attempt to define general purpose service abstractions must address the disambiguation of the term. Service ontologies and service knowledge management efforts mainly aim at elucidating service semantics. Each discipline has multiple biased service-related concepts, so that in order to build comprehensive multi-disciplinary service models, the service-related concepts of the involved disciplines have to be integrated and structured in a consistent way. We claim that this requires a modular approach in which general purpose service semantics can be further extended or specialised with domain-specific concepts. Service-related and domain-specific concepts can be integrated and structured in many different ways. This paper proposes a semantics classification scheme based on service aspects that are essential for a services ecosystem

Resilient Critical Infrastructure Management using Service Oriented Architecture

Abstract—The SERSCIS project aims to support the use of interconnected systems of services in Critical Infrastructure (CI) applications. The problem of system interconnectedness is aptly demonstrated by ‘Airport Collaborative Decision Making’ (ACDM). Failure or underperformance of any of the interlinked ICT systems may compromise the ability of airports to plan their use of resources to sustain high levels of air traffic, or to provide accurate aircraft movement forecasts to the wider European air traffic management systems. The proposed solution is to introduce further SERSCIS ICT components to manage dependability and interdependency. These use semantic models of the critical infrastructure, including its ICT services, to identify faults and potential risks and to increase human awareness of them. Semantics allows information and services to be described in such a way that makes them understandable to computers. Thus when a failure (or a threat of failure) is detected, SERSCIS components can take action to manage the consequences, including changing the interdependency relationships between services. In some cases, the components will be able to take action autonomously — e.g. to manage ‘local’ issues such as the allocation of CPU time to maintain service performance, or the selection of services where there are redundant sources available. In other cases the components will alert human operators so they can take action instead. The goal of this paper is to describe a Service Oriented Architecture (SOA) that can be used to address the management of ICT components and interdependencies in critical infrastructure systems. Index Terms—resilience; QoS; SOA; critical infrastructure, SLA

Designing a consulting services architecture model

textDuring my years of experience in the technology industry, it has become obvious that standard processes and methodologies within the engineering discipline are at a mature state. The realization though is that software engineering specifically lags behind. Most software engineering methodologies that I have studied focus on the mission of software development. It is this realization and the need for structure that led me to review existing methodologies used within my company's software services organization. The definition of what a successful software services methodology entails is rather limited. This report will provide a history of existing software engineering methodologies that I have studied, describe an initial services method that was being developed within my organization, develop a new model that addresses previous shortcomings and identify additional components required to further define a strong software services-oriented delivery methodology.Electrical and Computer Engineerin

Asset management and governance: an analysis of fleet management process issues in an asset-intensive organization

Efficient asset management is a key performance driver for asset-intensive organizations. Achieving high utilization and return on investment on physical assets are central corporate objectives for public and private organisations alike. Current approaches on asset management include the engineering and governance perspectives. Both perspectives offer valuable but incomplete insights on the management of asset performance: experience demonstrates that an exclusive focus on one or the other may lead to sub-optimal asset and organizational performance. In this paper, we investigate how an integrated approach to asset management can be constructed in the context of vehicle fleets. Beginning with an analysis of how the asset management process is operated through the asset lifecycle, we identify key engineering and organizational factors influencing asset performance. The relationships between factors are analyzed to provide an integrated fleet asset management approach

Aligning a Service Provisioning Model of a Service-Oriented System with the ITIL v.3 Life Cycle

Bringing together the ICT and the business layer of a service-oriented system (SoS) remains a great challenge. Few papers tackle the management of SoS from the business and organizational point of view. One solution is to use the well-known ITIL v.3 framework. The latter enables to transform the organization into a service-oriented organizational which focuses on the value provided to the service customers. In this paper, we align the steps of the service provisioning model with the ITIL v.3 processes. The alignment proposed should help organizations and IT teams to integrate their ICT layer, represented by the SoS, and their business layer, represented by ITIL v.3. One main advantage of this combined use of ITIL and a SoS is the full service orientation of the company.Comment: This document is the technical work of a conference paper submitted to the International Conference on Exploring Service Science 1.5 (IESS 2015