IBM SmartCloud Application Collaborative Lifecycle Management Service

Transcription

1 IBM Terms of Use SaaS Specific Offering Terms IBM SmartCloud Application Collaborative Lifecycle Management Service The Terms of Use ( ToU ) is composed of this IBM Terms of Use - SaaS Specific Offering Terms ( SaaS Specific Offering Terms ) and a document entitled IBM Terms of Use - General Terms ( General Terms ) available at the following URL: The ToU is in addition to the IBM International Passport Advantage Agreement, the IBM International Passport Advantage Express Agreement, or the IBM International Agreement for Selected IBM SaaS Offerings, as applicable ( Agreement ) and together with the ToU make the complete agreement. Should a conflict arise between the General Terms and these SaaS Specific Offering Terms, these SaaS Specific Offering Terms will prevail over the General Terms. Customer may use the IBM SaaS only if Customer first accepts the Terms of Use. By ordering, accessing or using the IBM SaaS Customer agrees to the ToU. By clicking an Accept button after being presented with these SaaS Specific Offering Terms, you are also accepting the General Terms. IF YOU ARE ACCEPTING THE ToU ON BEHALF OF CUSTOMER, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND CUSTOMER TO THE ToU. IF YOU DO NOT AGREE WITH THE ToU OR DO NOT HAVE FULL AUTHORITY TO BIND CUSTOMER TO THE ToU THEN DO NOT IN ANY MANNER USE OR PARTICIPATE IN ANY OF THE FUNCTIONALITY OFFERED AS PART OF THE IBM SAAS. 1. IBM SaaS The following IBM SaaS offerings are covered by these SaaS Specific Offering Terms: IBM SmartCloud Application Collaborative Lifecycle Management Service Contributor Role IBM SmartCloud Application Collaborative Lifecycle Management Service Author Role 2. Charges and Billing 2.1 Charge Metrics The IBM Saas offering is sold under the following charge metric(s): Authorized User is a unit of measure by which the IBM SaaS can be obtained. Customer must obtain separate, dedicated entitlements for each unique Authorized User given access to the the IBM SaaS in any manner directly or indirectly (for example: via a multiplexing program, device, or application server) through any means. Sufficient entitlements must be obtained to cover the number of Authorized Users given access to the IBM SaaS during the measurement period specified in Customer's Proof of Entitlement (PoE) or Transaction Document. 2.2 Billing Options The amount payable for the IBM SaaS is specified in a Transaction Document. The billing options for the IBM SaaS subscription fee are as follows: a. Entire commitment amount upfront b. Monthly (in arrears) c. Quarterly (upfront) d. Annually (upfront) The selected billing option will be valid for the length of the term specified in a PoE or a Transaction Document. The amount payable per billing cycle will be based on the annual subscription fee and number of billing cycles in a year. 2.3 Partial Month Charges The Partial Month charge is a pro-rated daily rate that will be charged to Customer. The Partial Month Charges are calculated based on the remaining days of the partial month starting on the date Customer is notified by IBM that their access to the IBM SaaS is available. 2.4 Overage Charges If Customer's actual usage of the IBM SaaS exceeds the entitlement specified in a PoE or Transaction Document, then Customer will be invoiced for the overage in accordance with the overage rates specified in the applicable PoE or Transaction Document. i (03/2013) Page 1 of 5

2 3. Renewal of a Subscription Period 3.1 Automatic Renewal of a Subscription Period For IBM SaaS offerings ordered under the terms of the IBM International Passport Advantage Agreement or IBM International Passport Advantage Express Agreement, the terms of the first two paragraphs of Section of the Agreement: Annual Renewal of Software Subscription and Support and Selected Support, including any applicable Country-unique terms, apply to this IBM SaaS offering except that for purposes of these Terms of Use: a. the words software subscription and support or Selected Support are replaced by the words IBM SaaS Subscription Period ; and b. to prevent an automatic renewal of the IBM SaaS Subscription Period, Customer must provide IBM with ninety (90) days written notice of cancellation prior to the end of the applicable Subscription Period. 4. Technical Support During the Subscription Period, technical support is provided for the IBM SaaS via an online forum called the IBM SmartCloud Enterprise Support Community ( Forum ) located at: Customer may, once logged into the Account, post questions, discussion topics, and information or feedback within the Forum. Anything Customer posts to the Forum may be viewed by other customers registered to use the Services. IBM assumes no responsibility (and expressly disclaims responsibility) for the accuracy or completeness of any posted information. IBM will monitor the Forum and respond to posts requesting technical support on use of the Cloud Web Portal, access to Services, VM Instance and Service Instance creation, and Service Component Software management functions. Forum support is in English only. IBM will monitor the Forum Monday through Friday (excluding national holidays) between the hours of 9 a.m. and 5 p.m. in the time zone of each cloud data centers and will use commercially reasonable efforts to post answers back to the Forum by the next business day. 5. IBM SaaS Offering Additional Terms 5.1 IBM SaaS User Profile Information In connection with Customer s use of the IBM SaaS, Customer acknowledges and agrees that: (i) IBM SaaS User names, titles, company names and photographs may be posted by an IBM SaaS User as part of a profile ( Profile ) and that the Profile can be viewed by other IBM SaaS Users, and (ii) at any time Customer may correct or remove the IBM SaaS User Profile from the IBM SaaS and such correction or removal may prevent access to the IBM SaaS. 5.2 Links to Third Party Websites or Other Services If Customer or an IBM SaaS User transmits Content to a third party website or other service that is linked to or made accessible by the IBM SaaS, Customer and the IBM User provide IBM with the consent to enable any such transmission of Content, but such interaction is solely between Customer and the third party website or service. IBM makes no warrantees or representations about such third party sites or services, and shall have no liability for such third party sites or services. 5.3 Prerequisite Environment Access In order to use the IBM SaaS, Customer must first acquire and maintain an account in the IBM SmartCloud Enterprise ( SCE ). SCE access is acquired separately from this IBM SaaS and the terms governing such use and access of the SCE are defined in a separate agreement. Customer must remain in good standing to the SCE in order to continue to access the IBM SaaS. When a Customer no longer requires the use of the IBM SaaS, persistent storage and a reserved IP address will remain active and available until Customer specifically orders the deletion of this persistent storage block or reserved IP address. Charges will incur and Customer agrees to pay for the then current charges for storage and a reserved IP address in accordance with the terms of Customer s SCE terms of service. Charges for the persistent storage block and reserved IP address are billed separately from entitlements granted under this Terms of Use. 5.4 Entitlements not required for IBM SaaS Administrators Customer will receive a reasonable number of Administrator user accounts for the administration and maintenance of Customer s access to the IBM SaaS. The Administrator user does not require an i (03/2013) Page 2 of 5

3 Authorized User entitlement unless the Administrator is also assigned a user role as an Author or Contributor. i (03/2013) Page 3 of 5

4 IBM Terms of Use IBM SaaS Specification Appendix A 1. IBM SaaS Overview This IBM SaaS offering s a pay-per user service hosted by IBM SmartCloud Application Services that provides rapidly activated, integrated, team-based agile development capabilities based on IBM Rational Collaborative Lifecycle Management. IBM SaaS provides the combined capabilities of IBM Rational Team Concert ( RTC ), IBM Rational Requirements Composer ( RRC ), and IBM Rational Quality Manager ( RQM ) in one service offering to connect the work of analysts with development and test teams across these software disciplines: Change and configuration management Requirements management Quality management 2. IBM SaaS Capabilities 2.1 Service Administrator The IBM SaaS offering allows for a Customer to assign a service initiator to obtain administrator rights and further gives the Customer the ability to manage the IBM SaaS User s access to the environment, create and delete projects, and assign and delete IBM SaaS roles within projects. The service initiator may assign additional users to have the administrator privileges. 2.2 Service Management Console A service management console allows Service Administrators to create new projects, create new users, assign users a role and assign them access to projects within the IBM SaaS. IBM SaaS Users access the service management console to update their profile information and for password changes Notifications The IBM SaaS includes a notification function that notifies IBM SaaS Users about their IBM SaaS access, project assignments, role assignments and password changes. 2.4 Standardized Project and Process Templates The IBM SaaS provides a single, standard template to create associated project areas for quality management, requirements management, and change and configuration management. The change and configuration management project area is configured to use the Scrum process template. 2.5 Role-based Charges The IBM SaaS allows Customer to assign one or more roles to each user. Charges for purchased entitlements are incurred whether or not assigned to users. The IBM SaaS allows for roles to be assigned and removed by Service Administrators in its discretion. IBM SaaS Users may use assigned roles for any number of projects. 2.6 Lead Roles Customer is capable of assigning a IBM SaaS User with an Author role the corresponding Lead Author role, which provides administrative privileges within the applications that are not automated via the service management console. There is a different lead role for each of the three applications: Rational Team Concert, Rational Requirements Composer and Rational Quality Manager. 2.7 Daily Automatic Online Backup The IBM SaaS will execute a daily backup at a time established by the Service Administrator. This backup is used for automated recovery of the IBM SaaS, as needed. The Service Administrator may select a time of day for the backup to minimize interference with ongoing projects and IBM SaaS Users. 2.8 Export Customer Data Customers may export their IBM SaaS data from the cloud for storage at a location of their own choosing and expense. i (03/2013) Page 4 of 5

5 2.9 Accounting Details Page The service management portal provides the ability for Customer to view IBM SaaS user role consumption information for a selected time period Customer Initiated IBM SaaS Update or Refresh The IBM SaaS permits Customer to launch an automated service update or refresh at a convenient time Automated Monitoring and Recovery The IBM SaaS will monitor the availability of the service instance, and execute a recovery if it becomes unresponsive or unreachable. 3. User Role Definitions 3.1 Contributor Role IBM SaaS Users with entitlements for the Contributor Role are given access to the following functionality: a. Read and write access to planning, change management and reports of RTC b. Read only access to test management functions of RQM c. Read only access to requirements management of RRC 3.2 Author Role IBM SaaS Users with entitlements for the Author Role are given access to all the functionality granted to the Contributor Role plus the Service Administrator may enable the following additional features based on the type of Author Role assigned: a. Developer Read and write access to software configuration management capabilities of RTC b. Quality Professional c. Analyst Read and write access to test management capabilities of RQM Read and write access to create requirements and requirement collections of RRC while using RQM Read and write access requirements management of RRC i (03/2013) Page 5 of 5