Introduction - Rutgers University



<Project Name>Business Process ModelTable of Contents TOC \o "1-3" \h \z \u 1Introduction PAGEREF _Toc507811320 \h 31.1Purpose PAGEREF _Toc507811321 \h 31.2Assumptions PAGEREF _Toc507811322 \h 32Version Control PAGEREF _Toc507811323 \h 43Business Process Review: “As Is” Model PAGEREF _Toc507811324 \h 53.1Management Processes PAGEREF _Toc507811325 \h 53.2Operational Processes PAGEREF _Toc507811326 \h 53.3Supporting Processes PAGEREF _Toc507811327 \h 74Gap Analysis Matrix PAGEREF _Toc507811328 \h 85Implementation Plan: “To Be” Model PAGEREF _Toc507811329 \h 96Attachments PAGEREF _Toc507811330 \h 107Approvals PAGEREF _Toc507811331 \h 11IntroductionPurposeA Business Process Model is created to help with the requirements analysis and design of the proposed system. The three main purposes of a Business Process Model are to:Capture current business processes providing insight into how work is executed, who is involved, and how activities flow from beginning to end. Redesign and Improve business processes to reduce inefficiencies, drive down costs, and respond faster to customer requests. A process has to be documented before it can be redesigned. Automate existing process. The relationships of a business process in the context of the rest of the enterprise systems (e.g., data architecture, organizational structure, strategies, etc.) create greater capabilities when analysing and planning enterprise changes.AssumptionsThis document assumes that process improvement is one of the business objectives of the project and initiation has begun. Version ControlVersionDatePersonChange1.0MM/DD/YYYYInitial Document CreationBusiness Process Review: “As Is” ModelManagement ProcessesDocument processes that govern the system and/or application operations. Examples include corporate compliance, strategic planning, workforce management, product planning, and/or others that typically define the approach to decision-making and work flows.Operational ProcessesDocument, prioritize and create work flow diagrams for all operational processes that may be affected by the system and/or application.In order to best document these processes, the following information should be collected for each:Process DataDefinitionNamefunction nameObjective/Descriptionpurpose of the process or business objective fulfilledInput(s)who/what is required to execute the processSteps:sequential activities needed to complete the processOutput(s)who/what is the desired result of the processException(s)special case that circumvents the processMeasurement(s)(if applicable) duration or quantity of inputs/cycles needed to complete the processPriorityHigh, Medium, Low based on importance to the overall projectProcess Flowchart as described above:Swim Lane Diagrams are effective ways to visually represent processes via cross-functional flowcharts. Activities are grouped by lanes symbolizing functional areas. This highlights job sharing and often helps to identify supporting/sub-processes in those areas.Example of horizontal swim lane:Example of vertical swim lane:PAYROLL PROCESSSupporting ProcessesDocument sub-processes that will support the core processes, i.e. finance, service center, etc.Gap Analysis MatrixThe goal of gap analysis is to identify the gap between current processes with potential processes to improve performance. The two questions answered should be “Where are we now?” and “Where do we want to be?”In order to best analyse each process and document gaps, a chart should be created with the following information:Gap Analysis DataDescriptionProcess NameReference name of the operational process being analysedCurrent StateSummarize how the process runs today; reference operational process stepsDesired StateSummarize how the process needs to run better or could remain the sameGap Identification(Yes –or – No) Identify if gap(s) exists between the current state and desired stateDeficiency/ImplicationDescribe the gap(s) discoveredFactorsDescribe limitations and/or causes of the gap(s)Action PlanDescribe plan for improvement in order to reach the desired process state Implementation Plan: “To Be” ModelDetail overall action plan steps, timeline, and resources needed to close the gaps discovered. Create new work flow charts for processes in their desired state.Process NameThe current gap(s) will be addressed by…. New Process Flow DiagramAttachmentsList attachment name(s) or insert embedded file/hyperlink(s) to be included as supporting documentation ApprovalsThe individuals below have reviewed and approve the plan outlined in this document.APPROVED BY:Project RoleName and TitleSignature/ApprovalDate ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download