IT governance portal
Faced with the main operational difficulties that CIOs have, Ankaa Pmo®
responds with a management tool that allows, depending on the activated modules:
- Business Application Asset Management (APM)
- the implementation of a database of hardware and software configurations (CMDB/SAM)
- cartography and architecture of the SI (URBA)
- centralized management of operational, business and technical documentation as well as FAQs (Doc & FAQ)
- managing a service catalog associated with applications or hardware (ITSM)
- the management of the user requests (Ticketing) carried out with regard to the service offering resulting from the service catalog.
- management and guidance of project portfolios (PPM) business or technical
APM module (Application Portfolio Management)
The Application Portfolio Management (APM) module aims to provide all the elements necessary for the management of the business application assets, namely the identification and precise qualification of all the business applications of the company.
The APM module makes it possible to develop a multidimensional vision of the business application assets. It offers as by default the following qualification axes:
- Responsibility: allows each business asset to document all the stakeholders (MO, ME, manager, host, …)
- Risk: allows each business asset to qualify the level of associated risks (operational, technical, image, …)
- Health check: allows for each business asset to qualify their state of health check (obsolescence, performance, maintainability, complexity, …)
- Technology: allows for each business asset to describe all the technologies / skills needed for its OLS
Each element is associated with a set of descriptive information and can be enriched at will.
CMDB module (Configuration Management Database)
The objective of the CMDB module is to provide all the elements necessary for managing a set of physical assets (of whatever nature: IT infrastructure, telephony, equipment, etc.).
The CMDB module is preconfigured with a minimum level of asset description. The MSDS for each type of asset can be specialized to add all the necessary metadata to the desired level of description .
The specialization of an active form is an act of parameterization  of the solution to best suit the ambitions of the user. It is not a specific development.
Depending on the desired level of functionality, the CMDB module may include:
- A sub-module contract to manage and track any type of contract associated with assets or software / packages.
- A localization sub-module allowing the “geographical” location of the assets (zone, country, site, building, hall, …)
- A SAM sub-module for the identification and tracking of all software / software installations on IT equipment. The SAM module uses the “technology” sub-module to establish a unique list of software / packages.
- A deployment sub-module to manage the link between the business applications and the technical resources (software / software packages) and thus produce all types of impact / dependency dashboards between the APM / SAM / CMDB overview.
A graphically mapped sub-module allowing the graphic description of the connections between means / assets.
  The level of description can evolve over time to support a rise in asset management within the organization.
 We ensure 100% upward compatibility of the configuration. A configuration made for the N version of the platform is fully compatible with all N + X versions to follow.
URBA module (SI urbanization)
The objective of the URBA module is to enable you to rationalize and urbanize your IS. It makes it possible to develop all the graphically maps needed to manage transformation projects for both the business and technical levels.
The URBA module in particular:
- To develop a business vision by describing the processes, activities, and organization of the company.
- To develop a functional vision of the company (business functional graphically maps) and applications (application functions).
- Bring functional visions together to assess the suitability of applications for functional needs or to identify redundancies or gaps.
- Describe the information manipulated by the stakeholders, processes, functions, applications.
- To describe all information flows in order to perceive all the functional interfaces, applications, techniques, …
The URBA module can be extended with a risk component to develop a complete vision of the operational and technical risks and all the control procedures associated with them
Docs & Faq Module (Docs & Faq Module)
The objective of the Documentation & FAQ module is to centralize the reference documentation whether it is business, application or technical.
It allows you to build a single document portal centralizing all your documentation in order to make it accessible to all.
The module allows:
- Centralized management of a document repository
- Fine tune modeling of operating documents or procedures
- Automatic generation and automatic updating of the documents produced (in Web or Office format)
- Management of business, application or technical FAQs as well as their publication in the form of a Web or Office document
- The indexing of all documentation based on a dictionary of key words relevant to your context.
In addition, the Documentation & FAQ module allows you to manage and distribute any type of third-party documents produced by any type of tool (uploading, indexing and dissemination via the website).
Depending on the desired level of functionality, the Documentation & FAQ module may include a “Reader feedback” management module that allows anyone viewing the portal to report an error or add information to enrich your document database and to keep it alive.
ITSM module (IT Service Management)
The objective of the ITSM module is to provide all the necessary elements for managing and displaying a catalog of services for internal or external customers.
The ITSM module makes it possible to produce one or more portals  of services dedicated to:
- the exposure of services to the appropriate readership
- pre-qualification (through tree questionnaires of the decision tree type) of service requests and dispatching them to adhoc processing tools (ticketing module, other ticketing application, third-party platform, etc.)
- the publication of KPI for monitoring service commitments on the basis of information from the Ticketing module or information from third-party solutions .
The service portals can include all or part of information from other modules (application heritage, application or business documentation, FAQ, …) to “push” the information that is useful to the target readerships of these portals.
Depending on the desired level of functionality, the ITSM module can include:
- An investigation sub-module allowing the management of survey questionnaires
- An SLA sub-module allowing the definition of SLA on perimeters (described in terms of staff) and associated with automatic KPIs .
 We can train your internal teams to develop the skills needed to complete additional portals or to modify the portal initially provided.
 The ITSM module provides automatic KPIs based on information from the Ticketing module. For KPIs built on the basis of third-party application information, they involve interfaces in the form of XML file exchanges or Web Service calls. The production of these interfaces generally involves platform-specific computer development whose complexity varies according to the interfaces proposed by said third-party applications.
 Automatic KPIs are built based on information from the Ticketing module. If this module is not used the KPIs associated with SLAs are obtained from third party tools on the basis of interface plugin to be developed.
Ticketing module (Helpdesk)
The Ticketing module allows the creation  and the management of service tickets.
The Ticketing module allows:
- The management of different types of requests (issue, request for services, request for upgrades) on the basis of the different services offered through the ITSM module
- Follow-up of the actions carried out for each ticket
- The creation of an audit trail for each ticket
- The definition of a configurable life cycle for each type of request
- The centralization of all the exchanges Users / Team in charge in order to preserve the history
- The association of tickets with public FAQs  or private (under conditions of use of the Documentation & FAQs module)
Depending on the desired level of functionality, the Ticketing module may include:
- An Action sub-module to manage action plans assigned to stakeholders
An entity / structure sub-module to describe the organizations (organizational and personnel units) involved in the processing of service requests and assign them responsibilities in these processes
 The creation of tickets can be done through the ticketing module or through a service portal from the ITSM module
 The public FAQs are exposed in the service portals in order to develop the autonomy of the users
PPM module (Project Portfolio Management)
The PPM module (Project Portfolio Management) allows the management of project portfolios.
The PPM module enables portfolio management based on a configurable project life cycle. It can thus go back to the preliminary projects and implement the phases / stages corresponding to your organization.
The PPM module allows you to develop a multidimensional vision of your project portfolios:
- Business / transformation dimension related to applications (APM) or to business functions (URBA)
- Technical dimension related to the assets of the CMDB Dimension support and / or evolutions in connection with the tickets (anomaly, request of evolution, …)
- Technological dimension related to technologies and their instances in the CMDB
- Other dimensions …
In addition, the PPM module allows you to standardize the organization of your projects to ensure better monitoring by formalizing:
- The subdivision / activities and their programming
- Les Deliverables
- The teams
- The risks
- Dependencies Groupings into programs
- Governance and monitoring
Operationally, the PPM module provides:
- A management and monitoring tool for action plans
- A tool for centralizing project documents
- A tool for monitoring the project life in the form of a logbook
- A tool for centralizing exchanges in order to keep track of them and to develop the community of project stakeholders
Depending on the desired level of functionality, the PPM module can include:
- A sub-module Entering times to manage stakeholder charges
- A sub-module Remains to be done to calculate a predictive performance of the project
- A purchase and billing sub-module to manage and track purchases related to the project and billing plan (of your client)
You want more information on how to integrate the core portal into your business context. Leave us your details and we will answer you quickly.