AIM BP.080.

3 FUTURE PROCESS MODEL Office of Shared Services Build Stage 1 Note: This document is current as of Build Stage 1 (26th October 2005) and will be updated further during the Build Phase. Author: Creation Date: Last Updated: Document Ref: Version: Oracle Consulting September 15,2005 October 19, 2005 5.00 3.0

BP.080.3 Future Process Model Doc Ref: 5.00 Document Control Change Record 4 Date 15-Sep-05 15-Sep-05 22-Sep-05 27-Sep-05 12-Oct-05 19-Oct-05 Author Oracle Consulting Mark Price Mark Price Mark Price Glyn East Mark Price Version Change Reference No Previous Document Baseline version Added Payroll Information Issued Updated Payroll information - Issued Included AR, updated after Build St age 1 - Issued 0.1 0.2 1.0 2.0 3.0 Reviewers Name Dean Cunnane Stan Toohey Phil May Position Oracle Solution Architect Business Processes Lead, HR and Payroll Busin ess Processes Lead, Finance Distribution Copy No. 1 2 3 4 Name Library Master Glyn East Ian Grundy/Jason Pentony Location Project Library Oracle Project Manager OSS Business Solution Project Ma nagers Note To Holders: If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document c ontrol purposes. If you receive a hard copy of this document, please write your name on the front cover, for document control purposes. File Ref: BP080 OSS Future Process Model v3.0.doc (v. 3.0) Company Confidential - For internal use only Page ii

BP.080.3 Future Process Model Doc Ref: 5.00 Contents Document Control ............................................................... ................................................. ii Introduction............... ................................................................................ ............................ 5 Chart of Accounts ............................... ................................................................................ .. 6 Multiple Organisations .................................................... .................................................... 7 Sets of Books ........... ................................................................................ ............................... 8 Accounting to Financial Reports .............. .......................................................................... 9 Sub ledger Journals to Post ........................................................ ................................... 9 Budgets to Approval ...................... ............................................................................. 10 Taxation....................................................................... .................................................. 18 Period End Close to Financ ial Reports .................................................................... . 19 Receipt to Assets ......................................................... ................................................. 20 Assets to Depreciation .... ................................................................................ ............ 24 Bank Statement to Reconciliation ............................... ............................................... 28 Credit to Cash............... ................................................................................ ................ 29 Statement to Collections ................................... .......................................................... 31 Project Costing .. ................................................................................ .................................. 33 Plan to Project Budget.................... ............................................................................. 33 Execution to Asset ............................................................ ........................................... 37 Analysis to Closure ............. ................................................................................ ........ 45 Human Resources..................................................... .......................................................... 47 HRMS Foundation... ................................................................................ .................... 47 Recruitment ............................................ ...................................................................... 52 Learni ng Management................................................................... ............................. 58 Performance Management ........................ ................................................................. 64 Occupationa l Health & Safety............................................................... ..................... 68 Workers Compensation .................................. ............................................................ 77 Workplace Equity and Dispute Resolution ........................................................ ..... 82 Procure to Pay ........................................................ ............................................................. 85 Requisition to Receipt Direct for Procurement.................................................. ... 85 Catalog Setup to Management.............................................. ..................................... 87 Click to Requisition .................. ................................................................................ ... 88 Requisition to Receipt Indirect for Procurement.......................... ........................ 89 Requisition to Receipt Indirect for Accounting ..... ............................................... 91 Supplier Invoice to Payment.. ................................................................................ .... 94 Supplier Return to Debit................................................ ............................................. 96 Supplier Return to Replacement

............................................................................... 97 Payroll ..................................................................... ............................................................. 98 Time Collection to Payroll..................................................................... ..................... 98 File Ref: BP080 OSS Future Process Model v3.0.doc (v. 3.0) Company Confidential - For internal use only Page iii

BP.080.3 Future Process Model Doc Ref: 5.00 Payroll to Payment ............................................................. ......................................... 99 Payroll Awards Structure........... .............................................................................. 1 00 Grade Step Progression ...................................................... ...................................... 103 Manage Employee Payroll Data ........ ...................................................................... 104 Overp ayments......................................................................... ................................... 105 Salary Packaging........................ ................................................................................ 106 Multiple Assignments....................................................... ........................................ 109 Year End Processing................ ................................................................................ .. 112 Termination to Payroll .................................................. ............................................ 113 Absence to Payroll ............ ................................................................................ ......... 114 Open and Closed Issues for this Deliverable ...................... .......................................... 117 Open Issues...................... ................................................................................ ........... 117 Closed Issues .................................................. ............................................................ 117 File Ref: BP080 OSS Future Process Model v3.0.doc (v. 3.0) Company Confidential - For internal use only Page iv

Doc Ref: 5.00 Introduction The document serves as a summary of the results of the Conference Room Pilot (CR P 2.2) and details all business flow diagrams developed during this process. Con ference Room Pilots workshops were conducted for the following business flows Ac counting to Financial Reports Procure to Pay Human Resources Credit to Collectio ns Project Costing Conference Room Pilot 2.2 focused more on the underlying details below the stand ard Oracle Business Flows to draw out detailed requirements and to give the team s a consistent methodology for capturing this data. As such, teams were asked to consider the following topics during the Conference Room Pilot workshops for ea ch of the detailed flows: Interfaces Data Migration Security Integration Touchpo ints Documents attributable to the process Reports Portal Requirements Additiona l Setup requirements Workflows Templates Other Requirements This document summar ises the detailed business process flows developed during this period, as well a s a overview of each process. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 5 of 117

Doc Ref: 5.00 Chart of Accounts The Chart of Account (Accounting Key Flexfield) structure forms the foundation f or all Oracle Applications with an accounting impact. It is used to record accou nting transactions, balances and to perform financial reporting. The chart of ac count structure may contain up to a maximum of 30 segments however, such a large number of segments is not recommended. Typically, a chart of account structure containing approx 4-8 segments is generally sufficient for financial reporting p urposes. Design Council has signed off the Chart of Account Framework. The follo wing Accounting Flexfield structure will be configured within the applications m oving forward. No. 1 2 3 4 5 6 Segment Name Entity Cost Centre Account Fund Project Agency Defi ned Example Length 3 7 6 3 8 6 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 6 of 117

Doc Ref: 5.00 Multiple Organisations The diagram below depicts the CRP 2.2 multi-org structure based on the Design St atement of Works document. This forms the foundation for the proposed structure within the Oracle Applications but does not represent the final solution. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 7 of 117

Doc Ref: 5.00 Sets of Books Within the Oracle Applications, the set of books is considered to be the highest level for financial reporting. It partitions and secures GL accounting informat ion such as journal entries and account balances and is defined by:1. 2. 3. Cale ndar Currency Chart of Accounts To determine the need for a multicompany organisation structure, and therefore mu ltiple sets of books, it is necessary to understand the financial information fo r each agency. You need multiple sets of books if one of the following is true: You have agencies that require different Chart of Account structures to record i nformation about transactions and balances. At this stage, the proposed solution will have a single chart of account structure to be used for all entities. You have agencies that use different accounting calendars. The proposed solution wil l have a single calendar (1 July 30 June) with 12 monthly periods and one adjust ing period for year-end finalisation of accounts. You have agencies that require different functional/base currencies and report in another base currency Only one Set of Books is proposed. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 8 of 117

Doc Ref: 5.00 Accounting to Financial Reports Subledger Journals to Post Process Summary Subledger Journals to Post demonstrates the business processes f low covering the creation of journal entries into the general ledger from import ed sources. This sub flow also supports the entry of manual journals and the pos ting of all journal entries residing within the general ledger. Chart of account s (CoA) maintenance will be a centralised function. The process flow diagram at a lower level has been included within this document. Process Flows Detailed pro cess diagrams developed during the Conference Room Pilot phase for Process FM110 9 and FM0507. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 9 of 117

Doc Ref: 5.00 Budgets to Approval Process Summary For the Whole of Government (WoG), agencies are responsible for the development of their budgets, complying with all Department of Treasury and Finance (DTF) budgeting requirements and deadlines. The Office of Shared Service (OSS) is responsible for managing the Oracle Financial Analyser (OFA) as the Wo G Budget tool, developing and maintaining common templates within the system. As the discipline of budgeting and forecasting is agency-specific, budget data pre pared in OFA with be developed using differing types of budgetary techniques, in cluding Top Down, Bottom Up, Zero-Based and Marginal. In addition, agencies may have their own budgeting criteria, or budgeting perspectives for modeling their budget. External data or non-financial BP080 OSS Future Process Model v3.0.doc Company Confidential Page 10 of 117

Doc Ref: 5.00 data may need to be loaded into budgeting system for such purpose. For example, FTE rate for each agency is needed from HR system for FTE costs budgeting. Durin g the budgeting cycle, there is a budget approval processes within each agency t o review and approve the budget submitted from subordinated budget users. This p rocess may be repeated several times until the budget data is approved and final ized. Once this process is completed the Agency is responsible for: Submitting t he approved budget data to the shared data set, held by the Office of Shared Ser vice (OSS), for uploading into the General Ledger; Producing operating and capit al budget submissions for DTF and uploading adjustments in the Adjustment Tracki ng Module (ATM) of Treasury Information Management System (TIMS). Timely budget data submission and uploads are essential for up-to-dated informat ion required to support financial reporting and analysis. Descriptive Overview o f Budgeting & Forecasting Oracle Financial Analyzer (OFA) allows all people with budget responsibilities within an agency to have direct access to the system. L ine Managers will be able to prepare budgets and submit their budget information directly into the OFA budgeting system for consolidation, analysis, review and approval. Within each agency, there is an internal review and approval process d uring the budgeting cycle. Management at differing levels will review the budget data submitted by subordinates, then approve or reject the budget data. Once th e budget is finalized the agency will submit the data to the shared data set, ma intained by OSS, for upload into the general ledger. Additional data files will also be generated by the Agency for upload into the ATM of TIMS, satisfying DTF budgetary requirements. Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 11 of 117

Doc Ref: 5.00 The diagram above depicts the processes of extracting information from the Gener al ledger to OFA and the development and maintenance of budget templates in OFA. The Oracle Applications General Ledger Super User and OFA Super Administrator i n OSS are responsible for these processes. This process starts with extraction o f CoA structures and financial data from the GL to OFA. The standardised GL Link for integration between Oracle General Ledger (OGL) and OFA, allows for Chart o f Account (CoA) information and financial data balances to be extracted and load ed into OFA, as required for purpose of budget development and forecasting. Once the extraction from GL is complete, using the OFA loading processes the data is loaded into the shared database by the OFA super administrator. From the GL upd ate, OSS budget team members are able to revise existing templates or develop ne w budgeting templates within OFA. These budgeting templates are then distributed within OFA for Agency use. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 12 of 117

Doc Ref: 5.00 The process of budget development is agency specific. Budget data prepared in OF A can be developed using differing types of budgetary techniques, including Top Down, Bottom Up, Zero-Based and Marginal. A majority of Agencies develop their b udgets using a bottom up approach. Data is developed at a lower level, such as i ndividual cost centre, program or activity. Analysis of the budget can be perfor med a number of ways, from the traditional organisational structure to business oriented budgeting. As an agency budget data will be consolidated within OFA, re ports can be generated from the system to effectively analysis this data. For ex ample, analysing the comparison between the developed budget to budget targets. To facilitate budget development by Agencies, external data can be loaded into O FA. For example the Public Service Award rates for Travel. This external data ca n be loaded at the OFA Super Administrator level and then shared across Agencies . The diagram above depicts the internal budget approval process within each agenc y. Within the OFA system architecture, data for each agency is stored and manage d in a centralised shared database. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 13 of 117

Doc Ref: 5.00 When Line Managers have finalised entering their budget data into Budget templat es, they will need to update an approval log in OFA. This is to provide informat ion on budget status and budgets that require review and approval. An OFA report on this approval log can be generated and published to the portal page for revi ew by the Agency's Budgeting Officers and Approvers of the submitted budgets. The Approvers of submitted budgets will be required to log into the OFA system to re view the budgets. After the budget data is reviewed, the budget will either be a pproved or rejected. The budget status will then have to be updated in the appro val log. If the budget is rejected and requires additional work this will also h ave to be indicated in the log with a reason. For budget data to be upload into the General Ledger module for reporting and an alysis, an Agency's approved budget needs to be submitted to OSS shared data set. The diagram above depicts the process for submitting a budget from an Agency to the OSS shared data set. Agencies are required to freeze the budget data to ensu re that no further updates occur to the approved budget. The Agency Administrato r submits the approved budget into the shared dataset at the agency level. This process is required to align the budget to the CoA structure within the General Ledger. The Agency Administrator submits the shared dataset controlled by the Ag ency to the shared dataset controlled by the OSS. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 14 of 117

Doc Ref: 5.00 The process flow diagram above depicts the main tasks involved in importing the approved budget data from OFA into the GL system. This write back process will c ommerce after agencies have submitted their finalized approved budget to the OSS shared data set. Using the standard OFA-GL Link set up, the OFA super administr ator in OSS will submit the data write back to the GL. This data will be written back to specific budgets defined in the GL. During the write back process, CoA account combinations for the budget data will be created in GL. As part of this process it is necessary to maintain the budget organisations, after the budget w rite back to the GL, to ensure that the new combination are assigned to a budget organisation. After this write back process is competed, standard reports can b e generated or a FSG reports can be created by Agencies as a means of validating the loaded budget. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 15 of 117

Doc Ref: 5.00 OFA standard functionality allows for the process of developing and planning bud gets data to be Agency specific. For examples differing budgetary approaches wit h can be taken are: Target budgeting using a top-down approach. In this techniqu e budget data is entered at a high level and driven down to cost centres. Cost c entre Managers then provide the relevant detailed budget information and align t heir programs to the allocated budget target. Bottom up approach. For this techn ique Line Managers develop their budgets based on the Agency objectives at a det ailed Project or Cost Center. To assist with the formulation of an Agency's budget , WoG and Agency specific budget models can be developed within OFA. This modeli ng can includes the use of budgeting rate tables for budget planning and where n ecessary the upload external data via flat files to assist with this process. Agencies are required to load their approved budget into the Adjustment Tracking Module (ATM) of Treasury Information Management System (TIMS). This is a Depart ment of Treasury and Finance (DTF) budgetary requirement. The diagram above depi cts this process. To allow for budget data to be uploaded into the ATM of TIMS i n the correct format, several mapping tables will be defined within OFA. The fir st mapping sequence will map the GL CoA accounts to the TIMS accounts. This mapp ing table will allow several GL accounts to be mapped into a single TIMS account . This table is populated during data loading. The second mapping sequence will map the TIMS accounts to the Counter Party Identifier (CPID). Most Accounts can be mapped to a single CPID. However for accounts that have to be mapped to sever al CPID, the amount for these accounts can be split based on a ratio defined by each agency. The Agency Administrator will be required to review and adjust the mapping prior to exporting the budget data. The Agency Administrator will submit a task to export budget data from OFA after reviewing all of the mapped informa tion in their shared database. The text files generated will be used for uploadi ng into the ATM of the TIMS system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 16 of 117

Doc Ref: 5.00 For Agencies using the Oracle Project Costing Module, project budgets developed within OFA will need to be interfaced back to the Project Costing for reporting purposes. The diagram above depicts this process. In order to facilitate the pro cess, the budget within OFA has to be consolidated at an Agency level. A mapping table will be used to correlate the projects defined within Project costing aga inst the projects defined within OFA. Agencies will be responsible for reviewing and updating the mapping table prior to generating the data files from within O FA. Once completed, Agencies will need to submit a task to export the budget dat a from OFA into a text file format for uploading into the Project Costing module . All variance analysis reporting will be performed out of the General Ledger modu le. Users will be provided access to run reports from either the core applicatio n or by running reports using Oracle Report Manager. The later has functionality for publishing reports to the portal page. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 17 of 117

Doc Ref: 5.00 Variations can occur by: Incorrect coding of expenditure Unplanned expenditure D elays in posting expenditure Delays in Agency programs Incorrect budget amounts established. Variations to expenditure if proven can be corrected by completing a journal using the Web ADI functionality. amendments to budget are performed wi thin OFA and an updated Budget will be uploaded to the GL. All Taxation Process Summary The Taxation (GST Reporting) business flow consists of three sta ges. 1. 2. 3. GST Governance: Ad Hoc compliance checks during the processing per iod. BAS Reconciliation: Reconciliation of BAS as per ASG/ASSIST GST Toolkit rec ommended methodology. BAS Lodgement: OSS and Agencies' review of BAS and subsequen t OSS lodgement of BAS returns. Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 18 of 117

Doc Ref: 5.00 Period End Close to Financial Reports Process Summary Period End Close to Financial Reports business flow demonstrates the business pr ocesses for closing the current period and open the next period in the subledger s. For the CRP 2.2, this covered the following modules: Purchasing Payables Proj ect Costing Fixed Assets Receivables General Ledger The flow also demonstrates t he relevant processes impacting the General Ledger such as entering period end j ournals, generating recurring, mass allocation, reversing journals and the recon ciliation of control account balances back to subledgers. The process for import ing all subsystems journals is covered in the BF140 Subledger Journals to Post d ocument. Lastly, the generation of statutory and management reporting is also in cluded in this flow, particularly reporting from the General Ledger module howev er, detailed reporting requirements are still being finalized. Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 19 of 117

Doc Ref: 5.00 Receipt to Assets Process Summary Receipt to Assets business flow demonstrates the business processes for recordin g fixed assets. This flow enables users to manually enter assets, transfer invoi ce lines marked as assets in accounts payable as Mass Additions to Oracle Assets , transfer capitalizations from Oracle projects, and use ADI and/or WebADI to up load Asset lines from other sources thru Excel worksheet. This also allows expor ting of Asset information into a file than can be sent to 3rd party systems. Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 20 of 117

Doc Ref: 5.00 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 21 of 117

Doc Ref: 5.00 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 22 of 117

Doc Ref: 5.00 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 23 of 117

Doc Ref: 5.00 Assets to Depreciation Process Summary The Assets to Depreciation business flow demonstrates the business processes for maintaining fixed assets and calculating depreciation. This flow enables users to perform maintenance for individual assets or a range of assets. The business flow also covers recording of physical inventory, transfer, reclassification, ad justment, revaluation, retirement and calculation of future depreciation expense . Agencies use iAssets to raise and accept requests for transfer. Again this flo w shows the usefulness of webADI in entering transactions as manifested in proce ssing stocktake and dataloader in Asset Revaluation. Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 24 of 117

Doc Ref: 5.00 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 25 of 117

Doc Ref: 5.00 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 26 of 117

Doc Ref: 5.00 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 27 of 117

Doc Ref: 5.00 Bank Statement to Reconciliation Process Summary As part of the Bank Reconciliation process, OSS needs to ensure that all relevan t bank statements have been uploaded into the system and reconciled with the exi sting bank transactions. Reconciliation should be automated to a large extent. M iscellaneous bank transactions are automatically created and reconciled for bank charges etc. Whenever transactions are not reconciled, a user would investigate and manually reconcile the unreconciled lines on the bank statement. Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 28 of 117

Doc Ref: 5.00 Credit to Cash Process Summary Credit Approval to Customer As part of the Credit Management process, there is a need to ensure that custome r's credit limits are set up. The end user can set up credit limits while creating the customer information, or update it at a later stage. Based on an analysis o f the history of the customer, statements, collections, past due and aging, the credit limits may be changed. The fields act only as reference data fields unles s Order Management is used to raise sales orders and invoices there from. Order Management is not in scope for the detailed design and build/test stages of this implementation. Process Flow Process Summary Customer Master Data Creation & Maintenance Creation and maintenance of records about customers (debtors) is an ongoing acti vity in any business undertaking and happens throughout the business year. At va rious times during the year new customers need to be added or existing customers need to be updated. OSS has a requirement to create and maintain customers and customer information including addresses, contact details, phone numbers, contac t roles, banks of the customer, payment control features like payment methods an d payment terms, dunning and statement requirements, default tax codes, accounti ng information etc. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 29 of 117

Doc Ref: 5.00 Process Flow Process Summary Invoice to Cash As part of the OSS process, invoices need to be entered into the Oracle system e ither at the Shared Service Centre, or by the agencies where access to the Oracl e system is provided to the agencies. Invoices are created only when a debt need s to be created for a customer. Receipts are either received by cash or through credit card/cheques/B-Pay /EFT. These need to be captured and recorded into the system and applied to the invoices to close the customer debt. The receivables a nd revenue details from core agency systems need to be recorded into the Oracle system, either through Accounts Receivables or directly into the General Ledger BP080 OSS Future Process Model v3.0.doc Company Confidential Page 30 of 117

Doc Ref: 5.00 Process Flow Statement to Collections Process Summary As per the business requirements of the agencies and OSS, reminders need to be s ent to the customer when the invoices remain unpaid beyond the due date. In case of delay in payment, collecting officers would initiate collection activities, that need to be recorded. In a few cases, customers are assigned to debt collect ion agencies and debt recovery charges are incurred. Also, disputes may be raise d by the customers, which need to go through a process of approvals, if they are to be converted into credit memos. OSS would like to have the capability of cre ating and sending statements if and when required. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 31 of 117

Doc Ref: 5.00 Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 32 of 117

Doc Ref: 5.00 Project Costing Plan to Project Budget Process Summary Plan to Project Budget demonstrates the business process flow covering the creat ion and maintenance of a project, as well as, the addition and maintenance of a budget of a project. This sub-flow supports the manual entry of projects into th e Oracle Application and the interaction with OFA for the creation of an initial budget. In addition the sub-flow also supports the maintenance of both the proj ect details and the supporting project budget. Processes identified as being con ducted within the Agency environment, on occasion, may in fact be conducted with in the Shared Service Centre. This event arises when the Agency concerned is dee med a light project user, and has a SLA agreement with the OSS. This occurs when t he Agency may not have all of the required knowledge or access to support the en try and maintenance of both the project and budget. Process Flow OSS Draft Future Business Flow : Plan to Project Budget External Project Managem ent Enterprise Roles OSS Project Manager Agency Approver PM5801 PM5801 Extract & Extract & Maintain Maintain Project Plan Project Plan Project manager maintains the work plan for the project. Export Project Plan? No END Yes PM5802 PM5802 Export Export Project Project Plan Plan Project manager Exports project work plan from external system. External Project Management Project Definition, Creation & Maintenance PM5815 PM5815 PM5818 PM5818 Yes No Export Project Plan? PM5824 PM5824 PM5800 PM5800 Select Project Select Project Template & Work Template & Work Breakdown Structur e Breakdown Structure PM selects appropriate project template which defines work breakdown structure Define Define Project Project Details Details Project manager defines and sets up the project. Approve Approve Project Project The project is approved. Import Import Project Project Plan Plan Yes Yes Ext. Plan Update Req.? No PM5819 PM5819 Maintain Maintain Project Project Details Details

 Project manager maintains the project. Project Execution to Asset Projects, Financials Project Budgeting PM5840 PM5840 PM5827 PM5827 PM5841 PM5841 PM5828 PM5828 Import Import From From OFA OFA Import Import Project Project Budget Budget Export Export To To OFA OFA Maintain Maintain Project Project Budget Budget Project manager maintains the project budget and requests approval. Projects Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 . BP080 OSS Future Process Model v3.0.doc Company Confidential Page 33 of 117

Doc Ref: 5.00 OSS Draft Future Business Flow : Select Project Template & Work Breakdown Struct ure PM5815 PM5815.1 PM5815.1 Need to Need to create create Project Project Identified Identified Project template available ? PM5815.2 PM5815.2 Yes Is Agency Supported by OSS ? No Select Select Project Project Template Template No Yes PM5815.3 PM5815.3 Create and Maintain Project Template Select Select Project Project Template Template PM5818 Define Project Details Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 Select project template and work breakdown structure demonstrates the business f low covering the initiation of the project creation cycle. This process identifi es the project template required to be used for the creation of a project. It al so highlights if a suitable template is available, to satisfy the Agencies requi rement for creation of a project. OSS Draft Future Business Flow : Define Project Details PM5818 PM5815 Select Project Template PM5818.1 PM5818.1 Is Agency supported by OSS ? No Complete Complete Required Required Project Project Details Details Project WBS & Details Complete No Template Requires Permanent change

Yes Yes PM5818.2 PM5818.2 Yes No PM5818.3 PM5818.3 Complete Complete Required Required Project Project Details Details Project WBS & Details Complete Yes PM5824 Approve Project Amend Amend Required Required Project Project Details Details No Template Requires Permanent change PM5818.4 PM5818.4 Amend Amend Required Required Project Project Details Details Create & Maintiain Project Tempates Enterprise Roles OSS Agency Member Project Manager Yes Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 The define project details flow demonstrates the business process flow covering the population of project related details, for newly created projects. This flow also takes into account that under certain circumstances the details required f or a newly created project may not exist within the template structures. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 34 of 117

Doc Ref: 5.00 In addition, this flow identifies if the existing templates are suitable for the project, or if changes are required to project template(s), to support a shift in the Agency business requirements. OSS Draft Future Business Flow : Define Project Details PM5819 PM5819.1 PM5819.1 Identified Identified Need to Need to Amend Amend Project Details Project Detail s PM5819.2 PM5819.2 Is Agency supported by OSS ? No Amend Amend Required Required Project Project Details Details Project WBS & Details Complete No Template Requires Permanent change Yes PM5819.3 PM5819.3 Yes No PM5819.2 PM5819.2 Amend Amend Required Required Project Project Details Details Project WBS & Details Complete Yes Approve Project Execution to Asset Amend Amend Required Required Project Project Details Details Yes No Template Requires Permanent change PM5819.3 PM5819.3 No Amend Amend Required Required Project Project Details Details Create & Maintain Project Templates Enterprise Roles OSS Agency Member Project Manager Yes

Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 The Maintain Project Details flow demonstrates the business process flow coverin g the maintenance of project related details, for created projects. In addition, this flow identifies if the existing templates are suitable for the project, or if changes are required to project template(s), to support a shift in the Agenc y business requirements. OSS Draft Future Business Flow : Approve Project PM5824 Define Project Details (PM5818) Maintain Project Details (PM5819) PM5824.1 PM5824.1 Is Agency supported by OSS ? No Effect Effect Project Project Status Status Change Change Maintain Project Details Yes No PM5824.2 PM5824.2 PM5824.4 PM5824.4 PM5824.5 PM5824.5 Effect Effect Project Project Status Status Change Change Workflow Workflow Status Status Change Change Invoked Invoked Agency Agency Review of Review of Workflow Workflow Approved ? Yes PM5824.3 PM5824.3 Enterprise Roles OSS Agency Member Project Manager Notify Notify Agency Of Agency Of Projects Projects Availability Availability Execution to Asset Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 Project Approval demonstrates the business process flow covering the approval of a created project, enabling the project to incur expenditure. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 35 of 117

Doc Ref: 5.00 This sub flow supports the use of a project approval workflow, in the event that the Agency has created and approved the project. Under certain circumstances th e Agency may have a SLA with the OSS, which requires the OSS to act as an agent and create the project, on behalf of the agency. In this case where the project is deemed to be pre-approved a workflow is not invoked. OSS Draft Future Business Flow : Import Project Budget PM5827 OFA Budget Tool Execution to Asset PM5827.1 PM5827.1 Budget Budget Loaded Loaded From From OFA OFA Load Successful Yes No PM5827.3 PM5827.3 Correct Correct Interface Interface Rejection Rejection PM5827.2 PM5827.2 Review Review Rejection Rejection Reason Reason Enterprise Roles OSS Agency Member Project Manager Yes Rejection is Interface Related No OFA Budget Tool Maintain Project Details Copyright 2005, Oracle Corporation. All rights reserved. August 25, 2005 Release 11i.10 Slide 1 Import Project Budget demonstrates the business process flow covering the adopti on of an initial project budget. OFA is deemed to be OSS budgeting tool and as s uch is the source of approved project budgets in the first instance. OSS Draft Future Business Flow : Maintain Project Budget PM5827 PM5828.1 PM5828.1 PM5828.2 PM5828.2 PM5828.3 PM5828.3 PM5828.4 PM5828.4 Identified Identified Need to Need to Amend Amend Project Budget Project Budget Is Agency Supported by OSS ? No Maintain Maintain Project Project Budget Budget Submit Submit Project Project Budget Budget Change Change

Review Review Project Project Budget Budget Change Change Yes PM5828.8 PM5828.8 PM5828.7 PM5828.7 Yes PM5828.5 PM5828.5 Submit Submit Project Project Budget Budget Change Change Maintain Maintain Project Project Budget Budget Budget Correction Required Review Review Rejection Rejection Reason Reason No No Approved No PM5828.9 PM5828.9 PM5828.6 PM5828.6 Advise Advise Agency of Agency of Budget Change Budget Change Completed Complete d Identify Required Identify Required Correction for Correction for Rejection Reje ction Reason Reason Yes Maintain Project Details PM5828.10 PM5828.10 Review Review Changed Changed Budget Budget No Correct OFA Budget Tool Execution To Asset Yes Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 36 of 117

Doc Ref: 5.00 Maintain Project Budget demonstrates the business process flow covering the amen dment and alteration of a project budget. Initial budgets are loaded from OFA, u sing the PM5827 Import Project Budget process, however changes to project budget s are identified and processed using this business flow. Where project budgets h ave been amended within the PA application the process includes a workflow proce ss to approve any budget changes. The budgets held against projects provide a re porting aspect only and are not used for any encumbrance or expenditure checking . Where budgets are altered within PA, the change is uploaded to the OFA tool to enable the change to be effected within the GL. Execution to Asset Process Summary Project Execution to Asset process flow demonstrates the business process flow c overing the creation and maintenance of expenditure transactions, as well as the passing of costed expenditures to the Oracle Fixed Assets application. The sub flow supports the manual entry of expenditure batches, processing of integrated transactions and the interface of asset and financial data to Oracle Fixed Asset s. The OSS operates in an agent capacity and is responsible solely for the proce ssing of data in a timely manner, on behalf of the Agency. The high level flow b elow is identified in more specific details below. Process Flow OSS D raft Future Business Flow : Project Execution to Asset Project Expenditures PM 5857 PM5857 PM5848 PM 5848 PM 5851 P M5851 Plan to Pr oject Bud get Process Process Project Project E xpe nd itures E xpe nd itures O SS periodic ally im port an d pr oc ess trans actions. Ma nage Ma nage Project Project Com m itm ents Com m itm ents Create project r elated purch as e requisition an d purch as e orders. PM5862 PM 5862 Process Project Process Project Supp lier Supp lier Invo ice Invo ice E xpe nd i tures E xpe nd itures Su pplier invoic es m atch ed an d proc ess ed in O S S.. PM5863 PM5863 PM5858 PM 5858 Enterprise Roles O SS Agenc y M em ber Pr oject M anager Process Process Project Project Allocatio ns Allocatio ns Project alloc ations pr oc ess, bas ed on agreed alloc ation schedules. Ma nage Ma nage Project Project E xpe nd iture E xpe nd iture Adjustm ents` Adju stm ents` Project m an ager reviews project ch arges an d advis es of nec ess ary adjustm ents. Process Process Project Project E xpe nd iture E xpe nd iture Adjustm ents Adjus tm ents Project expen diture adjustm ents proc ess in O SS as r equired P rojects, P urchasing, F ina ncia ls

Project Expenditures PM 5860 PM5860 PM5864 P M5864 PM5865 PM 5865 Generate G enerate Fina ncia l l Fina ncia Tra nsactio ns Tra nsactio ns Th e proc ess es required to gen er ate financial trans action to G en eral ledg er are su bm itted. Ma nage Ma nage Project Project Assets Assets Project M an ager create relevant ass ets within th e Capital projects. G en era te ass et lin es to allow interfac e to Ass ets. Process Process Project Project Assets Assets Th e proc ess to transfer ass ets plac ed into s ervic e in subm itted. Analysis to Project Closure Receipt to Assets P rojects, F inancials Copyright 2005, Oracle C orporation. A ll rig hts reserved. A ugust 25, 2005 R e lease 11i.10 Slide 1 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 37 of 117

Doc Ref: 5.00 O SS D raft Future B usiness Flow : P roject E xecution to Asset P M 5857 Pr ocess L abor Ho urs Pr ocess L abor Costs Pr ocess Burde n C osts Pr ocess M isc. Expe nditures P M 5857.1 P M 5857.1 P M 5 857 .2 P M 5 857.2 P M 5857.3 P M 5857.3 Project Expe nd iture Project E xpe nd iture Source :: Source Labor Labor H ours H ours Project Expe nd iture Project Expe nd iture Source :: Source Labor Labor C ost $ C ost $ Project E xpe nd iture P roject E xpe nd iture Source :: S ource Burde n C osts Burde n C osts P M 5 857 .4 P M 5 857 .4 Project Expe nd iture Project Expe nd iture Source :: Source M isc. M isc. E xpe nd itures E xpe nd itures Enterprise Roles O SS Agenc y M em ber Pr oject M anager PM 5857 Pr ocess Projec t Expen ditures P M 5857.5 P M 5857.5 P M 58 57 .6 P M 5 857 .6 P M 58 57.7 P M 5 857 .7 Project E xpe nd iture Project E xpe nd iture Source :: Source Project Project A llocatio ns Allocatio ns P roject Expe nd iture Project Expe nd iture S ource :: Source GL GL A llocatio ns A llocatio ns P roject Expe nd iture Project Expe nd iture S ource :: Source U sage U sage Tra nsactio ns Tra nsactio ns P M 58 57.8 P M 58 57.8 P roject Expe nd iture P roject Expe nd iture S ource :: S ource R eve nue S o u rces R eve nue S o urces Pr ocess Project A llocations Pr ocess G L Project A llocations Pr ocess Usage T ransactions

Pr ocess Re ven ue So urces C opyr ig ht 2005, O racle C orporation. A ll rig hts rese rved. A ug ust 25, 20 05 R elease 11i.10 S lide 1 Process Project Expenditures demonstrates the business process flow covering the creation and maintenance of project related expenditures. The details provided show the numerous sources and transactions that may be incurred against a projec t. Each of these processes is described in detail and illustrated below, within a high level process identification. Specific reference should be made to each d etailed flow. O SS D raft Future B usiness Flow : Process Labor H ours PM 5857 PM 5857 Pr ocess L abor Ho urs PM 5860 G e nerate Financial Transactions No P M 5857.1.1 P M 5857.1.1 P M 5857.1.2 P M 5857.1.2 P M 5857.1.3 P M 5857.1.3 P M 5857.1.4 P M 5857.1.4 Prepare Prepare Project Project R elated R elated Labor H ours Labor H ours U pload U pload Project Project R elated R elated Labor H ours Labor H ours Subm it Subm it E xpe nd iture E xpe nd iture Batches Batches R ejected R ecords Yes Ide ntify Ide ntify R eason R eason For For R ejection R ejection P M 5857.1.8 P M 5857.1.8 P M 5857.1.7 P M 5857.1.7 P M 5857.1.5 P M 5857.1.5 C orrect C orrect D ata D ata On On Age nc y Ad vice Age nc y Ad vice Ad vise of Ad vise of C orrectio ns C orrectio ns R equired R equired N otify N otify Age nc y of Age nc y of R ejections R ejections Yes H ours D ata Error No P M 5857.1.6 P M 5857.1.6 Application Set Up M aintain Project Details N otify N otify Age nc y of Age nc y of R ejection R ejection R eason R eason Enterprise Roles O SS Agenc y M em ber Pr oject M anager C opyrig ht 2005, O racle C orporation. A ll rights rese rved. S eptem ber 2, 20 05 R elease 11i.10 S lide 1

BP080 OSS Future Process Model v3.0.doc Company Confidential Page 38 of 117

Doc Ref: 5.00 Process Labor costs demonstrates the business process covering the creation and entry of labor cost transactions. This process is used, where the Project costin g module, is not responsible for the calculation of labor costs against a projec t, using costing rates for specific individuals, but relates to the processing o f whole dollars against a project. The calculation of the charge is done outside of the Oracle application and entered as a charge against the project, as a pre costed transaction. It is perceived that Agencies will either use this process to attribute labor costs to projects or alternatively us the PM5857.1 Process La bor Hours process. Each of the processes are exclusive and do not operate in con junction with each other. OSS Draft Future Business Flow : Process Burden Costs PM5857 PM5857 Process Labor Hours PM5857 Process Labor Costs PM5857 Process Usage Costs PM5857 Process Miscellaneous Expenditures PM5857 Process GL Balance Project All ocations PM5857 Process Project Allocations PM5860 Generate Financial Transactio ns No PM5857.3.1 PM5857.3.1 PM5857.3.2 PM5857.3.2 Submit Submit Burden Burden Cost Cost Process Process Rejected Records Yes Identify Identify Reason Reason For For Rejection Rejection PM5857.3.3 PM5857.3.3 Application Set Up Maintain Project Details Notify Notify Agency of Agency of Rejection Rejection Reason Reason Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. August 25, 2005 Release 11i.10 Slide 1 Process Burden Costs demonstrates the business process flow covering the calcula tion of burden amounts to be attributed against costed transactions already know n to the Project. This process relies upon maintenance and availability of Burde n Cost Schedules being available for the data combinations entered and costed wi thin the application. Upon transition to the Shared Service center, these Burden Cost schedules will be entered as part of the Agencies original configuration. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 39 of 117

Doc Ref: 5.00 OSS Draft Future Business Flow : Process Miscellaneous Expenditures PM5857 PM5857 Process Misc. Expenditures PM5860 Generate Financial Transactions No PM5857.4.1 PM5857.4.1 PM5857.4.2 PM5857.4.2 PM5857.4.3 PM5857.4.3 PM5857.4.4 PM5 857.4.4 Prepare Prepare Misc Costs Misc Costs Expenditure Expenditure Batches Batches Upload Upload Misc Costs Misc Costs Expenditure Expenditure Batches Batches Submit Submit Expenditure Expenditure Batches Batches Rejected Records Yes Identify Identify Reason Reason For For Rejection Rejection PM5857.4.8 PM5857.4.8 PM5857.4.7 PM5857.4.7 PM5857.4.5 PM5857.4.5 Correct Correct Data Data On On Agency Advice Agency Advice Advise of Advise of Corrections Corrections Required Required Notify Notify Agency of Agency of Rejections Rejections Yes Batch Data Error No PM5857.4.6 PM5857.4.6 Application Set Up Maintain Project Details Notify Notify Agency of Agency of Rejection Rejection Reason Reason Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 Process Miscellaneous Expenditures demonstrates the business process covering th e processing of Expenditures against a project from external to Oracle sources. These transactions are processed as pre costed, in other words the Oracle applic ation is not required to apply any cost rates to these transactions and processe s the values passed from the data source. OSS Draft Future Business Flow : Process Project Allocations PM5857 PM5857 Process Project Allocations PM5860 Generate Financial Transactions

No PM5857.5.1 PM5857.5.1 PM5857.5.2 PM5857.5.2 Submit Submit Project Project Allocations Allocations Rejected Records Yes Identify Identify Reason Reason For For Rejection Rejection PM5857.5.3 PM5857.5.3 Application Set Up Maintain Project Details Notify Notify Agency of Agency of Rejection Rejection Reason Reason Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. August 25, 2005 Release 11i.10 Slide 1 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 40 of 117

Doc Ref: 5.00 Process Project Allocations demonstrates the business process flow covering the calculation of allocation amounts to be attributed against projects from a sourc e of an existing project. This process relies upon maintenance and availability of Project Allocation Schedules being available for the data combinations entere d within the application. Upon transition to the Shared Service centre, these Pr oject Allocation schedules will be entered as part of the Agencies original conf iguration. Project Allocation schedules can be quite detailed and specific atten tion should be paid to the results of each allocation run. OSS Draft Future Business Flow : Process GL Balance Project Allocations PM5857 PM5857 Process GL Balance Project Allocations PM5860 Generate Financial Transactions No PM5857.6.1 PM5857.6.1 PM5857.6.2 PM5857.6.2 Submit Submit GL Balance GL Balance Project Project Allocations Allocations Rejected Records Yes Identify Identify Reason Reason For For Rejection Rejection PM5860.6.3 PM5860.6.3 Application Set Up Maintain Project Details Notify Notify Agency of Agency of Rejection Rejection Reason Reason Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. August 25, 2005 Release 11i.10 Slide 1 Process GL Allocations demonstrates the business process flow covering the calcu lation of allocation amounts to be attributed against projects from a source of a balance in a General Ledger account. This process relies upon maintenance and availability of GL Allocation Schedules being available for the data combination s entered within the application. Upon transition to the Shared Service centre, these GL Allocation schedules will be entered as part of the Agencies original c onfiguration. GL Allocation schedules can be quite detailed and specific attenti on should be paid to the results of each allocation run. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 41 of 117

Doc Ref: 5.00 OSS Draft Future Business Flow : Process Usage Costs PM5857 PM5857 Process Usages PM5860 Generate Financial Transactions No PM5857.7.1 PM5857.7.1 PM5857.7.2 PM5857.7.2 PM5857.7.3 PM5857.7.3 PM5857.7.4 PM5 857.7.4 Prepare Prepare Usage Usage Batches Batches Upload Upload Usage Usage Batches Batches Submit Submit Expenditure Expenditure Batches Batches Rejected Records Yes Identify Identify Reason Reason For For Rejection Rejection PM5857.7.8 PM5857.7.8 PM5857.7.7 PM5857.7.7 PM5857.7.5 PM5857.7.5 Correct Correct Data Data On On Agency Advice Agency Advice Advise of Advise of Corrections Corrections Required Required Notify Notify Agency of Agency of Rejections Rejections Yes Batch Data Error No PM5857.7.6 PM5857.7.6 Application Set Up Maintain Project Details Notify Notify Agency of Agency of Rejection Rejection Reason Reason Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 Process Usage Costs demonstrates the business process covering the creation and entry of volume related transactions that require costing. This process is used, where the Project costing module, is responsible for the calculation of Usage c osts against a project, using costing rates for specific resources. OSS Draft Future Business Flow : Manage Project Commitments PM5848 PM5858 Manage Project Commitments No PM5848.1 PM5848.1

Review Review Project Project Commitments Commitments Action Required Yes Enterprise Roles OSS Agency Member Project Manager Requisition and Purchase Orde r Process Accounts Payable Invoice Process PM5848.2 PM5848.2 Advise Advise Of Of Resolution Resolution Copyright 2005, Oracle Corporation. All rights reserved. August 25, 2005 Release 11i.10 Slide 1 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 42 of 117

Doc Ref: 5.00 Manage Project commitments demonstrates the business process flow covering the i dentification and analysis of committed expenditure against a project. The flow does not highlight any specific application related activities, as the processin g and approval of project commitments is addressed within the Purchasing and Pay ables modules. Specific details can be found in each of these areas process docu mentation. OSS Draft Future Business Flow : Process Supplier Invoice Expenditures PM5857 End No PM5857.1 PM5857.1 PM5857.2 PM5857.2 PM5857 Process Supplier Invoice Expenditures Import Import Supplier Supplier Invoice Invoice Transactions Transactions Review Review Import Import Output Output Report Report Rejected Records Yes PM5857.3 PM5857.3 Maintain Project Details Amend Application Set Up Identify Identify Reason Reason For For Rejection Rejection Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. September 2, 2005 Relea se 11i.10 Slide 1 Process Supplier Invoice Expenditures demonstrates the business process flow cov ering the transfer of Supplier Invoices from the Accounts Payable module, where the invoice is processed against a project. The flow does not highlight any spec ific application related activities within the Accounts Payable area, as the pro cessing is addressed within the Payables module. Specific details can be found i n the Accounts Payable process documentation. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 43 of 117

Doc Ref: 5.00 OSS Draft Future Business Flow : Generate Financial Transactions PM5860 Process Labor Costs Process Burden Costs Sub ledger Journals to Post Process Misc. Expenditures Process Project Allocations No Process GL Project Allocations PM5860.1 PM5860.1 PM5860.2 PM5860.2 Interface Interface To General To General Ledger Ledger Process Usage Transactions Review Review Interface Interface Output Output Report Report Rejected Records Yes Revenue Transaction PM5860.4 PM5860.4 PM5860.3 PM5860.3 Correct Correct Transactions Transactions source or amend source or amend Auto A ccounting Auto Accounting Identify Identify Reason Reason For For Rejection Rejection Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. August 25, 2005 Release 11i.10 Slide 1 Generate Financial Transactions demonstrates the business process flow for the t ransfer of financial amounts from the Project module to the General Ledger. Each of the various processes identified within this document, have cause for genera ting financial transactions with the General Ledger, in particular those transac tions that have originated within the Project costing module. Each of these tran saction sources require auto accounting rules to be configured to enable the PA module to generate the appropriate General Ledger account to effect a financial posting. OSS Draft Future Business Flow : Manage Project Assets PM5864 Plan to Project Budget PM5851 Process Supplier Invoice Expenditures PM5857 Proce ss Project Expenditures PM5862 Process Expenditure Adjustments PM5858 Process Pr oject Allocations PM5865 Process Project Assets PM5860.1 PM5860.1 PM5860.2 PM5860.2 Define & Define & Maintain Maintain Project Project Assets Assets Assign Assign Project Project Assets Assets PM5865 Process Project Assets

Enterprise Roles OSS Agency Member Project Manager Copyright 2005, Oracle Corporation. All rights reserved. August 25, 2005 Release 11i.10 Slide 1 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 44 of 117

Doc Ref: 5.00 Manage Project Assets demonstrates the business flow for the identification and collation of Asset related information, where the Project Costing module is resp onsible for the transfer of assets to Oracle Fixed Assets. OSS Draft Future Business Flow : Process Project Assets PM5865 PM 5851 Process S upplier Invoice Expe nditures PM 5857 Process Project Expendit ures PM 5862 Process Ex penditure Adjustments PM 5858 Process Project Allocation s PM 5864 M ana ge Project Assets PM5865.1 PM5865.1 P M5865.2 PM5865.2 PM5865.2 PM5865.2 Generate Generate Project Project Asset Asset Lines Lines Review Review Project Project Asset Lines Asset L ines Allocate Allocate Unassigned Unassigned Asset Asset Costs Costs PM5865.1 PM5865.1 PM5865.2 PM5865.2 Fixed Assets Post M ass Additions No Rejected Lines Interface Interface Asset Asset Lines Lines To F A To F A Yes Prepared for Capitalisation Confirm Confirm W ith OSS W ith OSS Capitalisation Capitalisation Readiness Read iness Yes PM5865.1 P M5865.1 No Review Revie w Rejected Rejected Lines Lines PM5865.1 PM5865.1 PM5865.1 PM5865.1 Project Data Related Yes PM5865.2 PM5865.2 PM5865.1 P M5865.1 No Review Review Projects Projects And F A And F A Configuration Configuration Prior Period Prior Period Asset Lines Asset Lines Interfaced Interfaced to FA to FA Enterprise Roles OSS Agenc y M em ber Pr oject M anager Review Review Asset Asset Rejections Rejections

Notify Notify Agency Agency Of Of Rejections Rejections PM 5864 M ana ge Project Assets Next Period Processing Copyright 2005, Oracle C orporation. A ll rights reserved. Septem ber 2, 2005 Re lease 11i.10 Slide 1 Process Project Assets demonstrates the business process covering the generation of amounts to be capitalised, for capital projects. These amounts are then tran sferred to the Fixed Assets module, for capitalisation. Analysis to Closure OSS Draft Future Business Flow : Analysis to Project Closure Project Execution to Asset Project Execution to Asset Period End Close to Financ ial Reports Project Execution PM5833 PM5833 PM5863 PM5863 PM5839 PM5839 Project Close Out PM5873 PM5873 Manage Manage Project Project Manage Project Manage Project Expenditure Expenditure Adjustments Adjustments Project manager advises of all necessary expenditure item adjustments to the pro ject prior to the period end close. Review Review Project Project Performance Performance Project performance information is gathered and disseminated. This includes stat us reporting, progress measurement and forecasting. Close Close Project Project Project manager gathers and disseminates all pertinent project information prior to project completion. Project manager closes and archives the project. Project manager analyzes budget to actual variances by project, task or resource . Review Capital Projects Project Costing, Project Billing Option, Project Management Project Costing, Project Billing Option, Project Management Enterprise Roles Project Manager Copyright 2005, Oracle Corporation. All rights reserved. August 26, 2005 Release 11i.10 Slide 1 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 45 of 117

Doc Ref: 5.00 Analysis to Project Closure demonstrates the business process covering the analy sis of project expenditure and budgets, as well as the maintenance of a project through the project lifecycle. This sub flow supports the changing of project st atuses and review and adjustment of expenditures and budgets contained within a project. This process is solely managed through the agency and is supported by t he expenditure, budget and Project maintenance processes contained within the Pl an to Budget and Execution to Asset flows. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 46 of 117

Doc Ref: 5.00 Human Resources HRMS Foundation Process Summary The HRMS Definition Phase is the summary of a range of initiatives designed to a lign the requirements of the Government of Western Australia and the functionali ty of Oracle Human Resources Management (HRMS). These initiatives have involved representatives of the Office of Shared Services (OSS) and Oracle Consulting. In itiatives have included: Daily interactions between OSS staff and Oracle consult ants, An initial conference room pilot (CRP 2.1) based on the Request for Tender and initial understandings, Workshops following the CRP2.1 to clarify requireme nts, demonstrate functionality and prepare the subsequent CRP, CRP 2.2 to refine OSS business flows and functional needs The Oracle modules covered were Human Resource Management (Core), Human Resource s Self-Service, Oracle iRecruitment, Oracle Learning Management and Performance Management. This phase sought to confirm the suitability of Oracle HRMS to the O SS business requirements and to determine the degree of fit for functionality an d identify gaps and alternative solutions. Process Flow Depicted below is the Whole of Government Office of Shared Services Human Resour ces High Level Organisational Data Management Process. This is the process that is followed when a new organisation or position requires creating, or an existin g organisation or position requires change or reclassified. The High Level Organ isational Data Management process is broken down into more detail in the followi ng processes: Organisational Structure New / Update Position / TSA Review / New Page 47 of 117 Company Confidential BP080 OSS Future Process Model v3.0.doc

Doc Ref: 5.00 Position Data / JDF Update Position Update / Abolish (vacant) Position Update / Abolish (Surplus Employees) Position Update Specified Callings & Criteria Progre ssion positions Position Update Specified Callings & Criteria Progression positi ons (review when vacant) . Depicted below is the Whole of Government Office of Shared Services Human Reso urces Organisational Structure New/Update Process. This process is followed when a new organisation is required or an existing organisation requires updating BP080 OSS Future Process Model v3.0.doc Company Confidential Page 48 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Position / TSA Review / New Process. This process is followed when a new pos ition is required or an existing position is to be reviewed. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Position Data / JDF Update Process. This process is followed when an existin g positions data needs to be updated or the position JDF requires updating. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 49 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Position Update / Abolish (Vacant) Process. This process is followed when a position is updated or abolished and the position becomes vacant. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Position Update / Abolish (Surplus Employees) Process. This process is follo wed when a position is updated or abolished and the result of the abolishment is the creation of a surplus employee. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 50 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Position Update Specified Callings and Criteria Progression Positions Proces s. This process is followed when a position is to be reclassified. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Position Update Specified Callings and Criteria Progression Positions (revie w when vacant) Process. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 51 of 117

Doc Ref: 5.00

Recruitment Depicted below is the Whole of Government Office of Shared Services Human Resour ces High Level Recruitment Process. This is the process that is followed when a position becomes vacant and is required to be filled. The High Level Recruitment process is broken down into more detail in the following processes: Create cancy Posting a Vacancy - Open Posting a Vacancy Closed `Entry Level' Recruitment (L evel 1 clerical and admin) Applicant Process Unsolicited Applicant Process Selec tion Process Hire Process Contract for Service BP080 OSS Future Process Model v3.0.doc Company Confidential Page 52 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Create a Vacancy Process. This is the process that is followed when a positi on becomes vacant and a manager requests that the position be filled. All vacanc ies have to be interfaced to RAMS to gain clearance for posting. RAMS check all the records for a suitable redeployee before granting approval for any posting. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Posting a Vacancy Open Process. This is the process that is followed when RA MS has granted posting clearance and the Agency has decided to continue with the recruitment process. This process defines the posting of a vacancy that is post ed to all Agency websites. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 53 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Posting a Vacancy Closed Process. This is the process that is followed when RAMS has granted posting clearance and the Agency has decided to continue with t he recruitment process. This process defines the posting of a vacancy that is po sted only on the website of the Agency that raised the vacancy. Posting of this type of vacancy is only used where the opportunity is of a finite periodnot to be used for permanent appointments. Depicted below is the Whole of Government Office of Shared Services Human Resour ces `Entry Level' Recruitment Process. This is the process that is followed when a l evel 1 position becomes vacant and a manager requests that the position be fille d. All vacancies have to be interfaced to RAMS to gain clearance. RAMS refers su itable level 1 candidates from the pool database. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 54 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Applicant Process. This is the process that is followed when an employee or external applicant applies for a vacancy or a redeployee is identified as a pote ntial match for a vacancy. Please note that the lightly shaded process blocks de picted below are part of the vacancy process and are only defined in this proces s to give an indication of how the applicant process is started. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Unsolicited Applicant Process. This is the process that is followed when an applicant shows interest in a position at a government agency but there are no v acancies currently open. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 55 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Recruitment Selection Process. This is the process that the applicant goes t hrough once they have applied for a vacancy. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Recruitment Hire Process. This is the process that the applicant goes throug h once they have successfully completed the selection process. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 56 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Contract for Service/Volunteer Process. This is the process that the manager goes through to employ a contingent worker. That is, Contract for Service perso n, Volunteer or Work Experience person. These workers are not paid through the p ayroll system but require access to the system. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Pool Recruitment Process. This is the process that is followed when a manage r requests that a position is to be filled and a previous pool recruitment proce ss is identified. All vacancies have to be interfaced to RAMS to gain clearance. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 57 of 117

Doc Ref: 5.00 Learning Management The high level business flow depicted below is the Whole of Government Office of Shared Services Human Resources High Level Learning Management Process. This is the process that is followed when a Manager or employee initiate a development program for the employee. The High Level Learning Management process is broken d own into more detail in the following processes: Identify and Prioritise skill g aps Collect and analyse Learning requirements Define Learning Strategy Define Le arning Content Create Learning Delivery Framework Manage Learning Delivery Evalu ate Learning Strategy BP080 OSS Future Process Model v3.0.doc Company Confidential Page 58 of 117

Doc Ref: 5.00 The high level business flow depicts the Whole of Government Office of Shared Se rvices Human Resources Set up a Class Process. This is the process that is follo wed when a Learning Administrator establishes Courses, Offerings and Classes wit hin the Whole of Government Catalog. The Set up a Class process is broken down i nto more detail in the following processes, Build the Course Create the Offering Create the Classes BP080 OSS Future Process Model v3.0.doc Company Confidential Page 59 of 117

Doc Ref: 5.00 The high level business flow depicts the Whole of Government Office of Shared Se rvices Human Resources Enroll in a Class Process. This is the process that is fo llowed when an Employee or Manager logs into the Learning Management Homepage an d searches for and books a course. The process shows approvals and notifications . The high level business flow depicts the Whole of Government Office of Shared Se rvices Human Resources Administer and Evaluate a Class Process. This is the proc ess that is followed when a Learning Manager undertakes the administration of en rolments, evaluation and financial arrangements associated with completing cours e. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 60 of 117

Doc Ref: 5.00 The high level business flow depicts the Whole of Government Office of Shared Se rvices Human Resources Organisational Learning Paths Process. This is the proces s that is followed when there is a requirement to undertake bulk enrollment with in Learning Management. Bulk enrollments may be by Org Unit, Job Type, Level or other criteria. The high level business flow depicts the Whole of Government Office of Shared Se rvices Human Resources Individual Learning Path Process. This is the process tha t is followed when a Manager and Employee agree to establish a series of trainin g initiatives (Learning Path) for an employee. It involves creating a Learning P ath from options within the catalog and completing enrolment and approvals. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 61 of 117

Doc Ref: 5.00 The high level business flow depicts the Whole of Government Office of Shared Se rvices Human Resources Enroll in an External Class Process. This is the process that is followed when a Manager and Employee search for an appropriate Class wit hin Learning Management and cannot find one. After approval an external course can be booked. The Learning Management system is then updated through self-service. The high-level business flow depicts the Whole of Government Office of Shared Se rvices Human Resources enrolling external learner in a class Process. This is th e process that is followed to ensure that all external learners are entered into the Learning Management system after they've identified a learning activity in th e OSS System, contacted the learning administrator and enrolled in a class. The learner's organization will enter in the system as a customer via procurement. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 62 of 117

Doc Ref: 5.00 The high level business flow depicts the Whole of Government Office of Shared Se rvices Human Resources Administer Training Resources Process. This is the proces s that is followed to ensure that all new resources are entered into the Learnin g Management system and where required established as Suppliers within Oracle Fi nancial system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 63 of 117

Doc Ref: 5.00 Performance Management The high level business flow depicted below is the Whole of Government, the Offi ce of Shared Services, Human Resources High Level Performance Management (PM) Pr ocess. This is the process that is followed when a new or existing employee unde rtakes the process of setting work objectives and subsequent reviews against tho se objectives. The High Level performance Management process is broken down into more detail in the following processes: Employee Performance Planning Employee Performance Progress Employee Performance Achievement, and if required Substandard Performance. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 64 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Employee Performance Management Planning Process. This is the process that i s followed when a Manager and a person who is a new assignment set and complete Planning Meeting. Government of WA Internal Transfer of Person at Grade New Employee HRPMPP01 Employee Performance Management Internal HAD (Temporary) of Person Promotion of Person Planning Manager & Employee Manager Prepare for meeting: Check JDF Check Agency Policy and Guidelines HRPMPP06 New Assignment HRPMPP02 Set up meeting HRPMPP05 Secondary Assignment HRPMPP03 Planning Meeting Agree on: Objectives Competencies Performance Indicators Learning P aths Career Development Other employee interests HRPMPP07 Learning Management HRPMPP08 Manager & Employee Agree on meeting outcomes and set next meeting date HRPMPP09 Yes Move onto Progress Meeting Process HRPMPP10 No Escalate for resolution HRPMPP11 Process Key: Oracle Performance Mgt External system Office of Shared Services Ag ency Depicted below is the Whole of Government Office of Shared Services Human Resour ces Performance Management Employee Performance Planning Process. This is the pr ocess that is followed when a Manager and an existing employee set and completes a Planning Meeting. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 65 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Employee Performance Management Progress Process. This is the process that i s followed when a Manager and an employee meet to review the outcomes of the Pla nning Meeting and amend if necessary. It is the time that the Planning Meeting o utcomes are reviewed and amended if necessary. Any Learning Management/Career Ma nagement issues or Substandard Performance issues may also be considered. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Performance Management Manage Performance Achievement Meeting Process. This is the process that completes the Performance Management cycle. The employee and manager meet to review and assess progress made towards achieving Planning/Prog ress Meeting outcomes. Any Learning Management/Career Development issues or Subs tandard Performance issues may also be considered. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 66 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Performance Management Substandard Performance Process. This is the process that allows a Manager and Employee to work together to resolve performance issue s and develop plans and actions to resolve them. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Performance Management Separation survey Process. This is the process that i s followed when an employee leaves State Government employment or permanently mo ves to a Employees who are leaving the agency are invited to complete a survey i n regard to their employment experiences. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 67 of 117

Doc Ref: 5.00 Occupational Health & Safety Depicted below is the Whole of Government Office of Shared Services Human Resour ces Incident Logging Process. This is the process that is followed when an emplo yee logs an incident, which has occurred. The High Level Incident Logging proces s is broken down into more detail in the following processes undertaken by the: Employee Manager OSH Representative OSH Coordinator Depicted below is the Whole of Government Office of Shared Services Human Resour ces Employee Logging an incident Process. This process is followed when an incid ent needs to be logged in the system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 68 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Manager Logging an incident Process. This process is followed when a manager is notified an incident has been logged in the system. Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Representatives action in the incident logging Process. This process is followed when an OSH Representative is notified an incident has been logged in t he system BP080 OSS Future Process Model v3.0.doc Company Confidential Page 69 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Coordinators action in the incident logging Process. This process is fol lowed when an OSH Coordinator is notified an incident has been logged in the sys tem. Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Incident Report Data Process. This process is followed to meet legislati ve requirements in making incident data available to employees. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 70 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Hazard Logging Process. This is the process that is followed when an employe e logs a hazard, which has occurred. The High Level Hazard Logging process is br oken down into more detail in the following processes Employee Manager OSH Repre sentative OSH Coordinator BP080 OSS Future Process Model v3.0.doc Company Confidential Page 71 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Employee Logging a Hazard Process. This process is followed when a Hazard ne eds to be logged in the system. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Manager Logging a Hazard Process. This process is followed when a manager is notified a Hazard has been logged in the system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 72 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Representatives action in the Hazard logging Process. This process is fo llowed when an OSH Representative is notified a Hazard has been logged in the sy stem. Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Coordinators action in the hazard logging Process. This process is follo wed when an OSH Coordinator is notified a hazard has been logged in the system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 73 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Hazard Report Data Process. This process is followed to meet legislative requirements in making Hazard data available to employees Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Non Employee Occurrence Process. This process is followed when a non-emp loyee needs to report an incident or hazard to an agency where they are working or visiting so the data is captured in the system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 74 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Representative Elections Process. This process is followed when election s for OSH Representatives need to be held. Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Assessments Process. This process is followed when an OSH Representative undertakes an assessment. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 75 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Workplace Inspections Process. This process is followed when an OSH Repr esentative or OSH Coordinator carries out legislative workplace inspections. Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Health Surveillance Process. This process is followed when an OSH Coordi nator undertakes health surveillance. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 76 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces OSH Provisional Improvement Notices Process. This process is followed when a n OSH Representative in an Agency raises a provisional improvement notice (PINS) .

Workers Compensation Depicted below is the Whole of Government Office of Shared Services Human Resour ces Workers Compensation Process. This is the process that is followed when an e mployee logs a Workers Compensation Claim through to the recommendation, payment and recovery of the money. The High Level Workers Compensation process is broke n down into more detail in the following processes undertaken by the: Workers C mpensation New Claim Workers Compensation Recurrence of Injury Manager's Recommend ation on a Claim (new or a recurrence) Workers Compensation Administrator Injury Management Claims Meetings Interfaces BP080 OSS Future Process Model v3.0.doc Company Confidential Page 77 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Workers Compensation new claim Process. This process is followed when an emp loyee enters a new claim in the system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 78 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Workers Compensation Recurrence of Injury Process. This process is followed when an employee enters a Workers Compensation Recurrence of Injury for an old c laim already recorded in the system. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Workers Compensation Manager's Recommendation Process. This process is followe d when an employee has lodged a new claim or recurrence claim in the system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 79 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Workers Compensation Administrator Process. This process is followed when an employee has entered a new claim or a recurrence of injury in the system. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Workers Compensation Injury Management Process. This process is followed aft er a workers compensation claim or recurrence of injury claim has been entered i nto the system and the employee requires the injury management process to start. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 80 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Workers Compensation Claims Meetings Process. This process is followed when an employee has entered a new claim or recurrence of an injury in the system. Th e Workers Compensation administrator enters details of any claim meetings that h ave occurred between RiskCover, OSS, Rehabilitation providers and Agencies. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Workers Compensation Interfaces. The interfaces are part of the process foll owing an employee lodging a new workers compensation claim or a recurrence of in jury claim for an old claim already recorded in the system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 81 of 117

Doc Ref: 5.00 Workplace Equity and Dispute Resolution Depicted below is the Whole of Government Office of Shared Services Human Resour ces EEO Diversity Information recording Process. This process is followed when a n employee returns their diversity survey or updates their data in the system. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 82 of 117

Doc Ref: 5.00 Depicted below is the Whole of Government Office of Shared Services Human Resour ces Lodging a Breach of Standards Process. This process is followed when an empl oyee or External applicant lodges a Breach of Standards. Depicted below is the Whole of Government Office of Shared Services Human Resour ces Lodging a Formal Grievance Process. This process is followed when an employe e lodges a Formal Grievance. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 83 of 117

Doc Ref: 5.00 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 84 of 117

Doc Ref: 5.00 Procure to Pay Requisition to Receipt Direct for Procurement Process Summary This flow follows the replenishment process for inventory-planned items where re quisitions are created in Purchasing. An Agency that supports Inventory Manageme nt will have the replenishment of inventory performed by Purchase orders or Blan ket Release that can be automatically created and managed through to receipt. Re quisitions can be either generated from the Min/Max planning program and are sub mitted for review and approval by HR Position Hierarchy or created manually foll owing the similar approval process. Purchase Orders and Blanket Releases can be auto-created from requisitions and also created as Standard Purchase orders. Thi s process also covers the copying of previous PO documents to a newly created on e and purchase order cancellation. PO documents are approved depending on HR Pos ition Hierarchy and distributed to Supplier by the Suppliers preferred method of transmission. Inventory item is received from Suppliers and entered into receiv ing and located within the controlled sub inventory. NOTE# 1. 2. 3. 4. On day 1 of going live, there will be no Inventory Agencies involved. All requisitions th at required approval intervention will be authorized via Internet Procurement wh ere the Approval Hierarchy is invoked. No Purchase Orders will be issued in core Procurement without a Requisition either manual or on-line. All Gaps identified in the Requisition to Receipt - Indirect for Procurement as listed below apply to this process. PR0128.01 Additional Requisition Information for Approver in email notification PR0128.02 Approval Group listing. PR0128.03 Approval Assignment Listing. PR0128. 04 HR Position Hierarchy PR1182.01 Configure PO Create Document WF to auto creat e PO based on WoG criteria. PR0153.01 Modification to the PO print layout. Inclu de Government of WA Logo. PR0153.02 Provide functionality to print attachments. PR0153.03 Configure Fax utility. PR0153.04 Configure SMTP Email Server PR0153.05 Restrict PO Print to Agency specific orders. Secure Print PO to agency buyer. P R0153.06 Restrict to print only Agency specific PO information PR1935.01 Customi se Receipt Traveler. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 85 of 117

Doc Ref: 5.00 PR1935.02 Notify buyer and receiving location when items are not received on tim e, supported by workflow. Process Flows Approving employee approves Internet Procurement requisition or planning requisi tion. Approvals are based on WoG Position Hierarchy and Agency specific Hierarch y. Approvals will be controlled, based on the Approval Groups and Approval Assig nments, defining the employee's approval limits determined by amount, category or account code. Vacation rules are established to determine variation in approval process when Approving Officer is unavailable. Requisition Pool: Approved Requis itions then await Purchasing action or depending on criteria is automatically cr eated into an approved or un-approved purchase order. The Buyer (QA) approves the purchase order. Purchase Order approvals are based o n WoG Position Hierarchy and specific Agency Hierarchy. Approvals will be contro lled based on the Approval Groups and Approval Assignments defining the Buyers a pproval limits determined by amount, category or account code. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 86 of 117

Doc Ref: 5.00 In the case of Inventory the Inventory Controller or Inventory Buyer will have t he appropriate access levels to determine replenishment values. The Agency Lead Buyer will manage Buyer works loads, including where a Buyer is on leave or unav ailable. Catalog Setup to Management Process Summary This flow covers managing content in the I-procurement catalog, security and use r access from the establishment of catalog restrictive groups (realms), and docu ments such as Common Use Agreements (Global Contract and Blanket Agreements), In formational Catalogs, I-procurement Item Catalogs and Agency specific Local Cont ract and Blanket Order Agreements. It also includes developing buyer specific pr ice lists, which reflects pre-negotiated contracts through to uploading of suppl ier items publishing items. Data security over the visibility of contract docume nts by Agency is considered mandatory. Modifications to Internet Procurement wil l be required where Agencies share Operating Units. It is proposed to secure Age ncy agreements by the Agencies inventory organization using Sub Ledger Security. There has been no defined requirement for Supplier punch-out during CRP2.2 BP080 OSS Future Process Model v3.0.doc Company Confidential Page 87 of 117

Doc Ref: 5.00 Process Flow Click to Requisition Process Summary This flow facilitates the requisitioning process. It covers managing of user pro files, searching catalogs, shopping lists, selecting payment methods and managin g requisitions. The process commences with the Requisitioner managing their indi vidual profiles. It then provides the Requisitioner with the ability to search I -Procurement shopping lists and establish their own personal shopping lists. Req uisitioner - can obtain quotations themselves or refer request to Buyer (Sourcin g) to obtain quotes on their behalf. Requisition Approver Approval (generally fi nancial or separation of duties based) for Requisition. (Note Requisition may be auto approved depending on Financial and Procurement delegation of Requisitione r To be determine through Agency specific Approval Groups and Approval Assignmen t.) Buyer (Sourcing) obtains quotes and undertakes sourcing either in their own right or on behalf of others initiated either from a non-ERP direct approach (e. g. phone call, email, etc), in which case they obtain quotes and then prepare th e Requisition; or via an incomplete Requisition forwarded by a Requisitioner via Internet Procurement. Buyer (QA) Quality assurance of procurement process prior to issue of Purchase Order. May be involved in the sourcing process. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 88 of 117

Doc Ref: 5.00 Process Flow Requisition to Receipt Indirect for Procurement Process Summary This flow follows requisitions created in Internet Procurement for catalog and n on-catalog items. Purchase orders can either be automatically created or the Age ncy Buyer can create and managed through to receipt. Requisitions are submitted for review and approved through the HR Position Hierarchy. Purchase orders can b e generated automatically without Buyer intervention from approved requisitions or auto-created from requisitions. This process also covers the copying of previ ous PO documents to a newly created document and purchase order cancellation. Pu rchase Orders are reviewed and/or approved through the HR Position Hierarchy and distributed to Supplier by the Suppliers preferred method of transmission. Good s/Services are received from Suppliers and are either entered into Oracle Purcha sing - Receiving (Core Applications) or Internet Procurement. Where a number of Agencies are sharing an Operating Unit, document security is required. It is pro posed to secure documents such as Purchase Order, Contract Purchase Agreements ( CPAs), Blankets, Requisitions and RFQ/Quotations to specific Agencies. Currently standard functionality is unable to secure the above documents by Agency where multi agencies share the same Operating Unit. The method proposed for this is ba sed around each Agency being associated to an Inventory Organisation. Security w ould be based on the Agency's Inventory Organisation, the users Menu Responsibilit y and HR Location (Deliver To Location). Note#: There are to be no Purchase Orde rs issued in core Procurement without a Requisition either manual requisition or on-line. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 89 of 117

Doc Ref: 5.00 Process Flows Approving employee approves Internet Procurement requisition or planning requisi tion. Approvals are based on WoG Position Hierarchy and Agency specific Hierarch y. Approvals will be controlled, based on the Approval Groups and Approval Assig nments, defining the employee's approval limits determined by amount, category or account code. Vacation rules are established to determine variation in approval process when Approving Officer is unavailable. Requisition Pool: Approved Requis itions then await Purchasing action or depending on criteria is automatically cr eated into an approved or un-approved purchase order. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 90 of 117

Doc Ref: 5.00 The Buyer (QA) approves the purchase order. Purchase Order approvals are based o n WoG Position Hierarchy and specific Agency Hierarchy. Approvals will be contro lled based on the Approval Groups and Approval Assignments defining the Buyers a pproval limits determined by amount, category or account code. The Agency Lead B uyer will manage Buyer works loads, including where a Buyer is on leave or unava ilable The Buyer (QA) approves the purchase order. Requisition to Receipt Indirect for Accounting Process Summary This flow follows the accounting entries created in Internet Procurement and Pur chasing for catalog and non-catalog items. Purchase orders can either be automat ically created or the Buyer can construct and manage through to receipt. The Acc ounting method used in the Requisition to Receipt process is Accrual Accounting. E ncumbrance Accounting will not be implemented. The Account Generator process in Internet Procurement and Purchasing builds charge, budget, accrual, and variance accounts for each purchase order, release, and requisition distribution based o n the HR Deliver To Location (Attribute1 Entity code GL Segment1, Attribute2 Cos t Centre GL Segment2) assigned to the Requisitioner or chosen by the Requisition er or Buyer and the product or services category GL expense account assigned to it for non-project related general expense items and capital purchases. In the c ase of Project related requisitions or purchase orders the charge account is bui lt based on the Project Number, Project Task, Expenditure Type and Expenditure O rg. General Ledger standard security rules created by the Finance team will rest rict the Requisitioner and Buyer Agency to their allocated cost centre combinati ons and will disallow any breach of these rules. GST Tax responsibility will be managed and maintain by Accounts Payables and not captured in Requisitioning or Purchase Orders. The Purchase Orders generated will be transmitted to the Suppli er, Exclusive of GST. The Common Use Agreements will inform the Buyer that the S upplier charges or does not Charge GST on certain commodities although this will not impact on the buyers ability to create a purchase order exclusive of GST. N o accounting entry is created in the general ledger until period end, where Purc hasing automatically creates a balanced journal entry for each uninvoiced receip t. Purchasing accrues uninvoiced receipts of expense items exclusive of GST when you close an accounting period. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 91 of 117

Doc Ref: 5.00 No accounting entry is created in the general ledger for non-received purchase o rders. That is, purchase orders that have been approved and no receiving transac tion or invoices have been applied. At Period End the Uninvoiced Receipts Report is used to analyze the uninvoiced expense receipts before accrual of these rece ipts. The Receipt Accruals PeriodEnd process creates periodend accruals for the unin voiced receipts for the expense distributions. Purchasing creates an accrual jou rnal entry in General Ledger for each uninvoiced receipt. When opening the next period, Purchasing automatically reverses the accrual entries. In this flow, Req uisitions are submitted for review and approval by HR Position Hierarchy. Purcha se orders are auto-created from requisitions and also created manually. This pro cess also covers the copying of previous PO documents to a newly created one and purchase order cancellation. PO documents are reviewed and/or approved by HR Po sition Hierarchy and distributed to Supplier by the Suppliers preferred method o f transmission. Goods/Services are received from Suppliers and are either entere d into receiving (Core Applications) or Internet Procurement. Where a number of Agencies are sharing an Operating Unit, document security is required. It is pro posed to secure documents such as Purchase Order, Contract Purchase Agreements ( CPAs), Blankets, Requisitions and RFQ/Quotations to specific Agencies. Currently standard functionality is unable to secure the above documents by Agency where multi agencies share the same Operating Unit. The method proposed for this is ba sed around each Agency being associated to an Inventory Organisation. Security w ould be based on the Agency's Inventory Organisation, the users Menu Responsibilit y and HR Location (Deliver To Location). Note#: There are to be no Purchase Orde rs issued in core Procurement without a Requisition either manual requisition or on-line. Process Flows Approving employee approves Internet Procurement requisition or planning requisi tion. Approvals are based on WoG Position Hierarchy and Agency specific Hierarch y. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 92 of 117

Doc Ref: 5.00 Approvals will be controlled, based on the Approval Groups and Approval Assignme nts, defining the employee's approval limits determined by amount, category or acc ount code. Vacation rules are established to determine variation in approval pro cess when Approving Officer is unavailable. Approved Requisitions then await Pur chasing action in the requisition Pool or depending on criteria is automatically created into an approved or un-approved purchase order. The Buyer (QA) approves the purchase order. Purchase Order approvals are based o n WoG Position Hierarchy and specific Agency Hierarchy. Approvals will be contro lled based on the Approval Groups and Approval Assignments defining the Buyers a pproval limits determined by amount, category or account code. The Agency Lead B uyer will manage Buyer works loads, including where a Buyer is on leave or unava ilable The Buyer (QA) approves the purchase order. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 93 of 117

Doc Ref: 5.00 Supplier Invoice to Payment Process Summary This business flow covers invoice entry and management to payment processing. Su pplier Invoice to Payment demonstrates the business processes of receiving, reco rding and paying supplier invoices. Supplier invoices, credit notes, debit memos , RCTI's, recurring invoices and prepayments for PO matched and non-matched are en tered, approved and managed using the Invoice Workbench. Invoices are validated and invoice holds are managed. Non-matched invoices are routed to the Agency CFO for approval. Supplier payments and payment batches are processed using the Pay ments Workbench. Payments will be made based on the WoG Operating Unit structure . The Payables Transfer to General Ledger program will be run at regular interva ls to transfer invoice and payment accounting entries to the general ledger inte rface ready for posting. Standard Function Security will be employed to restrict access to certain functions and actions. This flow also enables the AP Supplier Maintenance Officer to manage Commercial and Non-Commercial Suppliers, Supplier Sites and Suppliers Bank details. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 94 of 117

Doc Ref: 5.00 Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 95 of 117

Doc Ref: 5.00 Supplier Return to Debit Process Summary Supplier Return to Debit demonstrates the business processes for returning items to a supplier for debit. This flow enables users to create an RMA for return of a damaged or defective product, send the product back to the supplier, and reco rd a debit memo for the return transaction. This business flow covers the return s process where a debit memo or Supplier Credit note is required to effect the r eturn of goods and services and where no replacement is required. This business flow covers the Core and Self Service functionality of the Oracle applications/modul es involved. Where a central delivery point for internal distribution to multipl e delivery points within that Agency, it is most likely that Core Applications, Returns function would be used. The returns Self-Service feature of Internet Procu rement will be used in most instances within the OSS System. The individual user and users attached to a Self-Service Group will use this function. The business r ule applied here is, only received credit notes to offset the return transaction will be applied. Debit memos will only be used where the Supplier is under an R CTI agreement. Prior to Returning Supplier Material, any of the following busine ss flows must be executed Requisition to Receipt Indirect, Requisition to Receip t Direct. Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 96 of 117

Doc Ref: 5.00 Supplier Return to Replacement Process Summary Supplier Return to Replacement demonstrates the business processes for returning items to a supplier for replacement. This flow enables users to create an RMA f or return of a damaged or defective product, send the product back to the suppli er, and process the receipt of a replacement product. No Credit or Debit Memos a re generated This business flow covers the Core and Self Service functionality of th e Oracle applications/modules involved. Where a central delivery point for inter nal distribution to multiple delivery points within that Agency, it is most like ly that Core Applications, Returns function would be used. The returns Self-Servic e feature of Internet Procurement will be used in most instances within the OSS System. The individual user and users attached to a Self-Service Group will use th is function. Prior to Returning Supplier Material, any of the following business flows must be executed Requisition to Receipt Indirect, Requisition to Receipt Direct Process Flow BP080 OSS Future Process Model v3.0.doc Company Confidential Page 97 of 117

Doc Ref: 5.00 Payroll Time Collection to Payroll Process Flow HR2103 Define and Maintain Schedules & Shifts OTL Administrator HR2104 Define and Maintain Holidays OTL Administrator HR2108 Enter Time Employee or Supervisor HR2109 Adjust Time Entered Employee or Supervisor HR2110 Review Time History Employee or Supervisor HR2114 Manage Time Reports Supervisor or Branch Manager HR2115 Approve Time Entered Supervisor and Branch Manager Out out Scope LMS001 External Rostering System External Rostering to Payroll Payroll Administrator HR1319 Perform Payroll Calculation. Payroll Administrator Payroll to Payment Legend: Event Temporal Event Process Step Manual Process Step Automated Process Step Rol es Copyright 1999 Oracle Corporation, All rights reserved Expandable Sub-process Decision Data Store External Rostering System Process Summary Refer to the BF140 Time Collection to Payroll v3 for further details of this bus iness process. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 98 of 117

Doc Ref: 5.00 Payroll to Payment Process Flow Compensate to Compete (continued) Payroll to Payment Business Flow Termination to Payroll Benefits to Payroll Employee Incident to Workers Compensatio n Personal Assessment to Promotion Time Collection to Payroll Processing Planning C ompensation to Commission HR1216 HR1216 Perform Perform On-Demand On-Demand Payment Process Payment Process HR1224 HR1224 HR1319 HR1319 HR1242 HR1242 Make Make Retroactive Retroactive Changes Changes Perform Perform Payroll Payroll Calculation Calculation Manage Manage Payment Payment Distribution Distribution HR1243 HR1243 HR3235 HR3235 HR1244 HR1244 Administer Administer 3rd Party 3rd Party Vendors Vendors Perform Perform Payroll Payroll Costing Costing Report and Report and Transfer Transfer Financial Data Financial Data HR3233 HR3233 Post to Post to Payroll Payroll Generate Payroll Reports Generate Payroll Reports HR3234 HR3234 Verify and Reconcile Payroll Verify and Reconcile Payroll Bank Statement to Cash Reconciliation Sub-ledger Journals to Post Payroll Team Roles (OSS) Quality Assurance Roles (OSS) Payroll Team Roles (Cluster-Specific) Senior Payroll Officer Personnel/Payroll Officer Support Officer Payroll Team Leader Senior Payrun Officer Pay Run Officer Assurance Team Leader Senior PPR Quality Assurance Officer PPR Quality Assurance Officer

Process Summary Refer to the BF140 Payroll to Payment Processing v1.4 for further details of thi s business process. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 99 of 117

Doc Ref: 5.00 Payroll Awards Structure Process Flow Process Summary A summary of each agreement is listed below. Collective Agreement - Award, Agreement & Agency Specific Agreements Under the governments employment agreements there are various agreements types t hat need to be considered when calculating Payroll payments and absence accruals . These employment agreement types are as follows; Awards, Agreements & Agency Specific Agreements Custom & Practice Conditions Workplace Agreements Minimum Conditions General Order The relationships between these agreement types can vary depending on the ruling of each condition within these types. Some examples of the relationships are as follows; BP080 OSS Future Process Model v3.0.doc Company Confidential Page 100 of 117

Doc Ref: 5.00 General Order conditions may override conditions in an employees Award or Agreem ent, Where a condition does not exist in any of the Awards, Agreements, General Orders, etc. then the condition values in the Minimum Conditions policy document are to be used, Custom & Practice Conditions may override conditions in an empl oyees Award or Agreement, Due to the many variations in the way these agreement types are dealt with a man ageable solution is required. This solution is a combination of Payroll configur ation with associated Fast Formula and manual intervention by Payroll staff to e nsure that the correct payment or absence calculation occurs. Award, Agreement & Agency Specific Agreements Award, Agreement & Agency Specific Agreements is a h ierarchical-based structure where the Agency Specific Agreements are subordinate to Agreements and Agreements are subordinate to Awards. This hierarchy is consi stent with the majority of the Awards & Agreements but there are a select few wh ere the hierarchy is different. For the select few that the hierarchy is differe nt (i.e.) CALM, Department of Fisheries and Zoo. Custom & Practice Conditions Cu stom & Practice Conditions is a statement that defines selective conditions that an employee or range of employees may be entitled to. This condition may be as a result of an employee receiving an entitlement condition for a period of time for example, but was not entitled to the condition based on the Award. The emplo yee/s negotiate an agreement to continue the condition or a modification of it. Workplace Agreements A Workplace Agreement is a specific agreement that relates to an employee. This agreement can contain various conditions based on the emplo yment contract agreed to by both the employee and government agency. Minimum Con ditions Minimum conditions are a policy document that defines the minimum workin g conditions that an employee in the government service is entitled to. Note, in most cases the Awards, Agreements, etc. will at least be equal to or better tha n the minimum conditions. General Order A General Order is a policy statement th at defines a condition or range of conditions that can affect any number of empl oyees based on rulings within the Order. The Order can either override condition s within Awards/Agreements, Minimum Conditions, etc. or substitute these conditi ons if the value is better than in the Awards/Agreements, etc. Other Considerati ons The Award Detail Reckoner spreadsheet that specifies the Award/Agreement con ditions will be used as the basis for determining the Award/Agreement configurat ion. There may be a requirement to store additional conditions based on the exis ting conditions; for example, a Condition of Standard Hours per Day may be used to store Standard Hours per Week. Award, Agreement & Agency Specific Agreements The following business flow defines the steps involved in the change of Award, A greement or Agency Specific Agreements. Award/Agreement Addition, Variation & Obsolesce Requirement Award/Agreement Hierarchy, Condition & Glossary Modification Award/Agreement Addition, Variation & Obsolesce Payroll Payment Validation The Federal & State Government based Award; Agreement or Agency Specific Agreeme nt particulars are required for payroll and absence payment. These particulars a re used to derive the following; Eligibility for payment Payment amounts Deducti on amounts Absence eligibility Page 101 of 117 Company Confidential BP080 OSS Future Process Model v3.0.doc

Doc Ref: 5.00 Absence amounts Within Oracle Payroll an Award, Agreement or Agency Specific Agreement will be r ecorded as a Collective Agreement. A Workplace agreement could be contained in t he Collective Agreement structure but would not be linked to a base award or agr eement. The Collective Agreement structure is made up of the following component s; Collective Agreements (Award/ Agreements) Collective Agreement Entitlements (Conditions) User Defined Table - Award, Agreement & Agency Specific Agreements The following business flow defines the steps involved in the change of Award, Agreement or A gency Specific Agreements. Award/Agreement Addition, Variation & Obsolesce Requirement Award/Agreement Hierarchy, Condition & Glossary Modification Award/Agreement Addition, Variation & Obsolesce Payroll Payment Validation The Federal & State Government based Award, Agreement or Agency Specific Agreeme nt particulars are required for payroll and absence payment. These particulars a re used to derive the following; Eligibility for payment Payment amounts Deducti on amounts Absence eligibility Absence amounts Within Oracle Payroll a configuration tool called a `User Defined Table' (UDT) will be used to store the configuration of an Award, Agreement or Agency Specific Agr eement. The UDT is `Date Tracked' to enable retrospective changes in Award or Agreem ent modifications. Therefore, when a Retro pay process is performed, retrospecti ve payments can occur. In addition, retrospective changes can dynamically change leave accruals when respective absence conditions change. The People Group flex field will contain an either the Award, Agreement or Agency Specific Agreement name in the 1st Segment. The users will enter short name Award or Agreement name s into the People Group flex fields. For example; 1. Segment1: Award, i.e. `PSA' BP080 OSS Future Process Model v3.0.doc Company Confidential Page 102 of 117

Doc Ref: 5.00 Grade Step Progression Process Flow Process Summary Refer to BF140 Payroll to Payment Administration Grade Progression v1.08 for det ails of this flow. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 103 of 117

Doc Ref: 5.00 Manage Employee Payroll Data Process Flow Process Summary Voluntary deductions will be managed from three perspectives. An employee thru E mployee Self Service will enter specific voluntary deductions. There are also vo luntary deductions that will be entered into the system by OSS staff. A list of these voluntary deductions will be provided in the BF162 Payroll Deduction Eleme nt Configuration document. Employees may also manage payment to other entities, which are not included in ESS Voluntary Deductions, and OSS requires manage the Voluntary Deductions within the core application. This Process Step will describ e all three ways of managing payments to the different deduction houses. With re gard to allowances, there are specific allowances that will be managed through E mployee Self Service. Manager Self Service will be used if the employee does not have access to the system and his supervisor has agreed to enter the allowance claim for his subordinate. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 104 of 117

Doc Ref: 5.00 Overpayments Process Flow Process Summary An overpayment is a monetary gain for which there is no entitlem ent, legislative or other, be it as direct cash or paid time. An overpaid salary is any payment paid to an employee through the payroll to which the employee is not entitled. Overpayments will in most cases be identified through the retro p ay process and other quality assurance processes identified for payroll reportin g. Other overpayments identified outside this process will require transactions to be entered. Some examples of overpaid salaries include: Leave without pay whe re there is no opportunity to make adjustments out of the following pay period. An employee may be placed on the incorrect salary step, which is adjusted to the correct salary step. An employee may be paid leave or allowances to which they are not entitled. An overpaid salary can only be recovered from an employee's salary once the employ ee acknowledges they have been overpaid and permits the OSS to recover the outst anding debt via their pay. Refer to BF140 Payroll to Payment Administration Overpayments v1.05 for further details of this process flow. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 105 of 117

Doc Ref: 5.00 Salary Packaging Process Flow Process Summary Salary packaging arrangements are entered into by the agreement between the empl oyee and employer. Once agreed, the employee arranges with the Salary Packaging provider to administer the package on the employee's behalf. The information updat ed for the employee's salary packaging element is updated by the appropriate salar y packaging providers either via an interface or report. It is envisaged that al l ongoing maintenance of salary packaging element is updated through the interfa ce between the provider and the Office of Shared Services (OSS). Salary Packagin g Elements Salary Packaging elements are to be created for both pre-tax and post -tax deductions for each of the salary packaging service providers. These elemen ts require a pay value within the input values as the dollar value is uploaded o r downloaded via the interface. The values are shown separately on the employees' payslip and reported as salary packaging. Employees can only employ the salary pac kaging provider appointed by the agency or employer agency to administer their p ackage. The eligibility criteria for the element are used to validate the provid er against the agency and allow the employees to be eligible to the element if t he criteria are met. The Salary packaging provider calculates and maintains the employees package. Therefore the Pre-tax and Post-tax element will be sent to OS S. An employee has the choice to salary package superannuation deductions direct ly to GESB/FESA super, rather than choosing the Salary Packaging Provider. If th is occurs the Pre tax superannuation element will be updated by GESB via the GES B interface into the superannuation elements. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 106 of 117

Doc Ref: 5.00 Employees must request salary packaging changes for superannuation funds such as Pension scheme and Gold state schemes via GESB only. These funds are not availa ble for employees to update and maintain information via ESS due to the fixed cr iteria for managing these funds. Pre-Tax Weststate contributions can be altered and maintained by the employee through ESS and the updated value is processed to GESB via the interface file. Eligible employees may salary package deductions f or GEHA housing. Agencies who allow employees to salary package these deductions will require specific details to be forwarded to OSS for updating into the syst em. GEHA elements will not be available for employees to update via ESS. Eligibl e employees may salary package deductions for rental arrangements for Main Road housing. Main Roads who allow employees to salary package these deductions will require to be forwarded to OSS for updating into the system. The MR elements wil l not be available for employees to update via ESS. The following elements have been identified and are reflected in the BF 162 Dedu ctions. Elements and Interface (Statement of Works) Element Name PTD McMillan Shakespeare pre tax PT McMillan Shakespeare post tax Superannuation Elements Interface McMillian and Shakespeare (MD 050 supplied) McMillian and Shakespeare (MD 050 su pplied) Superannuation is covered in the MD 050 Superannuation document Element Name GEHA pre-tax MR pre-tax Salary Packaging Refund FBT Shortfall Recovery Input Tax Credits Description Rental Rental Tax by marginal rate (PAYG) Pre-tax deduction Tax by PAYG Elements and Interfaces (Future roll ins) Element Name Paradigm pre tax Paradigm post tax PKF pre-tax PKF post-tax Salary Packaging Ser vices pre-tax Salary Packaging Services post-tax Salpac pre-tax Salpac post-tax SmartSalary pre-tax SmartSalary post-tax Refunds Reports Interface for Paradigm Interface for Paradigm Report Identified Report Identifie d Report Identified Report Identified Report Identified Report Identified Interf ace for SmartSalary Interface for SmartSalary Where a refund is sent through to OSS through the Salary Packaging Provider via the interface, this amount is paid by Salary Packaging Refund element to the emp loyee's regular salary and PAYG tax is charged according to marginal rate. Input T ax Credits (ITC) that are paid to employees will be sent back to the salary pack age provider by Finance. Finance is responsible for the calculation for terminat ed employees and a report will be provided to OSS every 3 months for entry. Emai l provided by M. Stagg23/8/05 Salary Packaging ITC Reporting Requirements The fo llowing reports have been identified for Salary Packaging: New Report Identified : Page 107 of 117 Company Confidential BP080 OSS Future Process Model v3.0.doc

Doc Ref: 5.00 Report to identify employee's salary packaging amounts that have exceeded 50% of t he employees base salary. This report is used for quality assurance purposes (Pa yroll Report). When an employee has been identified that their package has excee ded the OSS will contact the employee and the agency to advise. Salary Packaging Provider (HRPYPPRP19) Fringe Benefits Tax Recovery Finance advises the OSS when an employee needs to b e pursued for payment of Fringe Benefits Tax Liability. Payroll will receive the details of outstanding FBT shortfall from Finance via a report and this informa tion requires negotiation between OSS and the employee. Once the value is determ ined the element is updated by OSS via the FBT shortfall recovery element, to pr ocess the pursuing repayment back to the appropriate account. The report is prod uced by Finance in June of each year, once the FBT processing is completed for t he ATO. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 108 of 117

Doc Ref: 5.00 Multiple Assignments Process Flow 1 OSS checks current assignment details of employee who is going to be "Hired" i nto another position Manual Process 2 Is this going to be a concurrent assignment/ position for the employee 3 Yes 4 OSS updates the application with Accepted status Core HR HRR16 OSS hires the employee by creating a new secondary assignment record Customise Hire process No 45 OSS Updates employees primary assignment Core HR Maintain records through OSS 5 Employee record will have more than one assignment/ position Core HR Maintain records through ESS Post to Payroll Maintain records through MSS 7 Person-specific information OSS Enters and Maintains Personal Details Core HR 8 OSS Enters and Maintains Contact Details Core HR 9 OSS Enters and Maintains Competence Profile, Education and Qualifications, Awa rds Core HR 10 OSS Enters and Maintains Training Records Core HR Go to Process Step 45 Maintain records through OSS 6 OSS enters and maintains data under one employee record Core HR Assignment-specific information 11 OSS Enters and Maintains Absence Information Custom Form

12 OSS Enters and Maintains Assignment Time Information Core HR 13 OSS Enters and Maintains Disciplinary Records Custom Form 14 OSS Enters and Maintains Grievance Records Custom Form 15 OSS Enters and Maintains OSH Records Custom Form 16 OSS Enters and Maintains Deductions/ Allowances Core HR 20 18 Person-specific information 17 Employee updates Person and Assignment spec ific information through ESS Employee Self Service 19 Employee updates Contact Details Employee Self Service Employee updates Personal Details Employee Self Service Employee updates Competence Profile, Education and Qualifications, Awards Employee Self Service 21 Employee updates Training Records Employee Self Service Manager Approval 25 26 Employee Submits Deductions, Allowances and/ or Disbursem ents 22 Employee selects which assignment is to be updated Custom Form in ESS 23 Employee Submits Absence Details Custom Form in ESS 24 Employee Submits Timecard Custom Form in ESS Employee Submits Performance Appraisal Custom Form in ESS Assignment-specific information ID Custom Employee Self Service 27 Employee Applies for a Job within WoG Custom Employee Self Service 28 Employee Enrols in a Class Custom Employee Self Service 29 Employee submits Grievance online Custom Employee Self Service 30 Employee Submits Purchase Request

Custom iProc Self Service Employee Submits iExpense Self Service (To Be Proposed) Custom iExpense Self Service BP080 OSS Future Process Model v3.0.doc Company Confidential Page 109 of 117

Doc Ref: 5.00 33 Supervisor Reassigns Self Service Request Workflow Notification 34 Supervisor Delegates or Transfers ownership Workflow Notification Go to Process Step 31 35 Supervisor requests for more information Workflow Notification 36 Employee provides addl info and resubmits request to supervisor Workflow Notification 31 ManagerApproval Supervisor Approves request? 38 37 Supervisor returns request for correction Workflow Notification Employee corrects information and re-submits request to Supervisor Workflow Notification Post to Payroll Yes 32 Employee record is updated. Changes recorded in HRMS tables Core HR 39 Supervisor updates employees request Workflow Notification Go to Process Step 32 40 Supervisor rejects request Workflow Notification 41 Employee is notified that claim has been rejected Workflow Notification End of Process 44 42 Maintain records through MSS Supervisor selects em ployee record Custom Manager Self Service 43 Supervisor selects em ployee assignm ent Custom Manager Self Service Supervisor updates both Person and Assignm ent specific inform ation through MSS Custom Manager Self Service Go to Process Step 34 These will include the following : Competence Profiles Education and Qualificati ons Other Professional Qualifications (Awards) Resum e W ork Preferences Apprais als Em ployee Perm anent Transfer Em ployee Review Em ployee Secondm ent In/Out Em ployee Temporary Transfer Higher Duties Assignm ent Extending Higher Duties A ssignm ent Leave of Absence Release Inform ation

Process Summary In Oracle HRMS, a job or post held by an employee is referred to as an Assignment. It is the central concept that relates employees to the structu res in which they work and the compensation and benefits for which they are elig ible. It is made up of many attributes: organisation (e.g. department, division, region), GRE (government reporting entity) job title, position, location, grade, payroll frequency (i.e. weekly, fortnightly or monthly), salary basis (monthly or hourly), pay amount, and user-definable attributes to differentiate one assig nment from another. See Figure 1. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 110 of 117

Doc Ref: 5.00 Each assignment may have its own rate of pay and other unique compensation and b enefits eligibility requirements. Additionally, each assignment may report into a different part of an organisation, be funded differently, accrue different lea ve accruals and may require costing to be different. Each assignment may require using Employee Self Service (ESS) and having the appropriate manager approve th e transaction by Manager Self Service (MSS). Managers may also require having ac cess to view and updating their subordinate employee's personal and assignment rec ords Whenever an employee holds more than one assignment in Oracle HRMS at any g iven point in time, this is referred to as an employee holding multiple assignmen ts. An employee can have multiple assignments, but only one is the primary assign ment. All others are secondary assignments. Managers will be able to view the pe rsonal and assignment information of their subordinates. However, in Employee Se lf Service, some functions may not be available to secondary assignments For fur ther details of this process flow please refer to the BF140 Multiple Assignments BP080 OSS Future Process Model v3.0.doc Company Confidential Page 111 of 117

Doc Ref: 5.00 Year End Processing Process Flow Process Summary The end of year processing for Australia is focused on the reconciliation and pr oduction of the plain paper Payment Summaries and the electronic lodgement with the Australian Taxation Office (ATO). Employers have a legislative requirement t o report to the ATO, details of payment summaries issued to employees during the taxation financial year. Payment Summaries must be processed in compliance with the Australian Taxation Office Guidelines and legislation. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 112 of 117

Doc Ref: 5.00 Termination to Payroll Process Flow Process Summary Refer to BF140 Payroll to Payment Termination to Payroll v1.05.d oc for further details of this process. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 113 of 117

Doc Ref: 5.00 Absence to Payroll Leave Entry Process Diagram Manager / Delegate Leave Entry Bulk Entry (WebADI) No Valid Entry? No Yes Employee Leave Entry Valid Entry? Yes Manager / Delegate Approval Yes Approved Absence Leave Payment Yes Yes Valid Entry? Valid Entry? No OSS Leave Entry (On Behalf of Employee) No OSS Leave Entry (Adjustment) Employee Self-Service Entry Employees will enter applications for leave online via Oracle Employee Self Serv ice (ESS). This can be for a future period, in advance or in arrears. Employees can modify existing leave applications that are not pending for approval (i.e. b efore submitting the entry, or after the request has been approved or rejected), however employees will not be able to delete existing leave entries. The modifi cation or deletion of the existing absence entries can only be performed by the employee if the absence if for a future date. Once the start date and end date o f the absence booking has elapsed the employee will no longer be able to modify the leave booking. During the absence entry process via self service the employe e can nominate if the leave is to be paid in advance. This will be processed by the standard Advance Pay process within Oracle Payroll. All payment for leave an d associated allowances will be driven from the leave bookings entered within Or acle HRMS. Where the employee is required to enter timesheets (either electronic ally within Oracle, in an external system or manually) the hours entered on the timesheet should correlate to the absence bookings entered. If there is a discre pancy between the time entered on the timesheet and the absence entry the timesh eet should not be accepted until the absence booking or the timesheet entry has been amended so the two records are aligned. Self-Service Absence Type List of V alues (LOV) OSS require the list of absences available to the employee to select from when entering an absence to be restricted based on eligibility. This list of values will be restricted by modifying the standard LOV to only display absen ce types satisfy one of the following criteria: 1. The employee's current assignme nt is eligible to the element according to the element links defined for the abs

ence type element; The employee has an outstanding entitlement for the absence t ype. 2. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 114 of 117

Doc Ref: 5.00 In addition to this criteria an additional value will be defined against the abs ence type in Oracle to determine if the absence type should be visible in the se lf service applications. This is to allow leave types such as Workers Compensati on to be entered by OSS only via the professional user interface. Manager Self-Service Entry In the same manner as employee's entering absences via ESS, managers can enter abs ences on behalf of their subordinates within Manager Self-Service (MSS). The sam e functionality is available for the manager as was available for the employee, therefore Managers can submit applications for leave on behalf of subordinates o nline via Oracle Manager Self Service (MSS). This can be for a current period, i n advance or in arrears. In addition, managers can modify existing leave applica tions that are pending for approval. Managers can also delete existing leave ent ries. The modification or deletion of the existing absence entries can only be p erformed by the manager if the absence is for a future date. Once the start date and end date of the absence booking has elapsed the manager will no longer be a ble to modify the leave booking. The modification to elapsed entries will need t o be performed within the professional user interface by OSS. During the absence entry process via self service the manager can nominate if the leave is to be p aid in advance. This will be processed by the standard Advance Pay process withi n Oracle Payroll. Managers will also be able to approve or reject leave applicat ions that are entered directly by the employee or when entered on behalf of the employee via OSS. It is also a requirement that these functions can be delegated to another nominated employee to manage the leave applications for the manager's subordinates. Manual Leave Applications Where an employee does not have access to Employee Self Service and/or cannot en ter the leave applications electronically the request will be submitted by a pap er based application to the employee's manager or delegate to be entered into Orac le on their behalf. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 115 of 117

Doc Ref: 5.00 Leave Payment Diagram Absence Element Hours Taken Leave Payment Fast Formula Leave with Loading Leave without Loading Leave with Loading Payment Element Pay Value Hours Pay Value Leave without Loading Payment Element Hours Leave Loading Payment Formula Leave Loading Amount Shift Loading Amount Leave Loading Payment Element Pay Value Shift Leave Loading Payment Element Pay Value Standard Leave Payment Leave payments are driven from the leave bookings entered into Oracle Applicatio ns via Self-Service, WebADI, Professional User Interface or via an external appl ication. As an employee takes leave an element entry is created within Oracle Pa yroll that spans the pay periods affected. This element is processed during the payrun for the employee to generate payment. Details in relation to Leave loadin g, Staff Movements, Higher Duties, Retrospective Payments and Pay in Advance hav e been incorporated into the BF140 Absence to Payroll V1.04 document. Refer to the BF140 Absence to Payroll v1.7 for further details of the business p rocess flow for Leave. BP080 OSS Future Process Model v3.0.doc Company Confidential Page 116 of 117

Doc Ref: 5.00 Open and Closed Issues for this Deliverable Open Issues Details contained within the BF140 deliverables. ID Issue Resolution Responsibility Target Date Impact Date Closed Issues Details contained within the BF140 deliverables. ID Issue Resolution Responsibility Target Date Impact Date BP080 OSS Future Process Model v3.0.doc Company Confidential Page 117 of 117