1. Integrating Your Critical Business Systems in the Cloud Era
The Importance of Integration Lifecycle Management
Hello, I’m ____________________ and here with me from Scribe are _______________________ and ______________________________.
I’d like to spend the next minutes in a conversation about the challenges we all face with the proliferation of the cloud. Specifically around the challenges of integrating all of the cloud based business applications that are available to provide your organization with ability to grow and adapt to meet the needs of your customers.
We will also talk about the concept of the integration lifecycle management and the importance of solutions to help you manage your integration environment.

2. Today’s “Digital” Businesses Use More Applications
Specialty Applications and Analytics Require Better Integrated Systems
Yesterday
Disconnected, Monolithic Apps
CRM
ERP
Legacy
Connected, Specialty Cloud Apps that Help Agility/Analytics
Today and Future
ERP
CRM
Legacy
Your Enterprise
Mkt. Auto.
Field Service
Power BI
Dyn 365
Sales
Marketing
Field Service
Customer Service
Project Services
Financials
Operations
CPQ
Data Services
Cust. Service
Analytics
Traditionally data integration for organizations meant connecting front office and back office applications and also integrating legacy data sources.
But as our companies embrace the cloud, it has opened up an ecosystem of new SaaS based applications and API-centric solutions
Such as Cloud based Marketing Automation tools like Hubspot, Marketo and Eloqua,
Or CPQ or Configure Price Quote applications like Experlogix
And now with Dynamics 365 we have even more options to choose the cloud based applications that provide competitive advantages for our business.
So Integration across your enterprise and to the cloud is .

3. Even Dynamics 365 Users Need Integration
Migrate to Dynamics 365
Complex Integration within Dynamics 365
Integration to other ERP and CRM Systems
Integrations to Cloud Apps
Data integration is still a key requirement for Dynamics 365 Users
Migration to Dynamics 365 from legacy systems, or on premise Dynamics applications. CRM to AX2012
You may have deployed some highly customized, complex solutions built on top of Dynamics CRM such as Healthcare, Public Safety, CPQ/Configurator.
Our you may have other solutions in place or in other divisions of your company such as SFDC, etc
And Integrations to other specialized or best of breed Cloud Apps

4. Challenges
“We want basic integration, but it must account for our custom fields and objects”
“We thought once we moved to the cloud this would be out of the box.”
“We don’t have the tools to troubleshoot and support.”
“Working on someone else’s custom integration is really challenging .”
But integration has its challenges- and being in the integration business here are some of the issues we hear at Scribe:
We just need a basic integration – “ but please - don’t forget my custom fields and objects”.
Internal survey at Scribe found 90% of our cloud customers are mapping custom fields or objects.
The cloud makes everything easier – shouldn’t this just work ‘out of the box’? (talk about “native” integrations offered CRM to Marketing applications that are “generic”)
Who will troubleshoot and support this integration deployment over time?
And integrations that are custom-coded – what happens if your IT team needs to try to fix an integration that was coded by someone else?
Which leads us to the Buy vs Build Integration discussion

5. As Cloud Integration Complexity Grows
1 CONNECTION
Manageable but inefficient
+10 CONNECTIONS
Time and resource consuming, costly, varied quality, not core to our business
+ SUPPORT & MAINTENANCE
Modern systems are not static. Requirement evolution and platform evolution require new approaches
As I mentioned earlier, most end user customers today begin their foray into the world of integration by having a simple requirement for a single point to point integration – maybe accounts and contacts in your ERP of Marketing Automation system to accounts and contacts in your CRM system. Quickly custom coding this effort, while not the most efficient, is not too painful.
<click>
But what happens once you realize the value of integrating a few applications – you can begin to recognize the need to create and the value of creating, integrations across a number of other application sets.
Your IT department or your partner now needs to educate themselves on potentially a new set of APIs and application nuances and would find that there is little that can be re-used from project to project. Custom integration work can quickly consume a large slice of your application and development resources. IT or partner response times and project quality can be impacted.
But the challenge doesn’t stop there. The next challenge comes in managing all of the inherent maintenance, support, and upgrade costs over time across these multiple integrations.

6. MAJOR DRAWBACKS TO CUSTOM DATA INTEGRATION
TOTAL COST OF CUSTOM INTEGRATIONS
MAINTENANCE & OPERATIONAL COSTS
90%
Of the TCO for custom-coded integration comes from maintenance costs
INITIAL INFRASTRUCTURE
ONGOING PERSONNEL
Initial Development Costs
DEPLOYMENT PERSONNEL
ONGOING INFRASTRUCTURE
CUSTOM-CODED INTEGRATIONS REQUIRE COST & TIME THAT ARE UNDERESTIMATED BY MOST
Let’s dig into those maintenance costs further.
According to Gartner up to 90% of the total cost of ownership of custom code comes after deployment.
It comes in the form of maintenance and operational costs such as infrastructure costs, and personnel costs ongoing to update the software, keep it running, make changes to address new changes in the business, etc. Source: Gartner (Gartner “Decision Point for the Build vs. Buy Software Sourcing Decision”, Published: 3 July 2012)
So who pays for these costs? Do you want to be in the business of maintaining custom integrations?
These are estimated ongoing costs from the Gartner Study:
Initial infrastructure can be 5-20% of ongoing costs
Deployment personnel can be 5-15% of ongoing costs
Ongoing personnel can be 50-85% of ongoing costs
Ongoing infrastructure can be 5-15% of ongoing costs.

7. Scribe’s iPaaS Platform
Allows application consultants and business analysts to build solutions in a fast and agile environment
VISUAL DESIGN ENVIRONMENT
Complete control of your integration deployments via a single interface
CUSTOMER CONSOLE
A tailored, collaborative customer/partner experience that runs anywhere.
FLEXIBLE DEPLOYMENT
VALUE-BASED PRICING
Transparent & simple pricing options,
Lets take a look at the integration platform itself.
<click>
The first major capability of the platform is the visual design environment that empowers non-programmers to solve for complex integration needs. Your IT consultants or business analysts (or those of your partner) can quickly create re-usable integration templates to common use cases that can be deployed across multiple application environments. Anything that is built is completely self-documenting so that any user of Scribe’s iPaaS platform can quickly understand the approach and design. The environment is powerful, fast, and agile.
You may also find that you or your partner will need the ability to create, deploy, and manage multiple integrations across multiple departments or divisions over time to be successful. Scribe understands this and can provide customers with a master tenant where they can provision, configure, and manage their various integration scenarios from a single pane of glass. Ease of manageability.
With Scribe online, you or your partner have the ability to acces the platform via a single web portal – through your iphone, iPad, laptop, etc…
Finally, we have priced our platform using a simple connections and features based model, which can scale from the simplest point to point integration scenarios to the most complex, enterprise wide deployments

8. An Integration Platform Built for Success
An Integration Platform Built for Success
To learn more or to begin a free trial
Visit
Contact
Your Enterprise
I hope that you found this talk interesting – if you have integration needs, Hitachi, in conjunction with Scribe can certainly help – please stop by our table to learn more or check out our website.
Thank you.

9. 20 YEARS EXPERIENCE
14,000 CUSTOMERS AND PARTNERS

10. Design Approach for Successful ILCM Outcomes
Connect key systems and touch points and provide for configurable integration outcomes.
Design for adaptation. Cloud systems rapidly evolve and your integration approach must be adaptive.
Strive for long term project success and profitability.
There are 3 simple keys to managing this integration lifecycle. As a baseline, you and your partner of course, need to focus on deploying a configurable integration solution that can be easily deployed and managed over time. <click> and designing integrations for agility and adaptability is a must in the cloud era - with the multitude of cloud apps now available <click> It’s also very clear that long term success of your project needs to be your ultimate goal. This is where Scribe’s iPaaS platform can help.