ROGSI/DMS stores more information and data in the ROGSI/DMS database as any other BCM tool.
ROGSI/DMS combines the following tools:

  • Process Management
  • Service Management
  • Asset Management
  • Contract Management
  • Address Management
  • Graphical  Planning System
  • Disaster Management System
  • Production Management System
  • Workflow Management System
  • Mobile Documentation


  • BIA - Business Impact Analysis
  • RIA – Risk Analysis

All data are stored in database. No redundant data are stored in the database. Changes of data are valid for all related data.

Insert of data can be done by entering all data into the fields, either in rows or in the form view or you can import most of the data into the database. This reduces the time for the first time to fill the database and also for the maintenance. Also the quality is often better than by online maintenance. Imports can be executed automatically, controlled by any scheduler.

The maintenance of the processes is most important to see which processes must be available without any interruption and what is the maximum downtime. All kind of processes, services or application can be maintained in RGOSI/DMS. All relevant resources are linked to these processes. Just by a mouse click you can see, which server is needed, who is responsible, what SLA is signed or whatever is related to this records.

The disaster recovery plans are the heart of the BCM documentation. But also plans for smaller interrupts or any disturbance are very helpful to get back to normal business in a short time. Plans can be created for work around, recovery or even set up of resources for the normal business.

Plans are structured in plans, blocks and activities. Plans can contain other plans, blocks or activities. Queries allow controlling the process at any step. An integrated release management controls the number of plans. If a new plan or a modified plan is released, the old version is stored in an archive. An active execution of plans guides the teams and persons through all steps of the plan. Several teams can work at the same plan. Again: when a plan was completely executed, this plan is stored in the archive and can be seen at any time.