1 / 60

Rethinking the Integrative Foundation of Enterprises – The Activity Domain Theory

Rethinking the Integrative Foundation of Enterprises – The Activity Domain Theory. Lars Taxén Linköping University www.neana.se lars.taxen@gmail.com. My background. Methods, processes, IT, Information systems project management. 34 yrs. Coordination & Integration

blake
Download Presentation

Rethinking the Integrative Foundation of Enterprises – The Activity Domain Theory

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Rethinking the Integrative Foundation of Enterprises – The Activity Domain Theory Lars Taxén Linköping University www.neana.se lars.taxen@gmail.com

  2. My background Methods, processes, IT, Information systems project management 34 yrs Coordination & Integration PhD (2003), Associate prof. (2007) >15 yrs > 10 yrs Consulting (2009)

  3. Outline • My professional context • Some existing integrational approaches • The Activity Domain • Integrating product development • The System Anatomy • The Enterprise Anatomy • IT system implementation • Some takeaways

  4. My professional context

  5. Enterprise Integration! ? Wikipedia Creative Commons

  6. Some existing integrational approaches

  7. ??? • …. • Design/ Build Hubble Window • Construct Hardware • Design / build Mission Control Table • ….

  8. ???

  9. ???

  10. Zachman EA

  11. All yellow classes are Baselined Product Portfolio Main Requirement All Green classes are Items: should have the following (from Product Mgmt) 1 1 1 1 1..* 1..* structured in (from Product Mgmt) BOS Not Baselined Items attribute: 0..1 0..1 structured by configurations slogan (from Product Mgmt) Identification, status, version variants content stability customer name product versions generates project priority target system type generates market opportunity 0..1 0..1 1..* 1..* 0..* 0..* source bunisess area 1 1 customerPriority description 1..* 1..* grouped into Change Request Feature (FAJ) (from Configuration Mgmt) (from Product Mgmt) impacts 1 1 specification specified by Customer 1..* 1..* description 1..* 1..* satisfies needs 1 1 changes (from Product Mgmt) benefits Reference Model agreement justified by 1 1 slogan (from System Domain) Acceptance Test criteria status checkpoint 1..* 1..* type Contract 1 1 (from Product Mgmt) Baseline (from Product Mgmt) Business Case agreed characteristics agreement 1..* 1..* (from Configuration Mgmt) committed delivery date 1 1 (from Product Mgmt) test strategy status grouped into penalty 1..* 1..* risk structured by description terms and condition opportunity version 1 1 0..* 0..* type 1..* 1..* verified by 1..* 1..* identifier Product release give reason for assumption Product package (from Product Mgmt) price interface constraints (from Product Mgmt) 1..* 1..* configuration cost 1 1 1..* 1..* sellable unit system release volume orderble unit R-state +trace from implemented in 0..* 0..* 0..* 0..* 1..* 1..* Delivery Product generates 1..* 1..* 1..* 1..* (from Project Mgmt) 1 1 Requirement included in +trace to 1..* 1..* 1..* 1..* (from System Domain) type (from System Domain) Use Case 0..* 0..* product no provider type (from System Domain) R-state satisfied in 1..* 1..* receiver status checkpoint brief description * * variant 1..* 1..* delivery quality area expected result 0..* 0..* specified by life cycle SoC 1..* 1..* delivery date agreement of source prerequisites (from Project Mgmt) configuration project priority flow description 1..* 1..* 1 1 deviation customer priority structure 1..* 1..* verified by impacts slogan 1 1 1..* 1..* verified by 1..* 1..* 1..* 1..* 1..* 1..* 1..* 1..* depends on 0..* 0..* +functional 1 1 0..1 0..1 {subset} 1..* 1..* Project Anatomy +functional 1..* 1..* System Anatomy agreed requirement (from Project Mgmt) +non-functional 1..* 1..* (from System Domain) 1 1 resource dependencies sw dependency mapping time depencencies group together Test Case 1 1 depends on 1..* 1..* o_hw dependency mapping cost dependencies (from System Doma... 1..* 1..* specification satisfied by 0..1 0..1 +test set type 1 1 1 1 1 1 test level 1 1 pre-requisites depends on based on based on Work Item 1 1 (from System Domain) 1..* 1..* Work package 1 1 1..* 1..* activity 1..* 1..* results in (from Project Mgmt) statement of verification Increment expected result resource estimation 1 1 1..* 1..* +content 1 1 1..* 1..* 1..* 1..* (from Project Mgmt) +content assigned to time estimation Test Result start cost estimation (from System Domain) end 1 1 milestone 1..* 1..* results in A Logical Data Model in practice…

  12. Another Logical Data model …

  13. What’s the difference?

  14. Model evolution A-domain ? 1996 1997 1998 1999 2000 2001 2002 2003 2004 S-domain X C-domain L-domain X

  15. Useless Useful Chiseled out “on the combat field” between 1996 - 2003 Defined by a consultant “in the chamber”

  16. Existing integrating approaches not particularly successful

  17. The Activity Domain- Back to basics- What does it take to integrate an activity?

  18. The Activity Domain Activity Modalities - objectivation Focus on a target, motivated by a need - contextualization Frame a context of relevance - spatialization Orient ourselves in space - temporalization Conceive of actions leading to the goal - stabilization Learn how to act relevantly - transition Change focus Enact means Align individual meanings

  19. Objectivation Contextualization Spatialization Temporalization Stabilization Transition Cognitive –Neural, inner realm Social, external realm Temporalization Spatialization

  20. The Activity Domain is regarded as the integrative foundation for all human activities, including organizational ones Why? Because we still employ the same biological abilities in all situations we encounter in every-day life, including organizations

  21. A contemporary Activity Domain PLM systems Target objectivation spatialization Cooperation Enact means Align individual meanings Business rules Information models temporalization transition Process models stabilization

  22. The structure of the Activity Domain outcome is a prerequisite for produces motive motivated by Activity Domain needs fulfills work object modifies has actors resources in enact capabilities based on activity modalities objectivation contextualization spatialization temporalization stabilization transition

  23. Integrating product development

  24. Management based on Activity Domains

  25. Early phases? ?

  26. “The most important thing when working with complex systems is to manage dependencies” Jack Järkvik (1990s)

  27. The System Anatomy- an integrating image in early phases

  28. Entrance Comfort Sanitation Nutrition Cleaning ? Ground

  29. Entrance Comfort Sanitation Nutrition Cleaning The System Anatomy What capabilities are needed? How do they depend on each other ? Ground

  30. Comfort Cleaning [shower, washing machine, water] Sanitation [water toilet, water] Nutrition [stove, refrigerator, food] Heating and cooling [heating element, AC] Basic comfort Precipitation protection [roof] Entering [door] Light inside [window] Wind protection [wall, door] Distribution [pipes, cables] Isolation [wall, floor, roof] Structure support [frame studs] Ground isolation [floor] Load distribution [foundation] Utility access [waste-pipe, electricity, water] Physical access [road] Anchoring [ground]

  31. Comfort Cleaning Sanitation Nutrition Heating and cooling Basic comfort Precipitation protection Entrering Light inside Wind protection Distribution Isolation A system anatomy for a house Structure support Ground isolation Load distribution Utility access Physical access Anchoring

  32. An anatomy for a processor SFC SW (33) MAS fault MAS Fault handling SFC handling SFC (HW) (SW) (33) (33) AXE Parameter MIP for SFC LA for SFC CPS - SW (20, 30, (33) (SW) (33) 33) MAS Fault handling capacity (HW) Serial RP bus at MIP I - test for (33) FC (20, 30, 33) SFC (33) SFC APS (33) FCSUC with new AXE Parameter FURAX interface IPU HW for DBS - SW (20, 30, (20, 30, 33) SFC (33) Loading 33) Communication Communication functions buffer (Restart) buffer CPS - SW MAS fault handling (SW) (33) (30, 33) (20) capacity (SW) (33) Backup in 212 33 SYREI, Initiated reload (30, 33) AXE Parameter Increase number of Parallel Start APS (20, 30, 33) blocks to 4K (SW) (33) APS Support for (30, 33) Communication Test/ Measurement buffer (20, 30, (SW) (33) 33) OCS over IPNA MAS CPT for (30, 33) capacity (33) IPNA Error handling (30, 33) CPS Kernel (SW) (33) MAS (SW) 100 Mbit Ethernet termination in 212 30 Start - Up , Single CP (33) CPT Initiate reload Initial load (33) (30, 33) MAS (SW) Increase of MIP Program store (30, 33) CP Reload from IPNA (30, 33) IPNA Load from AP (30, 33) Create Initial dump (33) MIP for Capacity De - Compress (33) dump in CP (20, 30, 33) MIP I - test for IPNA (30, 33) MIP I - test for IPNA Start Compress dump Capacity (33) DSU HW (30, 33) in I/O (IO 20, (30, 33) 30, 40) IPU HW for APG 40 Capacity (33)

  33. An anatomy for a processor (objectivation) SFC SW (33) MAS fault MAS Fault handling SFC handling SFC (HW) (SW) (33) (33) AXE Parameter MIP for SFC LA for SFC CPS - SW (20, 30, (33) (SW) (33) 33) MAS Fault handling capacity (HW) Serial RP bus at MIP I - test for (33) FC (20, 30, 33) SFC (33) SFC APS (33) FCSUC with new AXE Parameter FURAX interface IPU HW for DBS - SW (20, 30, (20, 30, 33) SFC (33) Loading 33) Communication Communication functions buffer (Restart) buffer CPS - SW MAS fault handling (SW) (33) (30, 33) (20) capacity (SW) (33) Backup in 212 33 SYREI, Initiated reload (30, 33) AXE Parameter Increase number of Parallel Start APS (20, 30, 33) blocks to 4K (SW) (33) APS Support for (30, 33) Communication Test/ Measurement buffer (20, 30, (SW) (33) 33) OCS over IPNA MAS CPT for (30, 33) capacity (33) IPNA Error handling (30, 33) CPS Kernel (SW) (33) MAS (SW) 100 Mbit Ethernet termination in 212 30 Start - Up , Single CP (33) CPT Initiate reload Initial load (33) (30, 33) MAS (SW) Increase of MIP Program store (30, 33) CP Reload from IPNA (30, 33) IPNA Load from AP (30, 33) Create Initial dump (33) MIP for Capacity De - Compress (33) dump in CP (20, 30, 33) MIP I - test for IPNA (30, 33) MIP I - test for IPNA Start Compress dump Capacity (33) DSU HW (30, 33) in I/O (IO 20, (30, 33) 30, 40) IPU HW for APG 40 Capacity (33)

  34. Activity domains SFC SW (33) MAS fault MAS Fault handling SFC handling SFC (HW) (SW) (33) (33) AXE Parameter MIP for SFC LA for SFC CPS - SW (20, 30, (33) (SW) (33) 33) MAS Fault handling capacity Serial RP bus at MIP I - test for (HW)(33) FC (20, 30, 33) SFC (33) SFC APS (33) FCSUC with new AXE Parameter FURAX interface IPU HW for DBS - SW (20, 30, (20, 30, 33) SFC (33) Loading 33) Communication Communication functions buffer (Restart) buffer CPS - SW MAS fault handling (SW) (33) (30, 33) (20) capacity (SW) (33) Backup in 212 33 SYREI, Initiated reload (30, 33) AXE Parameter Increase number of Parallel Start APS (20, 30, 33) blocks to 4K (SW) (33) APS Support for (30, 33) Communication Test/ Measurement buffer (20, 30, (SW) (33) 33) OCS over IPNA MAS CPT for (30, 33) capacity (33) IPNA Error handling (30, 33) CPS Kernel (SW) (33) MAS (SW) 100 Mbit Ethernet termination in 212 30 Start - Up , Single CP (33) CPT Initiate reload Initial load (33) (30, 33) MAS (SW) Increase of MIP Program store (30, 33) CP Reload from IPNA (30, 33) IPNA Load from AP (30, 33) Create Initial dump (33) MIP for Capacity De - Compress (33) dump in CP (20, 30, 33) MIP I - test for IPNA (30, 33) MIP I - test for IPNA Start Compress dump Capacity (33) DSU HW (30, 33) in I/O (IO 20, (30, 33) 30, 40) IPU HW for APG 40 Capacity (33)

  35. Activity domains (contextualization) SFC SW (33) MAS fault MAS Fault handling SFC handling SFC (HW) (SW) (33) (33) AXE Parameter MIP for SFC LA for SFC CPS - SW (20, 30, (33) (SW) (33) 33) MAS Fault handling capacity Serial RP bus at MIP I - test for (HW)(33) FC (20, 30, 33) SFC (33) SFC APS (33) FCSUC with new AXE Parameter FURAX interface IPU HW for DBS - SW (20, 30, (20, 30, 33) SFC (33) Loading 33) Communication Communication functions buffer (Restart) buffer CPS - SW MAS fault handling (SW) (33) (30, 33) (20) capacity (SW) (33) Backup in 212 33 SYREI, Initiated reload (30, 33) AXE Parameter Increase number of Parallel Start APS (20, 30, 33) blocks to 4K (SW) (33) APS Support for (30, 33) Communication Test/ Measurement buffer (20, 30, (SW) (33) 33) OCS over IPNA MAS CPT for (30, 33) capacity (33) IPNA Error handling (30, 33) CPS Kernel (SW) (33) MAS (SW) 100 Mbit Ethernet termination in 212 30 Start - Up , Single CP (33) CPT Initiate reload Initial load (33) (30, 33) MAS (SW) Increase of MIP Program store (30, 33) CP Reload from IPNA (30, 33) IPNA Load from AP (30, 33) Create Initial dump (33) MIP for Capacity De - Compress (33) dump in CP (20, 30, 33) MIP I - test for IPNA (30, 33) MIP I - test for IPNA Start Compress dump Capacity (33) DSU HW (30, 33) in I/O (IO 20, (30, 33) 30, 40) IPU HW for APG 40 Capacity (33)

  36. Integration plan MAS (SW) 100 Mbit Ethernet termination in 212 30 CP Reload from IPNA (30,33) MAS Fault handling SFC (SW) (33) MIP for SFC (33) MIP I-test for SPC (33) MIP I-test for IPNA (30,33) Parallel Start (33) v13 v14 v15 v16 v17 v18 v19 v20 v21 v22 v23 v24 v25 v26 MIP for Capacity (33) IPU HW for Capacity (33) Communication buffer CPS-SW (20) Start-Up Single CP (33) MAS Fault handling capacity (HW)(33) Create Initial dump (33) Increase number of blocks to 4K (SW) (30, 33) DSU HW (30, 33) FCSUC with new FURAX interface (20, 30, 33) De-Compress dump in CP (21) (30, 33) AXE Parameter CPS-SW (20, 30, 33) MAS (SW) Increase of MIP Program store (30, 33) CPS Kernel (SW) (33)

  37. Integration plan (temporalization) MAS (SW) 100 Mbit Ethernet termination in 212 30 CP Reload from IPNA (30,33) MAS Fault handling SFC (SW) (33) MIP for SFC (33) MIP I-test for SPC (33) MIP I-test for IPNA (30,33) Parallel Start (33) v13 v14 v15 v16 v17 v18 v19 v20 v21 v22 v23 v24 v25 v26 MIP for Capacity (33) IPU HW for Capacity (33) Communication buffer CPS-SW (20) Start-Up Single CP (33) MAS Fault handling capacity (HW)(33) Create Initial dump (33) Increase number of blocks to 4K (SW) (30, 33) DSU HW (30, 33) FCSUC with new FURAX interface (20, 30, 33) De-Compress dump in CP (21) (30, 33) AXE Parameter CPS-SW (20, 30, 33) MAS (SW) Increase of MIP Program store (30, 33) CPS Kernel (SW) (33)

  38. Target trajectory through Activity Domains

  39. The Enterprise Anatomy

  40. The Activity Domain Needs Product

  41. Business process Ericsson Business Process PC 5 PC 4 SC 8 t t n n e e s s PC 3 PC 6 l l e e m m a a c c b b e e Implement In - Service i i v v o o g g r r l l Solution Support a a e e G G n n S S a a M M t t n n PC 2 e e y y l l m m Supply p p g g p p Solution a a u u n n S S a a M M t t n n t t e e PC 0 PC 1 n n m m u u e e Create o o g g Sales Sales c c a a Business c c n n A A a a M M t t n n SC 7 t t SC 1 SC 2 SC 5 e e c c m m u u Define Product Design Prepare Exibit Product in d d g g Define Business a a o o Content Market Offer Deployment Service Content r r n n P P a a M M SC 4 t t n n e e SC 3 m m m m e e t t Specify g g s s a a y y Product n n S S a a M M t t n n & & e e SC 6 m m n n t t s s e e Design & Verify g g e e i i g g s s T T Product a a e e n n D D a a M M

  42. Business process (temporalization) Ericsson Business Process PC 5 PC 4 SC 8 t t n n e e s s PC 3 PC 6 l l e e m m a a c c b b e e Implement In - Service i i v v o o g g r r l l Solution Support a a e e G G n n S S a a M M t t n n PC 2 e e y y l l m m Supply p p g g p p Solution a a u u n n S S a a M M t t n n t t e e PC 0 PC 1 n n m m u u e e Create o o g g Sales Sales c c a a Business c c n n A A a a M M t t n n SC 7 t t SC 1 SC 2 SC 5 e e c c m m u u Define Product Design Prepare Exibit Product in d d g g Define Business a a o o Content Market Offer Deployment Service Content r r n n P P a a M M SC 4 t t n n e e SC 3 m m m m e e t t Specify g g s s a a y y Product n n S S a a M M t t n n & & e e SC 6 m m n n t t s s e e Design & Verify g g e e i i g g s s T T Product a a e e n n D D a a M M

  43. Activity Domains as Business Capabilities Implement Solution Supply Solution In-Service Support Exhibit Product in Service Sales Needs Product Design & Verify Product Create Business Prepare Deployment Design Market Offer Specify Product Define Business Opportunity Define Product Content

  44. Define activity domains Implement Solution Supply Solution In-Service Support Exhibit Product in Service Sales Design & Verify Product Create Business Prepare Deployment Design Market Offer • Activity Domains • Target • Motive Specify Product Define Business Opportunity Define Product Content

  45. ■ Performance Fulfillment ■ Solution Fulfillment ■ Product in Service ■ Performance Need or Incident ■ Solution need ■ Changes & Expectations & Gap ■ New Standards & Technology Define the enterprise anatomy Implement Solution Supply Solution In-Service Support Exhibit Product in Service Sales Design & Verify Product Create Business Prepare Deployment Design Market Offer • Activity Domains • Target • Motive • Dependencies between domains Specify Product Define Business Opportunity Define Product Content

  46. Transitions ■ Performance Fulfillment ■ Solution Fulfillment ■ Product in Service • Activity Domains • Target • Motive • Dependencies between domains • Transitions between domains • Mapping rules, translations, interfaces … In-Service Support Implement Solution ■ Performance Need or Incident Supply Solution Exhibit Product in Service Sales Prepare Deployment Create Business Design & Verify Product Design Market Offer ■ Solution need Specify Product Define Product Content Define Business Opportunity ■ Changes & Expectations & Gap ■ New Standards & Technology

  47. The internals of each domain ■ Performance Fulfillment ■ Solution Fulfillment ■ Product in Service • Activity Domains • Target • Motive • Dependencies between domains • Transitions between domains • Mapping rules, translations, interfaces … • Activity modalities for each domain • Information Model – relevant things • Process Models – ordered actions • Business rules – valid actions • PLM, ERP – means • Enacting means • Aligning individual meanings In-Service Support Implement Solution ■ Performance Need or Incident Supply Solution Exhibit Product in Service Sales Prepare Deployment Create Business Design & Verify Product Design Market Offer ■ Solution need Specify Product Define Product Content Define Business Opportunity ■ Changes & Expectations & Gap ■ New Standards & Technology

  48. Activity Domain process model (temporalization) New Product Developmentstates SC1: Market offer intent SC2: Product release intent SC3: Product model approval SC4: Design Implementation Decision SC5: Market offer SC6: Product quality approved SC6.5: Product ready for deployment SC7: Market release decision SC8: Full deployment acknowledged Delivery to Order states PC0: Offer requested PC1: Order / Contract PC2: Product arrived PC3: Ready for Acceptance PC4: Customer Acceptance PC5: Product in service PC6: Solution fulfillment Performance Need or Incident Solution need PC3,4,5 PC0 PC1 PC2 PC6 Sales object Changes & expectations.- Gaps New standards & technologies SC1 SC2 SC5 Solution SC3,4 SC6 SC6.5 SC7 SC8 Product Design Market Offer Create Business Sales Supply Solution Implement Solution Define Business Opportunity Define Product Content Specify Product Design & Verify Product Prepare Deployment Exhibit Product in Service In Service Support

  49. Sales object {PC0, PC1, PC2, PC3, PC4, PC5, PC6} Solution {SC1, SC2, SC5} Product {SC3, SC4, SC6, SC6.5, SC7, SC8} SO S P consists_of includes described_by described_by described_by D Document is_a Performance Need or Incident Solution need Changes & expectations - Gap New standards & technologies …. Activity Domain information model (spatialization)

More Related