Canary as Site Historian vs others (Ignition, OSI PI, AWS)

For a Site Historian requirement, I am exploring the historians available in the market and understanding where each Historian fits well. Can anyone throw light on the following questions?

1) Canary vs. Ignition
  Q: Under what circumstances would an Ignition customer choose Canary as the target historian or embed Canary's charts/applications into Ignition Designer? (I do see that Ignition has its Historian, asset modeling through partner modules, and two visualization systems)
    Q: Does Canary also directly compete with Ignition? If so, how?

2) Canary vs. OSI PI
  Q: Are there any significant advantages in choosing Canary over OSI PI? (OSI PI has 400+ interfaces, Historian, asset framework, and visualization)

3) Canary vs. AWS
  Q: With Greengrass, Timestream, and SiteWise, AWS offers robust connectivity, Historian, asset modeling, and visualization. With AWS Outposts, they can also be a Site Historian (apart from being a Cloud Historian). What are the use-cases where one would prefer Canary over AWS, and what are the unique advantages?

2replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Will wait for others in the community (partners & end users) to respond krish  and then provide some additional perspective

  • Sure, looking forward to hearing from the community. Thanks in advance.

Like Follow
  • 1 mth agoLast active
  • 2Replies
  • 54Views
  • 3 Following