___________ER_EXAMPLE1 Exchange_Service_Life (Estimated)

Overview

Scope

The scope of this exchange requirement is to enable the exchange of information about the Estimated Service Life of a type or occurrence of an element or product.

General Description

Estimated Service Life (ESL) is the service life that a product or parts of a product would be expected to have in a set of specific in use conditions calculated by adjusting the reference in use conditions in terms of materials, design, environment, use and maintenance.

In ISO 15686-1:2000, the concept of Reference Service Life (RSL) is defined as the 'service life that a building or parts of a building would expect or is predicted to have in a certain set of reference in-use performances'.

A person working with the service life planning (SLP) of a product is faced with the problem of forecasting the service life of its components. Even if there are certain service life data available, i.e. RSLs, these can rarely be used directly. This is because the project-specific in-use conditions, to which the product and its constituent components will be subjected, are usually different from those under which the service life data are valid, i.e. the reference in-use conditions.

In ISO 15686-8:2008, the Factor method is described as a means to overcome this problem. The factor classes are defined as:

A quality of components
B design level
C work execution level
D indoor environment
E outdoor environment
F usage conditions
G maintenance level

The evaluation of an ESL according to the Factor method requires the input of an RSL as well as the numbers of the Factor classes A to G. A proper choice of the numbers of the factors will depend on the difference between the project-specific and the reference in-use conditions. Therefore, in order to enable estimations of the Factor classes A to G jointly with RSL, the reference in-use conditions in terms of the factor classes should, as far as possible, be included when providing data.

The Factor method is used to modify an RSL to obtain an estimated service life (ESL) of an element or product, while considering the difference between the project-specific and the reference in-use conditions. This is carried out by multiplying the RSL by a number of factors, each of which reflect the difference between the two sets of in-use conditions within a particular factor class:

ESL = RSL * Factor A * Factor B * Factor C * Factor D * Factor E * Factor F * Factor G.

However, the factors themselves may be subject to variation from a normal condition due to the specific reference conditions adopted and object in-use conditions. Whilst these can be absorbed into the factor equation above, it is easier to see their impact as a set of parameters P acting on the factors F as below:

ESL = RSL * (Fa * Pa) * (Fb * Pb) * (Fc * Pc) * (Fd * Pd) * (Fe * Pe) * (Ff * Pf) ** (Fg * Pg)

where:

Fn represents each of the service life factors that can be applied
Pn represents the combination of reference in use parameters and object specific in use parameters that is applied to the factor.

As with Design Life and Reference Service Life, Estimated Service Life also has 'optimistic' and 'pessimistic' values that can be determined by the following equation:

DeltaESL = ESL * sqrt ( (DeltaRSL/RSL)^2 + (DeltaA/A)^2 + (DeltaB/B)^2 + (DeltaC/C)^2 + (DeltaD/D)^2 + (DeltaE/E)^2 + (DeltaF/F)^2 + (DeltaG/G)^2 )

Note that, according to ISO 15686-8:2007, in use parameters that have no effect on service life can be omitted from this equation.

The ESL of a product is expected to be able to be determined using factor information derived from an externmal data source or library. Typically, such a data source is expected to be maintained by an insurance company or related organization, a national centre dealing with service life issues (e.g. a national research centre), a trade association, an information broker or similar. It may also be available directly from a product manufacturer.

For a given product, the reference service life is determined for a set of 'in use' conditions and must be modified through the application of the factors as described above. Whilst the factor definitions are consistent across products, the parameters that determine the factors can vary according to the type of product and are also expected to vary according to locality (country/region etc. The determination of the in use condition as and their impact on service life may be determined by a 'grid' or matrix of possibilities similar to that defined for the French 'Reference Service Life Platform' ('Duree de Vie de Batiment)

It is not within the scope of this exchange requirement to set down the precise components of individual product grids. However, it is anticipated that these may be specified by local exchange requirements.

Information Description

Information required concerning the external library reference includes:

Name of the library
Publisher or authority responsible for making it available
Version number or reference
Date on which the version referenced became effective
Address or location of the library e.g. as a web address

The elements or products for which Estimated Service Life data is required need to be identified.

For each of the service life factors (A-G)`

Assessment of its object specific in use condition (as defined in table C.3 of ISO 15686-8:2008); this will be a selection of Poor/ Normal/ Good in each case

The term object specific relates to the use of an occurrence or designated grouping of occurrences of the product (e.g. all windows of type X located in the North facing wall above the 5th storey of the building)

Assessment of its reference in use condition (as defined in table C.3 of ISO 15686-8:2008); this will be a selection of Poor/ Normal/ Good in each case

The term reference relates to the difference in expected use of the product between the initial manufacturer/supplier test conditions and the conditions that are expected to apply to the use of the product (e.g. windows of type X are manufactured and tested in Nottingham, an inland city with a relatively mild set of climatic conditions whilst the intended use of the windows is in Blackpool, a coastal city subject to Atlantic gales and heavy sea spray that will reduce the estimated service life from the reference value)

The value of the factor determined by adjusting the base factor value by the modifying in use conditions factor values (see table C.4 in ISO 15686-8:2008)
The calculated value for the Estimated Service Life according to the formula given in section C.3 of ISO 15686-8:2008 and described above
The calculated values of optimistic and pessimistic Estimated Service Life as shown in section C.3 of ISO 15686-8:2008 and described above
The date on which the product was set into use for the purpose of calculating estimated service life.
Assessment of data quality (based on the level of trust given to methods and procedures used in the acquisition and compilation of the data) and rated as Poor, Good or Excellent
Assessment of data reliability (based on the level of trust given to validation or testing authorities quoted for the data) and rated as Poor, Good or Excellent

Coordinated design and procurement, Production information, Construction mandatory ER_EXAMPLE1 exchange_requirement ___________UR_EXAMPLE1 Preconditions

To enable the estimated service life to be assessed, the building model as constructed must be available. This must include the specific product occurrences as well as the type.

mandatory UR_EXAMPLE1 user_requirement ___________UR_EXAMPLE2 Select Objects

Idea

Explanation

Select Objects

Select the objects that are to have the service life assigned.

For Estimated Service Life, the object(s) selected will be occurrences of products of a particular type. Occurrences will be collected into groups for easier referencing.

Since the physical objects exist (by design), they already have globally unique identity and owner history.

Physical objects may have a name whose provision is required by other exchange requirements. It is not a specific need for service life planning and therefore, the name attribute of physical objects should not be changed through this exchange requirement.

Physical objects may have a description whose provision is required by other exchange requirements. It is not a specific need for service life planning and therefore, the description attribute of physical objects should not be changed through this exchange requirement.

mandatory UR_EXAMPLE2 user_requirement ___________UR_EXAMPLE3 Assign To Group

*Idea*	*Explanation*
Set Group	Set the physical object group to which the objects are to be assigned The group must be assigned a globally unique identifier which should be handled directly by software. It should also have an owner history that, minimally ,defines the date of creation, the date of last modification, last modifying user and responsible software application.
Name	Provide a familiar name for the group by which it may be further identified. The name of the group must be provided so that the group can be identified. For instance, a group named NorthWindows may collect together all windows of a certain type that have been placed in openings in a north facing wall.
Description	Provide a description for the group The description of the group should be provided to amplify the name. For example, the group named NorthWindows may have the description - Single side opening triple glazed windows in north facing walls - .
Grouping	Assign the selected objects to the set group The assignment to the group must be assigned a globally unique identifier which should be handled directly by software. It should also have an owner history that, minimally, defines the date of creation, the date of last modification, last modifying user and responsible software application. The name and description attributes of the assignment relationship do not need to be asserted for this group assignment.

mandatory UR_EXAMPLE3 user_requirement ___________UR_EXAMPLE4 Associate Library (Library Reference)

Reference to an external data source from which service life information is obtained

*Idea*	*Explanation*
Location	Set the location of the library Location is the URI/URL/URN at which the external data source or library is found. The library location must be asserted when the library is referenced
Item Reference	Set the item reference This is an identifier or pointer to the relevant item with the external data source or library and must be asserted so that the particular data item is identifiable. Typically, this may be seen as an extension to the URI/URL/URN address specifying location.
Name	Provide a name for the library reference This is for human reading purposes and does not have to be asserted.
Language	State the language of the library reference This is the language used by the library reference and must be asserted. Note that language names used should be drawn from ISO standard naming when possible.
Referenced Library	Provides a pointer to the general identifying data about the library. It is not a strict requirement that this information is provided but it is strongly recommended that it should be.

mandatory UR_EXAMPLE4 user_requirement ___________UR_EXAMPLE5 Associate Library (Library Information)

Idea

Explanation

Name

Set the name used to identify the library

The name of the library must be asserted

Version

Set the identifier or version number of the library used

Not a mandatory attribute but recommended that it should be asserted.

Publisher

Set the organization that publishes the library

Publication Date

Set the publication date of the version of the library used

Publication Location

Set the location of the library publication

Location is the URI/URL/URN at which the external data source or library is found.

Note that the publication location attribute need not be asserted when library reference is used since the external reference location fulfils the same purpose.

mandatory UR_EXAMPLE5 user_requirement ___________UR_EXAMPLE6 Associate Library (Library Association)

Idea

Explanation

Associate Library Reference

Make an association between the objects that are to have a Reference Service Life and the library from which the Reference Service Life data is obtained

The association of objects to library must be assigned a globally unique identifier which should be handled directly by software. It should also have an owner history that, minimally, defines the date of creation, the date of last modification, last modifying user and responsible software application.

The name and description attributes of the association relationship do not need to be asserted.

mandatory UR_EXAMPLE6 user_requirement ___________UR_EXAMPLE7 Set Service Life (Estimated, Service Life Factor)

There are seven different service life factors that can be determined named A-G according to ISO 15686-8:2008. The setting of the value for each service life factor follows the same procedure as below:

*Idea*	*Explanation*
Factor Type	Select the predefined type of service life factor that is to be set. The service life factor type must be asserted. The predefined types of service life factor that are typically used are those defined in ISO 15686 and include: QUALITYOFCOMPONENTS DESIGNLEVEL WORKEXECUTIONLEVEL INDOORENVIRONMENT OUTDOORENVIRONMENT INUSECONDITIONS MAINTENANCELEVEL
Object Specific In-Use Condition	Assess the object specific in use condition for the selected objects or object group Values for object specific in use condition are as defined in table C.3 of ISO 15686-8:2008 This will be a selection of poor/normal/good in each case
Reference In-Use Condition	Assess the reference in use condition for the selected objects or object group Values reference in use condition are as defined in table C.3 of ISO 15686-8:2008 This will be a selection of poor/normal/good in each case
Factor Value	Set the value of the factor This value must be asserted. The value of the factor is determined by adjusting the base factor value by the modifying in use conditions factor values (see table C.4 in ISO 15686-8:2008)

mandatory UR_EXAMPLE7 user_requirement ___________UR_EXAMPLE8 Set Service Life (Estimated, Service Life)

Sets the value to the Estimated Service Life of a type object/type product or an object occurrence.

*Idea*	*Explanation*
Select Objects	The identification of the physical objects that are to carry service life information has already been carried out as part of the Object Selection process above.
Estimated Service Life	Set a value for Estimated Service Life, Optimistic Estimated Service Life and Pessimistic Estimated Service Life. Estimated Service Life values are calculated according to formulae given in section C.3 of ISO 15686-8:2008 and described above Estimated Service Life, Optimistic Estimated Service Life and Pessimistic Estimated Service Life must be asserted in the context of this exchange requirement. Refer to ISO 15686-8:2008 for further information on methodology for determining Estimated Service Life values.
Set Date	Set the date on which an object or objects were set into use for the purpose of determining Estimated Service Life. Only the date time value is required for a service life assessment (since the time periods expected are sufficiently long that smaller units of time can be safely ignored).
Data Quality	Assess the quality of the Estimated Service Life data provided. Assessment of data quality should be based on the level of trust given to methods and procedures used in the acquisition and compilation of the data. The value will be either Poor, Normal or Good
Data Reliability	Assess the reliability of the Estimated Service Life data provided. Assessment of data reliability should be based on the level of trust given to validation or testing authorities quoted for the data. The value will be either Poor, Normal or Good
Define Service Life Factors	Bring together service life factors into a property set and define them for as a set for a single occurrence of service life The definition of service life factors as properties within a service life must be assigned a globally unique identifier which should be handled directly by software. It should also have an owner history that, minimally, defines the date of creation, the date of last modification, last modifying user and responsible software application. The name and description attributes of the definition relationship do not need to be asserted.
Assign Service Life	Assign the Estimated Service Life to the selected objects The assignment of Estimated Service Life properties for objects must be assigned a globally unique identifier which should be handled directly by software. It should also have an owner history that, minimally, defines the date of creation, the date of last modification, last modifying user and responsible software application. The name and description attributes of the assignment relationship do not need to be asserted.

mandatory UR_EXAMPLE8 user_requirement ______________REL_NST1 Task aggregation 1 Task aggregation 1 0.01 IDM TEMPLATE IDM TEMPLATE nochange 10 10 2008 12 30 0 0.1 Created 0.01 IDM TEMPLATE IDM TEMPLATE modified 07 11 2008 15 0 0 0.2 Added AUTHOR1 AEC3 Ltd Author1 userdefined IDM IDM author AUTHOR1@AUTHOR1.com Wix Jeffrey