MCPVault Clear — Elevator MCP Completeness Pack Engine

Audience

regional multifamily and mixed-use property managers with 3-40 elevator-equipped buildings (Colorado Front Range beachhead, Fairfax County VA secondary)

Problem

Every elevator and escalator an owner operates needs a written, equipment-specific Maintenance Control Program under ASME A17.1 §8.6, with maintenance, callback, and FEO-test records retained roughly five years and viewable on-site. But the MCP usually lives with whichever vendor wrote it, most owners have never reviewed it, and Colorado and Fairfax County both now treat a missing or incomplete MCP as an inspection-failure condition — not a footnote.

Offer

On MCPVault Clear, facilities coordinators stop guessing whether their elevators will pass a documentation review and start proving it. Upload the MCP, vendor logs, callback history, and machine-room photos; AI extracts and gap-scores the file against the adopted ASME A17.1 §8.6 / AHJ checklist, and a compliance analyst — with a licensed elevator consultant/QEI on escalation for missing-MCP-authorship or contested code interpretation — releases a Completeness Pack, a vendor chase kit, and a dated vault index.

Operating process

[
  {
    "body": "Upload the MCP, vendor logs, callback history, inspection reports, and machine-room photos for one building or conveyance. Each document gets a document ID on arrival, and unit IDs and vendor names are canonicalized against your building roster — ambiguous matches go to a human, not a guess.",
    "title": "Intake: upload the building file"
  },
  {
    "body": "AI OCRs and classifies the file, matches it to the adopted ASME A17.1 §8.6 checklist for your AHJ edition (Colorado 7 CCR 1101-8, Fairfax County Elevator Program), and checks the MCP for equipment-specificity and coverage-timeline completeness.",
    "title": "Extract and match against the AHJ checklist"
  },
  {
    "body": "No MCP, no on-site accessibility instructions, under-5-year retention where required, and missing FEO tests where required all run through versioned deterministic gates — never a language model's judgment call — and each hard gap cites its checklist clause and evidence pointer.",
    "title": "Score hard gaps in deterministic rules"
  },
  {
    "body": "A compliance analyst reviews the gap matrix and releases green and yellow packs. Missing-MCP-authorship and contested code-interpretation cases escalate — a hand-off, not a rejection — to a licensed elevator consultant/QEI, who releases the red pack.",
    "title": "Human release gate"
  },
  {
    "body": "The Completeness Pack PDF, vendor chase kit, and dated vault index land in your folder the same release cycle. QA runs a second-pass sample against anti-fabrication checks before anything ships.",
    "title": "Deliver the pack and chase kit"
  },
  {
    "body": "If you've purchased the Chase Desk, we track vendor cure evidence until hard gaps close. Portfolio Desk buildings get a quarterly re-scan on the calendar, and every failed inspection or AHJ comment feeds back into the checklist library.",
    "title": "Watch the vendor cure and the next re-scan"
  }
]

Evidence status

Domain-design coverage

Passed: 20; total: 20; coverage: 100.

Open the complete public blueprint DNA (JSON)