Successfully reported this slideshow.

Ni2 demo april07

1,000 views

Published on

  • Be the first to comment

  • Be the first to like this

Ni2 demo april07

  1. 1. Main Menu Change & Release Management Configuration Management CMDB Platform Multi-Domain Configuration Absolute Visibility on Network and IT
  2. 2. CMDB Platform <ul><li>The N(i) 2 CMDB was built from the ground up and not as an extension to an existing domain </li></ul><ul><li>As a standalone application, it provides insightful analytics and visuals </li></ul><ul><li>As an enterprise CMDB, it has no limitations in its CI scope: equipment, event, content, etc. </li></ul><ul><li>It is built on a operability standards and its object model delivers true federation </li></ul>
  3. 3. Repository of CIs & Relations <ul><li>Treats all objects as CIs including objects like incidents, requests, tasks… </li></ul><ul><li>Tracks CI instance attributes </li></ul><ul><li>Tracks CI change history </li></ul><ul><li>Maintains external file attachments like configuration files </li></ul><ul><li>Manages relations between CIs </li></ul>Click here for more…
  4. 4. Catalogs <ul><li>Catalogs are used to standardize technology and to normalize policies </li></ul><ul><li>CIs inherit some of their properties and rules from catalog items. </li></ul><ul><li>Catalog Items are classified by category, sub-category, class, and type </li></ul><ul><li>Catalogs are built with the Catalog Management module or could be populated through data import </li></ul>Click here for more…
  5. 5. CMDB Generic Reporting <ul><li>Provides a set of generic reports that can report on CIs in different output format: </li></ul><ul><ul><li>Tabular </li></ul></ul><ul><ul><li>Schematic </li></ul></ul><ul><ul><li>Location </li></ul></ul><ul><ul><li>Statistic </li></ul></ul><ul><li>Provides extensive amount of domain specific reports </li></ul><ul><li>Provides Ni2 Query Language (NQL) that leverages the N(i)² object model concepts (CI, relationships and business rules) </li></ul>Click here for more…
  6. 6. Multi-Domains Dependency <ul><li>Generates application models (software, interfaces, adapters, processes) </li></ul><ul><li>Maps applications to logical infrastructure (cluster nodes, application server....) </li></ul><ul><li>Maps logical nodes to physical infrastructure (servers, chassis, storage, locations…) </li></ul><ul><li>Maps applications to service model enabling the definition of Service Oriented Architecture (SOA) </li></ul><ul><li>Models impact of services on business </li></ul>Click here for more…
  7. 7. Impact Analysis <ul><li>Analyzes the configuration make-up of a service </li></ul><ul><li>Analyzes any CI impact on people </li></ul><ul><li>Allows to define any impact theme for any domain </li></ul>Click here for more…
  8. 8. Locations <ul><li>Manages containership relation between cities, buildings, floors, rooms, racks… </li></ul><ul><li>Manages CI locations on floor-plans </li></ul><ul><li>Manages CI locations on maps (Maps can be extracted from GIS services or map files) </li></ul><ul><li>Tracks civic addresses </li></ul>Click here for more…
  9. 9. Configuration Management <ul><li>The N(i) 2 CMDB offers multiple strategies to manage CIs: </li></ul><ul><li>During initial load, powerful import tools may be used to massively populate the CMDB </li></ul><ul><li>In the change process, features and workflows help register all changes in the CMDB </li></ul><ul><li>Discovery tools assist in updating the CMDB with logical CIs, and in auditing release changes </li></ul>
  10. 10. IMAC Functions <ul><li>Provides a set of features to add/modify/delete CIs and relations </li></ul><ul><li>Supports linking external attachments to CIs </li></ul><ul><li>Allows the management of attachments within a content management component </li></ul><ul><li>Provides features to define multiple graphical representation for CIs based on the viewing context </li></ul>Click here for more…
  11. 11. Discovery <ul><li>Discovers hardware and software assets </li></ul><ul><li>Extracts asset attributes like serial number and host name </li></ul><ul><li>Automatically builds relations between discovered items </li></ul><ul><li>Uses SNMP or/and WMI protocols </li></ul><ul><li>Discovers based on a host name, a single IP, a range of IPs, or a full subnet </li></ul><ul><li>Leverages rule based reconciliation engine </li></ul>Click here for more…
  12. 12. Import / Export <ul><li>Imports CIs and their attributes from any formatted text file </li></ul><ul><li>Imports CIs relations </li></ul><ul><li>Restructures raw data into N(i) 2 object data </li></ul><ul><li>Reconciles imported data with existing data in the CMDB </li></ul><ul><li>Leverages a staging area to audit changes </li></ul><ul><li>Exports CIs and their relations from the CMDB </li></ul>Click here for more…
  13. 13. Multi-Domain Configuration Management <ul><li>The N(i) 2 CMDB architecture is designed to support multiple IT domains </li></ul><ul><li>The N(i) 2 CMDB breaks down IT silos by federating and sharing information across domains </li></ul><ul><li>In addition to the N(i) 2 CMDB, a series of management and modeling applications offer domain specific configuration management tools </li></ul>Organization Design Service Design Network Design Connectivity Design Structure Design Rack Design Asset Design
  14. 14. Rack Design <ul><li>Manages mounting positions in racks </li></ul><ul><li>Manages cards position in chassis </li></ul><ul><li>Supports rack design through reporting on heat dissipation, power load, physical characteristics… </li></ul><ul><li>Tracks physical connectivity between devices </li></ul>Click here for more…
  15. 15. Connectivity Design <ul><li>Manages circuits between sites </li></ul><ul><li>Treats circuit as an asset by tracking circuit’s TCO </li></ul><ul><li>Manages channels in network facility for accurate capacity management planning </li></ul><ul><li>Analyzes circuit dependencies for better change assessment </li></ul>Click here for more…
  16. 16. Supporting Structure Design <ul><li>Manages port to port connections </li></ul><ul><li>Manages connections between sites </li></ul><ul><li>Leverages a spatially enabled environment </li></ul>Click here for more…
  17. 17. Network Design <ul><li>Manages network inventory including sub-nets, IP addresses … </li></ul><ul><li>Dynamically generates networks schematics from the CMDB </li></ul><ul><li>Tracks IP addresses availability </li></ul><ul><li>Tracks DHCP ranges </li></ul>Click here for more…
  18. 18. Organization & Service Design <ul><li>Tracks human resources, organizations, groups… </li></ul><ul><li>Reports on organization structure, hierarchy… </li></ul><ul><li>Provides tools to model business services </li></ul><ul><li>Reports on services dependency, allocations… </li></ul>Click here for more…
  19. 19. Change & Release Management <ul><li>The N(i) 2 CMDB supports three types of change process: active and proactive </li></ul><ul><li>Reactive: unplanned changes are discovered through a discovery process </li></ul><ul><li>Active: changes occur via a request and the CMDB manages the change process lifecycle </li></ul><ul><li>Proactive: changes are modeled and their impacts assessed via “what if” scenarios </li></ul>
  20. 20. Request Change <ul><li>Advanced request for change management </li></ul><ul><li>Request classification through policy catalog </li></ul><ul><li>Automatic notification to change manager </li></ul><ul><li>Identification of impacted configuration items through the CMDB </li></ul>Click here for more…
  21. 21. Assess Change <ul><li>Checks current configurations for conflicts with future infrastructure changes </li></ul><ul><li>Models future “as intended” changes in alternate scenarios </li></ul><ul><li>Analyses change impact on business from financial of and logistic perspectives </li></ul>Click here for more…
  22. 22. Authorize Change <ul><li>Change process supported by an approval engine </li></ul><ul><li>Support for the escalation process </li></ul><ul><li>Change history tracking for auditing and Sox compliancy </li></ul>Click here for more…
  23. 23. Build & Test Change <ul><li>Audits planned changes to extract required deployment activities </li></ul><ul><li>Automatically generates release plan to ensure all change activities are regarded </li></ul><ul><li>Optimizes change plans through alternate scenarios </li></ul>Click here for more…
  24. 24. Roll Out Change <ul><li>Schedules release tasks </li></ul><ul><li>Manages tasks dependencies </li></ul><ul><li>Assigns tasks to deployment staff </li></ul><ul><li>Ensures availability of resources through common calendar </li></ul>Click here for more…

×