July 06, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club
Collaboration Syndicate This
Print this article    Email this article    Talk Back!    Write to Editor
Intra-Enterprise Collaboration
07/10/2005
By John Stelzer, Director of Industry Development, Sterling Commerce

The shift to growth-oriented initiatives is causing companies to reach outside the enterprise to collaborate with others in its supply ecosystem. This multi-enterprise collaboration (MEC) is the technique by which organizations are able to progress along the path toward visible business. Its components involve the availability, analysis, and application of information to generate worth. In this article, we turn to examples of MEC within an enterprise.

ADVERTISEMENT
Our Popular Webinars
BPM for Financial Services
Roundtable Discussion: Open Source Market Update
Evolving Security Architectures and SOA for Better Business Collaboration
Getting Started with BPM
Roundtable Discussion: MDM's Role as a Critical Enabler for SOA
More Webinars

MEC WITHIN THE CORPORATION

The term multi-enterprise collaboration need not be taken literally in order to realize substantial benefits. While its words imply that it only encompasses interaction between two or more companies, there are also valid examples where entities behave like autonomous enterprises within a single company.

For example, in industries where growth or diversification through acquisition is widely practiced, it is increasingly common to find enterprises with separate business units, divisions, and in some cases autonomous companies within the corporation. Often, these entities function very independently with little or no collaboration.

In some cases, these are disparate businesses with little in common. In these situations, there may be little opportunity—or reason—for a high degree of collaboration. However, in most instances, there is at least some level at which increased collaboration would benefit the participants, the company as a whole, and—very likely—others in their supply ecosystem. For such situations, MEC should be applied to the interaction between these internal “enterprises.”

Example #1: Manufacturer Internal MEC

Consider, for instance, a national homebuilder—we’ll call them Company X—that grew through acquisition. A significant portion of Company X’s growth had come by acquiring local builders that had a regional presence in an area where Company X did not previously have a footprint.

Company X allowed each of its acquired businesses to operate much the same after the acquisition as it had before. A new division would continue to use pre-existing computer systems and business applications; it would continue to buy from the same suppliers as before (sometimes directly from the manufacturer, sometimes from a local distributor); its product identification and categorizations were kept “as is,” etc. [Figure 1]

The company’s rapid rate of growth—and its willingness to allow each division to continue to operate in a particularly autonomous fashion—meant that the corporation was unable to obtain or leverage a holistic view of their entire business. For example, the product codes—used to order product and track which supplies were purchased and from whom they were bought—had not been rationalized or normalized across divisions. This meant that Division One might purchase a particular product type from the national manufacturer, Division Two might purchase it from a local distributor, and Division Three might be purchasing a substitute product from yet another source.

Page 1

More Top Stories
RFG: Is it Time for Web 2.0 Collaboration? Gold Club Protected
Is Governance the Silver Bullet of Agility? Gold Club Protected
Doing Risk Management Right Gold Club Protected
Forrester Research: BPM Tool Use Varies By Sector Gold Club Protected
What Microsoft Gains (and Faces) With Yahoo! Gold Club Protected
Closeout Special: Microsoft Bids for Yahoo! Gold Club Protected
More Top Stories
Related News
Microsoft and Micro Focus Invest in Enterprise Application Modernization
AmberPoint Launches Systems Integrator Partner Program
StarVest Partners Acquires IRON Solutions
More News
Subscribe to our Newsletters
ebizQ Weekly Gold Club Update
Live Webinar Updates
Updates from ebizQ Partners
ebizQ SOA Update
ebizQ BPM Update
ebizQ Security Update
ebizQ BI Update
ebizQ Open Source Software Update
Virtual Show Newsletter
ebizQ Web 2.0 and the Enterprise
Your E-mail Address:
Changing Tires on a Moving Car
Case studies and solutions for governing the continuous evolution of complex SOA systems

Date: Jul 15, 2008
Time: 12:00 PM ET
(16:00 GMT)

REGISTER TODAY!
Roundtable Discussion: MDM's Role as a Critical Enabler for SOA
Date: Jul 16, 2008
Time: 12:00 PM ET
(16:00 GMT)

REGISTER TODAY!
Archived Webinars | Upcoming Webinars
  BI for Consumer Packaged Goods

By: Don Tapscott WHILE HISTORICALLY consumer packaged goods (CPG) organizations have made significant investments in data collection and...Learn More

ebizQ also recommends
 Optimal Service-Parts Management: Part One
 The Geek Gap: Do Suits Care?
 Collaboration and Social Media <i>Taking Stock of Today's Experiences and Tomorrow's Opportunities</i>
 BPM Done Right
 Mitigate Risk with Security Assessments
More White Papers

Marketing Solutions | Feedback | About ebizQ | Unsubscribe | Privacy Policy | Site Map

Live Chat