# Kepware vs Ignition for tag organization

**URL:** <https://forum.inductiveautomation.com/t/kepware-vs-ignition-for-tag-organization/110198>\
**Category:** Ignition\
**Created:** [August 27, 2025, 4:23am UTC](https://forum.inductiveautomation.com/t/kepware-vs-ignition-for-tag-organization/110198 "2025-08-27T04:23:08Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\
**Post date:** [August 27, 2025, 4:45pm UTC](https://forum.inductiveautomation.com/t/kepware-vs-ignition-for-tag-organization/110198/11 "2025-08-27T16:45:38Z")

</div>

Interesting..you didn’t mention this a year ago when I laid out the organization.

> [@Project Default Tag Provider Limitations](https://forum.inductiveautomation.com/t/project-default-tag-provider-limitations/91861):
>
> 8.1.38 Vision Maybe I'm using the Tag Provider wrong, but it's breaking my historical trends and sparklines. I have a project that encompasses several PLCs. Each PLC is under a different developer, so for organization purposes, we have a tag provider for each OPC link to a PLC. Of course some HMIs will cover multiple PLCs and hence use multiple tag providers. Within the development of a project I often switch the project between the default tag provider for quicker drag/drop tag access into…

I agree about discipline, but please explain how it’s going to blow up on multiple site rollout. It’s been a time and organization saver on this particular rollout.

---

_[View the full topic](https://forum.inductiveautomation.com/t/kepware-vs-ignition-for-tag-organization/110198)._