Your SlideShare is downloading. ×
En Portfolio Caps 2009
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

En Portfolio Caps 2009


Published on

Architecture and Performances Management on ERP, CRM, HRM, SCM and BI solutions

Architecture and Performances Management on ERP, CRM, HRM, SCM and BI solutions

Published in: Technology, Business

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Overview on CAPS offer
    Consulting in Architecture & Solutions Performance
    Patrick Saint-Jean
    Senior Manager
    Business Team leader
    Yazid Beniddir
    Gilles Angot
    Senior Manager
    HRM Activity leader
    Senior Manager
    CRM/BI/SCM Activity leader
  • 2. No. 2
    19 juillet 2009
    Consulting in Architecture and Performance of Solutions (CAPS)
    • The Business Team strategicpositioning
    For more than 10 years, our specialties are wide and complex integration projects of main ERP, CRM, SCM, HRMand BI solutions on the technical architecture side.
    Our methodology is based on architecture frameworks, as TOGAF, were we build and enhance technological foundations to achieve solutions SLA in line with companies constraints, evolutions and strategies. In these contexts, we drive and boost technical performance of the systems, the computing production industrialization and their deployment.
    • Offers
    • 3. Architecture overview: audit of the As Is and progress plan of the software packages technical architectures.
    • 4. Architecture design and model: technical base definition to manage software packages and support project team in integration stage.
    • 5. International deployment: technical core model definition and deployment processes industrialization.
    • 6. Production governance: model definition and solution exploitation industrialization
    • 7. Change management: technical and version upgrade of wide solutions.
    • 8. Main Clients
    • 9. Natixis, AGF, Airbus, la Poste, Géodis, Poweo, EDF, GDF-Suez, Areva, SFR, France Télécom, Bouygues Télécom, Ministère de l’Education Nationale, Mairie de Paris
    • 10. Emblematic references
    Natixis : Reengeneeringof the accounting core for the finance & international invest bank, in a European regulation context and a fusion. Based on Oracle PeopleSoft Enterprise solution, the mission was to define and realize a technical base suitable for support 500 simultaneous connections and manage the integration of 4 million accounting writing a day. The architecture framework deployment provided us knowledge to answer to these demands in details. As a result, it became a new standard for the client for all its new projects.
    Portfolio CAPS
  • 11. No. 3
    19 July 2009
    The CAPS Business Team: Managers & Key Figures
    40 consultants
    10 managers
    Revenue: 5.8M€
    ERP: 2.1M€
    HRM: 1.7M€
    CRM: 1.8M€
    BI/SCM: 0.2M€
    Portfolio CAPS
  • 12. No. 4
    19 juillet 2009
    The Technical Architecture
    The architecture has to be built as an answer to the company strategy and the trade stake.
    It support fundamental levels of performance exigency: Performance, Robustness, Flexibility and Upgradability
    Environmental & organizational practices adaptation: rationalization programs in the Information Systems impose internal standards and practices providing an easier appropriation of internal and external teams.
    Portfolio CAPS
    The Logicaarchitecture framework guarantees the whole technical integration building are realized in their functional ambitions.
    The conceptual approach of the technical architecture is structured on the definition of strength Lines, which found the architecture dynamism.
    The plurality of technical and functional problematic is treated trough autonomousbuildings unified in a technical core model.
    Logica approach in models of architecture maturity, dissociates objectives supported by the solution and the imperative project, production necessities.
  • 13. No. 5
    19 juillet 2009
    The CAPS Meta Offers: Solution Architecture
    • To accompany the group on all wide integration projects, whatever is the software package environment, through a differentiating architecture method regarding competitors..
    Portfolio CAPS
    Progress Plan
  • 14. No. 6
    19 juillet 2009
    To guarantee performance engagements in the building of an information system, whatever is the complexity
    The CAPS Meta Offers: the Continuous Technical Performance
    Portfolio CAPS
    • Technical accompaniment of the functional workshops
    • 15. Identification of strength lines
    • 16. DAT & Dimensioning hardware
    • 17. Applicative optimization
    • 18. Technical pre-optimization
    • 19. Define pertinent performance indicators
    • 20. Tools/Measures on the indicators
    • 21. Publishing and historising performances
    • 22. Predictive Analysis and capacity planning
    • 23. Trade scenarios identification, and benchmark
    • 24. Fictive data generation
    • 25. Performance tests industrialization
    • 26. Load tests in step
    • 27. Performance referential construction
  • No. 7
    19 July 2009
    Portfolio CAPS
    Solution Architecture
    • Progress Plan
    • 28. Architecture Conception
    • 29. Complex integration of solutions
    • 30. International deployment
    • 31. Migrations
  • No. 8
    19 July 2009
    Portfolio CAPS
    Logica Architecture Framework
    The LMC technical architecture approach on major solution integration projects is founded on famous architecture frameworks, enriched by IT Service Management measures for organizational, configuration management and industrialization areas.
    • Foundations of the architecture are issued from standardization IS programs, observed through trade stakes.
    • 32. This iterative procedure is applied to the whole life cycle of the software solution, which first step is the building of a technical core model.
    • 33. Huge evolutions are treated as a coherent and industrialized matter, through a controlled evolution of this core model.
  • No. 9
    19 July 2009
    Logica Architecture Framework
    • Roles identification
    • 34. Technological standards and norms understanding
    • 35. Global shared services understanding
    • 36. Current technical overhaul programs, their maturity level and their scheduling identification
    • 37. Technical and production organizational processes analysis
    • 38. Perimeter, stake and company objects definition
    • 39. Geographical and organizational structure definition
    • 40. Trade objects and requirements formalization
    • 41. Trade processes, functions and services listing
    • 42. Organizational change
    • 43. Skill transfer
    • 44. Technological referential formalization
    • 45. Applicative modeling
    • 46. Stream modeling
    • 47. Processes modeling
    • 48. Service library identification
    • 49. Performance tests
    • 50. Robustness tests
    • 51. Intrusion tests
    • 52. Hardware & software technical infrastructure identification
    • 53. System, network and middleware mean identification
    • 54. Lacks and weaknesses identification for major retained scenarios
    • 55. Palliative solutions identification and impact analysis
    • 56. Implementation project follow-up
    • 57. Perimeter adjustment
    • 58. Planning adjustment
    • 59. Configuration management
    • 60. Deliverable management
    • 61. Impact survey on the Information System and other connate projects.
    • 62. Projects prioritization & scheduling
    • 63. Loads and costs finalization
    • 64. Schedule implementation planning setup
    Portfolio CAPS
  • 65. No. 10
    19 July 2009
    Throughprinciples of governance and security, conception of a technical core model is based on :
    The applicative architecture,
    the interoperability, and the accessibility,
    The infrastructure architecture.
    The architecture is piloted by the group strategy ambition:
    Practices and tools convergence,
    Referential & common services unification,
    Cost rationalization by industrialization of the exploiting devices.
    Constitution of operational support centers
    Local specificities are analyzed to measure their impact on the global architecture:
    Development: type and developing scale
    Respect of the eco-systems: suppliers, customers, competition and market.
    Behavior: load peaks, holidays
    Technical deployment capacity
    Skills and industrialization level.
    • The architecture strength lines are established as follows: :
    • 66. Central Architecture, activity continuity plan and local access means,
    • 67. Architectures in continental Data-Centers, or by subsidiaries, consolidation and data replication processes,
    • 68. Architecture, offshore, interoperability, consolidation and local competence management processes.
    Architecture Strength Lines
    Portfolio CAPS
  • 69. No. 11
    19 July 2009
    Maturity Models of a Technical Architecture
    In order to dread the architecture solution in all its dimensions in production, LMC has defined an approach base on 3 observable levels.
    Portfolio CAPS
  • 70. No. 12
    19 July 2009
    Design of a Technical Architecture
    Line infrastructure on business
    • To transform key business needs into structuring technical constraints.
    • 71. To integrate company norms and standards.
    • 72. To identify strength, alternatives and make the arbitration easier.
    • 73. Bests practices and experience return.
    Industrialize production process
    Build the Technical Core Model
    • To make converge performance, scalability, reliability, availability and security works.
    • 74. To formalize a configuration management and a industrial management of the applicative environments.
    • 75. To define exploitation organization
    • 76. To constitute a n efficient technical support center.
    Rationalize resources
    Take into account LOCALISATIONS
    • To identify technical resources needs to answer to the constraints exposed in Line (1) step.
    • 77. To constitute a directory of shared services
    • 78. To rationalize infrastructures
    • 79. To make practices and technological tools converge.
    Portfolio CAPS
  • 80. No. 13
    19 July 2009
    Technical Accompaniment for Subsidiaries Deployment
    To control the impact of successive deployments in subsidiaries of the applicative solution, in terms of QoS and stability, a building model for the architecture has been defined in 3 levels:
    Setup of a Common Technical Base (STC):
    Rationalization of the hardware infrastructure and of the shared services,
    Integration of the applicative configuration management practices,
    Setup of an architecture unifying optimization of the Total Possession Cost and preservation of local QoS.
    Definition and setup of Technical Core Model instances (CMT):
    Preservation of the trade core model,
    Standardization of the approach and of the technologies
    Rationalization of the costs and realization delays,
    Building of the production plan et governance
    Subsidiaries deployment pack (PDF):
    Pick-up charge of localizations,
    Production plan adjustments.
    Portfolio CAPS
  • 81. No. 14
    19 July 2009
    The Subsidiaries Deployment Pack contains the whole elements to guarantee a quick and secure deployment for each new subsidiary.
    It is composed of the following elements:
    A cartography of the final user computers, printers and required updates (hardware and software) to guarantee a local performance level,
    The needs analysis in terms of bandwidth and upgrades – locally and globally-,
    An applicative security at two levels: a security level for the entire subsidiaries group of a CMT instance, and a second level dedicated to the each subsidiary.
    An exhaustive list of configurations, data and specific objects for the subsidiary, beyond the functional core model,
    The organization in terms of treatment capacity (batch files, parallelization level),
    The management of data restoration and interfaces,
    The batch production plan of the subsidiary and its impact on the BPP on the CMT instance it refers to,
    The scheduling of the jobs needs by the subsidiary deployment, in adequacy with the global planning of the deployment project.
    Technical Accompaniment for Subsidiaries Deployment
    Portfolio CAPS
  • 82. No. 15
    19 July 2009
    Portfolio CAPS
    Solution Architecture
    The Continuous Technical Performance
  • 83. No. 16
    19 July 2009
    The Technical Performance Continues
    The systems performance is a continuous process which traverse each project and continues in production
    3 main steps can be distinguished, which key points are:
    Portfolio CAPS
  • 84. No. 17
    19 July 2009
    The technical configuration of the production system has to be qualified in upstream from all release of an evolution that can potentially impact the system performance.
    This qualification step must be industrialized through an automated process called « Performance Benchmark ». This iterative process can be split up into 4 main steps:
    The Technical Performance Continues, focus on the Test Manufacture
    Portfolio CAPS
  • 85. No. 18
    19 July 2009
    Portfolio CAPS
    Solution Architecture
    Main References
  • 86. Major References
    No. 19
    Portfolio CAPS
  • 87. No. 20
    Major References
    Portfolio CAPS
  • 88. No. 21
    Références majeures
    Portfolio CAPS
  • 89. No. 22
    19 July 2009
    Portfolio CAPS
    Solution Architecture
    Offers cards
  • 90. No. 23
    19 juillet 2009
    Description Offer Card
    Portfolio CAPS
  • 91. No. 24
    19 juillet 2009
    Description Offer Card
    Portfolio CAPS
  • 92. No. 25
    19 juillet 2009
    Description Offer Card
    Portfolio CAPS
  • 93. No. 26
    19 juillet 2009
    Description Offer Card
    Portfolio CAPS
  • 94. No. 27
    19 juillet 2009
    Description Offer Card
    Portfolio CAPS
  • 95. No. 28
    19 juillet 2009
    Description Offer Card
    Portfolio CAPS