# In general: where are requirements mapped in the IFC?

**URL:** <https://forums.buildingsmart.org/t/in-general-where-are-requirements-mapped-in-the-ifc/2413>\
**Category:** Users\
**Created:** [February 17, 2020, 1:24pm UTC](https://forums.buildingsmart.org/t/in-general-where-are-requirements-mapped-in-the-ifc/2413 "2020-02-17T13:24:45Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![tsolsen](https://avatars.discourse-cdn.com/v4/letter/t/e56c9b/32.png) [@tsolsen](https://forums.buildingsmart.org/u/tsolsen)\
**Post date:** [February 28, 2020, 7:22am UTC](https://forums.buildingsmart.org/t/in-general-where-are-requirements-mapped-in-the-ifc/2413/28 "2020-02-28T07:22:49Z")

</div>

If I may give a suggestion to the OP, until a solution is found within BS.

Prefix Pset, is according to your need, switched to something like:  
_Req\__ for Required  
_AsB\__ for As Built (if you need to document it, otherwise I’d leave it).  
_Add\__ for anything extra you may add, outside of established Psets by BS, Client, x.

Add _Req_ and _AsB_ as suffix to parameters, where they have a equivalent BS \*Common one.

_Req\_DoorCommon - FireRatingReq_  
_AsB\_DoorCommon - FireRatingAsB_  
_Add\_DoorCommon - HasFunctionX_

This is how I recommend it in Denmark, and similar syntax for requirements, is widely used in Norway.  
While not perfect, it’s functional today. And naturally, many other methods could be used, nor problem. Just make sure that you document the one you pick.

---

_[View the full topic](https://forums.buildingsmart.org/t/in-general-where-are-requirements-mapped-in-the-ifc/2413)._
