Capped at ten electricians, the medical office building finishes seventeen days late, so MT381's Unit 7 schedule adds two for 26 working days, keeps December 15 and lists the float spent. Searches like "mt 381 unit 7 assignment example", "mt381 unit 7 sample" and "mt381 unit 7 example" land here.
What a finished MT381 Unit 7 resource-leveled schedule looks like
Paired histograms anchor eight pages. The first plots daily electricians from early dates, peaking at 18 on ten working days between July 20 and August 9 and exceeding ten on 26. The second repeats the count after leveling to a cap of ten, never above the line but stretched across more weeks. A results table compares three runs of a serial leveling script that schedules the lowest late start first: unlimited, capped at ten, and capped at ten with twelve allowed from July 20 through August 24. A second resource runs alongside, telehandlers, limited to two by the staging area, with unleveled demand peaking at five. Float before and after is tabulated for every activity that moved, and each run's critical path is drawn in bold on a reduced copy of the network.
How a MT381 Unit 7 example is structured
Leveling here tests three staffing answers, and the page reports each answer's consequence instead of presenting one tidy histogram. The capped run shows what the subcontractor's commitment really means: overhead and in-wall rough-in on each level must take turns, switchgear termination waits behind level 3, and the path leaves the envelope and drywall chain for electrical work, finishing January 11, 2028. The windowed run shows the peak is short. Two more electricians for 26 working days absorb it, completion holds, and every delay stays inside float. Telehandlers are leveled in the same pass, brick veneer sliding 23 days later within its 36 and roofing 14 within its 19. What leveling spent is itemized next, because float consumed now is unavailable later: level 3 rough-in and roofing each end with three days, and paving drops from 37 to 14.
Eighteen against ten
Overhead rough-in on two levels overlaps in-wall rough-in on a third, six electricians apiece. The early-date histogram tops ten on 26 working days and reaches 18 on ten of them.
Capped at ten, the path jumps
Rough-in on each level waits its turn, switchgear termination queues behind level 3, and completion moves from December 15 to January 11. Electrical rough-in becomes the controlling chain.
Twelve for twenty-six days
Allowing twelve electricians from July 20 through August 24 clears the peak. Completion holds at December 15, and no activity moves beyond its own float in the windowed run.
Two telehandlers, five requests
Brick, curtain wall, roofing and framing all want machines at once. Leveling pushes brick 23 days later inside its 36 of float and roofing 14 inside its 19.
Float spent, itemized
Level 3 rough-in and roofing finish with three days each; paving falls from 37 to 14. The table lists every change so the next update starts from honest margins.
Where marks go in MT381 Unit 7
A histogram that shows a peak and then declares it leveled, saying nothing about what moved or what the finish did, is the weak version of this assignment. Leveling is judged on consequence: the new completion date, the float consumed and where the critical path went. A path that moved without comment suggests nobody reran the calculation. Crews treated as unlimited, or one crew shown on two levels on the same day, repeat the fault the unit is designed to expose. A comparison of alternatives is often rewarded, such as a hard cap set against a short-term addition, because a real manager chooses between them. Equipment deserves the same test as labor wherever the site limits it. Leveled schedules that quietly spend every remaining day of float, leaving later updates no margin, attract a closing remark.
Get a MT381 Unit 7 example written to your instructions
Attach the network and resource assignments your Unit 7 prompt uses, the crew or equipment limits it sets, and the rubric, noting any required software. The free first schedule, returned within 24-48h, levels to your limits, reports the new completion date and the float consumed, and shows exactly where the critical path moved.
MT381 Unit 7 questions, answered
Does leveling always delay the project?
No. Leveling first shifts activities within their float, and if the peak fits there, completion holds. Only when float runs out does the finish move. The sample shows both outcomes: a short-term addition keeps the date, while a hard cap pushes completion seventeen working days later and changes the critical path.
Which activities should leveling delay first?
Most leveling routines favor activities with the least float or the earliest late start, so the ones that can wait are the ones that wait. Your software or course may use a different rule. Whatever the rule, state it, because different priorities produce different leveled schedules from the same network.
Why track float after leveling?
Because leveling spends float, and float spent now is unavailable when a delay arrives later. A schedule that ends leveling with several chains at two or three days is fragile even if the finish date held. Listing float before and after tells the reader how much protection actually remains.