Create Work Orders

Search for, create, display, or modify one or different work orders (WOs).

Create a simple WO

1. Navigate to: Features > Core > Work order management > New WO.

2. In the WO data section, enter the following information:

   • Work interval from: The minimum date to schedule the WO

   • Work interval to : The maximum date to schedule the WO.

3. In the Technical object field, click the Magnifying glass icon.

4. Click the Search customers tab or the Search facilities tab, and use the  filters to search for and select the customer or facility. 

5. In the WO type section, select the following information:

   • Request type: A list of options from the facility/customer.

   • Service type: A list of options from the request types.

6. Click Save.

Create a detailed WO

1. Navigate to: Main menu > Features > Core > Work order management > New WO.

2. Fill out all required fields in each header.

3. Before you save the header, click the WO operations button at the bottom.

• To check the association of the work cycle with the order header, click the Replace cycle, enter operations tab.

  • If no work cycle has been associated, you can add the operations manually. 

• To see all operations automatically associated through the work cycle, click the WO operations sequence tab.

  • At the top left, use the Vertical line menu to reorganize the column, display the mode, and/or add new operations.

  • If you click the Add operation icon, you can define a new operation.

Replace a WO work cycle

1.  In WO operations, click the Replace cycle, enter operations tab.

2. Replace the work cycle associated with this WO:

   1. Click the Replace cycle tab to replace the work cycle associated with the WO type. 

   2. Choose an available work cycle, configured in the header, and select Replace cycle.

3. Right click an operation.

4. Click one of the following options:

   1. Unplanned intervention outcome: When operations are “Schedulable”, the outcome may be defined although the intervention hasn’t been scheduled yet.

   2. Unlock operation: Unlock the WO operation.

   3. Cancel operation: Cancel the WO operation.

   4. Associate materials: Associate the materials with the WO operation or modify already-associated ones. See Associate materials.

   5. Associate tools: Associate generic tools with the specific operation.

   6. Add sheet: Associate a dynamic form with the WO operation. 

      • An operation may be associated with many dynamic form templates.

      • Operators must fill out the different dynamic forms that are required.

      • Note: If entering a dynamic form previously associated with the operation, the system returns a blocking error message.

   7. Associate sheet with day: Associate the WO operation with a dynamic form  instance that only refers to a specific day. 

      • The dynamic form is in “Processed” status and isn’t bound to a WO operation, just the working day.

   8. Edit: Access the Edit WO operation window.

   9. Agreement: Display the associated agreement. 

      • The SO field in the operation type marks the difference between internal and external operations.

5. Finish all changes to the operations.

6. In the Operations menu at the bottom-left, click Ok.

7. Click Insert.

8. Click Save.

Associate materials

Create a list of the materials associated with the WO operation from the Materials master data. 

To approve materials for the specific WO type:

1. Enter materials in the Associated materials list table.

2. Click Confirm.

3. Find the material association window.

4. In the Materials list table, select the materials to associate with the WO operation.

5. Select the corresponding units of measurements for the materials in the Material field.

6. Specify the required quantity for each material.

7. Click Save.

Make a WO scheduleable

1. Open a WO search. See Search Work Orders.

2. Validate a WO.

   • Once you validate the WO, the order status changes from “Open” to “Scheduleable”. 

• Managed by operation: Specific operations determine the duration and cardinality.

  • Specific operations determine how the WO is scheduled and debriefed.

• Managed by order: WO duration, team cardinality and residual WO duration usually defines the order.

  • The WO header determines how the WO is scheduled and debriefed.

Find all activity interventions

When an operation has a partial or final outcome, its intervention object generates in the platform. If an operation had both a final and many partial accountings, it may be associated with one or different interventions. 

To find the interventions related to the selected operation:

1. Navigate to Features > Core > Work order management > New WO.

2. Fill out all required fields in each header.

3. At the bottom, click WO operations.

4. Click the WO operations sequence tab.

5. Find the Slots outcomes / Activity interventions section.

Access more WO information

Further major WO functions are reported at the bottom of the Work Order page:

• Show WO scheduling: Specify the intervention status, planned resources, the assignment slot, and the outcome causal.
  Multimedia contents: Shows the multimedia contents of WOs.

• Display advanced history: Access a detailed view of the editing history of the header and WO positions.

• Appointment slot: Manually set appointment slots.

• Related orders: Access related orders with a parent-child dependency.

• Authorizing process: See WO authorization processes.

• SLA monitor: Track the progress of any Service Level Agreements (SLAs).

• Create fictitious facility: Make a facility for testing.

• WO notes: See notes about WOs.

Integrate external systems with WOs

Often, WO generation is based on external systems like CRM/ERP or IOT. You can use a dedicated service like Web Service SOAP or API REST to receive WO generation requests from the external source. Generally there are two scenarios:

• The WO framework is defined in the source system and received by the platform.

  • The external system forwards the list of N operations, time data, number of the team members and further related information.

• The platform defines the WO framework and details work cycles and the minimum set of information from the external system, such as:

  • Order type.

  • Technical object / address.

Support synchronous queries

NextGen FSM supports many standard integration flows from external systems and a full synchronization of the job management process.

• Relies on major frameworks, such as Apache CXF, to comply with synchronous Application-To-Application (A2A) integration requirements

• Can create apps that successfully integrate into the operating business environments.

A2A communications rely on:

• HTTP or HTTPS as the preferred transmission protocol.

• XML, Json, Csv as the data format to share basic data.

• REST as the basic communication paradigm.

• SOAP as the preferred structured messaging format.

• WebServices as an interoperability and standardization tool for SOAP messages.

Support asynchronous queries

Data import/export flows fall within the category of asynchronous queries. They can be based on batch file generation procedures, on massive messaging on asynchronous channels, or on the compilation of border tables in a shared DB. 

• Access standard communication protocols or data interchange formats through full J2EE support and open source support.

• Create detailed integration flows like initial alignment processes, massive integrations, and feeding considerable amounts of data.

For closed communication standards, use different available protocols through enterprise application integration middleware like:

• TIBCO

• SAP PI/PO/BTP

• DellBoomi