Just Add Power System Takeover Guide: Identification, Inventory, and Documentation

Oct 30, 2026

Overview

Use this guide to take over an unfamiliar Just Add Power system. First identify whether it already uses AMP, then recover the available system information before completing the remaining inventory. You can document a JADConfig or unknown system without installing or running JADConfig.

For an AMP Standardized Configuration or AMP Alternate Configuration system, use its Gather Details workflow before manually rebuilding the inventory. Save the available results, verify them against the installation, and complete the Takeover Form with any missing information. For a non-AMP system, or when identification or retrieval remains unsuccessful, use the manual steps in this guide.

JADConfig End of Support: January 1, 2027. Beginning on that date, a system must be migrated to AMP before the Just Add Power Support Team can provide further troubleshooting or system service. JADConfig-related support-site articles, documentation, downloads, and drivers are scheduled for removal beginning on that date. See the JADConfig End of Support Notice.

End of Support does not disable an existing system. The survey below preserves the information needed to plan its next steps without relying on JADConfig availability.

Before You Begin

Confirm access to the jobsite, equipment, network administrator, and control system programmer.
Record the reason for the takeover and the system's current condition. Identify which sources and displays work, which fail, and whether switching or endpoint control is affected.
Open or print the Takeover Form. Use its second-page addendum for additional switches and attach a device-by-device inventory when the summary fields are insufficient.
Take an overview photograph of the rack and existing connections before touching the wiring. Collect detailed device and port photographs as needed after identifying the system type.
Agree on any interruption needed to access concealed equipment or display a diagnostic screen. Begin with checks that leave the operating system connected.

Preserve the existing configuration: Do not factory reset equipment, upload switch configuration files, execute AMP Build New, update firmware, change addresses or VLANs, or move device, uplink, or stack connections during the survey. Those actions belong to a separately planned service or migration procedure.

For each value, record where it came from and whether it was verified on-site. Keep old report values separate from current observations when they disagree. Store credentials in the jobsite's protected service records; avoid exposing them in general photographs or shared examples.

First, Identify the System Type

Before tracing every device or manually collecting addresses, check whether the installation uses AMP Standardized Configuration or AMP Alternate Configuration. Ask the owner, previous installer, or service technician how it was configured and whether it has been migrated since its original installation. Record the type as Confirmed, Suspected, or Unknown, with the supporting evidence.

Look for a jobsite-specific AMP project or Report File on the original service PC or in the site records. Check its configuration type, switch identity, and a sample of installed devices or port connections. You do not need to complete the full physical inventory to make this initial comparison. See AMP Projects and Reports for the folder location and access steps.

If records are missing, inspect a small sample of readily accessible switch connections and ask the programmer or network administrator to inspect the existing control project and switch configuration. Use the indicators below together. An AMP installation on a service PC, an IP address pattern, a supported switch, device firmware, or port order alone does not establish how this jobsite was configured. See Standardized and Alternate Configurations for the differences.

Keep identification and access separate: A confirmed AMP system may still be unreachable. If the type is unclear, use only the switch access, network connection, or device address checks needed to obtain more evidence, then return here. You do not need a complete manual inventory before checking for AMP.

System Type Indicators

Inspect existing records and settings without changing them. Port patterns describe assigned ports; empty reserved ports, later changes, and unresolved cable destinations can obscure the visible order.

Evidence	Possible Interpretation	What to Check Next
Jobsite-specific AMP project or report identifies Standardized or Alternate Configuration	Evidence of an AMP installation	Compare the date, device identities, network settings, and a sample of connections with the current installation. Check for a later migration or replacement.
Decoder ports begin at port 1, Encoder ports follow, and the designated network uplink is the last RJ-45 port of the single switch or Switch 1	AMP Standardized port pattern	Compare the records and actual assignments with AMP Standardized switch configuration guidelines. Check a sample rather than tracing every endpoint first.
Switch configuration contains the expected AMP VLAN structure, including system VLAN 100 and source VLANs beginning at 101	Additional evidence of AMP Standardized Configuration	Compare device-port membership with How VLAN Switching Works. Retain the existing configuration; VLAN numbers alone are not proof.
Data Network on port 1, followed by Encoder ports and then Decoder ports; legacy switch configuration uses Decoder VLAN 10 and source VLANs beginning at 11	Common JADConfig pattern	Compare any saved JADConfig report with the current switch and connections. A historical report does not rule out a later AMP migration.
Devices share a dedicated VLAN and source selection uses Decoder Channel assignments	Multicast Switching, which may be AMP Alternate or manually configured	Look for a matching AMP Alternate project/report and inspect existing network and device settings with the administrator. Multicast Switching supports both AMP and manual setup; the switching method alone does not establish AMP history.
Older 2G Series hardware uses a single-VLAN multicast design	A possible legacy multicast installation	Record the exact hardware and existing settings. Do not classify it as AMP Alternate: AMP 2G Legacy Mode requires Standardized Configuration.
Several switches share one management interface and use stack-member IDs, or have separate management interfaces and trunk links	Clues about the network topology	Use Stacking vs Trunking to identify members and links. The topology alone does not establish configuration history.
Control project identifies a switching driver, command target, or serial connection	Evidence of how sources are controlled	Ask the programmer to verify the installed driver and target. A generic device or endpoint-control driver, or a serial cable alone, does not establish the configuration type.

If the property contains separate matrices or networks, identify each independently. Do not combine devices from different systems into one inventory solely because they share a rack or building.

Choose Your Takeover Path

Identification Result	Next Action
AMP Standardized Configuration	Use Standardized Gather Details first, then verify the results and document gaps. Include supported systems already operating in AMP 2G Legacy Mode.
AMP Alternate Configuration	Use Alternate Gather Details first, then verify device information and document the network with its administrator.
JADConfig or another identified non-AMP configuration	Recover existing records and use the manual survey for missing or unverified information. Plan any migration separately.
Suspected AMP or Unknown	Use the minimum access checks above to seek supporting evidence. If the type remains unresolved, continue the manual survey and retain its confidence level. You do not need to prove that it is non-AMP to proceed.
AMP identified, but Gather Details cannot complete	Keep the AMP identification. Record the retrieval failure and use recovered records and targeted manual checks for unresolved items.

Gather Details for an Existing AMP System

Use the workflow for the identified AMP configuration before manually collecting every device address or switch connection. Preserve any existing project and report, then save new results separately for comparison. The original configuration PC is useful for recovering files but is not a prerequisite for using AMP on your service PC.

Establish a wired connection and the correct network path first. Use a documented device address where available. If the connection or address is unknown, complete the relevant network connection and device address checks, then return to the appropriate workflow below. Keep devices connected to their assigned ports.

AMP Standardized Configuration

Connect the service PC through a verified Data Network connection. Confirm the network path to an existing Encoder or Decoder, including any required routing.
Open AMP and select Service > Gather Details.
Follow Gather Details with AMP to retrieve the current system information and generate a Report File containing IP addresses, device counts, and port connections.
Save the new report with the takeover records, then continue to Review the Gathered Information.

AMP Alternate Configuration

Connect the service PC using a wired adapter and confirm access to the established devices through the site's existing VLAN and routing design. Have the network administrator verify the connection if needed.
From the AMP start screen, select Alternate Configuration in the lower-left corner and acknowledge the disclaimer.
Open Gather Details from the Alternate Configuration service options and follow its prompts to gather the available system information.
Save the available results with the takeover records. Continue to Review the Gathered Information and obtain any missing switch, port, and network details from the administrator or manual inspection.

Alternate Configuration uses a separately managed multicast network. Do not assume its results include the same switch inventory or port mapping as a Standardized report. The linked Standardized video demonstrates a different entry path.

Review the Gathered Information

Compare the results with the expected installed equipment and recovered records. Match device identities, network settings, and available assignments to a sample of the actual installation.
Account for missing, offline, disconnected, or inaccessible devices separately. A successful retrieval does not establish that every installed device was included.
Use verified results to populate the Takeover Form and attached inventory. Confirm source and display names, control-system details, physical locations, and inter-switch connections wherever the results do not establish them.
Continue at Gather System Details. Use the manual sections only for the checks and missing information still needed.

Avoid duplicating the inventory: Use verified retrieved information as the starting record. Manually trace or inspect unresolved connections and equipment rather than recreating every known field.

If Gather Details Cannot Complete

Record the AMP version, selected configuration workflow, device address or other inputs, PC connection, and any error shown. Check the existing power, wired connection, address, routing, and access permissions. Keep the identification result separate from the retrieval result: failure does not prove the system uses JADConfig or that equipment is absent.

If access remains unavailable, use recovered records and the manual survey to fill the gaps. Record unresolved items for Support rather than resetting equipment or starting a configuration workflow. For an affected TP-Link Standardized system, the switch-firmware service issue may be relevant; evaluate any corrective work separately from this survey.

Check for Existing Documentation

Ask the owner, previous installer, network administrator, and control system programmer for existing reports, project files, cable schedules, network diagrams, switch configuration backups, and control system programming. Copy the available records before changing the installation.

A report may contain switch management settings, device addresses, device counts, and port assignments. Check its date and compare it with the installed hardware. A saved report describes the system when the report was created.

AMP Projects and Reports

On the PC previously used to configure or service the system, open AMP.
Select the top-left menu, then File > Open Projects Folder.
Locate the jobsite's project and Report File. Preserve a copy and compare the switch and endpoint inventory with the installation.

The usual location is C:\Users\[YourUsername]\Documents\Just Add Power\AMP\Projects. See Open the AMP Projects Folder if the folder is unavailable or redirected.

If the records identify AMP Standardized or AMP Alternate Configuration, use the applicable Gather Details workflow before completing the manual inventory. A missing project folder on your own PC does not show how the jobsite was configured.

Recover records without reconfiguring: A saved project may describe configuration work that was never completed. Compare it with the current installation and retrieved information. Do not load an unfinished configuration workflow or execute Build New to test the system identity.

JADConfig Reports

Recover existing reports as files. You do not need to launch JADConfig to locate or read a saved report.

On the original configuration PC or its backup, open File Explorer.
Check C:\Program Files (x86)\Just Add Power\JADConfig\Reports. If it is missing, ask for a backup or previously exported copy.
Check the report date and compare its switch models, device counts, and port assignments with the installed system.
Keep the original report with the survey and record any differences in the Takeover Form.

If no report exists: Continue with the physical inventory below. Do not delay the survey to obtain JADConfig, and do not reset equipment to recreate a report.

Preserve Switch Configuration Backups

If switch login is available, export a backup before any planned service changes. Use the instructions for the installed manufacturer and interface:

Record the switch identity, firmware, export date, and configuration type. Where available, preserve both running and startup configurations: running settings may include changes not saved for the next boot. Do not save, overwrite, upload, or reboot the switch merely to make the files match. Use manufacturer instructions for other models.

Store backups in protected jobsite records because they can contain credentials and network details. A backup preserves configuration evidence; it does not by itself confirm source/display mapping or compatibility with another switch model.

Tools to Bring

Bring a Windows PC, a wired Ethernet adapter, labels, a camera, and access to the Takeover Form. Prepare the following tools as needed for the installed equipment.

Software

Advanced Matrix Programmer (AMP) for established AMP workflows and the planned migration.
Bonjour Browser for supported devices reachable on the same local network.
PuTTY for supported terminal access.
IPv4 discovery software approved for use on the site's network.
Switch manufacturer documentation for the exact model, including console cable and terminal settings.

JADConfig is not required for this survey. Retain any existing jobsite reports and configuration backups.

Hardware

USB-to-serial adapter and the appropriate switch console cable
Just Add Power debug cable when serial access to a device may be required
Known-working network and HDMI cables
Headphones with a 3.5 mm connector
A compatible spare power supply when devices are not powered using PoE:

Bring labels for both ends of each network cable. Use only a power supply appropriate for the exact device model.

Gather System Details

Complete the Takeover Form using recovered documentation and the verified results from the applicable AMP Gather Details workflow. Use the sections below to check the installation, fill missing fields, and resolve differences. For non-AMP or unidentified systems without useful records, work through the full manual survey. If the type becomes clear during that work, return to Choose Your Takeover Path before continuing unnecessary manual checks.

Use Unknown, Inaccessible, or Not present as appropriate. An unanswered field does not explain whether the item was checked.

Attach a device-by-device source/display map. For each switch, account for the installed Encoders and Decoders, including offline equipment. Use existing port assignments where verified and trace unresolved connections. A port range or photograph alone may not preserve the complete mapping.

Contact and Jobsite Information

Record the current service contact's first and last name, company, telephone number, email address, and jobsite name. Include the survey date and a contact for the network and control system when available.

Control System

Record: The control platform, processor model, programmer contact, project availability, installed switching driver or plugin, and its connection target.

Identify the control processor in the rack and compare it with the project documentation.
Ask the programmer to identify whether switching uses an official Just Add Power driver, a third-party driver, or custom programming. Record the driver name and version when available.
Record whether commands target a switch or a Just Add Power device, the configured IP address, and whether the connection uses Ethernet or serial.
Record which source and display names correspond to each Encoder and Decoder. Include IR, RS232, CEC, audio, USB, or other connections that must be preserved.
Confirm who can supply and update the control project. Mark driver details as Unknown if the project cannot be inspected.

Review Control System Drivers for integration resources. Prepare driver changes as part of migration planning; leave the active control program in place during the survey.

Device Series

Read the exact model label on every Encoder and Decoder. Record the model, labeled MAC address, physical location, and whether it is an Encoder or Decoder. Compare labels with accessible device information where possible.

For older enclosure labels or remotely reported models, use Identify a 2G Series Model or Identify an Omega Series or Ultra Series Model. Apply command-based methods only where the article supports the installed firmware. Hardware series alone does not identify the configuration software.

Check every installed series on the form. A product photograph helps recognize hardware, but the label and exact model identify it. Devices with similar enclosures can have different capabilities.

MaxColor Series

Record the full MaxColor model from the label, including any suffix. Keep its firmware and connection information separate from other installed series.

MaxColor Series Decoder hardware example

Ultra Series

Record the exact Ultra Series model. If the installation also contains 2G Series devices, check model-specific 2G Legacy Mode compatibility before planning migration.

Ultra Series Decoder hardware example

Omega Series

Record the exact Omega Series model. Older records may describe Omega hardware as 2G/3G; preserve that original label alongside the verified model.

Omega Series Decoder hardware example

2G Series

Record each 2G Series model. AMP supports eligible systems through 2G Legacy Mode in Standardized Configuration. Review the exact hardware mix and limitations before planning the transition.

2G Series Decoder hardware example

1G Series

Identify and record 1G Series hardware separately. Do not assume it can be included in an AMP configuration; request an evaluation of the required replacement path.

1G Series device hardware example

Switch Information

Complete one switch entry for every switch carrying Just Add Power traffic. Record the physical location and any existing switch or stack-member ID. If an ID is unavailable, assign a temporary survey label such as Rack A / Switch A; keep it separate from any future AMP switch assignment.

Switch Model and Hardware Version

Read the manufacturer label and record the complete model number, hardware version, serial number, and labeled MAC address.
If the label is inaccessible, check the system information page through an existing management connection. Record the switch firmware version when available.
Photograph the label and the port numbers. For a stack, identify each physical member rather than recording only the shared management address.
Repeat for all switches and record the total switch count.

Example switch manufacturer label showing the switch model and MAC address

For AMP Standardized migration planning, compare the exact model and hardware version with Supported Switches for AMP Standardized Systems. For multiple switches, also review Multi-Switch Considerations.

Compatibility and identification are separate checks: A current support list determines suitability for the planned AMP system. It does not prove how an older installation was configured. Preserve the installed configuration and available reports as evidence.

Switch Management IP Address and Login

Record: The management IP address and subnet mask when available, access method, and whether the supplied login was accepted. A responding IP address is not proof of a successful login.

Start with the report, network records, and control project. Connect the service PC to a known Data Network connection, then check the methods below.

Locate the Switch Address

Record the PC's wired IPv4 address, subnet mask, and default gateway. In Windows, execute ipconfig in Command Prompt to view the adapter settings.
Ask the network administrator to check the router's client list, DHCP leases, reservations, and network records for the switch. A statically addressed switch may not appear in the DHCP lease list.
If the switch is not documented, scan the authorized local IPv4 subnet using an approved discovery tool. Compare a result with the switch's labeled MAC address and model; a manufacturer name alone is insufficient.
Open the candidate address in a browser and verify the switch identity and login. Record any address or credentials that remain unconfirmed.

Comparison of switch label information with an Advanced IP Scanner result

Advanced IP Scanner range and scan controls

Example router connected-client lists used to identify a switch IP address

No result does not mean no switch: A scan covers only the selected address range and reachable networks. A different management subnet or VLAN, filtering, or an incorrect PC connection can prevent discovery. Ask the network administrator to verify the management network before changing anything.

If Network Access Is Unavailable

Check whether the exact switch has a console port and obtain its manufacturer-specified cable and terminal settings.
Use the manufacturer's documented display-only procedures to inspect the current management settings and system information, if the available credentials permit access.
Record the result. If access cannot be established, mark the management address or login as Unknown and continue the physical inventory.

Do not use password recovery, reboot, factory reset, or configuration commands to complete this survey. Missing credentials can be addressed during a planned migration after the required connection mapping has been recorded.

Encoder Ports and Count

Inventory each installed Encoder, including disconnected or unpowered units. Distinguish the installed count from the powered or reachable count.

Starting at the lowest connected Encoder port on the current switch, trace the network cable through any patch panel to the Encoder. Record intermediate panel labels.
Record the device model, labeled MAC address, physical location, connected source, switch identifier, and full port designation.
Match the physical connection with existing cable labels, port descriptions, or a switch MAC address table when available. MAC entries learned through an inter-switch link do not identify the endpoint's local port; continue tracing on the downstream switch.
Label the device and its cable consistently without removing useful existing labels. Record every network connection for devices that use more than one switch port.
Enter the count and first/last port in the form. Attach the exact port list when there are gaps or additional connections.

A link LED confirms a link, not the identity of the device. An empty or dark port is not proof that no installed device belongs there. Mark unresolved cable destinations for follow-up.

Decoder Ports and Count

Starting at the lowest connected Decoder port on the current switch, trace each connection through any patch panel to the Decoder.
Record the device model, labeled MAC address, physical location, connected display or destination, switch identifier, and full port designation.
Record associated control, audio, USB, and video-wall connections or assignments when present.
Label the device and cable consistently. Include unpowered or disconnected Decoders and identify their condition separately.
Enter the count and first/last port in the form. Attach the individual connection list and repeat the inventory on every switch.

Keep the current device order and control-system names in the inventory. Do not move cables to make the existing installation match an expected port pattern. The migration preparation guide supplies the E1/E2 and D1/D2 labeling sequence when a JADConfig system is being prepared for AMP.

Data Network Connection

Trace the existing connection from the Just Add Power switch toward the router, core switch, or control network.
Record the port and equipment at both ends. Compare the physical connection with port descriptions, the report, and network documentation.
For multiple switches, record every inter-switch link and stack connection separately, including the port at each end, cable type, and physical stack-member identifiers.
Record the router model, relevant network subnets, and existing routing information when available from the network administrator.

Verify the service-PC connection: An unused port may already be assigned to an Encoder or Decoder VLAN. Connect through a verified Data Network access point. Do not disconnect an endpoint, change VLAN membership, or break a stack to gain access.

If device access requires routing, first confirm the actual Device Network, subnet mask, and next-hop address from the installed configuration or network records. Then follow Static Routing for an Established Just Add Power System with the network administrator. Do not guess routing values from an IP-address pattern.

Working control does not establish PC access: The control processor may use its own gateway or a different permitted network path. That does not provide routing for the service PC. Verify access from the PC itself. For Alternate Configuration, use the site's actual inter-VLAN router or Layer-3 switch as appropriate; do not assume an AMP Standardized switch gateway.

Device IP Address

The form requests one Encoder or Decoder IP address. Identify the specific device and record its switch connection, model, address, subnet mask, and gateway when available. Continue recording additional device addresses as they are verified.

Begin with a saved report or the control project's endpoint settings. Treat saved addresses as unconfirmed until matched with the installed equipment.

Check Local Discovery Where Available

For Omega Series, Ultra Series, and MaxColor Series devices on the same local network as the service PC:

Open Bonjour Browser and expand Web Server (HTTP).
Select a device and record the displayed address and service name.
Match it to the physical device using the label and MAC information when available. See Bonjour Browser Device Discovery.

Bonjour discovery does not normally cross VLAN or routed boundaries. An established VLAN system's endpoints may not appear from the Data Network even when video works. Do not change VLANs or move endpoints to make them discoverable. This procedure does not assume Bonjour support on 2G Series or 1G Series hardware.

Read a Decoder Diagnostic Screen

A diagnostic screen can provide a Decoder address without first establishing a network connection. Use an existing diagnostic screen if one is already visible.

Confirm the interruption first: Removing an Encoder's HDMI input interrupts that source for every destination currently viewing it. Agree on an appropriate source and service window before performing the following steps.

Identify a display connected to a Decoder and the source it is currently viewing. Record the original source selection.
Locate the Encoder for that source and disconnect only its HDMI input cable. Leave power, network cables, and switch connections in place.
Wait for the diagnostic screen. The documented procedure for 2G Series, Omega Series, Ultra Series, and MaxColor Series describes a wait of approximately 10 seconds; the screen layout depends on the installed firmware.
Photograph the full screen. Record the Decoder's Local IP or RX IP and any model, firmware, or date information shown.
Reconnect the same HDMI cable and verify that the affected destinations return to their previous operation.

The Local/RX field identifies the Decoder. A Remote/TX field can show the last Encoder viewed; do not use that field alone to identify the current Encoder.

If a diagnostic screen does not appear or the required fields are absent, record the result. Do not reset the device or change its settings to force the screen. See Locate a Device IP Address for Omega Series, Ultra Series, and MaxColor Series, and use the 2G guidance in the firmware section below for older hardware.

Just Add Power Decoder diagnostic screen showing device and firmware information

Verify Access to the Identified Device

After establishing the correct network path, open the device address in a browser using the interface supported by that model and firmware. Compare the displayed identity with the physical inventory and record whether access succeeded. Use Access a Device for Omega Series, Ultra Series, and MaxColor Series, or Access a 2G Series or 2G Legacy Mode webUI for older hardware.

If the system is identified as AMP Standardized or AMP Alternate Configuration, return to its Gather Details workflow before manually collecting the remaining information. If identification or retrieval remains unresolved, continue the manual survey and record the uncertainty.

If access fails, record the PC connection, the observed device address, and the method attempted. A visible diagnostic address does not establish reachability. Continue documenting physical connections instead of changing addresses or starting a configuration workflow.

Firmware Version

Record: The complete version string, build or displayed firmware date, device model, and the method used to obtain it. Identify which device each value belongs to.

Omega Series, Ultra Series, and MaxColor Series: View the firmware information in the device webUI, diagnostic screen, or an applicable AMP inventory. See Identify the Firmware Version of a Device.
2G Series: On a reachable device, open System > Version Information in its webUI. If only the diagnostic screen is available, record the complete displayed date and a photograph. Do not invent a version number from the date.
Other or inaccessible hardware: Record the exact label, any displayed version information, and what remains unknown.

Record each version encountered, especially after hardware replacements or where multiple series are installed. A report's firmware entry remains historical until checked against the current device.

Check compatibility before updating: Compatible firmware is required, but version strings may differ by series, model, and operating state. Do not assume every device must carry the same version string. Leave firmware unchanged during this survey; use the applicable AMP compatibility workflow during the planned transition.

Changes and Additional Notes

List changes already made since taking responsibility for the system, including replaced hardware, moved connections, firmware or address changes, and control programming updates. Include the date, original and new values when known, and the effect on operation.

Attach the following when they do not fit in the form:

The device-by-device source/display map and all network connections.
Installed, powered, and reachable counts, with offline equipment identified.
Inter-switch and stack connections, mixed series, and devices using multiple ports.
Disagreements between reports, physical labels, and current observations.
Unknown values, inaccessible equipment, missing credentials, and the next person or access needed to resolve them.

Plan the AMP Transition

For an established JADConfig system, use the completed takeover record to begin the preparation guide for a single-switch system or a multi-switch system. Complete the Migration Form as well as the Takeover Form when planning that transition.

Confirm the exact device models and which existing switches can be retained. Review model, hardware version, firmware requirements, capacity, and multi-switch requirements before acquiring replacements.
For 2G Series systems, review 2G Legacy Mode Compatibility. This mode requires Standardized Configuration, has model-specific restrictions, and limits compatible Omega Series and Ultra Series devices to 2G capabilities, including a maximum video resolution of 1080p.
Prepare the control system update with the programmer. Plan the AMP-compatible switching driver, endpoint-control address changes, and routing requirements. If the installation uses SwitchPlease, coordinate the replacement control integration with the provider before the transition.
Acquire required hardware and prepare the control project before scheduling downtime. Leave the current program and system connections in place during preparation.
Schedule configuration, repatching, firmware changes, control deployment, and commissioning together. Use the final AMP Report File to confirm new addresses and complete the control update.

A completed survey is the starting point for migration planning. It does not confirm that every installed device or switch can be retained.

Complete the Takeover

Check every form field. Record the configuration type and confidence level separately from the access and retrieval results. Enter Unknown with a reason wherever a value could not be verified.
Reconcile device counts with the device-by-device inventory. Identify each Encoder's source, each Decoder's destination, and every switch connection.
Attach labeled equipment and connection photographs, diagnostic-screen photographs, recovered reports, and available switch and control project backups.
Confirm that any temporary HDMI interruption has been restored. Restore service-PC network settings changed for access, remove temporary service routes when no longer needed, and record the system's condition at the end of the visit.
Save the form and supporting records with the jobsite documentation. Keep credentials protected.
If assistance is needed, submit the completed Takeover Form to Just Add Power Support. Include the existing ticket number when available. For a JADConfig transition, include the Migration Form and identify the unresolved planning questions.

Survey complete: Another technician should be able to identify the hardware, follow the source and display connections, distinguish verified settings from unknown values, and understand the required next steps from the saved record.