For the C-level executive team at Oasis the most critical strategic decision with regard to Web 2.0 technologies is processes, systems and functional areas can take the greatest advantage of their benefits. It is clear that the globally-based distributed order management process could be much more collaborative given its breadth of activity across so many manufacturing centers. The need for creating a collaborative distributed order management system globally is what differentiates best-in-class manufacturers from those that struggle to stay profitable (Alt, Gizanis, Legner, 2005). The use of Web 2.0-based applications for enabling greater levels of collaboration globally in the Oasis product development teams is also a high priority, as this specific process is essential for the new product development and introduction (NPDI) process to be effective. The rapid adoption of collaborative new product development processes has continued to revolutionize the development of new products and services, and has been particularly effective in globally diapered teams (Shamsuzzoha, Kyllonen, Helo, 2009). This aspect of Web 2.0 has a highly pragmatic value for Oasis in that the benefits gained can be seen in the reflected increased time-to-market of new designs, in addition to enhanced metrics of performance for the new product design and development process. With the need to coordinate development efforts between 65 designers across Taiwan, China, Japan, U.S. And the Netherlands, a Web-based collaboration platform and applications that have the efficiency and performance of Web 2.0-based applications is critical. Collaboration platforms used for the NPDI processes also need to have exceptionally high levels of security and authentication to the 256-bit level to be effective (Shamsuzzoha, Kyllonen, Helo, 2009). For Oasis and the highly competitive industry they compete in, security needs to be engrained in the application, in addition to the development of scalability features for supporting 24/7 access across a broad range of geographies as well. All of these factors need to be contained within a functional definition of the NPDI portal and working areas of the SOA framework. Part II: Oasis Bicycles Case Analysis

Introduction

As CIOs are given the challenge of creating transformational change through the use of IT while also delivering secure, reliable and scalable services and keeping the company running from an information standpoint, the selection of an ERP vendor to partner with is critically important. For the CIO, their decision to select one ERP system over another has career implications. Choosing the best possible ERP system can also significantly increase their marketability for future career growth as well. For the CIO of Oasis these are all considerations as the decision is made which ERP provider they partner with. Oasis' unique manufacturing needs could be automated by Epicor and their Microsoft .Net platform, Infor, Microsoft, SAP, or Oracle. There are literally dozens of other smaller ERP vendors to also choose from. These are the most active in the area of manufacturing. The criteria of their ERP system being able to scale globally and also keep the same system of record for managing pricing is clear, as is the need to support non-traditional workflows including quote-to-order and build-to-order. Oasis needs to keep their requirement of supporting demand-driven supply chains at the forefront of their priorities as well.

When all of these factors are taken into account and the needs of Oasis evaluated relative to these companies, the best possible ERP system would be from SAP AG. SAP's expertise in global deployments and the ability to define and execute collaborative production processes that support make-to-stock and quote-to-order is evident in their legacy of the Variant Configurator and its use with the Internet Pricing Configurator (IPC) engine. These two modules would be used for capturing both standardized and build-to-order bicycle orders. The SAP architecture also has several modules for managing operations including a Manufacturing Execution Systems (MES) workflow that would allow for Oasis to align the best possible manufacturing center to fulfill each specific order. There is also a distributed order management system integrated in the SAP platform for supporting multiple location workflows. The need for a globally-based distributed order management system is critical for a globally-based enterprise to operate profitably (Alt, Gizanis, Legner, 2005). Finally SAP has a CRM suite of applications that can also manage the marketing and sales processes of Oasis. The MySAP CRM suite of applications are integrated to the IPC which makes it possible for Oasis to complete quotes and order interactively from any distributor, dealer or service point in their network. The SAP ERP Financials are better aligned with manufacturing than competitors given their support for pricing and costing variations by geographic locations, including tax considerations by regional area. All of these factors support choosing SAP as the ERP system for Oasis. In conclusion SAP's development of NetWeaver, their SOA platform, will further assist Oasis...

This can be daunting, as the culture of outsourcing companies is often significantly different than those of manufacturing companies. Oasis needs to consider internal consolidation of service areas as thei direction proposed by the IT investment in SAP would make this possible. As the bicycle business is highly unique, the management of knowledge and its value is best kept inside the company. Outsourcing non-strategic processes including payroll, Accounts Payable and Accounts Receivable could over time free up more resources to support the core business strategies and functions of the company. This would be the best strategy for Oasis as it will be the least invasive in terms of cultural conflict and the least likely to fail. For Oasis and their global development plans and the speed at which information needs to move, it is highly recommended to not outsourcing any core functional area of their business. The need to have a very rapid time-to-market is critical in their industry and outsourcing a core strategic area of the business would run a very great risk of crippling their ability to stay demand-driven. This is a key aspect of their overall strategic direction and investment in an ERP system to begin with.
References

Adel M. Aladwani. 2001. Change management strategies for successful ERP implementation. Business Process Management Journal 7, no. 3, (January 1): 266-275.

Rainer Alt, Dimitrios Gizanis, and Christine Legner. 2005. Collaborative order management: toward standard solutions for interorganisational order management. International Journal of Technology Management 31, no. 1,2, (January 1): 78-97.

Bernoff, J., and C. Li. 2008. Harnessing the Power of the Oh-So-Social Web. MIT Sloan Management Review 49, no. 3, (April 1): 36-42.

(Brown, He, 2007)

David H. Brown, and Susan He. 2007. Patterns of ERP Adoption and Implementation in China and Some Implications. Electronic Markets 17, no. 2, (May 1): 132.

Chan, E., A. Mills, and D. Walker. 2008. Impact of leadership and power on successful ERP adoption. International Journal of Human Resources Development and Management 8, no. 3, (July 1): 216.

Chang, H., C. Yin, and H. Chou. 2008. Diffusion of Enterprise Resource Planning Systems in Taiwan: Influence Sources and the Y2K Effect. International Journal of Enterprise Information Systems 4, no. 1, (January 1): 34-47.

John E. Ettlie, Victor J. Perotti, Daniel A Joseph, and Mark J. Cotteleer. 2005. Strategic predictors of successful enterprise system deployment. International Journal of Operations & Production Management 25, no. 9/10, (September 1): 953-972.

Yvonne Van Everdingen, Jos Van Hillegersberg, and Eric Waarts. 2000. ERP adoption by European midsize companies. Association for Computing Machinery. Communications of the ACM 43, no. 4, (April 1): 27-31.

Morton, N., and Q. Hu. 2008. Implications of the fit between organizational structure and ERP: A structural contingency theory perspective. International Journal of Information Management 28, no. 5, (October 1): 391.

Tim O'Reilly. 2006. Web 2.0: Stuck on a Name or Hooked on Value? Dr. Dobb's Journal, July 1, 10.

Robin G. Qiu. (2007). A service-oriented integration framework for semiconductor manufacturing systems. International Journal of Manufacturing Technology and Management, 10(2/3), 177

Rothenberger, M., and Srite. 2009. An Investigation of Customization in ERP System Implementations. IEEE Transactions on Engineering Management 56, no. 4, (November 1): 663.

Ahm Shamsuzzoha, Sami Kyllonen, and Petri Helo. 2009. Collaborative customized product development framework. Industrial Management + Data Systems 109, no. 5, (June 10): 718-735.

Appendix A Web 2.0 Meme Map

Appendix B: Web 2.0 Applications

WEB 2.0 APPLICATIONS

Applications

Descriptions

Blogs

Online diary or journal entry on the Internet, which primarily supports text, photo (photoblog), video (vlog), and audio (podcast) formats

• Google, AOL, and Yahoo offer free blogging platforms

Mashup

• Web service that gathers related content from more than one source

• IBM's mashup applications enable project managers to match team resources with a map to identify the geographical locations of the resources

Peer-to-Peer Networking

• A technique for effectively sharing music, audio, and text files

• Napster and Gnutella are popular peer-to-peer networks

Real Simple Syndication (RSS)

• Feed-based technology that, with the aid of an RSS reader, enables users to subscribe to newly released content such as text, Web pages, sound files, photos, and video

• RSS feed may contain the full content,…