Military Airfields / CES Work Orders
CES Work Orders
Civil Engineer work orders coordinated in the same picture the airfield runs on.
The problem
Civil Engineer doesn't need a second work-order system to check
A discrepancy assigned to a Civil Engineer shop still has to get worked, but if the shop tracks that work somewhere else entirely, the same problem now exists in two places, and the two can quietly disagree about what's actually been done.
And "fixed" isn't the same fact as "closed": a shop needs to know which of those it's actually holding for a given item, not guess from a status word that means something different depending on who's reading it.
How it works
The same discrepancy record, filtered to one shop's queue
- 01
One shop's queue, not the whole board
CES Work Orders reads the same discrepancy log the rest of the airfield already works from, filtered down to what's open and actually assigned to a Civil Engineer shop, with a tab for each shop and one for all of them together.
- 02
Five tiles, the state of the queue at a glance
New, In Work, Project, awaiting verification, and anything open past 30 days. The shape of the workload is visible before a single record is opened.
- 03
Move it forward without leaving the row
Update a discrepancy right where it sits: mark it in work, flag it as a project, or mark the work completed. Those are the status choices that are actually CES's to make, and nothing more.
- 04
Closing the loop stays on the airfield side
Marking work completed moves a discrepancy to awaiting verification, not straight to closed. Confirming the fix and closing the record out is a separate step, and verification of the fix is kept on the airfield side, not with the shop that performed it.
The benefit
What it automates
One record, not two to keep in sync
CES works the exact discrepancy the rest of the airfield already opened. There's no separate work-order system for the two to drift apart on.
The queue only shows what's actually CES's
Open, assigned to a Civil Engineer shop, still outstanding. Filtered automatically, so nobody's scanning the full discrepancy board looking for their own shop's name.
Completed isn't closed until it's verified
Marking work completed hands it back for airfield-side verification instead of calling it done on the spot, so the record shows what was actually confirmed.
Related
Works alongside
FAQ
Straight answers
Is CES Work Orders a separate system from Discrepancies?
No. It's the same discrepancy record, filtered to what's open and assigned to a Civil Engineer shop. There's nothing to keep in sync, because there's only one record.
Can CES close out a work order from this page?
No. CES can mark a discrepancy in work, flag it as a project, or mark the work completed. Closing the record (confirming the fix and stamping the closure date) is a separate airfield-side step. An Airfield Manager or base admin signs off, never the shop itself.
Can CES open a new discrepancy from this page?
Not from here. CES Work Orders is where assigned work moves forward, not where new discrepancies get opened. Reporting one still happens wherever it's found: an inspection, a check, or the discrepancy log itself.
How is the queue organized?
By shop, with a tab for each one plus a combined view, and five tiles (New, In Work, Project, awaiting verification, and anything open past 30 days) showing the state of the queue before you open a single record.