Figure 2 illustrates the event-driven business process for the Property Appraisal process of figure 1, where requests are sent to multiple partner companies for retrieving specific portions of Property details. The responses are aggregated and updated to a back-end database. In the solution illustrated below, data is exchanged between the enterprise and partners via Https calls and WebService calls.

The nodes in figure 2 represent Fiorano business-components running as independent processes, while the lines between the nodes represent the directional flow of messages (events) when the business process executes.

1. Loan documents are received from the WebClient. The requests are typically sent in by loan consultants who underwrite loans. "Http Receive" Adapter service receives the loan request.
2. The backend DB is updated with the request, which typically creates a new record for the customer and the interested property. The received request is transformed to appropriate database format before it is sent to the DBAdapter.
3. Email is sent back to the client in case of failure in receipt of the request.
4. The document is securely posted via HTTP(S) to partner applications for doing property verification. The response contains appropriate information about the property.
5. Document information is posted via WebService calls to partner applications to retrieve appropriate information about the property.
6. The responses from the different partner applications are aggregated.
7. The backend DB is updated with the latest status of the loan using the DB Adapter.
8. Email is sent to the client on the status of the order.

• Business data can be sent and received in different protocols like FTP, HTTP(S), SMTP, TCP, etc. In addition, inbuilt support for data transfer in secure mode is available.
• The need for installation of additional software on partner locations is eliminated. Fiorano ESB™ Peer Server provides for fine grained deployment and monitoring control of services.
• Addition and removal of business partners can be done rapidly enabling real-time modifications to business processes.
• Fiorano ESB™ supports services written in different programming languages (C, C#, C++, VB and Java) and s them communicate with each other across the enterprise framework.
• Business Analysts get the "complete picture" of the business data flow. In addition, they can define business process with sub-flows to handle individual error/exception conditions processes spanning multiple partners and enterprise.

Time taken to "SOA Enable" the Business processes

Fiorano ESB™ solutions are quicker to implement. This is simply because the solutions have in-built capabilities to accommodate complex business scenarios with minimal programming efforts.

In the "loan processing" scenario discussed above, the time schedule for the different implementation activities is listed below.

Fiorano's business solutions are developed by live mapping of real-time components onto the business process flow. These real-time components represent the actual systems and applications across the enterprise. As a result, Fiorano's SOA solutions closely resemble the actual business process flow diagram. Business analysts can easily get the "bigger picture" with Fiorano's solutions and can rapidly modify business flows based on changing business requirements.

ROI on Fiorano ESB™ SOA Solution

As illustrated in the calculations below, the ROI percentage in the first year is 340%, rising to 988% in three years. The calculations are for a 1 Billion Revenue Business; with $500 Million/year in expenses and $100 Million/year in profit. The resource costs have been taken as $150,000/person/year (base salary, benefits, overhead)

In such B2B scenarios, integration projects are traditionally developed as point-to-point applications using different technologies resulting in a tightly coupled integration environment that are:

• Expensive to manage/maintain and change. Heavily dependent on database systems that required significant amount of coding and manual interventions to complete business processes
• Inflexible to addition/removal of partner companies. Any change in business process requires code changes
• Not scalable and low on performance
• Unable to provide for a business analyst view of the business process