Common use of Specific Restrictions Applicable to a Floating License Clause in Contracts

Specific Restrictions Applicable to a Floating License. If Customer’s License Certificate indicates that Customer has obtained a “Floating Developer License” or a “Floating Build Server License” to the SDP, then, Customer has obtained a Floating License and the following requirements, restrictions and limitations apply: (i) Notwithstanding anything to the contrary, in order to be a Licensed Developer and access Floating Licenses, Customer Developers who are contractors or agents of Customer or Customer Affiliate must have a Customer or Customer Affiliate email address, e.g. if Customer’s standard employee email format is xxxxxxxxxxxx@xxxxxxxxxxxx.xxx, Customer’s and Customer’s Affiliates’ contractors or agents must have an equivalent email address in order to be a Licensed Developer. (ii) With any Floating Developer License purchased, Customer will obtain a License Key for use by its Licensed Developers. In connection with the purchase (applicable to SDP 7.1 only), Customer may also request a License Key for its Floating Build Server License (at no additional charge) in order to install and deploy SDP on a Build Server. The License Key obtained with the Floating Developer License may only be used to install Software on Licensed Developer’s Developer System, but such key may not be used to deploy the Software on Build Server(s). A License Key obtained with the Floating Build Server License must be requested and used to install Software on Customer’s Build Server(s). (iii) The Floating License is managed by a License Manager Tool provided by BlackBerry to Customer. Customer must deploy and use the License Manager Tool supplied by BlackBerry to manage its Floating License(s). A single Floating License token is provided in connection with a purchase of each Floating Developer License. Using the License Manager Tool, a single Floating License token can be checked out by a Customer Developer for development activities or the token may be checked out on a Build Server for the duration of a single Build on the Build Server. Every Customer Developer must check out a Floating License token during development activities to be properly “licensed” to access and use SDP, whether such development activities are taking place on Developer System or on a Build Server. Only one Developer may use a Floating License token at any given time. Alternatively, a single Floating License token may be checked out to a single Build on a Build Server onto which the SDP has been installed for the duration of Build. (iv) The total number of concurrent Builds on any Build Server deploying SDP plus the total number of Licensed Developers accessing and using the SDP shall not exceed the total number of Floating Licenses purchased. (v) Customer and/or Licensed Developer may not share use of a Developer System, that has SDP installed and is not a Target System, with other developers, unless such developers are Licensed Developers. Developer System(s) with a Floating Developer License may only be used by Licensed Developers.

Specific Restrictions Applicable to a Floating License. If CustomerPartner’s License Certificate indicates that Customer Partner has obtained a “Floating Developer License” or a “Floating Build Server License” to the SDP, then, Customer Partner has obtained a Floating License and the following requirements, restrictions and limitations apply: (i) Notwithstanding anything to the contrary, in order to be a Licensed Developer and access Floating Licenses, Customer Partner Developers who are contractors or agents of Customer Partner or Customer Partner Affiliate must have a Customer Partner or Customer Partner Affiliate email address, e.g. if CustomerPartner’s standard employee email format is xxxxxxxxxxxx@xxxxxxxxxxxx.xxxxxxxxxxxxxxx@xxxxxxxxxxx.xxx, CustomerPartner’s and CustomerPartner’s Affiliates’ contractors or agents must have an equivalent email address in order to be a Licensed Developer. (ii) With any Floating Developer License purchasedobtained, Customer Partner will obtain a License Key for use by its Licensed Developers. In connection with obtaining the purchase Floating License (applicable to SDP 7.1 only), Customer Partner may also request a License Key for its Floating Build Server License (at no additional charge) in order to install and deploy SDP on a Build Server. The License Key obtained with the Floating Developer License may only be used to install Software on Licensed Developer’s Developer Partner System, but such key may not be used to deploy the Software on Build Server(s). A License Key obtained with the Floating Build Server License must be requested and used to install Software on CustomerPartner’s Build Server(s). (iii) The Floating License is managed by a License Manager Tool provided by BlackBerry to CustomerPartner. Customer Partner must deploy and use the License Manager Tool supplied by BlackBerry to manage its Floating License(s). A single Floating License token is provided in connection with a purchase of each Floating Developer License. Using the License Manager Tool, a single Floating License token can be checked out by a Customer Developer for development activities or the token may be checked out on a Build Server for the duration of a single Build on the Build Server. Every Customer Developer must check out a Floating License token during development activities to be properly “licensed” to access and use SDP, whether such development activities are taking place on Developer Partner System or on a Build Server. Only one Developer may use a Floating License token at any given time. Alternatively, a single Floating License token may be checked out to a single Build on a Build Server onto which the SDP has been installed for the duration of Build. (iv) The total number of concurrent Builds on any Floating Build Server deploying SDP plus the total number of Licensed Developers accessing and using the SDP shall not exceed the total number of Floating Licenses purchasedobtained. (v) Customer Partner and/or Licensed Developer may not share use of a Developer Partner System, that has SDP installed and is not a Sample Target System, System or Sample Partner Applications with other developers, unless such developers are Licensed Developers. Developer Partner System(s) with a Floating Developer License may only be used by Licensed Developers.

Specific Restrictions Applicable to a Floating License. If Customer’s License Certificate indicates that Customer has obtained a “Floating Developer License” or a “Floating Build Server License” to the SDP, then, Customer has obtained a Floating License and the following requirements, restrictions and limitations apply: (i) Notwithstanding anything to the contrary, in order to be a Licensed Developer and access Floating Licenses, Customer Developers who are contractors or agents of Customer or Customer Affiliate must have a Customer or Customer Affiliate email address, e.g. if Customer’s standard employee email format is xxxxxxxxxxxx@xxxxxxxxxxxx.xxx, Customer’s and Customer’s Affiliates’ contractors or agents must have an equivalent email address in order to be a Licensed Developer. (ii) With any Floating Developer License purchased, Customer will obtain a License Key for use by its Licensed Developers. In connection with the purchase (applicable to SDP 7.1 only)purchase, Customer may also request a License Key for its Floating Build Server License (at no additional charge) in order to install and deploy SDP on a Build Server. The License Key obtained with the Floating Developer License may only be used to install Software on Licensed Developer’s Developer System, but such key may not be used to deploy the Software on Build Server(s). A License Key obtained with the Floating Build Server License must be requested and used to install Software on Customer’s Build Server(s). (iiiii) The Floating License is managed by a License Manager Tool provided by BlackBerry to Customer. Customer must deploy and use the License Manager Tool supplied by BlackBerry to manage its Floating License(s). A single Floating License token is provided in connection with a purchase of each Floating Developer License. Using the License Manager Tool, a single Floating License token can be checked out by a Customer Developer for development activities or the token may be checked out on a Build Server for the duration of a single Build on the Build Server. Every Customer Developer must check out a Floating License token during development activities to be properly “licensed” to access and use SDP, whether such development activities are taking place on Developer System or on a Build Server. Only one Developer may use a Floating License token at any given time. Alternatively, a single Floating License token may be checked out to a single Build on a Build Server onto which the SDP has been installed for the duration of Build. (iviii) The total number of concurrent Builds on any Build Server deploying SDP plus the total number of Licensed Developers accessing and using the SDP shall not exceed the total number of Floating Licenses purchased. (v) Customer and/or Licensed Developer may not share use of a Developer System, that has SDP installed and is not a Target System, with other developers, unless such developers are Licensed Developers. Developer System(s) with a Floating Developer License may only be used by Licensed Developers.

Specific Restrictions Applicable to a Floating License. If Customer’s License Certificate indicates that Customer has obtained a “Floating Developer License” or a “Floating Build Server License” to the SDPSDP Software, then, Customer has obtained a Floating License and the following requirements, restrictions and limitations apply: (i) Notwithstanding anything to the contrary, in order to be a Licensed Developer and access Floating Licenses, Customer Developers who are contractors or agents of Customer or Customer Affiliate must have a Customer or Customer Affiliate email address, e.g. if Customer’s standard employee email format is xxxxxxxxxxxx@xxxxxxxxxxxx.xxx, Customer’s and Customer’s Affiliates’ contractors or agents must have an equivalent email address in order to be a Licensed Developer. (ii) With any Floating Developer License purchased, Customer will obtain a License Key for use by its Licensed Developers. In connection with the purchase (applicable to SDP 7.1 only)purchase, Customer may also request a License Key for its Floating Build Server License (at no additional charge) in order to install and deploy SDP Software on a Build Server. The License Key obtained with the Floating Developer License may only be used to install Software on Licensed Developer’s Developer System, but such key may not be used to deploy the Software on Build Server(s). A License Key obtained with the Floating Build Server License must be requested and used to install Software on Customer’s Build Server(s). (iiiii) The Floating License is managed by a License Manager Tool provided by BlackBerry to Customer. Customer must deploy and use the License Manager Tool supplied by BlackBerry to manage its Floating License(s). A single Floating License token is provided in connection with a purchase of each Floating Developer License. Using the License Manager Tool, a single Floating License token can be checked out by a Customer Developer for development activities or the token may be checked out on a Build Server for the duration of a single Build on the Build Server. Every Customer Developer must check out a Floating License token during development activities to be properly “licensed” to access and use SDPSDP Software, whether such development activities are taking place on Developer System or on a Build Server. Only one Developer may use a Floating License token at any given time. Alternatively, a single Floating License token may be checked out to a single Build on a Build Server onto which the SDP Software has been installed for the duration of Build. (iviii) The total number of concurrent Builds on any Build Server deploying SDP Software plus the total number of Licensed Developers accessing and using the SDP Software shall not exceed the total number of Floating Licenses purchased. (v) Customer and/or Licensed Developer may not share use of a Developer System, that has SDP installed and is not a Target System, with other developers, unless such developers are Licensed Developers. Developer System(s) with a Floating Developer License may only be used by Licensed Developers.

Specific Restrictions Applicable to a Floating License. If Customer’s License Certificate indicates that Customer has obtained a “Floating Developer License” or a “Floating Build Server License” to the SDP, then, Customer has obtained a Floating License and the following requirements, restrictions and limitations apply: (i) Notwithstanding anything to the contrary, in order to be a Licensed Developer and access Floating Licenses, Customer Developers who are contractors or agents of Customer or Customer Affiliate must have a Customer or Customer Affiliate email address, e.g. if Customer’s standard employee email format is xxxxxxxxxxxx@xxxxxxxxxxxx.xxx, Customer’s and Customer’s Affiliates’ contractors or agents must have an equivalent email address in order to be a Licensed Developer. (ii) With any Floating Developer License purchased, Customer will obtain a License Key for use by its Licensed Developers. In connection with the purchase (applicable to SDP 7.1 only)purchase, Customer may also request a License Key for its Floating Build Server License (at no additional charge) in order to install and deploy SDP on a Build Server. The License Key obtained with the Floating Developer License may only be used to install Software on Licensed Developer’s Developer System, but such key may not be used to deploy the Software on Build Server(s). A License Key obtained with the Floating Build Server License must be requested and used to install Software on Customer’s Build Server(s). (iii) The Floating License is managed by a License Manager Tool provided by BlackBerry to Customer. Customer must deploy and use the License Manager Tool supplied by BlackBerry to manage its Floating License(s). A single Floating License token is provided in connection with a purchase of each Floating Developer License. Using the License Manager Tool, a single Floating License token can be checked out by a Customer Developer for development activities or the token may be checked out on a Build Server for the duration of a single Build on the Build Server. Every Customer Developer must check out a Floating License token during development activities to be properly “licensed” to access and use SDP, whether such development activities are taking place on Developer System or on a Build Server. Only one Developer may use a Floating License token at any given time. Alternatively, a single Floating License token may be checked out to a single Build on a Build Server onto which the SDP has been installed for the duration of Build. (iv) The total number of concurrent Builds on any Build Server deploying SDP plus the total number of Licensed Developers accessing and using the SDP shall not exceed the total number of Floating Licenses purchased. (v) Customer and/or Licensed Developer may not share use of a Developer System, that has SDP installed and is not a Target System, with other developers, unless such developers are Licensed Developers. Developer System(s) with a Floating Developer License may only be used by Licensed Developers.