> For the complete documentation index, see [llms.txt](https://luum.io/llms.txt).
> Canonical page: [Project Deployment Guide](https://luum.io/docs/amatis/programming/project-deployment).

LUUM.IO

# **Project Deployment Guide** - GUIDE

## Project Deployment for Amatis Controls and X-PoE Systems

Setting up a project with Amatis Controls and X-PoE switches requires careful coordination across design, configuration, installation, and optimization. To support successful deployments, the Project Deployment Guide offers a structured, step-by-step framework that teams should follow at the outset of any new project.

This guide should be considered a foundational reference for any Amatis or X-PoE deployment. Following it ensures reliable performance, minimal rework, and consistent results across projects.

## Purpose of the Guide

The Project Deployment Guide outlines the major activities required to bring a system from concept to commissioning. It serves as a checklist and planning tool to help:

- Ensure complete documentation and load profiling before deployment
- Align programming behavior with user expectations
- Minimize onsite troubleshooting through pre-configuration
- Streamline installation and testing
- Deliver a validated and optimized lighting control system

## Deployment Workflow Overview

The deployment process is grouped into four major phases. Each one contains best practices and task-level guidance to ensure a smooth handoff between stages:

### Design & Planning:

This initial phase focuses on gathering documentation and translating project requirements into a fully specified lighting control design.

Key tasks:

1. Collect floor plans, fixture schedules, and circuiting details
2. Calculate fixture loads per X-PoE port
3. Assign switch/port IDs, load numbers, and device names
4. Design the network architecture and power distribution
5. Perform fixture testing and load profiling to establish control parameters

> **Pro tip**
> Assign unique identifiers (like XS1-3 for switches and MS-103-1 for motion sensors) early and consistently—these will be used throughout deployment.
>
### Pre-Programming & Configuration:

Before any hardware is installed, the system can be structured in the Amatis platform. Pre-configuration helps reduce setup time and errors later in the process.

Key tasks:

1. Define light levels, switch behavior, scheduling, and occupancy rules
2. Build location structure and placeholder devices in the config app
3. Pre-load load types for each X-PoE port
4. Assign network profiles to wireless placeholders
5. Schedule a programming review for team alignment

> **Pro tip**
> Pre-programming is optional but strongly recommended. It creates a solid foundation for faster commissioning.
>
### Installation & Deployment

This phase brings the system to life—hardware is installed, firmware is updated, and devices are connected and configured.

Key tasks:

1. Install and configure AMBRs and X-PoE switches
2. Coordinate network/firewall access with IT
3. Install wireless devices and update firmware
4. Capture MAC addresses for all devices
5. Associate live devices with placeholders using MAC tables
6. Finalize wireless network migration and device communication

> **Pro tip**
> MAC address capture is critical—label and log everything during installation to simplify mapping and troubleshooting later.
>
### Testing & Optimization

Once installed, the system is verified and refined for performance and client satisfaction.

Key tasks:

1. Sync final programming to all devices
2. Validate device communication and firmware
3. Test lighting scenes in various locations
4. Fine-tune dimming, timeouts, and schedules
5. Conduct a client walkthrough and apply any requested adjustments

> **Pro tip**
> Testing in real use conditions is essential. Simulate day-to-day behavior (e.g., occupancy, scene changes) to catch edge cases early.
>
## Download the Guide

Project Deployment Guide (PDF), available from Luum.io.

This document includes detailed checklists, naming conventions, and best practices across all stages. It should be used as a reference from the start of any Amatis Controls or X-PoE deployment.

## Related Information

### Technical Support

Questions about deploying a project can be sent to [support@luum.io](mailto:support@luum.io). Include the site and the step you are on.

### Document Feedback

While we have taken great care to ensure the accuracy and completeness of this document, we welcome your feedback and suggestions. If you notice any errors or omissions, or feel a topic could benefit from further explanation, please email your feedback to [support@luum.io](mailto:support@luum.io).

### Revision History

| Date | Revision | Notes |
| --- | --- | --- |
| 11/3/2026 | A | Converted to the current guide format. |

### Disclaimer

All rights, title, and interest in and to this guide, including without limitation all copyright, trademark, patent, trade secret, and other proprietary rights, belong solely and exclusively to Luum.io and/or its licensors. This guide is provided solely for the purpose of planning an Amatis Controls or X-PoE deployment, and no license or other rights are granted or implied hereby. No part of this guide may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of Luum.io. The contents of this guide are subject to change without notice. The information contained herein is provided on an 'as is' basis and is for informational purposes only. Luum.io makes no warranty, express or implied, as to the accuracy, completeness, or usefulness of this information, nor does it assume any legal liability or responsibility for the consequences of any errors or omissions therein. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

---

_©2026 Luum.io. All rights reserved._
