The HDPlus IT management software provides critical architecture review processes that will help your team improve reliability, set standards, and reduce IT costs. Our experience has shown that establishing IT standardization is the foundation to improve system availability, reliability, and support software processes.
An architecture review can be requested by the user via the HDPlus support software platform. The user is presented with a short form to capture basic information regarding the request: description, time frame, contact information, business unit, and budget, at which point an architecture review control number is assigned.
HDPlus provides critical communications throughout the architecture review process as key milestones occur, updating the originator and key team members, via automated emails. The requester will also receive a request confirmation email that their request has been successfully submitted. The team leader assigned to the request will select the appropriate IT staff, coordinate meetings, and is responsible for driving each phase of the architecture review, including the project review meeting and deliverables.
Meetings are scheduled via the HDPlus interface with the internal customer initiating the project kick-off meeting; all other meetings are maintained and scheduled via HDPlus ensuring good communications are maintained at all times throughout the lifecycle of the process. The requester and all key stakeholders will receive automatic email status and dashboard updates.
Throughout the architecture review process, stored within HDPlus, is a repository that contains design documents, risk assessment, quotes received, and a final architecture recommendation.
An architecture review captures key information and confirms that installation requirements are adequate to support a new system, documents any special cabling, IP addresses, DNS naming, and components such as: rack space in the data center, power requirements, and HVAC capacity. In addition, reminders are sent via email to ensure maintenance contracts are invoked after the warranty periods end.
The repository becomes a source of technical information in case upgrades are needed or for future projects that are similar in scope.
Alerting – Throughout the course of its architecture review lifecycle, if delays or slow responses are experienced, the next level of management is notified to ensure every request receives efficient and prompt attention.
Reporting – Full reporting is available for architecture reviews, providing both summary and detailed reports, examples include the number of reviews entered last month or last week, how long to service the request, spread of requests from different departments, etc.
Dashboard – Status updates are summarized for managers and will include progress reports of open architecture reviews.