Use cases

There are two types of use cases which need to be defined in the BLIS project

1. Software use cases
2. Interoperability use cases

The software use cases describe the functionality inside a software product which is needed by the end user of the software to perform certain tasks in their daily practice. These use cases should focus on areas which are enabled by data exchange with other software products.

The interoperability use cases describe how the software use cases can be enabled using IFCs. These use cases should contain a definition of the data which should be exchanged between software products. In practice this will be a list of IFC R2.0 objects and attributes which need to be supported to enable the desired data exchange. In addition these use cases may contain definitions about how the data should be structured and exchanged.

Possible interoperability use cases could be

• Arch. design ß à Cost estimating
• Arch. design ß à Scheduling
• Cost Estimating ß à Scheduling
• Arch. design ß à HVAC load calculations
• Arch. design ß à HVAC system design
• Arch/HVAC design ß à Energy code checking

The goal of the BLIS project is to find at least 4 partners to support an interoperability use case, two on each side of the data exchange. If you want to actively participate in a use case or you want to define a new use case, please contact Richard See or Jiri Hietanen.