Table of Contents

<componentType> Element (for line)

This element adds a component type definition.

Parent Elements

componentTypes

Attributes

Name Type Description Required
name string A short, human-readable name for the component type. This name is used when referring to the component type in screen prompts and is converted to upper-case and appended to defects generated for component verification faults. Yes
associatedBuyoffs string A comma-separated list of buyoff names specifying which buyoffs are associated with this component type. The associated buyoff(s) cannot be set when this component is invalid. If this component changes from valid to invalid, any associated buyoffs that were previously set will be cleared. No
checkInstalledOnly boolean If this is true, workstations will not prompt for serial or model number scans for this component type. Instead, workstations will prompt the operator for whether the component is installed (yes/no). The prompt will display the component type name, with "Installed? [Yes] [No]" below it. No (defaults to false)
groupName string If this is set, serial number uniqueness checks will include all component types listed for this line that share the same group name. For example, if a unit requires both "Compressor 1" and "Compressor 2" component scans, the group names for each can be set to "Compressor" so that compressor serial S1 previously scanned for "Compressor 1" will not be allowed as a scan for "Compressor 2". No
mergePreassemblyUnitModelMustMatch boolean If this is true, the preassembly unit model number must match the unit model number when merging a preassembly of this type into a unit. Only the model numbers are compared; the model number aliases are ignored. No (defaults to false)
optional boolean Whether this should be considered optional for a unit, making this informational only. If this is true, then this will be ignored when performing final checks or sequence checks. This is useful for testing, or for adding this temporarily so that units already on the line will not be rejected. Typically, when this is true, associatedBuyoffs should not be set. No (defaults to false)
rejectUnitBarCodeScans boolean If this is true, when a workstation is prompting for this component to be scanned, any scans of the current unit's bar codes will be rejected. This helps prevent accidentally recording unit bar codes from being recorded as component serial numbers. No (defaults to false)
requirePartsListEntry boolean If this is true, all units for which this component applies must have a parts list entry. This setting can affect the determination of component applicability to scanned units. See the remarks below for more information. No (defaults to false)
scanComponentModel boolean If this is true, workstations will prompt for the model number to be scanned for this component type. If this is false, then workstations will not prompt to scan the component model number, and NULL will be saved to the database for the model number. The scanComponentModel and scanComponentSerial settings cannot both be false. No (defaults to true)
scanComponentSerial boolean If this is true, workstations will prompt for the serial number to be scanned for this component type after the component model number is scanned. If the component serial scan is canceled, NULL is saved for the serial number. If this is false, then workstations will not prompt to scan the component serial number, and NULL will be saved to the database for the serial number. The scanComponentModel and scanComponentSerial settings cannot both be false. No (defaults to false)
sequence float Defines the sequence number for this component type, used by sequence checks. See sequenceCheck for <onUnitRelease> or <onUnitScan> for more information. No
uniqueSerialNumbers boolean If this is true, component serial numbers must be unique for this component type. The check will include all components of this component type recorded in this Acuit Pinpoint database. groupName can be used to perform the check across additional component types. If uniqueSerialNumbersPerPartNumber is true, this setting is ignored. No (defaults to false)
uniqueSerialNumbersPerPartNumber boolean If this is true, component serial numbers must be unique for this component type, for a particular component model number. Repeated serial numbers are allowed as long as the component model numbers differ. If this is true, it takes precedence over uniqueSerialNumbers. No (defaults to false)

Child Elements

Name Description Required
authorization Defines the authorization for overriding component scans. This replaces any default authorization specified by the <componentVerification> element. Only the Override permission type is applicable. No
barCodes Defines the component bar code formats. If this is not provided, then component numbers cannot be scanned with a bar code scanner and will have to be manually entered at the station. No
modelNumber Defines the component model number settings. If this is not provided, then the settings will assume their default values (see the referenced section). No
partsFromQuery Specifies acceptable parts for this component type from a SQL query. See the remarks below for more information. No
partsFromTable Specifies acceptable parts for this component type from an Acuit Pinpoint table. See the remarks below for more information. No
partsList Specifies acceptable parts for this component type via an inline list. No
rejectParts Defines one or more parts lists that specify parts that will be rejected for this component type. No
serialNumber Defines the component serial number settings. If this is not provided, then the settings will assume their default values (see the referenced section). No
unitFilter Defines the units for which this component applies. If this is not specified, applicability is determined from the parts list (see the remarks below). No

Remarks

Parts lists can be obtained from a number of different sources:

  • A parts list can be listed inline in the configuration via the <partsList> element.
  • A parts list can be obtained via a SQL query via the <partsFromQuery> element.
  • A parts list can be obtained from an Acuit Pinpoint table via the <partsFromTable> element.

If multiple parts sources are specified, then the parts from each source will be combined. If no parts are specified via any of the above sources, then any component numbers will be accepted when the component part is scanned. If one or more sources are specified, but they contain no entries, then every component will be rejected.

If any reject parts are defined via the <rejectParts> element, then those parts are checked first; if an entry that matches the scanned unit and scanned component numbers is found, the component will be rejected.

If the component was not rejected via a reject parts list, then all acceptable parts list entries are checked, in order from first to last, looking for an entry that matches the scanned unit and scanned component numbers. The first entry found that matches all criteria will cause the component to be accepted. If no entries are found that match, then the component will be rejected.

The following logic is used to determine whether this component type applies to a particular unit:

  • If unitFilter is specified, then it explicitly specifies the applicable units.
  • If unitFilter is not are specified, then the following logic is used:
    • If requirePartsListEntry is true, then every unit model should have at least one entry in the parts list, and applicability is determined via componentModelNum and componentSerialNum for the matching part(s): if those values are blank for all matching part(s), then the component is deemed to not apply to the unit. If there is no entry in the parts list for the unit, then any component scanned will be rejected as invalid.
    • If requirePartsListEntry is false, then the parts list is used to determine to what units this component type applies, as follows:
      • If no parts list is specified, then this component is deemed to apply to all units.
      • If a parts list is specified, then the component type is deemed to apply to the unit if one or more entries in the list apply to the unit (i.e., unitModelNum and unitSerialNum for that part match the unit, and componentModelNum and componentSerialNum for that part are not blank).

The recommended approach is as follows:

  • Do not specify unitFilter.
  • Set requirePartsListEntry to true.
  • Ensure that every unit model that will be scanned is listed in the parts list for this component, leaving the component numbers (componentModelNum and/or componentSerialNum) blank for units to which this component do not apply.

This approach will ensure that component numbers for all unit models must be explicitly configured. Should a unit be scanned for which the component numbers are not configured, the component scan will be required, but all numbers scanned will be rejected.