IBF 5070 Module 5 Written Assignment: Break-Even Prices and Scenarios for the Solar Project Example

Reviewed by Edgar Pennington, MBA Thomas Edison State University Updated October 2026

This IBF 5070 Module 5 example answers the written assignment on break-even and scenario analysis in Financial Modeling, part of TESU's MBA in Finance. IBF-5070 asks in this module how models find the value of an input at which a project just breaks even and how scenarios that change several inputs together show a range of outcomes. Both are applied to the 60 MW Cumberland farm. It computes the break-even contract price, generation and construction cost, builds downside and upside scenarios, and explains how management should use the results in negotiating the power contract and the construction agreement. Each break-even is converted into room for error, so inputs measured in dollars, megawatt-hours and watts can be compared.

CourseIBF-5070 Financial Modeling
ModuleModule 5
Paper typeModule 5 written assignment: break-even and scenario analysis
LengthAbout 594 words, 5 pages
FormatAPA 7 student paper
SchoolThomas Edison State University
ProgramMBA in Finance
UpdatedOctober 2026

Free sample paper for IBF 5070 Module 5

1

How Much Room Is There? Break-Even and Scenario Analysis for the Cumberland Solar Project

Student Name

MBA in Finance, Thomas Edison State University

IBF-5070: Financial Modeling

Mentor Name

Month Day, Year

What this page is doingThe title states the question break-even analysis answers, how far the assumptions can move before the project stops creating value.
2

How Much Room Is There? Break-Even and Scenario Analysis for the Cumberland Solar Project

Introduction

Module 4 found that the Cumberland project's NPV of about $3.1 million could be erased by any one of several realistic changes. Sensitivity tests move one input; break-even finds how far it can move before value vanishes; scenarios move several together. Bodmer (2015) describes break-even values as a way to turn uncertainty into specific targets, which suits a project about to enter negotiations. Each technique answers a different question, and together they show management where it has room to negotiate and where it does not, before any probabilities are attached in the next module.

Break-Even Values

Break-even values were found by solving the model for an NPV of zero at 7 percent, changing one input while holding the rest at the base case.

The project has less than 5 percent of room on its two main revenue drivers. The independent engineer's P90 estimate is 7 percent below P50, so a P90 outcome alone would destroy value. Construction cost has the most room, about $7 million on a $94 million budget.

InputBase caseBreak-evenRoom for error
Contract price, first year$70.00 per MWh$66.72 per MWh4.7%
GenerationP50, 110,376 MWh3.7% below P503.7%
Construction cost$1.20 per watt$1.28 per watt6.3%
What this page is doingExpressing each break-even as room for error, a percentage from the base case, makes inputs with different units directly comparable.
3

Scenarios

Scenarios combine changes that could plausibly occur together. A downside scenario combines P90 generation, construction costs 10 percent over budget and market prices after the contract 30 percent below the base case. An upside scenario combines generation 5 percent above P50, construction costs 5 percent under budget and market prices 20 percent above the base case.

The downside loss is larger than the upside gain from the base case, about $15.4 million against $10.2 million. This asymmetry arises because the downside scenario's changes are larger, reflecting the view that cost overruns and weak output are more likely to be severe than their favorable counterparts. Graham and Harvey (2001) found that more than half of the chief financial officers they surveyed used sensitivity or scenario analysis when evaluating projects, which reflects how seldom a single estimate is trusted.

ScenarioNPV at 7%, $ millionsAfter-tax IRR
Downside(12.4)4.7%
Base case3.17.5%
Upside13.39.0%

Examining the Output

The scenarios do not say how likely each outcome is; that question is for Module 6. What they do show is that the project's value depends heavily on factors Bayshore can partly control. Two actions follow. First, Bayshore should seek a contract price of at least $72 per MWh, which would raise base-case NPV by about $1.9 million, to about $5.0 million, and widen the room for error on price to about 7 percent. Second, it should sign a fixed-price construction contract at or below $1.20 per watt, removing most of the construction risk in the downside scenario.

Limitations

Break-even analysis holds every other input at its base value, which can be misleading when inputs are related. Scenarios capture relationships, but their choice is a judgment, and a downside that is not severe enough gives false comfort. Hertz (1964) argued that single-point estimates and a few scenarios hide the full range of outcomes, the case for the probabilistic analysis in the next module.

Conclusion

The Cumberland project breaks even at a contract price of $66.72 per MWh, generation 3.7 percent below P50 or construction at $1.28 per watt. A combined downside would cost about $12 million of value. Management should negotiate a contract price of at least $72 and a fixed-price construction agreement before committing.

References

Bodmer, E. (2015). Corporate and project finance modeling: Theory and practice. Wiley.

Graham, J. R., & Harvey, C. R. (2001). The theory and practice of corporate finance: Evidence from the field. Journal of Financial Economics, 60(2-3), 187-243. https://doi.org/10.1016/S0304-405X(01)00044-7

Hertz, D. B. (1964). Risk analysis in capital investment. Harvard Business Review, 42(1), 95-106.

What the IBF 5070 Module 5 instructions ask for

The fourth IBF-5070 written assignment asks you to apply break-even and scenario analysis to a financial model. You solve for the input values that bring NPV, or another target, to zero, build scenarios that move several inputs at once and explain the decision they point to. Use your spreadsheet's goal seek or data table functions and report the results in tables. State how you chose each scenario's changes, since a scenario is only as useful as its assumptions. Close with what management should do in light of the analysis, such as targets for negotiations. If your model's output is not NPV, apply the same ideas to the measure that matters, such as a coverage ratio or an equity return. Explain how the result would change if the input you solved for moved together with another.

How this IBF 5070 Module 5 example is built

The paper links back to the sensitivity results from Module 4. A break-even table reports the value of each input at zero NPV and converts each to a percentage of room for error. A scenario section defines downside and upside cases and reports their values and returns, explaining the asymmetry. An output section turns the results into two negotiating targets with their effect on value. A limitations section explains what break-even and scenarios cannot show, citing early research on risk analysis, and sets up the probabilistic module. The tables report each break-even and scenario result in the same units as the base case, which makes comparison immediate. The recommendations quantify their effect on value, so management can see what each negotiating target is worth in dollars.

Where the marks sit in the IBF 5070 Module 5 rubric

Mentors grade this assignment on correct break-even calculations, well-reasoned scenarios, clear interpretation of the output and practical recommendations. Answers that express break-evens in comparable terms, and that explain why scenarios are built as they are, show understanding. Turning results into specific actions, such as a contract price target, demonstrates judgment. Recognizing the limits of each technique earns credit and prepares for the next module. Survey evidence on how companies use these tools adds support from research. Mentors also check that break-even values were solved correctly, which a reader can test by noting that NPV at the break-even input should be zero. Papers that report results in both dollars and percentages make it easy to compare inputs measured in different units.

IBF 5070 Module 5 help: mistakes that cost marks

Students lose points by reporting break-even values without saying what they mean, by building scenarios that change inputs arbitrarily or by treating scenario results as probabilities. Explain the room for error each break-even implies. Base each scenario on a story of what could happen together. Say what the scenarios do not tell you. End with actions management can take, and quantify their effect on value where you can. Use the spreadsheet's goal seek for single break-evens and a data table for ranges, and say which you used. A free first sample on your own IBF-5070 Module 5 model is available on request.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official Thomas Edison State University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.

More IBF 5070 and MBA in Finance sample papers

IBF 5070 Module 5 questions, answered

Where can I find a free IBF 5070 Module 5 sample paper?

Break-even prices and downside and upside scenarios for the solar project are worked above.

What is break-even analysis in a financial model?

Finding the value of an input at which the output, such as NPV, equals zero, holding other inputs constant.

How does scenario analysis differ from sensitivity analysis?

Sensitivity changes one input at a time; scenario analysis changes several inputs together to reflect a plausible story.

Do scenarios show how likely an outcome is?

No. Scenarios show possible outcomes; probabilistic analysis is needed to estimate their likelihood.

How can break-even results guide negotiations?

They show the price, cost or volume a deal must achieve for the project to create value, which can be set as targets.