CONOPS A product of CONOPS
Core module · Records

Every request on the floor becomes a record with an owner, a clock and a history.

Shop Floor Tickets, NPI items, MPS savings and PLM changes stop arriving by walk-up and sticky note. A kiosk form captures them in under 90 seconds, queues route them, SLA clocks keep them honest.

In production Engineering managers, quality, shop-floor leads Reads the ERP, never writes to it
CONOPS | MOS · Records · Engineering queue
Open in queue
27
Healthy
Breaching SLA
3
Critical
Median triage
41 min
Warning
QFI-N-00412 Fixture crack, cell 7 · Shop Floor Ticket SLA 2h left
QFI-N-00409 First article hold, P/N 61-2207 · NPI Breached
QFI-N-00407 Coolant spec change · PLM change In review
QFI-N-00404 Deburr time reduction · MPS savings Awaiting owner
Department queue with SLA state, as the engineering lead sees it at shift start.
Outcomes

What changes when Records is live

Requests stop getting lost
Every ask, from a cracked fixture to an NPI hold, is a typed record in a department queue with an owner, a priority and an SLA clock.
Triage happens the same day
Breach alerts and aging views put the oldest, most expensive items in front of the right lead before the morning meeting.
History is never argued about
Temporal tables keep every edit, comment and status change. Six months later the record shows who decided what, and when.
Feature walk-through

As built, in the order your team meets it

Screens shown are rendered stand-ins for the real views; production screenshots use seed demo data with customer names and part numbers replaced.

01 / 06

Kiosk-friendly submit form

A large-target form built for a shared terminal at the cell. Category, location and a photo are enough; the record is numbered and routed on submit. A submission takes under 90 seconds.

  • Per-site numbering, for example QFI-N-00012
  • Category drives the queue and the SLA
  • Email-in creates records from a shared mailbox
Records · Kiosk-friendly submit form
Submit path
Kiosk form Numbered record Department queue SLA clock running
02 / 06

Typed record categories

Shop Floor Ticket, NPI, MPS savings and PLM change each carry their own fields, priorities and response plans. New record types are configuration, added per site without a deployment.

Records · Typed record categories
Record types
TypeOwner queueSLAAuto-launch
Shop Floor Ticket Maintenance / Eng 4 h triage Triage workflow
NPI item Engineering 2 d review NPI gate review
MPS savings Ops excellence 5 d Savings approval
PLM change Config control 3 d ECN approval
03 / 06

Quick-entry and bulk-edit grids

Leads work a queue as a grid: inline edits, multi-select reassignment, saved views per role and per site. Comments and @-mentions stay on the record.

  • Saved views by role, site and department
  • Bulk reassign, reprioritize, close
  • Comments, mentions and email-out from the record
  • Archive with full retrieval
04 / 06

SLA clocks and breach alerts

Each category has a response and a resolution clock. Breaches escalate to the department lead and, if ignored, to the site lead. The aging view is the first page of the daily meeting pack.

Records · SLA clocks and breach alerts
SLA attainment by departmenttarget 95%
Maintenance 97%
Engineering 91%
Quality 84%
Programming 96%
05 / 06

Attachments and email on Microsoft 365

Files live in SharePoint Online in your tenant, versioned and scanned. Notifications go through an email outbox; replies to a shared mailbox land back on the record. Every endpoint supports GCC High.

  • SharePoint Online attachments via Graph API
  • Email-out notifications, email-in replies
  • Works on the .us endpoints
  • No vendor-hosted storage
06 / 06

Import wizard and support intake

Bring the backlog in from the spreadsheet that preceded the system, with column mapping and validation. The same intake handles support tickets to CONOPS, so there is one place to look.

  • Column mapping with preview and validation
  • Import history and rollback
  • Support-ticket intake into the same queues
Data it reads

Nothing is written to your ERP

Records is a module of CONOPS | MOS (Manufacturing Operating System). It reads from the platform warehouse, which pulls change-only loads nightly from each site's ERP over a linked server. The ERP is never written to, and adding a site is configuration, not code.

How a site's ERP is onboarded

ERP datasets used by Records
  • Part master (for part lookups on a record)
  • Job orders (to attach a ticket to a job)
  • Customers and programs (for routing and reporting)

Records is primarily application data; ERP datasets are used for lookups and reporting context.

Who uses it

By role

Shop-floor lead

Submits from the kiosk, sees the status of what the cell asked for, gets a reply on the record.

Engineering manager

Works the department queue, reassigns, sets priority, answers breach alerts.

Quality

Owns holds and first-article items, tracks aging and root cause.

Site leadership

Reads the SLA and aging views in the daily pack; no edits needed.

Next step

See a ticket go from kiosk to closed, with every step on the record.

We walk through your current request paths, the record types you need on day one and how queues and SLAs would be set for each department.