Chromatography process development requirements

Process development endpoint

Describe the intended output and the process decisions your team wants to investigate. Request clarification of the information needed for a development proposal.

Use process objective brief to describe the decision your project team needs to make and the material or output it wants reviewed. Separate the requested outcome from the observations your own reviewers will assess. Ask the bidder to identify unanswered questions in that target description and to relate its response to the same project objective before commercial scope is discussed. Identify the review question associated with the requested output so that the proposed scope can be assessed against the purpose of the enquiry.

Process starting information

Collect the current method description and relevant sample background. Ask the supplier to identify unresolved inputs before proposing a project scope.

Organize process starting dossier around the current method description, the observations available for disclosure and the questions still unresolved. Identify the author or owner of the method record so that requests for additional information reach the appropriate project role. Ask which parts of the proposed work depend on further method information, and keep those questions attached to the current method discussion. Ask the method owner to mark documents that describe completed work separately from proposed changes awaiting a laboratory decision.

Development stage boundaries

Identify the project stages already completed and the next decision requiring support. Request a response confined to the requested development stage.

Use development stage map to name the proposed stages in sequence and show where the requested project scope starts and ends. Ask the supplier to explain unfamiliar stage labels against that sequence. Identify the material entering and leaving the proposed scope, then compare the explanation with the equipment schedule so that your engineering team can assess the same proposed arrangement across all project documents. Ask for the stage names in the diagram and the equipment schedule to be cross referenced where different labels are used for the same proposed scope.

Process interface definition

Describe the upstream and downstream boundaries relevant to the project. Ask for the documents needed to review the proposed development arrangement.

In process boundary diagram, identify what lies inside the proposed package and what belongs to the existing project. Name the owner of each side of the connection and the drawing each owner needs to review. Ask the bidder to mark the proposed interface clearly, then have the responsible engineer compare that response with the actual host or adjacent equipment documents used for the enquiry. Request identification of the document defining the existing connection as well as the drawing describing the proposed side of the interface.

Development review documents

List the observations and records your team wants to review during a proposed project. Request a document schedule tied to the stated process questions.

Use development review plan to separate the questions assigned to each project reviewer and the documents needed to answer them. Connect each open question with the proposed item or stage it affects. Ask for a response addressing those questions individually, and have the responsible reviewer record the agreed description that the purchasing team should use when it prepares the request for commercial terms. Ask the assigned reviewer to distinguish a request for more information from approval of the proposed item, so that open questions remain clear.

Process purchasing decision

Separate requested development work from a later equipment purchase. Ask bidders to identify the scope and documents associated with the present decision.

For process procurement schedule, identify the requested items individually and describe the boundary of each item in plain language. Ask the bidder to mark the equipment or work addressed by its response and identify any requested element needing separate discussion. Keep the proposed scope connected to the project brief so that a price comparison relates to the same requested equipment or work. Request separate identification of requested items that remain open for discussion so that they can be reviewed without obscuring the proposed inclusions.