One section per tag: the instrument submittal package, with everything still missing on its own list.

The order is in and the submittal is due. Your applications engineer works down the tags: the cut sheet for the model code ordered, a dimensional drawing, a wiring diagram, the certificates the spec asks for and the range each unit will be calibrated to. Some of that comes from a manufacturer's library, some from the factory on request, and none of it counts until it matches the tag.

In the test, AI reads copies of each order, the spec section and the documents your team gathered, and assembles the package tag by tag, with an index, each section's contents and a list of what the documents don't cover. It marks options on a cut sheet only where the order names them. It makes no judgment about compliance, and your engineer reviews and releases every package.

A cut sheet has to be marked to the tag. Eastern Municipal Water District's Section 17005, revised in April 2016, wants manufacturers' literature marked to show what applies, with the rest crossed out. It asks for a bill of materials listing manufacturer, quantity, description, size, range and catalog or part number, and for summary data sheets in ISA-20.00.01 format: equipment name and ISA tag, complete model number, location, input and output characteristics, range and gradation in engineering units, wetted and enclosure materials, and the enclosure's NEMA classification. Drawings come reduced to 11 by 17 at most. A model that serves several tags still gets a section under each one, marked for that tag's options.

Loop and wiring documents hold numbers that live elsewhere. ISA-5.4-1991 sets minimum content for instrument loop diagrams: identification of loop components, interconnections, energy sources and control actions. Eastern Municipal goes further and ends each loop diagram with a table of the transmitter's output capability, every receiver's input impedance, estimated wiring impedance, total loop impedance and reserve capacity. Oakland County, Michigan wants wiring diagrams that separate what the manufacturer installed from what gets wired in the field. Winnipeg's 2007 package calls for a loop diagram per device, with terminal and wire numbers filled in as shop drawings become available. Whether your desk owes those depends on the order, and numbers that don't exist yet go on the missing list as open rather than sitting in a blank that looks finished.

Tags have to agree from the page to the device. Oakland County wants a permanently attached tag carrying the engineer's identification, and the manufacturer's too if they differ. Eastern Municipal wants a rectangular Type 316 stainless tag engraved with the project tag number. In Owosso, Michigan's 2020 addendum, each transmitter carries a stainless tag with calibration data on its body. Winnipeg's general section has smart transmitters programmed with range and tag number before calibration, then asks for a printed record of serial numbers against assigned tags. So the calibration range on the order, the range in the package and the range on the tag are three places a mismatch can start, and the draft sets them side by side wherever the documents give them.

A certificate can say less than it seems to. NIST's published traceability policy and FAQ say the provider of a measurement result is responsible for establishing its traceability, and that NIST's own test report numbers are for administrative purposes and shouldn't be used or required as the sole proof. NIST also says it certifies only results it provides itself. A spec may say NIST traceable. Eastern Municipal's section, for one, has field calibration done with test instruments traceable to NIST and a sheet for each instrument recording the readings as finally adjusted. The phrase on a certificate isn't proof on its own, so the draft lists the certificate each section asks for, whether your files hold one, and the tag and serial it names. Judging it stays with your engineer.

Deviations and resubmittals cost calendar time. Oakland County wants a written deviation request at least fourteen days before product delivery, justified requirement by requirement, and recommends listing deviations in the initial product submittal. New York State's master section has submittals tabbed in the order specified and subject to a re-evaluation fee under its general conditions. Greater Sudbury wants shop drawings to show each instrument's proposed enclosure rating, any hazardous classification rating and associated intrinsically safe relay panels. The draft never says a product complies; it lists what each section asks for and where the package answers it. Your reviewer, usually the applications engineer who releases these, checks that each tag has its section, that no page came from a similar model, and that the missing list is complete. These documents are named for context only, not as legal or engineering advice.

Once your reviewer says yes, packages for new orders get the same draft for about 30 days.

Your applications engineer reviews and releases each package, requests each document from the factory and answers the customer. Any change of model stays with your engineer and the customer's engineer.

That month carries a fixed price agreed before signing. Monthly support and any later job are separate decisions.