News on the Cover

Navigating Through the RFP/PO Process
Is automation the only answer?

Striving to simplify a convoluted request-for-proposal and purchase order process polluted by financial and legal straits, as well as a "sacred cow" mentality, can be a monumental task for even the most seasoned materials management professional.

Ask anyone in this technocentric era for tips on how providers can reform and simplify their PO and RFP structures without sacrificing any financial and legal protections and still get the information they need to make an effective buying decision and you’ll likely hear the same refrain: Automate the process and do them electronically. Not that there’s anything inherently wrong with such a logical response but it’s akin to the whimsical doctor’s advice of "take two aspirin and call me in the morning."

Not everyone agrees, of course. "I don’t think you can separate [simplification] from electronics," said Ruth Holman, R.N., clinical resource manager of materials management at Bloomington (IN) Hospital and Healthcare System. "Technology will be a big part of the improvements."

To an extent, Holman’s right, but she acknowledged that there may be no way around the detailed nature of the content needed. "I think society drives the complexity," she noted. "Everyone has to have all the bases covered for their own protection, whether I am selling the product or buying it."

Using electronic data interchange (EDI) or online capabilities via the Internet or the World Wide Web certainly can speed up an otherwise mundane process but it does very little to justify all the content included in the RFP and PO documents that seem to make them as complicated as the federal tax code.

Diagnosis: The challenges and complications
Admittedly, providers and suppliers alike are hamstrung by a host of legal and financial requirements (read: terms and conditions) designed to protect one another from fraud and abuse, as well as ensure that service level commitments are met.

"The whole point of an RFP is to make sure there’s nothing funky going on with a supplier and to make sure that supplier has the best interests of the customer in mind," said Joe Colonna, president and CEO of Strategic Initiatives in Healthcare (Jackson, NJ). "Really, it’s so the facility doesn’t get sued. What we really need is a strong ethics policy. Once you have that why do you need all the bells and whistles on the RFP and PO?"

Nearly two years ago Michael Bohon, director, Perigon LLC (Chicago) worked on a project for a hospital to redesign and standardize the RFP and contracting process. "The result of the project demonstrates the absurdity of the process," he said. The committee developed an instructional document that was 67 pages long. But Bohon recognizes the reason why you can’t simplify the process too much. "You have to make sure you’re covered on the financial and legal side," he said. But he criticizes the lack of consistency. "You have to have a defined method on how it’s to be done but you have to have some flexibility built into that process."

Facilities eliminate that flexibility when they overemphasize the RFP data and process in order to demonstrate that the process was conducted in an objective, rigorous and scientific manner, according to Eileen McGinnity, president, Aspen Healthcare Metrics (Englewood, CO). Such process-driven decisions take place at the expense of what they’re trying to accomplish.

"When the RFP is designed principally around facilitating a strict ‘apples-to-apples’ comparison between supplier offerings, the big picture may be lost," McGinnity said. "This is more true of RFPs for new business process partners (e.g., GPO, capital equipment, IT) than for products. A comparison matrix approach can work well when like products are being evaluated – even complex clinical products. But it limits what can be done to weigh the strengths and weaknesses of potential business process partners.

"Rigid RFP structures pigeonhole each respondent’s offering into a pre-determined matrix," she continued. "This limits expansiveness and creativity. The goal of the evaluators becomes filling in the matrix, not necessarily exploring the best options. What if the best solution is an innovative approach to an old problem, and therefore does not fit the grid? The selection process will filter out innovation, in favor of superficial data analysis."

Bohon acknowledged, however, that RFPs and POs probably need to be fairly deep and complex. "The problem is when you make them too complex to be valuable," he added.

So why has the RFP and PO process become so convoluted?

Theories abound but they generally involve some interwoven threads. "People don’t understand the importance of it," Bohon noted. "When you explain to them how it should be done then they tell you they don’t have time to do all the work."

In fact, Bohon is a staunch advocate for healthcare materials managers writing their own RFPs and POs. "Outside of healthcare that’s a routine practice in other industries," he said. "Healthcare is one of the few industries that allows suppliers to write out contracts. Healthcare has become kind of lazy in that they depend on the GPOs and vendors to do most of the work." Last year Bohon developed an online instructional course for Accenture’s Supply Chain Academy (www.supplychainacademy.com) in conjunction with the Institute for Supply Management that outlines RFP and PO development basics.

Nick Gaich, vice president of materials management and customer service at Stanford (CA) Hospital and Clinics, attributes the current practices to habit. "There is a part of me that feels that the old adage of ‘That’s the way it’s always been done’ holds true," Gaich said. "Historically our industry has not been quick to move towards change and to some degree I believe this plays out here as well. Add to this the real need and concerns relative to audit, compliance and the inherent responsibilities of overseeing a significant cash component of an organization and it proves to be very strong motivator for those of us who shoulder the opportunity."

McGinnity concurred with the habitual idea. "People in healthcare move from place to place, taking their old practices with them," she said. "No matter where they go, they’ll probably have to manage many competing organizational priorities with limited resources. In the interest of time, it may be attractive to dust off an old RFP and use it again, even if it’s not the best fit. When there is too much to do, and too little time, an imperfect something is better than a perfect nothing for getting the job done."

Consultants also have played a key role in how the RFP and PO process has evolved over the years.

"When a provider is faced with making a business decision that will have a big impact on a key business practices – choosing a new GPO, identifying a capital equipment company as a strategic partner in a new heart hospital, selecting mission-critical IT systems, choosing strategic vendors for physician preference items – providers will often use a consultant," she said.

"The hospital may be looking for the specialized clinical or business practice expertise the consultant brings to the selection process," she continued. "In other cases, the hospital simply doesn’t have the resources; the consultant is a ‘sophisticated temp’ to help accomplish the selection process expeditiously. In still other cases, the culture of the hospital may be to rely on outside consultants in any major business process change.

"In any case, consultants are relied upon for what they bring – analytical tools, proven processes – and what they know – industry knowledge, familiarity with suppliers/products in a sector, etc. That the consultant brings a particular methodology is to be expected. It speeds things up and prevents the hospital from reinventing the wheel to get a good result," she said.

Diagnosis: The potential solutions
One way to approach streamlining the RFP and PO process is to focus on them separately. After all, they are different documents designed to achieve different outcomes.

"The RFP is an invitation to prospective sellers to extend an offer to sell certain of their products or services at a price," said Lynn Everard, a prominent Florida-based healthcare supply chain consultant and strategist. "Acceptance of the seller’s can occur in two ways: The issuance of a PO or multiple POs over time or joint agreement to create a contractual relationship and both are legal documents. An RFP can be considered a legal document but the seller in extending the offer has the right to qualify pricing, terms and conditions. For example, he can state that the pricing is good for a certain time period or he can state a termination date for the offer if unaccepted by the buyer by that date."

On the other hand, the PO serves a different purpose. "The PO is a legal document and binds the buyer to the terms and conditions stated on the face of the PO and in the boilerplate," he noted.

Gaich noted that he wouldn’t necessarily revise the PO process from a structural perspective. "Keeping in mind that the PO becomes the binding document of exchange, maintaining its discipline is essential," he said. "From a transactional perspective, moving towards uniformity in design, (one look, one feel) would be one of my first pushes towards simplifying the system.

"From the RFP perspective I would agree that we spend way too much time and effort in detail that ultimately proves to generate little true value," he continued. "I would look for a reform that discontinues line item specifics mandating more of a solution document format. The ultimate goal is to bring the supplier and provider together under a framework that spells out the provider’s wants, needs and expectations, and then allows the supplier to creatively fit the need from a service and pricing model. Moving away from low-end, low-value details and moving towards an accelerated negotiation phase of the process pushes both parties to better understand aspects of service, pricing, expectations sooner in the exchange."

One way to look at refining the RFP and PO process is to treat it like a job search that involves due diligence and detailed background checks, according to Colonna. Spot strategic connections and exclude any bidding information in much the same way you don’t put salary demands on a resume or discuss it in an initial interview.

"You’re trying to match a product need with a supplier and hopefully develop a strategic relationship with a vendor," he said. "That means you have to find somebody that’s a good fit for your organization. It’s the same as trying to hire an employee."

The RFP represents a detailed job description of what’s needed, he continued. You display the skills or specifications you are looking for and what expectations you have. "It’s a chance for the customer and the supplier to outline their expectations." It’s not about whether a vendor can deliver a product or service at the lowest price or the vendor telling you how great it is, he added.

Colonna admits that POs may be harder to change because they require so many financial and legal elements for an organization’s protection. Still, the PO, which he likens to the paycheck in the job search example, should be treated separately from the RFP.

Another way to slim down RFP content is for organizations and their employees to sign a strict ethical agreement with penalties for non-compliance, he suggested. That way, everyone’s covered for any business tactic and transaction.

Ironically, Bohon contends that RFP and PO process reform should include three steps. He calls for a pre-qualification questionnaire that asks open-ended essay questions in order to help facilities weed out prospects. He also argues that the RFP itself needs to be more generalized and not tied in any way to the PO. "Sometimes when you make the RFP too specific you drive away certain companies from participating," he said. Bohon frowns on the idea of reworking RFP information into the PO. "I’ve seen it happen where people literally take the wording out of the RFP and turn that into the PO," he noted. The third step of the process involves final negotiations and a signed contract.

Bohon also recommends that facilities contact companies like MD Buyline (Dallas), which offers market research and product evaluation services, as well as contractual consultations.

Currently, more than 3,200 hospitals work with MD Buyline, according to Mike Clemens, vice president and COO. The company offers RFP templates that member facilities can download and customize for their use. "Typically, hospitals have told us they can spend about 40 hours doing their own RFPs," Clemens said. "With our template, they can cut that down to two hours."

McGinnity offers five tips for providers to streamline the RFP process and make it more realistic.

1. Eliminate all but the most necessary legalese (if any is needed at all). "After all, this isn’t a contract; it’s simply a request for information at this point," she said. "The legal jargon and caveats can wait until the deal is closer to being inked and it has to be turned into a contract the lawyers can all live with."

2. Start with the end in mind. "The end is to identify the best partner(s) for key business processes. Often an RFP’s focus is one component rather than the larger picture (e.g., price of an item or service, rather than total cost and quality of care impact). The RFP document is just the first step. The process should include provider meetings with potential suppliers, in which the provider elaborates on the overall operational and financial goals the RFP is intended to support."

3. Require proof sources and investigate them. "RFPs often don’t ask for contacts at other providers where the supplier’s solution has created a desired result. The hospital doesn’t check references to understand how the supplier’s success stories will apply in a new circumstance."

4. Ask respondents to disclose relationships with consultants to the RFP process, and vice versa. "The process should be geared to find the best possible supplier from the universe of qualified possibilities, not from a limited supplier group with incentive or other relationships with the consultants."

5. Specify the provider’s position on confidentiality of the RFP response. "Accept no unreasonable limitations on the use of information that will be returned in the RFP. A current fashion is for vendors to seek to expand traditional limitations on confidentiality of their bid information, including their proposed pricing. This appears to be designed to prevent information sharing among hospitals within an IDN. Some vendors specify that their information cannot be shared with consultants hired by the provider to help facilitate the selection process – a demand that hurts the hospital’s ability to conduct its business. The provider may, however, agree to treat bid information such that it will not be shared with the vendor’s competitors."

Providers should structure their RFPs with their ultimate goal in sight – identifying new partners for key business purposes – and not to enable a consultant to complete a comparison matrix of bid responses, McGinnity emphasized. In addition, she noted that providers should retain control of their "confidential" information throughout the process and not enable bidders to dictate what’s secret and non-transparent.

"We have to stop thinking that everybody else is the enemy," Colonna said. "Too many times in healthcare we have these adversarial relationships from the start. It’s amazing how much disinformation is out there and most of it is negative and based on perceptions." HPN

Annoying RFP No-Nos

•Bad formatting (including rigid matrices). Electronic documents have helped this somewhat but when the format dictates content, it’s maddening.

•Questions that are not well grouped by topic. The easiest way to get an RFP done is to parcel it out to various departments or subject matter experts and have them tackle specific sections. If the questions they need to answer are all over the place, it’s easy to miss something.

•RFPs for consulting services that describe a very vague or general goal ("General Hospital would like proposal for consulting assistance to become the Midwest’s preeminent cardiovascular center.") and ask the respondent to submit a detailed project timeline/plan to accomplish the vague goal.

•Unrealistic deadlines.

•Difficulty getting answers to clarifying questions.

•Administrative protocols that add no value to the substance of the RFP (e.g., "submit X copies of your response with one type of title page and X copies with a different title page;" "include a notarized statement that no company principal has been convicted of a felony," etc.).

•RFPs for consulting services that will be awarded based on a fixed project fee, but which require "time and materials" detail of consulting hours.

 

February 2005