Computation and cognition: toward a foundation for cognitive science
Computation and cognition: toward a foundation for cognitive science
Application prototyping: a requirements definition strategy for the 80s
Application prototyping: a requirements definition strategy for the 80s
Defining managerial problems: a framework for prescriptive theorizing
Management Science
The illusion of ‘best practice’ in information systems for operations management
European Journal of Information Systems
Material Requirements Planning: The New Way of Life in Production and Inventory Management
Material Requirements Planning: The New Way of Life in Production and Inventory Management
Production Control: A Structural and Design Oriented Approach
Production Control: A Structural and Design Oriented Approach
The critical success factors for ERP implementation: an organizational fit perspective
Information and Management
Improving information requirements determination: a cognitive perspective
Information and Management
Fuzzy modeling Enterprise Resource Planning tool selection
Computer Standards & Interfaces
Computers and Industrial Engineering
Hi-index | 0.00 |
Whereas much of the modeling literature in supply chain planning addresses the analysis of decision models and presents solution techniques and much of the empirical literature on planning systems such as ERP and APS software addresses implementation challenges from an organizational perspective, research on the modeling process of capturing the planning process in planning software is very scarce. In this paper, we examine this modeling process. Our approach is based on a normative method for hierarchical planning and presents a case study where this modeling process was used. We analyze the process, relate it to the literature on modeling, and demonstrate the value of the theory in explaining major observations. We conclude that the hierarchical premise on which most planning processes are based is very difficult to capture in an advanced planning system, and find that users and organizations essentially circumvent this problem by creating their own workflows, independent of the system's prescribed one.