6.	Methodology 
The whole replacement will be divided into below phases:
•	Hardware confirmation
•	Internal examination
•	Replacement
•	Site acceptance tests
•	Nursing period
•	CCM Integration
•	Hardware disposal 
6.1	Hardware Confirmation
The hardware that has arrived will be verified by the Marine Department. After that, these hardware items will be delivered to Tidalis APAC for preparation and internal examination.
6.2	Internal Examination & Pre-deployment Preparation
The confirmed servers will be sent to Tidalis for preparation, which includes:
•	Pre-installation of software.
•	Compatibility testing.
•	Operational testing in a controlled testing environment. Refer to Section 7 Internal Examinations (assumed to be a separate detailed section).
•	Crucially, pre-configuration of a test environment for Data Processors (DP), Radar Data Processors (RDP) and Central Track Processors (CTP/COP) nodes to operate in test mode, compatible with the test mode RDPs. This is essential for the live vs. test comparison phase during on-site replacement.
6.3	Phased Replacement
To minimize the impact of the work and facilitate real-time comparison, the replacement will be separated by sites and will proceed with one RDP at a time per site, leveraging the oper and test modes for validation.

General Procedure for Each RADAR-Subsystem Replacement (2 servers per site):
Each RADAR-subsystem replacement will begin by addressing one of the two RDP servers at a site, specifically designed to ensure continuous operation and enable live comparison. The order will typically start with a non-main operational RDP if applicable, or Group B as specified.
Before initiating the replacement at any site, Tidalis will:
•	Confirm the current operational subsystem status.
•	Ensure that corresponding DP and CTP/COP nodes have a test mode instance or configuration ready to communicate with the new RDP server in test mode. This is a critical prerequisite for the comparison process.
In principle, only the RDP servers will be replaced. Other components, such as KVM, cables, and power relevant, will be adapted for use with the new servers unless any unexpected issues arise during the replacement. Tidalis will confirm these components will work as before replacement.
After replacing hardware at a remote site, Tidalis will place the existing hardware in the MD approved area at the site, pending further instructions. If the replacement causes an unacceptable impact, Tidalis will restore the existing hardware as part of a rollback procedure.
Detailed Step-by-Step for Replacing two RDPs at a Site:
(Applies to MAW, VTC, BHD, CTB, KCCS, NPO, SKC RADAR-subsystem replacements)
Let's use MAW as an example (RDP0111, RDP0112). This procedure will be replicated for all sites.
6.3.1	 Phase 1: Replacement of the First RDP and Live vs. Test Comparison
1.	Selection: Identify the first RDP server for replacement (e.g., MAW Group B: RDP0112).
2.	New Hardware Installation: The software-pre-installed new server (RDP0112) will physically substitute the existing RDP0112 hardware.
•	Crucially, the existing RDP0111 will remain in oper mode and fully functional, ensuring no disruption to live operations.
3.	Initial Boot & Test Mode Activation: Connect the existing cables to relevant ports on the new RDP0112 server and boot up the system. Immediately upon successful boot, Tidalis will change the node's mode to test: 
$ vtmis-node change test
4.	Test Environment Verification: Verify that the new RDP0112 (in test mode) is successfully communicating with the designated DP and CTP/COP nodes that have also been set to test mode.
5.	Live vs. Test Comparison (Initial SAT): With the existing RDP0111 still in oper mode and the new RDP0112 in test mode, Tidalis will conduct a focused comparison (an initial System Acceptance Test) to observe and analyze their respective data streams and operational parameters.
•	This comparison will allow direct observation of the new RDP's performance and data integrity (test mode) against the established production system (oper mode) without impacting live operations.
•	Any discrepancies will be identified and addressed before proceeding.
6.	Transition to Operational Mode (if successful): If the comparison confirms satisfactory performance and data consistency from the new RDP0112 in test mode, Tidalis will transition it to oper mode: 
$ vtmis-node change oper
7.	Operational Verification: Confirm that the new RDP0112 is now fully integrated and operating correctly in oper mode alongside the existing RDP0111.
6.3.2	 Phase 2: Replacement of the Second RDP and Final Site Integration
1.	Selection: Identify the second RDP server for replacement (e.g., MAW Group A: RDP0111).
2.	New Hardware Installation: The software-pre-installed new server (RDP0111) will physically substitute the existing RDP0111 hardware.
•	At this point, the newly installed RDP0112 will be in oper mode, maintaining continuous operation during this replacement.
3.	Initial Boot & Operational Mode: Connect the existing cables to relevant ports on the new RDP0111 server and boot up the system. The server will be brought online in oper mode (or transitioned to oper mode after initial boot).
4.	High Availability & Final Site SAT: Once both new RDPs (RDP0111 and RDP0112) are installed and operating in oper mode, Tidalis will confirm high availability supported by both groups. A comprehensive Site Acceptance Test (SAT) will then be conducted for the entire RADAR-subsystem at the site. This SAT will ensure both new RDPs function seamlessly together and meet all operational requirements.
5.	Nursing Period Initiation: If all SAT criteria pass, the nursing period will be initiated for this site.

edit the above part for me, as the final should be (new test mode RDP+ test mode CTP(=COP)+test mode IP(CSP)+test mode DP(for viewing the tracks))  vs live DP(for viewing the tracks)
as we cannot view tracks directly on the radar display processors(RDP)