In development

Preparing door hardware order forms

An in-development workflow maps cost-report details into a manufacturer’s order form.

Door & frame distribution

The workflow

OPENING A-204 / ILLUSTRATIVEDoor elevation → order fieldsExtraction remains in development
Single-door elevation with hardware details3′–0″ OPENING7′–0″ HEIGHTDOOR LEAFLEVER3 HINGES

ElevationDoor + hardware details

MANUFACTURER ORDER SHEETOpening A-204
Opening3′–0″ × 7′–0″
HandRH / single
HingesH-01 / standard
LatchL-02 / mortise
Mapped field setReview required
Illustrative workflow

Independent work, outside my role at Terakeet. Employment experience

The problem

For each new job, estimators re-key three or four internal cost reports into a macro-enabled manufacturer form. They translate hardware codes from memory, and misspelled strings can be rejected by the manufacturer’s system.

The reports include opening costs, door manufacturing details, and sometimes frame data or a schedule. Their formats vary, door identifiers are inconsistent, and the manufacturer’s form expects exact product strings in one of forty-five entry slots per workbook.

What I built

The workflow maps internal hardware codes to the manufacturer’s required strings, applies exclusion and consolidation rules, splits pair doors into active and inactive leaves, and populates the form. The mapping has been validated against real jobs; extraction is still being finished.

  1. Extract and normalize

    Combine structured parsing with visual reading, then normalize fractional sizes and inconsistent opening identifiers.

  2. Translate and apply rules

    Use an editable code mapping, exclude out-of-scope doors, consolidate identical specifications, and split pair leaves.

  3. Prepare the workbook

    Preserve the macro-enabled form and recalculate its formula fields while surfacing uncertain cases for review.

The outcome

Mappings and form rules have been validated against real jobs, including pair-door splitting and consolidation of identical openings. The extraction pass remains unfinished, so the full workflow is still in development.

The mapping library and business rules have been checked against six jobs covering sixty-eight doors. The next milestone is to run the extraction pass end to end on a validated job and review the resulting form and flags.

Business impact

When extraction is complete, the workflow is intended to reduce re-keying and code-translation work while giving estimators a populated form and flagged uncertainties to review.

  • Validated code mappings
  • Form population in development
  • Estimator review still needed