Technology

Be free of
manufacturer dependency!

FieldBots Bridge

FieldBots integrates service robots for facility management through Cloud-to-Cloud connections or hardware and software Bridges to enable real-time communication between your swarm and the FieldBots Cloud.

Read documentation
Components
Internet best practices and long-term partners

FieldBots uses a technological basis that is considered state-of-the-art today and, apart from the business logics, is largely supplier- and stack-independent. Based on the user and their application scenarios, processes were modelled that were mapped with proven concepts, products and providers.

  • The FieldPass microservice infrastructure, which specialises in mapping building-vicinity services, has been developed by Feil, Feil & Feil over the past 10 years and has since been used in countless customer projects in the industry.
  • Keycloak for the secure administration of identities, roles and rights forms the audited basis of FieldPass and offers a complete implementation of OpenID Connect and OAuth 2.0.
  • FieldBots is developed in-house at Feil, Feil & Feil in Ludwigsburg near Stuttgart and at the affiliate FFUF Manila in the Philippines in an agile development mode.
  • The development, test and live environments of FieldBots and FieldPass are hosted and professionally operated in Microsoft's Azure Cloud on European servers.
  • By using the Azure IoT Hub, the FieldBots Bridges are securely and scalably connected to the FieldBots Cloud. In doing so, FieldBots also takes over automatic management of the Bridges.
  • Angular
  • Kotlin
  • Flutter
class BotService { constructor(private botRepository: BotRepository) { } loadAllRoombas(): Observable { return this.botRepository.getAll({ type: Type.ROOMBA, page: 1, maxResults: 100, }); } }
class Bots( private val botApi: BotApi ) { suspend fun loadAllRoombas(): List { return botApi.getAll( type = Type.ROOMBA, page = 1, maxResults = 100, ) } }
class BotService { final BotRepository botRepository; Future> loadAllRoombas() { return botRepository.getAll( type: Type.ROOMBA, page: 1, maxResults: 100, ); } }
Basic approach
Paradigms
in development

10 years of experience in the digitisation of building operations and their service providers have created paradigms in the corporate group, which FieldBots also follows. They guarantee a solid, future-proof overall product without making the mistakes that often occur when starting to develop a new product.

  • ⭕️ API deadline approac
  • ♀️  Focus on users and use cas
  • 🌏 Internationalisation capability
  • 🚀 Multi-platform technologies
  • 🏝 Offline capabilit
Professionelle
Operations
Professional operations

Since FieldBots is based on FieldPass, as with all other business models mapped with FieldPass, it is operated professionally following an operating concept. In addition to regular patches and function updates for the security and future viability of the technological basis, this also means systematic monitoring of all microservices and applications. It includes documentation of all occurrences for the traceability of problems and their solution. FieldBots also offers second-level support during business hours from Monday to Friday from 8:00 a.m. to 6:00 p.m., which can be extended upon request. The FieldBots Cloud is operated natively and scalably in dedicated environments for development, quality assurance and productive use in the European part of the Microsoft Azure Cloud.

Development
Standardised development processes

FieldBots has been developed using a proven, agile process that is based on state-of-the-art technology and best practices of the industry. For example, the infrastructure as Code Tool Terraform is used to set up environments and deployment pipelines. Binding branch management according to Gitflow allows for the controlled rollout of individual features based on epics and user stories. Systematic code reviewing by our software architects with a precise process for pull requests are part of our development standard, as is reasonable test coverage through unit tests. Automatic linting avoids widespread malpractices from occurring.