What makes enterprise unified communications work
A comprehensive collection of articles, videos and more, hand-picked by our editors
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
The following is an excerpt from Enterprise Integration: The Essential Guide to Integration Solutions, by Beth Gold-Bernstein. It is reprinted here with permission from Addison-Wesley Professional; Copyright 2004.
9.1 Executive Overview
The purpose of integration is almost always to support improving a business process to increase business efficiency. Process-level integration defines the interactions among systems through business workflow definitions. The instructions for the integration are defined at the business process level rather than the technical-interface level. Although a technical integration infrastructure is still a necessity to implement process integration, the processes themselves are technology independent. This enables change to be made quickly and easily, increasing business agility.
The role of the Process Integration Architecture is to create process models and definitions as managed entities that can be easily viewed and changed in response to changes in a business. The Process Integration Architecture defines end-to-end business processes, which are then automated across existing systems on disparate platforms.
The key benefit of the Business Integration Architecture is the business level view it provides of the endto- end process. Process integration technology includes dashboards that enable business managers to track key performance indicators in near real time. Process simulation and analytics provide feedback to help companies optimize business processes, reduce cost, and achieve competitive advantage through better processes. Case Study 9.1 describes how General Electric has achieved significant business process improvement with amazing operational results (Lindorff 2002).
Case Study 9.1
Real Time Process Improvement at General Electric
General Electric is well known as an organization that has a maniacal focus on process improvement. This focus has moved beyond just management practices to the digitization of their business described by their CIO, Gary Reiner, as an "e-buy, e-make, and e-sell" strategy. GE, like other leading companies, is realizing that the future of process improvement is closely associated with the ability to harness their information and automate their processes.
An example of how GE has implemented process improvement is the use of digital dashboards that allow mission-critical operations such as sales, daily order rates, and inventory levels to be monitored in near real time. With this data in hand, automated notifications and status changes can be noted, allowing management and staff to react quicker to changes in their environment. A digital dashboard is critical to any process-improvement activity, because you cannot manage what you do not measure. Without measuring in real time you cannot react in real time. Every process-improvement program should include the use of digital dashboards as a best practice.
General Electric has always been a pioneer in the area of process improvement. By adopting the real-time enterprise philosophy coined by the Gartner Group, they have seen impacts both enterprise wide and at the business unit level. Some examples are:
• 5% improvement in Power Systems' inventory turns
• 10% improvement in Power Systems' receivable turnover
• $680 million cut from purchasing costs through online auctions
• $3 million saved in Plastics Division on payroll
• Twice as many customers handled per sales person
Process automation is one of the key business functions that organizations must master as a core competency to be able to effectively compete. As in the past, GE will be a leader blazing a trail that others must follow.
The Process Integration Architecture also improves alignment between IT and business. It starts with business process models that business people can understand and review. These models depict the shared understanding between the business and IT staff of the end-to-end business process. The process can then be automated directly from the model. This significantly reduces the chance of misinterpreting the business requirement or getting the process wrong. As the process can span multiple business units and managers, there may not be one manager who owns or even understands the complete end-to-end process. The process models represent a shared understanding of how business is conducted across the enterprise, and should be managed as valuable assets.
This chapter appears last in the Enterprise Integration Architecture section because most companies implement it last (if at all). Companies have not been historically strong on process management and improvement—although those that focus on process tend to be the market leaders in their industry. The next section defines why it is so important for companies to pay attention to process.
Companies that do implement a process integration architecture and infrastructure will start their integration projects by modeling the business process and drill down from there, defining which applications, services, and information is required to complete the process. This tends to be a faster and more efficient approach than a bottom-up integration connectivity approach, and is far more responsive to change.
9.2 Why Process Is Important to Business
The benefits of business process management are not a new revelation. It has been known for over half of this century that optimizing business processes yields measurable results. In the 1950s Dr.W. Edward Deming, a mathematician and statistician, proved that improvements in managing business processes lead to improvements in overall business and significant competitive advantage. As a result of Dr. Deming's work, Japanese manufacturing companies were able to produce higher quality products at a lower cost and gain competitive advantage. For his efforts, in May 1960, the Emperor of Japan decorated him with the Second Order Medal of the Sacred Treasure and Japanese manufacturers created the annual Deming Prize in his honor.
Deming taught that variation is created at every step in a production process, and variations have the potential to cause defects. Therefore, the causes of variation need to be identified and reduced and companies need to practice continuous product and process improvement to improve quality and productivity, and decrease costs. Deming proposed a continuous feedback and measurement cycle to reduce defects and improve product quality, usually referred to as the Plan-Do-Check-Act cycle.
• PLAN. Design or revise business process components to improve results
• DO. Implement the plan and measure its performance
• CHECK. Assess the measurements and report the results to decision makers
• ACT. Decide on changes needed to improve the process
The Plan-Do-Check-Act cycle is a continuous cycle. To achieve measurable results and business benefit, companies must practice continuous process improvement. Wal-Mart, the world's largest company, is able to require its suppliers to support its process improvement in a manner remarkably similar to the Deming cycle. Case Study 9.2 details the Levi Strauss & Co. experience (Girard 2003).
Dr. Deming's work gave rise to a number of initiatives to manage and measure the efficiency and effectiveness of business, including Total Quality Management (TQM), balanced scorecard, Six Sigma, and ISO 9001. These initiatives can help companies understand how to define key performance indicators to measure their business (see sidebar—How to Measure Success, page 164). These metrics can then be used on a management dashboard.
Despite half a century of research and proven success, few companies have optimized their business processes. In the early 1990s, based on Dr. Michael Hammer's best-selling book Reengineering the Corporation, corporations began systematic efforts to improve their business processes. Unfortunately, those initiatives were often less than successful. A key inhibitor to the success of business process reengineering (BPR) was a lack of technology to support the focus on radical reengineering of business processes. The logic for business processes was either buried in the code for each application or was manually performed, requiring significant custom coding and integration efforts to achieve results. This led to great organizational upheaval. In contrast, emerging process integration technology enables companies to leverage existing IT investments and automate new processes that use them.
Process integration supports the Plan-Do-Check-Act cycle to enable process optimization. The business process integration tools provide process modeling, to "Plan" the process, automation and integration to implement or "Do" the process, monitoring tools and dashboards to "Check" processes, and simulation and analytical tools to help companies "Act" to improve processes.
Case Study 9.2
Improving the Supply Chain at Levi Strauss & Co.
Levi Strauss & Co. is one of the most recognizable brand names and popular products in the world. However, like all companies, they must be constantly changing with the needs of market. An important part of their strategy going forward was to distribute their products through Wal-Mart. The implications of this decision were profound to the IT organization. According to Bain Consulting, a key attribute to successfully doing business with Wal-Mart is "the ability to use technology and better business practices to control costs and reduce prices." Furthermore, Wal-Mart sets the bar very high in terms of their requirements for the supply-chain support necessary from their vendors. These facts required a transformation of the supply-chains process and supporting technology in order to execute Levi Strauss & Co.'s strategy to do business with Wal-Mart.
Levi Strauss & Co. embarked on an initiative to improve its supply chain, including efforts aimed at tracking product as it moved through the supply chain. This allowed greater ability to forecast and improved the ability to replenish as well as manage inventory. Before the changes, product was delivered at a low mark of 65%; after the changes, this improved to 95%. One key aspect of the system improvements was the addition of dashboards as the mechanism to monitor and react to the improvements in the supply chain.
Dashboards are a view into a diversity of information that represents the state of a set of processes that must be integrated together. Good process integration incorporates the concept of dashboards into the design to allow the process to be monitored and acted upon by the appropriate personnel.
The supply chain at Levi Strauss & Co. is one area of focus for process improvement that every manufacturing company will need to address. Central to these initiatives is the ability to unlock the information across the system, synthesize and communicate it, and allow actions to be taken either by people or by systems.
How to Measure Success
Each of the process management and measurement initiatives below defines metrics for measuring the efficiency, effectiveness, and quality of business processes. There are no clear guidelines for choosing a particular method. It is more a matter of whether the origins and goals of the method resonate with the organization, or what others in your industry are using, or even what your BPM tool supports.
Total Quality Management (TQM). Directly inspired by Dr. Deming's ideas, TQM was initiated by the US Department of Defense in 1987, and provided a new focus on total ownership cost in acquisitions. TQM includes eight key elements: ethics, integrity, trust, training, teamwork, leadership, recognition, and communication.
Baldrige Award. The civilian equivalent of TQM, this award is a measurement of excellence and is highly prestigious for a company to win, requiring significant investment in time, money, and commitment. Seven categories are evaluated: leadership; strategic planning; customer and market focus; measurement, analysis, and knowledge management; human resource focus; process management; and business results.
Balanced Scorecard. Balanced scorecard defines what to measure beyond traditional financial numbers. It is an approach to aligning strategy with action, and measures the effectiveness of strategies. Categories of measurement include: process redesign and improvement, work group productivity, management support, and competitive advantage. Some business process management (BPM) tools provide balanced scorecard dashboards.
Six Sigma. The objective of this methodology rooted in mathematics and statistics is to reduce process output variation to allow no more than 3.4 defects per million. The method includes sub-methodologies for improving existing processes and creating new processes. Six Sigma can be and is often used in combination with balanced scorecard.
ISO 9001. ISO is a worldwide federation of national standards bodies from more than 140 countries. ISO 9001 is a certification process to measure excellence; it includes a process model based on the Plan-Do- Check-Act cycle. ISO 9001 criteria includes the following:
• Management responsibility
• Quality system
• Design control
• Contract review
• Document and data control
• Control of customer supplied product
• Control of test equipment
• Process control
• Handling, storage, delivery, etc.
• Internal quality audits
• Inspection and test status
• Control of quality records
• Product identification and traceability
• Control of nonconforming product
• Inspection and testing
• Corrective and preventative action
• Statistical techniques
9.3 Understanding Process Integration Technology
Just as there are many Eskimo words for snow, there are multiple terms that describe different types of process-based tools. Each of these is best suited to a particular type of process solution. This section discusses the different types of process-integration technologies, including Business Process Management (BPM), Business Process Integration (BPI), Business Process Automation (BPA),Workflow Automation (WA), Business Activity Monitoring (BAM), and Web Service Orchestration (WSO).
9.3.1 Business Process Management (BPM)
We view BPM as the broadest implementation of process management functionality. It includes support for all aspects of designing, implementing, monitoring, and managing both automated and manual business processes. This includes process modeling, process automation and integration, workflow integration (for manual processes), real-time monitoring and alerts, operational and business dashboards, analytics including key performance indicators, and process simulation for enabling process optimization. BPM solutions are recommended for companies looking to implement business dashboards, practice proactive process management, and work towards process optimization. Alternatively, companies looking for compliance or industry solutions may find the solutions are implemented in (and come with) BPM technology. The company then has the infrastructure necessary for continuous process improvement. General Motors Corporation has mastered the art of BPM with results that are nothing less than incredible (Bacheldor 2003). Case Study 9.3 describes its results.
Case Study 9.3
Improving Margins Through Process Improvement at General Motors Corporation
General Motors Corporation's IT department has demonstrated that process integration can bring substantial business value to an organization. The CIO, Ralph Szygenda, enhanced a variety of core processes in the past few years with significant results in several areas.
Supply chain and logistics processes are core to many enterprises and are a good place to look for opportunities in process integration. At GM they are trying to create a virtual factory by tying together engineering, procurement, and manufacturing processes to cut the time it takes to assemble an automobile. By focusing on this at GM, the results have been staggering; the average time to assemble a car was cut down from 32 hours in 1998 to 26 hours today. In an operation the size of GM, this converts to a savings of $1 billion.
However, at any large organization the opportunities for process improvement are abundant. GM has added online capabilities for dealers that allow them to submit customer-financing applications. These applications are forwarded to the General Motors Acceptance Corp, or GMAC, for processing. A small process improvement like this was able to save $500,000 for GMAC.
Process improvements are core to the CIO's strategy at GM, with a focus on making rapid, incremental improvements that are delivered in short time frames. This best practice can be applied to any size organization.
9.3.2 Business Process Integration (BPI)
BPI refers to process-level integration, as opposed to message-level or pointto- point integration. BPI includes the ability to design and model the process, integrate it with the underlying applications, and monitor the process on an endto- end basis. The monitoring and management capabilities, however, tend to be on the operational level, not the business management level. BPI does not provide analytics and simulation. In other words, it provides process integration without process management.
BPI is appropriate when your management has little interest in process management and improvement and just wants to get the job done as quickly as possible, but the process is changeable, differs by location or business unit, or the underlying applications are changing. The major benefit of a process abstraction layer provided by BPI is that it adds agility for change.
9.3.3 Business Process Automation (BPA)
BPA refers to automating business processes. These tools tend to be transaction oriented and do not necessarily support long-lived transactions or manual processes. BPA tools generally include process modeling, application integration, and processing rules, and may include a development tool for new development, process monitoring, and operational-level management. Companies looking to automate transaction-based processes that do not involve humans and complete in seconds or nano-seconds rather than hours, days or weeks, should consider a BPA tool.
9.3.4 Workflow Automation
Workflow automation focuses on reducing the lag time in manual business processes. It includes a workflow engine that controls the flow of work across workers and departments according to a set of business rules. Managers can assign work to different types of workers. The workflow engine provides load balancing across all workers, accounting for backlogs, vacations, etc. Therefore, work can be automatically and efficiently assigned.Workflow tools provide work portals where employees can see all assignments and report when they're done, to trigger the next part of the processes.
Most business processes include some manual steps. Therefore, most BPM vendors include some support for workflow, but the extent of workflow features differs widely. If your processes have just a few manual steps, such as exceptions and approvals, then minimal workflow features will be sufficient. However if your processes have a significant manual component, then fully investigate the workflow capabilities of any tool you choose, including robust work management features.
9.3.5 Business Activity Monitoring (BAM)
BAM is a term coined by Gartner Group and currently in the cycle Gartner refers to as market push or the start of media infatuation. However, it is more accurately at the stage of vendor infatuation, with each vendor rushing to promote its BAM capability, because Gartner asserted that by 2004 BAM would be one of the four top initiatives driving IT investment, affecting every industry. Although monitoring and analytics are an essential part of BPM, Gartner defined additional BAM capabilities for combining real-time alerts with business intelligence, trend analysis, and data mining. This is the marriage between business integration and business intelligence.
The widespread industry acceptance of BAM is due in part to vendors eagerly looking to define themselves with the next big thing. However, although they all declare they have BAM capabilities, they're at different levels of BAM. Some provide monitoring dashboards that provide notifications, then a person needs to go and do something to react to the alert. The system does not guide the reaction—it only provides the alert. The next stage of BAM integrates business intelligence with near real-time analytics, so when the manager is alerted, he or she also has the information to make a better decision about what to do next to respond to the alert. The next stage of BAM uses business rules based on analytical results and automatically takes action instead of just alerting a person to take action.
This wide variance of capability means there are many types of BAM vendors. The BPM vendors all offer BAM solutions, the EAI vendors have added BAM capabilities or just relabeled what they already had as BAM. There are business intelligence vendors, system management vendors, and pure-play BAM vendors. The BAM market is still in the very early stages.
9.3.6 Web Service Orchestration (WSO)
WSO provides process-level development and coordination among Web services. WSO is used to define and implement the flow of control between the service components of a composite application. Web services can reside on multiple platforms and technologies. They can be components in an application server or legacy applications on a mainframe, and both can participate in a single composite application. The WSO tool includes process modeling, a process engine, and operational-level monitoring and management.Many application server vendors are providing basic WSO tools to enable composite application assembly of application server applications.
WSO is a good fit for composite applications consisting of all Web services. However, if the composite application requires complex integration with multiple platforms and technologies and end-to-end real time process monitoring and management, a BPM solution might be a better fit.
The process integration market is expanding, and buyers will find solutions being offered from a variety of different vendors, including the integration vendors, application-server vendors, and pure-play BPM vendors, as well as workflow and document management vendors, rules engine vendors, and soon, business intelligence vendors. Moreover, companies looking for compliance and industry solutions will find that BPM vendors are offering them, and the technology may come into the enterprise through a packaged solution.
By providing end-to-end, real-time visibility into business processes these tools help companies increase operational efficiency and decrease costs. Because process integration provides a layer of business process abstraction that is physically separated from the applications and implementation technology, it enables rapid business change.
9.4 Process Standards
Although every process tool on the market offers some kind of modeling capability, most are proprietary tools. They may do a fine job modeling your process, but offer no portability or long-term protection of the models. A process model represents valuable corporate knowledge and a significant corporate investment. Portions of the end-to-end process may be known and managed by different people in different parts of the organization. The process model captures the knowledge from across the organization and enables the company to optimize at an enterprise level to maximize ROI. For this reason, process models should be managed over time as valuable corporate assets.
Process modeling standards help companies protect their process investment by enabling portability across tools. This prevents technology lock-in. A standard process execution notation that can be exported and imported by all tools effectively solves the most important problem of technology lock-in. The process modeling standards companies will want to consider include BPEL, UML, and IDEF.
9.4.1 Business Process Execution Language for Web Services (BPEL4WS)
Often known as BPEL, Business Process Execution Language for Web Services is the emerging leader for standard process representation. BPEL is an amalgamation of XLANG from Microsoft and WSFL from IBM, and supersedes both approaches. Microsoft, IBM, and BEA, along with others, joined together to submit the BPEL specification to the international standards body OASIS.
BPEL is a standard execution language, not a standard notation. This means that tools will implement their own styles of models and produce BPEL code from the models. A number of vendors of existing modeling tools have announced support for BPEL. The BPEL standard enables portability of models among tools. Although BPEL is becoming an important process-modeling standard to pay attention to, there are also some others companies may want to consider.
9.4.2 Unified Modeling Language (UML)
The Object Management Group's (OMG) UML is also a relevant process modeling standard, especially for companies focused on new development, and who already use UML. Furthermore, the OMG's Model Driven Architecture (MDA) is a generic approach that can be applied to a wide variety of business problems, including process management.MDA creates a metamodel in UML that abstracts the definition from the implementation.Using this approach, the same model can be used to generate code for multiple platforms. MDA provides the framework to integrate different standards, languages, technologies, and platforms.
Companies implementing composite applications that include new development will be interested in a UML-based approach to process modeling. Developers are usually the ones to define the flow of control in the composite application, and UML has wide acceptance for systems development and among system developers.
9.4.3 Business Process Management Initiative (BPMI) and the Workflow Management Coalition (WfMC)
BPMI and WfMC are two other noteworthy process organizations. BPMI (http:// www.bpmi.org/index.esp) was established to create specifications to "standardize the management of business processes that span multiple applications, corporate departments, and business partners, behind the firewall and over the Internet." BPMI is working on notation standards as well as process query language.WfMC is an organization focusing on the human component of business processes, including processes for assigning work, sharing documents, and managing task lists. Both BPMI and WfMC support and are contributing to the BPEL standard.
9.4.4 Integration Definition for Function Modeling (IDEF0)
IDEF is based on the Structured Analysis and Design Technique (SADT) introduced by Douglas T. Ross in the early 1970s. In 1981, the US Air Force Program for Integrated Computer-Aided Manufacturing (ICAM) standardized and adopted it as a Federal Information Processing Standard (FIPS), and made public a subset of SADT, called IDEF0. This standard is still in widespread use today, and is an extremely important modeling standard for organizations doing business with the federal government.
Companies should pay attention to the evolution of process standards to ensure the portability of their business models and maximize their process investment over time.
9.5 Process Integration Architecture Specification
See Appendix G for the complete Process Integration Architecture Specification.
The Process Specification provides guidance for applying a process-driven approach to integration. This document is a guide to creating the process specification for the composite applications or process-driven business solutions.
The scope of a Process Specification is usually limited to a set of business processes associated with an integration project. The document should define the business processes and underlying applications to be integrated.We recommend not boiling the ocean. Start with a few business processes that will deliver measurable impact to the business.
9.5.3 Key Participants
This section identifies all stakeholders in the business process(es) being integrated, including business managers who control all or part of the process, system designers and architect(s), and the development team who will execute the implementation. Because the end-to-end process may cross multiple business domains, it may be difficult initially to define all business stakeholders. The process design, review, and verification may, therefore, be an iterative process, with new stakeholders and roles identified along the way.
9.5.4 Business Process Descriptions
This section describes the business processes that have been identified in the requirements. To identify the business processes that need to be defined as part of this specification, start with the Statement of Purpose and the scope of responsibilities defined in the Business Strategies and Initiatives Specification. (Figure 9-1). An alternative way to identify business processes is a bottom up approach (see the process flow models and sequence diagram, section 9.5.5).
Figure 9-1 Statement of Purpose
Reduce the order delivery time
Increase accuracy and decrease time of information provided to other systems and decision makers
Automate business processes to improve efficiency
Automate the online order process by integrating transactions with back-end systems
Automate flow of orders to third party suppliers
Provide real-time visibility and management of the end-to-end order process
Provide online order tracking
Decrease time between order and delivery
Decrease error rates of transactions
Will decrease headcount for order entry department
Will change phone order process
Figure 9-2 Business Process Description Table
Description of Business Process
Business Process Owner
Services Involved in the Process
Outcome of the Business Process
The Process Description Table can be used to identify each process that will be modeled and implemented (Figure 9-2). A name and a business owner identify each business process. A description of the process is provided along with the event that kicks off the process, the business services that are part of the process and the outcome expected which ends the process. If no services have been defined, then define the functions to be performed as part of the process.
9.5.5 Process Flow Models
A process flow model is a combination of the event(s) that start the process, actors involved throughout the process, services provided by software components, the messages passed between and among services, and the business rules controlling the flow of the process. Each process flow model should have a description of each of these entities as well as a process diagram.
The best way to keep models up-to-date is to do it in software. Paper documentation requires changes to be made and distributed in print. It makes keeping the specification up-to-date with the real process far more difficult. It is easier, cheaper, faster, and better to manage models in software. Therefore, this part of the specification may actually have a reference to the process model stored in software. If your modeling tool provides browser-based access to models, then the URL would be part of the process-specification document. Copies of the model may be included in this specification to distribute printed documentation to be used in the verification process.However, it must be recognized that these models can quickly become out of date as the processes change. Therefore, it is important to include the date and version number of all printed process models.
The process model, including the diagram and all associated specifications, should include the following information:
• The kickoff event(s) of the process. There could be more than one starting point, depending on the purpose and the operation of the process. If a process contains more than one starting point, include all of them.
• All tasks/functions/services to be performed during the execution of the process.
• The order in which the tasks/functions/services should be accomplished, including any tasks that may be performed in parallel.
• All decision points, both those having to do with choosing a path through the process and those that determine whether or not the process should continue.
• The business rules that determine the path of the process.
• Any points at which the process path may split or merge.
• The messages input to and output from each task/function/service.
• The completion point of the process.As a process may have multiple starting points, it can also have multiple completion points.
In order to bridge the gap between IT and business and have a seamless handoff between process design and implementation it is important to hand off a business-process model to programmers in a manner they will recognize and use. As noted in section 9.4, there are a number of different modeling methods and systems of notation. The evolving process standards are likely to impact future adoption of a particular modeling method (see Figure 9-3). In the meantime, each tool either supports its own proprietary notation or it supports one of the more widely used methods, such as activity diagrams (usually modified) (Figure 9-4), data flow diagrams (DFD) (Figure 9-5), or IDEF (Figure 9-6). UML is relevant because it has become the most widely applied standard design notation for programmers. The choice of which type of modeling method to use will depend on which industry you're in as well as which tool you use.
Several vendors are now providing different perspectives for different roles in the process. Some are using Eclipse, an open source framework for tools integration, to enable different models for different design perspectives.
9.5.6 Process Design Reviews
Process design reviews are critical to the overall success and agility of the system. The design reviews should include all relevant stakeholders, defined in the Key Participants section. All parts of the model need to be reviewed and verified. Participants need to verify the portions of the process they are responsible for, including all tasks, functions, and/or services, inputs to and outputs from each service, decision points along the process and business rules that determine the process flow of control, as well as all exception and compensation rules. The overall process should be reviewed for opportunities to decrease time and cost, and increase business flexibility and advantage.
9.5.7 Conclusions and Commentary
This section should provide any final comments on the process, the design, or the usage of the system. It should also include any known issues or upcoming business events, such as a merger or acquisition that might have significant impact on some business processes.
9.6 Best Practices in Process Integration
• Plan-Do-Check-Act. Model and verify business processes with all stakeholders. Automate and integrate processes. Monitor processes on a real-time basis with business and operational dashboards, and practice continuous process improvement.
• Manage process models as a corporate asset. The model contains knowledge of the end-to-end business process, which multiple business managers from across the company may have participated in creating. This represents a significant investment. Manage the investment in modeling business processes so that it provides a payoff down the road.
• Standardize. Once again, companies should consider the importance and benefits of standards for long-term viability, reuse, and management of business processes.When a company standardizes on a single modeling method, it facilitates communication and verification of process models across different groups and lowers training costs.
Case Study 9.4 describes how Costco applied process integration and these best practices to improve their decision making process and business results (2003).
Case Study 9.4 Process Improvement Is at the Heart of Costco's Electronic Hardware Services Division
The Electronic Hardware Services (EHS) division of Costco is focused on improving the management of returned computers. In-house and third-party resources are used to refurbish the returned items. EHS has applied a process-integration strategy to their operation with goals to improve its internal effectiveness, reduce costs, and improve on the management of third parties. Its strategy requires significant collection of data from a variety of sources to allow
• Automation of the refurbishment processes
• Tracking of costs at each step in the refurbishment process
• Managing warranty claims
• Dashboards to provide management insight into the operations
Through the automation and integration of processes the EHS division has seen results such as identifying a repeat-trouble pattern and removing the item from sale. This resulted in a strong case for full cost recovery from the vendor rather than having to sell at salvage, plus the removal of future returns. In this one instance it resulted in an increase in cost recovery of $212,000. In addition, through the efforts of process automation the EHS organization became more efficient than third parties. The result was a cost reduction of 66%.
EHS was able to significantly reduce its costs by focusing on the core business process and applying technology. Three lessons learned from this are: focus on the core process, have a point of comparison to judge progress and adjust accordingly, and provide insight through the use of dashboards.
9.7 Next Steps
The Enterprise Integration Architecture provides guidelines and standards for all integration projects. Although the Process Integration Architecture is often last to be defined in the integration adoption cycle, once the infrastructure is in place it should become the starting place for integration solutions. Part III of the book describes technologies and reference architectures for specific types of integration solutions (see Figure 9-7). It must be noted that some integration projects require a combination of integration styles. Chapter 14 provides a reference architecture for a completely integrated enterprise that combines all styles of integration.
Read other excerpts and download more sample chapters from our manufacturing ERP bookshelf