Overview of th Capability Idea
Download as PPTX, PDF0 likes394 views
This document proposes an approach called Capability Driven Development (CDD) to support evolving organizations. CDD models an organization's capabilities as patterns that can be configured and adapted at runtime to respond to changing business contexts. The document outlines key CDD concepts like capabilities, contexts, goals and patterns. It presents an initial meta-model and an extended meta-model considering cloud services. An example case shows how capabilities for older and modern buildings are modeled with different contexts, goals and patterns. The document concludes by outlining needs for CDD methods, tools, patterns and business models.
Overview of th Capability Idea
- 1. Capability Driven Development – an Approach to Support Evolving Organizations Janis Stirna1, Jānis Grabis2, Martin Henkel1, Jelena Zdravkovic1 1 Department of Computer and Systems Sciences, Stockholm University, Sweden 2 Information Technology Institute, Riga Technical University, Latvia paper at PoEM 2012
- 2. Outline Background and the challenge The Capability Concept Meta-model for Capability Modeling Example case Outlook…
- 3. Background: Enterprise Modelling (EM) EM is a method for developing, acquiring, and communicating enterprise knowledge and user requirements by a structured, iterative, and modelling approach. The approach is guided by a number of conceptual sub-models, each focusing on a particular aspect of the application. The EM process involves a group of stakeholders and a modelling facilitator EM application in practice is usually supported by computerized tools – EM tools us es , refers _to G o als M o d el m otiv ates , requires C o n cep ts M o d el defines , is _res pons ible_for m otiv ates , affec ts , requires defined_by us es , refers _to B usiness R u les B u sin ess R ules odel M o d el defines , is _res pons ible_for triggers A cto rs an d R eso u rces M o d el defines s upports us es , produc es B u sin ess P ro cess M o d el perform s , is _res pons ible_for m otiv ates , requires refers _to T ech n ical C o m p o n en ts an d R eq u irem en ts M o d el 3
- 4. Background: patterns in an organizational setting generic and abstract organisational design proposals that can be easily adapted and reused in different organisational situations 4
- 5. Background: Patterns can be executable The AKM platform, developed in the MAPPER project 5
- 6. The Challenge Changing business contexts Influences of collaborators’ business models Limited support for changes in non-functional requirements Inability to model execution contexts High cost of developing applications for different contexts Limited platform usage Gap between EM and MDD
- 7. Capability We need: rapid response to changes in the business context development of new capabilities run-time configuration and adjustment of applications Capability is the ability to continuously deliver a certain business value in dynamically changing circumstances.
- 8. Key Concepts Enterprise and capability models Goal KPI Capability delivery context models Context KPI Capability delivery patterns Resource allocation Process variants Service and/or cloud variants
- 9. Initial meta-model for Capability Design requires Contextl KPI Goal KPI requires Measurable Property Context Type KPI measured by defines influences Context Situation has Context requires Pattern requires supported by Process Variant Capability requires requires Process Goal motivates Resource
- 10. requires Extended meta-model considering cloud services Contextl KPI Goal KPI requires Measurable Property measured by Context Type KPI defines influences Context has Context Set has status has requires supported by Context Situation requires Pattern Process Variant delivered by requires Capability requires requires Goal motivates Process supported by Resource Design Delivery Cloud Service IaaS related _to PaaS realized SaaS Service Component Operational SC has Implementation (BPEL, WSDL) Business SC Cloud Resource
- 11. Example Case A building operator aims to run its buildings efficiently and in an environmentally sustainable manner FP7 project EnRiMa – Energy Efficiency and Risk Management in Public Buildings Different buildings to be operated efficiently in different environments Market conditions Energy technologies ICT technologies
- 12. Example Case: Goal Model Goal 1: To run the building efficiently and environmentally sustainable Goal 1.1: To satisfy occupant requirements require GoalKPI: Occupant satissfaction GoalKPI: Desired temperature (C) Goal 1.2: To minimize CO2 emissions Goal 1.3: To minimize energy consumption Goal 1.4: To minimize energy costs Goal 1.5: To use renewable energy requires requires requires requires GoalKPI: CO2 emissions (kg per year) GoalKPI: Energy consumption (kWh/m2) GoalKPI: Enery costs (€) GoalKPI: Renewables (%) FP7 project EnRiMa – “Energy Efficiency and Risk Management in Public Buildings” (proj. no. 260041)
- 13. Capability, context and capability delivery pattern for “Older building with low ICT infrastructure” Cability: Older building, low ICT infrastructure ReqContext: No PV installed ReqContext: No energy storage ReqContext: Some data available ReqContext: Closed ICT infrastructure, ReqContext: Fixed price energy contracts required by Context situation: MI building in Riga Context: No PV installed Context: No energy storage Context: Fixed electricity and gas prices Context KPI: desired temperature 19 C Context KPI: CO2 emissions 1100 kg per year) Context KPI: Energy consumption 200 kWh/m2 Context KPI: Enery costs 100000€ Context: Closed proprietary system Context: Ambient temperature data for 3 months Context KPI: Renewables 5% Pattern: Older building, low ICT Solution: supported by Proc: Energy audit and configuration Proc: Infrastructure integration process Proc: Deploymen in cloud Proc: negotiate temperature intervals with the occupants Proc: Passive monitoring and advisory mode for these KPIs uses uses required by required by Pattern: Manual data entry Pattern: Run template based audit
- 14. Capability, context and capability delivery pattern for “Modern building with high ICT infrastructure.” Cability: Modern building, high ICT infrastructure ReqContext: No PV installed ReqContext: No energy storage ReqContext: Sensor data available ReqContext: Open ICT infrastructure, ReqContext: Open energy market supported by required by Context situation: AH building in Stockholm Context: No PV installed Context: No energy storage Context: Spot pricing model Context KPI: desired temperature 18.521.5 C Context KPI: CO2 emissions 1100 kg per year) Context KPI: Energy consumption 90 kWh/m2 Context KPI: Enery costs 100000€ Context: Siemens Desigo building management system Context: Sensor data available for 2 years Context KPI: Renewables 50 % required by required by Pattern: Modern building, high ICT Solution: Proc: Energy audit and configuration Proc: Infrastructure integration process Proc: Deployment as external service Proc: negotiate temperature intervals with the occupants Proc: daily update of building sensor data, weather data, pricing data, scenario generation Proc: Active optimization with these KPIs Pattern: Integrate with Siemens Desigo uses Pattern: Run full energy audit
- 15. Two Capability Delivery Patterns Capability Capability: Old Capability: Modern delivery pattern building, low ICT building, high ICT contains: ICT infrastructure integration process Pattern: Manual data entry Pattern: Integrate with Siemens Desigo Energy audit and configuration Pattern: Template based audit Pattern: Run full energy audit
- 16. CDD Methodology Business change & Required capability 16
- 17. What we need… Methods for capability design pattern capturing and design; matching with capabilities Runtime adjustment … Tools … Actual patterns (e.g. best practices, services, etc) … Business models ….