Common use of Requirements for software identification Clause in Contracts

Requirements for software identification. 9.3.1. For the purpose of ensuring the software of the System can be identified, an R15XSWIN may be implemented by the vehicle manufacturer. If R15XSWIN is not implemented, an alternative software identification system (i.e. software version) shall be implemented.

Appears in 6 contracts

Samples: wiki.unece.org, wiki.unece.org, wiki.unece.org

AutoNDA by SimpleDocs

Requirements for software identification. 9.3.1. For the purpose of ensuring the software of the System can be identified, an R15XSWIN R157SWIN may be implemented by the vehicle manufacturer. If R15XSWIN R157SWIN is not implemented, an alternative software identification system (i.e. software version) shall be implemented.

Appears in 4 contracts

Samples: www.marklines.com, unece.org, unece.org

AutoNDA by SimpleDocs
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!