SWA Workflow 1
-
Upload
andik-manchesterunited -
Category
Documents
-
view
246 -
download
2
description
Transcript of SWA Workflow 1
-
SWA WORKFLOW
-
Work Flow Between PT4 and SWAPresentation / Author / Date AssignedDispatchedAcknowledgedAcknowledged [Onsite is captured in Audit trail]ExecutedClose RequestClosedAcceptedWork in progress(onsite) Note: Pending status is optional in between accepted and close requestWO dispatched with key[BCDE]WO A[key]WO O[key]WO C[key]
Presentation / Author / Date
-
The WO SMS is received by the concerned engineer
-
The engineer make the WO to Onsite to represent that he/she is working on it.
-
The engineer sends an Close Request, when he/she rectifies the fault it.Note: Reason code need to be configure in tool by the administrator
-
Pending work flow
Pending status is optional in between accepted and close request.The task can be move to pending after Accepted or after Onsite. SMS format is WO P[key][Pending reason code] . e.g. WO PBCDE004 or it can also be WO P[key](in this case default reason will capture).The task can be released from pending by sending the same SMS without reason code. e.g. WO PBCDEHigh priority Tickets can be restricted from pending.
-
WORKFLOWWO Message with key [XYXY]WO AXYXYWO PXYXY WO CXYXY 2 001 WO PXYXY001WO OXYXY
WO DISPATCHWO ACCEPTEDWO PENDINGWO BACK TO ACCEPTEDWO ONSITEWO CLOSE REQUEST
WO MESSAGE RECEIVEDACCEPT WO MESSAGEPENDING WO MESSAGE[if required] NOTE:001 is the reason code for pendingRELEASE PENDIND WO MESSAGEONSITE WO MESSAGESCLOSE REQUEST MESSAGES[WO C(key) (no. of site visit) (RCA reason code)
-
NOTE: For both suspension and Release the key word is PMOVING TO PENDING STATUSRELEASE FROM PENDING STATUS
-
The following message will be received if the engineers tried pending for restricted priorities
-
THANK YOU
*