Cloud Management (draft)

cloud management allows you to configure and manage the integration between manufacturing connect (mc) and google cloud's manufacturing data engine (mde) here you specify how industrial data from edge devices is structured, transformed, and passed to mde manufacturing data engine (mde) https //docs cloud google com/manufacturing data engine/docs/overview is an end to end solution that delivers scalable and seamless connectivity between the factory floor and the cloud in combination with manufacturing connect cloud management has the following components cloud tags tags that extend the concept of mce tags with additional metadata, dimensional data, live data, and contextual configurations each tag can have one or more types assigned and you can override configuration settings as needed metadata versioned json schemas that define the structure and fields available to a tag types bind one or more metadata schemas and define where processed data is sent for example, some supported output destinations are bigquery, bigtable, cloud storage, and pubsub json message classes a rules engine using spring expressions that evaluates incoming message payloads by priority to determine which parser to apply parsers transform incoming messages from manufacturing connect into formats accepted by mde each parser is assigned a type that defines how the payload is processed and where it is sent file ingestion configures the format of incoming files for processing by mde notifications system messages reported by mde indicating operational status additionally, you can use cloud configuration to uploading a configuration package (zip file containing metadata, type, and message class definitions), typically for migrating configurations between environments such as test and production for more information, see cloud configuration docid 2rcivcggepx9uhujw19ol messages processing the messages processing toggle at the top of the page pauses all message processing across cloud management pause message processing before making significant configuration changes or performing an upgrade workflow setting up cloud management follows a dependency order consider configuring component in this order define metadata schemas create the json schemas that define what contextual fields a tag can hold, such as asset location or alarm configuration create types group one or more metadata schemas into a type and configure the output destinations where processed data is sent configure cloud tags assign one or more types to each tag the tag inherits the metadata structure and output destinations from its assigned types create message classes write spring expressions that evaluate incoming message payloads and route them to the correct parser based on priority create parsers connect each parser to a message class and an output type, then write the whistle transformation code that maps the raw message payload to the format the type expects configure file ingestion if your integration receives file based data, define ingestion specifications in the file ingestion tab to specify the source folder and file format monitor notifications use the notifications tab to review system messages and warnings reported during operation