When to Consider Exceptions to an Appian Shared Environment

Appian Max Team — Tue, 23 Apr 2024 13:06:56 GMT

Current Revision posted to Article by Appian Max Team on 4/23/2024 1:06:56 PM

Introduction

Appian strongly recommends to use a shared platform for all users and applications. This helps ensure that your business can scale effectively and efficiently while maintaining superior digital experience for your customers. Listed below are some of the compelling factors in favor of setting up a shared Appian platform within an enterprise:

Real Time Visibility and Unified View
Overall Savings in Total Cost of Ownership (TCO)
Seamless, Consistent and Personalized User Experience
Significant Process Efficiency Improvements

In certain rare scenarios, customers are forced to opt out of this approach and go with a segregated installation instead. This document compares the two setups and lists out some of the exceptional scenarios when customers take the segregated installation route.

Setups

In a Segregated Installation setup, each of the applications are hosted on their respective platform and a separate Appian url is provided to the users to login into the separate Appian interfaces.

In a Shared Platform setup, each of the enterprise applications is hosted on the single Appian instance, and users of all applications use a unique Appian url.

Comparative Analysis

The table below is a comparative analysis of the two installation approaches in light of some of the influencing factors:

#	Influencing Factor	Segregated Installation	Shared Platform	Decision Drivers	Details
1	Enterprise Agility(Definition)			Real-Time Visibility Low Information Cost Better Customer Experience	As customers continue to increase Appian adoption across the enterprise, a Shared platform helps build synergies across different enterprise functions, generating personalized insights and thereby faster response to outside situations.
2	Overall TCO			Operational and Maintenance Cost Infrastructure Maintenance Platform Upgrades & Hotfixing	Significant time & resource investment, along with redundant effort is required for performing server maintenance and management across multiple environments.
3	End User Productivity			Single Source of Truth Data Integrity Lesser Confusion Avoid Unnecessary Time Delays	For application spanning multiple Lines of Business, user productivity is significantly better if all information is available in a single Appian system.
4	Data & User Security (Compartmentalization)			External vs Internal vs Contractual Users Confidentiality Requirements Regulatory Requirements	It is not uncommon for customers to compartmentalize the enterprise systems as a risk mitigation measure for issues that can potentially arise due to data confidentiality or a security breach.
5	Geographic Scaling & Expansion Costs			Global Applications Seamless Rollouts	Expansion to new geographies, markets, and product lines can be accomplished faster with an integrated platform.
6	Change Management & Platform Governance			Comprehensive Change Management Planning Platform Management and Governance Program Management Business Review with Stakeholders Enterprise Communication Plan Shared Services Management	Some investment is needed upfront while devising an enterprise strategy on a Shared platform. Also, ongoing collaboration is required between IT & Business leadership to ensure successful adoption of the platform.
7	Different Non-Functional Requirements			High Availability Business Continuity Data Retention SLAs - RPO, RTO	Not all enterprise applications are expected to fit in the same category of non-functional requirements. For example, certain mission critical applications may have strict uptime requirements while a simple survey application may not. Advanced infrastructure configuration comes at a higher cost and this may not be commensurate to justify investment for certain applications
8	Trend Reporting and Decisioning			End to End View of the System Tailored reporting to suit any business function - C Level / Middle Management	Reporting and thus decision making is significantly enhanced and expedited if the data aggregation is done across records residing on the Shared platform
9	Reuse and Collaboration			Develop common components & services Shared Appian Best Practices Center of Excellence	Well channelized team dynamics can lead to significant cost savings if common code can be reused across multiple applications on the platform. Teams working on the same platform environment tend to have better understanding and cohesion leading to better collaboration and thus better ROI.

Exception Scenarios

The table below lists out some of the exception scenarios when to consider a Segregated Appian installation.

#	Scenario	Key Factors
1	Customer has a mission critical application with very high transaction volumes and 24x7 site availability with virtually no tolerance for downtime. The application is so critical that it requires its own dedicated hardware and environment.	High daily business volumes High availability Very high resource utilization
2	Customer whose industry is heavily regulated and who is required to comply with rules, regulations, controls and strict processes related to their data/security/workflow	Data Security Standards & Policies Compliance & Regulation (Internal/External) Geographic Challenges
3	Applications deal with secured/sensitive data and unsecured/publicly available data. The risks of accidentally exposing data to the wrong users is a risk that must be mitigated and avoided at all cost.	Data & User Security Overall TCO
4	Applications have distinct and non-overlapping user sets, data sets, or processes, with little to no potential benefits accruing from aggregate analysis, process standardization, or economies of scale	Distinct and separate user communities No data requirements in common High degree of domain specialization Discreet and independent process flows

Tags: environments, Solutions Architecture, Platform

When to Consider Exceptions to an Appian Shared Environment

joel.larin — Thu, 02 Nov 2023 14:49:17 GMT

Revision 6 posted to Article by joel.larin on 11/2/2023 2:49:17 PM

Introduction

Real Time Visibility and Unified View
Overall Savings in Total Cost of Ownership (TCO)
Seamless, Consistent and Personalized User Experience
Significant Process Efficiency Improvements

Setups

In a Segregated Installation setup, each of the applications are hosted on their respective platform and a separate Appian url is provided to the users to login into the separate Appian interfaces.

In a Shared Platform setup, each of the enterprise applications is hosted on the single Appian instance, and users of all applications use a unique Appian url.

Comparative Analysis

The table below is a comparative analysis of the two installation approaches in light of some of the influencing factors:

#	Influencing Factor	Segregated Installation	Shared Platform	Decision Drivers	Details
1	Enterprise Agility(Definition)			Real-Time Visibility Low Information Cost Better Customer Experience	As customers continue to increase Appian adoption across the enterprise, a Shared platform helps build synergies across different enterprise functions, generating personalized insights and thereby faster response to outside situations.
2	Overall TCO			Operational and Maintenance Cost Infrastructure Maintenance Platform Upgrades & Hotfixing	Significant time & resource investment, along with redundant effort is required for performing server maintenance and management across multiple environments.
3	End User Productivity			Single Source of Truth Data Integrity Lesser Confusion Avoid Unnecessary Time Delays	For application spanning multiple Lines of Business, user productivity is significantly better if all information is available in a single Appian system.
4	Data & User Security (Compartmentalization)			External vs Internal vs Contractual Users Confidentiality Requirements Regulatory Requirements	It is not uncommon for customers to compartmentalize the enterprise systems as a risk mitigation measure for issues that can potentially arise due to data confidentiality or a security breach.
5	Geographic Scaling & Expansion Costs			Global Applications Seamless Rollouts	Expansion to new geographies, markets, and product lines can be accomplished faster with an integrated platform.
6	Change Management & Platform Governance			Comprehensive Change Management Planning Platform Management and Governance Program Management Business Review with Stakeholders Enterprise Communication Plan Shared Services Management	Some investment is needed upfront while devising an enterprise strategy on a Shared platform. Also, ongoing collaboration is required between IT & Business leadership to ensure successful adoption of the platform.
7	Different Non-Functional Requirements			High Availability Business Continuity Data Retention SLAs - RPO, RTO	Not all enterprise applications are expected to fit in the same category of non-functional requirements. For example, certain mission critical applications may have strict uptime requirements while a simple survey application may not. Advanced infrastructure configuration comes at a higher cost and this may not be commensurate to justify investment for certain applications
8	Trend Reporting and Decisioning			End to End View of the System Tailored reporting to suit any business function - C Level / Middle Management	Reporting and thus decision making is significantly enhanced and expedited if the data aggregation is done across records residing on the Shared platform
9	Reuse and Collaboration			Develop common components & services Shared Appian Best Practices Center of Excellence	Well channelized team dynamics can lead to significant cost savings if common code can be reused across multiple applications on the platform. Teams working on the same platform environment tend to have better understanding and cohesion leading to better collaboration and thus better ROI.

Exception Scenarios

The table below lists out some of the exception scenarios when to consider a Segregated Appian installation.

#	Scenario	Key Factors
1	Customer has a mission critical application with very high transaction volumes and 24x7 site availability with virtually no tolerance for downtime. The application is so critical that it requires its own dedicated hardware and environment.	High daily business volumes High availability Very high resource utilization
2	Customer whose industry is heavily regulated and who is required to comply with rules, regulations, controls and strict processes related to their data/security/workflow	Data Security Standards & Policies Compliance & Regulation (Internal/External) Geographic Challenges
3	Applications deal with secured/sensitive data and unsecured/publicly available data. The risks of accidentally exposing data to the wrong users is a risk that must be mitigated and avoided at all cost.	Data & User Security Overall TCO
4	Applications have distinct and non-overlapping user sets, data sets, or processes, with little to no potential benefits accruing from aggregate analysis, process standardization, or economies of scale	Distinct and separate user communities No data requirements in common High degree of domain specialization Discreet and independent process flows

Tags: environments, Solutions Architecture, Platform

When to Consider Exceptions to an Appian Shared Environment

joel.larin — Thu, 02 Nov 2023 14:48:42 GMT

Revision 5 posted to Article by joel.larin on 11/2/2023 2:48:42 PM

Introduction

Real Time Visibility and Unified View
Overall Savings in Total Cost of Ownership (TCO)
Seamless, Consistent and Personalized User Experience
Significant Process Efficiency Improvements

Setups

In a Segregated Installation setup, each of the applications are hosted on their respective platform and a separate Appian url is provided to the users to login into the separate Appian interfaces.

In a Shared Platform setup, each of the enterprise applications is hosted on the single Appian instance, and users of all applications use a unique Appian url.

Comparative Analysis

The table below is a comparative analysis of the two installation approaches in light of some of the influencing factors:

#	Influencing Factor	Segregated Installation	Shared Platform	Decision Drivers	Details
1	Enterprise Agility(Definition)			Real-Time Visibility Low Information Cost Better Customer Experience	As customers continue to increase Appian adoption across the enterprise, a Shared platform helps build synergies across different enterprise functions, generating personalized insights and thereby faster response to outside situations.
2	Overall TCO			Operational and Maintenance Cost Infrastructure Maintenance Platform Upgrades & Hotfixing	Significant time & resource investment, along with redundant effort is required for performing server maintenance and management across multiple environments.
3	End User Productivity			Single Source of Truth Data Integrity Lesser Confusion Avoid Unnecessary Time Delays	For application spanning multiple Lines of Business, user productivity is significantly better if all information is available in a single Appian system.
4	Data & User Security (Compartmentalization)			External vs Internal vs Contractual Users Confidentiality Requirements Regulatory Requirements	It is not uncommon for customers to compartmentalize the enterprise systems as a risk mitigation measure for issues that can potentially arise due to data confidentiality or a security breach.
5	Geographic Scaling & Expansion Costs			Global Applications Seamless Rollouts	Expansion to new geographies, markets, and product lines can be accomplished faster with an integrated platform.
6	Change Management & Platform Governance			Comprehensive Change Management Planning Platform Management and Governance Program Management Business Review with Stakeholders Enterprise Communication Plan Shared Services Management	Some investment is needed upfront while devising an enterprise strategy on a Shared platform. Also, ongoing collaboration is required between IT & Business leadership to ensure successful adoption of the platform.
7	Different Non-Functional Requirements			High Availability Business Continuity Data Retention SLAs - RPO, RTO	Not all enterprise applications are expected to fit in the same category of non-functional requirements. For example, certain mission critical applications may have strict uptime requirements while a simple survey application may not. Advanced infrastructure configuration comes at a higher cost and this may not be commensurate to justify investment for certain applications
8	Trend Reporting and Decisioning			End to End View of the System Tailored reporting to suit any business function - C Level / Middle Management	Reporting and thus decision making is significantly enhanced and expedited if the data aggregation is done across records residing on the Shared platform
9	Reuse and Collaboration			Develop common components & services Shared Appian Best Practices Center of Excellence	Well channelized team dynamics can lead to significant cost savings if common code can be reused across multiple applications on the platform. Teams working on the same platform environment tend to have better understanding and cohesion leading to better collaboration and thus better ROI.

Exception Scenarios

The table below lists out some of the exception scenarios when to consider a Segregated Appian installation.

#	Scenario	Key Factors
1	Customer has a mission critical application with very high transaction volumes and 24x7 site availability with virtually no tolerance for downtime. The application is so critical that it requires its own dedicated hardware and environment.	High daily business volumes High availability Very high resource utilization
2	Customer whose industry is heavily regulated and who is required to comply with rules, regulations, controls and strict processes related to their data/security/workflow	Data Security Standards & Policies Compliance & Regulation (Internal/External) Geographic Challenges
3	Applications deal with secured/sensitive data and unsecured/publicly available data. The risks of accidentally exposing data to the wrong users is a risk that must be mitigated and avoided at all cost.	Data & User Security Overall TCO
4	Applications have distinct and non-overlapping user sets, data sets, or processes, with little to no potential benefits accruing from aggregate analysis, process standardization, or economies of scale	Distinct and separate user communities No data requirements in common High degree of domain specialization Discreet and independent process flows

Tags: environments, Solutions Architecture, Platform

When to Consider Exceptions to an Appian Shared Environment

joel.larin — Thu, 02 Nov 2023 14:47:15 GMT

Revision 4 posted to Article by joel.larin on 11/2/2023 2:47:15 PM

Introduction

Real Time Visibility and Unified View
Overall Savings in Total Cost of Ownership (TCO)
Seamless, Consistent and Personalized User Experience
Significant Process Efficiency Improvements

Setups

In a Segregated Installation setup, each of the applications are hosted on their respective platform and a separate Appian url is provided to the users to login into the separate Appian interfaces.

In a Shared Platform setup, each of the enterprise applications is hosted on the single Appian instance, and users of all applications use a unique Appian url.

Comparative Analysis

The table below is a comparative analysis of the two installation approaches in light of some of the influencing factors:

#	Influencing Factor	Segregated Installation	Shared Platform	Decision Drivers	Details
1	Enterprise Agility(Definition)			Real-Time Visibility Low Information Cost Better Customer Experience	As customers continue to increase Appian adoption across the enterprise, a Shared platform helps build synergies across different enterprise functions, generating personalized insights and thereby faster response to outside situations.
2	Overall TCO			Operational and Maintenance Cost Infrastructure Maintenance Platform Upgrades & Hotfixing	Significant time & resource investment, along with redundant effort is required for performing server maintenance and management across multiple environments.
3	End User Productivity			Single Source of Truth Data Integrity Lesser Confusion Avoid Unnecessary Time Delays	For application spanning multiple Lines of Business, user productivity is significantly better if all information is available in a single Appian system.
4	Data & User Security (Compartmentalization)			External vs Internal vs Contractual Users Confidentiality Requirements Regulatory Requirements	It is not uncommon for customers to compartmentalize the enterprise systems as a risk mitigation measure for issues that can potentially arise due to data confidentiality or a security breach.
5	Geographic Scaling & Expansion Costs			Global Applications Seamless Rollouts	Expansion to new geographies, markets, and product lines can be accomplished faster with an integrated platform.
6	Change Management & Platform Governance			Comprehensive Change Management Planning Platform Management and Governance Program Management Business Review with Stakeholders Enterprise Communication Plan Shared Services Management	Some investment is needed upfront while devising an enterprise strategy on a Shared platform. Also, ongoing collaboration is required between IT & Business leadership to ensure successful adoption of the platform.
7	Different Non-Functional Requirements			High Availability Business Continuity Data Retention SLAs - RPO, RTO	Not all enterprise applications are expected to fit in the same category of non-functional requirements. For example, certain mission critical applications may have strict uptime requirements while a simple survey application may not. Advanced infrastructure configuration comes at a higher cost and this may not be commensurate to justify investment for certain applications
8	Trend Reporting and Decisioning			End to End View of the System Tailored reporting to suit any business function - C Level / Middle Management	Reporting and thus decision making is significantly enhanced and expedited if the data aggregation is done across records residing on the Shared platform
9	Reuse and Collaboration			Develop common components & services Shared Appian Best Practices Center of Excellence	Well channelized team dynamics can lead to significant cost savings if common code can be reused across multiple applications on the platform. Teams working on the same platform environment tend to have better understanding and cohesion leading to better collaboration and thus better ROI.

Exception Scenarios

The table below lists out some of the exception scenarios when to consider a Segregated Appian installation.

#	Scenario	Key Factors
1	Customer has a mission critical application with very high transaction volumes and 24x7 site availability with virtually no tolerance for downtime. The application is so critical that it requires its own dedicated hardware and environment.	High daily business volumes High availability Very high resource utilization
2	Customer whose industry is heavily regulated and who is required to comply with rules, regulations, controls and strict processes related to their data/security/workflow	Data Security Standards & Policies Compliance & Regulation (Internal/External) Geographic Challenges
3	Applications deal with secured/sensitive data and unsecured/publicly available data. The risks of accidentally exposing data to the wrong users is a risk that must be mitigated and avoided at all cost.	Data & User Security Overall TCO
4	Applications have distinct and non-overlapping user sets, data sets, or processes, with little to no potential benefits accruing from aggregate analysis, process standardization, or economies of scale	Distinct and separate user communities No data requirements in common High degree of domain specialization Discreet and independent process flows

Tags: environments, Solutions Architecture, Platform

When to Consider Exceptions to an Appian Shared Environment

matt.cosenza — Tue, 31 Oct 2023 19:46:22 GMT

Revision 3 posted to Article by matt.cosenza on 10/31/2023 7:46:22 PM

Introduction

Real Time Visibility and Unified View
Overall Savings in Total Cost of Ownership (TCO)
Seamless, Consistent and Personalized User Experience
Significant Process Efficiency Improvements

Setups

In a Segregated Installation setup, each of the applications are hosted on their respective platform and a separate Appian url is provided to the users to login into the separate Appian interfaces.

In a Shared Platform setup, each of the enterprise applications is hosted on the single Appian instance, and users of all applications use a unique Appian url.

Comparative Analysis

The table below is a comparative analysis of the two installation approaches in light of some of the influencing factors:

#	Influencing Factor	Segregated Installation	Shared Platform	Decision Drivers	Details
1	Enterprise Agility(Definition)			Real-Time Visibility Low Information Cost Better Customer Experience	As customers continue to increase Appian adoption across the enterprise, a Shared platform helps build synergies across different enterprise functions, generating personalized insights and thereby faster response to outside situations.
2	Overall TCO			Operational and Maintenance Cost Infrastructure Maintenance Platform Upgrades & Hotfixing	Significant time & resource investment, along with redundant effort is required for performing server maintenance and management across multiple environments.
3	End User Productivity			Single Source of Truth Data Integrity Lesser Confusion Avoid Unnecessary Time Delays	For application spanning multiple Lines of Business, user productivity is significantly better if all information is available in a single Appian system.
4	Data & User Security (Compartmentalization)			External vs Internal vs Contractual Users Confidentiality Requirements Regulatory Requirements	It is not uncommon for customers to compartmentalize the enterprise systems as a risk mitigation measure for issues that can potentially arise due to data confidentiality or a security breach.
5	Geographic Scaling & Expansion Costs			Global Applications Seamless Rollouts	Expansion to new geographies, markets, and product lines can be accomplished faster with an integrated platform.
6	Change Management & Platform Governance			Comprehensive Change Management Planning Platform Management and Governance Program Management Business Review with Stakeholders Enterprise Communication Plan Shared Services Management	Some investment is needed upfront while devising an enterprise strategy on a Shared platform. Also, ongoing collaboration is required between IT & Business leadership to ensure successful adoption of the platform.
7	Different Non-Functional Requirements			High Availability Business Continuity Data Retention SLAs - RPO, RTO	Not all enterprise applications are expected to fit in the same category of non-functional requirements. For example, certain mission critical applications may have strict uptime requirements while a simple survey application may not. Advanced infrastructure configuration comes at a higher cost and this may not be commensurate to justify investment for certain applications
8	Trend Reporting and Decisioning			End to End View of the System Tailored reporting to suit any business function - C Level / Middle Management	Reporting and thus decision making is significantly enhanced and expedited if the data aggregation is done across records residing on the Shared platform
9	Reuse and Collaboration			Develop common components & services Shared Appian Best Practices Center of Excellence	Well channelized team dynamics can lead to significant cost savings if common code can be reused across multiple applications on the platform. Teams working on the same platform environment tend to have better understanding and cohesion leading to better collaboration and thus better ROI.

Exception Scenarios

The table below lists out some of the exception scenarios when to consider a Segregated Appian installation.

#	Scenario	Key Factors
1	Customer has a mission critical application with very high transaction volumes and 24x7 site availability with virtually no tolerance for downtime. The application is so critical that it requires its own dedicated hardware and environment.	High daily business volumes High availability Very high resource utilization
2	Customer whose industry is heavily regulated and who is required to comply with rules, regulations, controls and strict processes related to their data/security/workflow	Data Security Standards & Policies Compliance & Regulation (Internal/External) Geographic Challenges
3	Applications deal with secured/sensitive data and unsecured/publicly available data. The risks of accidentally exposing data to the wrong users is a risk that must be mitigated and avoided at all cost.	Data & User Security Overall TCO
4	Applications have distinct and non-overlapping user sets, data sets, or processes, with little to no potential benefits accruing from aggregate analysis, process standardization, or economies of scale	Distinct and separate user communities No data requirements in common High degree of domain specialization Discreet and independent process flows

Tags: environments, Solutions Architecture, Platform

When to Consider Exceptions to an Appian Shared Environment

matt.cosenza — Tue, 31 Oct 2023 19:46:14 GMT

Revision 2 posted to Article by matt.cosenza on 10/31/2023 7:46:14 PM

Introduction

Real Time Visibility and Unified View
Overall Savings in Total Cost of Ownership (TCO)
Seamless, Consistent and Personalized User Experience
Significant Process Efficiency Improvements

Setups

In a Segregated Installation setup, each of the applications are hosted on their respective platform and a separate Appian url is provided to the users to login into the separate Appian interfaces.

In a Shared Platform setup, each of the enterprise applications is hosted on the single Appian instance, and users of all applications use a unique Appian url.

Comparative Analysis

The table below is a comparative analysis of the two installation approaches in light of some of the influencing factors:

#	Influencing Factor	Segregated Installation	Shared Platform	Decision Drivers	Details
1	Enterprise Agility(Definition)			Real-Time Visibility Low Information Cost Better Customer Experience	As customers continue to increase Appian adoption across the enterprise, a Shared platform helps build synergies across different enterprise functions, generating personalized insights and thereby faster response to outside situations.
2	Overall TCO			Operational and Maintenance Cost Infrastructure Maintenance Platform Upgrades & Hotfixing	Significant time & resource investment, along with redundant effort is required for performing server maintenance and management across multiple environments.
3	End User Productivity			Single Source of Truth Data Integrity Lesser Confusion Avoid Unnecessary Time Delays	For application spanning multiple Lines of Business, user productivity is significantly better if all information is available in a single Appian system.
4	Data & User Security (Compartmentalization)			External vs Internal vs Contractual Users Confidentiality Requirements Regulatory Requirements	It is not uncommon for customers to compartmentalize the enterprise systems as a risk mitigation measure for issues that can potentially arise due to data confidentiality or a security breach.
5	Geographic Scaling & Expansion Costs			Global Applications Seamless Rollouts	Expansion to new geographies, markets, and product lines can be accomplished faster with an integrated platform.
6	Change Management & Platform Governance			Comprehensive Change Management Planning Platform Management and Governance Program Management Business Review with Stakeholders Enterprise Communication Plan Shared Services Management	Some investment is needed upfront while devising an enterprise strategy on a Shared platform. Also, ongoing collaboration is required between IT & Business leadership to ensure successful adoption of the platform.
7	Different Non-Functional Requirements			High Availability Business Continuity Data Retention SLAs - RPO, RTO	Not all enterprise applications are expected to fit in the same category of non-functional requirements. For example, certain mission critical applications may have strict uptime requirements while a simple survey application may not. Advanced infrastructure configuration comes at a higher cost and this may not be commensurate to justify investment for certain applications
8	Trend Reporting and Decisioning			End to End View of the System Tailored reporting to suit any business function - C Level / Middle Management	Reporting and thus decision making is significantly enhanced and expedited if the data aggregation is done across records residing on the Shared platform
9	Reuse and Collaboration			Develop common components & services Shared Appian Best Practices Center of Excellence	Well channelized team dynamics can lead to significant cost savings if common code can be reused across multiple applications on the platform. Teams working on the same platform environment tend to have better understanding and cohesion leading to better collaboration and thus better ROI.

Exception Scenarios

The table below lists out some of the exception scenarios when to consider a Segregated Appian installation.

#	Scenario	Key Factors
1	Customer has a mission critical application with very high transaction volumes and 24x7 site availability with virtually no tolerance for downtime. The application is so critical that it requires its own dedicated hardware and environment.	High daily business volumes High availability Very high resource utilization
2	Customer whose industry is heavily regulated and who is required to comply with rules, regulations, controls and strict processes related to their data/security/workflow	Data Security Standards & Policies Compliance & Regulation (Internal/External) Geographic Challenges
3	Applications deal with secured/sensitive data and unsecured/publicly available data. The risks of accidentally exposing data to the wrong users is a risk that must be mitigated and avoided at all cost.	Data & User Security Overall TCO
4	Applications have distinct and non-overlapping user sets, data sets, or processes, with little to no potential benefits accruing from aggregate analysis, process standardization, or economies of scale	Distinct and separate user communities No data requirements in common High degree of domain specialization Discreet and independent process flows

When to Consider Exceptions to an Appian Shared Environment

joel.larin — Wed, 06 Sep 2023 14:51:58 GMT

Revision 1 posted to Article by joel.larin on 9/6/2023 2:51:58 PM

fgjd