Enhanced in v9.6: Accessible Door Rule – SOL/208

The just released version (9.6) of Solibri Model Checker (SMC) includes significant enhancements to the Accessible Door Rule – SOL/208.  The following article describes those enhancements in more detail.  The example model, ruleset, and classifications used in this article can be downloaded from the link below:

SMC Building V9.6 Door Maneuvering Clearances.zip

Prior to this release, door maneuvering requirements were limited to a single free area in front of the push side of the door (free door back side), and a single latch side area on the pull side of a door (Free Door Side).  Also, the width of the free area in front of the pull side (Free Door Front Side) and push side (Free Door Back Side) had to be entered rather than being based on the actual width of the door:

Front Approach, Pull Side Maneuvering Clearance Check in SMC v9.5

In version 9.6, now both the latch (handle) and hinge sides of a door can be checked for a free area on both the pull and push sides of the door.   Also, the width of the area in front of the pull side and push side of the door can be determined by the actual width of the door rather than a specified dimension:

Front Approach, Pull Side Maneuvering Clearance Check in SMC v9.6

Above we see a check for maneuvering clearances for a front approach on the pull side of a door based on the requirements found in the ADA standards as issued by the Department of Justice (DOJ):

404.2.4 Maneuvering Clearances.

This rule ensures that single swing doors have a maneuvering space that extends 18 inches (455 mm) minimum beyond the latch side of the door and 60 inches (1525 mm) minimum perpendicular to the doorway for a front approach on the pull side.

Using Self-Configuring (Gatekeeper) Rules to Check Maneuvering Clearances Based on Approach.

The maneuvering clearance requirements for accessibility of a door depend on the approach (front, hinge, or latch) and whether the door is equipped with a closer and latch.  The Accessible Door Rule – SOL/208 does not have a component filter table to check specific door types; however, you are able to pass specific doors to the rule through self-configuring (gatekeeper) rules.   A detailed explanation of self-configuring rulesets can be found here:

SELF-CONFIGURING RULESETS: GATEKEEPER RULES

As an example, single swing doors that have a latch approach on the pull side equipped with a closer should have a maneuvering space that extends 24 inches (915 mm) minimum beyond the latch side of the door and 54 inches (1525 mm) minimum perpendicular to the doorway.

In the image below, we see a door that leads from a corridor to a balcony that has both a closer and latch with a latch approach on the pull-side as specified by its properties under the property group “data”.

Door with a closer and latch that has a latch approach on the pull-side

By classifying these doors based on their approaches and whether they have a closer and latch, these properties can be checked in the “Components to Check” filter parameters table in a gatekeeper rule to only pass those components based on those properties.

Latch Approach, Pull Side Gatekeeper Rule

Here we see the previously mentioned door fails the requirements as the balcony wall intersects the required free area that extends 54″ perpendicular to the door:

Latch Approach, Pull Side Result

Another method can be used if the door approach is not specified as a property of the door.  Since the requirements of one of the three approaches must be satisfied, gatekeeper rules can be used to check each requirement passing those components that fail to sub-rules.  Below we see that all doors are first checked against the requirements of a Front Approach on the pull side of the door.  Those doors that fail this check are then passed to a sub-rule that checks the requirement of a hinge approach.  Again those that fail are passed to sub-rules for an alternate requirements of a hinge approach, and finally a latch approach.  Since the balcony wall is too close in all four approach requirements, a result is found as seen below:

Checking all Approaches through Gatekeeper Rules