Field Readiness Checklist v1

Hard rule. This checklist is green before a NOTQIN engineer walks into a customer plant. If any 🔴 item remains, the site visit is delayed, not “we’ll figure it out on-site.”

Used during. Diagnostic phase (Wave J) before the Pilot site deployment (Wave L). One checklist filled per pilot customer.

Owner. Mouad ships v1 template. Per-customer instance is owned by the Diagnostic lead (likely Ahmed or Imrane). Oussama reviews v1 from the auto perspective.


A — Customer environment (must answer BEFORE site visit)

#ItemStatusSourceNotes
A1Plant address, gate contact, working hours⚫
A2IT contact + OT contact (named individuals)⚫
A3Confirmed PLC vendors + models (Siemens S7-15xx? Schneider M580? Allen-Bradley ControlLogix? Omron?)⚫
A4Confirmed PLC firmware versions⚫
A5Confirmed network protocols on plant LAN (PROFINET, EtherNet/IP, Modbus TCP, OPC UA)⚫
A6Existing SCADA/HMI vendor (Ignition, Wonderware/AVEVA, WinCC, FactoryTalk, custom)⚫
A7Existing MES (or none)⚫
A8ERP vendor + version (Odoo, SAP, Sage, custom)⚫
A9Energy meters present? Brand? Communication protocol?⚫
A10Existing data historian (if any)⚫

B — Network / security (negotiate BEFORE site visit)

#ItemStatusSourceNotes
B1IT-approved network segmentation diagram (OT zone ↔ DMZ ↔ IT)⚫
B2Outbound MQTT port (8883 TLS) allowed from edge collector?⚫
B3NTP source on plant network (for timestamp sync)⚫
B4Firewall change request submitted and approved⚫
B5mTLS cert exchange procedure agreed⚫
B6Customer IT approves NOTQIN-controlled broker (in-country hosting per CNDP)⚫
B7Data-flow diagram signed off by customer DPO / CNDP-equivalent⚫

C — Equipment / signals (verified during scoping call)

#ItemStatusNotes
C1List of lines/machines in scope of pilot⚫
C2Tag list available (or PLC project file accessible)⚫
C3Required tags for OEE present (state, part count, reject count)⚫
C4Required tags for downtime intelligence (fault codes, idle reasons)⚫
C5Sample-rate budget realistic vs PLC scan time⚫
C6Operator-entry UX agreed for unmeasured fields (downtime reasons, batch IDs)⚫

D — NOTQIN side (we control these)

#ItemStatusNotes
D1Sector pack audit complete and green (auto: Sector Pack Audits/auto-2026-05 · steel: Sector Pack Audits/cbam-steel-2026-05)⚫
D2Edge collector image built + tested with this customer’s protocols⚫
D3Customer droplet provisioned (per WS-A runbook)⚫
D4Factory-app branded + sector-configured for this customer⚫
D5Smoke-test pack validated against the customer’s tag list⚫
D6On-call runbook (who to call when something breaks at 2 AM)⚫
#ItemStatusNotes
E1NDA signed⚫
E2Diagnostic SOW signed (if site visit is during Diagnostic)⚫
E3Pilot SOW signed (if site visit is for pilot deployment)⚫
E4CNDP declaration filed⚫
E5Insurance / liability coverage in place⚫

Per-customer instance template

When using this for a real customer, copy this file to 01_Project Portfolio/NOTQIN Ecosystem/Pilots/<customer>/Field Readiness Checklist.md and fill in.

Kill-criteria

If any of the following are 🔴 at T-7 days from site visit:

  • A3 / A5 — unsupported PLC or protocol on our side → engineering scope re-baseline, possible no-go
  • B6 / E4 — CNDP-incompatible hosting → legal escalation
  • E1 / E2 / E3 — paperwork → push site visit, do not “trust handshake”

See also