...
Anchor |
---|
| _Toc133236298 |
---|
| _Toc133236298 |
---|
|
Anchor |
---|
| _Toc127198614 |
---|
| _Toc127198614 |
---|
|
Table of Contents
Anchor |
---|
| _Toc133236299 |
---|
| _Toc133236299 |
---|
|
SummaryThe Shoplogix Data Collector software is designed to work in conjunction with an Open Platform Communication (OPC) server (ex. Kepware’s KEPServerEX) on the same local system to extract data from manufacturing production equipment including but not limited to Programmable Logic Controllers (PLC), Robotic Logic Controllers (RLC), Process Automation Controllers (PAC), and other I/O devices and sensors on an existing ethernet-based machine network. Machine data is aggregated and encrypted by the Shoplogix Data Collector software before pushed up to Shoplogix’s Amazon Web Service (AWS) Elastic Compute Cloud (EC2) web host, where it is decrypted and parsed for analytics and metric calculations. Although rare, any configuration change to the interaction between the web host and the Shoplogix Data Collector software are pulled down. Metrics are then retrievable by accessing the Shoplogix web portal. As the Shoplogix interface is a hosted web-based system, per-station external network accessible web-browsing is required.
...
This document will outline the system minimum and recommended requirements of each software component and their respective services, network topology, and data flow diagrams. Furthermore, the document will outline best practices with regards to ancillary hardware.
Anchor |
---|
| _Toc127198616 |
---|
| _Toc127198616 |
---|
|
Anchor |
---|
| _Toc133236300 |
---|
| _Toc133236300 |
---|
|
Shoplogix System Requirements Anchor |
---|
| _Toc127198617 |
---|
| _Toc127198617 |
---|
|
Anchor |
---|
| _Toc133236301 |
---|
| _Toc133236301 |
---|
|
Local Collector SystemShoplogix requires a dedicated Windows-based system to operate. It is recommended that the system be either a virtual machine (VM) hosted on the customer’s server-farm, or that it be hosted on a physical desktop PC. All software components, required or optional, listed in this document must be installed on the same system. The system must also have network access, whether through virtual or physical Network Interface Cards (NICs), to the internal machine network where the production equipment to be monitored resides and to the external Internet network to push/pull data from the web portal hosted by Shoplogix.
...
*Note: be aware that any IT policy required software including but not limited to security and intrusion detection software may affect the system requirements listed above.
Anchor |
---|
| _Toc127198618 |
---|
| _Toc127198618 |
---|
|
Anchor |
---|
| _Toc133236302 |
---|
| _Toc133236302 |
---|
|
Operating Requirements Anchor |
---|
| _Toc127198619 |
---|
| _Toc127198619 |
---|
|
Anchor |
---|
| _Toc133236303 |
---|
| _Toc133236303 |
---|
|
Shoplogix Data CollectorCPU: | 4 Cores, 3.0 GHz |
Memory: | 4 GB |
Free Disk Space*: | 80 GB |
Operating System: | Windows 10, or 11 Windows Server 2019, or 2022 |
Features and Services: | .NET Framework 4.8 Windows Imaging Component and Windows Installer 3.1, or later |
...
*Note: growth rate storage scales against scan rate of tags, the number of associated machine connections, and associated job transactions; average growth rate for ten (10) machines with cycle count and sparse jobs is approximately 10 MB/day.
Anchor |
---|
| _Toc127198620 |
---|
| _Toc127198620 |
---|
|
Anchor |
---|
| _Toc133236304 |
---|
| _Toc133236304 |
---|
|
Kepware KEPServerEX V6 OPC ServerCPU: | 1.0 GHz |
Memory: | 1 GB |
Free Disk Space: | 530 MB |
Operating System: | Windows 8, 10, or 11 (Professional or Enterprise Editions) Windows Server 2012, 2016, 2019, or 2022 |
Features and Services: | .NET Framework 3.5 |
...
Note: The KEPServerEX installation and licensing are tethered to the host MAC address.
Anchor |
---|
| _Toc127198622 |
---|
| _Toc127198622 |
---|
|
Anchor |
---|
| _Toc133236305 |
---|
| _Toc133236305 |
---|
|
IT Security and Policies Anchor |
---|
| _Toc127198623 |
---|
| _Toc127198623 |
---|
|
Anchor |
---|
| _Toc133236306 |
---|
| _Toc133236306 |
---|
|
Port ExceptionsDepending on the IT policy, exceptions may need to be made to allow for applications to communicate inside/outside the network. Below is the list of port exceptions required by the Shoplogix system:
...
*Note: the list consists of common protocols used; only the ports defined by the technical discovery process and/or otherwise stated during implementation will be required.
Anchor |
---|
| _Toc127198624 |
---|
| _Toc127198624 |
---|
|
Anchor |
---|
| _Toc133236307 |
---|
| _Toc133236307 |
---|
|
Application ExceptionsDepending on the IT policy, exceptions may need to be made to allow for applications to communicate inside/outside the network. Below is the list of applications and their respective file paths:
...
Anchor |
---|
| _Toc133236342 |
---|
| _Toc133236342 |
---|
|
Table 5: Application Exceptions List
Anchor |
---|
| _Toc127198625 |
---|
| _Toc127198625 |
---|
|
Anchor |
---|
| _Toc133236308 |
---|
| _Toc133236308 |
---|
|
Directory WhitelistingDepending on the IT policy, exceptions may need to be made to allow for files and directories to be whitelisted from intrusion detect and/or malware software. Below is the list of file paths to be whitelisted:
...
Anchor |
---|
| _Toc133236343 |
---|
| _Toc133236343 |
---|
|
Table 6: Directory Whitelist
Anchor |
---|
| _Toc127198626 |
---|
| _Toc127198626 |
---|
|
Anchor |
---|
| _Toc133236309 |
---|
| _Toc133236309 |
---|
|
Service and User PermissionsDepending on the IT policy, exceptions may need to be made with regards to service accounts and/or user access levels. During implementation, a local administrator with network access (ex. Active Directory domain user with local administrator rights) will be required to properly install the necessary component software for the Shoplogix system.
...
Anchor |
---|
| _Toc133236344 |
---|
| _Toc133236344 |
---|
|
Table 7: Service and User Permission List
Anchor |
---|
| _Toc133236310 |
---|
| _Toc133236310 |
---|
|
System and Network ArchitectureThe Shoplogix system requires persisted communication between the data collector and the web host as well as between the data collector and the machine network. For the purposes of simplifying the explanation, the system is broken down into three (3) main components:
...
To mitigate the above problem, it is recommended that a robust communication channel be maintained between the data collection devices and the data collector PC. Therefore, wired communication networking is the preferred method of communication between data collection devices and the data collector PC while it is strongly recommended that wireless devices and communication not be used due to the potential for disconnects and attenuation in industrial and manufacturing environments. If opting to continue with wireless networking, your mileage may vary, and it will be up to the customer to diagnose any potential networking and data loss issues as the first step in any troubleshooting process.
Anchor |
---|
| _Toc127198627 |
---|
| _Toc127198627 |
---|
|
Anchor |
---|
| _Toc133236311 |
---|
| _Toc133236311 |
---|
|
Data Encryption and SecurityAll external communication between the Shoplogix system and the AWS EC2 web host is authenticated and encrypted using Transport Layer Security (TLS) 1.2. Machine data is aggregated by the Shoplogix Data Collector software before being pushed up to the AWS EC2 instance for processing [internal > external]. When required, system configuration changes and updates are pushed from the AWS EC2 instance down to the Shoplogix system [external > internal].
Anchor |
---|
| _Toc127198628 |
---|
| _Toc127198628 |
---|
|
Anchor |
---|
| _Toc133236312 |
---|
| _Toc133236312 |
---|
|
Time SynchronizationIt is strongly recommended that the system be synchronized with a corporate NTP server as transactions and message payloads are timestamped using the system’s clock. Asynchronous transactions and message payloads can cause data discrepancies, including but not limited to incorrect metric calculations and data loss.
Anchor |
---|
| _Toc127198629 |
---|
| _Toc127198629 |
---|
|
Anchor |
---|
| _Toc133236313 |
---|
| _Toc133236313 |
---|
|
System Maintenance and UpdatesIt is the customer’s responsibility that the system be routinely maintained as the expectation is to have reasonably high uptime for persistent data collection. As such, it is strongly recommended that the system be included in the maintenance plan managed by IT, whether local or corporate, including but not limited to scheduling Windows updates, scheduled system reboot cycles, and routine system maintenance.
Anchor |
---|
| _Toc127198630 |
---|
| _Toc127198630 |
---|
|
Anchor |
---|
| _Toc133236314 |
---|
| _Toc133236314 |
---|
|
Remote Access and Virtual Private Network (VPN)Remote access and VPN requirements are at the discretion of the customer’s IT policy; as far as Shoplogix is concerned, we are brand- and protocol-agnostic. However, there are different access levels of needs depending on the phase of the project, as outlined in the sections below.
Anchor |
---|
| _Toc127198631 |
---|
| _Toc127198631 |
---|
|
Anchor |
---|
| _Toc133236315 |
---|
| _Toc133236315 |
---|
|
Implementation PhaseShoplogix considers the implementation phase of the project as the deployment phase or hyper-care phase, where system access will be in high demand. During this phase of the project, Shoplogix will require access to the system to install, configure, and/or validate data with the intent to convert the system to be production ready (go-live). It is strongly recommended that during this phase of the project Shoplogix is given unfettered remote access to the system to prevent administrative hold-up of the project schedule.
Anchor |
---|
| _Toc127198632 |
---|
| _Toc127198632 |
---|
|
Anchor |
---|
| _Toc133236316 |
---|
| _Toc133236316 |
---|
|
Support PhaseDuring the support phase of the project, Shoplogix’s demand for system access is low. A typical situation would include Shoplogix requesting access to the system to troubleshoot an issue or incident as identified by the customer, or if Shoplogix determines there to be a bug that needs to be addressed and will pro-actively need system access to triage. Although it is strongly recommended that access established during the Implementation Phase be upheld, Shoplogix understands that it is unreasonable to have a permanent “back door” into a customer’s system from an external contractor and believe it to be reasonable to downgrade system access to “upon request as necessary”.
Anchor |
---|
| _Toc127198636 |
---|
| _Toc127198636 |
---|
|
Anchor |
---|
| _Toc133236317 |
---|
| _Toc133236317 |
---|
|
Web Portal Access Anchor |
---|
| _Toc127198637 |
---|
| _Toc127198637 |
---|
|
Anchor |
---|
| _Toc133236318 |
---|
| _Toc133236318 |
---|
|
BrowsersIt is expected that each user will have browser access to the web portal. Shoplogix has performed extensive testing with Google Chrome, Microsoft Edge, and other Chromium-based browsers within our development and sandbox-QA environments. Limited-to-no compatibility testing was performed against Mozilla Firefox and other browsers which may display visual artifacts if used. Microsoft Internet Explorer has been deprecated and phased out of support, resulting in it being considered unfit for use. As such, the recommended browser are Google Chrome, Microsoft Edge, or other Chromium-based browsers. Note: caching is required for metric display when accessing the Shoplogix Whiteboard and Analytics Portal, therefore we recommend that Smart TV’s built-in browsers not be used as they have significant memory limitations.
Anchor |
---|
| _Toc133236319 |
---|
| _Toc133236319 |
---|
|
IP Address/Uniform Resource Locator (URL) WhitelistingAlthough elastic addresses are assigned to each AWS EC2 instance, there are circumstances where the IP address will need to be changed. For this reason, it is strongly recommended that URL whitelisting be used as it is fixed to entitlement. The web portal for the data collection, entry, and visualization is not pre-allocated and will need to be configured during entitlement at the implementation phase; an assigned URL will need to be conveyed from the Shoplogix team during the implementation phase. The URL homepage syntax will reflect the following structure: https://<company>.shoplogix.com/*, where * denotes any subsequent page during navigation. Additionally, the operational analytics web portal will also need to be whitelisted, where the structure is not tied to any entitlement: https://portal.shoplogix.com/*; and the authentication for user login: https://identity.shoplogix.com/*.
Anchor |
---|
| _Toc127198639 |
---|
| _Toc127198639 |
---|
|
Anchor |
---|
| _Toc133236320 |
---|
| _Toc133236320 |
---|
|
User Access Anchor |
---|
| _Toc133236321 |
---|
| _Toc133236321 |
---|
|
Basic AuthenticationBasic authentication is used for local communication between services, API calls, and job upload templating. This authentication method is only used locally – users will not be able access to the local collector system or AWS EC2 instance with this authentication.
Anchor |
---|
| _Toc133236322 |
---|
| _Toc133236322 |
---|
|
OAuth AuthenticationDuring implementation, the customer will need to supply a list of names and associated email addresses for proper OAuth registration and authentication to access the AWS EC2 web portal (whiteboard and analytics portal) hosted by Shoplogix. Once registered, an email will be sent to the associated email addresses for password creation. Once done, users will be able to log into the web portal using their email/password. Note: if required, Shoplogix can issue a reset password creation email to users who require assistance.
Anchor |
---|
| _Toc133236323 |
---|
| _Toc133236323 |
---|
|
Active Directory AuthenticationAD authentication can be configured for web portal access, upon request.
Anchor |
---|
| _Toc127198647 |
---|
| _Toc127198647 |
---|
|
Anchor |
---|
| _Toc133236324 |
---|
| _Toc133236324 |
---|
|
Ancillary HardwareTwo of the three core functions of the Shoplogix system are qualified data entry and quantified data visualization. It requires operations to have the necessary tools to both manually enter qualifying reasons or comments and see the changes made for actionable information. This is accomplished by deploying a mix of workstations, monitors, TVs and peripheral equipment including barcode scanners. However, due to each customer’s facilities having their own environmental factors to consider, there is no single recommendation that will adhere to all variables present. Below is a general list of considerations:
...
The following sections are based on options that Shoplogix has historically seen deployed at customer facilities and should not be considered as either exhaustive or prohibitive of alternate solutions, including reallocation of existing resources for this project. It is the sole responsibility of the customer to source, requisition, purchase (or repurpose), and maintain hardware while ensuring conformance to their facility’s environmental, operational, and IT policies and needs.
Anchor |
---|
| _Toc133236325 |
---|
| _Toc133236325 |
---|
|
Operator Data Entry Anchor |
---|
| _Toc133236326 |
---|
| _Toc133236326 |
---|
|
WorkstationsWorkstations are typically used in fixed areas of operations, where there is little necessary movement from the operator to get to and from the production area. As far as Shoplogix is concerned, workstations can either be thin or fat clients at the discretion of the customer, so long as the workstation can perform data entry, data visualization, or both functions as required. Keep in mind that the Shoplogix web portal requires internet access, through a URL by whitelisting or not, so the system specifications are based on a web browser’s minimal requirements while the environmental factors to consider as substantial. Depending on whether the purpose is for data entry or visualization, some items on the list below of historically used workstations by our customer-base may be more relevant than others – the list is neither exhaustive nor prohibitive:
...
Note: workstations require an associated monitor for display, network access, and peripheral equipment including keyboard and mouse if not touchscreen capable.
Anchor |
---|
| _Toc133236327 |
---|
| _Toc133236327 |
---|
|
TabletsTablets are a great tool for operators to interact with the Shoplogix system for data entry and data visualization while being able to freely remove around their production area. In general, so long as the tablet can run a web browser and can access the Shoplogix web portal, whitelisted or not, it is sufficient. Below is a list of historically used hardware by our customer-base – the list is neither exhaustive nor prohibitive:
...
Anchor |
---|
| _Toc133236348 |
---|
| _Toc133236348 |
---|
|
Table 10: Tablets
Anchor |
---|
| _Toc133236328 |
---|
| _Toc133236328 |
---|
|
Facilities Data Visualization Anchor |
---|
| _Toc127198651 |
---|
| _Toc127198651 |
---|
|
Anchor |
---|
| _Toc133236329 |
---|
| _Toc133236329 |
---|
|
TelevisionsThere are dozens of brands and hundreds of models of deployed televisions across our customer-base with the common restriction being not using Smart TV in-built web browsers due to their limited CPU, memory, and security updates that causes poor performance when accessing the Shoplogix web portal for extended periods of time. Environmental, operational, and IT policies and needs will dictate which TVs should be used.
Anchor |
---|
| _Toc127198648 |
---|
| _Toc127198648 |
---|
|
Anchor |
---|
| _Toc133236330 |
---|
| _Toc133236330 |
---|
|
Barcode ScannersSome processes can be augmented with a manual barcode scanner to work inline with manual entry on a workstation for the Shoplogix system. Shoplogix leverages the wedge-scanner functionality of 1D/2D barcode scanners to inject delimited string values. Below is a list of historically used scanners by our customer-base – the list is neither exhaustive nor prohibitive:
...
Note 2: IP scanners have not been tested for production.
Anchor |
---|
| _Toc127198652 |
---|
| _Toc127198652 |
---|
|
Anchor |
---|
| _Toc133236331 |
---|
| _Toc133236331 |
---|
|
Ancillary SoftwareShoplogix uses various software tools during the implementation and support phases of projects to assist with deployment and troubleshooting respectively. Below is a list of applications that historically have been used during a project life cycle – although neither exhaustive nor prohibitive, the listed software are grouped into assumed risk-levels as related to vendor trusted status or to atypical data payload and/or network traffic access:
...
Anchor |
---|
| _Toc133236332 |
---|
| _Toc133236332 |
---|
|
iNTERFACEWARE Iguana
iNTERFACEWARE’s Iguana is an optional add-on that requires additional subscription and services per quotation and purchase order independent of the core implementation services and subscription costs due to the application engineering time required per use-case. The Shoplogix Data Collector software can leverage Iguana solution to Extract, Transform, and Load (ETL) parsed ERP job standards and other non-OPC-centric data. Iguana has two standard deployment topologies, depending on use-case: cloud-hosted solution and on-premise solution.
Anchor |
---|
| _Toc133236333 |
---|
| _Toc133236333 |
---|
|
Operating RequirementsCPU: | Intel-i3 |
Memory: | 4 GB |
Free Disk Space: | Varies depending on message load |
Operating System: | Windows 8, 10, or 11 Windows Server 2016, 2019, or 2022 Mac OS X Linux |
Anchor |
---|
| _Toc133236351 |
---|
| _Toc133236351 |
---|
|
Table 13:
Operating Requirements for Iguana Anchor |
---|
| _Toc133236334 |
---|
| _Toc133236334 |
---|
|
Port ExceptionsPort Number | Description |
iNTERFACEWARE Iguana – default [user configurable] – internal communication |
6543 | Dashboard |
Anchor |
---|
| _Toc133236352 |
---|
| _Toc133236352 |
---|
|
Table 14: Port Exceptions for Iguana
Anchor |
---|
| _Toc133236335 |
---|
| _Toc133236335 |
---|
|
Application ExceptionsApplication | File Path – default [user configurable] |
iNTERFACEWARE Iguana – external/internal communication |
Iguana Runtime | %ROOT%\Program Files\iNTERFACEWARE\Iguana\iguana_service.exe |
Anchor |
---|
| _Toc133236353 |
---|
| _Toc133236353 |
---|
|
Table 15: Application Exceptions for Iguana
Anchor |
---|
| _Toc133236336 |
---|
| _Toc133236336 |
---|
|
Directory WhitelistingFile Path – default [user configurable] |
iNTERFACEWARE Iguana |
%ROOT%\Program Files\iNTERFACEWARE\ |
%ROOT%\Program Files (x86)\iNTERFACEWARE\ |
Anchor |
---|
| _Toc133236354 |
---|
| _Toc133236354 |
---|
|
Table 16: Directory Whitelist for Iguana
Anchor |
---|
| _Toc133236337 |
---|
| _Toc133236337 |
---|
|
Service and User PermissionsService | User Access |
iNTERFACEWARE Iguana |
iNTERFACEWARE Iguana | Local System |
...