Flowline logoFlowline
Open navigation
HomeDemoDocsUpdatesAboutRequest Access
Docs

Flowline product docs

A lightweight guide to how Flowline turns project packages into extracted design elements, review flags, schedules, and draft engineering outputs.

Getting Started

  1. 1Upload or connect a representative project package.
  2. 2Select a workflow such as drainage schedule extraction or SWM review.
  3. 3Review extracted design elements and plan references.
  4. 4Resolve flags for missing fields, uncertain mappings, and profile checks.
  5. 5Export a draft schedule, quantity table, or review memo.

Supported Inputs

  1. 1DGN model and reference files from MicroStation or Bentley-centered workflows.
  2. 2Plan PDFs with sheets, profiles, labels, schedules, and standard details.
  3. 3Shapefiles and GIS layers for topo, contours, land use, utilities, or constraints.
  4. 4Stormwater reports and technical narratives.
  5. 5Agency standards, specifications, design criteria, and pay item references.

Demo Walkthrough

  1. 1Inventory a compact drainage plan package.
  2. 2Group plan, model, sheet, and GIS/topo inputs.
  3. 3Generate a derived storm drain schedule for engineer review.
  4. 4Attach confidence and review flags to each extracted row.
  5. 5Summarize what must be checked before formal deliverable use.

Architecture

  1. 1Project package ingestion identifies files, references, and likely discipline context.
  2. 2CAD/GIS/document extraction converts raw artifacts into candidate engineering objects.
  3. 3An engineering object model tracks structures, pipes, labels, quantities, references, and assumptions.
  4. 4Standards/spec reasoning maps objects to pay items, measurement rules, and review checks.
  5. 5Engineer-reviewable outputs expose sources, confidence, flags, and draft exports.
Principles

Designed for review, not blind automation

The architecture keeps the engineer in the loop by preserving sources, confidence, assumptions, and review flags across every output.

Inputs stay traceable to project files and plan references.
Outputs remain draft until reviewed by a qualified engineer.
Future parsing can plug into the same object model and UI surfaces.

Open the MVP walkthrough

The demo shows how the first project-package workflow will feel to reviewers and design partners.

View Demo