Craftsman Information Device Operation flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Byte and bit

A bit is one binary digit (0 or 1); a byte is 8 bits. Storage and file sizes are quoted in bytes, while network speeds are usually quoted in bits per second.

Unique record key

A field or combination that identifies exactly one record, such as a serial or job number. Duplicate keys cause overwrites during sync and make records impossible to separate later.

UTC timestamp storage

Records store time in Coordinated Universal Time and display a local offset. This keeps ordering correct across time zones and daylight-saving changes when devices from several sites sync together.

Offline write queue

A local list of records awaiting sync, each tagged pending, sent, or confirmed. Without state tags, a reconnect can resend records and create silent duplicates.

Audit trail fields

The minimum audit entry holds the user, device ID, timestamp, field changed, old value, and new value. The old value is what makes a correction reversible.

Data classification tiers

Records are labeled public, internal, confidential, or restricted. The tier sets encryption, sharing, and retention rules, so a device holding restricted data must encrypt at rest.

Factory reset consequence

A factory reset erases local records and credentials but leaves server-side data untouched. Any unsynced work is lost, so export or confirm sync before resetting.

Automatic network time

The device sets its clock from the network instead of manual entry. Drift beyond about two minutes breaks timestamp ordering and can invalidate token-based sign-in.

Firmware update conditions

Apply firmware only on mains power or a battery above 50 percent, and never interrupt the write phase. An interrupted flash can leave the unit unusable.

Enrollment profile

A management package that pushes Wi-Fi settings, certificates, and app configuration to the device. Failed application usually means an expired certificate or wrong enrollment token.

Least-privilege roles

Operators, supervisors, and administrators get only the permissions their task needs. Administrator accounts are reserved for configuration, not routine data entry.

Setup acceptance test

Before handover, capture one record, sync it, retrieve it on the server, and confirm the audit entry shows the right user, device, and timestamp.

Start-of-shift checks

Confirm charge or swap the battery, verify network and sync status, confirm the pending queue is empty, then open the assigned work list before capturing any data.

End-of-shift sync

Submit open records, force a sync, confirm zero pending items, log out, and place the device on charge in its assigned location.

Work-order state flow

Orders move assigned, in progress, paused, complete, closed. Skipping a state or closing with open sub-tasks creates reconciliation gaps at shift end.

Barcode scan distance

Hold the scanner 10 to 25 cm from the label with the beam roughly perpendicular. Repeated no-reads usually indicate a damaged or low-contrast label.

Written shift handover

Handover records open items, device condition, and pending syncs in writing or in-app. Verbal-only handover loses exceptions and leaves the next operator without context.

Point-of-failure exception

When a step cannot be completed, record the reason code and photo evidence at that moment. Reconstructing exceptions later produces inaccurate records.

Double-entry verification

High-consequence fields such as serial numbers, quantities, and measurements are entered twice or scanned instead of typed. A mismatch between entries blocks submission.

Form-level validation

Required fields, min and max ranges, and pattern masks catch most entry errors before the record is saved, rather than after it reaches the server.

Unit-with-value rule

Every measurement is stored with its unit, such as mm, kg, or degrees Celsius. Mixing unit systems in one field is a frequent cause of recalls and rework.

Correction record protocol

Submitted values are never overwritten. A correction record references the original and carries a reason and approver, so the history stays intact and auditable.

Search narrowing order

Start with the unique key such as serial or job number, then narrow by date range, then use free text. Free-text-only searches return false matches.

Look-alike serial check

Before acting on a retrieved record, confirm the key and date match the intent. Serials differing by one character are a known source of wrong-record actions.

Fault isolation order

Check power and charge, then connections and card seating, then network, then application, then permissions. Fix the lowest layer before moving upward.

Forced restart procedure

If the device will not respond, charge it 30 minutes on a known-good charger, then hold power for 10 to 15 seconds. No response suggests battery or hardware failure.

Sync failure checklist

Check signal strength, server address, certificate validity, and account lock status, then retry. Record the error code before clearing it for escalation.

Scanner no-read test

Clean the window, inspect label contrast and damage, then scan a known-good label. If that also fails, the scanner needs recalibration or escalation.

Escalation data package

Include device serial, firmware version, error code, time of fault, steps already tried, and whether data is at risk. Missing details delay repair.

Lithium battery hazard

Never puncture, crush, or charge a lithium battery below 0 degrees Celsius. A swollen, hot, or leaking battery goes to a fire-resistant area and is reported.

Ex-rated device rule

In hazardous zones, only intrinsically safe certified devices may be used. Standard units must never be substituted, and the certification label must stay legible.

Record retention period

Regulated records are kept for the period set by the applicable standard or contract. Deleting them early is a compliance breach even when the data looks obsolete.