What does the iDN12 System Do? iDN12 is a Cloud Based Building Information Management System Space relative to Buildings, Floors and Spaces - spaces include rooms and workstations. Part of tracking space includes areas relative to BOMA standards including Vertical Penetrations, Building Common, Floor Common and Mezzanine areas. There is a direct relationship between space management and CAD drawings whereby all areas for Floors, Spaces, Vertical Penetrations, Common areas and Mezzanines are represented as polylines in the drawing. To address larger scale facilities, additional functionality has been added for tracking Properties including complexes, sites and campuses and the tracking of multiple buildings associated to a single property. This can include performing BOMA calculations for common areas directly related to properties. Tracking of space also includes performing BOMA calculations relative to space (R/U ratios) and area roll-up and chargeback calculations to the organizational hierarchy.
These areas provide the ability to specify offices and I or workstations within a space. This type of space is used where multiple organizational units use sub-spaces within a space. Sub-spaces can be represented as a polylined area in CAD or as a database entry only. Typical users of sub-spaces would include school boards, universities, health-care facilities or corporate clients who have areas shared by multiple departments. Parking:Not a common requirement but this capability provides links to parking spaces. This can be based on a polyline on a site plan drawing or as database records only, associations to parking should be made to either part of the organizational hierarchy or to a person.
• Buildings by Property including optional BOMA related calculations • Floors by Building • Spaces by Floor & Building • Sub-spaces by Space • BOMA Space Report • Spaces I Sub-spaces by Type • Common Areas by Floor & Building Track Organizational Information Organizational information is structured to associate space, assets and personnel information. The system has the ability to track all levels of a client’s organizational hierarchy without customization (single level or multi-level organizational hierarchy). The relationship between CAD and organizational information can be made by association to spaces & sub-spaces (polylines) or via an organizational polyline defining an area where polylined spaces have not been defined. Typical Organizational Reporting Requirements Over and above reports that show information on individual organizational table, the following relational reports have been created: •Space & Sub-space by Organizational hierarchy (including chargeback calculations) Personnel information is tracked specifically for relationship to space, assets, moves and work requests. Typically the association is made in the database and there is no requirement for a connection to CAD. Personnel information often comes from an outside source such as an HR system offering the ability to import this information on an on-going basis without disturbing connections to assets or organizational information. Personnel Reporting Requirement Over and above reports that show information on individual personnel table, the following relational reports would need to be created:
Track Work Requests On demand work requests are more commonly used in typical facility management requirements than preventative maintenance systems which require extensive documentation and scheduling input prior to being functional. Work request functionality is typically database only with associations to space, personnel, assets and organizational information; based on these associations CAD information can be used as part of work requests but is not typical. A bar code option is in place to improve work flows. Typical Work Request Reporting Requirements Over and above reports that show information on individual work request tables, the following relational reports would need to be created: • Work Requests by Location (Buildings & Floors) • Work Requests by Personnel• Work Requests by Organizational Hierarchy • Work Requests by Date (prompted date range) • Open Work Requests • Closed Work Requests Track Assets Assets
represent virtually anything in a facility including equipment,
computers and furniture. Assets have the ability to be associated to any
level of the space hierarchy (properties, buildings, floors, spaces and
sub-spaces) and be represented as either a database record or as an
entity in CAD (block or polyline). Small items such as fire pulls,
extinguishers and door fire ratings can be highlighted as a “Halo” for
easy visibility. A bar code option is in place to tag assets if
required. Over and above reports that show information on individual asset tables, the following relational reports have been created: • Assets by Type Use • Assets by Location (Buildings, Floors, Spaces & Sub-spaces) • Assets by Personnel • Assets by Organization Track Leases Lease management functionality provides the ability to associate leases to spaces and assets with similar capabilities for tracking expiry dates, tickler notifications, costs and in the case of assets, the physical location. Leases can have a direct relationship to CAD via polylines representing suites, or by association to assets represented as entities in drawings. Leased areas related to polylines in CAD also offer the ability to manually enter the actual lease area instead of taking the area directly from the suite polyline. All lease information has the ability to be created as database records only.
• Suites & Leases by Location (Buildings & Floors) • Suites by Lease • Leases by Tenant • Leases by Expiry Date (prompted date range) • Assets by Lease |
|
|
iDN12 |