We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Telecommunication Assets
Marcus_Ballance
Member IT Monkey ✭
I'm looking for a method to manage circuits and other telecommunication services, that would typically follow the same format as any other asset (associated with contract, associated with vendor, associated with departments/locations), but just aren't quite either hardware or software assets. Telephone numbers, circuits (physical and logical), as well as wireless delivered would all comprise this type of asset.
4
Comments
Yes, yes, yes, 100 times yes!
We use spreadsheets today to track the attributes of our circuits, capacity, Fiber vs Copper, etc. which means that we cannot connect circuits to Incident, or Vendor CI records, etc.
We use Business Services to be able to associate "circuits" to Incidents, Problems, etc today, but it would be soooo much better if we had real CIs for circuits.
Can't you use any existing attribute, like Note to maintain those attributes? If you'd use same format like capacity;fiber;etc. this workaround could replace Excel spreadsheets and have all information in 1 CI.
With respect, you can do that, but it doesn't accomplish the need to manage assets as assets. The circuit ID is not an attribute of a piece of hardware. It is a distinct asset provided by a vendor, with its own contract, its own SLA and its own metrics. If I replace a router, should I lose the history associated with upstream network problems?
In a previous work environment, we wrote our own MP to accomplish this, but it would be great to see it baked into a solution like Cireson.