The DOMA operation group provides document management functions with easy versioning and flexible access control.

To set up DOMA:

• set the standard system setting "doc_base_dir" to a directory accessible by the web server
• set the DOMA system setting "allowed_file_extensions" to the file types you want to allow in the document store
• set the DOMA system setting "max_file_size" to the maximum allowed file size in MB
• set the DOMA system setting "min_free_disk_space" to the minimum free disk space to preserve in MB

An automatic document ID is assigned when a document is checked in. This document ID can be used as a reference to the document in other operations.

DOMA provides multiple mechanisms for access control in the E2 and E3 edition:

• E2 and E3 edition
  Security level: users must be entitled to a level equal or higher than the level which is assigned to the document to be allowed viewing it
  Operation-specific protection: an operation specific function is used to determine whether a user can view a document (e.g. based on his or her organizational position)
  
  
• E3 edition
  Data area level protection: the user must have access to one of the data areas assigned to the document to be allowed viewing it
  Location level protection: the user must have access to one of the locations assigned to the document to be allowed viewing it

The COMA operation group provides a database for the contractual relations of a company.

It provides predefined data fields as well as general-purpose database fields.

To set up COMA:

1. define the standard data fields for all contract types,
2. define custom contract types which you can set up to include additional data fields or exclude standard data fields

Using these contract types, you create and edit contract entries.

The following data fields should always be included in all contract types:

• the review date: you can set this to the date you want the contract to be reviewed (e.g. 1 month before auto-renewal if not canceled)
• the expired status: when a contract is no longer valid (by canceling or expiration), you can set the expired status to yes to move the contract in the expired area

It is recommended to keep these data fields in the data field list for the standard contract type.

FIPS is a financial planning module with support for

• balance sheet (B/S)
• profit and loss statement (P/L)
• cash flow statement (C/F)
• statistical sheet
• several types of analysis (structure analysis, budget-actual comparison, figure analysis)

FIPS uses and stores the following value types:

• initial values (entered once per year, can be based on automatically computed values)
• budget values (automatically used when working on planning sheets of future years)
• actual values (values entered for past periods of the current year)
• forecast values (values entered for future periods of the current year)

Internally, for each figure and year, FIPS stores one initial value, one row of budget values and one row of actual/forecast values. The initial value is used as the basis for the computation of both budget and actual YTD values. Actual/forecast values are stored in one row, but interpreted differently depending on the current month (value entries for the current month or previous months are treated as actual values, entries for future months are treated as forecast values.

KPIS is an operation group with support for

• defining corporate key performance indicators (KPI)
• decentralized, web-based input of monthly KPI figures
• navigating through KPI charts in a management review and adding actions
• output of a management report in on-screen and printable formats

KPIS supports KPI for multiple locations by allowing:

• the definition of common KPI for all locations
• the exclusion of common KPI from reporting for individual locations
• the definition of local KPI for individual locations

It should be noted that by design KPIS is not a semantic system (does not associate meaning wit the figures it manages). Instead, it provides a different method for value interpretation through chart drawing rules. In practice, that means:

• if you want to do a target-actual comparison, you have to create a target KPI and a budget KPI; for KPIS, these figures will initially not be related in any way
• to make these KPI appear related, you use the same group ID and adjacent sequence IDs 
• to see when a target has not been reached, you set up coloring rules in the chart definition (example rule: if KPI1 < KPI2, set the chart color to red)

As you can individually define entirely different KPI scenarios, this approach is highly flexible, but requires some one-time configuration when you initially define the KPI.

E3 edition only

In the E3 edition, an advanced KPI access control system is provided:

• KPI are associated with a read and a write data area
• KPI figures are input by location
• in order to read a KPI figure, an application user must have read or write access to the read data area for a location
• in order to write a KPI figure, an application user must have write access to the write data area for a location

Using the advanced control system, complex configurations are possible. For example, using one data area per department, the following setup could be achieved in a multi-location corporation:

• the production manager is given write access to the production data area for his or her location and read access to the production area for similar locations for benchmarking purposes
• the quality manager is given write access to the quality data area for his or her location and read access to all other KPI-relevant data areas for the purpose of preparing a management review
• the accountants are given write access to the the logistics data area with inventory KPI, and the supply chain, purchasing, sales and production managers are given read access in order to monitor optimization of the inventory
• the headquarter controller is given read access to the financial data area for all locations
• the general manager is given read access to all KPI-relevant data areas

PEDE (PEople DEvelopment) supports

• defining the organization (structure, workforce)
• defining the skill system (positions, qualifications and abilities)
• defining the personnel processes and relating them to positions 
• visualization of target-actual differences in manpower need (by position, by process) and skills (qualification matrix)
• planning and recording personnel training
• training effectiveness evaluation

PEDE uses and advanced access control system which greatly reduces the amount of configuration required and which allows every user to participate in the people development process in compliance with his or her organizational role. The advanced access control system derives permissions from the organizational role of a user. For instance, the head of a department can see skills of the employees assigned to him or her, but not the skills of other employees.

SARS (Sales Acquisition Reporting System) provides tools to track and analyze new business opportunities. It supports:

• creation and distribution of the minutes of customer dialogue (customer visits, phone talks, discussion events, ...)
• defining the system to analyze the sales and customer acquisition process
• tracking of new potential projects and associated sales opportunities
• analyzing the causes of lost projects
• monitoring the performance of the quotation process
• deriving the sales forecast resulting from new projects