{ "schema_version": "core-reviewed-term-ai-handoff-v2", "version": "core-reviewed-term-ai-handoff-v2", "compat": { "backward_compatible_schema_versions": [ "core-reviewed-term-ai-handoff-v1" ], "v1_fields_preserved": true }, "contract_status": "preview", "distribution": "per_term_read_only_ai_handoff", "no_write_operations": true, "content_tier": "db_backed", "canonical": { "url": "https://core.yogoq.com/ko-KR/core/capacity-planning", "slug": "capacity-planning", "locale": "ko-KR" }, "summary": { "schema_version": "core-reviewed-term-summary-v1", "term_id": "8d0a0db5-ec40-5128-b9d0-05d41012e93a", "canonical_slug": "capacity-planning", "canonical_url": "https://core.yogoq.com/ko-KR/core/capacity-planning", "locale": "ko-KR", "display_name": "キャパシティ計画", "english_name": "Capacity Planning", "abbreviation": null, "short_definition": "Capacity Planning is the planning practice that matches expected demand with people, systems, supplier, and process capacity over a defined horizon. It is used for whether to add capacity, rebalance demand, change servi…", "content_tier": "db_backed", "quality": "reviewed", "publication_status": "published_reviewed", "version": "core-reviewed-term-summary-v1", "last_reviewed_at": "2026-05-14T00:00:00.000Z", "sources_count": 2, "limitations_key": "core-trust-policy-v1-2026-06-22" }, "aliases": [ { "text": "キャパシティ計画", "type": "display_name", "locale": "ko-KR" }, { "text": "Capacity Planning", "type": "english_name", "locale": "en-US" }, { "text": "キャパシティ・プランニング", "type": "katakana", "locale": "ko-KR" }, { "text": "キャパシティ計画", "type": "localized_title", "locale": "ja-JP" } ], "content": { "definition": { "key": "definition", "title": "一言でいうと", "text": "Capacity Planning is the planning practice that matches expected demand with people, systems, supplier, and process capacity over a defined horizon. It is used for whether to add capacity, rebalance demand, change service levels, or accept waiting by reading demand forecast, workload mix, utilization, constraint capacity, hiring lead time, and service target and deciding whether to add capacity, rebalance demand, change service levels, or accept waiting.", "items": [] }, "formula": null, "boundary": { "key": "boundary", "title": "含めるもの / 含めないもの", "text": "Keep the inclusion and exclusion rules stable so decisions can be compared over time. Include | demand range, workload mix, constrained resource, ramp time | These decide whether available capacity is real Exclude | headline headcount, nominal licenses, unused theoretical capacity | They can overstate what the system can deliver Define explicitly | planning horizon, service target, surge rule, capacity owner | Capacity decisions depend on time and promised service", "items": [ "Include | demand range, workload mix, constrained resource, ramp time | These decide whether available capacity is real", "Exclude | headline headcount, nominal licenses, unused theoretical capacity | They can overstate what the system can deliver", "Define explicitly | planning horizon, service target, surge rule, capacity owner | Capacity decisions depend on time and promised service" ] }, "usage": [ { "key": "meaning", "title": "意味", "text": "Capacity Planning is a practical concept for improving operating, risk, and organization decisions. It makes demand forecast, workload mix, utilization, constraint capacity, hiring lead time, and service target visible under shared assumptions so teams can decide whether to add capacity, rebalance demand, change service levels, or accept waiting. Without clear capacity planning boundaries, owners, and review cadence, teams can improve one local view while moving capacity planning pressure elsewhere.", "items": [] }, { "key": "usage", "title": "役立つ場面", "text": "Capacity Planning changes decisions by turning demand forecast, workload mix, utilization, constraint capacity, hiring lead time, and service target into evidence for where scarce capacity and budget should go. It sets boundaries so improvement, control, resilience, and customer impact can be weighed in the same review. It makes whether to add capacity, rebalance demand, change service levels, or accept waiting operational by naming owners, triggers, and review cadence instead of leaving the concept as a discussion point.", "items": [ "Capacity Planning changes decisions by turning demand forecast, workload mix, utilization, constraint capacity, hiring lead time, and service target into evidence for where scarce capacity and budget should go.", "It sets boundaries so improvement, control, resilience, and customer impact can be weighed in the same review.", "It makes whether to add capacity, rebalance demand, change service levels, or accept waiting operational by naming owners, triggers, and review cadence instead of leaving the concept as a discussion point." ] }, { "key": "usage", "title": "使い方のポイント", "text": null, "items": [ "Plan by the constrained resource, not by average headcount.", "Use demand ranges and workload mix instead of a single volume forecast.", "Separate permanent capacity from flexible capacity and overtime.", "Connect capacity decisions to service level and cash consequences.", "In every Capacity Planning review, record the customer impact, risk tradeoff, accountable owner, and next review date alongside the metric movement." ] }, { "key": "drivers", "title": "何が数字を動かすか", "text": "Breaking the topic into drivers shows which operating action is likely to move the result. Demand mix | Different work types consume different capacity | Track complexity, not only volume Ramp time | Capacity that arrives late cannot protect current service | Include hiring, training, supplier, or system lead time Utilization target | High utilization increases waiting and fragility | Keep buffers where variability is high", "items": [ "Demand mix | Different work types consume different capacity | Track complexity, not only volume", "Ramp time | Capacity that arrives late cannot protect current service | Include hiring, training, supplier, or system lead time", "Utilization target | High utilization increases waiting and fragility | Keep buffers where variability is high" ] } ], "misunderstandings": [ { "key": "misunderstandings", "title": "よくある誤解 / 落とし穴", "text": null, "items": [ "Average demand hides peak load and mix shifts.", "Adding headcount does not add capacity if training or system access is the constraint.", "Running at full utilization usually increases queue time." ] } ], "examples": [ { "key": "examples", "title": "最小例", "text": "A customer success team plans only by account count and misses renewal season load. It rebuilds the plan around complex renewals, onboarding demand, and manager review time. The team adds temporary specialist capacity and shifts low-risk accounts to self-serve guidance. In this example, Capacity Planning is treated as an operating decision that connects constraints, ownership, measurement, and review, so the team can reassess the change using the same evidence later.", "items": [] } ], "comparisons": [ { "key": "comparisons", "title": "似ている言葉との違い", "text": "Sales capacity planning | Plans selling capacity | Capacity planning applies the same constraint logic to broader operations Supply chain management | Coordinates supply flow | Capacity planning determines whether the flow has enough constrained resources Service level design | Sets promises | Capacity planning tests whether those promises can be met", "items": [ "Sales capacity planning | Plans selling capacity | Capacity planning applies the same constraint logic to broader operations", "Supply chain management | Coordinates supply flow | Capacity planning determines whether the flow has enough constrained resources", "Service level design | Sets promises | Capacity planning tests whether those promises can be met" ] } ], "faq": [ { "question": "What is the unit of capacity?", "answer": "Use the resource that constrains output: skilled hours, machine time, review slots, supplier capacity, or system throughput." }, { "question": "Why not plan from average utilization?", "answer": "Averages hide peaks, variability, and workload mix, which are what create queues." }, { "question": "When should capacity be added?", "answer": "Add capacity before the constraint breaches service targets, accounting for ramp time." } ] }, "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "sources": { "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "visible_sources": [ { "label": "Principles of Management (Open Textbook Library)", "url": "https://open.umn.edu/opentextbooks/textbooks/principles-of-management", "kind": "tier_s" }, { "label": "Wikipedia reference: Operations Management", "url": "https://en.wikipedia.org/wiki/Operations_management", "kind": "supplemental" } ] }, "related_terms": [ { "topic_id": "5c96f8de-9847-52ca-bfda-c57537acde07", "canonical_slug": "supply-chain-management", "canonical_url": "https://core.yogoq.com/ko-KR/core/supply-chain-management", "title": "サプライチェーン・マネジメント（SCM）", "relation_type": "used_together" }, { "topic_id": "2da62c33-3da8-5dbb-9b0f-506e7283e280", "canonical_slug": "service-level-design", "canonical_url": "https://core.yogoq.com/ko-KR/core/service-level-design", "title": "サービスレベル設計", "relation_type": "used_together" }, { "topic_id": "cddd4eb6-3707-5306-966d-33f92a779f54", "canonical_slug": "sales-capacity-planning", "canonical_url": "https://core.yogoq.com/ko-KR/core/sales-capacity-planning", "title": "営業キャパシティ計画", "relation_type": "related" } ], "relations": [ { "term_id": "5c96f8de-9847-52ca-bfda-c57537acde07", "canonical_slug": "supply-chain-management", "canonical_url": "https://core.yogoq.com/ko-KR/core/supply-chain-management", "display_name": "サプライチェーン・マネジメント（SCM）", "relation_type": "related", "source_relation_type": "used_together" }, { "term_id": "2da62c33-3da8-5dbb-9b0f-506e7283e280", "canonical_slug": "service-level-design", "canonical_url": "https://core.yogoq.com/ko-KR/core/service-level-design", "display_name": "サービスレベル設計", "relation_type": "related", "source_relation_type": "used_together" }, { "term_id": "cddd4eb6-3707-5306-966d-33f92a779f54", "canonical_slug": "sales-capacity-planning", "canonical_url": "https://core.yogoq.com/ko-KR/core/sales-capacity-planning", "display_name": "営業キャパシティ計画", "relation_type": "related", "source_relation_type": "related" } ], "chunk_ids": [ "core:chunk:capacity-planning:ko-KR:definition:b9e098c3ccb84cc5", "core:chunk:capacity-planning:ko-KR:boundary:ced02a50ad826911", "core:chunk:capacity-planning:ko-KR:meaning:fdb49ecb41c19310", "core:chunk:capacity-planning:ko-KR:usage:35eede5ebc3f88b7", "core:chunk:capacity-planning:ko-KR:usage:8dd0d4aa858ce224", "core:chunk:capacity-planning:ko-KR:drivers:b7f3ae5d9f8980e6", "core:chunk:capacity-planning:ko-KR:misunderstandings:6ad90c87097d68b5", "core:chunk:capacity-planning:ko-KR:examples:f62daf2ca1a48ff6", "core:chunk:capacity-planning:ko-KR:comparisons:b96da1451e0c6488", "core:chunk:capacity-planning:ko-KR:faq:22d42187c800b1b4", "core:chunk:capacity-planning:ko-KR:faq:880ff96c8b176c49", "core:chunk:capacity-planning:ko-KR:faq:73e9c429d219000e" ], "chunks": [ { "chunk_id": "core:chunk:capacity-planning:ko-KR:definition:b9e098c3ccb84cc5", "section_key": "definition", "heading": "一言でいうと", "text": "Capacity Planning is the planning practice that matches expected demand with people, systems, supplier, and process capacity over a defined horizon. It is used for whether to add capacity, rebalance demand, change service levels, or accept waiting by reading demand forecast, workload mix, utilization, constraint capacity, hiring lead time, and service target and deciding whether to add capacity, rebalance demand, change service levels, or accept waiting.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "b9e098c3ccb84cc5aff8c2c63806a00a4aefc9e1d3f3fd648a011806104bcbb7" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:boundary:ced02a50ad826911", "section_key": "boundary", "heading": "含めるもの / 含めないもの", "text": "Keep the inclusion and exclusion rules stable so decisions can be compared over time. Include | demand range, workload mix, constrained resource, ramp time | These decide whether available capacity is real Exclude | headline headcount, nominal licenses, unused theoretical capacity | They can overstate what the system can deliver Define explicitly | planning horizon, service target, surge rule, capacity owner | Capacity decisions depend on time and promised service Include | demand range, workload mix, constrained resource, ramp time | These decide whether available capacity is real Exclude | headline headcount, nominal licenses, unused theoretical capacity | They can overstate what the system can deliver Define explicitly | planning horizon, service target, surge rule, capacity owner | Capacity decisions depend on time and promised service", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "ced02a50ad8269114294e1bc6e73b9285fbc6a8a37509e0924bf62983235e14d" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:meaning:fdb49ecb41c19310", "section_key": "meaning", "heading": "意味", "text": "Capacity Planning is a practical concept for improving operating, risk, and organization decisions. It makes demand forecast, workload mix, utilization, constraint capacity, hiring lead time, and service target visible under shared assumptions so teams can decide whether to add capacity, rebalance demand, change service levels, or accept waiting. Without clear capacity planning boundaries, owners, and review cadence, teams can improve one local view while moving capacity planning pressure elsewhere.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "fdb49ecb41c19310d87f25953248e57b6f0de8066a3af8240bf2011a1d0f7571" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:usage:35eede5ebc3f88b7", "section_key": "usage", "heading": "役立つ場面", "text": "Capacity Planning changes decisions by turning demand forecast, workload mix, utilization, constraint capacity, hiring lead time, and service target into evidence for where scarce capacity and budget should go. It sets boundaries so improvement, control, resilience, and customer impact can be weighed in the same review. It makes whether to add capacity, rebalance demand, change service levels, or accept waiting operational by naming owners, triggers, and review cadence instead of leaving the concept as a discussion point. Capacity Planning changes decisions by turning demand forecast, workload mix, utilization, constraint capacity, hiring lead time, and service target into evidence for where scarce capacity and budget should go. It sets boundaries so improvement, control, resilience, and customer impact can be weighed in the same review. It makes whether to add capacity, rebalance demand, change service levels, or accept waiting operational by naming owners, triggers, and review cadence instead of leaving the concept as a discussion point.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "35eede5ebc3f88b716c419ab1786c384ebe5bcc599aacc52f05f3b5b3dea65b3" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:usage:8dd0d4aa858ce224", "section_key": "usage", "heading": "使い方のポイント", "text": "Plan by the constrained resource, not by average headcount. Use demand ranges and workload mix instead of a single volume forecast. Separate permanent capacity from flexible capacity and overtime. Connect capacity decisions to service level and cash consequences. In every Capacity Planning review, record the customer impact, risk tradeoff, accountable owner, and next review date alongside the metric movement.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "8dd0d4aa858ce2247a70ad2f2b6b5c86f8a05a640010f7ec59b0a77362f7079f" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:drivers:b7f3ae5d9f8980e6", "section_key": "drivers", "heading": "何が数字を動かすか", "text": "Breaking the topic into drivers shows which operating action is likely to move the result. Demand mix | Different work types consume different capacity | Track complexity, not only volume Ramp time | Capacity that arrives late cannot protect current service | Include hiring, training, supplier, or system lead time Utilization target | High utilization increases waiting and fragility | Keep buffers where variability is high Demand mix | Different work types consume different capacity | Track complexity, not only volume Ramp time | Capacity that arrives late cannot protect current service | Include hiring, training, supplier, or system lead time Utilization target | High utilization increases waiting and fragility | Keep buffers where variability is high", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "b7f3ae5d9f8980e634a225039882839812f9b9f8fd3bcd6fae6bfa61d1779a10" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:misunderstandings:6ad90c87097d68b5", "section_key": "misunderstandings", "heading": "よくある誤解 / 落とし穴", "text": "Average demand hides peak load and mix shifts. Adding headcount does not add capacity if training or system access is the constraint. Running at full utilization usually increases queue time.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "6ad90c87097d68b5fd578a3e55c1cdf8870d6e4128eef7f8224850c2b900dab5" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:examples:f62daf2ca1a48ff6", "section_key": "examples", "heading": "最小例", "text": "A customer success team plans only by account count and misses renewal season load. It rebuilds the plan around complex renewals, onboarding demand, and manager review time. The team adds temporary specialist capacity and shifts low-risk accounts to self-serve guidance. In this example, Capacity Planning is treated as an operating decision that connects constraints, ownership, measurement, and review, so the team can reassess the change using the same evidence later.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "f62daf2ca1a48ff6862998243d53865278d762444e592043a072f7c9c18fc77a" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:comparisons:b96da1451e0c6488", "section_key": "comparisons", "heading": "似ている言葉との違い", "text": "Sales capacity planning | Plans selling capacity | Capacity planning applies the same constraint logic to broader operations Supply chain management | Coordinates supply flow | Capacity planning determines whether the flow has enough constrained resources Service level design | Sets promises | Capacity planning tests whether those promises can be met Sales capacity planning | Plans selling capacity | Capacity planning applies the same constraint logic to broader operations Supply chain management | Coordinates supply flow | Capacity planning determines whether the flow has enough constrained resources Service level design | Sets promises | Capacity planning tests whether those promises can be met", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "b96da1451e0c6488e9e1737451686b8f90bf393dbfd1d8429bd34c096478b5dd" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:faq:22d42187c800b1b4", "section_key": "faq", "heading": "What is the unit of capacity?", "text": "What is the unit of capacity? Use the resource that constrains output: skilled hours, machine time, review slots, supplier capacity, or system throughput.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "22d42187c800b1b4ee9f359b79a939c0891367005ae4f0e120d0ff0034df47e2" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:faq:880ff96c8b176c49", "section_key": "faq", "heading": "Why not plan from average utilization?", "text": "Why not plan from average utilization? Averages hide peaks, variability, and workload mix, which are what create queues.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "880ff96c8b176c49fa599c971add5a2be438d9732fb19294592281fc8867dc1c" }, { "chunk_id": "core:chunk:capacity-planning:ko-KR:faq:73e9c429d219000e", "section_key": "faq", "heading": "When should capacity be added?", "text": "When should capacity be added? Add capacity before the constraint breaches service targets, accounting for ramp time.", "source_refs": [ "concept:business-concept-0057:en-US", "concept:business-concept-0057:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "content_hash": "73e9c429d219000e671dceeccc23acbcf460ab07fc25bf34abda0731c33f8198" } ], "content_hash": "44ed77b916ab7a6e317284da8030fd30f3320a4d1a8a805e1414e9ad65f3e7d4", "hash_algorithm": "sha256", "rag": { "chunk_id_policy": "core:chunk:{canonical_slug}:{locale}:{section_key}:{sha256_16}", "content_hash_policy": "sha256_stable_json", "source_refs_precision": "source_object_ref_or_source_key_current_snapshot" }, "quality": { "content_tier": "db_backed", "quality": "reviewed", "publication_status": "published_reviewed", "source_count": 2, "last_reviewed_at": "2026-05-14T00:00:00.000Z", "trust_policy_version": "core-trust-policy-v1-2026-06-22" }, "limitations": { "policy_version": "core-trust-policy-v1-2026-06-22", "professional_advice_boundary": "reference_only_not_professional_advice", "text": "이 페이지는 조사와 학습을 위한 참조 정보입니다. 회계, 법무, 금융, 의료, 보안 등 개별 판단은 1차 출처나 전문가 확인을 우선하세요.", "items": [ "공개 페이지는 일반 이해와 실무 맥락을 돕는 자료이며, 개별 사안의 전문 조언이 아닙니다.", "제도, 가격, 규제, 회계 기준, 제품 사양처럼 빠르게 변하는 정보는 최종 판단 전에 1차 출처를 확인해야 합니다.", "AI 지원 제작·감사 흐름을 사용하더라도 공개 여부는 품질 게이트와 사람이 읽을 수 있는 증거에 기반해 다룹니다." ] } }