This manual is for MHA-FPX5016 Assessment 2, start to submission. Assessment 2 is the decision deliverable, and the assessment usually hands you a system, a proposed replacement or a shortlist and asks which one an organization should choose and why, which means weighted requirements fixed before anybody scored anything and a cost model containing the lines no vendor quotes. Decision criteria fail on missing arithmetic, so here the numbers are the paper. The rest of this manual is the method, a criterion-mapped structure and an annotated sample excerpt. Prefer somebody else built the model? A premium original sample for this assessment returns inside 24 to 48 hours, with revisions free until the guide is satisfied. Your courseroom may print this as MHA FPX 5016 Assessment 2 or MHA5016 Assessment 2; it is the same deliverable, and MHA-FPX5016 Assessment 2 is what this manual walks through.
One honesty note before the manual: Capella revises courses and scoring guides over time, so always write to the exact scoring guide attached to your assessment in the courseroom. The course identity above is verified on capella.edu; the method and structure below are our tutors' approach to it, not Capella's official rubric text.
How MHA-FPX5016 Assessment 2 is scored
Four levels per criterion, no letter grade, and the descriptions do double duty as an outline. Read them as the specification for the section you are about to draft:
| Level | What it means on a system evaluation and recommendation |
|---|---|
| Distinguished | Weights are set and attributed before any score exists, every cost input is marked sourced or assumed, and the recommendation says what would change it. The top level asks for something the one below does not; locate that clause and satisfy it on the page. |
| Proficient | The evaluation is complete and the recommendation follows from it. Sound work, quiet about how much the answer depends on the weights. |
| Basic | A comparison table with scores nobody can trace and a cost figure that is really a license quote. It looks finished and cannot be audited. |
| Non-performance | A required part of the analysis is missing, most often the cost of ownership or the requirements themselves. There is no partial credit for a section that is not there. |
Everything in this deliverable turns on whether a stranger could rebuild your conclusion from what is printed. Show the weights, show the inputs, show the assumptions, and the recommendation carries itself.
The MHA-FPX5016 Assessment 2 method, step by step
-
Write the requirements before you look at a product
State what the organization needs the system to do, in language a demonstration could pass or fail. A requirement nobody can test is a preference. Then weight the list, record who set the weights and on what date, because weights chosen after a demonstration will always match whoever presented best.
-
Build the cost model from the lines nobody quotes
License is the smallest interesting number in the model. Add implementation, interfaces, annual maintenance as a percentage of license, training hours taken out of production, temporary cover across go live, the parallel run, and the internal analysts who will support the platform for five years. That last line is frequently the largest one on the page.
-
Source or label every input
Certification listings, awarded public procurement contracts, published requests for proposals and trade reporting supply real figures for a model nobody will let you quote for. Mark each input sourced or assumed, print a range rather than a false point estimate, and a transparent model built from public numbers will outscore a confident one nobody can check.
-
Score, then interrogate the margin
Multiply, total, rank, and then ask whether the gap between the top two options is larger than the noise inside your own exercise. Where it is not, say so, name the two requirements that genuinely decide the choice, and state the evidence that would settle them. Reporting a narrow total as though the arithmetic decided is the commonest way to lose the analysis criterion.
-
Test the weights before you defend the answer
Move the heaviest weight up and down by five points and watch whether the winner changes. If it does, your recommendation is a statement about your weighting rather than about the products, and writing that into the document is worth far more than hiding it.
-
Write the recommendation as a decision, then submit early
Name the choice, the conditions attached to it, the approval path and what would reverse it. Then submit with time left, since faculty have two business days and a cost model always needs one more pass once somebody else has read it.
A structure that maps to the criteria
Treat the figures below as planning targets our tutors use for a typical 5016 evaluation, not as Capella limits; the section your guide weights heaviest should be the longest one you write.
| Section | What it must do | Guide |
|---|---|---|
| Decision and context | The organization, what is wrong with the current arrangement, and the choice being put to a committee. | ~150 words |
| Requirements and weights | Testable requirements, the weights applied, who set them and on what date. | ~250 words |
| Option analysis | Each option scored against the requirements, with the reasoning behind any score that decides the outcome. | ~300 words |
| Cost of ownership | Every cost line across the horizon, each marked sourced or assumed, internal support included. | ~300 words |
| Risk, implementation and sensitivity | What could go wrong, the rollout sequence, and what happens to the answer when the weights move. | ~250 words |
| Recommendation and references | The decision, its conditions, what would reverse it, and current APA matched both ways. | ~200 words |
Annotated sample excerpt
One original worked paragraph from our writers, built to show how the arithmetic should look on the page. Learn the structure from it and rebuild it around your own figures.
Replacing the laboratory system across the reference laboratory and both hospital laboratories is quoted at $410,000 in licenses, $265,000 in implementation and four interfaces at $24,000 each, which is $771,000 before the organization has run a single specimen through it.1 Maintenance at 18 percent of license adds $73,800 a year, and supporting the platform internally takes an estimated 1.8 analyst positions at $99,200 fully loaded, so the five year total reaches $1,777,000 and the license everybody argued about is 23 percent of it.2 Every figure above is either taken from a published procurement award for a comparable installation or flagged as an assumption in the model workbook, and the two assumptions that matter, the analyst count and the maintenance percentage, are the ones the sensitivity table moves.3
- 1The arithmetic is shown rather than summarized, so a reader can check the addition without asking anybody for the workbook.
- 2The internal support line is included and then set against the license, which is the comparison that changes how a committee reads the entire proposal.
- 3Sourced inputs are separated from assumed ones and the assumptions that decide the total are named. These amounts are constructed to illustrate the shape of a five year model.
The full premium sample for your exact assessment, written fresh to your scoring guide and issue, is free to request. Study it, revise it into your own voice, and submit work you understand.
The five mistakes that cost Distinguished
- Weights set after the demonstrations. Scores that quietly reward whichever vendor presented last, with nothing in the document showing when the criteria were fixed.
- The license quote called the cost. A total with no maintenance, no interfaces, no training and no internal staffing, understating the commitment by a factor of four or five.
- A margin treated as a verdict. Reporting a tenth of a point between two products as though the model had decided, when the exercise cannot resolve a gap that small.
- Unlabeled inputs. A cost table where sourced figures and invented ones look identical, which makes the whole model unusable to a reviewer.
- No sensitivity anywhere. A recommendation that never says which assumption it rests on, so nobody learns what would change the answer.
Pre-submission checklist
- Requirements written so a demonstration could pass or fail each one
- Weights recorded with an owner and a date, fixed before any scoring began
- Every cost line present and marked sourced or assumed, internal support included
- The margin between the leading options interrogated rather than simply reported
- One sensitivity run printed, with the assumption it turns on named
- Self-scored on each criterion, current APA both ways, submitted with revision time left
System recommendation due?
Send the guide, the shortlist and any pricing or workflow detail you can share. We build the requirements matrix with dated weights, a cost model whose every line is labeled, and a sensitivity run, returned as a premium original sample inside 24 to 48 hours with free revisions until the criteria clear.