Lookup or reference tables within the base data supply list of values for different sections in the system. A good example is the cost centres. There should be a list of cost centres available but if a user enters a non existent value, this value should be validated and not be accepted.
The company’s organizational structure is developed and evolves within the base table.
As an example we can assign a certain employee as a worker in a certain workgroup. E.g. Mr. Smith is assigned to the electronics department by assigning the 2 base table values.
Later, if there is a reference to Mr. Smith in the system, the function will validate and show that Mr. Smith is a electrician and works for a certain branch. All this predefinition of structural settings can be applied within the organizational base data.
If, at a later stage, somebody requests an electrician, the system can provide a list of qualified, unassigned electricians.
All these settings and assignments are flexible and are not mandatory. The system administrator will decide all these settings.
SMaintain can define very complex structures even for multi national enterprises, by using all the offered base tables.
SMaintain is applicable in a very "lean" way as well and can support very flat structures, allowing rapid implementation.
Base data is divided in 3 groups.
General Base data
Describes the operational economic assignments of the internal staff, their group organization and financial assignments in cost centre structures. It also categorises suppliers of materials and services. Work category definitions like "repair”, “scheduled maintenance”, “investment” etc." can be done to allow precise analysis at a later date, based on these definitions. Furthermore fault codes and other General Base data types are available.
Material base data
Describes the stock or purchasing department’s specific base tables, such as "measurement units”, “spare part groups”, “type of delivery”, “payment types” and many more.
System base data.
Defines the configuration of the system. It is used to define the levels at which you want to structure your assets as well as system parameters for definition of settings in the system, which are available for customizing without programming needs.
These settings are defined on system implementation while the base data entry is performed. The customer will decide about these settings on initial implementation.
The correct security settings and layout definitions for the users and groups are part of the system base data.
