
70f454ae45512d029bcd6f946922191e.ppt
- Количество слайдов: 31
Architecture Learning Program B and TI Example Enterprise Architecture Xnet project
Agenda Objectives and scope Engagement Roadmap Principles Conceptual architecture Alternatives Migration Roadmaps © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 4 Capgemini University – Technology Services School
Project objectives and background The overall objective of the Xnet project is to define how to integrate Microsoft Sharepoint in the company landscape and to define a consistent architecture and transformation roadmap (at the enterprise level) for : team collaboration needs, portal and web publishing, workflows, identity management Microsoft Sharepoint choice is in line with the company strategy to go towards technology industry standards. © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 5 Capgemini University – Technology Services School
Project scope In scope : Team document management: Team/Project Document publishing (short life), Team announcement board, Team/project document collaborative review/ update / approval Innovation, creativity: Idea management, Wiki, Team poll, Forum, Q&A Synchronous communication: Instant messaging Team activity management: Task mgt / action plan, Team monitoring, Meeting minutes Calendar sharing Project mgt: Light project mgt, Dashboard Collaboration item workflow Web publishing: Solutions for developing/managing ST intranet web site Identity Management (Include Single Sign On) The collected business needs will cover internet/extranet/intranet domains. Out of scope : Workflows within processes integration supported by web. Methods / TIBCO Workflows within applications (SAP or other packages, legacy applications) © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 6 Capgemini University – Technology Services School
Engagement roadmap © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 7 Capgemini University – Technology Services School
Principles Process to define principles : Gather business and IT objectives (from interviews) with priorities Transform Objectives into principles (business and IT) ú Principles are classified by business domains at the beginning. Some business principles are common to several business domains ú IT principles are classified as “enterprise” or “project” level. Enterprise level principles will form the foundation for Enterprise Architecture principles that must be applied for every future architecture project. © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 8 Capgemini University – Technology Services School
Principle Principles are derived from business/IT objectives and constraints. Principles priority were derived from objectives priority. Business objectives are classified by business domains. Principles are classified by type (business and IT principles). Business/IT objectives analysis helped us to understand rationales and implications for principles. The following slides only show some examples of principles. © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 9 Capgemini University – Technology Services School
Principle (examples) Business © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 10 Capgemini University – Technology Services School
Principle (examples) Business © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 11 Capgemini University – Technology Services School
Principle (examples) IT © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 12 Capgemini University – Technology Services School
Business Principles (grouped by topic) Principle Group Principle name Priority Rationalization of the ST way of working and exposure to partners One face to customer Business processes global alignment (user management, other business processes) Decrease administrative cost for user management Standardisation of communication channel High Team efficiency Improve efficiency through formalized workflow (manufacturing) Allow easy cross functional and cross location collaboration Workflow must be managed by business user Unique project management for product development (FTM and PTM) Very High Information and application sharing Easy integration of new services/application Quick integration& implementation of new requirements (web site) Relevant and reliable data ISO-TS compliancy for information management (respect ST information strategy) High Security Strong security (Only dedicated partner could have granted access to their own data. ) Separate Business domains (specific team working environment if needed) High Implementation planning Implementation of collaboration features must be implemented in Q 1 2008 for external partners. (On Line Marketing is a company 1 Change footer in VIEW menu (for Author / Dpt / meeting) priority). Very High 3 00 Mth 07 / 7 WKxx Capgemini University – Technology Services School
ICT Enterprise Architecture principles (1) Principle name Principle description Build solution using MS Microsoft Office professional (inc Share. Point) is a by default building block in the solution Very High Documentum for document management Document management solution, based on Documentum, will provide document services to manage simple documents. Very High SAP Unless SAP is the preferred choice for business solutions Very High Buy before build Use packages (application or infrastructure) wherever possible, before building internally ( when packages features aligned with business requirements). High Collaborative solution alignment An alignment between extranet and intranet solution is needed: at least the same portal solution will be used for both Intranet and Extranet. High Application independence of portal infrastructure Portal migration does not mean application migration High Unique source of information for key business processes Ensure Information integrity and accuracy for Key business activities (examples) : access to detailed material declaration , complaint handling , ensure effectiveness and efficiency for corrective actions High Easiness to access services The user must have as less as possible multiple procedures/login-password to access applications and services Middle Change footer in VIEW menu (for Author / Dpt / meeting) 00 Mth 07 / 7 WKxx Priority 1 4 Capgemini University – Technology Services School
Xnet project Architecture principles (2) Principle name Principle description Priority e. Room can be a short term solution for external collaboration e. Room can be used for external collaboration in the first phase, Middle SAP EP as a solution SAP Enterprise portal is one of the potential solution as it will be in the landscape Global ID management Identity management solution must support global ID management throughout ST Audit and compliance Be able to track and audit application access Very high Reduce time and effort to connect new system to Identity management solution High Easy new system connection if we can not demonstrate that the new standard solution (MSsharepoint) can be implemented in extranet scope for end of the year. Low Middle Identity management principle to be refined (see later in the presentation) Change footer in VIEW menu (for Author / Dpt / meeting) 00 Mth 07 / 7 WKxx 1 5 Capgemini University – Technology Services School
Conceptual architecture Business requirements Business Domain Purchasing : Improving supplier relationship Sales and marketing : Improving Customer relationship Contact management (e. g Campaign) Catalog management Customized Content management Supplier identificatio And evaluation Quotation Contract management Acknowledgment And delivery Quote Selling management (e. g Shopping basket Configuration, …) Pricing management Order generation and tracking Invoice payment Collaborative inventory Forecast/plan collaboration Billing and payment Support Complains and returns Design collaboration Catalog management Improving Product development and manufacturing Defect management Alert monitoring Project management Improving Quality processes Engineering data analysis Project management Document Audit Action plan follow-up Information control (policy, security, taxonomy, lifecycle) Action plan follow -up Search content Job management Travel & Expenses management Vacation management Improving enterprise support Search people Improving Employee relationship (HR) Financial and management reporting Projects budget dashboard Business Service © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 16 Capgemini University – Technology Services School
conceptual Architecture List of TI Services supporting Business services Portal Services (templates, customiz. ) Controlled Document Mgmt Directory Services Workflow Document Mgmt` Office Client Search (content, people, . . . ) Light Project Mgmt Security & Resource Access Authentication & SSO Web Publishing Dashboards, KPI, . . . Subscription Services (RSS) Mail Services Collaboration Tools (Forum, Wiki, Blog, . . . ) Instant Messaging Calendars Shared Calendars Search User Profiling © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 17 Capgemini University – Technology Services School
Architecture analyzed alternatives for XNet architecture Alternative 1: Light company Enterprise portal and all applications (including collaboration) integrated into it Rationale: enterprise portal is fully independent on all applications which can be replaced at any time Alternative 2 : Company Enterprise portal integrating main Information Systems Components (i. e. SAP) Rationale: ease integration of SAP applications, leverage on SAP platform and on SAP user management Alternative 3: Company Enterprise portal integrating Collaboration components (Share. Point) Rationale: ease/optimize integration of collaboration and web publishing, and leverage on Microsoft Office products, including for user management © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 18 Capgemini University – Technology Services School
Technology alternatives versus Architecture alternatives Alternative 1: Light Enterprise portal and all applications (including collaboration) integrated into it Technology: ú Portal: Liferay (already chosen for one business domain On-Line marketing) ú Collaboration: Microsoft Share. Point ú Identity mgt: TO BE DEFINED Phase 2 and 3 of the project Alternative 2 : Enterprise portal integrating main Information Systems Components (i. e. SAP) Technology: ú Portal: SAP EP ú Collaboration: Microsoft Share. Point ú Identity mgt: SAP user mgt+ TO BE DEFINED SOFTWARE Phase 2 and 3 of the project Alternative 3: Enterprise portal integrating Collaboration components (Share. Point) Technology: ú Portal: Microsoft Share. Point ú Collaboration: Microsoft Share. Point ú Identity mgt: Active Directory + TO BE DEFINED SOFTWARE Phase 2 and 3 of the project © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 19 Capgemini University – Technology Services School
Legenda to explain the logical grouping The grouping could be seen either by TIC (TI Components) or by Business Objects The color of the clusters is related to the TIC or BO Blue : Microsoft technology Yellow : Open Source or new technology Pink : Existing applications of products Green : SAP technology © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 20 Capgemini University – Technology Services School
Alternative 1: Light enterprise portal Share. Point (MOSS) Liferay Workflow User Profiling Document Mgmt` Search (content, people, . . . ) Dashboards, KPI, . . . Calendar Security & Resource Access Search Web Publishing Light Project Mgmt Subscription Services (RSS) Collaboration Tools Portal Services (templates, customiz. ) Integrated With Authentication & SSO Uses Import data (Forum, Wiki, Blog, . . . ) Uses SUN i. Planet Directory Services Uses Open Source or Commercial Software Natively Integrated With Open Source or Commercial Software MS Office 2003 Shared Calendars Instant Messaging Read/Write Office Client Uses EDOCS Mirapoint Mail Server Controlled Document Mgmt Outlook integration Mail Services © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 21 Capgemini University – Technology Services School
Alternative 1: Light enterprise portal Rely on Liferay portal (as extranet choice) Organisation can leverage J 2 EE skills for portlets development No impact on current company infrastructure (mail, directory, . . . ) SSO between collaboration tool and Liferay/CAS is already proved (technical POC) Convergence principle is not respected (Liferay vs Share. Point future migration, other open source software for instant messaging and calendar sharing) © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 22 Capgemini University – Technology Services School
Alternative 2: SAP Enterprise Portal Share. Point (MOSS) Workflow User Profiling SAP EP Document Mgmt` Search (content, people, . . . ) Dashboards, KPI, . . . Security & Resource Access Calendars Web Publishing Search Subscription Services (RSS) to be integrated with Collaboration Tools Portal Services (templates, customiz. ) Light Project Mgmt Uses Import data (Forum, Wiki, Blog, . . . ) Uses Authentication & SSO Uses SUN i. Planet Directory Services Uses Open Source or Commercial Software Open Source Read/Write or Commercial Software Natively Integrated With Uses MS Office 2003 Shared Calendars Instant Messaging Office Client Read/Write EDOCS Mirapoint Mail Server Controlled Document Mgmt Mail Services © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 23 Outlook integration Capgemini University – Technology Services School
Alternative 2: SAP EP Very similar to alternative 1 SAP EP will be anyhow present in landscape as SAP application portal, but it adds complexity to position it as Enterprise Portal Easy to expose in the portal (as IView) business content coming from SAP modules In case of extranet deployment SAP EP licensing model can be a big issue Convergence principle is respected partially (ok for SAP, not ok for other packages supporting instant messaging, calendar sharing) © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 24 Capgemini University – Technology Services School
Alternative 3: full Microsoft stack Share. Point (MOSS) Workflow User Profiling Search (content, people, . . . ) Dashboards, KPI, . . . Light Project Mgmt Security & Resource Access Portal Services Collaboration Tools (templates, customiz. ) (Forum, Wiki, Blog, . . . ) Web Publishing Authentication & SSO Natively Integrated With Document Mgmt` Uses Subscription Services (RSS) Read/Write MOCS Communication Server Natively Integrated With Uses Natively Integrated With EDOCS Controlled Document Mgmt © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 25 Directory Services Calendar Natively Integrated With Instant Messaging Active Directory MS Office 2003 Office Client Exchange Mail Server Mail Services Shared Calendars Full Outlook integration Capgemini University – Technology Services School
Alternative 3: full Microsoft stack Simplified architecture (no separated portal package) High level of integration of all elements Big impact on company infrastructure (cost, effort, skills, . . . ) Convergence principle fully respected © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 26 Capgemini University – Technology Services School
Business Principles Alternatives comparison Principle Group Alt 1 Alt 2 Alt 3 Light enterprise portal SAP EP Full MS Rationalization of the way of working and exposure to partners Team efficiency Information and application sharing Security Implementation planning 2 3 1 Ranked positions © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 27 Capgemini University – Technology Services School
IT principles Alternatives comparison Principle name Alt 1 Alt 2 Alt 3 Light enterprise portal SAP EP Full MS Build solution using MS Documentum for document management SAP Unless Buy before build Collaborative solution alignment Application independence of portal infrastructure Unique source of information for key business processes Easiness to access services © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 28 Capgemini University – Technology Services School
IT principles Alternatives comparison Principle name Alt 1 Alt 2 Alt 3 Light enterprise portal SAP EP Full MS 3 2 1 e. Room can be a short term solution for external collaboration SAP EP as a solution Global ID management Audit and compliance Easy new system connection Identity management principle to be refined In future phase of the project © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 29 Capgemini University – Technology Services School
XNET : Final recommendations Based on business requirements, architecture principles collected, 3 alternatives of architecture were analyzed The recommendation for the company is to go for a full Microsoft strategy (especially to support, extended mail services, instant messaging, full calendar sharing and full integration with office) This recommendation provides following benefits: Maximization of usability/productivity through an integrated solution Standard of the industry As this requires significant investment and increase of operational cost, an approval of this strategy is required at company level and should Trigger a Microsoft implementation program © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 30 Capgemini University – Technology Services School
Target Architecture and implementation roadmap Share. Point (MOSS) Identity mgt TBD Workflow User Profiling Search Initial foundation focused on Search (content, people, . . . ) collaboration. Dashboards, KPI, . . . H 1 2008 to create in Light Project Mgmt Security & Portal Services for urgent needs Collaboration Tools (templates, customiz. ) (Forum, Wiki, Blog, . . . ) Resource Access full solution to. Authentication be deployed in 2009 Web Publishing Document Mgmt` Subscription Services (RSS) Calendar Natively Integrated With Uses MOCS Communication Server Directory Services Natively Integrated With Read/Write (Connector) Active Directory MS Office 2003 Uses Office Client 2008/2009 focus on Exchange / Full Outlook integration Mocs / Active directory implementation to create Mail Server EDOCS WCM Exchange foundations and Controlled Document Shared Web Content mgt Mail Services Mgmt Calendars to provide productivity features Microsoft Capgemini University Documentum Platform platform – Technology Services School This is a physical grouping © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 31 Instant Messaging
Global program/projects roadmap Microsoft global contract to renew end June This is a Tmap Pilot Deployed Forecast to be confirmed at the end of the architecture study (Q 4) © 2000 -2007 Capgemini - All Rights Reserved Architecture Learning Program IAF 4. 0 / 32 Capgemini University – Technology Services School
Questions © 2006 Capgemini - All rights reserved © 2000 -2007 Capgemini - All Rights Reserved July 2006 – Architecture Essentials- IAF 4. 0 / 33 Architecture Learning Program IAF 4. 0 / 33 Capgemini University – Technology Services School
70f454ae45512d029bcd6f946922191e.ppt