Paton Hall

Paton Hall — Training

Status: Working document. Planning record, not a commitment. EPTAC relationship: in conversation. Nothing signed (PH-032) — every course, cohort and date in this document is intent until that changes. Speculative sections are fenced and marked as such. Compiled: 2026-08-11 Purpose: The whole training programme in one place — from build-night curiosity to IPC certification — with each part written at the strength it can carry. Companion to: 00-repository.md, whose §7 is the summary this document expands and whose §13 is the register that governs it.

0. How to read this document

  • Point form throughout. Density over polish. Same house rules as 00-repository.md §0.
  • Sections 1–9 are the programme. §10 is links. The sections run in order of increasing warrant: what the Hall can do today, then what it intends to do, then what only IPC can do.
  • Load-bearing claims carry an ID (PH-056) and a status. The register in 00-repository.md §13 governs. Where the register and the tone of a sentence here disagree, the register wins.
  • A fence marks a section as direction rather than claim. It opens with a blockquote beginning "Direction, not commitment." and runs to the end of that section.
  • Nothing inside a fence carries an ID.
  • Nothing inside a fence should be quoted as a plan, a costing or a promise.
  • A fenced section is not weaker evidence. It is not evidence. It is the shape of a thing that has not been built yet.
  • The words certified, certification and credential mean IPC in this document and nothing else. Informal instruction is described as attested, completed, built or shown.
  • Both rules are checked mechanically by scripts/check_training.py rather than by careful reading, because careful reading is exactly what fails on a long document.

1. Why training is the spine, and the Hamilton gap

  • Open nights, build nights and learning days build a membership. Training builds standing with employers. Those are different audiences, and only one of them signs a purchase order.
  • Certified training generates trust with industry faster than any amount of community programming. The reasons are set out in 00-repository.md §7.1 and are not repeated here: the credential is externally standardised, it is what the electronics industry actually checks for, it is directly useful to Hamilton-area plant operators, and it is fundable under PH-009 / PH-010.
  • The consequence for this document: the programme is arranged by who warrants each rung, not by subject matter or difficulty. That is the axis an employer reads on, so it is the axis §2 sets out before anything else.

1.1 Where the training currently is

  • PH-056 As of August 2026, EPTAC operates 24 North American locations, three of them Canadian: Markham, Ottawa and Halifax. Location counts move; this one is dated because it will need re-checking, not because it is doubted.
  • PH-057 The nearest EPTAC facility to Hamilton is EPTAC Corporation of Canada, 590 Alden Road Suite 204, Markham, ON L3R 8N2 — roughly 70 km, across the top of the GTA. There is no EPTAC facility in Hamilton.
  • The arithmetic that follows, and no more than the arithmetic: a Hamilton plant sending four people to a four-day course is paying for sixteen person-days of travel on top of tuition.
  • That is the entire gap, stated plainly. It is not a claim about demand, about willingness to pay, or about what any particular employer will decide to do. It is a distance and a course length.
  • 12-onepager-industry.md makes this argument in the abstract — travel, hotels, days off the floor. The two claims above are the concrete version, and they are the form to use when someone asks what "out of town" actually costs.
  • None of this is an EPTAC commitment to Hamilton. PH-032 stands unchanged: in conversation, nothing signed. A gap in coverage is an argument for the room; it is not an agreement to fill it.

2. Recognition

Read this before any of the rungs. It says what each one yields, which is the only thing a learner or an employer needs settled before deciding whether a rung is worth the time.

  • The ladder is continuous in subject and distinct in warrant. A learner moves through soldering, boards, microcontrollers and industrial systems without changing topic. What changes is who stands behind the record at the end.
  • The line falls between attestation and certification. Below it, a named human vouches. Above it, an external standard does, and the Hall's opinion is irrelevant.
Tier What it is Who warrants it What it is called
Artifact The thing you built, shown at a demo night Self-evident — it works or it does not "Show what you built"
Attestation A named instructor records that a learner completed a sequence, and what it covered A specific person, by name "Attested by —"
Certification IPC-A-610, CID, J-STD-001 and the rest IPC, delivered by EPTAC "IPC-certified"
  • The Hall can issue the first two today, with no partner and no permission and no capital. It can never issue the third, and says so wherever it says anything.
  • Attestation is deliberately weaker than a credential, and the weakness is the design, not a shortfall waiting to be fixed. It is one person's word and it says so on its face: a name, a date, the sequence completed, and what that sequence covered.
  • Why one person's word is worth anything: a controls engineer with thirty years in Hamilton plants, recording that someone completed the industrial-systems sequence and built a working panel, is worth something to a local employer because it does not pretend to be a standard. The employer knows exactly what they are reading — one experienced person's assessment, attributed to someone named. A house certificate dressed up as a standard would be worth less than that, and would cost the Hall the one thing it cannot buy back.
  • The commitment, restated verbatim from 12-onepager-industry.md and unchanged here: "Graduates are IPC-certified. We do not blur, substitute for, or rebrand that credential."
  • The working test applied to every line of §3 onward: if a sentence about informal instruction could be misread as a certification claim, it is written wrong. The checker catches the vocabulary. The judgement stays ours.

3. Entry — build nights and the open bench

The bottom rung, and the only one that already exists.

  • PH-054 Build nights provide floor, power, benches and hours for physical work — wrenching, robotics, assembly and test. Members supply their own tools.
  • No curriculum, no enrolment, no sequence. Someone turns up with a thing that does not work yet.
  • What it yields is an artifact, and nothing else. That is the whole of the recognition at this rung, and it is enough: the thing either runs or it does not.
  • The bay door is the practical difference from every other room in the city. A rig, a robot or a pallet comes straight in off the drive. A second-floor coworking space cannot make that offer at any price.
  • This rung is the intake for every rung above it. Nobody arrives at the Hall intending to sit an IPC exam. They arrive with a project.

4. Enthusiast — microcontrollers and the physical layer

Direction, not commitment. Nothing in this section is a claim, a costing or a promise. It is the shape of the thing we think is worth building.

Single evenings, each led by someone from the region who already does the work for a living or for love.

  • Boards and toolchains. Getting a first microcontroller doing something real — clock, I/O, a flashing light that means something. The evening ends with the board on the bench doing the thing.
  • Sensors and signal conditioning. Reading the physical world: what a raw sensor output actually looks like, why it is noisy, and what has to happen to it before a processor can use it.
  • Motor control. The evening where a microcontroller stops being a small computer and starts being machinery. Drivers, current, heat, and what happens when a stall goes unnoticed.
  • Power, enclosure and mechanical fit. Why a bench prototype fails on a plant floor — vibration, dust, temperature, supply that is not clean, and a housing that has to survive being stepped on.
  • Bring-your-own-project clinics. No syllabus. People bring what is stuck and the room unsticks it.

What a learner takes away:

  • The thing they built, which they can show at a demo night.
  • If they worked through a sequence rather than a single evening, an attestation from the instructor who taught it, naming what was covered.

The offer to a prospective teacher, stated plainly: one evening, your subject, our floor, our people, your name on it. No fee to you and no fee from you. If it goes well, do it again.

5. Structured — industrial systems

Direction, not commitment. Nothing in this section is a claim, a costing or a promise. It is the shape of the thing we think is worth building.

Where the hobby layer turns into what the plants in this city actually run. Taught as a sequence over several evenings rather than as one-offs, because this is the rung that produces capability an employer can use.

  • PLCs and ladder logic, set beside embedded C. Deliberately taught together. A learner sees the same job written in two dialects and understands why industry chose the one it did. Most teaching material presents these as separate worlds; on a plant floor they sit two cabinets apart.
  • Fieldbus and industrial protocols. Modbus, CAN and EtherCAT — what each was built for, where each is actually found, and how to get a device talking on a bus somebody else specified.
  • The 4–20 mA current loop and the measurement layer. Why industry standardised on current rather than voltage, what a live loop tells you that a data sheet does not, and how a broken sensor announces itself.
  • Panel building and I/O wiring. Terminations, labelling, segregation, and the difference between a panel that passes inspection and one that merely works.
  • Safety and interlocks. Treated as design rather than as a compliance chore appended at the end.

What a learner takes away:

  • A working panel or rig, built by them.
  • An attestation naming the sequence completed and what it covered.

This is the rung where an attestation carries the most weight, and the reason is local rather than technical: a named controls engineer with thirty years in Hamilton plants is exactly the person a Hamilton employer would have asked anyway.

6. Certified — the EPTAC and IPC pathway

PH-032 governs everything in this section: EPTAC relationship status is in conversation, nothing signed. Every course, price, cohort and date below is intent. None of it is an agreement, and none of it should be repeated to an employer as one.

6.1 The catalogue, and what the room can hold

Durations and levels as published by EPTAC, verified August 2026. Where EPTAC does not publish a duration, this table says so rather than estimating.

Course Standard Duration Levels Room
IPC-A-610 IPC-A-610 4 days CIS, CIT, CSE, recert Fits today
IPC Designer (CID) IPC-2221 / IPC-2222 4 days (3 lecture, 1 review and test) CID Fits today
IPC Advanced Designer (CID+) IPC-2221 / IPC-2222 4 days CID+ Fits today
Interactive Inspection Lab IPC-A-610 1 day Knowledge-based Fits today
IPC-A-600 IPC-A-600 not published CIS, CIT, CSE, recert Unverified — see §9
J-STD-001 J-STD-001 Instructor 5 days; Specialist not published CIS, CIT, CSE, recert Needs benches
J-STD-001 Aerospace J-STD-001 Aerospace 1 day CIS, CIT, recert Needs benches
Hand Soldering Certification J-STD-001 Variable, modular CIS Needs benches
Advanced Micro SMT Hand Soldering J-STD-001 2 days Skill-based Needs benches
IPC-7711/7721 IPC-7711/7721 5 days CIS, CIT, CSE, recert Needs benches
IPC-A-620 IPC-A-620 4 days CIS, CIT, CSE, recert Needs benches
Hands-On Cable Wire Harness Lab IPC-A-620 1 day Skill-based Needs benches

Four courses fit the room as it stands, not one. 00-repository.md §7.2 originally named IPC-A-610 alone. That was incomplete rather than wrong, and the correction is recorded there.

IPC-A-600 is marked Unverified deliberately. It is bare-board inspection, so it is plausibly classroom-suitable on the same reasoning as A-610 — but plausibly is not a basis for a row in this repository. It sits in §9 until EPTAC confirms.

6.2 The design credential

  • PH-058 CID stands for Certified Interconnect Designer, an IPC Designers Council credential, delivered by EPTAC under the course name "IPC Designer Certification".
  • PH-059 The CID exam is built on IPC-2221 and IPC-2222 — design rules, material selection, layer stackup, component placement, hole-to-copper clearances, and manufacturable design practice.
  • PH-060 CID is a prerequisite for CID+. The advanced tier cannot be taken first.
  • PH-061 Neither CID nor CID+ expires, and neither requires recertification.
  • PH-062 CID suits designers with roughly two years of hands-on PCB design experience. EPTAC guidance, not a hard prerequisite.

Two consequences worth stating:

  • No renewal cost changes the funding conversation. PH-031 puts recertification for the A-610 and J-STD-001 family at 60–70% of initial. A credential that never expires is a single line in a training budget rather than a recurring one, and that is easier for an employer to approve.
  • The two-year expectation is what joins §5 to §6. CID sits at the top of the informal track, not at its entrance. Someone who came up through microcontroller evenings and the industrial-systems sequence is approaching the profile CID assumes. That is the ladder closing, and it is the reason this document treats informal instruction and certification as one programme rather than two.

6.3 Money

  • PH-031 Market reference pricing: IPC-A-610 CIS roughly $700–1,200 per student; combined A-610 and J-STD-001 packages $1,400–2,300; recertification at 60–70% of initial; team and on-site programmes from approximately $10,000.
  • EPTAC does not publish CID pricing. It is not estimated here. See §9.
  • Cohort economics, the hosted-trainer launch model and the per-seat-versus-room-fee question are set out in 00-repository.md §7.3 and not repeated.
  • The funding position is in 12-onepager-industry.md and governed by PH-009 / PH-010: the Ontario Job Grant and Skills Development Fund mean the employer often is not paying out of pocket. Verify current intake before citing any of it to a client.

7. Advanced — the bench roadmap

The hands-on certifications are gated by the room, not by willingness.

  • What gates them: ESD control, fume extraction, and specific insurance. A working manufacturer's floor handles these as a matter of course; a general-purpose community room does not. Set out in 00-repository.md §7.2.
  • PH-033 Indicative capital for a teaching-grade bench cell: $10,000–25,000 — ESD bench and matting, inspection microscope, professional irons and hot-air stations, portable fume extraction, test gear, and a camera-and-display rig.
  • PH-034 Comparators: a 20-station institutional lab runs $100,000–300,000+; recently funded mobile training labs run $500,000–1,200,000. A single well-built bench is roughly 20–50× cheaper and teaches the same standard.
  • The dual use is the argument. The bench is not a training cost centre waiting on a signed contract. It is a member benefit on build nights and a teaching instrument during certification, and it earns its keep on the first of those whether or not the second ever arrives.
  • Tenure constrains the build. Mats rather than flooring, portable extraction rather than ducted, knock-down frames. Costs slightly more and preserves the whole investment when the address changes. See 00-repository.md §4.3.
  • The camera-and-display rig deserves its own line: it converts one bench into a room-scale teaching instrument, so one trainer demonstrates to a full seminar rather than four people crowding a microscope.

8. The instructor question

The bottleneck has the same shape at both ends of the ladder, and it is people rather than equipment.

8.1 The certified end

  • PH-035 The constraint on training capacity is certified instructors, not equipment or rooms.
  • The Certified IPC Trainer (CIT) path is the multiplier. Each CIT credential in the building expands what can be delivered without a partner supplying an instructor.
  • Securing or sponsoring a CIT is the highest-leverage single investment available to the Hall. It belongs in Phase 2 as a named priority rather than being discovered late.

8.2 The informal end

Direction, not commitment. Nothing in this section is a claim, a costing or a promise. It is the shape of the thing we think is worth building.

  • Who they are. The retired controls engineer who still reads the standards. The working PLC specialist between contracts. The embedded hobbyist with a day job and a basement bench better than most labs. Hamilton has these people. It does not currently have a room that asks them for an evening.
  • What the Hall offers them. A floor, an audience that wants to be there, and their name on what they taught.
  • What the Hall owes them. Not overstating what their evening was. An attestation carries a person's name, and a room that inflates what it hands out is spending someone else's reputation.
  • The recruiting problem is the retention problem. One evening is easy to say yes to. A sequence is a real commitment, and the sequences are where the value is. That gap is not solved yet.

9. What we do not know

These are things EPTAC does not publish. They are recorded as questions rather than filled with plausible numbers, and nothing in this section carries an ID because none of it is a claim.

  • Facility requirements for hosting a certified trainer — room, seating, AV, insurance.
  • Minimum and maximum class sizes for a hosted cohort.
  • Commercial terms for hosting — per-seat share, room fee, or another structure entirely.
  • Whether CID can be hosted on the same terms as A-610. Both are classroom courses, but that does not mean they carry the same arrangement.
  • CID and CID+ pricing. Not published. Not estimated here.
  • What EPTAC requires of a host that is not itself a manufacturer. Every hosting arrangement described publicly involves a plant. The Hall is not one.
  • Whether IPC-A-600 fits the room without build-out. Bare-board inspection suggests it does, on the same reasoning as A-610. It has not been confirmed.

The route to answers is EPTAC's customized-training intake, sales@eptac.com, or 1-800-643-7822. Asking costs nothing and would close most of this section.

10. Links

EPTAC — the organisation

EPTAC — courses that fit the room today

EPTAC — courses that need the bench roadmap

Standards and credentials

Funding

Verify current intake before citing any of this to a client. Programme windows move.

The informal half — primary sources for §4 and §5

Governing bodies and vendor documentation only. Blogs, forums and aggregators are deliberately excluded, however good.

Microcontroller platforms

Industrial protocols and fieldbus

PLC and controls

Measurement layer and standards

11. Working notes

How this document was arrived at, kept in the open on the same principle as the claims register: the reasoning is published, not just the conclusion. These are process records rather than reader-facing material, and nothing in them overrides §0–§10.

  • Handoff notes — current state, the two integrity rules and how to run them, and the seven questions still open with EPTAC. Start here if you are picking this up.
  • Design spec — the decisions behind the structure: why speculation is fenced, why recognition comes before the rungs, and why the CID correction was made as a correction rather than a quiet amendment.
  • Implementation plan — the task-by-task build, including the checker's source and the link-verification results.

The checker itself is at scripts/check_training.py. It is the reason the two rules in §0 are enforced rather than merely stated.

← All documents