Lesson 1Approval and planning: authorisation rules, estimated labour, parts and toolsSee how approval and planning in Coswin 8i use auth rules, labour guesses, and parts/tools plans to release only needed work and save resources well.
Configuring approval levels and rolesBudget, cost center and capex checksEstimating labor hours and skill levelsPre‑planning parts, tools and servicesStatus codes for planning and approvalLesson 2Work order creation: mandatory fields (asset, priority, requestor, description)Learn setting must-fill fields for new work orders in Coswin 8i, like asset, priority, asker, and details, so planning, scheduling, and doing teams get full, solid info.
Default values and auto‑population rulesValidating asset and location referencesPriority matrices and risk‑based fieldsCapturing requester and contact channelsStandardizing problem descriptions and titlesLesson 3Execution: on-site data capture fields (start/stop times, labour hours, downtime)Learn execution fields techs must fill in Coswin 8i, like start/stop times, labour hours, downtime, and site notes, for true costs, KPIs, and resource checks.
Recording start, stop and pause timesCapturing labor hours by person or teamLogging operational and repair downtimeDocumenting on‑site findings and risksReal‑time updates from mobile devicesLesson 4Work order classification: failure codes, symptom vs cause, standard defect listsSee classifying work orders with Coswin 8i failure codes, spotting symptoms from causes, and using defect lists so checks, KPIs, and reliability use steady data.
Designing failure, cause and remedy code setsSeparating symptom, cause and action fieldsUsing standard defect lists by asset classLinking codes to reliability and KPI reportsGovernance for adding or changing codesLesson 5Assignment: scheduling technicians, shift planning, and skill matchingLearn how Coswin 8i aids assigning and scheduling techs, with shift plans, skill/cert matches, and load balance, keeping data fields true and current.
Assigning technicians and work teamsShift calendars and availability rulesSkill, trade and certification fieldsBalancing workload across resourcesRescheduling and reassignment trackingLesson 6Audits and periodic data reviews: methods to detect bad or missing dataLearn designing audits and data reviews in Coswin 8i to spot missing, uneven, or poor work order data, and fix via dashboards, exception reports, and user tips.
Defining data quality KPIs and thresholdsBuilding exception and completeness reportsSampling work orders for manual reviewCorrecting historical data and backfillingFeedback loops and user coaching actionsLesson 7Checklist and mobile data capture: enforcing mandatory checklist completionSee Coswin 8i checklists and mobile forms forcing must-steps, full inspection notes, and techs noting all readings, measures, and confirms before close.
Creating task checklists and inspection formsDefining mandatory checklist questionsRecording readings and measurement limitsUsing mobile apps for offline data captureBlocking closure when checks are incompleteLesson 8Closure: final fields required (root cause, corrective actions, comments, downtime)See final fields to fill before closing work orders in Coswin 8i, like root cause, fixes, notes, and downtime, for checks, audits, and steady improvements.
Root cause and corrective action fieldsRecording functional and total downtimeTechnician comments and work notesVerifying checklist and test completionCustomer acceptance and sign‑off dataLesson 9Escalation and rework handling: reopen rules and nested work ordersSee Coswin 8i handling escalations, rework, and reopened orders, with rules for nested/child orders, keeping history clear and repeat faults tracked right.
Defining escalation triggers and pathsReopen rules and status transitionsCreating child and follow‑up work ordersLinking rework to original failuresReporting on repeat and chronic issuesLesson 10Ensuring data quality: validation rules, mandatory fields, dropdowns and standardised codesSee Coswin 8i enforcing data quality via check rules, must-fields, dropdowns, and standard codes, cutting free-text changes for steady, checkable upkeep records.
Field validation and conditional rulesMandatory versus optional field designDropdown lists and controlled vocabulariesStandard code tables and reference dataHandling legacy and migrated data issuesLesson 11Work request initiation: required input fields and failure reporting best practicesLearn capturing good work requests in Coswin 8i, set must-inputs, and structure fault details so planners/techs get clear, doable info for right diagnosis and priority.
Configuring mandatory request header fieldsCapturing location, asset and requester detailsWriting clear problem and symptom descriptionsAttaching photos and documents to requestsUsing request templates for recurring issuesLesson 12Parts consumption and serial-tracking: parts issued, batch/lot numbers, quantity usedSee Coswin 8i noting parts use and serial tracking on orders, with issued amounts, batch/lot numbers, and serial parts, for tracking, costs, and stock control.
Issuing parts directly to work ordersRecording quantity, unit and cost dataCapturing batch, lot and expiry detailsTracking serialized components by assetReconciling stock and work order usageLesson 13Testing and validation: acceptance criteria and functional test recordsSee setting acceptance rules and noting functional tests in Coswin 8i, ensuring done work is checked, noted, and trackable for audits, safety, warranty, or rules.
Defining test and acceptance criteriaRecording functional and safety testsLinking tests to checklists and tasksCapturing test results and sign‑offsTraceability for audits and warranties
