As someone who needs to create displays and other 'artifacts' from context, I need to be able to use different names for Attributes depending on the language of the user SO THAT I don't need to build multiple displays for each language.

Ability to define a global library of asset templates and assets and then map site data structures into it SO THAT we can standardize easier across sites when the underlying systems and equipment structures are different (and focused more on automation design rather than the use of the data).

Support the ability to handle connectivity models that map out relationships between assets/elements and associate different assets together based on their relationships.

Support Table Lookup functionality in OCS Context, similar to AF where the meaning of a value (Code 7) is deciphered via a lookup table.

Support Table Lookup functionality in AF to OCS.

Allow event frame reporting to be moved into the cloud to sustain a higher scalability for enterprise analytics and evalution

When I create an Asset Rule I have a Token Value Mapping, some of my Mappings have a delimiter in them. I would like to be able to easily specify to map that Mapping to the same words, but with a different delimiter, without having to define each one individually. For instance I would like to go from Gasrate to Gas rate and SRProd_velocity to SRP rod velocity.

Ability to create user-defined patterns that can be parsed from the stream name to create Assets, Asset Attributes, & Asset Measurements. Currently the service uses delimiters to aid in the construction of a pattern.

This would help customer create and manage Assets in Bulk.

For example, a stream name with B.1234.Temp can be deconstructed into Assets: Boiler 1234 with related data such as Temperature referencing the stream.

Ability to create user-defined patterns that can be parsed from the stream name to add context. Currently the service uses delimiters to aid in the construction of a pattern. For example, a stream name with B1234 can be deconstructed into equipment: Boiler and equipment ID: 1234

It isn't apparent in the user experience that multiple rules can contribute to the same assets.

Be able to specify hierarchical parent/child relationships between assets that also support these relationships changing over time for mobile Assets that get deployed to different locations.

When I want to create assets with types from an asset rule, I am not usually aware of all the properties the type will need before hand. So generally I create the asset rule, create a type from one of the generated assets, and then add the asset type Id through the API.

It would be great if it allows typing on the asset preview page.

I would like to be able quickly make a metadata rule and I have on that is similar to what I would like. I would to be able to copy a metadata rule in the portal.

I would like to be able to use the Stream Views capabilities in OCS to be able to flatten nested streams.

Enable a way for people across different companies to collaborate together with the goal of defining standard Asset Views/Shapes for different types of assets (pumps, steam turbines, tanks, etc.) that can be published and used by all customers SO THAT Industrial Operators and Service Providers can easily to exchange operational data, consume service offerings, and enable future bench marking services.

Imagine publicly available Asset Views developed through a model similar to Wikipedia.