Skip to content
  • Categories
Collapse
Solibri Society Forum
  1. Home
  2. Comments & Feedback
  3. Tech Talks
  4. Gatekeeper check

Gatekeeper check

Scheduled Pinned Locked Moved Tech Talks
5 Posts 5 Posters 1.6k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    Samb
    wrote on last edited by
    #1

    Hi guys!

    I’d like to check the following:

    If an MEP-guy requests a void with a certain object, that he didn’t forget the object at any place. i’d only like an issue where he didnt place the void. Screenshot over here

    Rule:
    -General intersection SOL/1/5.0 (Wall vs Duct) Check only failed
    – General intersection SOL/1/5.0 (Duct vs object)

    The problem i get is that the results i have are the ones where the object is located, nog the ones where they forgot the object.

    Anyone got an idea? Thanks!

    Lauri LuomaL 1 Reply Last reply
    0
    • Lauri LuomaL Offline
      Lauri LuomaL Offline
      Lauri Luoma Solibrians
      replied to Samb on last edited by
      #2

      Hey @Samb!

      This is quite tricky to check… also because a MEP object (e.g. a duct) can pass multiple walls so we don’t want the duct to pass in case it has only one void in one of the walls. I’ve tried to achieve this checking in the attached model.

      MEP voids rule test.smc

      It’s a gatekeeper of 3 rules, first rule #234 checks how many walls a certain duct is passing,
      -> check all passed components (e.g. ducts passing 1 wall).

      Next rule #222 checks that there is the same amount of voids or openings close by to the duct. (same amount as walls the duct passes)
      -> check all failed components (no opening or void found close to the duct)

      Last rule #1 will report the ducts that are clashing with walls.

      So this type of rule is made for MEP passing 1 wall, 2 walls, 3 walls… etc. Please have a look at the attached model with the example ruleset. Note that you need to define the voids in the rule to work in your own model. This might not be the perfect solution and maybe something that the Rules API could tackle. But with the existing rules this might be the solution?

      1 Reply Last reply
      1
      • Daniel D.D Offline
        Daniel D.D Offline
        Daniel D.
        wrote on last edited by
        #3

        Hey Samb,

        you could continue using your rule by adding a third rule:

        -General intersection SOL/1/5.0 (Wall vs Duct) Check only failed
        – General intersection SOL/1/5.0 (Duct vs object) Check only passed
        —General intersection SOL/1/5.0 (Wall vs Duct)

        the first rule checks for intersections of walls and ducts
        (go on with ducts that collide with walls)
        the second rule checks for intersections between ducts and provisions for voids
        (go on with ducts that do NOT colide)
        the third rule checks for intersections between walls and ducts again

        as a result you should get the ducts that collide with walls without a provision for void…
        I hope it works for you,

        cheers, Daniel

        N L 2 Replies Last reply
        0
        • N Offline
          N Offline
          naveedzargar
          replied to Daniel D. on last edited by
          #4

          @daniel-d Hi Daniel, can you share the rule-set, as mine following the steps is not creating the desired results. Thanks

          1 Reply Last reply
          0
          • L Offline
            L Offline
            LindaFernstrom
            replied to Daniel D. on last edited by
            #5

            @daniel-d Could you please share the ruleset, thanks

            1 Reply Last reply
            0

            Copyright © 2025 Solibri Inc. | Powered by NodeBB

            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories