Sky-Walker's building blocks


Software does not run on it's own. A secure and steady hardware architecture is the foundation of highly technological software applications. The figure below represents a typical hardware architecture used to support the Sky-Walker Open Integration platform.

Sky-Walker Hardware Architecture Ethernet Workstation Servers Subsystems Integration Video Wall Network



Sky-Walker can be configured in three ways:

1. Stand-alone system

Sky-Walker Stand-Alone Icon

This is the simplest configuration. Database server and workstation are installed on one PC, together with the Sky-Walker software and drivers. This configuration is used when a maximum of one client is required and only a few systems must be connected. The client also functions as a server.


2. Client-Server with one server

Sky-Walker Client-Server with one Server Principle

Server and workstation run on separate PCs. This configuration is used when more than one client is required.


3. Client-Server with multiple servers

Sky-Walker Configuration Client Multiple Servers Principle

This configuration is used when many systems must be connected. The required processes run on multiple servers to ensure that tasks and workloads are divided. The number of servers and clients are project specific and depend on the load of systems to be connected.



One of Sky-Walkers major strengths is the way it can display graphical screens and/or live video images across both local workstations and video walls, simultaneously or one by one.

The graphical user interface can be built across multiple monitors, linked through one graphical workstation. For example, it is possible to display the graphical screens on one monitor and the real-time alarm buffers or live video images (or other) on the video wall.




Each workstation runs the Sky-Walker Client software and, when required, the Configuration software. The operating system is the most recent version of Windows commercially available. The default language of the operating system is English, but this can be changed as Sky-Walker supports all languages. The workstation requirements are as follows:

Sky-Walker Workstation Requirements PSIM Building Management Workstation



All third party subsystems are connected to the Ethernet, either directly or via a converter to enable communication with the Sky-Walker system, via:

  • A communication port (RS232, RS485, Ethernet, Lon...)
  • A communication protocol: the protocol describes the system language.

All connected subsystems work autonomously. The programming of different subsystems is through software delivered by each individual supplier of that system. Interactions between different systems can be set, e.g. an alarm caused by intrusion automatically makes a specific camera record what’s happening. These triggers make it possible to set up advanced automated procedures.



The servers run the back-end software, necessary for the communication between external systems (fire panel, intrusion panel, camera’s, access control, HVAC, lighting systems, ...) and graphical workstations. Depending on the project, the server requirements can be adjusted as required. The following minimum server requirements are necessary:

Sky-Walker Server Requirements Building Management PSIM Platform Software



Different devices communicate with each other through the Ethernet using the TCP/IP protocol. All servers, workstations and subsystems on the network need to be uniquely identified by a fixed IP address. Communication between all modules is enabled through specific IP ports.

To run the Sky-Walker application, we use the existing customer IP network. There are of course, some minimum requirements that have to be met, depending on the size and nature of the project. Enough bandwidth has to be available to guarantee adequate functioning and sufficient performance during the transmission of data and video. Also the latency on the network is important to guarantee high performance for real-time data transmission.

LAN Cable Network Building Management PSIM