Technical Services

Technical services support design, building, testing and upkeep of systems, such as drawings, inspections, equipment and software tools.

• Terms: specification, drawing, tolerance, standard, test, fault, maintenance, documentation.
• A specification says what a thing must do and how well.
• Tolerance is the allowed difference from a target size.
• Read one simple drawing or data sheet and list its key details.
• Know the common units: millimetres, metres, volts, amps, kilograms, degrees Celsius.
• Learn the difference between a drawing, a data sheet and a manual.
• List the tools in your field and say what each measures.

Activity. Read one data sheet or drawing and write a list of ten key facts with units.

Standard to meet. Task: extract key facts. Condition: one simple drawing or sheet. Standard: ten facts with correct units and terms.

Technical jobs need planning, method and records.

• Steps: understand the need, plan, prepare, do, test, document, hand over.
• Write the method step by step with safety checks.
• Version your documents so everyone uses the latest one.
• Record what was changed, when and by whom.
• Write down the need in one sentence and confirm it with the client before you start.
• List the tools, parts and safety gear before the job, not during it.
• Hand over with a short summary of what was done and what to check next.

Activity. Write a method for a simple task, such as testing a circuit or checking a measuring tool.

Standard to meet. Task: write a step-by-step method. Condition: for one simple task. Standard: another person can follow it, with safety steps and a record sheet.

Reliable measures and clear records are the heart of technical work.

• Use the right tool and check that it is calibrated.
• Compare measured values with the specification and mark pass or fail.
• Repeat tests if the result is close to the limit.
• Write the result with units, date, tool used and your initials.
• Take the reading at the same place and in the same way each time.
• Mark each result pass, fail or recheck, and say why.
• Keep the failed parts apart so no one uses them.

Activity. Test ten items against a specification and write a test report.

Standard to meet. Task: complete a test report. Condition: with calibrated tools. Standard: all results with units, pass or fail marked correctly, and a clear conclusion.

Technical work is often regulated for public safety.

• Engineering work that affects public safety is regulated by provincial engineering bodies. Do not offer work or titles you are not licensed for. Check with the provincial body.
• Technologists and technicians can have their own certification routes. Check what employers accept.
• Electrical, gas, pressure and building work follow codes and may need permits and licensed workers. Check the current rules.
• Workplace safety rules apply to all sites and labs, including lockout and protective gear.
• Ask the provincial body what work needs a licensed person and what a technician may do under supervision.
• Check which codes and standards apply to your type of work and where to read them.
• Write the steps of lockout for your equipment and practise them.

Activity. Build a rules table for the type of technical work you plan to do.

Standard to meet. Task: build a rules table. Condition: official pages only. Standard: each row has enforcer, action and date checked; scope limits are written clearly.

Diagnose before you fix. A guess costs time and money.

• Describe the symptom clearly: what, when and how often.
• List possible causes and test the easiest first.
• Change one thing at a time and retest.
• Record the cause, the fix and how you proved it worked.
• Check power, connections and settings before you open a device.
• Write down what was tried, in order, so you do not repeat a step.
• Ask the user to show the fault, so you see it yourself.

Activity. Diagnose and fix a staged fault in a practice kit and write a fault report.

Standard to meet. Task: complete a fault report. Condition: practice equipment, supervised. Standard: symptom, tests, cause, fix and retest result are all recorded.

Technical work must be priced for time, tools, risk and follow-up.

• List tasks, hours, parts, travel, tools, insurance and a buffer for rework.
• Price per hour, per job or per test, and use the method that fits the work and the client.
• Track actual hours against your estimate.
• State the warranty and what it does not cover in writing before the job starts.
• Add the time to travel, set up and write the report to your hours.
• Set a rule for extra work: it is quoted and agreed before it is done.
• Keep records of tools and calibration costs as part of your overhead.

Activity. Build an estimate and cost sheet for one job, then compare to the actual hours.

Standard to meet. Task: estimate and track a job. Condition: for a real or practice job. Standard: units shown, formulas visible, difference between estimate and actual explained.

Mistakes can harm people and cost money. Build habits that catch them early.

• Use checklists and second-person checks for critical steps.
• Keep a risk register: wrong measure, missed standard, tool failure, data loss, injury.
• Protect drawings and client data with backups and access limits.
• Report incidents and near-misses so they can be fixed.
• Name one person who checks each critical step.
• Rate each risk for chance and harm, and start with the highest.
• Review the register after each job and add anything new.

Activity. Write a risk register of eight rows and a one-page quality plan.

Standard to meet. Task: write a risk register and quality plan. Condition: reviewed by a mentor. Standard: each risk has control, owner and review date.

Run a small real service and decide how to grow.

• Pilot for 30 to 60 days with clear scope and a stop rule.
• Track hours, errors, rework, client feedback and income.
• Write a handover pack so another person could maintain your work.
• Plan the next 12 months: training, tools and licensing steps.
• Pick one client type and one service for the pilot.
• Ask the client to sign off the scope and results at the end.
• List the tools and training you need to buy or learn next.

Activity. Run the pilot, write the review and the plan, and present to a panel of three.

Standard to meet. Task: run a technical service pilot. Condition: within your licence and safety rules. Standard: records complete, rework measured, decision supported by numbers.

L1: Practice aware learner. You can define: name the main terms, people and rules of technical Services. Focus module: Know the words and fields of technical services (Understand, 6 h). Technical services support design, building, testing and upkeep of systems, such as drawings, inspections, equipment and software tools. Key points: Terms: specification, drawing, tolerance, standard, test, fault, maintenance, documentation. A specification says what a thing must do and how well. Tolerance is the allowed difference from a target size. Read one simple drawing or data sheet and list its key details. Know the common units: millimetres, metres, volts, amps, kilograms, degrees Celsius. Learn the difference between a drawing, a data sheet and a manual. List the tools in your field and say what each measures.

Speaker notes. Teach: open with the worked example. A part must be 50 mm long with a tolerance of plus or minus 0.2 mm. Anything from 49.8 to 50.2 passes, a range of 0.4 mm. A part of 50.3 mm is 0.1 mm over the top limit and fails. Then set the activity: Read one data sheet or drawing and write a list of ten key facts with units. Mark against the standard: Task: extract key facts. Condition: one simple drawing or sheet. Standard: ten facts with correct units and terms. Check at this level: What is a specification? Model answer: A statement of what a thing must do and how well. Level note: Start here if new. Evidence: a one-page glossary and a visit or interview note.

L2: Assistant. You can describe: explain how technical Services works from first contact to result. Focus module: Explain how a technical job is planned and done (Apply, 6 h). Technical jobs need planning, method and records. Key points: Steps: understand the need, plan, prepare, do, test, document, hand over. Write the method step by step with safety checks. Version your documents so everyone uses the latest one. Record what was changed, when and by whom. Write down the need in one sentence and confirm it with the client before you start. List the tools, parts and safety gear before the job, not during it. Hand over with a short summary of what was done and what to check next.

Speaker notes. Teach: open with the worked example. Change log: 'v2, 12 March, replaced sensor type, retested, results attached, signed by JT.' If a project has versions v1 to v5, there are 5 - 1 = 4 changes recorded after the first issue. Then set the activity: Write a method for a simple task, such as testing a circuit or checking a measuring tool. Mark against the standard: Task: write a step-by-step method. Condition: for one simple task. Standard: another person can follow it, with safety steps and a record sheet. Check at this level: Why version documents? Model answer: So everyone uses the latest one and changes are traceable. Level note: Evidence: a flow chart and a two-minute spoken explanation.

L3: Associate. You can apply: carry out a routine task in technical Services to a written standard. Focus module: Measure, test and document to a standard (Apply, 10 h). Reliable measures and clear records are the heart of technical work. Key points: Use the right tool and check that it is calibrated. Compare measured values with the specification and mark pass or fail. Repeat tests if the result is close to the limit. Write the result with units, date, tool used and your initials. Take the reading at the same place and in the same way each time. Mark each result pass, fail or recheck, and say why. Keep the failed parts apart so no one uses them.

Speaker notes. Teach: open with the worked example. Measured 50.3 mm against a limit of 50.2 mm: fail. Repeat gives 50.3 again. Report: part rejected, cause to be checked. If 2 of 10 parts fail, the fail rate is 2 / 10 = 20 percent. Then set the activity: Test ten items against a specification and write a test report. Mark against the standard: Task: complete a test report. Condition: with calibrated tools. Standard: all results with units, pass or fail marked correctly, and a clear conclusion. Check at this level: Why calibrate tools? Model answer: So measurements can be trusted. Level note: Evidence: a supervised task record that meets the standard once.

L4: Practitioner. You can analyse: diagnose why a technical Services result missed its target and fix it. Focus module: Know who may do what: licences, standards and safety (Evaluate, 8 h). Technical work is often regulated for public safety. Key points: Engineering work that affects public safety is regulated by provincial engineering bodies. Do not offer work or titles you are not licensed for. Check with the provincial body. Technologists and technicians can have their own certification routes. Check what employers accept. Electrical, gas, pressure and building work follow codes and may need permits and licensed workers. Check the current rules. Workplace safety rules apply to all sites and labs, including lockout and protective gear. Ask the provincial body what work needs a licensed person and what a technician may do under supervision. Check which codes and standards apply to your type of work and where to read them. Write the steps of lockout for your equipment and practise them.

Speaker notes. Teach: open with the worked example. Rules table row: 'Structural design sign-off | provincial engineering body | needs a licensed engineer | before drawings are issued | stamped drawing on file'. If sign-off takes 2 weeks and drawings are due on week 5, request it by week 3 at the latest. Then set the activity: Build a rules table for the type of technical work you plan to do. Mark against the standard: Task: build a rules table. Condition: official pages only. Standard: each row has enforcer, action and date checked; scope limits are written clearly. Check at this level: Who regulates engineering work in Canada? Model answer: Provincial engineering bodies; check yours. Level note: Evidence: a fault or gap analysis with a fix and a repeat test. This course targets this level.

L5: Senior practitioner or team lead. You can evaluate: judge options for technical Services against cost, risk and quality. Focus module: Price technical work and manage a job (Create, 6 h). Technical work must be priced for time, tools, risk and follow-up. Key points: List tasks, hours, parts, travel, tools, insurance and a buffer for rework. Price per hour, per job or per test, and use the method that fits the work and the client. Track actual hours against your estimate. State the warranty and what it does not cover in writing before the job starts. Add the time to travel, set up and write the report to your hours. Set a rule for extra work: it is quoted and agreed before it is done. Keep records of tools and calibration costs as part of your overhead.

Speaker notes. Teach: open with the worked example. An example price of 150 CAD per hour for 20 hours is 3,000 CAD. Cost is 35 per hour, so 20 x 35 = 700. Margin is 3,000 - 700 = 2,300, which is 115 per hour. If rework adds 3 hours at your cost, the margin falls by 3 x 35 = 105. Teaching figures only. Then set the activity: Build an estimate and cost sheet for one job, then compare to the actual hours. Mark against the standard: Task: estimate and track a job. Condition: for a real or practice job. Standard: units shown, formulas visible, difference between estimate and actual explained. Check at this level (this question is covered in module 2: Explain how a technical job is planned and done): Why version documents? Model answer: So everyone uses the latest one and changes are traceable. Level note: Evidence: an options paper with numbers and a recommendation defended to a panel.

L6: Practice or programme head. You can create: design and pilot a new offer or process in technical Services. Focus module: Manage risk, quality and client data (Evaluate, 6 h). Mistakes can harm people and cost money. Build habits that catch them early. Key points: Use checklists and second-person checks for critical steps. Keep a risk register: wrong measure, missed standard, tool failure, data loss, injury. Protect drawings and client data with backups and access limits. Report incidents and near-misses so they can be fixed. Name one person who checks each critical step. Rate each risk for chance and harm, and start with the highest. Review the register after each job and add anything new.

Speaker notes. Teach: open with the worked example. A near-miss: a wrong drawing version was used. Fix: old versions moved to an archive folder and the latest marked on the cover. If the team had 12 drawings in use and 3 were out of date, 3 / 12 = 25 percent were wrong, so the archive step is worth the effort. Then set the activity: Write a risk register of eight rows and a one-page quality plan. Mark against the standard: Task: write a risk register and quality plan. Condition: reviewed by a mentor. Standard: each risk has control, owner and review date. Check at this level: What goes in a risk register? Model answer: Risk, likelihood, harm, control, owner and review date. Level note: Evidence: a pilot with measured results over at least 30 days.

L7: Partner or director. You can lead: run a team or business in technical Services and develop others. Focus module: Run a technical service for real and grow (Create, 8 h). Run a small real service and decide how to grow. Key points: Pilot for 30 to 60 days with clear scope and a stop rule. Track hours, errors, rework, client feedback and income. Write a handover pack so another person could maintain your work. Plan the next 12 months: training, tools and licensing steps. Pick one client type and one service for the pilot. Ask the client to sign off the scope and results at the end. List the tools and training you need to buy or learn next.

Speaker notes. Teach: open with the worked example. Stop rule: 'If rework passes 15 percent of hours, pause new jobs and fix the method.' On 100 hours worked, 15 percent is 15 hours. If rework takes 18 hours, it is 18 percent and the rule is triggered. Then set the activity: Run the pilot, write the review and the plan, and present to a panel of three. Mark against the standard: Task: run a technical service pilot. Condition: within your licence and safety rules. Standard: records complete, rework measured, decision supported by numbers. Check at this level (this question is covered in module 7: Manage risk, quality and client data): Why report near-misses? Model answer: They show problems before someone is hurt. Level note: Evidence: a record of results over a year and of people you have coached to a higher level.