March 2026

These are the March 2026 release notes of NDD Orbix.

See a summary of all updates and click on the links to navigate each one.

March 27, 2026

NDD Orbix portal:

NEW FEATURES

March 18, 2026

NDD Orbix portal:

FIXES

March 11, 2026

DCA and Cloud Connector agent (Windows version 1.2.15):

NEW FEATURES

IMPROVEMENTS

FIXES

APPROVALS

March 09, 2026

ASM portal:

NEW FEATURES

March 04, 2026

Integration APIs:

NEW FEATURES


March 27, 2026

New features

Supply stock management by delivery location

To allow structured and traceable control of supplies stored at each physical location within the operation, NDD Orbix now integrates physical stock control into the replenishment process, increasing operational accuracy and data reliability.

The main benefits of this feature are:

  • Stock control by physical location, reflecting the reality of the operation

  • Separation between replenishment stock (reserved) and safety stock

  • Individual traceability of items (origin, demand type, and receipt date)

  • Automatic write-off of items based on reliable exchanges (not applicable to thermal printers)

  • Reduction of discrepancies between physical inventory and the system

  • Greater control over waste and misuse of supplies

  • Support for decision-making based on actual balance and demand planning

Each delivery location represents a physical storage point linked to a customer (and optionally to a site). It controls linked devices, registered products, available balance, quantity to be received, and safety rules.

In addition, safety rules can be configured to ensure preventive stock levels and prevent operational disruptions.

Information

For providers who already have data on the portal prior to contracting this feature, upon activation, a delivery location will be automatically created for each existing site, and items will be automatically quantified based on the demand planning already recorded in the system.

This ensures that the feature is activated in a structured manner, without loss of information and with operational continuity.

This feature consolidates the complete cycle of physical and logical control of supplies, increasing the efficiency of supply management.

Information

For more information, access Manage printer supply stock (for printers) and Manage thermal printer supply stock (for thermal printers).


Scheduled replenishment of supplies

Scheduled replenishment improves the calculation of supply requirements by taking into account not only the estimated consumption of printers, but also the actual available stock and the safety stock rules configured for each delivery location.

As a result, the forecast becomes more accurate and aligned with the reality of the operation, reducing the risk of supply shortages or surpluses.

When generating the scheduled replenishment, the system calculates the requirement based on consumption history, average production, supply efficiency, available stock, items already ordered, and safety stock rules.

After generation, you can review the data, run simulations, and adjust quantities before finalizing the process. The system then automatically generates the necessary purchase orders, already factoring in the validated final requirement.

This advancement reinforces NDD Orbix’s commitment to delivering greater efficiency, control, and profitability for your operation by integrating forecasting, stock, and order generation into a single, streamlined workflow.

Information

For more information, access Generate scheduled replenishment for printer supplies (for printers) and Generate scheduled replenishment for thermal printer supplies (for thermal printers).


March 18, 2026

Fixes

Failure to generate EcoPrint Comparative report

When generating the predefined EcoPrint Comparative report, a timeout error occurred due to the large volume of data processed in some database tables. Queries exceeded the time limit because they had to scan through a very large number of records, resulting in failures during report generation.

To fix this, we created new indexes in the columns of the tables involved, allowing the database to optimize the search and sorting of records. As a result, queries now use index seek instead of table scan, significantly reducing execution time and eliminating timeout errors.

In addition, we improved data search methods and consolidated information to reduce volume, optimizing database space.


March 11, 2026

New features

Creation of the orbix.settings.json file (Agent: DCA and Cloud Connector)

DCA and Cloud Connector now generates a new configuration file called orbix.settings.json, created at the root of the following folders:

  • Installation folder (default: C:\Program Files (x86)\NDD TECH\DCA and Cloud Connector).

  • Work folder (default: C:\NDD TECH\Workfolder).

This file centralizes configuration information shared between agent services.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15, as instructed at Update the agent or gateway on portal.


Service recovery settings (Agent: DCA and Cloud Connector)

You can now access recovery options in the DCA and Cloud Connector service properties in Windows.

With this configuration, the Service Control Manager (SCM) can automatically restart the service in case of a failure.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15, as instructed at Update the agent or gateway on portal.


Improvements

Automatic update of configurations before printer discovery and monitoring (Service: NDD - Printer Monitor)

To ensure that the printer discovery and monitoring process always uses the latest configurations defined in the portal, we have adjusted the service flow to automatically download the configurations before starting these operations.

With this improvement, discovery and monitoring will always use the most updated configurations, reducing potential inconsistencies when changes are made in the portal.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Adjustment to serial number capture on Brother models (Service: NDD - Printer Monitor)

To ensure correct identification of the serial number on some Brother printers, we have added an alternative collection method when this information is not returned by the default method used by the system.

With this adjustment, when the serial number is not available on the first attempt, the system will perform a new query through an alternative path to try to obtain the information.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Fallback for capturing serial numbers on Ricoh equipment (Service: NDD - Printer Monitor USB)

To ensure unique identification of Ricoh equipment when the device returns a generic serial number, we have implemented a fallback mechanism in the capture process.

In such cases (for example, when the serial number starts with “FIX”), the system will use the Windows ContainerID value as the equipment identifier, ensuring that a unique value is used for identification.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor USB (Windows) service to version 1.1.19, as instructed at Update the agent or gateway on portal.


Fixes

NDD - Printer Monitor service took control of DCA and Cloud Connector files (Agent: DCA and Cloud Connector)

In some scenarios, the NDD - Printer Monitor service took control of files in the DCA and Cloud Connector Workfolder, which could cause failures and interrupt the correct monitoring of services.

To prevent this behavior, we have implemented a validation at the beginning of the NDD - Printer Monitor service execution. It will read the settings from the orbix.settings.json file, which centralizes important information.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15, as instructed at Update the agent or gateway on portal.


Local logs displaying service namespace instead of content (Agent: DCA and Cloud Connector)

In local logs (...\Workfolder\dca-local-logs-<data>.log), when the Serilog:MinimumLevel:Default configuration was set to Verbose, the log responsible for recording the content read from the appsettings.json file for each service only displayed the class namespace instead of the content.

💡

Example

2026-03-06 12:15:04.781 -03:00 [VRB] [ThrId: 7] Appsettings content for 'SoftwareMonitorService': nddSmart.DCA.Domain.Features.Services.Appsettings.SoftwareMonitor.SoftwareMonitorAppsettings..

To fix this, we adjusted the log structure so that the content is displayed correctly.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15, as instructed at Update the agent or gateway on portal.


.SPL file with a name different from the default (Service: NDD - Supply Watch)

On some machines, when printing to shared print queues, Windows wrote the .SPL file name differently from the default. However, the NDD - Queues Monitor service continued to report the original name. This inconsistency prevented the NDD - Supply Watch service from locating the file, preventing the application of saving rules.

To fix this, we implemented a registry configuration in Windows that disables this non-default name writing behavior.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Supply Watch (Windows) service to version 1.2.4, as instructed at Update the agent or gateway on portal.


Alerts remained open on the portal even after resolution on the equipment (Service: NDD - Printer Monitor)

In some cases, alerts continued to be displayed with open status on the NDD Orbix portal, even after the problem had already been resolved directly on the equipment. This behavior could occur in alerts that remained active for longer periods before being resolved.

To fix this, we adjusted the validation related to the time of occurrence of alerts, ensuring that events that have already been resolved are processed correctly and have their status updated on the portal.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Incorrect manufacturer identification in network equipment (Service: NDD - Printer Monitor)

During the manufacturer identification process when capturing device information, some HP network switches were being incorrectly identified as Alaris equipment.

To fix this, we adjusted the Alaris manufacturer capture and identification flow, ensuring that devices are classified correctly.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Error that prevented the capture of supply content on Brother MFC-L612DW equipment (Service: NDD - Printer Monitor)

During the capture of supplies on Brother MFC-L612DW equipment, a hexadecimal conversion error occurred that prevented the capture of content.

To fix this, we adjusted the encoding model used for this equipment.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Adjustment in the collection and presentation of meters on Epson equipment (Service: NDD - Printer Monitor)

During the collection and presentation of meters in the monitoring of Epson equipment, some values were not displayed correctly. In certain situations, when the equipment did not return the “total” value of the meter, the system performed an incorrect calculation of the mono meter, which could result in a negative value.

To fix this, we adjusted the way meters are validated and displayed. When the mono meter value returns negative, the system will make up to three new attempts to capture the equipment information. If the value remains negative in all attempts, the meter reading will be interrupted in that collection, preventing the display of incorrect data.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Adjustment to the capture and display of graphic counters on Lexmark CX431adw equipment (Service: NDD - Printer Monitor)

During the processing and addition of counters collected from monitoring Lexmark CX431adw equipment, graphic counters were not being displayed in the system, even when the printer returned this information correctly.

To fix this, we made an adjustment to the process of adding and recognizing these meters. With the correction, the specific meters returned by the equipment are now identified and displayed correctly, including:

  • Graphics Color

  • Business Color

  • Highlight Color

These meters were already available from the printer through the monitoring protocol, but were not being correctly incorporated into the presentation of data in the system. After the adjustment, the information is now displayed normally whenever it is returned by the equipment.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Adjustment to serial number collection on Xerox equipment (Service: NDD - Printer Monitor)

During the monitoring stage of some Xerox equipment models, the serial number was not being displayed in the system after the device information was collected.

To fix this, we made an adjustment to the serial number capture process. When the system does not identify the value on the first attempt (empty return), a new collection attempt will be made using an alternative path to query the equipment, increasing the reliability of identifying this information.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Adjustment to the monitoring filter for alerts (Service: NDD - Printer Monitor)

When the monitoring filter was configured to allow or block the monitoring of certain equipment, this rule was only applied to the collection of counters and supplies, and was not considered during the monitoring of alerts.

To fix this, we adjusted the monitoring filter so that alerts also comply with the configured rules, as is already the case with meter and supply collection.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


Adjustment to the capture of supplies and meters on HP Flow MFP E52645 equipment (Service: NDD - Printer Monitor USB)

During the process of collecting information from HP Flow MFP E52645 equipment, when a supply or meter was not returned correctly by the device, the capture process was interrupted, preventing the collection of other information.

To fix this, we adjusted the collection process so that if any supplies or meters are not returned correctly, the capture of other items continues normally. In addition, when the description of supplies is not returned by the equipment, a corresponding generic description will be automatically assigned. For the status field, when there is no return from the equipment, the value “Unknown” will be assigned.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor USB (Windows) service to version 1.1.19, as instructed at Update the agent or gateway on portal.


Approvals

Approved USB printers (Service: NDD - Printer Monitor USB)

 

Meters capture

Supplies capture

Ricoh

AFICIO MP C300

-

Incompatible printers:

  • Brother ADS-4700W

  • Brother ADS-2800W

  • Canon DR-S350NW

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor USB (Windows) service to version 1.1.19, as instructed at Update the agent or gateway on portal.


Adjusted network printers models (Service: NDD - Printer Monitor)

Brother

MFC-L6912DW

Epson

WF-C878R

Lexmark

CX431adw

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.15 and the NDD - Printer Monitor (Windows) service to version 1.1.30, as instructed at Update the agent or gateway on portal.


March 09, 2026

New features

Bulk import of meters via spreadsheet on the ASM portal

ASM now allows bulk import of equipment meters via spreadsheet in Excel or CSV formats.

With the new functionality, users can import values in a structured and secure manner, quickly updating meters for equipment not integrated with NDD Print MPS or NDD Orbix and reusing data from third-party software.

The update significantly reduces manual effort, increases the accuracy of recorded information, and makes the meter management process more efficient and reliable, especially for contracts with a large volume of devices.

Information

For more details on using the feature, access Registrar contadores dos equipamentos.


March 04, 2026

New features

ASM API available for integration

The API for the NDD Orbix ASM (Automated Services Management) module is now available, allowing direct integration with external systems for portal information management.

With this API, it is possible to create, query, update, and delete records related to the main ASM features. This new feature expands the possibilities for automation and integration, in addition to facilitating data synchronization between the ASM portal and other systems used in the operation, such as ERPs and management platforms.

Information

For more details on the available endpoints, visit the API reference.