Empty unit space

[DCIM_Support]

This question was originally posted on DCIM Support by Andrius Gataveckas on 2019-05-07

---

Is it possible to allocate an empty unit space to a customer? If not, are there any plans to introduce a unit level management functionality?

(CID:143755952)

[DCIM_Support · Accepted solution]

This answer was originally posted on DCIM Support by Jef Faridi on 2019-05-07

---

Hi Andrius,

With DCO Colo it is possible to create an empty cage and allocate it to a customer.

Kind regards

(CID:143755975)

[DCIM_Support]

This comment was originally posted on DCIM Support by Andrius Gataveckas on 2019-05-07

---

What if I have a rack that has 21 out of 42 units assigned for one customer, but the rest of 21 units are sold to another customer, who has not got anything installed. Is there a way to mark those units as allocated for that customer but not actually occupied?

(CID:143755988)

[DCIM_Support]

This comment was originally posted on DCIM Support by Ed Tarento on 2019-05-07

---

Hi Andrius

Do you have DCO Change?  You can reserve this and sync into your change management process.  Another simple solution is to create a 1U Genomes entry (I've used blanking panel as a template) and place the units in the U position for the client.  If you have DCO Capacity, you can tag the items, otherwise you can create a custom property or just name the items

Cheers

Ed

(CID:143756054)

[DCIM_Support]

This comment was originally posted on DCIM Support by Andrius Gataveckas on 2019-05-08

---

Hi Ed, no, we are not using DCO Change. If we create 1U genomes entries with blanking panels, will it then show that those units are occupied within the free space report? Thank you.

(CID:143756169)

[DCIM_Support]

This comment was originally posted on DCIM Support by Ed Tarento on 2019-05-08

---

Good point.  They will appear as occupied in the free space report. 

Another way of looking at it ...... Are these "reserved" U positions really "free"?  Can they be sold to another customer?    Perhaps "free" could mean empty and not reserved?  

Ed

(CID:143756191)

[DCIM_Support]

This comment was originally posted on DCIM Support by Andrius Gataveckas on 2019-05-08

---

Yes, "free" should mean empty. They cannot be sold to another customer.

(CID:143756217)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2019-05-08

---

Hi Andrius,

In DCO, in general access rights/permission can be location, room, cage and/rack based. 

In your scenario, where one rack may be assigned to two different customers, then I can think of the following work-around:

a) if the DCO is not intended to be used/accessed by customers, then those free/"empty"/reserved U positions could be field (occupied) by non-powered devices, such as patch-panels. In this way assets(patch-panels) Tags and/or properties settings could be used to mark it for a certain customer... and would also appear in the reports.

b) if the DCO is intended to be used/access by customers, then "dividing" the 42 U rack to two smaller racks, eg. using two 21 U racks instead, could be considered. Downside: increase in used license, and also racks cannot be mounted on top of each other.

Kind regards

(CID:143756296)

[DCIM_Support]

This comment was originally posted on DCIM Support by Andrius Gataveckas on 2019-05-08

---

Hi Jef,

Thank you for your input, appreciate the answers. I guess we will have to select one of two workarounds, even though neither of them really suits the business requirement.

By any chance, do you happen to know if there are plans for future software releases to allow management on the unit level? Maybe it is possible to request it as a feature?

(CID:143756302)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2019-05-08

---

Hi Andrius,

As far as I know U based access level never been discussed, but I will take your feed back to our management team, thanks.

Kind regards

(CID:143756309)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.