Grouping an Omaha installer's entire workload into seven end-to-end processes, this MT400 Unit 2 process architecture outline cross-references each one to APQC categories. Searches like "mt 400 unit 2 assignment example", "mt400 unit 2 sample" and "mt400 unit 2 example" land here.
What a finished MT400 Unit 2 process architecture outline looks like
Five pages plus a one-page diagram. The diagram is a level-zero process map in three bands: three core processes (lead to contract, contract to cash, service request to resolution), three enabling ones (source to pay, recruit to certified installer, record to report) and one managing process, plan to review. A table follows with a row per process giving its triggering event, its end state in the receiver's terms, the departments it crosses and the APQC Process Classification Framework categories it draws on, such as 3.0 Market and Sell Products and Services and 6.0 Manage Customer Service. Contract to cash then receives a level-one breakdown into six subprocesses, measure through collect. A crosswalk grid marks which of Ridgeway's eleven departments touches which process, and the shaded cells make the handoffs visible at a glance.
How a MT400 Unit 2 example is structured
The outline reasons from outside in. It begins with the parties Ridgeway serves and the outcomes each expects, then asks which chains of work deliver those outcomes, so no process is named for a department. Boundaries are set by events: contract to cash starts when a homeowner signs and ends when the final payment clears, whatever departments sit between. The framework cross-reference comes next and is handled with care, because the APQC framework classifies work into categories, process groups, processes, activities and tasks rather than drawing flows; each end-to-end process therefore draws on several categories at once. Decomposition stops at level one on purpose, since mapping detail belongs to the handoff work later in the term. The crosswalk closes the outline and sets up prioritization by showing contract to cash touching seven departments, more than any other process.
Who Ridgeway serves
Homeowners, the financing company, window manufacturers and installers themselves, each with the outcome a process owes them written as a finished state.
A level-zero map in three bands
Core, enabling and managing processes on a single page, named as verb-to-noun pairs so every label states where the work begins and where it ends.
Events at both ends
A table of triggers and end states, including the rule that contract to cash closes on cleared payment rather than on installation.
APQC categories drawn on
Framework references for each process, with a note that the classification lists work by category while the outline follows it across categories end to end.
Contract to cash, level one
Measure, configure and release, receive and stage, install, close out and collect, each with the departments that perform it.
The department crosswalk
Eleven departments against seven processes, shaded where each touches each, with the heaviest row flagged for the matrix that follows.
Where marks go in MT400 Unit 2
An organization chart with arrows drawn between its boxes is not an architecture, and graders deduct heavily for it, because each box still stops at a department's edge. Process names are graded more closely than many writers expect; a label such as installation names a function, while contract to cash names a flow with a beginning and an end. Instructors frequently check that every process has a triggering event and an outcome stated from the receiver's side. Framework references earn credit when they are accurate and lose it when a writer claims the APQC framework itself draws end-to-end flows. Forty level-one entries cannot be managed as a portfolio, and deep decomposition spends pages the rubric saves for later units. A missing crosswalk leaves the handoffs asserted rather than shown.
Get a MT400 Unit 2 example written to your instructions
Architecture outlines depend on the organization described, so the free first custom sample starts from the case in your Unit 2 prompt and the rubric attached to it. Expect process names, event boundaries and framework references within 24-48h, drawn in the framework version or drawing tool named for your section, with a crosswalk showing where departments meet.
MT400 Unit 2 questions, answered
How many processes should an MT400 architecture outline name?
Few enough to manage as a set, which for a mid-size organization means somewhere between five and twelve end-to-end processes at the top level. The sample names seven. If your prompt describes a larger organization, group related chains rather than listing every activity, and keep deeper breakdown for the process your later units will analyze.
Do I have to use the APQC Process Classification Framework?
Only if your prompt asks for it, though it is a common reference. It classifies work in a hierarchy of categories, process groups, processes, activities and tasks, which makes it useful for checking that nothing is missing. It does not draw your organization's end-to-end flows, so the outline still has to assemble those itself.
Is a level-zero process map the same as a BPMN model?
No. A level-zero map shows the processes an organization runs and how they group, often on one page with no step detail. BPMN 2.0 models the steps, events, gateways and handoffs inside a single process. Many sections expect the one-page map at this stage and a BPMN model later, when one priority process is analyzed.