Field Equipment Standard Operating Procedures (Beta)

Prerequisite: The “Multi-device Work Order” feature is enabled, which adds the Sub-object [Work Order Device] CasesDeviceObj.

picture coming soon:

Access path: Service Connector -> System Settings -> Field Standard Operations

picture coming soon:

1. Device Field Standard Operation Templates

First, create standard operation templates for different device models.

1. Under the “Device” tab, click [New] to create a standard operation template.

picture coming soon:

1. Enter the template name, device applicability conditions, description, and select the standard operation process layout.

picture coming soon:

1.2 Device Standard Operation Processes

Processes: For Work Orders with multiple field service steps, you can divide them into multiple processes (e.g., preparation, repair tasks, result checks).

Multi-process scenario: Click “+” to add a process. For single-process scenarios, no add button will appear. Click the process panel to enter the process name and description. Click the “Delete” button to remove the current process.

picture coming soon:

1.3 Device Standard Operation Actions

Actions: Define what needs to be done. Click “Add Action” to create a new action item within a process. Click “Node Settings” on the right to enter the action name and description. Device standard operations currently support only single actions and three action types:

1. Edit Object:
   • Edit fields in the [Device] object (e.g., device location, description) or fields in related objects (e.g., “Last Follow-up Time” in the [Account] object).
   • Process editing: Supports editing both primary and Sub-objects together.
2. Select or Create Related Object:
   • Select an existing related object record to associate with the device.
   • When “Create New Only (No Existing Association)” is checked, only new related object records can be created (e.g., new device operation records).
3. Batch Create Related Objects:
   • Batch create records for objects related to the device (e.g., [Spare Parts Consumption] object).

picture coming soon:

1. Action Execution Prompts: Add guidance or steps to help engineers perform tasks correctly, improving efficiency.
2. Device Action Assignee: Cannot be set independently; follows the Work Order standard operation assignee.
3. Action Settings:
   • Required: Validates whether the action is completed when clicking “Complete Sign-off” for the process or “Complete” for the standard operation action.
   • Prerequisite Action: This action cannot be executed until prerequisite actions (within the same process) are completed.
   • Show “Skip This Step” Button: Displays a skip option when the current action is incomplete.
   • Auto-Skip: Automatically proceeds to the next action after completion (applies only to mobile app).
   • Completion Conditions: Click “Edit” to add validation functions for action completion.
   • Post-Completion Actions: Click “Edit” to add functions that execute automatically after action completion.

picture coming soon:

2. Adding Device Standard Operations to Work Order Field Standard Operations

1. Select the Work Order standard operation that requires device standard operations.
2. In the process, click “Add Device Standard Operation”: The system automatically matches each Work Order device’s conditions and generates pending standard operations.
3. Set assignees for all device standard operation instances (default: Work Order Engineer).

picture coming soon:

3. Triggering Device Standard Operation Instances via Work Order Standard Operations

1. When a Work Order involves multiple Fault devices requiring different actions from assignees, use multi-device Work Order SOPs.
2. The system automatically matches each device’s conditions and generates pending standard operations.
3. Engineers must complete all required actions for each device’s standard operations before completing the Work Order standard operation.

picture coming soon: