Title: WholeofGovernment Finance and HR Business Solution Update
1Whole-of-Government Finance and HR Business
Solution Update
2Shared services
- Shared services implementation from 2003 to 2008
- Established shared service providers and
collocated staff - Rolled out whole-of-Government eRecruitment
solution, finance business solution into 11
agencies and piloted HR. Appointed Prime
Contractor (IBM) to complete rollout - More than 100 million to date in financial
returns to Government, savings in payroll
disbursement contracts, IT infrastructure and
procurement. - CorpTech has the dual role of implementing
whole-of-Government standard human resources (HR)
and finance business solutions, and providing
systems support for these solutions - including contract management of the Prime
Contractor (appointed in December 2007).
3Why appoint a Prime Contractor?
- A Prime Contractor model
- allows for fixed price contracts and reasonable
certainty on budgets - allows for definition of discrete work package
with fixed delivery schedules - allows competitive vendor pressure to be
maintained.
4Standard Offer to dateFinance process scope
Note This is the high-level scope there are
specific exclusions from some of the in-scope
processes
In Scope
Out Of Scope
5Standard Offer to dateHR process scope
Note This is the high-level scope there are
specific exclusions from some of the in-scope
processes
In Scope
Out Of Scope
6Line of Business (LOB)Background
- LOB scope includes
- Program Project Management (PPM)use of SAP
Project Systems and Investment Management
functionality - Asset Maintenance (AM)use of SAP Plant
Maintenance - Salesuse of SAP Sales Distribution.
7Current participating LOB agencies
8IBM recommended that a number of potential
requirements not be considered
- Scope items not recommended include
- duplicate requirements
- configuration requirements that are within the
scope of the overall solution - requirements met by existing functionality
- a large number of low priority requirements, i.e.
if the agency or SSP accepted that it was not a
legislative requirement and that not delivering
it would not risk service delivery, incur
additional cost or be a step back from current
methods - requirements which were not consistent with the
Standard Offer or which were not considered good
practice - requirements which would have a negative legal,
statutory, industrial relations, business
controls or policy impact - requirements which were not technically feasible.
9Forward Planning
- Provide surety of
- scope
- schedule
- funding
- Confirmation of core HR/Payroll and Finance
functions - Validate agency specific requirements
- Identification of key issues.
10IBMs Forward Planning stages
Review/validate standard offer baseline
Review and approval
Define scope
Refine standard offer baseline
11Finance
- Based on the feedback, IBM does not believe that
it is necessary to make major changes to the
current Standard Offer for finance. - Not surprising given the current finance solution
has been implemented successfully in a
significant number of agencies. - IBM identified potential refinements to the
solution - Addressing scope items which had previously been
deferred - Fine-tuning the current finance Standard Offer
through additional core or shared SAP
customisations - Meeting agency-specific requirements through
additional SAP customisations
12Human resources
- During the workshops 1,300 requirements were
identified. - Minimal shift at the requirements level in
comparison to current Standard Offer Baseline. - Moderate change at the application solution level.
13Deliverables
- IBM produced
- Requirements SpecificationThis document outlined
the additional functionality requested by SSPs or
agencies from the sector validation activity. - Scope DefinitionThis document defined the
Standard Offer recommendations for finance, HR
and LOB business solutions (core and shared) and
agency specific functionality (this is in
addition to the Standard Offer Baseline). - Release Plan and scheduleThis document detailed
the approach and timelines to design, develop and
implement the Standard Offer and agency specific
recommendations. It did not include costs.
14Agencies and shared service providers
- identified the business critical issues
- validated the assumptions CorpTech and IBM made
around agency complexity for the release schedule - validated the implementation activities for each
agency, shared service provider, CorpTech Service
Management and IBM - consolidated responses for finance, HR and the
release schedule.
15How agency feedback was addressed
- Categorisation of requirements
- Whole-of-Government
- Agency specific.
- Whole-of-Government
- Up-front detailed design
- Based upon best practice models
- Dedicated team led by IBM
- Leverage current knowledge
- Opportunity for participation.
- Agency specific
- Designed at time of agency implementation
- Based upon best practice models.
16Go-forward strategy
- Takes into account outcomes of Forward Planning
and other changes and is based on the following
principles - address the urgent needs of the original Phase
1 agencies - Queensland Health
- Department of Education, Training and the Arts
- Department of Emergency Services
- Department of Corrective Services.
- provide certainty for remaining agencies
- maximise the use of whole-of-Government processes
and core build - ensure cost effective and sustainable solution
and technology platforms - seek opportunities to accelerate some components
of the program - remain within existing budget allocation
- manage the program as an integrated program of
work.
17Go-forward strategyNext steps
- Finalise go-forward strategy
- Endorsement of go-forward strategy
- Communication to sector of detail
- IBM provides Phase 2 pricing.
18Summary
- IBM engaged to complete the design/build and
implementation. - Phase 1risk mitigation
- Phase 2remaining agencies.
19Questions?
- Steve Mitchell
- CorpTech
- 07 322 46251
- steve.mitchell_at_corptech.qld.gov.au
- www.corptech.qld.gov.au