NEXCOM NCS network and communication platforms

Define network functions and equipment scope

Start with the platform’s task: routing, running a network application, virtualising functions, connecting industrial segments or operating at the edge. Attach a diagram showing external and internal links, and assign a clear role to each port used by the application.

Identify the software solution, installation method and existing configuration. For a new project, list required functions and the team responsible for setup. Separate the computer, interface modules and software scope in the specification so purchasing follows the actual system architecture.

Record the full model and hardware revision

Photograph the DNA, NSA, ISA or other platform label, serial number and configuration stickers. Suffix letters belong to the product designation. NSA 7150 and NSA 7150A have different product specifications; QAT for the A version is considered with that model’s documentation.

For a LAN module, provide its full code, revision and installed location. Mark ports and slots in a front panel photograph. Where several similar enclosures are deployed, label the materials by asset number to keep configurations and earlier purchasing documents associated with the right unit.

Map ports and network modules

For each link, record port type, purpose, network segment and transmission medium. Include cable and connected device designations, plus removable interface components used in the installation.

Select NC/ND/NI/NL/NQ/NV/NX LAN modules with the host appliance and slot generation. Provide the installed module label and photographs. Slot location links the item to the complete configuration, while the port list relates it to the existing network links.

Describe expected operation during power loss and system restart, including bypass functions used by the hardware and software configuration. Include existing settings with passwords removed.

Describe the workload for appliance selection

Provide a workload profile covering traffic types, connections, active network functions and application operation. Distinguish measured values from project targets.

A measurement should refer to the set of functions planned for the platform, allowing selection to follow the actual application and its operating conditions.

For a new project, describe normal operation and peak periods. List concurrent tasks and applications requiring separate computing resources.

If virtual machines are used, specify their roles and allocation of memory, storage and network connections, keeping the required resources attached to identifiable functions.

Compare options under the same software, active functions and interface layout. Processor specifications and port counts inform selection, while practical checks follow the network task.

Relate rackmount equipment to site infrastructure

For NSA, describe the rack, mounting position and cable space. Include front and rear access, installation accessories and connection direction.

NSA 7150 specifies 2U, two third-generation Intel Xeon Scalable processors and eight PCIe 4 LAN slots. Provide the module allocation, role of each port and computing configuration to be used with the chosen application. Keep all parameters tied to the exact model selected.

For power, record the installed supply code, connectors and rack source arrangement. The NSA 7150 specification lists 1+1 CRPS 1300 W power. Describe external sources and redundancy as parts of the actual equipment deployment, including which connections will remain when a component is replaced.

Specify memory, storage and expansion

Provide memory module labels, quantity and location. NSA 7150 lists twenty DDR4 ECC memory positions.

NSA 3190A specifies two 2.5-inch SSD/HDD bays and DDR4 memory. For drive enquiries, describe interface, installed location and disk purpose.

For a complete system, distinguish working data, boot environment and the required storage equipment so the supplied scope corresponds to the application’s configuration.

Relate expansion cards and separate TPM items to the exact platform documentation. Include component code, slot or connector and its role in the system.

For replacement, list settings to be transferred and identify the person responsible for restoring the software environment and checking the assembled configuration.

Prepare an ISA industrial network project

For ISA 120/122/140/141/142, attach the OT segment diagram and list equipment at network boundaries. Identify links needed by production, the path of control traffic and exchange with supervisory systems. Use that diagram to define the interface scope of the proposed hardware platform.

Describe the software environment, exchange rules and services using the current project configuration. List ordinary equipment operations that the system should preserve.

For replacement in an existing installation, provide port configuration and the sequence for restoring connections. Checks should cover data reading, command exchange and application interaction under site procedures.

Record the expected result of each action and the local team responsible for carrying out the commissioning work.

Build the communication platform configuration

For DFA, FTA and TCA, describe network architecture and computing function placement. A 5G, FWA or uCPE project starts with the service diagram, connections and software environment.

Identify the platform’s role, adjacent network equipment and the interfaces required to operate the proposed configuration.

Separate hardware, software components and integration work. For a complete system, list memory, storage, modules and mounting items.

For component supply, mark parts retained from the existing installation and describe how the final assembly will be checked against the specified communication functions and equipment scope.

Preserve the software environment during repair

Record operating system, application, driver and module versions. Keep available images and configurations under internal site procedures.

Include a materials list, boot arrangement and software dependencies in the enquiry so restoration tasks after hardware replacement have a defined scope alongside the purchasing list.

When comparing platform replacement with a LAN module purchase, identify settings, addresses and devices retained in service. List software installation and configuration transfer tasks separately.

Make responsibility for starting the software and checking network functions clear within the project’s defined supply and integration scope.

Agree the specification and incoming checks

Collect the full code, quantity, labels and photographs in one enquiry. Add network diagram, workload, software environment and interface table for a project.

Give different hardware revisions or deployments separate entries, retaining the source of each designation and its relationship to a specific installed position.

The agreed schedule makes the quotation and delivery comparable by label, completeness and intended installation position, and provides the receiving team with a practical reference.

At receipt, compare model, suffix, revision, connectors and component quantities. Keep packaging and product photographs with the order. Run the agreed working checks after installation.