Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

1. The Problem

A mail order pharmacy operations relied on legacy SCADA applications for KPI reporting. These applications failed modern security audits (including Veracode) and lacked flexibility for real-time downtime, OEE, and event monitoring. The fragmented system created compliance risks, delayed KPI visibility, and limited scalability for enterprise-wide deployment.

2. The Solution:

FrameworX was implemented to modernize KPI reporting and provide a secure, scalable enterprise platform. A key enabler was the FrameworX Edge project acting as a Calculation Engine, which processes raw PLC data in real time before passing it into GE Historian. This enabled advanced downtime and OEE calculations at the edge, reducing historian load and improving overall system responsiveness. The solution included secure local data collection, Windows Server infrastructure, and integrated dashboards for downtime, OEE, and event monitoring.

Simple Architecture Diagram:

Rockwell PLCs → FrameworX Edge Project (Calc Engine) → FrameworX Local Engine → GE Historian 6.0

FrameworX Portal & Monitor Services

CVS SQL Server

Technical Specifications:

  • PLCs: Rockwell Automation (including custom controllers)

...

  • Integration: FrameworX Edge → GE Historian → SQL MES Event Monitor

3. Key Enablers:

  • Edge Project as Calculation Engine: Real-time KPI and downtime/OEE calculations at the edge, minimizing historian overhea

...

  • Integrated Dashboards: FrameworX Portal & Monitor providing real-time MES event monitoring with SQL integration

4. The Results:

  • Delivered real-time KPI visibility for downtime, OEE, and security metrics critical to pharmacy operations

...