Today’s post is from our archive at SafeSourcing.

Last week we covered the key components in setting up and running a pilot event for a new procurement process or with a 3rd party strategic sourcing partner.  Once you have completed your pilot and moved forward into a roll-out or contract situation the next key step is to develop a Standard Operating Procedure document and strategy so that events can begin with a similar structure each time and adjusted from there.  Today we will be taking a look at some of the pieces that you should consider when creating this document.

Process Overview – The foundation of the SOP document begins with an explanation of the process and why the company has chosen to make the changes supporting this document.  Frequently this will include some language form the executive team showing their support of the process.  In the overview you will want to define the main groups that will be involved and the level of sponsorship and management to be included in each project for its success.  Research, communication, project management and a subject matter expert will all be key pieces to consider.

Project checklist – The project checklist will be the basis from which the expectations of the projects will be tracked.  Key components need to include a detailed breakdown of each stage of the project.  Associated with each activity will be an owner of the step, an estimated duration for completion, and a begin and end date for the item.  Many companies will use a project planning software package to assist with this process or at least a spreadsheet which will track and project the timeline milestones.  The project checklist also provides departments new to the process a view of what they will be expected to be responsible for.  This allows them to budget their time and prevents tasks from slipping through the cracks.

Template Documents – When new processes get introduced to the rest of the company it is very important as stated above to provide departments with as much detail about the process upfront as possible.  While the event checklist will help, one of the other key components of this package is to provide the stakeholders with some template documents to start with.  These documents include suggested notifications to internal resources and external suppliers, RFx templates for goods, services and software, suggested scorecard templates and supplier presentation template agendas and scorecards if that step is one included in the project.  These documents provide value to your internal stakeholders because it does not require them to start from scratch and can shorten project timelines.

Whether you are just starting a new process or improving a procurement you have had in place for years, developing a Standard Operating Procedure package that can be shared with other departments can ensure success for future projects and increase the confidence they have with your procurement team.  For more information on how SafeSourcing can assist with structuring standard operating procedures for these projects or on our “Risk Free” trial program, please contact a SafeSourcing Customer Service Representative.  We have an entire customer services team waiting to assist you today.

We look forward to your comments

Today’s post is an excerpt from a White Paper titled RFX Strategies for Success  SafeSourcing.

The world of procurement is continually changing, and this includes the world of e-procurement when it comes to the requirement for information, a proposal, or a quote.  The differences between the three requests, what expectations are when receiving the requests back, and how to make a sound business decision with what has been presented are what separate each stage in giving procurement professionals a blueprint on where to start in the process.

The Request for Information (RFI)

A request for information (RFI) is a request made typically during the project planning phase where a buyer cannot clearly identify product requirements, specifications, and purchase options. RFIs clearly indicate that award of a contract will not automatically follow.1

An example for a use of a RFI would be if a company acquired a used warehouse that need to be turned into a distribution center. It has some racking installed but needs more.  There has not been a defined idea of what  layout will be needed to improve the warehouse for DC use, nor what types of rack are needed, how much material is needed, nor how long it will take to install the racking. The existing racking is in adequate shape but it is unknown whether it is safe, placed appropriately, outdated, or even needed. This situation often is a good time to rely on experts to provide feedback as to these needs.  The best practice is to get at minimum of  three (3) but I’d recommended getting 4 to 6, submissions from your requests for information from racking manufactures, distributor, and/or installers.

The higher supplier count, in an area where you have no knowledge, provides the data to begin to make more decisions from multiple perspectives. With at least 3 it begins to become more clear to see if there are major differences between suppliers and how they operate.  Lead time, outsourcing, geographical coverage are all very important pieces of information to gather from the suppliers at this stage.

The application of an RFI can be used on new goods for use, re-sale, packaging design, any and all services, software, hardware, equipment of any kind, actually it is limitless as to what you can utilize a RFI for in business.

If you’d like more information as to how to use the three unique steps of the eRFX process at your company, please contact a SafeSourcing customer services representative.

We look forward to and appreciate your comments.