|
|
| (6 versioni intermedie di uno stesso utente non sono mostrate) |
| Riga 1: |
Riga 1: |
| − | For a complete overview of itmSUITE® please visit the following sections. | + | |
| | + | <nowiki/>ItmSUITE® is an integrated software suite that supports the introduction and maturation of established best practice in the fields of portfolio, project and Service management. It offers support that is simple yet without compromises for all the activities that are at the heart of IT management such as Service Desk, Incident Management, Change Management, Problem Management, Release Management, Asset Management, Configuration Management, Service Level Management, Service Catalogue Management, and Portfolio and Project Management. The image shown below shows the schema for the areas of management that are supported by ItmSUITE®. For further information on how this translates into concrete support and benefits when ItmSUITE®. is adopted please use the mouse and click on the area that you are interested in. |
| | | | |
| − | === [[itmSUITE® - Key features|Key features]] ===
| + | <strong>Main benefits that come from the adoption of the itmSUITE® :</strong> |
| − | This section illustrates the key functionalities and benefits of itmSUITE®.
| + | * Efficient support for the introduction and maturation of best practice for Portfolio, Programme, Project Management and IT Service Management; |
| − | | + | * Complete functional cover in continual improvement; |
| − | ==== IT Service Management ====
| + | * Extremely short time and low effort required in the start up phase; |
| − | <strong>ItmSUITE®</strong> supports the adoption of the most successful best practices and standards in IT Service Management (ITILR, ISO/IEC 20000). It does so first of all by supporting the inter-linking practices (Management Control, Benefits Management, Financial Management, Risk Management, Organisational Governance,Resource Management) and then with its distinctive characteristics (Service Orientation and Roles Readiness,Business Rules Engine, Dashboard and Reporting Engine, Easy Integration, Codeless Customization) but also in a more specific way in the different action areas of IT Service Management ( in particular in the phases of the management of the service lifecycle and specific processes). | + | * Effective integration to client needs, without compromises; |
| − | Look in greater detail at the characteristics and itmSUITER support available in the field of IT Service Management by selecting the area that you are interested in, in the figure.
| + | * Reduction in number of tools to be managed and on long term integration maintenance (significant decrease in the Total Cost of Ownership); |
| − | | + | * Autonomous and intuitive codeless configuration, (this means that you are independent of product specialists and as a result there is an increase in the speed of integration and a decrease in the Total Cost of Ownership); |
| − | '''Main benefits deriving from the adoption of itmSUITE® :'''
| + | * After-sale support offered by a team of qualified and certified personnel on IT Service Management best practices (e.g. ITIL ); |
| − | * Efficient support for the introduction and maturation of best practice for Portfolio, Programme, Project Management and IT Service Management | + | * Flessibilità dei contratti di servizio per il supporto; |
| − | * Complete functional cover in continual improvement | + | * Flexible support service contracts; |
| − | * Availability of pre-configured processes that will facilitate and speed up the start up phase.
| + | * Turn-key solutions available (training and consulting on best practices provided + software) to guarantee results within a pre-determined time period. |
| − | * Extremely short time and low effort required in the start up phase | + | '''Additional information about itmSUITE® are available at the following links :''' |
| − | * Effective integration to client needs, without compromises. | + | * [[ItmSUITE® - Key features|Key features]] |
| − | * Reduction in number of tools to be managed and on long term integration maintenance (significant decrease in the Total Cost of Ownership) | + | * [[ItmSUITE® - Core modules|Core modules]] |
| − | * Autonomous and intuitive codeless configuration, (this means that you are independent of product specialists and as a result there is an increase in the speed of integration and a decrease in the Total Cost of Ownership) | + | * [[ItmSUITE® - Complementary modules|Complementary modules]] |
| − | * After-sale support offered by a team of qualified and certified personnel on IT Service Management best practices (e.g. ITIL ) | + | * [[Architecture]] |
| − | * Flexible support service contracts | + | * [[Glossary]] |
| − | * Turn-key solutions available (training and consulting on best practices provided + software) to guarantee results within a pre-determined time period | + | [[category:ItmSUITE®]] |
| − | * Availability of sustainable investment offers (e.g. software license rental or Software as a Service)
| |
| − | | |
| − | ===== Service Strategy =====
| |
| − | L' itmSUITE® support this fundamental phase of the IT services lifecycle, in particular the following processes:
| |
| − | * Demand Management
| |
| − | * Financial Management for IT Service
| |
| − | * Service Portfolio Management
| |
| − | '''Main features of itmSUITE® useful in this area :''' | |
| − | * Support for the optimal definition of the IT services and projects portfolio.
| |
| − | * Effective and efficient management of IT services
| |
| − | * Budget and economic control of the costs and earnings related to IT services and projects.
| |
| − | * Management of the risks and benefits related to the implementation of the IT strategy.
| |
| − | * Planning and control of the resources.
| |
| − | '''Main benefits deriving from the adoption of itmSUITE® :'''
| |
| − | * Concrete help offered so client can clearly understand the type and level of service that they need and the subsequent delivery of these services in the best way.
| |
| − | * Support for the creation and update of a portfolio for transformation initiatives that will maximise the possibility of achieving the strategies.
| |
| − | * Improvement in the capacity to manage risk and therefore a higher probability of achieving desired results within a specified time limit and within budget.
| |
| − | * Improvement in the ability to respond rapidly and efficiently to change.
| |
| − | * Improvement in communication between service clients and suppliers so that both have a clearer vision of what has been requested and how to achieve it.
| |
| − | | |
| − | ====== Demand Management ======
| |
| − | ItmSUITE® makes it possible to effectively and efficiently support the execution of the Demand Management processes (service requests). This applies to both individual and aggregated requests ( planning and evaluation of overall resource requests).
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Flexible and codeless management of the workflow configuration for the punctual management of requests, without compromises.
| |
| − | * Multi-level and graphic support for the planning and control of the use of human resources that takes into account all the activities carried out (assistence, projects etc)
| |
| − | * Real time calculations on whether the SLAs/OLAs have been achieved on time and maximum efficiency in the presentation and communication of results.
| |
| − | * Extremely flexible and modular 'self service' portal for the management of all requests and notifications.
| |
| − | * Possibility to define and monitor the performance of KPIs and to configure notifications and automatic actions (eg. request to carry out an activity) with regards to the reaching of benchmark levels.
| |
| − | * Advanced and personalised reporting of REP module.
| |
| − | * Ease of integration with external systems dedicated to the management of the acquisition and/or evasion of requests parts of the process.
| |
| − | '''Main benefits deriving from the adoption of itmSUITE® :'''
| |
| − | * Quick, effective and efficient management of requests
| |
| − | * Improved planning and control of the overall use of human resources.
| |
| − | * Control over process performance
| |
| − | * Increase in client satisfaction.
| |
| − | | |
| − | ====== Financial Management for IT Services ======
| |
| − | itmSUITE® offers an effective process for IT Financial Management and aims at making the reliable and efficient management of costs and revenues for both individual and/or aggregate projects and services possible. Projetcs can be manage d in a similar way. The unusual thing about this solution is that it also offers management possibilities for any organisation that has a manageable workflow, for example problem, change, improvement actions etc.
| |
| − | | |
| − | itmSUITE® makes it possible to manage budgets, final balance sheets and also forecasts as well as the activities necessary for their definition (for example, the definition of final balance sheets via timesheets, the management of reimbursement expenses and the implementation of of other kinds of costs). This means that there can be flexible management of the different threads of management to adapt to the needs and levels of complexity required.
| |
| − | | |
| − | The solution package is completed by the possibility to define the methods of control for the evolution of expenses with any discrepancies between the control plan and the actual performance highlighted. There is also a complete basic report and the availability of a powerful reporting motor to create others.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Financial management concerning the budget, final balance and forecast for projects, services and processes
| |
| − | * Possibility to freely define categories of cost
| |
| − | * Possibility to manage revenues (invoicing available)
| |
| − | * Management and visibility of costs and/or revenues per service and/or project
| |
| − | * Possibility to save "snapshots" of economic data (budgets, final balances and forecasts of services and/or projects) and to link them to control milestones that are synchronized for analysis and comparisons
| |
| − | * Integrated management module of final balance that enables allocation of efforts to services and projects with a clear procedure based on real data
| |
| − | * Management and visibility of costs even on single processes (eg. change, problem, etc.)
| |
| − | * Powerful and flexible reporting engine
| |
| − | * Possibility to define and monitor the patterns of costs and to configure automated notifications and actions (eg. reminder notice) when predefined threshold values are reached
| |
| − | '''Main benefits deriving from the adoption of itmSUITE® :'''
| |
| − | * It permits the estimate and control of operating and investment costs of projects and services
| |
| − | * It offers the possibility of total transparency of costs for services, projects and their aggregates.
| |
| − | * It permits the management of revenues and, in the final analysis, reveals the margins of the services and/or projects.
| |
| − | | |
| − | ====== Service Portfolio Management ======
| |
| − | itmSUITE ® effectively supports the Portfolio Management of IT services.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Possibility to manage one or more portfolios as an aggregation of services
| |
| − | * Management of the categorization of services based on the classification variables of the portfolio
| |
| − | * Representation of the composition, structure and status of portfolios based on classification variables
| |
| − | '''Main benefits deriving from the use of itmSUITE® :'''
| |
| − | * Makes it easier to understand the structure of the portfolio of services
| |
| − | * It simplifies the decision making process with regards to how to structure the portfolio in the future in a way that supports the strategy (effectiveness in the management of portfolios)
| |
| − | * Makes the maintenance of the structure of portfolios of services easier (effectiveness in the management of portfolios)
| |
| − | * Makes it easier to understand the status of the portfolio of services (effectiveness in the management of portfolios)
| |
| − | * Significantly contributes to the realisation of the service provider's strategy
| |
| − | | |
| − | ===== Service Design =====
| |
| − | <strong>itmSUITE®</strong> supports this fundamental stage of the IT services lifecycle. In particular, the following processes:
| |
| − | * Design Coordination
| |
| − | * Service Catalogue Management
| |
| − | * Service Level Management
| |
| − | * Availability Management
| |
| − | Discover how by looking at the detailed profiles.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area : '''
| |
| − | * Management of the design activities for services at all levels of complexity (eg. via projects and, change);
| |
| − | * Management and communication of the catalog of services;
| |
| − | * Management of the availability of end-to-end services;
| |
| − | * Definition and control of the performance levels of the external services provided to clients (SLA), inside and outside the organisation to suppliers.
| |
| − | '''Main benefits deriving from the adoption of the itmSUITE® :'''
| |
| − | * Improvement in the ability to accurately predict and manage the costs, timescales and risks associated to the Service Design phase;
| |
| − | * Contributes to the increase in the number of successful changes;
| |
| − | * Re-use of the Service Design assets between projects and services;
| |
| − | * Contributes to the reduction in time expenditure through the planning of the service.
| |
| − | | |
| − | ====== Availability Management ======
| |
| − | <strong>itmSUITE®</strong> supports the visualization and comprehension of the end-to-end availability of services starting from that of their components. Monitoring of the availability of the latter is performed by tools that are not part of <strong>itmSUITE®</strong> but that can be easily integrated.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Configuration Management System (including Configuration Management Data Base, CMDB) that allows visual mapping of the structured relationships between service components;
| |
| − | * Support for the preparation of impact maps between the components that takes into account redundancies too;
| |
| − | * Integration, through simple configurations, with external tools that monitor service components;
| |
| − | * Graphical representation of the end-to-end state of the services with drill-down option on components;
| |
| − | * Console for visualization of messages of changes of status of components and services with RAG (Red, Amber, Green) alerts;
| |
| − | * Possibility to trigger processes in response to the reaching of predetermined statuses or conditions of events or services;
| |
| − | '''Main advantages deriving from the use of itmSUITE® :'''
| |
| − | * Immediate detection of the availability of services as single components but, above all, as end-to-end too;
| |
| − | * Faster response times to issues related to the availability of single component and end-to-end services;
| |
| − | * Increased efficiency in response to issues on the availability of of single component and end-to-end services;
| |
| − | | |
| − | ====== Design Coordination ======
| |
| − | <strong>itmSUITE®</strong> provides full support to this activity and also assures an essential contribution to all automation areas that are strictly correlated, and in particular to Project Management . The process of Design Coordination includes both the design activities of services and the design of specific service requests (new or changed).In both cases, itmSUITE® is able to support the coordination action in the best way.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Management of all the aspects of the overall activity that applies to the process of design (ex. planning, costs, efforts, quality, issues and risks);
| |
| − | * Management of all the aspects of activity of design either as single request of a new service or as change to a service (ex. planning, costs, efforts, quality, issues and risks);
| |
| − | * Integration of the management of design activities with all the other management activities of lifecycle services;
| |
| − | * Support to the realization and documentation of outputs of service design (ex. modelling from Enterprise Architecture Management standpoint) and supported in particular by the CMS module;
| |
| − | * Easier monitoring of the progress of design processes and design activities.
| |
| − | '''Main advantages deriving from the use of itmSUITE® :'''
| |
| − | * Availability of the results of service design (Service Design Package) with higher forecasting precision of times and costs;
| |
| − | * Higher accuracy in managing risks connected to design and, therefore, better quality (meeting expected requirements) in design outputs and consequently in the final results;
| |
| − | * Reduction in variations and related costs not only for design activities but, above all, for the successive stages of the service lifecycle;
| |
| − | * Increase in the efficiency and effectiveness of the activities of service design;
| |
| − | * Increase in customers and user satisfaction.
| |
| − | | |
| − | ====== Service Catalogue Management ======
| |
| − | itmSUITE® fully supports the design and management of the service catalogue , whether the services are of a business or technical nature (in other words those that are not promoted as part of the business but that are necessary for the correct functioning of the other services) in line with IT Service Management best practice. The service catalogue is managed in such a way that it offers support to operational activities that will be presented to the client and also represents the core skeleton of the itmSUITE® as used for IT Service Management. | |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Support to the design of the architecture of the service catalogue
| |
| − | * Support to the design of the architecture and content of a single service
| |
| − | * Publication of the service catalogue with specific views that can be configured
| |
| − | * Automation of the management of service requests
| |
| − | * This service is a key element for the management of any kind of IT Service Management process
| |
| − | '''Main benefits derving from the use of itmSUITE® :'''
| |
| − | * All business and IT areas have access to information regarding IT services that is accurate, exhaustive (details and status included) and consistent
| |
| − | * Effectiveness and efficiency in the management and publication of information regarding the service catalogue
| |
| − | * Improved security for access to information about the service catalogue
| |
| − | * Flexibility, effectiveness and efficiency in the management of service requests
| |
| − | | |
| − | ====== Service Level Management ======
| |
| − | itmSUITE® fully supports the design and management of service level agreements with customers (Service Level Agreement or SLA), with internal service providers (Operational Level Agreement or OLA) and with suppliers (Underpinning Contract or UC). The information about service levels reached can then be made available to any organisation or on any list and in this way itmSUITE® favours real time alignment of IT with business needs.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Management of information regarding SLAs/OLAs/ICs
| |
| − | * Real-time calculation of SLAs/OLAs/UCs
| |
| − | * Automated communication and actions in response to the performance of SLAs/OLAs/UCs
| |
| − | * Reports on progress of SLAs/OLAs/UCs
| |
| − | '''Main advantages deriving from the use of itmSUITE® :'''
| |
| − | * Effective measuring of service levels reached
| |
| − | * Automation of all the aspects of management of SLAs/OLAs/UCs
| |
| − | * Faster and more effective action in case of targets not reached
| |
| − | * Forecasting of possibility that targets may not be met and related corrective action
| |
| − | * Decision making support and improvement in the alignment between IT actions and business needs
| |
| − | * Better communication and, in the final analysis, relationships with customers
| |
| − | | |
| − | ===== Service Transition =====
| |
| − | itmSUITE ® supports the transition stage during the production of new services or changes being made to existing IT services. In particular, the processes of:
| |
| − | * Transition Planning & Support
| |
| − | * Change Management
| |
| − | * Service Asset & Configuration Management
| |
| − | * Release & Deployment Management
| |
| − | * Service Validation & Testing
| |
| − | * Knowledge Management
| |
| − | Discover how by looking at the detailed profiles.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Management of the transition activities of the services at all levels of complexity (eg. through projects or changes); | |
| − | * Provides support to the introduction of structured and optimized processes of change management exactly as requested;
| |
| − | * Configuration Management of both visual and end-to-end IT services;
| |
| − | * Asset management integrated with Configuration Management and all the other processes;
| |
| − | * Release & Deployment Management controlled and integrated with Change, Incident and Problem Management;
| |
| − | * Indexing of all data and information managed regardless of its format (eg. document, record) that makes searches easier;
| |
| − | * Powerful and flexible reporting engine.
| |
| − | '''Main benefits deriving from the use of itmSUITE® :'''
| |
| − | * Increased accuracy in forecasting and managing costs, time schedules and risks associated with the stage of Service Transition;
| |
| − | * Higher results in successful implementation of changes;
| |
| − | * Re-use of the assets of Service Transition between projects and services;
| |
| − | * Improvement of the efficiency in carrying out the transition of the service from design to production;
| |
| − | * Contribution in reducing lead times of service transition;
| |
| − | * Increase in the confidence about the ability of the service to meet requirements, objectives and planned costs;
| |
| − | * Better control on service assets and configurations.
| |
| − | | |
| − | ====== Transition, Planning & Support ======
| |
| − | itmSUITE® provides full support to this activity and also assures an essential contribution to all those automation areas strictly linked to it, and in particular to Project Management. The process of Transition Planning & Support includes the activities performed and resources involved in services (new or changes) through all the stages of design up to that of production.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Management of all the aspects of the entire activity of transiton (eg. planning, costs, efforts, quality, issues and risks);
| |
| − | * Visibility and management of the workload of human resources;
| |
| − | * Integration and management of the activities of transition that encompass all the other activities of management of the lifecycle of the services.
| |
| − | '''Main advantages from the use of itmSUITE® :'''
| |
| − | * Improvement of the effectiveness and efficiency of the transition activities of planning and support;
| |
| − | * Increase in the ability to support the change (management of a higher number of changes and releases);
| |
| − | * Improved control of the integrity of the assets during the transition phase of the services and a subsequent reduction in risk and associated negative impact.
| |
| − | | |
| − | ====== Change Management ======
| |
| − | Change Management was one of the first processes to be supported by itmSUITE ® and as such is now one of the most well established. Aspects of particular interest that make it stand out compared to other solutions on the market are that it offers:
| |
| − | * support during the impact assessment stage with automated selection of the type of Change;
| |
| − | * simple and easy creation of Change Models that automate specific Change Management processes without compromises;
| |
| − | * support to the assignment and control of activities and, more generally, of all the aspects of a complex Change Management activity that falls within the ambit of Project Managment (planning, management of costs and risks, etc.)
| |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Possibility to configure the automation of processes of Change Management without compromises
| |
| − | * Specific functions that support best practices inherent to Change Management (ex. Change Assessment, integration and management of economic data related to Changes such as budget, final balance and forecast)
| |
| − | * Availability of pre-configured Change Management process cartridges in line with best practice (ITIL ®)
| |
| − | * Reporting procedures
| |
| − | '''Main benefits deriving from the adoption of itmSUITE® :'''
| |
| − | * Reduction in automation times of Change Management
| |
| − | * Increase in the ability to design, estimate impact and implement Changes that meet requirements at optimized costs
| |
| − | * A refined approach to meeting regulatory, legal or internal requirements related to Change Management
| |
| − | * Reduction in the number of unauthorized and/or failed Changes
| |
| − | * Protection of business against unwanted side effects Change Management might cause
| |
| − | * Overall tracking of Changes
| |
| − | * Improvement in the management of risks
| |
| − | * Rise in staff productivity thanks to significantly fewer inefficiencies caused by Changes and because of greater efficiency in the management of the Change itself
| |
| − | * Reduction in average refresh period needed after service failures so that corrective changes can be implemented more quickly.
| |
| − | | |
| − | ====== Release & Deployment Management ======
| |
| − | With itmSUITE ® we recognised the the uniqueness and importance of the Release & Deployment Management process long before our competitors and, in fact, we do not consider it as just a variant of Change Management.
| |
| − | | |
| − | It is for this reason that the Release entity is explicitly managed by a specific process and it is possible to correlate it with any other process managed, and via workflows (eg. Incident, Change, etc.).
| |
| − | In this context, then, the possibility to exploit the functionalities of itmSUITE ® deriving from the support of Project Management is crucial. Indeed the management of Release & Deployment for major releases requires the ability to plan, coordinate and supervise activities which are inter-linked in order to reach a common goal, just like in a project.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Offers support for the automation of the process of Release & Deployment mangement in line with best practice;
| |
| − | * Specific functions to support Release Management, for example:
| |
| − | ** Automated generation of the number of Releases;
| |
| − | ** Automated generation and update with deployment Changes of the Release;
| |
| − | ** Integration and management of economic data related to Changes like budget, final balance and forecast;
| |
| − | ** Integration of Release information with all the other information managed by itmSUITE ® (eg. Change, Incident, project deliverables etc.);
| |
| − | ** Tracking of the activities;
| |
| − | ** Reporting procedures.
| |
| − | '''Main benefits deriving from the adoptuon of itmSUITE® :'''
| |
| − | * Release of Change is quicker, risks are minimized and costs are optimized;
| |
| − | * Improvement in the ability to explain to users how to use new Changes;
| |
| − | * Contribution in meeting requirements (eg. regulatory or internal);
| |
| − | * Reduction of the number of non-authorized and/or failed Releases;
| |
| − | * Protection of the business against unwanted side effects of Releases.
| |
| − | | |
| − | ====== Service Asset & Configuration Management ======
| |
| − | itmSUITE ® and, in particular, the visualCMS ® module was the tool that anticipated market trends and the actual evolution of best practices. The fundamental points to bear in mind to be able to create a successful CMS ( including CMDB) in line with best practice are:
| |
| − | * service orientation;
| |
| − | * to start top-down and not bottom-up;
| |
| − | * to begin from the stage of service design;
| |
| − | * to concentrate on critical services;
| |
| − | * to keep manual control (tools do not know what is part of a logic service);
| |
| − | * to facilitate the initial population and/or control and audit of the CMS via automatic discovery of the configuration elements of the IT Services.
| |
| − | For many years, the market has been developing tools inspired by an inverted approach, in other words the gathering of CIs (Configuration Items) via discovery and the organisation of the aforementioned in services (bottom -up approach) where the graphic aspect is primarily a marketing front but does not coincide with the usability of the solution.
| |
| − | | |
| − | itmSUITE ® is meant to offer the utmost usability to all those who design top-down service models and, furthermore, to allow the re-use of information gathered with discovery tools; this results in a reduction of management fees and harmony between the actual solution and the original project.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Optimal automation of the process of Asset & Configuration Management
| |
| − | * Possibility to categorize and freely define types and attributes of CIs and their operation
| |
| − | * Support to the definition of mapping conventions of configurations (ex. aspect of entities, relations, etc.)
| |
| − | * Native visual modelling that is very user-friendly and with textual features
| |
| − | * Full integration with the process of Change Management that guarantees complete control over Configuration Items
| |
| − | * Possibility to configure acquisition and reconciliation of data (entites and relations) from external sources (ex. discovery tools)
| |
| − | * Possibility to publish all or part of the contents of the CMS (that comprises the CMDB) on portals (ex. SharePoint) and web tools
| |
| − | * Access and use of information of the CMS with processes that are supported by itmSUITE ®
| |
| − | * Reporting procedures
| |
| − | '''Main advantages deriving from the use of itmSUITE® :'''
| |
| − | * Staff can easily access and understand the contents and configuration of services
| |
| − | * Better planning and better forecast of the impacts of Changes and Releases resulting in a significant reduction of side effects
| |
| − | * Easier resolution of Incidents resulting in increased capability to meet relevant service levels
| |
| − | * Compliance with standards and requirements (eg. regulatory) related to documentation, management of assets and configuration
| |
| − | * Tracking of modifications carried out on Configuration Items and related items.
| |
| − | * Support for calculation of the costs of services
| |
| − | * Efficiency and effectiveness in the management of Assets and configurations leading to savings on associated costs
| |
| − | * Optimisation of the costs related to the activities of population and control/ audit of the CMS thanks to the automatic discovery of the configuration elements of the Services.
| |
| − | | |
| − | ====== Knowledge Management ======
| |
| − | The aim of knowledge management is to enable the sharing of ideas, experiences and information so that the most pertinent and useful ones are available to the right people at the right time. The approach that itmSUITE ® uses to support this aim is based on the following:
| |
| − | * a search engine that catalogues all the information from documents through to messages and recordings (eg. the Incident or the Change) to discussions etc. This makes it possible to understand the context in which the information was generated;
| |
| − | * a system based on messages that is perfectly integrated with email systems and that is also able to provide contextual communications ( eg. a message integrated with an Incident or project activity that can be traced back to the message drawer but also during a consultation about a specific Incident or project activity);
| |
| − | * support for the management of discussion forums;
| |
| − | * an information broadcast motor that lets you manage very sophisticated publications in a simple way through the workflow;
| |
| − | * Integration with social networks and communication sharing systems, and external integrations.
| |
| − | '''Main characteristics of itmSUITE® useful in this area :'''
| |
| − | * Management of contextual documentation ( generic deposit and specific contextual archiving in relation to an Incident or Change etc);
| |
| − | * Search engine for all the information ( documents and system records) with management of personalisable context searches;
| |
| − | * Internal contextual message system;
| |
| − | * Gestione forum contestuali;
| |
| − | * Management of contextual forums;
| |
| − | * Gestione processi di pubblicazione delle informazioni broadcast e visualizzazione come news a visibilità configurabile;
| |
| − | * Management of publication processes for information broadcast and visualisation such as news with configurable visibility.
| |
| − | '''Main benefits deriving from the adoption of itmSUITE® :'''
| |
| − | * Data, information and knowledge for people who need it when they need it
| |
| − | | |
| − | ===== Service Operation =====
| |
| − | itmSUITE® supports the management stage of IT services in production. In particular, the processes of:
| |
| − | * Incident Management
| |
| − | * Request Fulfilment
| |
| − | * Problem Management
| |
| − | * Event Management
| |
| − | * Access Management
| |
| − | Discover how by looking at the detailed profiles.
| |
| − | | |
| − | '''Main features of itmSUITE® useful in this area :'''
| |
| − | * Codeless and flexible management of workflow configuration that allows for the automation of the process models without compromises.
| |
| − | * Real-time calculation of targets met by SLA/OLA and maximum effectiveness in the presentation and communication of results
| |
| − | * Extremely flexible and modular "self-service" portal for the management of all requests and notices
| |
| − | * Easy to integrate with external monitoring systems via mail or web services to generate or automatically update its scope (eg.Incident)
| |
| − | * for the generation or automatic update of entities (ex. Incident)
| |
| − | '''Main benefits deriving from the adoption of itmSUITE® :'''
| |
| − | * Reduction in effort and costs incurred to provide the service
| |
| − | * Reduction in effort and management costs of inefficiencies, for both the service provider and customer
| |
| − | * Availability of key data, for example the incidents, input for other processes with the aim of improving and justifying investments
| |
| − | * Respect of objectives and security policies
| |
| − | * Faster and standardized access to services | |
| − | * Faster response times (eg. to events) and the automation of several activities
| |
| − | | |
| − | === [[itmSUITE® - Core modules|Core modules]] ===
| |
| − | This section illustrates the core modules of itmSUITE®.
| |
| − | | |
| − | ==== SM - Service Desk and Service Management ====
| |
| − | This is one of the core modules of itmSUITE® and as such can be activated autonomously. It includes a powerful workflow motor which can be freely configured to support the execution of the IT Service Management processes. SME also has the appropriate functions needed to operate a modern Service Desk, based on service management best practice and standards such as ITIL and ISO/IEC 20000.
| |
| − | | |
| − | For this module, various pre-configured processes that speed up and simplify process activation in line with the best practice and standards are available. These include:
| |
| − | * Demand Management
| |
| − | * Incident Management
| |
| − | * Change Management
| |
| − | * Problem Management
| |
| − | * Request Fulfilment
| |
| − | * Release & Deployment Management
| |
| − | * Access Management
| |
| − | * Ecc.<nowiki/>
| |
| − | The workflow motor can be configured in an unlimited number of ways and as such this module is able to support other processes, for example sales and purchasing, that are outside the restricted field of IT. This module is perfectly integrated with the PM (Project and Portfolio Management) module and numerous other complementary modules.
| |
| − | | |
| − | Together they form a comprehensive and powerful automation tool for IT management (services and projects), key elements for the IT system of a service provider.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * PM - Project and Portfolio Management
| |
| − | * CMS - Configuration Management System
| |
| − | * FM - Financial Management
| |
| − | * OCE - Service Level Management
| |
| − | * ASM - Asset and Service Management
| |
| − | * REP - Reporting Management
| |
| − | * EEM - External Event Management
| |
| − | | |
| − | ==== PM - Project and Portfolio Management ====
| |
| − | This is one of the core modules of itmSUITE® and as such can be activated autonomously. It supports the execution and maturation of management and project processes (Project Management) and project portfolios (Portfolio Management) in line with recognised best practice (eg. PMBoK® or
| |
| − | PRINCE2®).
| |
| − | | |
| − | This module is perfectly integrated with the SM (Service Desk and Service Management) module and numerous other complementary modules.
| |
| − | | |
| − | Together they form a comprehensive and powerful automation tool for IT management (services and projects), key elements for the IT system of a service provider.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * SM - Service Desk and Service Management
| |
| − | * FM - Financial Management
| |
| − | * OCE - Service Level Management
| |
| − | * REP - Reporting Management
| |
| − | * EEM - External Event Management
| |
| − | | |
| − | ==== CSM - Configuration Management System ====
| |
| − | This is one of the core modules of itmSUITE® and as such can be activated autonomously. It supports the creation and maintenance of a modern Configuration Management System, in line with recognised IT Management best practice and standards , in particular ITIL® e ISO/IEC 20000.
| |
| − | In particular, it makes it possible to manage both the hardware and software configuration elements and the relationships between them, both graphically and intuitively.
| |
| − | This module is perfectly integrated with the SM (Service Desk and Service Management) module and DE (Discovery Engine) core modules as well as other complementary modules.
| |
| − | This means you can really get the most out of your investment in the configuration system by making it available to other IT service management processes, which will reap the benefits of Configuration Management.
| |
| − | | |
| − | The main functions of the CMS module are:
| |
| − | * Flexible configuration of entity models, and the relationships and attributes of the configuration elements.
| |
| − | * Graphic production of IT Service mapping
| |
| − | * Navigation and advanced information searches
| |
| − | * Impact analysis
| |
| − | * Monitoring support of end-to-end status
| |
| − | * Reconciliation of information from external systems (via the RE module- Reconciliation Engine)
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * SM - Service Desk and Service Management
| |
| − | * DE – Discovery Engine
| |
| − | * RE - Reconciliation Engine
| |
| − | * SP - Sharepoint Publisher
| |
| − | * REP - Reporting Management
| |
| − | * EEM - External Event Management
| |
| − | | |
| − | ==== DE - Discovery Engine ====
| |
| − | This core module works through agents that can be distributed on the different systems of Unix, Linux or Windows and which make it possible to explore the features of hardware, basic software and application software ( including custom) thanks to the creation of a 'finger print'.
| |
| − | | |
| − | Based on the OCS NG open source product the solution has been enhanced with the ability to explore relationships between software and software. The module has a graphic interface so that the information gathered can be consulted and used autonomously.
| |
| − | | |
| − | Thanks to the related RE- Reconciliation Engine module it is possible to use the system to supply the itmSUITE® CMS module; in other words to automatically supply the Configuration System with the aim of populating or checking and controlling the information on it.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * CMS - Configuration Management System
| |
| − | * RE - Reconciliation Engine
| |
| − | * REP - Reporting Management | |
| − | | |
| − | === [[itmSUITE® - Complementary modules|Complementary modules]] ===
| |
| − | This section illustrates the complementary modules of itmSUITE®.
| |
| − | | |
| − | ==== FM - Financial Management ====
| |
| − | This complementary module is compatible with the core modules SM (SM – Service Desk and Service Management) and PM (Project and Portfolio Management).
| |
| − | It makes it possible to manage budgets, final balance sheets and forecasts for human resources, expenses and ad hoc general expenses (for example costs relating to the purchase of hardware, software, equipment etc).
| |
| − | | |
| − | At a high level, the main functions that this module offers are as follows:
| |
| − | * management of timesheets and expenses;
| |
| − | * management of purchase contracts;
| |
| − | * management of sales contracts;
| |
| − | * management of project budget, final balance sheets and forecasts ( in conjunction with the PM module);
| |
| − | * management of project budget, final balance sheets and forecasts ( in conjunction with the SM module);
| |
| − | * management of budget, final balance sheets and forecasts for individual processes (eg. change, problem, requests etc) ( in conjunction with the SM module);
| |
| − | * Pro-forma invoicing for projects and / or services ( in conjunction with PM or SM modules).
| |
| − | The module offers a basic reportinf function that with the REP (Reporting Management) module becomes unlimited.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * SM - Service Desk and Service Management
| |
| − | * PM - Project and Portfolio Management
| |
| − | * REP - Reporting Management
| |
| − | | |
| − | ==== OCE - Service Level Management ====
| |
| − | This complementary module is compatible with the core modules, SM (Service Desk and Service Management and PM (Project and Portfolio Management).
| |
| − | It makes it possible to define and control KPIs and targets that can easily be used for the management of service levels with clients and suppliers or internally.
| |
| − | | |
| − | At a high level, the main functions that this module offers are as follows:
| |
| − | * the definition of KPIs and targets via a graphic interface;
| |
| − | * near real time calculation of the indicators;
| |
| − | * visualisation of the indicators on lists or records of information (eg. incident, change, projects);
| |
| − | * use of the calculated indicators to trigger action, in other words the rules of business that can be freely configured in the SM (Service Desk and Service Management) module or PM (Project and Portfolio Management) module (for example by sending messages, opening tickets, changing information etc);
| |
| − | * use of the calculated indicators to create reports;
| |
| − | The module offers a basic reporting function that with REP (Reporting Management) module becomes unlimited.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * SM - Service Desk and Service Management
| |
| − | * PM - Project and Portfolio Management
| |
| − | * ASM - Asset and Service Management
| |
| − | * REP - Reporting Management
| |
| − | | |
| − | ==== ASM - Asset and Service Management ====
| |
| − | This complementary module requires the presence of the SM core module – Service Desk and Service
| |
| − | Management.
| |
| − | Its activation makes the CMS (Configuration Management System) database module available and through this, the possibility to insert and modify assets (eg. hardware, software, equipment etc)
| |
| − | The typology of the assets and the attributes (information) which can be managed are freely definable.
| |
| − | The assets can be connected to the SM module ( Service Desk and Service Management) management information . In this way, for example, it is possible to connect a specific configuration element to an incident or a change or an endowment which is personal to a resource.
| |
| − | | |
| − | The module offers the basic reporting function which can become unlimited by adding the REP module ( Reporting Management).
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * SM - Service Desk and Service Management
| |
| − | * REP - Reporting Management
| |
| − | | |
| − | ==== RE - Reconciliation Engine ====
| |
| − | This complementary module requires the presence of the core module CMS- Configuration Management System
| |
| − | It makes it possible to acquire information on the configuration elements or the relationships between those that come from external systems to the itmSUITE, for example CMDB or external asset management systems or even ERP systems or simple calculation sheets, and to manage their intelligent upload into the CMS database via freely configurable rules.
| |
| − | In particular,it permits the verification of this information ( via freely definable reconciliation keys) and the different ways to behave ( creation of a new configuration element, substitution of data with up to date information etc). New interfaces (plug ins can be created, upon request, for any external system)
| |
| − | It also goes with the DE-Discovery Engine core module for which it offers a plug in that makes it possible to intelligently upload the information on the configuration elements identified by DE- Discovery Engine in the itmSUITE® CMS.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * CMS - Configuration Management System
| |
| − | * DE – Discovery Engine
| |
| − | | |
| − | ==== SP - Sharepoint Publisher ====
| |
| − | This complementary module permits interaction between the core CMS (Configuration Management System) module and portals based on Microsoft Sharepoint
| |
| − | | |
| − | The CMS side offers all the functions needed to totally or partially export the CMS content, including the configuration elements and the graphic representation of these (maps). The Sharepoint side offers a collection of components ( Web Parts) that make it possible to browse the information contained on the Sharepoint pages while maintaining all the original links between the different information.
| |
| − | | |
| − | In this way, it is possible to publish 'snapshots' of the Configuration Management System at certain moments on evolved communication tools (Sharepoint) which mean structured information from the CMS can be combined with non-structured information. This component is particularly useful and efficient for the creation of a Service Catalogue in line with IT Service Management best.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * CMS - Configuration Management System
| |
| − | | |
| − | ==== REP - Reporting Management ====
| |
| − | This complementary module is based on the open source BIRT product which has a designer reporting with drag & drop interface and an engine for the execution and presentation of the report that is perfectly integrated with other modules itmSUITE ®. These modules have natively some reports, but the module REP - Reporting Management allows you to integrate new ones made with the designer. It is therefore an indispensable tool for those who do not have or do not intend to implement a reporting platform independent but who wish to rely on itmSUITE ® for this.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * SM - Service Desk and Service Management
| |
| − | * PM - Project and Portfolio Management
| |
| − | * CMS - Configuration Management System
| |
| − | * DE – Discovery Engine
| |
| − | * FM - Financial Management
| |
| − | * OCE - Service Level Management
| |
| − | * ASM - Asset and Service Management
| |
| − | | |
| − | ==== EEM - External Event Management ====
| |
| − | It is more than likely that an organisation that manages projects or services, either internally or externally, will have to communicate with other external systems ( typical examples are infrastructure monitoring systems or client/supplier trouble ticketing systems)
| |
| − | It is for this reason that the itmSUITE® architecture has been studied specifically to manage the integration of the system.
| |
| − | In particular, there is an internal bus for integration between all the modules ( MB-message Bus) which is included with the purchase of any core module and the EEM -External Event Management- module. The lattter is set up for dialogue with external systems, and this can take place via mail or web services.
| |
| − | The EEM parser interprets the messages that arrive and activates the processes that have to deal with them thanks to the business rule management components (known as Action Engine) of the various itmSUITE® modules.
| |
| − | The integration of itmSUITE® in relation to external systems usually occurs via the Action Engine where the triggers and steps to be taken on the external systems which offer such services, are configured.
| |
| − | | |
| − | Typical examples of integration are as follows:
| |
| − | * Opening or update of Incident and/ or Change based on notifications coming from the monitoring system ( eg. poor service or a server back in service);
| |
| − | * Opening or update of Incident, Change or problem based on notifications coming from the systems that manage external tickets.
| |
| − | The integration with LDAP and Active Directory is managed by the itmSUITE® core modules and doesn't require the installation of the EEM component.
| |
| − | | |
| − | ====== Related Modules ======
| |
| − | * SM - Service Desk and Service Management
| |
| − | * PM - Project and Portfolio Management | |
| − | * CMS - Configuration Management System
| |
| − | | |
| − | === [[itmSUITE® - Architecture|Architecture]] ===
| |
| − | This section illustrates the architecture itmSUITE®.
| |
| − | | |
| − | === [[Glossary|Glossary]] ===
| |
| − | This section contains the glossary for the key concepts and terms used by itmSUITE®.
| |
| − | | |
| − | ==== [[sottotitlo|test]] ====
| |
| − | ciao questa è una prova
| |
| − | | |
| − | ===== [[altra prova3|altra prova]] =====
| |
| − | ciao ciao ciao
| |
| − | | |
| − | === [[dssddsfdsf|fdsdsfadsasf]] ===
| |
| − | test[[category:ItmSUITE®]]
| |
