Time to Value: Successful Cloud Software Implementation

Transcription

1 Time to Value: Successful Cloud Software Implementation Cloud & Data Security 2015 Client Conference

2 About the Presenter Scott Schimberg, CPA, CMA Partner, Consulting, Armanino Scott became a Certified Management Accountant in 1995 and obtained his CPA certificate in He has a mixture of industry experience and has held positions as Assistant Controller, Controller and VP of Finance. He also has more than 13 years of consulting experience, where he has focused on implementing ERP systems.

3 Agenda Learning Objectives On Premise vs Cloud Implementations Cloud Based Software Solution What s Included Cloud Implementation Tools and Trends Cloud Specific Implementation Cloud Security Considerations

4 Learning Objectives Examine the similarities and differences of on-premise vs. cloud implementations Learn how an implementation can be done 100% remotely Identify essential Cloud software solution components

5 On Premise vs. Cloud Implementations 2015 Client Conference

6 Similarities Project Management is required Need an Implementation Methodology and Plan Typical high level steps o Requirements gathering o Design and configure o Testing o Training o Deploy or go live o Support

7 Major Differences Cloud deployments are typically done remote Nothing installed at client s office or systems. Most frequent on site requests o Kickoff meeting o Complex requirements gathering o Training Flexibility with database o Onsite has access, cloud ask to do

8 Major Differences Quick implementations o No setup and configuration of servers and workstations.

9 Cloud Based Software Solution What s Included 2015 Client Conference

10 Cloud Computing Stack - Types SaaS - Applications for end-users delivered over the cloud PaaS Tools used to deliver Applications for end-users (hosted environments) IaaS underlying infrastructure that runs the SaaS and PaaS solutions, servers, storage, networks and operating systems

11 Types of Deployment and What s Included SaaS Hosted (PaaS) On Premise or PaaS Software Multi-tenant Managed servers And software installation Customer managed Disaster recover Included Usually included Customer deploys Support Included Portions included Typically extra cost Sandbox Usually extra Usually extra Customer deploys Integration API API/direct to database Guaranteed Up Time API/direct to database Included with SLA Included with SLA Customer manages Security Included Managed service Customer manages Upgrades Included Depends on provider Customer Manages

12 Cloud Implementation Tools and Trends 2015 Client Conference

13 Meetings and Trainings Video conferencing Screen sharing tools Recording meetings Survey of meetings and trainings Shared Drives work papers and documents Online project management tool

14 Cloud Specific Implementation 2015 Client Conference

15 System Activation Software provider sends introduction communication Customer completes initial setup information o Company ID o Initial user o Other basic information Software provider activates software SOC 16 Report Initial user add

16 Browser Access Access is typically through a supported browser Make sure supported browser is used by all members Non-supported browsers may: o Work for a significant portion of the functionality o Have issues with only certain forms, buttons, etc. o Create error messages and stop or slow work o Cause data corruption

17 Sandbox Sandbox is highly recommended o Better for training new employees o Integration support Common Sandboxes offered o Copy of live system that can be refreshed o An extra environment (needs to be configured and populated with data) Password security is important o Copy of your data

18 Integration and Customization Sandbox is highly recommended Hosting of development code and solutions Upgrade considerations Connectivity requirements

19 Implementation Time Implementation Timeline o Generally 60 to 90 days for most SMB clients (non-distribution and manufacturing) o Integrations could take more time Meetings o Short and focused o Meetings a couple times per week for 1 to 2 hours End users typically have implementation work after meetings o Gathering requirements information o Compiling data

20 Implementation Steps Requirements gathering Configuration Testing Training Data migration Deployment Transition to support

21 Cloud Security Considerations 2015 Client Conference

22 System Security SSAE 16 SOC1 Type II audited and PCI DSS certified Tightly restricted access to production data including biometric access controls Hardened networks and firewalls Real-time activity log tracking Automated security scanning and third party white hat penetration testing Virus resistance reinforced through software architecture Encryption for all data transmission Multiple fiber trunks and mirrored RAID storage Standby servers and redundant network components Redundant uninterruptable power supplies and parallel redundant generators

23 Data-Level Security Full daily backups to multiple locations Continuous backups of transaction data Secure streaming of transaction data to remote disaster recovery center

24 Application Security Highly granular level of control over user access o Permissions, role-based access Option of requiring 2-step user verification every time a user signs on through an unrecognized device Enforced password changes and automatic session timeouts Option to set acceptable IP ranges from which users may log in

25 Conclusion Examine the similarities and differences of on-premise vs. cloud implementations Learn how an implementation can be done 100% remotely Identify essential Cloud software solution components

26 What Questions Do You Have?

27 Scott Schimberg, CPA phone: Client Conference

28 COMING UP NEXT: Building an Enterprise Application Strategy Around Cloud Technologies 2015 Client Conference