Fuuz Platform System Requirements

Fuuz Platform System Requirements

1. Fuuz Cloud:

  1. Browser Access: The Fuuz Cloud is accessible through modern web browsers, ensuring compatibility with a wide range of devices and operating systems.
  2. Browser Compatibility: The platform is optimized to run smoothly on popular browsers such as Chrome, Firefox, Edge, and more.
  3. Browser Updates: It's recommended to disable automatic browser updates to maintain stability and consistency across access points.

System Requirements:

  1. Operating System: Fuuz is compatible with various versions of Windows operating systems, MacOS, iOS, Linux (Fuuz Cloud is browser-based)
  2. Processor: A multi-core processor is recommended to handle the processing demands of communication and data exchange.
  3. Memory (RAM): The recommended RAM can vary depending on the number of devices and tags you plan to connect. Generally, a minimum of 4 GB of RAM is suggested, and more may be needed for larger deployments.
  4. Disk Space: The amount of disc space required typically is not a huge consideration, because the application runs completely in the browser, and the only time data is consumed on your device is if you were to download/extract.
  5. Network Interface: A reliable network interface is essential for seamless communication with industrial devices and systems. Wi-Fi is acceptable, however wired connections are always preferred wherever possible.

2. Fuuz Gateway:

  1. Device Gateway: The Fuuz Gateway serves as the data pipeline for industrial controls, file folders, and other data assets residing behind your firewall.
  2. Hardware: It can run on physical PCs, servers, or virtual machines, offering flexibility in deployment.
  3. Configuration: The configuration of the Fuuz Gateway is managed from the cloud, allowing seamless remote management and updates.

System Requirements:

  1. Operating System: Fuuz Gateway is compatible with various versions of Windows operating systems.
  2. Processor: A multi-core processor is recommended to handle the processing demands of communication and data exchange.
  3. Memory (RAM): The Device Gateway only uses about 150mb - 300mb but the recommended RAM can vary depending on the number of devices and tags you plan to connect. Generally, a minimum of 4-8 GB of RAM is suggested to run comfortably with Windows and all the other process a machine might have , and more may be needed for larger deployments.
  4. Disk Space: The Device Gateway takes 1gb-2gb of hard disk space but the amount of space required will depend on the factors below. Typically, several gigabytes of disk space are required, and it's advisable to have ample space for future data growth.
    1. number of devices and tags,
    2. application logs
    3. historical data retention.
    4. store and forward
  5. Network Interface: A reliable network interface is essential for seamless communication with industrial devices and systems.

Additional Considerations:

  1. Virtualization: MFGx products can often be run in virtualized environments. However, ensure that the virtualization platform meets the recommended requirements and provides sufficient resources.
  2. Redundancy and High Availability: For critical applications, you may consider setting up redundancy and high availability configurations to ensure continuous operation in case of server failures.
  3. Integration with Other Software: Depending on your use case, you may need to ensure compatibility with other software systems, such as database servers or visualization tools.

As server requirements can vary based on specific factors, it's crucial to review the product documentation, consult with your IT team, and potentially reach out to MFGx support or sales team for guidance tailored to your deployment needs.

These system requirements provide the foundation for an optimal Fuuz Platform experience. By ensuring compatibility, flexibility, and controlled administration, the Fuuz Platform is poised to empower manufacturing operations with a reliable and efficient data management solution.

    • Related Articles

    • SOC Compliance

      The Fuuz Platform runs on the AWS Cloud Network - AWS Datacenters hold and process all of the Fuuz platform data and any data you may persist within the platform. https://aws.amazon.com/compliance/soc-faqs/ AWS System and Organization Controls (SOC) ...
    • General Platform FAQ's

      In this space, we will be posting general platform FAQ’s to help address more generic questions that often come up with customers who are utilizing the platform tools in Fuuz. Q: What is an Industrial Intelligence Platform? A: Fuuz is the first ...
    • Fuuz can be your "Connected Worker Platform"

      <br> Connected Worker Platform: How Fuuz AI Bridges the Gap Between Simple Digital Work Instructions and Complete MES Introduction Connected Worker Platforms (CWP) have emerged as a popular solution for providing real-time shop floor work ...
    • System connectivity validation - testing a connection when your 3rd party moves its hosting

      In this video, our engineer responds to an alert from a 3rd party, in this case Plex ERP, but this could be any system. Sometimes software vendors will 'move' their hosting and that can present some concerns for your integrations. Of course, we at ...
    • Industry 3 and Industry 4 differences in ERP and MES Integrations

      The opinions and views within this video, are from a well known industry expert Walker Reynolds <br> MES to ERP Communications: Industry 3.0 vs Industry 4.0 Integration Approaches Introduction Manufacturing organizations face critical ...