Process ID

SPL.1

Process name

Supplier Tendering

Process purpose

The purpose of the Supplier Tendering Process is to establish an interface to respond to customer inquiries and requests for proposal, prepare and submit proposals, and confirm assignments through the establishment of a relevant agreement/contract.

Process outcomes

As a result of successful implementation of this process:

1) a communication interface is established and maintained in order to respond to customer inquiries and requests for proposal;

2) requests for proposal are evaluated according to defined criteria to determine whether or not to submit a proposal;

3) the need to undertake preliminary surveys or feasibility studies is determined;

4) suitable staff are identified to perform the proposed work;

5) a supplier proposal is prepared in response to the customer request; and

6) formal confirmation of agreement is obtained.

Base practices

SPL.1.BP1: Establish communication interface. A communication interface is established and maintained in order to respond to customer inquiries or requests for proposal. [OUTCOME 1]

SPL.1.BP2: Perform customer inquiry screening. Perform customer enquiry screening to ensure validity of contract, ensuring the right person is quickly identified to process the lead. [OUTCOME 1]

SPL.1.BP3: Establish customer proposal evaluation criteria. Establish evaluation criteria to determine whether or not to submit a proposal based on appropriate criteria. [OUTCOME 2]

SPL.1.BP4: Evaluate customer request for proposal. Requests for proposal are evaluated according to appropriate criteria. [OUTCOME 2]

SPL.1.BP5: Determine need for preliminary pre-studies. Determine need for preliminary pre-studies to ensure that a firm quotation can be made based on available requirements. [OUTCOME 3]

SPL.1.BP6: Identify and nominate staff. Identify and nominate staff with appropriate competence for the assignment. [OUTCOME 4]

SPL.1.BP7: Prepare supplier proposal response. A supplier proposal response is prepared in response to the customer request. [OUTCOME 5]

SPL.1.BP8: Establish confirmation of agreement. Formally confirm the agreement to protect the interests of customer and supplier. [OUTCOME 6]

NOTE.1: The nature of the commitment should be agreed and evidenced in writing. Only authorized signatories should be able to commit to a contract.

Output work products

02-01 Commitment/agreement → [OUTCOME 6]

08-12 Project plan → [OUTCOME 4] 12-04 Supplier proposal response → [OUTCOME 5] 13-04 Communication record → [OUTCOME 1, 6]

13-15 Proposal review record → [OUTCOME 3, 4]

13-19 Review record → [OUTCOME 2]

Process ID

SPL.2

Process name

Product Release

Process purpose

The purpose of the Product Release Process is to control the release of a product to the intended customer.

Process outcomes

As a result of successful implementation of this process:

1) the contents of the product release are determined;

2) the release is assembled from configured items;

3) the release documentation is defined and produced;

4) the release delivery mechanism and media are determined;

5) release approval is effected against defined criteria;

6) the product release is made available to the intended customer; and

7) confirmation of release is obtained.

Base practices

SPL.2.BP1: Define the functional content of releases. Establish a plan for releases that identifies the functionality to be included in each release. [OUTCOME 1, 3]

NOTE 1: The plan should point out which application parameters influencing the identified functionality are effective for which release.

SPL.2.BP2: Define release products. The products associated with the release are defined. [OUTCOME 1]

NOTE 2: The release products may include programming tools where these are stated. In automotive terms a release may be associated with a sample

e.g. A, B, C.

SPL.2.BP3: Establish a product release classification and numbering scheme. A product release classification and numbering scheme are established based upon the intended purpose and expectations of the release(s). [OUTCOME 2]

NOTE 3: A release numbering implementation may include

 the major release number

 the feature release number

 the defect repair number

 the alpha or beta release

 the iteration within the alpha or beta release

SPL.2.BP4: Define the build activities and build environment. A consistent build process is established and maintained. [OUTCOME 2]

NOTE 4: A specified and consistent build environment should be used by all parties.

SPL.2.BP5: Build the release from configured items. The release is built from configured items to ensure integrity. [OUTCOME 2]

NOTE 5: Where relevant the software release should be programmed onto the correct hardware revision before release.

SPL2.BP6: Communicate the type, service level and duration of support for a release. The type, service level and duration of support for a release are identified and communicated. [OUTCOME 3]

SPL.2.BP7: Determine the delivery media type for the release. The media type for product delivery is determined in accordance with the needs of the customer. [OUTCOME 4]

NOTE 6: The media type for delivery may be intermediate (placed on an adequate media and delivered to customer), or direct (such as delivered in firmware as part of the package) or a mix of both. The release may be delivered electronically by placement on a server. The release may also need to be duplicated before delivery.

SPL.2.BP8: Identify the packaging for the release media. The packaging for different types of media is identified. [OUTCOME 4]

NOTE 7: The packaging for certain types of media may need physical or electronic protection for instance specific encryption techniques.

SPL.2.BP9: Define and produce the product release documentation/release notes. Ensure that all documentation to support the release is produced, reviewed, approved and available. [OUTCOME 3]

SPL.2.BP10: Ensure product release approval before delivery. Criteria for the product release are satisfied before release takes place. [OUTCOME 5]

SPL.2.BP11: Ensure consistency. Ensure consistency between software release number, paper label and EPROM-Label (if relevant). [OUTCOME 5]

SPL.2.BP12: Provide a release note. A release is supported by information detailing key characteristics of the release. [OUTCOME 6]

NOTE 8: The release note may include an introduction, the environmental requirements, installation procedures, product invocation, new feature identification and a list of defect resolutions, known defects and workarounds.

SPL.2.BP13: Deliver the release to the intended customer. The product is delivered to the intended customer with positive confirmation of receipt. [OUTCOME 6, 7]

NOTE 9: Confirmation of receipt may be achieved by hand, electronically, by post, by telephone or through a distribution service provider.

NOTE 10: These practices are typically supported by the SUP.8 Configuration Management Process.

Output work products

08-16 Release plan

11-03 Product release information

→

→

[Outcome 1, 3]

[OUTCOME 1, 3, 4, 6]

11-04 Product release package

→

[OUTCOME 2, 3, 6]

11-07 Temporary solution

→

[Outcome 6]

13-06 Delivery record

→

[Outcome 6,7]

13-13 Product release approval record

→

[Outcome 5]

15-03 Configuration status report → [OUTCOME 2]

18-06 Product release criteria → [OUTCOME 5, 7]