NOTQIN — OT Track

NOTQIN Team Onboarding & Alignment Pack 2026

17 min read

NOTQIN Team Onboarding & Alignment Pack 2026

Why this pack exists. Before we ship marching orders, the four of you need (a) enough context to think independently about the project, (b) the theoretical floor that makes our customer conversations defensible, and (c) a real chance to push back, disagree, and correct the direction. Without that, the Path-to-Pilot plan is just Ahmed’s plan with your names on it.

Goal of this pack. Two weeks from now (target 2026-06-07), we meet for an Alignment Meeting where each of you has read the canonical material, formed your own view, and brings specific structured feedback (§5). After that meeting, we re-baseline the Path-to-Pilot doc and start Wave I (discovery sprint) with the plan you helped write, not the one Ahmed handed you.

Time budget. Shared floor (§4) ≈ 5–6 hours. Your role-specific deep dive (§2) ≈ 8–12 hours. Optional 3-month deepening (§3) ≈ 30–40 hours over the quarter. Spread across two weeks, not one weekend.

0. How to use this pack

  1. Day 1 (this week). Read §1 (the project in 5 minutes) + §4 (the shared concept floor headline). Confirm you accept the workstream Accountable role in NOTQIN Path-to-Pilot — Team Orchestration 2026 §1, or push back now.
  2. Week 1. Work through the Required Reading for your role in §2. Take notes in your own working file inside 01_Project Portfolio/NOTQIN Ecosystem/<your-name>-notes.md. Don’t optimize the notes for me — optimize them for you understanding the system.
  3. Week 2. Finish required reading. Start the Optional 3-Month Deepening list (§3). Fill in the §5 structured feedback form. Bring it to the Alignment Meeting.
  4. 2026-06-07 — Alignment Meeting (90 min). Round-table the §5 answers. Converge on plan corrections. Re-baseline Path-to-Pilot together. Start Wave I the following Monday.

Honesty floor. If at any point during the two weeks you decide the project, the role, or the time commitment doesn’t fit — tell Ahmed before the Alignment Meeting, not after. We’d rather know.

1. The project in 5 minutes

What NOTQIN is. A data-driven decision layer for Moroccan industrial suppliers. We connect Level 0–2 (machines, sensors, PLCs) to Level 3–4 (MES, ERP, decisions) using a Unified Namespace backbone built on MQTT + Sparkplug B, and we surface that as dashboards, alerts, and audit packs that customers actually use.

What NOTQIN is not. Not “AI dashboards for factories.” Not a SCADA replacement. Not an OPC UA gateway vendor. Not a generic IoT platform. The product is the decision layer, not the plumbing.

Why now, why Morocco. Tanger Med has ~120 automotive operators. AMICA reports >260 suppliers, 3 OEMs, >€15B exports, 69% integration rate heading toward 75% by 2030. CBAM enters fee phase Jan 2026 for steel/cement/aluminium/fertilizer exporters. Every one of those numbers is pressure on Moroccan industrials to capture and use operational data they currently don’t. We are the layer that turns that pressure into a budget line.

Where we are today (2026-05-24).

  • 🔴 Zero signed paying customers.
  • ✅ Working product: 5 sector packs (auto, cement, textile, aero, agrifood), simulator, factory-app, IEIA module, CBAM Agent, ERP picker — all shipped through Wave G.
  • ✅ Working thesis: NOTQIN Industrial Intelligence Operating Thesis 2026 — the 5-layer model + 9-stage roadmap that ties everything together.
  • ✅ Working sales material: 4 pitch HTMLs, target lists, GTM playbooks.
  • ⚠️ Brand is mid-rebrand (Smartex → NOTQIN, due to a Portuguese Series A collision).
  • ⚠️ Solo founder until today — Ahmed has carried all six workstreams alone.

What the four of you change. With Elwalid on AI, Imrane on GTM, and Oussama + Mouad on OT engineering, we can finally run six workstreams in parallel and credibly chase first paid pilot live by mid-August 2026. That target is in NOTQIN Path-to-Pilot — Team Orchestration 2026 — and it’s negotiable in the Alignment Meeting.

The six target questions every customer must be able to answer with NOTQIN. Memorize these. They’re the opening lines of every cold email and the success test of every dashboard.

  1. Which machine or process is creating the most contract risk?
  2. Which defects are causing OEM rejection or rework?
  3. Which line stoppages threaten OTIF delivery?
  4. Which maintenance actions actually reduce downtime?
  5. Which energy or process changes improve margin?
  6. Which data proves compliance during customer audits (IATF 16949, AS9100D, CBAM, CNDP)?

2. Required reading per role (Week 1, ~8–12 hours)

For each item: read order matters. Skipping ahead works less well than it looks.

2.A — Elwalid (AI lead, WS-B)

The thesis: NOTQIN’s AI must be honest, causal, and SPC-grounded before it is ML-fancy. Stage 6 (SPC) is the credibility floor; Stage 7 (PdM) and Stage 9 (causal) are where you’ll spend most of your time.

  1. NOTQIN Industrial Intelligence Operating Thesis 2026 — full read. Pay extra attention to §4 (5-layer model), §5 Stages 4–9, §6 (MVP scope).
  2. ISA-95 — Distilled + OT-UNS Reference Card — the data-model floor your AI sits on.
  3. HiveMQ MQTT Essentials — Distilled — understand the transport so you know what guarantees you do and don’t have.
  4. Morocco UNS Standard v0.1 (if file exists; else 02_Knowledge Base/Industry 4.0/) — the namespace your event stream conforms to.
  5. Walker Reynolds 4.0 Solutions intel — MEMORY.md entry project_40solutions + linked file. The 10-pillar maturity model and the UNS → Agentic AI evolution narrative.
  6. ThreadCloud + Knowledge Graphs memory entry — UNS = 2D-for-humans, KG = 3D-for-agents. Read this before you propose a KG layer for NOTQIN.
  7. NIST Smart Manufacturing data analytics paper (open-access; link in Reading List — Smartex Founder Curriculum 2026) — the two barriers (tool choice + decision integration). The second is our wedge.
  8. PFE Backbone B5 (IA) — 07_Learning/PFE Research/study-guides/B5* — connects to ENSA-Berrechid SIBD theory you’ll be evaluated on by Moroccan engineering counterparts.

Expected output by Alignment Meeting: a 1-page “what I’d build first” note in 01_Project Portfolio/NOTQIN Ecosystem/AI Spike Notes — Elwalid.md + 3 questions the thesis doesn’t answer.

2.B — Imrane (GTM lead, WS-C + WS-D)

The thesis: Moroccan industrials don’t buy “AI.” They buy fewer line stops, fewer rejected parts, audit-proof CBAM evidence. Your job is to translate the thesis into language that wins meetings.

  1. NOTQIN Go-to-Market OS — full read. The 3-audience funnel, pricing menu, demo script, objection responses.
  2. NOTQIN GTM — Aeronautics & Automotive — sector override. NOT CBAM-driven; OEM scorecard + line-stop economics + IATF/AS9100D.
  3. NOTQIN Customer Engagement Playbook — ICP + 5-stage funnel for discovery.
  4. NOTQIN Pilot Playbook — Trust Ladder rungs + MUST-NOTs. Know what we will and won’t agree to in a pilot.
  5. Feasibility Study — NOTQIN Auto Tier-2 Scorecard 2026 — the narrow thesis behind your WS-C target list.
  6. AMICA Tier-2 Target List 2026 — your working file. Rows 4–12 are blank; filling them is your Wave H deliverable.
  7. Master — Customer Anatomy + Appx C (Quality) + Appx E (Demo & Objections) — what we say in front of a customer and why.
  8. Moroccan Industrial Maturity Dossier (MEMORY.md → project_moroccan_industrial_maturity + linked vault files) — the 22+ companies scored on 11 dimensions. Named contacts inside.
  9. Ehab Mes — Arabic-Market Positioning Intelligence 2026 — Arabic register reference for the parts of our communication that should sound Moroccan-Arab, not Silicon-Valley-translated.
  10. Manufacturing Hub — Operator Pain Framings 2026 — verbatim operator pain vocab. Use these phrases, not corporate-speak.

Expected output by Alignment Meeting: AMICA Tier-2 Target List 2026 rows 4–12 filled with named contacts + 5 draft cold-email opening lines grounded in the §1 six target questions + 1 page of disagreements with the GTM OS pricing or playbook.

2.C — Oussama (OT engineer, WS-E auto focus)

The thesis: OT integration is where pilots die. Your job is to ensure that when we walk into a Moroccan plant, nothing surprises us. The auto sector pack must be field-ready, not just simulator-correct.

  1. NOTQIN Industrial Intelligence Operating Thesis 2026 — focus on §4 (5-layer model), §5 Stages 1–4.
  2. ISA-95 — Distilled — read end-to-end. You’ll be defending Level 0–3 architecture in customer rooms.
  3. HiveMQ MQTT Essentials — Distilled — pub/sub, QoS, retained messages, LWT, sessions.
  4. OT-UNS Reference Card — print and keep on your desk.
  5. Sparkplug B specification (Eclipse Tahu — public spec) — the encoding rules. Read at least the Topic Namespace and Birth/Death Certificate sections.
  6. Morocco UNS Standard v0.1 + v0.2 (02_Knowledge Base/Industry 4.0/) — focus on the auto sector overlay and the security envelope (TLS 1.3, mTLS, Ed25519).
  7. Existing auto sector pack — packages/sector-packs/auto/ in the code repo. Audit it against the Morocco UNS Standard auto overlay. Your Wave H deliverable.
  8. Aero MRO — Wrong-Part Detection on Test Cell 2026 — read this even though you’re auto-focused. It teaches the discipline of physics-signature-on-UNS that we’ll generalize to auto sub-min RCA.
  9. Master — Customer Anatomy Appx A (Auto) — Renault/Stellantis/BYD reality. Plant org, supplier scorecards, JIT/JIS pressures.
  10. PFE Backbone B3 (Processus) — 07_Learning/PFE Research/study-guides/B3* — process management theory you’ll need for the PFE viva.

Expected output by Alignment Meeting: Auto sector-pack audit at 01_Project Portfolio/NOTQIN Ecosystem/Sector Pack Audits/auto-2026-05.md with prioritized gap list + ≥3 PRs opened against packages/sector-packs/auto/.

2.D — Mouad (OT engineer, WS-E CBAM/steel focus)

The thesis: YNNA Steel has a Jan 2026 CBAM forcing function. If our CBAM/steel pack is field-ready before our auto pack, the CBAM warm-intro track (WS-D) could deliver the first signed pilot before WS-C. Your work is gating.

  1. NOTQIN Industrial Intelligence Operating Thesis 2026 — same focus as Oussama (§4 + §5 Stages 1–4 + §8.E energy wedge).
  2. ISA-95 — Distilled + HiveMQ MQTT Essentials — Distilled + OT-UNS Reference Card — same floor as Oussama.
  3. Sparkplug B specification — same.
  4. Morocco UNS Standard v0.1 + v0.2 — focus on the YNNA Steel overlay and the CBAM compliance envelope.
  5. CBAM Regulation — if note exists; else build a 1-page note for the vault as a Week-2 task. EU regulation 2023/956 + implementing acts. Embedded emissions reporting requirements.
  6. Existing CBAM Agent module (in code repo) — understand what’s already built before you add. Don’t duplicate.
  7. Existing steel sector pack (or cement if steel doesn’t exist separately) — audit against the YNNA Steel overlay.
  8. Moroccan Industrial Maturity Dossier — focus on the steel & cement section. Sonasid, YNNA Steel, OCP via OCP Group, LafargeHolcim Maroc.
  9. PFE Backbone B2 (Données) — 07_Learning/PFE Research/study-guides/B2*.

Expected output by Alignment Meeting: Field-readiness checklist template at 01_Project Portfolio/NOTQIN Ecosystem/Field Readiness Checklist v1.md + CBAM/steel pack audit + ≥3 PRs.

2.E — Ahmed (founder)

You wrote most of this material. Your “required reading” is different:

  1. Re-read NOTQIN Path-to-Pilot — Team Orchestration 2026 and the NOTQIN Industrial Intelligence Operating Thesis 2026 as if you were one of the four — note where they’re ambiguous, where they over-assume context, where a new reader would stall.
  2. Read all four §5 feedback forms before the Alignment Meeting. Resist the urge to respond before the meeting itself — let disagreement breathe.
  3. Pre-decide which §9 anti-list items are negotiable and which are not.

3. Optional 3-month deepening (Wave I–M, ~30–40 hours, spread out)

Beyond the required floor, here’s what each role should be learning over the next quarter to make our customer conversations defensible at industrial-engineer level. None of this is a deliverable — it’s the difference between “AI student with a sales deck” and “someone the plant manager respects.”

Elwalid

  • Statistical Quality Control — Montgomery — Chapters 1–8 (control charts, capability indices). Maps to Thesis Stage 6.
  • Introduction to Statistical Learning — JWHT — Chapters 1–4 + 8 (trees). Re-orientation if you came from deep learning first.
  • Practical MLOps — for deployment / monitoring discipline.
  • NASA C-MAPSS turbofan dataset + 1 bearing-vibration public dataset — implement one baseline RUL model. Honest framing: practice, not customer evidence.
  • DoWhy library tutorial — causal hypothesis cards (Thesis Stage 9).
  • ISO 22400 standard (skim) — KPI formulas, units, time behavior. Cite verbatim when defining NOTQIN dashboards.

Imrane

  • The Challenger Sale — Dixon & Adamson — the teach/tailor/take-control posture for industrial B2B.
  • SPIN Selling — Rackham — for discovery-call question discipline.
  • Smartex Deep Research Playbook §16 cadence — adopt the fortnightly AMICA / GIMAS pulse rhythm.
  • Read the next 4 weeks of Manufacturing Hub — Operator Pain Framings 2026 source podcasts as they ship. Build the operator-pain vocabulary.
  • LinkedIn-content study — read Founder LinkedIn Cadence + 1 industrial-founder you admire weekly.
  • 2 customer discovery calls as observer (Ahmed leads, you take notes) before you lead your first one.

Oussama

  • Factory Physics — Hopp & Spearman — Chapters 1–7 (flow, variability, bottlenecks). Maps to Thesis Stage 1.
  • The Goal — Goldratt — the bottleneck-thinking novel; one weekend read.
  • Industrial Network Security (Byres/Green) or equivalent — IEC 62443 zones/conduits at conceptual level.
  • Eclipse Tahu reference implementation (Java or Python) — walk through it once.
  • Inductive Automation Ignition free trial — install, run the UNS quickstart, understand what the dominant SCADA looks like.
  • Visit one Moroccan plant in person if possible (any plant — friend-of-family, ENSA contact). Build floor-floor intuition.

Mouad

  • Same Hopp & Spearman + Goldratt as Oussama.
  • Designing Data-Intensive Applications — Kleppmann — Chapters 1–4 + 11. Stream processing literacy.
  • EU CBAM implementing regulation 2023/1773 — embedded-emissions methodology, default values, verification. Read the regulation itself, not just summaries.
  • 1 paper from the CESMII ProductionStateEnergyConsumption schema work.
  • Same Ignition trial as Oussama.

Shared (everyone, at your own pace)

  • Toyota Production System — Taiichi Ohno — short, foundational. Lean / jidoka / JIT vocabulary that every plant manager grew up on.
  • The relevant Reading List — Smartex Founder Curriculum 2026 domains for your role.
  • One Smartex Deep Research Playbook cycle observed each fortnight — see how Ahmed runs deep research so you can run your own.

4. Shared concept floor (everyone, ~3 hours)

The minimum vocabulary we all share before we walk into a customer room together. Test yourself at the Alignment Meeting — Ahmed will spot-check definitions.

ConceptSource for your readThe 1-line test
ISA-95 5 levelsISA-95 — DistilledName Level 0–4 and one example each, in 30 sec
Unified NamespaceOT-UNS Reference CardWhy does UNS beat point-to-point integration?
MQTT pub/sub + QoSHiveMQ MQTT Essentials — DistilledWhen do you use QoS 1 vs QoS 2 in a plant?
Sparkplug BOT-UNS Card + Tahu specWhat’s a Birth Certificate and why does it exist?
ISO 22400 OEEThesis §5 Stage 1OEE = ? · what data do you need to compute it?
IATF 16949 + PPAP / 8DCustomer Anatomy Appx CWhat’s the supplier-scorecard chain of evidence?
CBAMVault note + regulationWhat does Jan 2026 actually change for YNNA Steel?
CNDP / Law 09-08Vault + Morocco UNS v0.2Can we process customer data without a CNDP declaration?
The 5-layer modelThesis §4Physical → Signal → Event → KPI → Decision — example for each
The 6 target questionsThis pack §1Recite from memory

If you can’t pass the 1-line test on any row, that’s your first 30-min read.

5. Structured feedback form (Week 2, ~90 min per person)

The Alignment Meeting is worthless if I get “looks good.” Each of you fills out this form in your own file at 01_Project Portfolio/NOTQIN Ecosystem/Feedback — <YourName> 2026-06.md and brings it to the meeting. Skip no question. “I don’t know yet” is a valid answer — vagueness is not.

5.1 — Your understanding (in your own words)

  1. Describe NOTQIN in 3 sentences as if telling a Moroccan industrial-engineer cousin who has never heard of it. Do not copy-paste from §1.
  2. What is the 5-layer model and where does YOUR workstream sit on it?
  3. What are the six target questions? (Yes, just recite — proves you read.)

5.2 — Disagreement (at least one — force yourself)

  1. One thing in the NOTQIN Industrial Intelligence Operating Thesis 2026 you disagree with — or where you think it overclaims, underclaims, or is missing a layer. If you don’t have one, you didn’t read it critically.
  2. One thing in NOTQIN Path-to-Pilot — Team Orchestration 2026 that won’t survive contact with reality. What gets cut first?
  3. One thing in your workstream’s §2 (WS-B / WS-C / WS-E) Definition of Done that you’d rewrite to be more honest or more useful.

5.3 — Risk (your view, not Ahmed’s)

  1. What’s the first thing that will go wrong on this plan, in your honest estimate? Be specific (which workstream, which week, which dependency).
  2. What’s the silent risk Ahmed isn’t seeing? Something he can’t see because he wrote the plan.
  3. What’s the risk YOU bring to the team? (Honest self-audit. Time conflicts, knowledge gap, communication style, exam-period collision.)

5.4 — Direction correction

  1. If we have to cut ONE workstream entirely to fit reality, which one and why?
  2. If we have to slip the pilot date by a month, what would buy us the most quality?
  3. If we have ONE friendly first customer fall in our lap tomorrow, what’s the smallest thing we could deliver to them in 4 weeks?
  4. Which of the §0 six target questions is the WEAKEST starting wedge for Moroccan customers, in your view?

5.5 — Logistics (answer specifically — vague answers will be re-asked at the meeting)

  1. Realistic hours per week you can commit between today and 2026-08-17 (pilot-live target). Include exam-period dips.
  2. Hard conflicts — exams, defenses, family, paid work. Dates.
  3. What do you need from Ahmed to succeed in your workstream? (Time? Decisions? Money? Access to a specific person?)
  4. What do you need from the rest of the team?
  5. Equity / compensation expectations — write what you’d consider fair. Don’t be polite. We’ll discuss as a group.

5.6 — One free-form box

  1. Anything else. Including: “I don’t think I’m the right person for this workstream” or “I think we should reconsider the project entirely.” This is your safe channel.

6. Alignment Meeting (target 2026-06-07, 90 min)

Agenda — strict.

MinBlockFormat
0–10Ahmed: 5-min recap of the project + 5-min recap of the plan. No defense, just framing.Talk
10–55Round-table — each person walks their §5 feedback form (10 min × 4). Others only ask clarifying questions, no rebuttal.Round-table
55–75Convergence — pick the 3–5 changes the team agrees should land in the Path-to-Pilot doc.Discussion
75–85Logistics lock — hours, hard conflicts, comp framework.Discussion
85–90Wave I commitment — who does what by 2026-06-22.Decision

Outputs of the meeting:

  • Rewritten Path-to-Pilot doc (Ahmed edits within 24h, posts to team channel).
  • Locked time commitments + comp framework letter (Ahmed drafts within 1 week).
  • Wave I sprint commitments live in the team channel.

Action items

  • 2026-05-26 (Mon) — Share this pack with Elwalid, Imrane, Oussama, Mouad. Confirm receipt + role acceptance. (Ahmed)
  • 2026-05-26 — Each team member creates 01_Project Portfolio/NOTQIN Ecosystem/<name>-notes.md for their reading notes. (All)
  • 2026-05-31 — End-of-Week-1 lightweight check-in (15 min async or sync): how is the required reading going, any blockers? (All)
  • 2026-06-05 (Fri) — Each team member’s §5 feedback form complete, posted to team channel. (Elwalid, Imrane, Oussama, Mouad)
  • 2026-06-06 — Ahmed reads all four feedback forms. No public response yet. (Ahmed)
  • 2026-06-07 — Alignment Meeting (90 min). (All)
  • 2026-06-08 — Ahmed rewrites NOTQIN Path-to-Pilot — Team Orchestration 2026 reflecting Alignment Meeting decisions. (Ahmed)
  • 2026-06-09 — Wave I kickoff. Discovery sprint starts. (All — per re-baselined plan)

Open items

  • Is two weeks enough? If anyone reports at the Day-5 check-in that the required reading needs three weeks, slip Wave I by a week. Better than fake confidence.
  • Coordination tool — pick at the Day-1 kick-off call. Discord, WhatsApp, or Slack.
  • Should the Alignment Meeting be recorded? Pros: future team members onboard from it. Cons: people self-censor. Default: not recorded, decisions written up after.
  • What if one person’s feedback (§5) reveals they shouldn’t be on this team? Ahmed has private 1:1 with that person within 48h of meeting. Honesty floor applies.
  • Compensation discussion timing — at the Alignment Meeting or 1:1s after? Risk of group dynamics distorting individual asks. Lean toward: group framework agreement, individual numbers in 1:1.

See also

Graph View

Backlinks