bimSystems (alpha) - organizing design and development of technical systems - process plants and HVAC systems!


The Engineering ToolBox bimSystems can be used to organize design, development and documentation of technical systems - like

Use bimSystems to build projects "brick by brick" by defining the system structure and adding components with technical data and specifications. Add documents like P&ID's and process flow diagrams to systems, manufacturers data to components, architectural drawings to buildings and floors, site plans to sites and so on.

Use contracts to keep track of deliveries, delivery borders and contracted and estimated project costs.

Share or publish projects with colleagues or participants working on any type of device - desktops, pads and phones - by saving and sharing data files to Google Drive, public or private web servers or to local network drives.

Note! - this application is in alpha phase - it may be unstable and features may be added, changed or removed depending on users feedback.

We appreciate any comments or tips to improve bimSystems. Contact information is at the end of this page.

The Engineering ToolBox bimSystems is copyrighted but can be used with NO WARRANTY or LIABILITY.

Example projects


Technical applications in projects are organized in "Systems".

Information like technical data and documents can be connected to objects on all levels.

Components can connect to "types" and inherit information, properties and documents from the types. The use of types can be very efficient if two or more components are similar.

Components can be located by connection to room.

Deliveries and costs can be connected to components through contracts. Contracted (verified) and pending (estimated not contracted) costs can be tracked during design and construction.

Outdoor systems may be implemented by adding an "outdoor" buildings.

The tag structure of systems, components and types are flexible. Commonly used structures can be adapted.


Physical areas in projects are organized in "Buildings".

Information and documents - architectural drawings, floor plans and so on - can be added to building objects on all levels.

System components can be connected to rooms. 

Areas added to rooms accumulates all the way up to site.


Contracts are used to define deliveries and delivery borders and to keep track of contracted and pending costs during design and construction of projects.

Connecting components to contract items specifies product and/or service deliveries. Note! - several contract items can be connected to a single component. This is useful where delivery and installation work connected to a component - example a pump - is in one contract, and the electrical connections of the pump is in an other.

Contracted (or verified) and pending (or assumed, not verified) costs can be used to keep track of the estimated total costs through the design and construction a project.

Contracts connects to companies.


Documents are used to connect external information from public or private web servers or local drives to objects in projects. Typical documents to connect are

Documents with url's starting with "http://.." or "https://.." can be opened directly by clicking the provided links within the application. Local files with url's starting with "file://.." can be added, but due to the browser restrictions - can not be opened directly by clicking the links. To open local files - copy the url and paste it into the adress field of an open browser window.

Be aware that access to non public urls may be restricted for other users and that urls located inside intranets - or urls that require users to be logged in to specific services - may not be available for all potential users of a project.

Documents can connect to sites, buildings, floors, rooms, systems, components, types and contracts. A document can also connect to more than one object. It may also be efficient to connect documents to "types" instead of "components".


A type is a collection of properties and documents and is used to collect information common for more than one component.

A type can be shared between many components and a component inherit the properties (definitions, not values) and the documents from the connected type. Connecting types to components makes the design more consistent and the design process more efficient.

More "fine grained" types with specific information can be made by copying generic types - like copy and modify "Fan" to "Fan, Centrifugal" or even to "Fan, Centrifugal, Manufacturer X" - and adding more specific and detailed information.


Properties are used in types and components to make the specifications more consistent throughout projects.




Google Drive


© all rights reserved -