Intel is one of the Biggest Company

Intel Company is one of the Biggest company in manufacture of computer prouducts. Intel Corporation is an American global technology company and the world's largest semiconductor chip maker, based on revenue. It is the inventor of the x86 series of microprocessors, the processors found in most personal computers. Intel was founded on July 18, 1968, as Integrated Electronics Corporation (though a common misconception is that "Intel" is from the word intelligence) and is based in Santa Clara, California, USA. Intel also makes motherboard chipsets, network interface controllers and integrated circuits, flash memory, graphic chips, embedded processors and other devices related to communications and computing. Founded by semiconductor pioneers Robert Noyce and Gordon Moore and widely associated with the executive leadership and vision of Andrew Grove, Intel combines advanced chip design capability with a leading-edge manufacturing capability. Originally known primarily to engineers and technologists, Intel's "Intel Inside" advertising campaign of the 1990s made it and its Pentium processor household names.

Intel was an early developer of SRAM and DRAM memory chips, and this represented the majority of its business until 1981. While Intel created the first commercial microprocessor chip in 1971, it was not until the success of the personal computer (PC) that this became their primary business. During the 1990s, Intel invested heavily in new microprocessor designs fostering the rapid growth of the computer industry. During this period Intel became the dominant supplier of microprocessors for PCs, and was known for aggressive and sometimes controversial tactics in defense of its market position, particularly against AMD, as well as a struggle with Microsoft for control over the direction of the PC industry. The 2010 rankings of the world's 100 most powerful brands published by Millward Brown Optimor showed the company's brand value at number 48. I like Intel. Thank you.

Company Overview of Cignex:


The CIGNEX was created by a team of entrepreneurs dedicated to Making Open Source Work for for Enterprises.

CIGNEX was founded in Santa Clara, CA in 2000. They will helped enterprises migrate to open source technologies across Enterprise Content Management, Portals & Social Collaboration, e-commerce, Business Intelligence and ERP through a proven open source adoption methodology. By combining best practices from over 200 successful engagements with the shared knowledge derived from a combined 200 years of consulting experience in the management team, Cignex've developed a powerful, flexible approach to building and deploying Enterprise solutions based on open source technologies.

With the increasing adoption of open source technologies globally, CIGNEX identified the need to extend its offerings to

  • support the existing proprietary tools & technologies of its clients to facilitate a seamless migration to open source solutions
  • seamlessly integrate the open source solutions with existing Enterprise applications such as ERP, CRM, etc.
  • incorporate functional domain expertise to roll out Open Source ERP solutions

With the above objectives in mind, CIGNEX has gone through the following two mergers to form CIGNEX Holding Corporation (CHC).

  • Apar Technologies, a specialist IT Professional Services and Consulting organisation, in 2008.
  • AGS Technologies, an SAP, Oracle and Open Source ERP Consulting organisation providing end-to-end Implementations, Integration, Migration, Optimisation, Maintenance & Support services, in 2010. Each of the management team members of AGS has over 20 years of experience in ERP.

What Cignex do

Open source is, by definition, available at no cost to any and all who want to deploy it. Open source platform providers and their associated communities develop, enhance, and, at times, support the core technology - eliminating exorbitant licensing fees and reducing the cost of customization and ongoing maintenance.

As a leading open source system integrator, CIGNEX takes a holistic view of your IT and business landscape. Cignex understand your business drivers, your IT needs and provide open source Enterprise solutions that help businesses in keeping IT costs down, thereby ensuring that the funds can be deployed to more critical business functions. By teaming with CIGNEX, our customers achieve the functionality and integration they are seeking, customized to their needs and at a lower cost, resulting in a dramatically improved ROI.

Cignex also provide SAP strategic and tactical consulting services. Cignex provide expert Functional and Technical teams to help our clients:
• Identify and select the right ERP tools
• Set-up the Project Management Office (PMO) to drive the ERP roll-out
• Implement, Integrate, Optimize, Upgrade and provide ongoing support services
• Provide Managed Services
As an SAP authorised services partner, Cignex have developed a focussed competency on SAP Upgrades, e-Sourcing and Spend Analytics.
As a part of our efforts to improve ROI for our clients, CIGNEX offers a best sourcing execution model. Based on the project needs, Cignex provide our clients options of Onsite, Near-site & Offshore locations for cost-effectively executing the projects. The offshore option has enabled CIGNEX to develop a continuous (and sizeable) pool of trained and experienced open source professionals. The team is constantly identifying and evaluating open source tools and products that meet the key criteria to be considered an Enterprise-class solution. Our clients benefit from this research, as CIGNEX recommends only those tools, products and frameworks that meet the project requirements of our Enterprise clients.
This knowledge has also been shared by our teams by authoring multiple white papers and 7 books on open source technologies that have benefited enterprises globally.

Cignex have also invested in developing solution frameworks, what Cignex term as Accelerators, to help clients jump-start the adoption process. Some of the Accelerators developed by CIGNEX include Contract Lifecycle Management, Migration Toolkit from Documentum to Alfresco.

SAP Jobs at Arteria Technologies: Career Opportunities



.noJob CodePositionExperienceLocation1ARTERIA_0003/ABAP/DEVSAP ABAP Developers1+Bangalore2ARTERIA_0003/ABAP/SDEVSAP ABAP Senior Developers2+Bangalore3ARTERIA_0004/ABAP/TLTeam Lead3+Bangalore4ARTERIA_0009/SAP WebDynpro, Portal & SIFbA experienceSAP WebDynpro, Portal & SIFbA Project Manager4+Bangalor

Capgemini SAP Opportunities


Technology Opportunities: "Jobs in ERP
3252 : SAP FICO Consultant
3253 : Consultant / Sr. Consultant - FICO - JVA
3300 : SAP IS Retail Forecasting & Replenishment
3530 : SAP HR Manager for Mumbai location
3629 : SAP Service & Delivery Management at Kolkata location"

Wipro needs SAP Consultants


Source: wipro.com

Job CodeJob TitleCountryCityArea of ExpertiseExperience Level

70440SAP CRM Technical Consultant-L1IndiaPuneCRM (Customer Relation Management)1-3 YEARS

76503Sr. Executive - FinanceIndiaBangaloreFinance / Accounts / Auditing1-3 YEARS

78705SAP HR Associate Consultant-L2IndiaBangaloreSAP1-3 YEARS

78957SAP FI Associate Consultant-L2IndiaKolkataSAP1-3 YEARS

79713Package Appl TeS SAPQTP Test Engr-L2IndiaHyderabadTesting Services1-3 YEARS

80258SAP ABAP Associate Consultant-L2IndiaBangaloreSAP1-3 YEARS

80487SAP ISI Associate Consultant-L2IndiaBangaloreSAP1-3 YEARS

80770SAP ABAP Associate Consultant-L2IndiaBangaloreSAP1-3 YEARS

81870SAP BI Developer-L3IndiaPuneSAP1-3 YEARS

82054Package Appl TeS SAPQC Test Engr-L2IndiaMumbaiSAP1-3 YEARS




Small vendors specialize to compete in BI


HANNOVER--Amid the BI (business intelligence) push from software giants, a smaller BI vendor says it is standing firm through specialization.

Speaking to ZDNet Asia at the company's CeBIT booth on Tuesday, LucaNet consultant Ramon Munoz Gonzalez said the company is targeting businesses through specialization in legal consolidation tools.

Gonzalez explained that the process of legal consolidation is a reporting audit function mandated by the German government, and companies need to perform this to comply with the law.

The 10-year-old company's intimate knowledge and focus on this area are its differentiation, he said, which has allowed it to target companies across industries.

Furthermore, smaller companies may be intimidated by the costs involved with some of the larger software vendors, such as SAP, he said.

LucaNet targets SMBs (small and midsize businesses), and makes its tools compatible with ERP (enterprise resource planning) systems and databases from some of the bigger boys--namely, Microsoft and SAP--to allow smaller companies to plug into existing systems, without embarking on larger implementations, said Gonzalez.

But the software giants, which offer the gamut of IT backend software, tout ease of integration across their portfolios.

In an interview with ZDNet Asia, SAP platforms solutions sales specialist, Oliver Hillermeier, said standalone BI vendors cannot guarantee tight integration with existing systems because these are out of their control.

Standalone BI implementations also have to start the data extraction process within customers' databases from scratch. On the other hand, a BI tool from an ERP vendor can provide the reporting and analysis as combined content through the front end, said Hillermeier.

SAP had 24 percent of the BI market last year with its Business Objects acquision, according to Gartner figures.

The company is also making BI more accessible to more workers through customized reports for different job functions, said the SAP executive.

"The openness and usability of our reports have been much improved than what we offered before, and that allows us to reach more workers," he said.

SAP, in previous interviews with ZDNet Asia, said BI adoption is providing aninroad for SAP into organizations.

In an interview last month, SAP also said BI will be the fastest-moving segment for the company in the Asia-Pacific region, with BI revenues contributing to half of the company's earnings in the region.

Fellow German software giant, Software AG, has also been on a push to make its products more accessible to users. In a press conference yesterday, its CEO expounded the company's direction to take its software to more office workers down the chain, through user-friendly dashboards and displays.

In an IBM poll last October, 87 percent of CIOs in Southeast Asia said BI and analytics were a top priroity for them, and saw the use of these tools as a crucial way to enhance competitive value for their organizations.

SAP bets on software for sustainability


What's an enterprise software company doing getting into sustainability? After all, the environmental footprint from software production pales in comparison to resource-intensive industries such as power generation or even running data centers that deliver Web services such as search.

SAP is trying to get ahead of the curve in environmental sustainability strictly for business reasons, according to Peter Graf, who last March was named chief sustainability officer at the Germany-based software heavyweight.

SAP's customers are businesses, which need to comply with regulations, such as reporting greenhouse gas emissions or tracking hazardous substances it may use.

But that's just the beginning. SAP is designing software to manage environmental and social aspects of a business, which can contribute to the bottom line or lower risk, argues Graf. For example, an obvious way to hedge against the volatile price of oil is to use less of it, he says. But that's just one of many natural resources--water, metals, food, energy--that companies can manage more intelligently.

That's where software comes in. Enterprise applications make their mark in business by automating processes such as managing a supply chain. Now, there are tools to manage the natural resources companies use. Last month, SAP released a hosted application called Sustainability Performance Management, a dashboard to track factors such as a company's carbon footprint or water use.


ZDNet Asia's sister site CNET spoke to Graf about SAP's internal push around sustainability and industry at large.

Q: A lot of companies don't have regulations that force them to lower their carbon footprint or make efficient use of natural resources. So what's the pitch to them for your software?
Graf: The pitch has been evolved through observation after about 100 customer interactions so far. I usually divide people into three categories. The first category are people who ignore the topic as long as they can. They consider having to move when there is a law or a supply chain partner [forces them]. By the way, SAP customers demand information from us so they can continue doing business with us. They want to be sure we have human rights policies, we have an environmental policy--specific requirements. The business case for these people is to comply at the lowest cost and risk.

That's about half the market today. The other part, which is about 45 percent, is who I call the opportunistic guys. They optimize their productivity in terms of resources such as energy, water--any natural resource--because there is price volatility which is dramatic in oil, water, food. That's happening because we are adding 2 billion people who all want their fair access and, since there is only so much that the planet can produce, prices are going up.

The other side of the opportunistic thinking is to think in terms of products. Anything from laundry detergent to electric cars, sustainably produced shoes, anything you can think of. The reason here is that consumers are becoming so much more aware and they are really driving this conversation. They demand accountability, they demand information, they demand that organizations are transparent. And there is a branding aspect to this, which helps attract employees.

The third group are the ones that go about this strategically--I always mention Nike, Coca-Cola, or Nestle. These companies have figured out that if you do not change the way you operate, you're putting your business model at risk. So for SAP, we think we need to change our software because we think it will be harder to sell software systems that don't have sustainability built in them in a comprehensive way. For Nestle, to make very high-quality food they need to have a working planet that's not polluted and there is a reliable supply of natural products. Coca-Cola is very aggressive around water and water protection--the vast majority of the water they use goes into watering sugar cane. Nike, which has a lot of outsourced manufacturing, can't afford to have any irregularities in terms of human rights, because it hurts their brand.

It seems like there's been a higher awareness among consumers about global warming over the past few years. But you're saying that that may not be the biggest motivator for a business to take environmental sustainability seriously.
Even if a business doesn't necessarily need to be concerned about global warming, [they need to be concerned with the environment]. In principle, a car doesn't need a working planet. Why would a company that produces cars look at [sustainability], apart from the branding issue and the ability to sell a product? Well, [consider] the resources you need to produce that car. Today we put copper cables--and copper prices have really gone through the roof--into the car. Then it comes back, it's crushed, it's melted. And now you have a lot lower-grade steel because there is copper "pollution" in it. The problem is that to retrieve that copper, which gets more and more scarce, the cost is so high.

There's something wrong in the cycle. If you want to produce cars in a hundred years that use copper, you're going to find a way to retrieve that copper. Otherwise we'll be in the landfills not far from today digging out natural resources. Right now, it's a linear chain: we extract stuff from the ground, we go and process it, we consume, and we dispose of it. That's the thing that's concerning people. It needs to be a cycle.

So what's the business case for managing natural resources?
Right now, it's all about mitigating risk from volatile prices.

So what sort of software have you developed to deal with this?
Carbon impact is an application that allows an organization to assess and act on information about energy and carbon--how much energy they use globally and what carbon impact comes from that.

That's one of the applications where SAP creates information--just like in an HR system you would have information about attrition, or a financial system would have margin and revenue information. So sustainability is about managing all of this, creating a view where you can look at the entire organization on aspects of social, environmental, and economic impact.

It's about setting targets, it's the monitoring targets, it's about benchmarking against others in the company--plant A versus plant B--and others in your industry, and finally reporting on this information.

Has SAP become more sustainable since you became chief sustainability officer? What have you changed in the process?
Graf: I would absolutely say so. There are a couple of areas. There's a change on the internal side of the house--in other words, what we do ourselves. And there's been a change on the enabler side of the house, which is what we do for our customers.

The most important thing is that we now have a mindset and targets and an understanding of sustainability that is managed and elevated to the strategic level. We used to be tactical in sustainability since 1996.

What's the difference between a strategic and tactical approach to environmental sustainability?
Tactical is defined as partnering to develop some point solutions, helping people comply with regulations--more the reactive stuff.

When sustainability is part of corporate strategy, you want to have visibility into the business at a level that is much higher than you need to just comply with regulations. You want an ability to manage a performance, report, and predict outcomes. You need to understand the operational elements, extract information, and give people insight and then take action.

I see that many times companies have sustainability going on in the marketing department but not in the operational divisions. As a sustainability officer, I work where value is at a software company, which is the creation of the software. That's really the shift that has happened. I think sustainability officers are best served in this sort of situation. So if you're in a consumer goods company, you should probably have responsibility for product management. If you work in chemicals, you should probably know how energy is used to run your plants.

Apotheker resigns as SAP's chief executive


The chief executive officer of SAP, Leo Apotheker, has resigned his post and from the company's board, after the board declined to extend his contract.

The resignation, which was reportedly by mutual decision, is effective immediately.

To replace the SAP's board has appointed co-CEOs: Bill McDermott, head of field organization, and Jim Hagemann Snabe, head of product development.

"The new setup of the SAP executive board will allow SAP to better align product innovation with customer needs," SAP Chairman Hasso Plattner said in a statement. "The new leadership team will continue to drive forward SAP's strategy and focus on profitable growth, and will deliver its innovations in 2010 to expand SAP's leadership of the business software market."

Stung by lower sales and earnings, SAP actually beat expectations in the final quarter of 2009. The company in January reported sales of 10.67 billion euros (US$14.9 billion), 8 percent lower than the 11.56 billion euros (US$15.82 billion) from 2008.

Despite the downturn, overall fourth-quarter sales and especially those from software-related services beat estimates from both the company and analysts. Operating margins for the full year also were better than expected. SAP attributed the improvement in part to cost cuts and layoffs it had announced earlier in the year.

Apotheker was appointed co-chief executive in 2008, serving with then-current CEO Henning Kagermann. He took over the role of CEO in 2009 after 19 years with the company.

Accenture's Country Manager Retires

Business process outsourcing (BPO) firm Accenture yesterday said its Philippine head, Beth G. Lui, has retired and was replaced by Manolito Tayag as country managing director and George Son Keng Po as head of the local Delivery Center Network (DCN) for Technology. “[Ms. Lui] has made an invaluable contribution to the company and leaves a legacy of excellence and leadership in Accenture over the last 31 years,” the firm said in a statement. Mr. Tayag will have “overall operational responsibility for the growth and sustainability of the business in the Philippines,” which has 15,000 workers. Mr. Tayag was a member of the board of directors of the Philippine Software Industry Association from 2006 to 2007. Mr. Son Keng Po, meanwhile, has been with Accenture for 23 years and “brings tremendous solutions delivery experience and leadership in application management, custom and package design and installation, data conversion, and software re-engineering in the resources and financial services sectors.” As head of the DCN for Technology he will be “responsible for the overall operations, delivery, and business results of the delivery center.” Benedict Hernandez remains as BPO operations chief.

"Core system" customization vs configuration

Increasingly, ERP vendors have tried to reduce the need for customization by providing built-in "configuration" tools to address most customers' needs for changing how the out-of-the-box core system works. Key differences between customization and configuration include:

  • Customization is always optional, whereas some degree of configuration (e.g., setting up cost/profit centre structures, organisational trees, purchase approval rules, etc.) may be needed before the software will work at all.
  • Configuration is available to all customers, whereas customization allows individual customer to implement proprietary "market-beating" processes.
  • Configuration changes tend to be recorded as entries in vendor-supplied data tables, whereas customization usually requires some element of programming and/or changes to table structures or views.
  • The effect of configuration changes on the performance of the system is relatively predictable and is largely the responsibility of the ERP vendor. The effect of customization is unpredictable and may require time-consuming stress testing by the implementation team.
  • Configuration changes are almost always guaranteed to survive upgrades to new software versions. Some customizations (e.g. code that uses pre-defined "hooks" that are called before/after displaying data screens) will survive upgrades, though they will still need to be re-tested. More extensive customizations (e.g. those involving changes to fundamental data structures) will be overwritten during upgrades and must be re-implemented manually.

By this analysis, customizing an ERP package can be unexpectedly expensive and complicated, and tends to delay delivery of the obvious benefits of an integrated system. Nevertheless, customizing an ERP suite gives the scope to implement secret recipes for excellence in specific areas while ensuring that industry best practices are achieved in less sensitive areas.

Extensions

In this context, "Extensions" refers to ways that an ERP environment can be "extended" (supplemented) with third-party programs. It is technically easy to expose most ERP transactions to outside programs that do other things, e.g.:

  • archiving, reporting and republishing (these are easiest to achieve, because they mainly address static data);
  • performing transactional data captures, e.g. using scanners, tills or RFIDs (also relatively easy because they touch existing data);

However, because ERP applications typically contain sophisticated rules that control how data can be created or changed, some such functions can be very difficult to implement.

Advantages

In the absence of an ERP system, a large manufacturer may find itself with many software applications that cannot communicate or interface effectively with one another. Tasks that need to interface with one another may involve:

  • ERP systems connect the necessary software in order for accurate forecasting to be done. This allows inventory levels to be kept at maximum efficiency and the company to be more profitable.
  • Integration among different functional areas to ensure proper communication, productivity and efficiency
  • Design engineering (how to best make the product)
  • Order tracking, from acceptance through fulfillment
  • The revenue cycle, from invoice through cash receipt
  • Managing inter-dependencies of complex processes bill of materials
  • Tracking the three-way match between purchase orders (what was ordered), inventory receipts (what arrived), and costing (what the vendor invoiced)
  • The accounting for all of these tasks: tracking the revenue, cost and profit at a granular level.

ERP Systems centralize the data in one place. Benefits of this include:

  • Eliminates the problem of synchronizing changes between multiple systems - consolidation of finance, marketing and sales, human resource, and manufacturing applications
  • Permits control of business processes that cross functional boundaries
  • Provides top-down view of the enterprise (no "islands of information"), real time information is available to management anywhere, anytime to make proper decisions.
  • Reduces the risk of loss of sensitive data by consolidating multiple permissions and security models into a single structure.
  • Shorten production leadtime and delivery time
  • Facilitating business learning, empowering, and building common visions

Some security features are included within an ERP system to protect against both outsider crime, such as industrial espionage, and insider crime, such as embezzlement. A data-tampering scenario, for example, might involve a disgruntled employee intentionally modifying prices to below-the-breakeven point in order to attempt to interfere with the company's profit or other sabotage. ERP systems typically provide functionality for implementing internal controls to prevent actions of this kind. ERP vendors are also moving toward better integration with other kinds of information security tools

Disadvantages

Problems with ERP systems are mainly due to inadequate investment in ongoing training for the involved IT personnel - including those implementing and testing changes - as well as a lack of corporate policy protecting the integrity of the data in the ERP systems and the ways in which it is used.

Disadvantages

  • Customizsation of the ERP software is limited...
  • Re-engineering of business processes to fit the "industry standard" prescribed by the ERP system may lead to a loss of competitive advantage.
  • ERP systems can be very expensive (This has led to a new category of "ERP light" solutions)
  • ERPs are often seen as too rigid and too difficult to adapt to the specific workflow and business process of some companies—this is cited as one of the main causes of their failure.
  • Many of the integrated links need high accuracy in other applications to work effectively. A company can achieve minimum standards, then over time "dirty data" will reduce the reliability of some applications.
  • Once a system is established, switching costs are very high for any one of the partners (reducing flexibility and strategic control at the corporate level).
  • The blurring of company boundaries can cause problems in accountability, lines of responsibility, and employee morale.
  • Resistance in sharing sensitive internal information between departments can reduce the effectiveness of the software.
  • Some large organizations may have multiple departments with separate, independent resources, missions, chains-of-command, etc, and consolidation into a single enterprise may yield limited benefits.

Implementation


Businesses have a wide scope of applications and processes throughout their functional units; producing ERP software systems that are typically complex and usually impose significant changes on staff work practices. Implementing ERP software is typically too complex for "in-house" skill, so it is desirable and highly advised to hire outside consultants who are professionally trained to implement these systems. This is typically the most cost effective way. There are three types of services that may be employed for - Consulting, Customization, Support. The length of time to implement an ERP system depends on the size of the business, the number of modules, the extent of customization, the scope of the change and the willingness of the customer to take ownership for the project. ERP systems are modular, so they don't all need be implemented at once. It can be divided into various stages, or phase-ins. The typical project is about 14 months and requires around 150 consultants. A small project (e.g., a company of less than 100 staff) can be planned and delivered within 3–9 months; however, a large, multi-site or multi-country implementation can take years. The length of the implementations is closely tied to the amount of customization desired.

To implement ERP systems, companies often seek the help of an ERP vendor or of third-party consulting companies. These firms typically provide three areas of professional services: consulting; customization; and support. The client organization can also employ independent program management, business analysis, change management, and UAT specialists to ensure their business requirements remain a priority during implementation.

Data migration is one of the most important activities in determining the success of an ERP implementation. Since many decisions must be made before migration, a significant amount of planning must occur. Unfortunately, data migration is the last activity before the production phase of an ERP implementation, and therefore receives minimal attention due to time constraints. The following are steps of a data migration strategy that can help with the success of an ERP implementation:

  1. Identifying the data to be migrated
  2. Determining the timing of data migration
  3. Generating the data templates
  4. Freezing the tools for data migration
  5. Deciding on migration related setups
  6. Deciding on data archiving

Process preparation

ERP vendors have designed their systems around standard business processes, based upon best business practices. Different vendor(s) have different types of processes but they are all of a standard, modular nature. Firms that want to implement ERP systems are consequently forced to adapt their organizations to standardized processes as opposed to adapting the ERP package to the existing processes. Neglecting to map current business processes prior to starting ERP implementation is a main reason for failure of ERP projects. It is therefore crucial that organizations perform a thorough business process analysis before selecting an ERP vendor and setting off on the implementation track. This analysis should map out all present operational processes, enabling selection of an ERP vendor whose standard modules are most closely aligned with the established organization. Redesign can then be implemented to achieve further process congruence. Research indicates that the risk of business process mismatch is decreased by:

  • linking each current organizational process to the organization's strategy;
  • analyzing the effectiveness of each process in light of its current related business capability;
  • understanding the automated solutions currently implemented.

ERP implementation is considerably more difficult (and politically charged) in organizations structured into nearly independent business units, each responsible for their own profit and loss, because they will each have different processes, business rules, data semantics, authorization hierarchies and decision centers. Solutions include requirements coordination negotiated by local change management professionals or, if this is not possible, federated implementation using loosely integrated instances (e.g. linked via Master Data Management) specifically configured and/or customized to meet local needs.

A disadvantage usually attributed to ERP is that business process redesign to fit the standardized ERP modules can lead to a loss of competitive advantage. While documented cases exist where this has indeed materialized, other cases show that following thorough process preparation ERP systems can actually increase sustainable competitive advantage.

Configuration

Configuring an ERP system is largely a matter of balancing the way you want the system to work with the way the system lets you work. Begin by deciding which modules to install, then adjust the system using configuration tables to achieve the best possible fit in working with your company’s processes.

Modules — Most systems are modular simply for the flexibility of implementing some functions but not others. Some common modules, such as finance and accounting are adopted by nearly all companies implementing enterprise systems; others however such as human resource management are not needed by some companies and therefore not adopted. A service company for example will not likely need a module for manufacturing. Other times companies will not adopt a module because they already have their own proprietary system they believe to be superior. Generally speaking the greater number of modules selected, the greater the integration benefits, but also the increase in costs, risks and changes involved.

Configuration Tables – A configuration table enables a company to tailor a particular aspect of the system to the way it chooses to do business. For example, an organization can select the type of inventory accounting – FIFO or LIFO – it will employ or whether it wants to recognize revenue by geographical unit, product line, or distribution channel.

So what happens when the options the system allows just aren't good enough? At this point a company has two choices, both of which are not ideal. It can re-write some of the enterprise system’s code, or it can continue to use an existing system and build interfaces between it and the new enterprise system. Both options will add time and cost to the implementation process. Additionally they can dilute the system’s integration benefits. The more customized the system becomes the less possible seamless communication between suppliers and customers.

Consulting services

Many organizations do not have sufficient internal skills to implement an ERP project. This results in many organizations offering consulting services for ERP implementation. Typically, a consulting team is responsible for the entire ERP implementation including:

  1. selecting
  2. planning
  3. training
  4. testing
  5. implementation
  6. delivery

of any customized modules. Examples of customization includes creating processes and reports for compliance, additional product training; creation of process triggers and workflow; specialist advice to improve how the ERP is used in the business; system optimization; and assistance writing reports, complex data extracts or implementing Business Intelligence

For most mid-sized companies, the cost of the implementation will range from around the list price of the ERP user licenses to up to twice this amount (depending on the level of customization required). Large companies, and especially those with multiple sites or countries, will often spend considerably more on the implementation than the cost of the user licenses—three to five times more is not uncommon for a multi-site implementation.

Unlike most single-purpose applications, ERP packages have historically included full source code and shipped with vendor-supported team IDEs for customizing and extending the delivered code. During the early years of ERP the guarantee of mature tools and support for extensive customization was an important sales argument when a potential customer was considering developing their own unique solution in-house, or assembling a cross-functional solution by integrating multiple "best of breed" applications.

Commercial applications


Manufacturing

Engineering, bills of material, scheduling, capacity, workflow management, quality control, cost management, manufacturing process, manufacturing projects, manufacturing flow

Supply chain management

Order to cash, inventory, order entry, purchasing, product configurator, supply chain planning, supplier scheduling, inspection of goods, claim processing, commission calculation

Financials

General ledger, cash management, accounts payable, accounts receivable, fixed assets

Project management

Costing, billing, time and expense, performance units, activity management

Human resources

Human resources, payroll, training, time and attendance, rostering, benefits

Customer relationship management

Sales and marketing, commissions, service, customer contact and call center support

Data services

Various "self-service" interfaces for customers, suppliers, and/or employees

Access control

Management of user privileges for various processes

History

The term "Enterprise resource planning" originally derived from manufacturing resource planning (MRP II) that followed material requirements planning (MRP). MRP evolved into ERP when "routings" became a major part of the software architecture and a company's capacity planning activity also became a part of the standard software activity. ERP systems typically handle the manufacturing, logistics, distribution, inventory, shipping, invoicing, and accounting for a company. ERP software can aid in the control of many business activities, including sales, marketing, delivery, billing, production, inventory management, quality management, and human resource management

ERP systems saw a large boost in sales in the 1990s as companies faced the Y2K problem in their legacy systems. Many companies took this opportunity to replace such information systems with ERP systems. This rapid growth in sales was followed by a slump in 1999, at which time most companies had already implemented their Y2K solution.

ERP systems are often incorrectly called back office systems indicating that customers and the general public are not directly involved. This is contrasted with front office systems like customer relationship management (CRM) systems that deal directly with the customers, or the eBusiness systems such as eCommerce, eGovernment, eTelecom, and eFinance, or supplier relationship management (SRM) systems

ERP systems are cross-functional and enterprise-wide. All functional departments that are involved in operations or production are integrated in one system. In addition to areas such as manufacturing, warehousing, logistics, and information technology, this typically includes accounting, human resources, marketing and strategic management.

ERP II, a term coined in the early 2000s, is often used to describe what would be the next generation of ERP software. This new generation of software is web-based and allows both employees and external resources (such as suppliers and customers) real-time access to the system's data.

EAS — Enterprise Application Suite is a new name for formerly developed ERP systems which include (almost) all segments of business using ordinary Internet browsers as thin client

Though traditionally ERP packages have been on-premise installations, ERP systems are now also available as Software as a Service.

Best practices are incorporated into most ERP vendor's software packages. When implementing an ERP system, organizations can choose between customizing the software or modifying their business processes to the "best practice" function delivered in the "out-of-the-box" version of the software.

Prior to ERP, software was developed to fit individual processes of an individual business. Due to the complexities of most ERP systems and the negative consequences of a failed ERP implementation, most vendors have included "Best Practices" into their software. These "Best Practices" are what the Vendor deems as the most efficient way to carry out a particular business process in an Integrated Enterprise-Wide system. A study conducted by Ludwigshafen University of Applied Science surveyed 192 companies and concluded that companies which implemented industry best practices decreased mission-critical project tasks such as configuration, documentation, testing and training. In addition, the use of best practices reduced over risk by 71% when compared to other software implementations.

The use of best practices can make complying with requirements such as IFRS, Sarbanes-Oxley, or Basel II easier. They can also help where the process is a commodity such as electronic funds transfer. This is because the procedure of capturing and reporting legislative or commodity content can be readily codified within the ERP software, and then replicated with confidence across multiple businesses who have the same business requirement.

Enterprise resource planning


Enterprise resource planning (ERP) is an integrated computer-based system used to manage internal and external resources including tangible assets, financial resources, materials, and human resources. It is a software architecture whose purpose is to facilitate the flow of information between all business functions inside the boundaries of the organization and manage the connections to outside stakeholders. Built on a centralized database and normally utilizing a common computing platform, ERP systems consolidate all business operations into a uniform and enterprise wide system environment.

An ERP system can either reside on a centralized server or be distributed across modular hardware and software units that provide "services" and communicate on a local area network. The distributed design allows a business to assemble modules from different vendors without the need for the placement of multiple copies of complex, expensive computer systems in areas which will not use their full capacity

Origin of the term

The initialism ERP was first employed by research and analysis firm Gartner Group in 1990 as an extension of MRP (Material Requirements Planning; later manufacturing resource planning) and CIM (Computer Integrated Manufacturing), and while not supplanting these terms, it has come to represent a larger whole. It came into use as makers of MRP software started to develop software applications beyond the manufacturing arena. ERP systems now attempt to cover all core functions of an enterprise, regardless of the organization's business or charter. These systems can now be found in non-manufacturing businesses, non-profit organizations and governments.

To be considered an ERP system, a software package should have the following traits:

  • Should be integrated and operate in real-time with no periodic batch updates.
  • All applications should access one database to prevent redundant data and multiple data definitions.
  • All modules should have the same look and feel.
  • Users should be able to access any information in the system without needed integration work on the part of the IS department.

Components

  • Transactional Backbone
    • Financials
    • Distribution
    • Human Resources
    • Product lifecycle management
  • Advanced Applications
    • Customer Relationship Management (CRM)
    • Supply chain management
      • Purchasing
      • Manufacturing
      • Distribution
    • Warehouse Management System
  • Management Portal/Dashboard
    • Decision Support System

These modules can exist in a system or utilized in an ad-hoc fashion.

Privacy and data security system


One of the primary functions of these tools is to collect information about clients, thus a company must consider the desire for privacy and data security, as well as the legislative and cultural norms. Some clients prefer assurances that their data will not be shared with third parties without their prior consent and that safeguards are in place to prevent illegal access by third parties.

Market structures

This market grew by 12.5 percent in 2008, from revenue of $8.13 billion in 2007 to $9.15 billion in 2008. The following table lists the top vendors in 2006-2008 (figures in millions of US dollars) published in Gartner studies.

Vendor

2008 Revenue

2008 Share (%)

2007 Revenue

2007 Share (%)

2006 Revenue

2006 Share (%)

SAP

2,055

22.5

2,050.8

25.3

1,681.7

26.6

Oracle

1,475

16.1

1,319.8

16.3

1,016.8

15.5

Salesforce.com

965

10.6

676.5

8.3

451.7

6.9

Microsoft

581

6.4

332.1

4.1

176.1

2.7

Amdocs

451

4.9

421.0

5.2

365.9

5.6

Others

3,620

39.6

3,289.1

40.6

2,881.6

43.7

Total

9,147

100

8,089.3

100

6,573.8

100

Implementation


Implementation Issues

Dramatic increases in revenue, higher rates of client satisfaction, and significant savings in operating costs are some of the benefits to an enterprise. Proponents emphasize that technology should be implemented only in the context of careful strategic and operational planning. Implementations almost invariably fall short when one or more facets of this prescription are ignored:

  • Poor planning: Initiatives can easily fail when efforts are limited to choosing and deploying software, without an accompanying rationale, context, and support for the workforce. In other instances, enterprises simply automate flawed client-facing processes rather than redesign them according to best practices.
  • Poor integration: For many companies, integrations are piecemeal initiatives that address a glaring need: improving a particular client-facing process or two or automating a favored sales or client support channel. Such “point solutions” offer little or no integration or alignment with a company’s overall strategy. They offer a less than complete client view and often lead to unsatisfactory user experiences.
  • Toward a solution: overcoming siloed thinking. Experts advise organizations to recognize the immense value of integrating their client-facing operations. In this view, internally-focused, department-centric views should be discarded in favor of reorienting processes toward information-sharing across marketing, sales, and service. For example, sales representatives need to know about current issues and relevant marketing promotions before attempting to cross-sell to a specific client. Marketing staff should be able to leverage client information from sales and service to better target campaigns and offers. And support agents require quick and complete access to a client’s sales and service history.

Adoption Issues

Historically, the landscape is littered with instances of low adoption rates. In 2003, a Gartner report estimated that more than $1 billion had been spent on software that wasn’t being used. More recent research indicates that the problem, while perhaps less severe, is a long way from being solved. According to CSO Insights, less than 40 percent of 1,275 participating companies had end-user adoption rates above 90 percent.

In a 2007 survey from the U.K., four-fifths of senior executives reported that their biggest challenge is getting their staff to use the systems they’d installed. Further, 43 percent of respondents said they use less than half the functionality of their existing system; 72 percent indicated they’d trade functionality for ease of use; 51 percent cited data synchronization as a major issue; and 67 percent said that finding time to evaluate systems was a major problem. With expenditures expected to exceed $11 billion in 2010, enterprises need to address and overcome persistent adoption challenges. Specialists offer these recommendations for boosting adoptions rates and coaxing users to blend these tools into their daily workflow:

  • Choose a system that’s easy to use: All solutions are not created equal. Some vendors offer more user-friendly applications than others, and simplicity should be as important a decision factor as functionality.
  • Choose the right capabilities: Employees need to know that time invested in learning and usage will yield personal advantages. If not, they will work around or ignore the system.
  • Provide training: Changing the way people work is no small task, and help is usually a requirement. Even with today’s more usable systems, many staffers still need assistance with learning and adoption.

Social Media


Social media sites like Twitter and Facebook are greatly amplifying the voice of people in the marketplace and are predicted to have profound and far-reaching effects on the ways companies manage their clients. This is because people are using these social media sites to share opinions and experiences on companies, products, and services. As social media isn’t moderated or censored, individuals can say anything they want about a company or brand, whether pro or con.

Increasingly, companies are looking to gain access to these conversations and take part in the dialogue. More than a few systems are now integrating to social networking sites. Social media promoters cite a number of business advantages, such as using online communities as a source of high-quality leads and a vehicle for crowd sourcing solutions to client-support problems. Companies can also leverage client stated habits and preferences to personalize and even “hyper-target” their sales and marketing communications.

Some analysts take the view that business-to-business marketers should proceed cautiously when weaving social media into their business processes. These observers recommend careful market research to determine if and where the phenomenon can provide measurable benefits for client interactions, sales, and support.

Non-profit and Membership-based

Systems for non-profit and membership-based organizations help track constituents and their involvement in the organization. Capabilities typically include tracking the following: fund-raising, demographics, membership levels, membership directories, volunteering and communications with individuals.

Many include tools for identifying potential donors based on previous donations and participation. In light of the growth of social networking tools, there may be some overlap between social/community driven tools and non-profit/membership tools.

Strategy

Choosing and implementing a system is a major undertaking. For enterprises of any appreciable size, a complete and detailed plan is required to obtain the funding, resources, and company-wide support that can make the initiative successful. Benefits must be defined, risks assessed, and cost quantified in three general areas:

  • Processes: Though these systems have many technological components, business processes lie at its core. It can be seen as a more client-centric way of doing business, enabled by technology that consolidates and intelligently distributes pertinent information about clients, sales, marketing effectiveness, responsiveness, and market trends. Therefore, before choosing a technology platform, a company needs to analyze its business workflows and processes; some will likely need re-engineering to better serve the overall goal of winning and satisfying clients. Moreover, planners need to determine the types of client information that are most relevant, and how best to employ them.
  • People: For an initiative to be effective, an organization must convince its staff that change is good and that the new technology and workflows will benefit employees as well as clients. Senior executives need to be strong and visible advocates who can clearly state and support the case for change. Collaboration, teamwork, and two-way communication should be encouraged across hierarchical boundaries, especially with respect to process improvement.
  • Technology: In evaluating technology, key factors include alignment with the company’s business process strategy and goals; the ability to deliver the right data to the right employees; and sufficient ease of use that users won’t balk. Platform selection is best undertaken by a carefully chosen group of executives who understand the business processes to be automated as well as the various software issues. Depending upon the size of the company and the breadth of data, choosing an application can take anywhere from a few weeks to a year or more.

Types/variations


Sales force automation

The sales force automation (SFA) system provides an array of capabilities to streamline all phases of the sales process, minimizing the time that sales representatives need to spend on manual data entry and administration. This allows them to successfully pursue more clients in a shorter amount of time than would otherwise be possible. At the heart of SFA is a contact management system for tracking and recording every stage in the sales process for each prospective client, from initial contact to final disposition. Many SFA applications also include insights into opportunities, territories, sales forecasts and workflow automation, quote generation, and product knowledge. Newly-emerged priorities are modules for Web 2.0 e-commerce and pricing.

Marketing

Systems for marketing (also known as marketing automation) help the enterprise identify and target its best clients and generate qualified leads for the sales team. A key marketing capability is tracking and measuring multichannel campaigns, including email, search, social media, and direct mail. Metrics monitored include clicks, responses, leads, deals, and revenue. As marketing departments are increasingly obliged to demonstrate revenue impact, today’.

Customer Service and Support

Recognizing that service is an important differentiator, organizations are increasingly turning to technology platforms to help them improve their clients’ experience while aiming to increase efficiency and minimize costs. Even so, a 2009 study revealed that only 39% of corporate executives believe their employees have the right tools and authority to solve client problems.“. The core for these applications has been and still is comprehensive call center solutions, including such features as intelligent call routing, computer telephone integration (CTI), and escalation capabilities.

Analytics

Relevant analytics capabilities are often interwoven into applications for sales, marketing, and service. These features can be complemented and augmented with links to separate, purpose-built applications for analytics and business intelligence. Sales analytics let companies monitor and understand client actions and preferences, through sales forecasting, data quality, and dashboards that graphically display

Marketing applications generally come with predictive analytics to improve segmentation and targeting, and features for measuring the effectiveness of online, offline, and search marketing campaign Web analytics have evolved significantly from their starting point of merely tracking mouse clicks on Web sites. By evaluating “buy signals,” marketers can see which prospects are most likely to transact and also identify those who are bogged down in a sales process and need assistance Marketing and finance personnel also use analytics to assess the value of multi-faceted programs as a whole.

These types of analytics are increasing in popularity as companies demand greater visibility into the performance of call centers and other support channels, in order to correct problems before they affect satisfaction levels. Support-focused applications typically include dashboards similar to those for sales, plus capabilities to measure and analyze response times, service quality, agent performance, and the frequency of various issues.

Integrated/Collaborative

Departments within enterprises—especially large enterprises—tend to function in their own little worlds. Traditionally, inter-departmental interaction and collaboration have been infrequent and rivalries not uncommon. More recently, the development and adoption of the tools and services has fostered greater fluidity and cooperation among sales, service, and marketing. This finds expression in the concept of collaborative systems which uses technology to build bridges between departments.

For example, feedback from a technical support center can enlighten marketers about specific services and product features clients are asking for. Reps, in their turn, want to be able to pursue these opportunities without the time-wasting burden of re-entering records and contact data into a separate SFA system. Conversely, lack of integration can have negative consequences: system isn’t adopted and integrated among all departments, several sources might contact the same clients for an identical purpose. Owing to these factors, many of the top-rated and most popular products come as integrated suites.

Small Business

Basic client service can be accomplished by a contact manager system, an integrated solution that lets organizations and individuals efficiently track and record interactions, including emails, documents, jobs, faxes, scheduling, and more. This kind of solution is gaining traction with even very small businesses, thanks to the ease and time savings of handling client contact through a centralized application rather than several different pieces of software, each with its own data collection system. In contrast these tools usually focus on accounts rather than individual contacts. They also generally include opportunity insight for tracking sales pipelines plus added functionality for marketing and service. As with larger enterprises, small businesses are finding value in online solutions, especially for mobile and telecommuting workers.

SAP Business Suite


SAP Business Suite is a bundle of business applications that provide integration of information and processes, collaboration, industry-specific functionality, and scalability. SAP Business Suite is based on SAP's technology platform called NetWeaver.

Built on an open, service-oriented architecture (SOA) – and powered by the SAP NetWeaver technology platform, SAP Business Suite offers companies an opportunity to transform business processes efficiently and integrate business processes that enable them to compete more effectively in their industry.

Customer relationship management

Customer relationship management is a broadly recognized, widely-implemented strategy for managing and nurturing a company’s interactions with clients and sales prospects. It involves using technology to organize, automate, and synchronize business processes—principally sales activities, but also those for marketing, customer service, and technical support. The overall goals are to find, attract, and win new clients, nurture and retain those the company already has, entice former clients back into the fold, and reduce the costs of marketing and client service. Once simply a label for a category of software tools, today, it generally denotes a company-wide business strategy embracing all client-facing departments and even beyond. When an implementation is effective, people, processes, and technology work in synergy to increase profitability, and reduce operational costs.

Benefits

These tools have been shown to help companies attain these objectives:

  • Streamlined sales and marketing processes
  • Higher sales productivity
  • Added cross-selling and up-selling opportunities
  • Improved service, loyalty, and retention
  • Increased call center efficiency
  • Higher close rates
  • Better profiling and targeting
  • Reduced expenses
  • Increased market share
  • Higher overall profitability
  • Marginal costing

Related Trends

What trends are affecting CRM tools? Perhaps the most notable trend has been the growth of tools delivered via the Web, also known as cloud computing and software as a service (SaaS). In contrast with traditional on-premises software, cloud-computing applications are sold by subscription, accessed via a secure Internet connection, and displayed on a Web browser. Companies don’t incur the initial capital expense of purchasing software; nor must they buy and maintain IT hardware to run it on.

Challenges

Despite the benefits, many companies are still not fully leveraging these tools and services to align marketing, sales, and service to best serve the enterprise.

Tools and workflows can be complex to implement, especially for large enterprises. Previously these tools were generally limited to contact management: monitoring and recording interactions and communications. Software solutions then expanded to embrace deal tracking, territories, opportunities, and at the sales pipeline itself. Next came the advent of tools for other client-facing business functions, as described below. These technologies have been, and still are, offered as on-premises software that companies purchase and run on their own IT infrastructure.

Often, implementations are fragmented; isolated initiatives by individual departments to address their own needs. Systems that start disunited usually stay that way: siloed thinking and decision processes frequently lead to separate and incompatible systems, and dysfunctional processes.