wGrow - Team Notes

I. Introduction

A. Background

The customer, a production company for food ingredients, had a key production facility with multiple airpufying equipment. The company was looking for a solution to manage the equipment, including the ability to preset parameters, save different sets of settings, check filters, trigger maintenance alarms, and produce usage and air quality reports.

B. Objectives

The objective of the project was to deploy Bluetooth components into the equipment and design a Server-Based System with a Web Interface and a Mobile Interface (PWA) to meet the customer's requirements. The solution needed to be user-friendly, scalable, and robust, allowing engineers to easily manage the equipment from anywhere.

C. Scope of Work

The scope of work included the design and implementation of the Server-Based System, the Web Interface, and the Mobile Interface (PWA). The solution needed to provide the following functionality:

1. Preset parameters to turn the equipment on and off
2. Save different sets of settings to cater to different situations
3. Check the filters and trigger maintenance alarms
4. Produce weekly and monthly usage reports
5. Produce air quality reports
6. View power consumption information

II. Solution Design

A. Server-Based System

1. Architecture Overview
   
   The Server-Based System was designed to be the central repository of all data and information related to the airpufying equipment. The system was built using a robust and scalable architecture, allowing it to handle a large volume of data and concurrent users.

2. Database Design
   
   The database was designed to store information such as equipment settings, filter status, usage reports, air quality reports, power consumption, and maintenance alarms. The following tables were created:

a. Equipment Information Table The Equipment Information Table stored information about each piece of equipment, including its unique identifier, location, and status.

b. Usage Report Table The Usage Report Table stored information about the usage of each piece of equipment, including the dates and times of usage and the duration of usage.

c. Air Quality Report Table The Air Quality Report Table stored information about the air quality in the production facility, including the air quality readings and the dates and times of the readings.

d. Power Consumption Table The Power Consumption Table stored information about the power consumption of each piece of equipment, including the power consumption readings and the dates and times of the readings.

e. Maintenance Alarm Table The Maintenance Alarm Table stored information about maintenance alarms triggered for each piece of equipment, including the date and time of the alarm and the type of maintenance required.

3. Software Architecture
   
   The software architecture was designed to provide the following functionality:

a. Modules Overview The software was divided into modules, including a module for equipment management, a module for report generation, and a module for maintenance management.

b. Communication Protocols The system was designed to use Bluetooth for communication between the equipment and the server. The communication protocol used was based on the Bluetooth Low Energy (BLE) standard.

B. Web Interface

1. User Interface Design The Web Interface was designed to be user-friendly and intuitive, allowing engineers to easily access and manage the equipment information.

2. Functionality Overview The Web Interface provided the following functionality:

1. Preset parameters to turn the equipment on and off
2. Save different sets of settings to cater to different situations
3. Check the filters and trigger maintenance alarms
4. Produce weekly and monthly usage reports
5. Produce air quality reports
6. View power consumption information

C. Mobile Interface (PWA)

1. User Interface
   
   Design The Mobile Interface was designed as a Progressive Web Application (PWA), allowing engineers to access the system from their mobile devices. The user interface was designed to be fast and responsive, providing a seamless user experience on mobile devices.

2. Functionality Overview
   
   The Mobile Interface provided the same functionality as the Web Interface, allowing engineers to manage the equipment on the go.

III. Implementation Details

A. Server Environment

1. Hardware Requirements
   
   The server was implemented using a high-performance server with enough storage and RAM to handle the expected volume of data.

2. Network Environment
   
   The server was connected to the network using a reliable and fast network connection, ensuring that the data could be transmitted quickly and efficiently.

3. Server Configuration
   
   The server was configured to ensure maximum security and performance, including the implementation of firewalls and other security measures.

B. Bluetooth IOT Device Management

1. Coding Sample in C#
   
   The following is a sample of the code used to manage the Bluetooth IOT devices:

a. Connection Establishment

private async void ConnectToDevice(BluetoothLEDevice device)
{
    if (device == null)
        return;

    var result = await device.ConnectAsync();
    if (result == BluetoothError.Success)
    {
        var services = await device.GetGattServicesAsync();
        foreach (var service in services.Services)
        {
            var characteristics = await service.GetCharacteristicsAsync();
            foreach (var characteristic in characteristics.Characteristics)
            {
                // Do something with the characteristic
            }
        }
    }
}

b. Data Collection

private async void ReadDataFromCharacteristic(GattCharacteristic characteristic)
{
    if (characteristic == null)
        return;

    var result = await characteristic.ReadValueAsync();
    if (result.Status == GattCommunicationStatus.Success)
    {
        var value = result.Value;
        // Do something with the value
    }
}

c. Data Synchronization with Server

private async void SynchronizeDataWithServer(byte[] data)
{
    using (var client = new HttpClient())
    {
        var content = new ByteArrayContent(data);
        var result = await client.PostAsync("http://server/api/data", content);
        if (result.IsSuccessStatusCode)
        {
            // Data synchronized successfully
        }
    }
}

IV. Conclusion

A. Project Outcome

The project was successfully completed, delivering a Server-Based System with a Web Interface and a Mobile Interface (PWA) to the customer. The solution provided the customer with the ability to manage their airpufying equipment from anywhere, and the ability to access important information such as usage reports, air quality reports, power consumption, and maintenance alarms.

B. Team's Ability to Handle Similar Projects

The successful completion of the project demonstrated our team's ability to handle similar projects, including the design and implementation of Server-Based Systems, Web Interfaces, and Mobile Interfaces (PWA).

V. References

A. Technologies Used

1. Bluetooth Low Energy (BLE)
2. C#
3. HTML
4. CSS
5. JavaScript

B. Documentation and Guidelines

1. Bluetooth Low Energy (BLE) specification
2. Microsoft documentation for C#
3. W3C documentation for HTML, CSS, and JavaScript

C. Future Enhancements

Potential future enhancements to the solution include:

1. Integration with other systems, such as a CRM or ERP system
2. Implementation of machine learning algorithms to improve equipment efficiency and maintenance schedules
3. Expansion of the Mobile Interface (PWA) to include additional functionality, such as push notifications for maintenance alarms
4. Implementation of additional security measures, such as encryption for sensitive data.

This case study demonstrates the successful deployment of Bluetooth components for airpufying equipment management, providing the customer with the ability to manage their equipment from anywhere and access important information. Our team's ability to handle similar projects was demonstrated by the successful delivery of the solution, meeting the customer's requirements and exceeding their expectations.