Workflow: HQ creates a new issue

1

HQ

1. HQ creates an issue.

2. Issue is approved and sent to QA.

   • Example:

     HQ = Canon Australia.

   • Field issue with Application software.

Video: 0001 HQ creates new issue

Click "here" to visit the video.

2

QA

1. QA (Quality Assurance) receives issue from HQ.

2. QA accepts the issue.

3. QA adapts the QA information.

4. QA select the counter measure location.

5. The issue is requested for approval by QA.

6. QA escalation is sent to Dev/Plant.

Video: 0002 QA receives (and escalates to Dev/Plant)

Click "here" to visit the video.

3

Dev/Plant

1. Dev/Plant receives issue from QA.

2. Dev/Plant accepts the issue from QA.

3. Dev/Plant creates R&D tracking number.

   JIRA number in Poing/TFS number in Venlo).

R&D tracking number is used to trace the issue.

Video: 0003 Dev/Plant receives and creates tracking number

Click "here" to visit the video.

4

Dev/Plant

A solution is found.

1. Dev/Plant creates counter measurement release.

   Example: Hardware modification.

2. The issue is requested for approval by Dev/Plant.

3. Dev/Plant approves the issue.

4. Submit a reply to QA (Quality Assurance).

Video: 0004 Dev/Plant Issue approval

Click "here" to visit the video.

5

QA

1. QA receives a reply from Dev/Plant.

2. Check counter measure release.

3. Fill in and tick the Request Closure Simultaneously.

4. The solution is requested for approval.

5. QA approves the issue.

6. Submit a reply to HQ.

Video: 0005 QA Reply received

Click "here" to visit the video.

6

HQ

1. HQ receives a reply from QA.

2. Check the counter measure release.

3. HQ fills in the reply type.

4. Submit a closure reply to QA.

Video: 0006 HQ Reply received

Click "here" to visit the video.