Field Service Start Date Examples
The following examples show how the Field Service Start Date field affects the Program pattern and the first Case date in different scenarios. For information about the underlying field behavior, see What the Program Feature Automatically Sets or Controls.
-
Example 1 - For a six-monthly PM Project Type that creates maintenance cases, if Start Date is 1 January 1 and Field Service Start Date is January 10, the first Case date is January 10 and all subsequent Cases are scheduled after that accordingly.
-
Example 2 - For the same six-monthly PM pattern, if Start Date is January 1 and Field Service Start Date is December 10, the first created Case date becomes June 10 rather than 1 January 1. The Program pattern is calculated from Field Service Start Date, but Cases still aren't created earlier than the Project Start Date.
-
Example 3 - For a six-monthly alternating minor-major maintenance pattern with Start Date of January 1, the first created Case follows the Case Type that's set first in the FSM configuration.
Here's the configuration snippet for Example 3:
,{
"//": "PM Six Monthly",
"project": [46],
"interval": 12,
"case": {
"type": 27,
"details": "${project.comments}",
"assigned": 5
}
},{
"//": "PM Six Monthly",
"project": [46],
"interval": 12,
"offset": 6,
"case": {
"type": 28,
"details": "${project.comments}",
"assigned": 5
}
}
In Example 3, Case Type 27 is Minor and 28 is Major, so the minor case is created first. The offset of 6 is what shifts the second Case Type by six months. The interval of 12 means each type repeats every twelve months.
Example 4 - For a six-monthly alternating minor-major maintenance pattern with Start Date of January 1 and Field Service Start Date of December 10, the Program logic shifts so that the first Case created is a major case rather than a minor case.