I would like to see a couple of features for Station services implemented, with an eye towards making a potential shutdown easier on the Consumer of these services.
- An ability for a station manager to see who has jobs running/clones installed on Indy services and clone bays, and how much time is left on the Indy jobs.
- An Ability to impose a stop on any new jobs or clone installs prior to unfitting the service/ de-commisioning the structure.
2 Likes
Regarding the first item listed, what seems eons ago, there used to be a function somewhat similar to what you are requesting.
I canāt remember exactly what I was looking at, maybe it was the fees paid into the corp wallet.
Anyhow, I once made a public raitaru private, and I contacted each user of the raitaruās services and told them in advance that the structure was going private and to seek services elsewhere. I was able to give everyone a date. I remember emailing going back and forth on this.
So, I see this request as useful and support it.
My alliance renames structures to āMOVE OUTā long in advance to decommissioning.
That seems to do the trick.
People will see in their asset window that they need to bring stuff elsewhere in advance and people know not to store new clones or start industry jobs in such structures.
While I see the use of a setting to disable new jobs and clone installs, a simple rename of the structure to something like āDO NOT USEā would already fix this issue.
1 Like
It would be nice if you could block any new jobs for industry or research, but allow existing ones to finish. Even within an Alliance with good communication, some still donāt listen. We used to rename structures āClosing -ā and send Alliance wide emails sometimes months in advance, and you still get people whining about lost jobs or assets. Right now the best you can do is blast out a closing date and do what you have to do!