Host software environment
Identify the software environment and the project roles responsible for integration. Ask the supplier what information is needed to review the connection request.
For host software brief, name the host function that needs a response from the proposed equipment and identify the information your software team needs to interpret it. Ask for the command or message description relevant to that function. Keep connection questions separate from the meaning of the returned information, and request enough documentation for the software reviewer to assess the proposed interface before approval. Ask the software reviewer to distinguish a requested command from the status information needed to establish how the proposed equipment has responded.
Command interface questions
List the functions the host application needs to control. Request the relevant command documentation for the exact proposed equipment configuration.
For command interface request, name the host function that needs a response from the proposed equipment and identify the information your software team needs to interpret it. Ask for the command or message description relevant to that function. Keep connection questions separate from the meaning of the returned information, and request enough documentation for the software reviewer to assess the proposed interface before approval. Ask the software reviewer to distinguish a requested command from the status information needed to establish how the proposed equipment has responded.
Status and fault records
Describe the status information and fault messages required by your software team. Ask for the proposed message definitions and related documentation.
For status message schedule, name the host function that needs a response from the proposed equipment and identify the information your software team needs to interpret it. Ask for the command or message description relevant to that function. Keep connection questions separate from the meaning of the returned information, and request enough documentation for the software reviewer to assess the proposed interface before approval. Ask the software reviewer to distinguish a requested command from the status information needed to establish how the proposed equipment has responded.
Connection boundary drawing
Prepare a diagram showing the intended system boundaries and responsible parties. Request the connection documents needed to assess the proposed arrangement.
In communication 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.
Integration assessment plan
Ask your software team to define how the proposed interface will be reviewed. Request a response identifying the documents and demonstrations needed.
Use integration assessment brief 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.
Software change control
Request identification of the software and document revisions relevant to the quotation. Ask how proposed changes would be described for your team's review.
For software revision register, identify the product or equipment item addressed by each requested document. Ask for a document title and the reference needed to connect it with the current proposal. Refer unfamiliar document terminology to the responsible project reviewer, and request clarification where a returned document concerns a different item or configuration from the one described in the purchasing enquiry. Ask the document reviewer to identify which unresolved questions concern missing information and which concern a document referring to the wrong proposed item.
Chromatography system communication integration: documents to request
| Ask about | Request with your inquiry |
|---|---|
| Which details should the host software brief identify for host software environment? | Host software brief |
| Which details should the command interface request identify for command interface questions? | Command interface request |
| Which details should the status message schedule identify for status and fault records? | Status message schedule |
| Which details should the communication boundary diagram identify for connection boundary drawing? | Communication boundary diagram |
| Which details should the integration assessment brief identify for integration assessment plan? | Integration assessment brief |
| Which details should the software revision register identify for software change control? | Software revision register |