In Part 1, I described how I would establish the business rationale for an Enterprise Historian migration by grounding the discussion in operational pain points, stakeholder input, and strategic objectives.
In Part 2, I focus on the next critical step: determining whether a migration is actually feasible—from a financial, organizational, and execution standpoint. A compelling vision without a credible cost and delivery model will never make it past executive review.
1. How I Approach Feasibility as a Director
Before recommending a migration, I need to answer three fundamental questions:
- Can we afford it?
- Do we have the right people and capabilities to execute it?
- Does the long-term value justify the disruption and investment?
To answer these questions, I work closely with finance, IT, operations, and analytics leadership to build a realistic and defensible model—one that reflects both direct costs and organizational impact.
2. Building the Financial Model: TCO, CapEx, and OpEx
My first step is to establish a clear baseline of what our current Historian truly costs the organization today. This is often underestimated.
A. Current-State Total Cost of Ownership (TCO)
I collaborate with IT, procurement, and finance to capture all relevant cost components, including:
- Software licensing and maintenance
- Hardware refresh cycles and depreciation
- Infrastructure hosting (data center or cloud IaaS)
- Vendor support contracts
- Internal labor required to operate and maintain the platform
This creates a credible “As-Is” TCO that becomes the anchor for all comparisons.
B. Future-State Cost Model (CapEx and OpEx)
Next, I model the “To-Be” state, accounting for:
- Platform subscription or consumption-based costs
- Storage and compute growth projections
- Network and data egress considerations
- Security, monitoring, and compliance tooling
Depending on the target architecture, CapEx may decrease significantly while OpEx becomes more variable and usage-driven. I work with finance to ensure this shift aligns with budgeting and forecasting expectations.
The goal isn’t just to show cost reduction—it’s to show cost flexibility and transparency.
C. One-Time Migration Costs
I explicitly separate one-time investment costs from steady-state operating expenses, including:
- Data migration and historical backfill
- Parallel run periods
- Tooling and automation development
- Validation, testing, and cutover activities
This avoids the common mistake of burying migration costs inside OpEx assumptions.
3. Human Capital: The Most Underestimated Cost
Technology migrations rarely fail because of technology. They fail because of people and capacity constraints.
As a Director, I assess human capital impact early and honestly.
A. Internal Team Capacity and Skills
I work with engineering, operations, and IT leadership to evaluate:
- Do we have internal expertise in modern time-series platforms and cloud architectures?
- How much capacity can internal teams realistically allocate without impacting operations?
- What skills gaps exist today, and how long would it take to close them?
This assessment informs whether we rely primarily on internal teams, external partners, or a hybrid model.
B. Training and Change Management
A modern Historian platform changes how teams work. I account for:
- Training time for engineers, analysts, and support staff
- Updates to operational procedures and incident response
- Shifts in ownership between OT and IT teams
These costs are real—even if they don’t appear neatly in a spreadsheet.
4. Professional Services: Strategic Use, Not Dependency
I view professional services as an accelerator, not a crutch.
I typically evaluate:
- Which activities are best handled by external specialists (e.g., migration tooling, architecture design, security reviews)
- Which capabilities must be internalized to ensure long-term sustainability
This approach reduces execution risk while preventing long-term vendor dependency.
5. Bringing It Together: The Business Case Framework
Once financial and organizational inputs are collected, I consolidate everything into an executive-ready view:
| Category | Considerations |
|---|---|
| As-Is TCO | Current steady-state cost and risk |
| To-Be OpEx | Future operating model and flexibility |
| One-Time Investment | Migration, tooling, and services |
| Human Capital | Internal effort, training, change impact |
| Strategic Value | Analytics enablement, resilience, scalability |
This framework allows leadership to evaluate the migration holistically—not just as an IT project, but as a business transformation.
6. How This Informs the Go / No-Go Decision
At this point, I can answer the questions executives care about most:
- Does the migration reduce long-term cost and risk?
- Does it unlock capabilities we can’t achieve today?
- Is the investment proportional to the value delivered?
- Can we execute without destabilizing operations?
If the answers are yes, I move forward with confidence. If not, I recalibrate scope, timing, or approach.
Sami Joueidi holds a Master’s degree in Electrical Engineering and brings over 15 years of experience leading AI-driven transformations across startups and enterprises. A seasoned technology leader, Sami has led customer adoption programs, cross-functional engineering teams, and go-to-market strategies that deliver real business impact.
He’s passionate about turning complex ideas into practical solutions, and about helping teams bridge the gap between innovation and execution. Whether architecting scalable systems or demystifying AI concepts, Sami brings a blend of strategic thinking and hands-on problem-solving to every challenge.
© Sami Joueidi and www.cafesami.com, 2025.
Feel free to share excerpts with proper credit and a link back to the original post.
