Seismi Cattle Control User Guide

Seismi Cattle Control brings cattle identity, location, health warnings, vaccination, treatment, sales, integrations, and system monitoring into one workspace. This guide explains what each area is for, what the main statuses mean, and how the areas work together.

The features visible to you depend on your role and permissions. If a menu item described here is unavailable, contact your organization administrator.

Screenshots in this guide illustrate the relevant workflow. Minor spacing, data values, and controls may differ between releases and permission levels.

Getting started

Sign in

Open https://iot.seismi.co/. The sign-in service returns you to Seismi Cattle Control after authentication. If you were sent a link to a specific page, successful sign-in should return you to that page.

The default interface language is English. You can change the language later from the menu under your profile image.

Understand the page layout

• Use the left navigation menu to move between functional areas.
• Use Page Search in the header to find an available page by name.
• Select Help to open the section of this guide for the page you are viewing.
• Open the profile menu to view your information, change language, or sign out.

Accounts and permissions

Organization and user-management pages are permission-controlled. Administrators may be able to create users, assign workplaces, and configure permissions. Standard cattle-operation users may not see these pages.

When creating an account, choose the delivery method that matches your security process:

• Email invitation sends the user an account activation or sign-in message.
• Password reset link lets the user set a private password without the administrator knowing it.
• Temporary password is appropriate only when your organization has a secure way to deliver it and requires the user to replace it.
• No credential message creates the account without sending access information; use this only when credentials will be delivered through another approved channel.

Location overview

The Location Overview provides a quick operational summary for the selected location. It combines server-resource status, the current map, fence warnings, and low-power warnings.

The Status chart shows CPU, memory, and disk utilization as percentages from 0% to 100%. Short, small changes are normal. Use the chart to notice sustained high utilization rather than reacting to a single point. Backend and frontend version information appears below the chart for support and troubleshooting.

The map is blank when there is no configured scene, no station data, or no valid tag coordinates. Coordinates that are missing or invalid are ignored instead of being plotted.

Scenes

A scene represents a physical cattle area, such as a pen group, barn, or facility map. Scene configuration determines how location data is presented in that area.

Authorized users can configure the scene background map, dimensions, rotation, base-station positions, tag appearance, and optional 3D assets. Confirm the dimensions and station positions before relying on displayed cattle locations. Changes to a scene affect every user who opens that scene.

Real-time location

Use Real-time Location to see the latest valid position of each connected cattle tag.

• Select the correct scene before interpreting positions.
• In 2D mode, markers show positions on the configured facility map.
• In 3D mode, cattle labels display the cattle name when available; otherwise they display the ear-tag identifier.
• The information panel shows health status, heart rate, respiratory rate, temperature, blood oxygen, activity, and coordinates when those values are available.
• Click a cattle model or its information panel to focus and move the camera closer.

An empty or --- value means the measurement is not available. It does not by itself mean the animal is unhealthy.

History track

History Track answers two different questions:

1. Where was the animal at the selected time? Selecting a date and time immediately loads the closest available positions. You do not need to press Play to see the initial positions.
2. How did the animal move after that time? Press Play to advance the selected time continuously. Pause, speed, previous-hour, and next-hour controls help inspect the period of interest.

If no cattle appear, confirm that the correct scene is selected and that the tags reported valid positions during the selected period.

Stations and tag devices

Base stations receive data from cattle tags and provide the reference points used for location. Tag devices are the physical sensors assigned to cattle.

Use the device pages to confirm assignment, connectivity, battery state, and recent data. A device may exist without showing a cattle name if it has not been assigned. A cattle record may exist without live measurements if its tag is offline or unassigned.

Measurement data ranges

Choose a data source and time range based on the question you are answering:

• Real-time data is best for checking whether a device is currently reporting. A short window such as 30 seconds focuses on the newest samples, but a longer window may be necessary when tags upload intermittently.
• Historical data is best for reviewing a completed measurement or comparing a longer period. Select a range that includes the expected recording time.

The time-range control changes how much data is displayed; it does not change how the device measures or uploads data.

Cattle management

Use Cattle Management to maintain the operational identity of each animal and its relationship to a tag and pen.

• Add one cattle record when registering an individual animal.
• Use bulk import when onboarding many animals from an approved template.
• Assign the correct ear tag so location and health data can be associated with the animal.
• Give the animal a name when your operation uses names. Where no name exists, the interface shows the ear-tag identifier instead.

An ear-tag value such as 6892 is therefore not an automatically generated cattle name; it is the fallback identifier for an unnamed animal.

Alarms

Alarm Pens summarizes warning counts by pen. Alarm Cattle lists individual animals, symptoms, score, severity, time, and available actions.

• High requires prompt review.
• Medium indicates a condition that should be monitored or assessed.
• Symptoms may contain a full observation and wrap onto multiple lines.

An alarm is decision support, not a diagnosis. Confirm the animal's condition using your operation's inspection and veterinary process. Use the available action to open the related treatment information when follow-up is required.

Vaccination records

A vaccination record is a planned vaccination group. Create the record first, add the vaccines and dose per head, and then add the cattle that must receive that vaccination.

• Processing means at least one cattle assigned to the record has not yet been marked as vaccinated.
• Completed means every cattle assigned to the record has been vaccinated.

The record date currently represents the time recorded by the system. If you are entering vaccinations performed earlier, confirm your organization's back-entry process before relying on that date as the administration time.

Open Vaccine Information to review the vaccine list, doses, batch information, notes, cattle, and per-cattle status.

Treatment records

Treatment records connect a cattle health concern with the actions taken to address it. The active-treatment list shows the cattle identifier, symptoms, treatment, description, time, and available actions.

Use the cattle name when one exists. If it does not, the ear-tag identifier is displayed. Open the treatment detail to review the animal's treatment history rather than relying only on the latest row.

Sales records

Sales records track buyer, unit price, target quantity, sold quantity, total weight, and total amount. A processing status means the planned group has not been fully completed; a completed status means all planned cattle have been processed for the sale.

Integration management

Integrations connect Seismi Cattle Control with an approved external cattle platform.

1. Select Add Integration.
2. Choose the platform and enter the required credentials.
3. Use Test Connection to verify that the credentials and remote service are working.
4. Save the integration only after the test succeeds.

Ping latency is the response time of the connection test, not a cattle health measurement. Disabling an integration stops synchronization without deleting its configuration. Deleting an integration permanently removes the saved configuration.

Never share API keys or secrets in screenshots, email, or support messages.

Clinical tests and data analysis

Clinical Test and Data Analysis pages are intended for authorized users reviewing measurement files and study data. Uploaded ECG files include creation time, measurement start time, duration, and actions such as view or download.

Use the file's measurement start time when matching it to a test session. Creation time only tells you when the file entered the platform.

System status and settings

System Status summarizes file usage and recent file activity. Storage values use the unit displayed beside the value. Thirty-day charts help identify growth trends rather than cattle health conditions.

System Settings pages are available only to authorized administrators. Email configuration controls operational notifications, while file-service configuration controls where uploaded files are stored. Test changes before depending on them in production.

Profile and language

Open your profile image and select My Information to review account details. Language is also located in this menu so it does not distract from operational pages. English is the default language for new browsers.

Account ID editing is intentionally unavailable. Stable account identifiers reduce integration, audit, and login edge cases.

Notifications and support

Success messages describe the action and affected object, for example, “Integration Performance Beef updated successfully.” If an operation fails, keep the page open and record the action, object name, time, and visible error before contacting support.

When requesting support, include:

• The page name and scene.
• The cattle name or ear-tag identifier, when relevant.
• The time the issue occurred.
• The expected result and actual result.
• Backend and frontend versions from Location Overview.

Do not include passwords, API secrets, session tokens, or personal credentials.