Meetings · Models
A model coordination meeting is useful when it starts from the clashes that are still open and ends with a name and a date against each one. This page gives a working agenda for that meeting and shows how to run it in Fidrel: the clash check, the meeting record, the items with their owners and the carry-over to the next meeting.
30 days free · No long-term contract.
A check across architecture, structure and services can list hundreds of clashes, and walking through them in order burns the hour. Most are the same few problems repeated, and the meeting needs the ones that block work.
A clash gets looked at, agreed to be a problem and left. Two weeks later it is still in the model, because the meeting never recorded who would change what and by when.
A line saying the duct and the beam conflict on level 3 means little to someone opening the minutes later. Without the view, the camera and the objects, the reader starts the search again.
A running order that works for most coordination meetings: first, which model versions are in the federated view, so everyone is talking about the same version of each model; second, the items carried over from last time, each with its owner and due date; third, the new clashes, grouped by the trade that has to move; fourth, decisions that affect several trades; and last, who exports the next clash report and when. Put the heaviest group first, because attendance and attention are highest at the start.
Meetings & decisions
An NCR made from a clash keeps the camera, the selection and the section with it, and Show in 3D reopens that view. Meetings, items and decisions are numbered MTG, ITM and DEC, so a line in the minutes can be cited by number. Every record also has a change log that shows, field by field, who changed what and when, which settles most arguments about what was agreed.
Step 1
Open the models together with Federated model, choose Clash detection, pick what to check against what, set the Tolerance (mm) and press Run check. Export report (CSV) before you change anything, because new criteria clear the old results.
Step 2
Under Meetings choose New meeting, set the Meeting type to Coordination meeting, and fill in date, location, the online meeting link, Participants, Chair and Note taker. Status starts as draft and moves to scheduled.
Step 3
Open a clash in the list and press Create deviation. A short form asks for a title, a description and a Responsible person, and the record created is an NCR. It carries the view with it, so the next person opens the model where you were.
Step 4
Add an agenda item for each group of clashes, with a Responsible person and a Due date. Attach the clash report, and link each NCR to its item with Add relationship, so the item shows what is being fixed.
Step 5
Mark the meeting Held. Close the items that are done, and bring open ones into the next meeting with Add existing agenda item so nothing is retyped. If the group decides something, use Register as decision.
A person who is made responsible for an item gets a notification in Fidrel, and the item stays under Assigned to me on their Home page until it is closed. An item has the statuses open, in progress and closed, so a status check at the next meeting is a look at the list rather than a round of questions.
Fidrel does not run the meeting or assign clashes to people automatically; someone chooses which clashes to raise and who owns them. The agenda is a field in the meeting record that you write yourself, and Fidrel applies no standard or plan to it. A test runs when you ask for it, not by itself when a new version is uploaded.
Your trial applies to your first own project and starts when that project is created. No card required. Afterwards, choose card or invoice to continue.
The project system of the future connects people, documents and decisions. Discover the thinking behind Fidrel.
Read more
On site, answers need to be close at hand. Fidrel displays DWG drawings in your mobile browser, within the project’s document structure.
Read more
When everyone can see the next step, moving the project forward becomes easier. Fidrel brings activities, dates and reported progress together in a shared Gantt view.
Read moreMeetings · Models
Anything else on your mind? We are happy to help.
Talk to usThe model versions under review, items carried over with owners and due dates, the new clashes grouped by trade, any decisions that affect several trades, and who exports the next report and when.
Run Clash detection on the federated model and use Export report (CSV) to circulate it beforehand. In the meeting, open a clash and use Create deviation to turn it into an NCR with a responsible person.
Every NCR and every agenda item has a Responsible person and a due date. The person is notified in Fidrel, and the item shows under Assigned to me until it is closed.
Yes. In the next meeting use Add existing agenda item to bring an open item forward. It keeps its number, owner and history instead of being retyped.
No. You or the note taker write them in the meeting record. Fidrel keeps the participants, the items, the decisions and a change log beside them, and the NCRs link back to the model view.
