Oracle Hyperion applications - Essbase, Planning and Financial Management (Consolidation) - are the most widely-used financial analytic applications in the world. They all experience extreme peaks in usage, primarily during period-end close. Few corporate IT operations provision enough server capacity to provide good response time to Finance Departments during these close periods, which tends to make a challenging time even more difficult. Because of these factors, Hyperion applications are ideally suited for cloud computing in an enterprise setting. Join Larry Hill from Full 360 to discuss his firm’s deep experience with the benefits and best practices related to this or key workload running in the Amazon cloud.

1. Oracle Hyperion in the Cloud

2. Agenda
• Background
• The State of Hyperion - 2012
• Why Run Hyperion in the Cloud?
• Hyperion in the Cloud Use Cases
• Full 360 Client Experiences
• Q&A

3. Full 360 Inc.
• Consultancy & Systems Integrator
﹣ 15 years – Hyperion applications
﹣ Analytic Data Warehousing and BI
﹣ Experts in Essbase, Planning and HFM
• Inaugural AWS Solution Provider
﹣ Working with AWS since 2007
﹣ First Hyperion EPM Images on AWS - 2009
﹣ Named 1 of 15 Premiere AWS Partners
• Clients
﹣ Past: Deutsche Bank, Citibank, JPM Chase, CIT Group…
﹣ Current: BofA/Merrill Lynch, HBO, Jefferies & Co., Guy
Carpenter/MMC, Chubb, Toyota
﹣ Cloud: American Airlines, MIMAARTS

4. The State of Hyperion - 2012
• Market Leader in EPM
﹣ Multi-dimensional Analysis (Essbase)
﹣ Budgeting/Planning/Forecasting (Planning)
﹣ Financial Consolidation (Financial Management)
﹣ Reporting/Analysis (Financial Reporting, OBIEE)
• Performance Concerns
﹣ Multi-dimensional “Cubes” require large servers
﹣ Oracle recommends against VMWare environment
﹣ Limited additional server power for period-ends
• Conflicting Finance – IT Priorities
﹣ Peak Performance vs. Cost Control
﹣ Critical-situation response vs. Systematic Support
﹣ Limited user visibility into system processes

5. State of Hyperion – 2012, Con’t
• Hyperion is “A Horse of A Different Color” to IT
﹣ Essbase is very different from Relational databases
﹣ Script-based process automation and ETL
﹣ No Version Control, Change Management
﹣ Admin skills not readily transferable from traditional IT
• Hyperion Cloud Adoption is Lagging
- IT is evaluating, testing, piloting other applications first
- Finance still has Security Concerns
- Hyperion application migration to the Cloud is behind the market

6. Why run Hyperion in the Cloud?
• Excellent Security
• Lower Cost
• Agility
﹣ The Ability to move faster and more effectively than traditional
methods
• Elasticity
﹣ Cloud-speak for Flexibility in all Dimensions
• World-wide Reach
• Shared Control between Finance and IT
6

7. Amazon Security Standards
Certifications Physical Security HW, SW, Network
SOC 1 Type 2 Datacenters in Systematic change
(formerly SAS-70) nondescript facilities management
ISO 27001 Physical access Phased updates
strictly controlled deployment
PCI DSS for EC2,
S3, EBS, VPC, RDS, Must pass two-factor Safe storage
ELB, IAM authentication at decommission
least twice for floor
FISMA Moderate Automated
access
Compliant Controls monitoring and self-
Physical access audit
HIPAA & ITAR
Compliant logged and audited Advanced network
Architecture protection

8. Networking & Security
AWS Direct Amazon Virtual Dedicated
Connect Private Cloud (VPC) Instances
Single Tenant
Compute Instance
Internet
Dedicated connection Private VPN Amazon EC2
between your connection to your resources running on
datacenter and AWS AWS resources private hardware

9. Full 360 Security/Backup Best Practices
• Virtual Private Cloud (VPC)
﹣ VPC = Cloud extension of Virtual Private Network (VPN)
﹣ Extends your Firewall out into the Amazon Cloud
• Backup/Disaster Recovery
﹣ AWS “Snapshot” of entire server: OS, Application, Disk
﹣ Saved to different Amazon Datacenter (Availability Zone)
﹣ Subsequent snapshots only of changed blocks
﹣ Can restore as a complete image as of a particular snapshot
﹣ Can also backup selectively to S3, file by file

10. Recent Amazon History
• “Everything Fails, All the Time”
﹣ So plan for Disaster in order to Avoid it
• 3 Outages in past two years in the U.S.
﹣ Single “Availability Zone” out of 13
• Full 360 Clients utilizing Backup/Recovery Best Practices
﹣ Re-started most recent Backup copy in different AZ
﹣ Some didn’t notice outage
﹣ Most down less than 1 hour
﹣ Longest outage 4 hours

11. Why run Hyperion in the Cloud?
• Excellent Security
• Lower Cost
• Elasticity
• Agility
• World-wide Reach
• Shared Control between Finance and IT
11

12. Total Cost of Ownership
• No/Low Capital Outlay
﹣ On-demand Hyperion-class servers start at $.26/hour ($188/month)
﹣ 1-, 3-year Reserve Instance is $276 up-front, $.16/hour
﹣ Disk is $100-125/month per Terabyte
• “Infrastructure for the same cost as Servers”
﹣ Server is only 30-50% of the fully-loaded cost
﹣ AWS Price is for ALL infrastructure – not just server
﹣ IDC Study – 70% Savings with AWS
﹣ FTSE 10 Bank Example – 89% lower cost for Essbase Servers
• Bring Your Own Hyperion License
﹣ Most Oracle licensing is user-based: don’t care where server is
﹣ Existing Hyperion license easily applied to Cloud
﹣ VERY favorable comparison to Oracle-on-Demand, Oracle Cloud
• Amazon Total Cost of Ownership Calculator
﹣ http://aws.amazon.com/tco-calculator

13. Cloud Pricing
Amazon Server Instances One-time Hourly Monthly Yearly
US (VA) (Each) (Each) (Each) (Total Qty)
On-Demand (Hourly) Windows (24x7)
Standard Large 2 cpu, 7.5 GB $0.46 $336
High-Memory Extra Large 2 cpu, 17 GB $0.57 $416
3 Standard Extra Large 4 cpu, 15 GB $0.92 $672 $24,178
High-Memory Dbl Extra Large 4 cpu, 34 GB $1.14 $832
High-Memory Quad Extra Large 8 cpu, 68 GB $2.28 $1,664
1-Year Commitment** Medium Utilization
Standard Large 2 cpu, 7.5 GB $640 $0.175 $128
High-Memory Extra Large 2 cpu, 17 GB $850 $0.203 $148
3 Standard Extra Large 4 cpu, 15 GB $1,280 $0.35 $256 $13,038
46%
High-Memory Dbl Extra Large 4 cpu, 34 GB $1,700 $0.405 $296 Off
High-Memory Quad Extra Large 8 cpu, 68 GB $3,400 $0.81 $591
3-Year Commitment** Medium Utilization
Standard Large 2 cpu, 7.5 GB $1,000 $0.156 $114
High-Memory Extra Large 2 cpu, 17 GB $1,283 $0.175 $128
3 Standard Extra Large 4 cpu, 15 GB $2,000 $0.312 $227.76 $10,199
58%
High-Memory Dbl Extra Large 4 cpu, 34 GB $2,566 $0.35 $256 Off
High-Memory Quad Extra Large 8 cpu, 68 GB $5,132 $0.70 $511
Elastic Block Storage 100 Gigabytes $0.10 $10 $120

14. Wall Street & Amazon
3000 CPUs for one
3000--
firm’s risk management
processes
Compute Capacity
300 CPUs on
300 -- weekends
Wednesday Thursday Friday Saturday Sunday Monday Tuesday

15. Why run Hyperion in the Cloud?
• Excellent Security
• Lower Cost
• Elasticity
• Agility
• World-wide Reach
• Shared Control between Finance and IT
15

16. “Classic” Infrastructure Growth
Infrastructure
Cost $
Large Customer
Capital Dissatisfaction
Expenditure
Predicted
Demand
Opportunity Traditional
Cost Hardware
Actual
Demand
Automated
Virtualization
time
16

17. Hyperion Infrastructure Growth
Infrastructure
Cost $
User
Dissatisfaction
Unused
Capacity
Actual
Demand
Capital
Investment
Q1 Q2 Q3 Year-End
17

18. Elasticity
Scalable compute power – On-demand
• Large increase in period-end processing power
– for low cost
• Example
﹣ Upgrade to 8-core, 68 GB instance for $1.93/hour
﹣ 10 hrs a day for 20 days of Close < $500
﹣ Make 50-100 personnel in Finance more productive
during The Close

19. Agility
• No Infrastructure Provisioning Delay
﹣ Just-in-time Infrastructure to reduce planning requirements
﹣ Simplified development; no Dev-Test-QA-Prod, just Dev-Test
and Go
• Examples
﹣ Sandboxes for “on-demand” development
﹣ New Essbase versions in an afternoon
﹣ Multiple concurrent versions (v11.1.13, v11.1.2.1, v11.1.2.2)
﹣ Archive old versions and re-start as needed
﹣ “Personal” Essbase Cubes

20. Why run Hyperion in the Cloud?
• Excellent Security
• Lower Cost
• Agility
• Elasticity
• World-wide Reach
• Shared Control between Finance and IT
20

21. AWS Global Reach
GovCloud US West US West US East South EU Asia Asia Australia
(US ITAR (Northern (Oregon) (Northern America (Ireland) Pacific Pacific /NZ
Region) California) Virginia) (Sao Paulo) (Singapore) (Tokyo) (Sydney)
Europe
Amsterdam (2)
Dublin
North America Frankfurt (2)
Ashburn, VA (2) London (2)
Asia
Dallas, TX (2) Hong Kong
Madrid
Jacksonville, FL Osaka
Milan
Los Angeles, CA (2) Singapore (2)
Paris (2)
Miami, FL Sydney
Stockholm
Newark, NJ Tokyo (2)
New York, NY (2) South America
Palo Alto, CA Sao Paulo
Seattle, WA
San Jose, CA
South Bend, IN
St. Louis, MO
AWS Regions Australia/New
AWS Edge Locations Zealand
Sydney

22. Global Reach for Hyperion Users
• Geographically Distributed Hyperion
﹣ Custom Planning in Asia, Europe, S. America, U.S
﹣ Essbase Cubes close to response-time sensitve users
﹣ Hyperion Financial Management applications by Region with
central consolidation
﹣ Local OBIEE Dashboards for good response time
• Result?
- Local Applications with Centralized Cost Savings and Control

23. Why run Hyperion in the Cloud?
• Excellent Security
• Lower Cost
• Agility
• Elasticity
• World-wide Reach
• Shared Control between Finance and IT
23

24. Shared Control between Finance & IT
• The Cloud reduces IT’s structural limitations
﹣ Purchase Decisions
﹣ Installation, Configuration, Management of Servers, Disk
﹣ Network Management
﹣ Forecasting for growth
﹣ i.e. “Heavy Lifting”
• Makes Hyperion Managed Services Viable
﹣ Shared Vendor-Client Control of Infrastructure
﹣ IT’s standards extend into the Cloud
﹣ Better visibility for Finance into Environment
﹣ Less IT responsibility for “Hyperion of a Different Color”
﹣ More responsive to Finance’s immediate needs
24

25. Cloud Hyperion Use Cases
• Sandboxes
﹣ Test out new versions (e.g. 11.1.2.2)
• “Instant” Development Capacity
﹣ Quick project start without waiting for infrastructure
• Production Applications
﹣ Lower-cost year-round Production
﹣ On-demand power for End of Period Peaks
﹣ Temporary Capacity Add for “Spikey” Applications
﹣ Calculate a cube on fast, temporary instance, run on lower-cost
• On-Demand Recovery, Automatic Snapshots for Backup
﹣ Mirror Hyperion applications in the Cloud
• Training
﹣ In-house or Cloud Vendor

26. Full 360 Client Experiences
• Major US Airline - Maintenance & Engineering
﹣ Essbase for Planning/Forecasting
﹣ “Closet to Cloud”
﹣ Stability and Security for low cost
• Hyperion Consulting Companies
﹣ Sandboxes for Version Upgrades
﹣ Quick implementations for client “saves”
• 123OLAP – Leading Hyperion Training Vendor
﹣ On-Demand Training – Essbase, Planning, HFM, Reporting
﹣ Quick instantiation from AMI template
﹣ Auto-refresh (new image)
﹣ Value-added service: transfer to client for extended training, use
• NYC-based Media Services Company
﹣ More responsive to client growth, peaks
﹣ Personal Essbase cube for heavy user

27. AWS Test Lab Program
• AWS Test Lab Program
﹣ Try out a Hyperion application and AWS at the same time
﹣ Ready-to-go Application instance, Lab script
﹣ 5 hours of AWS instance time
﹣ Support by AWS Partner
• Full 360 Hyperion Test Lab
﹣ Hyperion Planning instance on-demend
﹣ 1-hour lab script – typical Planning to Reporting scenario
﹣ Support by Full 360
﹣ More planned: Public Sector Planning/Budgeting,
Essbase/OBIEE, HFM

28. Summary
Why Move your Hyperion to the Cloud?
• It’s Safe
• It’s Flexible
• It’s Not Hard to Do
• It’s Cheaper
• It’s Faster
And in 5 years, everyone will be there…

29. Full 360 Contact Information
Larry Hill
﹣ Director of Business Development
﹣ 646.543.0062
﹣ Larry.Hill@Full360.com
NYC Area with World-wide reach

30. Q&A

31. We are sincerely eager
to hear your
FEEDBACK on this
presentation and on
re:Invent.
Please fill out an
evaluation form when
you have a chance.