From the first shop-floor walk to a working prototype: the roles, phases and verbs this SOP runs on.

Engagement

One full on-site customer project: progressed from problem framing through build and industrialization to handoff and exit.

Engagements

Engagement list: the entry point for all field projects.

FDE

Forward Deployed Engineer: an engineer who embeds at the customer site with the product to deliver solutions fast.

force

Force advance: bypasses the block, but gates still evaluate and record; exceptions land in the audit log.

Gemba

Site walk: engineers embed on the shop floor to observe real processes, equipment and pain points (maps to the site_survey phase).

Gemba walk

From Japanese genba (the actual place): walk the shop floor where value is created, observe real work and talk to operators instead of judging from reports. A core lean/Toyota practice.

prototype

Real-data prototype: build a verifiable prototype on the customer's real data, not demo data.

qualification

Qualification: confirm the problem is real and the customer has budget and intent.

SOP

Standard Operating Procedure; here, the 18-phase project lifecycle.

stakeholder_map

Stakeholder map: identify decision-makers, users, blockers and what each wants.

Zone

SOP phase group: A pre-engagement → B build → C industrialization → D handoff & exit.

zones

Phase groups (Zone): A pre-engagement → B build → C industrialization → D handoff & exit.

The predicates re-evaluated on every phase advance, plus the hard conditions the contract side has to meet.

FAT/SAT

FAT = Factory Acceptance Test; SAT = Site Acceptance Test — both need the customer's signature.

Gate

Predicate-style gate: re-evaluated on every phase advance (e.g. dual sponsor, FAT/SAT sign-off); a failure blocks the advance and a stale pass never counts.

Gates

Gate list: every gate that applies to this project and its status.

overlay

Overlay: extra gates that only apply to the industrial profile (factory icon).

sponsor

The project's decision-maker/funding stakeholder; this SOP requires a business and an industrial sponsor to jointly confirm success criteria.

success_criteria

Success criteria: contractual, measurable acceptance conditions signed off by both sponsors.

Success criteria成功标准

Success criteria (success_criteria): contractual, measurable acceptance conditions confirmed by the dual sponsors.

Gates门禁

Gates: the gate-check results applying to the current phase (pass/blocked).

Scenario configuration and the data itself: what to ingest, how to forge it, and what counts as enough.

Context

Project context: a structured set of site, stakeholders, success criteria, SLOs, functional safety and assets.

Corpus

Corpus: the sample set for training/eval; forging is the pipeline of cleaning, PII masking, dedup, gap-filling and synthesis.

JSONL

One JSON object per line; common for sample and eval data.

KPI

Key Performance Indicator; the ticket and manufacturing scenarios use different catalogs.

manufacturing

Manufacturing / embodied-robotics scenario: OPC UA, MQTT, ROS2 and other industrial feeds + 6 industrial compliance gates.

min_samples

Minimum real samples per category; below it the category is a gap and triggers synthesis.

PII

Personally Identifiable Information (name/email/phone); automatically masked during forging.

Profile

Scenario profile: defines available connectors, the KPI catalog and applicable gates (ticket support / manufacturing).

stub

Stub: interface and data model ready, the real system not yet wired.

synth_per_gap

How many synthetic samples to add per gap category.

ticket

Support-ticket scenario: CSV/Zammad/Salesforce/MySQL ingestion, no industrial gates.

Stakeholder干系人

Stakeholder: project roles (decision-maker, users, ops, union…) and their success metrics.

Corpus forging语料锻造

Corpus forging: raw data (CSV etc.) → PII masking → dedup → quality gate → coverage analysis → targeted synthesis → report.

Shop-floor data sources, protocols and production-line metrics.

DexNet

UC Berkeley grasp-planning network and benchmark dataset; a common reference for pick success.

Historian

Time-series historian: stores process history (temperature, takt, alarms…).

ISA-95

The international standard for enterprise-to-shop-floor integration; the basis of the MES data model.

MES

Manufacturing Execution System: shop-floor data source for work orders, quality and downtime.

MQTT-Sparkplug

MQTT: lightweight pub/sub protocol; Sparkplug B standardizes its industrial payload semantics.

MTBF

Mean Time Between Failures (hours); higher is more reliable.

OEE

Overall Equipment Effectiveness = availability × performance × quality; world-class ≥ 0.85.

OPC

Tencent Cloud OPC (Other Professional Certification): the product-competency exam for channel partners.

OPC UA

Unified industrial-automation communication protocol; reads PLC tag data directly.

pick success

Robotic pick success rate; DexNet benchmark ≈ 0.80.

PLC

Programmable Logic Controller: the control unit of production equipment.

ROS2 Bag

ROS 2 recording/replay format, common for robot trajectories and sensor data.

Functional-safety levels, deployment shapes and labour co-determination — the compliance that becomes gates.

air-gapped

Air-gapped deployment: physically isolated from external networks; installs and updates go through an offline checklist.

CE

EU conformity marking: the product meets the relevant EU directives.

EU AI Act

EU AI Act: risk-tiered AI regulation; high-risk uses require compliance assessment and documentation.

IEC 61508

Functional-safety standard for E/E/PE systems; defines SIL levels.

ISO 10218

Industrial robot safety standard: risk-assessment requirements for collaborative and regular robots.

ISO 13849

Machinery functional-safety standard; defines Performance Levels PL / PLr.

OT/IT separationOT/IT 隔离

OT/IT separation: isolating the shop-floor operational-technology network from the corporate IT network — a common industrial security requirement.

PLr

Required Performance Level (ISO 13849); PL is the level actually achieved.

SIL

Safety Integrity Level (IEC 61508).

works_council

German Works Constitution Act (BetrVG §87) co-determination: deployments involving employee monitoring/performance need union consent.

Functional safety功能安全

Functional Safety: standards ensuring machinery/control systems stay safe under failure (PL/SIL levels).

Works council工会

Employee representative body; in Germany, deployments involving employee monitoring/performance require its co-determination (works_council gate).

Air-gapped气隙

Air-gapped: a closed network physically isolated from external networks.

Shift system班次

Shift system (e.g. 3 shifts); 24/7 lines need shift-handover integration (shift_handover gate).

After go-live: service commitments, drift monitoring, the backflow flywheel, and the exit.

bad case

Bad-case mining: find poorly performing samples from eval results, then classify and attribute them.

drift

Drift: data distribution/quality shifting over time and degrading the model; monitor it to trigger retraining.

Flywheel

Flywheel: field events flow back as corpus with weekly incremental retraining — the loop that makes the system better the longer it runs.

on-call

Rotating duty response: alerts route to whoever is on call so someone can act around the clock.

runbook

Operations runbook: failure-handling steps, rollback plans and escalation paths.

SLA

Service Level Agreement: the external contractual commitment, usually backed by several SLOs.

SLO

Service Level Objective: an internal, measurable quality commitment, e.g. '99% of tickets first-responded within 5 minutes'.

Alert route告警路由

Alert route: the channel/on-call group an SLO breach pages (alert_route).

Drift漂移

Drift: data distribution/quality shifting over time and eroding the model; a monitoring item.

Handoff package移交包

Handoff package: the full artifact set delivered to the customer at project end — runbook, model, monitoring config, known limitations and more.

Flywheel飞轮

The data flywheel: event backflow → corpus increment → retraining; the longer a project runs, the better the model fits that customer.

AgentScope runtime concepts, external systems, and the feature names inside the workbench.

ACA

Alibaba Cloud Associate: the entry-level LLM engineer certification (aca13).

ACP

Alibaba Cloud Professional: the advanced LLM engineer certification (acp26).

AgentState

AgentScope's agent state object; the permission context is injected into the runtime through it.

RAG

Retrieval-Augmented Generation: retrieve from a knowledge base first, then generate the answer.

Salesforce

CRM platform; here a customer/ticket data source.

SubAgentTemplate

AgentScope's sub-agent blueprint: a template with a preset role, tools and prompt.

Toolkit

AgentScope's tool collection: binds connectors/functions as callable agent tools.

Zammad

Open-source helpdesk/ticketing system.

Workbench工作台

Workbench: cross-project overview — global stats, project matrix, recent skills.

Skills library技能库

Skills library: reusable methodology/field notes in research / implementation / optimization / methodology.

Consolidate沉淀

Consolidate field experience into a reusable skill for later retrieval and reuse.

Journal现场记录

Journal: research / implementation / optimization field notes; one click turns them into skill drafts.