Which product is this for?
After a conversation, we identified that every CI/Asset has the ability to link/attach documentation. We will investigate how well it meets all our needs; and if the user flow is appropriate. It is definitely a baseline start.
That leaves only vendor information, which we would prefer to be in the Vendor accounts, but might either require adjustment of our thinking, creation of another subclass, etc. The idea of a relationship to the vendor, be it a product or a service (like a fire department), however, makes sense. suggestions are welcome. We'd like all CI-related vendors to come from the same table where it is best that all vendors are kept. At this time that appears to be Vendor Accounts.
We still need to add the following for each attached/linked document:
- A field labeling the document. We would prefer this to be a drop down do that a consistent set of labels can be used. A system admin can update the drop down list
- A text field for optional notes, and required if the label (see above) is "Other". This allows for periodic label choice reviews and updates.
We also need the ability to link a CI to a Vendor Account record. Can this be done through a Relationship?
Like Documentation, we would like a labeling drop down available, and a notes field, required if the label is Other.
A couple use cases
- We want to identify the outside party who provides the support for a specific CI
- We have a series of local contacts for a [Physical] Location CI, like:
- Fire Department
- Local Hospital
- Facility Insurer
- Media outlet