project title: occupant aware, intelligent and adaptive ... · the tool/service infrastructure...

Adapt4EE Deliverable D4.3 Dissemination Level (PU) Grant Agreement No. 288150

January 2014 1 BOC

SEVENTH FRAMEWORK PROGRAMME

ICT systems for Energy Efficiency

Project Title:

Occupant Aware, Intelligent and Adaptive Enterprises

Adapt4EE, Grant Agreement No. 288150

Deliverable

Pilot Domain Reference Models

(Explanatory Notes)

Deliverable No. D4.3

Workpackage No. WP4 Workpackage Title and task type

Enterprise Management System Implementation

Task No. T4.4 Task Title Open Reference Models for the Pilot Domains

Lead beneficiary BOC

Dissemination level PU

Nature of Deliverable P

Delivery date 31 January 2013

Status (F: final; D: draft; RD: revised

draft):

D

File Name: D4.3 Pilot Domain Reference Models.doc

Project start date and duration 01 November 2011, 36 Months


January 2014 2 BOC

Authors List

Leading Author (Editor)

Surname Initials Beneficiary Name Contact email

Brennan T BOC [email protected]

Co-authors (in alphabetic order)

# Surname Initials Beneficiary Name Contact email

1 Tsitsanis T HYPERTECH [email protected]

Reviewers List

List of Reviewers (in alphabetic order)

# Surname Initials Beneficiary Name Contact email

1 van Krevelen R ALMENDE [email protected]

2 Simoes P ISA [email protected]

3

4

5

6

7

8

mailto:[email protected]







January 2014 3 BOC

Document history

Version Date Status Modifications made by

1.0 31st November

2013

TOC prepared T Brennan

2.0 31st January

2014

Contributions collected

and deliverable finalized

T Brennan


January 2014 4 BOC

List of definitions & abbreviations

Abbreviation Definition

AAC ASSOCIACAO ACADEMICA DE COIMBRA

ADL Adonis Definition Language

AEC Architecture Engineering and Construction

BIM Building Information Model

BPM Business Process Management

BPMN Business Process Model and Notation

CIM Common Information Model

eTOM Enhanced Telecoms Operations Map

gbXML Green Building Extensible Markup Language

ITIL Information Technology Infrastructure Library

RTF Rich Text Format

SCOR Supply Chain Operations Reference

SVN Apache Subversion

TOGAF The Open Group Architecture Framework

XML Extensible Markup Language

UNAV UNIVERSIDAD DE NAVARRA


January 2014 5 BOC

Executive Summary This document reports on the final task of WP4 – T4.4 Open Reference Models for

the Pilot Domains. The results of the work performed in T4.4 provided open

anonymized models that can be reused within the scope of Adapt4EE and other

projects in the AEC domain but they also have potential to be reused in more

generic business scenarios of their respective domains. The outcome of this work

is presented as reusable packages of business process for specific domains

developed in collaboration with the pilot partners of the project and will be

published within the community. Candidate community spaces have been

selected and the publishing process has been triggered accordingly. As a

prototype deliverable the document at hand represents the explanatory notes and

provides details on the methodology followed and results achieved in developing

the packages.

As the concluding task, T4.4 built on the previous results that were achieved in

T4.1 and T4.2 resulting in deliverable D4.1 – Pilot Domain Business Process and

Resource Models [1]. D4.1 has been used as input, further enriched and detailed

and packaged according to a common process to a) anonymize confidential data

from the pilot domain b) structure the package according to a common format

and c) provide the necessary file representation to share the information. Basic

annotation with keywords and additional metadata was added to describe the

actual content.

Overall, the following results have been achieved during the execution of T4.4:

Domains included: 2

o Health Care derived from UNAV in Navarra

o Multipurpose Complex derived from AAC in Coimbra

Areas analysed: 9

o UNAV Administration Area

o UNAV Day Care Area

o UNAV Nephrology Area

o UNAV Oncology Area

o AAC ISA Design and Development Area

o AAC ISA Financial Area

o AAC ISA Innovation Area

o AAC ISA Procurement Area

o AAC LEITE Eye Clinic Area

Number of packages: 11

Overall number of models: 136

Overall number of activities: 659

Access to the packages is provided through a dedicated secure SVN repository

that allows registered interested users access to the models for use in the related

projects. After registration for access the community members are supported in

providing modifications and updates/additions back to the repository. The

repository is accessible at: https://secure.boc-group.eu/svn/adapt4ee/

To obtain a username and password for SVN access please send an email request

to [email protected]. Since the packages are characterized as “open” the initial

release represents the results derived from the Adapt4EE pilot perspective.

Through collaboration and interaction with the community on the selected

platform, further enhancements and additions are expected.



January 2014 6 BOC

Table of Contents List of definitions & abbreviations .................................................................. 4

Executive Summary ..................................................................................... 5

List of figures .............................................................................................. 7

List of tables ............................................................................................... 8

1. Introduction ...................................................................................... 9

2. Understanding the Term - Reference Model ......................................... 10

2.1. Definition: Reference Models ....................................................... 10

2.2. Definition: OPEN Reference Model ................................................ 10

2.3. Use of Reference Models in Industry ............................................. 11

2.4. Existing Industry Reference Models .............................................. 11

2.5. Reference Models in ADAPT4EE: Community Involvement ............... 12

3. From Adapt4EE BPM Models to Open Reference Models ......................... 13

4. Usage of Adapt4EE Open Reference Models ......................................... 20

4.1. Read Open Reference Models....................................................... 20

4.2. Modify and Update Open Reference Models ................................... 20

5. Conclusion ...................................................................................... 22

References ............................................................................................... 23

Annex I: Industry Reference Frameworks ..................................................... 24

ITIL ......................................................................................................... 24

ETOM ....................................................................................................... 25

IBMs Insurance Application Architecture ....................................................... 25

SCOR ....................................................................................................... 26

TOGAF ..................................................................................................... 27

Annex II: ADONIS Community Edition ......................................................... 28

ADONIS Community Edition ........................................................................ 28

ADONIS Community Edition for Windows XP Professional ............................... 28

ADONIS Community Edition for Windows Vista/7........................................... 28

Further Software for All Operating Systems (recommended) ........................... 29

Annex III: Open Reference Models Cover Sheets ........................................... 34


January 2014 7 BOC

List of figures Figure 1 - Open Reference Model Transformation Methodology........................ 13

Figure 2 Dependencies of Models................................................................. 14

Figure 3 - Detailed Resource Model Mapped to gbXML .................................... 14

Figure 4 Detailed Business Processes - Check-in Process of a Healthcare Clinic . 15

Figure 5 Skeleton Activity Models Check-in Process of a Healthcare Clinic ........ 16

Figure 6 - Specific Location Names at UNAV ................................................. 17

Figure 7 - Healthcare CIM Location Names ................................................... 17

Figure 8 - UNAV Working Environment with Employee Names ......................... 18

Figure 9 - List of Healthcare Roles for Oncology Department ........................... 19

Figure 10 - Sample Open Model Package Cover Sheet .................................... 20

Figure 11 - Open Reference Model Group Structure ....................................... 21

Figure 12 - Information Technology Infrastructure Library [14] ....................... 24

Figure 13 - Enhanced Telecoms Operations Map (eTOM) [10] ......................... 25

Figure 14 - IBM Industry Models Speak the Language of Business [11] ............ 26

Figure 15 - Five Distinct Management Processes [15] .................................... 27

Figure 16 - TOGAF Architecture Development Method (ADM) [17] ................... 27

Figure 17 - ADONIS Component Bar ............................................................ 29

Figure 18 - ADL Import Dialog .................................................................... 30

Figure 19 - ADL file import dialog ................................................................ 30

Figure 20 - ADONIS Model Import Selection Dialog ........................................ 31

Figure 21 - Online Collaboration Portal ......................................................... 32

Figure 22 - Online Collaboration Portal Model Upload Function ........................ 32

Figure 23 - Context Menu to Export Models to CIM ........................................ 33

Figure 24 - Model Package Cover Sheet Template ......................................... 34

Figure 25 - Healthcare Cover Sheet ............................................................. 34

Figure 26 - Healthcare - Administration Cover Sheet ..................................... 35

Figure 27 - Healthcare – Daycare Cover Sheet .............................................. 35

Figure 28 - Healthcare - Nephrology Cover Sheet .......................................... 36

Figure 29 - Healthcare - Oncology Cover Sheet ............................................. 36

Figure 30 - Software House Cover Sheet ...................................................... 37

Figure 31 - Software House - Design and Development .................................. 37

Figure 32 - Software House - Financial Cover Sheet ....................................... 38

Figure 33 - Software House - Innovation Cover Sheet .................................... 38

Figure 34 - Software House - Procurement Cover Sheet ................................. 39

Figure 35 - Eye Clinic Cover Page ................................................................ 39


January 2014 8 BOC

List of tables Table 1 Step 1 – Analyse the Inputs ............................................................ 15

Table 2 Step 2 – Identify Common Process Variants ...................................... 16

Table 3 Step 3 – Standardise into Reusable Processes ................................... 17

Table 4 Step 4 – Remove Personal or Confidential Content ............................. 19

Table 5 Step 5 – Annotate Metadata to Reference Models ............................... 19


January 2014 9 BOC

1. Introduction The document at hand represents explanatory notes to the final prototype D4.3

developed in context of WP4. As a sustainable result from the work package the

content developed with respect to business process and resource models using

the ADONIS Business Process Management Toolkit, applying the methodology of

Adapt4EE and using the software components developed is released in the format

of open reference models. These models are intended to support designers and

engineers to use the Adapt4EE system and integrate BPM artefacts in their

operation by building on pre-existing, pre-packaged models for specific domains.

These packages can be used as-is without further modification but also allow for

additions, modifications and domain/organisation specific customization through

the tool/service infrastructure developed in the project.

The work presented in this document builds strongly on the pilot results achieved

in T4.1 and T4.2 and presented in D4.1 [1]. From a technological perspective the

deliverables in context of WP2 (D2.2) [2][1] and WP6 (D6.2) [3] are of relevance

to understand a) the way the packages are structured and b) how the BPM

module interacts with the overall Adapt4EE solution.

This explanatory note is structured as follows:

- Chapter 2 provides an overview of what a reference model is and how they

are used in various industries. A synopsis of existing frameworks and

reference models is also provided. Chapter 2 also introduces the term

Open Reference Model and explains the concept behind the initiative for

building up a knowledge base of free open reference models to be used by

domain experts and non-experts alike.

- Chapter 3 gives an overview of the approach and steps taken to create

open reference models from the detailed business processes, resource

models and working environment models that were developed in T4.1 and

T4.2. This transformation task for the pilot domains was performed in

T4.4, the description in this chapter is understood as a guidance chapter

for future releases of packages by the community.

- Chapter 4 provides a short overview of what is contained in the open

reference model packages and explains how to gain access to the contents

of the packages and to read/modify the models.

- Chapter 5 concludes the deliverable and outlines how the open reference

models will be used in the future in conjunction with the other Adapt4EE

results.

- Annex I – provides an overview on a number of existing industry reference

models

- Annex II – outlines the hardware and software requirements to install and

use the ADONIS Community Edition. It also provides a user guide of how

to access and download the software, how to import an ADL (ADONIS

Definition Language) model file, how to upload an ADL file to the

collaboration portal and also how to export the Common Information

Model data.

- Annex III – is a set of Open Reference Model cover sheets for each

process that is included in the model stack.


January 2014 10 BOC

2. Understanding the Term - Reference Model In the following chapter we define what a model is, what a reference model is and

how open reference models differ to the generic reference models. The chapter

will conclude with an understanding of how the use of open reference models

applies to the Adapt4EE project and the sustainability of the results in the future.

A generic definition of what a model represents is to say that a model is used as a

description for a social role, archetype, or job in the context of various domains

like architecture, design, fashion, cars, statistics and even zoology [4]. A more

technical definition of what a model is, states that models are a representation of

either a reality or a vision that are created for some certain purpose with an

intended goal in mind. Both types of model definition can be used as the basis of

creating a reference model depending on the domain requirements.

2.1. Definition: Reference Models

As model content is developed reference models can be created from a stack of

existing models from a specific domain as they are used to pull together a bird’s

eye view of the complete domain or of a more specific problem space. Once

created a reference model can be considered as a generic abstract framework or

as a domain specific ontology consisting of a set of clearly defined concepts [5].

Reference models are typically defined by experts of a certain domain with a

common goal of encouraging clearer communication for other members of the

same domain or community. Reference models also support the development of

consistent standards or specifications supporting the domain moving forward.

Reference models can be used as a beneficial education tool for explaining

concepts from a complex domain simply to a non-specialist. This ensures that a

standard vocabulary and set of terms is also used from the outset between all

parties to avoid miscommunication.

The use of reference models is becoming more popular in certain domains as

content is being created by specialists and working groups and the use of pre-

existing reference material and their approaches is more commonplace focusing

structured process definition based on a set of reference processes for example.

It is still early days in the development of reference model content so it is hard to

quantify their specific use in industry and their benefits but reference models can

definitely add significant value in building a strong BPM capability within an

organization without reinventing the wheel each time a new project is started.

Successful use of a set of reference processes can expedite the efforts of process

definition leading to the conversion to standardized processes in an organization.

2.2. Definition: OPEN Reference Model

Open reference models differ slightly to the generic reference models outlined

above. The "open" in "open model" refers to the terms of usage of models in

reference to those used on an open basis. The creation, development and

maintenance of open models is considered to be community based. Experts and

non-experts alike can be part of the user community and any interested party is

free to use the content and apply it to their needs. An "open model" is licensed

under the terms which provide the licensee with unrestricted access to all model

representations and documentation as well as royalty-free, non-exclusive rights

to copy, redistribute, use and modify the model and the model documentation.

A reference model is typically a conceptual model. On a conceptual level, models

represent abstractions of real-world phenomena relevant to a specific modeling

task and valid for a specific time frame. Conceptual models can be aimed at

providing representations of software systems that are accessible not only to

modelers and software developers, but also to domain experts and prospective


January 2014 11 BOC

end users. For this reason, they focus on general concepts commonly used within

a certain domain abstracting from technical aspects. By allowing for various

abstractions, e.g. data abstraction, object abstraction, and process abstraction,

they contribute to the reduction of complexity and risk. This allows such models

to be understandable by domain experts and non-experts alike and supports

communication among the various stakeholders involved in a project.

2.3. Use of Reference Models in Industry

Using reference models together with other tools and elements of BPM helps

organizations to become more responsive to market changes and improves their

core business by using standardized and industry specific best practices. The

reference processes cannot simply be implemented alone as there has to be a

commitment and dedication from the organisation as a whole to employ a value

driven approach to BPM and avoiding the pitfalls of focusing on methods and

tools. Frameworks of reference model adoption projects can sometimes require

even more up front efforts to ensure smart decisions are taken at the beginning

of the project to reduce rework and to broaden the cultural acceptance and speed

of adoption of the framework.

For people who are not experts in the area of BPM, the use of a reference model

appears to make very practical sense. Instead of getting writers block and staring

at a blank sheet of paper, it is possible to get a head start by utilizing parts of a

generic model that applies in some way to the organisation which speeds up the

arduous initial task of identifying, sorting, categorizing and organizing their

processes into an understandable process architecture [6]. A process framework

then enables an organization to rapidly get on the same process page and drive

consistency across all the process and performance initiatives that are running. A

certain level of maturity needs to exist within an organization to fully exploit the

value of implementing a reference model so baselines should be defined in the

early stages so that perceived benefits can be measured against a roadmap for

increasing value.

2.4. Existing Industry Reference Models

There are two main types of existing industry reference models. There are

reference models that describe best practices for a specific domain or area of

expertise and whereas other are more focused on a description of the actual

structure of the business process architecture. Domain specific reference models

exist to address different types of organizations and the common issues that they

face for instance in the Insurance or Telecommunications industry. A number of

reference models exist for BPM but models exist also to address other domains

within an organization such as IT service management, in the areas of strategy

and performance management and enterprise architecture management. There

are currently approximately 30 different reference models for business in use

including well known examples which we will describe in Annex I such as:

Supply Chain Operations Reference (SCOR) Model: as a process

reference model developed and endorsed by the Supply Chain Council [7].

ITIL - is the most widely accepted approach to IT service management in

the world. ITIL provides a cohesive set of best practice, drawn from the

public and private sectors internationally [8].

TOGAF - Version 9.1 is a detailed method and set of supporting resources

for developing an Enterprise Architecture [9].

eTOM is the Business Process Framework (eTOM) from the TMForum’s

blueprint for enabling successful business transformation and is a critical

component of their Frameworx [10].


January 2014 12 BOC

IBM Insurance Application Architecture models are a comprehensive

suite of models comprising of data, process and service-based models that

help insurers accelerate the planning of business process transformation

[11].

2.5. Reference Models in ADAPT4EE: Community Involvement

In Adapt4EE the Open Reference Models are being developed to ensure the

sustainability of the results achieved in WP4 will remain within the AEC domain

going forward through the projects SVN site as the following URL:

https://secure.boc-group.eu/svn/adapt4ee/. The open model packages developed

at the two pilot sites are readily available to download and to be reused by

designer and engineers together with the results of the other work packages of

Adapt4EE and the results of the project as a whole. The packages consist of both

the detailed business processes that have been anonymized and changed into

reference models and also the skeleton activity models that were developed in

T4.1 and T4.2. Skeleton activities and the differences in comparison to normal

business activities have been fully described in the deliverable D4.1 [1].

Interested users will be able to reuse the models from the healthcare domain for

example to avoid or at least reduce the high volume man power requirement to

model the business processes, resources and organizational aspects for the

healthcare practice that is undertaking the project. They will therefore not be

starting from scratch and as the models are open they can add to the models if

additional processes are found to be executed regularly in the space being

assessed. Likewise if only a smaller selection of processes is required for the

specific simulation run then they can be exported separately in the CIM XML

schema as necessary. It will be possible to use the open reference models as the

baseline and change certain parameters that may apply to the organization using

the new space being developed or refurbished. For example if there are more

employees of a specific role working in the organization or if there is a higher

volume of a certain process that is performed in a busier environment then these

parameters can be changed.

https://secure.boc-group.eu/svn/adapt4ee/


January 2014 13 BOC

3. From Adapt4EE BPM Models to Open Reference Models

The purpose of this section of the deliverable is to introduce the approach applied

to update/modify the detailed business process, resource and related models into

open reference models. The purpose of this section is to introduce the approach

and develop a common methodology as a checklist to transform newly created

BPM packages before being released to the community.

In the following the methodology to perform this transformation is briefly

introduced, each phase of the methodology applied is detailed by providing an

analysis on input and output relations as well as providing an example of the

steps performed.

Figure 1 - Open Reference Model Transformation Methodology

In order to create the open reference models for the pilot domains a procedural

approach was introduced. The various phases of the procedure model are

illustrated by Figure 1 above. Each of the phases of the procedure model is

described in the following section using a common template.

1 Analyse the Inputs

Before the open models could be developed the existing models that were

presented in D4.1 – Pilot Domain Business Process and Resource models [1]

needed to be analyzed so that candidates for open model development could be

selected from the model stack. The models needed to be seen to be common

models that were describing processes for everyday activities in the given

domain.

Considerations:

- Granularity: an important aspect in deriving the packages does lie upon

the level of granularity to be applied. For the pilot domains, and due to

the approach chosen to develop the models, different levels of granularity

are supported, ranging from full domain models to process areas – the

analysis results in this area are input to step 2

- Re-usability: re-usability must be ensured during this phase. Pilot specific

elements are removed and excluded from the package (e.g. specific

elements that only occur for UNAV/AAC) – the analysis results in this area

are input to step 3


January 2014 14 BOC

Application on Pilot Results UNAV/AAC

All inputs that were modeled in T4.1 and T4.2. It was decided to include all

model types that were utilized from the modeling method provided by the

ADONIS tool. As a result the packages that were created include Business

Process Models, Business Process Diagrams (BPMN 2.0), Working Environment

Models and IT System models. The IT System models were used to represent the

locations and the resources used to support the process execution.

Figure 2 Dependencies of Models

The enumeration values for the spaces where the activities are executed in the

pilot domains were taken from the Green Building XML open schema. This

schema has become the de facto industry standard and helps facilitate the

transfer of building properties stored in 3D building information models (BIM) to

engineering analysis and simulation tools. By using this existing schema and

enumeration values any new processes that are added to the open reference

models can use the complete list of space types as defined by gbXML and will

therefore cover almost all types of building spaces. A smaller model containing

only the subset of space types that were taken into account based on the pilot

areas being monitored in the two pilot sites is also part of the open reference

models.

Figure 3 - Detailed Resource Model Mapped to gbXML


January 2014 15 BOC

The same approach was used for the creation of the resource models. There

were a number of resources modelled in the pilot domains and each of the

various resources were mapped to an equipment type enumeration value taken

from the gbXML schema. A full model containing all possible equipment types

that are contained in the gbXML schema has been included in the open reference

models. For the 2 pilot domains smaller models were created only containing the

subset of resource types that were used to support the execution of the models.

Table 1 Step 1 – Analyse the Inputs

2 Identify Common Process Variants

A Business Process Variant is a fundamental flow variant of a Business Process

which uses the same input and delivers the same measurable outcome. We

needed to see if any such processes existed across the model stack that were

created during WP4. If any such variants were discovered they were considered

prime candidates to be developed into a single open reference model as they

could be used as a starting point for more than one scenario based on the target

variant of the process.


Some processes that were modeled at the pilots in task 4.1 were modeled using

a similar structure from different areas of the pilot domains. The processes

resulted in a similar outcome and were therefore candidates to become a single

reference model. The activities were also being performed in similar space types

and by employees of the same role. These models were then merged using the

common elements to form open reference models.

Figure 4 Detailed Business Processes - Check-in Process of a Healthcare Clinic


January 2014 16 BOC

Figure 5 Skeleton Activity Models Check-in Process of a Healthcare Clinic

Table 2 Step 2 – Identify Common Process Variants

3 Standardise into Reusable Processes

This step was employed to minimize the variation in the processes that were

chosen to be part of the open reference models so that they could be applied in

any proposed building within the same domain. A standardized process is a

process with a series of repeatable steps. It should be clear and concise and

remove any unnecessary waste where possible.


In some of the detailed processes it was required to remove and merge some of

the steps or activities to create more uniform processes. This was not performed

to the same degree of aggregation that was applied to create the skeleton

activities. For the detailed business processes each of the single activities that

were modelled needed to have a gereric reference to the building space or

location where it is expected that such an activity would be executed. In the

detailed business processes as modelled in T4.1 specific location names were

used that were identifiable in the pilot areas. To develop the open reference

models these names had to be mapped to the space types taken from the gbXML

schema to ensure that they were generic names used to describe the space type

where the activity was being performed. This aided in the creation of the

standardised processes and also ensured that all data protection policies were

adhered to in relation to the space names.


January 2014 17 BOC

Figure 6 - Specific Location Names at UNAV

Figure 6 above illustrates the specific names that were given to the locations

where the activities were being performed on the 8th floor of the UNAV clinic. And

below in Figure 7 is the list of space types from gbXML that were used to make

the references more generic. Each of the references that were created in the

detailed business processes for each activity were changed to only used the space

types listed here.

Figure 7 - Healthcare CIM Location Names

Table 3 Step 3 – Standardise into Reusable Processes

4 Remove Personal or Confidential Content

To ensure that we abided by the data protection constraints of the project we

needed to remove any personal or confidential content that was contained in the


January 2014 18 BOC

detailed business processes for the pilot domains. As the open reference models

will be readily available to the public they needed to be anonymized for this

reason. All personal names and references to members of staff within the pilot

domains needed to be removed from the models. It was also necessary to

generalize the space types and resources used in all business processes. Each

business process and other model types needed to be renamed to remove the

reference to the pilot partners.


For the two pilot sites one of the key goals was to anonymize all of the models

that were created so that they could be released with no problems surrounding

the data protection and privacy issues that the participating pilot companies

could face.

Figure 8 - UNAV Working Environment with Employee Names

For the working environment models all of the individual employee names were

removed and the departments of the organisations were removed meaning only

the roles involved in the businesses processes were part of the open model

package that was developed.

Figure 8 shows an example of the model containing only role objects that can be

referenced by the business process models and by the business process diagram

(BPMN 2.0) models.


January 2014 19 BOC

Figure 9 - List of Healthcare Roles for Oncology Department

In T4.1 and T4.2 a specific naming structure was adhered to so that the models

that belonged to the different pilot domains could be easily recognised using the

partner abbreviations of UNAV and AAC. For the open reference model packages

the names of the pilot partners was removed from the name of each model and

replaced where necessary to specify the domain with the name of the domain

that the model related to for example ‘WE Healthcare Administration’ for the

working environment model for the healthcare pilot domain.

Table 4 Step 4 – Remove Personal or Confidential Content

5 Annotate Metadata to Reference Models

To ensure that we abided by the data protection constraints of the project we

needed to remove any personal or confidential content that was contained in the

detailed business processes for the pilot domains. As the open reference models

will be readily available to the public they needed to be anonymized for this

reason. All personal names and references to members of staff within the pilot

domains needed to be removed from the models. It was also necessary to

generalize the space types and resources used in all business processes. Each

business process and other model types needed to be renamed to remove the

reference to the pilot partners.


The necessary metadata description did happen on package level. For each

package a cover sheet provides information on the actual content and related

artifacts.

Table 5 Step 5 – Annotate Metadata to Reference Models


January 2014 20 BOC

4. Usage of Adapt4EE Open Reference Models The open reference models of Adapt4EE are provided as self-contained packages

that can be used to:

a) Read model information and apply in the Adapt4EE system to start

simulation jobs etc. without further modification

b) Modify and update package content to the domain/organisation in focus.

4.1. Read Open Reference Models

In order for the end user to read the contents of the model packages they must

install the ADONIS Community Edition [13] and import the ADL file provided. The

instructions how to download the software and import the relevant file is outlined

in the Annex II. Alternatively to get an overview of what is contained in the

package the end user can peruse the RTF document that is provided on the SVN

repository or browse through the model images that are also available.

Figure 10 - Sample Open Model Package Cover Sheet

Each open reference model package created comes with a cover sheet providing

an overview of the contents of the package. Figure 10 illustrates a example of the

cover sheet for the healthcare package. All other cover sheets can be found in

Annex III. The open reference models have been designed using the BPMN 2.0

standard for modelling. To understand the meaning of the various objects used

from the BPMN method and their representaion in ADONIS you can download a

free BPMN poster from the Adonis Community website [12].

4.2. Modify and Update Open Reference Models

The open reference packages are available to the AEC community via the projects

SVN page - https://secure.boc-group.eu/svn/adapt4ee/

There is a package available for the healthcare domain taken from the UNAV pilot

areas in the clinic in Pamplona and there is a package available for an eye clinic


January 2014 21 BOC

and a software house from the mixed use facility to represent the work performed

at the AAC pilot in the Coimbra football stadium. These packages were further

broken down into separate packages for the various process areas examined

within each pilot.

The packages have been split for each domain into packages containing the

following elements:

ADL file of the detailed business processes and the skeleton activity

models as a base for modification and import of the open reference models

in the ADONIS Community Edition [13]

ADOXML file of the open reference models that can be imported into the

ADONIS Community Edition or analysed externally

XML file of complete package aligned to Common Information Model

A folder is also provided containing the images of all the models included

in the specific package

An RTF document is provided containing all the information that is stored

in the models including the images of the models and all notebook

information.

Each ADL file containing all models have the following model group structure

inside as shown in Figure 11 below.

Figure 11 - Open Reference Model Group Structure

To be able to modify the content of the open reference models that have been

developed in T4.4 the end users will need to have the ADONIS Community Edition

Software [13] installed on their machines available online for free at

http://www.adonis-community.com/. In Annex II we explain how the open

reference models can be explored for reuse and also how to install and use the

software that is required to modify and adapt the package content.

Further details on how to get started with ADONIS and modify pre-existing

package can be found in the annex (Hardware/Software Requirements, User

guides).

http://www.adonis-community.com/


January 2014 22 BOC

5. Conclusion In this deliverable we presented the results of the work performed in the scope of

Adapt4EE task 4.4 – Open Reference Models for the Pilot Domains. The goal of

the task was to create packages of models to enable the results of the modelling

tasks in T4.1 and T4.2 to be shared in the public domain and to enhance the

sustainability of the open model content in the future. In total 11 open model

reference packages have been developed as a result of task 4.4. The domain

packages were split into packages for the complete domain and into smaller

packages for single areas in each domain to make it easier for the end user to run

small or large simulations based on their requirements. The total number of

models produced was 136 and the total number of activities modelled was 659.

The open models will primarily be targeted at the AEC community and other

Adapt4EE stakeholders interested in building simulation so that they can use real

business process information in their simulation model rather than just average

values for the purposes of alternative design evaluation. The models have been

shared through an SVN and as the models are ‘open’ in nature it is foreseen that

the packages will be built upon in the future to incorporate additional building

types or business domains. In the future the full package of open models will also

be available on eeSemantics Wiki page.


January 2014 23 BOC

References

[1] Adapt4EE Deliverable D4.1 – Pilot Domain Business Process and Resource

Models

[2] Adapt4EE Deliverable D2.2 – Adapt4EE Common Information Model

[3] Adapt4EE Deliverable D6.2 – Adapt4EE System Prototype

[4] The definition of a model available at the open model inititiative website:

http://omi.dke.univie.ac.at

[5] Definition of a reference model, URL:

http://en.wikipedia.org/wiki/Reference_model

[6] BPTrends Reference Models: The Long, Long Shortcut A Ramias, C Wilkins

2012.

[7] The SCOR reference models are available at the following URL:

https://supply-chain.org/scor

[8] Definition taken from the official ITIL Site at the following URL:

http://www.itil-officialsite.com/AboutITIL/WhatisITIL.aspx

[9] TOGAF Version 9.1 is available at the following URL: -

http://www.opengroup.org/togaf/

[10] eTOM is available through the TMForum at the following URL:

https://www.tmforum.org/

[11] IBM Insurance Application Architecture Models,

IBM_Insurance_Models.pdf, IBM 2007.

[12] BPMN Notation Explained - http://www.adonis-

community.com/fileadmin/media/BPMN/BPMN-2.0-poster.pdf

[13] ADONIS Community Edition freeware software is available for download

at the following URL: www.adonis-community.com

[14] The ITIL Service Lifecycle Image is available at the following URL:

http://www.milldesk.com/what-is-itil-2/

[15] The image of the SCOR reference model is available at the following URL:

http://scor-software-model-framework.softsia.com/

[16] The TOGAF Pocket Guide V9.1 is available through -

https://store.opengroup.org/catalog/product_info.php?products_id=123

[17] The TOGAF image is available at the following URL :

http://www.orbussoftware.com/enterprise-architecture/togaf-9/

http://en.wikipedia.org/wiki/Reference_model

https://supply-chain.org/scor

http://www.itil-officialsite.com/AboutITIL/WhatisITIL.aspx

https://www.tmforum.org/

http://209.240.136.95/Data-Movement-Warehousing/InfoSphere/PDFs/IBM_Insurance_Models.pdf

http://209.240.136.95/Data-Movement-Warehousing/InfoSphere/PDFs/IBM_Insurance_Models.pdf


http://www.milldesk.com/what-is-itil-2/

http://scor-software-model-framework.softsia.com/

http://www.orbussoftware.com/enterprise-architecture/togaf-9/


January 2014 24 BOC

Annex I: Industry Reference Frameworks

ITIL ITIL is the most widely adopted approach for IT Service Management in the

world. It encompasses a set of ‘good practices’ that offer a practical, no-nonsense

reference framework for identifying, planning, delivering and supporting IT

services to the business. ITIL advocates that IT services must be aligned to the

needs of the business and underpin the core business processes. It provides

guidance to organizations on how to use IT as a tool to facilitate business change,

transformation and growth.

Figure 12 - Information Technology Infrastructure Library [14]

The ITIL best practices are currently detailed within five core publications which

provide a systematic and professional approach to the management of IT

services, enabling organizations to deliver appropriate services and continually

ensure they are meeting business goals and delivering benefits. The five core

guides map the entire ITIL Service Lifecycle, beginning with the identification of

customer needs and drivers of IT requirements, through to the design and

implementation of the service into operation and finally on to the monitoring and

improvement phase of the services defined.

By adopting ITIL and by improving the processes around IT organizations can

begin to experience a huge range of benefits that:

Improve customer satisfaction through a more professional approach to

service delivery

Improve productivity

Improve the use of skills and experience

Improve delivery of third party service.

Improve resource utilization

Decrease rework

Eliminate redundant work

Improve upon project deliverables and time

Improve availability, reliability and security of mission critical IT services

Justify the cost of service quality

Provide services that meet business, customer and user demands

Integrate central processes

Document and communicate roles and responsibilities in service provision

Provide demonstrable performance indicators


January 2014 25 BOC

ETOM eTOM stands for Enhanced Telecom Operations Map. The Enhanced Telecom

Operations Map is an ongoing initiative developed by the TM Forum to deliver a

business process framework for the telecommunications industry. The eTOM

business process framework was developed to map out the processes involved at

an enterprise level. TM Forum's eTOM (Enhanced Telecom Operations Map)

serves as a blueprint for how a telecommunications company can integrate these

processes in order to successfully compete through the implementation of a

business process driven methodology [10].

The Enhanced Telecom Operations Map (eTOM) starts at the high level process

view and then uses a hierarchical structure to breakdown each process according

to where they exist within the enterprise. The eTOM business process framework

is a tool used for process creation, process analysis, and process improvement.

Figure 13 - Enhanced Telecoms Operations Map (eTOM) [10]

Some reference frameworks can even be used in conjunction with one another if

the requirements are ICT Enterprises can leverage the past experience of the IT

service and telecommunications industry in the operations space by

simultaneously adopting ITIL as described in section 2.2.1 and the Business

process Framework (eTOM).

IBMs Insurance Application Architecture As the insurance industry continues to deal with a fast pace of change, insurers

face difficult new challenges. The IBM Insurance Application Architecture provides

an architectural framework for the development of application solutions for the

insurance industry. It is based on a general Insurance Business Architecture

developed to provide common structures capable of representing the various

business requirements occurring in global insurance companies. It’s a

comprehensive suite of models comprising of data, process and service-based

models that help insurers accelerate the planning and requirements analysis of

business process transformation, core system renewal and consolidated reporting

solutions. It contains the proven business knowledge and best practices required

to support critical business issues and ensure that IT projects are linked with

business requirements [11].


January 2014 26 BOC

IAA describes the business of the insurer and is an efficient communication bridge

between business and technology communities. It is designed to be readily

accessible to business users and by focusing on industry issues such as Sales and

Customer Services, Marketing and Analytics, Customer Relationship Management,

Policy Administration, Product Development, Insurance Claims and Risk and

Compliance.

The IAA models have coverage in the following areas: LOB Customer Acquisition

(Individual Insurance), LOB Underwriting (Individual Insurance), LOB Customer

Acquisition (Group Insurance), LOB Policy Administration (Individual), LOB Claim

Management (Individual), LOB Policy Administration / Claim (Group), Financial

Transaction / Investment, Reinsurance Management, Intermediary Management,

Provider Management, Human Resource Management, Customer Relationship

Management, Marketing Management, Product Development, Risk Policy

Management, Risk Mitigation and Assessment, and Risk Reporting and Review.

Figure 14 - IBM Industry Models Speak the Language of Business [11]

SCOR The Supply Chain Operations Reference-model (SCOR®) is a process reference

model that has been developed and endorsed by Supply Chain Council as the

cross-industry standard diagnostic tool for supply chain management. The SCOR

Framework is the basis for all supply chain management. The metrics in SCOR

provide a solid foundation for measuring performance and identifying priorities

but the actual processes are the common language for all supply chain

operations. SCOR enables users to address, improve and communicate supply

chain management practices within and between all interested parties [7].

The SCOR-model has been developed to describe the business activities

associated with all phases of satisfying a customer's demand. By describing

supply chains using process building blocks, the model can be used to describe

supply chains that are very simple or very complex using a common set of

definitions. As a result, disparate industries can be linked to describe the depth

and breadth of virtually any supply chain. The model has been able to

successfully describe and provide a basis for supply chain improvement for global

projects as well as site-specific projects. The 5 key management processes that

SCOR is developed around are Plan, Source, Make, Deliver and Return. An

illustration of how they relate to each other and the various stakeholders can be

seen below in Figure 15.

http://en.wikipedia.org/wiki/Customer_relationship_management

http://en.wikipedia.org/wiki/Insurance#Complexity_of_insurance_policy_contracts

http://en.wikipedia.org/wiki/Product_development

http://en.wikipedia.org/wiki/Insurance#Claims

http://en.wikipedia.org/wiki/Governance,_risk_management,_and_compliance

http://en.wikipedia.org/wiki/Governance,_risk_management,_and_compliance


January 2014 27 BOC

Figure 15 - Five Distinct Management Processes [15]

TOGAF TOGAF (The Open Group Architecture Framework) is an industry standard

architecture framework. This can be used freely by any organization or individual

aiming to develop information systems architecture and to utilize it effectively.

Put simply, TOGAF is a tool for assisting in the acceptance, production, use, and

maintenance of architectures. It is based on an iterative process model supported

by best practices and a reusable set of existing architectural assets.[16]

There are many architecture frameworks, but TOGAF is unique in containing a

method for developing architecture - the TOGAF Architecture Development

Method (ADM). TOGAF covers the development of 4 related types of

architectures. These four types of architecture are commonly accepted as subsets

of an overall enterprise architecture, all of which TOGAF is designed to support.

They are the Business, Data, Application and Technology Architectures.

Figure 16 - TOGAF Architecture Development Method (ADM) [17]

TOGAF has been developed and continuously evolved by representatives from

some of the world’s leading IT customer and vendor organizations, working in The

Open Group’s Architecture Forum.

Using TOGAF makes it easier for individuals from organizations to work together

to produce high quality business outcomes with less chance of misunderstanding

and wasted effort. Therefore organizations can spend more time achieving

business value rather than discussing how to do the job.


January 2014 28 BOC

Annex II: ADONIS Community Edition Hardware requirements

ADONIS Community Edition

Processor Pentium 4 or equivalent processor (or higher)

(Note: ADONIS is a 32-bit Windows application. ADONIS

can be executed on 32-bit as well as on 64-bit Windows.)

Speed ADONIS:

At least 1,8 GHz (higher recommended)

Database Management System (DBMS):

According to the specification of the DBMS vendor

RAM ADONIS:

At least 1 GB (more recommended)

Database Management System (DBMS):

According to the specification of the DBMS vendor

Hard disk

capacity ADONIS:

Approx. 260 MB for the installation of ADONIS

Plus approx. 400–700 MB for every 1,000 models in

the database

Database Management System (DBMS)

SQL Server Express Edition: approx. 300 MB

for other DBMS: according to the specification of

the DBMS vendor

Screen resolution At least 1024 x 768 (1280 x 960 or higher

recommended)

Colour depth At least 65,536 colours / 16-bit (16 million colours / 32-

bit recommended)

Software requirements

ADONIS Community Edition for Windows XP Professional

Operating

systems

Windows XP Professional Edition (only 32-bit)

Database

management

systems

Microsoft SQL Server 2005/2008/2008 Express (32-

bit and 64-bit)

ADONIS Community Edition for Windows Vista/7

Operating

systems

Windows Vista (32-bit and 64-bit)

Windows 7 (32-bit and 64-bit)

Database

management

Microsoft SQL Server 2005/2008/2008 Express (32-

bit and 64-bit)


January 2014 29 BOC

systems

Further Software for All Operating Systems (recommended)

Simulation Microsoft Excel XP/2003/2007/2010

(when using the Excel-based simulation result

comparison; executing macros must be allowed.

When using the function ‘Calculate current values’ in

the Evaluation component, Excel must be installed on

the same machine the client is running)

Documentation Microsoft Word 2003(SP3)/2007/2010

(if the Word or RTF documentation generation is to be

used)

Adobe Acrobat Reader 6.0 (or higher, for viewing

generated PDF documentation)

Mozilla Firefox 3.5 or higher (for viewing generated

HTML documentation)

Microsoft Internet Explorer 7.0/8.0/9.0 (for viewing

generated HTML documentation)

User Guide to Access ADONIS Community Edition

To download the ADONIS Community Edition the end user must go to the

following webpage - www.adonis-community.com and register an account. Once

registered the end user will be able to download and install the software. All

supporting documentation and help files can be found on the website. If the user

experiences any problems with the installation there is a forum available where

support is provided by the forum moderators. Once the software is installed

successfully the next step will be to import one of the open reference model

packages. This functionality used to import the models is explained in the next

section.

User Guide to Import an ADL File

There is a simple way to exchange models in the ADONIS environment. The ADL

Import/Export component allows you to save your models in text format (ASCII)

and, if necessary, import them into a different ADONIS:CE database to share with

other users. The different model packages have been created using this

functionality. As mentioned the user must Import a model package to read the

contents of the models.

To Import a model package to the ADONIS Community Edition please follow the

steps below.

1. From the main menu bar the Import/Export Component must be selected.

See Figure 17 below.

Figure 17 - ADONIS Component Bar

2. Then click on Model – ADL Import – Models/Attribute Profiles, see Figure

18 below.



January 2014 30 BOC

Figure 18 - ADL Import Dialog

3. From the next dialog the user must browse for and select the .adl file that

contains the open reference models and click OK. See Figure 19 below.

Figure 19 - ADL file import dialog

4. Then on the next dialog the user must select all the models they would

like to import from the .adl file and on the right hand side you choose a

model group folder where you want the models to be stored. This will

typically be a model group called Models for a first time model import.

Click Import. See Figure 20 below.


January 2014 31 BOC

Figure 20 - ADONIS Model Import Selection Dialog

If any changes are made the open reference models and the end user would like

to export the results to be shared with other users they need to follow the steps

outlined below.

1. From the main menu bar, select “Model”, “ADL Export/Import” and specify

the export/import options.

2. Through tabs "Models" and "Attribute profiles" you can toggle between

model and attribute profile selection. In the window "Selection" the

complete hierarchy of models, model groups or attribute profiles are

visible.

3. Select in the window "ADL Export - Selection" the models and/or model

groups to be exported.

4. Define the required export options:

Including models – The selected models will be imported.

Including referenced models – Apart from the selected models to be

exported, the models referenced to these selected models will be

exported - regardless of their selection. Clicking on the option

"References" will enable you to change the settings.

Including model groups – The selected model groups will be exported.

Recursive (model groups) – Separately from the selected model groups

to be exported, all the sub groups of all hierarchy levels will be

exported. ("Recursive (model groups)" is only accessible, if option

"Model groups" is active.)

Including referenced attribute profiles – All referenced attribute profiles

of the models to be exported will also be exported. ("Including

referenced attribute profiles" is only accessible, if the option "Models"

is active.)

User Guide to Upload an ADL File to the Portal

When the end user is satisfied with the content of the their open models and

would like to use them in a simulation run using the Adapt4EE Platform it is

necessary to convert the open reference models into a format that can be

imported into the CIM and that is aligned to the CIM XML schema. To do so the


January 2014 32 BOC

end user must upload the .adl file to the Adapt4EE online collaboration portal

which is available at the following URL:

http://83.65.190.83/ADAPT4EEAPP/

The user is presented with the login screen that can be seen in Figure 21 and can

login using the user name and password provided.

Figure 21 - Online Collaboration Portal

After logging in to the portal the first step is to browse for the .adl file that has

been exported from the ADONIS Community Edition by clicking on Model

Management > Upload model as shown in Figure 22 below. The user then can

browse for the exported file and upload it to the online collaboration portal.

Figure 22 - Online Collaboration Portal Model Upload Function

User Guide How to Export the CIM Data

The final step is to export the business processes to the XML schema that has

been aligned with the Common Information Model (CIM). To do so the user can

either export a single model to be used as part of a building simulation run or a

complete package of models contained in a model group. When the user right

clicks on either a single model or on a model group they are presented with the

context menu illustrated in Figure 23 below. Once the user clicks on the menu

item highlighted “XML (CIM Schema) Export” then the business process(es) and

http://83.65.190.83/ADAPT4EEAPP/


January 2014 33 BOC

enterprise related data are exported as an XML file that has been aligned with the

CIM schema.

Figure 23 - Context Menu to Export Models to CIM


January 2014 34 BOC

Annex III: Open Reference Models Cover Sheets

Figure 24 - Model Package Cover Sheet Template

Figure 25 - Healthcare Cover Sheet


January 2014 35 BOC

Figure 26 - Healthcare - Administration Cover Sheet

Figure 27 - Healthcare – Daycare Cover Sheet


January 2014 36 BOC

Figure 28 - Healthcare - Nephrology Cover Sheet

Figure 29 - Healthcare - Oncology Cover Sheet


January 2014 37 BOC

Figure 30 - Software House Cover Sheet

Figure 31 - Software House - Design and Development


January 2014 38 BOC

Figure 32 - Software House - Financial Cover Sheet

Figure 33 - Software House - Innovation Cover Sheet


January 2014 39 BOC

Figure 34 - Software House - Procurement Cover Sheet

Figure 35 - Eye Clinic Cover Page

project title: occupant aware, intelligent and adaptive ... · the tool/service infrastructure...

Documents