diff --git a/ai/oracle-digital-assistant/README.md b/ai/oracle-digital-assistant/README.md index d75045cab..df8e2562b 100644 --- a/ai/oracle-digital-assistant/README.md +++ b/ai/oracle-digital-assistant/README.md @@ -12,9 +12,6 @@ Reviewed: 21.08.2025 # Team Publications -- [Solution Definition Document - Oracle Digital Assistant](#team-publications) - - A Template to use for ODA projects - - [ODA Multi Agent](https://github.com/oracle-devrel/technology-engineering/tree/main/ai/oracle-digital-assistant/oda-multi-agent) - Using Agent calling tools in ODA @@ -32,8 +29,8 @@ Reviewed: 21.08.2025 - [Live Lab - ODA with Generative AI Agent](https://livelabs.oracle.com/pls/apex/dbpm/r/livelabs/view-workshop?wid=4112) - Use ODA with Generative AI Agent to search documents like Word/Excel, Images, Video, Audio or Websites -- [Live Lab - Immerse Conversational Interfaces](https://apexapps.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=3452) - - How to combine Digital Assistant with other AI Services +- [Live Lab - Agentic Agents using Oracle Digital Assistant](https://livelabs.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=4212) + - Explore how to build Agentic AI using Oracle Digital Assistant ## Workshops diff --git a/ai/oracle-digital-assistant/oda-workshop/README.md b/ai/oracle-digital-assistant/oda-workshop/README.md index 40ca4ea08..8d027f0be 100644 --- a/ai/oracle-digital-assistant/oda-workshop/README.md +++ b/ai/oracle-digital-assistant/oda-workshop/README.md @@ -21,7 +21,7 @@ Conversational AI specialist this workshop is a proven methodology and many customers have used it as a major stepping stone in a successful Conversational AI strategy. -Reviewed: 31.10.2024 +Reviewed: 22.09.2025 # When to use this asset? diff --git a/ai/oracle-digital-assistant/solution-definition/LICENSE b/ai/oracle-digital-assistant/oda-workshop/files/LICENSE similarity index 97% rename from ai/oracle-digital-assistant/solution-definition/LICENSE rename to ai/oracle-digital-assistant/oda-workshop/files/LICENSE index 8dc7c0703..2e98a1e85 100644 --- a/ai/oracle-digital-assistant/solution-definition/LICENSE +++ b/ai/oracle-digital-assistant/oda-workshop/files/LICENSE @@ -1,35 +1,35 @@ -Copyright (c) 2025 Oracle and/or its affiliates. - -The Universal Permissive License (UPL), Version 1.0 - -Subject to the condition set forth below, permission is hereby granted to any -person obtaining a copy of this software, associated documentation and/or data -(collectively the "Software"), free of charge and under any and all copyright -rights in the Software, and any and all patent rights owned or freely -licensable by each licensor hereunder covering either (i) the unmodified -Software as contributed to or provided by such licensor, or (ii) the Larger -Works (as defined below), to deal in both - -(a) the Software, and -(b) any piece of software and/or hardware listed in the lrgrwrks.txt file if -one is included with the Software (each a "Larger Work" to which the Software -is contributed by such licensors), - -without restriction, including without limitation the rights to copy, create -derivative works of, display, perform, and distribute the Software and make, -use, sell, offer for sale, import, export, have made, and have sold the -Software and the Larger Work(s), and to sublicense the foregoing rights on -either these or other terms. - -This license is subject to the following condition: -The above copyright notice and either this complete permission notice or at -a minimum a reference to the UPL must be included in all copies or -substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. \ No newline at end of file +Copyright (c) 2025 Oracle and/or its affiliates. + +The Universal Permissive License (UPL), Version 1.0 + +Subject to the condition set forth below, permission is hereby granted to any +person obtaining a copy of this software, associated documentation and/or data +(collectively the "Software"), free of charge and under any and all copyright +rights in the Software, and any and all patent rights owned or freely +licensable by each licensor hereunder covering either (i) the unmodified +Software as contributed to or provided by such licensor, or (ii) the Larger +Works (as defined below), to deal in both + +(a) the Software, and +(b) any piece of software and/or hardware listed in the lrgrwrks.txt file if +one is included with the Software (each a "Larger Work" to which the Software +is contributed by such licensors), + +without restriction, including without limitation the rights to copy, create +derivative works of, display, perform, and distribute the Software and make, +use, sell, offer for sale, import, export, have made, and have sold the +Software and the Larger Work(s), and to sublicense the foregoing rights on +either these or other terms. + +This license is subject to the following condition: +The above copyright notice and either this complete permission notice or at +a minimum a reference to the UPL must be included in all copies or +substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/ai/oracle-digital-assistant/solution-definition/README.md b/ai/oracle-digital-assistant/solution-definition/README.md deleted file mode 100644 index 0ecd133d3..000000000 --- a/ai/oracle-digital-assistant/solution-definition/README.md +++ /dev/null @@ -1,24 +0,0 @@ -# Solution Definition Document ODA - -This is a documentation template for an ODA solution. It's based on an architecture best-practices pattern and needs to be tailored for different use cases and requirements. -This document provides a high-level solution definition for the Oracle Digital Assistant solution and aims at describing the current state, to-be state as well as a potential project scope and timeline. - -Reviewed: 31.10.2024 - -# When to use this asset? - -When you design a solution and want to describe it in a solution document. -The intended purpose is to provide all parties involved a clear and well-defined insight into the scope of work and intention of the project as it will be done as part of the Oracle service. - -# How to use this asset? - -Use the Word or Markdown template, and fill in the chapters with your relevant content and context. -Describe the customer's business and background. What is the context of the customer's industry and LoB? What are the business needs and goals that this Workload is an enabler for? How does this technical solution impact and support the customer's business goals? Does this solution support a specific customer strategy, or maybe certain customer values? How does this solution help our customers to either generate more revenue or save costs? - -# License - -Copyright (c) 2025 Oracle and/or its affiliates. - -Licensed under the Universal Permissive License (UPL), Version 1.0. - -See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details. diff --git a/ai/oracle-digital-assistant/solution-definition/files/Solution-Definition_ODA.md b/ai/oracle-digital-assistant/solution-definition/files/Solution-Definition_ODA.md deleted file mode 100644 index 4ac23d73b..000000000 --- a/ai/oracle-digital-assistant/solution-definition/files/Solution-Definition_ODA.md +++ /dev/null @@ -1,758 +0,0 @@ ---- -doc: - author: Maurits Dijkens #Mandatory - version: 3.0 #Mandatory - cover: #Mandatory - title: #Mandatory - - Solution Definition #Mandatory - - ODA to OCI #Mandatory - subtitle: #Mandatory - - Solution Definition #Mandatory - customer: #Mandatory - name: Customer #Mandatory - alias: Customer Alias #Mandatory - config: - impl: - type: TBD #Mandatory: Can be 'Oracle Lift', 'Oracle Fast Start', 'Partner' etc. Use with ${doc.config.impl.type} - handover: ${doc.customer.name} #Mandatory: Please specify to whom to hand over the project after implementation. eg.: The Customer, a 3rd party implementation or operations partner, etc. - draft: false - history: - - version: 1.0 - date: 1st June 2022 - authors: Martijn de Grunt - - Base Template - comments: - - Created a new WAD. To be used for iterative review and improvement. - - version: 3.0 - date: 25th October 2023 - authors: Maurits Dijkens - comments: - - Base Template - - Updated Template per new Solution Definition Guidelines. - team: - - name: Maurits Dijkens - email: maurits.dijkens@oracle.com - role: Tech Solution Specialist - company: Oracle - - name: Martijn de Grunt - email: martijn.grunt@oracle.com - role: Tech Solution Specialist - company: Oracle - acronyms: - Dev: Development ---- - -*Guide:* - -*Author Responsibility* - -- *Chapter 1-3: Sales Consultant* -- *Chapter 4: Implementer* - -# Document Control - - - -## Version Control - - - - -Version | Author | Date | Comment ---- | --- | --- | --- -3.0 | Maurits Dijkens | October 25th, 2023 | Updated Template per new Solution Definition Guidelines. -1.0 | Martijn de Grunt | June 1st, 2022 | First version (WAD) - - -## Team - - - - -Name | eMail | Role | Company ---- | --- | --- | --- -Name | name.surname@oracle.com | Cloud Architect | Oracle - - -## Abbreviations List - -Abbreviation | Meaning -------|----------------------------------------- -OCI | Oracle Cloud Infrastructure -ODA | Oracle Digital Assistant -IDCS | Identity Cloud service -OIC | Oracle Integration Cloud -VBCS | Visual Builder Cloud Service -API | Applicaton Programming Interface -ATP | Oracle Autonomous Transaction Processing -PaaS | Platform as a service -IaaS | Infrastructure as a service -FAQs | Frequently Asked Questions -IdP | Identity provider -SP | Service Provider -RTO | Recovery Time Objective -RPO | Recovery Point Operation - -## Document Purpose -This document provides a high-level solution definition for the Oracle Digital Assistant solution and aims at describing the current state, to-be state as well as a potential 'Oracle ${doc.config.impl.type}' project scope and timeline. The intended purpose is to provide all parties involved a clear and well-defined insight into the scope of work and intention of the project as it will be done as part of the Oracle ${doc.config.impl.type} service. - -# Business Context - - -*Guide:* - -*Describe the customer's business and background. What is the context of the customer's industry and LoB? What are the business needs and goals that this Workload is an enabler for? How does this technical solution impact and support the customer's business goals? Does this solution support a specific customer strategy, or maybe certain customer values? How does this solution help our customers to either generate more revenue or save costs?* - -## Executive Summary - - -*Guide:* - -*A section describing the Oracle differentiator and key values of the solution of our solution for the customer, allowing the customer to make decisions quickly.* - -## Workload Business Value - - -*Guide:* - -*A clear statement of specific business value as part of the full workload scope. Try to keep it SMART: Specific, Measurable, Assignable, Realistic, and Time-Related - Agree on the business value with the customer. Keep it business-focused, and speak the language of the LoB which benefits from this Workload: "Increase Customer Retention by 3% in the next year" or "Grow Customer Base with Executive Decision-Making from our Sales and Support Data". Avoid technical success criteria such as "Migrate App X to Oracle Cloud" or "Provision 5 Compute Instances". Avoid Oracle success criteria and language "Get Workload Consuming on OCI".* - - - - - -# Workload Requirements and Architecture - -## Overview - - -*Guide:* - -*Describe the Workload: What applications and environments are part of this Workload migration or new implementation project, and what are their names? The implementation will be scoped later and can be a subset of the Solution Definition and proposed overall solution. For example, a Workload could exist of two applications, but the implementer would only include one environment of one application. The workload chapter is about the whole Workload and the implementation scope will be described later in the chapter [Solution Scope](#solution-scope).* - -## Non-Functional Requirements - - -*Guide:* - -*Describe the high-level technical requirements for the Workload. Consider all sub-chapters, but decide and choose which Non-Functional Requirements are necessary for your engagement. You might not need to capture all requirements for all sub-chapters.* - -*This chapter is for describing customer-specific requirements (needs), not to explain Oracle solutions or capabilities.* - -### Regulations and Compliances Requirements - -*Guide:* - -*This section captures specific regulatory or compliance requirements for the Workload. These may limit the types of technologies that can be used and may drive some architectural decisions.* - -*The Oracle Cloud Infrastructure Compliance Documents service lets you view and download compliance documents: -https://docs.oracle.com/en-us/iaas/Content/ComplianceDocuments/Concepts/compliancedocsoverview.htm* - -*If there are none, then please state it. Leave the second sentence as a default in the document.* - -*Example:* - -At the time of this document creation, no Regulatory and Compliance requirements have been specified. - -In addition to these requirements, the [CIS Oracle Cloud Infrastructure Foundation Benchmark, v1.2](https://www.cisecurity.org/benchmark/Oracle_Cloud) will be applied to the Customer tenancy. - -### Environments - -*Guide:* - -*A diagram or list detailing all the required environments (e.g. development, text, live, production, etc.).* - -*If you like to describe a current state, you can use or add the chapter 'Current Sate Architecture' before the 'Future State Architecture'.* - - -Example: - -Name | Size of Prod | Location | DR | Scope -:--- |:--- |:--- |:--- |:--- -Production | 100% | Malaga | Yes | Not in Scope / On-prem -DR | 50% | Sevilla | No | Workload -Dev & Test | 25% | Sevilla | No | Workload - ${doc.config.impl.type} - - -### High Availability and Disaster Recovery Requirements - -*Guide:* - -*This section captures the resilience and recovery requirements for the Workload. Note that these may be different from the current system.* - -*The Recovery Point Objective (RPO) and Recovery Time Objective (RTO) requirement of each environment should be captured in the environments section above, and wherever possible.* - -- *What are the RTO and RPO requirements of the Application?* -- *What are the SLAs of the application?* -- *What are the backup requirements* - -*Note that if needed, this section may also include an overview of the proposed backup and disaster recovery proposed architectures.* - -*This chapter is mandatory, while there could be no requirements on HA/DR, please mention that in a short single sentence.* - -*Example:* - -At the time of this document creation, no Resilience or Recovery requirements have been specified. - -### Security Requirements - -*Guide:* - -*Capture the Non-Functional Requirements for security-related topics. The requirements can be (but don't have to be) separated into:* -- *Identity and Access Management* -- *Data Security* - -*Other security topics, such as network security, application security, key management, or others can be added if needed.* - -*Example:* - -At the time of this document creation, no Security requirements have been specified. - -### Networking Requirements - -*Guide* - -*Capture the Non-Functional Requirements for networking-related topics. You can use the networking questions in the [Annex](#networking-requirement-considerations)* - -*Example:* - -At the time of this document creation, no Networking requirements have been specified. - -## Future State Architecture - - -*Guide:* - -*The Workload Future State Architecture can be described in various forms. In the easiest case, we describe a Logical Architecture, possibly with a System Context Diagram. A high-level physical architecture is mandatory as a description of your solution.* - -*This should be the final architecture as part of the pre-sales solution, not an intermediate or draft version* - -*Additional architectures, in the subsections, can be used to describe needs for specific workloads.* - -### Mandatory Security Best Practices - -*Guide:* - -*Use this text for every engagement. Do not change. Aligned with the Cloud Adoption Framework* - -```{.snippet} -sec-best-practices -``` - -### Naming Conventions - -*Guide:* - -*This chapter describes naming convention best practices and usually does not require any changes. If changes are required please refer to [Landing Zone GitHub](https://github.com/oracle-devrel/technology-engineering/tree/main/landing-zones). The naming convention zone needs to be described in the Solution Design by the service provider.* - -*Use this template ONLY for new cloud deployments and remove it for brownfield deployments.* - -```{.snippet} -ar-naming-convention -``` - -### OCI Landing Zone Solution Definition - -*Guide:* - -*This chapter describes landing zone best practices and usually does not require any changes. If changes are required please refer to [Landing Zone GitHub](https://github.com/oracle-devrel/technology-engineering/tree/main/landing-zones). The full landing zone needs to be described in the Solution Design by the service provider.* - -*Use this template ONLY for new cloud deployments and remove it for brownfield deployments.* - -```{.snippet} -ar-landingzone -``` - -### Logical Architecture - - -*Guide:* - -*Provide a high-level logical Oracle solution for the complete Workload. Indicate Oracle products as abstract groups, and not as physical detailed instances. Create an architecture diagram following the latest notation and describe the solution.* - -*To implement a solution the Physical Architecture is needed in the next chapter. The physical notation can show individual components with physical attributes such as IP addresses, hostnames, or sizes.* - -*[The Oracle Cloud Notation, OCI Architecture Diagram Toolkits](https://docs.oracle.com/en-us/iaas/Content/General/Reference/graphicsfordiagrams.htm)* - -### Physical Architecture - - -*Guide:* - -*The Workload Architecture is typically described in a physical form. This should include all solution components. You do not have to provide solution build or deployment details such as IP addresses.* - -*Please describe the solution with an architecture image plus a written text. If you have certain specifics you like to explain, you can also use the Solution Consideration chapter to describe the details there.* - -*[The Oracle Cloud Notation, OCI Architecture Diagram Toolkits](https://docs.oracle.com/en-us/iaas/Content/General/Reference/graphicsfordiagrams.htm)* - -*Reference:* - -[StarterPacks (use the search)](https://github.com/oracle-devrel/technology-engineering/) - -*Example:* - -![Future State Deployment Diagram - EBS Workload Multi-AD, DR Design Diagram](images/MultiADDR-DeploymentDiagram-V2.pdf) - -## Solution Considerations - - -*Guide:* - -*Describe certain aspects of your solution in detail. What are the security, resilience, networking, and operations decisions you have taken that are important for your customer?* - -### High Availability and Disaster Recovery - -*Reference:* - -- [Resilliance on OCI](https://docs.public.oneportal.content.oci.oraclecloud.com/en-us/iaas/Content/cloud-adoption-framework/era-resiliency.htm) -- [Workload Related Content](https://github.com/oracle-devrel/technology-engineering/) - -### Security - -*Guide:* - -*Please describe your solution from a security point of view. Generic security guidelines are in the Annex chapter.* - -*Example:* - -Please see our security guidelines in the [Annex](#security-guidelines). - -### Networking - -*Reference:* - -*A list of possible Oracle solutions can be found in the [Annex](#networking-solutions).* - -## Sizing and Bill of Materials - - -*Guide:* - -*Estimate and size the physically needed resources of the Workload. The information can be collected and is based upon previously gathered capacities, business user numbers, integration points, or translated existing on-premises resources. The sizing is possibly done with or even without a Physical Architecture. It is okay to make assumptions and to clearly state them!* - -*Clarify with sales your assumptions and your sizing. Get your sales to finalize the BoM with discounts or other sales calculations. Review the final BoM and ensure the sales are using the correct product SKUs / Part Number.* - -*Even if the BoM and sizing were done with the help of Excel between the different teams, ensure that this chapter includes or links to the final BoM as well.* - -*WIP* -- *Revision of existing discovery templates* -- *Consolidated data gathering sheet (sizing focused)* -- *Workload-specific sizing process/methodology* - - - - - - - -# Project Implementation (Only for Oracle Implementations!) - -## Solution Scope - -### Disclaimer - - -*Guide:* - -*A scope disclaimer should limit scope changes and create awareness that a change of scope needs to be agreed upon by both parties.* - -*Example:* - -```{.snippet} -uc-disclaimer -``` - -### Overview - - -*Guide:* - -*Describe the scope of the implementation as a sub-set of the Workload scope. For example one environment from one application.* - -*Example:* - -- Design and configure “least privilege” access controls and enable user access using OCI IAM compartments, groups, and policies. -- Design and provide a secure, scalable OCI network architecture. - - -### Business Value - - -*Guide:* - -*What's the value for the customer to do an Oracle implementation? For example, speed of deployment and the resulting impact on time to market, and free service. Do not describe Oracle's value or consumption.* - -*Example:* - -```{.snippet} -uc-business-value -``` - -### Success Criteria - - -*Guide:* - -*Technical success criteria for the implementation. As always be S.M.A.R.T: Specific, Measurable, Achievable, Relevant, Timebound. Example: 'Deployment of all OCI resources for the scoped environments in 3 months'.* - -*Example:* - -The below-listed success criteria are for the ${doc.config.impl.type} implementation only. Partner activities and success criteria are not listed in this documentation. - -- Finish provisioning of all OCI resources -- Establish all required network connectivity -- Successfully pass all test cases -- Finished handover with documentation -- Complete the Implementation Security Checklist - -## Workplan - -### Deliverables - - -*Guide:* - -*Describe deliverables within the implementation scope. Including this documentation as Solution Definition and the later following Solution Design. This should be a generic reusable text, provided by the implementers.* - -### Included Activities - - -*Guide:* - -*Describe the implementation activities in detail. It does not need to include a list of cloud services or OCI capabilities, but rather includes activities such as 'Provisioning of Infrastructure Components'. Include scope boundaries in terms of the number of environments, resource count to be provisioned, data volume to be migrated, etc.* - -*Example:* -The implementation scope of work includes the following activities: - -**OCI Foundation & Network** -- OCI Foundation Setup - 1 Region (REGION NAME) -- OCI Networking configuration - * Creation of VCN for up to 3 environments (up to 12 VCNs total) - * DRG and inter-VCN routing - * Deployment of standard Security lists and NSG in VCN - * Deployment of Route Tables in VCNs -- Configure one site-to-site IPSec VPN between OCI & on-premises -- Configure Web Application Firewall to route the incoming internet traffic to Load Balancers and configure recommended rules -- Configure bastion service to allow admin users to connect to the tenancy through the internet access - -**Security** -- Enable Cloud Guard -- Enable Datasafe and Register the Databases in scope -- Enable VSS -- Configure OCI IAM Domains - -**Database** -- Migrate one non-prod database with one iteration -- Migrate one prod database with two iterations - -### Recommended Activities - - -*Guide:* - -*All activities not stated in the [Included Activities](#included-activities) are out of scope, as described in the [Disclaimer](#disclaimer). We do not provide a list of excluded activities to not create expectations based on a grey area between included and excluded activities. Here we only recommend further activities that happen to not be included but are not a full list of excluded activities.* - -*Example:* - -All items not explicitly stated to be within the scope of the implementation project will be considered out of scope. Oracle recommends the use of professional services to implement extensions or customizations beyond the original scope, or to operate the solution with any of Oracle's certified partners. As a part of this engagement, the below activities are considered to be out of implementation scope. - -- Any activities at customer on-premises or existing data center e.g. patching & backups required for migration -- Any integration with other products than in scope -- Any backup and recovery strategy implementation including third-party backup tool implementation -- Application upgrade of any Oracle or other vendor or open source software. -- SSL certificate management and configuration -- Any form of testing and validations, including but not limited to performance testing, load testing, HA testing, DR testing, and tuning of any component in the solution -- Any vulnerability assessment and penetration testing including server hardening, audit certification implementation -- Any functional testing is to be conducted by the customer and/or third party involved -- Any third-party firewall implementation, security tools, monitoring tools implementation -- Troubleshooting existing open issues, including the performance of the application -- Training on deployed products and OCI services -- Run and maintain the support of the environment and end-user training - - -### Timeline - - -*Guide:* - -*Provide a high-level implementation plan. Use phases to communicate an iterative implementation if needed. Include prerequisites in the plan.* - -#### Phase 1: - -#### Phase n: - -### Implementation RACI -*Guide:* - -*Describe for all activities the RACI (Responsible, Accountable, Consultant, Informed) matrix* - -*Example:* - -Num | Activity | Oracle | Customer ---- | ------ | --- | --- -1 | Conduct Project Kickoff | AR | C -2 | Provide access to the source environment, including all the relevant ports opened | I |AR -3 | Provide VPN credentials for Oracle team, OCI console access details | I | AR -4 | Prepare Source System, apply required patches on source environments for migration, and take source environment backup to OCI | I | AR -5 | Backup of source Database | C | AR -6 | Provision Landing Zone with related Network and policies in scope | AR | C -7 | Configure site-to-site VPN between onPrem and OCI tenancy | AR | C -8 | Migrate non-Prod database in scope | AR | C -9 | Perform Pre and Post functional migration tasks | I | AR -10 | Perform functional/customization/integration testing and Validation of application within the project timeline | I | AR -11 | Provide OCI technical support during validation | AR | C -12 | Prepare production runbook and perform Production Cutover | C | AR -13 | Provide timely support for HW, OS, network related issues at source | I | AR -14 | Procure of SSL Certificates | C | AR -15 | Provide access to My Oracle Support required for product support along with CSI number | I | AR - -**R- Responsible, A- Accountable, C- Consulted, I- Informed ** - - -### Assumptions - - -*Guide:* - -*List any assumptions, if any, which could impact the solution architecture or the implementation.* - -*Example:* - -**Generic assumptions** -- It is assumed that all required contractual agreements between Oracle and the Customer are in place to ensure uninterrupted execution of the project. -- It is assumed that all work will be done remotely and within either central European time or India Standard Time normal office working hours. -- It is assumed that upgrades are excluded from the scope of work and no production systems/production cutover is part of the scope of work undertaken by the Oracle Service -- It is assumed that all required Oracle cloud technical resources are available for use during the duration of the project and that engineers involved have been granted the appropriate access to those technical resources by the customer before the start of the project. -- It is assumed that all required customer resources, and if applicable third-party resources, are available during the duration of the project to work openly and collaboratively to realize the project goals uninterruptedly. -- It is assumed that all required customer resources, and if applicable third-party resources are aware of all technical and non-technical details of the as-is and to-be components. All resources are committed to technical work as far as is needed for the execution of the project. -- It is assumed that all required documentation, system details, and access needed for the execution of the project can be given/granted to parties involved when and where deemed needed for the success of the project. -- It is assumed that the customer will have adequate licenses for all the products that may/will be used during the project and that appropriate support contracts for those products are in place where the customer will take the responsibility of managing any potential service request towards a support organization to seek resolution of a problem. -- It is assumed the customer will provide the appropriate level of information and guidance on rules and regulations which can directly and/or indirectly influence the project or the resulting deliverables. This includes, however not limited to, customer-specific naming conventions, security implementation requirements, internal SLA requirements as well as details for legal and regulatory compliance. It will be the responsibility of the customer to ensure that the solution will adhere to this. -- It is assumed that under the customer's responsibility, the customer will ensure and validate that the solution will be placed under the proper controls for ensuring business continuity, system availability, recoverability, security control, and monitoring and management as part of a post-project task. -- It is assumed that the customer will take responsibility for testing all functional and non-functional parts of the solution within the provided timeline and ensure a proper test report will be shared with the full team (including customer, Oracle, and if applicable third party). -- It is assumed that any requirement, deliverable, or expectation that is not clearly defined as in-scope of the project will not be handled as part of the project and is placed under the responsibility of the customer to be handled outside of the project. - -**Project-specific assumptions** -- It is assumed that sufficient network bandwidth (greater than 200 GB) is available between OCI and Customer onPremise for any data transfer. -- It is assumed that the customer, or a partner of your choice, will own the control, access, management, and further development of your OCI environment following the deployment of your solution. - -### Obligations - - -*Guide:* - -*List any obligations required by the customer to perform or have available, if any, which could impact the architecture or the implementation. Please always include this chapter to capture the obligation that we have admin access to the customer's tenancy.* - -*Example:* - -- You will have purchased the appropriate Universal Credits for the services required for the project. -- The implementation team will have admin access to the customer's tenancy for implementation. -- You will ensure the appropriate product training has been obtained to maintain and support the implementation -- Your business team will be available for the Testing phase, which will be completed within the agreed testing window. -- You will provide project management for the project and will manage any third-party suppliers or vendors. -- You will provide the implementation team with appropriate access to your tenancy & relevant on-premises applications/database to perform implementation activities. We recommend the least-privilege access principle. -- You will revoke implementor access on production goLive or after project completion. -- You will take consistent and restorable backups of your existing data and application before implementation. - -**Add for EBS migration** -- Your on-premise source non-prod environment would be a fresh clone from the production environment for easy simulation of issues. -- You would be responsible for applying and testing all migration-related patches on the on-premise source environment. -- You will ensure that the relevant pre-requisite patches have been applied on the on-premise source environment as per MOS DocID 2517025.1: Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure: - * Table 5 - Source Environment Requirements with Target Database Tier on Oracle Cloud Infrastructure Compute VM (Under 4.2.2 section) and - * Section 4.5.5 Applying the Latest Critical Patch Updates (CPU) and Security Fixes - - -### Transition Plan - - -*Guide:* - -*The Transition Plan describes the handover of the project, after the implementation. Please ensure the accepting transition party is filled out.* - -```{.snippet} -uc-transition-plan -``` - -# Annex - - -## Security Guidelines - -```{.snippet} -annex-common-security -``` - -## Networking Requirement Considerations - -```{.snippet} -annex-common-networking -``` - -## Networking Solutions - -```{.snippet} -networking-products -``` - - diff --git a/ai/oracle-digital-assistant/solution-definition/files/Solution-Definition_ODA.pdf b/ai/oracle-digital-assistant/solution-definition/files/Solution-Definition_ODA.pdf deleted file mode 100644 index 663a6ddea..000000000 Binary files a/ai/oracle-digital-assistant/solution-definition/files/Solution-Definition_ODA.pdf and /dev/null differ diff --git a/ai/oracle-digital-assistant/templates/concierge-template/README.md b/ai/oracle-digital-assistant/templates/concierge-template/README.md index d9c1cce8a..abb023530 100644 --- a/ai/oracle-digital-assistant/templates/concierge-template/README.md +++ b/ai/oracle-digital-assistant/templates/concierge-template/README.md @@ -2,7 +2,7 @@ The Concierge Template is a skill for quickly setting up a Knowledge bot. -Reviewed: 31.10.2024 +Reviewed: 22.09.2025 Concierge Template WebSDK diff --git a/ai/oracle-digital-assistant/templates/hcm-ml/README.md b/ai/oracle-digital-assistant/templates/hcm-ml/README.md index 73ba4a7ed..af69b9e26 100644 --- a/ai/oracle-digital-assistant/templates/hcm-ml/README.md +++ b/ai/oracle-digital-assistant/templates/hcm-ml/README.md @@ -3,7 +3,7 @@ The HCM-ML Template is a quick start to easily add multi language and Q&A to the HCM out-of-the-box skill. The provided documentations describes an entry-level exercise to start working with Oracle Digital Assistant using the HCM_ML template as a starting point to use the HCM SaaS skill in a multi-lingual way. -Reviewed: 31.10.2024 +Reviewed: 22.09.2025 # When to use this asset?