Five Nines Mechatronics

Local inference · Phoenix, Arizona

AI software that runs inside your network.

Drawing and submittal review, data extraction from PDFs, automated report and document generation, desktop applications, browser tools and the integrations between them. Built for telecom, fiber, civil, structural, survey, geotech and architecture firms, and installed on your hardware, so submittals, site data and client files stay inside your firewall.

Built by a small team, with one point of contact throughout. If you want it demonstrated with the network interface disabled, that is how it will be demonstrated.

Example · compound_plan_C-2_rev1.pdf4 issues flagged
A compound plan with an automated markup A telecom compound drawing. A revision cloud marks an equipment pad, with a note that the plan shows three cabinets while the equipment schedule on sheet E-1 lists four. A stamp reads: processed locally, 0 bytes transmitted. 60'-0" MONOPOLE GENERATOR PAD EQUIPMENT PAD COMPOUND PLAN SHEET C-2 REV 1 CABINET QTY 3 SCHED E-1 QTY 4 VERIFY PROCESSED LOCALLY 0 BYTES TRANSMITTED
One example of many: a telecom compound plan checked against its equipment schedule. The same engine reads lab data, title commitments, specifications and submittals.
Fully localInference runs on your hardware. No drawings, PDFs or results are uploaded anywhere.
Works offlineNo connection needed at runtime, on a secured site or in a field trailer.
Yours at handoverFull source code and documentation. No subscription, no seat licensing, no lock-in.

01 / Architecture

Inference on your hardware, not someone else's.

Every cloud AI tool has the same entry requirement: upload the drawings first. Under a carrier NDA or a client confidentiality clause, that ends the conversation. These tools remove the upload entirely.

Data path

PDF in, markup out, nothing in between

The model weights sit on a workstation or server inside your office, the way your CAD licenses do. No API call, no vendor storage bucket, no retention policy to negotiate with a carrier's security team. There is no third party in the data path because there is no third party.

Availability

Runs with the interface disabled

No connection required at runtime. Useful in a field trailer, on a secured site, or the week the firewall is being rebuilt. Availability is the point: five nines is the standard the name refers to.

Cost model

No token or seat metering

Cloud inference bills per page or per user, and a full CD set is a lot of pages. Here the cost is the build. Run it across ten sheets or ten thousand for the same price.

Rule set

Your standards, encoded

Checks follow your QA checklist, the carrier's submittal requirements and your report templates, rather than a general model's assumptions about drawings.

Capacity

A team behind the build

Larger programs are staffed with developers from my team, so scope does not stall on one calendar. You still deal with one point of contact, and the same person is there at handover.

Delivery

Full source at handover

Complete source code, documentation and training on delivery. No subscription and no lock-in. Your data, templates and rules remain yours.

02 / Capabilities

By discipline.

Each tool performs one bounded, verifiable task. A single line from any list is typically a few weeks of work, not a platform. Some of these are built, some are scoped. Ask which, and you will get a straight answer.

Wireless / telecom A&E

CD sets, zoning drawings, site audits

  • Run a CD set against the carrier checklist and return a redlined PDF
  • Antenna, radio and coax schedules reconciled against the RFDS
  • Rev 0 to Rev 1 comparison, sheet by sheet, with a change list
  • Title blocks, sheet index, stamps and dates, where resubmittals originate
  • Structural report parsed, proposed loading flagged against capacity
  • Closeout packages assembled into a single PDF: photos, as-builts, checklists
  • Lease exhibits and zoning drawings checked against the survey

Fiber / OSP / cooperatives

Construction prints, make-ready, as-builts

  • OSP prints checked for footage, splice point and handhole callout agreement
  • Permit conditions reconciled against the issued construction package
  • Pole data extracted from make-ready files, exceptions routed to your reviewer
  • As-built compared to design, deltas listed
  • Progress and location-count reporting generated from project data
  • Material documentation compiled from vendor submittals

Civil / structural

Plan sets and calc packages

  • Dead sheet references, missing callouts and superseded general notes
  • Calculation packages assembled and formatted consistently
  • Quantity takeoff extracted into your estimating workbook
  • Shop drawings and product data checked against the specification
  • First-draft RFI responses written from your project history
  • Solar permit sets: module counts, attachment spacing, sheet-to-sheet consistency

Land surveying

Title work and field data

  • Legal descriptions, easements and exceptions extracted into an ALTA Table A checklist
  • Record calls compared against measured data, differences flagged
  • Reports and plat notes generated from field data in your format
  • Thirty years of project files searchable by parcel, owner or address

Geotech / materials testing

Lab and field reporting

  • Lab data sheets converted into finished reports in your template
  • Compaction and break results read from field logs, out-of-spec values flagged
  • Boring logs generated from field notes
  • Project-wide result summaries for the final report

Architecture

Submittals, specifications, project archive

  • Submittals checked against the specification sections that actually apply
  • Door, window and finish schedules reconciled against the plans
  • Specification book and past projects queried in plain language
  • First-pass code checklist review for an architect to confirm or reject
  • Proposal and RFQ drafts assembled from completed work

Firm-wide

Applies to every discipline above

  • An assistant that answers from your documents and no one else's
  • Offline summaries of reports, notes and long threads
  • Transmittals, cover sheets and standard letters populated from project data

03 / Specification

Where it runs and what it emits.

Not a privacy statement. A parts list.

Host
Workstation or server inside your office. Windows, macOS or Linux.
Connectivity
Not required at runtime. Model weights are installed locally.
Egress
None. No drawings, PDFs or results leave your network.
Inputs
PDF drawing sets, scanned documents, spreadsheets, field and lab data.
Outputs
Redlined PDFs, issue lists, workbooks and finished reports in your format.
Authority
Yours. The software proposes; your licensed reviewer approves every markup before it leaves the office.
Handover
Source code, documentation and training. No subscription.

04 / Process

Requirements first, in writing.

01

Discovery call

Thirty minutes, no charge. Which review or report consumes the hours, and how correctness is defined.

02

Written proposal

Scope, deliverables, price and schedule in writing before any work begins.

03

Pilot

One workflow, executed on your drawings, on your machine, at an agreed price.

04

Build and install

Something running early, regular check-ins, deployed on your hardware.

05

Handover

Source, documentation and training. Invoice on completion, net 15.

05 / The firm

Who you would be working with

Five Nines Mechatronics is a small Phoenix software firm working in three areas: AI automation that runs on local hardware, desktop applications for the work that happens inside an office, and websites and browser tools. I lead every build and stay your single point of contact from the first call through handover, bringing in developers from my team as the work needs them, so a larger program does not stall on one person's calendar.

The telecom work started with a submittal review application built for a five-person A&E team, which meant a long stretch inside other people's drawing sets learning where errors actually hide. The nineteen calculators published under Tools came from the same habit of building the thing rather than describing it. My background is in mechatronics and controls, which is why what I build tends to be organized around tolerances, checks and repeatable output instead of dashboards.

You get a direct number, not a ticket queue.

06 / Work

Shipped and in use.

Live links open the real thing, not a mockup.

Desktop application

State 48 Reviewer Tool

Telecom site audit and review for a five-person A&E team. Automated processing across submittal packages, generated review reports, and integration with the legacy systems the workflow already depended on. Runs on the team's own machines.

Interface walkthrough available on a call.

Browser tools

The Benches

Nineteen technical calculators covering servo sizing, beam and column analysis, bolted joints, PID tuning and ISO fits. Each computes client-side, so nothing entered leaves the device. Same rule as everything else here.

Open the tools

Website

State 48 Consulting

Service architecture across site acquisition, A&E and small cell, structured so a carrier or tower partner can locate the exact capability they are sourcing.

Visit the site

07 / Commercial

Quoted per project, never per hour.

A single-checklist tool and a full review system are not the same scope, so there is no menu price. Each project is scoped on the discovery call and priced in writing. Once agreed, the proposal figure is the invoice figure.

Engagement 01

Pilot

  • One workflow, such as a single drawing type against your checklist
  • Executed on your machine, against your own drawings
  • A measured read on accuracy before committing further

Engagement 02

Local AI system

  • Complete desktop or server application for your team
  • Drawing review, data extraction and report generation as scoped
  • Integration with existing systems and templates
  • Source code, documentation and a support window

Engagement 03

Websites and browser tools

  • Hand-coded sites for engineering and construction firms
  • Calculators and configurators that compute client-side
  • Accessible, fast, indexed properly
Number of rules or checks applied
Count of document and drawing types
Source quality: vector PDFs or scans
Integrations with existing systems
Seats or machines deployed
How much existing work is reusable
Length of the support window
Hardware, where the workload requires it

Fixed price per project, not hourly, so there is no meter running while you think. A service agreement and a deposit apply for new clients and larger builds. Hardware is quoted separately where required.

08 / Contact

What is consuming your team’s hours?

Describe it in a sentence or a page. Response within one business day. The discovery call is thirty minutes and costs nothing.

Thirty minutes, no charge. Bring a drawing set, a report template, or the stack of PDFs nobody wants to retype.