Project Considerations Checklist

The objective is to comprehend and resolve any problems or issues by creating a secure and stable system. This involves securely collecting various data points, recording all crucial values, and implementing straightforward limit alarms to ensure that the system is stable and functioning properly.

GraphWorX™ plays a crucial role in monitoring the TFMS. It creates an easily interpreted display and can add devices to the system. The goal is to achieve alarm monitoring with the added benefit of being able to drill down into device details for further failure analysis, making it an invaluable tool in the TFMS monitoring process.

System component identification is important—locations, devices, or equipment that need to be monitored. The objective in this process is significant as it aids in estimating the project size, upon which we can make informed decisions.

The TFMS project has one location comprised of three tanks with various components like pressure sensors, pumps, and valves. The system uses approximately 48 tags with an update rate in seconds.

The objective is to identify the number and type of equipment integrated into the project. The TFMS includes the following devices and quantities:

• 3 tanks
• 6 pumps (2 pumps per tank)
• 6 valves (2 valves per tank)
• 6 pressure indicators (2 pressure indicators per tank)
• 6 flow meters (2 flow meters per tank)

We will create the TFMS equipment assets (categories and equipment classes) in Workbench.

The objective is identifying and defining device data points (tags) for equipment classes. This effort helps reduce the number of equipment classes by identifying devices with the same data points. The TFMS data points are:

• Tanks—Depth (%), Density (kg/m3), Inner Pressure (MPa), Temperature (°C)
• Pumps—Command (Opened/Closed), Status (Opened/Closed)
• Valves—Command (Opened/Closed), Status (Opened/Closed)
• Pressure Indicators—Pressure (MPa)
• Flow Meters—Flow (m3/h)

The objective is to understand which protocol, such as OPC UA, BACnet, and Modbus, is best suited for the project and enable only that protocol for the system. The TFMS connects devices and equipment to OPC UA and Mitsubishi Electric FA. We will use our DeviceXPlorer OPC Server as a simulated data source.

Improve system security by whitelisting only used protocols. The objective is to inform the local IT department of what protocols to allow the from the data connectivity item. For example, TFMS is using the following protocols:

• HTTP (port 80) / HTTPS (port 443)—Network firewall between the servers and clients
• TCP (port 52250)—Takebishi DeviceXPlorer OPC UA server remote connection (if applicable)

The objective is to determine the individuals who will be using the GENESIS platform and the security permissions they require. It is important to identify all users, their roles, and their rights to manage and view data within the system. The TFMS users and their corresponding access rights (permissions) are as follows:

• Administrator—This role involves controlling the system, establishing account security policies, adding or removing users, and defining access permissions and user passwords.
• Operator—This role is for users with various privileges who need access to alarms, equipment, and system displays.

The objective is to determine the architecture based on the system size. Consult with ICONICS if needed. The system size can be multi-tier or single-tier.

• Multi-tier architecture is suitable for large deployments where more server resources are required for complex calculations and equipment monitoring (>100k tags).
• Single-tier architecture is suitable for small to medium-sized local deployments (<100k tags).