SAP & ERP Consulting from the Customer Point of View

SAP implementation ROI, SAP architecture, & SAP business solutions

ERP vs. ERP II vs. ERP III Future Enterprise Applications

May 31st, 2010

ERP vs ERP ii vs ERP iiiAbstract on ERP I, ERP II, & ERP III

ERP applications integrate enterprise operations within and across enterprise legal entities, or company codes. ERP ii (or ERP 2) applications extend supply functionality to external enterprises (generally vendor-affiliated companies or enterprises) to reduce cost, improve supply chain efficiency, and to perform collaborative innovation.  ERP iii (or ERP 3)enterprises go to the next level of integrating the ERP and ERP ii functionality to include customers and the sales side of the marketplace in general.

Moving To the Border-less Enterprise

I’ve heard and read lots of material about the enterprise applications and what the next generation of ERP is.  Some have suggested that ERP systems were just manufacturing tools (see e.g. ERPwire article on major differences between ERP vs. ERP ii).  They then suggested the next generation of ERP systems, or ERP ii systems, were little more than an extension of ERP functionality to new industry sectors.  In my opinion this is a completely misplaced assessment.  Just changing industry sectors does not change what an ERP application does so a broader definition is more appropriate.

Before we go into the details and background of each of the 3 generations of enterprise applications here are my definitions for ERP, ERP ii, and ERP iii systems:

ERP Definition

An ERP (Enterprise Resource Planning) system integrates virtually all operational business functions and processes and automates entries to finance and reporting within the enterprise (the legal entity or entities that make up an entire company no matter where its operations are).  ERP systems focus almost exclusively on operational excellence value propositions of process efficiency and automation.

ERP II (or, in other words second generation ERP, ERP 2) Definition

Through collaboration, SOA, and other interface, data exchange, or interaction methods the ERP ii systems move beyond Enterprise boundaries (or a basic ERP system) and into the vendor space including the supply, design, and engineering collaboration areas. ERP ii systems continue to enhance operational excellence and start to introduce a measure of the innovation value proposition.

ERP III (or, in other words third generation ERP, ERP 3) Definition

Through collaboration, direct contact, social media, and various data streams within and outside of the enterprise ERP iii integrates marketplace fans and critics into the extended ERP and ERP ii organizations.  From this integration of the customer and vendor a constructive dialog and exchange of information is created to innovate, produce, and then sell / distribute better products or services.  This closes the value proposition loop by going outside of the enterprise boundaries and finding ways to bring customer input, needs, wants, and insight into the enterprise.  ERP iii system create a strong synergy between innovation and customer focus.

ERP System Definition or ERP Defined

The acronym ERP literally stands for “Enterprise Resource Planning.”  And this is exactly where I disagree with the ERPwire definition proposal.  Just a manufacturing system is not an “enterprise” system at all.  It is merely a manufacturing system, or an MES (Manufacturing Execution System).

As the university studies and academic literature note, ERP systems are “a single instance of data, a full process chain of dependencies” (see Change Management Strategies and Knowledge Transfer Processes for a Successful SAP Project citing Kallinikos, 2004). In the ERP industry we (consultants and integrators) frequently refer to any ERP system as a type of “back office” application or system.  By “back office” we are referring to company centered business functions into a single database, or, a single “system of record.”  “Back office” processes are fully within the border and boundary of the enterprise.

In 2000, in an article addressing ERP ii, Gartner noted that they had defined ERP in 1990:

In 1990, Gartner defined ERP, establishing a new vision for the resource planning domain. That vision centered on resource planning and inventory accuracy, as well as visibility beyond the plant and throughout the manufacturing enterprise, regardless of whether the enterprise was a process manufacturer, discrete manufacturer or both. ERP has since appeared in different “flavors.” Extended ERP reflected the fact that many nonmanufacturing industries turned to ERP systems for “backbone” financial transaction processing capabilities (Bond, et. al., 2000 pg. 2, note 2).

That article went on to note that the accepted definition (in 2000 and beyond) had become:

Despite [the] original definition, ERP has become the accepted term for back-office transaction processing systems, regardless of the industry or region (Bond, et. al., 2000 pg. 3).

The definition I have provided is as comprehensive as the original Gartner proposal and includes the later understanding of the application to more industries and business functions.

ERP Focuses on the Operational Excellence Value Proposition

This site provides a much more detailed explanation of the functions and operations of an ERP system like SAP under the section “What is SAP?” ( http://www.r3now.com/define-sap ).

I generally try to categorize all system efforts and business functions into one of three “value proposition” buckets–, operational excellence (ERP), innovation (ERP ii), and customer focus (ERP iii).  The ERP context is almost exclusively focused on the “operational excellence” portion of business “back office” transactional processing.

ERP vs. ERP ii — What is ERP ii?

The next generations of Enterprise applications, or ERP ii systems, extend the “back office” ERP system processing to the extended supply chain.  They extend the enterprise into the supply chain outside of their legal entity borders as an active participant. This would include VMI (Vendor Managed Inventory) processing and KANBAN type demand and supply signals to vendors for JIT (Just In Time) stock management.  But it goes far beyond that, it is the “innovation” portion of the value proposition that is addressed here.

SAP includes ERP ii type extended supply chain applications like SRM (Supplier Relationship Management) and APO (Advanced Planning and Optimization) to help move the supply chain beyond the enterprise borders.

ERP II Creates Collaboration Hubs Beyond Planning Functions and Distribution Functions

Together with the extended supply chain applications there are a number of various exchanges such as common catalogs that are published to the web and integrate with their customer ordering.   Some examples of external exchanges can be seen in initiatives such as “Covisint” for the automotive industry, or Grainger’s online catalog system (although it is not a competitive based platform like Covisint), and many others.

One of the key functions or features of ERP ii systems is supply chain or vendor collaboration, which extends to engineering design and development.  Most enterprises using SRM systems use this to focus on cost reductions, vendor competition, and supply chain efficiencies.  They are generally geared to the “operational excellence” system domain but there is a LOT of untapped possibility.

The highest and best use of ERP ii functionality includes active collaboration with vendors to reduce cost, improve quality, reduce extended supply chain cycle times, and even co-engineer (or co-develop) better products and services.

Many ERP ii solutions now include some type of built-in “reverse auctions” where companies can place requirements out for competitive bids in various formats.  These exchanges might include data interchange methods such as EDI (Electronic Data Interchange) or other standards compliant communication protocols, but they are much more, they are active collaboration hubs.  Together with these collaboration hubs, SOA extensions are being used to extend collaboration and engineering design work to the extended supply chain.

How Has SAP Implemented ERP ii System?

SAP has created an entire collaboration network called the SAP Community Network or SCN (http://scn.sap.com) where customers, vendors, consultants, and any interested party can exchange information, ideas, or dialog.  SAP has implemented ERP ii systems internally through the development of specialized vendor partnerships it calls an “Ecohub” (http://ecohub.sdn.sap.com/).  This is a place where vendors, partners, or other firms with specialized SAP solutions can integrate and promote their offerings to enhance SAP’s various software offerings.  Along with that there are code exchanges, “how-to” articles, discussion forums, and many other types of collaborative information exchanges.  This is similar to what I proposed a few years ago when I wrote “SAP, ERP III, SOA — Learning Organizations through Social Media Collaboration.”

Operational Excellence and Innovation Value Propositions

ERP ii systems integrate the external vendors and suppliers into enterprise processes so that they can directly impact productivity, cost, and efficiency.  Some elements of ERP ii include engineering staff augmentation, free or at a very reasonable rate to the “customer company,” and as a value added service from vendors.  For vendors the ability to augment engineering functions can mean customer retention; for the customer companies this may mean higher quality and lower cost products or services.

SAP’s ERP offerings include PLM (Product Lifecycle Management) with CAD integration for several off the shelf CAD programs.  Although the PLM functionality is primarily used for internal engineering processes it can be pushed out into the extended supply chain for collaborative engineering and design.  That collaboration can be used for innovation if it is properly structured and implemented.  This is in conjunction with other integrated application offerings such as SRM and APO.

By extending engineering or collaboration functions outside of the enterprise, but still within the supply chain, innovation can be introduced into the ERP ii enterprise (see the entire series on Process Execution of Business and IT Innovation).   However, the primary feature of ERP ii systems is the additional operational excellence that is brought about by extended supply chain processing.  Very few companies have succeeded at collaborating with the extended supply chain by introducing extended engineering capabilities, or vendor insight to produce significant innovation.  Most ERP ii systems only work to extend the supply chain beyond the boundaries of the enterprise for cost savings and efficiencies (operational excellence).

Using SOA (Service Oriented Architecture) for Creating ERP ii and ERP iii Enterprises

The promise of ERP ii system success that moves toward ERP iii (discussed in a moment) is SOA or Service Oriented Architecture.

In layman’s terms, SOA is the ability to create a set of “talking points” from any internal system to external systems. 

They are the data structures and data schemas that are published for other systems to interact with and begin to create the framework for the “borderless enterprise.”

ERP iii Defined, What is ERP iii and How Does it Go Beyond ERP ii?

ERP iii addresses the final domain of enterprise class applications by addressing the customer focus value proposition.  It is the extension of technology capabilities which brings collaboration with customers and the broader marketplace into the enterprise system.  This goes way beyond what we currently refer to as CRM (Customer Relationship Management) systems of today.  Today’s CRM applications still operate within the walls of the enterprise and are generally used for managing the sales force rather than moving the enterprise out into the wider marketplace and to direct interaction with customers.

ERP iii from a high level is fairly easy to define, however what it looks like in a few years is difficult to predict.  The areas that ERP iii touches are in a rapid state of change because of the dynamic nature of social media and the global marketplace.

ERP iii Defined

ERP applications integrate enterprise operations within and across enterprise legal entities, or company codes. ERP ii applications extend supply functionality to external enterprises (generally vendor-affiliated companies or enterprises) to reduce cost, improve supply chain efficiency, and to perform collaborative innovation.  ERP iii enterprises go to the next level of integrating the ERP and ERP ii functionality to include customers and the sales side of the marketplace in general.

The end state of the ERP iii enterprise would include a dialog between customers (and potential customers), the ERP organization, and the extended supply chain so that even suppliers would participate in the sales side of the marketplace.  Because there is little or no information in the markeplace about ERP iii direction and design I am offering a more detailed definition here:

Through collaboration, direct contact, social media, and various data streams within and outside of the enterprise ERP iii integrates marketplace fans and critics into the extended ERP and ERP ii organizations.  From the integration of customers and vendors beyond the enterprise boundaries a constructive dialog or information exchange is created to innovate, produce, and then sell (or distribute) better products or services.

ERP iii will create the “borderless enterprise” by bringing together a host of technology sources such as:

  • Collaboration tools (within the enterprise and across the supply chain and marketplace)
  • Social media
  • Internet technologies
  • SOA
  • Smart information integration and synthesis (specialized search with analytics or within specific information domains).  An early example of this type of search is a web service called “Lijit.”  Lijit allows you to manually assign searchable information sources for a customized, high value “search engine.”
  • Extended marketing analytics that are “like” tracking cookies but less invasive and use additional sources of information and research beyond the web (a good example is like grocery store checkout programs that automatically print coupons on the back of your store receipts based on what you just purchased).
  • Direct customer collaboration (we see early examples of this in the Dell “designed by me” and “I made Windows 7” television commercial marketing campaigns).

The Future of ERP iii Systems

Within the extended SAP enterprise (which is my area of expertise) I see many of the seeds of ERP iii germinating and beginning to grow.  Even though the initial “green shoots” are there for an ERP iii revolution I don’t anticipate that occurring for several years within SAP.

Today SAP has:

  • Very active, country specific SAP User Groups (xSUG, in America is it ASUG) with “influence councils”
  • Community forums (previously mentioned)
  • “Mentor Groups” within the community network.

While these all contain the seeds of ERP iii outlets I do not see a lot of the raw material being converted into application enhancements to directly address business marketplace demands.  There are still way too many technical solutions for for technical needs and not enough for genuine business needs.

ERP iii integrates marketplace fans and critics into the extended ERP and ERP ii organizations to innovate, produce, and then sell (or distribute) “customer-centric” products or services.

I doubt that the integration of more social media will move the ERP iii needle much further.  SAP like any other company that embarks on this type of transformational exercise must begin to use their well established outlets to drive innovation and to meet marketplace requirements (see the entire series on Process Execution of Business and IT Innovation).

Social Media and ERP iii

Social media outlets like Facebook, Twitter, and other resources will need to become more sophisticated to produce meaningful differences in business-centered innovation or customer focus.  That sophistication for business will mean finding a means to use those outlets for genuine business competitive advantage.

It will take business some time to find new ways to tap into the collective marketplace consciousness through social media in spite of the massive number of what I refer to as “snake oil sales” people.  Social media in the enterprise will not be useful until the snake oil sales finally align actual business needs to areas of the enterprise (sales, marketing, HR recruiting, etc.) that align with business goals and directions (see Social Media Fads and the Risk to the Enterprise).

Before ERP iii systems are ready for the extended marketplace and for customer interaction it will require “back office” integration with social media (see ERP III – Is the Integration of Collaboration the Future of Enterprise Applications).

As social media and collaboration tools mature over the next 10 or more years then corporations will finally build the ERP iii systems for integration into the wider marketplace.  By then the ERP ii systems will have finally matured to the point that some of them can provide meaningful integration between the enterprise, the entire supply chain and the sales side of the marketplace in general.

ERP, ERP ii, and ERP iii Conclusion

Considering this specialized class of business systems through the lens of the high level value propositions of 1) operations, 2) innovation, and 3) customers; here is my summary:

ERP (Enterprise Resource Planning)

Primarily focused on the “back office” with a heavy emphasis on operations, automation, cost control, financial activity, and lagging business indicators of performance.

ERP ii (the second generation of Enterprise Resource Planning)

Extends “back office” processing functions and operations into the extended supply chain with a heavy emphasis on supply chain automation, additional efficiency, more cost control, and some vendor collaboration for limited innovation.  This area of the application moves into the “last mile” of improvements that can be more expensive to implement and yield lower returns.  However, carried out properly with significant supply chain collaboration and joint engineering or development efforts this can provide new / innovative products or services addressing both lagging indicators of cost control and efficiency while exploring leading indicators of new products or services.

ERP iii (the next generation of Enterprise Resource Planning)

This will encompass the integration of social media with new marketplace intelligence and analytics into the ERP ii enterprise.  With a very simply “hub and spoke” idea, the enterprise will constitute the “hub” and the extended supply chain vendors, engineers, and designers, together with customers and market analysis as some of the “spokes.”  This will be enabled by the ERP application that is extended with collaboration and social media tools.  The ERP, ERP ii, and ERP iii functions will all be integrated with new analytics and “smart source” search methods to integrate and synthesize trend, market, and product or service information.  This will close the loop on the ERP ii innovation and will bring a new customer focused business paradigm into the enterprise that goes far beyond today’s CRM applications.

ERP iii state companies will be marketplace disrupters who are agile, nimble, and global.  They will be able to spot emerging trends and unmet customer demands (needs or wants) far more quickly and with greater ability than their peers.  From those trends and customer needs these companies will be able to quickly execute innovation programs to develop new products and services to quickly fill those customer demands.  The most advanced of these new “disruptive innovators” will be the companies who can intelligently synthesize all of the various data points to understand customer demands that are not even articulated.

======================

Bond, B., Genovese, Y., Miklovic, D., Wood, N., Zrimsek, B., and Rayner, N. (2000). ERP Is Dead — Long Live ERP II; Gartner Publications.

Kallinikos, J. (2004), “Deconstructing Information Packages. Organizational and Behavioral Implications of ERP Systems.” Information Technology and People, Vol. 17, No. 1, pp. 8-30.

Related Posts:

SAP, ERP III, SOA — Learning Organizations through Social Media Collaboration

April 27th, 2007

 SAP, ERP III, SOA, and collaboration

Knowledge Management Introduction

Everyone’s heard the buzzwords, ERP, SAP, SOA, you name it.  In the technology area they’re everywhere.  These are just acronyms for ways companies try to leverage technology for competitive business advantage.  Reduce costs, streamline operations, increase revenue, and transform your organization.[1]

Since ERP applications and technology transformation have entered the business world there remains one area that enterprises struggle with –, the realm of capturing and then converting employee “know how” into ERP solutions–, Knowledge Management.[2],[3]  There is a simple, inexpensive way to implement ERP III, enabling your ERP application to transform your enterprise into a learning organization.  ERP III is simply a way to capture that “know how” to develop SOA (Service Oriented Architecture) and business solutions to create real competitive advantage.

Background for SOA, Knowledge Management, and ERP III

The ERP revolution began with integrating the “back office” functions of the enterprise: purchasing, ordering, financials, HR, distribution, inventory, etc.  The idea is that the whole enterprise relies upon a common set of data from a single database which provides one version of the truth or a lie–, one version to rely upon or correct nevertheless.  Then we have ERP II, extending the ERP application from the back office to the extended supply chain, to the web, to the banks, and beyond. 

Enter SOA or Service Oriented Architecture, the idea of “universal” and completely reusable application services that can be “plugged in” to other applications.  This SOA architecture would then allow for the rapid assembly of dynamic process chains and application chains as business and opportunity needs arise.  SOA holds tremendous promise to enhance and extend the idea of ERP II even further, but an idea that will take time and tremendous effort to get off the ground and do effectively. 

ERP III and the Learning Organization

The next generation of business transformation is ERP III, or the ERP enabled learning organization.[4] However, SOA’s success and timeliness are  directly tied to how well an enterprise is able to create a “learning organization” within its development and IT ranks.  But this learning organization method can and should be applied to the entire organization.

This learning organization approach is one of the key backbones to a successful SOA initiative as well.  The cornerstone of effective SOA re-use policies and procedures, service standards, and validated service development is directly correlated to how well the enterprises developers are able to collaborate and coordinate their efforts (especially in an ad hoc manner).

Service Oriented Architecture, or “SOA” requires a level of participation, collaboration, and information exchange like never before to be successful.  True “SOA” requires a blending of technology, collaboration, and cooperation with highly structured standards to achieve a significant level of trust in the development work.  While many suggest that this level of collaboration, integration, and reliability within the enterprise may take enterprises as long as 10 years to accomplish, the methods defined in this paper can dramatically reduce that time and effort. [5]

What is Knowledge Management?  [6]

There seems to be no widely accepted “definition” for knowledge management, and as I review the information on Wikipedia about Knowledge Management I find a rambling discussion of high level theoretical constructs with little substance.  As a result I am offering my definition here, and some clarification, which helps to distinguish knowledge from information. 

“Knowledge Management is not information management.  It is the process of transforming unstructured data into contextual information and then applying that information.  Knowledge as “contextual information” is the ability to draw on information and combine it with experience by applying it to a particular situation or circumstance when it is needed.  Knowledge Management is the process of capturing, codifying, and disseminating information so that it provides some value in a particular context.”

Bill Wood

My personal opinion is that the reason there is little consensus on a Knowledge Management definition is because most “knowledge management” discussions surround information management.  They are the codification or classification systems that help to capture and codify knowledge but they do not take knowledge to the next step of infusing it into the enterprise (or creating a learning organization).  And from there, pushing it still further to the application of that information in a value added context for day to day activities.  It is only with the application of information coupled with experience that something becomes “knowledge”–, it is NOT some system.

For the enterprise to continue to “wring value” out of the ERP implementation or other technology investments, the enterprise must change.  For the ERP enterprise to be effective, technology must support the capture, organization, and implementation of the unstructured knowledge contained in people’s heads, or jotted down on crib sheets.  This is not an easy task.

Knowledge is not data and information. Data consists of facts, observations, occurrences, numbers, and things that are objectively perceived.

Information is a collection of various aggregated or synthesized data points. From there, Knowledge is the mix of information, experience, and context adding value to an activity or process…

Knowledge Management is the systematic process by which an organization maximizes the uncodified and codified knowledge within an organization.

Author(s) unkown.

Before beginning it is crucial to understand the often misused, misunderstood, and even abused concept of “Knowledge Management.”  Contrary to so many of the technology offerings out there, knowledge management rarely is a system, however systems do facilitate knowledge management. 

Systems, by their nature and design are information tools.  Too many times the term “Knowledge Management” is used to describe information gathering and classification systems–, information systems.  Some even call their systems “knowledge bases,” and maybe they are bases for knowledge, however, they are not knowledge management systems.  Until information is learned, and then applied, it is not knowledge, it is merely information.

Knowledge Management, Collaboration Tools, and ERP III – Current and Future State

The initial process of implementing SAP requires taking structured and unstructured data, along with the processes from legacy systems and people, then placing this information into a highly structured application.  At its most effective, the initial SAP implementation captures some cost savings, process improvements, and revenue generating opportunities.  However, no initial implementation is able to capture the vast unstructured knowledge that resides in people’s heads. 

The SAP enterprise current state, with the application you’ve implemented, and possibly some of the ERP II enhancements, still has the possibility to deliver far greater benefit without significant cost.  To capture and leverage that benefit requires an enterprise wide cultural transformation.  People must begin to both act and think differently.

To extend the SAP application’s usefulness and achieve greater benefit it is critical to a) capture the “unstructured” information, b) then organize, classify, or categorize it, and then c) translate and structure that into more useful application solutions.  This process also facilitates the implementation of SOA within the SAP environment.

The first step toward the future state is to create a collaborative learning organization.  A learning organization is an organization that is constantly acquiring and applying new information and thereby gaining knowledge.  Once that information is captured, it can then be structured into solutions, some process based, and others technology based. Some of the solutions can be translated into additional, value added SAP enhancements or additional SAP functionality.

A Collaborative Knowledge Management Model for a Learning Organization

Based on my time at Hitachi Consulting, as the SAP Knowledge Manager, I made use of the best resources I could find in the arena of “Knowledge Management.”  Based on that research, and leveraging the pioneering efforts of other true knowledge managers, I created the model you see here.  It is consistent with much of the literature that exists today, however, in 2000, it was a pioneering effort.

1)  Raw Data:  The unstructured data, ideas, “crib notes,” and thoughts that we all have.  However in this instance, it is the raw data surrounding the job or responsibility that the individual performs within the enterprise.  Sometimes these are the “workarounds” to get something done when you run into obstacles or roadblocks, other times they are just shortcuts or techniques to perform a job or function.

Knowledge Management Process

2)    Organized Information:  This is the process of capturing and classifying that raw data.  This is where the “knowledge bases” and other types of information systems come in.  Many enterprises make it this far. Sometimes these are the “workarounds” to get something done when you run into roadblocks or obstacles.  Other times they might be the shortcuts or techniques to more efficiently perform a job or function.

3)    Acquired Information Experience: This is the interaction with the organized information.  This can be through search functions, employed taxonomies, reports, or other methods of accessing the organized information.  This is after the capture of the information in steps 1) and 2) above, and involves its wider availability than in the individual who originally developed or “held” the knowledge or information.  Few organizations or enterprises make it much further than this.  However, this is the beginning of the true learning organization.

4)    Applied Experience (Knowledge!):  This is the practical application of the organized information after it has been acquired.  Whether this acquisition is through word of mouth, training, or some type of information management system (that is wrong named a knowledge management system) or through a “knowledge base”. This is where the cost savings, revenue opportunities, continuous process improvement opportunities, and real competitive advantage begins to come to fruition.

5)    Refined Experience:  This is more of the inherent “knowing” what to do in a broad variety of contexts that may not be directly related to the task or issue at hand.  It is when an individual can draw on that level of inner experiences mixed with intuition and make the right decision or provide the right answers when there is not enough information to make such a determination under normal circumstances.  This can also be a type of “making the complex appear to be simple.” 

There is a simple and effective method to capture the unstructured information, organize and classify it, and then disseminate it in such a way as to create a true learning organization.  This method, outlined below, will help to move your organization through the 5 steps noted here.

Practical and Inexpensive Ways to Move Toward ERP III and SOA Today!

Since I am not a big fan of reinventing the wheel I look for existing ways to solve current problems.  To that end, the key to moving ahead on ERP III is to create a collaborative culture, from the collaborative culture, you create a learning organization by using some of the existing collaborative tools.  The answer lies in using some of the popular web technologies making a splash today.

Enter the “cool” and the “fun” factor in the enterprise–, “social networking” is one of the hottest, and most vibrant collaborative uses of technology anywhere.  From MySpace to FaceBook to online forums, these sites connect people for personal exchanges.  While not appropriate for the types of personal exchanges on the world wide web, that same technology can be used to create a collaborative environment around cost savings, process improvements, system enhancements, revenue opportunities, and general business improvement for competitive advantage.  The list of possibilities is only limited by what you can imagine can be leveraged from participant knowledge.

Forums can also be used to capture SOA related standards, common development services, and to do code or object reviews.  They can be used to capture SOA best practices while facilitating broader development community participation in standards, services, and object re-use policies.  The collaborative nature, and the ability to offer code improvement suggestions, bug fixes, standards exchanges, or development and solutions discussions, in a threaded forum will prove invaluable to an organizations SOA initiatives.

To make this a reality, the key is to leverage tools, and define a process that captures the unstructured information .  Once it is captured, methodically move that to process changes or to structured application solutions within SAP or an SOA initiative.

Defined below is a set of free tools, along with proposed solutions on how to apply those tools in a practical manner:

1)    ANY networked PC (you don’t really need “heavy duty” hardware here unless you just must have blistering performance)

2)    Download the free Uniform Server application that works on Windows.  It contains Apache Web Server, MySQL, and PHP (including PHP My Admin).  http://www.uniformserver.com/   You only need to unzip this file to a local directory, and then double-click (or execute) the Start Server file.

3)    Download and Install the latest PHP Bulletin Board open source application:  http://www.phpbb.com/downloads/   (Set up the MySQL database and copy the web files to the proper local directory of the newly created web server from step 2).  To see the forums in action, go to the PHPBB site at: http://www.phpbb.com/community/

4)    Structure the Groups to match the business department (create a new forum “group”), and then create 4 sub-areas under each department link.  A)  Cost Savings, B)  Revenue Generation, C)  Process Improvement,  D) System Changes.

5)    Structure additional groups to match SOA service development.  An SOA topic with sub-forums for A) standards, B) services, C) objects, etc.

6)    Have the users create the hyperlinks in their SAP user menu.  A hyperlink for that departments topic in the bulletin board is easy to add to the SAP user menu (right click on the favorites menu, then add a web address, it’s really that simple.)

7)    Adjust department and user goals to include evaluating forum contributions, based on points earned for participation, and aligned with the forum structure that applies to them (for example, cost savings, revenue generation, SOA standards, etc.)

8)    For the system changes option, create an inexpensive interface to read the MySQL table for this area and generate a separate approval / response process.  This way the changes, and responses to those change requests, as well as the details of the change request, are captured in an easily searchable database.

9)    To produce the most useful solutions, follow a “PDCA” process (Plan, Do, Check, Act).  After a discussion thread has reached a certain point where the exchanges have stopped, reduced to a trickle, or a specific date deadline, have someone review the entire threaded discussion, capture the most salient posts (by using the hyperlinks to the posts), and then summarize those hyperlinks into a single post. Call a meeting with the key stakeholders, review the salient points and produce a position paper or some other summary document and then publish that for final review.

The PHPBB forum software contains several developer implemented modifications that are available, and fully supported at no charge [7].  For example they have a “cash” modification that is nothing more than adding a point system based [8] on how active a forum participant is.  In combination with the ability to develop groups, and to have moderators approve posts, this is an effective way to manage the information “clutter.”

Goals can be based on the number of points.  Posts can be reviewed and approved by the department supervisor, or even a skip-level manager as the moderator.  This ensures that the submissions are both high quality, and that they are being reviewed. 

Over time, in areas such as manufacturing maintenance, or any other similar situations, enough quality information could be captured to create solution databases.  This would facilitate the introduction of PM (Plant Maintenance) [9] for both preventive and predictive maintenance programs.

The searchable nature of the forums allows for quick and easy information retrieval in the short term.  Over a longer period of time, the information can be structured and implemented as various types of system solutions to address recurring themes or various business opportunities. 

Collaboration, virtual discussions, and even “debates” will ultimately occur in such a way that they help to refine various business issues or problems.  In the future, as the issues arise again, going back through the old dialogs may yield a new perspective or new direction for the future.  In the end, the cultural change to a learning organization will begin, and along with it new information and ultimately new knowledge will emerge to use for competitive advantage.

ERP III, Knowledge Management, Collaboration, and Learning Organizations – The Conclusion

Competitive advantage and the emergence of the extended enterprise through SOA, and the extended supply chain demand greater collaboration.  This collaboration is a key component of creating the learning organization.

SOA and additional benefit realization from an SAP implementation depend heavily on the ability of an organization to capture competitive advantage from the knowledge of the employee base.  Even skilled IT contractors must rely heavily upon the acquired knowledge and wisdom of those who actually perform the enterprise’s processes on a day to day basis. 

No matter how skilled an IT professional may be, there will always be some things that escape detection or discovery because of the nature of intangible “knowledge” that exists within any individual or organization.  The key to leveraging the IT investment in SAP and in implementing an effective SOA program is in finding ways to create collaborative communities to expose that knowledge.  This collaboration can become the basis of a “learning organization” that is a key to transforming both the enterprise and the IT infrastructure that supports it. Using today’s “social networking” tools, as a means to advance that collaborative culture is one of the most cost effective ways to accomplish the task of organizational transformation.

 

~~~~~~~~~~~~~~~~~~~~~~

[1]  SAP as a Change Enabler  http://www.r3now.com/sap-as-a-change-enabler

[2]  Knowledge Management—Emerging Perspectives: http://www.systems-thinking.org/kmgmt/kmgmt.htm

[3]  Knowledge Management Journal – Business process modeling through the knowledge management perspective: http://www.emeraldinsight.com/Insight/ViewContentServlet?Filename=Published/EmeraldFullTextArticle/Articles/2300100303.html

[4]  Learning Organization from Wikipedia – http://en.wikipedia.org/wiki/Learning_organization

[5]  Hitachi Consulting, where I previously worked in the SAP practice as a functional consultant and the SAP Knowledge Manager has published a white paper on SOA that explains both its promise and its drawbacks; SOA – CIO Savior or Nemesis, http://www.hitachiconsulting.com/downloadPdf.cfm?ID=414

[6]  One important distinction to note here is that this paper will focus on the implementation of the “learning organization” in practical ways throughout the enterprise.  This “learning organization” approach has far reaching affects beyond SOA, it has the ability to transform business through the use of enabling technologies.

[7]  For example, see this forum which lists many of the validated and approved modifications, along with full support information and enhancement options.  http://www.phpbb.com/community/viewforum.php?f=15

[8] Forum with information for installing, updating, and enhancing or modifying the “cash” (i.e. points) modification to the PHPBB forum.  http://www.phpbb.com/community/viewtopic.php?p=539420

How to access the modifications while the modification database is unavailable (it is currently undergoing a complete update and re-write).  http://www.phpbb.com/community/viewtopic.php?f=15&t=527421

[9]  For example, see SAP’s Plant Maintenance solution:  http://help.sap.com/saphelp_47x200/helpdata/en/66/158661547611d182cc0000e829fbfe/frameset.htm

Related Posts: