ICT

Application of SHAPE Technologies in Production and Process Optimization

IESA 2010 WorkshopUse of MDI/SOA concepts in Industry

Brian Elvesæter1, Arne-Jørgen Berre1 and Einar Landre2

1 SINTEF ICT, P. O. Box 124 Blindern, N-0314 Oslo, Norway2 Statoil, Forusbeen 50, N-4035 Stavanger, Norway

ICT

Presentation Outline

SHAPE FP7 Project Solution Overview SoaML Solution Matrix Methodology Framework

Statoil Case Study Business Context Use Case Challenges

Application of SHAPE Technologies Questions

ICT

SHAPE FP7 Project

Project acronym SHAPE

Project full title Semantically-enabled

Heterogeneous Service Architecture and Platforms Engineering

Grant agreement number ICT-2007-216408

Website http://www.shape-project.eu/

Duration 30 months Dec 2008 – June 2010

Objective Develop an infrastructure for

model-driven engineering for service-oriented landscapes with support for various technology platforms and extensions for advanced service provision and consumption techniques.

Partners SINTEF (Norway) ESI (Spain) SAP AG (Germany) SOFTEAM (France) UIBK (Austria) DFKI (Germany) Statoil (Norway) Saarstahl (Germany)

ICT

SHAPE Solution Overview The technologies developed in the

project are centred around SoaML Metamodel for describing service-

oriented landscapes that is standardized in OMG.

SoaML is extended with metamodels for other technology platforms advanced service engineering

techniques The project provides

integrated tool suite that supports the modelling

encompasses the necessary model transformations

methodology framework that provides role-specific guided procedures for creating all model types and supports the creation of customized methodologies for individual engineering projects

SoaML

CoreService

Variability

PIM4SWS

PIM4Agents

P2P/Grid/Components/…

SHA-ML

WSDL, WSMO, OWLS, JACK, JADE, JXTA, OGSA, CORBA, …

J2EE, NetWeaver, .Net, …

Flexible Business ModellingBPMN EPC BMM

PIMsfor differentArchitectural Styles

Execution Environments

PSMImplementation Models

CIMBusiness Models

PIMSystem Models

…

SoaML

CoreService

Variability

PIM4SWS

PIM4Agents

P2P/Grid/Components/…

SHA-ML

WSDL, WSMO, OWLS, JACK, JADE, JXTA, OGSA, CORBA, …

J2EE, NetWeaver, .Net, …

Flexible Business ModellingFlexible Business ModellingBPMN EPC BMM

PIMsfor differentArchitectural Styles

Execution Environments

PSMImplementation Models

CIMBusiness Models

PIMSystem Models

…

ICT

SoaML

Service oriented architecture Modeling Language (SoaML) Extensions to UML2.1 to

support service concepts. SoaML focuses on the basic

service modelling concepts. A foundation for further

extensions both related to integration with other OMG metamodels like BPMN 2.0, SBVR, OSM, ODM and others.

Website: http://www.soaml.org

Capabilities: identifying services specifying services defining service consumers and

providers policies for using and providing

services. defining classification schemes defining service and service

usage requirements and linking them to related OMG metamodels, such as the BMM and BPMN 2.0.

ICT

SHAPE Solution Matrix

Meta-Models

Model Trans-formations

SHAPE Tool Suite

SHAPE Methodology

Flexible Business Modelling

Service & SOA Modelling

Integration of Agent Technology

Integration of SWS Technologies

Service Customization

1

2

3

4

5

BPMN, EPCData, Org., RulesBMM, Ontologies

SoaML

SHAML – Agent Extension

SHAML – SWS Extension

Service Variability Metamodel

Tech

nolo

gica

l Inn

ovat

ions

CIM->CIM (mult.)CIM -> PIM (mult.)

SoaML -> WS SoaML -> JEE

SoaML -> PIM4AgentsPIm4Agents -> PSM

SoaML-> SWSPimSWSPim -> WSMO

SoaML-> SV-Spec.SV-Res. -> Soaml

CIMFlexModelio

ModelioComposition Studio

PIM4Agents

WSMT

Service Variability Tools

CIMFlex ModelingBPMN + UML Ontology Engin.

SoaML & WS Modelling

Agent Modelling (PIM ->PIM2PSM->PSM)

Service Variability Modelling & Variant Creation

SWS Modelling (PIM ->PIM2PSM->PSM)

MDE Infrastructure

ICT

SHAPE Methodology Framework

Methods provide structured guidance. A matrix structure for organizing the

methodology content. Partial processes that define suitable

engineering procedures. Use and extend the Eclipse Process

Framework (EPF).

ICT

The focus now is implementation of IO generation 1 solutions and strategic planning of IO generation 2 solutions.

Generation 1 activities focus on integration across onshore and offshore, while generation 2 activities focus on integration across companies.

Business Context Statoil is an integrated technology-

based international energy company primarily focused on upstream oil and gas operations. The oil and gas industry need to improve

operational efficiency. The Norwegian Oil Industry Association

(OLF) has defined the term Integrated Operations (IO) as “real time data onshore from offshore fields and new integrated work processes” . increased exchange of information

across geographical and organizational boundaries, internally and externally.

drive for new IT solutions For this information exchange to be

successful, good interoperable IT solutions and standards are needed. With Integrated Operations the need for

standards are revitalized and changed.

ICT

Use Case Challenges

Production and Process Optimization (PPO) Use case within Integrated

Operations

Business and SoaML Modelling1. Enable integrated and

comprehensive modelling of the business processes.

2. Design services for enabling the consistent and automated information exchange among the various IT systems.

Service Variability3. Enable system integration via

central services using simplified variants that allow an easy usage and integration.

Semantic Web Services4. Handle the integration of the often

incompatible information and data structures used within the various production systems.

ICT

Application of SHAPE Technologies

SHAPE Methodology Tool

01

2

3 4 Define service variability (4) and semantic web service (5) for PRODML subset

Define the methodology for the use case

Define the business architecture for PPO

Specify the service-oriented architecture for PPO

MethodEngineer

BusinessArchitect

SystemArchitect

SystemDeveloper

ICT

Define Methodology

Business challenge Methodological support

for service and system engineering

Provide guidance for the various roles

Adaptable to individual scenarios

Role Method Engineer

SHAPE technologies SHAPE Methodology

Customization Tool

Tool suite steps Methodology configuration

wizard

Custom delivery process Publish methodology website

0

ICT

Business Modelling

Business challenge Enable integrated and

comprehensive modelling of the business processes.

Derive and specify IT requirements/services that aligns with the business models

Role Business Architect

SHAPE technologies CIMFlex Modelio

Tool suite steps BMM modelling

BPMN modelling

1

Optimize process facilitites

Optimize production network

Optimize intelligent wells

Optimize reservoir performance Production optimization

Improved reservoir management

<<part>>

<<part>>

<<part>>

<<part>> <<+influence>>

ICT

Service Modelling (1/2)

Business challenge Specify and design new

services for PPO Modernise/wrap existing

services using standards such as PRODML

Role System Architect

SHAPE technologies SoaML Modelio

Tool suite steps Services Architecture

Network of participant roles providing and consumingservices to fulfil a purpose.

2

ContinuousProductionOptimization<<ServicesArchitecture>>

rsadoa:ReviewSuggestionsAndDecideOnActions

opf:OptimizeProcessFacility

dpmao:DetailedProductionMonitoringAndOptimization

iaatal:ImplementActionsAccordingToActionList

cpi:ConductPOGInteraction

facility

coordinator

:OPSLeader

:ProcessEngineer

:POGCoordinator

:DPOGroup

:HeadOfOperations

ICT

Service Modelling (2/2)

Tool suite steps (cont.) Service contracts/interfaces

Defines the terms, conditions, interfaces and choreography.

Participants Represent organizational units

or system components.

Tool suite steps (cont.) Operation signatures Message types

*comment

* componentC ontent

0..1sourceFlow

1..*0..1

period

0..1

productVolumes

0..1

productVolumes

documentInfo0..1

<<query>>produc tV olumeQ uerySet

0..1

<<query>>productVolumeQuerySet

0..1

produc tV olume

*

commonData

0 ..1

cus tomData

0..1

operator

0..1

geographicC ontext

0..1

issuedBy

0..1

approver

0..1

facility

0..1

1..*

personName

0..1

address

*

offshoreLocation

0..1

northSeaO ffshore1

downtimeReason

*parameterSet

*

flow

0..1 *comment

*

relatedFac ility

0..1

portDiff

*

product

0..1*

volumeV alue 0..1

componentC ontent*

comment

*

alert

0 ..1

produc tV olumes

0..1produc tV olumeQ uerySet

0..1

PROD_ProductVolumeSoap_GiveDataType<<SOAML.MessageType>> PROD_ProductVolumeSoap_GetSupportedPatternsResponseType

<<SOAML.MessageType>>

cs_productVolumeAlert

cs_volumeValue

cs_productVolumeComponentContent

cs_refProductFlow

cs_productVolumePeriod

cs_productVolumeProduct

cs_productVolumePortDifference

cs_productVolumeRelatedFacility

cs_productVolumeFlow

cs_productVolumeParameterSetcs_datedComment cs_northSeaOffshore

cs_offshoreLocation

cs_generalAddress

cs_personName

cs_productVolumeFacility

cs_geographicContext

cs_businessAssociategrp_productVolume

obj_productVolume

PROD_ProductVolumeSoap_GetDataAsyncResultsResponseType<<SOAML.MessageType>>

PROD_ProductVolumeSoap_GetDataSyncResponseType<<SOAML.MessageType>>obj_productVolumes

PROD_ProductVolumeSoap_GetDataAsyncInitiateType<<SOAML.MessageType>>

PROD_ProductVolumeSoap_GetDataSyncType<<SOAML.MessageType>>

PROD_ProductVolumeSoap<<interface, SOAML.ServiceInterface>>

cs_customData

cs_commonData

cs_documentInfoProdml

description : commentStringtype : kindStringleve l : kindStringtarget : commentString

pres : pressureMeasuretemp : thermodynamicTemperatureMeasurevolume : volumeQualifiedMeasure

moleAmt : amountOfSubstanceMeasureconcentration : volumePerVolumeMeasuredensityStd : densityMeasuredensityFlowRate : massFlowRateMeasuredensity : densityMeasurereferenceKind : ReportingProductk ind : ReportingProductuid : uidString

parentfacility : refNameStringreferencedFlow : refNameString

moleAmt : amountOfSubstanceMeasureefficiency : volumePerVolumeMeasurework : workMeasuremass : massMeasurepres : pressureQualifiedMeasuretemp : thermodynamicTemperatureQualifiedMeasureflowRate : volumeFlowRateQualifiedMeasurevolumeStd : volumeQualifiedMeasurevolume : volumeQualifiedMeasuredateEnd : datedateStart : datedTimEnd : timestampdTimStart : timestampdate : datedTim : timestampkind : ReportingPerioduid : uidString

densityStabilizedCrude : densityMeasurebswStabilizedCrude : volumePerVolumeMeasurervpStabilizedCrude : pressureMeasuregrossCalorificValueStd : modulusOfCompressionMeasurewobbeIndex : modulusOfCompressionMeasurewaterDewpoint : thermodynamicTemperatureMeasurehcDewpoint : thermodynamicTemperatureMeasuresg : dimensionlessMeasuredensityStd : densityMeasuredensity : densityMeasurebswPrevious : volumePerVolumeMeasurebsw : volumePerVolumeMeasuretvp : pressureMeasurervp : pressureMeasuresplitFactor : nonNegativeFractionname : nameStructkind : ReportingProductuid : uidString

chokeRelative : lengthPerLengthMeasurechokeSize : lengthMeasuretempDiff : thermodynamicTemperatureMeasurepresDiff : pressureMeasureport : refNameStringuid : uidString network : refNameString

unit : refNameStringport : refNameStringk ind : ReportingFacilityfacilityParent2 : facilityIdentifierStructfacilityParent1 : facilityIdentifierStructname : facilityIdentifierStruct

absoluteMinPres : pressureMeasurepres : pressureMeasuretemp : thermodynamicTemperatureMeasureatmosphere : pressureMeasurewaterConcVol : volumePerVolumeMeasurewaterConcMass : massConcentrationMeasuregorMTD : volumePerVolumeMeasuregor : volumePerVolumeMeasuresourceFlow : refNameStringversionSource : nameStringversion : timestampsubQualifier : FlowSubQualifierqualifier : FlowQualifierfacilityAlias[*] : nameStructfacility : facilityIdentifierStructdirection : ProductionFlowPortTypeport : re fNameStringkind : ReportingFlowname : nameStringuid : uidString

remark : commentStringdTimEnd : timestampdTimStart : timestamprole : k indStringwho : nameStringuid : uidString

blockSuffix : str2quadrant : nameStringareaName : nameString

comment : commentStringblockID[1..4] : nameStringareaName : nameString

postalCode : kindStringcountry : nameStringcounty : nameStringprovince : nameStringstate : nameStringcity : nameStringstreet[1..4] : nameStringname : nameStringuid : uidStringkind : AddressKindEnum

suffix[0..9] : nameStringlast : nameStringmiddle : nameStringfirst : nameStringprefix : nameString

operationTime : timeMeasurecapacity : volumeMeasurewellInjecting : logicalBooleanwellProducing : logicalBooleancontextFacility : facilityIdentifierStructnetwork : refNameStringunit : refNameStringfacilityAlias : nameStructfacilityParent2 : facilityIdentifierStructfacilityParent1 : facilityIdentifierStructname : facilityIdentifierStructuid : uidString

comment : commentStringfield : nameStructstate : nameStringcountry : nameString

comment : commentStringpersonnelCount : nonNegativeCountcontact[*] : refNameStringassociatedWith : re fNameStringcontactPreference[*] : ContactPreferenceemail[*] : emailQualifierStructphoneNumber[*] : phoneNumberStructa lias[*] : nameStructrole[1..*] : nameStructname : nameStringuid : uidString

standardTempPres : StandardTempPressproductFlowModel : re fNameStringapprovalDate : dateissueDate : datetitle : nameStructcalculationMethod : CalculationMethoddTimCurrent : timestampdTimMax : endpointQualifiedDateTimedTimMin : endpointQualifiedDateTimedateEnd : datedateStart : datedTimEnd : timestampdTimStart : timestampperiodKind : ReportingPeriodk ind : kindStringcontextFacility[*] : facilityIdentifierStructinstallation : facilityIdentifierStruct

name : nameStructuid : uidString

version : schemaVersionStringProdml

Options : Options

Options : Options

GetSupportedPatterns(in Parameter : GetSupportedPatternsType):PROD_ProductVolumeSoap_GetSupportedPatternsResponseTypeGetServiceInfo(in Parameter : GetServiceInfoType):GetServiceInfoResponseTypeGiveData(in Parameter : PROD_ProductVolumeSoap_GiveDataType):GiveDataResponseTypeGetDataAsyncResults(in Parameter : GetDataAsyncResultsType):PROD_ProductVolumeSoap_GetDataAsyncResultsResponseTypeGetDataAsyncControl(in Parameter : GetDataAsyncControlType):GetDataAsyncControlResponseTypeGetDataAsyncStatus(in Parameter : GetDataAsyncStatusType):GetDataAsyncStatusResponseTypeGetDataAsyncInitiate(in Parameter : PROD_ProductVolumeSoap_GetDataAsyncInitiateType):GetDataAsyncInitiateResponseTypeGetDataSync(in Parameter : PROD_ProductVolumeSoap_GetDataSyncType):PROD_ProductVolumeSoap_GetDataSyncResponseType

any[*] : xs:anyType

comments : commentStringitemState : ItemStatedTimLastChange : timestampdTimCreation : timestampsourceName : nameString QueryParam : queryParam

AuditTrail : auditTypesecurityInformation : SecurityInfoTypeProdmlFileCreationInformation : fileCreationType

2

OptimizeProcessFacility<<ServiceContract>>

OptimizeProcessFacilityInterface<<ServiceInterface>>

ProcessFacility<<interface>>

ProcessCoordinator<<interface>>

Actions()ChokePositions()

Confirmation()

processFacility:ProcessFacilitycoordinator:ProcessCoordinator

facility:ProcessFacilitycoordinator:ProcessCoordinator

POGCoordinator<<Participant>>

ProcessEngineer<<Participant>>

:OptimizeProcessFacilityInterface :OptimizeProcessFacilityInterface

ProcessFacility

ProcessCoordinatorProcessCoordinator

ProcessFacility

ICT

Define service variability

Business challenge Exists legacy systems with

complex interfaces. Want to integrate these using

simplified service variants. Want to make use of industry

standards (complex). Only want to use suitable

subset of standards. Role

System Developer SHAPE technologies

Service Variability Tool Modelio

Tool suite steps Import the SoaML model Specify the service variant Specify the service resolution Export the service variant

Import into Modelio Generate the WSDL

3

0 ..1

alert

*

comment

* componentC ontent

0 ..1volumeV alue

* 0..1

product

*

portDiff

0 ..1

relatedFac ility

*

comment *0..1

flow

*

parameterSet*

downtimeReason

1 northSeaO ffshore

0 ..1

offshoreLocation

*

address

0 ..1

personName

1..*

0..1

facility

0 ..1

approver

0 ..1

is suedBy

0..1

geographicC ontext

0 ..1

operator

0 ..1

cus tomData

0 ..1

commonData

*

produc tV olume

0..1 documentInfo

period

0..1 1..*

sourceFlow 0 ..1

componentC ontent*

comment *

<<query>>productVolumeQuerySet

0..1 productVolumes

0..10..1

produc tV olumes

0..1<<query>>productV olumeQ uerySet

0 ..1

cs_productVolumeAlert

cs_volumeValue

cs_productVolumeComponentContent

cs_refProductFlow

cs_productVolumePeriod

cs_productVolumeProduct

cs_productVolumePortDifference

cs_productVolumeRelatedFacility

cs_productVolumeFlow

cs_productVolumeParameterSetcs_datedComment cs_northSeaOffshore

cs_offshoreLocation

cs_generalAddress

cs_personName

cs_productVolumeFacility

cs_geographicContext

cs_businessAssociategrp_productVolume

obj_productVolume

obj_productVolumes

cs_customData

cs_commonData

cs_documentInfoProdml

PROD_ProductVolumeSoap_SimpleVariant<<interface, SOAML.ServiceInterface>>

PROD_GetDataSyncType_SimpleVariant<<SOAML.MessageType>>

PROD_GetDataSyncResponseType_SimpleVariant<<SOAML.MessageType>>

PROD_GiveDataType_SimpleVariant<<SOAML.MessageType>>

PROD_GetSupportedPatternsResponseType_SimpleVariant<<SOAML.MessageType>>

description : commentStringtype : k indStringlevel : k indStringtarget : commentString

pres : pressureMeasuretemp : thermodynamicTemperatureMeasurevolume : volumeQualifiedMeasure

moleAmt : amountOfSubstanceMeasureconcentration : volumePerVolumeMeasuredensityStd : densityMeasuredensityFlowRate : massFlowRateMeasuredensity : densityMeasurereferenceKind : ReportingProductkind : ReportingProductuid : uidString

parentfacility : refNameStringreferencedFlow : refNameString

moleAmt : amountOfSubstanceMeasureefficiency : volumePerVolumeMeasurework : workMeasuremass : massMeasurepres : pressureQualifiedMeasuretemp : thermodynamicTemperatureQualifiedMeasureflowRate : volumeFlowRateQualifiedMeasurevolumeStd : volumeQualifiedMeasurevolume : volumeQualifiedMeasuredateEnd : datedateStart : datedTimEnd : timestampdTimStart : timestampdate : datedTim : timestampkind : ReportingPerioduid : uidString

densityStabilizedCrude : densityMeasurebswStabilizedCrude : volumePerVolumeMeasurervpStabilizedCrude : pressureMeasuregrossCalorificValueStd : modulusOfCompressionMeasurewobbeIndex : modulusOfCompressionMeasurewaterDewpoint : thermodynamicTemperatureMeasurehcDewpoint : thermodynamicTemperatureMeasuresg : dimensionlessMeasuredensityStd : densityMeasuredensity : densityMeasurebswPrevious : volumePerVolumeMeasurebsw : volumePerVolumeMeasuretvp : pressureMeasurervp : pressureMeasuresplitFactor : nonNegativeFractionname : nameStructkind : ReportingProductuid : uidString

chokeRelative : lengthPerLengthMeasurechokeSize : lengthMeasuretempDiff : thermodynamicTemperatureMeasurepresDiff : pressureMeasureport : refNameStringuid : uidString network : refNameString

unit : refNameStringport : refNameStringkind : ReportingFacilityfacilityParent2 : facilityIdentifierStructfacilityParent1 : facilityIdentifierStructname : facilityIdentifierStruct

absoluteMinPres : pressureMeasurepres : pressureMeasuretemp : thermodynamicTemperatureMeasureatmosphere : pressureMeasurewaterConcVol : volumePerVolumeMeasurewaterConcMass : massConcentrationMeasuregorMTD : volumePerVolumeMeasuregor : volumePerVolumeMeasuresourceFlow : refNameStringversionSource : nameStringversion : timestampsubQualifier : FlowSubQualifierqualifier : FlowQualifierfacilityAlias[*] : nameStructfacility : facilityIdentifierStructdirection : ProductionFlowPortTypeport : refNameStringkind : ReportingFlowname : nameStringuid : uidString

remark : commentStringdTimEnd : timestampdTimStart : timestamprole : k indStringwho : nameStringuid : uidString

blockSuffix : str2quadrant : nameStringareaName : nameString

comment : commentStringblockID[1..4] : nameStringareaName : nameString

postalCode : k indStringcountry : nameStringcounty : nameStringprovince : nameStringstate : nameStringcity : nameStringstreet[1..4] : nameStringname : nameStringuid : uidStringkind : AddressKindEnum

suffix[0..9] : nameStringlast : nameStringmiddle : nameStringfirst : nameStringprefix : nameString

operationTime : timeMeasurecapacity : volumeMeasurewellInjecting : logicalBooleanwellProducing : logicalBooleancontextFacility : facilityIdentifierStructnetwork : refNameStringunit : refNameStringfacilityAlias : nameStructfacilityParent2 : facilityIdentifierStructfacilityParent1 : facilityIdentifierStructname : facilityIdentifierStructuid : uidString

comment : commentStringfield : nameStructstate : nameStringcountry : nameString

comment : commentStringpersonnelCount : nonNegativeCountcontact[*] : refNameStringassociatedWith : refNameStringcontactPreference[*] : ContactPreferenceemail[*] : emailQualifierStructphoneNumber[*] : phoneNumberStructalias[*] : nameStructrole[1..*] : nameStructname : nameStringuid : uidString

standardTempPres : StandardTempPressproductFlowModel : refNameStringapprovalDate : dateissueDate : datetitle : nameStructcalculationMethod : CalculationMethoddTimCurrent : timestampdTimMax : endpointQualifiedDateTimedTimMin : endpointQualifiedDateTimedateEnd : datedateStart : datedTimEnd : timestampdTimStart : timestampperiodKind : ReportingPeriodkind : k indStringcontextFacility[*] : facilityIdentifierStructinstallation : facilityIdentifierStruct

name : nameStructuid : uidString

version : schemaVersionStringProdml

any[*] : xs:anyType

comments : commentStringitemState : ItemStatedTimLastChange : timestampdTimCreation : timestampsourceName : nameString QueryParam : queryParam

AuditTrail : auditTypesecurityInformation : SecurityInfoTypeProdmlFileCreationInformation : fileCreationType

GetDataSync(in Parameter : PROD_GetDataSyncType_SimpleVariant):PROD_GetDataSyncResponseType_SimpleVariantGiveData(in Parameter : PROD_GiveDataType_SimpleVariant):GiveDataResponseTypeGetSupportedPatterns(in Parameter : GetSupportedPatternsType):PROD_GetSupportedPatternsResponseType_SimpleVariant

ICT

Define Semantic Web Services

Business challenge Dynamic service request (based on

goals) Information mapping between

different data formats and structures

EC legacy system with approved Well Test data

IFM legacy system with estimated Well Test data

Use PRODML WellTest subset Role

System Developer SHAPE technologies

Modelio with SoaML4SWS WSMT WSMX

Tool suite steps Define

ontologies Transform

to WSML Refine

WSML

4

ICT

Evaluation of Results In the progress of writing up the final validation report.

Statoil participates in research projects such as a SHAPE as part of a technology feasibility study in order to experiment with and evaluate new technology and methodological approaches.

The evaluation will provide an input to future strategic decision regarding technology and methodology choices.

Initial conclusions The SHAPE results (languages, tools and methods) do provide the main concepts

and support for constructing business and service models. Business and SoaML modelling Service Variability Semantic Web Services

Methodology improvement areas Too “technology-driven” (CIM, PIM, and PSM) – should be more focused on users (roles

and tasks) Improve methodology website/navigation structure for users Some guidelines need revision (BPMN 2.0, aligned with latest changes of SoaML) Further illustrative examples.

Tool suite improvement areas Usability issues Integration issues

ICT

Thanks for your attention!

Questions?