Advanced Configuration: For features that do not exist out-of-the-box, an Advanced Configuration can accommodate on forms, active links, filters, escalations, integrations, menus, reports, or dashboards.
Application Data: Application data is optional data that can be loaded into the system. Examples of this include assignment routing, incident templates, and change approval mappings.
Country-Specific Staffing: Upon Customer’s request and BMC resource availability, BMC will deviate from BMC’s Standard Delivery model. BMC will work with Customer to understand and address their country-specific staffing requirements. The staffing choice from which country a BMC resource comes from will be mutually agreed to by BMC and Customer.
Foundation Data: Foundation data is data required for the application to function properly and is defined as:
- Companies
- Organizations
- Sites and Location Structures
- Support Organizations and Groups
- People (includes group memberships, application permissions, and functional roles)
- Operational Services Catalog
- Software Catalog
Helix Prescriptive Test Cases: A set of BMC pre-defined test cases for ITSM, BMC Digital Workplace, and Smart IT from which Customer will choose to be modified to test their BMC Helix Pre-production environment to reflect changes due to Advanced Configurations.
Integration Testing: Integration testing is a procedure to validate that the BMC integration components are functioning properly.
Non-standard Configurations: Non-standard Configurations are those configurations that do not follow the requirements as defined under the definition of Standard Configurations.
Non-standard Integrations: Non-standard Integrations are those integrations that do not follow the requirements as defined under the definition of Standard Integrations.
Standard Configurations: For purposes of this migration offering, BMC’s definition of “Standard Configurations” are those configurations, advanced configurations, and customizations that follow BMC Helix Operations recommended best practices which are:
- Customizations may not involve the installation of a third-party application in the cloud
- Customizations are not using any Run process commands to execute non-BMC created executable, batch, or Java ARchive (JAR) files
- No direct write connection to the database is allowed. Read-only access is permitted via an ODBC or JDBC connection only
- No direct SQL statements are allowed in the workflow
Customizations should not involve any changes to the standard BMC Helix service image or infrastructure configuration, for example, a different Java Runtime Environment (JRE) or Java Development Kit (JDK) version other than BMC's standard version is not allowed.
Standard Delivery: A mix of BMC consultants and project managers sourced from various BMC locations.
Standard Integrations: BMC provides a flexible model for data integrations to and from its BMC Helix services. Integrations may be configured using any approved communication method or adapter. The following is the list of approved integration methods: C API, Java API, AR System plug-ins, Open Database Connectivity (ODBC) access, BMC Atrium Integrator (AI) adapter, Managed File Transfer (MFT), Security Assertion Markup Language (SAML), Simple Mail Transfer Protocol (SMTP), and Computer Telephony Integration (CTI).
System Testing: System testing is a procedure to validate that the BMC components are working as a complete solution as designed.
Unit Testing: Unit testing is a procedure to validate that the individual units of each application are functioning properly.
