Intentsys.net Value Proposition

Confidential & ProprietaryCopyright © 2014 Intentsys.net

Int|Ent|Sys in a Nutshell

Your Organization needs… To integrate multiple discrete IT systems or

just simply that one business-critical system To reach out to Customer- and Vendor

Systems To integrate to a Cloud (SaaS) system Integration for a new Business- or IT

Initiative like ERP implementation, Shared Service Center, Customer Service Excellence…..

Top System Integration Challenges across Industries and company size…. The Total Cost of Ownership How an array of discrete systems handle

exceptional, sudden, unplanned business situations

Technical criticalities Real-Time, Performance etc Integrity issue of Data not being in synch Security- and Reliability aspects Alignment of Business and IT teams

Solution and BenefitsImplemented Cross System Processes running on a dedicated Integration Platform Lowers Cost to own your integration space Faster Time-to-Market and Time-to-Value Increased Business User Efficacy Collaboration between Business and IT Cross-System Processes are reliable and available

Intentsys.net Value Proposition

Domain Expertise in Cross-System Process Technology & Cloud Integration

Partner Network

L0

http://www.intentsys.net/



Sales Order Cycle is slow

System doesn’t indicate when a delivery hasn’t arrived in time

Are your organizational heads facing any of these issues?

We work with multiple systems. We have to enter the same data twice, trice. There are typos and errors.

IT is unable to quickly adapt the systems to our market needs

Too costly system interfaces Too costly legacy systems

<Business> / <IT> (make your pick) does not understand my needs……

For our vendors, we extract data to a spreadsheet and expect them to revert via email. Isn’t that too slow?....

Business Head IT Head

Uncertain, whether my IT developers and admin are productive with managing system interfaces

Where do I find the specialists to manage the many disparate interface technologies?

Are the business transactions secure?

Are we using the appropriate interface technology standards?

Which transaction ran into error? What is the cause?

L1



Which of the following statements is true for your Organization?

“We need to integrate ONE mission-critical IT-System”

“We need to integrate multiple discrete IT systems and also lacking a Interface Lifecycle management and an Integration Strategy”

“We want to reach out to Customer and Vendor Systems”

“We need to integrate our on-premise system with a Cloud solution”

“We will be starting a new Business Initiative e.g. Shared Service Center, Customer Service Excellence or ERP implementation”

L1



Why Integration is Mission Critical or Why ERP has been such an incredible Success Story?

Foundation

WarehousingInventoryProcurement

AccountingReporting

Manufacturing SalesFoundation

Supply Chain Mgmt

Interfaces

Interfaces Interfaces

Interfaces

Being a Business Software, ERP - Enterprise Resource Planning is a suite of integrated applications/modules to transact business activities

One characteristic is, ERP is an integrated system that operates in (or near) real time without relying on periodic updates. It has got a common database that supports all applications.

Now built-in Integration between the modules is a major contributor to the success.

L2

In other words, the packaged Business Processes are on best practice standards and complete , the data is in integrity.



Stages of Enterprise Integration vs Competitive Advantage

Competitive Advantage

Integrated & Extended Enterprise

Business Suite (ERP & other Biz

Apps)

Cloud Applications

Middleware

Disparate Applications

Email

Departmental Analytics

Siloed Enterprise

Enterprise Resource Planning (ERP)

Corporate Portal

Business Warehouse

Integrated Enterprise Islands

Level ofIntegration

L2



Top Challenges across Industries and Company Size

Total Cost of Ownership of Integration Scenarios

Dealing with exceptional/sudden/unplanned business situations

Real-time requirements and other Time criticalities

Data(bases) not synchronized / out of integrity

Reliability and Availability issues

Impact of Business and IT are not aligned i.e. speaking a different language

L1



Total Cost of Ownership (1/2)

• Mounting technical debt– Exponential growth of integration needs with each additional Biz

system– IT time to maintain Legacy systems– number of resources and special skills– annual maintenance/support fees

• Low Developer- and Admin productivity– Multiple different platforms and tools. different capabilities, look&feel– overwhelming number of APIs– no re-use of Software artifacts. Each project starts from square 1– Technical incompatibilities at every level– Re-work due to lack of alignment with Biz

L2

CIO



Concern: “Each line (interface) costs $50,000 [USD] to $100,000 over 5 to 10 years” Valero Energy (largest oil refining company in North America)

Total Cost of Ownership (2/2)

• Lax IT governance– Technical standards (e.g.protocols, security) not leveraged– No re-use of artifacts and pattern

• Poor return on assets– expensive to run inhouse IT– Outsourcing of Systems and Services?– Systems Consolidation?

L2

CIO



Dealing with exceptional/sudden/unplanned business situations• Critical events such as unavailability/shortage of human

resources, inventory, machines, IT systems• Orchestration and Rule-based exceptions of “what-if”

scenarios

L2

COO

LoB Head



Technical Criticalities (1/2)

• Timing– Real Time Requirements– Batch Management– Slow Performance and Response time– Slow Process Cycles

• Integrity - Data(bases) out of synch (out of Integrity)– Human errors in case of frequent double data entry– Multiple Single points of failure (SPoF)– Lack of Trust in transactional- and decision making situations

L2

CIO

LoB Head

IT Ops Head



Technical Criticalities (2/2)

• Reliability aspects– Availability for planned and unplanned downtime– Disaster recovery– Scalable by increasing data throughput in asynchronous scenarios or

faster response time in synchronous scenarios.

• Security aspects– vulnerability to attacks for less secured integration scenarios e.g. man-

in-the-middle– reading and manipulating sensitive information– non-repudiation for B2B transactions

L2

CIO

LoB Head

IT Ops Head



Biz & IT alignment (speak different languages)

• Alignment of Business- and IT Strategy• Speed of business change determines speed of IT

projects• Failure potential due to miscommunication• Project pressure eventuates in lack of Design Thinking

and Simplification efforts

L2

CIO

LoB Head

IT Dev Head

COO

Biz Strategist

IT Strategist



Solution & Benefits – Cross System Process Technology

Use an Integration Platform or leverage installed product

Implement Cross System Process on top of Integration Platform

Life-Cycle - Operate, Monitor, Maintain, Add, Improve, Retire

Benefits

Cost advantages and Investment Justification

Faster Time-to-Market to meet the pace of the competition

Automation opportunity

Increasing Business User Efficacy

Improves Collaboration between Business an IT teams

Systems & Processes reliable, Data Integrity and System Availability

L1



Integration Platform Concept (1/3) L2

Conventional System Integration(point to point)

Dedicated Integration Platform




System Integration is actually an Integration of 2 process steps

Integration Platform worksteps

1. Define the interface with the underlying message structure

2. Or alternative accept the exposed interface by the System

3. Create the mapping between the message structures

4. Create any Integration Logic if required




Configure the routing to the Target System(s)

Choose the technology to connect the systems



SAP Offering - NetWeaver Process Integration

Business Extensibility

Foundation

Infrastructure Services

Lifecycle Management

Eclipse 3JEE5

Service Bus

Connectivity & Integration

SOA Governance

Mapping & Transformations

SAP NetWeaverProcess Integration

Process Integration Server

Service Repository & Registry

GovernanceWorkflows

L2

Software Capabilities Design-/Development- and Runtime

Preference for SAP customers since PI is built on the same Foundation (NetWeaver)



Mulesoft Offering – Anypoint Platform L2



Product Comparison by Analyst Gartner L2

For Cloud-Level Integration scenariosFor conventional A2A scenarios



Example: Enterprise Islands

Lets say…..

I am the CIO of a medium size (1000 employees) Office Furniture company.

5 years back, we have invested into a SAP A1 ERP.

Also run a simple HR system for 7 years. We are out of maintenance but system serves the purpose so far.

We recently went live with a standalone enterprise-level Data warehouse.

Now Business has decided to grow revenue through higher cadence with the sales force and better insight in the pipeline activities. They realized the sales module features won’t support sales pipeline activities.

We subscribed to a CRM Cloud solution by Salesforce.com to have a shortened implementation timeline and minimal disruption of our operational ERP

Even though CRM has got a reporting system it was decided to consolidate reports into the data warehouse.

CRM requires customer- and product master data from ERP and sales team details from HR. The forecast feeds back into the data warehouse.

My team has to build the interfaces to make it work……But Interfaces come in various colors and flavors

L2



Foundation


AccountingReporting


Supply Chain Mgmt

Interfaces


Interfaces

Example: Enterprise Islands

CRMApplication

(as a Service)

Data Warehouse

HumanResources

(legacy)

Interfaces

Interfaces

2

Customer master

Interfaces

Interfaces 1Product master

Interfaces

Interfaces

4Employee

master

Interfaces

Interfaces

3Forecast

L2



Build the Point-to-Point integration

1. Define message structures (and underlying data types) and define the interfaces in all systems involved

2. Alternatively explore the library for exposed interfaces per system

3. Connect the systems using the lowest common denominator e.g. if one system can only files then file communication is required

4. In either the source or the target system write a program to map the source to the target structure and build any program logic to manipulate the data

5. In case no interface is exposed, write a program to extract and post data

6. Do this exercise for each and every integration flow

L2



Conclusion - Benefits and Remaining ChallengesThe Integration Exercise is beneficial– The new CRM accesses up-to-date data anytime– The Master data stay centralized and are maintained as always (no change

management required)– Data sharing among all IT systems in an automated fashion eventuates in

quality data– User can trust data and focus on Business. No double entries required.– Supports faster cycle times in customer engagement– The Legacy HR is still useful for CRM activities– Quality cadence meetings with intelligence reports (BI is updated in due

time and with quality data)

Remaining Challenges– Still considerable manual programming involved

• To Integrate different technologies on different systems• High effort to integrate with multiple target systems

– To adhere to common technology standards– To monitor operations and maintain interfaces over their lifecycle– (Strategic Concern) Exponential increase in scope and cost of integration. – (Strategic Concern) “Time to Market” – To align requirements of Line-of-Business and IT teams

L2



IntegrationPlatform

Foundation


AccountingReporting


Supply Chain Mgmt

Interfaces


Interfaces

Solution - The Integrated Enterprise

CRMApplication

(as a Service)

Business Intelligence

HumanResources

Interfaces

InterfacesCustomer

master

Interfaces

InterfacesProduct master

Interfaces

Interfaces Employeemaster

Interfaces

Interfaces

Forecast

L2



Build the integration on the Integration Platform

(as shared in Integration Platform Concept slide)

1. Define the interface with the underlying message structure or re-use from repository

2. Or alternative accept the exposed interface per System3. Create the mapping between the message structures

or re-use from repository4. Add any integration logic if required (workflow)5. Configure the routing to the required number of

Target System(s) (one to one, one to many, many to many)

6. Choose the best suited adapters out of the box to connect the systems

7. Add the level of security needed

L2



Benefits (1/2)L2

• It delivers the Business benefits that we discussed earlier & addresses the remaining challenges effectively

• Increased Time-to-Value, since integrated process fulfill business requirements

• Total cost of ownership is reduced dramatically– Higher developer productivity– Helps to manage Scenario Lifecycle enforcing the use of standards and

re-use of existing software assets– Helps to manage legacy systems– Give deployment options of On-premise, Cloud and Hybrid



Benefits (2/2)L2

• Business Agility– Speedy Time to market providing expected competitive pace – Unlock processes for automation to increase cycle times and typical

delays through batch processing

• Business User efficacy– Data availability and Quality caused by real-time update options and

the avoidance of double data entry by users– Visibility and Alerts when business got issues. Quick and intelligent

system responses

• Collaboration between Business and IT team– Better transparency and priority setting in IT projects– IT projects create higher business value

• System reliability– Robust systems due to use of standards– Databases of discrete systems in synch– Reduced impact during maintenance activities



How are you impacted?L1



Other organizational Key Initiatives include

Key Business initiatives ERP Implementation or -Upgrade Mergers and Reorganizations Shared service centre Customer service excellence

Key IT initiatives A2A of ERP and other Business Systems B2B and EDI – Extending Processes to Business Partners SOA Governance Landscape optimization Legacy migration UI Modernization Cloud Initiatives

L2



Services Portfolio

Product Sales Education

Product features – Beginner to Advanced Best Practices for Cross-System Process Integration

Value Engineering As-Is Analysis and To-Be Design of Cross-System Integration

Scenarios Implementation

Scenario Development until Go-Live

L1



Why Intentsys.net

Domain expertise in cross system process technology & Cloud Integration

Partner Network Partnerships with best-in-class product vendor and specialized

development organization One-Stop Shop

Education, Value Engineering, Project Implementation

L1



Q&AL1



Thank you!

Ralf WildenPrincipal Consultant+65 [email protected]://www.intentsys.net

L1


mailto:[email protected]



Intentsys.net Value Proposition

Business

Transcript of Intentsys.net Value Proposition