ModelMedic is a model-health and QA/QC toolkit for Autodesk Revit published by ME Solutions, identified in its privacy policy as Mohamed Elzaiat. It brings six focused tools into one add-in: ModelCheck, LinkTrace, Warnalyzer, ModelMop, GridSync, and JoinMaster. Together they address repeatable model checks, link-coordinate investigation, selected warning fixes, targeted cleanup, element-to-grid alignment, and geometry join order. Its distinguishing proposition is the combination of inspection and remediation: users can identify selected problems and then address supported cases within Revit rather than collecting a report alone. The current marketplace lists the add-in as free. [1, 2]
 |
| ModelMedic - Main Window |
1. ModelCheck — Repeatable Model-Health Reviews
ModelCheck lets teams set project thresholds, run health checks, review pass/fail results, share settings, and export reports to Excel (.xlsx). The developer describes a distributed workflow in which a BIM manager defines thresholds and exports settings, team members import them and run checks, and results return for review. This could support recurring coordination checks and pre-issue reviews using consistent criteria. However, the retrieved product material does not enumerate the complete metric library, threshold ranges, weighting, check-setting format, or report schema. It should not be assumed to validate arbitrary client requirements, every BIM execution plan provision, or all information-delivery standards. [1, 3]
 |
| ModelMedic - ModelCheck Settings |
 |
| ModelMedic - ModelCheck Report |
2. LinkTrace — Link Placement and Coordinate Analysis
LinkTrace reviews RVT link placement and coordinate relationships. The marketplace identifies Shared Site status; Survey Point, Project Base Point, and Internal Origin deltas; rotation differences; placement source; and duplicated link instances. These checks can help distinguish a local placement problem from a broader coordination or coordinate-system discrepancy. A displayed delta is evidence to investigate, not an instruction to move the link or acquire/publish coordinates: a difference may be intentional. The public description confirms analysis, not automatic repair of shared-coordinate relationships or authority to overwrite a project’s agreed survey setup. [1]
 |
| ModelMedic - LinkTrace |
3. Warnalyzer — Warning Review and Supported Fixes
- Warning investigation: Review Revit warnings and select the affected elements.
- Joined but not intersecting: The developer describes resolving this condition by unjoining the affected geometry.
- Slightly off-axis elements: Supported corrections snap small alignment or rotation discrepancies within a tolerance.
- Duplicated instances: Supported duplicate removal retains one instance, according to the developer’s description. Rules for deciding which instance survives require confirmation.
- Duplicate Mark and Type Mark: A parameter resolver supports bulk cleanup of conflicting values. Naming patterns, exclusions, and downstream effects on tags and schedules should be tested.
Warnalyzer is not advertised as an automatic solution for every warning category. Even a supported correction can change design or documentation intent: a slight angle may be intentional, repeated marks may follow a legitimate convention, and coincident elements may represent different phases or requirements. Pilot corrections on controlled copies and verify geometry, hosting, tags, schedules, and warning counts afterward. [1, 3]
 |
| ModelMedic - Warnalyzer |
 |
| ModelMedic - Warnalyzer; Duplicate Mark/Type-mark Resolver |
4. ModelMop — Targeted Cleanup and Optimization
ModelMop offers selectable cleanup actions rather than a single undifferentiated purge. The current listing names unused content, views, sheets, links, CAD, PDFs, images, annotations, regions, groups, arrays, rooms, spaces, and areas. It also advertises family cleanup, Convert In-Place, workset assignment, and pinning of links, grids, and levels. The developer’s earlier overview additionally mentions empty worksets, filters, view templates, and group explosion. Those historical details should be checked against the installed version rather than treated as a complete current command specification. [1, 3]
The practical value is selective housekeeping and reference protection. However, unused does not always mean unnecessary: unplaced views, spare types, planning rooms, reference images, and templates may be intentional project resources. Likewise, in-place conversion, exploding groups, deleting sheets, or removing linked content can have substantial effects. Confirm previews, dependent deletions, protected-content exclusions, transaction behavior, and recovery procedures before enabling destructive actions. The listing does not establish that conversion preserves every constraint, relationship, parameter, and category behavior.
 |
| ModelMedic - ModelMop |
5. GridSync — Element-to-Grid Alignment
GridSync checks and corrects columns, walls, and beams using distance, center, and angle criteria. The marketplace identifies visible-element and selected-element scopes. The developer describes configurable distance/angle tolerances and correction logging. This makes it potentially useful for minor near-misses rather than wholesale geometric redesign. Teams must distinguish accidental drift from deliberate offsets, sloping framing, eccentric columns, and nonorthogonal layouts. Test pinned elements, constraints, groups, hosted components, sloped members, and worksharing ownership before applying corrections broadly. No public specification for all supported grid geometries or structural relationships was established. [1, 3]
 |
| ModelMedic - GridSync |
6. JoinMaster — Priority-Based Geometry Joins
JoinMaster automatically joins eligible intersecting elements and enforces join order according to a user-defined category priority. The developer gives Walls → Floors → Framing as an example of a priority sequence, not a universal recommended standard. The tool can potentially reduce repetitive join and switch-join operations and improve consistent representation. Join order also affects visible edges and quantity interpretation, so priorities should reflect the project’s modeling rules. Confirm supported category pairs, processing scope, exceptions, and effects on sections, material quantities, and schedules. The description does not establish a clash-detection or analytical-model coordination capability. [1, 3]
 |
| ModelMedic - JoinMaster |
Recommended QA/QC Workflow
- Establish a baseline: Record warnings, relevant health results, link-coordinate findings, and representative model behavior before changes.
- Standardize settings: Agree project-specific thresholds, alignment tolerances, join priorities, naming rules, and cleanup exclusions.
- Inspect before modifying: Start with ModelCheck and LinkTrace, then triage warning and alignment findings by impact and intent.
- Pilot targeted corrections: Use a sandboxed copy and limited selections for Warnalyzer, GridSync, ModelMop, and JoinMaster.
- Validate downstream effects: Review constraints, hosting, groups, phases, geometry, schedules, tags, quantities, joins, and coordinate relationships.
- Recheck and report: Rerun relevant checks and retain the Excel health report alongside a project record of accepted exceptions and actual corrections.
- Repeat at agreed milestones: Use a documented cadence appropriate to model maturity and deliverable risk. This workflow is evaluation guidance, not a confirmed automation feature.
Local Processing, Connectivity, and Privacy
The marketplace states that model operations run locally inside Revit and that model geometry and project content are not uploaded. It also acknowledges connections for update, availability, and version checks. The publisher’s privacy policy provides a more specific and material qualification: a weekly online update check is required, and the application may require a critical update before further use. Therefore, local model processing should not be described as fully offline operation or absence of transmitted identifiers. [1, 2]
The policy says update requests transmit the application version, Revit major version, a randomly generated installation ID, Revit username, and Windows account name. The hosting provider also records IP address and User-Agent as part of normal web requests. The publisher describes these uses as updates, compatibility, abuse prevention, and possible future entitlement validation, not advertising or analytics. Autodesk may also share purchaser name and email for entitlement and support. Although the policy’s general offline section says no default personal-data collection, its required-update section expressly lists identifiers; deployment review should use the more specific disclosure rather than characterize the software as having no data transmission. IT should confirm endpoints, retention, access, offline grace behavior, and the effect of blocked requests. [2]
Availability, Compatibility, and Support
- Publisher: ME Solutions; the privacy policy identifies Mohamed Elzaiat.
- Current listed price: Free on Autodesk Marketplace. The privacy policy anticipates possible future licensing; permanent free availability should not be assumed.
- Supported Revit versions: 2022, 2023, 2024, 2025, and 2026 in the current listing. Revit 2027 support was not established.
- Operating system and language: Windows 10/11; English.
- Current listed release: Version 1.0.8, last updated September 21, 2026. The marketplace gives June 17, 2026 as the release date.
- Public reviews: The retrieved marketplace listing shows one 5-star rating. Its “no known issues” FAQ is not evidence of error-free operation.
- Unconfirmed details: Installer prerequisites, administrative deployment switches, complete licensing terms, support response commitments, and detailed rollback behavior were not established. [1–3]
Overall Assessment
ModelMedic offers a broad, practical combination of model-health checks and selective remediation in a currently free Revit toolkit. Its strongest documented features are shareable checking thresholds, Excel reporting, link-coordinate diagnostics, fixes for several common warnings, targeted cleanup, tolerance-based alignment, and category-priority join control. It is best treated as a coordinated maintenance toolkit, not an all-purpose compliance validator, clash detector, or guarantee of improved performance. Adoption should depend on controlled testing of modifying commands and approval of the mandatory-update/privacy behavior. No independent performance benchmark was established, so productivity and reliability benefits remain to be evaluated on representative project models.
Sources
- Autodesk Marketplace — ModelMedic, ME Solutions. Primary current product source for the six modules, feature scope, Excel reporting, local model processing, free price, version and release dates, compatibility, operating system, language, and rating status.
- ModelMedic — Publisher Privacy Policy. Publisher identity and contact; effective September 18, 2025. Source for required weekly update checks, possible critical-update enforcement, transmitted identifiers, entitlement information, and potential future licensing.
- Mohamed Elzaiat — ModelMedic developer announcement. Supplementary developer-authored detail on distributed checking, warning fixes, alignment tolerances, cleanup, and join priorities. Earlier compatibility and early-access subscription statements are not substituted for the current marketplace listing.
Advertisement
No comments:
Post a Comment