Networking. The vendor must meet
the authentication and authorization
requirements of the network—for example, LDAP or AD, or single sign-on
Infrastrucutre security. The vendor
should understand and meet the enterprise’s security policies related to access management, perimeter security,
and data encryption.
Infrastructure sizing. The enterprise
should derive a concrete sizing plan including the number of environments
and compute and storage requirements based on its functional requirements, and evaluate the vendor closely
to ensure its software can scale and
meet those sizing needs.
High availability and disaster recovery.
The SRE team should have a clear understanding of reliability requirements
based on SLOs and customer objectives. Deciding on the high-availability
design such as active-active or active-passive, disaster-recovery requirements
and strategy,and data recovery (
recovery point objective) and restore (restore
point objective) are all critical when engaging the vendor. The enterprise must
ensure the vendor’s application can
meet its requirements, or that the vendor is willing to collaborate with the SRE
team to provide the needed reliability.
Data management. The vendor
should have a clear data management
discipline and methodologies when
it comes to data integrity, backup, recovery, and retention. Does the vendor
have a strong data security discipline
such as encryption of data both in transit and at rest?
Integrations. Make a list of all the
dependent systems and necessary integrations that the IT ecosystem requires—for example, authentication
services such as LDAP or AD; corporate
mail service and the necessary integrations; and service management workflows such as centralized backups,
monitoring, and logging.
Operability. Ensure the vendor has a
strong discipline of software updates/
upgrades, clearly defined maintenance
windows, and so on.
These requirements provide an overview of the core aspects and characteristics you should evaluate when choosing
an enterprise application. Note this is
not an exhaustive list, and requirements
may vary among enterprises.
Infrastructure evaluation. Infra-
structure requirements create the
foundation for the whole application.
Therefore, ensuring the end-to-end reliability of this base layer is critical.
Every enterprise is unique and has
its own set of infrastructure require-
ments and constraints. When evalu-
ating an enterprise application, you
want to ensure the vendor can comply
with the requirements of the enter-
prise’s IT ecosystem. For example,
suppose your enterprise has fully
adopted virtualization for internal
efficiencies and other business rea-
sons. In this case, the vendor’s ap-
plication should be compatible with
and supported on VMware. Other-
wise, the application could become
a nonstandard model in your IT orga-
nization, driving up costs related to
infrastructure, licensing, hardware,
Following are a set of key infrastructure requirements to ensure a vendor’s
software is compatible with an enterprise’s IT ecosystem.
Core infrastructure. The vendor must
meet an enterprise’s hardware, network, and operating system requirements. This includes specific hardware
models, enterprise databases, software
and operating systems versions that
the IT team supports.
Figure 2. Common platform.
Marketing Finance Legal Hr
Figure 3. Common platform layout.
Common Service Modules
e.g. Logging, Backups