Procedure PROC-01 · issue 3 · effective 1 March 2026
Handling supplier notices that affect the Kestrel plan
Owner: Programme Office · Asterholm Teknik AB (fictional operation)
Open the exercise →The flow
Steps 1 and 2 can start at the same time. Step 3 needs the change note from step 1. Step 4 brings all three together.
Record the notice
ReceivesProgramme Management · Procurement
Prepare the evidence
ReceivesNordvind · Quality
Check the plan
ReceivesTest Department · Programme Management
Prepare the brief
ReceivesProgramme owner · Steering group
Documents you need to know
| Document | What it says | Owner |
|---|---|---|
| B03 Programme plan rev E | Current plan: delivery week 42, customer demonstration week 46, temperature test week 47, formal decision point week 49. It changes only through a new revision approved by the programme owner. | Programme Office |
| B05 Integration plan | The temperature test requires four consecutive days in chamber TK-2. The unit must be delivered and approved in receiving inspection at least two weeks before the test starts. Booked chamber time is confirmed in the test department weekly bulletin (F05). | Integration Management |
| C07 Quality requirement YS-14 | Surface adhesion. A deviation requires written Quality approval, preceded by a documented impact assessment across the full temperature range. | Quality |
| C08 Rule RK-3 | A manufacturing change that may affect approved properties requires a new full inspection, normally five weeks. A waiver is decided jointly by the Quality Manager and the customer. | Quality |
| D05 Steering group note | The week-46 demonstration is not a contract milestone. Programme Management must report consequences before any deviation is accepted. | Management |
| D07 Customer contract, annex 3 | The commitment concerns the week-49 decision point, when the temperature test must be approved. Penalties apply to that point, not the demonstration. | Management |
| A08, A09, A10 | Nordvind’s changed delivery notice (week 44, or week 40 with a YS-14 deviation), Procurement’s evidence request and Nordvind’s promise to send the evidence. | Procurement |
| A13 Delivery register | Change notes are recorded here. | Procurement |
| ÄN · Change note | Written in step 1; registered in A13 | procurement coordinator |
| KB · Evidence request with status table | Written in step 2 | strategic buyer together with the quality engineer |
| PU · Draft plan with conflicts | Written in step 3 | integration lead, with the Test Manager for booking status |
| BU · Decision brief | Written in step 4 | programme manager |
What it is about
Kestrel Mk2 is Asterholm’s new electronics module. Its key component, the Kestrel unit, is supplied by Nordvind Systems AB. When Nordvind contacts Asterholm about delivery, quality or testing, the notice is handled in four steps so the right person receives the right evidence in time and nobody accepts a deviation without authority.
The procedure starts when Nordvind gives a notice that may affect the delivery date, quality requirements or test time. It makes no decisions. It ensures that the decision maker receives a brief that separates what is supported in writing, what is only promised and what is unknown.
Roles
The procedure identifies roles, not people. Find who holds each role now under People on the intranet; names appear in the documents. Looking this up is a small work step of its own.
| Role | Does | Decides on |
|---|---|---|
| Procurement coordinator | Step 1 | nothing |
| Strategic buyer | Step 2, all contact with Nordvind | what is requested from the supplier |
| Quality engineer | Step 2, assesses evidence | nothing |
| Quality Manager | receives steps 2 and 4 | YS-14 deviation (C07); RK-3 waiver jointly with the customer (C08) |
| Integration lead | Step 3 | integration sequence |
| Test Manager | receives step 3 | chamber time in TK-2 |
| Programme manager | Step 4 | recommendation |
| Programme owner | receives step 4 | the plan (B03), steering group decisions |
The four steps
Each step has four fields and two short texts to pass on.
Step 1 / 4
Record the notice
- Who
- procurement coordinator
- When
- the same day the notice arrives
- Writes
- ÄN · a change note in the delivery register
How to do it
Write down the date, sender and whether the notice was oral or written. Compare the claim with the current plan B03 (delivery week 42) and the latest written notice from Nordvind (A08: week 44, or week 40 with a deviation). Set the status: a phone call or promise is oral and unconfirmed; an email that agrees with an earlier notice is written and confirmed; a written notice that differs from the plan or an earlier notice is conflicting. Always write the difference from the plan as an open question. Overwrite nothing; add a new row.
Pass it on
To Programme Management the same day when the notice differs from the plan or contradicts an earlier notice, for investigation. To the strategic buyer when the notice is oral, so written confirmation is requested. A change note never changes the plan.
Step 2 / 4
Prepare the evidence
- Who
- strategic buyer together with the quality engineer
- When
- when Nordvind answers Procurement’s request (A09), or proposes a deviation
- Writes
- KB · an evidence request with a status table
How to do it
Review A09's three points: affected process parameters, an impact assessment across the full temperature range, and requalification needs. Mark each promised, received or reviewed. A promise is promised. An attachment is received, not reviewed, until Quality has read it. A low-temperature-only report does not make the full-range row received; it remains promised. Request missing items in writing, with a response date. If the change may affect approved properties, RK-3 applies. The Quality Manager decides a YS-14 deviation after a documented impact assessment.
Pass it on
The strategic buyer sends the request to Nordvind by the next day. Quality receives the table when all is received: the quality engineer assesses, the Quality Manager decides. Nobody tells Nordvind that a deviation is accepted before the Quality Manager’s written approval exists.
Step 3 / 4
Check the plan
- Who
- integration lead, with the Test Manager for booking status
- When
- when the change note shows a delivery date other than the plan, or test time is affected
- Writes
- PU · a draft plan with conflicts
How to do it
Count back two weeks from test start: with a week-47 start, receiving inspection must be approved by week 45. If the test moves, move the limit equally and show the calculation. Mark each row holds, clashes or unknown. Missing receiving information is unknown. Check the four-day TK-2 booking against the latest weekly bulletin; without confirmation it is unknown, and another party's booking clashes. TK-1 is not sufficient. A test ending after the week-49 decision point clashes with it. Write who must confirm what. The draft plan is working evidence, not a new plan.
Pass it on
To the Test Department the same week to confirm or rebook TK-2. To Programme Management for the consequences before the steering group. To the Programme Office planning coordinator if the plan needs a new revision.
Step 4 / 4
Compile the decision brief
- Who
- programme manager
- When
- before the steering group, and always before any deviation is accepted
- Writes
- BU · a decision brief of no more than one page
How to do it
Separate facts, proposals and decisions. Report what is written, promised or unknown. Set options against B03: standard week 44 or week 40 with a deviation; state coverage. Consequences: the week-46 demonstration is not a milestone; the week-49 decision point requires an approved test. List the gaps. List decisions with roles: a YS-14 deviation by the Quality Manager (C07), an RK-3 waiver by the Quality Manager and customer (C08), and a plan change by the Programme Owner. Mark the recommendation as a recommendation. Never grant clearance without the test and approvals.
Pass it on
To the Programme Owner and the steering group before the next meeting. The Quality Manager receives the decisions belonging to that role. The strategic buyer is told what may be said to Nordvind and what may not.
Who needs what, when
| Event | Receives | What | When |
|---|---|---|---|
| Notice differs from the plan or contradicts an earlier one | Programme Management | Change note | the same day |
| Oral notice | Procurement | Request for written confirmation | the same day |
| Incomplete response from Nordvind | Procurement → Nordvind | Evidence request | the next day |
| All evidence received | Quality | Status table | immediately |
| Delivery date affects the test | Test Department, Programme Management | Draft plan | the same week |
| Before a deviation is accepted, before the steering group | Programme Owner, Quality Manager, Procurement | Decision brief | before the meeting |
Terms used here
- Kestrel unit
- The component Nordvind Systems AB delivers for Kestrel Mk2.
- YS-14
- Asterholm quality requirement for surface adhesion (C07).
- Deviation
- Temporarily accepting that the requirement is not met. Requires written approval from Quality (C07 3.3).
- RK-3
- The rule on a new full inspection after a change (C08). The inspection normally takes five weeks.
- TK-2 / TK-1
- Temperature chambers. Only TK-2 can run the full temperature test (B05).
- Receiving inspection
- Asterholm inspection of a delivered unit before it may be used in a test.
- Formal decision point, week 49
- The contract checkpoint at which all mandatory tests must be approved (D07).