Alliant Software Suite - IT Infrastructure Requirements

  • 1 February 2024
  • 0 replies
  • 457 views
Alliant Software Suite - IT Infrastructure Requirements
Userlevel 5
Badge

Introduction

Welcome to the Alliant Software Suite IT Infrastructure guide. Whether you are an existing client looking to stay up to date or a prospect considering our software as a prospective user, this guide will provide you with comprehensive insights into our IT infrastructure requirements. 

Our services include two main options:

Firstly, the Alliant Cloud, expertly managed by our team and ideal for clients prioritizing ease, convenience, reliability, and enhanced security. Secondly, an in-house hardware configuration tailored for businesses that value autonomy and wish to manage their infrastructure in-house. 

Here, you'll find detailed comparisons, key benefits, and all the necessary information to determine which option aligns best with your company's unique needs. Embrace a seamless and efficient experience with the Alliant Software Suite, and remember, we're here to support you every step of the way.

Document Last Updated: on February 1st, 2024

 

Infrastructure Overview

 

Alliant can be deployed in two ways:
 

ALLIANT CLOUD or IN-HOUSE SERVERS

 

 

Deployment Overview

A typical Alliant deployment utilizes the following components.

  • The Alliant Server:   This server hosts the SQL Server (database).
  • Web Server (IIS Server): This server hosts all web services including Alliant Online, Service Module Web Portal, and handheld communications. 
  • Integrated Plant Equipment:  Printers, Scanners, Sorting systems, Soil Counting systems, Email, Faxing.
  • Clients:  Workstations, laptops, and mobile devices. The components will depend on the deployment method you choose (cloud vs in-house).
  • Printer Requirements: Information on printers compatible with Alliant.
  • Handheld Device Requirements: Specifications for compatible Android phones and tablets.
  • Barcode/RFID Scanner Requirements: Advice on selecting suitable barcode and RFID scanners.
  • Scale Requirements: Specifications and interfaces for compatible scales.
  • Email Recommendation: Guidelines for integrating email services, such as Office 365, with Alliant.
  • Faxing as a Service Recommendations: Guidelines for selecting faxing as a service solution.

Alliant Cloud Deployment Option

 

Our in-house IT division will install, manage, and support your Alliant Software Suite environment. This is a cloud environment where the application is accessible through a web browser. Each Alliant Cloud environment will be hosted separately and private only to your company. For connectivity between the cloud environment and plant equipment, Alliant IT will set up a point-to-point VPN between the cloud and your network.

With our all-inclusive agreement, all back-end setups of Alliant’s optional modules are installed and ready for our team to turn on when you are ready. Alliant Cloud works with the standard peripherals in the industry (scanners, scales, label printers, etc.), including third-party interfaces that send/receive information through the database and APIs (soil counting interfaces, garment sorting interfaces, third-party Android apps, etc.). The solution is also scalable in terms of storage space, processor speed, and memory usage. As you grow, your environment can be adjusted to meet your needs and provide you with an efficient and responsive application.

The next section will review how we license Alliant Cloud, what Alliant IT provides, and what the customer requires.
 

Licensing

Alliant Cloud licenses the servers, and for users, we use a per-user licensing model managed by Alliant IT. Each user can access the application via a web browser on any device. This is a dynamic user licensing system where you can request Alliant IT to add or remove users as needed. User pricing will automatically be adjusted when a user is added or dropped, providing a cost-effective and adaptable solution. This is in addition to every client's standard software leasing agreement, based on a tiered concurrent user and number of routes basis.

Provided by Alliant IT

  • Database/Application Server
  • Web Server (IIS)
    • Installation of Internet Information Services.
      • Configuration and management of SSL certificates.
  • Virtual Firewall and VPN Configuration and Management
  • Alliant IT Support for the Cloud Environment
  • Security Management including Zero Trust Security
  • All maintenance and updates for both the software and the infrastructure.
  • Installation and maintenance for the entire Alliant Suite. Included in our suite are: 
    • Alliant Route Accounting
    • Alliant Centralized Console
    • Service Module
    • Service Web Portal
    • Stockroom
      • Chipped Linen (if applicable)
      • Mat Tracking (if  applicable)
    • Integrated Payment Software
    • Alliant Mobile for Android
    • Alliant Online 2.0 (customer portal)
    • Alliant API

Customer Requirements

  • Bandwidth 
    • Minimum bandwidth up/down – 35Mbps.
    • Backup internet is recommended.
  • Local VPN and Firewall 
    • A Site-to-Site VPN is required between the Alliant Cloud and the main site if you have equipment that needs to communicate with the Alliant database.
      • If you currently have a firewall, Alliant IT will review it and see if it is supported.
      • Alliant IT can also include a Firewall as a service for your main location, where a firewall will be provided as a service to connect the Cloud environment using a VPN to the main site.
  • Peripherals Requirements
    • For input devices that are not sending via keyboard-wedge or TCP/IP will need a converter to send via IP.

Application Requirements

The Alliant Route Accounting 2.0 application runs on a web browser in the Alliant Cloud solution. This considerably lowers the workstation requirements to run Alliant.

If you are still looking for a recommendation on workstation hardware, please review the Workstation Requirements section of the In-House Server Deployment section.

The following browsers are supported:

  • Microsoft Edge (latest version).
  • Safari (latest version, Mac only).
  • Chrome (latest version).
  • Firefox (latest version).

Other requirements:

  • Must have JavaScript enabled.
  • CPU with at least two cores.
  • 4GB of RAM minimum.
  • Enough storage space to support the applications and workloads.
  • For optimal user experience when accessing the Alliant on the browser, multiple monitors or a high-resolution display should be utilized.
  • Windows 10 Enterprise or Pro edition installed on each machine in the environment.
  • Microsoft Remote Desktop Protocol (RDP) client version 8.1 or higher.

Printer Requirements

Selecting the right printer is essential for ensuring compatibility and high-quality output when using Alliant Route Accounting 2.0. 

Our software is designed to work efficiently with specific types of printers, ensuring that all reports and labels are produced with clarity and precision. Below are the printer requirements necessary for optimal functioning:

  • Windows Compatibility: The printer must be compatible with the version of Windows in use on the workstation.
  • Report Printing: All reporting in Alliant is formatted for 8½ x 11 plain paper and is compatible with laser printers.
  • Dot Matrix Printers: Our software is incompatible with dot matrix printers and cannot be used.
  • ID Tape/Barcode Label Printing: For specialized printing like ID tape and barcode labels, several customers successfully use thermal transfer printers, including brands like Penn Emblem and Thermopatch.

Handheld Device Requirements

The following handheld device requirements are designed to guarantee compatibility, functionality, and the best possible performance of the Alliant Mobile for Android application. Below are the detailed specifications and considerations for selecting a suitable handheld device:

  • Android Version: Must be Android 6.0 or greater.
  • Device Type: Both phones (recommended) and tablets are acceptable.
  • Screen Size: The screen size should be no greater than 7 inches for optimal usability.
  • Wi-Fi Capability: Devices must have Wi-Fi capability for network connectivity.
  • Connectivity Requirements: A Windows server running Internet Information Services (IIS) is necessary for handheld connectivity.
  • Real-Time Data/Invoice Transmittal:
    • A data plan is required for real-time transmittal (recommended).
    • A public web address is needed for external access.

Barcode/RFID Scanner Requirements

Alliant Systems offers strong integration capabilities with barcode or RFID readers, essential for scanning garments or chipped items efficiently. The following list outlines the recommended hardware specifications to ensure connectivity and functionality with our systems:

  • Scanner Availability: Ensure that a scanner (either barcode, RFID, or both) is accessible at each scanning point for operational efficiency.
  • Barcode Reader Compatibility: The barcode reader must be capable of reading the Interleaved 2 of 5 font, a common format used for various tagging and labeling applications, and be configured as a keyboard wedge.
  • RFID Reader Configuration: A single-scan RFID reader must be configurable as a keyboard wedge. This setup allows for single-read scans to be directly input into Alliant, streamlining the data capture process.
  • Bulk Scanning Capability: For operations requiring bulk scanning, Alliant supports integration with TCP/IP bulk scan readers and bulk scan readers using the Mercury interface. This feature is crucial for handling large volumes of items quickly and accurately.

On-Route Scanning Integration

If there is a need for on-route scanning, ensure that the barcode or RFID scanner is compatible and can connect via Bluetooth to the current Alliant Mobile for Android device. We are integrated with the TSL 1128 scanner for UHF RFID Bluetooth scanners.

Before finalizing your scanner selection, it is recommended to consult with Alliant to verify that the chosen devices meet these requirements and are fully compatible with our application.

Scale Requirements

Alliant Systems integrates with scales when using the Bulk Delivery module, allowing weight to be transmitted directly into Alliant. The following are the two compatible interfaces:

Dynamic Data Exchange (DDE):

  • Purpose: DDE is a protocol for exchanging data between Windows applications. It is primarily used for real-time data communication.
  • Functionality in Bulk Scales: In bulk scales, DDE allows the scale to send weight data directly to other applications, such as inventory management systems or databases. This is typically done in real-time, ensuring that data is updated instantly.
  • Benefits: The main advantage of using DDE is its ability to facilitate automatic and immediate data transfer, which minimizes errors and enhances efficiency. It’s particularly useful in dynamic environments where real-time data integration is crucial.

Serial Interface:

  • Purpose: Serial interfaces, such as RS232 or RS485, are traditional methods for direct, wired communication between devices.
  • Functionality in Bulk Scales: A bulk scale can transmit data to a computer or processor with a serial interface. This is a point-to-point connection where data is sent sequentially over a single channel.
  • Benefits: Serial interfaces are known for their reliability and simplicity. They are widely supported and can be used in a variety of environments. However, they typically do not simultaneously support real-time data exchange with multiple applications, as DDE does.

Before finalizing your scale selection, it is recommended to consult with Alliant to verify that the chosen scale meets these requirements and is fully compatible with our application.

Note: A TCP/IP interface might be required for a scale to connect to the network in order to communicate with the database server in the cloud.

Email Recommendations

Our application offers several email functionalities, and it can send various reports and notifications to internal users and external clients. This includes Service Module notifications, Invoices, Statements, Credit Card receipts, and ACH receipts.

We acknowledge the evolving landscape of email authentication methods. Our application currently supports app passwords, an older authentication method used by platforms like Google Workspace. However, this method is being phased out as the industry moves towards more secure standards. Consequently, we recommend Office 365, integrated with our product, which employs Modern Authentication for enhanced security and efficiency.

Email-To-Fax Service Recommendations

For customers who want to fax out Alliant reports, such as Invoices and Statements, to your clients, you will need to use an email-to-fax service. This third-party service allows you to use your email address to send the fax. For example, instead of sending a fax, you would send an email to an email address like faxnumber@faxservice.com. The email would then be sent out of Alliant and faxed to the customer from the third-party service. 

Some common providers are HelloFax, eFax, and RingCentral. The only requirement is having an “Email-to-Fax” feature.

Network Cabling Requirements

The network infrastructure plays a crucial role in ensuring our software's smooth operation and optimal performance. Specific network cabling standards must be met to facilitate efficient and reliable data transmission. These standards are designed to support high-speed data transfer and reduce the likelihood of connectivity issues. Below are the detailed network cabling requirements necessary for the seamless operation of our software:

  • Ethernet: Gigabit Ethernet (GbE).
  • Popular Name: 1000BASE-T.
  • Speed: 1000 Mbps or the highest available.
  • Media:
    • Category 5e Unshielded Twisted Pair (UTP) OR.
    • Category 6 Unshielded Twisted Pair (UTP).
  • Maximum Segment Length: 100 Meters.

In-House Server Deployment Option

 

This illustrates an Alliant deployment with in-house servers.

Welcome to the In-House Hosting section of our hardware selection guide for the Alliant Software Suite. This guide is meticulously crafted for organizations prioritizing control over their IT environment, emphasizing security, autonomy, and cutting-edge technology.

In this comprehensive guide, we outline the key requirements to ensure a robust and efficient setup, including:

  • Server Requirements: Configurations for optimal server performance, perfectly supporting the Alliant Software Suite.
  • Backup Recommendations: Robust strategies for data protection, ensuring business continuity and resilience.
  • Support Connectivity Requirements: Essential insights to maintain consistent, high-quality network performance.

This section provides detailed, actionable information to create an on-premises solution that is fully compatible with the Alliant Software Suite and customized to meet your organization's specific operational and security requirements.

 

Server Requirements

Our application architecture is designed to deliver optimal security and functionality when deployed on an in-house server, using a dual Windows Server setup, and is compatible with virtualization.

  • Database/Application Server:
    • Purpose: This server hosts the database and applications for internal use only.
      • Alliant Route Accounting 2.0
      • Centralized Console
    • Characteristics: It is configured to be accessible solely within the organization's internal network. This server handles all the backend processes, data storage, and internal-facing applications.
    • Security Considerations: As this server will contain sensitive internal data, standard security protocols within your internal network should be strictly followed.
       
  • Web Server (IIS): 
    • Purpose: This server will host the Alliant Online portal, manage handheld communications, and the Service Module web portal.

Database/Application Server Requirements

9 users or less

  • Server Hardware:
    • Processor: Pentium Xeon Processor (8 cores or more recommended).
    • Memory: 64GB RAM.
    • Storage: 1 TB of available SSD SAS or SSD SATA Hard Drive space (A fault-tolerant RAID 5 or disk mirror setup is recommended).
    • Network Card1 GB or higher recommended.
    • UPS Power Supply.
       
  • Data Recommendations:
    • A stand-alone SQL Server is recommended along with these server partitions:
      1. Operating System.
      2. SQL Database (including application files).
      3. SQL Log.
      4. SQL Backups.
    • A separate terminal server (RDS) is recommended for depot connectivity.
       
  • Software Requirements:
    • Operating System: Windows Server 2022 (Recommended) OR Windows Server 2019 Standard. 
      • Note: Windows Server 2016 is still supported for existing deployments but is not recommended for new installations.
    • SQL Version: SQL Server 2022 Standard (Recommended), SQL Server 2019 Standard OR SQL Server 2016 is still supported for existing deployments, but it is not recommended for new installations.
    • Nested Virtualization: Must be enabled if using a Virtual Machine (VM).

10 users or more

  • Hardware Requirements for :
    • Processor: Pentium Xeon Processor (8 cores or more recommended).
    • Memory: 128 GB RAM.
    • Storage: 1 TB of available SSD SAS or SSD SATA Hard Drive space (A fault-tolerant RAID 5 or disk mirroring setup is recommended).
    • Network Card: 1 GB or higher recommended.
    • UPS Power Supply.
       
  • Data Recommendations:
    • A stand-alone SQL Server is recommended along with these server partitions:
      1. Operating System.
      2. SQL Database (including application files).
      3. SQL Log.
      4. SQL Backups.
    • A separate terminal server is recommended for depot connectivity.
       
  • Software Requirements:
    • Operating System: Windows Server 2019 Standard OR Windows Server 2022 (Recommended).
    • SQL Version: SQL Server 2019 Standard OR SQL Server 2022 Standard (Recommended).
    • Nested Virtualization: Must be enabled if using a Virtual Machine (VM).

Web (IIS) Server Requirements

  • External Server in DMZ (Demilitarized Zone):
    • Purpose: The second server is dedicated to external-facing applications.
      • Alliant Mobile for Android
      • Alliant Online 2.0
      • Alliant Background Worker
      • Service Web App
      • Alliant API
    • Characteristics: It is set up in a DMZ, a separate, secured network segment outside the internal network but still under the organization's control. This server interacts with external users, providing them access to necessary applications.
    • Security Requirements: 
      • SSL (Secure Sockets Layer): It is strongly recommended to use SSL for all communications to and from this server. A HTTPS certificate is required. SSL helps encrypt the data in transit, thus enhancing the security of your external connections.
      • Required Security Measures: Implement robust firewall rules, intrusion detection systems, web application firewall (WAF), and regular security audits to safeguard this server, as it is more exposed to external threats.
  • Hardware Requirements for IIS Server
    • Processor: Pentium Xeon Processor (8 cores or more recommended).
    • Memory: 16 GB RAM.
    • Storage: 100 GB of available SATA or SAS/SATA Hard Drive space (A fault-tolerant RAID 5 or disk mirroring setup is highly recommended).
    • Network card: 1 GB.
    • UPS Power Supply.

 

Microsoft SQL Licensing Options

Microsoft SQL Server offers two primary licensing options designed to cater to different deployment scenarios and usage requirements.

  1. Core-Based Licensing: This option is ideal for high-density or virtualized environments. Licenses are required for each core in the server, offering a scalable and straightforward licensing approach. Alliant Systems recommends this model to maintain compliance effortlessly, as it eliminates the need to track the number of users.
     
  2. Server + CAL (Client Access License) Based Licensing: Preferred for scenarios with a well-defined number of users or devices, this model requires a separate license for the server and each user or device accessing it. It can be more cost-effective for smaller or more predictable environments. However, Alliant Systems does not recommend this option, as you will need to license every device that accesses our application:
    • Every Workstation that accesses Alliant Route Accounting 2.0.
    • Every Handheld/Tablet Device that runs Alliant Mobile for Android.
    • Every device that accesses the Service Module Web App.
    • Every one of your customers that uses the Alliant Online Customer Portal.

Below are links to Microsoft’s licensing datasheet and guide for SQL 2019 and SQL 2022.

  • Microsoft SQL Server 2022 Standard
    • Microsoft Licensing Datasheet: View
    • Microsoft Licensing Guide: View
  • Microsoft SQL Server 2019 Standard
    • Microsoft Licensing Datasheet: View
    • Microsoft Licensing Guide: View

Backup Plan Recommendations

It is imperative for customers to regularly back up the Alliant database. While Alliant can restore application files and reinstall the application along with necessary Windows features, the Alliant database is an exception and falls under the customer's responsibility. In the event of a disaster, any data stored in the Alliant database will be irretrievably lost without a customer-provided backup. Therefore, it is crucial for customers to implement a consistent backup strategy to safeguard their data against such losses. The following are some best practices when exploring a backup plan:

  • Backup storage space should be at least 1.5 times the size of the image backup.
    • It should have enough space to store 3 to 4 separate backups.
  • Backups should be stored daily in three places:
    • SQL backups located on the SQL Server.
    • Physical image backup located offsite.
    • Cloud image backup.
  • Monthly test restores of the backup should take place to ensure the integrity of the backups.

Note: We recommend imaged-based backups and not only data. An image-based backup will take a snapshot of the entire server including the operating system.

Support Connectivity Requirements

For efficient and timely support, Alliant Systems requires a direct connection to your SQL and Web servers. We aim to ensure that our support process is as seamless and secure as possible, aligning with your network configuration and security protocols. This connectivity is essential for tasks like sending program updates or addressing support issues. We offer several methods to establish this connection:

  • ConnectWise – Connect/ScreenConnect (Preferred): This is our preferred method due to its reliability and ease of use. Alliant Systems provides and hosts this service at no additional cost. The client tools will be installed on your system with our team's assistance.
  • Terminal Services/Remote Desktop: Suitable for direct, controlled access.
  • VPN: Offers a secure connection, especially for continuous or frequent support needs.
  • Other Methods: We understand the need for flexibility and are open to discussing alternative methods that better suit your infrastructure. Please consult with Alliant for additional options.

Workstation Requirements

Alliant Route Accounting 2.0 is designed for versatility and compatibility with a variety of workstation types, including desktops, laptops, all-in-ones, and hybrids like the Windows Surface Pro. However, it's important to note that this software is not compatible with operating systems designed for tablet devices, such as iOS or Android, and it does not work on Apple products. The detailed specifications below ensure optimal performance and compatibility with the software.

  • Hardware Requirements
    • Processor: Intel Core i5.
    • Memory: 8GB RAM.
    • Storage: 40GB Hard Drive (An SSD recommended for better performance).
    • Network Card: 1GB (Essential for handling data-intensive tasks).
    • Surge Suppressor: To protect the hardware from electrical surges.
       
  • Software and Display Requirements
    • Operating System:
      • Microsoft Windows 10 Professional.
      • Microsoft Windows 11 Professional (Recommended).
    • Monitor: Minimum resolution of 1024x768.
    • Display Scaling: Setting the DPI (dots per inch) above 100% may cause screens/options to be cut off. Keeping the scaling at 100% is advisable to ensure all interface elements are fully visible.

Printer Requirements

Selecting the right printer is essential for ensuring compatibility and high-quality output when using Alliant Route Accounting 2.0. Our software is designed to work efficiently with specific types of printers, ensuring that all reports and labels are produced with clarity and precision. Below are the printer requirements necessary for optimal functioning:

  • Windows Compatibility: The printer must be compatible with the version of Windows in use on the workstation.
  • Report Printing: All reporting in Alliant is formatted for 8½ x 11 plain paper and is compatible with laser printers.
  • Dot Matrix Printers: Our software is incompatible with dot matrix printers and cannot be used.
  • ID Tape/Barcode Label Printing: For specialized printing like ID tape and barcode labels, several customers successfully use thermal transfer printers, including brands like Penn Emblem and Thermopatch.

Handheld Device Requirements

The following handheld device requirements are designed to guarantee compatibility, functionality, and the best possible performance of the Alliant Mobile for Android application. Below are the detailed specifications and considerations for selecting a suitable handheld device:

  • Android Version: Must be Android 6.0 or greater.
  • Device Type: Both phones (recommended) and tablets are acceptable.
  • Screen Size: The screen size should be no greater than 7 inches for optimal usability.
  • Wi-Fi Capability: Devices must have Wi-Fi capability for network connectivity.
  • Connectivity Requirements: A Windows server running Internet Information Services (IIS) is necessary for handheld connectivity.
  • Real-Time Data/Invoice Transmittal:
    • A data plan is required for real-time transmittal (recommended).
    • A public web address is needed for external access.

Barcode/RFID Scanner Requirements

Alliant Systems offers strong integration capabilities with barcode or RFID readers, essential for efficiently scanning garments or chipped items. The following list outlines the recommended hardware specifications to ensure connectivity and functionality with our systems:

  • Scanner Availability: Ensure that a scanner (either barcode, RFID, or both) is accessible at each scanning point for operational efficiency.
  • Barcode Reader Compatibility: The barcode reader must be capable of reading the Interleaved 2 of 5 font, a common format used for various tagging and labeling applications.
  • RFID Reader Configuration: A single-scan RFID reader must be configurable as a keyboard wedge. This setup allows single-read scans directly input into Alliant, streamlining the data capture process.
  • Bulk Scanning Capability: For operations requiring bulk scanning, Alliant supports integration with TCP/IP bulk scan readers and bulk scan readers using the Mercury interface. This feature is crucial for handling large volumes of items quickly and accurately.
  • On-Route Scanning Integration: If there's a need for on-route scanning, ensure that the barcode or RFID scanner is compatible and can connect via Bluetooth to the current Alliant Mobile for Android devices. We are integrated with the TSL 1128 scanner for UHF RFID Bluetooth scanners.

Before finalizing your scanner selection, it is recommended to consult with Alliant to verify that the chosen devices meet these requirements and are fully compatible with our application.

On-Route Scanning Integration

If there is a need for on-route scanning, ensure that the barcode or RFID scanner is compatible and can connect via Bluetooth to the current Alliant Mobile for Android device. We are integrated with the TSL 1128 scanner for UHF RFID Bluetooth scanners.

Before finalizing your scanner selection, it is recommended to consult with Alliant to verify that the chosen devices meet these requirements and are fully compatible with our application.

Scale Requirements

Alliant Systems integrates with scales when using the bulk delivery module, allowing weight to be transmitted directly into Alliant. The following are the two compatible interfaces:

Dynamic Data Exchange (DDE):

  • Purpose: DDE is a protocol for exchanging data between Windows applications. It is primarily used for real-time data communication.
  • Functionality in Bulk Scales: In bulk scales, DDE allows the scale to send weight data directly to other applications, such as inventory management systems or databases. This is typically done in real-time, ensuring that data is updated instantly.
  • Benefits: The main advantage of using DDE is its ability to facilitate automatic and immediate data transfer, which minimizes errors and enhances efficiency. It’s particularly useful in dynamic environments where real-time data integration is crucial.

Serial Interface:

  • Purpose: Serial interfaces, such as RS232 or RS485, are traditional methods for direct, wired communication between devices.
  • Functionality in Bulk Scales: A bulk scale can transmit data to a computer or processor with a serial interface. This is a point-to-point connection where data is sent sequentially over a single channel.
  • Benefits: Serial interfaces are known for their reliability and simplicity. They are widely supported and can be used in a variety of environments. However, they typically do not simultaneously support real-time data exchange with multiple applications, as DDE does.

Before finalizing your scale selection, it is recommended to consult with Alliant to verify that the chosen scale meets these requirements and is fully compatible with our application.

Email Recommendations

Our application offers several email functionalities, and it is capable of sending a variety of reports and notifications to internal users and external clients. This includes Service Module notifications, Invoices, Statements, Credit Card receipts, and ACH receipts.

We acknowledge the evolving landscape of email authentication methods. Our application currently supports app passwords, an older authentication method used by platforms like Google Workspace. However, this method is being phased out as the industry moves towards more secure standards. Consequently, we recommend Office 365, integrated with our product, which employs Modern Authentication for enhanced security and efficiency.

Email-To-Fax Service Recommendations

For customers who want to fax out Alliant reports, such as Invoices and Statements, to your clients, you will need to use an email-to-fax service. This third-party service allows you to use your email address to send the fax. For example, instead of sending a fax, you would send an email to an email address like faxnumber@faxservice.com. The email would then be sent out of Alliant and faxed to the customer from the third-party service. 

Some common providers are HelloFax, eFax, and RingCentral. The only requirement is having an “Email-to-Fax” feature.

Network Cabling Requirements

The network infrastructure plays a crucial role in ensuring our software's smooth operation and optimal performance. Specific network cabling standards must be met to facilitate efficient and reliable data transmission. These standards are designed to support high-speed data transfer and reduce the likelihood of connectivity issues. Below are the detailed network cabling requirements necessary for the seamless operation of our software:

  • Ethernet: Gigabit Ethernet (GbE).
  • Popular Name: 1000BASE-T.
  • Speed: 1000 Mbps or the highest available.
  • Media:
    • Category 5e Unshielded Twisted Pair (UTP) OR.
    • Category 6 Unshielded Twisted Pair (UTP).
  • Maximum Segment Length: 100 Meters.

Conclusion

This guide aims to provide comprehensive insights into the hardware requirements for Alliant Systems. While we strive to cover all critical aspects, we understand that individual needs and scenarios may vary. Should you have any questions or require further assistance tailoring these requirements to your specific context, please do not hesitate to contact our support team at support@alliantsystems.com.


This topic has been closed for comments