---
title: "Pamamaraang critical path (CPM)"
source: "https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)"
wiki: "systems-analysis.info/int"
article: "Pamamaraang_critical_path_(CPM)"
language: "tl"
categories:
  - "Category:Operations research"
  - "Category:Project management"
  - "Category:Tagalog"
revision_id: 5434
wiki_created_at: 2026-09-06T23:49:15Z
wiki_modified_at: 2026-09-06T23:49:15Z
downloaded_at: 2026-09-07T23:08:27Z
---

# Pamamaraang critical path (CPM)

**Paraan ng Kritikal na Landas (CPM)** (Ingles: *Critical Path Method*, *CPM*) — isang deterministic na paraan ng network planning at pamamahala ng proyekto, na ginagamit para kalkulahin ang pagkakasunud-sunod ng mga gawain at ang pinakamaikling posibleng tagal ng pagkumpleto ng proyekto. Ang kritikal na landas — ito ang pinakamatagal na landas sa network model; ang pagkaantala ng anumang gawain sa landas na ito ay nagpapabago ng katapusan ng buong proyekto<sup>[\[1\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-enwiki-1)[\[2\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-kelley1959-2)</sup>.

## Kasaysayan

Ang CPM ay binuo noong huling bahagi ng 1950s nina James Kelley (Remington Rand) at Morgan Walker (DuPont). Ang kanilang ulat noong 1959 ay nagsilang simula ng pang-industriyang paggamit ng pamamaraan; nang maglaon ay nag-publish ang mga may-akda ng makasaysayang sanaysay tungkol sa pinagmulan ng CPM<sup>[\[2\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-kelley1959-2)[\[3\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-origins-3)</sup>. Sabay-sabay na nilikha sa Estados Unidos ang probabilistic na paraan ng PERT, na madalas gamitin kasabay ng CPM<sup>[\[1\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-enwiki-1)</sup>.

## Mga Pangunahing Konsepto

- **Gawain** (activity) — isang aksyon na may tagal **d** at mga dependency mula sa mga nauna.
- **Pangyayari/milestone** — isang sandali na walang tagal, na nagtatala ng estado ng proyekto.
- **Kritikal na landas** — ang pagkakasunud-sunod ng mga gawain na may pinakamataas na kabuuang tagal sa pagitan ng simula at katapusan ng modelo; ang mga gawain dito ay may zero na kabuuang reserba<sup>[\[1\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-enwiki-1)</sup>.
- **Pagkakasunud-sunod** ay tinutukoy ng mga relasyong FS, SS, FF, SF na may mga posibleng lag; sa praktis ginagamit ang PDM / AON (mga gawain — mga node), habang ang makasaysayang ADM / AOA ay mas bihirang makita<sup>[\[4\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-pdm-4)[\[5\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-adm-5)[\[6\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-dependency-6)</sup>.

## Pagkalkula ng mga Petsa at Reserba

Ang pagkalkula ay isinasagawa sa pamamagitan ng pasulong at pabalik na pagtawid sa network.

**Pasulong na pagtawid** (maagang mga petsa):

para sa mga paunang gawain: **ES = 0** (o ayon sa tinanggap na sukat);

para sa bawat gawain *j*: **ES<sub>j</sub> = max{ EF<sub>i</sub> ng lahat ng nauna na *i* }**;

**EF = ES + d**.

**Pabalik na pagtawid** (huling mga petsa):

para sa mga pangwakas na gawain: ang **LF** ay katumbas ng kabuuang tagal ng proyekto (o maagang katapusan ng pangwakas na milestone);

para sa bawat gawain *j*: **LS = LF − d**; **LF<sub>j</sub> = min{ LS<sub>s</sub> ng lahat ng kasunod na *s* }**<sup>[\[7\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-baker-7)[\[8\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-cmu-8)</sup>.

**Mga reserba** (float/slack):

**Kabuuang reserba (TF)**: **TF = LS − ES = LF − EF** — hanggang gaano katagal maaantala ang isang gawain nang hindi naiimpluwensyahan ang katapusan ng proyekto.

**Libreng reserba (FF)**: **FF = min{ ES<sub>succ</sub> } − EF** — pagkaantala nang hindi naiimpluwensyahan ang mga maagang simula ng mga kasunod<sup>[\[9\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-pressbooks-9)[\[10\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-pmi-ff-10)</sup>.

## Mga Ugnayan at Lag

Sa PDM, sinusuportahan ang apat na pangunahing uri ng dependency: **FS** (finish‑to‑start), **SS** (start‑to‑start), **FF** (finish‑to‑finish), **SF** (start‑to‑finish). Ang bawat ugnayan ay maaaring magkaroon ng lag (positibo o negatibo), halimbawa **FS + 2d** — ang simula ng kasunod ay dalawang araw pagkatapos ng katapusan ng nauna<sup>[\[6\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-dependency-6)</sup>.

## Pagpapaikli ng Tagal (crashing, fast‑tracking)

Ang pagpapaikli ng tagal ng proyekto ay posible sa pamamagitan ng:

- **Crashing** — ang layuning pagbabawas ng tagal ng mga kritikal na gawain sa pamamagitan ng karagdagang gastos; mas mainam na bawasan ang mga gawain na may pinakamababang "slope" ng halaga.

**Slope ng halaga** (halaga ng 1 unit ng pagpapaikli): **(C<sub>crash</sub> − C<sub>normal</sub>) / (D<sub>normal</sub> − D<sub>crash</sub>)**<sup>[\[11\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-crash-11)</sup>.

- **Fast‑tracking** — ang pagsasalin ng mga katanggap-tanggap na dependency sa parallel na pagpapatupad (halimbawa, FS → SS) na may pagtaas ng panganib ng muling paggawa<sup>[\[1\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-enwiki-1)</sup>.

## Mga Larangan ng Paggamit

Ginagamit ang CPM para bumuo ng mga iskedyul sa konstruksyon, enerhiya, makinarya, IT na mga proyekto at R&D. Ang pamamaraan ay pangunahin sa mga pamantayan ng pamamahala ng proyekto at systems engineering (PMI, NASA) at malawak na sinusuportahan ng software para sa pagpaplano<sup>[\[1\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-enwiki-1)[\[12\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-pmi-12)[\[13\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-nasa-13)</sup>.

## Mga Kalamangan

- Malinaw na pagkilala ng kritikal na landas at mga "bottleneck"; inuuna ang atensyon ng tagapamahala ng proyekto<sup>[\[1\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-enwiki-1)</sup>.
- Simpleng mga tuntunin sa pagkalkula ng mga maagang/huling petsa at reserba; transparency ng epekto ng mga pagbabago<sup>[\[7\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-baker-7)</sup>.
- Compatibility sa PDM/Gantt chart at mga tool para sa pagsusuri ng mga opsyon sa pagpapabilis<sup>[\[4\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-pdm-4)</sup>.

## Mga Limitasyon

- Hindi isinasaalang-alang ng pangunahing CPM model ang mga limitasyon sa resources at stochastic na kalikasan ng mga tagal; para dito ginagamit ang resource leveling at mga extension (halimbawa, *critical chain*)<sup>[\[1\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-enwiki-1)</sup>.
- Kapag gumagamit ng mga kumplikadong dependency at lag, ang interpretasyon ng mga reserba ay maaaring maging hindi-trivial; inirerekomenda ang pormal na kahulugan at kontrol ng mga tuntunin sa pagkalkula ng float sa mga kontraktwal na dokumento<sup>[\[10\]](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_note-pmi-ff-10)</sup>.

## Ugnayan sa Ibang mga Pamamaraan

- PERT — probabilistic na pagtatasa ng mga tagal (tatlong-puntong pagtatantya, β-approximation); gumagamit ang CPM ng deterministic na mga tagal.
- Gantt chart — kalendaryo na visualisasyon ng iskedyul, madalas gamitin kasabay ng CPM/PERT.
- Network planning — pangkalahatang grupo ng mga pamamaraan (CPM, PERT, ADM/AOA, PDM/AON).

## Tingnan Din

- PERT
- Gantt chart
- Network planning

## Talasanggunian

- Kelley, J. E.; Walker, M. R. (1959). *Critical‑Path Planning and Scheduling*. IRE‑AIEE‑ACM '59 (Eastern). *ACM Digital Library*. <a href="https://dl.acm.org/doi/10.1145/1460299.1460318" class="external autonumber" rel="nofollow">[14]</a>
- Kelley, J. E.; Walker, M. R. (1989). *Origins of CPM: A Personal History*. PM Network. *PMI*. <a href="https://www.pmi.org/learning/library/origins-cpm-personal-history-3762" class="external autonumber" rel="nofollow">[15]</a>
- PMI. *PMBOK® Guide*. <a href="https://www.pmi.org/pmbok-guide-standards/foundational/pmbok" class="external autonumber" rel="nofollow">[16]</a>
- NASA. *Systems Engineering Handbook* (SP‑2016‑6105 Rev2). <a href="https://www.nasa.gov/connect/ebooks/nasa-systems-engineering-handbook/" class="external autonumber" rel="nofollow">[17]</a>
- «Critical path method». *Wikipedia (en)*. <a href="https://en.wikipedia.org/wiki/Critical_path_method" class="external autonumber" rel="nofollow">[18]</a>
- «Precedence diagram method». *Wikipedia (en)*. <a href="https://en.wikipedia.org/wiki/Precedence_diagram_method" class="external autonumber" rel="nofollow">[19]</a>
- «Dependency (project management)». *Wikipedia (en)*. <a href="https://en.wikipedia.org/wiki/Dependency_%28project_management%29" class="external autonumber" rel="nofollow">[20]</a>
- «Arrow diagramming method». *Wikipedia (en)*. <a href="https://en.wikipedia.org/wiki/Arrow_diagramming_method" class="external autonumber" rel="nofollow">[21]</a>
- Baker, S. L. *Critical Path Method (CPM) — Analysis Steps*. University of South Carolina. <a href="https://sambaker.com/courses/J716/CPM/CPM.html" class="external autonumber" rel="nofollow">[22]</a>
- «Creating an Activity Network Diagram». *CSU Pressbooks*. <a href="https://pressbooks.ulib.csuohio.edu/project-management-navigating-the-complexity/chapter/7-4-creating-an-activity-network-diagram/" class="external autonumber" rel="nofollow">[23]</a>
- «Crashing Example». An‑Najah National University (halimbawa sa pagtuturo). <a href="https://staff-old.najah.edu/sites/default/files/CrashingExample.pdf" class="external autonumber" rel="nofollow">[24]</a>

## Tala

1.  <span id="cite_note-enwiki-1">↑ <sup>[1.0](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-enwiki_1-0)</sup> <sup>[1.1](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-enwiki_1-1)</sup> <sup>[1.2](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-enwiki_1-2)</sup> <sup>[1.3](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-enwiki_1-3)</sup> <sup>[1.4](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-enwiki_1-4)</sup> <sup>[1.5](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-enwiki_1-5)</sup> <sup>[1.6](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-enwiki_1-6)</sup> «Critical path method». *Wikipedia (en)*. <a href="https://en.wikipedia.org/wiki/Critical_path_method" class="external autonumber" rel="nofollow">[1]</a></span>
2.  <span id="cite_note-kelley1959-2">↑ <sup>[2.0](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-kelley1959_2-0)</sup> <sup>[2.1](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-kelley1959_2-1)</sup> Kelley, J. E., Jr.; Walker, M. R. (1959). «Critical-Path Planning and Scheduling». *IRE‑AIEE‑ACM '59 (Eastern)*. *ACM Digital Library*. <a href="https://dl.acm.org/doi/10.1145/1460299.1460318" class="external autonumber" rel="nofollow">[2]</a></span>
3.  <span id="cite_note-origins-3">[↑](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-origins_3-0) Kelley, J. E.; Walker, M. R. (1989). «Origins of CPM: A Personal History». *PM Network*. *Project Management Institute*. <a href="https://www.pmi.org/learning/library/origins-cpm-personal-history-3762" class="external autonumber" rel="nofollow">[3]</a></span>
4.  <span id="cite_note-pdm-4">↑ <sup>[4.0](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-pdm_4-0)</sup> <sup>[4.1](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-pdm_4-1)</sup> «Precedence diagram method». *Wikipedia (en)*. <a href="https://en.wikipedia.org/wiki/Precedence_diagram_method" class="external autonumber" rel="nofollow">[4]</a></span>
5.  <span id="cite_note-adm-5">[↑](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-adm_5-0) «Arrow diagramming method». *Wikipedia (en)*. <a href="https://en.wikipedia.org/wiki/Arrow_diagramming_method" class="external autonumber" rel="nofollow">[5]</a></span>
6.  <span id="cite_note-dependency-6">↑ <sup>[6.0](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-dependency_6-0)</sup> <sup>[6.1](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-dependency_6-1)</sup> «Dependency (project management)». *Wikipedia (en)*. <a href="https://en.wikipedia.org/wiki/Dependency_%28project_management%29" class="external autonumber" rel="nofollow">[6]</a></span>
7.  <span id="cite_note-baker-7">↑ <sup>[7.0](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-baker_7-0)</sup> <sup>[7.1](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-baker_7-1)</sup> Baker, S. L. «Critical Path Method (CPM) — Analysis Steps». University of South Carolina. <a href="https://sambaker.com/courses/J716/CPM/CPM.html" class="external autonumber" rel="nofollow">[7]</a></span>
8.  <span id="cite_note-cmu-8">[↑](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-cmu_8-0) «Fundamental Scheduling Procedures». *Project Management*, Carnegie Mellon University. <a href="https://www.cmu.edu/cee/projects/PMbook/10_Fundamental_Scheduling_Procedures.html" class="external autonumber" rel="nofollow">[8]</a></span>
9.  <span id="cite_note-pressbooks-9">[↑](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-pressbooks_9-0) «Creating an Activity Network Diagram». *Project Management — Navigating the Complexity*. Cleveland State University Pressbooks. <a href="https://pressbooks.ulib.csuohio.edu/project-management-navigating-the-complexity/chapter/7-4-creating-an-activity-network-diagram/" class="external autonumber" rel="nofollow">[9]</a></span>
10. <span id="cite_note-pmi-ff-10">↑ <sup>[10.0](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-pmi-ff_10-0)</sup> <sup>[10.1](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-pmi-ff_10-1)</sup> «Critical Path Method Calculations». *PMI*. <a href="https://www.pmi.org/learning/library/critical-path-method-calculations-scheduling-8040" class="external autonumber" rel="nofollow">[10]</a></span>
11. <span id="cite_note-crash-11">[↑](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-crash_11-0) «Crashing Example». An‑Najah National University (учебный пример). <a href="https://staff-old.najah.edu/sites/default/files/CrashingExample.pdf" class="external autonumber" rel="nofollow">[11]</a></span>
12. <span id="cite_note-pmi-12">[↑](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-pmi_12-0) PMI. *A Guide to the Project Management Body of Knowledge (PMBOK® Guide)*. <a href="https://www.pmi.org/pmbok-guide-standards/foundational/pmbok" class="external autonumber" rel="nofollow">[12]</a></span>
13. <span id="cite_note-nasa-13">[↑](https://systems-analysis.info/int/Pamamaraang_critical_path_(CPM)#cite_ref-nasa_13-0) NASA. *Systems Engineering Handbook* (NASA/SP‑2016‑6105 Rev2). <a href="https://www.nasa.gov/connect/ebooks/nasa-systems-engineering-handbook/" class="external autonumber" rel="nofollow">[13]</a></span>
