RTS Document Usage Guidelines for Suppliers
RTS Document Usage Guidelines for Suppliers
PRELIMINARY NOTES :
2/ Multiple components from the same supplier can be covered in the same RTS file if the design and processes are very similar. In that case all the part numbers
considered need to be mentioned both in the "Compliance Matrix" excel sheet and in the "Revisions Log" excel sheet.
3/ For some questions there is a difference made between development suppliers and non-development suppliers.
For development suppliers the drawings are developed by the supplier and specificed as such in Volvo documentation.
For non-development suppliers the drawings are developed by Volvo.
PURPOSE OF THE RTS :
The purpose of this document is to make sure the supplier understands early enough all the technical specifications of the component(s) supplied to Volvo and agrees on the
feasibility of these specifications.
This document also targets to collect, document and react early enough to the suppliers recommendations, inputs and advices on these technical specifications.
SUPPLIER RESPONSIBILITY :
1/ In respects to ISO9001:2008 and ISO /TS 16949§7.2.2 "Review of Requirements related to the Product",
the SUPPLIER is responsible for :
- organizing internal appropriate Design Reviews to analyse VOLVO Technical Specifications
- recording the results of the reviews in the RTS compliance matrix
- bringing it to the knowledge of VOLVO
When VOLVO Technical Specifications are changed, it is the SUPPLIER's Responsibility to conduct new Design Reviews and amend accordingly the RTS compliance
matrix.
UNLESS OTHERWISE SPECIFIED IN THE FILE, THIS DOCUMENT SHOULD BE USED THE SAME WAY FOR ALL CASES (NEW COMPONENTS DEVELOPED
WITHIN PROJECTS, FOR BOTH VOLVO AND SUPPLIER DEVELOPED DESIGNS, FOR RUNNING CHANGES ON COMPONENTS AFTER SOP, RESOURCING ETC)
If some requirements / questions are not understood this should be highlighted in the compliance matrix (column C & D), with a "GYR" (Green, Yellow, Red)
status:
In Column C :
Put "G" if requirement / question is reviewed and fully understood
Put "Y" if requirement / question is reviewed but unclear and need further explanations.
Put "R" if the suppliers considers that some part of the technical specification is not existing, is very late or is of so poor quality that it cannot be used for a proper work.
In column D : describe what items need to be clarified and add any needed question or comment
[Link]
How to use this file
If some requirements within the technical specifications are considered as not achievable this should be highlighted in the compliance matrix (column E to H)
with a "GYR" status :
In Column E :
Put "G" if the requirement / question is reviewed and agreed, and considered achievable
"Y" if the requirement / question is reviewed but raises minor concern, it can be achieved but needs actions
"R" if requirement / question is reviewed but raises major concern, it cannot be met
In Column F explain what is the concern for the requirements that are not achievable
In Column G propose some actions to resolve the concern and in column H a responsible person for the action.
At this stage the supplier may also make some recommendations for improvements to Volvo ("compliance matrix" sheet section 12), and propose some actions. This should
be done from the earliest design to avoid late changes.
The updated RTS excel file must then be sent back to the Volvo Buyer with the proposed quotation for the component(s). Internally in Volvo the Buyer is responsible to
collect the suppliers' answers and to communicate them internally to the Volvo SQE and the Volvo Design Engineer.
The Volvo internal RTS status is then "RTS initiated"
2/ After the supplier's selection, each time a significant change is made in the technical specification, the supplier has to :
- update the "Compliance Matrix" excel sheet
- update the "Revisions Log" excel sheet to keep track of the changes
- make sure the Volvo Buyer, SQE and Design Engineer receive the updated RTS excel file
If some concerns are raised, the supplier has to request a formal RTS review with Volvo (physically or via a phone conference) to share the concerns and agree on an action
plan with Volvo.
The progress on the action plan should be reported in the columns I, J and K
Under these conditions the VOLVO SQE, Design engineer and Buyer can sign the RTS (sheet "Revisions Log"). The Buyer sends it back to the supplier for signature.
The supplier sends the RTS and returns it to the buyer.
As hilighted previously, by signing the RTS the supplier commits on :
- the manufacturing feasibility of the component(s) with the specified conditions, tolerances, materials etc
- the feasibility of all the requirements included in the technical specifications (functionalities, testing requirements etc)
This feasibility commitment could be an assessment based on experience on similar products, the evidences of the achievement (capability assessment for tolerances, or
durability results for example) are not requested for the RTS signature.
4/ When the P level design is ready, and PRIOR TO THE P RELEASE the RTS file must be closed.
Volvo internal
The needed RTS for
conditions status is then "RTS
the closure are: signed". This has to be achieved prior to ANY tooling order.
- the "Revisions Log" sheet must be updated.
- the "Compliance Matrix" sheet must be updated showing which documents issues are discussed (drawings, PVR etc). No more minor concern should remain
- the actions progress must be updated and reported in the "Compliance Matrix" sheet. At this stage all the actions should have a closed status.
The Volvo internal RTS status is then "RTS closed"
The supplier will be sent a new blank RTS excel file and (except for supplier re-sourcing) a copy of the previously completed RTS file. To complete the new RTS, the
supplier should analyse the new technical specifications and fill in the whole document as described above
RTS Signature :
The RTS file has to be signed before the tooling order (if any tooling required for the modification) and before the PPAP.
The needed conditions for the signature are :
- no more major or minor concerns
- all the actions are closed
[Link]
REVIEW OF TECHNICAL SPECIFICATIONS (RTS)
Before filling in this document please read "How to use this file" under previous tab
RFQ or DCN No : RTS INITIATION DATE :
Part Name(s)
Project(s)
Supplier Name
Supplier Parma Code
Supplier Part Number(s)
Supplier Representative (name) Phone:
Required Signatures
Signature: Volvo Design Engineer (virtual signatures allowed) Date
Date
Additional Signatures
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
0 Function description
Have you received : description how it is meant to be used, what
it should be used for, if confidentiality needed etc..: where is that
stated among the documents sent to supplier
1 PVR
List below the PVR(s) - part numbers - for the component(s)
considered in this RTS (includes TR)
…..
2 Drawings
…..
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
4 Standards
…..
Page 6 of 18
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
5 5-1 / Critical characteristics
5-1 / special and Critical characteristics
If the component(s) has some criticality requirements, list here all
the criticality [1] , [2] and [3] characteristics or [SC] / [CC]. For
each of these characteristics answer if it is : understood (column
C & D) and achievable (column E to H)
criticality [1] or [CC] characteristics
…..
2R
…..
3R
…..
6 TR - Technical Requirements
List the TR document number(s) (references) applicable for the
component(s).
If no TR applicable for the component(s), enter NA (non
applicable) in column C
…..
Page 7 of 18
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
section requirement
…..
7 Test Methods
List here the testing methods that are defined for the verification
activities needed for the component, under supplier responsibility.
If no testing method is defined, enter NA (non applicable) in
column C
8 Master samples
List below the master samples that you have received for the
component(s). If no master sample has been received, enter NA
(non applicable) in column C
…..
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
List below all the legislations that are applicable for the
component. For each of these legislations answer if it is :
understood (column C & D) and achievable (column E to H). If no
legislation is applicable for the component(s), enter NA (non
applicable) in column C
…..
Substances tracking :
depending on the project, the supplier should be able to report
substances in IMDS.
10 Functional specifications
List below any functional specification applicable for the
component(s), not listed above
…..
Page 9 of 18
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
11 Other technical documents
…..
FREE SPACE (FOR ANY FURTHER COMMENT / RECOMMENDATION / RISK etc ) HIGHLIGHTED EITHER BY THE TEAM EITHER SUPPLIER OR BY VOLVO :
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
Total number
of actions still OPEN 0
Page 11 of 18
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
0 Function description
Have you received : description how it is meant to be used, what
it should be used for, if confidentiality needed etc..: where is that
stated among the documents sent to supplier
1 PVR
List below the PVR(s) - part numbers - for the component(s)
considered in this RTS (includes TR)
…..
2 Drawings
…..
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
…..
4 Standards
…..
Page 13 of 18
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
5 Special characteristics
5-1 / special and Critical characteristics
If the component(s) has some criticality requirements, list here all
the criticality [1] , [2] and [3] characteristics or [SC] / [CC]. For
each of these characteristics answer if it is : understood (column
C & D) and achievable (column E to H)
criticality [1] or [CC] characteristics
…..
2R
…..
3R
…..
6 TR - Technical Requirements
List the TR document number(s) (references) applicable for the
component(s).
If no TR applicable for the component(s), enter NA (non
applicable) in column C
…..
section requirement
Page 14 of 18
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
…..
7 Test Methods
List here the testing methods that are defined for the verification
activities needed for the component, under supplier responsibility.
If no testing method is defined, enter NA (non applicable) in
column C
8 Master samples
List below the master samples that you have received for the
component(s). If no master sample has been received, enter NA
(non applicable) in column C
…..
List below all the legislations that are applicable for the
component. For each of these legislations answer if it is :
understood (column C & D) and achievable (column E to H). If no
legislation is applicable for the component(s), enter NA (non
applicable) in column C
…..
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
Substances tracking :
depending on the project, the supplier should be able to report
substances in IMDS.
10 Functional specifications
List below any functional specification applicable for the
component(s), not listed above
…..
Page 16 of 18
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
11 Other technical documents
…..
FREE SPACE (FOR ANY FURTHER COMMENT / RECOMMENDATION / RISK etc ) HIGHLIGHTED EITHER BY THE TEAM EITHER SUPPLIER OR BY VOLVO :
Part Number(s):
Requirements understanding Requirements feasibility Action plan tracking
Are the requirements clear Enter here any needed comment Are the requirements
and understood ? achievable ? If the requirements are not achievable,
Comments and updates on Status Open /
Requirement / Topic If the requirement is not understood, describe describe what the concern is Needed Action Responsible
the action plan
Due date
Closed
"Green / Yellow / Red " what needs to be clarified "Green / Yellow / Red "
"GYR" status "GYR" status
A B C D E F G H I J K
Total number
of actions still OPEN 0
RTS Revisions Log Date of RTS
Latest Update :
Part Number(s):
Part(s) stage(s) and version(s): Date of RTS
Drawing Number(s): Initiation :
Description of the main technical changes. Date for Supplier Date for Supplier
Technical Technical
Reviews Updates
Should also be mentioned here : Specification Specification
- part number changes Understanding Agreement
- revision level changes
A release
B release
C release
P release