Enterprise Systems

Enterprise systems are the large, integrated software packages that run the core operations of an organization—its accounting, inventory, production, purchasing, sales, and increasingly its relationships with customers and suppliers.

12 frameworks, from 1955 to today · Information Systems · Business, Management & Finance

still a working view ended · each leads to its entry below

Overview

Enterprise systems are the large, integrated software packages that run the core operations of an organization—its accounting, inventory, production, purchasing, sales, and increasingly its relationships with customers and suppliers1. What distinguishes them from ordinary business software is integration: a single database and a shared set of rules, so that a sale entered in one place immediately updates inventory, triggers a purchase order, and posts to the ledger2. The field of enterprise systems, as information systems scholars study it, is the history of how these packages were built, sold, implemented, and reshaped by the organizations that adopted them—and of the recurring discovery that the hard part is never the software.

The stakes are practical and enormous. Enterprise systems are among the largest capital investments a firm makes in information technology, and their implementation projects routinely run over budget, disrupt operations, and fail outright. The field's central lesson, learned repeatedly since the 1960s, is that integration is as much an organizational and political achievement as a technical one.

From Inventory Control to Material Requirements Planning

The ancestor of the enterprise system was the manufacturing planning system of the 1960s3. Manufacturers needed to answer a deceptively simple question: given a production schedule for finished goods, what components and raw materials must be ordered, and when? The technique that answered it was Material Requirements Planning (MRP), formalized in the 1960s and popularized by Joseph Orlicky and Oliver Wight. MRP takes a master production schedule, a bill of materials (the recipe of parts for each product), and inventory records, and explodes them into time-phased requirements for each component. Its logic is arithmetic—gross requirements minus on-hand inventory plus safety stock, offset by lead times—but it was impossible to perform by hand at scale, so MRP was one of the first business applications that genuinely required a computer.

MRP's limitation was that it planned materials in isolation. It assumed capacity was available and ignored the financial consequences of the plan. In the 1970s, practitioners extended it into Manufacturing Resource Planning (MRP II), which added capacity planning, shop-floor scheduling, and—crucially—a feedback loop to finance, so that a production plan could be translated into cost and cash projections. Oliver Wight's "MRP II" label and his ABCD checklist for assessing how well a company used the system became widely taught standards. The ambition was now company-wide: one plan, one set of numbers, shared by manufacturing, purchasing, and finance.

The Socio-Technical Warning

Even as MRP spread, a parallel research tradition was documenting why such systems so often disappointed. The socio-technical systems approach, developed from the 1950s at the Tavistock Institute in London through studies of British coal mining and later manufacturing, held that a work system has two jointly optimized halves: the technical subsystem and the social subsystem. Change one without the other and performance suffers. Applied to MRP, the lesson was that a planning system imposed on an organization without redesigning roles, incentives, and work practices would be gamed or bypassed. This insight—that enterprise systems are organizational interventions, not merely software installations—became a founding premise of the field and shaped later research on implementation, user participation, and resistance.

Electronic Data Interchange and the Extended Enterprise

While manufacturers integrated internally, a different thread connected firms to each other. Electronic Data Interchange (EDI) is the computer-to-computer exchange of standardized business documents—purchase orders, invoices, shipping notices—between trading partners4. EDI standards emerged in the late 1960s and 1970s, notably the American ANSI X12 standard and the international EDIFACT standard developed under United Nations auspices in the 1980s. EDI worked: it removed manual re-keying and shortened order cycles. But it was expensive, ran over private value-added networks, and was dominated by large buyers who could compel suppliers to adopt it. EDI taught the field two durable lessons—that inter-organizational integration creates power asymmetries, and that standards are as much political settlements as technical ones—that carried directly into later supply chain systems.

Enterprise Resource Planning

The term Enterprise Resource Planning (ERP) was popularized in the early 1990s, most visibly by the Gartner Group, to describe software that integrated the whole enterprise rather than manufacturing alone. The decisive shift was architectural: instead of separate modules with interfaces, ERP packages ran on a single relational database with a common data model, so that every function read and wrote the same records. The leading products—SAP R/3, launched in 1992, and the offerings of Oracle, PeopleSoft, and J.D. Edwards—grew rapidly, and SAP in particular became the reference case of a German software firm conquering global corporate computing.

ERP's promise was a single version of the truth. Its cost was rigidity: the package encoded "best practices" that adopting firms were expected to accept, and customizing it was expensive and made upgrades painful. The recurring dilemma—adapt the software to the organization, or adapt the organization to the software—became the field's signature research question. Studies of ERP implementation in the 1990s and 2000s documented the "vanilla" strategy of minimal customization, the role of consultants and "key users," and the frequent gap between promised and realized benefits. The concept of the critical success factor—top management support, clear business case, user training, data quality—was codified largely through this literature.

Reengineering and Process Management

ERP arrived alongside a management fashion that gave it ideological cover. Business Process Reengineering (BPR), articulated most famously by Michael Hammer in a 1990 Harvard Business Review article and in Hammer and James Champy's 1993 book Reengineering the Corporation, argued that firms should stop automating existing processes and instead obliterate and redesign them around outcomes. "Don't automate, obliterate" was the slogan. ERP vendors and consultants sold packages as the vehicle for reengineered processes, since the software's built-in workflows implied a redesign whether the customer wanted one or not. BPR's excesses—mass layoffs justified in its name and a high failure rate—produced a backlash, and by the late 1990s the rhetoric softened into Business Process Management (BPM): a continuous, model-driven discipline of documenting, analyzing, and improving processes, supported by modeling notations such as BPMN and by workflow and process-aware information systems. BPM kept reengineering's focus on process while abandoning its revolutionary tone.

Extending Outward: CRM and Supply Chain Systems

With the core integrated, vendors pushed integration outward. Customer Relationship Management (CRM) systems, which consolidated sales force automation, marketing, and customer service onto a shared customer record, became a major category in the late 1990s, with Siebel as the dominant vendor before Salesforce's cloud model disrupted it from 1999. Supply Chain Management (SCM) systems extended planning across organizational boundaries—demand forecasting, supplier collaboration, and advanced planning and scheduling—building on MRP's logic but operating between firms. Both categories raised the same questions the field had already learned to ask: whose data is authoritative, who bears the cost of integration, and what happens when the system's model of the world diverges from the world.

Architecture, Services, and the Cloud

As ERP estates grew, firms faced the problem of many systems that still did not talk to each other. Enterprise architecture emerged as a discipline for describing an organization's business, information, application, and technology layers as a connected whole—the Zachman Framework, proposed by John Zachman in 1987, was an early and influential schema—so that integration could be planned rather than improvised. In the 2000s, service-oriented architecture (SOA) proposed that functionality be exposed as loosely coupled, reusable services that could be composed into processes, promising flexibility that monolithic ERP could not deliver. SOA's grander ambitions were partly absorbed into later web-services and microservices practice, and its sobering lesson—that governance, not technology, determines whether reuse happens—echoed the field's oldest findings.

The most recent structural shift is cloud ERP: enterprise systems delivered as subscription services rather than installed on-premises2. Workday, founded in 2005, built human capital and financial management natively for the cloud; SAP's S/4HANA and Oracle's Fusion applications followed. Cloud delivery changed the economics and the upgrade problem—vendors now push updates continuously—but it did not dissolve the organizational questions. Configuration, data migration, process fit, and change management remain the work, and the field's research agenda has shifted toward platform ecosystems, algorithmic management, and the governance of continuously changing systems.

Where the Field Stands

Today enterprise systems research and practice converge on a few durable positions. Integration is a socio-technical achievement, not a product feature. Implementation success depends on organizational readiness, executive sponsorship, and the negotiated fit between package and process. The boundary between the enterprise and its partners is now a design space—cloud, APIs, and platform ecosystems—rather than a fixed wall. Open questions remain: how firms govern continuous cloud updates they do not control; how intelligent automation and embedded analytics change the division of labor between system and worker; and whether the next generation of integrated platforms will finally deliver the flexibility that four decades of architecture movements have promised.

References

  1. Enterprise software (Definitions and industry, Enterprise systems), Wikipedia
  2. Enterprise resource planning, Wikipedia
  3. Manufacturing resource planning (History and evolution), Wikipedia
  4. Electronic data interchange, Wikipedia

The frameworks of Enterprise Systems

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1955-Present

    Sociotechnical system

    How should technical and social systems be jointly designed?

    Fly to its tower in Nousfarer

  2. 1965-1985

    Material Requirements Planning

    What components and materials must be ordered, and when?

    Fly to its tower in Nousfarer

  3. 1970-2000

    Electronic Data Interchange

    How can trading partners exchange business documents by computer?

    Fly to its tower in Nousfarer

  4. 1975-1995

    Manufacturing Resource Planning

    How can a production plan be translated into cost and cash?

    Fly to its tower in Nousfarer

  5. 1987-Present

    Enterprise architecture

    How can an organization's systems be described as a connected whole?

    Fly to its tower in Nousfarer

  6. 1990-1998

    Business process re-engineering

    Should firms automate existing processes or redesign them from scratch?

    Fly to its tower in Nousfarer

  7. 1992-Present

    Enterprise Resource Planning

    How can one database give every function a single version of the truth?

    Fly to its tower in Nousfarer

  8. 1995-Present

    Customer relationship management

    How can a firm consolidate all customer interactions onto one record?

    Fly to its tower in Nousfarer

  9. 1995-Present

    Supply chain management

    How can planning extend across organizational boundaries between firms?

    Fly to its tower in Nousfarer

  10. 1998-Present

    Business Process Management

    How can processes be continuously documented, analyzed, and improved?

    Fly to its tower in Nousfarer

  11. 2000-2015

    Service-oriented architecture

    How can functionality be exposed as reusable services composed into processes?

    Fly to its tower in Nousfarer

  12. 2005-Present

    Cloud ERP

    How can enterprise systems be delivered as subscription services?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Sociotechnical systemMaterial Requirements PlanningElectronic Data InterchangeManufacturing Resource PlanningEnterprise architectureBusiness process re-engineeringEnterprise Resource PlanningCustomer relationship managementSupply chain managementBusiness Process ManagementService-oriented architectureCloud ERP

Beyond the field

Where Enterprise Systems's ideas came from in other fields, and what they led to there: the strongest 12 of 74 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Enterprise Systems is a planet in Nousfarer

Its city has a tower for each of these 12 frameworks. Land, walk in, and climb one concept at a time.

Land on Enterprise Systems

Related fields

Fields its ideas are linked to

More in Information Systems

See where Enterprise Systems sits on the Map of Human Knowledge