FM-9 Portfolio and Asset Management - Performance Requirements (PAMPeR)
by
Juha Hyvarinen
—
last modified
Mar 06, 2011 08:41 PM
| Business needs: | ||||||||||||||||||||||||||||||||||||||||||||
|
Owners, managers and users of real property need to correlate
information about what is required, what has been approved, and what is
actually in place. For businesses, governments and other institutions
that occupy buildings to achieve their business purposes, they need to
correlate this information to ensure that business objectives are met,
and to achieve compliance with decisions already taken. Owners and
managers of buildings currently maintain information about their
portfolios of real property in various incompatible data formats.
Categories of information include, as a few examples, functional
performance requirements of occupant business units, financial
performance requirements as expressed in approved budgets, and
operational performance as expressed by individual users and customers.
In consequence of the lack of connectability between units of
information, managing compliance is typically incomplete or is
accomplished inefficiently by human inspection of the facilities or of
printouts of records about them. For instance, linking information
about a requirement for freedom from glare, information about a source
of illuminance, and information about the overall functionality of a
workplace in the data base of an occupant organization can now only be
done by manual translation of the data by a person.
Standards are being developed for consistent definitions of concepts and information objects, for use among owners, managers and occupants of buildings. For instance, ASTM has developed standards for whole buildings and facilities (Subcommittee E06.25), and for building economics (Subcommittee E06.81) and ISO is developing standards for user functional requirements and serviceability (TC 59/SC 3/WG 14) and measurement and prediction of service life (TC 59/SC 14). Therefore, it is becoming practicable to develop the deliverables proposed above. Features and benefits in summary: Owners, managers and users of real property will be enabled to correlate information about what performance is required, what has been approved, and what is actually in place in their facilities throughout their lifecycles. |
||||||||||||||||||||||||||||||||||||||||||||
|
Solution: |
||||||||||||||||||||||||||||||||||||||||||||
|
It is anticipated that this project will relate to schema at the
interoperability and domain layers of the IFC model generally and may
contribute additional requirements at the resource layer, particularly
in terms of the separation of requirements and deliverables at the
IfcPropertyResource schema. In terms of the capital projects planning aspect of this work, there will be a relationship to the IfcProcessExtension schema and it is probable that this schema will be generalized to a "schedule representation" in a manner similar to that adopted for cost and environmental impact representation if IFC 2x2. Because of the need to capture both requirements and performance data to enable comparison between what is expected and what is delivered, it is also considered that the project will contribute to extension of the "history capture" concepts initiated within the BS8 project for IFC 2x2 and, through this extension and formalization, will contribute extensively to the planning of the information architecture for future IFC model versions. |
||||||||||||||||||||||||||||||||||||||||||||
|
Scope of work: |
||||||||||||||||||||||||||||||||||||||||||||
|
In Scope: |
||||||||||||||||||||||||||||||||||||||||||||
Define the performance requirements and planning of capital projects or
improvements that meet the needs of the owner and/or users.
In the attached diagram, the scope includes information in the column at left, titled the Demand domain. |
||||||||||||||||||||||||||||||||||||||||||||
|
Out-of scope: |
||||||||||||||||||||||||||||||||||||||||||||
| Information in the diagram, in the center column, titled Project Delivery domain, and in the right column, titled Facilities In Use domain. | ||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||
| Project addresses | ||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||
| Remarks | ||||||||||||||||||||||||||||||||||||||||||||
| THIS PROJECT HAS BEEN INTEGRATED INTO IFC2x2 addendum 1 (Release July 2004) | ||||||||||||||||||||||||||||||||||||||||||||
Database listing all IFC capable applications launched
