Standard project plan for Selmo-based machine projects

This project plan defines a structured approach for implementing machine projects with the Selmo Standard. It serves as a template for planning, effort estimation, execution and documentation – with a focus on model-based process development in the Sequences (SEQ).

---

🎯 Project goal

A fully modeled, logically structured, safety-assured and CE-compliant machine control according to the Selmo standard:

• structured by Plant → HWZ → SEQ → Zone

• modeled across Logic, System and Parameter layers

• documented, tested, exported (PLC, HMI, CE)

The The number of SEQs determines the project scope.

---

📐 Project structure

1. Project definition & preparation

Milestone	Description
Project start	Goal definition, responsibilities
PFT analysis	Process – Function – Technology
Structure plan	Define Plant → HWZ → SEQ
Zone & IO pre-planning	Signals, types, addresses, safety requirements
Risk assessment (basic)	Preparation CE / safety concept

---

2. SEQ-oriented modeling (per Sequence)

Each A Sequence is an independent model block with sequence, zones, safety and parameters. These steps repeat for each SEQ:

Step	Goal
Model state logic	Sequence as SDEA: State, Timer, Decision, Repeater, Jump etc.
Define zones	Input / Output / In-Out / Mem, with signal, address, HMI text
Create bit control	Behavior of the zone per state: 0, S, i
Add parameter layer	Values such as times, repetitions, limits
Configure MXIC	manual releases for buttons with conditions
Define CMZ	Supervisions at SEQ, HWZ or PLANT level
StepTime & Teach	Time measurement and analysis for cycle optimization
Check HMI guidance	SEQ control: texts, colors, diagnostics understandable for the operator
Go through validation	Simulation, fault tests, step sequence
Perform export	PLC code, HMI texts, documentation (CSV, PDF)

⏱ Effort: per SEQ approx. 0.5 – 2 person-days, depending on complexity (single cycle or complex station)

---

3. System integration

Step	Goal
Check HWZ logic	Operating modes Hand / Auto / Reset
Test CMZ on HWZ / PLANT	Pressure, door, emergency stop etc.
Restart / reset behavior	modeled and testable
OPC UA / MES interfaces	Export mapping and integrate
Adjust visualization	HMI texts, colors, controls from model
Perform IO test	real signals ↔ modeled zones

---

4. Digitalization & twin (optional)

Step	Goal
Couple digital twin	Play out model behavior in simulation
State display in the twin	Display SEQ step, zone status, parameters live
Virtual validation	Sequence, error behavior, CMZ/MXIC in the test system
Feedback from twin	Adopt StepTime, reconcile HMI texts

---

5. Documentation & handover

Document	Content / purpose
IO mapping (Zone_IO_Map.csv)	Signals per zone with address and function
Parameter list (Parameter.csv)	IN/OUT values with unit and description
CMZ/MXIC definition	Safety functions, manual releases
Sequence diagram	State model from Logic Layer (SVG, PNG)
Change log (Model_ChangeLog.csv)	Revision history for CE and maintenance
CE documentation	Risk analysis, operating modes description, reset logic

---

🗂 Planning aid: SEQ as quantity framework

Example project: 1 machine with 2 stations

• Station 1: Clamp, inspect, unclamp → 3 SEQs

• Station 2: Singulation, transfer → 2 SEQs → Total effort = 5 SEQs = approx. 5–10 person-days (pure modeling)

---

🧾 Result

The project plan ensures:

• standardized procedure,

• clear quantity basis (SEQ-based),

• verifiable planning and progress control,

• standard-compliant and documented implementation.

📌 Each SEQ is a completed work step with its own engineering, testing and documentation package. The sum of all SEQs forms the complete machine process.