# ERP SOW — Estimated Manual Time Baseline V2

**OMEGANEON ERP Document Operations · Case Study supporting model**

- **Method:** Bottom-up Time-Motion Decomposition (GOMS-inspired, task-level; not a keystroke-level GOMS study)
- **Classification:** Estimated Manual Baseline — NOT an observed industry average
- **Scenario:** One medium-complexity ERP SOW; an existing template; available discovery notes/transcripts and requirements matrix; project decisions and fees are already documented
- **Start:** Same materials available to manual and automated workflows
- **Finish:** Internally QA-checked draft ready for authorized human approval
- **Excluded:** Fresh client discovery, new negotiations, stakeholder approval waiting, signing, delivery, and later client changes

## Step-by-step manual estimates

| # | Distinct action | Low (min) | High (min) | Reason for estimate |
|---|---|---:|---:|---|
| 1 | Open materials and identify correct versions | 5 | 10 | Existing source package, no broad search |
| 2 | Read notes/requirements and extract project facts | 25 | 40 | Multiple sources and details must be reviewed |
| 3 | Map scope, deliverables, assumptions, exclusions | 15 | 30 | Distinct structuring step before drafting |
| 4 | Draft project-specific narrative in existing template | 35 | 55 | Document sections written from extracted facts |
| 5 | Populate milestones, fees, roles and schedule tables | 15 | 25 | Only table assembly; no duplicate QA |
| 6 | Cross-check amounts, dates, scope and requirements | 20 | 35 | One substantive validation pass |
| 7 | Format, proofread and save review-ready draft | 10 | 20 | Formatting/typos, not a second consistency review |
| **Total** | **Active manual work — estimated** | **125** | **215** | **2h 05m–3h 35m** |

## Transparent arithmetic

```text
LOW      =   5 + 25 + 15 + 35 + 15 + 20 + 10 = 125 min (2h 05m)
HIGH     =  10 + 40 + 30 + 55 + 25 + 35 + 20 = 215 min (3h 35m)
MIDPOINT = (125 + 215) / 2 = 170 min (2h 50m)
```

## Workflow visualization

```mermaid
flowchart LR
  A["Open materials 5–10m"] --> B["Extract facts 25–40m"]
  B --> C["Structure scope 15–30m"]
  C --> D["Draft narrative 35–55m"]
  D --> E["Populate tables 15–25m"]
  E --> F["Consistency QA 20–35m"]
  F --> G["Final format + proofread 10–20m"]
```

## Comparison with observed OMEGANEON sandbox benchmark

| Measure | Value | Evidence type |
|---|---|---|
| Manual active time to QA-checked draft | 125–215 minutes | Step-based estimate |
| Automated Draft + QA machine runtime | 2.5–4.5 minutes | User-measured sandbox runtime; excludes human approval |
| Deterministic QA rules | 14 active checks | User-reported implementation |
| First-pass validation | 17/20 (85%) | User-measured sandbox result |
| Missing-input exception routing | 3/20 (15%) | User-measured sandbox result |
| OpenRouter inference cost | $0.25–$0.65 per document | User-measured API costs |

**Interpretation:** Machine runtime is not the total client delivery cycle. Net human time saved is calculated as **manual active work minus actual post-automation human review/exception work**, which must be recorded separately. No industry-average or measured net labor-savings claim is made here.

## Scope notes

- These times assume a usable existing template and moderately organized sources. A largely prefilled SOW will require less work; a newly scoped complex deployment will require more.
- Step 2 extracts facts; step 3 structures commitments. Step 5 builds tables; step 6 checks them. Step 7 does visual proofreading, not another full QA. This avoids double counting.
- The seven step-duration intervals are analyst assumptions, not sourced time-and-motion measurements. SOW content sections follow established guidance on scope, deliverables, milestones, roles, acceptance criteria, and commercial terms.
- Revise these estimates after a matched, timed manual sample is available.

## SOW content references (not sources for estimated minutes)

- [Statement of Work for Dynamics 365 implementations](https://solvingdynamics365.com/guides/statement-of-work-for-dynamics-365/)
- [ERP implementation SOW content](https://www.n2iminds.com/knowledge/consulting/what-a-statement-of-work-contains/)
