Live in production · Part of the ArcSuite

ArcV2_CC — BOM Report Tagger

The command center of the ArcSuite. Eleven tabs that turn a raw SSRS BOM dump into classified, tagged, work-ordered, planned, printed, and shipped material — live.

Role
Architect & sole developer
Stack
.NET 8 · C# · WPF · SQLite
Domain
BOM classification & work orders
Status
Live on the shop network
ArcV2_CC BOM Report Tagger showing the work-order grid beside a live work-order PDF in the split pane
The split-pane work view: the work-order grid on the left, the work-order PDF open on the right — drill-through without leaving the app.
11 tabs in one window
Auto BOM classification by rule
1 shared database with the suite

What it does

In JDE, a BOM arrives as a flat SSRS report — hundreds of lines of raw material with no context: which lines need drawings, which machine cuts them, what's done, what's next. ArcV2_CC downloads that report on a schedule, classifies every line against user-defined rules, and turns it into a live, queryable work surface that the rest of the ArcSuite reads from.

It is the write-side of the suite: OpsTool and the Digital Cubby report floor progress into it, and CC turns that into planning, printing, and shipping decisions.

The eleven tabs

TabWhat it does
WorkOrdersOne row per work order with live status rollups, drill-through to the work-order PDF in the split pane, and cross-filtering between the summary and the grids.
BOMThe classified BOM itself — every line tagged by the rule engine, with raw-material totals and line-status breakdowns.
Rules & ClassifiersUser-defined, multi-condition tagging rules. Change how lines classify without recompiling anything.
PlannerA ranked cut list scored by qty released − 25 × dependencies, with a dependency sprawl graph.
Print QueueWhat to print next, ready/not-ready gating, and per-work-order print and re-print counts.
MRP ReportScheduled SSRS pulls for the MRP parts report, with cross-instance de-duplication.
Omni ReportThe OmniWin parts feed — same scheduled-pull and de-dup pipeline.
NestPlansDragon, Omni, and HGG nest-plan intake, bucketed by machine and matched back to BOM lines.
Job BOMsPer-job BOM workbooks assembled from the classified lines.
Struct BucketStructural material held aside until its dependencies clear.
ShippingDrill-down over shipped workbooks, from work order down to packing-list lines.

How it fits the suite

CC never talks to the other apps directly. It commits to the shared arcv2.db on the network share and polls PRAGMA data_version every 30 seconds, so floor progress written by OpsTool appears in CC's grids within a minute — no IPC, no sockets, no message bus. The WoLineKey (work order minus the .0, plus the BOM line number) is the join key that ties everything together.

Anything CC prints goes through ArcV2_Print: watermarking, mandatory print confirmation, re-print reasons, and the shared print_events audit log.

Screenshots

The tabs

ArcV2_CC main window
The main window — eleven tabs, with the raw-material and line-status summaries pinned above the grid.
ArcV2_CC full work-order grid with raw-material and line-status summary panels
Full grid view with the raw-material and line-status summaries visible on every tab.
ArcV2_CC WorkOrders tab
WorkOrders — one row per work order with live status rollups.
ArcV2_CC BOM tab with classified lines
BOM — every line tagged by the rule engine, with raw-material totals.
ArcV2_CC Planner tab with ranked cut list
Planner — the ranked cut list with dependency scoring.
ArcV2_CC Print Queue tab
Print Queue — ready/not-ready gating with per-work-order print counts.
ArcV2_CC MRP Report tab
MRP Report — scheduled SSRS pulls with cross-instance de-duplication.
ArcV2_CC Omni Report tab
Omni Report — the OmniWin parts feed on the same scheduled-pull pipeline.
ArcV2_CC NestPlans tab
NestPlans — Dragon, Omni, and HGG nest-plan intake bucketed by machine.
ArcV2_CC Job BOMs tab
Job BOMs — per-job workbooks assembled from the classified lines.
ArcV2_CC Struct Bucket tab
Struct Bucket — structural material held aside until its dependencies clear.
ArcV2_CC Shipping tab
Shipping — drill-down from work order to packing-list lines.

The rule engine

ArcV2_CC rules list
The rules list — every classification rule in the database, editable without a rebuild.
ArcV2_CC rule editor dialog
The rule editor — name, priority, and target classifier for a rule.
ArcV2_CC rule conditions editor
Rule conditions — multi-condition matching against BOM line fields.
ArcV2_CC classifiers list
Classifiers — the targets rules assign lines to.

Statuses, roles & column settings

ArcV2_CC statuses configuration
Statuses — the work-order status vocabulary, configured rather than hard-coded.
ArcV2_CC roles configuration
Roles — who can do what, managed alongside the data.
ArcV2_CC column settings dialog
Column settings — pick which columns each grid shows, per user.
ArcV2_CC settings window
Settings — schedules, paths, and SSRS configuration in one window.

Popups & context actions

ArcV2_CC work-order detail popup
Work-order detail — double-click a line to open the full record.
ArcV2_CC work-order assignment dialog
Work-order assignment — assign a line without leaving the grid.
ArcV2_CC grid context menu
The grid context menu — the action buttons behind a right-click.

Engineering notes

  • Startup performance. A sequenced startup chain with deferred tab loads took the window from roughly 95 seconds to about 13 seconds to a ready grid — on the same hardware and the same data.
  • Rule engine. Classification is data, not code — multi-condition rules live in the database, so the shop re-tags lines without a rebuild.
  • Report pipeline. PowerShell 7 embedded for the SSRS BOM download, SHA-256 verified; HttpClient + Atom feeds for the scheduled report pulls.
  • Deployment. ClickOnce, so the shop updates itself from the network share.

Origin

CC descends from the ArcV2_System command center — the .NET-over-Avalonia prototype that established the JDE overlay pattern and the rule engine, carried forward into the production WPF suite.

Related projects