vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Converged infrastructure A way of structuring an information technology (IT) system by grouping multiple components into a single optimized computing package, components of which may include servers; data storage devices; networking equipment; and software for IT infrastructure management, automation and orchestration 
 Databases Products that provide some form of access to a database without the need for setting up physical hardware, installing software, or configuring for performance 
 Developer tools Products that support developing, testing, and debugging software 
 Enterprise applications Bundle of compatible products that deliver enterprise-grade app solutions for information sharing, automation, and agility 
 Integration Products that facilitate the connection of data, apps, APIs, and devices across an organization to be more efficient, productive, and agile 
 Internet of Things Products that support receiving and transferring data over wireless networks without human intervention 
 Logging and monitoring Products that support storing, searching, analyzing, and monitoring log data and events. And, products that support reviewing and managing the operational workflow and processes being logged 
 Mobile Products with specific or special utility for users creatings things to be used on mobile devices 
 Networking Products that support or augment the linking of computers so they can operate interactively 
 Security Products that provide the protection of stored data from theft, leakage, and deletion 
 Storage Products that support data to be created, read, updated, and deleted 



You can also scope your view of the catalog by using the Provider filter to browse by individual providers, and the Location filter to view products available in specific regions.





 Searching the catalog for deployable architectures 

You can search our growing catalog of deployable architectures to find preassmbled cloud auotmation solutions that solve common enterprise business needs, for example a secure infrastructure layer for highly regulated industries, such as financial services.

The following table lists the filter options that you can use when searching the catalog for deployable architectures.



Table 3. Options for filtering by category

 Option Description 

 AI / Machine Learning Products that enable systems to learn from data rather than through explicit programming 
 Analytics Products that facilitate the analysis of data, typically large sets of business data, by the use of mathematics, statistics, and other means 
 Blockchain Products that facilitate the process of recording transactions and tracking assets in a business network 
 Compute Infrastructure resources that serve as the basis for building apps in the cloud
Learning about Planning Analytics as a Service architecture and workload isolation 

Planning Analytics Workspace within Planning Analytics with Watson employs strict access controls, both at the tenant and user level, which ensures that information from one tenant is not accessible from another.



  Planning Analytics as a Service architecture 

This diagram illustrates how Planning Analytics Workspace within Planning Analytics with Watson validates content requests and isolates database instances.

Zoom

![Planning Analytics as a Service workload isolation](https://cloud.ibm.com/docs-content/v1/content/6f93007fb5e94d4955b919a5b90a98fbc17451af/planning-analytics/images/pa_saas-tenant-isolation.png)

Figure 1. Planning Analytics as a Service architecture





  Planning Analytics as a Service workload isolation 

Isolation includes tenant-specific configuration such as workbooks and plans. In addition, all access to tenant data is only permitted via Planning Analytics Workspace, which ensures that all content requests are validated against configured tenant and user access.

Planning Analytics Engine instances are also isolated from each other, even within a tenant. This ensures that database content is not only segregrated from other tenants, but also segregated from groups of users within the same tenant.
Services 



  Scope of Services 

IBM Maximo Application Suite as a Service (MAS SaaS) is an offering supported by IBM's Site Reliability Engineering (SRE) team. IBM has been hosting Maximo systems for more than 20 years and has deep experience provisioning and supporting Maximo in Cloud environments. The SRE team is solely focused on Maximo Application Suite delivery, providing expert IT administration for both infrastructure and operations and support for customers through the IBM Support Community Portal. Customers interact with the IBM Product Support and SRE team members via case creation, interaction and followup. Team members are based in Canada, the United States, Brazil, Ireland, India, China and Australia.

MAS SaaS is a subscription-based service offered on the Amazon Web Services (AWS) platform.

Zoom

![Enter image alt text right here.](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-SaaS-Operational-View.png)

Figure 1. MAS SaaS Scope of Services





  Service Description 

See the following link to the current Service Description for Maximo Application Suite as a Service. Please check this link regularly as the service description is updated periodically and the current version takes precedent.

[https://www.ibm.com/support/customer/csol/terms/?id=i126-9424](https://www.ibm.com/support/customer/csol/terms/?id=i126-9424)





  Service Level Agreement 

The Service Level Agreement (SLA) for MAS SaaS is described in Section 3.1 of the service description document (above).

SLA Summary for Maximo Application Suite as a SaaS (MAS SaaS):



*  99.9 % Availability (Production Environment)
*  SLA does not include planned or emergency maintenance windows. For details on the maintenance window schedule, see the Maintenance section
*  SLA applies to production environments only
*  Availability credits for availability of less than 99.9%
valueFrom:
fieldRef:
fieldPath: metadata.namespace
envFrom:
- configMapRef:
name: ibm-vpc-block-csi-configmap
image: icr.io/ibm/ibm-vpc-block-csi-driver:v3.0.0
imagePullPolicy: Always
securityContext:
privileged: false
allowPrivilegeEscalation: false
livenessProbe:
failureThreshold: 5
httpGet:
path: /healthz
port: healthz
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 3
name: iks-vpc-block-driver
ports:
- containerPort: 9808
name: healthz
protocol: TCP
resources:
limits:
cpu: 500m
memory: 500Mi
requests:
cpu: 50m
memory: 100Mi
volumeMounts:
- mountPath: /csi
name: socket-dir
- mountPath: /etc/storage_ibmc
name: customer-auth
readOnly: true
- mountPath: /etc/storage_ibmc/cluster_info
name: cluster-info
readOnly: true
serviceAccountName: ibm-vpc-block-controller-sa
volumes:
- emptyDir: {}
name: socket-dir
- name: customer-auth
secret:
secretName: storage-secret-store
- configMap:
name: cluster-info
name: cluster-info
volumeClaimTemplates: []
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
storageclass.beta.kubernetes.io/is-default-class: "true"
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
category: The type of the event. This can be incident, maintenance, announcement, or security bulletins.

componentNames: If a service is impacted, this field represents it. This also can be a global value like Component: IBM Cloud, not only a specific service. See the services on the [IBM Cloud catalog page](https://cloud.ibm.com/catalogservices).

regions: This field shows you the location of the event.

severity: This field refers to the severity of the event. This can be Severity 1, 2, 3 or 4 for incidents, high, medium, or low for maintenance, and major or minor for announcements. See the following detailed severity level descriptions:



* Incidents



* Severity 1: Business-critical functionality is inoperable or critical interference failed. This severity usually applies to the production environment and the inability to access services is causing a critical impact on operations.
* Severity 2: Core functionality is impacted. Service is operational but causing major impact on usage.
* Severity 3: Partial or noncritical disruption to functionality with minimal or isolated impact.
* Severity 4: A minor issue that requires action, but does not impact functionality or usage.



* Maintenance



* High impact: Maintenance will, or is likely to, cause service outages and disruptions.
* Medium impact: Maintenance will, or is likely to, cause measurable service degradation but not an actual outage.
* Low impact: Maintenance will cause no service disruption during or after the maintenance window.



* Announcements



* Major: Important incidents such as legal notices, service deprecation, or security patches.
* Minor: Informative announcements such as product enhancements.





state: This field is only for maintenance and notifications. See the following possible values:



* Values for Maintenance states: Planned, In progress, Completed, Canceled, Failed
* Values for Incident states: New issue, Investigating, Resolved



title: The title field tells you what the notification is about. This field is configured to support more languages, although only English is supported currently.

startTime, endTime: You can check when the event starts, and when it ends.
See also [blocklist](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3954055).





 analysis engine 

A program that analyzes artifacts, such as documents, and infers information about them, and which implements the UIMA Analysis Engine interface specification. Analysis engines are constructed from building blocks called annotators. An analysis engine can contain a single annotator, which is referred to as a primitive analysis engine, or multiple annotators, which is referred to as an aggregate analysis engine.





 annotation 

Information about a span of text. For example, an annotation might indicate that a span of text represents a company name.





 annotation process manager 

A role that is responsible for managing the full annotation lifecycle activities within a workspace. The project manager that is added to a workspace typically performs the activities of an annotation process manager.





 annotation set 



* In machine-based annotation, a collection of documents that can be used as blind data, training data, or test data.
* In human annotation, a collection of documents that are extracted from the corpus that allow the workload to be shared by multiple human annotators.







 anti-affinity 

Two or more container group instances that run on different network nodes to ensure higher availability for an app. See also [affinity](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2149238).





 API key 

A unique code that is passed to an API to identify the calling application or user. An API key is used to track and control how the API is being used, for example, to prevent malicious use or abuse of the API.





 API operation 

A unit of a REST API that can be invoked. An API operation comprises an HTTP verb and a URL path that is subordinate to the context root of the API.





 API resource 

A unit of a REST API that can be invoked. An API resource comprises an HTTP verb and a unique URL path that is subordinate to the context root of the API.





 app 

A web or mobile device application.
Architecture framework 

The architecture framework can be used as a guide to provide a consistent approach to architect hybrid, multi-cloud end-to-end solutions based on your requirements.

  How it works 

Cloud architecture can be thought of as a multi-dimensional matrix.

Zoom

![Reference Architecture](https://cloud.ibm.com/docs-content/v1/content/architecture-framework//images/cube.svg)

Cube diagram that shows the dimensions of a cloud architecture.

  Expand your skills 

[IBM Cloud Professional Architect Gain the skills and knowledge required to begin a career as an IBM Cloud Professional Architect.](https://www.ibm.com/training/path/ibmcloudprofessionalarchitect)[IBM Cloud Advanced Architect Concepts This badge earner has gained in-depth knowledge of scaling servers and databases, implementing application architecture, using compute options in solutions, designing environments for multicloud deployments, designing resilient solutions and applications, designing for RTO and RPO, disaster recovery, and designing highly available cloud solutions.](https://www.ibm.com/training/badge/ibm-cloud-advanced-architect-concepts)
Each persona uses different technical skills to successfully run and deploy apps to a cluster.

What are a cluster admin's main tasks and technical knowledge?
: As a cluster admin, you are responsible to set up, operate, secure, and manage the IBM Cloud infrastructure of your cluster. Typical tasks include:



* Size the cluster to provide enough capacity for your workloads.
* Design a cluster to meet the high availability, disaster recovery, and compliance standards of your company.
* Secure the cluster by setting up user permissions and limiting actions within the cluster to protect your compute resources, your network, and data.
* Plan and manage network communication between infrastructure components to ensure network security, segmentation, and compliance.
* Plan persistent storage options to meet data residency and data protection requirements.



The cluster admin persona must have a broad knowledge that includes compute, network, storage, security, and compliance. In a typical company, this knowledge is spread across multiple specialists, such as System Engineers, System Administrators, Network Engineers, Network Architects, IT Managers, or Security and Compliance Specialists. Consider assigning the cluster admin role to multiple people in your company so that you have the required knowledge to successfully operate your cluster.

What are an app developer's main tasks and technical skills?
: As a developer, you design, create, secure, deploy, test, run, and monitor cloud-native, containerized apps in an Kubernetes cluster. To create and run these apps, you must be familiar with the concept of microservices, the [12-factor app](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploy12factor) guidelines, [Docker and containerization principles](https://www.docker.com/), and available [Kubernetes deployment options](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploy).
When a mention is annotated as a coreference, the system creates a coreference chain. The coreference chain provides a way to view all of the mentions in context and verify that all of the occurrences belong together under the same entity type.





 corpus 

A collection of source documents that are used to train a machine learning model.





 credential 

Information acquired during authentication that describes a user, group associations, or other security-related identity attributes, and that is used to perform services such as authorization, auditing, or delegation. For example, a user ID and password are credentials that allow access to network and system resources.





 credit pool 

Within an enterprise billing unit, a consolidation of credit from all sources, including subscriptions and promotions, that is shared among accounts. See also [billing unit](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx9308099).





 CRN 

See [cloud resource name](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx9494304).





 crypto unit 

A single unit that represents a hardware security module and the corresponding software stack that is dedicated to the hardware security module for cryptography.





 cryptosystem 

A suite of algorithms that are used to implement a specific security service. Examples include RSA and Ed25519.





 CSR 

See [certificate signing request](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3530521).





 curate 

To select, collect, preserve, and maintain content relevant to a specific topic. Curation establishes, maintains, and adds value to data; it transforms data into trusted information and knowledge.





 custom domain 

The customized portion of the URL selected by the user to direct requests to the application. A custom domain makes up part of the route. A custom domain can be a shared domain, a shared subdomain, or a shared domain and host.
High availability for Satellite reference architecture 

As described in [High availability (HA) overview](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-high-availability), HA is important for all cloud-based applications. Ready to learn more specifics about HA in the Satellite reference architecture?



 High availability in your Satellite location 

For [HA in IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-hasatellite-ha-setup), you need to consider HA in three main areas within your Satellite location. For more information, see the following topics:



1. [Satellite control plane master](https://cloud.ibm.com/docs/satellite?topic=satellite-haha-control-plane-master)
2. [Satellite control plane worker nodes](https://cloud.ibm.com/docs/satellite?topic=satellite-haha-control-plane-worker)
3. [IBM Cloud services that run in your Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-haha-cloud-services) such as Red Hat OpenShift on IBM Cloud



In addition, you own all of the underlying infrastructure that the Satellite location components run on. Consider the following options to increase resiliency of that infrastructure:



* Add more compute hosts
* Add redundant power, network, and storage
* Isolate machines within one data center
* Spread hosts across physical locations





 Your workloads in Red Hat OpenShift on IBM Cloud 

After you have your underlying infrastructure in place, begin deploying your workloads in your on-premises Red Hat OpenShift on IBM Cloud workload clusters. You can use the cluster-autoscaler add-on to scale the worker pools in your cluster automatically to increase or decrease the number of worker nodes in the worker pool based on the sizing needs of your scheduled workloads.
These specific SRE individuals are assigned to the IRT schedule to also provide coverage.





 Client Requests for RCA 

RCA (Root Cause Analysis)

For Severity 1 incidents, IBM SRE and the Incident Response Team (IRT) have a primary goal to restore service and remediate any disruption as soon as possible. Addressing the symptoms of an issue can often be sufficient enough to successfully restore service, but the underlying root cause may not have been identified during this process due to time constraints. A Root Cause Analysis (RCA) can be requested by customers for further analysis to help identify the underlying cause. As part of this process, the client and/or their implementer may be required to review specific configurations within the Maximo or TRIRIGA application. Root Cause Analysis can include specific actions to prevent the same issue occurring again in the future. This detail will be given back to the client in the case itself, or in an associated child case if opened separately. Unlike an Incident Report, an RCA is not a separate document and doesn't include a summary of the primary issue or timeline of significant activity during the event. The original case will already have this detail captured.

Under what type of circumstances an RCA can be requested



* RCA's are only provided for production environments
* RCA's are provided for Severity 1 incidents that are outside of the agreed SLA (99.9% availability for the Production environment)
* RCA’s are not provided for single/isolated incidents
* RCA's can be provided for frequently recurring issues in production that have a significant impact on your business



How to request an RCA



* If the case in which the incident occurred is still open, customers can request a Root Cause Analysis as an entry within the case itself.
* If the case in which the incident occurred is closed, a new case should be opened by the customer specifically requesting an RCA. It should include the original case number of the incident.
* For example: "Request for RCA on TS00001111"



RCA lead times

An RCA can take between 5 to 10 business days to be completed. RCA detail will be provided in the applicable case.





 IBM Support Guides 

An IBM Support Guide for Maximo Application Suite is available. See link below.
For more information about how to flag documents, see [Flag documents of interest](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-cm-analyze-datacm-flags).





 Identify the text field 

When you analyze data with the Content Mining application, Discovery determines which field contains the body of the text to be analyzed. It does so by looking for the field with the highest average word count.

You can check which field is designated as the main text body field, and change it or augment it by changing the index type of another field.



1. Complete the steps in [Editing a collection](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-cm-edit-collectioncm-edit-collection-task) to get the collection into edit mode.
2. Click the Fields tab. Check the Index type column to find the field designated with the Analyzable text content index type.

You can change the field or set more than one text field to be an Analyzable text content index type.
3. Click Save.



If you select multiple fields to analyze, you cannot see the facet analysis for only one field. To view the analysis for multiple fields, you must group them.





 Group multiple text fields 



1. Complete the steps in [Editing a collection](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-cm-edit-collectioncm-edit-collection-task) to get the collection into edit mode.
2. Click the Contextual view tab, and then click Add view.
3. Complete the following fields:



* Name: The name or label of your grouped view.
* Id: The alphanumeric ID that Discovery uses when you submit a text query. For example, ans1.
* Fields: The text fields that have the Analyzable text content setting applied. Select one or multiple text fields that you want to group for facet analysis.



4. Click Add.

Repeat this task if you want to add more text fields that you want to group for facet analysis.
5.