Connecting the Dots: Leveraging Integrations & IoT with FMX

Executive Summary

Facilities and operations leaders face a common challenge: valuable data exists across multiple systems, but those systems don’t communicate with each other. Work orders live in one place, building automation data in another, and accounting in a third. Your team spends countless hours manually transferring information between systems, and critical insights remain locked away in isolated silos.

The promise of integrations and IoT (Internet of Things) is simple: connect your systems so data flows automatically where it’s needed, when it’s needed. This connectivity transforms how your organization operates—reducing manual data entry, enabling automated workflows, and providing the real-time visibility that allows you to prevent problems rather than just respond to them.

At FMX, we believe the path forward isn’t adding more standalone tools—it’s bringing your existing tech stack together into a connected ecosystem that serves your operations team, not the other way around.

Leveraging integrations and IoT can help you achieve:

• Automated workflows that eliminate repetitive manual tasks
• Real-time visibility into building performance and asset health
• Data-driven decisions powered by information from across your organization
• Proactive maintenance triggered by actual conditions, not arbitrary schedules
• Cross-departmental collaboration, enabled by shared information

The Connected Facility: Moving Beyond Standalone Systems

In practical terms, this might mean:

• Your building automation system (BAS) detects a temperature anomaly and automatically creates a work order in FMX
• A completed work order in FMX triggers an invoice in your accounting software
• IoT sensors monitor equipment runtime and automatically schedule preventive maintenance when thresholds are reached
• Your single sign-on (SSO) system manages user access across all platforms
• Athletic scheduling software shares your practice and game schedule with a central calendar

Why Connection Matters

The shift from standalone systems to connected ecosystems addresses several critical pain points:

Eliminating Double Entry

Every time your team manually transfers information from one system to another, you’re introducing opportunities for errors, delays, and wasted time. A connected ecosystem eliminates this redundant work.

Breaking Down Silos

When data lives in isolated systems, different departments operate with incomplete information. Connections ensure everyone has access to the full picture while still restricting the ability to modify powerful systems like your BAS.

Enabling Automation

The real power of connected systems isn’t just data sharing—it’s automated action. When systems can trigger each other, workflows that used to require human intervention can happen automatically.

Shifting from Reactive to Proactive

Standalone systems tell you what happened. Connected systems—especially with IoT—tell you what’s happening right now and what’s likely to happen next, allowing you to act before problems escalate.

Understanding Integrations: Connecting Your Software

Common Integration Types in FMX

Integrations can connect FMX with various categories of systems:

Business Systems

These are the administrative and financial tools your organization uses daily:

Accounting, ERP, Financial Software (QuickBooks, Workday, Oracle, etc.)

• Automatically sync vendor information
• Link work orders to the correct Purchase Order
• Generate invoices based on completed work orders
• Track maintenance spending against budgets
• Eliminate manual entry of financial data

Single Sign-On (SSO) Providers (Okta, Google, Microsoft)

• Streamline user access management
• Enhance security through centralized authentication
• Reduce IT overhead for password management
• Ensure consistent access policies across platforms

Mobile Device Management (MDM)

• Automatically provision and deprovision user access to FMX
• Synchronize user attributes and organizational structure
• Streamline device management for students and staff

Building Systems

Building Automation Systems (BAS) and Access Control

Your BAS manages HVAC, lighting, and other building systems, while your access control system manages building entry. Integrating them with FMX allows:

• System scheduling based on your event schedules (e.g., automatically turn HVAC on/off and lock/unlock doors)
• Automatic work order creation when systems operate outside normal parameters
• Historical performance data attached to assets
• Better tracking of energy consumption by specific assets (coming in the future)

Integration Management: Control Without Complexity

Modern platforms give you visibility and control over your connections. In FMX, you can:

• Monitor integration health to catch issues before they impact operations
• Configure data flows without writing code
• Audit data exchanges for compliance and troubleshooting
• Enable or disable integrations based on changing needs

This centralized management means you’re not dependent on our staff to manage the integrations on your site.

Building Custom Integrations

While FMX offers pre-built integrations for common systems, you may have unique tools specific to your organization or industry. FMX’s API (Application Programming Interface) allows your IT team or a developer to build custom integrations.

The basic concept:

1. Identify what data needs to flow between systems
2. Use FMX’s API documentation to understand available endpoints
3. Write code that exchanges data according to your specific requirements
4. Test thoroughly before deploying to production

While building custom integrations requires technical expertise, the investment pays dividends when you can connect specialized systems that are critical to your operations.

Understanding IoT: Connecting Your Physical Assets

IoT in Facilities Management

Common IoT applications in facilities and operations include:

Environmental Monitoring

• Temperature and humidity sensors
• Air quality monitors
• Water leak detectors
• Occupancy sensors

Asset Performance Monitoring

• Equipment runtime trackers
• Vibration sensors (indicating potential mechanical issues)
• Energy consumption monitors
• Predictive failure indicators

Safety and Security

• Access control systems
• Emergency notification devices
• Hazardous condition detectors (gas leaks, fire, etc.)

How IoT Data Transforms Operations

The value of IoT isn’t just in collecting data—it’s in acting on that data automatically.

Threshold-Based Triggers

IoT sensors can be configured to trigger actions when readings exceed defined thresholds:

Example: Temperature Monitoring

• A freezer’s temperature sensor detects readings above safe levels
• The IoT system sends data to FMX
• FMX automatically creates a high-priority work order
• The maintenance team receives immediate notification
• The issue is addressed before inventory is lost

Example: Equipment Runtime

• A sensor tracks hours of operation on a critical piece of equipment
• When runtime reaches the manufacturer’s recommended service interval, FMX automatically schedules preventive maintenance
• The maintenance team receives advance notice and can order parts
• Service happens during scheduled downtime, not as an emergency

Real-Time Visibility

IoT dashboards provide operations teams with live information:

• Current status of critical systems across all facilities
• Trending data that reveals developing issues
• Historical comparisons that identify seasonal patterns
• Geographic views showing which buildings or zones need attention

This visibility allows you to prioritize resources based on actual conditions, not guesswork.

Predictive Maintenance

By analyzing patterns in IoT data over time, you can predict failures before they occur:

• Vibration patterns
• Energy consumption changes that suggest efficiency loss
• Performance degradation that precedes complete failure

Predictive maintenance is the ultimate expression of proactive operations—fixing things before they break, not after.

IoT Platform Examples

Monnit

Wireless sensors for temperature, humidity, water detection, and more. Easy to deploy without extensive infrastructure.

Samsara

Fleet and asset tracking with robust IoT capabilities, commonly used for vehicle maintenance and mobile equipment management.

Building Automation Systems (BAS)

Many modern BAS systems include IoT capabilities or can be enhanced with IoT sensors to provide more granular data.

Real-World Impact: Customer Success Story

Teays Valley Local School District: Humidity Alarm Integration

The Challenge

Teays Valley Local School District operates multiple school buildings where environmental conditions directly impact student and staff comfort, as well as the performance of sensitive equipment. Humidity levels outside acceptable ranges can damage technology equipment, library materials, musical instruments, promote mold growth, and create uncomfortable conditions for students and staff.

Previously, humidity alarms from the building automation system required someone in facilities to notice the alert, manually document it, and then create a work order in FMX. This process introduced delays and the risk that alarms might be missed during busy periods or after hours.

The Solution

Teays Valley integrated its humidity monitoring system with FMX:

• Humidity sensors continuously monitor conditions in critical areas
• When readings exceed defined thresholds, the system automatically creates a work order in FMX
• The work order includes the specific location, current reading, and priority level
• Maintenance technicians receive immediate notification
• The work order captures a complete record of the incident and response

The Results

• Faster response times: Maintenance team addresses issues within minutes, not hours
• Complete documentation: Every humidity alarm has an associated work order with full details
• Proactive problem-solving: Pattern analysis reveals areas with recurring issues that need systematic fixes
• Peace of mind: Leadership knows that environmental conditions are continuously monitored and issues are immediately escalated

This integration exemplifies the power of connecting IoT sensors with a computerized maintenance management system (CMMS)—transforming raw data into automated action.

Getting Started: Building Your Connected Ecosystem

Step 1: Identify Integration Opportunities

Start by asking your team these questions:

What data do you enter manually into multiple systems?

If your team is typing the same information into FMX and another system, that’s a prime integration candidate.

What other software do you use daily?

Make a list of all the systems your operations team interacts with regularly. These are your integration targets.

What building systems do you wish could “talk” to FMX?

Your BAS, access control, energy management, and other building systems may already have integration capabilities.

What tasks do you do “every day” that feel like they should be automatic?

Repetitive workflows are excellent automation candidates once the right connections exist.

Step 2: Prioritize Based on Impact

Not all integrations deliver equal value. Prioritize based on:

Frequency: How often does this manual process occur?

Time savings: How much time would automation save?

Error reduction: How often do mistakes happen in manual data transfer?

Strategic value: Does this integration enable new capabilities, not just save time?

Start with high-frequency, high-impact integrations that will deliver quick wins and build momentum.

Step 3: Start With Pre-Built Integrations

FMX offers pre-built integrations for common systems. These typically require configuration rather than custom development:

• Work with your FMX customer success team to identify available integrations
• Follow implementation guides to configure connections
• Test thoroughly with a small group before rolling out organization-wide
• Train staff on new workflows enabled by integration

Step 4: Consider IoT for High-Value Assets

You don’t need to instrument everything. Focus IoT deployment on:

Critical systems: Equipment whose failure significantly impacts operations

High-cost assets: Expensive equipment where predictive maintenance justifies sensor investment

Problem areas: Locations or systems with recurring issues that need better monitoring

Safety-critical applications: Where real-time monitoring protects people or property

Start with a pilot deployment on one or two assets, prove the value, then expand.

Step 5: Build Custom Integrations When Justified

For specialized systems without pre-built integrations, consider custom development when:

• The system is mission-critical to your operations
• Manual data transfer consumes significant staff time
• The integration enables capabilities not otherwise possible
• You have technical resources (internal IT or a development partner)

Custom integrations require upfront investment but can deliver long-term value for truly unique needs.

Best Practices for Integration and IoT Success

Involve the Right Stakeholders

Successful integrations require collaboration across departments:

• Operations staff who understand workflows and pain points
• IT teams that manage systems and security
• Finance when integrating accounting systems
• Leadership to secure resources and organizational buy-in

Don’t let integrations be purely an IT project—the people who use the systems daily must be involved.

Start Simple, Then Expand

Begin with straightforward integrations:

• One-way data sync before attempting two-way synchronization
• Monitoring and alerts before automated action

Prove value with simple implementations, build expertise, then tackle more complex integrations.

Document Everything

Create clear documentation:

• What systems are integrated and how
• What data flows between them
• Who to contact when issues arise
• Step-by-step troubleshooting guides

This documentation is essential for training new staff and maintaining integrations over time.

Plan for Ongoing Management

Integrations aren’t “set it and forget it”:

• Workflows evolve, and integration requirements shift
• Integration health needs regular monitoring
• Staff changes require knowledge transfer

Build ongoing integration management into your operational planning.

Secure Your Connections

Work with IT to ensure:

• Integrations use secure authentication methods
• Data in transit is encrypted
• Access to integration configurations is restricted to authorized personnel
• Integration activities are logged for audit purposes

Security cannot be an afterthought when connecting systems.

Set Realistic Expectations

Be honest about:

• Implementation time: Complex integrations take longer than anticipated
• Change management: Staff need time to adapt to new workflows
• Imperfect data: Historical data quality issues may surface during integration
• Ongoing refinement: Initial integrations often need adjustment based on real-world use

Measure and Communicate Value

Track metrics that demonstrate integration impact:

• Time saved on manual data entry
• Reduction in data errors
• Faster response times to issues
• Improved visibility leading to better decisions
• Cost avoidance from predictive maintenance

Share these results with stakeholders and leadership to build support for further investment.

Common Challenges and How to Overcome Them

“Our systems are too old to integrate.”

The reality: Even legacy systems often have some integration capability—file exports, database access, or simple APIs. If direct integration isn’t possible, middleware solutions can bridge the gap.

The approach: Start with what’s possible today. Modern systems can be prioritized for integration while you plan replacements for truly unintegrable legacy systems.

“We don’t have the IT resources for this.”

The reality: Many integrations don’t require extensive IT involvement, especially pre-built connectors. For custom integrations, consider partnering with a development firm.

The approach: Focus first on pre-built integrations that require configuration rather than development. Build internal capability gradually.

“We’re worried about data security.”

The reality: Properly implemented integrations can actually improve security by centralizing authentication and creating clear audit trails.

The approach: Work with IT security from the beginning. Use established integration platforms with strong security credentials. Follow best practices for API key management and access control.

“Integration projects always take longer than expected.”

The reality: Complex integrations do often exceed initial timelines, especially when data quality issues surface.

The approach: Start with pilot projects that have clear scope. Build in time for testing and refinement. View initial implementations as learning opportunities that inform larger rollouts.

“What happens if the integration breaks?”

The reality: Integrations can fail due to system updates, network issues, or configuration changes.

The approach: Build monitoring and alerting so you know immediately when integrations fail. Have clear rollback procedures and manual processes as backups. Use integration platforms that provide visibility into connection health.

“Our staff is resistant to changing workflows.”

The reality: Change is difficult, especially when current processes are familiar.

The approach: Involve staff in identifying integration opportunities. Demonstrate how automations eliminate their least favorite tasks. Provide thorough training and support during transitions. Celebrate early wins.

The Path Forward: Your Connected Future

From Complexity to Clarity

The promise of integrations and IoT isn’t adding more technology—it’s using technology to reduce complexity. When your systems work together seamlessly:

• Your team spends less time on administrative tasks and more time on meaningful work
• Decisions are based on complete, real-time information rather than fragmented data
• Problems are caught early and addressed proactively
• Workflows are consistent and reliable, not dependent on individual memory
• Your organization operates more efficiently with existing resources

Starting Your Journey

You don’t need to connect everything at once. Start with:

1. One integration that addresses a clear pain point
2. One IoT application on a critical asset or problem area
3. Clear measurement of impact and value
4. Broad communication about results
5. Iterative expansion based on lessons learned

The organizations that thrive in the coming years will be those that embrace connectivity—not as a technology project, but as a fundamental shift in how operations work.

Three Actions You Can Take This Week

1. Audit Your Current State

Make a list of:

• All software systems your operations team uses
• Building systems that generate data or alerts
• Manual processes that involve transferring data between systems
• Critical assets that would benefit from continuous monitoring

2. Have a Team Conversation

Gather your operations team and ask:

• What manual tasks feel unnecessarily repetitive?
• What information do you wish you had that currently lives in another system?
• What problems do you learn about too late?

3. Explore Available Integrations

Connect with your FMX customer success team to:

• Review pre-built integrations that match your systems
• Discuss IoT platforms commonly used in your industry
• Understand implementation requirements and timelines
• Identify quick wins that can demonstrate value

Conclusion: The Connected Ecosystem Advantage

Transformation, Not Just Technology

Building a connected ecosystem isn’t about accumulating more software or sensors. It’s about transforming how your organization operates by ensuring the right information reaches the right people at the right time—automatically.

When your systems work together:

• Data flows where it’s needed without manual intervention
• Actions happen automatically based on real conditions
• Your team focuses on solving problems, not managing software
• Leadership has visibility into operations across all facilities
• Your organization operates proactively rather than reactively

This transformation doesn’t happen overnight. It’s built through thoughtful, incremental connections that deliver clear value and build momentum for broader change.

The Takeaway

The question isn’t whether to build a connected ecosystem—it’s how to do so strategically, starting with high-impact integrations and expanding as you demonstrate value.

You don’t need to be a technology expert. You need to be what you already are: someone who understands your operations, knows your team’s pain points, and can identify where eliminating manual work and gaining better visibility will create the most value.

The future of facilities management is connected. The only question is how quickly you’ll get there.

Additional Resources

Connect With FMX

• Explore available integrations in FMX
• Schedule a consultation with your FMX customer success team
• Review API documentation at <hostname>.gofmx.com/api for custom integration development

Questions for Planning

Use these questions to guide your integration and IoT strategy:

Integration Planning

• What systems does our operations team access daily?
• Where do we manually enter the same data in multiple places?
• What cross-departmental workflows could benefit from shared data?
• Which integrations would eliminate the most friction for our team?

IoT Planning

• What assets are most critical to our operations?
• Where do we have recurring problems that need better monitoring?
• What environmental conditions impact our buildings or operations?
• Which equipment failures create the biggest disruptions or costs?

Implementation Planning

• Who needs to be involved in integration decisions?
• What security or compliance requirements apply to our integrations?
• How will we measure and communicate the value of connections?
• What’s our plan for ongoing integration management and support?

Appendix: Learning to Build Integrations with LLMs

Large Language Models (LLMs) like Google Gemini, ChatGPT, and Claude can be powerful assistants when building custom integrations. Here are resources to help you leverage AI for integration development:

Getting Started with LLMs for API Integration

• Google AI Studio – Free environment for prototyping with Gemini models
• OpenAI Playground – Interactive environment for experimenting with ChatGPT
• Anthropic Console – Workspace for building with Claude

Prompt Engineering for Integration Tasks

• OpenAI Prompt Engineering Guide
• Google’s Introduction to Prompt Design
• Anthropic’s Prompt Engineering Guide

Using LLMs to Understand and Work with APIs

LLMs can help you with integration tasks such as:

• Understanding API documentation and identifying relevant endpoints
• Writing code to authenticate with APIs and make requests
• Parsing and transforming data between different API formats
• Debugging integration issues and error messages
• Generating webhook handlers and event processors

Practical Tips for Using LLMs in Integration Development

• Provide context: Share relevant API documentation snippets with the LLM
• Be specific: Clearly describe what data you’re trying to move between systems
• Iterate: Start with simple requests and build complexity gradually
• Verify: Always test LLM-generated code in a safe environment before production use
• Learn from examples: Ask the LLM to explain its code so you understand what it’s doing

Example Prompts for Integration Tasks

Try prompts like these when working with LLMs on FMX integrations:

“I need to write a Python script that retrieves work orders from the FMX API and creates corresponding tickets in [System Name]. Here’s the FMX API documentation for work orders: [paste documentation]. How should I structure this integration?”

“I’m getting this error when trying to authenticate with the FMX API: [paste error]. Here’s my current code: [paste code]. What’s wrong and how can I fix it?”

“I want to automatically create an FMX work order whenever a new ticket is created in our helpdesk system. What’s the best approach to set up this integration?”

Community Resources

• Stack Overflow – Search for API integration questions and solutions
• GitHub – Find example integration code and templates