3-1 Procurment Scheduling Brandon Meadows

3-1 Procurement Scheduling Brandon Meadows Southern New Hampshire University QSO 349: Project Contracting & Procurement January 22 nd , 2024

To create a successful schedule for a procurement project there is a few steps that need to be utilized. In procurement schedule inputs need to make sure the scope of the work is completely easy to follow and properly defined. With the case study for Harley Davidson Motor Co., they have gone with upgrading their software which best suits their needs as a company and is affordable. The table below shows what the work breakdown structure (WBS) will point out activities required to ensure procurement is successful. WBS Task Description 1.1 Supply Management Supply begins 1.1.1 Initial SiL’K planning meeting 1.1.2 Value presentation to Purchasing Leadership Group 1.1.3 “Let’s get wild” brainstorming session 2.1 Allocation of resources from purchasing to form the SiL’K project team 2.1.1 Mapping “as is” procurement process; identification of commodities across sites 2.2 Developing “to be” processes; systems team engaged 2.2.1 Change management communication to the stakeholder community 2.3 Completion of Functional

Leadership Group 1.1.3 “Let’s get wild” brainstorming session 1.1.2 30 Days Fall 1997 2.1 Allocation of resources from purchasing to form the SiL’K project team 1.1.3 24 Days November 1997 2.1.1 Mapping “as is” procurement process; identification of commonalities across sites 2.1 79 Days 11/02/1997-03/01/1998 2.2 Developing “to be” processes; systems team engaged 2.1.1 127 Days 04/1998-09/1998 2.2.1 Change management communication to the stakeholder community 2.1 ongoing 05/1998-ongoing 2.3 Completion of Functional Specification (RFQ); Distribution to internal stakeholders for review 2.2 7 Days 09/30/1998-10/09/1998 2.3.1 Feedback from internal stakeholders 2.3 4 Days 10/09/1998-10/16/1998 3.1 Distribution of RFQ and invitation to bid to selected software providers 2.3.1 6 Days 10/16/1998-10/25/1998 3.1.1 Software providers confirm the intention to bid 3.1 8 Days 10/25/1998-11/05/1998 3.1.2 Software Provider Conference 3.1.1 6 Days 11/05/1998-11/16/1998 3.2 Proposals due form potential software providers 3.1.2 10 Days 11/16/1998-12/01/1998 3.2.1 Formal presentation of proposals to Harley-Davidson 3.2 3 Days 12/01/1998-12/04/1998 3.2.2 Review of proposals and presentations 3.2.1 4 Days 12/07/1998-12/11/1998 3.3 Shortlist selection of three potential providers 3.2.2 19 Days 12/11/1998-01/10/1999 3.3.1 Two-day presentations and scripted demonstrations at shortlisting providers’ sites, and reference checks with installed customers 3.3 8 Days 01/10/1999-01/22/1999 3.3.2 Finalist selection 3.3.1 6 Days 01/30/1999 (Austin et al.’ 2003).

The direct success or failure of a project can sometimes be traced back to your procurement schedule. A properly created procurement schedule gives your team a necessary road map to follow. It provides the project team with each of their resource assignments, the proper amount of work effort that is needed as well as the expected start and end date for each subject. It can also be used as a tool to help with estimating and budgeting for larger projects as it helps a project team monitor the entire procuring process (Lindstrom, 2015).