Migration Strategies: Port, Redesign, or Hybrid?

Part 3 of 5: Optix Migration Planning Series

Click here for Part 2

You've assessed your ME application. You understand architecture principles. Now the tactical question: How do you actually migrate screens from ME to Optix?

Most OEMs use a primary strategy (typically hybrid for established lines, redesign for new products) but apply it flexibly based on screen type, customer needs, and business context.

Note: This guide assumes you understand Optix template architecture (Types, Instances, Aliases, and Reusable Options). If not, read The Architecture Advantage: Why Optix Template Design Determines ROI first. Migration strategy and architecture design are inseparable.

Quick definitions:

• Port: For truly static content that doesn't vary (help screens, documentation, 5-10% of application)
• Hybrid: Familiar UI with proper template architecture underneath (main recommendation for established OEM lines)
• Redesign: Modern UX from scratch (new product lines, major modernization needs)

Important: These strategies aren't rigid "pick one for everything" rules. They're conceptual approaches that can be applied flexibly:

• Different strategies for different product lines (hybrid migration Machine A, redesign Machine B)
• Different strategies within one machine (port static screens, redesign overview, hybrid approach on equipment details)
• Evolution over time (port first machine, redesign next generation)

Strategy 1: Screen-by-Screen Port

Recreate your ME screens in Optix as closely as possible: same layout, same navigation, same graphics (where possible), same terminology. Philosophy: "If it ain't broke, don't fix it."

The screen looks familiar to operators but leverages Optix's template architecture underneath. This is not a 1:1 copy of ME screens. You're building proper Types, Instances, and Aliases that happen to have ME's visual layout. Every tank display is an instance of TankTemplate with different parameters, not 50 separate screens.

What It Means

Port is for truly static, informational content that doesn't vary across machines: help screens, about/version displays, safety documentation, reference information that's identical on every machine.

Key distinction: If a screen varies by machine, customer, or configuration, it should NOT be ported. It should use templates (hybrid or redesign approach).

Example of appropriate port: Safety guidelines screen, operator manual reference, company contact information.

NOT appropriate for port: Equipment screens, process displays, anything with machine-specific parameters.

When to Use Port

Use port ONLY for:

• Help/about screens
• Static documentation displays
• Safety/regulatory information
• Content identical across all machines
• Typically 5-10% of your application

Critical: Port is not a strategy for your entire application. It's for the small percentage of static content.

Speed:

• Fastest approach for static content
• No parameterization needed
• Simple copy process

Appropriate Use:

• Static content doesn't need templates
• Same screen on every machine
• No efficiency loss because there's no variation

Limited Applicability:

• Only works for truly static content
• Can't handle machine-specific variations
• Doesn't scale to variable content

Not a Primary Strategy:

• Won't work for equipment screens
• Won't work for process displays
• Should be minority of your application

Step 1: Identify truly static screens

• Is this screen identical on all machines? (If no, use hybrid)
• Does it vary by customer or configuration? (If yes, use hybrid)
• Is it informational only with no parameters? (If no, use hybrid)

Step 2: Recreate in Optix

• Match layout and content
• No need for aliases or parameters (truly static)
• Test once, deploy to all machines

Typical timeline: 1-2 hours per static screen (minimal complexity)

Remember: This is a narrow use case. Most of your application should use hybrid or redesign approach.

Strategy 2: Hybrid Approach

Build proper template architecture while preserving operator familiarity. Equipment screens look recognizable but are built as reusable templates with parameters. Strategic improvements where they matter most (dashboard, data entry, navigation).

The approach:

• Static screens (5-10%): Port directly (help, about, documentation)
• Variable screens (80%): Template-driven with familiar UI (equipment, process, alarms)
• Strategic improvements (10-15%): Modernized where valuable (dashboard, data entry)

Philosophy: "Familiar interface, modern architecture underneath."

Key principle: Tank01 and Tank02 aren't separate screens—they're instances of TankTemplate that happens to look familiar to operators.

Why Hybrid is the Sweet Spot for OEMs

Unlike a pure port (which misses template benefits) or pure redesign (which disrupts operator familiarity), hybrid balances efficiency and familiarity.

What makes hybrid work:

• Operators see recognizable layouts (reduced training)
• Engineers build proper templates underneath (efficiency gains)
• Strategic modernization where it matters (dashboard, data entry)
• Static content stays static (help screens)

Critical distinction: Hybrid means building templates that look familiar, NOT porting screens without templates. Every equipment screen is still a template with instances. It just preserves the visual layout operators know.

Example:

• Bad approach: Copy Tank01 screen, modify for Tank02 (not hybrid, just bad port)
• Hybrid approach: Build TankTemplate with familiar layout, Tank01/Tank02 are parameterized instances

When to Use Hybrid

You're an established OEM with:

• Trained customer base expecting familiar interface
• Existing training materials and documentation
• Service technicians who know the screens
• Multiple machine variants (template benefits are huge)

Your ME screens are:

• Generally well-designed (logical, functional)
• Familiar to operators (muscle memory established)
• Not fundamentally broken (navigation works, information findable)

You want:

• Lower customer training burden
• Faster deployment than full redesign
• Template architecture efficiency gains
• Strategic improvements where they matter

For OEMs: Hybrid is the recommended starting point for established product lines. You get template efficiency with operator familiarity.

Advantages and Disadvantages

Advantages:

• Lower upfront cost than full redesign
• Focuses improvement effort on complex screens
• Allows learning during migration

Disadvantages:

• Design inconsistency (mix of old and new)
• Two classes of screens (efficient vs. manual)
• Ported screens may need eventual rework
• Decision fatigue (port vs. redesign for each screen)
• May not realize full template architecture ROI

How to Execute Hybrid

If pursuing hybrid approach, understand that most screens get the hybrid treatment (familiar layout & template architecture). You're applying hybrid methodology to variable content rather than choosing a port or redesign strategy.

Step 1: Categorize screens by treatment type

Key insight: The "hybrid treatment" (80-85%) means screens look familiar but are built with proper templates. This isn't porting. It's building TankTemplate that happens to look like the ME tank screen.

Example of hybrid treatment:

• ME approach: Tank01 screen (hard-coded tags), Tank02 screen (copied and modified)
• Hybrid treatment: TankTemplate with familiar layout, Tank01/Tank02 are instances with aliases
• Result: Operators see familiar tank screen, you manage one template instead of 50 screens

Step 2: Design template architecture for ALL screens

• Even ported static screens may need basic structure
• Hybrid treatment screens require full template architecture
• Redesigned screens still need templates (modern UX + parameterization)
• Define aliases and parameterization strategy across all screen types

Step 3: Build strategically redesigned screens first

• Dashboard (modern UX, still template-driven)
• Data entry (touchscreen optimization)
• Navigation structure (leverage Optix capabilities)
• Establishes design language for modern elements

Step 4: Build hybrid treatment screens

• Equipment templates with familiar layouts
• Process screens with recognized patterns
• Maintain visual consistency with redesigned elements
• Update graphics to match modern style while keeping layout

Step 5: Port truly static content

• Help/about screens
• Documentation displays
• Minimal effort, no templates needed

Step 6: Validate consistency

• Do all screens feel cohesive (modern + familiar blend)?
• Is template architecture working across all types?
• Are operators comfortable with the mix?
• Test navigation flow across screen types

Strategy 3: Full Redesign

Rethink the entire interface from scratch using modern UX principles, improved navigation, better graphics, and streamlined workflows. Take full advantage of Optix capabilities. Philosophy: "Migration is an opportunity to improve."

This approach pairs best with proper template architecture. Design once for modern UX, then parameterize for all machine variants.

When to Use Full Redesign

Use full redesign when ME interface has known problems (operators complain about navigation, information is hard to find, workflows are clunky, graphics are dated), you need modern features anyway (web/mobile clients require responsive design, multi-language support, touchscreen optimization), major operational changes are happening (process improvements, new equipment, different operator roles), or you have time and budget (design takes longer upfront, testing more involved).

For OEMs: Use full redesign when adding web/mobile clients (requires responsive design), launching a new product line (no legacy expectations), competitive differentiation is critical (modern UX matters), or ME interface has significant UX problems (operators complain, workflows are broken). Established machine lines with trained customers typically benefit more from hybrid approach.

Advantages

Modern UX:

• User Experience optimized from the start
• Responsive layouts for different screen sizes
• Better information architecture
• Improved workflows based on actual usage

Leverage Optix Features:

• Web clients (responsive design)
• Multi-language (built-in support)
• Better navigation
• Modern graphics and animations

Long-term Value:

• Interface designed for next 10 years
• Not constrained by ME legacy decisions
• Competitive advantage for OEMs
• Easier to add future enhancements

Template Architecture:

• Design with reusability from day one
• Modern UX + proper architecture = maximum ROI
• Clean foundation for all future machines

Disadvantages

Time:

• Design phase adds time
• More testing required
• Operator training more extensive
• Multiple design iterations

Risk:

• Operators must learn new interface
• Change management required for customers
• Acceptance criteria less clear
• Higher customer training burden (OEM concern)

Cost:

• UX design expertise needed
• More development iterations
• Higher engineering budget
• Customer training materials need complete rewrite

How to Execute Full Redesign

This approach requires careful planning. See the Migration Execution Guide for detailed FAT/SAT procedures and operator training strategies.

Step 1: Functional requirements (not screen replication)

• What information do operators need?
• What actions must they perform?
• What workflows are most common?
• Interview operators and customers

Step 2: UX design phase

• Sketch navigation structure
• Design information hierarchy
• Create mockups
• Review with operators and key customers
• Define visual language and design system

Step 3: Design template architecture

• Map UX design to Types and Instances
• Define parameterization strategy
• Identify reusable components
• Plan for machine variants

Step 4: Develop in Optix

• Build templates based on UX design
• Leverage Optix capabilities
• Modern graphics and layouts
• Implement template architecture properly

Step 5: Extensive operator testing

• Usability testing with actual operators
• Workflow validation
• Training material development
• Customer pilot programs (for OEMs)

Typical timeline: 4-8 hours per screen + 40-80 hours design phase + architecture design time.

Decision Framework for OEMs

Your primary strategy guides most decisions, but you'll apply it flexibly. An established OEM line might use screen-by-screen port as the primary approach, but still redesign the dashboard and navigation. A new product line might use full redesign, but port alarm displays.

The key: Have a primary strategy, but don't be dogmatic.

Choose Based on Your Situation

For Established Machine Lines

Recommendation: Hybrid approach as primary strategy

What this means:

• Build proper template architecture (Types, Instances, Aliases)
• Preserve familiar visual layouts for equipment screens
• Port truly static content (help screens, about pages)
• Strategically modernize high-value screens (dashboard, data entry)

Why hybrid works:

• Customers expect familiar interface
• Training burden minimized across installations
• Service technicians already know the layouts
• Template architecture delivers efficiency gains
• Existing documentation remains largely relevant

Implementation:

• Equipment screens: Template-driven with familiar layouts
• Dashboard: Modernized (first impression matters)
• Navigation: Improved (Optix is better here)
• Alarms: Template-driven, familiar format
• Help/static: Port as-is

Critical: Port the interface appearance, not the architecture. Build proper templates that happen to look like ME screens.

For New Product Lines

Recommendation: Full redesign with template architecture from day one

Why redesign works:

• No legacy interface expectations
• Opportunity to differentiate from competition
• Modern UX establishes new standard
• Clean foundation for product evolution
• Training materials built fresh anyway

Still include:

• Proper template architecture (non-negotiable)
• Some familiar patterns (alarm format familiar to service techs)

Result: Modern interface throughout, competitive advantage, strong foundation for future.

For Product Line Refresh

Recommendation: Depends on scope of refresh

Full redesign if:

• Rebranding the product line
• Adding web/mobile clients (requires responsive design)
• Major new features that change workflows
• Competitive pressure requires differentiation
• Customer expectations shifting with refresh

Hybrid if:

• Incremental improvements
• Maintaining brand consistency
• Customers expect familiar operation
• Timeline doesn't allow full redesign

Consider: Product refresh is your best opportunity for redesign. Customer expectation is "things will be different." Take advantage of it.

Migration Strategy by Screen Type

Note: These recommendations apply regardless of your overall strategy. Even when doing hybrid (main OEM recommendation), treatment varies by screen type. Think of these as guidance per screen type, not absolute rules.

Choose based on:

• Screen importance: Dashboard = first impression
• Operator interaction: Equipment = muscle memory
• Variation across machines: High variation = templates critical
• UX improvement opportunity: Data entry = worth modernizing

Overview/Dashboard Screens

Recommendation: Redesign (even within hybrid strategy)

Why: First screen operators see sets tone. This is your product's "face." Invest in modern graphics and clean information hierarchy.

Implementation:

• Modern Optix SVG graphics (scalable, crisp)
• Responsive layout (works on different panel sizes)
• Clear visual hierarchy
• Still template-driven if parameters vary by machine

For OEMs: This is worth modernizing even in hybrid approach. First impression matters.

Equipment Detail Screens

Recommendation: Hybrid (template-driven with familiar UI)

Why: Operators have muscle memory for these screens. Preserve familiar layout while building proper templates.

Implementation:

• Maintain recognizable visual layout
• Build as templates (MotorTemplate, TankTemplate, ValveTemplate)
• Instances with parameters (Motor01, Motor02 using aliases)
• Update graphics to modern style while keeping layout

Critical for OEMs: This is where template ROI happens. Don't just copy ME screens—build reusable equipment templates that look familiar.

Example:

• ME: Motor01 screen (hard-coded), Motor02 screen (copied and modified)
• Hybrid: MotorTemplate with familiar layout, Motor01/Motor02 are parameterized instances

Alarm Screens

Recommendation: Hybrid with Optix library widgets

Why: Operators trained on alarm response. Familiar format reduces errors. But leverage Optix's better capabilities.

Implementation:

• Use Optix alarm widgets (better filtering, better performance)
• Maintain familiar alarm format and layout
• Template-driven if alarm configuration varies by machine
• Improved acknowledgment workflow (Optix advantage)

Balance: Familiar format + Optix improvements.

Navigation Structure

Recommendation: Redesign

Why: Optix navigation is fundamentally better than ME. Already requires work to function in new environment. Extra effort to optimize pays off.

Implementation:

• Leverage breadcrumbs (Optix feature)
• Implement favorites/shortcuts
• Better popup/modal handling
• Search functionality (if applicable)

Result: Improved workflow even in hybrid approach.

Static/Help Screens

Recommendation: Port

Why: Identical on all machines. No parameters. No templates needed.

Implementation:

• Copy content and layout directly
• No aliases or parameterization needed
• Same on every machine
• Minimal testing required

Scope: Typically 5-10% of total application (help, about, safety documentation).

Common Migration Mistakes

Mistake 1: Pixel-Perfect Replication

Problem: Trying to match ME exactly in Optix, pixel by pixel.

Why it fails: Different platforms, different capabilities. You're fighting Optix's strengths.

Fix: Port layouts and workflows, not exact pixels. Use Optix's design patterns.

Mistake 2: Confusing Port with Hybrid

Problem: Treating hybrid as "port some, redesign others" instead of "templates with familiar UI."

Why it fails:

• Equipment screens get copied individually (no templates)
• "Port" interpreted as static bindings
• Miss all template efficiency gains

Fix: Understand that hybrid means:

• Build templates (TankTemplate, MotorTemplate)
• Preserve familiar layouts (operators recognize them)
• Every machine uses instances, not copies
• Port is ONLY for truly static content (help screens)

Example of doing it right:

• Tank01, Tank02, Tank03 all use TankTemplate
• Layout looks familiar to operators
• Parameters handled via aliases
• Change TankTemplate and all tanks update

Mistake 3: Redesigning Everything

Problem: "Let's modernize while we're at it!" applied to every screen.

Why it fails: Timeline explodes, scope creep, customer training burden skyrockets.

Fix: Be strategic. Full redesign is better than hybrid, but only when it makes business sense.

Mistake 4: No Customer/Operator Input

Problem: Engineers decide port vs. redesign without customer feedback.

Why it fails: Customers have strong preferences. Operators have valuable insights.

Fix: Interview customers and operators during assessment. Get feedback on proposed approach.

Mistake 5: Hybrid Without Architecture Planning

Problem: "We'll port simple screens and redesign complex ones" without thinking through template implications.

Why it fails: Ported screens don't leverage templates. Efficiency gains limited. Technical debt accumulates.

Fix: If going hybrid, ensure ALL screens use template architecture, even ported ones.

Testing Your Strategy

Pilot Project Approach

Before committing to full migration, test your strategy on representative screens.

Build 3-5 screens:

1. One overview screen (apply chosen strategy)
2. Two equipment screens (using template architecture)
3. One data entry screen (test PLC bindings)
4. One alarm/trend (validate standard approach)

Validate:

• Execution time (accurate estimates)
• Operator feedback (acceptable UX)
• Template architecture (works as designed)
• Visual consistency (cohesive feel)

Adjust your strategy based on learnings before migrating remaining screens.

For detailed testing protocols, see the Migration Execution Guide.

Hypotheticals

In practice, most successful migrations use a primary strategy applied flexibly:

Example 1: Established OEM Line

Primary strategy: Hybrid approach

Implementation:

• Equipment screens (70%): Template-driven with familiar layouts (MotorTemplate, TankTemplate, ValveTemplate)
• Dashboard (1 screen): Redesigned with modern graphics (first impression matters)
• Navigation: Redesigned (Optix is fundamentally better)
• Alarms (5%): Template-driven, familiar format
• Static screens (5%): Ported as-is (help, about, safety docs)

Result: Operators see mostly familiar interface with strategic improvements. Template architecture delivers 50-70% efficiency gains on subsequent machines.

Customer experience: "It's our machine, but nicer"

Example 2: New Product Line

Primary strategy: Full redesign

Implementation:

• All screens: Modern UX from start (touchscreen-optimized, responsive)
• Equipment screens: Still template-driven (proper architecture)
• Navigation: Fully redesigned (leverage all Optix capabilities)
• Alarm format: Modern but borrows established patterns (familiar to service techs who support multiple product lines)

Result: Modern interface throughout, competitive differentiation, strong foundation for product evolution.

Customer experience: "This is clearly next-generation"

Note: Even with full redesign, template architecture is still essential. Modern UX + templates = maximum value.

Conclusion

No single strategy is universally "correct." Match your approach to your situation.

For most OEMs: Hybrid approach with proper template architecture is the pragmatic choice. Build templates that preserve familiar equipment screen layouts while strategically modernizing high-value areas (dashboard, data entry, navigation). Port only truly static content (help screens, documentation).

For new product lines: Full redesign creates modern UX foundation and builds template architecture from day one.

Pure port (static bindings): Avoid. Use only for truly static content that doesn't vary across machines. Represents 5-10% of typical application.

Hybrid approach: The 'hybrid' approach (as a formal strategy) should be used for truly static informational screens that don't benefit from templates. However, flexibility within your primary strategy (port most screens but redesign dashboard, for example) is normal and smart. This isn't 'hybrid'—it's strategic application of your primary approach.

Key principle: Migration strategy and architecture design are inseparable. A port without templates is wasted effort. A redesign without architecture is just a pretty ME.

Test your chosen strategy on pilot screens before committing to full migration.

Next in Series: Part 4 - Development Best Practices for Optix

Need Migration Strategy Help?

ASQI can review your ME application and recommend the right migration strategy for your OEM situation.

Services:

• Migration strategy assessment
• Template architecture design
• Pilot project consulting
• Operator/customer feedback facilitation

Contact ASQI →

Related Articles

Assessment Phase: Know What You Have — Start here — inventory your current application before choosing a strategy.

The Architecture Advantage — Why proper template design determines ROI across all migration strategies.

Testing & Go-Live — After migration, validate everything works before cutover.