Cpm 122 Answer Key

CPM 122 at CSU Chico — What the Course Actually Covers

CPM 122 is a junior-level construction management course at California State University, Chico. The official catalog description is project scheduling and control using the critical path method. You learn how to build network diagrams, float out schedules, and track field progress against planned dates. The main text is usually Martin K. Parmelee's Scheduling Methods and Techniques or a similar PM-focused reference. The coursework is heavy on hand calculations before you ever open Primavera P6 or MS Project. Most of the grade comes from problem sets, midterm exams, and a final project that asks you to schedule a real building project from scratch.

CPM 122 Answer Key

I need to be honest about what this term means in the real world. There isn't one universal "answer key" for CPM 122. The problems change every semester — different project scopes, different activity lists, different resource constraints — so any site claiming to sell a single PDF with all answers is almost certainly wrong. The closest thing to an answer key is the solution manual that sometimes gets circulated, but even those are only accurate for the edition and problem set your instructor is using that term. Here's the core of the course, listed in roughly the order it shows up: When I was taking this, there was a problem involving a hospital wing renovation where two activities had a finish-to-start dependency with a 5-day lag, and then a third activity started from the second one with a 3-day lead. The professor wanted the network drawn both as a precedent diagram and as a node-style diagram. A lot of students missed that the lag was applied to the predecessor's finish, not the successor's start, which shifted the whole forward pass by two days and changed which path was actually critical.

My workaround was to draw the lag as a separate dummy activity on the diagram. That made the dependency explicit instead of hidden inside a label, and it prevented me from double-counting the float later. It adds one more box to the drawing, but it saves you from getting wrong answers on exams where the graders expect you to show your logic.

Where People Usually Lose Points

Here are the mistakes I see most often, organized by topic:

Network Drawing Errors

Students mix up dummies and real activities, or they introduce a loop that makes the network mathematically impossible. Before you start calculating, verify that every arrow points forward in time and that each activity has exactly one start node and one end node unless you're using the activity-on-arrow convention, in which case dummies must carry zero duration and zero cost.

Float Misinterpretation

Total float is not the same as free float. Free float is how much an activity can slip without delaying any successor. Total float is how much it can slip without delaying the project. They only match when an activity is on the sole path between its start and end events. If you treat them interchangeably, the crashing calculations go wrong.

Resource Leveling Without Logic Checks

Software will level resources automatically, but it might push activities onto paths that have no float. That creates a new critical path you didn't see. Always rerun the forward and backward passes after leveling to confirm the duration hasn't silently increased.

Counter-Intuitive Insight: Near-Critical Paths Matter More Than the Longest One

Beginners fixate on the critical path and ignore near-critical paths. In practice, a near-critical path with only 3 days of total float is often the real risk. When you crash one activity on the critical path by 5 days, the near-critical path can become the new critical path, and your time savings vanish. I learned this the hard way on a midterms project where we crashed five activities on the critical path and still finished exactly on the original date because a secondary path took over. Always track the top three longest paths, not just the longest.

Another Useful Nuance: Crash Cost Isn't Linear

Textbook problems make crashing look like a straight line — spend $500 per day saved, every day. Real schedules don't work that way. The first few days of crash usually come from overtime on low-resource activities. The last few days require adding crews, switching shifts, or buying faster materials, which jumps the cost curve. If your problem gives you a piecewise cost table, use the piecewise values. If it gives you a single daily rate, flag it to the professor before you submit, because applying that rate to the full crash window is almost always wrong.

Practical How-To for Getting Useful Study Material

Here is the most reliable path, in order:

1. Get the syllabus from your instructor and note the exact textbook edition and problem numbers for each assignment.
2. Check the CSU Chico Engineering library for the instructor solutions manual. It's usually reserved and checked out quickly, so go early.
3. For the software portion, ask your lab TA which version of Primavera P6 is installed. The interface changed enough between 2020 and 2024 that walkthrough videos often reference missing menus.
4. Form a small study group and compare network diagrams before submitting. Discrepancies between two people's diagrams usually reveal a dependency error in one of them.

If you search for a CPM 122 answer key online, expect most results to be generic construction scheduling PDFs that have nothing to do with the Chico course. The ones that are relevant are typically posted on the university's course site or shared through the engineering student association's Slack channel.

Limitations of This Course's Approach

CPM 122 teaches deterministic scheduling. It assumes activity durations are fixed once you pick a value. That works for textbook problems, but it fails in the field where weather, supplier delays, and trade coordination create probabilistic durations. If you want something closer to actual practice, pair this course with a reading on PERT or Monte Carlo schedule risk analysis. The deterministic CPM method is still the industry standard for baseline reporting, but don't walk into a job site thinking float is a safety buffer. It isn't. It's a shared pool of slack that gets consumed the moment any delay happens.

Final Note on Software and Manual Work

You will be graded on hand calculations even if you build the schedule in P6. Professors assign this because software hides logic errors. I recommend running the manual forward pass first, then modeling the same network in P6, then comparing both outputs. If they disagree, the manual path is where you find the bug — usually a missing lag or a misread predecessor link. The manual method takes about 20 to 30 minutes for a 25-activity network. The software version takes 10 minutes once the logic is clean, but the clean-up time after a broken import can easily exceed an hour.