What is Netsis 3 Enterprise?
Logo Netsis 3 Enterprise is an enterprise resource planning (ERP) product from Logo Yazılım, installed on the company's own server, and it is the top package of the Netsis family. In Logo's new product structure, the Netsis group goes by the name N-Series under Logo Edge. Its web-based version is Logo Netsis Wings Enterprise; the interface is available in Turkish and English as standard.
According to Logo's product page, on the production side the MRP module handles forecasting, master production scheduling (MPS), and material requirements planning. The Advanced Production Planning module schedules jobs by operation and machine, and the Quality Control module draws statistical control charts. Machine Maintenance is offered as an add-on module.
On the finance and distribution side there is a branch, business-unit, and holding hierarchy, consolidation, bank loans, foreign trade, and request and quotation management. The Dynamic Warehouse module tracks stock by warehouse cell. e-Document processing runs through Logo e-Solutions.
Companies that use Netsis 3 Enterprise
Logo lists distribution and wholesale, automotive, aerospace, chemicals, food and beverage, and construction as the sectors for the product. From an infrastructure point of view, manufacturers whose factory and branches work from separate sites are the most relevant group.
In these companies the ERP is not used from a single building. Finance and purchasing at head office, production and quality at the factory, and a distribution warehouse in another city all write to the same database. Month-end consolidation and MRP runs put a heavy load on the server for short periods.
Take a manufacturer with head office in one city and a factory in another. A buyer waits for the MRP result while the planner at the factory opens work orders. Two teams writing to the same database at once means capacity planning has to count concurrent sessions as well.
Desktop client, database, and integration interfaces
Netsis 3 Enterprise is a Windows application with a desktop client and a client-server design. Logo does not state the database engine on its product page. For Netsis Wings, which shares the same foundation, Oracle and Microsoft SQL Server are supported. Setups on ARGE Cloud use Microsoft SQL Server, and the version is confirmed before setup.
Four tools accompany the application. NetOpenX is a development interface for pushing records into Netsis and reading data out without bypassing its business logic. According to Logo, Netsis Rest API runs as a Windows service and therefore needs no IIS installation. Dynamic Coding and NDI (Netsis Data Inspector) count among the customization tools.
On the identity side, the Central Identity Control System supports single sign-on with Active Directory. Permissions can be defined at column, form, and row level. These permissions are defined inside the application, while single sign-on involves the domain design on the server side.
MRP and MPS runs and consolidation put the most load on the database. How users run the client from a factory or a branch is a separate infrastructure decision.
Because the desktop client runs on Windows, it is possible to run it on a terminal server (RDS) at remote sites instead of on each user's own computer. That keeps the query traffic between the client and the database inside the data center; only the screen image crosses the link.
Netsis 3 Enterprise setup on ARGE Cloud
The SQL Server database and the terminal servers run in your dedicated VPC on ARGE Cloud. ARGE Cloud is our own infrastructure in a data center in Istanbul, and a highly available (HA) firewall is placed in front of the VPC. In sizing we look at the number of companies, how often MRP runs, and the scope of consolidation. The number and memory of the terminal servers are planned around the number of sessions open at the same time.
Because MRP run times depend on memory and disk latency, the database runs on Dell and Supermicro servers with Xeon Platinum processors, enterprise NVMe drives, and 25–200G NVIDIA Mellanox networking. Where a stop in planning also stops the factory, an optional SQL HA cluster can be added. A disaster recovery (DR) site in a second data center is optional as well; we confirm Netsis's cluster and DR behavior with Logo before setup.
Factories and branches connect to the VPC over IPsec, MPLS, or SD-WAN and run the Netsis client on a terminal server. If the factory link drops, users cannot enter records until the connection returns, so we recommend a second link for the factory. The link is part of monitoring. Users outside the office connect over SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA.
If the Rest API has to be published to the internet, its traffic passes through a web application firewall (WAF). The e-document path is defined on the firewall for the required addresses only. We monitor servers, disks, memory, the SQL Server service, links, and backup results, with hours and response scope set in the contract. Security information and event management (SIEM), security orchestration, automation, and response (SOAR), antivirus, and XDR/EDR run in the service zone next to the VPC.
SQL Server backups go to the isolated backup zone. We write down the restore order together with you and run a restore test, and the test frequency is stated in the contract. We describe the backup design separately under backup and disaster recovery.
MRP parameters, customizations made with Dynamic Coding, and e-document definitions stay with your Logo partner. Licensing, application setup, version upgrades, and functional support also remain with your partner or Logo; we build and operate the infrastructure.
What we confirm with Logo before setup
- Microsoft SQL Server versions supported for the release you use
- Windows Server and terminal server requirements
- Server-side requirements of Netsis Rest API and NetOpenX
- Active Directory requirements for the Central Identity Control System
- Infrastructure impact of a move to Logo Edge N-Series, if you plan one
Technologies: Windows Server · Microsoft SQL Server · Remote Desktop Services (RDS) · Active Directory · IPsec · ARGE ZTNA · ARGE Cloud
Frequently asked questions
Does Netsis Rest API need IIS on the server?
No. According to Logo, the Rest API runs as a Windows service and does not need IIS. If the service is published externally, it is placed behind a WAF.
What happens to production records if the factory loses its connection?
While the server is on ARGE Cloud, factory users connect to the terminal server over the link. New records cannot be entered while the link is down, and work resumes when the connection returns. A second link is the measure we recommend to shorten that window.
Which database does Netsis 3 Enterprise run on?
Logo's product page does not name an engine. For Netsis Wings, which uses the same foundation, Oracle and Microsoft SQL Server are supported; we build on Microsoft SQL Server and confirm the version before setup.
Can single sign-on with Active Directory be set up?
Yes. According to Logo, the Central Identity Control System supports this. We build the domain design and the terminal server sessions, and the setting inside the product is handled by your Logo partner.
For Logo Netsis 3 Enterprise, licensing, implementation, and functional support are obtained from the vendor or your partner. Logo Yazılım makes the software and owns its name and trademark; ARGE ICT is not an official partner or reseller of the vendor, and it provides and operates the infrastructure underneath the software.