integrated business plan - hugmnhugmn.org/downloads/stj - hugmn pres… · ppt file · web...
TRANSCRIPT
1Confidential. For internal use only. Do not distribute.
HUGMN User Group MeetingSt. Jude Medical
The Road to Hyperion Bliss
Lisa Jones – Director, Financial Systems
2Confidential. For internal use only. Do not distribute.
Agenda Hyperion Road Map Hyperion Planning Implementation
Overview of Planning/Forecasting Process Redesign of Hyperion Planning Big Wins Lessons Learned
DRM Hyperion Planning Upgrade HFM Implementation FDM Batch Automation Application Support
3Confidential. For internal use only. Do not distribute.
Hyperion Road Map
4Confidential. For internal use only. Do not distribute.
STJ Forecast/Plan Cycles – No changes were made to our Planning process as a result of the Hyperion Planning Implementation
4
Cycle** February is the only month that does not have an active cycle**
Start End Cycle Length (system open to final
submission)
Forecast (4 Quarterly Forecasts)
Forecast1.1 12/19/13 01/12/14 24 days
Forecast2.1 03/01/14 04/11/14 41 days
Forecast3.1 05/31/14 07/11/14 41 days
Forecast4.1 07/27/14 10/10/14 75 days
Outlook (4 Quarterly Outlooks)
Outlook1.1 02/27/14 03/14/14 16 days
Outlook2.1 05/29/14 06/13/14 15 days
Outlook3.1 08/27/14 09/12/14 16 days
Outlook4.1 11/26/14 12/12/14 16 days
AOP (Annual Operating Plan) 07/27/14 11/14/14 110 days
STRAT (5 year Strategic Plan) 02/27/14 07/13/14 137 days
5Confidential. For internal use only. Do not distribute.
Hyperion Planning – Initial Design
REVSCOGS Input of Units, Revenue,
Scogs & Ocogs
OPEXPROJ Input of Operating expenses
by cost center, by project
WRKFORCE Detailed employee
information (US employees only, workforce planning has not been rolled out for OUS employees).
Hyperion Plan Types (CVPLAN)
Essbase Cubes (All BSO Cube)
FX2RVOP FX Engine used for loading
of actual data in transactional input and converting to USD. End users do not have access this cube.
CNFX3 Currency Neutralized data.
The majority of our management reporting is out of this Essbase cube
CMFX3• Currency Modeling. Used
only by Corporate FP&A to model planning data at various FX rate assumptions.
DRM EPMA Planning Essbase Cubes
6Confidential. For internal use only. Do not distribute.
Hyperion Planning – Initial Design
Reports
AcctPeriodGeoEntityYearScenarioVersion
AcctPeriodGeoEntityYearScenarioVersion
Project
ProjectEmployee
RevscogsInput/Calc/Agg
OpexprojInput/Calc/Agg
WrkforceInput/Calc/Agg
CNFX3Calc/Agg
AcctPeriodGeoEntityYearScenarioVersion
CMFX3Calc/Agg
7Confidential. For internal use only. Do not distribute.
Issues with original design
Biggest complaintfrom end users
8Confidential. For internal use only. Do not distribute. 88
BSOInput/Calc/Translate
Redesign - “Rocket the data”
ASOAggregate
1. Faster Aggregation2. Input/Calc and translate in BSO (CVPLN)3. Move zero level data to ASO4. Aggregate in ASO
Result: Moves the aggregation function to the ASO database
9Confidential. For internal use only. Do not distribute.
Hyperion Planning Re-design Highlights
10Confidential. For internal use only. Do not distribute.
Hyperion Planning – Big Wins
1. Currency Modeling – Previously we did not load plan/forecast data in local currency therefore it was very difficult to run accurate currency modeling. Now that all countries input in local dollars, we have a very accurate way to model planning data at different FX rate assumptions.
2. Currency Neutralization – All countries submit in local dollars, we are able to run currency neutral at all rates. This used to be maintained offline in Excel spreadsheets
3. One Global Planning System – We have one Planning system that is supported centrally by the EFS. This gives us transparency into the numbers since everyone is using the same system, provides more discipline in the planning process and serves as “one version of the truth”.
4. 15 Month AOP cycle – Beginning with FY12 Forecast4.1/FY13 AOP we implemented a 15 month rolling forecast. This allowed users ability to stay within one form instead of switching between cycles.
11Confidential. For internal use only. Do not distribute.
Hyperion Planning – Lessons LearnedLessons Learned
1. STJ Involvement – The majority of the project was designed and led by ExternalConsultants. The EFS team was not established until November 2010. We should have had full-time
dedicated STJ resources on the project from day 1.
2. Data Reconciliation - The effort of data reconciliation was significantly underestimated and we ultimately went live with no historical data.
3. Phased Implementation – We should have gone with a phased implementation (by division or by plan type) rather than implementing all divisions, all plan types at one time.
4. Delay Workforce – We should have looked at phasing in the workforce cube after all users were comfortable with the new Planning system. Workforce is definitely the most complicated cube type and initially EFS spent majority of production support on workforce related issues.
5. Financial Reports – too much time was spent on developing F/R reports that were never used. As time has gone by, we have started to create more reports, but in the beginning, 100% of the reporting was coming out of Spreadsheet Add-in or SmartView.
6. Consistency of Metadata – It is important to set standards and naming conventions at the start of the project so that your application is clean and consistent across all the dimensions.
7. Detailed Documentation within Calc Scripts– The best place to document what a Calc script is doing is within the calc script itself. If all of your Calc Scripts have good documentation it will allow for easier knowledge transfer between external consultants and internal resources.
8. Use of Global Forms – Important to get agreement with all divisions on web form design so you can use “global” forms that apply to all divisions rather than creating customized divisional web forms as it is more objects to maintain/update on a go-forward basis.
12Confidential. For internal use only. Do not distribute.
DRM – Data Relationship Manager
EFS TeamMaintains all metadata
Division FP&A users rely heavily on DRM to
view hierarchies
13Confidential. For internal use only. Do not distribute.
Why did we upgrade to 11.1.2.2
Version 11.1.2.2
We struggled with EPMA in the 11.1.1.3 versionGIT was heavily pushing physical to virtual serversErroneous Data Issue in 11.1.1.3 that was fixed in version 11.1.2.2SmartView enhancements with the new version of 11.1.2.2Organization Announcement drove many changes to web forms/metadata HFM and Planning need to be on the same version because they closely aligned and share workspace and/or metadata
14Confidential. For internal use only. Do not distribute.
What was included in the Upgrade
15Confidential. For internal use only. Do not distribute.
Lessons Learned of Upgrade
16Confidential. For internal use only. Do not distribute.
Hyperion Enterprise Overview
17Confidential. For internal use only. Do not distribute.
HFM Implementation
Goals/ObjectivesApply Lessons Learned from HP & Upgrade
Ensure that project was on time, on budget with no critical issues.
Avoid recreating Enterprise
Stepped back during requirements gathering to ensure we designed HFM to meet external reporting needs and not re-create Enterprise.
Centralize Mappings We wanted to implement more control to gain consistent and more accurate mapping of actuals
Project Team Smaller project team, longer burn rate. SME’s from STJ involved from day one of the project
HFM / HP Don’t duplicate data in multiple systems. Use HFM for what it was intended for.
18Confidential. For internal use only. Do not distribute.
Key Design Elements of HFM
19Confidential. For internal use only. Do not distribute.
Current Hyperion Environments
20Confidential. For internal use only. Do not distribute.
HFM Project Team
STJExternals
Magic of the Project Room•Project Team sat together from Day one. •Knowledge Transfer between externals & employees occurred on a daily basis•Impromptu Design / White board discussions early on and throughout project•No surprises•Team camaraderie
21Confidential. For internal use only. Do not distribute.
FDM Batch Automation
22Confidential. For internal use only. Do not distribute.
HFM Successes
Measure of Success
Project was on time, under budget with no defects heading into Go-live
We actually closed January quicker than we had in Enterprise for the first month under HFM
Data reconciliation was led by SME’s
We had 2 years of historical data in HFM within 2 months of having our dimensions built. By July of 2013 we were pretty much a week behind the official Hyperion Enterprise Close
Requirement Sign-off were held in person with all divisions meeting to walk through requirements
We had very little change requests or scope creep
Training was delivered by EFS TeamUser acceptance of HFM was very high and they picked up the new tool very quickly.
Unit Testing, UAT and Parallel Closes were very successfulWe completed 3 rounds of parallel testing and were able to close out all defects prior to Go-live
Knowledge Transfer occurred during project
We were able to roll off the external consultants within 1 week of closing the books for January. EFS team was ready to support the application
23Confidential. For internal use only. Do not distribute.
HFM Successes (cont’d)
Measure of Success
Out of box I/C Matching Reduced many manual hours spent on reconciling I/C matching reports
HFM Supplemental Web Forms
Huge gain in efficiencies by our SEC and Tax Department by leveraging HFM web forms. They now spend time analyzing the data instead of ticking & tying the data.
Duplicate Data No longer spend time reconciling detailed data between all the systems.
Accuracy of data mappingsThe reconciliation between source G/L (primary SAP) and HFM is almost automatic
Financial ReportingWe only created minimum amount of F/R reports in HFM. Users still tend to like Excel based reports.
Cash Flow by Legal EntityUtilize the HFM supplemental web forms to roll forward assets, Liab and equity and cash flow has been 85% automated
24Confidential. For internal use only. Do not distribute.
HFM – BIG WIN
25Confidential. For internal use only. Do not distribute.
EFS Support Model
26Confidential. For internal use only. Do not distribute.
Project ReOrg
Announced inJanuary 2014
In Production By July 2014
HFM was NOTImpacted!!!
Cutover wasSmooth &
System was stable
27Confidential. For internal use only. Do not distribute.
EnterpriseFinancialSystems
Team
User Counts
28Confidential. For internal use only. Do not distribute.
Our Journey over the past 4 years