Prompt systemMedium riskVersion 1.0.0New

Opening and Door-Window Type Mapper

Map existing openings, doors, and windows to proposed standard types while separating confirmed from unresolved hosts.

Part of RavenAI Standardized Building Elements
Section Nine · archiPrompt StudioPublished Jul 26, 2026Updated Jul 26, 2026

Required inputs

  • Existing element geometry and attributes · required
    Rhino geometry, Grasshopper data, CSV-style records, or structured text
  • Target type or assembly schema · required
    Structured text or JSON
  • Approved mapping rules and tolerances · required
    Structured text or JSON
  • Scope and review requirements · required
    Structured text

Compatibility

  • Rhino 8
  • Grasshopper
  • Raven

Last tested Jul 2026

Review boundary

A qualified project reviewer must approve target standards, mapping rules, tolerance-based matches, exceptions, proposed host relationships, and any downstream model write-back.

01

Input → method → output

The public process and a redacted example are visible before purchase.

How to install

Purchase the workflow, drop its file into Raven, add your project-specific instruction, and review the result in Grasshopper.

Install Raven AI
Purchase the workflow, add its file to Raven, enter a sample instruction, and review the generated Grasshopper deliverable.

SAMPLE INPUT

Existing element geometry and attributes + Target type or assembly schema + Approved mapping rules and tolerances + Scope and review requirements

PROCESS PREVIEW

4 controlled steps with quality checks

EXPECTED OUTPUT

Proposed standard register, source mapping table, exception queue, validation report, reviewer decision list, and bounded Grasshopper workflow plan or canvas edit summary.

Redacted output preview

Opening and Door-Window Type Mapper

Standalone prompt from RavenAI Standardized Building Elements

Independent systems
5
Default model action
Report-first
Review gates
Exceptions + mappings

Representative output

Opening Type and Host Register | Type ID | Category | Dimensions | Sources | Status | |---|---|---|---|---| | OPN-001 | Window candidate | 1200–1201 x 1500 mm; sill 900 mm | O-101, O-102 | Proposed—tolerance mapping review | | OPN-002 | Door candidate | 920 x 2100 mm; sill 0 mm | O-103 | Proposed | Host relationships | Source ID | Host result | Status | |---|---|---| | O-101 | W-EXT-01 | Confirmed as supplied | | O-102 | No host assigned | Exception: no supplied host or host geometry | | O-103 | W-EXT-02 | Confirmed as supplied | Grasshopper workflow Intake → opening profiler → category filter → supplied-host validator → type mapper → validation → registers, with unmatched records routed to exceptions. Revie…

Proposed standardization output — review required before any model update.

02

What it does

Map existing openings, doors, and windows to proposed standard types while separating confirmed from unresolved hosts. This independently usable prompt system is also included in RavenAI Standardized Building Elements. It inherits the Collection's reviewed integration setup, compatibility boundary, limitations, and human-review requirements.

Five element-specific, reviewable standardization workflows for producing proposed BIM type and assembly registers from existing model data.

Designed for

  • Run Opening and Door-Window Type Mapper without downloading the complete Collection
  • Normalize inconsistent wall-type records
  • Rationalize column and pier geometry classes
  • Create stair assembly registers from existing components
  • Classify slab and roof surface records
  • Map door/window/opening types and host relationships

03

Included files + delivery

README.mdMarkdownSetup, use, and professional boundary
PROMPT.mdMarkdownPrimary workflow entry point
variables.jsonJSONInputs and output configuration
sample-input.mdMarkdownRepresentative input structure
sample-output.mdMarkdownRepresentative output structure
manifest.jsonJSONPackage contract and permissions
qa-report.jsonJSONValidation and review record

Delivered as a versioned ZIP package. After verified payment, the exact purchased version is available through the buyer's private Library.

04

Workflow steps

  1. 01

    1. Select element workflow

    Choose the child system that matches the building-element boundary and load its variables template.

  2. 02

    2. Supply controlled inputs

    Provide existing geometry/attributes, the target schema, approved mapping rules, tolerances, and scope.

  3. 03

    3. Generate proposed standardization

    Use Raven in Grasshopper to plan or edit the bounded workflow; keep source data intact unless approved otherwise.

  4. 04

    4. Approve with a qualified reviewer

    Review mapping evidence, exceptions, and validation results before approving any model update.

05

Limitations + professional safety

Medium risk · human review required

A qualified project reviewer must approve target standards, mapping rules, tolerance-based matches, exceptions, proposed host relationships, and any downstream model write-back.

Jurisdiction: Project-defined; no jurisdiction-specific compliance assessment is included.

Known limitations

  • Works from supplied model information and approved mapping rules only.
  • Does not establish regulatory, structural, fire, acoustic, thermal, waterproofing, accessibility, egress, security, manufacturer, or construction conclusions.
  • Ambiguous, incomplete, and conflicting records are routed for review rather than resolved by assumption.
  • Raven availability, pricing, and plan limits should be confirmed on the official Raven website.

06

Security + quality

Declared permissions

  • Access to relevant Rhino/Grasshopper source geometry and attributes
  • Permission to install and use Raven in Rhino 8/Grasshopper where required
  • Authority to use approved project naming, mapping, and tolerance rules

Completion checks

  • Every mapped record retains a source ID.
  • Missing or conflicting values are listed as exceptions.
  • Tolerance-based matches are identified rather than hidden.
  • No unsupported performance or compliance values are assigned.
  • Proposed model updates require human review.
Package structure reviewedVersion 1.0.0Tested Jul 2026

07

Install + use

01

Download

Receive the immutable versioned ZIP package.

02

Read

Open SKILL.md or the named workflow entry point.

03

Prepare

Collect required inputs and remove sensitive data.

04

Run + review

Execute in a tested tool, then complete human review.

08

Reviews + trust

No public reviews yet

Synthetic ratings and review counts are not displayed.

Verified purchase requiredVersion-specificCreator response supported

Public reviews are withheld until the marketplace can verify purchase entitlement and support a trustworthy, version-specific review process.

09

Creator

Anonymous model coordination desk representing Section Nine

Section Nine

archiPrompt Studio

Architecture and BIM coordination · 16 years · Melbourne, Australia

Architects and BIM coordinators packaging repeatable quality-control methods for project teams.

A first-party specialization account operated and approved by archiPrompt.

View creator profile

10

FAQ + support + changelog

Does this collection determine compliant or buildable assemblies?

No. Each system creates proposed standardized information from supplied data and approved rules. It does not make code, structural, performance, or construction determinations.

Which prompt should I use?

Use the child prompt matching the element boundary. The collection index routes walls, columns/piers, stairs, slabs/roofs, and openings to separate systems.

Will the workflow overwrite my source model?

No. The prompts default to report-only behavior unless an explicit approved write-back instruction is supplied, and a qualified reviewer should approve changes first.

Where do I install Raven AI?

Use the official installation page: https://www.raven.build/en/download

Where can I review Raven AI pricing?

Review the current plans and access terms on the official pricing page: https://www.raven.build/en/pricing

Support

Package support covers prompt-file access and clarification of included workflow boundaries. Project-specific modeling, code, engineering, and implementation review remain the buyer's responsibility.

Latest changelog

v1.0 — Initial collection of five bounded building-element standardization workflows. Standalone component published with RavenAI Standardized Building Elements.

Updated Jul 26, 2026
Project-defined; no jurisdiction-specific compliance assessment is included.

Related workflows

Selected from shared project phases, disciplines, compatible tools, and adjacent deliverables—not generic popularity.

View all workflows
Back to browse

Privacy choices

Choose what archiPrompt measures.

Necessary

Authentication, checkout, security, and remembering this choice.

Always on

Marketing tracking and session replay are not in use. You can change this choice at any time from the site footer.