FORMĚS
Skip to content
INSTechnical insights

Engineering knowledge for project and asset decisions.

FORMĚS Insights focuses on practical technical questions encountered by owners, operators, developers, consultants, contractors and procurement teams—not generic corporate news.

01How to use Insights

Start with the decision, not the service name.

Each guide is structured around a real technical decision: when to engage, what the client should prepare, what a credible methodology should contain, expected outputs, common gaps and the FORMĚS capabilities that may be relevant.

  • 01Decision question
  • 02When to engage
  • 03Client inputs to prepare
  • 04Methodology
  • 05Expected deliverables
  • 06Common technical gaps
  • 07Related services and next action
Technical guide library

Six practical guides for technical decision-making.

Each guide is structured to help frame the technical question, identify useful inputs, understand the methodology and anticipate the outputs and common gaps that matter to the decision.

01Technical guide
Asset condition / structural integrity

What Should a Structural Condition Assessment Include?

A useful condition assessment does more than record visible defects. It establishes the decision to be made, gathers proportionate evidence, distinguishes symptoms from credible causes and translates findings into prioritized technical action.

6 engagement signals7 methodology steps
02Technical guide
Engineering assurance / design governance

Design Review vs Independent Design Verification

“Design review” can mean anything from a coordination check to a formal independent verification. The appointment should define the required independence, acceptance basis, depth of recalculation and authority to close technical findings.

6 engagement signals7 methodology steps
03Technical guide
Industrial assets / continued performance

When Does an Existing Industrial Structure Require an Integrity Assessment?

Industrial structures operate under combinations of age, exposure, vibration, equipment change, maintenance history and production constraints. Integrity assessment becomes necessary when the reliability of the current structural basis is no longer proportionate to the decision being made.

6 engagement signals7 methodology steps
04Technical guide
Inspection / QA/QC evidence

What Should a Third-Party Inspection Report Contain?

A useful inspection report must allow another competent person to understand what was inspected, against what requirement, what objective evidence was observed, what was not verified and what action or release status resulted.

5 engagement signals7 methodology steps
05Technical guide
Construction quality / assurance

Common QA/QC Gaps During Construction

Many quality failures are not caused by the absence of procedures. They arise because acceptance criteria, inspection timing, document status, traceability and closure are not connected tightly enough to the work as it happens.

6 engagement signals7 methodology steps
06Technical guide
Digital engineering / technical records

Using BIM for As-Built Verification

An as-built model is only useful if there is a defined relationship between field condition, source evidence, model updates, verification status and the downstream decision the information must support.

6 engagement signals7 methodology steps
What a client should be able to answer

Before any technical assignment starts, six questions usually matter.

  1. 01

    What decision or problem must the work resolve?

  2. 02

    What information and evidence already exist?

  3. 03

    What is uncertain, disputed, inaccessible or time-critical?

  4. 04

    Which standards, specifications, contractual criteria or operational requirements apply?

  5. 05

    What output must exist for the next approval, release, intervention or investment decision?

  6. 06

    Who owns the next action and when does the decision need to be made?

02Technical standard

Useful enough to support a technical conversation.

FORMĚS Insights is structured to make the technical question clearer before an enquiry begins—connecting decision context, evidence, methodology, expected deliverables, limitations and next action.

  • 01Problem definition
  • 02Decision context
  • 03Evidence / client inputs
  • 04Methodology
  • 05Expected deliverables
  • 06Common failure points
  • 07Limitations and next action
Technical enquiry