Here's an overview of our information model and the terminology we use to when we refer to it.
Kes organises standardisation around templates. These templates consist of assets which can have properties.
Schematically the information hierarchy looks as follows:
Project > Reports > Activity > Templates > Assets > Properties > (optional> Dependent Properties
I'll explain each component one by one.
Projects are our company's regular ABW-based projects. Reports are documents, usually Word or PDF documents, but could also be more technical documents such as PFD's or P&ID's.
An Activity is a project activity which we execute on behalf of a client. The output of such an activity is a deliverable, usually a report. For instance the client might need a permit or we need to create a basis of design. In general activities should map to your product breakdown structure/work orders.
A Template is a predefined set of standard texts, maps, images, and other data that go into a report.
The preconfigured sets are called Assets. All assets of a single template belong to an asset library. Assets can repeat. For instance if you are inspecting elevators and there are five elevators you might want a single asset that you repeat five times.
A Property is a piece of information that can be entered by end-user. It has a particular type for instance it is a single select input type, a location, an image, etc. The way to get the data from the end-user is by asking the end-user a question. A property also configure the question.
The properties configure the asset.