Aging Validated Computer Systems
Leaving unused validated systems active in the environment creates an unwelcome anchor to the past. For IT departments, budgets will start to balloon in relation to the number of these legacy systems. IT needs to reinvent itself every 3-5 years to keep up with the world’s corporate expectations of a viable computing work environment. Legacy systems have dependencies that hinder IT’s ability to reinvent itself. Countless hours are spent doing risk assessments on validated systems, thus ballooning the cost of change – this includes legacy systems on the network as well. The older the system, the harder it is to protect, maintain and advance its surroundings. Segmenting these systems is a key strategy to controlling costs.[/fusion_builder_column_inner]
Why Are We The Best?
Small Number of Validated Computer Systems:
For a small company with a small number of validated computer systems (High level overview):
- Identify the new location of the system (either in a Qualified Virtual environment or new physical hardware)
- One dry-run conversion for confirmation of data integrity and process
- Validation Plan and migration script created
- Change Control opened
- Update and design Documentation, Diagrams, Procedural or other Qualification paperwork
- Migrate system(s)
- Verify data integrity and application functionality
- Re-execute PQ or a pre-approved light version of the PQ
- Close Change Control and Validation Plan
For large validated system footprint
For large enterprise companies, there may be some pre-work (High level overview):
- Perform a series of documented migrations where data integrity and the operational ability of the applications can be proven to maintain compliance (non-validated systems can be used)
- Format migration script(s) into corporate templates
- Setup of two or three types of qualified environments:
- Portions segmented for occasional access with few ties to corporate network
- Deep archive where systems are kept, but not expected to ever be needed
- Currently active system that need to be on a qualified segment of the infrastructure
- Capacity verification
- One dry-run conversion for confirmation of data integrity and process
- Validation Plan and migration script created
- Change Control opened
- Update and design Documentation, Diagrams, Procedural or other Qualification paperwork
- Migrate system(s)
- Verify data integrity and application functionality
- Re-execute PQ or a pre-approved light version of the PQ
- Close Change Control and Validation Plan
Validated System Lifecycle Program
Creation of a Validated System Lifecycle Program (High level overview):
- Create a validation lifecycle run book
- Create a schedule of migrations
- Create a risk matrix and dependency chart
- Create migration budgeting tools for application owners
- Create any charge-back pricing structures
- Create templates for migration projects
- Create a communication, acceptance, procedural and time-management plan
- Create acceptance, communications and issue management processes
- Create report templates
- Create a brief recorded informational presentation for application owners to understand the process
- Create a training kit for each role in the program as well as required training for each participant
- Create an executive dashboard
- Run the program