The initials objectives for this use case were to:

  • transpose buildingSMART’s “BIM Uses” into French and establish the scope of each use case;
  • obtain the specifications for the functions or systems taken into account in each use case, and in consequence those of their constituent objects (geometry and attributes);
  • establish the interfaces/impacts between the systems (links between systems and objects);
  • configure existing tools (such as IDM (Information Delivery Manual) V2.0).

These objectives were clarified and completed by the UC1 working group with a view to:

  • making relevant proposals for developing BIM execution plans;
  • highlighting the differences between and complementary elements of the overall project (general BIM uses) and its component structures (specialised BIM uses);
  • adapting the lifecycle phases to the specific nature of infrastructures;
  • taking into account the concepts of systems engineering in the analysis of infrastructure organisation;
  • incorporating the principles and methods of requirements management;
  • orienting the conclusions of the discussion towards the following targets: standardisation bodies, other MINnD working groups, BIM end users and software publishers.

The deliverable proposes principles for structuring and then managing the information regarding an infrastructure:

  • By system: to do this, systems engineering provides a rigorous method with an approach along three lines:
    • an architectural line with three successive views: the operational view (needs), the functional view (requirements) and the organic view (components);
    • a line of progression in terms of complexity (from design of the components to the uses to which they are put);
    • a line of progression in terms of maturity and integration (from the concepts to the assembly of validated components).
  • By object: the infrastructure is composed of physical objects. The principle is to geolocate these objects, establish their volume and attach the information to the objects it concerns. This allows:
    rezultate liga 1 romania clasament liga 1 romania
    • all actors to view an object, a group of objects, a structure or the overall infrastructure;
    • the creation of views adapted to uses (by actor, by system, etc.);
    • sorting based on the location of the information.
  • By lifecycle phase: at a global level, the lifecycle must show the main phases of assembly, design, production and operation. The working group has shown that the lifecycle should be divided as follows:
    • into a global lifecycle with general tasks that cannot be split up and dealt with separately for the specific structures;
    • into as many lifecycles as are required by the subdivision of the product into specific structures (civil work structures, earthworks, operating systems, etc.).

At a more basic level, a V lifecycle must be set up to manage the maturity of the systems and objects.

  • By actor: the number and diversity of actors involved in an infrastructure means it is absolutely necessary to structure the panel of these actors: direct actors, indirect actors, influencing actors and stakeholders. In addition, the deliverable summarises the founding principles of the following two methods analysed by the working group, several elements of which have been reproduced above:
    • systems engineering;
    • requirements management.

Finally, the deliverable provides a glossary of the terms used, which should be incorporated into the general MINnD glossary.