Table 5 How our process discovery... | Emerald Publishing

Table 5

How our process discovery impacts the demand

Finding	Resource allocation	Impact on demand
(1) New DMS/scan is followed by task TAK agreement	Budget Business	Currently, the claim handler creates a manual task after receiving a task for a new document > potential automation/optimization during demand
(2) Task TAK agreement is followed by Update EPC stat	Budget Development, Architecture/Infrastructure	Early involvement of third party provider required, risk management of demand required
(3) Manual memo “TAK” is followed by a reserve change	Budget Business	Potential automation identified because TAK reduces reserve by 40%
(4) New claim DMS/scan is followed by task TAK agreement	Budget Development	Early involvement of other DevTeam during demand identified, additional budget and time
(5) Subclaim closed is sometimes followed by TAK document	Budget Business	Sometimes the TAK agreement is only identified after the subclaim is already closed > potential process optimization
(6) Existing external links to partner client	Budget Development, Architecture/Infrastructure	Support TestTeam to integrate internal provider for E2E test, demand
(7) Overall process map	Demand Management, Test Team, Release Management	Supports User STory and technical Specification for DevTeam, supports demand acceptance
(8) Memo TAK, task creation, document scan	Budget Development, Budget Business	Acceptance criteria for demand regarding tests and approval, by defining must have functionality

Finding	Resource allocation	Impact on demand
(1) New DMS/scan is followed by task TAK agreement	Budget Business	Currently, the claim handler creates a manual task after receiving a task for a new document > potential automation/optimization during demand
(2) Task TAK agreement is followed by Update EPC stat	Budget Development, Architecture/Infrastructure	Early involvement of third party provider required, risk management of demand required
(3) Manual memo “TAK” is followed by a reserve change	Budget Business	Potential automation identified because TAK reduces reserve by 40%
(4) New claim DMS/scan is followed by task TAK agreement	Budget Development	Early involvement of other DevTeam during demand identified, additional budget and time
(5) Subclaim closed is sometimes followed by TAK document	Budget Business	Sometimes the TAK agreement is only identified after the subclaim is already closed > potential process optimization
(6) Existing external links to partner client	Budget Development, Architecture/Infrastructure	Support TestTeam to integrate internal provider for E2E test, demand
(7) Overall process map	Demand Management, Test Team, Release Management	Supports User STory and technical Specification for DevTeam, supports demand acceptance
(8) Memo TAK, task creation, document scan	Budget Development, Budget Business	Acceptance criteria for demand regarding tests and approval, by defining must have functionality

Source(s): Created by authors