library management

As an administrator I require a better mechanism to manager AF Library objects across multiple AF servers. I would suggest extending the current library functionality in AF to include the following: * library can be versioned * Objects created in AF from a library are read-only and linked to the library. e.g. a user is unable to alter an element template that is created from a library. If the library is updated the linked object in AF is updated. If the object is removed from the library the equivalent object is removed from AF. * Powershell based interface for the management of libraries on AF servers. This will facilitate automation of the library management. Management would include deploying, updating and removing a library from an AF Server and AF Database. * Library dependency. A library should allow for dependencies. e.g. A smelter library depends on the core equipment library. I'm of the opinion that this is an essential element (pun intended) to making AF a truly enterprise solution.