Glanz: aiMOOC über GPT aiMOOC Action erstellt

2026-08-09T14:35:50Z

aiMOOC über GPT aiMOOC Action erstellt

Neue Seite

{{T}}
[[Category:English]]
[[Category:Operations Management]]

{{BR}}
= Introduction =

'''Operations management''' is the discipline of designing, running, controlling, and improving the processes that create goods and services. It connects organizational strategy with the everyday decisions that determine how people, equipment, information, materials, technology, and suppliers are coordinated. You encounter operations management in factories, hospitals, banks, airlines, universities, software services, restaurants, logistics networks, public agencies, and many other settings.

A useful starting point is the '''transformation model''': inputs such as labor, materials, information, capital, energy, and customer participation enter a process; activities transform those inputs; outputs emerge as goods, services, information, experiences, or combinations of these. Operations managers try to make this transformation effective and efficient while meeting requirements for quality, speed, dependability, flexibility, cost, safety, and sustainability.

[[File:Machine prepares materials for processing at a manufacturing facility.jpg|500px|frameless|center]]

Operations management is not limited to the factory floor. In a hospital, the operation includes patient flow, staffing, diagnostic capacity, bed availability, supplies, and clinical processes. In an online platform, it includes computing capacity, service reliability, response times, incident management, and the design of digital workflows. The same analytical ideas can therefore be transferred between sectors, although the operational details differ.

At university level, you should learn to combine '''quantitative models''' with '''managerial judgment'''. A model may help you estimate capacity, inventory, waiting time, or project duration, but the decision still depends on assumptions, risk, incentives, human behavior, ethics, and strategic priorities.

{{BR}}
= Operations Strategy and Performance =

Operations strategy explains how the operating system supports the wider goals of an organization. A low-cost strategy may require high utilization, standardized work, scale economies, and disciplined process control. A differentiation strategy may require flexibility, rapid innovation, customization, premium service, or exceptional reliability. Operations choices should therefore reinforce the value proposition rather than optimize isolated measures.

Common performance objectives include '''quality''', '''speed''', '''dependability''', '''flexibility''', and '''cost'''. Sustainability, resilience, safety, and employee well-being are also important operational concerns. These objectives can reinforce each other, but they can also create trade-offs. Excess capacity may increase cost while improving responsiveness. Large production batches may reduce setup frequency while increasing inventory and lead time. Very high utilization may look efficient while creating congestion and long waits.

Useful performance measures include throughput, cycle time, lead time, work in process, capacity utilization, defect rate, service level, on-time delivery, inventory turnover, overall equipment effectiveness, and cost per unit. A strong measurement system connects local metrics to customer value and strategic outcomes.

[[File:Product Lifecycle Management.svg|500px|frameless|center]]

When evaluating an operations decision, ask four questions: What customer or stakeholder need is being served? What process capability is required? What resources and constraints shape the decision? What unintended consequences could appear elsewhere in the system?

{{BR}}
== The Process View ==

A '''process''' is a structured sequence of activities that transforms inputs into outputs. Processes can be mapped at different levels, from an end-to-end order-to-delivery flow down to the individual steps of a workstation or service encounter. Mapping makes handoffs, delays, rework loops, decision points, and information flows visible.

Three basic flow concepts are especially important. '''Throughput''' is the rate at which a process produces completed units. '''Work in process''' is the number of units currently inside the process. '''Flow time''' is the average time a unit spends in the process. Under stable long-run conditions, Little's Law links them: work in process equals throughput multiplied by flow time.

This relationship is powerful because it applies to many systems. If a call center has an average of 24 customers in the system and completes 12 customers per hour, the average flow time is about two hours. If managers want shorter flow times without reducing throughput, they must reduce work in process or redesign the process.

{{BR}}
= Process Design and Analysis =

Process design determines how work is organized. High-volume, low-variety processes often use standardized flows, while low-volume, high-variety work usually requires more flexible resources and skills. Service processes may also involve customer contact, simultaneity of production and consumption, and demand that cannot be stored as finished inventory.

A '''bottleneck''' is the resource or stage that limits overall process capacity. Improving a non-bottleneck may increase local efficiency without increasing system output. Bottleneck analysis therefore starts with the capacity of each step, the required workload, and the way variability affects flow.

Process analysis commonly examines:
# [[Process Mapping|Process mapping]]: Represent activities, decisions, handoffs, delays, and information flows.
# [[Capacity Planning|Capacity planning]]: Compare available capacity with expected demand and identify constraints.
# [[Bottleneck|Bottleneck management]]: Protect and improve the resource that limits throughput.
# [[Queueing Theory|Queueing analysis]]: Study waiting created by demand and service variability.
# [[Standard Work|Standard work]]: Define a repeatable method while retaining a basis for improvement.

A key distinction is between '''cycle time''' and '''lead time'''. Cycle time often describes the time between completed units or the processing time of an activity, while lead time describes the elapsed time from a request or order until completion. In many operations, waiting accounts for far more of lead time than active processing.

{{BR}}
== Value Stream Mapping ==

Value-stream mapping extends process mapping by representing both material and information flows and by separating value-creating time from delays and other non-value-creating activity. A current-state map helps you see how the system actually behaves; a future-state map describes a more desirable flow and guides improvement work.

[[File:ValueStreamMapParts.png|500px|frameless|center]]

{{#ev:youtube|https://www.youtube.com/watch?v=O--ZVqQvaA8|500|center}}

When you analyze a value stream, avoid assuming that every non-processing activity is useless. Some activities are required by regulation, safety, risk control, or technical necessity even if the customer would not independently pay for them. The objective is to understand why each activity exists and whether it can be eliminated, simplified, combined, automated, or redesigned.

{{BR}}
= Forecasting and Capacity Planning =

Operations decisions depend on expectations about future demand. Forecasting methods range from expert judgment and market research to moving averages, exponential smoothing, regression, and more advanced predictive models. No forecasting method eliminates uncertainty, so managers should evaluate both the expected forecast and the distribution of plausible outcomes.

Forecast accuracy can be evaluated with measures such as mean absolute deviation, mean squared error, root mean squared error, and mean absolute percentage error. The choice of metric matters because different measures penalize errors differently. Forecasts should also be checked for bias, because a model that repeatedly overestimates or underestimates demand can systematically distort staffing, purchasing, and capacity decisions.

'''Capacity''' is the maximum sustainable output of a resource, process, facility, or network under specified conditions. Design capacity is an idealized maximum, while effective capacity reflects realistic operating conditions such as maintenance, setups, product mix, staffing rules, and planned downtime. A '''capacity cushion''' is deliberate spare capacity used to absorb demand peaks or uncertainty.

Capacity choices are often difficult to reverse. Adding a factory, warehouse, aircraft, data center, or hospital wing may require significant capital and long lead times. Managers therefore compare strategies such as leading demand with early capacity additions, lagging demand until utilization rises, or matching demand with smaller increments.

{{BR}}
= Inventory and Materials Planning =

Inventory exists because supply and demand are rarely perfectly synchronized. Common forms include raw materials, work in process, finished goods, maintenance supplies, spare parts, and pipeline inventory moving between locations. Inventory can protect service levels and stabilize operations, but it also ties up capital, consumes space, risks obsolescence, and can hide process problems.

Important inventory cost categories are '''ordering or setup cost''', '''holding cost''', '''shortage or stockout cost''', and the acquisition cost of the item. The economic order quantity model balances ordering and holding costs under restrictive assumptions such as relatively stable demand and lead time. In its basic form, EOQ = √(2DS/H), where D is annual demand, S is the cost per order, and H is annual holding cost per unit.

[[File:Gati Warehouse.png|500px|frameless|center]]

A '''reorder point''' determines when replenishment should be triggered. In a deterministic setting, it equals expected demand during lead time. Under uncertainty, managers often add '''safety stock''' to reduce the probability of a stockout. Higher service targets generally require more safety stock, so service and inventory investment must be balanced.

'''ABC analysis''' segments inventory by managerial importance, often using annual consumption value as a starting point. A-items receive close attention, while B- and C-items can use progressively simpler controls. The classification should not be purely financial: a low-cost component can still be operationally critical.

{{BR}}
== Materials Requirements Planning ==

Materials requirements planning, or MRP, supports dependent-demand items whose requirements are derived from a production plan. Core inputs include a master production schedule, bills of materials, inventory records, planned lead times, and lot-sizing rules. MRP time-phases component requirements so that materials arrive when needed for planned production.

[[File:MRP2.jpg|500px|frameless|center]]

MRP is powerful but sensitive to data quality. Inaccurate bills of materials, inventory records, lead times, or schedules can generate unrealistic planned orders. Later planning architectures extended MRP toward manufacturing resource planning and enterprise resource planning, integrating more functions and data.

{{BR}}
= Quality Management and Process Improvement =

Quality means consistently meeting relevant requirements and creating value for customers and stakeholders. In operations, quality is built through process design, capable equipment, trained people, reliable suppliers, clear specifications, mistake prevention, measurement, and systematic improvement. Final inspection alone cannot create quality after defects have already been produced.

'''Statistical process control''' uses data over time to distinguish routine process variation from signals that may indicate a meaningful change. A control chart typically includes a center line and statistically derived control limits. A point outside the limits or a non-random pattern can indicate a special cause that should be investigated. Control limits are not the same as engineering specification limits: one describes observed process behavior, while the other describes what is acceptable to the customer or design.

[[File:Anatomy of a control chart.png|500px|frameless|center]]

{{#ev:youtube|https://www.youtube.com/watch?v=W0qmmnjEUME|500|center}}

Continuous-improvement approaches include PDCA, root-cause analysis, mistake-proofing, and Six Sigma methods. A common Six Sigma improvement cycle is '''DMAIC''': define the problem, measure the process, analyze causes, improve the process, and control the gains. These methods are most effective when teams connect data analysis with direct observation of work and stakeholder knowledge.

{{BR}}
= Lean Operations, Just in Time, and Kanban =

Lean operations seek to create customer value with fewer unnecessary resources, delays, defects, movements, and interruptions. Lean thinking emphasizes flow, pull, respect for people, problem solving, and continuous improvement rather than simple cost cutting.

Common forms of waste include overproduction, waiting, unnecessary transport, overprocessing, excess inventory, unnecessary motion, defects, and underused human capability. Waste should be analyzed in context because an apparent buffer or extra step may exist to manage a real risk or constraint.

'''Just in time''' aims to provide the right item in the right quantity at the right time. A pull system authorizes work based on actual downstream consumption rather than releasing work only from a forecast. '''Kanban''' is one method for signaling replenishment and controlling work in process.

[[File:Kanban principles.svg|500px|frameless|center]]

{{#ev:youtube|https://www.youtube.com/watch?v=Zjx7zCjLjyw|500|center}}

Lean systems often expose problems instead of covering them with large buffers. That makes reliability, supplier coordination, stable processes, preventive maintenance, quick changeovers, and disciplined problem solving especially important. Lean methods should not be copied mechanically; they must be adapted to demand patterns, product characteristics, technology, workforce capabilities, and risk.

{{BR}}
= Scheduling and Project Operations =

Scheduling assigns jobs, people, machines, rooms, vehicles, or other resources to time periods. In repetitive operations, managers may sequence jobs using rules such as first come first served, shortest processing time, earliest due date, or critical ratio. Different rules optimize different objectives, so the performance criterion must be explicit.

A '''Gantt chart''' displays activities against time and can make planned duration, overlap, and progress visible.

[[File:Gantt Chart Template for Film Production.png|500px|frameless|center]]

In projects, network methods represent precedence relationships between activities. The '''critical path''' is the longest-duration path through the project network under the assumed activity durations. Activities on the critical path have no scheduling slack in the basic deterministic model, so delay to a critical activity can delay the project unless the schedule is recovered elsewhere.

[[File:Pert example network diagram visio.gif|500px|frameless|center]]

{{#ev:youtube|https://www.youtube.com/watch?v=xOTxEhwvbwQ|500|center}}

Project managers should not treat the critical path as permanently fixed. Durations, resource constraints, scope changes, and uncertainty can change which activities are critical. Regular schedule updates are therefore essential.

{{BR}}
= Supply Chain and Logistics Management =

An operation depends on a wider network of suppliers, logistics providers, distributors, partners, and customers. Supply chain management coordinates material, information, and financial flows across organizational boundaries. Key decisions include sourcing, supplier development, contract design, transportation, warehousing, inventory positioning, network design, and collaboration.

[[File:Warhouse Types in the Supply Chain.png|500px|frameless|center]]

The '''bullwhip effect''' describes how order variability can increase as signals move upstream through a supply chain. Contributing mechanisms can include demand-signal processing, order batching, shortage gaming, promotions, and long replenishment lead times. Better information sharing, shorter lead times, stable ordering practices, and aligned incentives can reduce amplification.

Supply chain design also involves resilience. Concentrating purchases with one supplier may lower cost and simplify coordination while increasing exposure to disruption. Redundant suppliers, safety stock, flexible capacity, postponement, and regional diversification can improve resilience but usually add cost or complexity. The appropriate balance depends on the consequences and probability of disruption.

{{#ev:youtube|https://www.youtube.com/watch?v=IqmrNUoiy7g|500|center}}

Sustainable supply chain decisions consider energy use, emissions, waste, labor conditions, traceability, circular flows, and end-of-life recovery. These issues should be integrated into operational objectives rather than treated as separate from cost, quality, delivery, and risk.

{{BR}}
= Service Operations and Queueing =

Service operations often involve customer participation, time-sensitive demand, and capacity that cannot be inventoried in advance. An empty hotel room, unused airline seat, or idle appointment slot usually cannot be stored for tomorrow. This makes demand management, staffing, reservation systems, self-service technology, and queue design central decisions.

Waiting occurs when demand temporarily exceeds available service capacity. Even when average capacity is greater than average demand, variability in arrivals and service times can create queues. As utilization becomes very high, waiting can rise sharply in many queueing systems. Managers therefore need to balance resource productivity with service responsiveness.

Queue design affects both actual and perceived waiting. Single pooled lines can often share variability across servers, while appointments can smooth arrivals. Digital status information can improve transparency. However, priority rules must be designed carefully because they influence fairness, access, and customer experience.

{{BR}}
= Digital and Sustainable Operations =

Digital technologies can improve visibility, prediction, coordination, and control. Enterprise resource planning systems integrate transactions and planning data; manufacturing execution systems connect production activity with shop-floor information; sensors and industrial internet technologies can monitor equipment and process conditions; analytics and artificial intelligence can support forecasting, maintenance, scheduling, and anomaly detection.

Technology does not remove the need for process design. Automating a poorly designed process can make waste faster and harder to see. Before automation, you should clarify the purpose of the process, simplify unnecessary steps, define data quality requirements, and specify how humans will monitor, override, or recover the system when conditions change.

Sustainable operations aim to reduce negative environmental and social impacts while maintaining required performance. Important approaches include energy efficiency, material efficiency, waste prevention, remanufacturing, repair, reuse, reverse logistics, life-cycle thinking, safer work design, and circular business models. Good operations decisions evaluate the full system rather than shifting cost or impact from one stage to another.

{{BR}}
= A Practical Decision Framework =

When facing an operations problem, use a disciplined sequence:
# [[Problem Definition|Define the operational objective]]: State the customer or stakeholder requirement and the decision to be made.
# [[Process Analysis|Map the process]]: Identify flows, queues, resources, decisions, constraints, and sources of variation.
# [[Data Analysis|Measure current performance]]: Select metrics and gather data that are reliable enough for the decision.
# [[Operations Research|Develop alternatives]]: Use models, experiments, simulation, benchmarking, or structured judgment to compare options.
# [[Continuous Improvement|Implement and learn]]: Pilot changes when possible, monitor results, and update the process as evidence accumulates.

The strongest operations decisions combine system thinking with local detail. Improving one metric, department, or resource is not automatically an improvement for the whole operation. You should ask whether the change improves end-to-end flow, customer value, risk, workforce conditions, and long-term capability.

{{BR}}
= Interactive Tasks =

{{BR}}
== Quiz: Test Your Knowledge ==

{{MC}}

'''What is the central purpose of operations management?'''
(Designing and controlling processes that create goods and services)
(!Managing only advertising and sales activities)
(!Preparing only financial statements for investors)
(!Replacing all human judgment with automation)

{{E}}
<br>

{{MC}}

'''Which resource is called a bottleneck?'''
(The resource that limits overall process capacity)
(!The resource with the newest equipment)
(!The resource with the lowest purchase price)
(!The resource with the largest storage area)

{{E}}
<br>

{{MC}}

'''What does Littles Law connect under stable conditions?'''
(Work in process throughput and flow time)
(!Price promotion and market share)
(!Defect rate wages and depreciation)
(!Cash taxes and shareholder equity)

{{E}}
<br>

{{MC}}

'''What cost tradeoff is central to the basic economic order quantity model?'''
(Ordering cost and holding cost)
(!Marketing cost and tax cost)
(!Training cost and legal cost)
(!Advertising cost and design cost)

{{E}}
<br>

{{MC}}

'''What is the purpose of a reorder point?'''
(To signal when replenishment should be triggered)
(!To calculate employee promotion dates)
(!To set the selling price of a product)
(!To choose the color of product packaging)

{{E}}
<br>

{{MC}}

'''What is a control chart primarily used to monitor?'''
(Process behavior and variation over time)
(!Competitor advertising themes)
(!Employee vacation preferences)
(!Corporate ownership changes)

{{E}}
<br>

{{MC}}

'''What principle best describes a Kanban pull system?'''
(Work is authorized by downstream consumption)
(!Work is released without regard to demand)
(!All inventory is eliminated immediately)
(!Every process uses one identical batch size)

{{E}}
<br>

{{MC}}

'''What does the critical path represent in a project network?'''
(The longest duration path through the network)
(!The activity with the highest material cost)
(!The route with the most employees)
(!The first activity entered into the schedule)

{{E}}
<br>

{{MC}}

'''What is the bullwhip effect?'''
(Amplification of order variability upstream)
(!Reduction of all lead times to zero)
(!Elimination of supplier relationships)
(!Conversion of services into physical goods)

{{E}}
<br>

{{MC}}

'''Why might an operation maintain a capacity cushion?'''
(To absorb demand peaks and uncertainty)
(!To guarantee that utilization is always complete)
(!To remove the need for forecasting)
(!To eliminate every fixed cost)

{{E}}
<br>

{{BR}}
== Memory Game ==

<div class="memo-quiz">
{|
|-
| Bottleneck || Resource that limits overall process output
|-
| Throughput || Rate at which completed units leave a process
|-
| Safety stock || Extra inventory held against uncertainty
|-
| Control chart || Time ordered display used to monitor process variation
|-
| Kanban || Signal that authorizes replenishment in a pull system
|-
| Critical path || Longest duration route through a project network
|-
| Bullwhip effect || Amplification of order variability along a supply chain
|}
{{E}}
<br>

{{BR}}
== Drag and Drop ==

<div class="lueckentext-quiz">

{| class="wikitable"
! Match the correct terms.
! Topic
|-
| '''Flow time'''
| Time a unit spends in a process
|-
| '''Capacity cushion'''
| Deliberate spare capability for uncertainty
|-
| '''Reorder point'''
| Trigger level for replenishment
|-
| '''Value stream'''
| End to end flow of activities and information
|-
| '''Root cause'''
| Underlying reason a problem occurs
|}
{{E}}

<br>
Match each operations-management concept with the description that best explains its role.
<br />

{{BR}}
== Crossword Puzzle ==

<div class="kreuzwort-quiz">
{|
|-
| Bottleneck || What do you call the resource that limits total process capacity?
|-
| Inventory || What term describes stored materials goods or work waiting in a system?
|-
| Kanban || What pull signal can authorize replenishment or production?
|-
| Forecasting || What activity estimates future demand from information and data?
|-
| Capacity || What term describes the maximum sustainable output of a resource or process?
|-
| Throughput || What term means the rate at which completed units leave a process?
|}
{{E}}
<br>

{{BR}}
== LearningApps ==

<iframe> https://learningapps.org/index.php?s=Operations+Management </iframe>

{{BR}}
== Cloze Text ==

<quiz display=simple>
{'''Complete the text.'''<br>
|type="{}"}
Operations management designs and improves the processes that create { goods and services }. A resource that limits overall system output is a { bottleneck }. Under stable conditions Little's Law connects throughput with flow time and { work in process }. Deliberate spare capacity used to handle uncertainty is a { capacity cushion }. The basic economic order quantity model balances ordering cost with { holding cost }. Inventory kept to protect against uncertainty is called { safety stock }. A time ordered chart used to monitor process variation is a { control chart }. Lean systems often use { pull } to authorize work from actual downstream demand. A replenishment signal in many lean systems is called { Kanban }. The longest duration route through a basic project network is the { critical path }. Upstream amplification of order variability is called the { bullwhip effect }. Sustainable operations consider environmental and social impacts across the whole { system }.
</quiz>

<br>

{{BR}}
= Open-Ended Tasks =

{{BR}}
=== Easy ===
# [[Process Observation]]: Observe a familiar service such as a café library or student help desk and draw a simple process map that shows inputs activities waiting points and outputs.
# [[Operations Metrics]]: Choose one everyday process and define three measures for quality speed dependability flexibility or cost explaining what each measure reveals.
# [[Inventory Walk]]: Identify five examples of inventory in a university workplace or household setting and explain why each item is held.
# [[Queue Diary]]: Record two waiting experiences during one day and describe the likely sources of demand or service variability.

{{BR}}
=== Standard ===
# [[Capacity Analysis]]: Measure or estimate the capacity of a multi-step process identify its bottleneck and propose one change that could increase end-to-end throughput.
# [[Forecast Evaluation]]: Use a small time series of real or simulated demand compare two simple forecasting methods and evaluate the errors with an appropriate metric.
# [[Value Stream Map]]: Create a current-state value-stream map for a student organization administrative process or small business and distinguish processing time from waiting.
# [[Quality Investigation]]: Collect repeated measurements from a stable process create a simple control chart and discuss whether any unusual patterns deserve investigation.

{{BR}}
=== Advanced ===
# [[Inventory Policy Design]]: Build and justify an inventory policy for a selected item including demand assumptions order quantity reorder logic safety stock and service implications.
# [[Supply Chain Resilience]]: Map a real product supply chain using public information identify at least three disruption risks and evaluate mitigation options with explicit tradeoffs.
# [[Operations Simulation]]: Build a spreadsheet or discrete-event simulation of a queue or production process test at least three scenarios and explain how variability changes performance.
# [[Sustainable Operations Project]]: Conduct an evidence-based improvement project for an operation that reduces waste energy material use or waiting while tracking effects on cost quality and service.

{{:Open Task - Create a MOOC}}

{{BR}}
= Learning Assessment =

# [[Process Diagnosis]]: Given a case with demand capacity work in process and waiting data identify the likely constraint and explain how your proposed intervention changes system performance.
# [[Inventory Decision]]: Compare a low-inventory policy with a high-service policy under uncertain demand and justify a recommendation using cost service risk and operational feasibility.
# [[Quality Reasoning]]: Interpret a control chart together with specification information and explain why statistical control and customer conformance are related but not identical ideas.
# [[Lean Transfer]]: Apply pull flow and waste reduction to a non-manufacturing setting and explain which lean practices transfer well and which need adaptation.
# [[Project Scheduling]]: Analyze a precedence network identify critical activities and evaluate how a delay resource constraint or changed duration could alter the project plan.
# [[Supply Chain Tradeoff]]: Recommend a sourcing and logistics configuration for a disruption-prone product and defend the balance among cost responsiveness resilience sustainability and supplier relationships.

<br>
<br>

{{BR}}
= Evidence of Learning =

'''Knowledge:''' You can explain the transformation model, operations strategy, process flow, bottlenecks, capacity, forecasting, inventory logic, MRP, statistical process control, lean systems, scheduling, project networks, supply chains, queueing, and sustainable operations.

'''Analytical skills:''' You can map processes, calculate and interpret core flow relationships, identify constraints, compare forecasts, reason about capacity, evaluate inventory policies, interpret control charts, and analyze project and supply-chain tradeoffs.

'''Practical skills:''' You can collect operational data, observe work directly, distinguish symptoms from root causes, construct models with explicit assumptions, compare alternatives, and communicate recommendations to technical and non-technical stakeholders.

'''Products:''' Strong evidence may include a process map, value-stream map, capacity model, forecast comparison, inventory policy, quality analysis, project network, simulation, supply-chain risk map, or documented improvement experiment.

'''Transfer:''' You can adapt operations concepts from manufacturing to services, healthcare, digital operations, public administration, logistics, education, and other contexts while recognizing differences in customer contact, variability, risk, and resource structure.

<br>
<br>

{{BR}}
= OERs on the Topic =

<iframe> https://en.m.wikipedia.org/wiki/Operations_management </iframe>

<br>

{{BR}}
= Linked Learning Areas =

{| align=center
{{:D-Tab}}
'''[[Operations Management]]'''
# [[Operations Strategy]]
# [[Process Management]]
# [[Capacity Planning]]
# [[Demand Forecasting]]
# [[Inventory Management]]
# [[Quality Management]]
# [[Lean Manufacturing]]
# [[Supply Chain Management]]
# [[Project Management]]
# [[Operations Research]]
|}

{{BR}}
= aiMOOC Projects =
[[Category:English]]
[[Category:Operations Management]]
[[Category:Higher Education]]
[[Category:Business Administration]]
[[Category:Management]]
[[Category:Industrial Engineering]]
[[Category:Supply Chain Management]]
[[Category:Production and Manufacturing]]
[[Category:Operations Research]]
[[Category:AI_MOOC]]
[[Category:GPT aiMOOC]]
{{MT}}

English:Operations Management - Versionsgeschichte

Glanz: aiMOOC über GPT aiMOOC Action erstellt