GEN Exclusives

More »

Feature Articles

More »
Nov 15, 2011 (Vol. 31, No. 20)

FSPs Provide an Option to Traditional CRO Approach

Functional Service Providers Can Provide More Focused Expertise and Economic Value

  • Interface

    Managing research and development using FSPs is unlike managing a traditional CRO relationship because of the multiple interfaces required to manage multiple FSPs. The client needs well-structured internal processes that can deal with multiple FSPs. “If not, errors can occur,” Piitulainen warned. “We went through a learning period before we standardized our processes.”

    The difference between CROs and FSPs is also noticeable in data analysis. A CRO typically would analyze the data, but an FSP pushes the data to the client. Therefore, the client needs strong informatics capabilities.

    As an FSP, Birks said, “We become really integrated into the client company.” Ideally, the relationship will be so seamless that the team seems to be a part of the client company. In a relationship like that, “We have more touch points, and we work across the entire portfolio. We also have to interact with other partners, by region or by function, to integrate data and bring it together into the information system.

    “Therefore, we must be very clear on study deliverables and standard operating procedures.” Typically, FSP relationships last several years.

  • Pilot

    Before beginning a project, particularly with a new team, run a pilot, Piitulainen emphasized. “Record everything. Then sit with the FSP to develop lessons learned and to identify any gaps.” He also advised implementing the lessons learned gradually. “It takes a few trials—depending on the team—to make the process smooth.”

    Keeping the same project managers in-house and within the FSPs also helps. “Project managers are worth gold. They are the most important asset. There must be a very good reason for removing them. Ensure that not all trials start at the same time,” he cautioned.

  • Technology

    “Once you decide to outsource, you can explore ways to leverage technology to automate processes or make more effective use of the data,” noted Tony Carita, president of CTB Solutions.

    The challenge is in blending the technology platforms used by the many groups within an organization and integrating legacy data. Typically, the outsourcing, legal, finance, and project-management groups “all have different platforms, and more than 90 percent of the time, they don’t talk with each other,” he said.

    Building a common platform integrating these groups necessitates determining system requirements, considering the business processes, identifying the handoffs, and designing a tool that allows each group to add its information.

    “It may be as simple as an Excel Workbook,” he said, or may be a fully functional application like SynSource, which CTB Solutions designed for the R&D environment, to cut across functional silos and provide an integrated solution.

    “SynSource supports requests for information, requests for proposals, bidding, negotiation, contract finalization, invoicing, benchmarking, earned value analysis, metrics, forecasting, and change management with a built-in document-management system all within a single web-based application.”

    An R&D outsourcing management tool should integrate each of the activities and groups involved in managing an outsourced project across the enterprise, and include an audit capability to match invoices against purchase orders. It should be visible across the organization and consistent across all providers.

    Currently, Carita said, “Very few tools are designed to optimize clinical R&D outsourcing across functional areas throughout the contract lifecycle. Usually, R&D uses tools designed for a fixed production environment, and we then make an attempt to force the more dynamic clinical trial process to fit the tool.”

  • Risks

    FSPs offer the flexibility to select best-in-class providers of specific services rather than the best overall provider, but that type of relationship comes at a price, according to Sally Osmond, executive vp of INC Research.

    Specifically, although the client gains the expertise associated with a particular aspect of the overall project, it loses the broad expertise and intellectual property aspects of the CRO. “With an FSP, the client company assumes it knows the blueprint of the model. Therefore, FSP relationships are best for well-established companies with ample in-house expertise to manage a project.”

    FSPs aren’t really different from other outsourcing arrangements, Osmond said. The implications, however, can be more far-reaching. “If a company outsources payroll and they’re late, all that happens is that payroll is late.”

    If, however, one of the many FSPs on a project is late, the effects ripple throughout multiple companies and may jeopardize the overall project. Therefore, ensuring such events don’t occur or are remediated requires a greater attention to interface management at the client company.

  • Relationships

    Click Image To Enlarge +
    For a CRO/client relationship to succeed, whether it be under the rubric of a traditional model or an FSP, excellent communication and trust remain absolute requirements. [iStockphoto]

    The key aspect of any arrangement with a contract research organization is the relationship, Osmond said. “If the relationship doesn’t work then the contract isn’t worth anything,” she emphasized.

    Although disparate corporate cultures may not be barriers to good relationships, complementary cultures are important factors in getting the best out of an FSP, Birks said.

    “Where you get a collaborative culture with shared decision-making, FSPs work extremely well. If, conversely, you take a buyer/vendor mentality, you are limited in what you can achieve.”

    There also is a danger in seeing outsourcing as merely another way to reduce costs, particularly when profit margins become so thin that nobody really wants to focus on the project. Likewise, “it will never work if senior management doesn’t support it,” Osmond said.

    A successful relationship between a CRO and a biopharma is based upon mutual benefit, Osmond stressed. Whether contracting for an FSP or a traditional full-service CRO arrangement, “The gains must be shared. The CRO should have the ability to leverage what’s been learned” without violating confidentiality agreements.

    For example, she said, using an FSP for data management may not make sense for the FSP if it does essentially the same thing year after year. But, if the relationship develops a way to manage data more efficiently, for example, and the CRO can leverage that knowledge with other clients, the project becomes more attractive and more likely to succeed.

    “Don’t think that a successful relationship will happen overnight,” Osmond cautioned. “If you do, you’ll be discouraged. Instead, develop the relationship and invest in it.”


Add a comment

  • You must be signed in to perform this action.
    Click here to Login or Register for free.
    You will be taken back to your selected item after Login/Registration.

Related content

Jobs

GEN Jobs powered by HireLifeScience.com connects you directly to employers in pharma, biotech, and the life sciences. View 40 to 50 fresh job postings daily or search for employment opportunities including those in R&D, clinical research, QA/QC, biomanufacturing, and regulatory affairs.
 Searching...
More »

GEN Poll

More » Poll Results »

Should “Special K” Get Special Treatment?

In the near term, what is the best way to use ketamine in treating depression?