Field Cards

A Field Card captures field knowledge about one fault, one simple job, or one area of a machine. Each card starts from tribal knowledge — shift logs, maintenance records, and the people who do the work — and carries photos of what the Technician will see. A card is smaller than a Task and bigger than a Solution.

Field Cards are generic: a card is model-based by default and applies to every unit of that model, not to one specific machine. Knowledge about a single unit belongs on that asset. See Asset Resources.

Field Cards are published with InSkill GPT Answers, App and Web visibility all on. With App and Web off, InSkill GPT still uses a card, but doesn't show it as a resource in the answer. See Editing Resource Attributes.

What Every Card Has in Common

Language: each card is made in English, the InSkill base language. When you ask for it, a card can also be made in the language of the expertise it comes from — for example, a Spanish version of a card built from Spanish shift logs. Each language version is marked with its suffix, such as -EN or -ES.
Status: each card starts as Field-derived, because its values come from the field. It becomes OEM verified once the machine maker — AZ Machine Works in the examples below — confirms them.

Card Types

Each card name links to a complete example card, with what each section covers and how to create one.

Code	Card	Use for	Main sections	Example ID
F	Fault Card	One fault on one machine type, combining what every line logged	Symptoms → Safety → Tools and parts → Diagnosis (checks ordered by how often each cause was logged) → Verification → If not resolved → Figures → Field notes → To be confirmed	`ACW-AZMachineWorks-AM650-Truck-F-001`
P	Procedure Card	Simple single jobs: swap, clean, refill, reset, calibrate	Safety → Tools and parts → Steps → Verification → If not resolved → Figures → Field notes → To be confirmed	`ACW-AZMachineWorks-AM650-Truck-P-001`
A	Atlas Card	Photo reference for one machine area: what things look like and where they are	Safety → How to use → Figure index → Photo panels (Defect, Location, Screen, Part, Result) → Shop-floor terms → To be confirmed	`ACW-AZMachineWorks-AM650-Truck-A-001`
E	Alarm Card	One alarm or HMI error code: its meaning, likely causes, and how to clear it	Alarm text and code → Meaning → Safety → Causes (most common first) → How to clear → Verification → If not resolved → To be confirmed	`ACW-AZMachineWorks-AM650-Truck-E-001`
S	Settings Card	Baseline settings for a machine or product format, with tolerance bands	Scope (machine, format, product) → Safety → Settings table (parameter, value, tolerance, where it's set) → Protected settings → Change rules → To be confirmed	`ACW-AZMachineWorks-AM650-Truck-S-001`
R	Parts Card	Critical spares for one assembly	Assembly → Parts table (part, SAP or OEM number, substitute, minimum stock, where it's kept) → Figures → To be confirmed	`ACW-AZMachineWorks-AM650-Truck-R-001`
O	Lockout Card	Isolating energy safely before work on one machine	Energy sources → Isolation points (with photos) → Lock-out order → Check zero energy → Restore order → To be confirmed	`ACW-AZMachineWorks-AM650-Truck-O-001`

Card IDs

Every card ID follows the same pattern: <Site>-<Brand>-<Model>-<MachineType>-<Code>-<Number>. In the examples above, ACW is the site (AZ Copper Works), AZMachineWorks is the machine maker, AM650 is the model, and Truck is the machine type. Cards are model-based by default, so the ID includes the model. Leave the model out only when a card applies to every model of the machine type. Each language version adds its suffix, as in ACW-AZMachineWorks-AM650-Truck-F-001-EN.

To decide between a Field Card, a Task, and a Solution, see When to Use. To build cards from shift logs and records, see Using AI to Generate.