Any satisfactory solution for IT documentation will naturally place main emphasis on the compilation and technical documentation of all IT components in use. The desired level of detail here will be decided by the user, and ranges from a pure compilation of all relevant manufacturer and model information to an exact representation of the basic infrastructure. This applies equally for all connection data from electricity, storage and data networks or the administration and assignment of software and licenses.
Contract and operating modes:
Besides technical documentation, i-doit also provides reliable compilation and assignment of contract and operating data for the documented objects, whether this is the maintenance agreement, indicating contacts and expiry date, or emergency response plans for components and systems, or digital manuals or configuration data. All documents in i-doit are in this regard subject to a version administration, and all amendments and adjustments will therefore always be clear and traceable. An easy-to-follow notification function and customizable threshold values mean reminders can be sent automatically by mail.
In addition to the direct dependencies arising from connection data or the assignment of software to systems, it is also possible to document manual dependencies arising indirectly from the IT business processes. Dependencies can also be defined to several objects in different directions. In this way it can be recognised at a glance which services or functions are no longer available in the case of some breakdown. These data will also be used by, for example, the add-on for the Nagios® network monitor.
i-doit allows several environments to be recorded and documented parallel, but independently of each other. The documentation of each client takes place on its own separate level, which does not allow any cross access between clients. This means that several distinct areas within a company or documentation for several different companies can be realised on one platform.
The Logbook in i-doit protocols all changes made to an object. In combination with an (optional) commentary function, these Logbook entries can also be provided with additional information in order to, for example, record the reason for some change. The Logbook also serves as an archive for different add-ons, in which the status or events from live operations can be stored. This functionality allows the Logbook to provide a central modification and status archive for the IT components in use.
Many of the settings in i-doit are configurable. It can, for example, be defined which objects are to be documented at which detail depth, whether and how summary pages for objects are to be displayed or which country-specific settings should apply. The system moreover also has multilingual capability and can be adjusted to additional languages by means of an installed editor. The my-doit area allows selective views of objects and provides an overview of the different active Workflows to which the user is currently connected.
To ensure full support we recommend using i-doit on one of the operating systems listed below. i-doit generally runs on any current operating system if an Apache Webserver, a MySQL-database and PHP in the respectively current version is installed.
- Apache Webserver 2.2, 2.4
- MySQL 5.1, 5.5 (deactivate safe mode) or MariaDB 5.5
- PHP 5.4.x, 5.5.x
Supported server systems:
- Microsoft Windows 7/8/Server 2003/2008/2012
- Red Hat Enterprise Linux (RHEL) 6.5/7.0 mit PHP 5.4
- SUSE Linux Enterprise Server (SLES) 12
- Ubuntu 12.04 LTS, 13.10, 14.04 LTS
- Debian GNU/Linux 7.0, 7.5
- Safari 7, 8
- Google Chrome 30-41
- Microsoft Internet Explorer 9-11
- Mozilla Firefox 24 ESR, 31 ESR, 30-36
- current multi-core processor
- 1 GB ram
- 1 GB hard disk space
These system requirements only fit to the latest release of i-doit.