Those Airport Drawings Are Marked SSI. A 2026 On-Site Box Lets Your Project Engineer Search Them Without Sending Them Anywhere.

4:40 p.m. in the trailer at Gate C

The project engineer on your terminal expansion has to return the security electronics rough-in submittal by Friday, and she is stuck on one question: does the conformed set still show conduit stub-ups at the new checkpoint podiums, or did ASI 14 move them six feet north? The answer is somewhere inside a 900-sheet drawing set and a project manual that runs past 2,400 pages. She has Bluebeam Revu open on one screen, Autodesk Docs on the other, the ASI log in Procore behind that, and roughly forty minutes before the electrical sub's coordinator goes home.

What she does not have is the thing your estimating department now uses every day. Every sheet in that set carries a banner along the bottom edge: SENSITIVE SECURITY INFORMATION. Under 49 CFR Parts 15 and 1520 those sheets are restricted, the airport authority wrote it into the special conditions, and dropping them into an outside service is not a gray area. So she reads. By hand. Until 6:15. Then she writes RFI 212 anyway, because she could not find it, and the sub sits for eight days waiting on the architect.

That hour, repeated across every restricted job, is what changed in 2026.

The jobs where the drawings are not yours to send anywhere

Most commercial GCs have three or four of these in the backlog at any given moment, and they are usually the good work — negotiated, repeat, decent fee. They are also the jobs where the office AI tool is switched off:

• Aviation. Terminal expansions, baggage handling, checkpoint reconfiguration, anything on the SIDA side. Sheets come marked SSI and you are a covered person under 49 CFR 1520 whether you wanted to be or not.
• Federal and DoD. A hangar door replacement, a barracks renovation, a Corps of Engineers job. The contract carries DFARS 252.204-7012 and, since the rule bit, a CMMC Level 2 requirement. The drawings and specs are Controlled Unclassified Information, any outside service touching them has to meet a FedRAMP Moderate equivalent, and the requirement flows down to every sub who touches the set.
• Detention, courthouse, and 911 dispatch centers. Sallyport hardware schedules, camera coverage plans, secure duct routing. County contracts routinely forbid third-party distribution outright.
• K-12. Many states now exempt school security plans from public records requests, and districts write clauses banning distribution of the door hardware, access control and camera sheets.
• Hyperscale data centers and hospitals. The owner's confidentiality exhibit covers the white space layout, the generator yard, the behavioral health unit door details. Breach it and you are off the program, not just off the job.

Running the model on your own hardware means the drawing set is read by a computer you own, sitting in a building you control, and nothing about that set is transmitted to anyone outside your company. That is the whole idea, and until this year it was not practical for a contractor.

What she does today, and the workaround everybody pretends is fine

Today the search is a person with a mouse. The conformed set is searchable if the architect issued clean sheets, but half the exhibits are scans, the as-builts from the 1998 concourse are photographed blueprints, and the specification book is a merged file from nine consultants. Bluebeam's search finds the word "podium" 214 times. None of the first forty hits are the one she needs.

The workaround everyone pretends is fine: she texts a photo of the sheet to the electrical foreman and asks him what got built. That is itself a distribution of a restricted document, on a personal phone, with no record, and nobody writes it in the daily report. The honest path — RFI 212 — costs seven to ten calendar days under the spec's RFI section, and if the sub sits idle that long you will see a delay claim before the pay application.

flowchart TD
  A["4:40pm: PE needs the checkpoint stub-up detail"] --> B{"Is the sheet marked SSI or CUI?"}
  B -->|Yes| C["Search runs on the box in the trailer server room"]
  B -->|No| D["Search runs on the office tool"]
  C --> E["Answer comes back with sheet number, ASI number, spec section"]
  D --> E
  E --> F{"Does the approved set actually answer it?"}
  F -->|Yes| G["PE returns the submittal the same afternoon"]
  F -->|No| H["PE writes RFI 212 with the sheets already cited"]

What changed in 2026: the computer that does the reading sits in your server room

Two things happened this year. First, the chips got there. Qualcomm's Dragonwing-class processors and their equivalents made it realistic to do serious document reading on a single machine you can buy, rack, or bolt into a job trailer — not a rented data center. For high-volume, repetitive reading of the kind a GC does, running it locally costs roughly ninety percent less than sending the same work out.

Second, the big companies stopped treating on-premises as the embarrassing option. Cisco's rollout of a personal AI agent to roughly 90,000 employees leans explicitly on on-premises handling for control and data protection. When a company that size decides the sensitive material stays inside the building, the vendors follow, and the on-site versions stop being the crippled ones.

For you that means one machine in the same rack as your Sage 300 CRE server, or a smaller one in the trailer at Gate C, that can be pointed at the conformed set, the project manual, the ASI log, the approved submittals and the RFI responses for that job and nothing else. Nothing leaves. Your CMMC assessor can see where it is, who can reach it, and what it touched.

Tuesday on the terminal job, run the new way

7:05 a.m. The superintendent asks at the tailgate whether the sound-rated ceiling over the new hold room matches the concourse side. The project engineer asks the on-site tool. Ninety seconds later: spec section 09 51 23, sheet A-621, revised by ASI 9. She writes it in the Raken daily report with the sheet numbers, which is what the owner's rep will want in six months.

1:30 p.m. Submittal review. The security electronics package is 340 pages of cut sheets. She asks it to list every place the submittal deviates from spec section 28 13 00 with the paragraph beside each one. It finds four, three trivial and one a different door position indicator than the basis of design. She rejects that item and cites the paragraph. The sub does not argue with a paragraph number.

4:40 p.m. The podium question. Answered in the trailer, not by text message to a foreman's personal phone, and no RFI 212.

The arithmetic: one project engineer, one restricted job, fourteen months

Assumptions, all stated so you can argue with them: one project engineer at $84,000 salary, burdened at 1.35, which is $54.52 an hour — call it $55. She currently spends six and a half hours a week searching restricted documents by hand. Local search takes that to two. The job runs 60 weeks. RFIs on this job average eleven a month; assume two a month were purely "I could not find it" and go away, and that each one costs your side two hours of project engineer and project manager time to write, log, chase and close.

Ten thousand dollars is not the reason to do this. The reason is that on an SSI or CUI job it is the only lawful way to do the search at all. Note also what is not in the table: the delay claim you did not receive because a sub did not sit idle for eight days.

Where this still needs a human

The machine does not know what is restricted. Somebody has to mark it — that is document control, usually a project engineer, and if they load the SSI set into the wrong place you have created exactly the problem you bought the box to avoid. Write it into your document control procedure before the first sheet arrives.

An on-site box does not satisfy DFARS 252.204-7012 or CMMC by itself. It removes the outside-service question. It does not remove access control, logging, physical security, or the System Security Plan your assessor will ask for.

And a search result is not a design decision. The architect of record still owns design intent, the RFI is still the instrument of record, and the building official does not accept a summary. Use it to find the sheet and cite it. Do not use it to decide whether the detail is adequate.

One practical warning: a machine in a job trailer is an asset on a jobsite — dust, heat, and trailers get broken into. Most contractors put the hardware in the main office and let the trailer reach it over the company connection.

Frequently asked questions

Do I need one of these in every job trailer?

No. One machine in your main office server room, reachable by the trailers over your own connection, covers a whole portfolio. Put hardware on site only when the contract says the material cannot leave the premises — some federal and detention jobs do say exactly that.

Is the on-site version noticeably worse than the cloud version?

For reading a drawing set and a specification book and telling you which sheet says what, no. For open-ended writing you might notice. The reading and citing work is where the local machine is more than good enough, and that is the work your project engineers are drowning in.

Can my subcontractors use it?

Only if they are already authorized to see the documents in it, and on CUI jobs that means the flow-down requirements apply to them too. In practice most GCs keep it internal and give subs answers with sheet citations rather than access to the set.

One last note that is adjacent rather than central. While your project engineer is buried in a restricted set, the office line is still ringing — subs chasing submittal status, the owner's rep, inspectors confirming a Thursday slot, and the plan room calls that turn into next year's bids. CallSphere builds AI voice and chat agents that answer the phone and the website chat, take the details, book the appointment and pass the lead on, 24 hours a day. It answers your phone line; it does not read your SSI drawings, and no honest vendor should tell you otherwise.