Speak to a rep about your business needs
See our product support options
General inquiries and locations
Contact usThis Service migrates Customer’s existing Remedy ITSM On-Premise platform to BMC Helix ITSM 22.1 and conducts performance testing of Advanced Configurations* and integrations to identify potential performance bottlenecks prior to production go-live.
BMC will perform the following:
Analyze and Design
Prepare for Migration
Migrate and Test
Prepare for Performance Testing
Conduct Performance Testing
Final Cut-over and Post-Production Assistance
Customer will be responsible for:
BMC will migrate your on premise Remedy ITSM based on one of the approaches below:
Delivery Options | Success Credits Required |
---|---|
Standard Delivery* | 160 |
Standard Delivery Country Specific Staffing* | 383 |
Comprehensive Standard Delivery | 204 |
Comprehensive Country Specific Staffing | 456 |
Solution Scope and Assumptions
Project Milestones: The following Milestones are established between the Customer and BMC. Once BMC has reached a milestone, the BMC project manager will issue a milestone completion letter to Customer.
Deliverables: Using BMC’s standard methodology and templates, the following Deliverables are in scope for this project and will be delivered:
Completion Criteria: BMC will have completed the Service when the in-scope Service have been completed and the Deliverables have been reviewed in accordance with the Terms of Use and delivered to the customer Project Manager.
Customer’s on premises BMC products:
Advanced Configuration: For features that do not exist out-of-the-box, an Advanced Configuration can accommodate 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:
Helix Prescriptive Test Cases: A set of BMC pre-defined test cases for ITSM, Digital Workplace, and Smart IT from which Customer will choose to be modified to test their 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 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, which may include BMC’s Global Services Delivery team in India and/or Mexico. The staffing choice from which country a BMC resource comes from will be solely at BMC’s discretion.
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.
Standard Testing Support Supports three weeks of customer testing and is intended for customers with a limited number of integrations and relatively less complex.
Comprehensive Testing Support: Supports an additional three weeks of customer testing over and above the standard three weeks of testing. This option is intended for customers with complex testing requirements OR exhaustive integrations / customizations.