The Asset information Consolidation and Evaluation (AiCE) module allows organisations to create repositories of user defined data sets that can be linked to Assets.   It allows repository data to be retained in the same application as other asset data thereby minimising interfaces and the synchronisation problems associated with maintaining disparate systems.

Download the Data Sheet –

The application supports:

• Creation of Repository Definitions with associated user defined repository fields.
• Data being loaded into the repository from various data source spreadsheets (csv),
• Creation of multiple instances of a Repository Definition. This allows, for example, a budgeting repository definition to be used to create a new instance for each financial year.
• Retention of multiple versions of an instance. The versions provide a history of the re-work processes which occurred. Each version is assigned to a User Group. Only users within a version’s nominated user group can maintain that version.
• Freezing of versions can be to prevent further changes.
• Individual repository lines being approved or rejected by the nominated approver, with new versions allowing the approver of each data source to be entered.
• Data fields that are neither key fields nor derived fields can be updated.
• The enquiry form can be used by authorities who submitted details and also when the process is finally reviewed. The enquiry using standard grid manipulation allows grouping by any field(s) such as;
  • Project type or
  • Asset type.
• Using the .NET grid technology, on large record number to provide the user the ability to manipulate data.
• An export to a .csv format file by the standard .Net grid, allowing reporting flexibility.

AiCE Overview

The following diagram shows how AiCE coexists within an organisations applications infrastructure.

Asset information Consolidation & Evaluation

AiCE Security

• Security supports restriction of functions based on the workplace(s) to which a user has access.
• Repository Data Access determines if access is available to All, a List or a Single Data Source for a Repository. Data lines can only be viewed and maintain by those had access to the originating data source.
• An individual can be assigned to multiple User Groups, with only those in the User group being able to maintain versions of an instance.

• Repository Data Access determines if access is available to All, a List or a Single Data Source for a Repository. Data lines can only be viewed and maintain by those had access to the originating data source.
• An individual can be assigned to multiple User Groups, with only those in the User group being able to maintain versions of an instance.