Approach, Objective and Scope
Simply, the objective is to improve productivity.
Characteristics that will help accomplish this include:
› enhanced infrastructure intelligence,
› better response times for existing applications,
› efficient support for new applications,
› higher availability,
› greater process and quality integration, and
› minimal capital and operations costs.
Strategically, the characteristics associated with administration and support of this infrastructure will incorporate but not be limited to; simplicity, evolutionary capability, ease of installation and operation, security and be multi-vendor-standards based.
The work plan and deliverables recognize that processes, infrastructures and services are unquestionably evolutionary in nature. Stringent schedules and the challenge of designing 'enterprise intelligence' that will accommodate the immediate needs and provide for evolutionary growth, demands a visionary, but practical solution. Priority is directed to those defined elements that have the greatest need for increased productivity/commonalty. Resources (people, equipment, money etc.) are best utilized in a consolidated and integrated deployment effort rather than fragmenting these resources over multiple projects.
The objective in the longer term is to increase project-oriented flexibility, while reducing costs for churn management and operations. Thus the challenge of providing increased responsiveness to the organization and simplified operation for the end-user, information/facility manager. The scale of these programs demands definition and the involvement/integration of the Client organization.
In allocating responsibilities, each project team leader will be prime for developing the planning logic specific to their area of responsibility. ORION will participate in this programming requirement, firstly to compile the logistical sequence of events, and secondly to ensure that the criteria can be developed as the component master plan for measurement and accountability. The sums of these project schedules are consolidated, logistical concurrence is introduced and the master schedule is presented and adopted by the entire team. The identified tasks and milestones are then used as administrative and technical benchmarks for accountability and measurement.
Team composition comprises strategically and functionally integrated offices. Internal project responsibility is clearly focused. Diffusing roles between day to day operations, design and implementation will lead to disruption, delays and cost impact when inevitable trade off between design scope and implementation realities demand resolution. Empowered key resources will resolve conflicting objectives . ORION's primary responsibility is to adhere to the control philosophy, to be focused on execution.
Characteristics that will help accomplish this include:
› enhanced infrastructure intelligence,
› better response times for existing applications,
› efficient support for new applications,
› higher availability,
› greater process and quality integration, and
› minimal capital and operations costs.
Strategically, the characteristics associated with administration and support of this infrastructure will incorporate but not be limited to; simplicity, evolutionary capability, ease of installation and operation, security and be multi-vendor-standards based.
The work plan and deliverables recognize that processes, infrastructures and services are unquestionably evolutionary in nature. Stringent schedules and the challenge of designing 'enterprise intelligence' that will accommodate the immediate needs and provide for evolutionary growth, demands a visionary, but practical solution. Priority is directed to those defined elements that have the greatest need for increased productivity/commonalty. Resources (people, equipment, money etc.) are best utilized in a consolidated and integrated deployment effort rather than fragmenting these resources over multiple projects.
The objective in the longer term is to increase project-oriented flexibility, while reducing costs for churn management and operations. Thus the challenge of providing increased responsiveness to the organization and simplified operation for the end-user, information/facility manager. The scale of these programs demands definition and the involvement/integration of the Client organization.
In allocating responsibilities, each project team leader will be prime for developing the planning logic specific to their area of responsibility. ORION will participate in this programming requirement, firstly to compile the logistical sequence of events, and secondly to ensure that the criteria can be developed as the component master plan for measurement and accountability. The sums of these project schedules are consolidated, logistical concurrence is introduced and the master schedule is presented and adopted by the entire team. The identified tasks and milestones are then used as administrative and technical benchmarks for accountability and measurement.
Team composition comprises strategically and functionally integrated offices. Internal project responsibility is clearly focused. Diffusing roles between day to day operations, design and implementation will lead to disruption, delays and cost impact when inevitable trade off between design scope and implementation realities demand resolution. Empowered key resources will resolve conflicting objectives . ORION's primary responsibility is to adhere to the control philosophy, to be focused on execution.