Skip to content
Technical design note

Survey workflow architecture

An architectural overview of scope, procedures, readiness, event records, reporting and deliverables.

SurveyIQ technical note

Technical design notes. Confirm supported product behaviour, configuration and project suitability through technical evaluation.

Abstract

A survey campaign involves several related records: contracted scope, procedures, work packages, observations, operational events, reports and deliverables. Their relationships matter when a technical reviewer needs to establish which information supported a particular decision.

Technical field. System architecture

Design considerations

  • Scope and procedure revisions establish the planned work. Execution records need to identify the revision that applied.
  • An observation, an interpretation and an approval serve different purposes. Their authorship and review responsibilities need to remain distinguishable.
  • Connections between workspaces require explicit identifiers, reference systems and revision handling. A common interface alone does not establish traceability.

Questions for technical evaluation

  • Which records and relationships are supported in the proposed configuration?
  • Can a reviewer follow a selected result or deliverable back to the relevant source records?
  • How are corrections, superseded records and incomplete information represented?

Scope of this note

This note describes workflow design and evaluation considerations. Supported behaviour, interfaces, controls and limitations need to be demonstrated for the proposed product configuration and intended project.

About this note

SurveyIQ technical note: Survey workflow architecture. This editorial edition focuses on architecture and evaluation considerations. Product qualification depends on the intended use and demonstrated configuration.

Evaluate the relevant workflow.

Discuss the data, engineering methods and outputs your project needs.

Request a technical demonstration