This is a draft version with 1 changes in review. The corresponding stable version was approved on 12 September 2019.
You are viewing an old version of this page. Return to the latest version.
Difference between revisions of "QM:Preparing an Offer"
| [unchecked revision] | [pending revision] |
(Tag: 2017 source edit) |
| Document Control | |
|---|---|
| Document type | Process description |
| Document number | 1232 |
| Version | |
| Status | |
| Comment | |
| Coverage | Vertrieb Sales |
| Involved groups | Executive Management, Product Management, Service Management |
| Standard specification | ISO 9001:2015(en) 8.2.1 Customer communication |
| Responsible Editor | |
| Reviewer | Martin Frischmann (external) |
| Approval by | |
| Approved date | |
| Valid from | |
| Valid until | |
General initial review[edit | edit source]
We distinguish between the following requests:
- it relates to the creation of a software system, or
- there is another reason.
If it is a request to create a software system, you must ensure the following (depending on customer requirements):
- The legal requirements are met,
- quality requirements of the customer were understood,
- a match between offer and contract,
- the order can be fulfilled in terms of content and dates and
- the business benefits of the company are guaranteed.
The procedure of the contract review described here is documented in the relevant Methods Manual.
Review[edit | edit source]
The contract must be formulated by a shareholder or an employee authorized by the shareholders' meeting and submitted to another shareholder for inspection before delivery to the customer. Only after the review is complete, a draft contract can be submitted to the customer. All other changes to a contract require a new review.
The review of the documents includes in particular the comparison of the contract text with the offer documents. In addition, the full coverage of customer requirements and the feasibility of the included goals are checked.
Acceptance of the offer must always be in writing. An informal Email is sufficient, but in most cases, the customer's purchase department sends an order document. In the case of content changes to contracts, the amended documents pass through the contract review once again. The changes are documented and communicated to the affected departments of our company.
Documentation[edit | edit source]
The contract verification procedures are recorded in the contract review form provided for this purpose. Depending on the nature of the request, the requirements made by the customers are recorded and this documentation is submitted to them for cross-checking. The documents of the contract review are subject to the documentation obligation according to section "Control of quality records" and are collected in the customer file related to orders or contracts.
{{QM Process
|Document type=Process description
|Document number=1232
|QM Coverage=VertriebSales
|Involved groups=Executive Management, Product Management, Service Management
|Standard specification=
ISO 9001:2015(en) 8.2.1 Customer communication
|Reviewer=Martin Frischmann (external)
|Valid from=2019/07/25
|Valid until=2022/10/03
|Coverage=Sales
}}
<bookshelf src="Book:Quality Handbook" />
==General initial review==
We distinguish between the following requests:
* it relates to the creation of a software system, or
* there is another reason.
If it is a request to create a software system, you must ensure the following (depending on customer requirements):
# The
#The legal requirements are met,
# quality #quality requirements of the customer were understood,
# a #a match between offer and contract,
# the #the order can be fulfilled in terms of content and dates and
# the #the business benefits of the company are guaranteed.
The procedure of the contract review described here is documented in the relevant Methods Manual.
==Review==
The contract must be formulated by a shareholder or an employee authorized by the shareholders' meeting and submitted to another shareholder for inspection before delivery to the customer. Only after the review is complete, a draft contract can be submitted to the customer. All other changes to a contract require a new review.
The review of the documents includes in particular the comparison of the contract text with the offer documents. In addition, the full coverage of customer requirements and the feasibility of the included goals are checked.
Acceptance of the offer must always be in writing. An informal Email is sufficient, but in most cases, the customer's purchase department sends an order document. In the case of content changes to contracts, the amended documents pass through the contract review once again. The changes are documented and communicated to the affected departments of our company.
== Documentation ==
The contract verification procedures are recorded in the contract review form provided for this purpose. Depending on the nature of the request, the requirements made by the customers are recorded and this documentation is submitted to them for cross-checking. The documents of the contract review are subject to the documentation obligation according to section "Control of quality records" and are collected in the customer file related to orders or contracts.| (3 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
|Document type=Process description | |Document type=Process description | ||
|Document number=1232 | |Document number=1232 | ||
| − | |Coverage= | + | |QM Coverage=Sales |
|Involved groups=Executive Management, Product Management, Service Management | |Involved groups=Executive Management, Product Management, Service Management | ||
| − | |Standard specification= | + | |Standard specification=ISO 9001:2015(en) 8.2.1 Customer communication |
|Reviewer=Martin Frischmann (external) | |Reviewer=Martin Frischmann (external) | ||
|Valid from=2019/07/25 | |Valid from=2019/07/25 | ||
|Valid until=2022/10/03 | |Valid until=2022/10/03 | ||
| + | |Coverage=Sales | ||
}} | }} | ||
<bookshelf src="Book:Quality Handbook" /> | <bookshelf src="Book:Quality Handbook" /> | ||
| Line 14: | Line 15: | ||
We distinguish between the following requests: | We distinguish between the following requests: | ||
| − | * it relates to the creation of a software system, or | + | *it relates to the creation of a software system, or |
| − | * there is another reason. | + | *there is another reason. |
If it is a request to create a software system, you must ensure the following (depending on customer requirements): | If it is a request to create a software system, you must ensure the following (depending on customer requirements): | ||
| − | # The legal requirements are met, | + | |
| − | # quality requirements of the customer were understood, | + | #The legal requirements are met, |
| − | # a match between offer and contract, | + | #quality requirements of the customer were understood, |
| − | # the order can be fulfilled in terms of content and dates and | + | #a match between offer and contract, |
| − | # the business benefits of the company are guaranteed. | + | #the order can be fulfilled in terms of content and dates and |
| + | #the business benefits of the company are guaranteed. | ||
The procedure of the contract review described here is documented in the relevant Methods Manual. | The procedure of the contract review described here is documented in the relevant Methods Manual. | ||
| Line 33: | Line 35: | ||
Acceptance of the offer must always be in writing. An informal Email is sufficient, but in most cases, the customer's purchase department sends an order document. In the case of content changes to contracts, the amended documents pass through the contract review once again. The changes are documented and communicated to the affected departments of our company. | Acceptance of the offer must always be in writing. An informal Email is sufficient, but in most cases, the customer's purchase department sends an order document. In the case of content changes to contracts, the amended documents pass through the contract review once again. The changes are documented and communicated to the affected departments of our company. | ||
| − | == Documentation == | + | ==Documentation== |
The contract verification procedures are recorded in the contract review form provided for this purpose. Depending on the nature of the request, the requirements made by the customers are recorded and this documentation is submitted to them for cross-checking. The documents of the contract review are subject to the documentation obligation according to section "Control of quality records" and are collected in the customer file related to orders or contracts. | The contract verification procedures are recorded in the contract review form provided for this purpose. Depending on the nature of the request, the requirements made by the customers are recorded and this documentation is submitted to them for cross-checking. The documents of the contract review are subject to the documentation obligation according to section "Control of quality records" and are collected in the customer file related to orders or contracts. | ||