In information systems changeover, what does the term “parallel run” specifically refer to?

Introduction / Context:
Parallel run is a classic system changeover strategy used during implementation of a new information system. The idea is to mitigate risk by keeping the trusted legacy process active while the new solution proves its accuracy and reliability under real workloads.

Given Data / Assumptions:

• There is an existing production system in use.
• A new system has been developed to replace it.
• Management wants to minimize operational risk during cutover.

Concept / Approach:
Parallel run means both systems process the same transactions for a defined window. Outputs are compared, discrepancies investigated, and corrective fixes applied. This approach provides strong assurance but carries additional cost and effort because two environments must be supported concurrently.

Step-by-Step Solution:

Verification / Alternative check:
An alternative is pilot or phased changeover. Those reduce overlap but do not provide full dual processing for all transactions, so assurance is weaker than parallel operation.

Why Other Options Are Wrong:

Common Pitfalls:
Stopping comparisons too early, failing to reconcile master data differences, and underestimating staff workload to run two systems are common issues.

Final Answer:
Operating the old system and the new system concurrently for a period.