This document contains an instructional text style and an instructional list bullet style, both identifiable in blue paragraphs.

Prior to finalising your document ensure you remove all instructional text. To do this: Word 2003 Right click on any blue paragraph. From the menu Select text with similar formatting. Hit Delete on your keyboard. If instructional text bullet styles are present click on any blue paragraph bullet style and repeat the step. Word 2007 Right click on any blue paragraph. From the menu select Styles and then Select text with similar formatting. Hit Delete on your keyboard. If instructional text bullet styles are present click on any blue paragraph bullet style and repeat the step. NB: Page and sections breaks may be out of alignment until all instructional text is removed.

AIM BP.080 Future Process Model

Type the Programme Name below if applicable. Delete the line if not required.

<Programme Name>
Follow these steps to set Document Properties. Word 2003 Open File/Properties/Summary. In the Subject field enter the Project Name. In the Author field enter Your Name. Click OK and save the document. Word 2007 Click MS Office Button/Prepare/Properties. In the Subject field enter the Project Name. In the Author field enter Your Name. Save the document. Update Fields You must now update these fields in the document. Click on a field and then the F9 key. Ensure you update fields on the cover page and headers in all sections of your document.

<Set Project Name in Document Properties>

<Component Name>
Document Identification File name: 87394043.doc
Information Technology Services

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Document Identification Version: Status: Date: Prepared by: Contributors:

The status field should indicate whether the document is Draft or Approved. Contributors are stakeholders that have contributed directly to the contents of this document.

Responsible Authorities Project Sponsor: Project Manager: Senior User: Service Owner: System Owner:

Add Authorities as required.

Page 2 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Document purpose
This document is used to capture the details of the future business model including processes and how Oracle applications will be mapped to suit the Future process requirements

Table of contents
1 Introduction............................................................................................................................................4 1.1 In Scope.....................................................................................................................................4 1.2 Out of scope...............................................................................................................................4 2 Current process - <name of process>.................................................................................................6 2.1 <High level business function>...................................................................................................7 2.2 Process relationships for <high level business function>............................................................8 3 Future process - <name of process>...................................................................................................9 3.1 <High level business function>...................................................................................................9 4 Process step catalogues.....................................................................................................................10 4.1 <Process name>.......................................................................................................................10 5 To-be activities.....................................................................................................................................11 6 Open and closed issues for this deliverable.....................................................................................12 6.1 Open issues..............................................................................................................................12 6.2 Closed issues...........................................................................................................................12 7 Document control................................................................................................................................13

Page 3 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Introduction

You should provide here a brief overview of the project that is no more than two paragraphs long. This should present in as few words as possible the background and aims of the project/ component. This section must reflect the content in the Project Brief. While this may seem needlessly repetitive, keep in mind that the audience may not have seen the preceding project documents for months if at all.

1.1

In Scope

Scope statements should define the boundaries for what the project will be attempting to deliver. They may refer to subjects such as high level functionality, organisational units, roles, processes or things. Examples: Conversion of new publication data to a format suitable for the publications uploads utility in Themis. Allocation of identifiers to each University author identified in the Thomson download file. Leave approval processes for all staff at a HEW 9 level and below. Surveying requirements in support of the Quality of Teaching business processes. Upgrade of VLSCI servers in the Q3 data hall iDataplex rack.

The scope of a project, what is to be included and excluded, should have been negotiated in discussions between the project manager, senior users and the business sponsor. The following are considered to be within the scope of this effort: 1. 2.

1.2

Out of scope

List any specific exclusions from this project or programme of work. It is important to be explicit and precise with each of the statements listed here. These statements should be reviewed carefully by the project manager, senior users and business sponsor. Examples: Removal of duplicate publications. This will enable only those publications not already held in Themis and the MIS to be included Enrolments for postgraduate students. Upload of publications data to Themis Publications Workbench. Migration of data from Merlin.

Page 4 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

The following are considered to be excluded from the scope of this effort: 1. 2.

Page 5 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Current process - <name of process>

Enter a description for each of the current process. You must provide a process flow diagram You can use application-supported process flows, such as those provided in Oracle Business Models as a starting point for creating the future process flow diagrams. You can then augment these process steps by adding the process steps required by the organization to support their unique processes.

Page 6 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

D r a w in g 2

O F 1 0 6 9 : E n te r O r d e r s

D e s c r ip t io n : T h e p r o c e s s o f ta k in g c u s t o m e r o r d e r s a n d e n te r in g t h e m o n t o t h e s y s t e m .

U p d a te d B y : O r a c le C o r p o r a t io n

12 M ay, 1999

R e v . 2 .0

O F 1 0 6 9 .1 O rd e r S u b m itte d D e te rm in e w h e t h e r t h is i s a n e w c u s to m e r
E n te r C u s to m e r In fo

O F 1 0 6 9 .2 Is th is a n e w c u s to m e r? E n te r th e o rd e r
E n te r O r d e r s

O F 1 0 6 9 .3 V e r if y o r d e r p r ic e s
E n te r O r d e r s N o

O F 1 0 6 9 .4 V e rify p a y m e n t te rm s
E n te r O r d e r s

O F 1 0 6 9 .5 V e r if y c u s t o m e r ' s ta x s ta tu s
E n te r O r d e r s

O F 1 0 6 9 .6 V e r if y t h e c u s t o m e r 's p u rc h a s e o r d e r has been o b t a in e d

O F 1 0 6 9 .7 I s P O o n f il e ?
Y es

V e r i f y t h a t s a le s o rd e r m a tc h e s PO

Customer Service Representative

O F 1 0 6 9 .8 D e te rm in e w h e th e r o rd e r is b e i n g s h ip p e d t o a n o th e r c o u n try

O F 1 0 6 9 .9 I s t h is a n in te r n a tio n a l s h ip m e n t ?
Yes

O F 1 0 6 9 .1 0 V e rify th a t a v a lid e x p o rt lic e n s e is o n f i le I s a v a l id e x p o rt lic e n s e o n file ?

No

D e te r m in e w h e t h e r a le t t e r o f c r e d i t i s o n f i le

O F 1 0 6 9 .1 1 S u b m it e x p o r t li c e n s e t o a p p r o p r ia t e agency

N o No

O F 1 0 6 9 .1 2 D e te rm in e w h e t h e r a n y o th e r h o l d s s h o u ld b e p la c e d o n t h e o rd e r

D o a n y h o ld s a p p ly to th is o rd e r?

No

Yes

N o

O F 1 0 6 9 .1 3 P la c e th e a p p r o p r ia t e h o ld s o n th e o rd e r

O F 1 0 6 9 .1 4 D e t e r m in e w h e th e r th is is a ru sh o rd e r I s th is a r u s h o rd e r?
Y es

O F 1 0 6 9 .1 5 N o tify th e C u s to m e r S e rv ic e M a n a g e r o f th e ru s h o rd e r

O F 1 0 6 9 .1 6 F i le t h e o r d e r d o c u m e n t a t io n O rd e r E n te re d

Legend:
Event T e m p o ra l Event P ro c e s s S te p M anua l P r o c e s s S te p A u to m a t e d P r o c e s s S te p N a v ig a tio n C o p y r ig h t 1 9 9 8 O r a c l e C o r p o r a t io n , A l l r ig h t s r e s e r v e d E x p a n d a b le S u b -p ro c e s s D e c i s io n D a ta S to re

E x te r n a l A g e n t

2.1

<High level business function>

Use this section as required. Use one row per business function. Follow these guidelines in using the columns:
Page 7 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Event ID #: The unique ID for each event. Event: The Title/name of the Event Process Title: List the Title/Name of the process. Description of process: A description of the process related to the event. Output: A result of the process.
Event Process Title Description of process Output

Event ID

2.2

Process relationships for <high level business function>

Enter a description of the relationships between the various processes.

Page 8 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Future process - <name of process>

Explain the proposed future process. Include a process flow diagram to better explain the future process.

3.1

<High level business function>

Use this section as required. Use one row per business function. Follow these guidelines in using the columns: 1) Function ID #: A unique sequence number for each elementary business function. An elementary business function is a business function which, if started, must either complete successfully or, if it cannot complete successfully, must undo any effects that it has had up to the point of failure; it is the lowest available unit of work or task; it corresponds to a process step in a business process. 2) Function Description: A brief description, beginning with an action verb that captures the functions purpose and deliverable task (note: each task should have one deliverable). 3) Function/Owner: Title of person executing the function. 4) Type: A combination of Manual or System-Assisted, and Internal or External. 5) Note: Additional relevant information about the function.
Function ID # Function Description Function Owner Type Notes

Page 9 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

4
4.1

Process step catalogues

<Process name>

Use this section as required by the project.The process step catalogue identifies the process steps that make up the business process. It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you will also be developing process steps for each process.
ID

ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It might make sense to build significance into the process ID; for example, BM 01 might represent the first step in the Bill of Material process. Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do not hesitate to add information for clarity. For example, answer phone, record (order) information and so on. Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third piece, and so on. Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is possible to key word notes in order to later retrieve all notes with the same key word. Agent: Identify the party who is responsible for the execution and completion of the step. Automation: Identify whether the step is manual or system-assisted.
Description Frequency Notes Agent Automation

Page 10 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

To-be activities

List out in detail any key activities that need to be acarried out as part of the future process flow. This component provides details of the activities to be carried out as part of the process flow.

Page 11 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Open and closed issues for this deliverable

Add open issues that you identify while writing or reviewing this document to the open issues section. As you resolve issues, move them to the closed issues section and keep the issue ID the same. Include an explanation of the resolution. When this deliverable is complete, any open issues should be transferred to the project- or process-level Risk and Issue Log (PJM.CR.040) and managed using a project-level Risk and Issue Form (PJM.CR.040). In addition, the open items should remain in the open issues section of this deliverable, but flagged in the resolution column as being transferred.

6.1
ID

Open issues
Issue Resolution Responsibility Target date Impact Date

6.2
ID

Closed issues
Issue Resolution Responsibility Target date Impact Date

Page 12 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Document control

Approvals
Version No. Approval Date Name Title Signature/Email ref

Review history
Version No. Review Date Name Title

Version history
Version No. Version Date Summary of Changes Prepared by:

Page 13 of 14

<Set Project Name in Document Properties>

AIM BP.080 Future Process Model

Template control
Delete the template control page prior to using/publishing your document.
Template Name AIM BP.080 Future Process Model Location ITS>Projects>Project Toolbox>Templates, Guides and Tools

Template approvals
Version No. 102 Approval Date 31 Jan 2011 Name Trevor Lynn Title Assistant PMO Manager Signature/Email ref 31 Jan 2011 T. Lynn

Template review history

Version No. 100 100 101 Review Date 22 Dec 2010 17 Jan 2011 28 Jan 2011 Name Deepa Ponnappan Trevor Lynn Deepa Ponnappan Title Business Analyst Manager Assistant PMO Manager Business Analyst Manager

Template version history

Version No. 100 101 102 Version Date 17 Dec 2010 24 Jan 2011 28 Jan 2011 Summary of Changes Change to new file name and version system. Document styles update. Documents restructure. Apply edits following review. Additions to instructional text on cover page. Finalise document. Minor edits. Final review Tamara Wishart Deepa Ponnappan Prepared by Tamara Wishart

Page 14 of 14