Storage tank knowledge is scattered across disciplines that rarely share a schema: mechanical engineers own shell calculations, civil engineers own foundations, corrosion specialists own coating histories, operators own the filling rhythm, and inspectors own the evidence. GenAnywhere, the content-shaping persona for industrial domains, unifies these by modeling each tank as a small system of typed entities with explicit invariants, then rendering every artifact — inspection index, turnover packet, regulator summary — from that single model. The architecture is entirely describable in prose.
The six core entities
At the center sits the Vessel, the tank as a continuous identity: tag, service, product history, and the protected-thing sentence. Hanging off the Vessel are five families. The Shell family holds courses, seams, coatings, and internals, each course typed with material, thickness history, and condition. The Nozzle family holds every penetration with its piping destination and retirement history, because nozzles outlive the units they served. The Foundation family holds geometry, survey epochs, and a settlement trend typed as moving, stopped, or accelerating. The Containment family holds dikes, double walls, pads, drainage paths, and fire protection, each typed with its failure-path behavior. The Evidence family holds inspection reports, photographs, thickness readings, and repair records, each linked to the exact shell course, nozzle, or foundation element it describes. Six families, one Vessel, and every document the site produces is a projection of them.
Invariants that surface contradictions early
The model earns its keep through invariants. Every Evidence item must resolve to a typed location — a shell course, a nozzle, a foundation point — so an orphaned photograph or an unlocated thickness reading becomes a visible defect instead of a buried file. Coating campaign dates must not overlap on the same course, which catches double-booked maintenance. Settlement trend type must agree with the direction of the last three survey epochs, so a narrative claiming stability cannot coexist with accelerating data. Every Nozzle whose served unit was retired must carry a blanking or removal entry, which surfaces live penetrations into dead piping. And every Containment element must reference a drainage decision, so no dike exists without a stated answer to where the liquid goes. Each invariant failure names the entity and the rule, turning review from excavation into triage.
Renderers: one model, many audiences
With entities and invariants in place, GenAnywhere renders audience-specific artifacts from the same source. The inspector's index projects only Evidence and its typed locations, ordered chronologically per course. The operator's turnover packet projects Vessel, Containment, and the plain-language operating layer, quoting the filler's notes verbatim. The regulator's summary projects Containment, Evidence counts, and invariant status, omitting commercial detail. The management review projects trend sentences — settlement direction, coating life remaining, inspection interval compliance — drawn from the same fields. Because every renderer reads the same entities, a new thickness reading propagates to the index, the packet, and the review in one motion; drift between documents becomes structurally impossible.
The asset pipeline for inspection evidence
Tank programs accumulate tens of thousands of evidence assets: internal photographs, ultrasonic thickness grids, coating holiday maps, drone shell surveys. GenAnywhere's pipeline registers each asset against the entity and location it depicts and the inspection epoch it belongs to, then enforces two rules. First, every asset cited in a rendered document must resolve to a registered Evidence item, so no orphaned figure survives a re-organization. Second, when a shell course's condition changes class between epochs, every asset registered to that course is flagged for re-review, guaranteeing the narrative and the photographs agree. The result is an evidence archive that remains queryable by course and epoch years after the inspector who captured it has moved on.
Why typed entities outlive their authors
The deepest argument for this architecture is organizational. Tank sites lose inspectors and operators faster than they replace them, and freeform reports carry their judgment out the door. A model with typed entities and invariants externalizes that judgment: the inspector's plain-language layer bound to a specific course is their expertise, still queryable a decade later. New staff inherit not a folder of PDFs but a vessel they can interrogate course by course, nozzle by nozzle, epoch by epoch. That is the difference between an archive and an institution, and it is the entire point of shaping storage tank content with GenAnywhere: the tank's intelligence outlives the people who kept it.
Top comments (0)