I love the way erwin Data Modeler creates data models and presents them for our users. It's a great drawing tool and it represents the foreign key relationships, and you can easily drag those relationships to make the model easy to read. I think it's great. I've been using it a long time, and I think the way it presents the data in a visual format is great. It works fine, it's gotten better over the years, and it's really good now. I can tell you that we're using it to manage CVS's data, which has some PHI and PII data, personal health information and personal identifiable information, which relates to HIPAA, the Privacy Act for medical information. We have to go through all of our tables, every column, and flag where it has PII data or PHI data and a couple of other flags that we use internally. I use the UDP feature, the user-defined property, for these extra data elements. erwin Data Modeler has a way that you can add identifiers for each column, and I use that feature a lot to track things that are specific to us, and we're using it for data governance. That's using an existing erwin Data Modeler feature to do that. There may be some data governance features built into erwin Data Modeler or some other related tool that we're not using, and if so, then I don't know about that. But I can tell you that we are using it to support our data governance needs, at least in a limited way using the UDPs for columns.
