Field-to-plan intelligence

SIH 2026 / SIH26122
Problem-statement stakeholderOil India Limited

Field intelligence.
Planning confidence.

SETU links site progress reports to Primavera P6 schedule activities. It explains each suggestion, flags conflicts and keeps the human planner in control.

No credentials needed · 3-minute public demo · Synthetic examples

Drilling rig and field infrastructure in a green landscape, from Oil India’s official upstream imagery
01 / UPSTREAMThe field is where the story begins.
From the site. Into the schedule.Context is the connection.
One report. A visible connection.Illustrative mapping / UPD-2026-001
  1. 01 / FIELD REPORT

    “Spool erection and field fit-up finished at Manifold A.”

    Original context stays with the report.
  2. 02 / SUGGESTED ACTIVITY

    Piping spool erection
    and field fit-up

    OIL-PIP-202-A · WBS 1.2.2.1
  3. 03 / PLANNER REVIEW

    The evidence informs.
    The planner decides.

    Pending review. No baseline write.

The translation gap

The work happened.
The schedule needs context.

A site note says “spool fit-up finished.” A plan needs an activity, a location and evidence. SETU makes that connection visible so the planner can decide.

Two people compare an engineering component with its technical drawing
Field context meets planning detail. Illustrative engineering photograph.
01

How the field speaks

“Spool erection and field fit-up finished at Manifold A.”

  • Project terminology and abbreviated notes
  • Work location and reported date
  • Supporting evidence to examine
02

What the planner needs

Schedule activity
Piping spool erection and field fit-up
Context
Manifold A · Piping · WBS 1.2.2.1
Decision
Review the suggestion against evidence

An activity suggestion is a starting point. It does not change the baseline.

The SETU pipeline

Six stages.
One accountable decision.

Move from what happened on site to what belongs in the plan. Keep the evidence connected at every step.

Trace a sample report
  1. 01

    Capture

    Bring field notes and structured reports into one review flow.

  2. 02

    Understand

    Extract activity, date, location, quantity and evidence.

  3. 03

    Match

    Compare domain terms, semantic similarity and project context.

  4. 04

    Validate

    Surface timing, scope, duplicate and ambiguity checks.

  5. 05

    Review

    A planner accepts, rejects, clarifies or remaps the suggestion.

  6. 06

    Trace & reuse

    Keep approved mappings and corrections available for later review.

Approval is a planner action. Matching and validation support that decision.

A report, in context

Follow the evidence.
Understand the decision.

Explore SETU Demo: follow a Supervisor observation through interpretation, matching, validation, a sample planner decision and its audit trail. About 3 minutes; no sign-in.

Read-only simulation
SETU / Field-to-plan reviewSynthetic data · No baseline writes

01 / Original evidence

Keep the site context intact.

The report text, location and date remain visible throughout review. A suggestion connects that evidence to a candidate activity.

The example is precomputed synthetic data. This walkthrough does not process new reports.

Step 1 of 6

Planner control

Confidence is a signal.
You make the call.

SETU suggests and validates. The planner checks the evidence, resolves ambiguity and owns the decision.

The Primavera P6 baseline stays read-only.

01 / Review

Check before you accept.

Examine the report, suggested activity and validation findings together.

02 / Resolve

Correct the connection.

Reject, request clarification or select a better target when the evidence does not support a suggestion.

03 / Trace

Keep the reason with the result.

Approved mappings feed traceable records and export. The prototype does not silently write to P6.

Institutional memory

Keep the context.
Carry it forward.

Reviewed mappings and planner corrections provide reusable project context. Future suggestions still need validation and review.

Example terminologyPiping
Field termspool
Planning contextPiping spool erection
  1. Store the reviewed mappingKeep the selected activity and supporting context.
  2. Record the correctionRetain the planner’s decision and audit history.
  3. Reuse governed terminologyBring verified aliases into the next matching cycle.

Illustrative terminology, not a measured accuracy improvement.

A closer look

Follow the evidence.
See why it matters.

Inspect the connection between a site report and a planning activity. The interactive walkthrough is available even when a recording is not.

Trace a sample report →
PIPELINE TRACEABILITYInteractive Walkthrough

Inspect the sample workflow

Follow stored sample evidence and a simulated planner decision. This public walkthrough does not run the matching engine or contact the live application.

Launch Walkthrough →

Live Product Access

Experience SETU live.
Planner & Supervisor portals.

Connect to the live deployed prototype on Cloudflare Pages. Site supervisors capture progress and project planners govern Primavera P6 baselines.

Hosted live on Cloudflare Pages at setu-app.pages.dev. Sign-in and an assigned role are required. Public evaluators should use the demo above; credentials are not supplied.

01 / Interactive walkthrough

AVAILABLE HERE

Open the six-stage, no-login evaluator walkthrough: observation, interpretation, matching, validation, planner reasoning and audit. The example uses synthetic data.

Explore SETU Demo · No Login ↓

03 / GitHub repository

OPEN SOURCE

Inspect the complete codebase, matching algorithms, database migrations, and benchmark suites.

Explore repository ↗

Evidence, not promises

What is implemented today?

Prototype source reviewed at commit 120b5e7 · 23 October 2026. Repository implementation does not prove every feature is configured in the hosted app.

Public demo
Six static, reproducible stages; synthetic fixtures and sample audit. No engine or database connection.
Matching & validation
Implemented in hybrid matcher and six validation checks. Aliases, semantic and fuzzy similarity, discipline and location evidence are combined.
Human control & security
Repository includes authenticated Supervisor and Planner workflows, accept/reject/remap review and audit/export. Supabase Auth, role checks and RLS protect the real app. The public demo has no access to those records.
Hosted availability
Live prototype (sign-in required) ↗: public shell reachable; authenticated operations and backend health are not verified here.
Innovation
Connect field terminology to schedule context, expose competing candidates and validation evidence, and retain planner corrections as reviewable institutional memory.
Applicability & limits
Designed for oil and gas construction progress review against imported P6 schedules. Requires project-specific terminology, reliable observations and planner judgment. No live P6 write-back, OIL pilot, autonomous approval or production accuracy is claimed.

40 reports and 220 activities describe historical synthetic calibration fixtures, not active users, current production throughput or field accuracy. Inspect benchmark methodology →

Landing page source →

Built to be examined

A working prototype.
An open implementation.

Review the source, workflow boundaries and benchmark methodology. SETU is a prototype for plan–field integration, developed for SIH 2026, problem statement SIH26122.

Oil India Limited is the problem-statement stakeholder. This page does not claim an operational pilot or endorsement.

Interface
React · TypeScript · Vite · Tailwind CSS
Matching
Domain aliases · fuzzy matching · semantic similarity · location context
Governance
Validation · planner review · audit history · approved export
Offline benchmark scope

40synthetic reports

220schedule activities

Synthetic, self-labelled calibration data. These are not production or field-pilot results.

Explore the repository