Participate in the Digital Twin economy

JSON-based REST APIs:

Twinit is made up of microservices, which can be used independently or together to create powerful Apps. All microservices are accessible via a rich set of JSON-based REST APIs, which make it easy to integrate with other systems and technologies.

JavaScript APIs:

Twinit also provides JavaScript APIs, which act as a wrapper on the back-end REST APIs. This makes it easy for developers to use the platform's functionality from within their own JavaScript code.

Script engine:

Twinit includes a script engine that allows JS scripts to be loaded in run time and executed both on the backend and the frontend. This makes it easy to create custom functionality that is tailored to the specific needs of your project.

Higher-order APIs:

The JavaScript APIs also include semantically higher-order APIs built using the wrapper APIs. This means that developers can use powerful, pre-built functions to perform common tasks quickly and easily.

App specific REST APIs:

Apps composed on Twinit can provision their own REST APIs with a simple API configuration and JS scripts thus removing the need to implement and deploy their own services.

Application Framework:

IPA-CORE is a Framework for developing Twinit Native Apps using scripts (JavaScript) and React components.

The scripts define your application’s backend, including the data model, data pipelines, business logic, user configurations, access control and permissions to name a few.

The scripts also dynamically controls the web client’s User Experience.

You can use out-of-the-box React components (IPA-LIB) and add your own React components to use within IPA-CORE.

You can build any UX that can be supported by React.

• A Twinit Platform Application (IPA) is created using the Twinit Application Framework (IPA-Core)
• Each IPA is assigned an App ID, and can support a variety of client interfaces – Native iOS or Android, web clients in React / Angular or any other, Desktop Apps in C# / Java or any other, widgets embedded in third party apps.
• The IPA uses the platform’s services as its backend.
• The backend of the IPA is defined by its set-up scripts and configuration scripts stored within workspaces (projects). The scripts for each project defines everything about the IPA, including its data model and its user experiences.
• The IPA can be can be re-composed to create customized solutions for each project.
• Only one instance of an IPA’s web client needs to be hosted by the App developer.

A Visual Studio code extension that integrates to the platform and provides you a development environment for implementing, debugging and versioning of JS scripts and application REST API configurations.

Twinit Apps may whitelist each other to deliver Interoperability natively. An App can provide permissions on its data to users of other Apps. Alternatively, an App can publish its data to other Apps, enabling many distinct Apps to share data and work in unison. This also allows clients to build a supervisory layer that sea mlessly interacts with all their point solutions, creating a whole that is greater than the sum of its parts.

Plugins:

Twinit Native Apps can use out of the box plugins to seamlessly integrate with popular BIM / CAD tools like Revit, AutoCAD, and Civil3D and exchange formats like IFC to extract 2D and 3D graphics, elements and property data and publish it to a project in Twinit.

Graphics Viewer:

A feature rich web-based graphics viewer (iaf-viewer) enables Apps to show 3D and 2D graphics in the browser. In addition Twinit provides a web-based Multi Modal Viewer (MMV) which integrates multiple graphic streams and build interactions between them. The MMV supports the Twinit iaf-viewer, ArcGIS viewer, Unreal Engine Pixelstream, Panellum Photospheres, and video streams. The list continues to grow.

Data sources:

Prebuilt connectors allow reading of data from different sources over various protocols.

• Haystack connector to read telemetry data from gateway devices that support a wide range of protocols like BacNET, Modbus and OPC.
  
• MQTT broker and Kafka connect to allow time series data from any IoT data source to be defined and persisted as needed by the App.
  
• Generic REST connector that supports several authentication mechanisms to integrate with any other enterprise App or data aggregation platform.
• A highly configurable BIM graphics and data import mechanism.