The scope of IBM Intelligent Analytics Cloud services

The vendor of an intelligent analysis cloud must define what services, http://www.aliyun.com/zixun/aggregation/13748.html, > infrastructure and software are needed in the cloud. In some ways, deciding which software and hardware to use depends on what services are available in the cloud. This depends on non-functional requirements, such as available time, response time, or number of users. In this section, we will discuss the factors that the vendor must consider, and what decisions must be made to define the service as detailed as possible. We will also give an example of why these details are selected in the lab environment.

Service requesters are responsible for adding business intelligence applications to the cloud. The application consists of reports and data, if appropriate. Such applications contain certain groups of users that need to be added, such as cloud users and Cloud Superuser.

Once the details are identified and documented, these details can serve as the basis for an intelligent analysis of the protocol between the cloud service provider and the service requester. The details are contained in a mutually agreed document.

Service Range

First, the service provider must determine the scope of the service. Considerations include the components you need to provide, the environment that is available, and whether you include support and support levels. The service provider must define how to continue when the requester needs multiple software levels.

Example 1 shows the scope of the considerations.

Example 1. The scope of intelligent analysis cloud in laboratory environment

A common infrastructure developed, tested, and produced in the latest Cognos version suitable for production (the assessment of production is done by the Intelligent Analytics Cloud vendor).

The Intelligent analytics Cloud provider delivers the infrastructure and provides operational support services for the shared Cognos BI production environment, including the Cognos product support for level 3rd issues. The managed environment will only be used to deliver the report content. This does not mean that the environment will be used as a data delivery mechanism. For example, although 100000 of line CSV data can be delivered, it is not allowed as a delivery mechanism.

Intelligent analytics cloud providers provide content and security management because intelligent analytics clouds are suitable for deployment to development, testing, and production environments. This includes moving content from development to testing to production, creating new folders, applying user groups securely to folders, creating user groups and applying their security to data sources, connecting and starting.

If the service requester "must" move to software that is higher than the current product level, the Smart Analytics cloud provider can adapt to the new trial and production environment. The requester will incur the installation and new production environment costs until the overall production environment is upgraded to that level, at which the requester returns the individual named user fees.

Access to specialized features

The scope of the smart Analysis cloud has been set in the service scope, and the cloud vendor must now define which user group or Cognos role to use which Cognos component is allowed. In addition, they must decide at what level the user groups for each service requester are managed. Example 2 shows the sample boundaries that you might want to set.

Example 2. Sample boundary Declaration

The service requester will use a standard Cognos connection interface, use a Cognos browser to process interactive reports in a public folder, and view the report output version. The service requester owns the user group and is responsible for the creation and management of the execution group. They also maintain a list of user group members. Public folder scheduling reports are limited to administrators, or to authorized/well-trained application administrators.

The method that requests a report plan needs to pass the defined feature user ID. The deletion/expiration of the report output is based on age and business justification. If the reporting specification does not exceed two years, or if there is no activity within six months, it will not be deleted. The permissions of the cloud Superuser to access Query Studio and the section Studio are limited to a subset of the user groups. The packages that are used for Query studio and in the address studio require processing restrictions. Storage is stored in my folders, not public folders, and interactive reports must be processed within 10 minutes. The batch/Dispatch report must be processed within 30 minutes.

Governance

The service provider must define the governance process:

How to move a test environment into production and what tools to use? Can the existing reporting structure be made available to other departments with the same needs?

In a lab environment, we decided to use a tool that, to some extent, would cause changes and allow tracing. The features and implementation details of the tool are described in the "New Employee Training Program" in section 6.2 of page 66th, and in the "New Employee Training Program" in chapter NO. 211 12th. The new employee training process and the roles involved will be covered in chapter 16th of page No. 253.

As the sample in Example 3 shows, you may want to use a new employee training program to perform the sample. In the sample lab environment, we allow other groups of users to use the existing reporting structure, however, this depends largely on the type of user group and the extent to which reuse is implemented.

Example 3. Governance implementation Considerations

The service requester initiates the next phase of the upgrade through the new employee training process and services provided in the new employee training program. The upgrade cycle time is usually less than 48 hours, provided all standard records are available. The upgrade request is managed by the new employee training process and procedures.

Intelligent Analytics Cloud vendors will manage all reports that run in any development or test environment to save services for other service requesters.

Support

Service providers must determine the type of support that each environment receives, as well as the differences in production, development, and test environments, such as the response time for weekdays over the weekend. How do I report events and issues? What severity levels are available and will they be handled differently? Example 4 shows several decisions that must be made about how to support cloud solutions. These decisions also affect the choices in the System management architecture. Event management, change management, and monitoring must be available when comprehensive intelligent analysis cloud support is provided. Although event and change management are not covered in the IBM Red Book, the monitoring architecture and its components are described in the "OSS: monitoring and activity management" and "monitoring" chapters.

Example 4. Provide application-supported decisions

24x7 support for production severity 1 to provide 24x5 support for development and test issues, weekends to support any issues found in development, testing, or production environments will report additional cost support for Cognos through a defined process, Including the intelligent analysis cloud provider considered necessary level 3 support intelligent Analysis Cloud vendors provide operational support for development and testing of all environments, providing 24/5 Cognos connections, the results studio, analysis Studio, Query Studio access, and 24/5 Support refers to the Sunday evening from 9 o'clock to Friday 5 o'clock in the afternoon. The Intelligent analytics Cloud provider will provide operational support as part of the standard service. The issues of development and testing will be reported in each public operating process. The Intelligent Analysis Cloud provider provides level 1 and level 2 support, including the use of Cognos to open Problem management reports (PMR) because the report is required to start Level 3 services. A severity of 1 problem can be obtained from the public help desk for support. The development, debugging, and coding of reports, or the modeling of metadata is not included in the support. Severity 1 issues must be submitted through a public process. A severity of 1 problem will be measured and the processing plan will be recorded and shared with the service requester if the Cognos product is involved.