A software developer, who decides to start IFC-implementation, usually has to go through the following tasks:

• Understand the technical background
• Very helpful is the website of the so called MSG (Model Support Group), which is the group actually developping and maintaining the IFC-data schema:
  http://msg.buildingsmart.com
• Specifications of IFC releases can be found there as well
• Decission on which IFC-release to implement.
• If you have no experiences in implementing interfaces to product models, such as IFC- or STEP-models the usage of a toolbox will be very helpful. 
• Toolboxes provide a C or C++ interface, which makes implementation of IFC-support much easier. 
• For each IFC release there are one or more definitions of so called "View Definitions". They describe a subset of the IFC model, which is implemented by specific application types in order to support information exchange in planning, construction and facility management processes. If none of the existing View Defintions is appropriate for you, get in contact with ISG-coordinator, so that a new view can be set-up.
• Also look for implementer guidelines, which are containing important information on how to use the model for software implementation
• For questions send an e-mail to the implementer's e-mail-list or start a discussion on the discussion forum in the ISG-Groove space  space. The modelling experts are also on the e-mail-list and can provide help in understanding the model. Every IAI-member can get an invitation to the ISG-Groove space by the ISG-coodinator.
• After the first results of your implementation, start to exchange example-files with others, ideally in the ISG-Groove space.
• As soon as your implementation is robust, you may want to pass certification. Send a request for certification at least 3 months in advance of the required date to ISG-coordinator, so that he can set up a certification workshop.
• Important documents which every implementer should take into consideration:
  • IFC-model specification
  • Implementer Guidelines
  • Implementer Agreements
  • View Definitions