Welcome to 313fm.com
Cloud-based Inspection and Patrol System
Follow the tutorial and kick off your 313FM inspection journey in just 10 minutes. The entire 313FM system consists of two core components:
1
Cloud Backend System
2
Mobile App
- The Cloud Backend System is designed to manage users’ inspection routes, frequencies, and reports. This tutorial provides a detailed walkthrough of the setup process for the Cloud Backend System.
- The Mobile App serves as the execution terminal for inspection operations, primarily for use by on-site inspectors. It automatically assigns work orders to inspectors’ Mobile App accounts based on the inspection plans configured and work orders created by users in the Cloud Backend System.
Preparations - Log in to the Cloud Backend System
Click the “Login” button on the official website’s navigation bar to be redirected to the Cloud Backend System login portal for access.
You can also use a computer browser to visit the following URL for login:
https://inter.313fm.com/#/login?langcode=EN
If you don’t have an account yet, you can click the button below to contact us and obtain a trial account.
Step 1 - Create Property Entity
The Property Entity is the foundation of all Inspection Points/Routine Tasks. Any operations of the system, such as Inspection Point Setup, Route Planning, and Statistics Analysis, fall under the selected Property Entity.
User must first create a “Property Entity” to perform subsequent actions.
The 313FM platform supports managing multiple projects with a single account, facilitating the development of enterprises and groups.
STEP 2 - Create User Accounts
The account used is for personnel within the property entity, and all patrol inspection personnel, work order processors, etc., need to perform tasks through the use of this account.
The user account can be set up based on roles, such as “Daily Patrol Inspector No.1”; it can also be set up according to the individual’s name, for instance, “Tom.”
Even if the account is set up by role, the executing personnel are still required to sign off on the completion of inspection tasks for verification purposes, ensuring that the company is aware of who the actual executor is.
STEP 3 - System Login
Data Administrator or Property Manager, may need to use the Web interface more often because some functions are not available on mobile APP.
For example, Data Administrator will access the system to modify the data and add a new user account, Property Manager to create inspection plan and access the report.
Normal User, responsible for inspection order execution, would mainly login to the mobile APP.
Step 4 - Inspection Point Maintenance
After creating Property Entity and User Accounts, you also need to define the “Inspection Points”. An Inspection Point refers to a location that requires check-in when personnel perform inspection and patrol tasks within a Property Entity, or assets such as facilities and equipment that need regular inspections.
Each Inspection Point is assigned a unique On-Site Tag. This setup ensures that inspectors must reach the corresponding location to initiate an inspection, and also captures key information such as the inspectors’ arrival time at the point.
The On-Site Tag supports QRCode, NFC, Bluetooth, and GPS.
STEP 5 - Create Inspection Plan
After setting up the Inspection Points, you need to create “Inspection Plan”.
In enterprise management, a task that requires regular execution is defined as an Inspection Plan.
The Inspection Plan defines who, when and where to patrol or inspect, as well as the specific inspection items to be carried out.
Mobile App Inspection
We have completed all configurations related to Inspection Plans in the Cloud Backend System. Next, follow the tutorial to experience the practical inspection process on the Mobile App.
Mobile APP – Part 1
Mobile APP – Part 2
More Features
In addition to the basic configurations above, more functional modules await your exploration.
Video Tutorial: Duty Logbook
Video Tutorial: Visitor Management
Video Tutorial: WorkOrderManual