MVD Internationalization

As the international standard-based Industry Foundation Class (IFC)(ISO/PAS 16739) data model is used increasingly around the world many specific business problems that would benefit from the direct exchange of data are identified.  The user/business requirements for such a data exchange are defined in an Information Delivery Manual (IDM). A solution that meets those requirements, through the use of software, is defined in a Model View Definition (MVD).  Software vendors implement support for one or more specific MVDs in their software applications.  Only after such implementations are completed and delivered to the building industry, can end-users use the data exchange defined in the IDM in their businesses.

buildingSmart International(bSI) strongly encourages MVD developers to initiate and conduct their efforts as bSI Aquariums or IFC extension projects (i.e. as official bSI projects). Alternatively, many projects that define IDMs and MVDs have been started in the past few years in regional contexts.  International software vendors are becoming concerned that they will be asked to implement support for different MVDs in different geographies.

Some are looking to bSI to coordinate and harmonize these IDMs/MVDs internationally.  A process for such internationalization under the bSI logo, is described below.

Background

a)    IDMs document end-user data exchange requirements in support of a specific business (end user) process. When complete, an IDM documents a complete definition of end user requirements – in the words of the end user.

b)    MVDs are produced by mapping concepts in the IDM to Concepts that can be implemented in software data exchange.  For each such concept, the MVD defines the data representation (using IFC) that will be exchanged between two software applications.  Thereby each MVD Concept provides unambiguous implementation guidance to software vendors, such that implementations by different vendors will be interoperable.  MVDs also provide the basis for testing those implementations for compliance.

c)    MVDs define the subset of the IFC-data model that is necessary to support the specific data exchange requirements defined in one or more IDM.

d)    bSI-MVD coordination is proposed to harmonize similar MVDs developed by different project teams – for the same or similar end user exchange scenarios.  The opportunity for bSI, in such harmonization and internationalization, is to evolve the IFC model in response to demonstrated industry needs.

Internationalization of MVD

a)    The current MVD website (www.blis-project.org/IAI-MVD/) is offered as a resource to assist the entire AEC/buildingSmart community in defining IDMs and MVDs for their business needs. bSI encourages its use without encumbrances. The IP and copyrights (IP&C) of MVD Diagrams belong to the MVD development project teams.

b)    bSI will recommend to MVD development project teams, that they invite bSI members to participate in their projects at an early stage.  Additionally, bSI will suggest that these MVD development teams consider contributing their MVD IP&C rights to bSI to consider for internationalization and harmonization with other, similar MVDs – and ultimately to augment these MVDs to be bSI MVDs.

c)    bSI MVDs are published on the official buildingSMART technical website, currently buildingsmart-tech.org.

d)    Development versions of bSI MVDs may also be published on the current MVD web site.  The site may also contain other MVD’s developed outside of bSI and will explain for each such MVD the scope of the intended data exchange standard.

e)    Proposals to develop bSI MVDs shall comply with the same requirements and consensus process as extension projects; at least three bS chapters (or alliances) supporting the project and two or more software vendors committed to implement it. Proposals having fewer supporting chapters will be deemed regional MVD’s and will not automatically be considered in evolving the IFC model.

f)    The purpose of bSI MVD development projects is to allow for international review by all interested parties and augmentation of MVDs with regional origins to make them internationally applicable. Additionally, MVDs intended to support the same/similar end-user exchange scenarios must be coordinated and harmonized.

g)    bSI MVD development projects could be organized as self-funded Aquariums projects, or as self-funded extension projects. Project will be advised to make a budget allowance for bSI’s coordination of the international review and consensus process. Beyond that, MVD coordinator activities related to a specific project shall be funded by the project.

h)    MVD Coordination is a responsibility of the Model Support Group (MSG) and is overseen by ITM.

i)    The specification of bSI MVDs uses a prescribed format, as defined by the MVD coordinator, reviewed by the Implementation Support Group (ISG) and approved by the International Technical Management (ITM) committee.

j)    The MVD Coordinator will lead bSI MVD coordination and has both the authority and responsibility to drive harmonization and consistency across various bSI MVD development projects.  This coordination shall include: consistent use of the IFC model, consistent use of MVD Concepts, and coordinated use of implementation agreements.

k)    As with all MVD development teams, bSI will fund a pro rata share of the overhead for maintaining the MVD website.

l)    MVDs may only become bSI MVDs after the IP&C are assigned to bSI (through a release signed by the original development team) and approved by the ITM.  It should be noted that implementation guidance for Concepts are shared across all MVDs (not just BSI MVDs) and therefore are not owned by any one organization, but by the community of MVD development project teams.