An order is a complex business object. It is made up of an object for data that is entered once only for each order (order header or footer), various partial orders for each order, and various order positions for each partial order. An order position is an item receipt, an item issue, work, or an order operation or production equipment.
A product or process design process creates order-independent data, known as master data. The most important object classes are the item, work center, and production equipment. The bill-of-material position, operation, and production equipment position object represent links between objects of the specified classes, thus enabling products and processes to be represented. Single-level or multilevel bills of material or where-used lists can be derived from the bill-of-material positions. Operations can be combined to form routing sheets or work center where-used lists.
Extensions arising from the variant-oriented concept concerns knowledge-based techniques for representing conditional positions in the bill of material and routing sheet. Product families can thus be suitably represented in a data model.
Extensions arising from the processor-oriented concept concern processor-oriented production structures and lot-control objects, in particular.
Product life cycle management (PLM), or engineering data management (EDM), bring together aspects of organization and processes as well as technical aspects of networking of IT systems. People have to agree on common data and functional models for general EDM tasks. These include class list of characteristics, object classes, and functions for release and change management.
Course sections and their intended learning outcomes
Intended learning outcomes: Describe order data in sales, distribution, production, and procurement. Explain in detail master data for products and processes. Disclose extensions arising from the variant-oriented and the processor-oriented concepts. Produce an overview on the management of product and engineering data.
Intended learning outcomes: Present the data structure of customers and suppliers. Describe the general data structure of orders in sales and distribution, production, and procurement. Disclose the data structure of the order and partial order header as well as the order position.
Intended learning outcomes: Describe master data of products, product structure, components, and operations. Explain the data structure of item master, bill of material, and where-used list. Disclose the data structure of work center master data, the work center hierarchy, as well as for operation, routing sheet, production equipment, bill of production equipment, and bill of tools.
Intended learning outcomes: Produce an overview on expert systems and knowledge-based systems. Explain the implementation of production rules. Present a data model for parameterized representation of a product family.
Intended learning outcomes: Explain objects such as process, technology, and the processor-oriented production structure. Describe objects for lot control.
Intended learning outcomes: Produce an overview on product life cycle management and engineering data management (EDM). Explain the engineering database as part of an IT system. Describe the data and functional model for general EDM tasks. Present object classes and functions for release and engineering change control.