Delivery time
Less building. More delivering.
Ready-made APIs and shared specifications help your team focus on connecting systems and delivering value.
Solutions built on the ExpressConnect platform
Choose the API packs, connectors and deployment model that fit your program, and build the APIs the packs do not cover in the browser.
API Packs
Each pack groups the REST resources for one functional area. Utilize the packs you need and APIs you create in the API Builder are assigned to a pack as you build them.
Portfolio
Buildings, floors, spaces, lands, leases and lease abstracts.
Maintenance
Work tasks, assets, inventories and comments.
Sustainability
Environmental energy items and related classifications.
Projects
Capital projects, Facilities projects, documents and comments.
Finance
Invoices, invoice line items, purchase orders, cost items and consumables.
- Explore API Builder
Create your own
Need an API the packs do not cover? Use API Builder to create it around your business data and processes.
Choose how your systems connect
Use reusable REST APIs for requests and ExpressEvent for changes that need to reach other systems.
From data model to published API with API Builder
Explore your data model, define your API, then generate, review and publish it inside TRIRIGA / MREF.
- Explore
Explore the live data model
Discover business objects, fields, actions and associations from your connected environment. Select the data and linked objects your API should expose.
- Define
Define the API you need
Follow the guided workflow to define an API, choose its pack and group, and configure resources and paths. Build around the business processes your application needs.
- Generate
Generate, review and publish
Generate APIs and supporting artifacts. Review the OpenAPI specification, and try the new API in API Explorer.
An API Explorer built for developers
Explore your APIs and download a software development kit (SDK) for the scope and language your application needs.
Find the API you need
Browse API packs, groups and resources. Explore parameters, try requests and inspect responses to check the API meets your application's requirements.
Use your team's language
Download SDKs in TypeScript, Python, Java or C#. Work with generated client methods and data models in the language your team already uses.
Download your SDK
Set the package name and version, choose the API versions to include, then download the generated source as a ZIP to build into your application.
Explore developer resources
From API definition to application code
Follow the workflow in these animated illustrations of the API Builder and API Explorer. Screens and data are simplified to show the process.
Illustrated workflow
API Builder
Define your API, choose fields and review the generated resources before publication.
Build the connections behind AI use cases
Artificial intelligence (AI) becomes useful when it understands the work around it. Explore how connected data and actions could support service teams, engineers and maintenance planners.
We are developing the ExpressConnect MCP Server to connect AI assistants with business data and actions through Model Context Protocol (MCP). The aim is to bring relevant records into each conversation, help teams decide what to do next and carry approved actions back into their operational systems.
AI-assisted service requests
Use photos and a short description to suggest a fault category and priority, spot similar requests and let the helpdesk review the details before submission.
From a reported fault to the right action
The MCP connection will bring asset details, location and related requests into the conversation, helping the assistant ask useful follow-up questions and prepare a complete request for review and submission.
Knowledge copilot
Help engineers find guidance in approved procedures and manuals, with source citations and relevant past work alongside the answer.
Answers grounded in the job at hand
The MCP connection will bring the asset, current task and maintenance history into the conversation. Combined with approved manuals and procedures, this will help the copilot suggest relevant next steps and show the evidence behind its guidance.
Maintenance War Room
Bring work tasks, technician locations and traffic into a shared operational picture. Explore AI-assisted task matching and review reassignment proposals before applying dispatch decisions.
A shared picture for coordinated decisions
The MCP connection will bring work priorities, asset status and crew availability into the War Room. Teams could explore reassignment options with travel and incident context, then approve dispatch changes before they reach operational systems.
AI use cases portal and MCP Server are upcoming solution areas
Connectors and middleware
Connect TRIRIGA / MREF to your integration platform through ExpressAPI. Its OpenAPI specification describes the available operations and data structures, helping you build connectors, configure requests and map data into your workflows.
IBM App Connect
Create a custom connector from the ExpressAPI OpenAPI specification, then use its actions to connect TRIRIGA / MREF with other applications in App Connect flows.
Custom connector
MuleSoft
Publish the ExpressAPI OpenAPI specification to Anypoint Exchange and use REST Connect to generate a connector for your Mule application flows.
Generated Mule connector
webMethods
Import the ExpressAPI OpenAPI specification into Designer to generate connector services, then map their inputs and outputs into your integration flows.
Generated REST services
Postman Flows
Import the ExpressAPI OpenAPI specification as a collection, then connect its requests in Postman Flows to build and test visual workflows.
Collection-based workflows
Azure Logic Apps
Create a compatible custom connector from the ExpressAPI definition, then add TRIRIGA / MREF actions to Logic Apps workflows and map data between systems.
Custom connector
AWS AppFlow and Step Functions
Build an AppFlow custom connector for ExpressAPI data transfers, or orchestrate ExpressAPI calls with HTTP tasks in Step Functions.
Custom connector / HTTP tasks
MuleSoft Composer
Use Composer's HTTP Connector to call ExpressAPI, configuring requests from the OpenAPI specification and mapping responses into business workflows.
HTTP Connector
Snowflake
Build a data-loading procedure that calls ExpressAPI through Snowflake external access, using the OpenAPI specification to map TRIRIGA / MREF records into analytical tables.
API data ingestion
Deployment models
ExpressConnect runs inside the TRIRIGA / MREF application server wherever that server lives. The external cache can be deployed separately in the cloud or in OpenShift containers.
On-premises
Installed on your own infrastructure.
Cloud
Deployed on cloud infrastructure managed by your company or a third party.
Hybrid
A combination of on-premises and cloud.
OpenShift Cluster
Deployed within an OpenShift cluster.
Webhook updates and scheduled refresh connect the application runtime to a separately deployed external cache. External cache in native cloud or OpenShift
Deploy the external cache on native cloud infrastructure or in containers within an OpenShift cluster.
Use case examples
See how organizations would use ExpressConnect to shorten integration programs.
Use case 1 of 3: Faster integration at lower cost
Plan delivery and ongoing costs
Scope the work you can reuse and the capabilities your team needs to maintain.
Cut integration delivery costs
Eliminate extensive custom development and reduce the effort needed for onboarding and testing.
1 of 4: Standardized building blocks
Plan the total cost of ownership
Ongoing savings beyond the initial delivery: one documented API layer, one data model, fewer point-to-point integrations to maintain.
1 of 5: Flexible commercial terms
Which packs fit your program?
Tell us which systems you need to connect and we will map them to the packs, connectors and license that fit, and show how the API Builder covers the rest.