Industrial IoT System Development
Budget: $1,500 – $3,000 USD
Local and Cloud-based Industrial IoT Platform
Desired features:
1. Communication Structure
It must be capable of communicating with devices produced by us or used in the industry via MQTT, Profinet, Modbus TCP/IP, Modbus RTU, and other communication protocols that may be determined during the project process. Devices for testing and necessary information will be provided by us.
2. Devices
Devices will be added to the system by selecting the communication protocols and making the necessary settings. Devices produced by us will be automatically added to the system according to their types. The communication of the devices will be monitored, and the system will alert if there is an issue.
3. Dashboard Panels
This section visualizes data received from devices. In this section, users will be able to create pages using drag and drop. After creating the page, the design can be modified using tools in edit mode. Tools include: graphical display, gauge, bars, text boxes, images uploaded from the computer or pre-existing images in the system, buttons, alarm indicators, and a few special tools to be described during the project phase.
4. User Operations
Users will have authorization levels in addition to the usual data. With this authorization level, sections that can be accessed in the dashboard panels and menus will be defined.
5. Local Data
This section is for creating data needed for the system or generating new data from the data collected from the field through specific calculations.
6. Alarms
This section is for creating comparative alarms for all data in the system.
7. Machines and Machine Groups
This section is for defining the machines present in the field. Necessary documents for the machines, such as PDF, video, text, etc., can also be uploaded.
8. Periodic Maintenance
This section is for creating special maintenance plans for machines. Maintenance tasks created at certain intervals will renew themselves for the same period once completed.
9. Maintenance Teams
Maintenance team groups will be created, users will be added to these groups, and these groups can be selected while creating maintenance tasks.
10. Real-time Fault Reporting
Personnel in the field will be able to select a machine and add any faults or problems they observe into the system. These faults will be displayed on the real-time fault monitoring page and will be repaired by a technical staff member, who will complete the process by adding necessary explanations, images, and videos. Once completed, the real-time fault will be removed from the system.
11. Reports
All data in the system will be recorded. Desired data can be reported by creating a template and simply changing the date range. Reports will visually display data in graphical and tabular formats and can be saved as PDF, Excel, or image files.
12. Difference Reports
This feature allows for the creation of a new document by reading the selected data over two date ranges and subtracting the smaller value from the larger value. The reports can be saved as PDF, Excel, or image files.
13. Document Creation
Using the same features as the dashboard panel, this section allows for the visualization of real-time data at a specified date, which can be saved as PDF, Excel, or image files.
14. Manual Data Entry
This section collects data from the field that needs to be manually entered into the system. You can think of it as always having a specific Excel template that you continuously use to record data.
15. Telegram System
We want alarms, maintenance tasks, real-time faults, and communication errors to be sent in real-time to a created Telegram group.
16. System Settings
This section allows for the adjustment of all features and necessary information and monitoring of the system status. Details will be determined as the project progresses.
!!! All data recording sections, such as faults, maintenance, real-time fault system, and manual data entry, must include reporting and filtering capabilities.
All details and necessary information will be mutually discussed and provided when the project begins.
The site will be available in both English and Turkish. If possible, it would be better to arrange a language file to allow the entire system language to be changed easily.
We are open to all suggestions and improvements from you.
Desired features:
1. Communication Structure
It must be capable of communicating with devices produced by us or used in the industry via MQTT, Profinet, Modbus TCP/IP, Modbus RTU, and other communication protocols that may be determined during the project process. Devices for testing and necessary information will be provided by us.
2. Devices
Devices will be added to the system by selecting the communication protocols and making the necessary settings. Devices produced by us will be automatically added to the system according to their types. The communication of the devices will be monitored, and the system will alert if there is an issue.
3. Dashboard Panels
This section visualizes data received from devices. In this section, users will be able to create pages using drag and drop. After creating the page, the design can be modified using tools in edit mode. Tools include: graphical display, gauge, bars, text boxes, images uploaded from the computer or pre-existing images in the system, buttons, alarm indicators, and a few special tools to be described during the project phase.
4. User Operations
Users will have authorization levels in addition to the usual data. With this authorization level, sections that can be accessed in the dashboard panels and menus will be defined.
5. Local Data
This section is for creating data needed for the system or generating new data from the data collected from the field through specific calculations.
6. Alarms
This section is for creating comparative alarms for all data in the system.
7. Machines and Machine Groups
This section is for defining the machines present in the field. Necessary documents for the machines, such as PDF, video, text, etc., can also be uploaded.
8. Periodic Maintenance
This section is for creating special maintenance plans for machines. Maintenance tasks created at certain intervals will renew themselves for the same period once completed.
9. Maintenance Teams
Maintenance team groups will be created, users will be added to these groups, and these groups can be selected while creating maintenance tasks.
10. Real-time Fault Reporting
Personnel in the field will be able to select a machine and add any faults or problems they observe into the system. These faults will be displayed on the real-time fault monitoring page and will be repaired by a technical staff member, who will complete the process by adding necessary explanations, images, and videos. Once completed, the real-time fault will be removed from the system.
11. Reports
All data in the system will be recorded. Desired data can be reported by creating a template and simply changing the date range. Reports will visually display data in graphical and tabular formats and can be saved as PDF, Excel, or image files.
12. Difference Reports
This feature allows for the creation of a new document by reading the selected data over two date ranges and subtracting the smaller value from the larger value. The reports can be saved as PDF, Excel, or image files.
13. Document Creation
Using the same features as the dashboard panel, this section allows for the visualization of real-time data at a specified date, which can be saved as PDF, Excel, or image files.
14. Manual Data Entry
This section collects data from the field that needs to be manually entered into the system. You can think of it as always having a specific Excel template that you continuously use to record data.
15. Telegram System
We want alarms, maintenance tasks, real-time faults, and communication errors to be sent in real-time to a created Telegram group.
16. System Settings
This section allows for the adjustment of all features and necessary information and monitoring of the system status. Details will be determined as the project progresses.
!!! All data recording sections, such as faults, maintenance, real-time fault system, and manual data entry, must include reporting and filtering capabilities.
All details and necessary information will be mutually discussed and provided when the project begins.
The site will be available in both English and Turkish. If possible, it would be better to arrange a language file to allow the entire system language to be changed easily.
We are open to all suggestions and improvements from you.