The jobs it assumes
Municipal, industrial, and OEM work: pump stations, packaging lines, process skids, packaged equipment. Projects with a site-and-panel structure, spec books that number their sections three different ways, and document work that spans years. The register mirrors how you deliver: sites, panels, and the equipment inside them.
The work it is built around
If you build the panels, program the controllers, and then owe the paperwork for the job, this is your tool. It is built for the shops CSIA, the Control System Integrators Association, represents: the ones that design, build, program, and document control systems, and answer for every page at each stage.
- Water and wastewater: pump stations, lift stations, and treatment plants, where the same panel repeats across a dozen sites and the O&M manual is a contract deliverable
- Building automation (BAS): controller, sensor, and network product data for integrated automation submittals, with the sequence documents that ride along
- Process and industrial instrumentation: transmitters, analyzers, and valves that each need their datasheet and catalog number marked
- Panel shops: UL 508A control panels with the component datasheets, SCCR ratings, and shop drawings a reviewer asks for
- OEM and packaged equipment: skids and machines delivered with a submittal up front and a manual at the end
Division 25 and 40 spec books
Integrated Automation (Division 25) and Process Interconnections (Division 40) sections bury their submittal demands in long lists, and HVAC controls under Division 23 do the same. Upload the spec book once: each section's demands become rows on the log, and every datasheet is checked against its section before the package ships.
One register, every deliverable
- Import the BOM per panel; parts match your shared library
- Compile the submittal package with per-item catalog highlighting
- Build the O&M manual from the same list, per-panel chapters and station BOM tables included
- Read the spec book once: each section's demands become the log, and every datasheet is checked against its section before it ships
- Send the package to the reviewing engineer by emailed link, opens and downloads tracked
- Keep as-built redlines, RFIs, and the punch list on the same project
- Issue everything through one log whose submissions are permanent
Who is behind it
Submittal Kit is built by an integrator project manager who assembled these packages by hand for years, and it is in use on real projects today. Support is answered by a person who knows what a transmittal is, not a ticket queue. Nothing leaves without your stamp: automation proposes, you accept.