Control Systems ELVB25CSYS · 2026-2027

Plan of approach (PoA)

Scope

Group

Weight / P-F

30% of Design & project management

Due

2026-12-04 Fri 23:59

Resit

2026-12-18 Fri 23:59

Submission point

Plan of approach / Plan van Aanpak

• Scope: Group. Weight: 30% of the Design and project management subcode.
• Due: 2026-12-04 Fri 23:59. Resit: 2026-12-18 Fri 23:59. Source: _src/deadlines.md.
• Submit at: "Plan of approach / Plan van Aanpak" (Brightspace dropbox); resit via "Plan of approach resit / Plan van aanpak herkansing". As a project group, create the plan and have one person submit it. Source (the page titled "01 Literature literatuur" holds the assignment text; the "02 Plan of Approach Plan van aanpak" page now only links the workshop slides): _src/text/02 Learning activities - Leeractiviteiten/03 POA - PVA/01 Literature literatuur.html.md.
• Content: Write the plan using the English template. Required outline: project description and scope supported by a literature review (assignment description in your own words, literature review, project goal, individual goals), project organisation, communication plan, planning (milestones, task definition, resourcing), risk management, disclaimers and agreements. Source: _src/text/02 Learning activities - Leeractiviteiten/03 POA - PVA/01 att - Control Systems - PoA Template_EN.pdf.md. No separate rule for the literature review is stated beyond the outline: the assignment page (_src/text/02 Learning activities - Leeractiviteiten/03 POA - PVA/01 Literature literatuur.html.md) does not set a number or type of sources.
• Template: _src/text/02 Learning activities - Leeractiviteiten/03 POA - PVA/01 att - Control Systems - PoA Template_EN.pdf.md (Dutch: _src/text/02 Learning activities - Leeractiviteiten/03 POA - PVA/01 att - Control Systems - PvA Template_NL.pdf.md).
• Workshop (2026 version, English, binding; replaces the 2025 slides and the 2025 deliverable date of 15 September): _src/text/02 Learning activities - Leeractiviteiten/03 POA - PVA/02 att - 2026 workshop PoA.pptx.md (Dutch copy: _src/text/02 Learning activities - Leeractiviteiten/03 POA - PVA/02 att - 2026 workshop PvA_NL.pptx.md).
  • Goal: the workshop is the basis for all later projects including internship and graduation; afterwards you know what a PoA is for, what it should contain and how to approach it.
  • A PoA is a roadmap: what the project is about, what is delivered, how, and what is needed; it is written clearly and unambiguously, and it is not static (designs evolve, so does the PoA). Design paradox: the more we know the less we can change, and the later the change the higher the cost.
  • Section guidance: assignment description in your own words, check that what you think the client asks is what was asked, state boundaries (what you will and will not do); problem definition reached via the literature (how it was approached in the past); project goal = preferred outcome and what you deliver, manage expectations; individual goals = what each member wants to learn, aligned within the team, and you are asked for a reflection on them at the end; team organisation = roles, responsibilities, team contract, meeting agenda and minutes; communication plan = whom, how, how often, which channel and directory; planning = Gantt chart or scrum board, deliverables, tasks, who, when, duration, interdependencies; risks = interdependencies, lead times, bottlenecks, personal vs team goals.
  • Slide outline: the long outline also lists problem definition, sustainability (materials, how acquired, end of life) and costs (people, material; budget with hours, people and material cost per task). The final slide shows the shortened outline without those three, which is the course template above.
  • Writing: brief and to the point, main vs side issues (appendices), use imagery, draw conclusions, logical order (index), the same language for the whole team.
  • Slide "Deliverable: 4th December (end of the day)": read Brightspace carefully and check the rubric; the PoA is assessed by your lecturer of PS; the "Project Description and Scope" section must clearly show that you understand the assignment; make clear agreements on how you work and what you expect from each other. The Dutch slide reads "Deadline PvA 4 December 23.59 uur".
• Grading: Graded 1–10; the final PoA grade must be at least 5.5. Rubric at the submission point. From _src/meta/dropbox.json, the rubric has two criteria:
  • Assignment description (max 70 points): template used; assignment clearly articulated; objectives precise, measurable and realistic; justification and integration with control systems; literature review supports choices.
  • Planning (max 30 points): detailed, realistic time planning with tasks assigned; task division, collaboration structure and/or quality agreement present. Not all rubric components need to be sufficient, but the final grade must be at least 5.5. Feedback and grade are published on Brightspace. No grading in weeks 52–53. Source: _src/text/02 Learning activities - Leeractiviteiten/03 POA - PVA/01 Literature literatuur.html.md (also gives the dates Fri 4 December and Fri 18 December, both 23:59, and [staff] as assessor; the Dutch half names [staff]).
• Prerequisites: Project choice; literature review; realistic planning (see group-plan.md).

Python assignment 1

Scope

Individual

Weight / P-F

P/F

Due

No Brightspace date; assessed week 48

Resit

Python assignment 1 resit

Submission point

Python assignment 1

• Scope: Individual. Weight: P/F (part of Design and project management).
• Due: No date in _src/deadlines.md (the field is "put here"); the Python timetable puts assessment 1 in week 48. Source: _src/text/02 Learning activities - Leeractiviteiten/04 Python/02 test.html.md.
• Submit at: "Python assignment 1"; resit "Python assignment 1 resit".
• Content / format: Upload your Jupyter Notebook before the deadline, then attend an oral assessment in a scheduled session and explain/modify/expand your work on the spot. Assignment 1 is the Python assignment 1.ipynb linked from _src/text/02 Learning activities - Leeractiviteiten/04 Python/01 Python assignments opdrachten.html.md.
• Grading: Rubric at the submission point with three pass/fail criteria (from _src/meta/dropbox.json): Functionality (program meets requirements and runs), Questioning (student can explain the code), Independent work (student can explain and justify choices). Overall P/F. The rubric is filled in during the demonstration with immediate verbal feedback and pass/fail; if insufficient, improve and resubmit for the resit. The earlier sentence "not all parts of the rubric need to be sufficient, but the overall rubric must be" was removed from the page in the 2026-11-12 crawl (_src/text/02 Learning activities - Leeractiviteiten/04 Python/01 Python assignments opdrachten.html.md).
• Prerequisites: Python fundamentals + GitHub (week 46); modules, packages, random and file handling; NumPy + Matplotlib (week 47). Source: _src/text/02 Learning activities - Leeractiviteiten/04 Python/02 test.html.md.

Python assignment 2

Scope

Individual

Weight / P-F

P/F

Due

No Brightspace date; assessed week 1

Resit

Python assignment 2 resit

Submission point

Python Assignment 2

• Scope: Individual. Weight: P/F (part of Design and project management).
• Due: No date in _src/deadlines.md; assessment 2 is in week 1 per the Python timetable.
• Submit at: "Python Assignment 2"; resit "Python assignment 2 resit".
• Content / format: Same pattern as assignment 1: upload the Jupyter Notebook and explain it orally. Assignment 2 follows classes, widgets and stream/frame updates (weeks 49–50).
• Grading: Same three-criterion pass/fail rubric as assignment 1.
• Prerequisites: Classes/OOP, widgets, stream/frame updates; assignment 1 passed.

Simulation

Scope

Group

Weight / P-F

70% of Design & project management

Due

2027-01-18 Mon 12:00

Resit

2027-02-01 Mon 09:00

Submission point

Simulation / Simulatie

• Scope: Group. Weight: 70% of Design and project management.
• Due: 2027-01-18 Mon 12:00. Resit: 2027-02-01 Mon 09:00. Source: _src/deadlines.md.
• Submit at: "Simulation / Simulatie"; resit "Simulation Resit / Simulatie herkansing". One group member submits a Jupyter notebook, then the group presents it in a scheduled timeslot.
• Content / format: A Jupyter notebook with a markdown cell (text and equations) before every code cell and a comment on every piece of code. Two parts:
  • Time domain, excluding controller design: everything self-written; only NumPy and Matplotlib; plot the response to at least two different inputs for both the non-linear and linearised model, showing all relevant variables; compare and discuss linear vs non-linear; investigate time-step size; investigate sensitivity to constants (mass, length, friction) and initial conditions.
  • s domain, including controller design: packages such as the Python control library allowed; derive and implement the plant transfer function, the controller transfer function and the closed-loop transfer function; give a closed-loop time-domain step response for at least three meaningfully different initial conditions; make and explain a pole-zero plot; explain under/over-damping, rise time, overshoot and settling time. After submission, present for 10 minutes with the notebook running on a laptop; everyone in the group must be able to explain and answer questions. Source: _src/text/02 Learning activities - Leeractiviteiten/05 Simulation - Simulatie/01 Simulation assignment Simulatie opdracht.html.md.
• Grading: Rubric at the submission point; the two rubric criteria are weighted 50 points each in _src/meta/dropbox.json (time-domain simulation; s-domain simulation including controller design). Not all rubric parts must be sufficient, but the final grade must be. Highest grade counts. To improve after the first attempt, tell [staff] so he schedules the resit.
• Prerequisites: Differential-equation model; linearisation; numerical solution; Laplace model; controller design (see group-plan.md).

Intermediate delivery

Scope

Group

Weight / P-F

P/F

Due

2027-01-15 Fri 23:59

Resit

2027-01-29 Fri 23:59

Submission point

Intermediate Project Delivery

• Scope: Group. Weight: P/F (part of Proof of concept).
• Due: 2027-01-15 Fri 23:59. Resit: 2027-01-29 Fri 23:59. Source: _src/deadlines.md.
• Submit at: "Intermediate Project Delivery"; resit "Intermediate Project Delivery resit". The delivery itself is a session in week 2 with several project groups.
• Content / format: The mechanical system must be ready and working; electrical components need not be present or working. During the session the group gives and receives feedback with fellow groups and receives coach feedback. Pass requirements: mechanical system well designed and finished, everyone in the group present, active feedback given and received. Source: _src/text/02 Learning activities - Leeractiviteiten/07 Project deliveries - Project opleveringen/01 Intermediate delivery.html.md.
• Grading: P/F. Resit during the project meeting with the coach in week 3 or 4, additionally requiring documentation of feedback from at least two other groups and a plan for using it.
• Prerequisites: PoA; mechanical build (build setup).

Test plan / test protocol

Scope

Group

Weight / P-F

10% of Proof of concept

Due

2027-01-22 Fri 23:59

Resit

2027-02-05 Fri 23:59

Submission point

Testplan

• Scope: Group. Weight: 10% of Proof of concept.
• Due: 2027-01-22 Fri 23:59. Resit: 2027-02-05 Fri 23:59. Source: _src/deadlines.md.
• Submit at: "Testplan"; resit "Testplan resit". A session in week 3 is used to share the plan and any protocols in class (class split into ELV2-2A+B and ELV2-2C+D halves).
• Content / format: Every group delivers a test plan and, if already available, protocols for the specific tests. Use the template based on the graduation-report template. A test plan defines the product and objectives, the criteria/requirements, how the product is tested in detail, how data are analysed, the schedule and task division, and the deliverables; a protocol gives the step-by-step test procedure. Sources: _src/text/02 Learning activities - Leeractiviteiten/07 Project deliveries - Project opleveringen/03 Test protocol.html.md, _src/text/02 Learning activities - Leeractiviteiten/07 Project deliveries - Project opleveringen/03 att - Test plan and protocols template.docx.md, _src/text/02 Learning activities - Leeractiviteiten/07 Project deliveries - Project opleveringen/04 Testing.pptx.md.
• Template: _src/text/02 Learning activities - Leeractiviteiten/07 Project deliveries - Project opleveringen/03 att - Test plan and protocols template.docx.md.
• Grading: Pass if you submit a test plan, are present and actively participate in the delivery session. Verbal feedback is given to improve it for the final project delivery.
• Prerequisites: PoA; requirements/customer requirements; a working or planned test setup.

Final delivery

Scope

Group

Weight / P-F

50% of Proof of concept

Due

2027-02-01 Mon 09:00

Resit

2027-02-08 Mon 09:00

Submission point

Final delivery / Eindoplevering

• Scope: Group. Weight: 50% of Proof of concept (English version is binding; owner rule 2026-11-12).
• Due: 2027-02-01 Mon 09:00. Resit: 2027-02-08 Mon 09:00. Source: _src/deadlines.md.
• Submit at: "Final delivery / Eindoplevering"; resit "Final delivery Resit / Eindoplevering herkansing". One person submits all group documentation, then the complete group attends a demonstration in week 5 (resit demonstration week 6).
• Content / format: Documentation plus a working final product at the demonstration. Teachers visit all groups, ask questions, fill in the rubric, give verbal feedback and the grade. The final-delivery maximum grade depends on the chosen project: fan inverted pendulum 8, ball beam 9, Segway 10. Source: _src/text/02 Learning activities - Leeractiviteiten/07 Project deliveries - Project opleveringen/05 Final delivery.html.md and _src/text/01 Course information - Cursusinformatie/06 Project description Projectbeschrijving.html.md.
• Grading: Rubric at the submission point; not all rubric parts need to be sufficient, but the final grade must be. The rubric is filled in on the spot. If insufficient, improve and resubmit for the resit; to improve a sufficient grade, explicitly inform [staff]. Highest grade counts.
• Prerequisites: PoA → build setup → build and tune controller → closed loop system → complete system → evaluate system; test protocol; simulation; Python assignment 2 for the user interface.

Reflection

Scope

Individual

Weight / P-F

40% of Proof of concept

Due

2027-02-05 Fri 17:00

Resit

2027-02-19 Fri 17:00

Submission point

Reflection / reflectie

• Scope: Individual. Weight: 40% of Proof of concept (English version is binding).
• Due: 2027-02-05 Fri 17:00. Resit: 2027-02-19 Fri 17:00; the meeting with the coach must be finished by the end of week 7. Source: _src/deadlines.md.
• Submit at: "Reflection / reflectie"; resit "Reflection Resit / reflectie Herkansing". The page also states the reflection is due 24 hours before your final coaching session, not at the end of the week (Brightspace calendar description in _src/meta/calendar.json).
• Content / format: A critical self-reflection of approximately half a page, submitted and brought to the final coaching session. Individual contributions are discussed there. Source: _src/text/02 Learning activities - Leeractiviteiten/07 Project deliveries - Project opleveringen/07 Reflection Reflectie.html.md.
• Grading: Rubric at the submission point. An insufficient written reflection → F. If sufficient, the group decides with the coach who is above/below average; the average of all reflection grades equals the group's final-delivery grade (individual adjustments, e.g. ±2, keep the average). Not all rubric parts need to be satisfactory but the final grade must be.
• Prerequisites: Final delivery grade (the reflection is anchored to it); individual goals from the PoA.

Practicals (pre/post assessments)

Scope

Individual

Weight / P-F

P/F

Due

Completed before 2027

Resit

Resit session week 4

Submission point

Pre/post quizzes; Assignment submission (LT Spice)

• Scope: Individual. Weight: P/F (part of Proof of concept).
• Due: All five practicals must be finished before 2027. Resit: a scheduled "resit for missed practicals" session in week 4. Source: _src/text/02 Learning activities - Leeractiviteiten/06 Practicals - Practica/01 Practical instruction practicum instructie.html.md.
• Submit at: the pre/post-assessment quizzes in Brightspace; the LT Spice results also have an "Assignment submission" point, and the analogue-PID practical asks you to upload your completed practical document. Quiz names are listed in practicals.md.
• Content / format: For each practical, complete the pre-assessment before the session, attend and actively participate, complete the tasks, and pass the post-assessment. The post-assessment may be retaken as often as needed. Attendance/participation plus a pass on the post-assessment gives a pass for that practical. All five practicals must pass.
• Grading: P/F per practical; pass only with attendance/participation checked off and a passing post-assessment. "Practicals 100%? 1 → Pass, 0 → Fail" (kickoff slides, _src/text/01 Course information - Cursusinformatie/02 att - kickoff control systems 2026 - 2027.pptx.md).
• Prerequisites: See each practical in practicals.md; for analogue PID, the PCB must be assembled before the session.

Exams

Modelling digital test

Scope

Individual

Weight / P-F

100% of Modelling theory

Due

2026-12-15 Tue

Resit

2027-01-18 Mon

Submission point

ANS

Control systems digital test

Scope

Individual

Weight / P-F

100% of Control systems theory

Due

2027-01-27 Wed

Resit

2027-02-19 Fri

Submission point

ANS

• Modelling digital test: individual, 100% of Modelling theory, ANS, 2026-12-15 Tue, resit 2027-01-18 Mon. Learning outcomes 1–8; formula sheet and example exam available. Source: _src/text/02 Learning activities - Leeractiviteiten/01 Modelling - Modellering/01 Testing modelling.html.md.
• Control systems digital test: individual, 100% of Control systems theory, ANS, 2027-01-27 Wed, resit 2027-02-19 Fri. Learning outcomes 1–9; formula sheet and practice exam available. Source: _src/text/02 Learning activities - Leeractiviteiten/02 Control systems - Regeltechniek/02 Testing control systems Toetsing regeltechniek.html.md.
• Both are taken on Hanze computers at the exam centre; see assessment.md for aids and pass rules.

How grading works

The course is split into four subcodes in Osiris. All four must be passed (grade 5.5 or higher); the subcode grades remain valid after the course ends. Source: _src/text/01 Course information - Cursusinformatie/03 Untitled - Copy (11).html.md.

Printed final-grade formula (verbatim):

G = 2·M + 3·C + 5·D + 5·P

The page does not show a division by 15 (the sum of the weights), although that is what a weighted average would require; see Open questions. The Dutch copy uses R (Regeltechniek) and O (Ontwerp) for C and D but is otherwise the same.

Source for the composition: _src/text/01 Course information - Cursusinformatie/03 Untitled - Copy (11).html.md and _src/text/01 Course information - Cursusinformatie/02 att - kickoff control systems 2026 - 2027.pptx.md.