Category filters can help you narrow down search results
What are container tickets?
Container tickets are primarily designed to handle rollout projects or device setup services.
A rollout project is usually a project with a bigger effort compared to just tickets with just one particular overall problem/task.
A rollout project in general requires service delivery to a whole location or department and requires one or more engineers and one or more appointments
in the process of delivering the service. This process normally requires more organizational efforts, than a standard ticket can deliver.
Additionally, to more organizational effort, you would also create more effort for the ticket system. For example, you suddenly require a lot of tickets regarding one big overall task because you need to roll out a lot of hardware, and software installations, or update installations at once to a whole department with a limited amount of time. Dispatchers, therefore, would need to assign tickets for every device the engineers need to install – and for an office with let’s say 100 employees – dispatchers would also need to create 100 separate tickets for this task. You can just imagine that this is not practical at all and a very manual and effort task. Container tickets will simplify the work for the dispatchers in this special use case and that’s also the use case where our new container tickets functionality really shines.
The container ticket is a superordinate ticket that can handle multiple appointments and engineers without the need to create separate tickets.
Appointments are handled inside the superordinate ticket (inside the Intervention tab of the Ticket Details). The dispatcher will see the appointment with a reference to the superordinate ticket inside the Timeline component. The major key difference to a standard ticket is that the dispatcher may assign multiple appointments and multiple engineers inside the Scheduling Assistant. Engineers also resolve tickets as usual inside the Fieldcode Mobile App, with the addition of the possibility to create child reports for more than one device/problem that the engineer resolves within one particular appointment.
How container tickets compare to standard tickets
The container ticket is a superordinate ticket that can handle multiple appointments and engineers without the need to create separate tickets.
Appointments and engineers are handled inside the superordinate ticket (inside the Intervention tab of the Ticket Details).
No, this is currently not supported.
For this case we recommend to cancel the container ticket and create a new ticket instead.
By default all roles have the option to convert tickets to container tickets.
There is no special configuration required inside Fieldcode Admin Panel concerning the utilization of container tickets.
Rollout projects
For example a company needs to rollout a bigger amount of devices a at once.
Project requirements:
- 20 Workstations need to be unpacked, installed, and configured at desks on-site at the customer location.
- Project has a tight deadline, must be completed within two days.
- Three engineers are in in charge for the project.
- One of the engineer only works half-day.
- Another one of the three engineers needs to travel half-day to reach the customer location.
- Serial numbers and the assigned employees are required for all device setups.
Device Setup Service projects
For example a hospital needs medical device setup services.
Project requirements:
- Technicians are sent to set up devices in course of 4 to 5 days.
- Technicians need to set up 8 to 10 setups each day.
- They do not want to schedule each setup individually since it is the same resource on the same location and it’s a fluent process.
- The project requires the assignment of multiple engineers to a ticket.
- The project requires to split a ticket to multiple onsite interventions.
- The project requires that the onsite times are adjusted for each technician individually.
- The project requires to have reporting enabled for each singly device in scope.
Container tickets are able to meet all those different requirements and circumstances.
- Container ticket – superordinate ticket – displayed in the Timeline – displayed in the Ticket Pool
- Container ticket appointment – displayed in the Intervention tab – displayed in the Timeline – not displayed in the Ticket Pool
- Child ticket/report – Subordinate ticket – not displayed in the Intervention tab (only in the child ticket itself) – displayed in the Ticket Pool (if RESOLVED)
- Standard ticket – displayed in the Timeline – displayed in the Ticket Pool
No, this is currently not supported.
Optimization of container tickets is currently not supported.
The child report is behaving like a regular ticket report, the only difference is that you handle multiple devices inside an appointment and report each.
The child report can be done by the engineer or dispatcher. A child report can become necessary if a engineer handles more than one device inside an appointment. The engineer would then create a child report inside his mobile application before closing the whole appointment for the day with the subordinate report. Child reports appear as resolved tickets inside the Ticket Pool.
Dispatchers can report additional child appointments and the whole appointment for a day (UNPUBLISHED APPOINTMENTS).
Engineers can report additional child appointments and the whole appointment for a day (PUBLISHED APPOINTMENTS).
Child ticket reports will appear as RESOLVED child tickets inside the Ticket Pool.
-> Please be advised that closing whole appointments inside the Fieldcode Mobile App also closes the possibility to add child ticket reports.
Absolutely!
You can tailor the child ticket report form to your specific business needs inside Fieldcode Admin Panel -> Forms.
It might be the case that your container ticket overlaps with another ticket in the Timeline.
In this case it is important to know, that your ticket is not lost, and you can still find it in the Ticket Pool and work with it regularly.
How to use container tickets
Let's go through the lifecycle of a container ticket to see how it compares to a default ticket in order to get more familiar with the usage container tickets:
Converting the regular ticket to a container ticket
Right-click on the ticket you want to convert in the Ticket Pool.
Then click on Convert to container ticket.
Note: Once you convert a ticket to a container ticket, you cannot revert it back to a standard ticket anymore.
Confirming the conversion of a regular ticket to a container ticket
You will be asked if you are sure that you want to convert the ticket, confirm by clicking on PROCEED.
The container ticket can be recognized by an icon in the Ticket Pool and by ticket category
Container and child tickets can be recognized by an icon in the Info/Alert/Part column. The container ticket has a "stacked ticket icon" while the child ticket has a "related ticket icon". What also changes is the ticket type, it changes from "Standard" to "Container" (displayed inside the Ticket Details Overview tab). If engineers or dispatchers create child ticket reports, the ticket type will be "Child".
Differences in the Scheduling Assistant compared to regular tickets
You schedule a container ticket in the same way as a regular ticket by clicking on Schedule appointment. The only thing that is a new option inside the Scheduling Assistant is that you are now able to select Multiple Appointments. Let's select that.
Notes:
- The container ticket is a superordinate ticket that can handle multiple appointments and engineers without the need to create separate tickets.
- You can still decide to schedule only one appointment, the child reporting is available as an option in this case.
Arranging multiple appointments for the container ticket
We will have a look at an exemplary case in the next step. You will notice an ENGINEER and APPOINTMENT column. You can select to whom you talked to, you can add one or multiple engineers, and you can add one or multiple appointments. You can do edits and updates to the appointments and engineers in the scheduling assistant as long as all appointments of the container ticket are UNPUBLISHED.
Use case example: Rollout of 20 new laptops for a fictive company IT Corporation
The IT Corporation wants to roll out 20 new laptops for their new office in Nuremberg. The Fieldcode company will be in charge for this job, the two engineers Smuthers and McNiell have two days to do the rollout which includes the hardware installation (connecting cables, plugin the monitors etc.) in the office and the software installation (install necessary company-needed programs etc.). Smuthers is in charge for the hardware installations on two days in the morning. McNiell is in charge for the software installations on two days in the evening.
Assigning engineers to the container ticket
The dispatcher clicks on the the Add button. The dispatcher clicks on Add engineer to add another engineer to the table. Then the dispatcher clicks on Add appointment to add another appointment to the scheduling table.
The dispatcher selects the two engineers:
McNeil and Smuthers.
Assigning appointment dates to the container ticket
The dispatcher clicks inside the calendar of the appointment column header and selects the date of the first day. Then the dispatcher clicks inside the calendar of the second appointment column header and selects the date of the second day.
Assigning appointment times to the container ticket
As next step the dispatcher assigns the the appointment times (time ranges) in all empty APPOINTMENT cells. Don't forget to click Save after finishing the assignments.
Note: You also have the flexibility to not assign times to certain engineers. This option is called Will not attend. You could use this option for example, if a technician should be scheduled for one day and have off the other day.
The container ticket is displayed for each assigned engineer in the Timeline
The container ticket is now split into several appointments, every appointment inside the container ticket is visible in the Timeline. Each appointment has the same container ticket number.
In each of the several appointments you can check all appointments (Intervention tab)
After the container ticket is scheduled the ticket moves back from the Dispatch tab to the General tab. Now it is important to understand how a container ticket is behaving:
A container ticket that has been scheduled moves to PENDING WAIT ONSITE status (if there's no other custom workflow configured).
How container tickets compare to standard tickets
- Appointments inside the container ticket can be PUBLISHED and UNPUBLISHED individually.
- The dispatcher schedules individual appointments and the workflow buttons for individual tickets
are inside the INTERVENTION tab. - Container tickets cannot be moved back to the Ticket Pool.
- Drag & Drop is disabled for container tickets (Ticket Pool->Timeline, Timeline->Timeline, Timeline->Ticket Pool) The D&D functionality is disabled for above-mentioned situations.
- The dispatcher can edit the container ticket and individual appointments if every ticket is UNPUBLISHED.
- As soon as one ticket is PUBLISHED dispatchers can only publish other tickets,
but not cancel individual appointments (Container ticket = Superordinate). - The dispatcher can still add/change/edit/delete certain appointments via the Scheduling Assistant. The container ticket stays on the current status until all appointments are either canceled (container ticket moves back to previous status) or reported (container ticket moves forward to next status).
- When all individual appointments are reported (either with child tickets being reported or appointment closed), the container ticket moves to the next status.
Child tickets appear as *RESOLVED/CLOSED tickets in the Ticket Pool search.
*Note: To which status a ticket moves is totally dependent on the configured and used workflow.
Workflows with validation: The ticket moves to the status RESOLVED.
Workflows with no validation: The ticket moves directly to the status CLOSED. - Container tickets that are on RESOLVED/CLOSED status cannot be deleted from the Timeline anymore.
Publishing all appointments of the container ticket
In the Intervention tab you click on PUBLISH APPOINTMENTS, select all engineers and click on PUBLISH.
All appointments will synchronize to all engineers and they can start the work on the service field. Engineers will now create child reports, and resolve the tickets. After all tickets have been reported, the container ticket will automatically move to RESOLVED/CLOSED.
How engineers should handle container tickets
- Appointments inside container tickets can include child tickets (because technicians install multiple laptops, for example), therefore it is advisable to create child reports and report child reports individually.
- If engineers close an appointment for the day, they have no option to create other child reports anymore.
iOS: How to create child ticket reports
- Child reports are created after the engineer arrived to the location and started to work on the ticket and then select the following in the Tickets tab - Create Child Report.
- Engineers should always select the correct name when using the report form. For example it could be the case on the field that other engineers fill out one engineer's report, because the other engineer is still busy with something else. Engineers should make sure to fill in the correct name when creating reports.
Android: How to create child ticket reports
- Child reports are created after the engineer drove to the location and started to work on the ticket and then select the following in Tickets tab - Create Child Report.
- Engineers should always select the correct name when using the report form. For example it could be the case on the field that other engineers fill out one engineer's report, because the other engineer is still busy with something else. Engineers should make sure to fill the correct name when creating reports.
Available actions BEFORE the container ticket has been published
If the container ticket was not published yet, dispatchers are able to cancel the whole container ticket (Cancel Ticket button), dispatchers are able to cancel individual appointments (Cancel Appointment button), dispatchers are able to report individual appointments (Report button), dispatchers are able to edit container ticket details (Edit button), and dispatchers are able to do child ticket reports via the Fieldcode Work Place (Child Ticket Report button). Engineers can do matching actions if appointments are PUBLISHED to them.
Additional info: How to quickly find matching tickets (Container - Child)?
You can find matching related child tickets/ matching container tickets by clicking on the search button for ticket type inside the Ticket Details tab - Overview.
Clicking on the search button will show the results listed inside the General tab in the Ticket Pool.
If you search inside a container ticket, the result will show the child tickets (subordinate).
If you search inside an child ticket, the result will show the superordinate container ticket (superordinate).
Impact of container tickers on various system parts
Workaround for impacted automated actions
If your company workflow heavily relies on automated actions, there is a workaround available to exclude container tickets from the automated actions.
This way you can still use all your other existing automated actions without losing the benefits of automated actions.
- Inside Fieldcode Admin Panel go to Automated Actions.
- Select the impacted automation in the list.
- Click on the Filters tab.
- You manually add the following filter to every already existing automated action:
Condition – Operator – Value
isContainer – is equal to – False - Automations should now have no effect on container tickets – however – they will still apply to regular tickets.
With this workaround, you can keep all your current automation without unwanted consequences! - Click on SAVE after configuring the filter.
- Repeat step 1 to 6 for other automations in the list!
Be advised that maybe not all automations in the list need this workaround – it mainly effects automations where appointment calculations happen.
