What is Expertise
Expertise is everything an InSkill copilot knows about a machine: formal expertise that has been written down and curated, and tribal expertise known by people.
Expertise is everything an InSkill copilot knows about a piece of equipment. InSkill GPT answers a Technician's question from the expertise loaded into the copilot, not from the internet, so every answer is only as good as the expertise behind it.
Expertise comes in two types: formal expertise, which has been written down and curated, and tribal expertise, which is known by people. A copilot holds both. InSkill turns them into forms that are more useful to Technicians, and controls who can see each item.
Types of Formal Expertise
Formal expertise has been written down and curated. It usually comes from the equipment maker or your own engineering team.
| Type | What it holds |
|---|---|
| Manuals | How to operate the equipment |
| IOMs | Installation, operation, and maintenance |
| Service manuals | Specifications, adjustments, and repair procedures |
| Parts manuals | Part numbers, quantities, and supersessions |
| Schematics | Electrical and hydraulic circuits |
| Training videos | How a job is done, shown step by step |
Formal expertise is added to a copilot as resources. For the file types InSkill accepts, see Supported Resource Formats.
Types of Tribal Expertise
Tribal expertise is known by people. Experienced Technicians, operators, and support teams learn it on the job: which cause turns up most often, what a fault looks like, the fix that works on this line. When it is written down at all, it is in tickets, notes, and records. InSkill captures it in the form that fits:
| Tribal expertise in | Becomes |
|---|---|
| Support tickets | Solutions |
| Handwritten notes | Field Cards |
| Maintenance records | Field Cards |
| The site's SOPs | Tasks that guide the work |
To choose the form for a piece of tribal expertise, see When to Use. To turn other expertise into more useful forms, see Enriching Expertise.
Expertise Working Together
On the AZ Machine Works Copilot (Truck), the hoist of the AM-650 haul truck is covered by both types of expertise at once:
- Formal: the 2025 Service Manual and the 2025 Maintenance and Parts Manual give the maker's specifications, as resources.
- Tribal: the Fault Card Hoist slow or will not raise captures what Technicians logged in the field: an ML screw left open is the most common cause, so it is checked first.
- Enriched: the Task Troubleshoot: Hoist Slow or Will Not Raise guides the repair step by step and records the readings.
When a Technician asks why the hoist is slow, InSkill GPT draws on all three, cites the manual pages it used, and points to the Task.
In This Section
| Page | What it covers |
|---|---|
| Supported Resource Formats | The resource types and file formats a copilot accepts |
| Secure Access | How InSkill controls who sees which expertise |
| Expertise Level and Users | The access levels that match each person to the expertise they may see |
| Enriching Expertise | Turning expertise into more useful forms, such as manuals into SOPs and images into Field Cards |
| Field Cards | The seven Field Card types, each with a complete example |
| Tasks / Work Instructions | The kinds of work a Task can guide and record |
| When to Use | Choosing between a Task, a Field Card, and a Solution, and when to promote or retire an item |
| Using AI to Generate | Turning raw records into Tasks, Field Cards, and Solutions with AI |
Updated 4 days ago