Reference no: EM132145496

Assessment Requirements

Students should conduct further research for any additional information required to complete assignment.

Outline

Assignment 2 part 2 will focus on the same ‘The Swinburne Cares Foundation donation process(es)' which used in assignment 1 and assignment 2 part 1.

This assignment requires you to continue working the same business case. As mentioned in the case description, the current process does not work efficiently. With your help, the company made the first step which adopted some best practices to fix some issues and problems. They also adopted methodologies, such as Lean to reduce the waste. To improve the process in a way that addresses the issues for a long term and reduces manual tasks as much as possible. The management are considering improving the process by using technology and BPMS.
Assignment Requirements Your Tasks

Your work should include two parts.

Part 1: Logical Automated Business Processing:

In the report part, you need to discuss:
- The benefits, drawbacks, risks and opportunities of automation in general.

- If automation is one of the solutions for the current business process problems/issues, why and why not.
- How important it is to consider automation in the long-term business process improvement practices.
- How automation can solve the case current process issues and problems.
- The automation implementation plan (brief).

In the modelling part, you should transform one of the current BPMN level 2 model(s) into a logical automated model that shows how the process can be automated by a process engine (BPMS). It should clearly show how each participant communicates with the process engine and what data is transmitted. You only need to consider the ‘happy' path when everything goes smoothly or ONE of the sub-processes.

Advice for logical Automated Design

- The automated design model must contain exactly one Executable pool (for the process engine). In the executable pool, there can be no user or manual tasks. There may be service tasks. All parties should communicate with the BPMS. It will require BPMN Level 2 elements.
- The automated logical design model will in general have many non-executable pools, one for each internal participant, generally human. Non-executable pools may contain just process fragments. Some of them may be no start or end events. Both level 1 and level 2 BPMN are acceptable.
- A non-executable pool interacts with the executable pool (BPMS) by Message Flows. A Message flow will connect with a Message Event in the executable pool and a task in the non-executable pool.
- The logical automated design model will have many white-box pools, one for each external participant. An external participant may interact with either an internal participant in a non-executable white pool, or directly with the process engine in the executable pool.
Part 2 Executable Automation Design by using Bizagi Studio or UIPath Community edition (Optional, attempt the task will gain up to 10 bonus marks)

Automation of the main BPMS pool with optional extension into one or more sub processes. This must be implemented by using an Automation tool, such as Bizagi Studio, Signavio Workflow Accelerator, or UIPath community edition (A copy of the automated model should be in the report appendices and the actual automation file(s) to be submitted via the modelling submission link). It is recommended that students use Bizagi Studio, since Signavio Workflow Accelerator has limited automation capabilities, and UIPath requires strong technical skills. Please note that:

- University cannot install Bizagi Studio into any labs due to the licencing requirements. However, similar to Bizagi Modeller, it is easy to install into your own computer, it is free for individual users.
- Similar to Bizagi Modeller, students with Macs that are not capable of running a Windows emulator will not be able to install Bizagi Studio. If you want to try, you need to find an alternative automation tool.
- UIPath does not include forms building capability so this must be provided by another toolset that is well integrated with UIPath such as Visual Studio. UIPath is widerly used in the industry, but for our unit study, as it involve a lot of work, we do not suggest.
Advice for executable Automated Design
- The automated design should address the whole of the main processing pool, and may be extended to address one or more of the sub processes. So we suggest you to focus on a ‘Happy Path'. It should be possible to ‘complete' the end-to-end process by traversing from the start event to any of the end events.
- User or manual tasks may be included in the solution however these should be automated wherever this is feasible. The design may also include service tasks that are automated via web services or toolset integrations.
- As much as possible of the underlying business data required to support the process should be captured via data forms in the automation solution. The design should also include the capability to review the historical data associated with each completed process instance.
- Business rules need to be incorporated into the automated design to ensure that activities, gateways and process flows are all executed correctly. This may involve validating data, performing checks, making calculations and updating business data.
- A minimum of one hundred unique process executions should be undertaken to verify the automated design. The record of these process instances, and the associated business data, must be submitted with the project work.
Submission Requirements
Just submit a single MSWord. Archives with multiple files and/or subfolders will not be accepted.
- A word-processed report of around 500 or +10% words which includes:
o Executive Summary (not included in the word count)

o Table of Contents (not included in the word count)
o Introduction
o Main body which includes:
- The benefits, drawbacks, risks and opportunities of automation and if automation is a process improvement option for the case provided. Why and why not.
- How automation can solve the case current process issues and problems.
- The automation plan (brief)
- Assumptions and limitations.
o Conclusion
o References (not included in the word count)

Attachment:- case study description.rar