Field Standard Operating Procedure (SOP) Template

Work Order Standard Operating Procedures (SOP) are designed to standardize on-site operations, supporting sequential or flexible execution of process steps to help engineers complete field work efficiently while recording their working hours.

Usage Example:

Navigation Path: Service Connector → System Settings → Field Standard Operations
picture coming soon:

1. Field Standard Operations Template

1. Click New to create a standard operations template.
   picture coming soon:

2. Fill in the template details:

   • Name: Title of the standard procedure.
   • Description: Purpose or notes for the procedure.
   • Type: Internal use or Service Provider use.
   • Scope: Define applicability rules (used in workflow nodes to match SOPs dynamically).

Select the process layout:
picture coming soon:

2. Standard Process Steps

Process Steps: Divide complex on-site services into stages (e.g., preparation, repair, inspection).
- Multi-step scenarios: Click “+” to add steps. For single-step workflows, no addition is needed.
- Edit or delete steps via the step panel.
picture coming soon:

3. Actions

Actions: Define tasks within steps. Click Add Action to create new tasks.
Action Modes:
1. One-Time Action: Performed once per SOP instance (e.g., confirm equipment fault).
2. Repeated Action: Executed at set intervals (e.g., daily checks).
picture coming soon:

3.1 One-Time Actions

#### 3.1.1 Action Types
- Edit Object:
- Modify Work Order fields (e.g., location, description) or linked objects (e.g., update device address).
- Supports parent-child object editing (e.g., device and fault records).
picture coming soon:

• Link or Create Objects:
  • Associate existing data or create new linked records (e.g., device logs).
    picture coming soon:
    picture coming soon:

• Batch Create Linked Objects: Bulk-create related records (e.g., spare parts consumption).
  picture coming soon:

• Add Inspection Groups: Predefined or rule-matched checklists.
  picture coming soon:

• Generate Service Reports: Auto-generate reports after mandatory actions.
  > Note: Does not support completion validation or post-action triggers.
  picture coming soon:
  picture coming soon:

• Feedback QR Codes: Consolidate actions into a single node for customer feedback.
  > Note: Only fixed templates are supported. For conditional templates, use standalone Feedback Nodes.
  picture coming soon:
  picture coming soon:

3.1.2 Action Prompts

Add guidance to assist engineers (e.g., tips or step-by-step instructions).
picture coming soon:
picture coming soon:

3.1.3 Assignees

Default: Work Order Engineer. Supports two fields: field_xcfwry__c (Engineer) and related_service_personnel__c (Co-engineer).
picture coming soon:

3.1.4 Action Settings

• Mandatory: Validates completion before sign-off.
• Prerequisites: Blocks execution until prior actions are done.
• Skip Option: Shows “Skip” button for non-mandatory actions.
• Auto-Skip: Automatically advances to the next action (App only).
• Completion Rules: Custom validation logic.
• Post-Action Triggers: Automated follow-ups.
  picture coming soon:

UI Example:
picture coming soon:

3.2 Repeated Actions

Execute at intervals (e.g., daily checks) until SOP completion.

3.2.1 Action Types

• Create Linked Objects: e.g., device logs.
  picture coming soon:
• Add Inspection Groups: Rule-based or predefined.
  picture coming soon:

3.2.2 Prompts & Assignees

Same as one-time actions.
> Note: For co-engineers, actions are frequency-based (e.g., once daily).
picture coming soon:

3.2.3 Frequency

• Unlimited: No cap (auto-generates every 5 mins).
• Daily: Generates at midnight.
• Per Check-In: Requires repeated check-ins.
  picture coming soon:

3.2.4 Settings

• Mandatory: Validates on sign-off (excludes unlimited actions).
• Completion Rules & Triggers: Validates/triggers per instance.
  picture coming soon:

Example:
picture coming soon:

4. Check-In for Standard Operations

Engineers must check in before starting actions and check out to complete SOP.

4.1 Single Check-In

For one-time visits. Configure:
- Check-in scenarios (distance validation, photo requirements).
- Allow adjustments: Timeframe and content edits.
picture coming soon:

4.2 Repeated Check-Ins

For multi-day tasks:
- Enable Repeated Check-In to allow multiple sign-ins/sign-outs.
- Missed check-outs auto-flag at 23:59 for later completion.
picture coming soon:

Example:
picture coming soon:

5. Global Repeated Actions & Check-Ins

Enable in Global Settings for ad-hoc tasks during extended operations.

5.1 Global Repeated Actions

Use Case: Ongoing multi-day tasks (e.g., sporadic updates).
- Add actions (e.g., create logs, inspections).
- Set assignees and frequency.
picture coming soon:

5.2 Global Repeated Check-Ins

Use Case: Daily location updates or waiting periods (e.g., delayed parts).
- Configure check-in scenarios and assignees.
picture coming soon:

6. Workflow Node: Field Standard Operations

Configure this node to execute SOPs. Assignees are defined in action settings.

• Template Selection: Fixed or rule-based (with fallback options).
• Custom Buttons: Rename primary actions or hide default “Complete” buttons.
  picture coming soon:
  picture coming soon: