nPower Technologies launches Scheduler 3.0.0 for multi-site AM production management

nPower Technologies, headquartered in Philadelphia, Pennsylvania, has released nPower Scheduler Release 3.0.0, an enterprise-grade update to its additive manufacturing production scheduling platform. The release transforms the software from a single-site tool into a multi-facility system, enabling users to run multiple schedulers within one installation accessible via a single web URL. Key features include independent scheduler configurations for each facility, flexible data integration from multiple ERPs or Excel files, native data maintenance screens for batching parameters, and role-based permissions configurable at the individual scheduler level. David Bennett, Chief Product Officer, stated the release provides the infrastructure that enterprise additive manufacturers need to scale operations across facilities.

This update addresses a persistent gap in the AM software stack: production scheduling that works across multiple sites with different equipment, materials, and data sources. As metal AM moves from pilot lines to repeatable factories — particularly in aerospace and medical production — the ability to manage distributed fleets from a single interface becomes critical. nPower competes in a thin but growing segment alongside solutions like AMFG, 3DPrinterOS, and Materialise Streamics, but its focus on deep scheduling logic rather than general MES or workflow management gives it a distinct position. The 3.0.0 release directly tackles the multi-site coordination problem that emerges when a contract manufacturer or OEM runs LPBF systems across several facilities, each with its own ERP and machine mix. By allowing separate schedulers for each site under one installation, nPower enables executive-level visibility without forcing a one-size-fits-all configuration.

For production managers running multi-site AM operations, this release removes a real friction point: the need to manually reconcile schedules across facilities or accept a single rigid scheduling engine that cannot accommodate local differences. The practical test will be how well the platform handles real-world data complexity — multiple ERPs with inconsistent field mappings, mixed machine fleets, and varying material qualifications. nPower must now execute on customer onboarding and integration support to turn this architectural upgrade into actual production throughput gains.