Ongoing Infrastructure Improvements
From DocWiki
This page is unchecked !!!| Overall Content Model |
| Where Activities Reside |
| Activities in Phase 5 |
| Phase 5 - Continuous Improvement |
|
| Content Model Relationship |
Contents |
Activity: Continuous Improvement - Infrastructure
Objective
There will be many opportunities to increase the business value delivered by the infrastructure environment. Besides the approach outlined in the Technology Blueprint, which is focused on delivering new capabilities, there should be a structured approach to looking at the existing environment and continuously improving the core capabilities that already exist.
Continuous improvement of the infrastructure environment is done to:
- Reduce cost
- Remove inefficiencies
- Improve software quality
- Improve manageability
- Reduce risk
Continuous improvement of the infrastructure environment involves closely monitoring the current-state environments and instituting tactical changes that are inline with the strategic vision.
Major Deliverables
- Improvements to integration infrastructure through re-configuration or re-design
- Changes to hardware
- Changes to Software Development approach
Tasks
Task 1: Continue Re-factoring and Integration
[ Edit Task ]
| Phase: | Phase 5 |
| Activity: | Ongoing Infrastructure Improvements |
| Sort Order: | 1 |
| Page Status: | Unchecked |
| Include Task?: | Used |
| Task Status: | Active, Incomplete |
| Short Name: | Re-factor Infrastructure |
| URL: | |
| Description: | Re-factoring toward a service- or Web-oriented architecture. |
| Objective: | [[HasObjective::Most integration processes are unnecessarily complex and difficult to mange. Organizations should strive to continuously improve their integration environment towards a service-oriented architecture based on principles of:
Revisiting existing integration infrastructure should be a planned part of the overall program – reviewing "working" components for quality and efficiency is still a valuable process. Feedback from the operation and monitoring lifecycle should act as the key input towards re-factoring.]] |
| Inputs: | Include:
|
| Outputs: | Include:
|
| Staffing: | |
| Total Hrs: | |
| Duration: | |
| Start Time: | |
| Cost: |
This page is unchecked !!!
Place whatever "free text" you wish here; it will appear at the bottom of the task listing.
Task 2: Continue Process Automation
[ Edit Task ]
| Phase: | Phase 5 |
| Activity: | Ongoing Infrastructure Improvements |
| Sort Order: | 2 |
| Page Status: | Unchecked |
| Include Task?: | Used |
| Task Status: | Active, Incomplete |
| Short Name: | Automate Processes |
| URL: | |
| Description: | Provide an ongoing process to automate processes. |
| Objective: | Manual business processes dominate most organizations. These manual processes, often the main avenue of performing work, have no ability to scale. Lack of end-to-end visibility into business processes result in "black holes" across organizational or departmental boundaries that breed a non-disciplined organization. To monitor the business activity, generating reports and Key Performance Indicator(s) is a heroic effort.
Most of these processes are unnecessarily manual, providing opportunities to significantly improve business capabilities. Automation of business processes helps to address some of the following issues:
These processes can be automated in a progressive fashion, focusing first on either the most inefficient processes or those that are easiest to automate. |
| Inputs: | Include:
|
| Outputs: | Include:
|
| Staffing: | |
| Total Hrs: | |
| Duration: | |
| Start Time: | |
| Cost: |
This page is unchecked !!!
Place whatever "free text" you wish here; it will appear at the bottom of the task listing.
Task 3: Upgrade Physical Infrastructure
[ Edit Task ]
| Phase: | Phase 5 |
| Activity: | Ongoing Infrastructure Improvements |
| Sort Order: | 3 |
| Page Status: | Unchecked |
| Include Task?: | Used |
| Task Status: | Active, Incomplete |
| Short Name: | Recommend Physical Infrastructure |
| URL: | |
| Description: | Upgrading physical infrastructure based on other information development improvements is a continuous process. |
| Objective: | Upgrading physical infrastructure related to hardware, network and platforms will provide a means to improve performance, reduce cost and scale to meet new business demands for higher volumes. Physical infrastructure changes can often be implemented reasonably easily, with major benefits to the business. Physical infrastructure changes should always be framed in terms that show business benefits, even if these benefits are non-functional.
Upgrading physical infrastructure shouldn’t just focus on the production environment. There are often major opportunities to improve efficiencies by improving infrastructure in the development and test environments. As even minor improvements in developer efficiency can greatly reduce cost and improve time-to-market, this is an area that should receive considerable focus. As cost/physical resource assets are continually decreasing, organizations should be intimately aware of changing physical infrastructure costs. There are often significant advantages that can be gained through consolidation or moving off legacy platforms. Infrastructure contracts should be reviewed at least every 6 months. |
| Inputs: | Include:
|
| Outputs: | Include:
|
| Staffing: | |
| Total Hrs: | |
| Duration: | |
| Start Time: | |
| Cost: |
This page is unchecked !!!
Place whatever "free text" you wish here; it will appear at the bottom of the task listing.
Task 4: Extend Metadata and Semantics
[ Edit Task ]
| Phase: | Phase 5 |
| Activity: | Ongoing Infrastructure Improvements |
| Sort Order: | 4 |
| Page Status: | Unchecked |
| Include Task?: | Used |
| Task Status: | Active, Incomplete |
| Short Name: | Continuous Metadata |
| URL: | |
| Description: | Provide for continuous initiatives to increase the use of metadata as a governing factor in the organization's information infrastructure. |
| Objective: | Organizations should be continuously moving towards a metadata-driven approach for integration. To achieve consistency, quality and reusability, metadata must be integrated between the sources of record for metadata. This metadata integration capability provides an ability to build metadata flows into and out of a managed metadata environment. Taking a metadata-driven approach also means:
The strategic architecture Blueprint should provide at least a long-term moving towards a metadata-driven architecture. This Metadata management approach will need to be across all components in the architecture. Foundation Capabilities for Metadata Management should be in place before moving to a more active metadata-driven integration approach. |
| Inputs: | Include:
|
| Outputs: | Include:
|
| Staffing: | |
| Total Hrs: | |
| Duration: | |
| Start Time: | |
| Cost: |
This page is unchecked !!!
Place whatever "free text" you wish here; it will appear at the bottom of the task listing.
Core Supporting Assets
Yellow Flags
- Resistance to re-factoring on the premise that the software already is in production
- Continuous Improvement of infrastructure must be managed specifically with the the infrastructure team, especially those not used to re-factoring and its benefits
