Oracle Smart Operations in Fusion Cloud SCM Integration

oracle and litmus have worked together to build an integration – focusing on oracle smart operations connected assets and equipment capabilities in fusion cloud supply chain & manufacturing (scm), alongside litmus edge's edge capabilities litmus created a solution template enabling customers to generate smart operations payloads within oracle cloud manufacturing and maintenance this integration supports data transmission through the rest api oauth integration oracle payload requirement the integration focuses on associating connected devices on litmus edge with the five predefined event types powered by smart operations capabilities within oracle fusion cloud manufacturing and oracle fusion cloud maintenance the five event types and payloads are listed below asset fault event asset status event operation execution start event quantity report event operation execution stop event the purpose is to provide smart operations for oracle / litmus customers to model 5 event types on litmus edge, generate events, and send them to oracle cloud manufacturing and maintenance via litmus's northbound rest api oauth integration example please refer to the oracle rest api for the oracle supply chain management cloud guide, which showcases these examples the breakdown of each of the key value pairs in each of the payloads is broken down as below entitycode device metadata eventtypecode metadata for each event eventtime event time at the time of event generation data data payload is generated via devicehub , analytics , and/or integrations on litmus edge quick start guide deploy litmus edge version 3 22 0 or later see installation and deployments docid\ sxt wzhesdji7womiawlo for details import the litmus edge template to the deployed instance of litmus edge documentation on how to apply a template can be found here configuring and generating the desired payload digital twins on litmus edge helps with standardization and governance to build the data schema and format for your devices on the plant floor for integration with oracle smart operations in manufacturing and maintenance, digital twins helps with building the payload necessary to be sent based on the specific customer requirement(s), tags, and mapping required for events, the transformation changes can be done in digital twins and analytics to build the payload for the five events note please reach out to your litmus support representative, or your system integrator partner for help and guidance for your specific use case building your data model using digital twins and analytics digital twins on litmus edge helps with standardization and governance to build the data schema and format for your devices on the plant floor for integration with oracle smart operations in manufacturing and maintenance, digital twins helps with building the payload necessary to be sent analytics on litmus edge helps transform the device payload and associate device values with event values for example, a payload for an asset fault event coming from the device may only contain fault code which can be associated with an associated fault type using analytics tengo script processor or javascript processor on analytics example asset fault event can be configured to map the fault code to a specific fault type using transformations in digital twin models defining the mapping using jsonata transformations as shown in the template once the desired payload is configured in digital twins, copy the topic from digital twins instance for the events that needs to be sent to oracle cloud manufacturing and oracle cloud maintenance data will be sent to oracle fusion scm using integrations on litmus edge data can be sent to oracle fusion scm using rest api integrations on litmus edge on the rest api connector, enter the oauth credentials to oracle the details around toauth token endpoint, client secret, client id, and scope can be requested from oracle for your integration important it is necessary to define the port after the base url on the rest api oauth configuration page https //\<base url> \<port number>/\<resource request/api call> once the connection is established, configure the outbound topic from digital twins instances as necessary example end to end configuration steps for asset fault event connect your device see connect a device for more details upload the template see template for more details add entitycode as metadata for your device on your digital twins static attributes ensure you have eventtypecode configured as " ca fault " on static attributes transformation associate your fault codes to fault types under " data payload transformation " by using the example on the template note for high volume fault codes, the data payload transformation can be done in analytics using a tengoscript processor or javascript processor to build the payload instead of transformations dynamic attributes maps the data and event payloads schema defines your payload structure be sure to upgrade the instance to apply changes copy the topic from instance topic in rest api integration as shown in integrations section the data will now be streaming to oracle smart operations for manufacturing and maintenance for the 5 event types configured from litmus edge