Octane SaaS Licenses and Migration Solution

The Vendor is required to provide octane SaaS licenses and migration solution for include:
- Discovery and current state assessment
1. Assess the current ALM environment (quality center or octane) by utilizing complete questionnaires, including all relevant details
•    Identify the current version and patch level of the application lifecycle management (ALM) system.
•    Determine the hosting model.
•    Document the number of projects, workspaces, and domains in use.
•    Review the user base and associated access roles.
•    List all custom fields, workflows, and business rules configured.
•    Capture details of integrations, including CI/CD pipelines, defect tracking tools, and APIs.
2. Analyze the collected data to identify system configurations, dependencies, and potential migration challenges
•    Identify the total data volume in the current ALM environment.
•    Review all attachments stored within the system.
•    Determine historical data retention requirements.
•    Assess any regulatory considerations impacting migration.
3. Identify gaps between source and target platform capabilities.
4. Provide risk analysis and mitigation plan.
- Migration strategy and planning
•    Detailed migration strategy covering both lift-and-shift (where supported) and transformational migration (e.g., ALM quality center to quality center and cloud octane to value edge mapping changes). 
•    Defined plans for data mapping, project and workspace consolidation, archival, downtime windows, and rollback procedures. 
•    Comprehensive project plan with milestones, dependencies, and timelines to ensure successful execution.
- Target cloud environment configuration
•    Configure the project and workspace structure within the target environment to support organizational requirements and migration objectives 
•    Configure roles and permissions to ensure appropriate access control and alignment with organizational security requirements. 
•    Configure authentication settings to enable single sign-on (SSO) for secure and seamless user access. 
•    Configure email and notification settings to ensure timely communication and system alerts for all relevant users. 
•    The vendor must align all configurations with the state’s data privacy and security policy
- Customization and workflow alignment
•    Review and refactor workflow scripts for quality center scenarios. 
•    Review and refactor business rules and calculated fields for octane and value edge scenarios. 
•    Align process configurations between the source and target environments.” 
•    Document all configuration changes made during the migration process. 
•    Validate user workflows after migration to ensure functionality and compliance.
- Testing and user acceptance
•    Support the execution of user acceptance testing (UAT) activities. 
•    Track all migration-related defects and ensure timely remediation. 
•    Provide detailed issue logs along with resolution tracking for transparency and accountability.
- Cutover and hyper care
•    Execute the production migration to transition all in-scope artifacts to the target environment
•    Provide a minimum of two to four weeks of post-go-live hyper care support to ensure system stability. 
•    Adhere to service level agreements (SLAs) for issue response during the stabilization period. 
•    Deliver a comprehensive final project closure report summarizing activities, outcomes, and lessons learned.