| Course | BU 436 Global Project Management and Sustainable Practices |
|---|---|
| Unit | Unit 8 |
| Paper type | Integrated global project plan |
| Length | About 900 words, 6 pages |
| Format | APA 7 student paper |
| School | Herzing University |
| Program | BS in Project Management |
| Updated | September 2026 |
Free sample paper for BU 436 Unit 8
The June Installation Date Did Not Survive the Ocean: An Integrated Global Project Plan for Forty Composite Solar Cold Rooms, Where Four Constraints Move the Same Dates
Student Name
Business, Herzing University
BU 436: Global Project Management and Sustainable Practices
Instructor Name
April 22, 2026
The June Installation Date Did Not Survive the Ocean: An Integrated Global Project Plan for Forty Composite Solar Cold Rooms, Where Four Constraints Move the Same Dates
What Integration Showed
Brightwell Cooling's project, a composite case for this course, delivers 40 solar cold rooms assembled in Monterrey, programmed from Pune and installed for cooperatives in central Kenya between April 2026 and January 2027. The earlier units each studied one constraint: the handoff gap between sites with no shared hours, certification before shipment, a supplier audit, and currency settlement dates. This plan puts all of them into one schedule. Doing so exposed a problem none of the separate analyses showed. The regulatory analysis and sustainability plan assumed the first installation in June. Once sea freight, which the sustainability plan chose over air, and pre-shipment certification were placed end to end after assembly, the earliest a cold room could reach a Kenyan site was the end of August. The June date was never achievable; it had been written before anyone added the ocean.
Buehler et al. (1994) showed that people planning a task focus on the steps of the task itself and neglect the delays around it, which is why their estimates run short. Integration is the step that forces those surrounding delays into view, and in this project it changed the most visible date the funder had been told.
The Integrated Schedule
The cold rooms move in three batches. The table shows each batch's path from assembly to installation, with the constraint that fixes each step.
| Batch | Assembly in Monterrey | Pre-shipment certification | Sails | Reaches sites | Installation window | Constraint that sets it |
|---|---|---|---|---|---|---|
| 1 (10 rooms) | June 1 to June 26 | June 29 to July 8 | July 10 | About August 28 | August 31 to September 25 | Firmware freeze May 29; transit about 6 weeks; before short rains |
| 2 (15 rooms) | June 29 to August 7 | August 17 to August 26 | August 28 | About October 9 | October 12 to November 13 | Supplier audit August 10 to 14; October 20 holiday; rains |
| 3 (15 rooms) | August 17 to September 25 | September 28 to October 7 | October 9 | About November 20 | November 23 to December 18 | December 12 holiday; rains; slack before January close |
Supporting work is dated backward from these windows. Kenyan hiring and solar licensing training start July 6, eight weeks before batch 1 installation. Work authorization for the two Columbus engineers is filed by July 15 for commissioning in early September. Kenyan data registration and the Pune contract's data clause are completed by August 14, before the first controller goes live. The university partner's food loss baseline at the 10 survey cooperatives runs in August, before any room arrives there. Firmware releases to installed rooms are blocked during Diwali week in early November.
How the Four Constraints Move the Same Dates
The handoff gap sets the start. Monterrey and Pune share no working hours, so every firmware question from assembly costs a day. The plan freezes firmware on May 29 and delivers it in a complete handoff package the morning assembly begins, June 1, instead of letting development overlap assembly. Without the freeze, a single week of back-and-forth would push batch 1's sailing past July 10 and its installation into the rains.
Certification adds seven working days after every batch. Because the certificate is issued per shipment, batches cannot be combined to save inspections without delaying the earlier rooms. Across three batches this adds about four weeks to the path, and it is the main reason batch 3 is installed during the short rains, when rural roads are slowest.
The supplier audit sits between batches 2 and 3. The Monterrey social audit is scheduled for August 10 to 14, after batch 2 assembly and before batch 3 begins. A serious finding would require correction within 14 days, and batch 3 assembly could slip from August 17 to about August 31, moving its installation window into late December. The plan protects against that with the one buffer the schedule has: about six weeks between the end of batch 3 installation and the project's close at the end of January.
The currency settlement dates are tied to assembly. The forward contract for the 40 percent peso payment settles on September 1 whatever happens, and the contract links that payment to completion of batch 2 assembly. Batch 2 is planned to finish August 7, three weeks before the payment date, so an ordinary slip does not leave Brightwell holding pesos it cannot yet pay out. The final 30 percent settles December 15, long after assembly ends on September 25.
Critical Path and Buffers
The critical path runs through batch 3: assembly, certification, sailing, clearance and installation, ending December 18. It has about six weeks of float to the January close, but the holiday season in Kenya and the Monterrey shutdown from December 24 mean the usable float is closer to four weeks. The December 18 last-shipment date identified in the context analysis is no longer binding, since the last sailing is October 9. The gap between them, ten weeks, is the plan's reserve against a failed audit or a delayed ship.
Cummings et al. (2009) found that coordination delays compound as work crosses more boundaries of time and place, and this plan has four sites and two oceans. The Project Management Institute's current guide treats the schedule as a model to be updated as conditions change rather than a fixed commitment (Project Management Institute, 2021). The plan will therefore be rebaselined at three points: after batch 1 sails, after the supplier audit and after batch 2 reaches Kenya. Each rebaseline will also recheck the currency hedge dates and the Kenyan hiring plan, since both were fixed to the current dates and would need to move with them. The cost of moving the June date was mostly avoided spending: hiring, work permits and data registration had been planned three months too early, and pushing them to July and August saves about two months of Kenyan payroll. Brightwell and every date in this plan are invented for the course.
References
Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the "planning fallacy": Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366-381. https://doi.org/10.1037/0022-3514.67.3.366
Cummings, J. N., Espinosa, J. A., & Pickering, C. K. (2009). Crossing spatial and temporal boundaries in globally distributed projects: A relational model of coordination delay. Information Systems Research, 20(3), 420-439. https://doi.org/10.1287/isre.1090.0239
Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK guide) (7th ed.). Project Management Institute.
The Herzing BU 436 Unit 8 instructions
The final unit of BU 436 asks students to combine the constraints studied during the course into one integrated project plan. Typical requirements are a schedule with key milestones, evidence that time zones, regulatory lead times, supplier activities and financial dates all appear in it, identification of the critical path and buffers, and an explanation of how constraints interact. Many instructors ask what happens where constraints conflict, and some expect the plan to correct earlier assumptions. Reusing earlier work is expected, but it must be reconciled rather than attached. A schedule table and a narrative explaining each constraint's effect are common, presented in APA 7, with a plan for when the schedule will be revisited.
Inside the BU 436 Unit 8 example
The plan begins with the main finding: combining constraints moved the first installation from June to the end of August. A table schedules three batches from assembly through certification, sailing and installation, with the constraint behind each date. Supporting tasks such as hiring, work authorization, data registration and the food loss baseline are then dated backward from the installation windows. A section explains how each of the four constraints moves specific dates, from the May 29 firmware freeze to the September 1 forward settlement. The final section identifies the critical path through batch 3, its usable float and the reserve created by an earlier last sailing, and sets three rebaseline points.
BU 436 Unit 8 rubric: what full points look like
Integrated plan rubrics at Herzing usually weigh schedule completeness, integration of constraints, critical path analysis, handling of conflicts and revision planning, with writing and APA. Schedule completeness earns credit when every major activity and supporting task has a date. Integration scores highest when each earlier constraint visibly affects specific dates rather than sitting in an appendix. Critical path analysis rewards identifying the longest path and the real float after holidays and shutdowns. Conflict handling is judged on whether the student shows where constraints collide and how the plan resolves them, including correcting earlier assumptions. Revision planning earns points for stating when and why the schedule will be rebaselined, since global plans change as conditions do.
Common BU 436 Unit 8 mistakes, and how to avoid them
Integrated plans often lose points by attaching earlier units as appendices without showing how they change the schedule. Another common problem is a timeline built forward from the start date that never checks lead times such as shipping or certification. Students frequently ignore holidays and shutdowns when calculating float. Some keep earlier dates that the combined constraints make impossible, rather than correcting them. Others name a critical path without explaining why it is critical. Plans also forget that financial dates, such as hedge settlements, are fixed even when work slips. Finally, a plan with no rebaseline points treats the first schedule as final, which rarely matches how global projects unfold.
Get a BU 436 Unit 8 example written to your instructions
Hand over the Unit 8 instructions and the BU 436 rubric your section uses, plus the earlier deliverables you are integrating. We write a custom example whose schedule carries location, handoff loss, permit duration, supplier qualification and settlement currency, with the collisions between them named and resolved. The first custom sample costs nothing and lands in 24 to 48 hours.
More BU 436 papers and project management samples
- BU 436 Unit 1: Global project context analysis
- BU 436 Unit 2: Communication and handoff plan
- BU 436 Unit 3: Decision rights and escalation
- BU 436 Unit 4: Regulatory and compliance analysis
- BU 436 Unit 5: Sustainability plan with costs
- BU 436 Unit 6: Supplier and procurement standards
- BU 436 Unit 7: Currency and financial risk
- BU 345 Unit 8: Project closeout file
- BU 396 Unit 8: Risk report to sponsor
- BU 433 Unit 8: Hybrid or scaling analysis
- BU 434 Unit 8: Traceability and validation plan
BU 436 Unit 8 questions, answered
How much of my earlier work should this reuse?
Reuse the substance and rewrite the presentation. The plan needs the locations, the obligations, the standards and the exposures you already established, but pasting whole sections in produces a document that repeats itself and never integrates. Carry the conclusions forward, cut the reasoning that got you there, and spend the space instead on where those conclusions now interact.
What if my constraints do not conflict anywhere?
Look again, because they almost always do. Check whether a holiday at one site sits inside a handoff chain, whether a certification lead time starts before a supplier has been qualified, whether a payment falls due while the approving office is closed. If after checking you genuinely find no collision, say so and show the checks you ran. An examined absence is credible; an unexamined one is not.
Could I hand in a plan modeled on a real project I worked on?
Model the shape, not the contents. The schedule your employer built, the supplier contracts underneath it, the compliance filings it depended on and the country operations data behind its estimates all remain that company's. Rebuild the project as a composite, state that in the opening, and let the assignment scenario supply the facts. The integration argument is what earns the marks anyway.
Where can I find a free BU 436 Unit 8 sample paper?
Nothing is charged for the entire BU 436 Unit 8 integrated global project plan above, which includes the batch schedule, the constraint analysis and margin notes. For your own project, share your instructions and a custom integrated plan is prepared free, generally within 48 hours.
What if my constraints in BU 436 Unit 8 do not conflict?
Look again at lead times and fixed dates. In the sample, shipping and certification together made an earlier installation date impossible, a conflict none of the separate analyses showed. If none truly conflict, explain how each still shapes the schedule.