| Course | PM FPX 4070 Procurement Management in Project Management |
|---|---|
| Assessment | Assessment 2 |
| Paper type | Statement of work |
| Length | About 1,110 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Business, Project Management |
| Updated | September 2026 |
Free sample paper for PM FPX 4070 Assessment 2
A Statement of Work for a Veterinary Hospital's Network and Phones: Deliverables Numbered and Defined, Acceptance Criteria Written as Tests, Exclusions That Do Work, Standards Named, No Adjectives Doing Contractual Work, and a Change Procedure
Student Name
Capella University
PM FPX 4070: Procurement Management in Project Management
Instructor Name
Month Day, Year
Background and Purpose
Maple Ridge Animal Hospital is moving into a renovated building and has chosen to buy, rather than self-perform, the installation of its network, wireless, phones, and workstation setup. This statement of work defines what the vendor will deliver so that the vendor can price it and the practice can accept or reject it. The Project Management Institute (2017) describes the procurement statement of work as a description of the item to be purchased in enough detail to let prospective sellers determine whether they can provide it.
Deliverables Numbered and Separately Defined
D1, horizontal cabling: 64 Category 6 data drops at the locations shown on drawing E-4, each terminated at both ends and labeled with a room and port number matching the drawing. D2, network equipment: one firewall, two 48-port switches with power over Ethernet, and 12 wireless access points at the locations on drawing E-4, installed in the existing equipment rack in room 118 and configured with the practice's existing network addressing. D3, wireless network: two networks, one for staff and one for guests, isolated from each other. D4, phone system: 28 desk phones, a cloud phone service with the practice's existing main number ported, an automated attendant with the call flow in Attachment A, and three hunt groups. D5, workstations: 26 existing workstations moved from Elm Street, reconnected, and tested with the practice management system; 4 new workstations imaged with the practice's standard image. D6, documentation: an as-built drawing showing every data drop and access point, a port map, network configuration backup, and administrator credentials delivered in a sealed envelope to the practice manager. D7, training: two one-hour sessions for front desk staff on the phone system.
Acceptance Criteria Written as Tests
Each deliverable is accepted when it passes a stated test. D1: every drop passes a Category 6 certification test with a certified tester; the vendor provides the test report for all 64 drops. D2: the firewall passes traffic to the internet at the contracted service speed; each switch port tested with a laptop. D3: a wireless survey shows signal of minus 67 dBm or stronger in every room listed in Attachment B; guests cannot reach staff devices, tested from a guest device. D4: test calls to and from each extension, each hunt group, and the main number; the automated attendant routes each option as specified. D5: each workstation logs into the practice management system and prints to its assigned printer. D6: the practice manager confirms receipt and that the drawing matches a physical check of 10 randomly chosen drops. D7: attendance recorded; each front desk staff member transfers a call and retrieves a voicemail. A test either passes or it does not. "Performs well" is an argument waiting to happen.
An Exclusions List That Does Work
The vendor is not responsible for electrical power circuits, which are provided by the general contractor. The vendor is not responsible for the internet service line, which the practice has ordered from its carrier. The vendor is not responsible for the practice management software or its data. The vendor will not replace the 26 existing workstations. The vendor will not provide ongoing managed services after the 90-day warranty unless contracted separately. The vendor will not install cabling outside the building.
Standards Named, Never Implied
Work must meet these named standards: cabling installed and tested to the Telecommunications Industry Association standard for balanced twisted-pair cabling, ANSI/TIA-568.2-D, for Category 6; electrical and low-voltage work in compliance with the National Electrical Code as adopted by the city; wireless access points supporting the IEEE 802.11ax standard; and labeling that matches drawing E-4. Naming standards means the vendor cannot substitute its own idea of good practice.
No Adjectives Doing Contractual Work
The document avoids terms like "high-quality," "robust," "adequate coverage," and "industry-leading." Where a quality is required, it is stated as a measure: a signal strength, a test result, or a standard.
Schedule and Site Conditions
Work occurs during weeks 31 to 33 of the project schedule, after the general contractor completes finishes in each area. The vendor will coordinate access through the practice manager and the contractor's superintendent.
A Change Procedure Inside the Document
Changes to deliverables, quantities, or schedule require a written change request from either party. The vendor prices the change within three business days. Changes up to 5,000 dollars may be approved in writing by the practice manager; larger changes require the practice owner's signature. No change work begins until approved in writing. Unit prices in Attachment C, such as per additional data drop, apply to quantity changes.
Roles and Contacts
The practice manager is the practice's single point of contact for the vendor and approves acceptance. Tyler Grant, the practice's IT coordinator, reviews technical submittals and witnesses tests. The vendor names a project lead who attends the weekly site meetings during installation and is the vendor's single point of contact. Naming contacts in the statement of work avoids instructions arriving from several people.
Submittals Before Installation
Before installation, the vendor submits the network configuration plan, the phone call flow as it will be built, and the wireless coverage design for review. The practice responds within three business days. Submittals do not change the deliverables; they confirm how the vendor will meet them.
Working Conditions
The vendor works on site between 7:00 a.m. and 6:00 p.m. on weekdays, coordinates with the general contractor for access to finished rooms, protects finished floors and walls, and removes its own packaging and debris daily.
Reporting During Installation
During weeks 31 to 33, the vendor reports daily by email to the practice manager with the number of drops installed and certified, equipment installed, and any problems or access delays. A short daily report catches issues while there is time to fix them within the three-week window.
Warranty
The vendor warrants workmanship for 90 days after acceptance and will respond to failures within one business day, on site if the failure cannot be fixed remotely. Equipment manufacturers' warranties pass through to the practice, and the vendor registers each item in the practice's name.
Conclusion
The statement of work numbers seven deliverables, attaches a pass-or-fail test to each, lists exclusions that answer likely disputes, names the cabling, electrical, and wireless standards, avoids adjectives in contractual terms, and sets a change procedure with approval limits and unit prices.
References
Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK guide) (6th ed.). Project Management Institute.
What the PM FPX 4070 Assessment 2 instructions ask for
Assessment 2 in PM FPX 4070 has you write the statement of work for the component you decided to buy. You give brief background and purpose, list and define each deliverable, set acceptance criteria that can be tested, state what is excluded, name the technical and industry standards that apply, describe the schedule and site conditions, and include a procedure for changes. A vendor should be able to price it from the page alone, and a dispute should be settled by reading it. Procurement texts and sample federal statements of work support the document.
How this PM FPX 4070 Assessment 2 example is built
The document is ordered the way a supplier reads it when deciding whether to bid. Background and objective come first and stay short, because a vendor needs context, not history. Scope follows immediately, with the inclusions stated and then the exclusions stated, since the second list is what a reader checks for. Deliverables occupy the center of the document and are numbered so that a change request can point at one of them. Each carries its acceptance criteria in the same place, rather than in a separate quality section that nobody cross-references. Schedule and milestones follow the deliverables, tying each numbered item to a date or a dependency. Standards, personnel and performance obligations come next, then reporting and governance. Assumptions, constraints and the change procedure close the document, because those are the sections a dispute is argued from.
Reading the PM FPX 4070 Assessment 2 scoring guide
The scoring guide rewards a statement of work a vendor could price without calling. Deliverables reach Distinguished when numbered and defined separately. Acceptance criteria score higher when written as tests, such as every phone registering on the system and completing a call. Exclusions earn credit when they settle likely disputes. Standards are judged on whether they are named, like a specific cabling standard. Language should avoid adjectives such as "high quality" that cannot be enforced, replacing each with a measure. The change procedure should sit inside the document, stating how a change is requested, priced and approved. Distinguished statements leave little room for disagreement.
PM FPX 4070 Assessment 2 help from the desk
Statements of work often describe the desired result in marketing language, like "a robust, modern network," which cannot be enforced. Another weakness is combining deliverables into one paragraph, so it is unclear what was delivered. Acceptance criteria are missing or subjective. Exclusions are absent, so the vendor assumes some things are included and the client assumes others. Standards are implied rather than named. The change procedure is left to the contract, so the first site surprise turns into an argument about who pays. Numbering each deliverable with its own acceptance test, and replacing every adjective with a measurable requirement, makes the document enforceable and supports the procurement plan in Assessment 3.
Get a PM FPX 4070 Assessment 2 example written to your instructions
Send us the Assessment 2 instructions and the scoring guide from your PM FPX 4070 courseroom, plus the scenario and whatever the project has decided to purchase. We produce a custom example to those criteria, numbered, with acceptance criteria on every deliverable and an exclusions list that holds, and return it in 24 to 48 hours. First sample free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More PM FPX 4070 papers and BS in Business, Project Management samples
- PM FPX 4070 Assessment 1: Make-or-Buy Analysis
- PM FPX 4070 Assessment 3: Procurement Plan
- PM FPX 4080 Assessment 2: Sprint Plan
- PM FPX 4060 Assessment 2: Risk Register
- PM FPX 1000 Assessment 2: Life Cycle Overview
- PM FPX 4050 Assessment 2: Communications Plan
PM FPX 4070 Assessment 2 questions, answered
What is the difference between a statement of work and a scope statement?
A scope statement describes what the project will produce for its own sponsor. A statement of work describes what a supplier will deliver to the project, under terms that can be enforced. The audience changes, and so does the language: internal scope can carry intent, while a supplier document has to survive somebody reading it looking for room.
How specific do acceptance criteria need to be?
Specific enough that two people could apply them and agree. A criterion such as passes the documented test cases with no severity one defects outstanding works, while meets business needs does not. Where a deliverable is a document rather than a system, define acceptance by review, by named approver and by the number of revision cycles included in the price.
Does this assessment need academic sources?
Most sections do expect them, even though the artifact is a working document. Procurement literature or a recognized standard usually sits behind the structure you chose, cited in current APA form in the introduction or a short rationale section. Check your instructions for the number required. The numbered document itself stays clean, with citations kept out of the clauses.
Where can I find a free PM FPX 4070 Assessment 2 sample paper?
The complete statement of work for the network and phone installation is here, with numbered deliverables, acceptance criteria written as tests, exclusions that do work, named standards and a change procedure.
What is the difference between a statement of work and a scope statement in PM FPX 4070 Assessment 2?
A scope statement describes the whole project for the team. A statement of work describes only the part being bought, written for a vendor who will price and deliver it.