Improving ECM Consultancy final presentation-v1.0

625 views

Published on

Final Presentation Master Thesis (2007)

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
625
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • 921 = het aantal keren dat ECM voorkomt in mijn afstudeerscriptie
    128 = het aantal afkorting in de afkortingenlijst
    18 = aantal ECM software leveranciers in het Gartner kwadrant van 2006) met de overnam van Stellent door Oracle: 17)
    789 = aantal CMS pakketten dat momenteel op CMS Matrix.org met elkaar vergeleken kan worden.
  • Improving ECM Consultancy final presentation-v1.0

    1. 1. Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish itself are registered trademarks of Atos Origin SA. August 2006 © 2006 Atos Origin. Confidential information owned by Atos Origin, to be used by the recipient only. This document or any part of it, may not be reproduced, copied, circulated and/or distributed nor quoted without prior written approval from Atos Origin. Improving ECM Consultancy Final presentation Nicole van den Wildenberg Eindhoven, TU/e, August 20th , 2007
    2. 2. 2 Custom presentation- or document control name Agenda » About the research: » Problem definition, assignment and context » Root causes » Design » Implementation » Evaluation » Conclusions & Recommendations
    3. 3. 3 Custom presentation- or document control name But first… B I N G O • • 921 128 • 18 • • • • • 789 •
    4. 4. 4 Custom presentation- or document control name The Research
    5. 5. 5 Custom presentation- or document control name Problem definition and assignment Final problem definition:Final problem definition: ECM business consultancy is not aligned with standards and best practices concerned with ECM and consultancy, thus causing a gap between the ECM demand and supply interactions on the one hand and ECM institutional design on the other. This causes sub optimization and a lack of quality. Final problem definition:Final problem definition: ECM business consultancy is not aligned with standards and best practices concerned with ECM and consultancy, thus causing a gap between the ECM demand and supply interactions on the one hand and ECM institutional design on the other. This causes sub optimization and a lack of quality. Final assignment (twofold):Final assignment (twofold): Describe how ECM business consultancy is executed in the current situation. Describe how standards and best practices concerned with ECM and consultancy influence ECM business consultancy. Determine the existing gap. Align ECM business consultancy with standards and best practices concerned with ECM and consultancy by designing a Computation Independent ECM business consultancy model and implement the ECM business consultancy model. This closes the gap. Final assignment (twofold):Final assignment (twofold): Describe how ECM business consultancy is executed in the current situation. Describe how standards and best practices concerned with ECM and consultancy influence ECM business consultancy. Determine the existing gap. Align ECM business consultancy with standards and best practices concerned with ECM and consultancy by designing a Computation Independent ECM business consultancy model and implement the ECM business consultancy model. This closes the gap.
    6. 6. 6 Custom presentation- or document control name Main research models and methods » The regulative cycle with reference models » Morioka’s triangle » Multilevel stakeholder analysis
    7. 7. 7 Custom presentation- or document control name Regulative cycle + reference models Orientation Set of problems / problem mess / Problem definition Diagnosis (analysis & mapping) Intervention (implementation) Plan (design) Evaluation benchmarking, market & competitor analysis reference model Translation site specific reference model real site work system
    8. 8. 8 Custom presentation- or document control name Morioka’s triangle: the research context Institutions Demand side Supply side pull push Technology Interactions Harmonization Legislation Standards
    9. 9. 9 Custom presentation- or document control name Multilevel stakeholder analysis: problems » Macro & meso scale: Institutions: » ECM standards and best practices authorities: application of standards and best practices is not a task of authorities, high variability of standards, extensive amount of standards. » Micro scale: Demand side: » ECM users: impact of ECM system implementations underestimated, lack of knowledge of standards. » Micro scale: Supply side: » ECM vendors: ECM systems are complex, complex requirements to ECM systems. » ECM system integrators: lack of a standardized way of working, lack of a standardized method to incorporate ECM standards and best practices in the delivery of ECM business consultancy. » Pico scale: Supply side: » ECM consultants: lack of standards and best practices to do the job.
    10. 10. 10 Custom presentation- or document control name Root causes & Opportunities
    11. 11. 11 Custom presentation- or document control name Root causes & Opportunities » Root causes: » Lack of a practicable model for applying ECM standards and best practices. » ECM systems are complex. » The impact of an ECM system implementation is underestimated. » Opportunities: » Risk reduction in the ECM strategy. » Development of ECM business consultancy delivery by Atos Origin. » Engaging in knowledge collaboration.
    12. 12. 12 Custom presentation- or document control name The Design
    13. 13. 13 Custom presentation- or document control name ECM consultancy activities » Creating ECM Awareness » Executing an ECM Scan » Designing an Enterprise Architecture » ECM Requirements Engineering » ECM Software Selection » Consultancy during an ECM implementation » Consultancy during System Operation & Maintenance
    14. 14. 14 Custom presentation- or document control name Design to bridge the gap » Design requirements: » Implementation independent » Practicable » Positioned between standards/best practices and ECM systems » Flexible » Add value for stakeholders » ECM business consultancy model » Repository » Process » Framework » Organization
    15. 15. 15 Custom presentation- or document control name ECM business consultancy repository
    16. 16. 16 Custom presentation- or document control name ECM business consultancy process » Define Stakeholders » Define Solution goals » Define Solution requirements » Mapping & Selection: » Map Requirements onto Components » Rank Components » Select Components » Maintain Knowledge Base » Feedback loops
    17. 17. 17 Custom presentation- or document control name ECM business consultancy framework » Goals » Requirements » Technical » Non-technical » Components descriptions » Maturity level » MoSCoW » Scoring & Mapping Metric Description 1 1 1 3ValueOrder [Ordinal] ‘Ad-Hoc’ Workflow, advanced workflow or BPM capabilities. 3ValueOrder = (Satisfactory, Acceptable, Poor) See Figure C. 3 WfMC basic process definition meta-model 2 2 3 4 5 3ValueOrder [Ordinal] 3ValueOrder = (Satisfactory, Acceptable, Poor) 2 3 4 5 6 Portability Non-technical factor Reliability Usability Efficiency Maintainability Security Functionality compliance 1 Use of BPEL, BPML, SWAP, WSCI See respective definitions Use Workflow Suitability of Data Accuracy Interoperability 1 Characteristic Functionality Suitability Suitability of Services
    18. 18. 18 Custom presentation- or document control name ECM business consultancy organization » Model Owner: responsible for facilitating the use and maintenance of the model. » Domain Experts: monitor change to the ECM domain and feed these back to the knowledge base in the form of goals and requirements. » Requirements Engineer; defines stakeholders, goals and solution requirements, stores them in the SUD repository. » Component Engineer: maintains the component descriptions in the knowledge base.
    19. 19. 19 Custom presentation- or document control name Implementation
    20. 20. 20 Custom presentation- or document control name Implementation 1. Implementation of the ECM business consultancy model. » Conversion: refine the model. » Training: train ECM consultants in the use of the model. » Testing and acceptance: execute a pilot and evaluate/assess the model. 2. Development of ECM business consultancy service products for Atos Origin. » Service Products must have added value for Atos Origin and its clients. ID Task Name Resource Names 1 Approval Sponsor 2 Kick off Sponsor 3 Enforcement 4 Arrange enforcement Sponsor 5 Write code of conduct Owner 6 Conversion 7 Coordinate conversion Owner 8 Participate in conversion ECMConsultants 9 Repository 10 Arrange repository Owner 11 Implement repository Owner 12 Arrange model maintenance Owner 13 Training 14 Arrange training Owner 15 Give initial training Owner 16 Follow training ECMConsultants 17 Service Product 18 Arrange service product development Business Development Manager 19 Coordinate/communicate with marketingBusiness Development Manager 20 Develop marketing collateral Business Development Manager 21 Pilot 22 Plan first pilot Owner 23 Execute first pilot ECMConsultants 24 Apply model ECMConsultants 25 Maintain model/feedback ECMConsultants 26 Arrange first focus group review Owner 3-9 Sponsor 3-9 Owner Owner ECM Consultants Owner Owner Owner Owner Owner ECM Consultants Business Development Manager Business Development Manager Business Development Manager Owner ECM Consultants ECM Consultants ECM Consultants Owner 29 6 14 22 30 8 16 24 1 9 17 25 3 11 19 27 4 12 20 28 5 20 Aug '07 10 Sep '07 1 Oct '07 22 Oct '07 12 Nov'07 3 Dec '07 24 Dec '07 14 Jan '08 4 Feb '08
    21. 21. 21 Custom presentation- or document control name The Evaluation
    22. 22. 22 Custom presentation- or document control name Evaluation » Credibility: affirmation by people in the context. » Transferability: a generic market domain model could be extended with an ECM domain model. » Dependability: the ECM business consultancy model is Computation Independent and is sensitive to changes in the ECM domain. » Confirmability: the ECM business consultancy model is based on information, conclusions and interpretations that can be traced back to their sources.
    23. 23. 23 Custom presentation- or document control name Conclusions & Recommendations
    24. 24. 24 Custom presentation- or document control name Conclusions Macro and meso scale: market and industries » The alignment between the demand and supply side in the ECM market is not optimal. The focus on technology is often too high and an alignment with an ECM user’s strategy is often missing. Micro scale: organizations » The ECM business consultancy model decreases the risks of implementing suboptimal ECM solutions. » The starting point for any ECM implementation should be an analysis of stakeholders, goals and requirements. » The ECM business consultancy model can (and will) be used by Atos Origin to deliver ECM solutions with a focus on the strategic level. Pico scale: individual human beings » The ECM consultants have affirmed that the ECM business consultancy model fills the perceived lack of a practicable model for delivering consultancy.
    25. 25. 25 Custom presentation- or document control name Recommendations » Implementations of the ECM business consultancy model. » Develop one or more service products based on the ECM business consultancy model; additionally develop a service product or solution concerned with pro-active, flexible compliance through ECM and Business Process Management (BPM). » Involve the Atos Origin’s Requirements Definition Center (RDC) in a review of the ECM domain models as presented in this research. » Review the ECM Scan based on the knowledge gained from this research. » Extend the ECM business consultancy model with software architecting according to the CARE/SA methodology on which the design has been based. » Perform additional research to include traceability of requirements throughout an entire ECM implementation.
    26. 26. Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish itself are registered trademarks of Atos Origin SA. August 2006 © 2006 Atos Origin. Confidential information owned by Atos Origin, to be used by the recipient only. This document or any part of it, may not be reproduced, copied, circulated and/or distributed nor quoted without prior written approval from Atos Origin. For more information please contact: Nicole van den Wildenberg m +31 (0)6 51 40 46 30 nicole.vandenwildenberg@atosorigin.com Atos Origin Nederland B.V. Papendorpseweg 93 3528 BJ, Utrecht www.atosorigin.com

    ×