Use Cases for Field Change Order
 |
The use cases for this feature are based on the standard reference scenario, with Iniscope International as the example organization. For more information, see Standard Organization for Work Order Management.
|
The following table describes common Field Change Order scenarios for administrators, service coordinators, and field service engineers.
|
Use Case
|
Scenario
|
|---|---|
|
Setting up reusable FCO configuration templates
|
An administrator at Iniscope International sets up FCO configuration templates for Soniscape ultrasound and laser product lines so every safety notice, firmware upgrade, or field correction starts from a validated baseline of properties and mappings. This matters because administrators reduce setup effort, service coordinators launch FCOs faster, and quality teams get consistent change documentation across regions. For more information, see Launching FCO Configuration Setup, Viewing FCO Configuration Templates, and Defining FCO Configuration Properties.
|
|
Creating an FCO header record for a product safety notice
|
A service coordinator at Iniscope International creates an FCO header record to roll out a corrective action on Soniscape SSI 1000 ultrasound machines after a supplier-reported defect. The coordinator associates a work plan and defines required parts so generated work orders carry the right tasks and inventory. This matters because field engineers receive executable, fully-scoped remediation work, customer downtime is shorter, and compliance deadlines are met. For more information, see Creating a FCO Header Record, Associate Work Plan with a FCO Header Record, and Defining Required Parts for an FCO.
|
|
Identifying Installed Products Affected by a Software Recall
|
An asset manager at the Insicope organization performs a field change analysis to identify installed products impacted by a software recall. When a software recall is issued for version v11.0, the asset manager needs to identify all affected installed products.
The asset manager defines an FCO search using the Technical Attributes search type and selects the Software Version technical attribute, which is configured as a lookup data type. The search is scoped to Installed Products that have v11.0 as the matching criteria.
Once the search is executed, the system evaluates the lookup technical attribute values stored for each installed product and matches them against the selected lookup value.
As a result, the FCO search generates result lines for only those installed products that are running software version v11.0.
When the asset manager reviews the FCO search results, only the installed products impacted by the recall are displayed.
This ensures accurate identification of affected installed products, reduces manual analysis, and enables timely corrective or preventive actions based on precise technical attribute data.
For more information, see Creating an FCO Search using Technical Attributes and .
|
|
Bulk loading impacted installed products from external sources
|
A quality engineer at Iniscope International bulk uploads installed product criteria received from a supplier defect report so every affected Soniscape ultrasound unit at hospital sites is included in the FCO scope. This matters because users avoid manual re-entry, the scope matches the supplier list exactly, and remediation can start without delay. For more information, see Bulk Uploading Installed Product Criteria to FCO Search.
|
|
Assigning FCOs directly from an installed product record
|
A field engineer at Iniscope International, while servicing a Soniscape microscope at a research facility, reviews open FCOs from the installed product record and assigns the asset to an active campaign that applies to it. This matters because eligible assets are not missed during routine visits, customers benefit from same-trip remediation, and the service organization avoids a second dispatch. For more information, see Assigning FCOs from an Installed Product Record.
|