Optix Migration Readiness Assessment

Before migrating to FactoryTalk Optix, you need to know what you have. This comprehensive checklist covers current system assessment, hardware evaluation, team readiness, and architecture planning. Document your ME application systematically to identify gaps and ensure a successful migration.

Current System Assessment

Application Inventory

Document your existing FactoryTalk View ME applications to establish a baseline for migration planning.

Item Notes
Total number of ME applications Count:
ME version documented (e.g., v13.00) Version:
All .MER files backed up Location:
Application runtime tested and validated Last test date:

Screen Analysis

Catalog all screens in your ME application and categorize them by complexity to estimate migration effort.

Item Notes
Total screen count documented Count:
Screens categorized by complexity Simple:____ Medium:____ Complex:____
Popup/overlay screens identified Count:

Complexity Rating Guide:

  • Simple: Display-only, minimal animations, standard objects
  • Medium: Data entry, navigation, basic animations, trend charts
  • Complex: Custom VBA scripts, complex animations, heavily customized objects and many global objects

Component Inventory

Identify all components used in your ME application, paying special attention to VBA scripts and global objects.

Item Notes
VBA scripts documented Script count:
Global objects cataloged Count:
Trend displays counted Count:

Migration Considerations:

  • VBA scripts will need refactoring into Optix Studio or conversion to C#. Assess if functionality is still needed
  • Global Objects should be refactored into Templates during your Optix conversion. Think of Templates like Global Objects with a foundation that can be slightly modified for individual use cases within your application.
  • Complex animations can be recreated using Optix's built-in features

Tag Database

Document your complete tag database structure and naming conventions for proper migration planning.

Item Notes
Total tag count
Tag database exported File:
Naming convention documented Convention:

Alarm Configuration

Review your current alarm setup to plan the transition to Optix's alarm system.

Item Notes
Alarm setup documented Y/N
Alarm priorities defined Priority levels:
Alarm History Screen Y/N
Alarm banner usage Y/N
Alarm suppression rules Rules documented:

Hardware & Network Evaluation

Hardware

For discrete deployments, Optix panels are your best bet. More complex deployments could benefit from IPCs.

Item Notes
Screen sizes needed:
IPC deployment? Y/N
Remote Access? Method:

Industrial PC Requirements

If deploying Optix on industrial PCs, document the hardware specifications needed.

Item Notes
PC specifications determined CPU/RAM/Storage:
Windows (or Linux) version selected Version:
Monitor resolution chosen Resolution:
Touch screen requirements Touch: Y/N

PLC Communication

Document your PLC communication setup to ensure seamless integration with Optix.

Item Notes
PLC model(s) documented Models:
Communication protocol Protocol:
PLC program version Version:

Migration Scope Definition

Screen Migration Strategy

Choose your migration approach based on your needs: direct port, full redesign, or hybrid.

Migration Approach Decision:

  • Screen-by-screen port: Faster, less improvement, maintains familiar UX
  • Full redesign: Slower, modernized UX, better long-term maintainability and efficiency gains
  • Hybrid: Port simple screens, redesign complex ones (Balanced approach)
Item Notes
Migration approach selected Screen-by-screen / Full redesign / Hybrid
Screens for direct port identified Count:
Screens for redesign identified Count:
New functionality planned Features:

Feature Requirements

Identify advanced features and integrations needed in your Optix application.

Item Notes
Web/mobile client needed Y/N
Multi-language support Languages:
External Database integration required Y/N
MES/ERP connectivity System:
Recipe management needed Recipe system:
Advanced reporting Report types:
Custom scripting required Use cases:

Custom Logic Development

Estimate the effort needed to convert VBA scripts and complex UI interactions to Optix.

Note: Many OEM applications can be accomplished through template configuration without custom scripting. Optix's built-in features (dynamic links, converters, built-in methods) handle most common scenarios.

Item Notes
Custom logic requirements identified Y/N
Complex UI interactions documented Y/N

Team Readiness & Training

Personnel Assessment

Identify your development team and ensure they have the necessary resources and licenses.

Item Notes
Development team identified: Y/N
Optix Studio Pro licenses obtained (for version control) Y/N
Development PLCs configured: Y/N
Roles and responsibilities assigned Y/N

Skills Assessment

Evaluate your team's current skill levels to plan appropriate training.

Item Notes
FactoryTalk View ME experience Experience level:
Object-oriented design familiarity Experience level:
Version control understanding Experience level:

Experience Levels: None / Basic / Intermediate / Advanced

Note: Optix Studio's built-in version control simplifies collaboration. Optix Studio handles commits, pulls, pushes, and history through intuitive buttons.

Training Plan

Schedule comprehensive training to ensure your team masters Optix's architecture and capabilities.

Recommended Training:

  • Rockwell Automation: "FactoryTalk Optix Fundamentals" course
  • Custom training: Contact ASQI for hands-on, project-specific training
  • Architecture Resource: See blog post here
  • Version Control Resource: ASQI's "Using Optix Studio Version Control" guide (coming soon)
Item Notes
Optix Studio fundamentals training Y/N
Template & Type creation training Y/N
Architecture principles training Y/N
Advanced Optix topics training Y/N
On-the-job mentorship planned Y/N

Development Environment Setup

Software Installation

Install and configure Optix Studio on all development workstations.

Item Notes
Optix Studio installed Version:
Visual Studio (for scripting) Version:

Version Control Setup

Configure version control in Optix Studio to enable collaboration and change tracking.

Optix Studio Version Control:

  • Built-in version control through intuitive UI
  • Commit, Pull, Push, History buttons (no command line needed)
  • Integrated with GitHub/GitLab through Studio interface
  • Reference: ASQI will publish "Using Optix Studio Version Control" guide
Item Notes
Team setup with GitHub or other VC Y/N
Repository created in Optix Studio Y/N
Backup strategy documented Y/N

Development Best Practices

Establish standards and processes for consistent, maintainable Optix development.

Item Notes
Naming conventions established Y/N
Folder structure standardized Y/N
Testing procedures and documentation planned Y/N

Integration Points

Data Connectivity

Plan connections to historians, databases, and communication protocols.

Item Notes
External Historian integration Y/N
External DB connections Y/N
Other connections (MQTT, REST, etc.) Y/N

Enterprise Systems

Document integrations with MES, ERP, CMMS, and authentication systems.

Item Notes
MES connectivity MES system:
ERP integration ERP system:
Authentication (LDAP/AD) Auth method:

Architecture & Template Strategy

Understanding the Reusable Option Methodology

Optix's template system allows configuration options to live at the template level. If a machine doesn't have an option enabled, it simply isn't used. When that option is needed again, it works without additional HMI or PLC programming.

See this article for a detailed analysis on design and architecture.

Architecture Assessment & Time Savings

Master Optix's type system, template inheritance, and configuration-driven approach for maximum ROI.

Key Insight: Most machines have 1-2 options not currently in the template. In legacy ME workflows, combining these options creates conflicts and requires significant integration work. With proper Optix architecture, once an option is built into the template (even if it's 10% more effort to abstract it), it's plug-and-play forever.

Item Notes
Types vs Instances concept understood Y/N
Template inheritance mastered Y/N
Alias usage for parameterization Y/N
Machine configuration options cataloged Y/N:
Which options can be template-driven? Percentage: %
Current time per machine Hours:
Estimated time for first Optix machine Hours: (expect +100%)
Estimated time for subsequent machines Hours: (configuration only)
Break-even point calculated Machine count:

Are You Ready?

If you've worked through these sections and documented most items, you're ready to begin planning your migration execution. The areas where you have gaps should guide your next steps:

Critical items before proceeding:

  • Architecture training completed (Section 7)
  • Template strategy defined (Section 7)
  • Development environment set up (Section 5)
  • Team identified and licensed (Section 4)

Use the Migration Execution Guide to plan timelines, manage risks, and coordinate the actual migration work.

Get Expert Help

Need assistance with your readiness assessment or migration planning?

ASQI LLC specializes in FactoryTalk Optix migrations, offering:

  • Migration readiness assessments
  • Architecture design and template strategy consultation
  • Hands-on development and implementation
  • On-site commissioning support
  • Ongoing training and knowledge transfer

Contact ASQI →


This assessment may be distributed freely for non-commercial use. Attribution to ASQI LLC is appreciated.


Assessment Phase: Know What You Have — Deep dive into the discovery process this checklist builds on.

When to Migrate to Optix (And When to Wait) — Not sure if now is the right time? This guide helps you decide.

Migration Execution Guide — Ready to go? Use this project-planning checklist for execution.