# Getting Started ## Introduction The Skysens AgPM platform is a cutting-edge AI based Industrial Internet of Things (A-IIoT) solution that integrates artificial intelligence (AI) to optimize and enhance industrial and technical operations. It effectively combines AI's predictive power with IoT's interconnected architecture to boost operational efficiency, improve resource management, and stimulate innovation across multiple technical sectors. This platform empowers industries by offering a comprehensive suite of tools and applications designed for real-time data collection, analysis, and feedback. By utilizing advanced AI algorithms, and IoT capabilities Skysens AgPM enhances predictive maintenance, boosts energy efficiency, and promotes sustainability through automated decision-making, asset management, and improved productivity AgPM is not just a software tool but also type of IoT infrastructure which facilitates especially wireless IoT connectivity with low cost devices and provides plug and play physical capabilities in order to empower physical operations and teams. Skysens AgPM is versatile, catering to industrial needs in manufacturing, logistics, facility management and smart cities. It provides a scalable infrastructure with no-code AI integration and plug-and-play IoT capabilities, ensuring ease of use at the operational level. This guide helps you to understand how AgPM platform, integrations, IoT capabilities and overall business and technical support works. ## General Considerations Skysens AgPM can run on cloud, private cloud and on premises environment depending on your project requirement. Depending on deployment type, some functions may differ such as AI and industrial data integrations. You can find more information on related matter. In order to to have maximum return of investment from technical project, Skysens provides hardware and integration services and consultancy in addition to AgPM platform. You can find more information at [hardware support](/support/hardware-support) and [consultancy pages](/consultancy). Depending of license type, these consultancy and support levels do change. Please refer to [support levels ](/support)page. For any inquires please email to # Agile Predictive Monitoring

Agile Predictive Monitoring represents a paradigm shift about how industries manage their assets and technical operations, emphasizing a dynamic and responsive approach with IoT and AI blend. At its core, this concept revolves around harnessing data-driven insights to anticipate and prevent potential issues, with easy to use AI and low cost IoT. In order to create flexible and reachable technology platform useful for anyone in any level in technical facilities, AgPM concept heavily relies on low cost wireless IoT capabilities and practical, context aware, high performance AI capabilities as well as no-code infrastructure. # Concept

Agile Predictive Monitoring is a modern approach to monitoring systems, designed to bring greater efficiency and adaptability to various industries. It has started to being developed in around mid 2010s with the rapid development in low-power, low-cost wireless IoT space and AI technologies, inspired from lean manufacturing and agile development principles. It aims to provide shortcut between physical data acquisition and AI applications and provide capabilities for all user levels inside the industrial enterprise. AgPM can be used for any enterprise which has technical assets and technical infrastructure such as manufacturing plant, logistical enterprises, airports, sea ports, municipality or city councils, shopping malls, residential and office buildings any many others. It revolves around key principles like **flexibility**, allowing a single platform to handle diverse applications simultaneously, reducing costs and addressing multiple issues at once. **User-centricity** is another cornerstone, focusing on user-friendly interfaces to minimize training, support, and adaptation time, ultimately enhancing profitability. **Scalability** is crucial, enabling businesses to expand their systems at their own pace without extra costs, while adaptability ensures compatibility with existing infrastructures and the ability to integrate various machines, equipment, and sensor types. Furthermore, **inclusivity** is prioritized by providing tailored interfaces and data for different users, facilitating effective data sharing. This approach aims to streamline operations, reduce costs, and improve decision-making across various sectors. Rapid **deployment** and **adaptability** is also a areas that AgPM platform has emphasis on, with **rapid deployment** for both IoT and platform capabilities, enterprises cut the time and budget between idea and analysis. With **adaptability**, additional 3rd party services and products wont be needed for most of the applications. # Hardware All IoT and industrial hardware no matter what the connectivity technology is, can be used to develop agile predictive monitoring capabilities. However, for easy and rapid deployment with low infrastructure cost AgPM concept emphasizes on :\ -**Wireless**\ **-Low cost**\ **-Plug and Play** IoT hardware. This strategy lowers the overall system deployment costs up to 10X due to OT and IT network complexities and sensor costs. For this, LoRaWAN, GSM, Bluetooth, Wifi hardware and systems being used extensively. Since low cost wireless hardware is main priority, LoRaWAN devices have a unique place in AgPM. For LoRaWAN, Skysens AgPM provides free LoRa Network Server capability and selected sensor catalog for plug and play usage.

LoRaWAN sensors can be deployed completely wireless with long battery life, long communication range and low costs. These sensors comes with extensive types and models such as vibration, temperature, air quality, location and others. Some of these sensors provide unique plug and play capability and edge processing capabilities which enables very low cost system development to a levels no other system can achieve.

Advantech Wireless LoRaWAN Vibration Sensor Deployment

In addition to LoRaWAN, AgPM supports 4G/5G infrastructure with low latency, very high bandwidth and data rates and uses industrial type gateway devices. ![](https://803875272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUGOLnOOPZHTcQBNC5GI%2Fuploads%2FD88FZplsiDiPaTQf4sVh%2Fimage.png?alt=media\&token=24ca010b-07bf-4b2e-97d0-58ac2d661d50) Cisco 5G Gateway ![](https://803875272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUGOLnOOPZHTcQBNC5GI%2Fuploads%2FlI6rwnjwXUYHY9Y5DEsc%2Fimage.png?alt=media\&token=30545978-06aa-49fb-b385-5854c0cd761e) Robustel 5G Gateway To select right hardware and architecture with optimal output for the project, Skysens AgPM hardware consultancy service is available for enterprise users. # Wireless Networks Given their flexibility and cost-efficiency, wireless networks are crucial for agile predictive monitoring systems. For applications involving low data rates, Low Power Wide Area Networks (LPWAN) like LoRaWAN are often preferred, while for high data rate applications, 4G, 5G, and WiFi are favored due to their high capacity and maturity.

The effective utilization of wireless network technologies is highly important for IoT systems. For comparison, especially for wide area networks, wireless infrastructure can be 10X lower cost with very short deployment times due to lower labor and deployment costs.

The Skysens AgPM platform is designed to effectively use wireless networks.Its wireless monitoring suite enables users to deploy and manage LoRaWAN networks and also 4G/5G network in public or private settings.

Skysens AgPM LoRaWAN Network Management Suite

With this approach, after the initial deployment of the wireless infrastructure, any user who has access to the platform in the enterprise can deploy IoT device where ever they want in the facility and start AI applications without IT involvement. This creates "I can do it" mindset in technical teams and rapidly increases speed of digital transformation.

Easy Sensor Deployment Capability With Wireless Infrastructure

# Platform AgPM platform is the main element of the concept and should be designed according to principles of it. AgPM principles dictates that platforms;\ -Should be easy to use with no-code interfaces \ -Should covers extensive use cases on single platform\ -Should manage wireless and wired devices and networks on plug and play level as much as possible\ -Should provide AI models up to the task with no code interfaces\ -Needs to be easily customizable for any type of user whether they are at managerial or operational level.\ -Should have ready to use integration and management interfaces for industrial and non industrial data sources This means no-code interfaces with high customization capabilities are crucial.

No Code Dashboard (Overview) Design with Drag and Drop Capabilities

Also, to address different use cases, AgPM platforms should support both real time and analytics use cases.

# AI Agile Predictive Monitoring concept aims to make AI available for operational teams as flexible and practical manner. For this, AI being used in several different ways for best output AI levels and capabilities can be listed as:\ \ **-Edge Level:** On-Sensor AI capabilities\ **-Analytics Level:** Unsupervised, machine learning capabilities on either stream or stored data\ **-Application Specific:** Specialized AI models to applications such as energy efficiency, predictive maintenance etc. \ **-Agents:** Pre-trained, LLM based agents acts as a expert in respective fields (maintenance, energy efficiency, health and safety etc.) with data analytics capabilities. These levels aimed provide AI capabilities as flexible as possible for all types of users and applications. \ Since AgPM is primed for practical AI usage and connecting real world operations with AI easily and efficiently, preferably plug-and-play level, several AI models are being used with different levels simultaneously. Please see [AI page](/agile-predictive-monitoring/ai) for more information.\ \

# Main Menu and Overview Where data flow like a river ## Main Menu

Main menu has two parts, header area and the side menu. Side menu has a sliding feature and can completely closed off for wider screen usage. Header area has quick action tools. These tools can be used for different screen use cases such as full screen mode for detailed data analysis or production monitoring, night mode for low light usage or anti glaring purposes, screen lock for operator screen usage.

Account information area records last login for security purposes and secure logout option. ## Oveview Overview is the main dashboard area for Skysens AgPM. It is completely customizable by user can be shared to another user in the enterprise with enterprise license.

Overview is the main area which has responsive design for mobile capabilities.

Overview widgets are divided by templates, users can design their own templates depending on the use case or Skysens team can design for the user depending of the specifications.

For best performance and usability, we suggest to use different templates with specific needs and applications with 5-7 widgets maximum in each. Templates can be deleted at Edit Template Menu with every widgets in it. **WARNING: THIS ACTION IS NOT REVERSIBLE**

# Overview Usecases Overview section can be used for operational or analytical purposes. Depending on the user preference, both usecases can be supported. Users can use overview as a real time monitoring, as SCADA-like interface but with AgPM capabilities:

Or can design an andon screen for factory floor informative screens:

Andon screen usage (representational image)

Or users can analyze current production rate and machine related events with connection to MES software:

Or can use overview as an data analytics purposes:

Location based usage is also very popular among users since users can monitor assets on maps and get latest notifications:

Global Map and Floor Plan Based Monitoring

Location tracking in real time is also important for logistics and safety applications:

Mobile friendly design also helps users to monitor their infrastructure on the go.

# Widget Types Widgets are the main analytics interfaces for various usecases. At overview all widgets can be resized and moved wit widgets resize lock button pushed. To add a new widget add new widget button is available.

Available widget can be added through add new widget menu. All widgets have their own menu depending on the widget requirements. Some widgets are very simplistic yet powerful, some widgets are for analytics purposes such as intensity or sankey diagram. #### Useful widgets for real time data monitoring: Value Gauge Table Notification Map Text Image #### Useful widgets for data analytics and comparison: Intensity Table Line Chart Bar Chart Line-Bar Chart Pie Chart Sankey Diagram # Value Value Widget For Direct Data Representation Value widget is a standard value publishing widget and can be used as output result of analytics or real time monitoring purposes. It can work with numbers and strings as a value. For strings, output of asset field can directly be published without any additional remarks.It makes it very useful for LLM enhanced applications such as error message generation. If string is used as a data source, color and threshold mechanism do not apply. For numbers data type, it is color codded and can publish a message depending on the value thresholds detailed in its configuration menu:

Widget menu includes multiple capabilities and follows same structure with other widget configuration capabilities.

# Gauge Value representation with relative status to maximum and minimum levels Gauge widget is popular widget for many industrial application and being used to show number values and respective levels to other limits.

It has a flexible interface and can represent multiple information on single widget interface:

Its configuration menu also includes some unique and standard features:

# Image Carousel for checking notes and images at overview with other widgets Image widget is a practical widget to check hand notes, photos, schematics, plans and other visual materials in overview without any third party viewer.

Its very useful for checking technical documents and schematics with other real time widgets.

Its configuration menu is easy to use:

As default, image widget works with static image files uploaded by user, however, it can be integrated to third party api for image flow such as CCTV screenshots, schematics or hand notes images with enterprise support. # Notification Easy access to notification interface Notification widget helps user to understand latest status and outputs of AI models or rules or conditions of assets such as offline or online. It can be configured to show all notifications or individual assets.

There is 2 main criteria option for notification publish: First one is "Last Notification" which shows **last 5 notification in last 24 hours** of entire asset list without any differentiation.It is being used to understand anomalies in entire system. Second one is "Asset" which shows **last 3 notification specific to selected assets without any time limit**.

Notification Widget Configuration Screen

Notification widget is very useful especially for AI enhanced asset monitoring applications. # Map Location based visualisation Map widget is the main location based monitoring widget for global or floorplan based location tracking as well as indoor and outdoor location tracking. It can be used to monitor various assets geographical locations on global map with additional GIS data layers if requested. For data layer addition please contact **Skysens Team**. In global map user can also track moving assets if location data is available.

Users can also use floor plan or industrial schematics based layouts with live data output and their alarm status. With this capability, SCADA-like use cases depends on real time data flow or AI outputs on system representation is possible.

Floorplan Layout (With SCADA Schematics)

# Text Advanced notepad for information Text widget is easy to use note taking and checking information whether its visual or written knowledge. Its mostly being used for taking notes and checking videos.

In addition to notes, photos can be added and notes can be created with hypelinks. Due to its flexibility, text widget can also be used for iframed applications which includes videos.

# Intensity Chart (Heatmap) Complex yet powerful analytics tool Intensity widget is complex analytical widget mostly being used to create heat maps in time domain. Users can analyze intensity of any system in time domain with different data parsing options.

It can be used to understand patterns, changes, spikes and other time dependent changes in the data.

It mostly being used to understand energy consumption patterns, resource and water usages, asset usage analysis, bottleneck analysis, inefficiency analysis, system loads, heat maps and their change in time.

Intensity Widget Configuration Menu General Features

It is color codded and X and Y axis is dependent on time intervals which can be configured according to data parsing configuration. Time frame can be selected according to user need and can be last 24 hour, last 7 days, last 30 days, last 180 days or custom time frame.

Due to inconsistent data flow from IoT sources by their nature and pixel based structure of intensity chart, data being parsed with pre-determined time intervals and parsing algorithms and can not directly connect to data flow itself without parsing. For direct visualization of time dependent data, please use [Line Chart](/main-menu-and-overview/widget-types/line-chart). Data can be analyzed with 4 different time interval option which are **hourly, daily, weekly and monthly**.(Interaction Period)

Data parsing configuration also provides 3 algorithm option to parse the data for every data time interval option selected. These are: **-Average:** Takes arithmetic average of all data falls in selected time interval. **-Percentage:** Rational difference between first data and last data in selected time lapse.It is used to understand change as ratio in time lapse. Can be used for consumption or counting analysis. **-Differential:** Nominal difference between first and last data in selected time lapse. Can be used to understand extreme changes.

After selecting time frame, interaction period (time interval) and data parsing algorithm, users can create a color gradient with color palette for minimum and maximum threshold values and notes to depending on values. Users can also create mid values in order to create more detailed color pallet and notes.

# Table Configurable data table for practical usage Table widget is very flexible and easy to use data visualization tool to create tabular data.

It can be used for IoT device monitoring for devices and gateways with pre-configured setup.

It can also work with LoRaWAN gateways to monitor their activity.

Custom table type has flexible features which lets user to design their own tables without any coding or data manipulation service.

Custom tables can have unlimited number of assets and their fields as a data. In addition to standard features, custom tables have "Table Design" feature which lets user to design its own table up to 9 rows.

User can change position and data of the rows. **Possible Data Types:** **-Name:** Name of the asset **-EUI:** (Extented Unique Identifier) Unique identifier number of the asset. **-Status:** Current status of asset (offline or online) within minimum of 10 minutes (or 3 data interval). **-Rssi:** (Received Signal Strength Indication) Wireless signal strength (if asset is LoRaWAN IoT device). **-Snr:** (Signal to Noise Ratio) Wireless signal quality indicator (if asset is LoRaWAN IoT device). **-Lastseen:** Last data sent time and date of asset. **-Value:** Last data of the asset. **-Alarm:** Notification status of asset for last 24 hours. -**Min-Max:** Minimum and maximum read values of the asset for specific field. # Line Chart Most common way of representation for time series data Skysens AgPM provides line chart with multiple features and can be used for real time data monitoring or comparative analytics with unlimited data time frame.

Similar to intensity chart, line chart has built-in analytics capabilities for better data handling.Its widget menu has multiple function to handle different time series simultaneously. Its being used as a histogram, trend analysis, comparison of two or more time series and other technical and non technical requirements. Since data parsing manipulation can help user to identify different angles on the data, line chart widget also offers multiple different parsing option. Users can visualize data flows directly, or, they can manipulate data parser in order to understand hidden patterns with data parsing algorithm and interaction period time(time interval) feature.

Data can be analyzed with 4 different time interval option which are **hourly, daily, weekly and monthly**.(Interaction Period) Data parsing configuration also provides 3 algorithm option to parse the data for every data time interval option selected. These are: **-Average:** Takes arithmetic average of all data falls in selected time interval. **-Percentage:** Rational difference between first data and last data in selected time lapse.It is used to understand change as ratio in time lapse. Can be used for consumption or counting analysis. **-Differential:** Nominal difference between first and last data in selected time lapse. Can be used to understand extreme changes. # Bar Chart (Histogram) Practical representation for time series data As line chart, bar chart is also very common way of representing time domain series data.

Bar Chart With Two Asset And Single Data Field

It is helpful to see difference between different data sets and can support unlimited asset and their fields with two Y axis on time domain.

Bar chart also have data parsing algorithm options in addition to data interval option for data manipulation. However, users can also publish data directly without any data manipulation like in line chart.

Data can be analyzed with 4 different time interval option which are **hourly, daily, weekly and monthly**.(Interaction Period) Data parsing configuration also provides 3 algorithm option to parse the data for every data time interval option selected. These are: **-Average:** Takes arithmetic average of all data falls in selected time interval. **-Percentage:** Rational difference between first data and last data in selected time lapse.It is used to understand change as ratio in time lapse. Can be used for consumption or counting analysis. **-Differential:** Nominal difference between first and last data in selected time lapse. Can be used to understand extreme changes. # Line - Bar Chart Hybrid chart for easy analyze of time series data Line-Bar chart is a hybrid chart combines both line and bar chart characteristics for better data analysis.

It is useful to understand relationship of two or more different type of data such as temperature vs water consumption on single graphic. As other analytic charts, it has advanced features to provide easy to use interface.

Since its basically combination of line and bar charts, its configuration needs to be done for both charts.

Similar to line chart and bar chart, line-bar chart also have data parsing and data manipulation capabilities. Data can be analyzed with 4 different time interval option which are **hourly, daily, weekly and monthly**.(Interaction Period) Data parsing configuration also provides 3 algorithm option to parse the data for every data time interval option selected. These are: **-Average:** Takes arithmetic average of all data falls in selected time interval. **-Percentage:** Rational difference between first data and last data in selected time lapse.It is used to understand change as ratio in time lapse. Can be used for consumption or counting analysis. **-Differential:** Nominal difference between first and last data in selected time lapse. Can be used to understand extreme changes. # Pie Chart Easy to understand relative difference between data values

Pie chart is simple, yet powerful analytics tool which have being used to understand relative values between similar data field. It is being used in use cases such as water consumption, energy consumption, carbon footprint and other similar areas which requires comparative analysis. Its configuration menu is similar to other charts and detailed enough for complex chart designs.

# Sankey Diagram Diagram to analyze flow Sankey diagram is complex analytics tool to to visualize flows and relations between assets and resources on single chart.

It is widely being used to analyze; **-Water footprint** **-Water network** **-Energy footprint** **-Energy network** **-Resource consumption** **-Production speed and flow** And many other application types globally. In order to create a sankey diagram user needs to create [application flow](broken://pages/H6xqlUk7v4DEGM3b6XNC) ( from application network view) first.

Related Application Flow Design For Example Sankey Diagram

Since most of the configuration being handled at application flow, sankey diagram menu is very simple.

# Best Practices Tips and Tricks for Better Dashboards ### Data Visualisation Overview can support number of dashboards and templates depending on your edition type (**free edition:** 1 template 5 widget, **premium and enterprise editions:**unlimited template and widgets) but for good performance **we recommend to use up to 5 templates with maximum 10 widgets each**.

Depending on Your Browser Performance, Too Much Widget Usage Can Cause Performance Issues

Again, depending on your internet connection and browser performance, requesting too many data points may cause performance issues. For example, requesting 5 years of data with 1 minutes intervals may cause delays and performance issues. Please contact Skysens team if you require your historic data beyond your standard retention limit. ### User Groups and Types We recommend to divide user types in two, such as operational and analytics. Operational users will require real time, on demand, data with multiple widget usage. For their perspective, large visual indicators such as gauge or value widgets are useful and more simplistic dashboard designs are needed.

Analytics users are usually more concern about capability of comparative analytics and data manipulation capabilities in order to understand changes on the data.

Due to these differences we recommend to deploy different user groups and overview design strategies depending on their use cases. ### Real Time Data Tracking Overview widgets do update itself every time you refresh the page, however, using live data switch will help you to track real time changes easily. In order to not to effect from bandwidth issues we recommend to use live data only if necessary such as real time monitoring.

Live Data Switch in Widget Configuration Menu

# Notifications Notification engine

Skysens AgPM Notification Engine Architecture

Skysens notifications is a service to track and trace alarms and other outputs about assets and systems to notify user and integrated systems. It has multiple built in features and work with native integration to [rules ](/rules-menu)and [AI ](/agile-predictive-monitoring/ai)services. Since Skysens AgPM has a [microservice ](https://en.wikipedia.org/wiki/Microservices)architecture, notification engine outputs can easily integrated to third party collaboration tools such as Microsoft Teams, Slack. Please check [integrations ](/integrations)for more information. # Notification Menu Notification management and user interface Notification menu can be used to track created notifications by the engine.

Users can see last notifications depending on assets. Recursive notifications roll backs to single input and can be seen from the "details" menu.

Users can delete notifications from "Move to History" button while taking notes in order to track and trace notification history with user actions related to it.

Notification History and Related Note Taken by User

Notifications can also be tracked from related [asset's details page](/asset/asset-details).

Asset History Listing in Asset Detail Page

Notifications also can be tracked from the [notification widget](/main-menu-and-overview/widget-types/notification) in overview.

# Notification Types Not all notifications created equal Notification engine can create several different notifications. ### Rule Based Notifications These types of notifications mainly created at [rules](/rules-menu) menu by user to track and trace deviations, anomalies for both about data and IoT infrastructure such as offline devices. These notifications can be sent as text, email, voice email or webhooks or APIs. Please see [integrations ](/integrations)page for more detail.

Typical Rule Setting to Send Email as a Notification Output

These types of notifications can be created as a separate web service for enterprise users. These types of notifications can be traced in [logs ](/logs)page too. ### Data Service Based Notifications These type of notifications works mostly as a separate service and with AI models. These notifications can be tracked like a rule based notifications and also asset fields table:

Steam Efficiency AI Based Notification Sourced By Data Service

These type of notifications acts like a standard asset field so they can be used in any field related item in widgets or reporting. Skysens AI agents also can create notifications or write directly in to asset fields. Please see [AI page](/ai) for more information. # Asset Main data container for all data Asset is the main data container for Skysens AgPM platform.It can be used to manipulate and keep data with its unique identification number and can called on any integration layer with this.Please check [integrations](/integrations) page for how to call assets from external services.

Assets can be a digital or physical data source, a sensor, a machine, a person or just a result of simple calculation. Assets are being tracked with with their ID (`EUI`) which is unique number in all Skysens system, asset name, asset type, fields (main data), priority information, image of an asset and their history (including notifications, notes, images). Only Asset ID number is unique.

### Data Fields Data fields are main data points of Skysens AgPM. Assets can include unlimited number of fields. Depending of type of asset, some of them can keep tens of different assets while others may keep only one field. Field values can be `null`, `integer`, `string`, `boolean` without any conflict. Fields cannot be changed once asset is created if it is not a [virtual asset](/asset/asset-types). # Asset Types Different types of assets can cover a lot Assets can represent everything including real world moving or stationary physical items, individual sensors or IoT devices, digital data sources, user inputted data forms, calculations or algorithms outputs, AI interfaces and other data related items. For simplicity we divide assets in to two categories, **digital assets** and **physical assets**. ## Digital Assets Digital assets are digital data sources and can be external or internal. All digital and non-digital assets have unique Asset ID number which can be called by Skysens API services. External data sources can be any non-physical data source including but not limited to, external API services, enterprise level systems, external AI models and others. Any external data source with `API`service with `JSON` data format can be integrated to Skysens AgPM. Please see [integrations page](/integrations) for more information. Internal digital data sources can be simulated assets or virtual assets. ### Simulated Assets Simulated assets are automatic data generators and acts like a standard IoT devices depending on their configuration in terms of data interval and data fields. They can be used to test dashboard designs, algorithms and integrations.

### Virtual Assets Virtual assets are virtual data containers and acts like a real assets depending on their designed parameters. Like any asset, virtual assets can be called with their unique ID which supports [Unified Name Space](https://www.hivemq.com/blog/what-is-unified-namespace-uns-iiot-industry-40/) architecture. **They can be used for various reasons:** -Keeping the algorithms or calculations outputs as separate items. For example calculation of average value of some fields and keeping it for scheduled reporting. -Creating a new group of fields which may belong to different assets in to a single asset. -Triggering notifications according to user designed groups and assets, instead of existing assets. -Getting user inputs or constants for advanced calculations, for example, carbon footprint constant or cost calculations. Virtual assets provides easy and flexible way of designing new data which may used to contextualize any topic for AI or other platform services consumption.

There are two types of virtual assets: **-Virtual Value Assets:** These are standard `field` based data assets and keeps all available types of data in their data fields. These type of assets can be configured with [rule engine](/rules-menu). **-Virtual Form Assets** Virtual form assets have designed to be used for user inputs or constant keeping. It works similar to other assets but fields names, values and units can be created by user itself instead of service. **These type of assets can be used for various reasons such as:** -Calculating prices or costs. -Tracking carbon footprint or similar enterprise level calculations. -Unit exchange constant and multipliers. In virtual forms, asset detail page is being used to add or remove field inputs.

### Physical Assets Physical assets cover all physical data sources such as IoT devices, industrial sensors, gateway devices, machine and equipment, moving assets, locations and other contextualized physical assets. As a digital asset type, these assets being created at [sources](/sources)[ page](/sources) depending on their data source whether it is a IoT device, industrial device or other data which directed directly from physical device . It can be contextualized with virtual sensor by grouping several different fields together to make physical features in to one asset. # Asset Listing Control tower for all your assets Asset menu and asset list provides overview of all assets on single page. Independent from asset type, all assets being listed in asset list depending on [user permission](/settings/user-role-management-settings).

With asset list features, users can check multiple items simultaneously about assets such as names, data sources, photos, status, latest data time, latest data with its fields, related rules, battery level (if it is a IoT device), their priority. Also users can mute notifications to be sent about the assets itself. User can download asset list as a XLS format and check asset's other informations easily with quick action menu. # Asset Details Asset information in a nutshell Asset details page provides most up to date information about digital or physical asset. It can contain all the information related the asset, its general information, visuals, data and its history.

### Asset Information Zone: **Asset ID:** Asset's unique ID number **Asset Name:** Asset's name which can be updated from Asset's Setting. **Asset Type:** Type of asset for reference information. **Data Fields:** Related data fields kept under asset. **Priority:** Assets importance for overall system for notification management purposes.Can be changed from settings. **Asset Image:** Image of related asset for easier management.Can be changed from settings. ### Asset's History Zone: Asset's history zone is logging area for all related notifications about the asset. It can also keep logs of texts and photos which created by the user. This feature is very useful for maintenance purposes.

Users Can Add Maintenance Notes, Visuals, Documents and Track Notifications.

### Asset's Data Zone: Users can monitor data which are specific to related asset with line chart and tabular representation. ### Data Download: It provides unstructured `CSV` for inputted time period. ### Asset(Device) Settings

Users can change name of the asset, its priority, global location and photo and check related rules. # Application Blueprints for real world Applications are small, configurable micro services, designed to be configured by the user to represent real world technical infrastructure and systems such as electrical infrastructure or water systems. After configuration, application service feeds data to [AI ](/ai)models, [reporting ](/reports)engine, [notification ](/notifications)engine and other related micro-services.

Similar to [virtual form assets](/asset/asset-types), users needed to inputs necessary information with pre-determined form structure specifically designed to specific application. Depending on application types, users might asked to tagged different fields and input constants.

Energy Application Form to Tag Energy Related Parameters in Asset's Data Fields

After tagging and inputting constants, user may asked to draw the network of physical system to digitize relationships for algorithms and AI models.

Example for Drag-drop Network Design For Energy Application

Network view also can be seen with "network view" button.

Users can also integrate AI agents and models directly in to assets or fields in network with enterprise [licensing](/licensing). # Rules Menu Main logic workers of the platform Rules are the main logic engine for manipulating data and creating new assets, grouping, data flows and notifications.

For data manipulation asset based micro services and AI models can be facilitated in addition to rule engine.However, rules engine is the main data manipulation service with its extensive logic design capabilities. With easy to use and/or gates, hierarchical modelling, no code integrations it covers various tasks such as grouping, notification creation, asset data calculation and manipulation.

Users can design rule hierarchies in order to create logic flows from first to last action.

Rule trigger sequence (Hierarchy) T0 First T0+4 Last

Rule list can be design according to required sequence. All rule elements aligned to the left starts at same time. Within each sequence, sub-rules are organized top-to-bottom, representing a hierarchical order of application With this flexibility users can design sequential logical systems which are designed to handle complex tasks. # Rules Edit and Frequency Editing the logic New rules can be created from "Add New Rule" button and can be edited from its details button.

Users can use rule detail page to design complex or simple rule settings depending on their need. Triggering an email for offline devices, or triggering a text message for threshold values are examples for simple rule designs. To analyze multiple sensors outputs and design linear relationship and create actions with simultaneous notifications are example for complex rule designs. Rule detail page composes with two areas. As in standard logic workers, Condition and Action sides are available left and right with their unique features. Users can also decide triggering frequency of rule from frequency setting.

### Rule Triggering Frequency Rules can be triggered with new incoming data from the asset or with time period decided by user.

User can set rule trigger for every time data arrives (Current) to subjected asset field or for beginning of every hour (Hourly) or every day (Daily). User can also create a custom timing triggers from the "Custom" selection from drop down.

Setting Time Trigger with Custom Frequency

In "Set a Custom Frequency" pop-up menu, user needs to select "frequency" drop-down, time period and time areas. **Frequency:** User need to select from minute, hour, day, week, month and year options to select when to trigger the rule. **Time Period:**Depending on selected frequency user needs to select repeating period If minutes is selected, user needs to decide triggering in every X time. If week is selected, user needs to decide which number of day(starting from monday) in a week rule will be triggered. If month is selected, number of day in the month must be selected. If year is selected, user needs to select which day in the year rule will be triggered. **Time:** This option works with frequency selection and user needs to decide which hour and minute rule will be triggered. # Condition How things will be handled Condition and action sides of the rule edit menu starts with condition checker cards which are basically programmable micro services for logic design purposes:

**Offline Status Checker:** This is a checkbox for asset offline checker service. Offline checker service is a micro-service which automatically checks physical assets connection offline status in predetermined time. (As default, time of the incoming data interval multiplied by 3) When If its checked, all drop-downs and switches other than asset selection will be inactive. After this checked users can design action side and decide what to do if device becomes offline such as sending text message or triggering another field or sending webhook to another system. **Asset:** Any asset on the users list can be selected here wheter its a digital or physical assets. **Field:** Fields related to selected asset can be selected here.All type of data will be listed here as default without any filtering for `boolean`or `integer` because of that user needs to select non-string field to make logic test and data manipulation relevant. **Data Time:** Since multiple condition checks can be created, user needs to select data time from this drop-down additionally. Similar to rule trigger data frequency selection, user can select "current" mode which triggers with incoming data without any time delay. In addition to current mode user can select time options from the list or can create its on timing. **Value Type:** Value type has 2 option, those are "Single" and "Multiple" data types and it directly works with "Data Time" and "Data Manipulation" selection. If "Single" is selected, condition checker takes first single data point before selected "Data Time" time and process it.If single is selected "Data Manipulation" option will be inactive. If "Multiple" is selected, condition checker will require "Data Manipulation" input and process entire data in "Data Time" selected period according to selected data manipulation algorithm. "Current" option wont be available if "Multiple" is selected.

**Data Manipulate:** It is only active if "Value Type" is selected as "Multiple". It is basically an algorithm service similar to widgets configuration menu and its being used to do sub-calculations for complex analytics. -Average: It takes arithmetic average of all data in time period selected in "Data Time". -Sum: It takes total sum of all data in time period selected in "Data Time". -Minimum: It takes mathematically minimum valued data of all data in time period selected in "Data Time". -Maximum: It takes numerical maximum valued data of all data in time period selected in "Data Time". -Multiply: It multiplies all data with each other in time period selected in "Data Time". -Division:It divides all data with each other in time period selected in "Data Time". -Difference(Range):It calculates absolute difference between maximum and minimum numerically valued data points in the data cluster in time period selected in "Data Time".**Useful to track performance or anomalies.** -Consumption:It calculates absolute numerical difference between last and first data point in time period selected in "Data Time".**Useful to monitor consumption of resources or metering.** #### Logic Test: User can create mathematical logic tests in condition cards as an option to create more complex rule designs. After selecting operator user needs to input value. Condition card will work as a sub logic controller and will jump to next condition card or action side if logic turns out to be `true`

#### Adding Another Condition Card Users can add additional condition card with `And`/`Or` logic gates and crate chain conditions easily.

Using Two Condition Cards With "And" Logic

# Action Fortune favors the bold Action side of the rule editing menu has multiple capabilities to output data according to user need. It also has built in data manipulation and custom calculation capabilities to design more complex data streams based on assets and fields manipulated at condition cards in condition side. Similar to "Condition" side of the rule edit menu it works in card logic which are microservice structure. Action cards can send notifications as Text, Email, Voice Message, or manipulate and write new data in to new fields in selected virtual sensors or trigger web-hooks for Slack, Microsoft Teams and other custom services.

General Action Card Structure (With Notifications)

#### Send Notifications Users can send notifications of output of condition side of the rule as Email, Text or Voice Message. #### Process Data After selecting "Process Data" in "Actions" list user can process and manipulate data which are outputted from "Condition" with single or multiple condition cards. If condition card is only one, only process method is "Custom" process method which enables user to write its own formulation with arithmetic operators.

Processing Data With Arithmetic Operators and Numbers

For multiple Condition cards scenario, other operators act same as in [Condition](/rules-menu/rules-edit-and-frequency/condition) cards. After creating the process method user can use this output to be sent as notification, webhook or it can be used to be set as a new data field in virtual sensor.

To write new data in to data container user needs to select a virtual sensor, than name of the new field and unit of the value needs to be input. #### Sending Webhooks Users can directly send webhooks wheter data is manipulated or not. For this, webhook URL is needed for Slack, Microsoft Teams or custom end points. Please see [integrations ](/integrations)page for more details.

# Sources How to fetch data Sources is the main data ingestion menu compromises most of the data ingestion services with easy to use user interface.

"Sources" are basically assets which represents in this menu as a data flows instead of data itself as in [assets ](/asset)page. User can create new sources (assets) from different connections (incoming server type) with "Add New Source" button. Every source has data source which can be industrial, non industrial, web based or virtual type as a [connection types](/sources/connection-types). With [Network Management](/sources/network-management-lorawan) page, user can manage LoRaWAN or private 5G/LTE (with enterprise license only) networks and monitor network performance. # Connection Types How to fetch data from outside Skysens AgPM provides various data connections. Depending on license type, user can directly establish connections from the menu.

Existing connection types via user interface

Due to high complexity and non-standardization between brands and systems some industrial and non industrial connections can be established only with Skysens Team. Please refer to [support ](/support/custom-software-engineering-and-integration-support)page for more information. # Modbus TCP Skysens AgPM can be connected any Modbus TCP devices. User can configure and start to monitor their data from a Modbus TCP data source. Modbus TCP adapts the Modbus industrial communication protocol for use over TCP/IP networks like Ethernet, enabling data exchange between devices in industrial automation settings via standard network infrastructure.

Adding a Modbus TCP source is three-step process: Source Information, Slave Information and Register Information.

**Source Information** * Services: A list of pre-configured services that can be helpful for load balancing * Name: Descriptive name for your Modbus TCP device * Self Connect (Optional) : Select If your Modbus tcp device supports slave mod that can be automatically connected * Addresses (Optional) : Select a configured IP, Port connection if you add some connections before * IP: Modbus TCP device IP address * Port: Modbus TCP device Port number * TCP-Timeout: TCP connection time out. For Ethernet connection it will be recommended 1s, for GPS connections it will be recommended 10s

**Slave Information** A Modbus TCP connection need to be have a slave ID in order to read data. Slave ID: Slave identifier is used established Modbus Communication. Interval: Data reading frequency (in seconds)

**Register Information** Modbus TCP registers are memory locations within a Modbus device used to store and exchange data; they are addressed for reading or writing various data types, enabling communication between a master and slave devices. You can read multiple registers on a single connection. Field Name: An identifier for register Address: Modbus Register Addresses Such as: 0001,0002 Quantity: Number of reading registers Unit: Reading data's unit Format: Data format. Such as: int32, float # MQTT Skysens AgPM can be connect your MQTT broker and subscribes a topic to receive data. For Adding A MQTT source, select MQTT on add new source menu.

Adding a MQTT source is three-step process: Source Information, Topic Information and Field Information.

**Source Information** To begin receiving device data, we must first establish a connection to an MQTT broker. This broker acts as the central hub, routing messages between the device and our system. Name: Descriptive name for your MQTT device Url: MQTT broker's public host name or IP address Port: MQTT broker's port number If your broker have some authentication method then select "Use Authentication" and enter the details.

**Topic Information** Topic is a string-based address used by the broker to route messages between publishers and subscribers, enabling organized, decoupled communication via a hierarchical structure and optional wildcards.

**Field Information** Field Name: An identifier for MQTT data object Field Key: Key name on MQTT data object Unit: Reading data's unit Format: Data format. Such as: int32, float # HTTP Skysens AgPM can be connect your HTTP server to receive data or generate an endpoint to receive data. For Adding A HTTP source, select HTTP on add new source menu.

Adding a HTTP source is three-step process: Source Information, Endpoint Information and Field Information.

**Source Information** Adding a HTTP source depends on your HTTP server management architecture. You can configure Skysens AgPM can connect your HTTP server and receive data or you can generate a custom integration URL that you can send your data. In second method you do not need to manage a HTTP server, you only need a simple HTTP client that sends data. Name: Descriptive name for your HTPP device If you want to use your HTTP server thats Skysens AgPM will connect your server and receive data. Select the "Use Your Http Server" option on the menu. Url: HTTP server public host name or IP address Port: HTTP server port number Request Type: Select the HTTP request method POST or GET If your HTTP server have some authentication method then select the authentication method according your authentication method; Basic, Bearer Token or Custom header.

If you want to use Skysens HTTP server, you only need to generate a custom URL for your device. Than create a HTTP client that sends request into your generated custom URL.

**Endpoint Information** Endpoint is data set exposed by the server's API, points different functions that returns different responses.

**Field Information** Field Name: An identifier for HTTP data object Field Key: Key name on HTTP data object Unit: Reading data's unit Format: Data format. Such as: int32, float # Device Catalog (LoRaWAN) Selection of devices Skysens LoRaWAN network server and third party LoRa Network Server (LNS) integration comes with large number of LoRaWAN IoT devices. **Currently, only Skysens LoRa Network Server is supported via Network Management and device catalog interface.** Most popular and Skysens tested devices are offered to end user via device catalog. **For devices not listed in the catalog please contact Skysens team. Team will add new devices to the list** **for free**** by your request.** For how LoRaWAN and its configurations work please refer to official LoRa Alliance [document](https://lora-alliance.org/wp-content/uploads/2020/11/RP_2-1.0.2.pdf).

When device is selected there is two option depending on its ownership, "**Already integrated to SKYSENS system**" or "**NOT integrated to SKYSENS system**". If device is already in Skysens database, you need to select "**Already integrated to SKYSENS system**" option. This option usually being used by enterprises which purchases devices directly from Skysens hardware support and/or uses a previously stocked device. If its selected, user only needs to write down EUI number of the device, select LoRaWAN connection method (ABP or OTAA) and select supported LoRaWAN frequency bands (currently EU868 and US915 MHz bands). Other information is already in Skysens system. If device is new and not already integrated "**NOT integrated to SKYSENS system**" needs to be selected.

Selecting Not Integrated Device with OTAA Joining Method

If device is not integrated, and uses OTAA, user needs to input Application EUI, Application Key, Class (ARX1, ARX2, CRX2),RX2 Frequency Window (869.525 MHz or 923.300 MHz) as addition. If it is ABP user will be asked for Device Adress, Network Session Key, Application Session Key as a difference.

Selecting Not Integrated Device with ABP Joining Method

# Network Management (LoRaWAN) LoRaWAN Network Management Managing a LoRaWAN network involves monitoring gateway connectivity and data flow, configuring devices with sending downlinks . Help to track gateway status, location and activity. **Currently, only Skysens LoRa Network Server is supported.** Can be divided by two main components gateway and device. # Gateway

* Gateway Activity help to virtualize timeline of gateway package traffic over time. * A google map that help to display geographic location of gateways #### Gateway List

* **Name:** The user-assigned, descriptive name of each gateway (e.g., "Yedek\@Istanbul"). * MAC: A Unique identifier, used for LoRaWAN network * IP Address: An IP address, shows last LoRaWAN network connection * Last Keep Alive: A time that last connection made by gateway onto LoRaWAN network * Total Data: Count of last receive data packages * Last Data Send Time: Last data package receive time * Edit/Delete Gateway: Helps to edit gateway details or remove from LoRaWAN network. #### Add Gateway Before connecting a LoRaWAN gateway to Skysens, ensure it supports LoRaWAN and set its LNS URL to Skysens' address, which enables data communication. Please refer to [support ](/support/custom-software-engineering-and-integration-support)page for more information. Adding a new gateway you need to fill information on menu.

* Gateway Name: Write a decriptime name for your gateway * MAC Address: The unique intentifier can be found on configuration file or a sticker on the gateway. * Backhaul Connection: Select a type of connection that gateway connect with, such as "LAN", "GSM" etc.. * Band: Select the correct band for your region and gateway; Skysens LNS currently supports European(EU868) and US(US915) bands.

* Map Types: Select a map type that track to your location of gateway. You can select a google map option or upload a floor plan and map the location of gateway.

* Select Users or User Groups from list if you want a notification about gateway when it went offline. * You can also add some note or images about installation of gateway. # Device #### Device List

* Device ID: A unique identifier for your device * Battery: Last battery level of device * SNR (Signal-to-Noise Ratio): SNR quantifies the clarity of a signal by comparing its strength to the background noise, revealing its quality * RSSI (Received Signal Strength Indicator): RSSI measures the raw power of a received radio signal, indicating its strength * Last RX: Last time of a package received from device * Status: Indicates devices status #### Send Downlink You can send a downlink a device or track your downlink history for a device. The downlink history provides a record of sent downlink messages, showing the message content, port, status, date, and any received responses.

* Port: Data is directed to the device via the LNS through this designated Port. Such as: "11" (Integer) * Downlink: Your downlink message. Such as: "020000000C" (Hexadecimal) # Virtual Sensor Virtual Sensors are virtual assets explained in [asset types](/asset/asset-types#virtual-assets). It creates an option to you create a source without a physical device representation. There is three type of virtual sensor: Virtual Value, Virtual Form, Virtual Simulation. Virtual Value is often used when you need a empty sensor that you can set output of a rule without interacting with physical device data. Virtual Form is often used when you want a simple placeholder sensors that store constant data. You can enter your constants or variable within a simple form. Simulation is a virtual representation of a physical device or a situation with some custom configurations.

# Value Virtual value

For Adding A Virtual Value source, select the Value on the option selection. Name is a decriptive name for your Virtual Value device # Form

For Adding A Virtual Value source, select the Value on the option selection. Name is a decriptive name for your Virtual Value device

# Simulation Simulate data from the selected device to test visualizations, dashboards, or data processing workflows without needing a physical device.

For Adding A Virtual Value source, select the Value on the option selection. Name is a descriptive name for your Virtual Value device Than select physical copy of you want to generate or you can create your own simulation data object.

Data Frequency: Define how often the virtual sensor should generate data. Configure sensor range configuration: Based on your device selection from catalog set ranges for sensors that can be used in simulations. You can select a randomize range or type a custom range for a given sensor. # Settings Where you change things Settings menu is main configuration menu for user, timezone, language, location and user roles and groups.

# Account Settings

Depending on their user level, users can change their name, phone number (with country code), time zone and preferred language. **Timezone also effects data and back-end services times and wrong selection may cause significant errors.** # Location Management (Settings)

Location enables users to create physical locations for physical and digital assets and manage them on satellite and floor plan maps. These location data then can be used in [map ](/main-menu-and-overview/widget-types/map)widget in overview section for visualization. Each location have global map position and floor plan and assets related to it.

# User/Role Management (Settings) User and role management provides simple and advanced capabilities for AgPM users. Firm code is the main enterprise code and users are belong to that firm codes in user base hierarchy in AgPM. In order to create entirely isolated user base, new firm code needs to be issued.Otherwise "Admin" level users can see entire user base from user list. Highest user level is "Admin" and it followed by "Supervisor", "User" and "Demo"

If user has "Admin" role, entire user base can be managed from a single list. User can create groups, assign users to these groups, change other users roles, change status of users from "active" to "passive" mode and hold their credentials, delete or add users, assign assets to these users.

Admin and Supervisor users can assign assets to different users. This way, users can manage their teams responsibility and data access. Admin and Supervisors also can create groups and assign different users to these groups.With this, team structure can be created easily and efficiently for work shifts, responsibility areas, data access. After adding new user group, new users can be added to group via number of groups drop down or user editing.

# Reports Reporting for duty Reports is the main data reporting engine for the AgPM. Users can create schedule recursive reports or create one time reports in PDF or XLS (custom report types only) formats and assign report receivers easily. Reports capability mostly being used by mid level management to check systems general functionality in daily or weekly or monthly basis. With combination of rules, virtual sensors and reports, users can have limitless reporting capabilities.

### Recursive (Scheduled) Reporting In addition to one time reports users can schedule recursive reports and create automatic reporting for selected times and time periods. In custom and application report types users can create recursive reporting for every day, every week, every month or every month.

Scheduled Reporting (For Custom and Application Report Types)

In recursion settings, user needs to set when report will be created and send. For asset and overview reporting scheduling time period is same with data range.

## Reporting Types There are 4 main reporting type is available generally for AgPM users. These are Overview(Alerts), Assets, Custom Type and Application reports. Every reporting type has distinct capability and can be facilitate for users for various reasons. **In addition to existing types, Skysens Team can add new report types depending on user requests.For inquiries related to new reporting requirements, please contact.** ### Overview (Alerts) Reports This report type gives all major and minor alerts for all assigned assets in selected data range. Users can see total breakdown of assigned assets, number of their alerts, assigned users on single PDF file. Depending selected date range, report can be recursive to be sent selected users. This report type is useful to track overall system performance, alerts and anomalies and general user information on scheduled basis.

### Asset Reports This report gives alerts, warnings, general information which consists daily maximum,minimum and average readouts of selected asset. This report type is useful to track assets conditions, alerts and general parameters in automated manner.

### Custom Reports Custom reports are very flexible reporting type which users can select related assets, fields in the assets and different color templates. Since asset fields can be re-programmed to be include different alarming and AI outputs, users can create their own advanced reporting capabilities with using together of rules, virtual sensors and reporting feature.For more information please check [reporting best practices](/reports/advanced-reporting) page.

### Application Reports Application reports are specifically designed reports for different [application ](/asset/application)types. In example, energy consumption report can be used if energy application already created from asset menu.This report will include general energy consumption, scope 1-2 carbon footprint, energy costs, active and reactive energy readouts with asset details and sub domains in the facility. Currently, energy consumption report is available for enterprise users, for other types, please contact **Skysens Team**.

# Advanced Reporting Tips and tricks for better reports ## Using Rules and Virtual Sensor Capabilities for Genuine Reporting Reporting can be used for various reasons. Some AgPM users use reports for weekly or monthly system reporting to see general system trends and raw data.However, to have best outcome, Skysens recommends to create virtual assets with rule and AI engines capabilities. This way, various scenario can be accomplished without constrained of reports section.

In example, user can select various energy related assets, program rules engine to analyze daily consumption, write it on to virtual sensor than select virtual sensor particular field to report. **Step 1:** Create a rule which calculates daily energy consumption of various assets and write it to a virtual asset field.

**Step 2:** Select that vitual asset field and use it as daily reporting engine with custom reporting.

Create a custom report for created virtual asset field

With this strategy, reporting engine can be used extensively for various scenarios. # Logs See what is going on Logs is available for admin users, is area to see what is going on in terms of output and users.

As default admin users can check email and text message outputs in real time and historically. For users with enterprise license logs can directly integrated via `WEBHOOK`and `REST` In addition to third party consumption, several other loggin options is available for enterprise users such as rules and user activity. # Integrations # API # AI # AgPM AI Concept # Application Specific Models # Statistical Models # AI Agents (Upcoming) # Licensing # Support Always on duty Depending on platform edition, Skysens Team provides support levels customized for user profiles.

These support levels includes maintenance support, training, and consultancy. Free and Premium editions have standardized support and consultancy packages, however, enterprise supports usually designed according to user need. # Response Time and Channels # Training # Hardware Support # Custom Software Engineering and Integration Support # Consultancy # Hardware and Network Consultancy # Data Mapping and AI Consultancy # Sustainability Consultancy and CoSIRI # Example Projects Examples through history With end to end integrations, AI and wireless IoT infrastructure there are many different project can be given as an example. However, for interesting takeaways, several projects will be mentioned in details here.

Standard Integration Levels of Skysens AgPM

# Thermal Optimization of Factory Floor # Remote Metering for Housing Community # Predictive Maintenance for Factory # Equipment Performance Analysis in Shipbuilding # Steam System Digital Twin With Steam Trap Monitoring