Skip to main content

Bench Test

Example: Project Columbus LG Chem 551.0262​

Purpose:
To ensure systematic execution, documentation, and resolution of issues during internal bench tests and subsequent bench tests, facilitating quality control and project progress.

Scope:
This process covers internal bench tests and bench tests following internal tests, focusing on programming, SCADA/graphics, engineering review, and project management teams.

1. Internal Bench Test (Thursday Afternoon)​

Schedule: Thursday, 3–5 PM
Participants:

  • Programming Team: Kirk, Anindya Bera
  • SCADA/Graphics: Prem Reddy-Shabad
  • Project Managers (PM): Connor, Zack

Steps:

  1. Send meeting invite for the internal bench test.
  2. Ensure the bench test checklist is complete, referring to Engineering > Sequence of Operation.
  3. If there was a previous test, confirm all prior issues/fails have been resolved.
  4. Request the programming team to upload the latest code to the controller.
  5. Attend the bench test, go through each item on the checklist thoroughly.
  6. After the test, send a follow-up email including results and note all outstanding issues or failures.

2. Bench Test Following Internal Test (Tuesday Afternoon)​

Schedule: Tuesday, 1–5 PM
Participants:

  • Programming Team: Kirk, Anindya Bera
  • SCADA/Graphics: Prem Reddy-Shabad
  • Engineer of Record (EOR): Robert Bieg, Mark Rappa, Elisha Webb
  • Project Managers (PM): Connor, Zack, Oscar, Austyn

Steps:

  1. Send meeting invite for the bench test following the internal test.
  2. Confirm all issues from the internal bench test have been addressed and fixed.
  3. Request the programming team to upload the latest code to the controller.
  4. Attend the bench test and methodically go through the checklist.
  5. Send a follow-up email with results, noting any outstanding issues or failures.
  6. Request the checklist for the next item by sending a request to the Team Lead (John). This request should be sent Wednesday morning, with a due date of Thursday end of day.

Roles and Responsibilities​

RoleResponsibilities
Programming TeamUpload code to the controller; confirm fixes have been applied
SCADA/GraphicsSupport graphics and SCADA system during testing
Project ManagersOrganize meetings; track issues and communication
Engineer of RecordReview test results and approve fixes
Team LeadProvide checklist for the next item

Inputs​

  • Bench test checklist
  • Latest code for upload to controller
  • Previous test results and issue logs

Outputs​

  • Completed bench test checklist with pass/fail status
  • Follow-up email documenting test outcomes and any unresolved issues
  • Updated checklist for the next test item

Notes​

  • Confirm all previous issues/fails have been addressed before proceeding with the next test phase.
  • Meeting invites are critical to ensure attendance across teams.
  • Timely follow-up and documentation are essential for tracking project progress and quality assurance.

This process document can be adjusted as needed for other projects or bench test contexts, maintaining the structured steps, roles, and communication flow as outlined.