on365 recognise that system planning is the most critical element of any IT infrastructure project. Planning errors lead to infrastructure errors that propagate and increase in magnitude through all consecutive development phases. These mistakes lead to unexpected costs, wasted time and generally a compromised IT solution that fails to meet business critical demands. on365 help avoid these challenges by introducing a flow-chart philosophy to IT infrastructure planning, the following outlines the basic methodology we bring to every project:
All sizes of IT facility require extensive planning, whether in the larger enterprise or the lighter requirements of an SME. IT implementation plans are often swamped with exhausting detail that doesn’t actually improve the decision makers chance of deciding upon the correct solution, on365 bring a simple approach to this phase of the process, ensuring that the correct choices are made at every step. With our experience in datacentre installation we can avoid small mistakes in the plans having far reaching consequences further down the line.
First steps to creation of a plan are as follow:
Process - initial steps in the on365 plan include assigning of responsibilities, project management appointment, agreeing and creating outsourcing relationships, budgeting, and scheduling.
System planning – the on365 plan transforms the original IT concept into a detailed installation design. To support the system planning effort, a clearly structured plan of data flow, business dependencies, and design strategy provides essential guidance. This “system planning sequence” is the pre-determined flow of ideas, historic activity, and data that transforms the initial project idea into a detailed installation plan. This part of the implementation plan has five clear sections that make it much easier to visualize and comprehend the flow of detailed activity that brings the plan to life.
The on365 Planning Sequence:
Determine IT Requirements
Through better understanding of a businesses current and future IT needs, on365 can advise the necessary changes and improvements to IT capability. From this point we can easily determine three important factors that will help shape the IT plan. These three points are criticality, capacity, and expected growth . Once established these three parameters help to begin developing the physical device requirement.
Develop System Concept - This stage of the on365 process takes the foundation parameters – criticality, capacity, and growth plan – and uses them to formulate a general concept of the physical infrastructure. The cornerstone of this is the selection of a reference design, which embodies the desired criticality and capacity, and has a scalability that will support the growth plan.
Determine User Requirements - Evaluation of user requirements determines whether they are valid, or should be adjusted in some way to reduce cost or avoid problems. User requirements for the project can be such things as key features and options, room constraints, existing IT constraints, and logistical constraints.
Preferences – Things that the user or client would like, but are subject to change or adjustment after consideration (or reconsideration) of cost and consequences.
Constraints – Things that either cannot be changed, or can only be changed at great expense or with unacceptable consequences. Constraints are preexisting conditions that are difficult or impossible to change.
Generate Specification - The on365 process of translating the user requirements (from the previous task) into a detailed kit-list. This particular sequence uses the intermediate step of creating a system specification. The specification consists of the following elements:
on365 specifications that do not vary from project to project. Examples of standard specifications are regulatory compliance, compatibility of subsystems, workmanship, safety, and best practices.
Client specifications that define the client-specific details of this project.
The last task in the planning sequence is the creation of a detailed final design for the installed system, this would typically include:
Despite planning being on the top of everyones “very important” list, and with the success of any IT project literally depending on it, planning is still considered too difficult, time consuming and complex for SME environments. on365 remove much of the complexity from IT planning by adopting a “dataflow” philosophy to every step of identifying, determining and implementing core strategies that complement the needs and requirements of the business, the individual and the rules and regulations that abound.
Throughout the project process, it is the two on365 planning phases – Prepare and Design – that lay the essential foundation for the project. In addition there is a common thread to the entire process, a simple flow of logic that successfully brings an idea or concept through planning and on to the final implementation phase. The parameters of this sequence are easily determined and in most cases follow this logical path:
When approached in this manner all aspects of the plan become more detailed and less abstract, tasks and responsibilities are clearly defined in a way that provides the right amount of information, with the right level of detail, at the right time. on365 adopt this method at everystage of the planning phase and by implementing this philosophy on365 ensure workload is reduced, unnecessary expense is minimised, project schedules are accelerated and decision making simplified for all of our clients.