Planner-owned automation · synthetic aerospace data

Design the report with Copilot. Run it with controlled automation.

A synthetic proof of concept showing how a report architect can use Copilot to draft mapping and Power Query logic, then hand approved rules to PAD, scripts, and Excel for deterministic execution.

Run the Copilot design session Transform the sample workbook

PLANNING OWNS NOWBusiness rules · acceptance · output shape

IT PARTNERS LATERCredentials · gateway · scale · governance

FOUNDATION-FIRST AUTOMATION CHAINCLOUD LAST

01
Architect constrainsSource grain, template, rules, owners, and acceptance totals
HUMAN
02
Copilot draftsField mapping, Power Query M, questions, and test cases
ASSIST
03
PAD retrievesSynthetic SyteLine-style ERP export through the existing UI
EDGE
04
Script hands off safelyFinal name, schema, hash, run ID, and work-folder boundary
CONTROL
05
Power Query transformsApproved, reviewable report-specific logic inside Excel
QUERY
06
Owner verifiesCounts, known examples, audit, archive, and release decision
APPROVE

THE OPERATING IDEA

Copilot shortens the design loop; it does not become the source of truth. The report owner approves the contract, and deterministic tools execute only that approved version.

One engine · three proofs

What the demo shows

Open scenario workbench →

Dataset → Report A

Convert 1,800 ERP-style rows into a formatted 30-line planner exception queue.

Filter · calculate · prioritize · reconcile

Report A → Report B

Remove columns, rename fields, derive urgency and ownership, and apply a new delivery layout.

16 columns → 10 columns

Report A → Summary

Aggregate exceptions into a site-by-status matrix, with an Office Script path for a native PivotTable.

30 actions → 6 site rows

TOOL 01 / RETRIEVE

ERP report terminal

A fictional SyteLine-style console shows the scheduled export edge that Power Automate Desktop can handle while a logged-in machine is available.

Run the simulated export

TOOL 02 / TAILOR

Self-service transformer

Select a scenario, load the matching template, source, and readable rule file, then receive a controlled workbook without Python.

Test all three scenarios

Reproducible evidence

Download the example artifacts

Kaggle source · MIT license ↗

01Synthetic ERP export1,800 site-part rows · CSV↓02Report A pairBlank template and expected filled workbook↓03Report B pairBlank action register and expected filled workbook↓04Pivot-style pairBlank summary and expected filled workbook↓05Native PivotTable scriptMicrosoft Office Script reference↓

ESCALATION BOUNDARY

Planning can own report logic and routine revisions. Escalate when the ERP schema changes, credentials or a gateway are required, regulated data enters scope, an approval decision is automated, or the workflow becomes a production service.