Information management is a business process that can be significantly improved by the use of a common language. Gellish English (or any other Gellish language variant) has unique characteristics to support this process. Those characteristics are:

• It is based on a common dictionary, that is based on international standards.
• It enables smooth integration of data and documents integration from different sources, because of the standardization of terminology and the unique identification of every object and every fact.
• It enables tracing, creation, modification and termination of the validity of every single fact or collection of facts.
• It supports version control, facilitated by auxiliary facts for the source, the date of creation and modification and the succession of facts, etc.
• It supports multi-language data integration.

The information management business process includes the following sub-processes.

This sub-process includes the specification and extension of a common language that should be used in all applications that store data that is managed. It might also cover the language that is used to communicate with business partners. This may be based on the Gellish English Dictionary-Taxonomy (or the Gellish Dutch Dictionary or any other variant of Gellish). The process may also include the development of a proprietary Gellish Domain Dictionary or a translation for your own application domain. The process also includes the extension of such a dictionary-taxonomy as required by your business, especially be managing the names and codes for individual things that are created in the organization. The Gellish Modeling Method includes guidelines on enhancement or extension of such a dictionary.

This includes a specification of which types of documents and data sets are required to be delivered when particular types facility components or products are produced or delivered. The method describes how such requirements models can be provided in the Gellish language in the form of one or more Gellish Database tables, so that they can be used by a computer to verify delivered documents and data.

This includes a [:Requirements Models|specification of requirements]] for qualities of the documents and data sets, such as completeness, consistency, timeliness, verification of technical adequacy and the use of standards. It also includes requirements about the delivery of auxiliary data, which are data about the documents and data sets (e.g. title, author, date of issues, etc.) as well as data about relations between the documents and the objects about which the documents and data sets provide information and data that define a facility model when the documents and data sets together provide information about a complex facility.

This includes the process to retrieve one or more documents and/or data sets (a package), check-out and registration of the party that is expected to modify the content of the documents or data sets. It may also include the provision of identifiers for the creation of new documents or data sets or of identifiers for the creation of objects about which the documents or data sets provide information. Typically the information is supplied to a design office or to a contractor or supplier, again expressed in the Gellish language, so thatit can be imported automatically in design systems.

This includes the actual creation or modification of the documents and data sets and of the auxiliary data conform the requirements. The creation of auxiliary data may also include the specification of data that define a Facility Model that is used to create a Facility Information Model (FIM) or a Building Information Model (BIM).

This includes the verification of the deliverables against requirements. It includes also the verification of completeness, timeliness, etc. and the correct usage of the common language for classification of documents, data sets, facility components, properties, etc. When the requirements as well as the deliverables are both created in the common Gellish language, then it is possible to use computer aided verification of the deliverables against the requirements.

This includes the storage of the documents and data sets and the auxiliary data in a Facility Information Model (using one or more information management systems) that are together able to also store the facility model and the relations between the facility components and the documents and data sets, their classification and requirements, as well as the content of the data sets, especially when those data sets are also expressed in the Gellish language.

This means that users are given access to query, search, retrieve and read the information.

Return to Start