Posts filed under ‘Uncategorized’
The scenario relates to routing the workflow to another task if it’s determined that the previous task was not performed correctly or the individual missed out on completing the task at 100%, Adeptia can route the workflow to a ‘correction’ flow based on any condition such as error threshold (in this case 30% or 40%).
We would need to design the models that would be invoked if the errors exceed 30% (or whatever thresholds) and what those pre-defined ‘correction’ flows would be.
So if the initial workflow task produces errors and if they exceed 30% then the application needs to identify that error condition and then route the workflow to another flow which would allow user to correct their mistakes.
Now as part of this workflow, a report detailing what those errors are can be generated for the manager so that they can analyze the trends along with the performance of that user working on their tasks.
Here’s an example:
Customer Care process that is started when a customer calls and a representative takes the call.
Step 1: Take Call
- This first task can have several data points that needs to be captured, and what if the call center rep fails to capture those data points (there could be other scenarios as well).
Step 2: Validation / Suggest Correction sub-workflow
- Here set of rules can be applied to determine whether the work completed in the previous step is 100%. If not then that task needs to be rerouted back to the call center rep and prompt for the data points that were not captured correctly. This would be a ‘correction’
workflow to help user correct their mistakes. This flow can also generate reports (and historical reports) to give Managers analysis of user performance and completion trends (similar to KPI dashboards).
Self correction to figure out “why” something was missed in Step 1 can be based on a Rules table that can be used to dynamically determine the right process to take. Adeptia architecture supports dynamic routing and process calls that can be based on what is done in the previous step of the workflow.
Step 3: Proceed to Technician onsite visit scheduling
- Now when the customer support case is routed to a next review step to ascertain if a technician is needed to resolve the customer support complaint all the information is available to complete this workflow.
In the below screenshots we have an example that checks for errors in the previous completed task and if errors are found, user would be assigned a new task which will have the original submitted content and instructions to correct those errors. Here the instructions can be a link to a video as shown below.
Adeptia announced the release of its EDI Integration Solution. This software solution helps companies automate date flows that generate Electronic Data Interchange (EDI) messages from internal data or process incoming EDI messages and integrate them with internal systems, databases and SaaS applications. Besides EDI-XML integration, Adeptia includes support for trading partner configuration and management. This solution includes support for ANSI X12 and UN/EDIFACT. All X12 standards and release versions are supported – from the popular 5010 and 4010 standards to others including the 4020, 4030 and the earlier 3010. All transaction sets are also supported including the transactions related to Health Insurance Portability and Accountability Act (HIPAA).
An example use of this EDI Integration Solution is for growing manufacturing and logistics companies to automatically handle increasing traffic of EDI messages. Usually the smaller organizations handle EDI in a manual way by using a business person to check manually for incoming EDI messages in the mailbox, download the message, open it in an EDI translator and then visually read the information and type it into their in-house order management, accounting and ERP systems. This approach does not scale when the organization grows and is interacting with many retailers and trading partners who not only want to exchange Purchase Orders and Invoices but also Advance Ship Notices and other transactions and so there are lot of incoming and outgoing EDI messages. This requires an end-to-end, fully integrated EDI solution for automatic processing and generation of EDI messages. The Adeptia EDI Integration solution easily and quickly meets this need.
“Despite advances in XML and Web Services, EDI still remains the dominant standard for data exchange between companies and organizations. Moreover, certain EDI standards such as ACORD AL3 in Insurance industry and HIPAA/HL7 in Healthcare have shown strong growth momentum in recent years. Adeptia has further strengthened the Business to Business Integration (B2Bi) capabilities of its product line with the availability of a powerful, yet easy-to-use EDI Integration Solution.”, said Lou Ennuso, CEO of Adeptia.
Document: Adeptia Unveils Next Generation SaaS Integration Solution . (1 page, 5 mins to review).
Traditional SaaS integration solutions have focused on just moving data in and out of SaaS applications. This approach may be fine for some scenarios such as data migration, reporting or synchronization. However, it is quite limiting because real world business problems require users to interact with data flows to review information, make decisions and route tasks. So, Adeptia has extended its existing SaaS Integration solution to allow SaaS applications to be integral part of customer’s business process flows.
For example, an order management process may require moving orders from Salesforce.com to an on-premise ERP system when a sale is completed and order won. However, this process would typically require workflow steps for business users to review and configure the order. A process flow such as this with multiple user workflow steps can be easily and rapidly configured in Adeptia. Adeptia offers an SOA-based, code-free approach with built-in connectivity to many SaaS applications such as Salesforce and NetSuite.
Data integration market has evolved over the last few years as more and more companies have realized that the business problems they were trying to solve by implementing data bridges did not really do the full job. Most problems require solutions that are more complex than just moving the bits and bytes. They require the data to be validated before it can be processed, errors need to be handled, notifications sent automatically on exceptions, information presented to business users to review and make decisions etc. etc. These solutions quickly grow beyond the capabilities of typical “integration products”.
Complete solutions require flexibility to handle various situations and scenarios and this typically requires a process-centric, services-based technology that includes human workflow capability. Integration-centric process management products, such as Adeptia, are best suited for these situations.
Document: SaaS Integration for Vendors. (11 slides, 5 mins to review).
As Software as a Service (SaaS) adoption has grown exponentially over the last few years, many customers using hosted applications have started asking the SaaS application vendors to provide data integration and connectivity capabilities. For various reasons, mainly driven by business needs, customers are looking to tightly integrate their data in the SaaS app with their on-premises back-end systems and databases.
There is an excellent article on this growing need in the Oct 20th, 2008 issue of InformationWeek by Mary Hayes Weier: SaaS Integration: Real-World Problems, And How CIOs Are Solving Them.
At Adeptia in recent months we have encountered an increasing demand from our customers for easy, fast and flexible SaaS integration solutions. Primarily these have centered around integration requirements from customers using Salesforce and NetSuite applications but now we see other SaaS apps as well as the whole market experiences growing adoption.
We have had numerous discussions with a number of SaaS vendors who are looking at how should they approach this whole issue of integration. It definitely seems to surprise the SaaS companies as they have mainly focused on creating the best, feature-rich application they could and have not given much thought to integrating the customer data with their internal systems.
Here are the key elements of advice we offer to these SaaS vendors:
- As with any other business issue, approach SaaS Integration as a STRATEGY and not a tactic.
- This means have an end goal in mind in terms of where you want to be with your integration capabilities and address the immediate customer need in a way (tactic) that puts you on path for that end goal.
- Address this need and grow your capabilities in an incremental but multi-phased approach.
- Bring in the experts since Integration is tough, difficult and complex.
In terms of options available to SaaS vendors, Adeptia offers the following framework:
- Option A: SaaS vendor provides integration services
- Option B: SaaS vendor publishes XML/Web Services interface
- Option C: SaaS vendor refers customers to Certified Partners
This framework is described in this document prepared by Adeptia (11 slides, 5 mins to review) and it covers the Pros and Cons of each option.
As SaaS and Cloud computing adoption grows over time, availability of viable integration options will be expected by customers of any SaaS provider. SaaS vendors who proactively take steps to implement a well-thought out integration strategy will be better positioned than those who treat it as an after-thought.
Document: Adeptia Enterprise Architecture Framework. (27 slides, 15 mins to review).
Over the years, as we sell and deploy our software for our customers, we are amazed to see how many companies do not have an Enterprise Architecture approach in place for their IT infrastructure. This is not just limited to smaller companies for whom an IT Enterprise Architecture (EA) may be an overkill but even many mid-sized to large businesses have not yet invested in putting an overarching enterprise architecture in place.
There are many reasons for not having this architecture in place but some of the main reasons we have observed are:
- Growth of business from when EA was not needed to now when it is
- Focus on day-to-day problem solving and short-term IT issues
- Focus on “must-have” needs rather than “nice-to-have” initiatives which is how EA is perceived
- Lack of skills in-house to drive, implement and manage EA
Although having an Enterprise Architecture in place is certainly not needed to successfully deploy Adeptia solutions, we recommend our customers to think about having fundamental practices of EA in place to get the maximum advantage from their investment in Adeptia. A well-executed Enterprise Architecture really gets the most value out of a process-centric and SOA-based software solution such as Adeptia.
Some of the benefits of Enterprise Architecture are:
- Aligns business strategy with technology investment
- Creates a vision and strategy for Information Technology
- “Blueprint” on how to view and approach IT projects
- Presents a Functional and a matching Technology view for every initiative
- Helps put a plan in place on how to get to the vision in an evolutionary, incremental way
- Provides a structure for consistent IT decision making
An Enterprise Architecture for each company would be unique as it will take into account its business model, strategic objectives, size of the business and IT applications and systems. Adeptia helps its customers by providing a “framework” to help them think about a model for how to design an EA that best meets their needs. Here is a document that describes the Adeptia Enterprise Architecture Framework. (27 slides, 15 mins to review). Please keep in mind this is only a “framework”, which is a roadmap or a starting point, and not a full-blown Enterprise Architecture.
This document recommends having two perspectives to an IT Enterprise Architecture: A Functional View and a Technology View. An EA would have the following four key elements:
Each of these elements have a number of other attributes as defined in the document.
We have found that this framework provides an excellent starting point to companies that have not thought about Enterprise Architecture or need a high-level introduction to taking a consistent approach towards all their IT projects and initiatives.