- Atlas
- Business, Management & Finance
- Enterprise Systems
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
- Sociotechnical system 1955-Present
- Material Requirements Planning 1965-1985
- Electronic Data Interchange 1970-2000
- Manufacturing Resource Planning 1975-1995
- Enterprise architecture 1987-Present
- Business process re-engineering 1990-1998
- Enterprise Resource Planning 1992-Present
- Customer relationship management 1995-Present
- Supply chain management 1995-Present
- Business Process Management 1998-Present
- Service-oriented architecture 2000-2015
- Cloud ERP 2005-Present
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
- Enterprise software (Definitions and industry, Enterprise systems), Wikipedia
- Enterprise resource planning, Wikipedia
- Manufacturing resource planning (History and evolution), Wikipedia
- 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.
- 1955-Present
Sociotechnical system
How should technical and social systems be jointly designed?
- 1965-1985
Material Requirements Planning
What components and materials must be ordered, and when?
- 1970-2000
Electronic Data Interchange
How can trading partners exchange business documents by computer?
- 1975-1995
Manufacturing Resource Planning
How can a production plan be translated into cost and cash?
- 1987-Present
Enterprise architecture
How can an organization's systems be described as a connected whole?
- 1990-1998
Business process re-engineering
Should firms automate existing processes or redesign them from scratch?
- 1992-Present
Enterprise Resource Planning
How can one database give every function a single version of the truth?
- 1995-Present
Customer relationship management
How can a firm consolidate all customer interactions onto one record?
- 1995-Present
Supply chain management
How can planning extend across organizational boundaries between firms?
- 1998-Present
Business Process Management
How can processes be continuously documented, analyzed, and improved?
- 2000-2015
Service-oriented architecture
How can functionality be exposed as reusable services composed into processes?
- 2005-Present
Cloud ERP
How can enterprise systems be delivered as subscription services?
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.
Manufacturing Resource Planning grew out of Material Requirements Planning
MRP II extended MRP's material planning with capacity planning, shop-floor scheduling, and a financial feedback loop, so a production plan could be translated into cost and cash projections. Oliver Wight's MRP II label and ABCD checklist codified the extension.
Carried by Oliver Wight.
Enterprise Resource Planning grew out of Material Requirements Planning
ERP grew out of MRP/MRP II manufacturing planning logic, generalizing the single-plan, single-set-of-numbers ambition from manufacturing to the whole enterprise on a shared database. The MRP explosion arithmetic and master-schedule concepts carried into ERP production modules.
Carried by SAP R/3 (1992).
Enterprise Resource Planning grew out of Manufacturing Resource Planning
ERP generalized MRP II's company-wide integration of manufacturing, purchasing, and finance into a single relational database covering all enterprise functions. The MRP II ambition of one plan and one set of numbers became ERP's core promise.
Carried by SAP R/3 (1992).
Business Process Management replaced Business process re-engineering
BPM replaced BPR's revolutionary rhetoric with a continuous, model-driven discipline of documenting, analyzing, and improving processes, keeping reengineering's focus on process while abandoning its obliterate-and-redesign tone. BPMN and workflow systems carried the process focus forward.
Carried by BPMN.
Cloud ERP grew out of Enterprise Resource Planning
Cloud ERP is ERP delivered as a subscription service rather than installed on-premises, carrying the same integrated single-database logic into a new delivery model. Salesforce's cloud model from 1999 disrupted the on-premises vendor landscape.
Carried by Salesforce.
Supply chain management influenced by Material Requirements Planning
SCM systems built on MRP's planning logic—demand forecasting, time-phased requirements, advanced planning and scheduling—but operated between firms rather than within one.
Supply chain management influenced by Electronic Data Interchange
EDI taught the field that inter-organizational integration creates power asymmetries and that standards are political settlements, lessons that carried directly into supply chain management systems extending planning across organizational boundaries.
Carried by ANSI X12; EDIFACT.
Service-oriented architecture influenced by Enterprise architecture
Enterprise architecture's layered description of business, information, application, and technology provided the planning vocabulary from which SOA proposed exposing functionality as loosely coupled, reusable services composed into processes.
Enterprise Resource Planning influenced by Business process re-engineering
BPR gave ERP ideological cover: vendors and consultants sold packages as vehicles for reengineered processes, since the software's built-in workflows implied a redesign. Hammer and Champy's reengineering argument shaped how ERP implementations were justified.
Carried by Michael Hammer; Reengineering the Corporation (1993).
Service-oriented architecture reacted against Enterprise Resource Planning
SOA arose as a response to monolithic ERP's rigidity, proposing loosely coupled, reusable services that could be composed into processes to deliver flexibility that integrated packages could not. Its governance lesson echoed ERP's oldest findings.
Cloud ERP influenced by Service-oriented architecture
SOA's service-oriented, loosely coupled delivery model was partly absorbed into later web-services and microservices practice, which shaped how cloud ERP vendors architected subscription-delivered enterprise systems.
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.
Material Requirements Planning led to Enterprise Resource Planning in Operations
Material Requirements Planning is the direct ancestor of ERP: MRP's bill-of-materials explosion and time-phased order logic became the manufacturing core of ERP systems. ERP extended MRP first to MRP II and then to enterprise scope.
Carried by Joseph Orlicky; Material Requirements Planning (1975).
Electronic Data Interchange led to E-Procurement in Procurement
E-procurement grew directly out of electronic data interchange: EDI's standards for purchase orders and invoices were the first electronic purchasing, and web-based e-procurement generalised that exchange to many suppliers. The later practice is a refinement and broadening of EDI-based purchasing.
Manufacturing Resource Planning grew out of Material Requirements Planning in Production Systems
MRP II derives directly from MRP, keeping the bill-of-material explosion at its core while adding capacity and cost planning.
Carried by Oliver Wight.
Manufacturing Resource Planning grew out of Material requirements planning in Supply Chain Engineering
MRP II was built as a refinement of MRP's time-phased material planning, broadening it to enterprise-wide resource planning.
Carried by Oliver Wight.
Manufacturing Resource Planning grew out of Material requirements planning in Industrial Engineering
MRP II grew directly out of material requirements planning, extending the material plan to capacity, shop-floor and financial planning in a closed loop.
Carried by Oliver Wight.
Manufacturing Resource Planning grew out of Material Requirements Planning in Production Planning And Control
Manufacturing resource planning is a direct extension of MRP, adding capacity and financial modules around the original material plan.
Carried by Oliver Wight.
Manufacturing Resource Planning led to Enterprise Resource Planning in Production Planning And Control
ERP grew directly out of MRP II, extending its manufacturing planning modules to finance, human resources and distribution across the whole enterprise; the major ERP vendors were former MRP II suppliers.
Manufacturing Resource Planning led to Enterprise Resource Planning in Operations
ERP grew directly out of Manufacturing Resource Planning (MRP II), extending its integrated planning logic from manufacturing to finance, HR and the whole enterprise. The MRP II modules and master-scheduling concepts carried over into ERP packages.
Carried by Oliver Wight.
Enterprise architecture led to Agile and lean enterprise architecture in Enterprise Architecture
Agile and lean enterprise architecture grew out of enterprise architecture as a reaction against its heavy, plan-driven methods, recasting it in iterative and lean terms. It is a branch of the enterprise architecture discipline.
Enterprise architecture led to Enterprise Architecture Modeling Languages in Enterprise Architecture
Enterprise architecture modeling languages were developed as the notation layer of the enterprise architecture discipline, giving its artifacts formal representation. They are a direct branch of enterprise architecture practice.
Enterprise architecture led to TOGAF Architecture Development Method in Enterprise Architecture
TOGAF's ADM was built as a method for developing enterprise architectures, growing out of the enterprise architecture practice that emerged in the late 1980s. The ADM codified the phases of producing an enterprise architecture, so it is a direct refinement of the earlier discipline.
Carried by The Open Group; TOGAF (1995).
Enterprise architecture led to ArchiMate in Enterprise Architecture
ArchiMate was created as a modeling language specifically for enterprise architecture, developed within the enterprise architecture community to give it a formal notation. It is a direct outgrowth of the enterprise architecture discipline.

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 SystemsRelated fields
Fields its ideas are linked to
- Enterprise Architecture 13 links
- Production Planning And Control 10 links
- Operations 6 links
- Cloud Computing 5 links
- Supply Chain Engineering 4 links
- Industrial Engineering 3 links
- Systems Analysis And Design 3 links
- Procurement 3 links
- Process Systems Engineering 2 links
- Information Systems 2 links
- Retailing 2 links
- Sales Management 2 links
More in Information Systems
- Business Analytics
- Decision Support Systems
- Digital Strategy
- Electronic Commerce
- Enterprise Architecture
- Information Systems
- It Governance
- Platform Strategy
- Sociotechnical Systems
- Systems Analysis And Design
See where Enterprise Systems sits on the Map of Human Knowledge