# Armeta — Full Content > Concatenated Markdown of the primary armeta.ai content layer, generated from the same source of truth as the live site. Source: https://armeta.ai Generated: 2026-08-06T10:22:32.417Z --- # Armeta — Engineering Intelligence Layer for Industrial Facilities Source: https://armeta.ai/ # The engineering intelligence layer for industrial facilities. Every critical engineering document in your facility's archive — P&IDs, piping isometrics, PFDs, line lists — contextualized, unified, and queryable. Deployed on your cloud or on-premise. In production today. CTA: Book a demo ## The Problem ### Your plant runs on engineering documents no software can read. P&IDs, piping isometrics, PFDs, and line lists are the master record of every operating facility — and the document set behind every MOC, HAZOP, LDAR survey, turnaround, revamp, and MTO. They sit siloed across formats, systems, and decades of archives, mostly as legacy PDFs that modern software can't read. Decades of CAD software was built to create them. None of it can read the archive you already have — so every downstream workflow starts from scratch, every time. ## Stats 01 — 80%+ of critical engineering documents in the US industrial installed base exist only as legacy PDFs — scanned paper, rasterized plots, and flat image files with no embedded metadata. 02 — 5 years the maximum interval between PHA revalidations mandated by OSHA 29 CFR 1910.119(e)(6). 03 — 70,000+ LDAR-regulated components traceable to P&IDs in a large US refinery. Sources: Armeta internal benchmarks · AFPM industry data · OSHA regulatory citations. ## Solution ### Upload a document. Get contextualized engineering data. Armeta's contextualization engine reads critical engineering documents — drawings and data tables — from the legacy PDFs your archive actually contains. No metadata, selectable text, or vector geometry required. The output is a unified engineering knowledge graph: equipment, lines, instruments, tags, spatial routing, cross-document connectivity, and revision deltas. Editable, auditable, delivered via API, JSON, or Excel. 01 — Ingest any document, any format. Legacy PDFs, scanned drawings, spreadsheets, vendor deliverables — all document types, all vintages. 02 — Extract symbols, tags, lines, and tabular records. Equipment, instruments, fittings, and welds on drawings; structured rows and columns on data tables. 03 — Contextualize entity resolution across drawings and data tables. The same line, tag, and equipment item carries one identity across documents. 04 — Compare every change between document revisions, flagged with source-region traceability and ready for audit. 05 — Deliver API, JSON, or Excel. Feeds your engineering systems, IT stack, and digital twins. CTA: See the platform in detail ### What Armeta reads Drawing — P&IDs Piping and instrumentation diagrams. Equipment, lines, instruments, tags, off-page connectors, and cross-drawing connectivity. Read more Drawing — Piping isometrics Spool-level pipe routing, fittings, welds, dimensions, and BOM extraction for fabrication and material take-off. Read more Drawing — PFDs Process flow diagrams. Major equipment, process streams, operating conditions, and material balances. Read more Data Table — Line lists Tabular line data: line numbers, sizes, materials, insulation, operating and design conditions. Reconciled against P&ID and isometric data. Read more New document types are added regularly. Contact us if your workflows depend on a type not listed here. ## Segments ### Built for every team that depends on engineering documents. For Operators Accelerate MTO, MOC, PHA revalidation, and LDAR workflows. Learn more For EPC Contractors Bid faster. Deliver cleaner. Protect margin on every project. Learn more For Engineering Firms Turn legacy drawings into structured engineering data. Learn more For EHS Consultants Defensible P&ID-to-component traceability for every compliance engagement. Learn more For OEMs Structured equipment data from your installed-base drawings. Learn more For Partners System integrators, vendors, resellers who serve the industrial market. Learn more ## Proof ### Validated where it matters. CERAWeek 2026 First place, Industrial Efficiency & Decarbonization track. Rice Alliance Energy Venture Day, Houston. Institutional backing Backed by a deep-tech venture fund, the founders of a unicorn company, and technical executives at global engineering firms. Investors and partners with deep technical and industrial experience. Built by operators Decades of building and scaling engineering and construction companies. Across global industrial facilities. Network Part of Alchemist Accelerator's Batch 41 — one of the most respected enterprise accelerators in the US — with a $1M pre-seed from its Gulf-region arm in Doha. Member of Greentown Labs, North America's largest climate-tech community, advancing decarbonization across heavy industry. CTA: See the proof ## Trust & Deployment ### Your drawings. Your environment. Your terms. Cloud Armeta-hosted, isolated per customer. Fastest time to value. On-premise Runs inside your network. Deployed with customers today. Private cloud Armeta-managed inside your own cloud environment. Security & Compliance SOC 2 Type I certified; Type II audit in progress (H1 2026). Data residency in US, EU, or customer-designated regions. Enterprise SSO, role-based access, full audit logs, and end-to-end encryption. CTAs: Explore our security practices · Vanta Trust Center ## Final CTA ### Your plant already has an engineering knowledge graph. It's just locked in PDF. See Armeta on your preconstruction workflow. CTA: Book a demo --- # Platform — Armeta Engineering Document Contextualization Engine Source: https://armeta.ai/platform/ # The platform that contextualizes every critical engineering document your plant depends on. Armeta's contextualization engine reads critical engineering documents — P&IDs, piping isometrics, line lists — from the legacy PDFs your archive actually contains: scanned paper, rasterized CAD plots, faded reproductions that smart-PDF tools can't touch. Purpose-built for industrial engineering. Not a generic OCR. Not an LLM wrapper. The engineering data foundation your facility has never had — from documents you already own. CTAs: Book a demo · See it in under 3 minutes ## How it works ### Five stages, one engineering knowledge graph. Every P&ID that passes through Armeta is processed in five stages. Each stage is inspectable, editable, and auditable. Every output is tied to a specific source region in the original drawing — drawing-traceable by design. #### Stage 01 · Ingest — Bring any document, in any format. Armeta ingests legacy PDFs and structured files regardless of origin, age, or document type: graphical drawings (P&IDs, piping isometrics, PFDs) and engineering data tables (line lists, data sheets). Scanned paper drawings from decades-old archives, rasterized CAD plots, flat image exports, faded reproductions, spreadsheet exports, and vendor deliverables. The ingest pipeline does not require selectable text, vector layers, or embedded tag data — it reads the legacy documents your archive actually contains. Your entire engineering archive, at scale. - File types: PDF (native + scanned), PNG, TIFF, JPG, XLSX - Batch ingest: Unit- or facility-scale archives - Typical throughput: Hundreds of documents / day #### Stage 02 · Extract — Symbols, tags, lines, and tabular records. The extraction engine adapts to each document type. For graphical drawings, it identifies every symbol, tag, annotation, dimension, fitting, and line. For engineering data tables, it parses tabular structure, column semantics, and row-level records. P&IDs yield equipment, instruments, and process connectivity. Piping isometrics yield spools, fittings, welds, dimensions, and fabrication BOMs. PFDs yield process streams and operating conditions. Line lists yield structured line-level attribute data — sizes, specs, conditions, and from-to connectivity. - Document types: P&IDs, isometrics, PFDs, line lists - Configures to: Your symbol library + conventions - Validation: Engineer-reviewed before delivery #### Stage 03 · Contextualize — Entity resolution across drawings and data tables. Armeta contextualizes data across document types and formats through entity resolution — the same line number, equipment tag, or instrument identifier is matched and reconciled across every drawing and data table in your archive. A line number on a P&ID resolves to its physical routing on the isometric, which reconciles against the line attributes on the line list. The result is a unified, multi-document-type engineering knowledge graph where graphical and tabular data reinforce each other — and discrepancies between them are surfaced automatically. - Scope: Unit-level or facility-level graph - Reconciliation: Tags and lines across every document - Discrepancies: Surfaced automatically #### Stage 04 · Compare — Every change between revisions, flagged and auditable. Armeta compares any two revisions of the same document — P&ID, isometric, or line list — and produces a structured delta: what was added, what was removed, what was modified. Every change is tied to a specific region on the source document and can be reviewed visually, exported as a change report, or fed directly into MOC documentation. This capability eliminates the "two prints and a red pen" reality of how most operators track drawing changes today. - Output: Structured delta, change report, MOC feed - Traceability: Every change document-region tagged #### Stage 05 · Deliver — Feeds your engineering systems, IT stack, and digital twins. Armeta's outputs are consumed via three channels: direct API integration, JSON exports for custom pipelines, or Excel deliverables for non-technical teams. The structured data is designed to feed into the systems your organization already runs — engineering document management, asset databases, digital twin platforms, and compliance software. Every output is versioned and traceable back to the source document and source region. The engineering knowledge graph Armeta builds is a living data foundation — it evolves with every document revision, every as-built update, and every new sheet added to your archive. Integrates with any downstream system via API. - Channels: REST API · JSON · Excel - Versioning: Source document + region retained ## Purpose-built ### Purpose-Built for Industrial Engineering Documents Armeta is not a generic document intelligence tool. The contextualization engine is purpose-built for the specific formats, symbology, tabular conventions, and domain logic of industrial engineering documents. It understands the semantic relationships between engineering entities — not just text on a page, but what a tag means, where a line routes, how a spec governs a component, and how a drawing connects to a data table. And it does not depend on smart PDFs. Most of the industrial engineering archive exists as scanned paper, rasterized CAD plots, and legacy image files — no embedded metadata, no selectable text, no vector layers. Armeta reads them all. ## What Armeta reads ### Every critical engineering document your facility depends on. Armeta is not a single-document-type tool. The contextualization engine adapts to each document's format — graphical or tabular — and contextualizes them into a unified engineering knowledge graph. DRAWINGS P&IDs — Piping & Instrumentation Diagrams The master schematic of your process. Armeta extracts equipment, lines, instruments, tags, off-page connectors, and builds cross-drawing connectivity across your entire facility archive. Piping Isometrics The fabrication and construction document for every pipe spool. Armeta extracts pipe routing, fittings (elbows, tees, reducers, flanges), welds, dimensions, materials, and generates structured BOMs for material take-off and fabrication tracking. PFDs — Process Flow Diagrams The high-level process overview showing major equipment, process streams, and operating conditions. Armeta extracts equipment blocks, stream data, temperatures, pressures, and flow rates. DATA TABLES Line Lists Tabular engineering records listing every line in a process unit: line number, size, material spec, insulation, operating and design conditions, from-to connectivity, and P&ID reference. Armeta extracts and structures line list data and reconciles it against P&ID and isometric data. New document types added regularly. Contact us if your workflows depend on a type not listed here. ## Accuracy and validation ### Accuracy you can put in a contract. Every extraction Armeta delivers is validated by our engineering team before it reaches you. This is not a pass-through of raw model output. It is a deliverable with an accuracy commitment. Accuracy metrics are established against your own documents and reported with the validated deliverable. - Visual review of every drawing — Every extracted graph is reviewed by an engineer against the source drawing before delivery. - Statistical accuracy sampling — Equipment, line, and instrument-level sampling against ground truth on every engagement. - Cross-drawing connectivity validation — Off-page connectors reconciled across the full set; dangling references flagged. - Revision delta review — Change reports reviewed against the source drawings before MOC packages are produced. ## Deployment ### Your drawings. Your environment. Your terms. Three deployment modes, chosen to match the security and governance constraints your engineering records actually live under. #### Mode 01 · Cloud — Fastest time to value Armeta-hosted, isolated per customer. Your engineering documents and extracted data remain segregated from every other customer environment. - Isolated tenant per customer - Data residency US, EU, or customer-designated region - Production-ready in days, not months #### Mode 02 · On-premise — Your network, your perimeter Armeta's contextualization engine runs inside your network. Your documents never leave your environment. Deployed with customers today under data residency and air-gap requirements. - Documents never leave the customer network - Air-gap-compatible deployment - Suitable for classified processes and strict residency policies #### Mode 03 · Private cloud — Managed inside your tenant Armeta-managed deployment inside your own cloud tenant. Cloud operational model, customer-controlled perimeter. - Customer-controlled cloud perimeter - Managed service lifecycle - Fits existing cloud governance frameworks ## Security ### Built for the facilities that cannot afford to get this wrong. Armeta meets the standards your security team expects. For security questionnaires, due diligence requests, or deeper technical detail, contact the Armeta team. - SOC 2 Type II audit — Independent audit in progress, completing H1 2026. - Data residency — US, EU, or customer-designated region. - Enterprise SSO — Integrates with your existing identity provider (SAML / OIDC). - Role-based access control — Granular permission management across users, projects, and data scopes. - End-to-end encryption — In transit and at rest, using industry-standard ciphers. - Full audit trail — Every action logged and retained for compliance purposes. ## Integration ### Fits the engineering stack you already run. Armeta's outputs are designed to feed the systems your organization already uses. Integration is delivered via API, JSON export, or structured Excel files. For specific integration patterns and deployment guides, see the Resources section. - Engineering document management systems - Asset management and maintenance platforms - Process historian and operations data systems - Digital twin platforms - Process safety management software - LDAR compliance databases - ERP and procurement systems - Custom pipelines via API or JSON ## Closing CTA ### See this workflow on your project data. Bring drawings, standards, catalogs, and specifications from a live project. See how Armeta checks, structures, searches, and generates outputs in the context your team works in. CTA: Book a demo --- # P&ID Contextualization — Structured Engineering Data from Piping and Instrumentation Diagrams Source: https://armeta.ai/platform/pids/ # Upload a P&ID. Get a structured, connected engineering knowledge graph. Platform · P&IDs Armeta's contextualization engine reads any legacy PDF P&ID — scanned paper, rasterized CAD plots, flat image exports, faded reproductions from decades-old archives — and turns it into structured, connected engineering data. Cross-drawing connectivity is resolved automatically, so off-page connectors are reconciled across your entire drawing set into a facility-wide engineering knowledge graph. CTA: Book a demo ## What Armeta extracts ### Every entity on the P&ID, identified and connected. The P&ID is the master schematic of your process. Armeta extracts every operationally meaningful entity on the sheet — not just text, but the engineering objects that text represents. #### Equipment items Vessels, columns, exchangers, drums, pumps, compressors, packages — every tagged equipment item identified, classified, and linked to its source region. #### Piping lines Every line on every sheet, with line number, size, spec, service, and routing parsed from the line label and resolved against your numbering convention. #### Instruments Transmitters, indicators, switches, controllers, analyzers — both inline and panel-mounted — with their loop tags and signal connections. #### Control valves Control valves, on/off valves, motorized valves, and their actuators, identified by tag and resolved to their controlling instrument loop. #### Safety devices Pressure relief valves, rupture disks, flame arrestors, and emergency isolation valves — captured with their setpoints and the systems they protect. #### Tags & annotations Every alphanumeric tag, callout, note, and revision cloud, captured with its position so engineers can audit extractions against the source drawing. #### Off-page connectors Every off-sheet reference identified, paired across the drawing set, and resolved into directional connections in the facility graph. #### Title-block metadata Drawing number, revision, sheet, project, area, unit — pulled directly from the title block and used as the indexing key for every other extraction. ## Cross-drawing connectivity ### 50 to 200+ sheets per unit, reconciled into one facility graph. A single process unit lives across dozens to hundreds of P&ID sheets. The engineering reality of the unit is the connectivity between those sheets — not the contents of any one drawing in isolation. Armeta resolves cross-sheet connectivity automatically. Off-page connectors are identified, paired, and reconciled into a directional graph that spans the full drawing set. Stage 01 — Per-sheet extraction Symbols, tags, and lines parsed sheet by sheet. Each sheet is processed independently. Equipment, lines, instruments, and off-page connectors are identified at the symbol level, with every extraction tied back to a specific region on the source drawing. Stage 02 — Connector identification Off-page connectors picked up wherever they live. Off-page connectors are identified regardless of style: triangle, arrow, circle, or vendor-specific. Each connector carries its referenced drawing, sheet, and line number into the graph so the next step has unambiguous handles to reconcile against. Stage 03 — Cross-sheet reconciliation 50 to 200+ sheets resolved into one connected graph. Connectors are matched across the full drawing set. A line leaving sheet 12 toward sheet 34 is paired with the matching connector on sheet 34. Conflicts, dangling references, and revision mismatches are surfaced as discrepancies rather than silently dropped. Stage 04 — Facility graph assembly One queryable map of every line, every tag, every connection. The reconciled set becomes a single, navigable engineering knowledge graph. Equipment tags trace back to source drawings, lines trace end-to-end through every sheet they touch, and the whole facility is addressable as structured data. ## Cross-document context ### How P&ID data contextualizes against isometrics and line lists. The P&ID is the anchor document, but it is not the only record. Armeta resolves entities across documents so the same line, the same tag, and the same equipment item carry one identity across drawings and data tables. Stage 01 — Line-number resolution The line on the P&ID is the line on the isometric. Line numbers are parsed using your numbering convention and used as the primary entity key across documents. The same line on a P&ID, an isometric, and a line list resolves to a single record in the graph. Stage 02 — Equipment-tag matching Tag identity, not tag substring. Equipment tags are normalized and matched against isometric title-block references and line list equipment columns. Soft matches (formatting variants, leading zeros, hyphens) are reconciled; hard mismatches are flagged for review rather than guessed. Stage 03 — Attribute reconciliation Where the documents disagree, you find out. Sizes, specs, services, and operating conditions are compared across documents. A line tagged 6" on the P&ID and 8" on the line list is surfaced as a discrepancy, not silently averaged. The graph keeps both values with their source documents. ## Workflows enabled ### What structured P&ID data unlocks. Once the P&ID is structured and connected, every downstream workflow stops starting from scratch. The engineering knowledge that used to be re-derived for every project becomes a queryable data layer. #### Automated MTO Aggregate piping, valve, and instrument counts straight from the extracted P&ID — bid-grade in days, not weeks. #### MOC reconciliation Compare any two P&ID revisions and produce a structured delta tied to source-drawing regions, ready for the MOC package. #### PHA / HAZOP revalidation Provide reviewers a queryable, current snapshot of every node, line, and safeguard before the revalidation meeting. #### LDAR component inventory Generate a defensible component inventory from the actual P&IDs, with traceability back to the drawing region for every flange, valve, and connector. #### Brownfield scope definition Identify which lines, equipment, and systems are affected by a modification scope before the field walk-down — driven by structured P&ID connectivity. #### As-built reconciliation Reconcile field-marked redlines against the latest issued P&IDs, with discrepancies surfaced as structured change records. ## Legacy PDF handling ### The drawings your archive actually contains. Armeta does not require smart PDFs. The vast majority of the global P&ID archive exists as flat images: scanned paper, rasterized CAD plots, and faded reproductions. No embedded metadata, no selectable text, no vector layers. The contextualization engine reads them all. If your team is working from the documents you actually have rather than an idealized smart-PDF set, Armeta meets you where the archive lives. #### Scanned paper drawings Decades-old paper P&IDs, scanned at any resolution, with smudges, fold lines, and stamp marks — read as-is. #### Rasterized CAD plots Flat-image PDF exports from legacy CAD systems with no embedded metadata, no selectable text, and no vector layer. #### Degraded reproductions Photocopies of photocopies, faded blueprints, low-contrast microfilm scans — the documents your archive actually contains. #### Mixed-vintage archives Sets that span symbol conventions across decades and authoring tools. Armeta adapts to your conventions sheet by sheet. ## Accuracy and validation ### Accuracy you can put in a contract. Every P&ID extraction Armeta delivers is validated by our engineering team before it reaches you. Accuracy metrics on your own drawings are reported with the validated deliverable. #### Engineer-reviewed extraction Every extracted graph is reviewed by an Armeta engineer against the source drawing before delivery. Not raw model output. #### Source-linked traceability Every entity in the graph is linked back to the exact region on the source sheet it was extracted from. Auditable, click-through, defensible. #### Statistical accuracy sampling Equipment-, line-, and instrument-level sampling against ground truth on every engagement. Accuracy metrics produced on your own drawings. #### Revision-delta review Change reports between revisions are reviewed against both source drawings before MOC packages are produced. ## Deployment ### Your drawings. Your environment. Your terms. Three deployment modes, chosen to match the security and governance constraints your engineering records actually live under. Mode 01 · Cloud — Fastest time to value Armeta-hosted, isolated per customer. Your engineering documents and extracted data remain segregated from every other customer environment. - Isolated tenant per customer - Data residency US, EU, or customer-designated region - Production-ready in days, not months Mode 02 · On-premise — Your network, your perimeter Armeta's contextualization engine runs inside your network. Your documents never leave your environment. Deployed with customers today under data residency and air-gap requirements. - Documents never leave the customer network - Air-gap-compatible deployment - Suitable for classified processes and strict residency policies Mode 03 · Private cloud — Managed inside your tenant Armeta-managed deployment inside your own cloud tenant. Cloud operational model, customer-controlled perimeter. - Customer-controlled cloud perimeter - Managed service lifecycle - Fits existing cloud governance frameworks ## Related document types ### One contextualization engine. Four document types. #### Piping isometrics Pipe routing, fittings, welds, dimensions, and BOMs reconciled against P&IDs and line lists. Read more → #### PFDs Equipment blocks, process streams, and operating conditions joined to detailed engineering data. Read more → #### Line lists Tabular line records: numbers, sizes, specs, conditions, and from-to data, reconciled to drawings. Read more → ## Closing CTA ### See P&IDs connected in your facility model. Walk through cross-sheet connectivity, structured equipment and line data, and revision comparison in a scoped session with your engineering team. CTA: Book a demo --- # Piping Isometric Contextualization — Automated Spool BOMs and Fabrication Data Source: https://armeta.ai/platform/piping-isometrics/ # Upload a piping isometric. Get a structured fabrication BOM. Platform · Piping Isometrics Armeta's contextualization engine reads any PDF piping isometric — scanned paper, hand-drawn legacy drawings, rasterized CAD plots, flat image exports — and outputs structured spool data: pipe routing, fittings, welds, dimensions, materials, and quantities. The output feeds fabrication tracking, MTO, and procurement, and it's contextualized against your P&ID and line list data so the isometric becomes part of the unified engineering knowledge graph. CTA: Book a demo ## What Armeta extracts ### Every component on every spool, captured and structured. The isometric is the most granular piping document you have. Armeta extracts the engineering objects on it — not just text, but pipe geometry, components, welds, and the BOM — with each entity tied back to the source region on the drawing. #### Pipe routing North arrow, elevation changes, and coordinates parsed from the isometric projection so the routing is preserved as structured data — not just an image. #### Fittings Elbows, tees, reducers, flanges, and inline valves identified by symbol and tagged with size, type, and material spec. #### Welds Field welds, shop welds, and weld numbers captured with their type and position. Feeds straight into weld maps and NDT planning. #### Dimensions Cut lengths, center-to-face, and center-to-center dimensions extracted with their reference points so spool fabrication data is shop-ready. #### Materials & line numbers Pipe spec, line number, service, and any spec breaks captured per segment, with the line number resolved against the P&ID and line list. #### BOM / parts list The bill of materials on the isometric is parsed into a structured table: every component with quantity, description, spec, size, and rating. #### Title-block reference Drawing number, revision, sheet, project, and the line-number tie back to the P&ID — used as the indexing key for every other extraction. ## Cross-document context ### How isometric data contextualizes against P&IDs and line lists. The isometric does not stand alone. It is the spatial expression of a line that already exists on the P&ID and in the line list. Armeta resolves the same line across documents so connectivity, attributes, and BOM data live on one record — not three siloed copies. The result: every fitting, every weld, and every dimension on the isometric is unambiguously attached to a line that lives end-to-end in the engineering knowledge graph. Stage 01 — P&ID line resolution The same line, the same identity, across documents. The line number on the isometric title block is matched against the same line on the P&ID. The schematic-level connectivity from the P&ID and the spatial routing from the isometric resolve to one record in the engineering knowledge graph. Stage 02 — Line-list attribute reconciliation Sizes, specs, and conditions cross-checked, not assumed. Spec, size, and design conditions on the isometric are reconciled against the line list. Where attributes disagree, both values are retained with their source documents and surfaced as a structured discrepancy — never silently averaged. Stage 03 — BOM aggregation into facility MTO Spool BOMs, rolled up to the unit and to the facility. Each isometric's BOM is the atomic unit of the piping MTO. Armeta aggregates BOMs across every isometric in your set, normalizes descriptions against your material catalogue, and produces an MTO that ties back to the source spool for every line item. ## Workflows enabled ### What structured isometric data unlocks. Once isometric content is structured and contextualized, the workflows that depend on it stop being manual roll-ups and become queryable. #### Automated MTO Aggregate spool BOMs across the full isometric set into a clean, deduplicated piping MTO ready for procurement. #### Fabrication tracking Spool-level structured data feeds shop tracking systems with weld counts, fitting counts, and cut lengths from day one. #### As-built reconciliation Compare issued isometrics against field-marked redlines, surface every change as a structured delta, and feed the as-built package directly. #### Procurement aggregation Component-level data normalized across thousands of isometrics so procurement runs on real, unit-traceable counts instead of hand totals. ## Legacy PDF handling ### The isometrics your archive actually contains. Most piping isometrics in operating facilities are not smart PDFs. They are scanned paper, hand-drawn legacy sheets, rasterized CAD plots, and flat image exports — with no embedded metadata, no selectable text, and no vector layer. Armeta reads them as-is. No conversion step, no pre-vectorization, no requirement to re-author the drawing in a modern CAD tool before it can be processed. ## Accuracy and validation ### Accuracy you can put in a contract. Every isometric extraction Armeta delivers is validated against the source drawing by our engineering team before it reaches you. Accuracy metrics on your own isometrics are reported with the validated deliverable. #### Engineer-reviewed extraction Every isometric extraction is reviewed by an Armeta engineer against the source drawing before delivery. Not raw model output. #### Source-linked traceability Every component, weld, and dimension in the structured output links back to the exact region on the source isometric it was extracted from. #### BOM-against-drawing sampling Random spool sampling against ground-truth BOMs on every engagement. Accuracy metrics produced on your own isometrics. #### Cross-document discrepancy reports Discrepancies between the isometric BOM, the P&ID, and the line list are surfaced as structured reports rather than absorbed silently. ## Deployment ### Your isometrics. Your environment. Your terms. Three deployment modes, chosen to match the security and governance constraints your engineering records actually live under. Mode 01 · Cloud — Fastest time to value Armeta-hosted, isolated per customer. Your engineering documents and extracted data remain segregated from every other customer environment. - Isolated tenant per customer - Data residency US, EU, or customer-designated region - Production-ready in days, not months Mode 02 · On-premise — Your network, your perimeter Armeta's contextualization engine runs inside your network. Your documents never leave your environment. Deployed with customers today under data residency and air-gap requirements. - Documents never leave the customer network - Air-gap-compatible deployment - Suitable for classified processes and strict residency policies Mode 03 · Private cloud — Managed inside your tenant Armeta-managed deployment inside your own cloud tenant. Cloud operational model, customer-controlled perimeter. - Customer-controlled cloud perimeter - Managed service lifecycle - Fits existing cloud governance frameworks ## Related document types ### One contextualization engine. Four document types. #### P&IDs Equipment, lines, instruments, tags, and cross-drawing connectivity from any legacy PDF. Read more → #### PFDs Equipment blocks, process streams, and operating conditions joined to detailed engineering data. Read more → #### Line lists Tabular line records: numbers, sizes, specs, conditions, and from-to data, reconciled to drawings. Read more → ## Closing CTA ### Turn isometrics into structured fabrication data. See spool-level BOMs reconciled with P&IDs and line lists—structured, traceable, and ready for estimating and procurement. CTA: Book a demo --- # PFD Contextualization — Structured Process Data from Process Flow Diagrams Source: https://armeta.ai/platform/pfds/ # Upload a PFD. Get structured process stream and equipment data. Platform · PFDs Armeta's contextualization engine reads any PDF Process Flow Diagram — scanned legacy drawing, rasterized CAD plot, flat image export, vendor deliverable — and extracts structured process data: equipment blocks, stream connections, flow rates, temperatures, pressures, compositions, and material balances. The output is contextualized against your P&ID and line list data, so high-level process intent connects to the detailed engineering record. CTA: Book a demo ## What Armeta extracts ### The process design, captured as data. The PFD is the document that explains what the process does. Armeta extracts every entity on the sheet so that intent becomes queryable rather than locked in a flat image. #### Major equipment blocks Vessels, columns, exchangers, drums, compressors, pumps, packages — every tagged equipment block on the PFD identified, classified, and resolved against your tag register. #### Process stream connections Every stream between equipment, with stream number, source, destination, and direction parsed into structured connectivity ready for graph assembly. #### Flow rates Mass and volumetric flow rates per stream extracted with units normalized so the structured output is queryable across vintages and authoring conventions. #### Temperatures Stream temperatures captured per stream and reconciled against design and operating columns on the line list where present. #### Pressures Stream pressures captured per stream, with units normalized and any operating-vs-design distinctions preserved. #### Compositions Stream compositions parsed from the stream-data table, with components normalized against your composition register where one exists. #### Material & energy balances Mass and energy balance data — whether shown on the PFD itself or referenced as a separate HMB — structured per stream and tied to the source. #### Battery limits & unit interfaces Off-PFD references and battery-limit connections to other units captured as structured edges so the graph spans facility-wide rather than stopping at the unit boundary. ## Cross-document context ### How PFD data contextualizes against P&IDs and line lists. The PFD is the highest-level engineering document of the process. The P&ID and the line list are the granular detail. Armeta resolves them into a single engineering knowledge graph so design intent and engineering record are addressable as one model. Equipment tags on the PFD resolve to their detailed representations on the P&ID, and stream data reconciles against line list attributes — with discrepancies surfaced for engineering review. Stage 01 — Equipment-tag resolution to P&ID Major equipment, joined to its detailed representation. Every equipment block on the PFD is matched to its detailed depiction on the P&ID. The PFD-level vessel becomes the same entity as the P&ID's vessel, with all of the P&ID's nozzles, instruments, and trim surfaced under it. Stage 02 — Stream-to-line reconciliation Streams resolved against line list attributes. PFD streams are reconciled against the line list. Where a PFD stream corresponds to one or more line-list lines, attributes — size, spec, service, design conditions — are cross-checked. Mismatches are surfaced as discrepancies, not silently absorbed. Stage 03 — Operating-condition cross-check Design intent versus engineering record, side by side. Operating conditions on the PFD are compared against design and operating values on the line list and against pressure/temperature annotations on the P&ID. The graph keeps each value with its source so engineers reconcile the differences with full evidence. ## PFD vs. P&ID ### Two documents. One process. Different things to capture. The PFD and the P&ID are not interchangeable. They describe the same process at different levels of detail, and each captures what the other deliberately leaves out. Both are needed to understand the unit — and both belong in the engineering knowledge graph. What the PFD captures System-level process intent. #### System-level overview Major equipment, principal streams, and how the process flows at the unit level. The document an engineer reads to answer "what does this process do?" #### Material & energy balances Mass and energy flows per stream. The quantitative backbone of the process design — typically absent from the P&ID. #### Stream compositions Component breakdowns per stream. The basis for utility loading, environmental compliance, and downstream specification. What the P&ID captures Component-level engineering reality. #### Every valve and instrument Block valves, control valves, check valves, isolation valves — every device is on the P&ID. The PFD shows none of them. #### Drains, vents, and utilities Local drains, vents, sample points, and minor utility connections live only on the P&ID. The PFD aggregates them away. #### Tag-level identity Equipment, line, and instrument tags resolved at full granularity. The PFD names equipment but does not tag every component beneath it. ## Workflows enabled ### What structured PFD data unlocks. Once the PFD is structured and contextualized against the P&ID and line list, system-level engineering decisions stop being driven by re-reading flat images. #### FEED verification Confirm the PFD against the heat and material balance and against the developing P&IDs during detailed engineering — without re-keying stream data into a spreadsheet. #### Brownfield process understanding Reconstruct the process intent of an operating unit from its PFD before scoping a modification, so the field team starts with system-level context. #### Process safety reviews Provide HAZOP and PHA reviewers with a structured PFD-level snapshot of process intent, equipment, and stream conditions before they open the P&IDs. #### HMB reconciliation Reconcile the heat and material balance against the structured PFD streams to surface unit-level imbalances early, when they are still inexpensive to fix. ## Accuracy and validation ### Accuracy you can put in a contract. Every PFD extraction Armeta delivers is validated against the source drawing by our engineering team before it reaches you. Accuracy metrics on your own PFDs are reported with the validated deliverable. #### Engineer-reviewed extraction Every PFD extraction is reviewed by an Armeta engineer against the source drawing before delivery. Not raw model output. #### Source-linked traceability Every equipment block, stream, and operating-condition value links back to the exact region on the source PFD it was extracted from. #### Stream-data cross-check Stream-data tables are cross-checked against on-PFD annotations and against any referenced heat and material balance — discrepancies surfaced rather than averaged. #### Schema fidelity Your stream-data schema is preserved. Columns are not dropped, not renamed, and not silently merged — the structured output round-trips cleanly back to your master. ## Deployment ### Your PFDs. Your environment. Your terms. Three deployment modes, chosen to match the security and governance constraints your engineering records actually live under. Mode 01 · Cloud — Fastest time to value Armeta-hosted, isolated per customer. Your engineering documents and extracted data remain segregated from every other customer environment. - Isolated tenant per customer - Data residency US, EU, or customer-designated region - Production-ready in days, not months Mode 02 · On-premise — Your network, your perimeter Armeta's contextualization engine runs inside your network. Your documents never leave your environment. Deployed with customers today under data residency and air-gap requirements. - Documents never leave the customer network - Air-gap-compatible deployment - Suitable for classified processes and strict residency policies Mode 03 · Private cloud — Managed inside your tenant Armeta-managed deployment inside your own cloud tenant. Cloud operational model, customer-controlled perimeter. - Customer-controlled cloud perimeter - Managed service lifecycle - Fits existing cloud governance frameworks ## Related document types ### One contextualization engine. Four document types. #### P&IDs Equipment, lines, instruments, tags, and cross-drawing connectivity from any legacy PDF. Read more → #### Piping isometrics Pipe routing, fittings, welds, dimensions, and BOMs reconciled against P&IDs and line lists. Read more → #### Line lists Tabular line records: numbers, sizes, specs, conditions, and from-to data, reconciled to drawings. Read more → ## Closing CTA ### Connect process intent to detailed engineering. See equipment, streams, and balances structured from PFDs and linked to P&IDs and line lists in one connected model. CTA: Book a demo --- # Line List Contextualization — Structured Piping Data from Engineering Tables Source: https://armeta.ai/platform/line-lists/ # Upload a line list. Get structured, reconciled line data. Platform · Line Lists Armeta parses engineering line lists — whether PDF tables, Excel exports, or scanned tabular documents — into structured line-level records: line numbers, sizes, material specs, insulation, design and operating conditions, from-to connectivity, and P&ID references. Line list data is contextualized against P&ID and isometric data to surface discrepancies and build the complete engineering knowledge graph. CTA: Book a demo ## What Armeta extracts ### Every column, every row, every attribute. The line list is the structured complement to the graphical record. Armeta preserves your schema and parses each column into queryable fields — including the columns that are usually flattened into free text. #### Line number Parsed using your numbering convention. Service codes, size, material class, area, and sequential identifier separated into structured fields. #### Nominal diameter Captured per row with units normalized — inches, millimeters, mixed-unit imports — so the structured output is queryable across vintages. #### Pipe spec / material class Material class assigned per line (e.g. A1A, B2B) extracted and resolved against your pipe specification register. #### Insulation Insulation type and thickness captured where present, including heat-tracing notes flagged as separate structured attributes. #### Design pressure & temperature Captured separately from operating values so any downstream stress, integrity, or compliance workflow has the right column to read. #### Operating pressure & temperature Operating-condition columns parsed and reconciled against the design columns and the source P&ID where applicable. #### Fluid service Service classification (hydrocarbon, hydrogen, sour, utility, etc.) captured per line and used for downstream regulatory tagging. #### From-to connectivity Origin and destination equipment tags or off-page references parsed into a structured connectivity column ready for graph assembly. #### P&ID reference Source P&ID drawing number per line — the join key used to reconcile the line list against the rest of the engineering archive. #### Remarks & special notes Heat tracing, slope requirements, NDT flags, and other free-text remarks structured as discrete tags rather than dropped on the floor. ## Cross-document reconciliation ### The line list as the reconciliation layer. A line that exists on a P&ID should appear on the line list. A line on the line list should have a corresponding isometric. Discrepancies between these three sources almost always indicate either a documentation error or an undocumented field modification — both of which matter. Armeta runs the reconciliation automatically and surfaces the disagreements as structured reports for engineering review. Stage 01 — Line-number entity resolution Every row, an addressable entity in the graph. Each line-list row is parsed against your numbering convention and promoted to a first-class entity. Soft variants (formatting, leading zeros, hyphens) are normalized; hard mismatches are flagged for review rather than silently merged. Stage 02 — P&ID-to-line-list match Schematic and tabular records, joined on identity. Every line on the line list is matched to its appearance on the P&ID. A line on the list with no P&ID presence is surfaced. A line on the P&ID with no list entry is surfaced. The two sources cross-validate each other rather than living in parallel. Stage 03 — Isometric verification Spatial reality, reconciled against the data table. Where isometrics exist, the line list is reconciled against the spatial record. Spec, size, and service are cross-checked spool by spool so the line list reflects what was actually fabricated and installed. Stage 04 — Discrepancy surfacing Disagreements made visible, not papered over. Where the P&ID, isometric, and line list disagree, Armeta produces a structured discrepancy report with both values and their source documents. Reconciliation is a decision your engineering team makes with full evidence, not a guess the model makes for you. ## Workflows enabled ### What structured line list data unlocks. Once the line list is structured and reconciled against the graphical record, the workflows that depend on it stop being spreadsheet archaeology. #### MTO verification Cross-check piping MTO produced from isometrics against the line list to catch missing lines, miscounted segments, or spec mismatches before the bid lands. #### Brownfield scope definition Filter the line list to the lines that touch a modification scope, then trace each line to its P&ID and isometric to size the work accurately. #### Data migration Migrate legacy line list spreadsheets and PDF tables into a modern engineering data hub or asset master with field-level traceability. #### Stress analysis line identification Surface the lines that meet design-condition thresholds for pipe stress review without manually filtering thousand-row spreadsheets. ## Format handling ### The line lists your archive actually contains. Real-world line lists come in every format engineering data has ever lived in: native Excel exports with merged headers, PDF tables with image-baked text, and scanned tabular documents from filing cabinets. Armeta reads them all. No re-keying. No template forcing. Your line-list schema is what comes out the other side — cleanly structured and joined to the rest of the engineering knowledge graph. ## Accuracy and validation ### Accuracy you can put in a contract. Every parsed line list Armeta delivers is validated against the source document by our engineering team before it reaches you. Accuracy metrics on your own line lists are reported with the validated deliverable. #### Engineer-reviewed parsing Every parsed line list is reviewed by an Armeta engineer against the source document before delivery. Not raw model output. #### Source-cell traceability Every structured field links back to the exact cell or region on the source line list — auditable, click-through, defensible. #### Cross-document discrepancy reports Differences between the line list, the P&ID, and the isometric are surfaced as structured reports so engineering reconciles them with full evidence. #### Schema fidelity Your line-list schema is preserved. Columns are not dropped, not renamed, and not silently merged — the structured output round-trips cleanly back to your master. ## Deployment ### Your line lists. Your environment. Your terms. Three deployment modes, chosen to match the security and governance constraints your engineering records actually live under. Mode 01 · Cloud — Fastest time to value Armeta-hosted, isolated per customer. Your engineering documents and extracted data remain segregated from every other customer environment. - Isolated tenant per customer - Data residency US, EU, or customer-designated region - Production-ready in days, not months Mode 02 · On-premise — Your network, your perimeter Armeta's contextualization engine runs inside your network. Your documents never leave your environment. Deployed with customers today under data residency and air-gap requirements. - Documents never leave the customer network - Air-gap-compatible deployment - Suitable for classified processes and strict residency policies Mode 03 · Private cloud — Managed inside your tenant Armeta-managed deployment inside your own cloud tenant. Cloud operational model, customer-controlled perimeter. - Customer-controlled cloud perimeter - Managed service lifecycle - Fits existing cloud governance frameworks ## Related document types ### One contextualization engine. Four document types. #### P&IDs Equipment, lines, instruments, tags, and cross-drawing connectivity from any legacy PDF. Read more → #### Piping isometrics Pipe routing, fittings, welds, dimensions, and BOMs reconciled against P&IDs and line lists. Read more → #### PFDs Equipment blocks, process streams, and operating conditions joined to detailed engineering data. Read more → ## Closing CTA ### Reconcile line lists with drawings automatically. See tabular line data structured and checked against P&IDs and isometrics, with discrepancies surfaced and traced to source. CTA: Book a demo --- # Armeta Products — AI Systems for the Built World Source: https://armeta.ai/products/ # Six products. One engineering understanding. AI systems for the documents, standards, estimates, and models that move projects from planning to execution. ## The Armeta product line - Armeta Smeta — AI-native cost estimating tool - Armeta Permit — Automated building permitting system - Armeta P&ID — Turns legacy process drawings into a connected model of the facility - Armeta Codes — Answers questions about construction codes, citing the exact document and clause. - Armeta Materials — Search construction products and validate specifications against official catalog codes. - Armeta CAD — AI-native CAD tool. Coming soon. --- # Armeta Smeta — AI Cost Estimating Source: https://armeta.ai/products/smeta/ # Estimate the work. Defend the number. Armeta Smeta brings estimate development, checking, collaboration, and issue into one web workspace. It connects project documentation, quantities, applicable rates, and requirements so every position can be reviewed against the source behind it. ## One estimate. Every source behind it. Develop quantities, apply rates, review findings, and issue the estimate without breaking the connection between the number and the documentation that supports it. Smeta works with Armeta Materials, Armeta Codes, Armeta P&ID, and Armeta Permit. ## A modern workspace for estimating teams. - One browser-based workspace - Shared project collaboration - Current regulatory and organization-specific rate libraries - Estimate imports, exports, and printed forms - Reusable templates and project sections - Centralized library and rule updates ## From project documentation to an issued estimate. 1. Document intake — drawings, specifications, schedules, existing estimates, and scope documents establish the pricing basis. 2. Quantity build — quantities are calculated from source documentation and prepared for specialist review. 3. Rate application — applicable libraries, organization rates, price lists, and project rules are resolved against the quantities. 4. Specialist review — arithmetic, duplicates, rate codes, library editions, omissions, and source consistency are checked. 5. Issue and exchange — the controlled estimate is delivered for approval, procurement, contracting, or owner verification. ## AI does the repetitive work. Specialists make the decision. - Ask the regulatory base in plain language and receive an answer with the source document and clause. - Build a draft estimate from drawings, including reviewable quantities. - Check an estimate against drawings, specifications, and schedules, then return an itemized review protocol. ## A review protocol, not a confidence score. Smeta checks arithmetic, duplicate positions, rate codes, rate-library editions, missing positions, and consistency with source documentation. Findings identify what should be checked and where so the responsible specialist can confirm each result. ## One product, adapted to the market where it runs. Applicable rate libraries, rules, forms, interchange formats, security requirements, and deployment models are configured for each jurisdiction and organization. Smeta supports cloud and on-premise deployment, encrypted data, account-based access, organization-specific libraries, and specialist confirmation of AI-produced results. ## Who uses it - Engineering firms - Construction firms - Asset owners - Governments and public-sector customers CTA: Book a demo --- # Armeta Permit — Automated Building Permitting Source: https://armeta.ai/products/permit/ # Catch the formal defects before the review does. Every submission package is hundreds or thousands of pages of mixed documentation. Armeta Permit reads that package — including scans, stamps, seals, and tables — classifies what it is looking at, and returns a structured review: completeness, validity, ownership, authenticity of credentials, and cross-document consistency. The specialist makes the decision. The system prepares the evidence. Deployed in production with a national construction expertise authority. ## Proven where the queue is real. - 1,309 projects received by the system - 864 projects fully reviewed in production - 6 minutes average review time per project - Completeness cycle compressed from 5 working days to 2 ## The expensive failure is usually formal. - Most packages fail the first gate - Formal defects burn calendar time - Experts should spend time on engineering, not mechanical comparison ## An assistant, not a judge. - Document classification - Completeness against the matrix - Project ownership - Validity and currency - Signatures, seals, and credentials - Cross-document consistency Every finding cites a page, sheet, or clause. Final authority stays with the human reviewer. ## From upload to an exportable review protocol. 1. Upload — bring the full package as it will be submitted. 2. Classify — know what every file is. 3. Check — run the formal gates that usually return a package. 4. Report — hand the specialist a review protocol, not a black-box score. ## One platform. Four modules. One analysis cycle. 1. Completeness — in production. 2. Analyst — structure, graph, semantic search, title-block control. 3. Expert — section-level engineering checks. 4. Estimates — arithmetic, rates, specification reconciliation, economic justification. Language models handle classification, extraction, and matching of wording. Deterministic algorithms own arithmetic and rule checks. ## Built on the logic of expertise. Jurisdiction-specific matrices, current and archival editions, transparency to applicants and reviewers, on-premise deployment, continuous improvement from live packages, and connections to Armeta Codes, Armeta Materials, and Smeta. ## Who uses it - Engineering firms - Construction firms - Asset owners - Governments and regulators CTA: Book a demo --- # Armeta P&ID — One Connected Facility Model Source: https://armeta.ai/products/pid/ # One connected model of the facility. A facility's process documentation is spread across thousands of drawings and tables produced over decades. Armeta reads them together — P&IDs, piping isometrics, PFDs, and line lists — and resolves them into one model where every equipment item, line, and instrument has a single identity, wherever it appears. CTA: Book a demo ## Every entity identified, connected, and traceable Equipment, piping lines, instruments, loops, valves, safety devices, tags, annotations, off-page connectors, title-block metadata, and revision changes. ## Thousands of documents become one facility model Per-sheet extraction → connector resolution → cross-sheet reconciliation → facility model. ## What the connected model unlocks Automated MTO, MOC reconciliation, PHA and HAZOP revalidation, LDAR component inventory, brownfield scope definition, and as-built reconciliation. ## Built for real archives. Delivered with evidence. Scanned paper, rasterized CAD plots, and mixed-vintage archives with engineer review, source-linked traceability, and accuracy sampling. ## Who uses it EPC contractors, engineering firms, asset owners and operators, OEMs, and EHS consultants. --- # Armeta Codes — Cited Answers from Construction Codes Source: https://armeta.ai/products/codes/ # What the code actually requires. The regulatory base that governs design and construction is vast and constantly revised. Armeta Codes finds the applicable requirements and answers engineering questions with links to the specific documents and clauses — so teams cite the current rule, not the one they remember. ## Ask the code. Get the clause. Pose an engineering question in plain language and receive an answer with the documents and clauses attached — ready to verify, cite, and reuse. ## The expensive part is not reading the code. It is finding the right one. - The regulatory base is enormous - Editions keep changing - Citation is the deliverable ## A codes assistant built for cited work. - Ask in plain language - Retrieve the relevant norms - Answer with multiple citations - Refine in dialogue - Keep dialogue history - Configure jurisdiction-specific regulatory bases ## From a plain question to a reusable citation. 1. Ask — start with the question that needs answering. 2. Retrieve — find the norms that govern the point. 3. Cite — read the answer with the sources attached. 4. Refine — narrow the question without starting over. ## One product, adapted to the market where it runs. Current editions, multi-document answers, specialist confirmation, connections to Armeta Permit and estimating products, and organization-specific standards are configured for each market. ## Who uses it - Engineering firms - Construction firms - Asset owners - Governments and regulators CTA: Book a demo --- # Armeta Materials — Construction Product Search and Catalog Validation Source: https://armeta.ai/products/materials/ # The right item, the right code, the right price. Applicable cost catalogs run to hundreds of thousands of positions, and finding the correct one is a search problem no keyword search solves well. Armeta Materials finds the item from a plain description, returns its code, standard, unit, and price, and lets teams assemble a new catalog-backed specification or check an existing one for compliance. ## Search the library. Build the set. Check what already exists. One workspace for finding the correct catalog position, assembling a new specification from validated hits, and reviewing an uploaded file for compliance. ## Catalog codes decide whether a specification survives review. - Catalog codes are mandatory where public money is spent - Manual matching is slow and brittle - Search and check belong together against the same registry ## Two workflows. One registry. - Semantic library search from a plain-language description or partial code - Assemble a new specification from matched positions - Line-by-line compliance check of an uploaded file - Highlighted findings for mismatches and outdated codes - Canonical codes for every position - Structured export for estimating, procurement, or formal submission ## From a plain description to an exportable result. 1. Describe or upload — start from a sentence or a finished file. 2. Resolve positions — map every line to a canonical catalog identity. 3. Build or correct — add validated positions or fix the ones that failed. 4. Export — issue the set in the format the next party expects. ## One product, adapted to the market where it runs. Jurisdiction-specific catalogs, organization libraries, current editions, specialist confirmation, connection to Armeta Smeta, and structured handoff are configured for each market and organization. ## Who uses it - Engineering firms - Construction firms - Asset owners - Governments and regulators CTA: Book a demo --- # Armeta CAD — Browser-based Professional Drafting Source: https://armeta.ai/products/cad/ # Draft the sheet. Issue the set. Coming soon. Armeta CAD is a professional 2D drawing editor that runs in the browser. Designers open a link, draw plant layouts, details, network schemes, and site plans, and issue sheet sets ready for print, review, and exchange — without installing software or tying a drawing to one machine. ## A professional drawing editor that lives in the browser. Open a link, draft the sheet, collaborate on the same file, and issue a print-ready set without installing software or locking the project to one workstation. ## Drafting tools with standards already in place. - Full drafting toolset with snaps, ortho, polar tracking, dynamic input, and command line - Layers, attributed blocks, block editor, groups, and property sources - Fonts, dimensions, line types, hatches, frames, and title blocks follow applicable standards by default - Parametric axis grids, tables, and typical details - Multi-sheet layouts, scaled viewports, and PDF issue - Honest DXF exchange with reported substitutions ## From first line to an issued sheet set. 1. Open and draft — start from a link with the same product version and standards set. 2. Collaborate — several people in one drawing, shared history, checkpoints, offline sync. 3. Exchange — read and write DXF; map unknown styles by intent; report unsupported entities. 4. Check and issue — find formatting and completeness problems before formal review. ## Intelligence built into the same model. - Standards checking before issue - Recognition and substitution on foreign-file import - Construction of drawings from specifications ## Built for industrial drawings, not sketch files. - Tens of thousands of objects without losing response - Precision tools on exact coordinates - Entities preserved through save, sync, and exchange - Readable exports and measurable printed sheets - Cloud or customer-controlled deployment - Libraries and first-sheet templates ## One product, adapted to the market where it runs. Sheet formats, title blocks, fonts, line types, hatches, and submission conventions are configured for each jurisdiction and organization. Armeta CAD produces 2D working documentation, exchanges drawings through DXF, and connects drafting checks to package review in Armeta Permit. Three-dimensional modeling is outside its scope. ## Who uses it - Engineering firms - Construction firms - Asset owners - Governments and regulators CTA: Book a demo --- # Proof — Armeta Validated Where It Matters Source: https://armeta.ai/proof/ # Validated where it matters. Proof Active deployments on real customer data, external validation in respected venues, and founders who've spent careers in the industry. ## External validation ### First place at CERAWeek 2026. Award · Houston Armeta took first place in the Industrial Efficiency and Decarbonization track at the CERAWeek 2026 Energy Venture Day, held in Houston. ### First place at Unicorn Battle. Award · Palo Alto Armeta took first place in the Unicorn Battle in Palo Alto. ## Founders and team ### Built by operators. Armeta was founded by engineering executives with combined experience spanning: 01. Decades building and scaling engineering organizations delivering megaprojects across oil and gas, petrochemicals and power, metals and mining, machine building and construction materials, civil engineering and infrastructure, green-energy projects, and space infrastructure. 02. Senior delivery leadership on capital projects across Asia, Europe, North America, the Middle East and Central Asia. 03. Joint ventures with Technip Energies and Tecnimont, partnerships with Fluor and FLSmidth, and long-running delivery relationships with international operators, contractors and state customers. 04. Twenty-plus years in senior technical and engineering leadership at international engineering and contracting groups. 05. Applied AI and machine learning development focused on domain-specific engineering and industrial applications. CTA: See the team ## Institutional backing ### Backed by investors who understand this market. ### Alchemist Accelerator Batch 41 Armeta is an Alchemist Accelerator Batch 41 company, backed by a one-million-dollar pre-seed investment from Alchemist Doha, the Gulf-region arm of Alchemist. Alchemist Accelerator is one of the most respected enterprise-focused accelerators in the United States, with a fifteen-year track record of producing successful enterprise software companies across industrial, logistics, security, and data markets. CTA: About Alchemist Accelerator ### ZaiNar Strategic partner A physical AI company valued at over $3 billion, with a board member who also serves on SpaceX's board. ZaiNar is backed by prominent technology leaders, including the co-founder of Yahoo, the co-founder of Siri, a founding engineer at Skype, and Amazon's Chief Scientist. ZaiNar's founders, Daniel Jacker and Jake Levy, believed in Armeta from its early days and have supported us in a variety of ways. ZaiNar is a strategic partner of Armeta. CTA: About ZaiNar ### Derek Toffer Investor and partner A former Fluor Corporation executive and currently serving as Vice President at Anvil Corporation. Derek shares his extensive industry expertise with Armeta and helps us navigate the U.S. market. ## Closing CTA ### See this workflow on your project data. Walk through the platform on representative project context with the engineering team. CTA: Book a demo --- # Clients — Armeta for Businesses and Governments Source: https://armeta.ai/solutions/ # Businesses and governments. Clients Design packages, cost estimates, standards, and facility drawings pass between engineers, builders, operators, and regulators. Armeta works on these documents at every handoff. ## Who we serve - Engineering firms - Construction firms - Asset owners - Governments and regulators CTA: Book a demo --- # For Engineering Firms — Armeta Source: https://armeta.ai/solutions/engineering-firms/ # Turn legacy engineering documents into contextualized engineering data. For engineering firms Engineering firms live in the gap between what the owner has and what the project needs. Armeta handles the full document set you encounter — P&IDs, piping isometrics, PFDs, and line lists, both graphical and tabular — and contextualizes them into a single engineering knowledge graph. Decades of inherited drawings and data tables, closed in days, not months. CTA: Book a demo ## The engineering firm problem ### Every project begins with someone else's drawings. Whether you're the designer of record on a brownfield revamp, the owner's engineer on a refinery modernization, or the domain consultant brought in for a process debottleneck, you start every engagement by reading drawings you didn't draw. The PDF archive you receive from the owner is the inheritance — and it's almost always in worse shape than advertised. Decoding it is the unbillable overhead that precedes every billable engineering hour. It is also the phase that determines whether your project proposal was accurate, whether your fee will hold, and whether the owner will trust you on the next engagement. The engineering knowledge graph Armeta produces is the data foundation for brownfield revamps, data migration, and owner-operator deliverables. ## Three engagements ### Three engagement types, one extraction engine. 01 / Brownfield revamps and debottlenecking Today: Every revamp begins with sorting the drawing archive the owner provides. PDF scans of 1990s P&IDs, AutoCAD drawings from the early 2000s, native CAD from the last five years, and as-builts of varying quality. Your engineering team spends the first month of the project doing forensic drawing archaeology instead of design work. With Armeta: Any drawing in any format becomes structured engineering data. The graph you produce in week one is the baseline your design team builds on for the rest of the engagement. Forensic archaeology becomes automated reconciliation. 02 / Data migration and digitization projects Today: Engineering firms are frequently engaged specifically to digitize an owner's P&ID archive — converting PDFs into a modern engineering system (SPPID, SmartPlant, AVEVA, etc.). The billable work is the re-drafting, which is slow and error-prone. With Armeta: The extraction layer does the heavy lift. Your engineering team focuses on what requires judgment — reconciliation, symbol mapping, exception handling — rather than on manual transcription. Projects deliver faster and with higher accuracy. 03 / Owner's engineer and design review work Today: Owner's engineer scopes often require reviewing the EPC's deliverables against the governing P&IDs. Comparing two versions of a drawing, checking whether the field installation matches the design, validating MTO accuracy — all of these require slow manual reads. With Armeta: Structured delta between any two revisions. Drawing-traceable evidence for every finding. Owner's engineer reports are defensible, auditable, and delivered on a timeline the owner actually needs. ## The economics ### The math works the first time you run it. A simplified calculation for a typical engineering firm engagement: The math · simplified P&IDs in project scope — 450 Manual engineering per P&ID — 16 hrs Loaded engineering cost — $120 / hr Manual cost to process — $864,000 Armeta extraction + validation per P&ID — 0.5 hrs Result Armeta cost to process — $27,000 Engineering hours reclaimed — 6,975 Direct engineering hours only. Does not include brownfield scope lock-in compression, fee-at-risk protection on fixed-price engagements, owner client retention value, or the strategic upside of delivering the same scope at a competitive fee. ## Evidence ### Deployed today, where your data lives. Proof — Live on legacy drawing migration projects today. Engineering firms currently use Armeta on brownfield revamp and legacy digitization engagements. External validation on the record: first place at CERAWeek 2026 Energy Venture Day, Industrial Efficiency and Decarbonization track. See the full proof page Deployment — Where your project data already lives. Cloud, on-premise, or private cloud. Deployed under owner data residency and firewall requirements, per-project access controls. SOC 2 Type II audit in progress, completing H1 2026. Security and deployment ## Closing CTA ### See this workflow on your project data. See Armeta applied to the workflow, data, and decisions your team owns. CTA: Book a demo --- # For Construction Firms — Armeta Source: https://armeta.ai/solutions/construction-firms/ # You live with the number you submit. For construction firms A contractor commits to a price built under time pressure from catalogs, standards and drawings that were never made to be read together. Every position in that estimate is either defensible or it is not, and which one it turns out to be usually becomes clear long after the bid was won. Armeta puts the documentation behind the number in order before the number is committed. CTA: Book a demo --- # For Asset Owners — Armeta Source: https://armeta.ai/solutions/asset-owners/ # Know what you are being handed. For asset owners An owner inherits documentation produced by other people and stays accountable for it long after those people are gone. Design packages, cost documentation, as-built drawings — it all arrives from outside, and it all becomes the owner's permanent record. Armeta checks what arrives, and makes what is already in the archive usable again. CTA: Book a demo --- # For Governments and Regulators — Armeta Source: https://armeta.ai/solutions/governments-regulators/ # Review at the speed the pipeline requires. For governments and regulators Review capacity is fixed. Submission volume is not. Armeta takes on the repetitive part of an examination and returns it as itemised findings for a specialist to confirm — so reviews move faster without adding reviewers, fewer formal errors survive to a decision, and the same requirement is applied the same way to every applicant. Every check leaves a record. The same system that prepares a package is the system that checks it, which means both sides work from one interpretation of the normative base. CTA: Book a demo --- # Resources — Armeta Technical Library Source: https://armeta.ai/resources/ # Technical resources for the built world. Resources A comprehensive engineering and construction glossary, plus field notes and technical insights from the Armeta team. CTA: Book a demo ## Reference library ### 148 terms. One connected glossary. Browse the vocabulary used to price, design, review, approve, deliver, and document projects. 01 — Glossary 148 definitions across cost estimating, design and permitting, standards and normative systems, project delivery, engineering drawings, structured data, and process safety. Featured: 01 Cost and estimating 02 Design, permitting and approval 03 Standards and normative base 04 Delivery and contracting 05 Drawings and engineering data 06 Supplemental process safety terms CTA: Browse the full glossary ## Blog and insights ### Insights from the Armeta team. Editorial content from the Armeta team on industrial digitization, P&ID data strategy, regulatory developments, and lessons learned from active deployments. CTA: Read the blog ## Closing CTA ### See this workflow on your project data. Book a demo to see Armeta check, structure, and connect the drawings, standards, catalogs, and specifications your team works with today. CTA: Book a demo --- # Engineering, Construction, and Standards Glossary Source: https://armeta.ai/resources/glossary/ # The language behind engineering and construction. Glossary Definitions for the terms used to price, design, review, approve, deliver, and document projects — from national normative systems to individual drawing objects. CTA: Book a demo ## Term directory ### 148 terms across five connected fields. Search the complete glossary or move through the five source clusters. Supplemental process-safety terms remain available alongside the document vocabulary. - Cluster A: Cost and estimating — 31 terms - Cluster B: Design, permitting and approval — 30 terms - Cluster C: Standards and normative base — 27 terms - Cluster D: Delivery and contracting — 26 terms - Cluster E: Drawings and engineering data — 29 terms - Supplemental glossary — 5 terms Per-card CTA: Read definition ## Closing CTA ### Put this vocabulary to work. See how Armeta understands the standards, catalogs, drawings, specifications, and project records behind these terms. CTA: Book a demo --- # Preconstruction | Engineering glossary Source: https://armeta.ai/resources/glossary/preconstruction/ Glossary · Cluster A: Cost and estimating # Preconstruction The phase of a capital project between the decision to invest and the start of physical work, in which the design is developed, costs are estimated, permits are obtained and the contracting strategy is decided. Last reviewed: August 4, 2026 ## In detail Preconstruction is where a project exists only as documents: feasibility studies, design packages, estimates, permit applications, tender submissions. The owner, the design organisation, the estimators, the permitting authorities and — once tendering begins — the contractors all work from these documents, and each discipline produces outputs that become inputs for the next. What makes the phase disproportionately important is the cost-influence curve. By the time construction starts, the large decisions — process configuration, plot layout, structural system, material specifications — are already fixed, and with them most of the final cost. Changing a line on a drawing during preconstruction costs hours; changing the built result of that line costs weeks and money. The characteristic failure of preconstruction is not bad decisions but stale information. Estimates built on superseded drawing revisions, permit packages citing withdrawn standards, tenders priced against different document sets — these errors are cheap to catch on paper and expensive to discover on site, and most of them come from documents falling out of sync rather than from anyone's judgement. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Cost estimate; Bill of Quantities (BOQ); Quantity take-off Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Cost estimate | Engineering glossary Source: https://armeta.ai/resources/glossary/cost-estimate/ Glossary · Cluster A: Cost and estimating # Cost estimate A forecast of the probable cost of a defined scope of work, produced at a specific level of design maturity and valid only for that scope, that maturity and that point in time. Last reviewed: August 4, 2026 ## In detail A cost estimate is built by estimators from whatever project definition exists when it is prepared. Early in a project that may be little more than capacity figures and historical analogies; later it is full quantity take-offs priced line by line. A complete estimate covers direct costs, indirect costs, escalation and contingency, and it should always state its basis: which drawing revisions, which price date, which exclusions. Estimates mature in recognised stages — from order-of-magnitude through to definitive — and every estimating organisation classifies them by how much design definition sits underneath. The number is only as reliable as that definition; an estimate quoted without its class and basis is a number without meaning. Where estimates go wrong is rarely arithmetic. It is scope drift: the design moves on, the estimate does not, and decisions continue to be made against a figure that no longer describes the project. The discipline of restating the estimate whenever the basis changes is what separates cost control from cost surprise. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Bill of Quantities (BOQ); Quantity take-off Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Bill of Quantities (BOQ) | Engineering glossary Source: https://armeta.ai/resources/glossary/bill-of-quantities-boq/ Glossary · Cluster A: Cost and estimating # Bill of Quantities (BOQ) A structured list of every item of work and material required for a project, with measured quantities, used as the basis for tendering and for valuing work as it is completed. Last reviewed: August 4, 2026 ## In detail A bill of quantities is produced from the design documentation, usually by a quantity surveyor or an estimator, and it converts drawings and specifications into a countable list. Each line carries a description, a unit of measurement, a quantity, and — once priced — a rate and a total. Because every bidder prices the same bill, tenders become comparable on price rather than on interpretation. The accuracy of a BOQ depends entirely on the documentation underneath it. If a drawing revision was missed, or a specification cites a standard that has since been superseded, the error propagates into every bid built on that bill and is usually discovered on site. Reconciling a BOQ against the drawings and the specification is slow, manual work, and it is repeated every time the design changes. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Quantity take-off Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Quantity take-off | Engineering glossary Source: https://armeta.ai/resources/glossary/quantity-take-off/ Glossary · Cluster A: Cost and estimating # Quantity take-off The process of measuring and counting the quantities of work and materials in a project directly from its drawings, models and specifications. Last reviewed: August 4, 2026 ## In detail A quantity take-off (QTO) is the measurement exercise that sits underneath every bill of quantities and every detailed estimate. Estimators or quantity surveyors work through the documentation drawing by drawing, applying a set of measurement rules — a published standard method of measurement or an internal convention — so that "one metre of wall" means the same thing on every project and to every bidder. The distinction from a material take-off is scope. A quantity take-off measures items of work — excavation, formwork, welding, painting — including the labour they carry, and it feeds pricing documents. A material take-off lists the physical materials to be purchased. The two overlap but are consumed by different people for different purposes. Take-off is where the most repetitive manual effort in estimating lives. It is counting and measuring at scale, it must be redone in part or in full for every design revision, and two experienced people measuring the same drawings routinely arrive at different quantities because they interpreted the documents, not just read them. Most disputes about an estimate are ultimately disputes about a take-off. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Material take-off (MTO) | Engineering glossary Source: https://armeta.ai/resources/glossary/mto-material-takeoff/ Glossary · Cluster A: Cost and estimating # Material take-off (MTO) A structured list of the physical materials — pipe, fittings, valves, structural steel, cable and similar — required to build a design, extracted from engineering drawings and models to drive procurement and estimating. Last reviewed: August 4, 2026 ## In detail A material take-off is produced by discipline engineers or estimators from the engineering deliverables of the moment. Early MTOs are taken from P&IDs, plot plans and preliminary routing, carry heavy allowances, and exist to get long-lead bulk orders moving and early estimates built. Detailed MTOs come later from isometrics and the 3D model, and final take-offs reconcile what was ordered against what the issued-for-construction design actually requires. MTOs conventionally separate tagged, engineered items — equipment and instruments specified individually — from bulk materials counted in aggregate. Procurement buys from the MTO, estimating prices from it, and construction plans material logistics around it, which means a single missed line reaches three departments. The failure modes are specific and repetitive: connections that continue on another sheet and are counted on neither, specification breaks applied inconsistently, and take-offs built on one revision while the design has moved to the next. Because the gaps are covered by growth allowances, systematic under-counting can stay invisible until materials run short on site — usually in exactly the bulk items with the longest lead times. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Unit rate | Engineering glossary Source: https://armeta.ai/resources/glossary/unit-rate/ Glossary · Cluster A: Cost and estimating # Unit rate The cost of one measured unit of a work item — one cubic metre of concrete placed, one metre of pipe welded — combining labour, materials, equipment, overheads and margin. Last reviewed: August 4, 2026 ## In detail Unit rates are the pricing atoms of estimating. A rate is built up from its resources: the labour hours a crew needs per unit, the material content including waste, the plant and equipment time, plus allocations for overheads and profit. Multiply rates by the quantities in a bill and you have a tender price; the same rates then value completed work during execution. Rates are only meaningful together with the measurement rules they assume. A rate for "pipework, installed" priced per metre is not comparable to one priced per weld or per kilogram, and a rate that includes testing is not comparable to one that excludes it. Where unit-rate estimating goes wrong is almost always here: rates borrowed from a catalogue or a previous project without checking what the unit actually covered, or applied to a site whose productivity bears no resemblance to the one the rate was observed on. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Schedule of rates | Engineering glossary Source: https://armeta.ai/resources/glossary/schedule-of-rates/ Glossary · Cluster A: Cost and estimating # Schedule of rates A pre-agreed list of unit rates for defined work items, without quantities, used to price work whose extent is not known in advance. Last reviewed: August 4, 2026 ## In detail A schedule of rates is what remains of a bill of quantities when the quantities are removed. The parties agree the rates up front; the work is then measured as it is actually done and paid at those rates. Schedules are the standard instrument for maintenance and term contracts, call-off frameworks, and — within lump-sum contracts — for valuing variations and change orders, where they remove one of the two arguments (the rate) and leave only the other (the quantity). The known weakness is asymmetry of information at bid time. Because bidders do not know the eventual quantities, a schedule can be gamed by pricing items expected to occur frequently high and rarely-used items low, producing a schedule that looks competitive in total but is expensive in practice. Owners counter this with estimated-quantity weightings — which quietly reintroduces the take-off problem the schedule was meant to avoid. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Cost catalog | Engineering glossary Source: https://armeta.ai/resources/glossary/cost-catalog/ Glossary · Cluster A: Cost and estimating # Cost catalog A maintained library of reference cost data — unit rates, resource norms, assemblies and material prices — from which estimates are built and against which bids are checked. Last reviewed: August 4, 2026 ## In detail Every estimating organisation prices from somewhere: commercial databases, published national reference bases, or an internal catalogue distilled from its own project history. A catalogue entry typically pairs a work description and unit with a rate or a resource build-up, and mature catalogues carry regional adjustment factors and dated price levels so a rate can be moved between locations and years. In several jurisdictions, including much of the CIS, the cost catalogue is not merely a convenience but part of the normative base: state-issued rates and norms that public-sector estimates must be assembled from, with compliance checked during expert review. Catalogues fail by decaying. Prices age, work methods change, and a rate observed on one kind of project gets silently reused on another. Because the catalogue sits underneath every estimate the organisation produces, an error in it does not stay in one project — it propagates into all of them, which is why the unglamorous work of maintaining, dating and back-testing the catalogue matters more than any individual estimate. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Cost breakdown structure (CBS) | Engineering glossary Source: https://armeta.ai/resources/glossary/cost-breakdown-structure-cbs/ Glossary · Cluster A: Cost and estimating # Cost breakdown structure (CBS) A hierarchical structure that organises all project costs into defined categories, so that estimates, budgets and actuals can be compared at the same levels. Last reviewed: August 4, 2026 ## In detail A cost breakdown structure answers the question "where does every unit of money get filed?" It decomposes total cost into consistent categories — by discipline, by cost type, by facility area, depending on the organisation — down to the level at which costs are collected and controlled. Estimators assemble the estimate against it, project controls report against it, and finance reconciles against it. The CBS lives alongside the work breakdown structure but is not the same thing: the WBS decomposes the work, the CBS decomposes the money, and every organisation needs a mapping between the two. That mapping is where trouble concentrates. When the estimate is structured one way, the contractor's invoices another, and the owner's ledger a third, comparing budget to actuals becomes a translation exercise done in spreadsheets — and the translation, not the costs, becomes the source of disagreement. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Work breakdown structure (WBS) | Engineering glossary Source: https://armeta.ai/resources/glossary/work-breakdown-structure-wbs/ Glossary · Cluster A: Cost and estimating # Work breakdown structure (WBS) A hierarchical decomposition of the total scope of a project into progressively smaller pieces of work, forming the common skeleton for scheduling, estimating and reporting. Last reviewed: August 4, 2026 ## In detail The WBS breaks a project into deliverables and work packages: plant, then area, then system, then package, in whatever logic suits the project. Its governing convention is the 100% rule — every level must contain all of the scope of the level above it, no more and no less — so that nothing in the project exists outside the structure. Its value is that everyone hangs their data on the same tree. The schedule sequences WBS elements, the estimate prices them, progress is measured against them, and change is logged against them. When a scope item cannot be located in the WBS, that is usually the first visible symptom of scope that was never captured at all. The common failures are structural: a WBS drawn by organisational department rather than by scope, so that work falling between departments has no home; or a structure defined after the estimate rather than before it, forcing a retrofit mapping that never quite closes. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Direct costs | Engineering glossary Source: https://armeta.ai/resources/glossary/direct-costs/ Glossary · Cluster A: Cost and estimating # Direct costs Costs that can be attributed to a specific, measurable item of permanent work — the labour, materials and equipment time consumed in building it. Last reviewed: August 4, 2026 ## In detail Direct costs are what unit rates are made of: the crew hours to place the concrete, the concrete itself, the pump that placed it. They scale with quantities — more metres of pipe means proportionally more direct cost — which is what makes them measurable, priceable per unit, and comparable between bidders. The boundary between direct and indirect is a matter of convention, not physics, and that is where comparisons break. One contractor treats scaffolding as a direct cost within the rates; another carries it in site overheads; a third prices it as a separate preliminaries item. All three tenders are legitimate and none are comparable line by line. Estimates and bids should state where the boundary was drawn, and bid levelling exists largely to redraw it consistently before prices are compared. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Indirect costs and overheads | Engineering glossary Source: https://armeta.ai/resources/glossary/indirect-costs-and-overheads/ Glossary · Cluster A: Cost and estimating # Indirect costs and overheads Costs required to deliver the project that cannot be attributed to any single item of work — site management, temporary facilities, equipment fleets, insurances and the contractor's share of head-office cost. Last reviewed: August 4, 2026 ## In detail Indirect costs divide into two layers. Site (or field) overheads are project-specific: supervision and site staff, offices and welfare facilities, temporary power and roads, general-use cranage, security, quality and safety functions. Head-office overheads are the contractor's cost of existing — management, premises, tendering — recovered as a percentage across all projects. Margin sits on top of both. Indirects are estimated differently from directs: not from quantities but from the execution plan, and above all from duration. A large share of site overhead is time-related — the site establishment costs roughly the same per month whether the month was productive or not — which is why schedule slippage flows almost directly into indirect cost growth, and why claims for delay are, financially, mostly claims for extended overheads. The estimating failure is treating indirects as a habitual percentage of directs. The ratio varies enormously with project duration, remoteness, and how much of the temporary infrastructure already exists, and a percentage carried over from a previous project encodes that project's conditions, not this one's. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Preliminaries | Engineering glossary Source: https://armeta.ai/resources/glossary/preliminaries/ Glossary · Cluster A: Cost and estimating # Preliminaries The section of a tender or bill of quantities that prices the contractor's general obligations and site-wide costs — establishment, management, temporary works, insurances — separately from the measured work items. Last reviewed: August 4, 2026 ## In detail Preliminaries (often "prelims") are the contractual packaging of site overheads in measured-works tendering, standard in UK-influenced practice. Rather than burying site-wide costs inside every unit rate, the bill carries them as their own priced section, split conventionally into fixed charges (mobilise the site, demobilise it) and time-related charges (run the site per week or month). The split matters downstream. When the contract period is extended, the time-related prelims provide the ready-made basis for valuing the prolongation; when scope grows without extending duration, they should not grow with it. Prelims that were priced as a single lump sum give away that leverage on both sides. At tender stage, prelims are also where pricing strategy hides. A bidder can shift money between prelims and rates to improve early cash flow or position for variations, so two bids with identical totals can behave very differently once the project starts. Reviewing the shape of the prelims, not just their total, is part of any serious bid evaluation. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Contingency | Engineering glossary Source: https://armeta.ai/resources/glossary/contingency/ Glossary · Cluster A: Cost and estimating # Contingency An amount included in an estimate or budget to cover costs that are expected to occur within the defined scope but cannot yet be itemised — the known-unknowns of the project. Last reviewed: August 4, 2026 ## In detail Contingency exists because an estimate built only from what is currently drawn will be exceeded by a project that is still being designed. It covers estimating inaccuracy, design development within scope, normal quantity growth, and pricing variability. It explicitly does not cover scope changes, major risk events or escalation — those have their own provisions — and it is not a management reserve for the unknown-unknowns outside the defined scope. Contingency is set either deterministically, as a percentage keyed to the estimate class — wide at order-of-magnitude, narrow at definitive — or probabilistically, by risk analysis that produces a distribution of outcomes and lets the organisation choose its confidence level. Two failure patterns dominate. The first is double-counting: allowances buried in quantities, padding in rates, and a percentage on top, producing an estimate nobody can defend. The second is the opposite: contingency treated as fat and cut to make a number acceptable, which does not change the project's cost — only the date on which it is discovered. Well-run projects manage contingency drawdown explicitly, logging what consumed it, so that the remaining amount is a live measure of remaining risk. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Cost escalation | Engineering glossary Source: https://armeta.ai/resources/glossary/cost-escalation/ Glossary · Cluster A: Cost and estimating # Cost escalation The anticipated change in prices between the date of an estimate and the dates when the work will actually be bought and built, provided for as a distinct line in the estimate. Last reviewed: August 4, 2026 ## In detail An estimate is priced at a stated base date; the project spends money over years. Escalation bridges the two. It is calculated by spreading the estimate over the expenditure schedule and applying forecast indices — construction cost indices, commodity forecasts, labour agreements — appropriate to each cost category, because steel, cable, fuel and labour do not move together. Escalation is deliberately kept separate from contingency: contingency covers uncertainty about what the project is, escalation covers movement in what things cost, and merging them makes it impossible to tell later which one was wrong. In volatile markets escalation can rival contingency in size, and contract drafting decides who carries it — a lump-sum contractor prices it in; a cost-plus owner pays it as it happens; indexed contracts share it by formula. The characteristic error is anchoring: pricing tomorrow's project on today's quotes and treating the result as conservative. A multi-year project priced without escalation is not a tight estimate — it is an estimate for a project that will be built entirely this month. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Value engineering | Engineering glossary Source: https://armeta.ai/resources/glossary/value-engineering/ Glossary · Cluster A: Cost and estimating # Value engineering A structured review of a design against the functions it must perform, seeking ways to deliver the same function at lower whole-life cost — as distinct from simply cutting scope or quality. Last reviewed: August 4, 2026 ## In detail Value engineering starts from function, not from the design in front of it. The discipline asks what each element is for — support the load, contain the pressure, provide the access — and then whether that function can be achieved another way: a different material, a simpler configuration, a standard component instead of an engineered one, or elimination of an element whose function turns out to be duplicated. Timing determines its worth. Applied during design development, VE proposals cost little to adopt because nothing has been bought or built. Applied late — typically when tenders come in over budget — the same exercise degenerates into "value engineering" as a euphemism for descoping under pressure, done without the redesign time to check consequences, which is where corners genuinely get cut. The honest version keeps whole-life cost in the equation. A cheaper material that doubles maintenance is not value engineering; it is a cost transfer to the operations budget, made by people who will not be paying it. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Order-of-magnitude estimate | Engineering glossary Source: https://armeta.ai/resources/glossary/order-of-magnitude-estimate/ Glossary · Cluster A: Cost and estimating # Order-of-magnitude estimate A screening-level cost estimate produced from minimal project definition, used to decide whether an idea deserves further study rather than to set a budget. Last reviewed: August 4, 2026 ## In detail An order-of-magnitude (or ballpark, or Class 5) estimate is prepared when the project is little more than a capacity and a location. It is built from analogy and scaling: costs of comparable past projects adjusted for size using capacity-factor relationships, parametric models, or factored methods that grow a total cost from early equipment figures. The design definition underneath it is a few percent at most, and the honest accuracy range is correspondingly wide — tens of percent in either direction, and asymmetric, since undiscovered scope is more common than undiscovered savings. Its legitimate uses are comparison and screening: option A against option B, proceed or drop. The recurring failure is memorial: the first number ever attached to a project is the one everyone remembers, and an order-of-magnitude figure quoted in an early paper quietly becomes the yardstick against which every subsequent, better-founded estimate is judged as "growth". Disciplined organisations publish these estimates only as ranges and with their class stamped on them. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Definitive estimate | Engineering glossary Source: https://armeta.ai/resources/glossary/definitive-estimate/ Glossary · Cluster A: Cost and estimating # Definitive estimate A high-maturity cost estimate built from substantially complete engineering and detailed take-offs, accurate enough to serve as the project's control budget and the basis for final investment commitment. Last reviewed: August 4, 2026 ## In detail A definitive estimate is what the estimating process has been converging toward: quantities taken off from near-complete drawings and models, pricing from firm quotations and current rates rather than allowances, indirects built from an actual execution plan and schedule, and contingency reduced to reflect how little remains undefined. In class terms it corresponds to the top of the scale — Class 2 and Class 1 — with expected accuracy in the single digits to low teens of percent. Because of that accuracy, it carries the most weight: final investment decisions, lump-sum contract prices and control baselines are set against it. From this point, cost management stops being estimating and becomes change control — every deviation is measured against the definitive baseline. Its cost is its cost. A definitive estimate requires most of the engineering to exist, which means most of the engineering money is spent before the most reliable number exists. Projects that demand definitive accuracy at concept stage are not asking for a better estimate; they are asking for the design to be finished early, and no estimating method substitutes for that. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Base estimate | Engineering glossary Source: https://armeta.ai/resources/glossary/base-estimate/ Glossary · Cluster A: Cost and estimating # Base estimate The estimated cost of the defined scope at current prices, before contingency, escalation and reserves are added — the "what we can see, at today's money" figure. Last reviewed: August 4, 2026 ## In detail The base estimate is the deterministic core of a total estimate: measured quantities priced at base-date rates, plus indirects, with the provisions for uncertainty stripped out and shown separately. Structuring estimates this way is what makes them auditable. Reviewers can interrogate the base against the drawings, the contingency against the risk register, and the escalation against the expenditure schedule — three separate conversations instead of one argument about a single number. It also makes estimates comparable over time. When the estimate is restated at the next design stage, movement in the base reveals scope and quantity growth, while movement in contingency reveals changing risk — provided the boundary was kept clean. Keeping it clean is the entire discipline. Allowances hidden in quantities and padding tucked into rates are contingency smuggled into the base, and once there, they can never be separated out again. An estimate whose base cannot be reconciled to the documentation is not conservative; it is simply unexplainable. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Cost norm | Engineering glossary Source: https://armeta.ai/resources/glossary/cost-norm/ Glossary · Cluster A: Cost and estimating # Cost norm A standardised statement of the resources — labour hours, materials, machine time — required to perform one unit of a defined work item, used as the objective core of an estimate. Last reviewed: August 4, 2026 ## In detail A norm answers "how much does this work take", separately from "what do those resources cost". Norm-based (resource-based) estimating builds every rate from that split: the norm supplies consumption per unit, current prices supply the money, and either can be updated without disturbing the other. Norms come from two traditions. In the normative estimating systems of the CIS and several other regions, norms are state-issued, codified and mandatory for public-sector work — estimates are assembled from the official norm base and checked against it during expert review. In market systems, the same role is played by company productivity databases, published references and negotiated labour norms; less codified, same logic. Norms fail by outliving their conditions. A labour norm encodes a method, a crew composition and a productivity environment; applied to a site with different methods or conditions, it produces precise-looking nonsense. The productivity factor that adjusts a norm to actual conditions is the most consequential and least documented number in a resource-based estimate. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Elemental cost plan | Engineering glossary Source: https://armeta.ai/resources/glossary/elemental-cost-plan/ Glossary · Cluster A: Cost and estimating # Elemental cost plan A cost plan organised by the functional elements of a building — substructure, frame, envelope, services — rather than by trades or materials, used to steer design toward a budget. Last reviewed: August 4, 2026 ## In detail An elemental cost plan allocates the budget to elements defined by function: everything that performs "keep the weather out" is the envelope, regardless of which trades build it. Standard elemental structures (in UK practice, those of the RICS New Rules of Measurement) make the allocation consistent from project to project, so element costs can be benchmarked per square metre against comparable buildings. Its purpose is design-stage control. Because elements map to design decisions rather than to procurement packages, the cost plan gives each designer a target — the frame has this much, the facade that much — and design development is checked against those targets iteratively. Overrun in one element becomes visible early enough to rebalance others, instead of surfacing as a single unaffordable tender. The limits are its boundaries: element definitions must be applied exactly for benchmarks to mean anything, and the elemental view must eventually be translated into the trade-and-package view that contractors price — a mapping exercise where scope can fall between the two structures if it is done carelessly. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Cost benchmarking | Engineering glossary Source: https://armeta.ai/resources/glossary/cost-benchmarking/ Glossary · Cluster A: Cost and estimating # Cost benchmarking Comparing a project's estimated or actual costs against a reference set of completed projects, normalised for size, location, time and scope, to test whether the numbers are reasonable. Last reviewed: August 4, 2026 ## In detail Benchmarking answers the question an estimate cannot answer about itself: is this normal? Metrics are chosen at a comparable level — cost per square metre, per tonne of steel, per installed megawatt, or element ratios — and the reference data is normalised before comparison: indexed to a common price date, adjusted by location factors, and screened for scope differences such as who carried the owner's costs or whether the site infrastructure existed. Done well, benchmarking is a diagnostic, not a verdict. An estimate 30% above the benchmark set is not wrong; it is carrying something the reference projects did not, and the useful output is finding out what. Reviewers and lenders use it exactly this way, as a structured request for explanation. Done badly, it is the most efficient way to launder a false number. Unnormalised comparisons — different years, different countries, different scope boundaries — can justify almost any figure, and a benchmark quoted without its basis deserves the same suspicion as an estimate quoted without one. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Budget vs estimate | Engineering glossary Source: https://armeta.ai/resources/glossary/budget-vs-estimate/ Glossary · Cluster A: Cost and estimating # Budget vs estimate An estimate is a prediction of what a scope of work will probably cost; a budget is a decision about how much money is allocated to it — related, but not the same number and not the same act. Last reviewed: August 4, 2026 ## In detail The estimate is produced by estimators and describes the project; the budget is set by the owner and constrains it. A well-formed budget is derived from an estimate — typically the base estimate plus contingency, escalation and owner's reserves at a chosen confidence level — but the derivation runs one way. Declaring a budget first and instructing the estimate to fit it is not estimating; it is negotiation with arithmetic as decoration. The two numbers also live differently. An estimate is restated whenever its basis changes; a budget, once authorised, changes only through formal governance. That is precisely their value as a pair: the drifting estimate measured against the fixed budget is how a project knows where it stands. Confusing the vocabulary has real consequences. When an early, wide-range estimate is announced as "the budget", every later refinement reads as overrun, and the project spends its life explaining growth that is actually definition. The discipline is small but strict: never publish an estimate without its class and basis, and never call it a budget until someone has actually committed the money. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # AACE estimate classes | Engineering glossary Source: https://armeta.ai/resources/glossary/aace-estimate-classes/ Glossary · Cluster A: Cost and estimating # AACE estimate classes A widely used framework, published by AACE International, that classifies cost estimates from Class 5 to Class 1 according to the level of project definition behind them and the accuracy that can honestly be expected. Last reviewed: August 4, 2026 ## In detail The classification, set out in AACE's recommended practices for cost estimate classification, ties three things together: the maturity of the engineering deliverables (from a few percent defined at Class 5 to essentially complete at Class 1), the estimating methods appropriate at that maturity (factored and parametric early, detailed take-off later), and the expected accuracy range, which narrows from tens of percent either way at Class 5 to around ten percent or better at Class 1. The exact ranges vary by industry and by each organisation's own history, which the practice explicitly acknowledges. Its value is shared vocabulary. "A Class 4 estimate" tells an owner, a lender and a reviewer the same thing about what the number is built on and how far it can be trusted, without anyone inspecting the take-offs. Most large owners and EPC firms key their gate decisions and contingency policy to estimate class. The abuse is class inflation: labelling an estimate by the accuracy the project wants rather than the definition it has. The class is determined by the deliverables that exist, and an estimate cannot be promoted a class by wishing — only by engineering. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Factored estimate | Engineering glossary Source: https://armeta.ai/resources/glossary/factored-estimate/ Glossary · Cluster A: Cost and estimating # Factored estimate An early estimating method for process plants in which total installed cost is derived by multiplying the cost of major equipment by empirically established factors. Last reviewed: August 4, 2026 ## In detail In process industries, the cost of the major equipment is knowable early — vendors will quote a compressor or a column from a datasheet long before the plant is designed. Factored estimating exploits the observed regularity that everything around the equipment (piping, steel, instruments, electrical, civil, installation labour, engineering) bears a fairly stable ratio to the equipment cost for a given type of plant. Multiply the equipment total by an overall factor — the classic Lang factors run roughly from three for solids-handling plants to nearly five for fluid-processing plants — or apply component factors per discipline for a finer result, and a total installed cost appears from remarkably little definition. It is the workhorse of order-of-magnitude and study estimates, and it fails in predictable ways: factors calibrated on greenfield plants applied to revamps inside a live facility, unusual metallurgy that distorts the equipment-to-bulks ratio, or site conditions the reference data set never contained. A factored estimate is an analogy, and it is only as good as the resemblance. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Parametric estimating | Engineering glossary Source: https://armeta.ai/resources/glossary/parametric-estimating/ Glossary · Cluster A: Cost and estimating # Parametric estimating Estimating cost from statistical relationships between cost and measurable project parameters — cost per square metre, per tonne of capacity, per kilometre — derived from historical data. Last reviewed: August 4, 2026 ## In detail Parametric estimating generalises the factored approach: instead of one ratio to equipment cost, it fits cost-estimating relationships to whatever parameters the historical data shows to be predictive — capacity, area, throughput, weight, power. The relationships range from a simple unit cost multiplied by a driver to multi-variable models with capacity exponents, and they are applied when the parameters are known but the design is not. The method is only as good as three things: the size and relevance of the underlying data set, the normalisation applied to it (time, location, scope boundaries), and the honesty about whether the new project sits inside the range the data covers. Extrapolating a relationship beyond the largest project it was fitted on is the classic failure — cost rarely scales linearly, and the exponent that was true from ten to fifty units of capacity has no obligation to hold at five hundred. Used within its range, parametrics are fast, cheap and defensible, which is why screening studies, benchmarking checks and independent reviews all lean on them. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Allowance | Engineering glossary Source: https://armeta.ai/resources/glossary/allowance/ Glossary · Cluster A: Cost and estimating # Allowance An amount included within the base estimate for an item that is known to be required but not yet defined in enough detail to measure — priced by judgement rather than take-off. Last reviewed: August 4, 2026 ## In detail Allowances fill the gaps that exist at every estimate stage: the design shows a pump but not yet its foundations, a route but not yet its supports. The estimator carries a judged amount — a percentage on the measured quantities or a lump figure per item — so the estimate reflects the whole expected scope, not just the drawn part. As design matures, allowances are progressively replaced by measured quantities, and watching that replacement is one of the cleanest indicators of estimate maturity. The distinction from contingency is definitional and worth policing: an allowance covers a known, specific item awaiting detail and sits inside the base estimate; contingency covers the unspecified residual uncertainty and sits on top of it. When allowances and contingency both quietly cover the same growth, the estimate is padded twice; when each assumes the other covers it, the growth is covered by neither. Every allowance should be listed, justified and closed out by name — an allowance nobody can enumerate is just contingency hiding in the base. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Provisional sum | Engineering glossary Source: https://armeta.ai/resources/glossary/provisional-sum/ Glossary · Cluster A: Cost and estimating # Provisional sum A stated amount included in a tender or contract for work that cannot be adequately defined at tender time, to be replaced by the actual cost of that work once it is instructed and done. Last reviewed: August 4, 2026 ## In detail A provisional sum is the contractual mechanism for tendering around a hole in the definition. The owner's side inserts a fixed figure for the undefined element — ground works pending investigation, a specialist package not yet designed — so all bidders carry the same placeholder and the tenders remain comparable. When the work is eventually defined and instructed, the sum is omitted and the real valued cost substituted, with the contract price adjusted either way. Standard forms distinguish defined provisional sums — where enough is known for the contractor to have allowed for them in programme and preliminaries — from undefined ones, where the contractor could not, and any time consequence becomes the owner's risk. The distinction decides who pays for the disruption, not just the work. The pathology is overuse. A tender heavy with provisional sums is a lump-sum contract in name only: price certainty has been deferred, not achieved, and each sum matures into a negotiation. Provisional sums measure, quite precisely, how unfinished the design was when it went to market. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # MTO growth allowance | Engineering glossary Source: https://armeta.ai/resources/glossary/mto-growth-allowance/ Glossary · Cluster A: Cost and estimating # MTO growth allowance A percentage added to the measured quantities of a material take-off to cover the growth expected between the current design stage and the final installed quantities. Last reviewed: August 4, 2026 ## In detail Every early MTO under-counts, for structural reasons: routing is preliminary, supports and specials are not yet designed, field adjustments have not happened, and cutting waste is real. Growth allowances compensate — set per material class and per MTO stage, heaviest on early bulk take-offs from P&IDs and preliminary routing, stepping down through the isometric-based MTOs, approaching only cutting and waste margins at the final take-off. Mature organisations calibrate the percentages from their own history of estimated-versus-final quantities rather than from folklore. The allowance is both necessary and dangerous. Necessary, because procurement of long-lead bulks cannot wait for the design to finish. Dangerous, because a blanket percentage covers whatever is missing without ever identifying it — a systematically under-counting take-off process and a healthy one produce the same-looking numbers until the growth allowance runs out, which it does on site, in the material with the longest lead time. Tracking actual growth against the allowance, package by package, is the only way to tell disciplined take-off from luck. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Bulk materials and tagged items | Engineering glossary Source: https://armeta.ai/resources/glossary/bulk-materials-and-tagged-items/ Glossary · Cluster A: Cost and estimating # Bulk materials and tagged items The two categories every engineering material list divides into: tagged items, specified and tracked individually by tag number, and bulk materials, specified by class and counted in aggregate. Last reviewed: August 4, 2026 ## In detail Tagged (engineered) items — pumps, vessels, instruments, packaged units — each carry a unique tag, a datasheet and usually a dedicated purchase order; they are known early, priced by quotation, and tracked one by one from requisition to installation. Bulks — pipe, fittings, flanges, cable, cable tray, structural steel, bolts, paint — are defined by specification classes and consumed in quantities that only emerge from take-off; they are bought in aggregated orders against the MTO and managed statistically, with growth allowances and surplus percentages instead of per-item tracking. The split runs through everything downstream: estimating treats tagged items as quoted line items and bulks as measured quantities at rates; procurement runs different processes for each; and material control on site is an inventory problem for bulks and a chain-of-custody problem for tags. Most quantity surprises live on the bulk side — tagged items are hard to lose, but nobody ever discovers on site that a pump is missing; they discover that the fittings are. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Total installed cost (TIC) | Engineering glossary Source: https://armeta.ai/resources/glossary/total-installed-cost-tic/ Glossary · Cluster A: Cost and estimating # Total installed cost (TIC) The full cost of delivering an operating asset — equipment, bulk materials, construction labour, indirects, engineering and project services — as distinct from the cost of the equipment alone. Last reviewed: August 4, 2026 ## In detail Total installed cost is the number that answers "what will this plant cost to build", and its defining property is how much of it is not equipment. In process facilities the major equipment is commonly well under half of TIC; the remainder is the bulks that connect it, the labour that erects it, the temporary infrastructure, the engineering, and the management of all of the above. This is precisely the regularity that factored estimating exploits, and the reason a vendor quote is nowhere near a project cost. Scope boundaries make TIC treacherous in comparison. Whether owner's costs, licence fees, spares, commissioning, escalation and contingency sit inside or outside "TIC" varies by organisation, and two projects quoting the same metric can differ by a fifth on definitions alone. Like every summary cost number, TIC means something only alongside its basis: what is in, what is out, and at what date's prices. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Preconstruction; Cost estimate; Bill of Quantities (BOQ) Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Design documentation | Engineering glossary Source: https://armeta.ai/resources/glossary/design-documentation/ Glossary · Cluster B: Design, permitting and approval # Design documentation The complete set of drawings, specifications, calculations, schedules and reports that defines what is to be built, produced in stages by the design organisation and consumed by everyone else on the project. Last reviewed: August 4, 2026 ## In detail Design documentation is the project, for as long as the project exists on paper. It is produced by a design institute, an engineering consultancy or an EPC contractor's engineering function, discipline by discipline, and every other party works from it: reviewers examine it, estimators measure it, authorities permit against it, and contractors build from it. Its structure is staged, and the stages differ by jurisdiction: schematic, design development and construction documents in North American practice; work stages in UK practice; the design-documentation and working-documentation split in CIS systems. Each stage has its own required content and its own consumers, and a document set that satisfies one jurisdiction's stage definition can fail another's on structure alone. The chronic weakness of design documentation is not any single document but coherence across the set. A project's definition is scattered across hundreds or thousands of files produced by different disciplines at different times, and the interfaces between them — a load on one drawing, the foundation for it on another, the specification for both in a third — are exactly where inconsistencies collect and where reviews concentrate. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Permitting package; Building permit; Design review Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Permitting package | Engineering glossary Source: https://armeta.ai/resources/glossary/permitting-package/ Glossary · Cluster B: Design, permitting and approval # Permitting package The specific subset of project documentation assembled and formatted for submission to an authority in order to obtain a permit or approval. Last reviewed: August 4, 2026 ## In detail A permitting package is not simply the design documentation with a cover letter. Each authority defines what a submission must contain — which documents, at what stage of development, with which certificates, signatures, forms and fees attached — and the package is assembled against that checklist, usually by the design organisation or a permitting consultant acting for the owner. The package leads a double life. To the project it is a milestone deliverable on the critical path; to the authority it is the only version of the project that exists, which means anything true of the project but absent from the package is, for approval purposes, not true. Assembling it is therefore an exercise in completeness and internal consistency under a deadline. It goes wrong at the formalities first: a missing section, an unsigned title page, a cited standard that has been superseded since the design was frozen. Rejections at this stage are cheap for the authority and expensive for the project, because each resubmission cycle costs weeks of calendar time regardless of how small the correction was. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Building permit; Design review Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Building permit | Engineering glossary Source: https://armeta.ai/resources/glossary/building-permit/ Glossary · Cluster B: Design, permitting and approval # Building permit The formal authorisation issued by a competent authority that allows construction of a defined project to begin, granted after the authority has reviewed the submitted documentation. Last reviewed: August 4, 2026 ## In detail A building permit is the state's checkpoint between design and site. Its issue confirms that the authority has examined the submission and found it acceptable under the applicable regulations — which is not the same as confirming the design is good, only that it is lawful to build. What is reviewed, by whom and how deeply varies enormously: some systems check zoning and life safety and rely on the designer's professional liability for the rest; others, including the state-examination systems of the CIS, review the engineering substance and the cost estimates before a permit can exist. Permits also come with conditions — inspections at defined stages, restrictions on hours or methods, requirements to be discharged before occupancy — and in many systems large projects are permitted in slices, with early-works or foundation permits allowing site start before the full approval lands. The scheduling failure is treating the permit as an administrative formality with a known duration. Review cycles are iterative, resubmission clocks restart, and a project that plans permit issue as a fixed date rather than a process with feedback loops usually discovers the difference on its baseline schedule. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Design review Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Design review | Engineering glossary Source: https://armeta.ai/resources/glossary/design-review/ Glossary · Cluster B: Design, permitting and approval # Design review A structured examination of design outputs against requirements, codes and project criteria at a defined point, carried out to catch errors and misalignments while they are still cheap to fix. Last reviewed: August 4, 2026 ## In detail Design reviews come in layers. Inside the design organisation, disciplines check their own work and each other's — interdisciplinary checks, squad checks, model reviews. Above that sit the owner's reviews at stage gates, third-party or independent verification where the risk warrants it, and finally the authority's review during permitting. Each layer has a different question: is it right, is it what we asked for, is it compliant. A review is only as good as its closure. The output of a real review is a comment log with dispositions — accepted, rejected with reason, action taken — and a design that demonstrably changed where it needed to. Reviews conducted as document circulation, where comments are collected but never adjudicated, produce the signature trail of quality assurance without the substance. Timing is the other half. The influence of a review decays with the design's maturity: a comment at concept redirects the project, the same comment at issued-for-construction generates a change order. Review effort concentrated late in the process is not rigour; it is a record of what it was too late to fix. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # State examination (State Expertise) | Engineering glossary Source: https://armeta.ai/resources/glossary/state-examination-state-expertise/ Glossary · Cluster B: Design, permitting and approval # State examination (State Expertise) A mandatory expert review of a project's design documentation — and in most such systems its cost estimates — by a state or state-accredited body, whose positive conclusion is a precondition for a construction permit. Last reviewed: August 4, 2026 ## In detail State examination is the institutional form of design review used across the CIS and in a number of other jurisdictions: before a project of the covered categories may be permitted, its documentation is submitted to an expertise body, examined by discipline experts against the normative base, and either returned with comments or issued a positive conclusion. For publicly funded projects the examination extends to the estimate documentation, checked line by line against the state cost norms and catalogues — the review is as much about whether the budget is justified as whether the building will stand. The process is formally structured: a completeness check on intake, a substantive review period, cycles of comments and responses, and a registered conclusion at the end. Both the required contents of the submission and the grounds for rejection are codified, which makes the process predictable in shape and unforgiving in detail. For designers, expertise is the exam at the end of the course, and much of the cost lives before submission: pre-checking thousands of pages against thousands of clauses, reconciling estimates with drawings, and verifying that every referenced standard is the currently valid edition. A comment cycle triggered by a formal defect costs the same calendar time as one triggered by a real engineering problem, which is why the manual pre-review effort is so heavy — and so repetitive. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Code compliance check | Engineering glossary Source: https://armeta.ai/resources/glossary/code-compliance-check/ Glossary · Cluster B: Design, permitting and approval # Code compliance check The verification that a design satisfies the requirements of the codes, standards and regulations that apply to it, traced clause by clause to the documents that demonstrate compliance. Last reviewed: August 4, 2026 ## In detail A compliance check has two halves, and the first is the one that gets skipped: establishing exactly which documents apply. The applicable set depends on jurisdiction, facility type, hazard category and date, and it shifts as standards are amended and superseded. Checking a design diligently against the wrong edition is a common and expensive way to be wrong. The second half is the tracing. For each applicable requirement, compliance lives somewhere specific — a dimension on a drawing, a value in a calculation, a material in a specification — and the check connects clause to evidence. Designers self-check as they work, independent reviewers and authorities re-check with fresh eyes, and regulated industries formalise the whole exercise as compliance matrices maintained through the project. The failure mode is that the tracing is manual, voluminous and perishable. A design revision can silently invalidate a compliance demonstration made three months earlier, and a matrix maintained by hand drifts from the documents it indexes. Most compliance findings in formal review are not exotic engineering judgements; they are exactly this drift, found by someone paid to look. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Completeness check | Engineering glossary Source: https://armeta.ai/resources/glossary/completeness-check/ Glossary · Cluster B: Design, permitting and approval # Completeness check A verification that a documentation set contains everything it is required to contain — every document, section, attachment, signature and form — performed before any substantive review begins. Last reviewed: August 4, 2026 ## In detail Completeness checking is the gate in front of the gate. Authorities and expertise bodies check submissions against a codified intake checklist and reject incomplete sets without reading further; owners and contractors run the same discipline on tender packages, vendor documentation and handover dossiers. The logic is procedural fairness and efficiency in one: substantive review clocks should not start on packages that cannot pass. The check is mechanical in principle — does item 14 exist, is it signed, is it the required revision — and laborious in practice, because "the required contents" is itself a moving target that varies by jurisdiction, project category and submission type, and because the set being checked runs to hundreds or thousands of files assembled from multiple organisations. What makes incompleteness expensive is asymmetry. The missing item is usually trivial to produce; the rejection that discovers it costs a full resubmission cycle. Teams that treat completeness as a formality to be checked at the end, rather than a structure the package is assembled into from the start, pay for the same trivial items several cycles in a row. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Submittal | Engineering glossary Source: https://armeta.ai/resources/glossary/submittal/ Glossary · Cluster B: Design, permitting and approval # Submittal A document, drawing, sample or product datasheet that a contractor sends to the design team for review and approval before the associated material is procured or the work executed. Last reviewed: August 4, 2026 ## In detail Submittals — shop drawings, product data, samples, method statements, test plans — are how the contractor's intended reality is checked against the designer's documented intent. The contract specifications define what must be submitted for each work section; the contractor assembles and schedules them; the designer reviews and returns each with an action code on the order of approved, approved as noted, revise and resubmit, or rejected. The submittal log is therefore a shadow schedule. Long-lead equipment cannot be ordered until its submittal clears, which places review turnaround directly on the procurement critical path, and a designer's review backlog converts quietly into site delay. Two misunderstandings cause most submittal disputes. First, approval of a submittal does not transfer design responsibility — the standard review stamps say, in effect, "consistent with design intent", not "we have re-engineered your shop drawing." Second, a submittal that deviates from the specification does not become compliant by being approved unless the deviation was explicitly flagged and accepted; buried deviations surface later as nonconformances with an approval stamp attached, which satisfies nobody. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Non-conformance report (NCR) | Engineering glossary Source: https://armeta.ai/resources/glossary/non-conformance-report-ncr/ Glossary · Cluster B: Design, permitting and approval # Non-conformance report (NCR) A formal record that work, material or documentation has been found not to conform to the specified requirements, together with the decision on what to do about it. Last reviewed: August 4, 2026 ## In detail An NCR is the quality system's honest ledger. It identifies the requirement, describes the departure, and — the part that matters — carries a disposition decided by people with the authority to decide it: use as is, repair, rework, or reject. Use-as-is and repair dispositions are engineering decisions and need the designer's or owner's concurrence, because they amount to accepting something other than what was specified. Beyond the individual case, NCRs are data. Their pattern — which supplier, which work type, which requirement keeps failing — is the cheapest diagnostic a project has, and trend analysis of NCRs is how systemic problems get found before they become systemic failures. The pathology is cultural. Where NCRs are treated as blame instruments, they stop being raised; the nonconformities continue, undocumented, and surface later as surprises with no paper trail. The second pathology is dispositions without analysis — "use as is" as a schedule-pressure reflex rather than an engineering judgement — which converts the quality record into a log of concessions nobody evaluated. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Request for information (RFI) | Engineering glossary Source: https://armeta.ai/resources/glossary/request-for-information-rfi/ Glossary · Cluster B: Design, permitting and approval # Request for information (RFI) A formal written question from the contractor to the design team asking for clarification, missing information or resolution of a conflict in the contract documents. Last reviewed: August 4, 2026 ## In detail RFIs exist because no documentation set is complete and self-consistent, and because on a contract, the answer to an ambiguity has commercial weight and must be written down. The contractor raises the question, the designer answers within a contractual or agreed turnaround, and the answer becomes part of the record — and, if it changes scope, the trigger for a change order. Read in aggregate, the RFI log is a measurement instrument. Its volume and content measure the quality of the documentation: RFIs asking "which revision governs" and "these two drawings disagree" are documentation defects surfacing one at a time, at site prices. Its response times measure the design team's capacity, and slow answers on critical-path work convert directly into delay — and into delay claims. The instrument is also played. RFIs are a recognised claim-building tool, drafted to put ambiguity on the record and start clocks, and design teams answer them accordingly, which can turn a clarification process into correspondence warfare. A project whose RFI log reads like litigation discovery is telling you something about its documents, its contract, or both. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Change order | Engineering glossary Source: https://armeta.ai/resources/glossary/change-order/ Glossary · Cluster B: Design, permitting and approval # Change order A formal, signed modification to the construction contract that changes the scope of work, the contract price, the schedule, or any combination of the three. Last reviewed: August 4, 2026 ## In detail A change order is how a live contract absorbs a changed reality: an owner's added scope, a design development that moved quantities, a site condition nobody priced. The instrument records what changed, what it costs, and what time it adds, and — critically — it is agreed and signed by both parties, converting a potential dispute into administered contract. Pricing comes from the contract's own machinery where possible: bill rates, schedules of rates, or negotiated lump sums where no rate fits. (In FIDIC and UK usage the same instrument is a variation; the mechanics differ in detail, the function is identical.) The discipline that matters is sequence. Work performed ahead of the signed paper — under verbal instruction, under schedule pressure — leaves the contractor carrying cost with no agreed entitlement and the owner facing a claim instead of a change order. Most construction disputes are change orders that never got signed. The quieter failure is cumulative impact. Each change prices its own direct cost, but fifty changes also destroy productivity, sequencing and supervision ratios in ways no individual order captured — a loss both parties can see and neither signed for. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Design basis (also: Basis of design) | Engineering glossary Source: https://armeta.ai/resources/glossary/design-basis-also-basis-of-design/ Glossary · Cluster B: Design, permitting and approval # Design basis (also: Basis of design) The documented set of requirements, criteria, codes, site data and assumptions from which a design is developed — the premises of the project, written down. Last reviewed: August 4, 2026 ## In detail Every design answers to something: the owner's functional requirements, the governing codes and their editions, the site's climate, geotechnical and utility data, capacity and performance targets, and the assumptions standing in for facts not yet known. The design basis is that material captured as a controlled document at the start of design, so that a thousand subsequent decisions are made against the same premises. Usage varies, and the variation is worth knowing. Many organisations use design basis and basis of design interchangeably. Others split them: the design basis as the owner's statement of requirements and constraints, and the basis of design as the designer's response — the document recording which systems, standards and approaches were selected to meet those requirements, and why. On a project where both documents exist, confusing them means confusing the question with the answer. The document fails by standing still. Assumptions get resolved, criteria get renegotiated, codes get updated — and if the basis is not revised with them, the project ends up with disciplines designing to different premises, each of them traceable to an edition of the truth. An out-of-date design basis is worse than none, because it is authoritative and wrong. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Front-end engineering design (FEED) | Engineering glossary Source: https://armeta.ai/resources/glossary/feed-front-end-engineering-design/ Glossary · Cluster B: Design, permitting and approval # Front-end engineering design (FEED) The engineering stage between concept and detailed design in which a project is defined thoroughly enough to fix its cost estimate, support the investment decision and form the basis of EPC tendering. Last reviewed: August 4, 2026 ## In detail FEED takes a selected concept and engineers it to the point of commitment: process design frozen in PFDs and P&IDs, major equipment specified and often priced by vendors, plot plan and layouts settled, the estimate matured to the class the investment decision requires, and the execution strategy — contracting model, schedule, long-lead plan — written down. Its deliverable is not a buildable design; it is a definable, priceable, tenderable one. FEED's economic function is risk transfer. When an EPC contractor bids lump-sum, it prices the FEED package; the completeness and internal consistency of that package determine how much risk premium sits in every bid, and after award, every gap in FEED comes back as a change order with the contractor holding the pen. Money withheld from FEED is not saved; it is borrowed from execution at a poor rate of interest. The stage also has a discipline attached: after FEED, the design is supposed to be frozen. Projects that keep "improving" the definition during EPC discover that they are running FEED and execution simultaneously, which is the most expensive possible way to do either. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Issued for Construction (IFC) | Engineering glossary Source: https://armeta.ai/resources/glossary/issued-for-construction-ifc/ Glossary · Cluster B: Design, permitting and approval # Issued for Construction (IFC) The revision status marking a document as reviewed, approved and released as the version from which construction may proceed. Last reviewed: August 4, 2026 ## In detail Engineering documents move through a ladder of issue statuses — issued for review, for approval, for tender, for design — and issued for construction is the top of it: the revision the contractor is entitled to build from and the owner is entitled to hold the work against. The IFC set is the contractual reality of the design; earlier revisions exist for history, not for building. Not to be confused with the other IFC in this glossary — Industry Foundation Classes, the open data schema for building information models. The two share nothing but the abbreviation, and both appear in the same project correspondence, which is why careful documents spell at least one of them out. IFC status goes wrong in two directions. Building from non-IFC revisions — a superseded print in a site office, a "for review" copy that looked final — is the classic field error, and revision control exists to prevent it. The subtler failure is IFC-in-name-only: documents stamped IFC that still carry holds and clouds, released to keep the schedule's document counts green. An IFC drawing with a hold on it transfers the hold to the site, where it costs the most to resolve. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # As-built documentation | Engineering glossary Source: https://armeta.ai/resources/glossary/as-built-documentation/ Glossary · Cluster B: Design, permitting and approval # As-built documentation Project documentation revised at completion to record what was actually constructed, incorporating every field change, deviation and accepted concession made during the build. Last reviewed: August 4, 2026 ## In detail No project is built exactly as issued. Routings move around obstructions, dimensions get adjusted to conditions, concessions are granted, changes are ordered — and the as-built set is the documentation reconciled to that reality. The conventional workflow is contractor red-line markups maintained during construction, incorporated by the design organisation into revised documents at the end, and delivered as part of the handover package. The consumers are everyone who arrives after the project team leaves: operations and maintenance, inspectors, and above all the engineers of the next modification, for whom the as-builts are the starting truth about the facility. Their accuracy is inherited by every future project on the site. And that is exactly where they fail. As-built production happens at the end of the job, when the budget is spent, the team is demobilising and the incentive to be thorough has left the site; markups go missing, and documents get restamped "as-built" without reconciliation. The gap surfaces years later, on the brownfield project whose first work package is discovering what was actually built — a survey exercise paid for because the last project's final deliverable was fiction. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Handover package | Engineering glossary Source: https://armeta.ai/resources/glossary/handover-package/ Glossary · Cluster B: Design, permitting and approval # Handover package The structured set of documentation transferred from the project to the owner at completion — as-builts, vendor documents, certificates, test records and operating information — constituting the asset's permanent record. Last reviewed: August 4, 2026 ## In detail When a project ends, the asset begins, and the handover package is what the asset gets to keep: as-built drawings and models, vendor manuals and datasheets, material and welding certificates, inspection and test records, commissioning results, permits and regulatory conclusions, spare parts data. The contents and structure are specified by the contract and the owner's information requirements, in some industries against formal information standards; completion of the package is typically tied to payment milestones, which is frequently the only reason it gets finished. The package's real customer is time. Operations runs on it, regulators audit against it, and decades of future maintenance, integrity management and modification projects will treat it as the ground truth about the facility. A certificate that cannot be found in year fifteen is, functionally, a component with no provenance. It fails the way as-builts fail, and for the same reason: assembled at the end, from whatever survived, by whoever is left. Owners who treat handover as a continuous obligation — documents delivered, verified and indexed progressively through execution — get an asset record; owners who treat it as a closing formality get boxes. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Professional engineer seal | Engineering glossary Source: https://armeta.ai/resources/glossary/professional-engineer-seal/ Glossary · Cluster B: Design, permitting and approval # Professional engineer seal The stamp of a licensed professional engineer applied to design documents in US and Canadian practice, signifying that the work was prepared by or under the direct supervision of that engineer, who accepts legal responsibility for it. Last reviewed: August 4, 2026 ## In detail In North American jurisdictions, engineering is a licensed profession and the seal is its instrument of accountability. State and provincial law defines which documents must be sealed for permitting and construction, and the sealing engineer must have been in responsible charge — the work done by them or under their direct supervision. The seal does not certify perfection; it attaches a named, licensed, disciplinable professional to the standard of care. The seal interacts with the review system rather than replacing it. Authorities in seal-based systems typically review less engineering substance than expertise-based systems do, precisely because responsibility already sits with the licensee — a structural difference worth understanding when projects cross between the two worlds. The characteristic abuse has a name: plan stamping — sealing work the engineer did not actually supervise, as a paid formality. It is a licence-revoking offence, and it exists because the seal is genuinely load-bearing: it is the difference between a drawing and a legal document. The mundane failures are administrative — expired licences, wrong-state seals, unsigned electronic stamps — and they stop submissions just as thoroughly as bad engineering. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Signature and seal requirements | Engineering glossary Source: https://armeta.ai/resources/glossary/signature-and-seal-requirements/ Glossary · Cluster B: Design, permitting and approval # Signature and seal requirements The rules, differing by jurisdiction, that determine who must sign, approve or stamp design documents for those documents to be valid for permitting and construction. Last reviewed: August 4, 2026 ## In detail Every jurisdiction attaches personal or organisational accountability to design documents; they just do it differently. North America runs on the licensed engineer's seal. Other systems run on chartered or registered professional regimes, on authorising signatures of designated project roles — in CIS practice, the chief project engineer's signature carries the integrating responsibility for the whole design — or on the licence and certification of the design organisation itself rather than the individual. Increasingly, all of them run on qualified electronic signatures, with their own validity rules layered on top. For anyone working across borders, these regimes are not interchangeable formats of the same thing; they allocate liability differently, and a document set perfectly authorised in one system can be legally unsigned in another. International projects routinely discover this at submission time. The failure mode is formal and total: signature defects are completeness-check rejections, and they reject the whole package. Wrong signatory role, missing counter-signature, a scan where a qualified e-signature was required — none of it is engineering, all of it is calendar time, and it is the most preventable class of rejection there is. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Revision control | Engineering glossary Source: https://armeta.ai/resources/glossary/revision-control/ Glossary · Cluster B: Design, permitting and approval # Revision control The discipline of identifying, tracking and distributing document versions so that at any moment there is exactly one revision of each document that everyone agrees is current. Last reviewed: August 4, 2026 ## In detail Every controlled document carries a revision code, an issue status, and a revision history recording what changed, when, by whom and why; a document management system or register tracks which revision is current and who holds copies; superseded revisions are marked or withdrawn. The machinery is unglamorous and universal, because every downstream activity — estimating, review, procurement, construction — is only correct with respect to a specific revision. Which is the point: nearly every documentation failure in this glossary is a revision-control failure wearing a costume. The estimate built on the superseded drawing, the compliance check against the outdated standard, the site working from last month's print, the two disciplines resolving the same interface differently — all of them are, mechanically, someone consuming revision N while the truth moved to N+1. Control degrades at the edges: the uncontrolled copy saved to a desktop, the marked-up PDF emailed outside the system, the vendor working from the revision attached to the purchase order months ago. The system knows what is current; the project runs on what people actually have open — and closing that gap is a permanent, manual, repeated effort on every project that has ever existed. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Detailed design (detail engineering) | Engineering glossary Source: https://armeta.ai/resources/glossary/detailed-design-detail-engineering/ Glossary · Cluster B: Design, permitting and approval # Detailed design (detail engineering) The engineering stage that converts a defined project into buildable documentation — the full set of drawings, models, isometrics, schedules and take-offs from which construction and procurement actually proceed. Last reviewed: August 4, 2026 ## In detail Where FEED decides what the project is, detailed design works out every remaining fact of it: piping engineered isometric by isometric, structures down to connections and rebar, cable by cable, instrument by instrument, with the 3D model coordinated across disciplines and the final material take-offs extracted from the result. It is the volume stage of engineering — most of the documents, most of the hours — performed by the EPC contractor's engineering organisation or a design institute, and consumed directly by procurement and the site. Its productivity depends almost entirely on what it inherits. Detail engineering on a frozen, consistent FEED basis is production; on an unfrozen basis it is rework at production headcount, with every upstream change rippling through hundreds of issued documents. The stage also runs concurrently with procurement and early construction, so its sequencing is dictated by the site's needs — and a detail-design effort that falls behind the construction sequence turns the entire project into a queue behind engineering. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Working documentation (the design/working split) | Engineering glossary Source: https://armeta.ai/resources/glossary/working-documentation-the-design-working-split/ Glossary · Cluster B: Design, permitting and approval # Working documentation (the design/working split) In CIS practice, the second of two documentation stages: the construction-level documents developed after the approved design documentation, which is the stage that undergoes state examination. Last reviewed: August 4, 2026 ## In detail CIS jurisdictions split documentation into two codified stages. Design documentation establishes the project's substance — layouts, engineering solutions, cost estimates — in a regulated structure, and it is this stage that goes through state examination and grounds the construction permit. Working documentation is then developed from the approved design: the detailed drawings, schedules and specifications the site actually builds from, roughly analogous to detailed-design deliverables or construction documents elsewhere, but defined by its own norms. The split has a consequence worth understanding: the examined stage and the built-from stage are different document sets. The working documentation must conform to the approved design documentation, and divergence between them — accumulated through detail development and field decisions — is a compliance question, not merely a coordination one, with re-examination triggered if the changes cross defined thresholds. International projects stumble on the mapping. The two-stage split is close enough to FEED-then-detailed-design to invite one-to-one translation and different enough to punish it; content that belongs in one system's first stage sits in the other's second, and a schedule or contract built on the false equivalence misplaces both the review cycle and the freeze point. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Interdisciplinary check (IDC / squad check) | Engineering glossary Source: https://armeta.ai/resources/glossary/interdisciplinary-check-idc-squad-check/ Glossary · Cluster B: Design, permitting and approval # Interdisciplinary check (IDC / squad check) The formal circulation of one discipline's deliverables to all affected disciplines for review and comment before the documents are issued. Last reviewed: August 4, 2026 ## In detail Engineering disciplines design in parallel and collide in the facility: the pipe routes through the steel, the cable tray wants the same corridor, the equipment nozzle loads the structure someone else sized. The interdisciplinary check is the procedural answer — before a deliverable is issued, it circulates to the disciplines it touches, each reviews for its own interfaces, comments are logged and dispositioned, and the issue goes out carrying the evidence. The check's value is exactly proportional to the attention paid, which is its weakness. IDC arrives as a deadline-adjacent task in every reviewer's queue, on top of their own production work, and the degraded form is familiar everywhere: signatures collected, interfaces unexamined. The comment log distinguishes the two — a real IDC leaves findings; a ritual one leaves initials. What the check misses gets found later by more expensive methods: clash detection in the model if the project runs one, and the site if it does not. Every field-discovered interference is an interface that some IDC, somewhere, signed past. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Master document register (MDR) | Engineering glossary Source: https://armeta.ai/resources/glossary/master-document-register-mdr/ Glossary · Cluster B: Design, permitting and approval # Master document register (MDR) The controlled index of every document a project will produce — with numbers, titles, revisions, statuses and planned dates — serving as both the catalogue of the documentation and the instrument for measuring engineering progress. Last reviewed: August 4, 2026 ## In detail The MDR is the documentation set's table of contents, written before the book: at project start the deliverables are enumerated, numbered and scheduled, and thereafter the register tracks each one's current revision, status and dates, planned against actual. Document control maintains it; engineering management runs on it, because deliverable counts and status-weighted progress against the MDR are the standard measure of how engineering is actually doing. Its quiet governing rule is that the register defines existence: a deliverable not on the MDR is not planned, not scheduled, not progressed and not missed — until it is suddenly needed. Scope discovered late usually turns out to have been absent from the register all along. As a progress instrument it invites gaming, and gets it: documents issued prematurely to move status counts, revisions cycling without converging, the register reporting ninety percent while the site waits for the ten percent that matters. An MDR measures document status faithfully; whether document status measures engineering is a question the register cannot answer about itself. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Transmittal | Engineering glossary Source: https://armeta.ai/resources/glossary/transmittal/ Glossary · Cluster B: Design, permitting and approval # Transmittal The formal cover record accompanying documents sent between project parties, establishing exactly which documents, at which revisions, were sent to whom, when and for what purpose. Last reviewed: August 4, 2026 ## In detail A transmittal is a small bureaucratic instrument with a large evidentiary job. Each one lists the enclosed documents with their revision codes, names the sender and recipient, states the purpose of issue — for review, for approval, for construction — and gets logged and numbered. Together the transmittal log answers the question that decides arguments: who had what information, as of when. That question turns out to be the hinge of most documentation disputes. Whether the contractor built from a superseded revision because the update was never sent, or despite receiving it, is the difference between the designer's problem and the contractor's — and the transmittal record is where the answer lives. Delay claims, defect allocations and change-order entitlement all reach for the same log. The system fails informally. Documents shared by email attachment, link or portal upload outside the transmittal process move information without moving the record, and the project develops two histories: what was formally issued and what people actually received. In quiet times nobody notices the divergence; in a dispute, the informal history is precisely the one that cannot be proven. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Vendor documentation | Engineering glossary Source: https://armeta.ai/resources/glossary/vendor-documentation/ Glossary · Cluster B: Design, permitting and approval # Vendor documentation The documents produced by equipment suppliers — drawings, datasheets, calculations, manuals and certificates — that must be reviewed by the project and integrated into its documentation set. Last reviewed: August 4, 2026 ## In detail Purchased equipment arrives with paper attached, and the paper is on the critical path more often than the equipment. The vendor's certified drawings carry the facts detail design is waiting for — footprints, nozzle positions, loads, connection sizes — and until they arrive and clear review, the foundations, piping and cabling around that equipment are engineered on assumptions. Each purchase order therefore specifies the vendor document requirements and their schedule, and the review cycle runs through the project's document control like any other deliverable set. The friction is structural: vendors produce documentation as a cost after winning the order, projects consume it as an input to everything downstream, and the two incentives meet in the expediting function. Late or repeatedly-rejected vendor data stalls engineering in ways the procurement schedule never shows. At the other end of the project, vendor documentation becomes a completeness problem: the certificates, manuals and final drawings owed to the handover package, collectable cheaply while the vendor still wants the final payment and expensively forever after. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Deviation request (concession) | Engineering glossary Source: https://armeta.ai/resources/glossary/deviation-request-concession/ Glossary · Cluster B: Design, permitting and approval # Deviation request (concession) A formal request, raised before the work is done, for permission to depart from a specified requirement — as distinct from a non-conformance report, which records a departure after the fact. Last reviewed: August 4, 2026 ## In detail Specifications meet reality ahead of time too: a material unavailable in the specified grade, a vendor's standard design that differs from the datasheet, a tolerance the chosen method cannot hold. The deviation request (in some systems, concession or waiver) puts the departure on the table before it happens — describing the requirement, the proposed departure, the justification and the technical assessment — for the owner or designer to accept, reject or accept with conditions. Approved, it becomes a documented, bounded exception; the timing is the entire difference between asking and confessing. Two disciplines keep the instrument honest. The first is scope: a concession applies to the case it describes — this batch, this unit, this once — and treating one as precedent quietly rewrites the specification without anyone deciding to. The second is the register: concessions accumulate, and their aggregate is a fact about the asset that the handover documentation must carry. A facility's real specification is the written one as amended by every concession granted along the way — which is only knowable if someone kept the list. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Hold | Engineering glossary Source: https://armeta.ai/resources/glossary/hold/ Glossary · Cluster B: Design, permitting and approval # Hold A marked restriction meaning "do not proceed past this point without resolution" — applied on drawings to areas pending information, and in inspection plans to work stages requiring sign-off before continuing. Last reviewed: August 4, 2026 ## In detail The word carries two related instruments, and this glossary's intro warned you about words like this. On documents, a hold is a clouded area of a drawing marked HOLD, flagging content that is unresolved — awaiting vendor data, a pending decision, an unconfirmed interface — on a document otherwise mature enough to issue. The hold list is tracked, and each hold is a small debt: the drawing is usable everywhere except the one place it isn't. In quality plans, a hold point is a stage in the work — before the concrete pour, before the weld is covered — past which the contractor may not proceed until a designated party has inspected and released it. Its softer sibling, the witness point, requires notification but allows work to continue; the hold point stops the job. The distinction is who bears the cost of proceeding: past a witness point, the inspector missed it; past a hold point, the contractor broke it. Both instruments fail the same way — under schedule pressure. Documents get issued for construction with holds still open, transferring the unresolved question to the field; hold points get worked through with the release signature collected afterwards. In each case the mechanism functioned perfectly as paperwork and not at all as control. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Management of change (MOC) | Engineering glossary Source: https://armeta.ai/resources/glossary/moc-management-of-change/ Glossary · Cluster B: Design, permitting and approval # Management of change (MOC) A formal process for evaluating, approving and documenting changes to a design, process or facility after its basis has been established, ensuring each change is reviewed for its consequences before it is made. Last reviewed: August 4, 2026 ## In detail Management of change begins from an uncomfortable fact: a design reviewed as a whole is safe as a whole, and every subsequent change re-opens the question locally. MOC procedure requires that a proposed change — to equipment, process conditions, materials, procedures or documents — be described, its technical and safety implications assessed by people competent to see them, approvals obtained at a level matching the risk, and the affected documentation updated before or promptly after implementation. In the process industries the discipline is regulatory, born of accidents caused by modifications nobody re-analysed; its formal boundary is the replacement-in-kind test — like-for-like replacement needs no MOC, anything else does. The boundary is where the process erodes. "Minor" changes, urgent changes, temporary changes that become permanent — each is a category of modification that slips past review precisely because it seemed too small to need one, and the accident record of the process industries is substantially a record of such changes. The second erosion is documentary: changes managed and approved but never propagated into the drawings, so the facility drifts from its documentation one authorised increment at a time — an as-built problem being manufactured in real time. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Punch list | Engineering glossary Source: https://armeta.ai/resources/glossary/punch-list/ Glossary · Cluster B: Design, permitting and approval # Punch list The list of incomplete, defective or outstanding items identified as a project approaches completion, each to be corrected and signed off before the work is finally accepted. Last reviewed: August 4, 2026 ## In detail As a project nears the end, walkdowns by the contractor, owner and designer sweep the work systematically and record everything short of complete: the unfinished, the damaged, the nonconforming-but-minor, the missing. The punch list (snag list, in UK usage) is that record — item, location, responsible party, status — and closing it out is the mechanics of getting from nearly-done to accepted, typically with money retained against completion. Mature projects categorise the items, because not all incompleteness is equal: items that affect safety or prevent operation must close before the next milestone — mechanical completion, energisation, handover — while cosmetic items may trail into the post-handover period by agreement. The categories are where the negotiation lives: what the contractor calls trailing paint, the owner may call an unfinished system. The list fails by arriving late and long. Punching compressed into the final weeks produces thousands of items at maximum schedule pressure and minimum contractor presence — closure slows precisely when everyone wants it fastest. Progressive punching, area by area as work completes, produces the same list earlier, shorter and cheaper; the difference is entirely in when someone chose to look. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Authority having jurisdiction (AHJ) | Engineering glossary Source: https://armeta.ai/resources/glossary/authority-having-jurisdiction-ahj/ Glossary · Cluster B: Design, permitting and approval # Authority having jurisdiction (AHJ) The organisation, office or official with the legal authority to enforce a code or regulation on a project and to approve or reject the work under it. Last reviewed: August 4, 2026 ## In detail "The authority" is grammatically singular and practically plural. A single project answers to a building authority, a fire authority, environmental regulators, utility companies with connection requirements, labour and technical-safety inspectorates, and — depending on the facility — industry-specific supervisory bodies, each an AHJ for its own domain, each with its own submissions, review cycles, inspections and approvals. The term itself comes from code language: the codes name the role abstractly precisely because who fills it varies by place and subject. Two properties of AHJs shape project planning. First, interpretation is part of their authority: the same code clause can be read differently by different offices, and the local reading is the operative one — which is why experienced teams engage AHJs early rather than discovering interpretations at review. Second, AHJs do not coordinate with each other; requirements can conflict, and reconciling them is the project's job, not theirs. The planning failure is the uncounted authority: an AHJ discovered late, with its own submission requirements and its own clock, inserted into a schedule that assumed the permit path was already fully enumerated. Enumerating the authorities is the first permitting deliverable, and the cheapest. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Design documentation; Permitting package; Building permit Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Standard | Engineering glossary Source: https://armeta.ai/resources/glossary/standard/ Glossary · Cluster C: Standards and normative base # Standard A document, established by consensus and approved by a recognised body, that sets out requirements, rules or characteristics for products, processes or services, intended for common and repeated use. Last reviewed: August 4, 2026 ## In detail Standards are written by committees — of national bodies, international organisations or industry societies — through a consensus process, and they exist so that the same technical question does not have to be answered from first principles on every project. A standard for pipe defines the pipe once; every specification thereafter can simply cite it. By nature a standard is voluntary. It acquires force through two doors: a law or regulation that incorporates it, or a contract or specification that cites it — after which "voluntary" is a description of its origin, not of anyone's obligations. A standard is also a dated object: it exists in editions, with amendments and corrections layered on, and a claim of compliance means little without the edition attached. The everyday failure is treating a standard's name as sufficient identification. Two parties both "complying with the standard" while holding different editions are complying with different documents — and the differences between editions are precisely the clauses somebody thought worth changing. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Code; Technical regulation; Normative base Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Code | Engineering glossary Source: https://armeta.ai/resources/glossary/code/ Glossary · Cluster C: Standards and normative base # Code In construction usage, a body of minimum mandatory requirements for the design and construction of facilities, given legal force by the jurisdiction that adopts it. Last reviewed: August 4, 2026 ## In detail A code is a standard with a badge. Building codes, fire codes and energy codes set the floor that all construction in a jurisdiction must meet, and they typically work by stating what must be achieved and then referencing standards for the detailed how — which is the practical division of labour between the two words: the code obliges, the standards it cites specify. Most codes begin life as model documents — the International Building Code is the prominent example — written by a code-development body and then adopted by each jurisdiction, almost always with local amendments and almost never at the newest edition. The operative law is therefore the adopted edition plus the amendments, not the model text, and "code compliance" is meaningless without knowing which combination governs the site. The word has a second life in the process industries, where documents like the ASME Boiler and Pressure Vessel Code are called codes by tradition: technically standards, but so widely adopted into law for pressure equipment that the traditional name tells the truth about their status. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Technical regulation; Normative base Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Technical regulation | Engineering glossary Source: https://armeta.ai/resources/glossary/technical-regulation/ Glossary · Cluster C: Standards and normative base # Technical regulation A government-issued document laying down mandatory requirements for products or their related processes, with which compliance is compulsory as a matter of law rather than choice. Last reviewed: August 4, 2026 ## In detail Technical regulation is the top layer of the modern two-layer architecture used by the EU, the Eurasian Economic Union and others: the regulation states the essential, mandatory requirements — safety, health, environment — and stays deliberately general, while voluntary standards underneath it provide detailed methods whose use grants a presumption of conformity with the regulation. Follow the listed standard and you are presumed compliant; follow another route and you carry the burden of demonstrating equivalence yourself. The architecture's purpose is to keep the law stable while the technology moves: regulations change rarely, the standards lists under them update continuously. Its price is that compliance becomes a two-document question — what the regulation requires, and which standards currently deliver presumption — and the second half moves. The recurring confusion is between the layers: citing a standard where the regulation is the legal obligation, or treating the regulation's general language as satisfiable without any recognised method at all. On cross-border projects, add a third confusion — assuming the layers divide the same way in every system. They do not. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Normative base Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Normative base | Engineering glossary Source: https://armeta.ai/resources/glossary/normative-base/ Glossary · Cluster C: Standards and normative base # Normative base The complete body of normative documents — codes, standards, technical regulations and norms — in force for a given jurisdiction, sector or project at a given point in time. Last reviewed: August 4, 2026 ## In detail Every design answers to a collection of documents, and the normative base is that collection considered as a whole. In CIS practice the term is literal and institutional: the normative base is codified, registered and maintained by the state, and expert review checks designs against it as a defined corpus. In other systems the same object exists less formally, as "the applicable codes and standards" — assembled per project, listed in the design basis, and no less binding for being uncodified. The base's defining property is motion. Standards are amended, superseded and withdrawn continuously; regulations change on political timescales; and the set that was in force when a design started differs from the set in force when it is reviewed. Projects therefore freeze a basis — the specific editions that govern this design — and manage departures from the freeze as changes. The failure is checking against different snapshots: the designer against the editions from project start, the reviewer against today's register, the specification citing a third vintage from the master spec it was copied from. All three are checking diligently; none are checking the same base. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Superseded standard | Engineering glossary Source: https://armeta.ai/resources/glossary/superseded-standard/ Glossary · Cluster C: Standards and normative base # Superseded standard A standard that has been replaced by a newer edition or a different document and is no longer the current version — though it may still legitimately govern existing designs, contracts and facilities. Last reviewed: August 4, 2026 ## In detail Standards die in two ways, and the difference matters. A superseded standard has a successor: the new edition or replacing document is now current, and the old one remains published for reference. A withdrawn standard has been removed without replacement — its subject no longer standardised, or absorbed elsewhere. Both remain applicable to what was built or contracted under them: a facility designed to the edition in force at the time is not made non-compliant by later editions, and in-service assessment is generally against the original basis unless law says otherwise. The problems run in both directions. Forward: new submissions citing superseded editions — usually inherited from a copy-pasted specification or an unmaintained master document — which is among the most common findings in formal review, and among the most mechanical to make. Backward: automatic "always use the latest" updating in mid-project, which silently breaks a frozen design basis and can invalidate completed calculations. The discipline is the same in both cases: every citation carries an edition, and every edition decision is deliberate. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Mandatory vs voluntary standard | Engineering glossary Source: https://armeta.ai/resources/glossary/mandatory-vs-voluntary-standard/ Glossary · Cluster C: Standards and normative base # Mandatory vs voluntary standard The distinction between standards whose application is required by law and those applied by choice — with the caveat that a voluntary standard becomes binding the moment a regulation or contract cites it. Last reviewed: August 4, 2026 ## In detail No standard is mandatory by birth; mandatoriness is conferred. The mechanisms vary by system: incorporation by reference into law, inclusion in a government-maintained mandatory list, citation under a technical regulation as the route to presumed conformity, or — the mechanism that catches people — citation in a contract or project specification, which makes a voluntary standard as binding as any statute for the parties who signed. The mapping also differs by jurisdiction for the same document. A standard voluntary at home may be mandatory where it has been adopted into another country's regulation; interstate and international standards carry different statuses in each adopting state. A project's compliance obligations are therefore a matrix — document by document, jurisdiction by jurisdiction — not a property of the standards themselves. The operational failure is the word "voluntary" doing too much work: a designer treating a spec-cited standard as optional guidance, or a reviewer demanding a standard that is voluntary and uncited. Both arguments end the same way — by finding the document that does or does not confer the obligation. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Harmonised standard | Engineering glossary Source: https://armeta.ai/resources/glossary/harmonised-standard/ Glossary · Cluster C: Standards and normative base # Harmonised standard In EU usage, a European standard developed at the European Commission's request and cited in the Official Journal, so that compliance with it grants presumption of conformity with EU legislation; more loosely, any standard aligned across jurisdictions. Last reviewed: August 4, 2026 ## In detail The precise meaning is a legal mechanism. Under the EU's New Approach, legislation states essential requirements, the Commission requests supporting standards from the European standardisation bodies, and once a resulting standard is cited in the Official Journal it becomes harmonised: using it creates the legal presumption that the essential requirements are met. The standard stays voluntary; the presumption is what you buy by following it. Construction products, machinery and pressure equipment all run on this machinery. The looser meaning — standards aligned between countries — describes a broader family: international standards adopted identically as national ones, interstate standards shared across the CIS, bilateral equivalence arrangements. Alignment reduces the translation cost of cross-border work, which is why everyone pursues it. The trap in both senses is assuming harmonised means identical in effect. Harmonised European standards still interact with national annexes and national implementations; adopted international standards acquire national deviations. Harmonisation narrows the differences; it rarely eliminates them, and the residue is exactly where cross-border designs get comments. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Specification | Engineering glossary Source: https://armeta.ai/resources/glossary/specification/ Glossary · Cluster C: Standards and normative base # Specification A project document that defines the requirements for the materials, products, workmanship and performance of a particular scope of work — the written half of the design, alongside the drawings. Last reviewed: August 4, 2026 ## In detail Where standards are written for everyone, specifications are written for this project: which pipe from the standard's options, which finish, which tests, which submittals, to what acceptance criteria. They are produced by the design organisation, structured by work sections, and consumed by bidders pricing them, contractors executing them, and inspectors holding work to them. With the drawings they form the contract's technical content, with a stated order of precedence for when the two disagree. Specifications divide by philosophy: prescriptive specs state exactly what to provide and how; performance specs state what the result must achieve and leave method to the contractor — a risk-allocation choice as much as a technical one, since whoever chooses the method owns its failure. In practice most specifications descend from master documents, edited per project — and that lineage is their weakness. Master specs accumulate superseded standard citations, options irrelevant to this project, and requirements contradicting these drawings; unedited residue becomes contractual text. A large share of RFIs, review findings and disputes trace to specification content nobody consciously chose. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Datasheet | Engineering glossary Source: https://armeta.ai/resources/glossary/datasheet/ Glossary · Cluster C: Standards and normative base # Datasheet A structured document recording the defining technical parameters of a specific equipment item or instrument — its duty, operating conditions, materials, dimensions and connections — maintained from requisition through vendor completion to as-built. Last reviewed: August 4, 2026 ## In detail A datasheet is the biography of a tagged item, written by several hands in sequence. Process engineering enters the duty and conditions; the mechanical or instrument discipline adds construction requirements; the datasheet then travels with the requisition to bidders, returns completed with the vendor's actuals, and settles into the project's records as the item's definitive description — consumed along the way by piping, electrical, civil and instrumentation, each taking the parameters that drive their own design. Its format is deliberately standardised — industry-standard datasheet forms exist for most equipment classes — because the document's value is that every reader knows where every parameter lives. Its failure is distributed truth. The same value — a flow, a rating, a nozzle size — exists on the datasheet, the P&ID, the model and the vendor drawing, and revisions do not reach all four at once. The datasheet that disagrees with the P&ID is a classic review finding and a classic field surprise, and reconciling tagged-item data across documents is one of engineering's permanent, manual background tasks. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Eurocodes | Engineering glossary Source: https://armeta.ai/resources/glossary/eurocodes/ Glossary · Cluster C: Standards and normative base # Eurocodes The suite of ten European standards, EN 1990 to EN 1999, governing structural and geotechnical design, applied together with the national annex of the country where the structure will be built. Last reviewed: August 4, 2026 ## In detail The Eurocodes cover the structural canon: the basis of design and actions on structures, then design in concrete, steel, composite, timber, masonry and aluminium, plus geotechnical and seismic design. They are the mandatory basis for structural design across most of Europe and have been adopted or admitted well beyond it — including in Kazakhstan, where they stand as a permitted alternative to the national construction norms, with Kazakh national annexes. Their architecture is the pairing rule: the codes deliberately leave safety-level and climate-dependent choices — partial factors, snow, wind, seismicity — as Nationally Determined Parameters, set in each country's national annex. A Eurocode calculation is complete only as code plus annex, and the annex is chosen by where the structure stands, not where the designer sits. The corresponding failures: designing with the annex of the engineer's home market, mixing parameters from different annexes in one design, or using the bare code where no annex exists without documenting the parameter choices. A second generation of the suite is progressively being published, which will re-run every one of those edition questions across the industry. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # International Building Code (IBC) | Engineering glossary Source: https://armeta.ai/resources/glossary/international-building-code-ibc/ Glossary · Cluster C: Standards and normative base # International Building Code (IBC) A model building code published by the International Code Council, adopted — usually with amendments — by jurisdictions across the United States and in several other countries as the legal basis of building regulation. Last reviewed: August 4, 2026 ## In detail The IBC is the flagship of the I-Code family, a coordinated set of model codes covering buildings, fire, plumbing, mechanical systems, energy and more, revised on a three-year cycle. As a model document it has no force anywhere by itself; each state or local jurisdiction adopts a specific edition, attaches its own amendments, and thereby turns the model into law for its territory. The code regulates by occupancy and risk — use classifications, construction types, heights and areas, egress, fire protection, structural criteria — and does much of its detailed work by referencing standards, pulling large parts of the standards world into law by citation. The practical consequence of the adoption model is fragmentation with a common skeleton: neighbouring jurisdictions can be on different editions with different amendments, and "IBC-compliant" is not a property a design can have in the abstract. The first question of any US project is which edition, as amended by whom — and the answer decides real requirements, because the three-year cycles are not cosmetic. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # ISO | Engineering glossary Source: https://armeta.ai/resources/glossary/iso/ Glossary · Cluster C: Standards and normative base # ISO The International Organization for Standardization — a worldwide federation of national standards bodies that develops voluntary international standards across nearly every field of technology, industry and management. Last reviewed: August 4, 2026 ## In detail ISO standards are written in technical committees staffed through national member bodies, approved by international ballot, and published as the closest thing the world has to a common technical language — tens of thousands of standards spanning materials, dimensions, testing, data, and the management-system standards (quality, environment, occupational safety) by which organisations get certified. The organisation explains its short name not as an acronym but as a coinage from the Greek isos, equal — the same in every language. ISO standards reach projects through adoption: published identically as European standards (EN ISO), taken into national catalogues by member bodies, cited by contracts and regulations. Alongside ISO sits its electrotechnical sibling, the IEC, with which it divides the technical world by long-standing agreement. The everyday abuses are linguistic. "ISO certified" as a free-floating quality claim means nothing — organisations certify to specific standards, and certification to a quality-management standard says the system is managed, not that any product is good. And an ISO citation, like any other, is incomplete without its edition. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # National annex | Engineering glossary Source: https://armeta.ai/resources/glossary/national-annex/ Glossary · Cluster C: Standards and normative base # National annex A country-specific supplement to an international or European standard that fixes the parameters and choices the parent standard leaves open to national determination, making the standard usable in that jurisdiction. Last reviewed: August 4, 2026 ## In detail International standardisation runs into national facts: climates differ, seismicity differs, and — less visibly — accepted levels of safety and cost differ, as sovereign choices. The national annex is the container for those facts. The parent standard defines the method and marks the open slots; the annex of each adopting country fills them — the partial factors, the load maps, the choices among permitted alternatives — and may add non-contradictory guidance of its own. The Eurocodes are the canonical case, but the pattern recurs wherever an international standard is nationally adopted. The operating rule is that the annex follows the structure: a bridge in one country is designed to the shared code with that country's annex, whoever designs it and wherever they sit. Multi-country portfolios therefore run one method with several parameter sets — the efficiency the system was built to deliver. The failures are parameter failures: the home-market annex used abroad, values from two annexes mixed in one calculation, or an adoption so new that the annex does not yet exist, leaving the parameters to be chosen and justified case by case — a fact best discovered before the review, not during it. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Clause reference | Engineering glossary Source: https://armeta.ai/resources/glossary/clause-reference/ Glossary · Cluster C: Standards and normative base # Clause reference A citation of a specific numbered provision within a standard or code — the level at which compliance is actually demonstrated, disputed and reviewed. Last reviewed: August 4, 2026 ## In detail Nobody complies with a standard in general; they comply with its clauses in particular. The clause is where the requirement lives, and clause references are the working currency of technical review — comments cite them, compliance matrices index by them, contracts incorporate by them, and expert conclusions stand on them. A finding that names its clause can be checked in a minute; a finding that gestures at a document invites a correspondence cycle instead. The fragility of the currency is that clause numbering belongs to an edition. Standards are restructured when revised, and clause 6.3.2 of one edition may be renumbered, merged or deleted in the next — so a clause reference without a dated edition is a pointer into an unspecified document, and automated cross-references break silently when the underlying edition moves. The craft, small but real: cite document, edition and clause together; quote the operative words where the stakes justify it; and when checking someone else's reference, verify the clause says what the citation claims — a nontrivial fraction do not, having been carried forward from an edition where they did. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # SNIP | Engineering glossary Source: https://armeta.ai/resources/glossary/snip/ Glossary · Cluster C: Standards and normative base # SNIP The construction norms and rules of the Soviet standardisation system — the ancestor of today's CIS construction codes, largely superseded, still widely cited by habit and searched by name. Last reviewed: August 4, 2026 ## In detail SNiP — stroitel'nye normy i pravila, construction norms and rules — was the backbone of Soviet construction regulation: a comprehensive, mandatory, state-issued corpus covering design, construction and estimating, applied uniformly across the union. Its successor states inherited it wholesale and have spent three decades reforming it along diverging paths: Russia reissued much of the corpus as svody pravil (SP) under its own technical-regulation framework; Kazakhstan replaced it in its 2015 reform with the SN RK / SP RK system and admitted the Eurocodes as an alternative; other republics ran their own versions of the same transition. The word outlived the documents. Engineers across the region still say "per SNiP" meaning "per the construction norms", search engines still receive the term daily, and legacy projects, old contracts and archived documentation cite SNiP designations that must be traced to their current successors — a mapping exercise with real content, because the successors are revisions, not renames. Citing a SNiP designation in a new submission is a standard review finding; assuming its successor says the same thing is the quieter mistake. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # GOST | Engineering glossary Source: https://armeta.ai/resources/glossary/gost/ Glossary · Cluster C: Standards and normative base # GOST The standards of the Soviet and post-Soviet standardisation system — today, interstate standards maintained across the CIS, alongside national derivatives such as Russia's GOST R and Kazakhstan's ST RK. Last reviewed: August 4, 2026 ## In detail GOST began as the all-union state standard and survived the union as an interstate one: standards adopted through the CIS-region interstate standardisation council apply across member states, forming a shared technical layer — the region's own harmonisation machinery — while each state also issues national standards (GOST R in Russia, ST RK in Kazakhstan) for its own needs. The corpus covers materials, products, test methods and documentation rules, and remains deeply embedded in the region's specifications, procurement and manufacturing. Their legal status has inverted over time: once mandatory by default, GOST standards are now generally voluntary, becoming binding through the modern mechanisms — listing under technical regulations, incorporation into law, or citation in contracts. Old instincts die harder than old rules, and the assumption that "it's a GOST, therefore mandatory" persists a generation after it stopped being true. For international projects the recurring work is equivalence: GOST materials against ASTM or EN grades, GOST test methods against ISO ones. Equivalence tables exist and are approximations; the grades are cousins, not twins, and pressure-boundary and structural applications deserve the comparison at property level, not table level. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # SN RK and SP RK | Engineering glossary Source: https://armeta.ai/resources/glossary/sn-rk-and-sp-rk/ Glossary · Cluster C: Standards and normative base # SN RK and SP RK Kazakhstan's construction normative system: SN RK, the state building norms carrying mandatory requirements, and SP RK, the rules sets providing accepted methods of meeting them — with the Eurocodes admitted as an alternative design route. Last reviewed: August 4, 2026 ## In detail Kazakhstan's 2015 reform of its construction normative base replaced the inherited SNiP model with a two-tier, performance-oriented structure on the European pattern: SN RK documents state the mandatory requirements — what must be achieved — while the paired SP RK documents provide deemed-to-satisfy methods of achieving them. Following the SP is the presumptive route to compliance; departing from it is permitted with justification, which is the essence of the parametric approach the reform adopted. The same reform admitted the Eurocodes, with Kazakh national annexes, as an alternative basis for structural design — placing Kazakhstan among the jurisdictions where two complete design routes coexist. The routes are alternatives, not ingredients: a design proceeds down one or the other, and mixing norms from both in a single calculation is a review finding waiting to be written. Two further confusions recur. Russian SP and Kazakh SP RK share an abbreviation, an ancestor and often a subject — and are different documents under different frameworks; citations must not migrate between them by resemblance. And legacy SNiP RK references persist in older materials, needing translation to their current successors rather than literal reuse. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # EAEU technical regulations | Engineering glossary Source: https://armeta.ai/resources/glossary/eaeu-technical-regulations/ Glossary · Cluster C: Standards and normative base # EAEU technical regulations Mandatory technical requirements adopted at the level of the Eurasian Economic Union, applying directly and uniformly across its member states, with conformity confirmed by the EAC mark. Last reviewed: August 4, 2026 ## In detail The EAEU — Russia, Kazakhstan, Belarus, Armenia and Kyrgyzstan — issues union-level technical regulations that supersede national requirements within their scope: one set of mandatory requirements, one conformity-assessment regime, one market. The architecture is the familiar two-layer model: each regulation states essential requirements and carries lists of standards — interstate and national — whose application grants presumption of conformity; products within scope must pass conformity assessment and bear the EAC marking to circulate anywhere in the union. For construction, the regulations matter chiefly at the product level: machinery, low-voltage equipment, pressure equipment and other categories used in building all fall under union regulations, and equipment procured for a Kazakh or Russian site must arrive with EAC conformity regardless of where it was made — a fact best communicated to vendors at requisition, not at customs. Buildings and structures themselves, and design documentation, remain regulated by national frameworks in the member states. The cross-border failure mode is layering: assuming the union regulation covers what national law covers, or the reverse. The scopes interlock rather than duplicate, and a project's compliance map needs both. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # ASME | Engineering glossary Source: https://armeta.ai/resources/glossary/asme/ Glossary · Cluster C: Standards and normative base # ASME The American Society of Mechanical Engineers — publisher of the Boiler and Pressure Vessel Code and the B31 piping codes, the dominant standards for pressure equipment across much of the world. Last reviewed: August 4, 2026 ## In detail ASME's construction-relevant centre of gravity is pressure: the Boiler and Pressure Vessel Code governs the design, fabrication, testing and certification of boilers and pressure vessels, and the B31 series governs piping — B31.3 for process plants being the daily companion of every piping engineer in the industry. The documents are standards by nature and law by adoption: incorporated into legislation across North America and specified contractually almost everywhere else, complete with ASME's own certification machinery of accredited manufacturers and certification marks. Their global reach creates the characteristic cross-border question: an international project may buy vessels built to ASME for a site whose law runs on another pressure regime — the EU's pressure equipment framework, or a national industrial-safety system — and the reconciliation between design code and legal regime is a real work package, involving assessments, approvals and sometimes redesign. Equipment is not compliant in general; it is compliant with a code, under a law, and the two are settled separately. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # ASTM | Engineering glossary Source: https://armeta.ai/resources/glossary/astm/ Glossary · Cluster C: Standards and normative base # ASTM ASTM International — a standards body whose tens of thousands of material, product and test-method standards are the reference layer cited underneath specifications and codes worldwide. Last reviewed: August 4, 2026 ## In detail ASTM standards rarely act alone; they act by citation. A piping specification calls for pipe to an ASTM material designation; a structural code references ASTM steels; a concrete spec invokes ASTM test methods for the properties it demands. The designations — a letter, a number, a grade — are among the most-typed strings in engineering documents, and the standards behind them define the chemistry, mechanical properties, tolerances and testing that a mill certificate then attests item by item. Because ASTM is the reference layer, its failure modes are inheritance problems. The specification cites a designation at an edition that has since moved; the material certificate attests the current edition; whether the difference matters is a question someone must actually answer rather than assume away. And the equivalence question runs here too — ASTM grades against EN and GOST counterparts — with the same caution as everywhere: correspondence tables are introductions, not proofs, and critical applications compare properties, not names. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # API | Engineering glossary Source: https://armeta.ai/resources/glossary/api/ Glossary · Cluster C: Standards and normative base # API The American Petroleum Institute — whose standards for equipment, materials and practices are the de facto global technical language of the oil and gas industry, applied far beyond any American jurisdiction. Last reviewed: August 4, 2026 ## In detail API standards cover the petroleum industry's specific hardware and hazards: storage tanks, centrifugal pumps and compressors for process service, wellhead and pipeline equipment, and the in-service inspection codes by which operating facilities assess piping, vessels and tanks through their lives. Ownership of the in-service layer is what distinguishes the API corpus — it governs not only how equipment is built but how the installed base is inspected, evaluated and kept running, which makes it as much an operations library as a construction one. Adoption is by industry gravity rather than law: an oil and gas project in any hemisphere will specify API equipment standards because operators, contractors and vendors all speak them, and vendor product lines are built to them. The standards then coexist with local legal regimes — national industrial-safety rules, union technical regulations — and the project carries both: API as the contractual technical basis, local law as the compliance floor, reconciled explicitly where they address the same equipment differently. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # IEC | Engineering glossary Source: https://armeta.ai/resources/glossary/iec/ Glossary · Cluster C: Standards and normative base # IEC The International Electrotechnical Commission — ISO's electrotechnical counterpart, whose standards govern electrical, electronic and instrumentation engineering worldwide, including equipment for explosive atmospheres and functional safety. Last reviewed: August 4, 2026 ## In detail By long-standing agreement the IEC holds the electrotechnical half of international standardisation: rotating machines, switchgear, cables, installations, instrumentation. For process and energy facilities two of its families carry particular weight — the standards for equipment in explosive atmospheres, underlying the Ex certification regimes, and the functional-safety standards behind safety-instrumented systems, which together shape how hazardous plants are electrified and protected. The global electrical world, however, is genuinely bipolar: IEC-based practice across most of the planet, and North American practice built on its own code and certification system, differing in voltages, protection philosophy, equipment ratings and hazardous-area classification method. The two are internally coherent and mutually untranslatable at the component level, so an international project declares its electrical basis early — and projects that inherit equipment, engineers or specifications from the other world pay a conversion cost that is never zero. The mundane failure is the mixed basis: IEC design with components certified to the other regime, or area classifications performed by one method and equipment selected by the other's categories. Electrical reviewers find these; commissioning finds the ones reviewers miss. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # NFPA | Engineering glossary Source: https://armeta.ai/resources/glossary/nfpa/ Glossary · Cluster C: Standards and normative base # NFPA The National Fire Protection Association — publisher of the US fire-safety canon, including the National Electrical Code (NFPA 70) and the sprinkler, alarm and life-safety standards adopted throughout North American practice and exported with it. Last reviewed: August 4, 2026 ## In detail NFPA's catalogue runs to hundreds of codes and standards, but a familiar core does most of the work on projects: the National Electrical Code governing electrical installation, the sprinkler and fire-alarm standards governing protection systems, and the life-safety code governing egress — each revised on regular cycles and adopted into law by jurisdictions, insurer requirements or owner specifications. In US practice the building code and the NFPA documents interlock, the code invoking the standards for its fire-protection substance. Beyond North America, NFPA travels with American practice: US-based operators, insurers and engineering firms specify it worldwide, so a facility in any region may run NFPA protection systems inside a non-US legal framework — the now-familiar pattern of contractual basis and legal floor coexisting, with the design demonstrating both. The classic collision is with the IEC/EN world, which answers the same fire and electrical questions by different methods: hazardous-area classification, detection philosophy and hydraulic design all diverge. As with the electrical basis generally, the fire-protection basis is a declaration to make once, early and in writing. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Normative reference | Engineering glossary Source: https://armeta.ai/resources/glossary/normative-reference/ Glossary · Cluster C: Standards and normative base # Normative reference The mechanism by which one standard incorporates provisions of another by citing it — making the cited document's requirements part of the citing one, to the extent stated. Last reviewed: August 4, 2026 ## In detail Standards are written on top of each other. Each opens with a normative-references clause listing the documents its own provisions depend on; through it, complying with one standard silently obliges compliance with parts of many. The references come in two flavours with sharply different behaviour: a dated reference binds to that specific edition, frozen regardless of later revisions; an undated reference means the latest edition applies — a citation that updates itself whenever the cited document does. Both flavours fail in character. Dated references age: the citing standard holds an obsolete edition of the cited one in force within its own scope, sometimes for years, until revised. Undated references drift: the requirement changes without the citing document changing, and a design compliant at the start of a project can fall out of compliance by reference, invisibly. Normative also has a sibling — informative — marking material that guides but does not bind, and confusing the two produces both imaginary obligations and missed real ones. The practical consequence: a project's true normative base includes the reference chains, not just the documents on the list — and the chains are where edition control quietly breaks. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Standards body | Engineering glossary Source: https://armeta.ai/resources/glossary/standards-body/ Glossary · Cluster C: Standards and normative base # Standards body An organisation that develops and publishes standards through a consensus process — international, regional, national or industry-based, each with its own scope, membership and authority. Last reviewed: August 4, 2026 ## In detail The standards world is a layered ecosystem. At the top, the international bodies — ISO and IEC dividing the technical world between them. Below, regional organisations: the European standardisation bodies producing EN standards, the CIS interstate council maintaining the shared GOST corpus. Then national bodies — one per country, holding the national catalogue and the seat in the international ones — and, orthogonal to geography, the industry societies whose names populate every specification: ASME, ASTM, API, NFPA, IEEE and their peers, writing the deep technical documents for their domains. Some bodies write standards; some, like the US national body, chiefly accredit the processes of others — a distinction that surprises people. What the layers share is process: committees, balloting, consensus, publication, revision cycles. What they do not share is authority — a body's standards bind only through the adoption mechanisms this cluster keeps returning to, and overlapping scopes between bodies are common, with the same subject standardised differently in two catalogues. For a project the ecosystem is background until it isn't: knowing which body's document governs, which adoption gives it force, and which body's revision cycle will move it mid-project is part of managing the normative base rather than being managed by it. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Edition, amendment and corrigendum | Engineering glossary Source: https://armeta.ai/resources/glossary/edition-amendment-and-corrigendum/ Glossary · Cluster C: Standards and normative base # Edition, amendment and corrigendum The three instruments by which a published standard changes: a new edition replaces it, an amendment modifies parts of it, and a corrigendum corrects errors in it — with the current version being the sum of all three. Last reviewed: August 4, 2026 ## In detail A standard's life after publication is layered change. A corrigendum fixes what was wrong from the start — typographical and technical errors — and applies as if always there. An amendment changes requirements: clauses revised, added or deleted, published as a separate document to be read with the parent. A new edition consolidates everything and starts the cycle again, superseding its predecessor. At any moment, "the standard" therefore means a specific stack — edition plus its amendments plus its corrigenda — and two engineers holding the same edition but different amendment states hold different requirements. The tracking burden is real and unevenly borne. Formal review checks against the full current stack; project document registers often record editions only; and citations in specifications almost never enumerate amendments, leaving the applicable state implicit and therefore arguable. Standards bodies publish the change trail, but the assembly is manual. The disciplined habit is small: record the full state — edition, amendments, corrigenda — in the frozen design basis, and treat every amendment issued mid-project as a change-control event, not a background update. The alternative is discovering the amendment through a review comment that cites it. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Prescriptive vs performance-based codes | Engineering glossary Source: https://armeta.ai/resources/glossary/prescriptive-vs-performance-based-codes/ Glossary · Cluster C: Standards and normative base # Prescriptive vs performance-based codes The two philosophies of regulation: prescriptive codes state exactly what to build, performance-based codes state what the result must achieve — and most real systems combine both. Last reviewed: August 4, 2026 ## In detail A prescriptive requirement is a recipe: this thickness, this spacing, this rating. It is checkable by inspection, predictable in cost, and demands no analysis — at the price of forbidding better solutions it never imagined. A performance requirement states the outcome — the structure withstands these loads, the occupants evacuate before untenable conditions — and leaves the method open, admitting innovation at the price of a verification burden: someone must demonstrate, by analysis and evidence, that the chosen solution performs, and someone with authority must accept the demonstration. Modern systems are deliberate hybrids, typically structured as mandatory performance requirements paired with deemed-to-satisfy prescriptive routes — follow the recipe and compliance is presumed; depart from it and carry the proof. Fire engineering lives on the performance route almost everywhere; Kazakhstan's 2015 reform rebuilt its whole construction base on this pattern; the EU's regulation architecture is the same idea at the legislative level. The failure modes mirror the philosophies. Prescriptive: recipes applied outside the situations they encoded. Performance: the freedom taken without the burden — alternative solutions asserted rather than demonstrated, arriving at review with innovation and no evidence, which converts the flexibility back into a rejection. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: Standard; Code; Technical regulation Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # EPC | Engineering glossary Source: https://armeta.ai/resources/glossary/epc-engineering-procurement-construction/ Glossary · Cluster D: Delivery and contracting # EPC A contracting model — Engineering, Procurement and Construction — in which a single contractor takes responsibility for designing, buying and building a complete facility under one contract, usually for a fixed price. Last reviewed: August 4, 2026 ## In detail EPC bundles the whole delivery chain into one pair of hands. The contractor engineers the facility from the owner's FEED package, procures everything in it, constructs it, and hands it over — carrying the integration risk between those activities that, in other models, lives with the owner. The commercial logic is single-point responsibility: when the pump does not fit the foundation, that is the EPC contractor's internal problem, not a dispute between the owner's separate contracts. The price of the transfer is the premium. An EPC contractor prices not just the work but the risk of the work, and the size of that premium is set almost entirely by the quality of the FEED package being bid: complete, consistent definition buys a tight price; gaps and ambiguity are priced as contingency or, worse, as a plan to recover through change orders. The model fails when its own logic is violated — most commonly by the owner. An owner who transfers the risk and then directs the means, drip-feeds preferences, or keeps redesigning has paid for risk transfer while behaving as if it never happened, and the claims file will eventually price the difference. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPCM; Lump-sum contract; Cost-plus contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # EPCM | Engineering glossary Source: https://armeta.ai/resources/glossary/epcm/ Glossary · Cluster D: Delivery and contracting # EPCM A delivery model — Engineering, Procurement and Construction Management — in which the contractor provides engineering and manages procurement and construction as a professional service, while the construction contracts and the risk remain with the owner. Last reviewed: August 4, 2026 ## In detail EPCM looks like EPC minus one letter and is a different animal. The EPCM contractor engineers the facility, runs procurement, and manages the construction contractors — but those contractors hold their contracts with the owner, and the EPCM firm is paid for services, not for a facility. The owner retains cost and schedule risk, direct commercial relationships, and the flexibility that comes with them: scope can evolve, packages can be tendered as definition matures, and no risk premium is being paid on the whole project value. The model suits situations where lump-sum transfer is poor value: immature scope, volatile markets, brownfield uncertainty, or owners with the capability and appetite to hold risk themselves. That last clause is the qualifying condition — EPCM presumes an owner able to make decisions at project speed and to own the consequences. The chronic failure is category confusion: owners contracting EPCM and expecting EPC outcomes — price certainty, single-point accountability — from a party that sold neither. When the cost grows, the EPCM contractor's liability is capped near its fee, and the owner discovers what "management services" meant all along. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; Lump-sum contract; Cost-plus contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Lump-sum contract | Engineering glossary Source: https://armeta.ai/resources/glossary/lump-sum-contract/ Glossary · Cluster D: Delivery and contracting # Lump-sum contract A contract in which the contractor agrees to deliver a defined scope of work for a fixed total price, carrying the risk that the work costs more than the price. Last reviewed: August 4, 2026 ## In detail The lump sum is the cleanest commercial promise in construction: this scope, this money. The owner gains price certainty and simple administration — payment against progress rather than audit of costs — and the contractor gains the upside of efficiency, keeping every unit of cost it beats out of the estimate. The promise is exactly as good as the scope definition underneath it. A fixed price for a defined scope is a transfer of estimating risk; a fixed price for an undefined scope is a fiction that will be corrected through the change mechanism, one variation at a time, with the contractor holding the pricing pen. This is why lump-sum contracting concentrates so much energy on the tender documents — every ambiguity is priced by every bidder, differently — and why the change-order and variation machinery is where lump-sum contracts actually live or die. The characteristic owner error is buying certainty that was never for sale: tendering lump-sum on incomplete definition because the board wants a fixed number. The number will be fixed. The project cost will not. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Cost-plus contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Cost-plus contract | Engineering glossary Source: https://armeta.ai/resources/glossary/cost-plus-contract/ Glossary · Cluster D: Delivery and contracting # Cost-plus contract A contract in which the owner reimburses the contractor's actual costs of performing the work, plus an agreed fee — fixed, percentage-based or incentive-linked. Last reviewed: August 4, 2026 ## In detail Cost-plus (reimbursable) contracting is what parties use when a fixed price would be a guess: scope still forming, schedule too urgent to wait for definition, or conditions too uncertain to price. The contractor opens its books, the owner pays what the work actually costs plus the fee, and the risk of cost outcomes sits with the owner — along with the obligation to run the audit, verification and control machinery that reimbursement demands. The fee structure carries the incentives, and choosing it is the real contract design. A percentage fee rewards spending; a fixed fee is neutral; incentive structures — target costs with shared over- and under-runs, or a guaranteed maximum price capping the owner's exposure — attempt to rebuild the efficiency motive that the lump sum provides for free. The model's failures are definitional and cultural. Definitional: "reimbursable cost" must be specified to the level of timesheets, rates, and what is inside the fee, or every invoice becomes a negotiation. Cultural: cost-plus with a passive owner is a project with no one minding the money — the contract form that most rewards owner capability is the one most often chosen by owners who lack it. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Tender | Engineering glossary Source: https://armeta.ai/resources/glossary/tender/ Glossary · Cluster D: Delivery and contracting # Tender The formal process by which an owner invites, receives and evaluates competing offers for a defined scope of work — and also the name of the offer itself. Last reviewed: August 4, 2026 ## In detail The word does double duty: an owner issues a tender (the process), and a contractor submits a tender (the offer). The process runs a standard arc — tender documents issued to bidders, a clarification period of formal queries and answers circulated to all, submission by deadline, evaluation, and award — with public procurement adding codified rules at every step and private owners improvising around the same skeleton. The tender documents are the whole game. Bidders price what the documents say, not what the owner meant; every gap is priced differently by every bidder, and every ambiguity is an evaluation problem now or a claim later. The clarification period exists to drain these before submission, and the quality of the questions received is a preview of the quality of the documents issued. Failures cluster at the ends. At the front: tender periods too short for the document volume, guaranteeing shallow pricing and post-award discovery. At the back: evaluation that selects the lowest number rather than the lowest realistic number — awarding to a bid whose price is an error or a strategy, then spending the contract finding out which. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Prequalification | Engineering glossary Source: https://armeta.ai/resources/glossary/prequalification/ Glossary · Cluster D: Delivery and contracting # Prequalification The screening of contractors or suppliers for capability before they are invited to bid — assessing financial standing, experience, resources and safety record so that the tender list contains only parties who could actually perform. Last reviewed: August 4, 2026 ## In detail Prequalification separates can they do it from what will it cost, and answers the first question first. Candidates submit evidence against published criteria — comparable project experience, financial statements, key personnel, equipment, quality and HSE systems and statistics — and only those who clear the bar receive tender documents. The logic protects both sides: the owner avoids evaluating (or worse, being obliged to accept) bids from parties who cannot perform, and serious bidders avoid pricing against unserious competition. Two failure modes dominate. The first is theatre: prequalification as document collection, where certificates are filed and nothing is verified — reference projects uncalled, financials unread, the safety statistics taken on faith. The second is misdirection: qualifying the entity that will not do the work — the impressive parent company prequalifies, the thinly resourced local subsidiary signs the contract — which is why careful prequalification names the performing entity and secures parent guarantees for the gap. Set the bar wrong and the process fails differently: too low and it filtered nothing; too high and the tender list is three companies who know their competition. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Contractor and subcontractor | Engineering glossary Source: https://armeta.ai/resources/glossary/contractor-and-subcontractor/ Glossary · Cluster D: Delivery and contracting # Contractor and subcontractor The contractual chain of construction: the (main) contractor holds the contract with the owner, and subcontractors hold their contracts with the contractor — not with the owner. Last reviewed: August 4, 2026 ## In detail Construction is delivered through a chain of two-party contracts, and the chain's defining legal fact is privity: the owner and a subcontractor, though they meet daily on site, generally have no contract with each other. The main contractor answers to the owner for all of the work, including the sixty percent it subcontracted; each subcontractor answers to the main contractor alone. Obligations travel down the chain through flow-down clauses that push main-contract terms into subcontracts, and money travels the same path, with each link's payment terms compounding the delay to the link below. The chain's health depends on back-to-back alignment: the subcontract's scope, specifications, programme and risk terms mirroring the relevant slice of the main contract. Every gap between the two is a risk the main contractor is holding without having priced — a scope item owed upward but not purchased downward. Owners break the chain from above, most often by instructing subcontractors directly — expedient in the moment, and a gift to any later dispute, since it blurs exactly the single line of responsibility the structure exists to preserve. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Asset owner | Engineering glossary Source: https://armeta.ai/resources/glossary/asset-owner/ Glossary · Cluster D: Delivery and contracting # Asset owner The party that owns, finances and will operate the facility being built — the entity for whose benefit the entire project structure exists, and whose decisions every other party is waiting on. Last reviewed: August 4, 2026 ## In detail The owner (employer, client, company — the vocabulary varies by contract form) sets the requirements, funds the work, holds the permits, accepts the risk allocations, and receives the asset. Everything else on a project is agency: designers, contractors and consultants act under contracts that all trace back to the owner's decisions about scope, budget, risk and pace. What contract structures quietly assume — and organisations quietly forget — is that ownership is a workload. Every delivery model leaves the owner with obligations: decisions on time, reviews on time, access, permits, free-issue items, payments. An under-resourced owner becomes the project's critical path without appearing on any schedule, and no contracting model transfers away the duty to decide. The other failure is grammatical: "the owner" is singular in the contract and plural in life — operations, engineering, procurement, finance and legal, each with a view, none with the pen. Projects that never resolve who speaks for the owner receive their coordination problem back as claims, since a contractor entitled to rely on the owner's instructions is entitled to be confused at the owner's expense. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Design institute | Engineering glossary Source: https://armeta.ai/resources/glossary/design-institute/ Glossary · Cluster D: Delivery and contracting # Design institute An institutional form of design organisation — characteristic of the CIS, China and neighbouring systems — in which a licensed organisation, rather than an individually licensed engineer, produces design documentation and carries responsibility for it. Last reviewed: August 4, 2026 ## In detail Where North American practice hangs design accountability on the licensed individual and their seal, the institute model hangs it on the organisation: design institutes hold the licences and accreditations, employ the disciplines, and issue documentation under organisational responsibility, with integrating authority vested in the chief project engineer role. The institutes descend from the specialised state design organisations of the planned economies — many historically dedicated to a single industry, holding deep normative and sectoral expertise — and today range from privatised successors to new commercial firms operating in the same institutional shape. Functionally, an institute is the counterpart of the engineering consultancy or architect-engineer elsewhere, and on international projects the two models must interoperate: documentation stages, review obligations and signature regimes all map approximately and none map exactly. The recurring friction is exactly that approximation — foreign partners treating an institute as a consultancy with unfamiliar paperwork, or local stakeholders expecting institute-model deliverables from firms structured for different stage definitions. The differences are institutional, not cosmetic, and projects that map them explicitly at the start spend less on discovering them later. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Greenfield | Engineering glossary Source: https://armeta.ai/resources/glossary/greenfield/ Glossary · Cluster D: Delivery and contracting # Greenfield A project built on a previously undeveloped site, with no existing facility to constrain the design — and no existing infrastructure to build upon. Last reviewed: August 4, 2026 ## In detail Greenfield is construction with a blank page: layout optimised rather than negotiated, systems designed whole rather than tied into, construction sequenced for efficiency rather than around live operations. Everything that makes brownfield work slow — surveys of what exists, shutdown windows, permits to work beside operating equipment — is simply absent. What is also absent is everything else. A greenfield site brings no power, water, roads, drainage, communications, workforce or camp; the project builds its own world before it builds the facility, and the site-development and infrastructure scope — with the geotechnical and hydrological unknowns underneath it — is routinely the most underestimated part of the venture. Permits start from zero as well: land, environmental, utilities, construction, each on its own clock. The characteristic failure is the clean-slate illusion: estimating the facility and discovering the site. The ground is never as assumed, the utilities are further than drawn, and the "undeveloped" land has owners, neighbours, ecology and archaeology. Greenfield removes the constraints of an existing plant and replaces them with the constraints of an existing planet. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Brownfield | Engineering glossary Source: https://armeta.ai/resources/glossary/brownfield/ Glossary · Cluster D: Delivery and contracting # Brownfield Work performed within or immediately alongside an existing facility, where the design must connect to, coexist with, and often keep running the plant that is already there. Last reviewed: August 4, 2026 ## In detail Brownfield inverts the greenfield bargain: the infrastructure exists, and everything else is a constraint. The design is negotiated with what stands — routing through congested racks, foundations between live services, tie-ins to systems that were built decades ago to standards since superseded. Construction is negotiated with operations: permits to work, hot-work restrictions, shutdown windows, and the standing rule that the operating plant's safety and production outrank the project's schedule. The defining brownfield problem is knowledge of the existing. The facility's documentation — the as-builts, the P&IDs, the records of every modification since startup — is the design basis for everything new, and it is reliable in inverse proportion to the facility's age. The gap between documents and reality is closed by surveys, walkdowns and laser scanning, a discovery cost that greenfield never pays, and the discoveries keep arriving through execution. Estimating carries the consequence: brownfield productivity is structurally lower — access, permits, interruptions, congestion — and estimates built on greenfield norms are wrong by design. The factor between the two is one of the most argued numbers in estimating, and the site always wins the argument. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Revamp | Engineering glossary Source: https://armeta.ai/resources/glossary/revamp/ Glossary · Cluster D: Delivery and contracting # Revamp The modification of an existing operating unit to change what it does — more capacity, different feedstock, better efficiency, new products — reusing as much of the existing plant as the new duty allows. Last reviewed: August 4, 2026 ## In detail A revamp is brownfield with a thesis: the existing asset, bought and depreciated, can be made to do more for less than a new one would cost. Revamp engineering therefore starts where greenfield engineering ends — with what exists. The existing equipment is rated against the new conditions, item by item: which vessels, exchangers, machines and lines can take the new duty, which need modification, which must be replaced. The economics live in that sorting, because every reuse is capital avoided and every wrong reuse is a late, expensive discovery. The inputs to that sorting are the facility's records — datasheets, as-builts, inspection histories — plus whatever surveys must fill their gaps, which makes documentation quality a direct driver of revamp cost and risk. The characteristic revamp failure is the reuse assumption that dies late: the exchanger that rating showed adequate until the actual fouling data surfaced, the foundation that could take the load until someone found the real drawings. Execution then inherits the turnaround problem: the tie-ins and replacements that need the unit down get compressed into shutdown windows, and the revamp's schedule is ultimately negotiated with the production plan. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Turnaround | Engineering glossary Source: https://armeta.ai/resources/glossary/turnaround/ Glossary · Cluster D: Delivery and contracting # Turnaround A planned, scheduled shutdown of an operating unit for inspection, maintenance and modification work that cannot be done while it runs — executed at maximum intensity because every day of downtime is lost production. Last reviewed: August 4, 2026 ## In detail A turnaround (TAR; also shutdown or outage) is the operating plant's periodic surgery: the unit comes down on a planned date, an enormous volume of work — statutory inspections, catalyst changes, equipment overhauls, and the project tie-ins that have been waiting for exactly this window — is executed around the clock by a workforce many times the site's normal population, and the unit returns to service. The economics are brutal and clarifying: the cost of the work is usually small beside the value of the production not happening, so the entire discipline optimises duration. That discipline is scope control. Turnaround scope is frozen months ahead so that planning, materials and labour can be locked to it; the enemy is late and emergent scope — the "while we're in there" additions and the discovery work that inspection reveals once equipment is open. Both are managed, contingency-planned and fought over daily. Turnarounds fail by growing: scope added past the freeze, discoveries beyond allowance, and the overrun measured not in labour cost but in days of lost production — the most expensive unit of account in the industry. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Scope of work | Engineering glossary Source: https://armeta.ai/resources/glossary/scope-of-work/ Glossary · Cluster D: Delivery and contracting # Scope of work The contractual description of everything a contractor is obliged to perform and deliver — and, by its boundaries, everything it is not. Last reviewed: August 4, 2026 ## In detail The scope of work is the contract's answer to "what, exactly, am I buying." It describes the work, the deliverables, the standards to which they are done, and — the part that decides disputes — the boundaries: battery limits, interfaces with other contracts, inclusions and exclusions, who supplies what to whom. On a multi-contract project, the scopes are a jigsaw cut by the owner, and the cutting is a design act: every interface created is a coordination obligation someone must hold. Scope fails at the seams, in two directions. Gaps — the item that falls between two contracts, described in neither, bought by no one — surface late, priced by whichever party is asked to absorb them, at post-award rates. Overlaps are quieter: the same work bought twice, discovered at payment if at all. Both are why interface registers and scope matrices exist, and why the exclusions list — read casually at award, forensically at claim — deserves its drafting time. The recurring drafting sin is description by reference: scope defined as "all works shown in the documents," inheriting every inconsistency those documents contain and converting each one into a scope argument. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # FIDIC | Engineering glossary Source: https://armeta.ai/resources/glossary/fidic/ Glossary · Cluster D: Delivery and contracting # FIDIC The International Federation of Consulting Engineers — publisher of the standard forms of contract that are the default framework for international construction and EPC projects across much of the world. Last reviewed: August 4, 2026 ## In detail FIDIC's contract forms are the closest thing international construction has to a common law. The main forms are keyed by risk allocation, and known by cover colour: the Red Book for construction to the employer's design, the Yellow Book for plant and design-build with contractor design, and the Silver Book for EPC/turnkey delivery with maximum risk on the contractor — with variants and companions around them. Multilateral lenders and cross-border projects reach for FIDIC precisely because both sides' lawyers have seen it before: the machinery of programme, payment, variations, claims and disputes is standardised, tested and translated. Two features of that machinery do disproportionate work. The contract administrator role — the Engineer in the Red and Yellow Books — determines and certifies between the parties; and the claims regime runs on strict notice: the famous 28-day windows within which a party must notify a claim or, under the default drafting, lose it. Time-bars convert contractual rights into administrative discipline, and they harvest the undisciplined annually. The standard forms' standard abuse is amendment: particular conditions that quietly rebalance the allocation the form was chosen for, producing a contract that looks like FIDIC and behaves like something else. The form's name reassures; the mark-up governs. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Lump-sum turnkey (LSTK) | Engineering glossary Source: https://armeta.ai/resources/glossary/lump-sum-turnkey-lstk/ Glossary · Cluster D: Delivery and contracting # Lump-sum turnkey (LSTK) EPC contracting in its most complete commercial form: a fixed price for a finished facility, handed over tested and ready to operate — the owner turns the key. Last reviewed: August 4, 2026 ## In detail LSTK stacks the two strongest transfers in contracting: the lump sum moves cost risk, the turnkey obligation moves completion risk. The contractor's promise is not effort but an outcome — a facility that, at handover, passes its performance tests and runs. The commercial machinery matches the promise: performance guarantees on capacity, efficiency and product quality; liquidated damages for delay and for performance shortfalls; payment tied to milestones and, at the end, to demonstrated performance rather than assembled hardware. The model is the standard vehicle for process plants and power projects, and for lender-financed ventures generally, because it produces the thing financiers can underwrite: a price, a date, and a warranted output, all with one throat to choke. Its honest price is the premium on all that certainty, and its honest limits are the owner obligations that survive it — feedstock, utilities, permits, decisions, access. "Turnkey" describes the handover, not the owner's project role, and owners who read it as permission to disengage rediscover the distinction in the claims register. The other quiet term worth reading twice: what the performance LDs actually buy out, and what happens when their cap is reached. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # ITT, RFP and RFQ | Engineering glossary Source: https://armeta.ai/resources/glossary/itt-rfp-and-rfq/ Glossary · Cluster D: Delivery and contracting # ITT, RFP and RFQ The three standard solicitation instruments: an invitation to tender seeks priced bids on a defined scope, a request for proposals seeks solutions as well as prices, and a request for quotations seeks prices for specified supply — though RFQ also means "request for qualifications" in some markets. Last reviewed: August 4, 2026 ## In detail The instruments differ by how much the buyer already knows. An RFQ (quotation) assumes the definition is complete — this item, this specification, this quantity — and asks only the price; evaluation is largely arithmetic. An ITT assumes the scope is defined and asks for conforming, comparable, priced tenders; evaluation is price-led with compliance screening. An RFP admits the buyer wants the market's thinking — the solution, the approach, the team — and evaluates on weighted criteria in which price is one factor; it belongs where definition is genuinely open, since what it buys in ideas it costs in comparability. The acronym collision is real and regional: in North American public procurement especially, RFQ frequently means request for qualifications — a prequalification instrument with no prices in it at all. Documents that say which they mean save everyone a round of correspondence. The failure is mismatch: an RFP where an ITT belonged converts a pricing exercise into an essay contest; an ITT on immature definition collects incomparable guesses with two decimal places. The instrument should be chosen by the maturity of the definition, not the habit of the procurement office. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Owner's engineer | Engineering glossary Source: https://armeta.ai/resources/glossary/owners-engineer/ Glossary · Cluster D: Delivery and contracting # Owner's engineer An engineering organisation retained by the owner to act as its technical representative — reviewing the contractor's design, monitoring execution, and supplying the engineering judgement the owner does not carry in-house. Last reviewed: August 4, 2026 ## In detail When the design capability sits on the contractor's side of the table — as it does in EPC and design-build — the owner needs its own eyes. The owner's engineer reviews design deliverables against the contract and the owner's requirements, witnesses tests, monitors progress and quality, advises on claims and changes, and generally ensures that the owner's acceptance decisions are informed ones. On lender-financed projects a sibling role, the lender's engineer, does the same for the money. The role's boundaries are its whole design. The OE reviews and recommends; the contractor designs and warrants; the owner decides. An OE that drifts into re-engineering — comments that redesign rather than review — slows the project, muddies the warranty, and hands the contractor a ready-made defence: the design failed where the owner's engineer changed it. The discipline of commenting on compliance rather than preference is what separates a review function from a second design office. The opposite failure is the OE as ornament: retained for lender optics, under-scoped, reviewing at a depth that assures nothing. The title on the organogram is not the function; the review scope and its authority are. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Project management consultant (PMC) | Engineering glossary Source: https://armeta.ai/resources/glossary/project-management-consultant-pmc/ Glossary · Cluster D: Delivery and contracting # Project management consultant (PMC) An organisation engaged to manage a project on the owner's behalf — running schedule, cost, contracts and interfaces across all the other parties — as the owner's agent rather than as a contractor for the work itself. Last reviewed: August 4, 2026 ## In detail The PMC model rents an owner a project organisation. Where the owner's permanent team is small and the project is not, the PMC supplies the management layer: planning and controls, procurement and contracts administration, interface coordination between contractors, reporting, and often site supervision — acting in the owner's name, under the owner's authority, for a fee. On multi-contract megaprojects the PMC is frequently the only party that sees the whole board. The model's tension is accountability without power. A PMC manages outcomes it does not contractually control — the contractors hold their contracts with the owner — and its liability is capped near its fee, a fraction of the costs its performance influences. The structure works when the owner delegates genuine authority and holds the PMC to genuine standards; it fails into two familiar shapes: the PMC as expensive postbox, processing paper between owner and contractors while decisions queue, or the PMC as shadow owner, exercising authority nobody formally granted until a dispute asks who decided. The layering also has a price in overhead and in distance — every message between owner and contractor passing through a paid intermediary — which is the fee's honest competition. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Long-lead items | Engineering glossary Source: https://armeta.ai/resources/glossary/long-lead-items/ Glossary · Cluster D: Delivery and contracting # Long-lead items Equipment and materials whose procurement time — engineering, fabrication and delivery — is so long that they must be ordered early, often before the main contract or even the investment decision, to protect the project schedule. Last reviewed: August 4, 2026 ## In detail Every schedule has items that set its spine: major rotating equipment, large vessels and exchangers, transformers, specialty alloys — purchases whose lead times are measured in many months or years and cannot be compressed by money alone. Projects manage them as a named list: identified during FEED, specified early from whatever definition exists, and ordered ahead of the pack, sometimes by the owner directly for later assignment (novation) to the EPC contractor. The early order is a deliberate trade. Committing before the design matures buys schedule and pays in change: the vendor is contracted on preliminary data, and every subsequent refinement of the datasheet is a variation to a purchase order already running. Managed knowingly — data frozen where it matters, holds tracked, changes budgeted — the trade is sound; the alternative is a critical path waiting on a forging slot. The failure that hurts most is the list itself: the long-lead item nobody put on it. Lead times move with market cycles — yesterday's routine purchase is this year's two-year queue — and the item discovered late arrives on the schedule as an immovable fact that redesign, expediting and premium freight can only partly soften. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Variation | Engineering glossary Source: https://armeta.ai/resources/glossary/variation/ Glossary · Cluster D: Delivery and contracting # Variation In FIDIC and UK-influenced contracts, an instructed change to the works — the sibling of the change order, with its own mechanics: the instruction comes first, and the valuation follows. Last reviewed: August 4, 2026 ## In detail A variation is the contract's licence for the employer's side to change the works — add, omit, alter — and the contractor's corresponding obligations: to comply with a properly instructed variation, and to be paid for it under the contract's valuation cascade. That cascade is the instrument's spine: contract rates where the work is of similar character and conditions; rates derived from them where it is comparable; fair valuation where nothing fits. Time consequences run in parallel through the extension-of-time machinery. The instruct-first mechanics distinguish it from the North American change-order habit of agreeing scope, price and time before proceeding. Under variation regimes the work often cannot wait for the valuation — the contractor performs under instruction and the money is determined after, by the contract administrator if the parties cannot agree — which keeps the job moving and moves the argument to the paperwork. The disputes are correspondingly predictable: whether an instruction was a variation at all or merely clarification of existing scope; whether the varied work's conditions still resemble those the rates assumed; and the cumulative effect of many variations on productivity — priced individually, felt collectively, claimed eventually. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Liquidated damages | Engineering glossary Source: https://armeta.ai/resources/glossary/liquidated-damages/ Glossary · Cluster D: Delivery and contracting # Liquidated damages Pre-agreed sums, fixed in the contract, payable for defined failures — most commonly per day of delay past the completion date, and in EPC contracts also per unit of performance shortfall. Last reviewed: August 4, 2026 ## In detail Liquidated damages convert a lawsuit into arithmetic. Rather than proving actual loss when the contractor finishes late, the owner deducts the agreed rate per day; rather than litigating a plant that makes ninety-seven percent of guaranteed capacity, the parties apply the agreed price per missing percent. The sums are set at contract as a genuine pre-estimate of the loss — a characterisation with legal weight, since jurisdictions differ sharply in their tolerance of amounts that look punitive rather than compensatory — and they typically operate under caps, expressed as a percentage of contract price, with delay and performance LDs sometimes sharing an aggregate ceiling. LDs discipline both parties' behaviour before any breach occurs. The contractor prices them into its risk and its schedule contingency; the owner, by fixing them, usually accepts them as the exclusive remedy for the failure they cover — a term worth reading as carefully as the rate. Set wrong, they misfire in both directions: too low, and the LDs become a cheap option — the contractor rationally pays them to divert resources to a better-paying deadline elsewhere; too high, and they return in the bid price as premium, or in court as an unenforceable penalty. The cap's exhaustion is the other cliff: what rights revive when the LDs run out is a question best answered at drafting, not at month fourteen of delay. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Retention | Engineering glossary Source: https://armeta.ai/resources/glossary/retention/ Glossary · Cluster D: Delivery and contracting # Retention A percentage withheld from each progress payment — commonly five to ten percent — held by the paying party as security for completion and the correction of defects, and released in stages after the work is done. Last reviewed: August 4, 2026 ## In detail Retention is security taken in the simplest possible form: money earned but not yet paid. Each interim payment is reduced by the retention percentage, the withheld pool grows with progress, and release follows the contract's milestones — conventionally half at completion or takeover, the remainder after the defects liability period, when the contractor has fixed what the period revealed. Its logic is leverage: the contractor's own money is the bond that brings crews back for the punch list and the warranty repairs. The alternative — a retention bond, exchanging the withheld cash for a bank or surety instrument — buys the contractor its cash flow back at the price of a fee, and buys the owner equivalent security on paper. Retention's real cost lives down the payment chain, where the percentages compound: withheld by the owner from the contractor, and by the contractor from every subcontractor, often on harsher release terms — the deepest pockets holding the smallest firms' margins for the longest time. Late release, disputed release and release conditioned on paperwork nobody prioritises are endemic; in several markets, retention reform and trust schemes exist precisely because the pool too often outlives the project, the defects and occasionally the payer. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Free-issue materials | Engineering glossary Source: https://armeta.ai/resources/glossary/free-issue-materials/ Glossary · Cluster D: Delivery and contracting # Free-issue materials Materials or equipment that the owner procures and supplies to the contractor for incorporation into the works — moving the supply obligation, and its risks, from contractor to owner. Last reviewed: August 4, 2026 ## In detail Owners free-issue for concrete reasons: long-lead equipment ordered before the contractor existed, bulk materials bought on frame agreements at prices no single project could get, owner-specified proprietary items, or simple economics of scale across a programme. The contractor installs what it did not buy, and the contract must then answer the questions purchasing normally answers: when items are delivered and where, who inspects and accepts them on receipt, when care, custody and control transfer, who insures them, and who bears surplus, damage and waste. Each answer is a claim category when left vague. Late free-issue is the classic: the contractor's schedule assumed the owner's delivery dates, and every slip is disruption with the owner's name on it — the mirror image of the risk transfer the owner sought elsewhere in the contract. Receipt disputes are second: defects discovered at installation, months after delivery, litigating whether inspection on arrival was the contractor's duty or a formality. The quiet administrative burden is reconciliation: owner-supplied quantities against installed quantities against the take-off, with wastage allowances agreed in advance — because material the owner bought and the contractor consumed is an account, and accounts want keeping. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Bid levelling | Engineering glossary Source: https://armeta.ai/resources/glossary/bid-levelling/ Glossary · Cluster D: Delivery and contracting # Bid levelling The adjustment of received bids onto a common basis — aligning scope interpretations, exclusions, clarifications and commercial terms — so that the comparison is between equivalent offers rather than raw totals. Last reviewed: August 4, 2026 ## In detail No two bids arrive on the same basis. Each carries its own exclusions and qualifications, its own reading of the ambiguities, its own assumptions where the documents were silent, and its own commercial terms behind the number on the form. Bid levelling is the evaluation discipline that reconstructs comparability: itemising every deviation from the tender basis, pricing each one's consequence, adjusting each bid to include what it excluded and remove what it added, and clarifying with bidders — in writing, through the formal channel — where intent is unclear. The levelled comparison routinely reorders the raw one, which is the whole point: the lowest submitted number is frequently the bid that excluded the most, and the exclusions are not discounts — they are invoices deferred to the contract, where they will be priced without competition. Levelling fails as arithmetic-only exercise: commercial adjustments made without technical review of what the deviations mean, or qualifications waved through as "to be resolved at award" — a phrase that means resolved at the winner's leisure. The levelling sheet, kept honestly, is also the project's first risk register: every line on it is an ambiguity the tender documents created, and the same list will reconvene at the first claim. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Local content | Engineering glossary Source: https://armeta.ai/resources/glossary/local-content/ Glossary · Cluster D: Delivery and contracting # Local content Requirements — statutory or contractual — that a defined share of a project's labour, goods and services be sourced from the host country, common across resource-rich jurisdictions. Last reviewed: August 4, 2026 ## In detail Local content is industrial policy delivered through procurement. Host governments — across Central Asia, the Middle East, Africa and beyond, Kazakhstan among the long-established examples — require or incentivise projects to employ national workforce, buy from domestic suppliers, and develop local capability, through licence conditions, procurement law, or contract terms flowed down the chain. The metrics vary by regime and the variation is the first trap: percentages may be counted by spend, by value added, by headcount or by certified origin, and a commitment made under one arithmetic can be unmeetable under another. Several Gulf states run formalised in-country-value programmes that score suppliers on exactly such formulas. For bidders, local content is a design constraint on the supply chain, priced and planned like any other: which packages can genuinely be sourced locally at the required quality, which need capability building, and what the compliance premium is. The recurring failure is the bid-stage promise made from a chart rather than a supply-chain survey — commitments that execution cannot meet, discovered at reporting time, with consequences ranging from penalties to standing with the very government whose future projects the commitment was meant to win. The steady-state burden is evidentiary: certification, origin documentation and periodic reporting, an administrative function projects under-scope with remarkable consistency. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: EPC; EPCM; Lump-sum contract Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # P&ID | Engineering glossary Source: https://armeta.ai/resources/glossary/pid-piping-and-instrumentation-diagram/ Glossary · Cluster E: Drawings and engineering data # P&ID A Piping and Instrumentation Diagram — the schematic drawing showing every pipe, valve, item of equipment, instrument and control function of a process system, and how they connect. Last reviewed: August 4, 2026 ## In detail The P&ID is the master document of a process facility. Process engineering produces it, and everyone else works from it: piping routes what it shows, instrumentation implements its loops, safety reviews walk it line by line in HAZOPs, operations trains on it, and maintenance isolates equipment by it. It is deliberately not to scale and not spatial — it shows what connects to what, not where anything is — which is exactly what makes it the reference for the facility's logic. Because everything downstream depends on it, the P&ID is also where inconsistency shows up first: the line list disagreeing on a size, the datasheet on a rating, the model on a connection. Keeping the P&ID reconciled with the documents that orbit it is a permanent background task on every project. The industry's larger P&ID problem is inheritance. Facilities outlive their tools, and much of the world's installed base is documented in P&IDs that exist as scans and flat CAD files — readable by people, opaque to systems — so that every revamp, every debottlenecking study and every digitalisation effort begins by re-extracting what the drawings already know. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: PFD; Piping isometric; Line list Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # PFD | Engineering glossary Source: https://armeta.ai/resources/glossary/pfd-process-flow-diagram/ Glossary · Cluster E: Drawings and engineering data # PFD A Process Flow Diagram — the higher-level schematic showing a facility's major equipment and main process streams, with the key operating conditions and the heat and material balance data. Last reviewed: August 4, 2026 ## In detail The PFD is the process design's summary statement: what the plant does, through which major equipment, at what flows, temperatures and pressures. It precedes the P&IDs in the design sequence — the PFD fixes the process scheme, the P&IDs then elaborate it into every line and instrument — and it stays useful long after, as the document by which anyone new understands the plant in an afternoon rather than a month. The PFD carries numbers as well as topology: stream data drawn from the simulation and the heat and material balance, which makes it the bridge between process modelling and engineering documents. Early estimating leans on it heavily — factored and parametric methods work from PFD-level definition. Its failure is drift. As detail design develops and the P&IDs absorb change after change, the PFD is the document least likely to be updated, and a facility can reach operation with a PFD describing the plant as first conceived rather than as built — harmless until someone bases a study on it. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; Piping isometric; Line list Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Piping isometric | Engineering glossary Source: https://armeta.ai/resources/glossary/piping-isometric-drawing/ Glossary · Cluster E: Drawings and engineering data # Piping isometric A drawing of a single pipeline, or part of one, drawn in isometric projection without scale — carrying the dimensions, welds, materials and bill of materials from which the line is fabricated and erected. Last reviewed: August 4, 2026 ## In detail The isometric is piping's unit of production. Each one shows one line's routing as a schematic 3D representation, dimensioned for fabrication, annotated with weld locations and types, and closed out with a bill of materials listing every pipe cut, fitting, flange and bolt set the line consumes. Shop fabrication builds spools from it, the field erects and welds from it, and detailed material take-offs are aggregated from its BOMs. In modern workflows isometrics are extracted from the 3D model rather than drawn — which relocates rather than removes the quality question: the iso is right when the model was, and late model changes must regenerate every affected iso or the shop builds the previous revision. The isometric is also where design meets fabrication logistics: the split into spools, the distinction between shop welds and field welds, and the field-fit allowances that acknowledge reality's tolerance for the model. Errors here are found by fit-up crews, one flange misalignment at a time. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Line list Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Line list | Engineering glossary Source: https://armeta.ai/resources/glossary/line-list/ Glossary · Cluster E: Drawings and engineering data # Line list The register of every piping line in a facility, recording each line's number, size, piping class, origin and destination, operating and design conditions, and requirements for insulation and testing. Last reviewed: August 4, 2026 ## In detail The line list is the piping system's index and database in one. Each line the P&IDs show gets a row, and the row accumulates the line's defining data — the conditions that size it, the class that sets its materials, the from–to that locates it in the plant's topology, the flags that drive stress analysis, heat tracing, insulation and test packs. Process and piping engineering maintain it jointly; stress, materials, testing and commissioning all consume it. Its value is exactly its danger: the same facts exist on the P&ID, in the model and on the list, and the three are maintained by different hands on different rhythms. A line resized on the P&ID but not the list, or reclassed on the list but not the model, is a defect with no owner until a reviewer or a hydrotest finds it. Mature projects define which document masters which field — and audit the reconciliation, because the definition alone has never once been enough. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Equipment list | Engineering glossary Source: https://armeta.ai/resources/glossary/equipment-list/ Glossary · Cluster E: Drawings and engineering data # Equipment list The register of all tagged equipment on a project, recording each item's tag number, description, service and key parameters — the index against which equipment is engineered, purchased and tracked. Last reviewed: August 4, 2026 ## In detail The equipment list enumerates the plant's engineered items — vessels, exchangers, pumps, compressors, packages — one row per tag, with the identifying and sizing data that lets every discipline and function find its workload in the list: mechanical engineers their datasheets to produce, procurement its requisitions, civil its foundations, electrical its loads. It is typically the first structured deliverable of a project and the spine that other registers hang from. Like the line list, it is a curated redundancy: its contents overlap the P&IDs, the datasheets and the model, and its accuracy is a maintenance discipline rather than a property. The characteristic failures are lifecycle ones — items added on P&IDs but never listed, deleted items surviving in the list and getting foundations designed for them, and duplicate or drifting entries where units were renumbered. The list is also where scope quietly grows: watching its row count and total duty over time is one of the simplest health metrics a project has. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Tag number | Engineering glossary Source: https://armeta.ai/resources/glossary/tag-number/ Glossary · Cluster E: Drawings and engineering data # Tag number The unique identifier assigned to each engineered item in a facility under the project's tagging convention — the key by which the same physical object is recognised across every drawing, list, system and decade. Last reviewed: August 4, 2026 ## In detail A tag — P-101A, FT-2034 — is an address in the plant's namespace. The tagging convention encodes meaning into its structure: item type, unit or area, sequence, suffixes for parallel items; and once assigned, the tag is how the item is referenced on the P&ID, in the datasheet, on the purchase order, in the maintenance system and on the nameplate bolted to the thing itself. Tags are what make the facility's information joinable: every document that mentions FT-2034 is talking about the same instrument, and the tag is the proof. Except when it isn't — and that exception is a whole category of industrial pain. Conventions drift between projects and eras; vendors ship items under their own numbering; brownfield sites accumulate retagging campaigns, legacy tags and duplicates; and the same equipment can live under different identifiers in the engineering archive and the maintenance system. Reconciling identity across those variations is, formally, an entity-resolution problem — and it is the unglamorous first task of every data-integration, digitalisation and revamp effort ever attempted on an existing plant. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Off-page connector | Engineering glossary Source: https://armeta.ai/resources/glossary/off-page-connector/ Glossary · Cluster E: Drawings and engineering data # Off-page connector A symbol marking where a line on a schematic continues on another sheet, carrying the reference to the drawing and connector where it resumes. Last reviewed: August 4, 2026 ## In detail No facility fits on one sheet. P&IDs and other schematics are cut into sheet-sized pieces, and off-page connectors are the stitching: an arrow-like symbol at the sheet edge, labelled with the destination drawing and continuation reference, with a matching symbol pointing back from the other side. Follow the pair and the line is continuous; the drawing set is a graph, and the connectors are its edges. Which is why broken connectors matter beyond tidiness. A reference pointing at a superseded sheet, a renumbered drawing, or nothing at all severs the topology — and severed topology has a specific cost in take-off work, where a line that "leaves the page" and is never picked up on the next one becomes quantities counted on neither sheet. Checking connector integrity across a set of hundreds of sheets is exactly the kind of exhaustive, mechanical verification that humans do slowly and reluctantly, and that every revision reopens. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Redline | Engineering glossary Source: https://armeta.ai/resources/glossary/redline/ Glossary · Cluster E: Drawings and engineering data # Redline A marked-up copy of a drawing recording changes made or required — traditionally in red pen — serving as the field's running record of how the work departed from the issued design. Last reviewed: August 4, 2026 ## In detail Redlines are how reality reports back. When the field routes around an obstruction, resizes a support, or implements an approved concession, the change is marked on the site's master set — the redlines — which accumulate through construction into the raw material of the as-built documentation. Review comments travel the same way: a marked-up drawing is often the most precise possible comment. The redline's weakness is its status: it is the only record of the change until someone incorporates it, and incorporation is exactly the end-of-project task that demobilisation starves. Markups that never reach the drawing office become the gap between documents and facility that the next project pays to rediscover — the as-built failure, at its origin. Sites that scan, log and transmit redlines continuously, rather than warehousing marked paper for a final campaign, are cheaply buying their future selves the truth. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Revision cloud | Engineering glossary Source: https://armeta.ai/resources/glossary/revision-cloud/ Glossary · Cluster E: Drawings and engineering data # Revision cloud The cloud-shaped outline drawn around the changed areas of a drawing, paired with a revision tag, so that a reader can see at a glance what differs from the previous issue. Last reviewed: August 4, 2026 ## In detail A drawing revision without clouds is a puzzle: something changed, and every reader must diff the sheet by eye to find it. Clouding is the courtesy and the control that prevents this — each changed region outlined, tagged with the revision marker, and described in the revision history block, so reviewers review the change rather than re-reviewing the drawing, and the field sees precisely what moved. The convention's failures are its two abuses. The silent edit — a change made without a cloud — defeats the entire mechanism, and is rightly treated as a documentation offence rather than an oversight, because downstream users legitimately rely on unclouded areas being unchanged. The stale cloud — markers surviving from previous revisions — degrades the signal more gently, until sheets carry archaeological layers of clouds and readers stop trusting any of them. Cloud discipline is small, mechanical and disproportionately load-bearing, like most of revision control. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # General arrangement drawing | Engineering glossary Source: https://armeta.ai/resources/glossary/general-arrangement-drawing/ Glossary · Cluster E: Drawings and engineering data # General arrangement drawing A scaled drawing showing the physical arrangement of equipment, structures and major components within an area — in plan, elevation and section — defining where everything actually sits. Last reviewed: August 4, 2026 ## In detail Where schematics define what connects, general arrangements (GAs) define what fits. The GA lays out an area to scale: equipment located and dimensioned, structures, platforms and access, major routing corridors — the spatial agreement that every discipline designs within and against. Civil takes foundations from it, piping routes to it, construction plans lifts and access around it, and operations inherits its judgements about maintainability every day thereafter. GAs are where spatial conflict is negotiated before steel makes it permanent: laydown for the exchanger bundle pull, crane access, escape routes, the pump that must be reachable by more than a contortionist. In model-based workflows the GA is extracted from the 3D model as a view — which is efficient, and which quietly relocates authority: when model and GA disagree, projects must have decided in advance which one governs, because a mixed 2D/3D workflow maintained by separate hands will manufacture such disagreements on schedule. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Plot plan | Engineering glossary Source: https://armeta.ai/resources/glossary/plot-plan/ Glossary · Cluster E: Drawings and engineering data # Plot plan The scaled layout of an entire facility — units, buildings, roads, pipe racks and infrastructure — fixing the spatial relationships and spacing on which safety, cost and future expansion all depend. Last reviewed: August 4, 2026 ## In detail The plot plan is the facility's first and most consequential spatial decision. Drawn early and frozen early, it arranges the units and their separations, routes the main racks and roads, positions the flare, the control room, the substations and the fence — and in doing so it fixes a remarkable share of the project's cost (rack lengths, cable runs, earthworks) and of its risk profile, since inter-unit spacing, hazardous-area separation and emergency access are plot-plan facts before they are anything else. Spacing tables and siting studies from the safety disciplines are its governing inputs. Its failure mode is its own success at freezing: the plot plan is set when equipment sizes are estimates, and late growth — the vendor's compressor package arriving a metre longer, the added exchanger, the future unit the business now wants — must be absorbed by a layout that has already spent its slack. Good plot plans budget that slack deliberately: space is cheapest on the day it is still paper. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Single-line diagram | Engineering glossary Source: https://armeta.ai/resources/glossary/single-line-diagram/ Glossary · Cluster E: Drawings and engineering data # Single-line diagram The electrical schematic that represents a facility's power system with each circuit drawn as a single line — showing sources, transformers, switchgear, distribution and protection in one connected view. Last reviewed: August 4, 2026 ## In detail The single-line (one-line) diagram is the electrical system's P&ID: a deliberately simplified topology in which three-phase circuits collapse to one line each, so that the whole power system — from incoming supply through transformers and switchboards to the loads — can be read as a structure. Electrical engineering designs by it; protection studies, load-flow and fault calculations are organised around it; operations switch and isolate by it; and arc-flash and safety programmes depend on it describing the system that actually exists. That last dependency is the sharp edge. Power systems are modified continuously through a facility's life, and an SLD that lags reality is not a documentation blemish but a hazard: isolation planned on a diagram that omits a source, protection coordinated against a topology that changed. Keeping the SLD current is a compliance obligation in many regimes and a survival habit in all of them — and on brownfield sites, verifying the SLD against the installed system is a standard, sobering first task. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # BIM | Engineering glossary Source: https://armeta.ai/resources/glossary/bim/ Glossary · Cluster E: Drawings and engineering data # BIM Building Information Modelling — the practice of designing and delivering construction projects through structured, object-based digital models that carry data as well as geometry, shared between the parties. Last reviewed: August 4, 2026 ## In detail BIM's substance is the shift from drawing documents to modelling objects: a wall or a pump in a BIM workflow is not lines but an object with properties — type, material, rating, relationships — from which drawings, schedules and quantities are derived views. Around the models sits the collaboration machinery: a common data environment where versions and statuses are managed, exchange formats for moving models between tools, and information requirements defining what data each party owes at each stage. Its promise is single-source truth: quantities taken from the model, coordination performed in it, and a data-rich asset handed to operations. Its delivery depends on the unglamorous parts — naming conventions, information requirements, model management — far more than on the software. The gap between the two has names. "Lonely BIM": modelling for one party's efficiency with no shared data flow. Models built as geometry with empty attributes, from which no take-off can be trusted. And the dual-truth problem — where drawings remain the contractual deliverable, maintained separately from the model until they disagree, at which point the project discovers it never decided which one governs. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Level of development (LOD) | Engineering glossary Source: https://armeta.ai/resources/glossary/level-of-development-lod/ Glossary · Cluster E: Drawings and engineering data # Level of development (LOD) A framework specifying how developed and reliable a model element is at a given stage — commonly on a scale from LOD 100 (conceptual) to LOD 500 (field-verified as-built) — and therefore what its geometry and data may be relied on for. Last reviewed: August 4, 2026 ## In detail A model always looks more finished than it is; LOD exists to say, element by element, how finished it actually is. The commonly used scale runs from conceptual placeholders through approximate and then accurately modelled geometry, on to fabrication-level detail and finally field-verified as-built representation, with each step defining what a consumer may legitimately do with the element — coordinate against it, quantify from it, fabricate from it. Project BIM plans assign target LODs per element type per stage, turning "model the design" into a specified deliverable. The terminology itself forks, in fine glossary tradition: development versus detail — an element can be geometrically detailed yet unreliable — and various frameworks split geometry from information or restate the whole idea as the level of information need. The words differ; the underlying question is constant: what, exactly, can I trust here? The failure is relying past the label — quantities taken off placeholder geometry, clearances checked against approximate shapes — usually because the label was in the BIM plan and the reliance happened in a hurry. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Clash detection | Engineering glossary Source: https://armeta.ai/resources/glossary/clash-detection/ Glossary · Cluster E: Drawings and engineering data # Clash detection The automated checking of a combined multi-discipline 3D model for spatial conflicts — elements occupying the same space, or violating required clearances — before those conflicts are found by construction. Last reviewed: August 4, 2026 ## In detail Clash detection federates the discipline models — piping, structural, electrical, HVAC — and searches the union for interference: hard clashes where objects intersect, and soft or clearance clashes where required space (access, maintenance envelopes, insulation) is violated. It runs in cycles as the models develop, feeding coordination meetings where clashes are assigned, resolved and re-checked; every clash resolved on screen is a field rework avoided at a fraction of the price. The practice's realities are managerial. A first run on a large model returns clashes by the thousand, most of them duplicates, trivialities or artefacts of modelling style, and the craft is in the rules and triage that surface the hundred that matter. And a clash-free model is a necessary condition, not a sufficient one: the software checks the finished geometry, not whether the pipe can be installed — erection sequence, welding access, pull spaces — and it checks only what was modelled, at the LOD it was modelled to. The clash report inherits every limitation of the model beneath it, silently. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Industry Foundation Classes (IFC) | Engineering glossary Source: https://armeta.ai/resources/glossary/industry-foundation-classes-ifc/ Glossary · Cluster E: Drawings and engineering data # Industry Foundation Classes (IFC) The open, vendor-neutral data schema for describing and exchanging building information models — the common language by which BIM data moves between different software tools. Last reviewed: August 4, 2026 ## In detail IFC, maintained by buildingSMART, defines a standard vocabulary of objects, properties and relationships for the built environment — walls, beams, systems, spaces, and the data attached to them — so that a model authored in one tool can be read by another without a private translator. It is the backbone of openBIM practice and, increasingly, of client mandates: owners specify IFC deliverables precisely so their asset data does not arrive locked to a vendor. Exchange is scoped by defined subsets tailored to purposes — coordination, handover — since no consumer needs everything. Not to be confused with the other IFC in this glossary — Issued for Construction, the drawing revision status. The two share three letters and a project, nothing else; correspondence that spells one of them out earns its keep. IFC's honest limitation is that translation is lossy in practice: parametric intelligence flattens to geometry-plus-properties, tool-specific data drops or mangles, and an export made as an afterthought validates as IFC while disappointing everyone downstream. Exchange quality is specified, tested and checked — or discovered. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # DEXPI | Engineering glossary Source: https://armeta.ai/resources/glossary/dexpi/ Glossary · Cluster E: Drawings and engineering data # DEXPI The process industry's standard for exchanging intelligent P&ID data — letting the full content of a P&ID, its objects, topology and attributes, move between software systems in machine-readable form. Last reviewed: August 4, 2026 ## In detail DEXPI (Data Exchange in the Process Industry) answers a specific, expensive question: how does a P&ID leave the tool that authored it without dying into a picture? The specification defines a standard representation of P&ID content — equipment, piping, instrumentation, their properties and their connectivity — carried in an XML-based format, so that owner-operators can receive intelligent P&IDs from contractors regardless of authoring system, and downstream applications can consume the diagram as data. The initiative is driven by process-industry owners and implemented, progressively, by the major authoring vendors, in alignment with the broader plant-data standardisation work around ISO 15926. Its scope is worth stating precisely: DEXPI standardises the exchange of already-intelligent P&IDs. It describes the destination, not the journey — the millions of legacy P&IDs existing as scans and flat CAD are outside its gift until something first reconstructs their content as data. And as with every exchange standard, conformance varies by implementation: what round-trips cleanly between tools is discovered by testing, not by reading the press releases. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Digital twin | Engineering glossary Source: https://armeta.ai/resources/glossary/digital-twin/ Glossary · Cluster E: Drawings and engineering data # Digital twin A digital representation of a physical asset that is kept connected to it — updated with the asset's data so that the model reflects, and can be used to reason about, the asset's actual state. Last reviewed: August 4, 2026 ## In detail The defining feature of a twin is the live link. A model describes an asset as designed or as built; a twin is fed by the asset — operating data, inspection results, modifications — so that queries, simulations and decisions run against current reality: what is this unit's condition, what happens if we push this parameter, which valve does this work order actually mean. The value cases are operational: performance monitoring, integrity and maintenance planning, operator training, scenario testing before touching the plant. The term's problem is inflation. "Digital twin" is applied to everything from a 3D viewer to a genuinely synchronised operational platform, and the honest questions cut through the marketing: what data flows in, how often, from where; what structure connects the geometry to the tags, documents and systems; and who maintains all of it after the project team leaves. A twin is a data liability wearing a data asset's clothes unless the feeding and governance are funded for the asset's life — the handover problem, again, at its largest scale. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Knowledge graph | Engineering glossary Source: https://armeta.ai/resources/glossary/knowledge-graph/ Glossary · Cluster E: Drawings and engineering data # Knowledge graph A way of structuring information as a network of entities and typed relationships — things, connected by what they mean to each other — that systems can traverse and query. Last reviewed: August 4, 2026 ## In detail A knowledge graph stores facts as connections: this pump feeds that exchanger, appears on this P&ID, is specified by that datasheet, belongs to this system. Where tables hold records and files hold documents, the graph holds the relationships between them as first-class data — which suits engineering information unusually well, since a facility is a network of typed connections, and most hard questions about one ("what does this isolation affect", "which documents change if this line is resized") are questions about paths through that network. Built over an asset's documents and registers, a graph becomes the queryable form of what the documentation collectively knows — with each fact ideally traceable to its source document, since an unverifiable graph is folklore at scale. Its quality ceiling is set at ingestion: the graph knows only what was extracted, resolved and linked correctly, so tag-identity mistakes and missed connections propagate into every downstream query. And like any structured store, it needs a maintained vocabulary of entity and relationship types — an ontology — or five years of incremental additions produce a graph that disagrees with itself about what its own edges mean. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # CAD | Engineering glossary Source: https://armeta.ai/resources/glossary/cad/ Glossary · Cluster E: Drawings and engineering data # CAD Computer-aided design — the family of software tools in which drawings and models are authored, from 2D drafting through 3D modelling to data-centric design systems. Last reviewed: August 4, 2026 ## In detail CAD is the pencil's successor three times over. First-generation tools digitised drafting: lines, arcs and text on electronic sheets, faster to edit and copy than paper but carrying no more meaning. 3D systems added geometry that could be coordinated, visualised and measured. Data-centric systems — plant design suites, BIM authoring tools — made the objects primary: the model as database, the drawings as generated views. All three generations remain in production use, often within one company, which is why "we have it in CAD" is a statement that means almost nothing until the generation is specified. The industry's stock of CAD legacy is its own subject. Decades of DWG and station files hold enormous embedded effort — and, for the older generations, hold it as geometry whose meaning lives in conventions, layer names and the memories of the people who drew it. Format longevity, tool obsolescence and the difference between having the file and having the information are problems every long-lived owner eventually funds, usually during a revamp that needed the information rather than the file. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # 2D drafting and 3D modelling | Engineering glossary Source: https://armeta.ai/resources/glossary/2d-drafting-and-3d-modelling/ Glossary · Cluster E: Drawings and engineering data # 2D drafting and 3D modelling The two modes of producing engineering documentation — authoring scaled drawings directly, versus building a 3D model from which drawings and data are derived — and the hybrid reality in which most projects run both. Last reviewed: August 4, 2026 ## In detail The modes differ in what is primary. In 2D drafting the drawing is the artefact: each sheet authored and maintained by hand, consistency between sheets a matter of discipline. In model-based work the 3D model is primary: coordinated in space, checked for clashes, quantified by extraction, with drawings generated as views — consistent with the model by construction, and with each other through it. The industry's actual state is hybrid, and durably so. Contracts and authorities still consume drawings; small projects and certain disciplines still draft; brownfield work inherits 2D archives whatever the new scope uses; and the model-based project still issues sheets because the fabricator, the reviewer and the law expect them. The hybrid's tax is dual maintenance: wherever a drawing can be edited independently of the model — or survives from before the model existed — the two can diverge, and the project needs an explicit rule for which governs. The transition between modes is not a software purchase but a data question: 2D archives become model-based information only through interpretation — of scans, of conventions, of what the draughtsman meant — which is precisely why the legacy stock persists as 2D long after the tools moved on. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Smart P&ID (intelligent P&ID) | Engineering glossary Source: https://armeta.ai/resources/glossary/smart-p-and-id-intelligent-p-and-id/ Glossary · Cluster E: Drawings and engineering data # Smart P&ID (intelligent P&ID) A P&ID authored as structured data — every symbol an object with attributes, every line a connection in a topology — so that the drawing is a view of a database rather than a picture of a plant. Last reviewed: August 4, 2026 ## In detail The distinction sounds technical and is total. A flat P&ID — a scan, a PDF, a drafted CAD file — is legible to engineers and inert to systems: its pump is a cluster of lines that resembles a pump. In a smart P&ID the pump is an object carrying its tag, type and properties, connected to line objects that know their size, class and destinations; the diagram and the data are one artefact. Everything downstream changes accordingly: line lists and equipment registers generate from the drawing instead of being reconciled against it, consistency rules run automatically, and the P&ID's content flows to other systems — via standards like DEXPI — as data rather than as homework. Two honest caveats govern the term. Intelligence is tool-bound until exchanged: a P&ID smart in its authoring system and delivered as PDF arrives flat. And the installed world is overwhelmingly flat — decades of scans and drafted files — so the practical question for owners is less "why author smart" (settled) than "what upgrades the legacy": redraw by hand, or reconstruct the objects and topology from the drawings that exist. Both are conversions of pictures into data; they differ in who, or what, does the reading. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Bill of materials (BOM) | Engineering glossary Source: https://armeta.ai/resources/glossary/bom-bill-of-materials/ Glossary · Cluster E: Drawings and engineering data # Bill of materials (BOM) The list of materials and components required to build a defined assembly or drawing — such as the table on a piping isometric — as distinct from a material take-off, which aggregates across a project, and a bill of quantities, which measures work for pricing. Last reviewed: August 4, 2026 ## In detail The three lists are cousins with different jobs, and the differences are worth exact words. A BOM belongs to an artefact: this isometric, this skid, this fabrication drawing, listing every component the assembly consumes — its scope is the drawing's scope, its consumer the fabricator. An MTO belongs to the project: quantities extracted and aggregated across many drawings and the model, structured for procurement and estimating — buy this much pipe, of these classes, by this date. A BOQ belongs to the contract: measured items of work, labour included, structured under measurement rules for tendering and payment. Same underlying plant; three structures, three audiences, three standards of care. The mappings between them are where quantities go to disagree. Isometric BOMs sum to the piping MTO — minus the allowances, plus the growth. The MTO informs the BOQ's material content — restructured under measurement rules that count differently. Reconciling the three is routine, manual and never quite finished; and a conversation in which two parties say "the bill" meaning different lists is a conversation heading somewhere expensive. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Legend sheet | Engineering glossary Source: https://armeta.ai/resources/glossary/legend-sheet/ Glossary · Cluster E: Drawings and engineering data # Legend sheet The sheet at the front of a drawing set that defines the symbols, line types, abbreviations and identification conventions used throughout it — the key without which the set cannot be reliably read. Last reviewed: August 4, 2026 ## In detail Drawing symbology is standardised only up to a point. Beyond the common core, every owner and engineering firm maintains its own conventions — valve symbols, line designations, instrument bubbles, tagging formats — and the legend sheets (lead sheets) are where a set declares its dialect. They are produced with the first issue of the set and consumed, ideally, by everyone who reads any sheet after; in practice, by newcomers, reviewers and anyone burned before. The failure is assumed fluency. Engineers read drawings all day and read legends almost never, importing the conventions of their last project into this one — and most of the time the dialects are close enough that nothing happens, which is exactly what trains the habit that eventually hurts. The same symbol meaning a different valve type, a line code ordering its fields differently: small divergences, invisible until quantified. Anything that reads drawings at scale inherits the problem in concentrated form — take-off across multiple legacy sets, from multiple eras and firms, means as many dialects as sources, and the legend sheets, where they survive, are the Rosetta stones of the exercise. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Piping class (pipe spec) | Engineering glossary Source: https://armeta.ai/resources/glossary/pipe-specification/ Glossary · Cluster E: Drawings and engineering data # Piping class (pipe spec) A specification defining the approved materials and components — pipe, fittings, flanges, valves, gaskets, bolting — for a given service, identified by a class code carried on the P&IDs and line list. Last reviewed: August 4, 2026 ## In detail Piping engineering does not select components line by line; it selects a class. Each piping class packages a coherent set of choices for a service envelope — the fluid, the pressure–temperature range, the corrosion allowance — so that specifying a line reduces to assigning its class, and every component on it follows from the class tables. The class code travels on the line number, and the specification behind it governs procurement, fabrication and inspection for everything built to it. Where classes change, the plant has a spec break — a defined point on a line where one class ends and another begins, marked on the P&ID and consequential everywhere: the components differ on each side, the MTO must count them to the correct class, and the break's exact position is a fact worth the drawing space it occupies. The failure modes are correspondingly concentrated: a wrong class assignment propagating into every component on the line; breaks placed ambiguously and taken off differently by different readers; and class revisions mid-project rippling through the MTO for every line that carries the code — a small edit with a long shadow. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Tie-in | Engineering glossary Source: https://armeta.ai/resources/glossary/tie-in/ Glossary · Cluster E: Drawings and engineering data # Tie-in A defined point at which new work connects to an existing system — specified, numbered and managed as a register, because each one is a controlled intrusion into a live facility. Last reviewed: August 4, 2026 ## In detail Tie-ins are where brownfield projects touch the plant that is already running, and they are managed with corresponding formality: a tie-in list enumerating every connection, each with its location, the existing line or system it enters, the method — a shutdown connection made with the system down and cleared, or a hot tap performed on the live line — and the isolation, draining and permitting the method requires. The list is a contract between the project and operations: these intrusions, at these points, in these windows. Each tie-in also carries a small discovery risk from the existing side: the line whose actual routing, wall thickness or condition differs from the documents — verified by walkdown, scan or UT before the window, or discovered during it, at window prices. Shutdown-dependent tie-ins concentrate the schedule risk further, queueing the project's connections into turnaround windows that will not wait. The classic failures: the tie-in discovered late, after the shutdown scope froze; the existing side not as documented; and the register treated as an engineering list rather than the operations negotiation it actually is. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Point cloud / laser scanning | Engineering glossary Source: https://armeta.ai/resources/glossary/point-cloud-laser-scanning/ Glossary · Cluster E: Drawings and engineering data # Point cloud / laser scanning The capture of existing physical conditions as millions of measured 3D points — producing a geometric record of a facility as it actually stands, against which brownfield design can be checked. Last reviewed: August 4, 2026 ## In detail A laser scanner sweeps a scene and returns a point cloud: dense, accurate 3D coordinates of every surface in view. Scans from many positions are registered into one cloud covering a unit or a site, and the result is the closest thing brownfield work gets to ground truth — new design routed through the cloud, clashes checked against reality rather than against as-builts of uncertain honesty, and dimensional questions answered from the desk instead of the scaffold. Where the documentation gap is the brownfield tax, scanning is how the tax is paid deliberately instead of accidentally. The honest limits: a cloud is geometry without meaning. It contains no tags, no line numbers, no topology — a pipe in the cloud is a tube of points until a human or an algorithm says which line it is — so scan-to-model is interpretation labour, priced accordingly, and usually scoped to what the project needs rather than everything the scanner saw. Coverage has shadows — behind equipment, under insulation, inside anything — and insulated lines are measured at the cladding, not the pipe. The cloud tells the truth, completely, about surfaces it could see; everything else is still inference. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Data handover | Engineering glossary Source: https://armeta.ai/resources/glossary/data-handover/ Glossary · Cluster E: Drawings and engineering data # Data handover The transfer of structured engineering information — tag registers, attributes, relationships, documents linked to the assets they describe — from project to owner, as distinct from handing over the documents alone. Last reviewed: August 4, 2026 ## In detail The handover package, in its traditional form, delivers documents: findable files, correctly indexed. Data handover raises the bar to information: the owner receives the plant's facts in structured form — every tag with its attributes, every document linked to the tags it concerns, hierarchies and relationships intact — loadable into maintenance, integrity and operations systems without an army re-keying PDFs. The demand side is codified in owner information requirements and in industry specifications written for exactly this purpose (the process industries' CFIHOS, built on the ISO 15926 foundations; the ISO 19650 framework in buildings), which define the classes, attributes and formats owed. The economics are unforgiving in both directions. Specified at contract and delivered progressively, structured data costs the project little — the information exists in its systems already. Unspecified, it does not arrive; and reconstructing it afterwards, from documents, is the expensive archaeology that half the industrial-data market exists to perform. The failure is thus almost always a procurement failure with a technical costume: the contract asked for documents, the owner needed data, and the difference was discovered at go-live of a maintenance system with empty fields. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # ISO 15926 | Engineering glossary Source: https://armeta.ai/resources/glossary/iso-15926/ Glossary · Cluster E: Drawings and engineering data # ISO 15926 The international standard for representing and integrating lifecycle information about process plants — a common data model and reference vocabulary intended to let plant information move between systems, organisations and decades without losing its meaning. Last reviewed: August 4, 2026 ## In detail ISO 15926 addresses the long problem: a process facility's information outlives every tool, format and contractor that touches it, and the standard's ambition is a representation neutral enough to survive them all — a generic data model plus reference libraries of standard classes, so that "centrifugal pump" and its properties mean the same thing in every compliant system, this year and in thirty. Its practical career has been as a foundation more than a product. Direct implementation is demanding — the standard's generality is real work to apply — and its adoption has flowed mainly through specifications derived from and aligned with it: DEXPI for P&ID exchange, CFIHOS for handover information, and owner data specifications built on its vocabularies. Judged as a deployable format it can look perpetually forthcoming; judged as the semantic groundwork under the process industry's interoperability efforts, it is quietly everywhere. For a project, the standard matters at one remove: the question is rarely "do we implement ISO 15926" and usually "which specification built on it does our owner's information requirement cite" — which is the form in which its decades of committee work actually arrive on site. ## Next step See how Armeta applies engineering intelligence in practice ## Related Terms: P&ID; PFD; Piping isometric Workflows: — Regulations: — ## Closing CTA ### See this workflow in practice. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # What is a HAZOP? Hazard and Operability Study Explained Source: https://armeta.ai/resources/glossary/hazop-hazard-and-operability/ Glossary · HAZOP # What is a HAZOP (Hazard and Operability Study)? A HAZOP — Hazard and Operability Study — is a structured methodology for conducting a Process Hazard Analysis (PHA) on a continuous or batch process system. It is the most widely used PHA methodology in the chemical, petrochemical, refining, and related process industries because of its systematic thoroughness. Last reviewed: April 30, 2026 ## How a HAZOP is conducted A HAZOP is performed by a multi-disciplinary team, typically including a process engineer, a safety specialist, an operations representative, a maintenance representative, and a facilitator or scribe. The team works through the process system node by node — dividing the system into discrete sections along the piping and equipment — and applies a standard set of guide words to each node. The guide words are: - No / None (e.g., no flow, no pressure) - More (e.g., more temperature, more pressure) - Less (e.g., less flow, less concentration) - As well as (e.g., impurity present in addition to the intended substance) - Part of (e.g., only one component of a mixture reaches the node) - Reverse (e.g., flow in the opposite direction) - Other than (e.g., a different substance entirely) For each combination of guide word and process parameter at each node, the team asks: what are the possible causes of this deviation, what are the consequences, and what safeguards are in place? Gaps in safeguards become HAZOP recommendations for action. ## Duration and resource intensity A full HAZOP on a complex process unit (for example, a refinery crude distillation unit or a large chemical reactor system) typically takes two to four weeks of multi-disciplinary team sessions, usually running four-to-eight hours per day. The preparation work — gathering and confirming Process Safety Information, including current P&IDs — typically consumes significantly more time than the HAZOP sessions themselves. ## HAZOP versus PHA In everyday conversation, the terms are often used interchangeably. Technically, HAZOP is one methodology for conducting a PHA — the regulatory requirement. OSHA 29 CFR 1910.119(e)(2) lists several acceptable PHA methodologies. HAZOP is the dominant choice for complex continuous processes; simpler processes may use What-If, Checklist, or hybrid methodologies. ## Revalidation cycles Under OSHA 29 CFR 1910.119(e)(6), a PHA — including a HAZOP — must be updated and revalidated at least every five years. Major process changes (handled through the Management of Change process) can also trigger PHA revisions outside the five-year cycle. ## The role of P&IDs in a HAZOP A HAZOP cannot be conducted without current, accurate P&IDs. The drawings define the nodes, the flows, the equipment, the instrumentation, and the protective systems that the HAZOP team evaluates. Stale or inaccurate P&IDs directly degrade the quality of a HAZOP. Because most facilities maintain their P&IDs as PDFs with ad-hoc revision control, the HAZOP preparation phase — confirming the drawings are current, aligning field walkdown findings with as-built records, and rebuilding Process Safety Information — routinely consumes more engineering hours than the HAZOP sessions themselves. ## Next step See how Armeta prepares P&IDs for HAZOP ## Related Terms: PHA — Process Hazard Analysis; MOC — Management of Change; PSI — Process Safety Information Workflows: PHA revalidation support Regulations: OSHA PSM — 29 CFR 1910.119 ## Closing CTA ### Your documents, your data — See Armeta on your preconstruction workflow. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # What is LDAR? Leak Detection and Repair Explained Source: https://armeta.ai/resources/glossary/ldar-leak-detection-and-repair/ Glossary · LDAR # What is Leak Detection and Repair (LDAR)? Leak Detection and Repair (LDAR) is the regulatory compliance program under which facilities handling volatile organic compounds (VOCs) or hazardous air pollutants (HAPs) systematically monitor equipment components for fugitive emissions and repair detected leaks within specified timeframes. LDAR is mandated by the Clean Air Act and codified across multiple EPA regulations in 40 CFR Parts 60, 61, and 63. Last reviewed: April 30, 2026 ## What counts as a leak A fugitive emission is an unintentional release from an equipment component — a valve stem, a pump seal, a flange, a connector — rather than from a designed emission point like a stack or a vent. LDAR regulations require operators to measure component emissions using EPA Method 21 (typically a portable flame ionization detector) and compare the reading against a leak threshold specified by the applicable rule. The two most common leak thresholds in US LDAR regulations are: - 500 ppmv above background — applied under many NESHAP rules and under NSPS Subpart VVa for valves in gas service - 10,000 ppmv above background — applied under older NSPS provisions and for certain lower-risk component types The threshold that applies depends on the specific regulation, the component type, and the service classification (gas service, light liquid, heavy liquid). Applying the wrong threshold to the wrong component is itself a recordkeeping violation, even if the underlying measurement is accurate. ## What components LDAR covers LDAR programs cover equipment components that contact VOC or HAP process streams. The typical scope includes: - Valves — by far the largest component category at most facilities - Pump seals and compressor seals - Flanges and connectors - Pressure relief devices (PRDs) - Sampling connections - Open-ended lines - Agitator seals (for reactor applications) A large US refinery typically carries seventy thousand or more LDAR-regulated components. Each component must be tagged, located, classified by service, assigned a monitoring frequency under the applicable rule, and tracked through its lifecycle of inspection, leak detection, repair verification, and retirement. ## The regulatory basis LDAR is not a single regulation — it is a requirement that appears across multiple Clean Air Act programs: - NSPS (New Source Performance Standards) under 40 CFR Part 60 — equipment leak subparts including VV, VVa, VVb, GGG, GGGa for SOCMI and petroleum refineries, and OOOOb/OOOOc for oil and gas facilities - NESHAP (National Emission Standards for Hazardous Air Pollutants) under 40 CFR Part 61 — including the Benzene NESHAP at Subpart J - NESHAP/MACT under 40 CFR Part 63 — including the Hazardous Organic NESHAP (HON) at Subpart H and the Refinery NESHAP at Subpart CC A facility subject to both an NSPS and a NESHAP for the same equipment must generally comply with the more stringent standard. ## The role of P&IDs in LDAR LDAR compliance requires an accurate, current component inventory — and the master record of which components exist in which service is the governing P&ID. EPA's Leak Detection and Repair: A Best Practices Guide (October 2007) specifically identifies misalignment between the P&ID and the physical component inventory as a source of incomplete monitoring and audit findings. Facilities that maintain their P&IDs as static PDFs routinely accumulate drift between the drawings and the field installation — undocumented field modifications, missing components, or components recorded but not installed. The LDAR program inherits this drift and carries it forward. ## Next step See how Armeta supports LDAR component inventory ## Related Terms: MOC — Management of Change; PSI — Process Safety Information; P&ID — Piping and Instrumentation Diagram Workflows: LDAR component inventory Regulations: EPA LDAR Best Practices; EPA Method 21 ## Closing CTA ### Your documents, your data — See Armeta on your preconstruction workflow. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # What is a PHA? Process Hazard Analysis Explained Source: https://armeta.ai/resources/glossary/pha-process-hazard-analysis/ Glossary · PHA # What is a Process Hazard Analysis (PHA)? A Process Hazard Analysis (PHA) is the systematic, multi-disciplinary evaluation of the hazards present in a covered process — and a regulatory requirement under OSHA's Process Safety Management standard at 29 CFR 1910.119(e) and EPA's Risk Management Program at 40 CFR 68.67. The PHA identifies, evaluates, and recommends control measures for the hazards involved in the process. Last reviewed: April 30, 2026 A PHA is not a single methodology — it is a regulatory requirement that can be satisfied by any of several acceptable analytical methodologies. The most common in the chemical, refining, and petrochemical industries is HAZOP. Other accepted methodologies include What-If, Checklist, What-If/Checklist, Failure Mode and Effects Analysis (FMEA), Fault Tree Analysis, and "an appropriate equivalent methodology" as recognized by OSHA in 29 CFR 1910.119(e)(2). ## What a PHA must address OSHA's PSM standard at 29 CFR 1910.119(e)(3) requires that the PHA address: - The hazards of the process - The identification of any previous incident which had a likely potential for catastrophic consequences in the workplace - Engineering and administrative controls applicable to the hazards and their interrelationships - Consequences of failure of engineering and administrative controls - Facility siting - Human factors - A qualitative evaluation of a range of the possible safety and health effects of failure of controls on employees in the workplace ## How a PHA is conducted A PHA is performed by a team that includes at least one person with expertise in engineering and process operations, one or more employees who have experience and knowledge specific to the process being evaluated, and one person who is knowledgeable in the specific PHA methodology being used. For continuous processes, the most common methodology is a HAZOP — see the HAZOP entry for details on how a HAZOP team works through a process system. The PHA must be documented. Each identified hazard, the existing safeguards, the team's evaluation of consequences and likelihood, and any recommended actions must be recorded. ## PHA recommendations and follow-up 29 CFR 1910.119(e)(5) requires the employer to establish a system to promptly address the team's findings and recommendations. The employer must assure that the recommendations are resolved in a timely manner and that the resolutions are documented; that documented resolutions are communicated to operating, maintenance, and other employees whose work assignments are in the process; and that the resolutions are completed. Open PHA recommendations — items the team identified as hazards that should be addressed but that have not yet been resolved — are a frequent target of OSHA enforcement attention. ## The five-year revalidation cycle 29 CFR 1910.119(e)(6) requires that the PHA be updated and revalidated by a team meeting the same expertise requirements at least every five years. The revalidation must assure the PHA is consistent with the current process. In practice, the engineering effort required to prepare a process for PHA revalidation — confirming Process Safety Information is current, including verifying the P&IDs reflect the as-installed plant — frequently consumes more engineering hours than the PHA sessions themselves. The revalidation interval has not changed since the standard was finalized in 1992; the engineering effort required to meet it has grown as facilities accumulate more years of MOC backlog and document drift. ## The role of P&IDs in a PHA P&IDs define the process system that the PHA evaluates. They establish the equipment, the piping, the instrumentation, the protective systems, and the operating envelope. The PHA team uses the drawings to walk through the process node by node, identify deviations, and evaluate consequences. If the P&IDs are not current — if MOCs have been implemented but not yet incorporated into the drawings of record — the PHA evaluates a process that no longer exists. This is the failure mode behind many post-incident investigation findings: the documents the PHA team reviewed did not reflect the plant the operators were running. ## Next step See how Armeta supports PHA revalidation ## Related Terms: HAZOP — Hazard and Operability Study; MOC — Management of Change; PSI — Process Safety Information Workflows: PHA revalidation support Regulations: OSHA PSM — 29 CFR 1910.119; EPA RMP — 40 CFR Part 68 ## Closing CTA ### Your documents, your data — See Armeta on your preconstruction workflow. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # What is PSI? Process Safety Information Explained Source: https://armeta.ai/resources/glossary/psi-process-safety-information/ Glossary · PSI # What is Process Safety Information (PSI)? Process Safety Information (PSI) is the documentation package required by OSHA's Process Safety Management standard at 29 CFR 1910.119(d). It is the foundation on which every other PSM element — Process Hazard Analysis, Mechanical Integrity, Operating Procedures, Management of Change, Pre-Startup Safety Review — is built. Without complete and current PSI, the rest of the PSM program cannot be conducted in a defensible way. Last reviewed: April 30, 2026 OSHA's standard requires the employer to complete a compilation of written process safety information before conducting any process hazard analysis. The compilation enables the employer and the employees involved in operating the process to identify and understand the hazards posed by those processes involving highly hazardous chemicals. ## What PSI must contain 29 CFR 1910.119(d) organizes PSI into three categories: ### Information pertaining to the hazards of the highly hazardous chemicals - Toxicity information - Permissible exposure limits - Physical data - Reactivity data - Corrosivity data - Thermal and chemical stability data - Hazardous effects of inadvertent mixing of different materials that could foreseeably occur In modern practice this category is satisfied by Safety Data Sheets and supplementary chemistry references. ### Information pertaining to the technology of the process - A block flow diagram or simplified process flow diagram (PFD) - Process chemistry - Maximum intended inventory - Safe upper and lower limits for items such as temperatures, pressures, flows or compositions - An evaluation of the consequences of deviations, including those affecting the safety and health of employees This category is satisfied by the FEED-stage and operational process documentation: PFDs, basis-of-design documents, process descriptions. ### Information pertaining to the equipment in the process - Materials of construction - Piping and Instrumentation Diagrams (P&IDs) - Electrical classification - Relief system design and design basis - Ventilation system design - Design codes and standards employed - Material and energy balances for processes built after 1992 - Safety systems (e.g., interlocks, detection or suppression systems) The employer must document that equipment complies with recognized and generally accepted good engineering practices. This third category — and specifically the P&IDs — is the engineering documentation core of the PSM program. Every other PSM element references back to it. ## Why P&IDs sit at the center of PSI Of the three PSI categories, the equipment information category — and within it, the P&IDs — is the one that: - Defines the physical scope of the covered process - Is referenced directly by the Process Hazard Analysis - Must be updated whenever a Management of Change is implemented - Is reviewed during Pre-Startup Safety Reviews - Is provided to employees who operate, maintain, or otherwise work with the process When OSHA cites PSI deficiencies in enforcement, the most frequently cited gap is P&IDs that are not current — drawings that do not reflect MOCs that have been implemented in the field, or drawings that pre-date the current configuration of the process. ## The PSI update obligation 29 CFR 1910.119(l)(4) requires that, when a change to a covered process results in a change to PSI, the PSI must be updated accordingly. This is the regulatory link that ties every Management of Change back to the governing P&IDs and other engineering documentation. In practice, most facilities run with a backlog of MOCs that have been physically implemented but for which the corresponding PSI updates — particularly P&ID redrafts — have not yet been completed. This backlog is the structural source of P&ID drift in operating PSM facilities. ## Why PSI reconciliation is the dominant pre-PHA effort Every five-year PHA revalidation begins with a PSI reconciliation: confirming that the P&IDs the team will work from reflect the current state of the plant. On facilities with multi-year MOC backlogs, this reconciliation routinely consumes more engineering effort than the PHA sessions themselves. The reconciliation typically involves: - Pulling every MOC closed since the last PHA - Checking which ones modified physical equipment or piping - Identifying which P&IDs are affected by each MOC - Verifying that the redline updates have been incorporated into the official drawings - Issuing rev-controlled updates for any drawings that are out of sync The volume of work and the manual nature of this reconciliation are why PHA revalidation timelines have stretched at most operating facilities, even though the underlying regulatory requirement (the five-year cycle) has not changed since 1992. ## Next step See how Armeta automates PSI reconciliation ## Related Terms: PHA — Process Hazard Analysis; HAZOP — Hazard and Operability Study; MOC — Management of Change Workflows: PHA revalidation support; Automated MOC reconciliation Regulations: OSHA PSM — 29 CFR 1910.119 ## Closing CTA ### Your documents, your data — See Armeta on your preconstruction workflow. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # What is a From-To List? Piping From-To Connectivity Explained Source: https://armeta.ai/resources/glossary/from-to-list/ Glossary · FROM-TO # What is a From-To List? A from-to list is the tabular record that defines the origin ("from") and destination ("to") of every piping line in a process unit or facility. Each row specifies a line number, the equipment tag or system reference where the line begins, and the equipment tag or system reference where the line ends. The from-to list is a subset of the broader line list, focused specifically on connectivity — it answers the question "where does this line come from and where does it go?" across the entire facility. Last reviewed: April 30, 2026 ## What a from-to list looks like A typical from-to list row contains: - Line number — the encoded identifier that ties to the P&ID, isometric, and line list - From — the equipment tag (e.g., V-101 reactor) or off-page connector reference where the line originates - To — the equipment tag or off-page connector reference where the line terminates - Service — the process fluid carried (e.g., reactor effluent, hydrogen makeup) - Source P&ID — the drawing on which the line is shown A from-to list for a refinery unit might run hundreds to a few thousand rows. A from-to list for a major capital project might run into tens of thousands. ## From-to data sources From-to information is not a primary engineering deliverable in the same way that the P&ID or the isometric is. It is derived information — extracted from primary documents and recorded in tabular form. The data sources for a from-to list: - P&IDs and PFDs — where lines connect equipment schematically. The "from" and "to" of every line are defined on the P&ID, either through direct connection at the equipment nozzle or through an off-page connector. - Piping isometrics — where physical routing is documented. The isometric confirms how the line physically gets from "from" to "to" — through which pipe rack, at which elevation, with which fittings. - Line list — where the from-to data is maintained as part of the engineering record. Discrepancies between these three sources indicate either a documentation error or an undocumented field modification. ## From-to lists in brownfield work On any modification to an existing facility, the from-to list is the first document engineers need to understand the scope. The questions a brownfield engineering team needs to answer at the start of a revamp: - Which lines connect to the equipment being modified? - Where do those lines go? - What other systems are affected by the modification? - Which P&IDs span the scope? - Which isometrics need to be reviewed for tie-ins? Without accurate from-to data, scope definition relies entirely on field walkthroughs and manual reading of the full P&ID set. On a unit with several hundred drawings, this is a multi-week engineering effort that runs at the start of every modification project. When the from-to data is current and structured, the same scoping question can be answered in hours rather than weeks. The engineering team queries the from-to list for every line connecting to the affected equipment, retrieves the corresponding P&IDs and isometrics, and proceeds directly to the technical scope definition. ## From-to connectivity and the engineering knowledge graph When from-to data is structured and contextualized across P&IDs, PFDs, isometrics, and line lists, it forms the connectivity backbone of the engineering knowledge graph — the logical map of how every line in the facility connects equipment to equipment and system to system. The connectivity backbone is what makes the rest of the engineering graph traversable: - Starting from any equipment tag, you can find every line connected to it - Starting from any line number, you can find every equipment item it touches - Starting from any system, you can find every line and every piece of equipment that belongs to that system - Starting from any process disturbance, you can trace which downstream lines and equipment are affected This is the network structure that makes a queryable engineering knowledge graph distinct from a flat structured extraction. ## Why from-to data is hard to maintain manually From-to data is among the most fragile parts of the engineering record because it depends on cross-document consistency. A change to a P&ID — a line rerouted, an equipment item replaced — must propagate to: - The line list (with updated from-to data) - Every isometric that contains the affected line - The from-to list itself - Operating procedures that reference the affected line When any of those propagations is missed, the from-to list drifts from the rest of the engineering record. After several years of accumulated MOCs and field changes, the from-to list typically has measurable drift relative to the as-installed plant. ## Next step See how Armeta extracts from-to connectivity ## Related Terms: Line List; P&ID — Piping and Instrumentation Diagram; Piping Isometric Drawing; MTO — Material Take-Off Workflows: Brownfield data migration; As-built reconciliation Regulations: — ## Closing CTA ### Your documents, your data — See Armeta on your preconstruction workflow. Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work. CTA: Book a demo --- # Blog and insights — Armeta Source: https://armeta.ai/resources/blog/ # Insights from the Armeta team. Blog and insights CTA: Book a demo ## Coming soon New articles are in progress. --- # Book a demo — Armeta Source: https://armeta.ai/demo/ Book a demo # See Armeta on your documentation. Tell us what you work on and bring a real document set. In the demonstration we run Armeta on documentation like yours and show you exactly what comes out. ### Demo form - Name — placeholder: Your full name - Organization — placeholder: Your organization - Role — placeholder: Your role or title - Phone number — placeholder: +1 555 000 0000 - Which product interests you — options: Armeta Smeta; Armeta Permit; Armeta P&ID; Armeta Codes; Armeta Materials; Armeta CAD; Not sure yet - E-mail — placeholder: you@company.com - Comments (optional) — placeholder: Tell us about your documents, questions, or timeline... We respond within one business day. Your information is used only to coordinate the conversation. Request demo ### After successful submit # Request received. A member of the Armeta team will respond within one business day to schedule the next step. If anything is urgent, write directly to hello@armeta.ai. ## What happens after you submit - 01 — A member of our team responds within one business day to schedule the session and understand your document set. - 02 — In the demonstration, we run Armeta on documentation like yours and show you exactly what comes out. --- # Company — Armeta Source: https://armeta.ai/company/ # About Armeta. Company Armeta builds AI systems for construction and heavy industries, helping projects move faster from planning to execution. The platform understands engineering content—including drawings, standards, catalogs, and specifications—and performs the work associated with it: checking, structuring, searching, and generating outputs. Armeta was founded in 2025 by engineers with decades of experience delivering major industrial projects. Today, the company has a team of around fifty people across the United States, Kazakhstan, and Qatar. ## Founders and leadership - Sanzhar Rakhmetzhanov — Co-Founder & Chairman of the Board - Temirlan Rakhmetzhanov — Co-Founder & CEO - Nuraly Baktygaliyev — Co-Founder & CTO - Ravi Belani — Investor & Board Observer - Daniel Jacker — Investor & Partner - Derek Toffer — Investor & Partner ## World-Class R&D ICPC finalists, IMO winners, and PhD researchers building production-grade systems. More than 50 people united by a shared vision. ## Technology Armeta combines proprietary machine learning models, computer vision, document intelligence, spatial reasoning, and domain-specific validation logic within a unified production system. Every AI-generated result is delivered through a purpose-built engineer review environment. The platform can operate as cloud-native SaaS or be deployed fully on-premises and air-gapped. ## Contact - hello@armeta.ai - San Francisco — Headquarters - Astana — Research & Development - Doha — Middle East hub CTA: Book a demo --- # About Armeta — The Engineering Intelligence Layer for Industrial Facilities Source: https://armeta.ai/company/about/ About # Armeta builds the engineering intelligence layer for industrial facilities. Every industrial facility in operation today — every refinery, chemical plant, LNG terminal, power station, pharmaceutical plant, pipeline, and offshore platform — runs on a set of critical engineering documents: P&IDs, piping isometrics, PFDs, and line lists. They are the master record of the facility. Every pipe, valve, instrument, safety device, and spatial routing appears across them. Every workflow that keeps the facility running safely, compliantly, and profitably depends on reading them. And in the vast majority of the global installed base, those documents exist only as legacy PDFs and spreadsheets. Armeta was founded in 2025 to close this gap. Our contextualization engine reads engineering documents — drawings and data tables alike, scanned or native, historical or as-built — and produces a unified, queryable engineering knowledge graph. The archive that every industrial facility has accumulated over decades becomes a structured, auditable resource for MTO, MOC, PHA revalidation, LDAR compliance, and every downstream workflow that depends on understanding what's in the documents. The company's founding insight is simple but consequential: decades of CAD software and document tooling have been built to create these engineering documents, and none of it can read the archive that every operating facility already has. The tools that companies like Hexagon, AVEVA, Bentley, and Autodesk have built are authoring tools. Armeta is the contextualization layer that sits between the legacy archive and every modern digital workflow. ## Who we build for Armeta serves every role across the industrial value chain that depends on critical engineering documents — drawings and data tables alike. Operators managing compliance and turnarounds, EPC contractors bidding and delivering projects, engineering firms handling brownfield revamps, EHS consultants producing audit-defensible compliance evidence, and OEMs structuring their installed-base archives. - 01 — Operators — managing compliance and turnarounds — Explore - 02 — EPC contractors — bidding and delivering projects — Explore - 03 — Engineering firms — handling brownfield revamps — Explore - 04 — EHS consultants — producing audit-defensible compliance evidence — Explore - 05 — OEMs — structuring their installed-base archives — Explore ## Where we are ### San Francisco HEADQUARTERS Commercial operations, executive leadership, and go-to-market team. ### Astana RESEARCH AND DEVELOPMENT Extraction engine development, engineering services, and customer validation. ### Doha GCC REPRESENTATION Gulf-region customer relationships and strategic partnerships. ## How to reach us Most productive starting point: book a demo through the primary call-to-action on this site. For partner inquiries, press, careers, or general questions, use the Contact page (/company/contact/) or reach out directly to the relevant team. - Book a demo - Contact the team --- # Team — Built by Engineers for Engineers Source: https://armeta.ai/company/team/ Leadership # Built by Engineers for Engineers. A leadership team with global engineering pedigree and hands-on experience in the most demanding industrial environments. ### Temirlan Rakhmetzhanov CO-FOUNDER & CEO Industrial Engineering and Business Management at Constructor University (Germany). Three-plus years operating inside a family-owned group of engineering companies, with hands-on exposure to industrial project execution and plant operations before founding Armeta. LinkedIn ### Nuraly Baktygaliyev CO-FOUNDER & CTO First-class honours in Computer Science from the University of the West of England. Leads Armeta's software architecture, AI/ML development, and the scalable document-processing systems behind the extraction engine. LinkedIn ### Sanzhar Rakhmetzhanov CO-FOUNDER & CEIO Studied at MIT, Stanford, and KTU. Twenty-five years in industrial technology with six successful exits, including building and scaling an industrial engineering business to $200M in annual revenue. Built joint ventures with Technip Energies and Maire Tecnimont in the EPC space. LinkedIn ### Francesco Giocolano CHIEF INDUSTRY OFFICER Former technical executive at Eni and Saipem. Twenty-plus years leading large-scale engineering and EPC projects across Europe, the Middle East, India, and Central Asia. PMP® certified. LinkedIn ### Ravi Belani INVESTOR AND BOARD OBSERVER Founder and CEO of Alchemist Accelerator. Lecturer and Board Advisor at Stanford Engineering's Center for Entrepreneurship. Early-stage investor in Twitch, Rigetti, LaunchDarkly, PubMatic, Onebrief, MoEngage, and Litmus. LinkedIn ## Research & Development # World-Class R&D. ICPC Finalists, IMO Winners, and PhD researchers building production-grade systems. ### Adil Aldosh HEAD OF R&D MSc in Data Science. Leads all machine learning initiatives across the platform, including the core extraction models and the training pipelines behind the proprietary P&ID dataset. ### Raiymbek Akshulakov ML ENGINEER UC Berkeley BSc and MSc. International Mathematical Olympiad winner. Leads computer vision research and model optimization for the P&ID extraction engine. ### Adi Abilgaziyev SOFTWARE ENGINEER Four-time ICPC World Finalist. Top 1% on LeetCode. Architects the high-performance backend systems that process millions of engineering drawings through the extraction pipeline. - 7 — BACKEND ENGINEERS - 6 — ML ENGINEERS - 3 — FRONTEND ENGINEERS - 1 — DEVOPS --- # Careers at Armeta — Build the Engineering Intelligence Layer for Industrial Facilities Source: https://armeta.ai/company/careers/ Careers # Build the infrastructure that every industrial facility will run on. Armeta is a small, focused team building the contextualization layer that structures every critical engineering document industrial facilities depend on — drawings and data tables alike. The work is technical, consequential, and domain-rich. We hire people who can combine strong engineering with real curiosity about how industrial facilities actually work. ## Open roles NO OPEN ROLES No open roles at this moment. If your background is a strong fit for Armeta and you'd like to be considered for future openings, contact us through the Contact page (/company/contact/). ## Who thrives at Armeta - 01 — Engineers who want depth in a specific, valuable domain rather than generic AI work - 02 — People with industrial experience who want to apply that experience to building tools, not consulting services - 03 — Founders and senior contributors who want to own significant scope early in a company's growth - 04 — People who care about shipping real products to real industrial customers, not about working on speculative research ## How we hire A brief, honest description of the hiring process. - 01 — First conversation — 30 minutes, usually with a founder. About your background, about Armeta, about whether there's a real fit. - 02 — Technical depth — One or two working sessions relevant to the role. We don't do leetcode. We do the actual kind of work the role requires. - 03 — Team meetings — Conversations with people you'd work with day-to-day. - 04 — Offer — We make decisions fast. If we're moving forward, you'll know within a week of the final round. --- # Contact Armeta Source: https://armeta.ai/company/contact/ Contact # Get in touch. - Book a demo ## Other inquiry channels CONTACT hello@armeta.ai ## Where we work - San Francisco — Headquarters - Astana — Research & Development - Doha — Middle East hub --- # Frequently Asked Questions — Armeta Source: https://armeta.ai/faq/ Support # Frequently Asked Questions Everything you need to know about Armeta and our P&ID Intelligence platform for procurement, compliance, and asset integrity. ## General **Q: What is Armeta?** A: Armeta is the AI-powered Engineering Intelligence Layer for industrial facilities. We transform static PDF P&IDs into structured, queryable engineering intelligence — deployable across every downstream workflow that depends on it, including procurement, EHS compliance, and asset integrity. **Q: Who is Armeta built for?** A: Armeta is purpose-built for EPC firms, owner-operators, EHS consultants, and inspection & integrity consultants in the oil & gas and chemical industries — anyone who depends on P&ID data for procurement, compliance, or asset integrity workflows. **Q: What types of drawings does Armeta support?** A: Armeta processes PDFs, scanned images, and legacy CAD exports of Piping and Instrumentation Diagrams (P&IDs). Our AI has been trained on thousands of proprietary, real-world engineering drawings — not public internet data. ## Product — Engineering & Procurement **Q: How does Armeta handle engineering & procurement workflows?** A: You upload your P&IDs to the platform. Our AI extracts every component — equipment, lines, instruments, tags, and spatial relationships — and structures them into procurement-ready output. Your engineer validates the results through our human-in-the-loop interface, and you export structured, audit-ready Material Take-Offs. **Q: How fast is it compared to manual extraction?** A: Armeta reduces per-sheet processing from 8–24 hours to under 30 minutes. A 300-P&ID project that would typically require weeks of manual work can be completed in a fraction of the time. **Q: What accuracy does Armeta achieve?** A: Armeta achieves 99% precision through its human-in-the-loop validation workflow. The AI performs the heavy lifting of extraction and classification, while your engineers review and confirm — combining machine speed with human judgment. **Q: Does it integrate with existing procurement systems?** A: Yes. Armeta delivers structured output in Excel, JSON, or via API — compatible with major ERP and procurement systems. The output slots directly into your existing workflows without manual reformatting. ## Product — EHS Compliance **Q: How does Armeta support EHS compliance?** A: From the same P&ID extraction, Armeta auto-identifies every regulated component and generates EPA & OSHA regulatory inventories — including BWON/NESHAP, LDAR, and emissions reports. No separate manual review required. **Q: How does it help avoid EPA fines?** A: EPA violations for non-compliance can cost up to $70,000 per day. Armeta automates the identification of every regulated component in your P&IDs — a process that is otherwise fully manual every audit cycle. By eliminating human errors in component identification, Armeta removes the root cause of most compliance violations. **Q: How long does a compliance audit take with Armeta?** A: Audits that traditionally take 2–4 weeks of engineering time can be completed in days, with full traceability and audit-ready documentation generated automatically from the structured P&ID data. ## Product — Asset Integrity **Q: How does Armeta support asset integrity?** A: Armeta extracts and structures the data needed for asset registers and corrosion circuit mapping directly from P&IDs. This feeds risk-based inspection programs and eliminates the manual process that often leads to gaps, missed inspections, and unplanned shutdowns. **Q: What are the risks of not having structured P&ID data for integrity?** A: When asset registers and corrosion circuit maps are built by hand, gaps are inevitable. Those gaps lead to missed inspections and unplanned shutdowns — costing millions per event. Armeta eliminates this risk by structuring the data directly from the source drawings. **Q: Who uses the asset integrity output?** A: Inspection & integrity consultants and owner-operators use Armeta's structured output to build and maintain accurate asset registers, define corrosion circuits, and feed risk-based inspection programs — all from the same P&ID extraction. ## Closing CTA Still have questions? Book a demo and our team will walk you through everything. Book a Demo --- # Security — Armeta Source: https://armeta.ai/security/ Security # Security. - Contact security team - Book a demo ## Security overview Armeta processes proprietary engineering drawings — P&IDs, plot plans, and related as-built documentation — for operators, EPCs, and engineering firms. That data is sensitive by nature: it describes the facility, the equipment, and often the safety envelope. Our security program is designed around that reality. Every commitment on this page is verifiable. Customers and prospects evaluating Armeta can request current documentation, subprocessor lists, and architecture summaries from the security team under NDA. - 01 — Certifications and audits — SOC 2 Type I certified; Type II audit in progress (H1 2026). Data residency in US, EU, or customer-designated regions. Enterprise SSO, role-based access, full audit logs, and end-to-end encryption. - 02 — Data protection — TLS 1.3 for all data in transit. AES-256 for all data at rest. Cryptographic material is managed by a dedicated key management service with rotation enforced on a fixed schedule. - 03 — Access controls — Single sign-on via SAML 2.0 and OIDC. Role-based access control aligned to customer directory groups. Full audit logs for authentication, authorization, and data access events, exportable to customer SIEM. - 04 — Data residency — US, EU, and customer-designated regions supported. Customer engineering data is stored in the region selected at onboarding and is not replicated across regions without explicit authorization. - 05 — Deployment options — Multi-tenant cloud, dedicated single-tenant cloud, and on-premise or customer-managed private cloud. Air-gapped deployments are supported for engagements that require them. - 06 — Incident response — 24x7 on-call rotation. Documented severity classification, communication SLAs, and post-incident review process. Customer-impacting incidents are reported in line with the terms of the engagement. ## Customer data handling Specific customer data handling terms — including access, retention, deletion, and regional constraints — are defined in each customer's master services agreement and data processing addendum. The defaults documented here are the minimum; individual engagements can tighten them but not relax them. For audit-facing customers, Armeta supports read-only auditor access to extraction outputs, traceability records, and provenance metadata as part of the engagement scope. ## Security contact For questionnaires, vulnerability reports, or a copy of the current security overview, write to security@armeta.ai. Responses within one business day. ## FAQ ### How is customer data segregated? Logical segregation at every layer — storage, compute, and processing — keyed to the customer tenant. Single-tenant and on-premise deployments provide physical segregation in addition to logical controls. ### What happens to customer data after an engagement ends? Retention, deletion, and return-of-data are governed by the terms of the engagement. The default posture is that customer data is deleted on request and on contract termination, subject to documented legal-hold requirements. ### Can we review Armeta's security documentation? Security questionnaires, architecture summaries, and subprocessor lists are available to qualified customers and prospects under NDA. Contact security@armeta.ai to request access. ### How do we report a vulnerability? Write to security@armeta.ai with as much detail as you can share. We acknowledge vulnerability reports within one business day and coordinate disclosure in good faith. --- # Privacy Policy — Armeta Source: https://armeta.ai/privacy/ Back to home Legal · Privacy Policy # Privacy Policy. This Privacy Policy explains how Armeta collects, uses, shares, and protects your personal data when you use our platform. By accessing or using our website and services, you consent to the practices described below. Last updated · January 25, 2026 ## 01 · Who We Are Armeta is an AI-powered platform for engineers operated by Armeta Inc. We are committed to protecting your personal data and complying with applicable privacy regulations, including the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and other relevant data protection laws. ## 02 · Information We Collect We collect the following categories of personal data: - Account information: Name, email, password (hashed), and organization (if provided) - Usage data: IP address, browser type, device information, time zone, and interaction logs - Payment data: Billing details (processed securely via third-party payment providers) - Communication: Messages, feedback, and support queries We do not knowingly collect personal data from individuals under 16. ## 03 · How We Use Your Data We use your information to: - Provide access to our platform and services - Process payments and manage subscriptions - Analyze usage for performance and improvement - Communicate updates, respond to inquiries, and offer support - Ensure platform security and prevent abuse We do not sell your personal information to third parties. ## 04 · Legal Basis for Processing If you are located in the European Economic Area (EEA), we process your data under the following legal bases: - Your consent - Performance of a contract - Compliance with legal obligations - Legitimate interests (e.g., improving our services) If you're a U.S. resident, we process your personal data in accordance with: - California Consumer Privacy Act (CCPA) - Other applicable U.S. federal and state laws You have the right to access, correct, delete, and limit use of your data, and to opt out of sale. ## 05 · Sharing of Data We may share your personal data with: - Service providers (e.g., hosting, payment processing, analytics) - Legal authorities, if required by law or in response to legal requests - Third parties in connection with a merger, acquisition, or business restructuring All third-party processors are contractually bound to protect your data. ## 06 · Data Retention We retain personal data only for as long as necessary for the purposes outlined above or as required by law. You can request deletion of your data at any time by contacting us. ## 07 · Your Rights - Access your personal data - Correct inaccurate data - Request data deletion ("right to be forgotten") - Object to or restrict processing - Request data portability - Withdraw consent (where applicable) To exercise your rights, contact us at hello@armeta.ai. ## 08 · Cookies and Tracking Technologies We use cookies and similar technologies to improve site functionality and user experience. You can manage cookie preferences through your browser settings. ## 09 · Data Security We use industry-standard security measures to protect your data, including encryption, access controls, and secure server infrastructure. However, no system is completely secure, and we cannot guarantee absolute protection. ## 10 · International Transfers Your data may be transferred to and processed in countries outside your own, including the United States. Where required, we use Standard Contractual Clauses or other legal mechanisms to protect international transfers. ## 11 · Changes to This Policy We may update this Privacy Policy periodically. We will notify you of significant changes via email or platform notice. The "Last Updated" date reflects the most recent revision. ## 12 · Contact Information For questions or privacy-related requests, please contact: Armeta Inc. 108 West 13th Street Wilmington, DE 19801, USA Email: hello@armeta.ai --- # Terms of Use — Armeta Source: https://armeta.ai/terms/ Back to home Legal · Terms of Use # Terms of Use. Welcome to Armeta, an AI-driven platform for engineers. These Terms of Use govern your access to and use of the armeta.ai website and services. By accessing or using our platform, you agree to these Terms. Last updated · January 25, 2026 ## 01 · Who We Are Armeta is operated by Armeta Inc., a company based in the United States. Armeta Inc. 108 West 13th Street Wilmington, Delaware 19801, USA Email: hello@armeta.ai ## 02 · Use of Our Services You agree to: - Use the service only for legal, professional, and authorized purposes - Not interfere with, disrupt, or misuse the platform - Not share login credentials or access tokens without authorization We reserve the right to restrict or terminate your account if these terms are violated. ## 03 · User Accounts To access some features, you must register for an account. You are responsible for: - Keeping your credentials secure - All activities under your account You agree to notify us immediately of any unauthorized use. ## 04 · Intellectual Property All content, software, models, and tools on Armeta are owned by Armeta Inc. or its partners. You may not copy, modify, distribute, or reverse engineer any part of our platform unless explicitly permitted. ## 05 · Paid Services If you purchase a subscription or pay for specific services, you agree to: - Provide accurate billing info - Authorize us (or our processor) to charge your payment method - Abide by the refund and cancellation terms (provided separately) ## 06 · Data Privacy Our data collection and usage are governed by our Privacy Policy, compliant with: - General Data Protection Regulation (EU GDPR) - California Consumer Privacy Act (CCPA) - Other applicable local, state, and international laws ## 07 · Limitation of Liability To the fullest extent permitted by law: - We do not guarantee that the platform will always be error-free or uninterrupted. - Armeta is not liable for indirect, incidental, or consequential damages arising from your use or inability to use the platform. Some jurisdictions do not allow limitation of liability, so this clause may not apply in full to you. ## 08 · Disclaimers All content and services are provided "as is" without warranties of any kind. We do not guarantee that: - Results from simulations or AI models are accurate or appropriate for real-world engineering decisions. - The platform will meet your specific expectations. We encourage professional oversight before acting on any automated output. ## 09 · Termination We reserve the right to terminate or suspend access at any time for violation of these Terms or applicable laws. ## 10 · Changes to the Terms We may revise these Terms at any time. When we do, we'll update the "Last Updated" date and notify users as appropriate. Continued use implies agreement to the latest Terms. ## 11 · Governing Law These Terms are governed by the laws of the State of California, USA, without regard to conflict of law principles. ## 12 · Contact Us For any questions regarding these Terms, contact: Armeta Inc. 108 West 13th Street Wilmington, Delaware 19801, USA Email: hello@armeta.ai --- # Sitemap — Every page on Armeta Source: https://armeta.ai/sitemap/ Sitemap # Every page on Armeta. A flat index of every indexable URL on armeta.ai. The XML version is at /sitemap.xml. Retrieval bots can read /llms.txt for an LLM-friendly view. Section index: - Primary (3) - Platform — Document types (4) - Solutions (7) - Glossary (17) - Regulations (8) - Workflows (8) - Comparisons (6) - Integrations (6) - Blog (7) - Company (4) - Talk with Armeta (2) - Legal (4) - FAQ (1) ## Primary Top-level marketing surface. - Homepage — / - Platform — /platform/ - Proof — /proof/ ## Platform — Document types Per-document-type detail pages on what Armeta extracts, contextualizes, and delivers. - Platform — P&IDs — /platform/pids/ - Platform — Piping Isometrics — /platform/piping-isometrics/ - Platform — PFDs — /platform/pfds/ - Platform — Line Lists — /platform/line-lists/ ## Clients Businesses and governments Armeta serves. - Clients — /solutions/ - For Engineering Firms — /solutions/engineering-firms/ - For Construction Firms — /solutions/construction-firms/ - For Asset Owners — /solutions/asset-owners/ - For Governments and Regulators — /solutions/governments-regulators/ ## Glossary Plain-English definitions for industrial-engineering terms. - Glossary — /resources/glossary/ - PHA — Process Hazard Analysis — /resources/glossary/pha-process-hazard-analysis/ - HAZOP — Hazard and Operability Study — /resources/glossary/hazop-hazard-and-operability/ - MOC — Management of Change — /resources/glossary/moc-management-of-change/ - PSI — Process Safety Information — /resources/glossary/psi-process-safety-information/ - LDAR — Leak Detection and Repair — /resources/glossary/ldar-leak-detection-and-repair/ - MTO — Material Take-Off — /resources/glossary/mto-material-takeoff/ - P&ID — Piping & Instrumentation Diagram — /resources/glossary/pid-piping-and-instrumentation-diagram/ - FEED — Front-End Engineering Design — /resources/glossary/feed-front-end-engineering-design/ - EPC — Engineering, Procurement, Construction — /resources/glossary/epc-engineering-procurement-construction/ - Turnaround — /resources/glossary/turnaround/ - Piping Isometric Drawing — /resources/glossary/piping-isometric-drawing/ - PFD — Process Flow Diagram — /resources/glossary/pfd-process-flow-diagram/ - Line List — /resources/glossary/line-list/ - BOM — Bill of Materials — /resources/glossary/bom-bill-of-materials/ - Pipe Specification — /resources/glossary/pipe-specification/ - From-To List — /resources/glossary/from-to-list/ ## Regulations U.S. EPA and OSHA regulations covered by Armeta workflows. - Regulations — /resources/regulations/ - OSHA PSM — 29 CFR 1910.119 — /resources/regulations/osha-psm-1910-119/ - EPA RMP — 40 CFR Part 68 — /resources/regulations/epa-rmp-40-cfr-68/ - EPA LDAR Best Practices — /resources/regulations/epa-ldar-best-practices/ - EPA Method 21 — /resources/regulations/epa-method-21/ - NSPS — 40 CFR Part 60 — /resources/regulations/nsps-40-cfr-60/ - NESHAP — 40 CFR Part 61 — /resources/regulations/neshap-40-cfr-61/ - MACT — 40 CFR Part 63 — /resources/regulations/mact-40-cfr-63/ ## Workflows Repeatable engineering processes Armeta accelerates. - Workflows — /resources/workflows/ - Automated MTO Extraction — /resources/workflows/automated-mto-extraction/ - MOC Reconciliation — /resources/workflows/moc-reconciliation/ - PHA Revalidation Support — /resources/workflows/pha-revalidation-support/ - LDAR Component Inventory — /resources/workflows/ldar-component-inventory/ - Brownfield Data Migration — /resources/workflows/brownfield-data-migration/ - As-Built Reconciliation — /resources/workflows/as-built-reconciliation/ - Turnaround Preparation — /resources/workflows/turnaround-preparation/ ## Comparisons How Armeta differs from adjacent approaches. - Comparisons — /resources/comparisons/ - Armeta vs. manual extraction — /resources/comparisons/armeta-vs-manual-extraction/ - Armeta vs. generic OCR — /resources/comparisons/armeta-vs-generic-ocr/ - Armeta and Hexagon Smart P&ID — /resources/comparisons/armeta-and-hexagon-smart-pid/ - Armeta and AVEVA P&ID — /resources/comparisons/armeta-and-aveva-pid/ - Armeta and Bentley OpenPlant — /resources/comparisons/armeta-and-bentley-openplant/ ## Integrations Where Armeta data flows downstream. - Integrations — /resources/integrations/ - SAP integration — /resources/integrations/sap-integration/ - IBM Maximo integration — /resources/integrations/ibm-maximo-integration/ - AVEVA PI System integration — /resources/integrations/aveva-pi-system-integration/ - Cognite Data Fusion integration — /resources/integrations/cognite-data-fusion-integration/ - Sphera PHA-Pro integration — /resources/integrations/sphera-pha-pro-integration/ ## Blog Field notes from operators and engineers. - Blog — /resources/blog/ ## Company Company overview and supporting pages. - Company — /company/ - About Armeta — /company/about/ - Team — /company/team/ - Careers — /company/careers/ - Contact — /company/contact/ ## Talk with Armeta Conversion entry points. - Demo — /demo/ ## Legal Security posture, privacy, and terms of use. - Security posture — /security/ - Privacy — /privacy/ - Terms — /terms/ - Sitemap — /sitemap/ ## FAQ Common questions and short answers. - Frequently Asked Questions — /faq/ ---