Normal
0
false
false
false
EN-CA
X-NONE
X-NONE
MicrosoftInternetExplorer4
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
Context is Everything
How many times have you have you asked a question
only to hear an answer like “Well, it depends. What exactly are you trying to do?”. There are times that raw information can’t tell us what we
need to know without putting it in a larger context.
Let's take a real world example. If I'm a maintenance planner trying to figure out which assets should be replaced during my next maintenance window, I'm going to go to my Asset Management System. I can get it to spit out a list of assets that have failed several times over the last year. But what are these assets connected to? Is there any safety consequences to shutting off this pipeline to do the work? Is some other work that's planned going to conflict with replacing this asset? Several of these questions can't be answered by simply spitting out a list of asset IDs. The maintenance planner will have to reference a diagram of the plant to answer several of these questions.
This is precisely the idea behind Augmented
Business Visualization. An Augmented
Business Visualization (ABV) solution is one where your structured data
(enterprise application data) and your unstructured data (documents, contracts,
floor plans, designs, etc.) come together to allow you to make better decisions. Essentially we're showing your business data into its context.
AutoVue allows you to create ABV solutions by integrating your
enterprise application with AutoVue’s hotspot framework. Hotspots can be defined for your
document. Users can click these hotspots to
trigger actions in your enterprise app. Similarly, the enterprise app can highlight the hotspots in your
document based on its business data, creating a visual dashboard of your
business data in the context of your document.
ABV is not new. We
introduced the hotspot framework in AutoVue 20.1 with text hotspots. Any text in a PDF or 2D CAD drawing could be
turned into a hotspot. In 20.2 we have enhanced
this to include 2 new types of hotspots: 3D and regional hotspots.
3D hotspots allow you to turn 3D parts into hotspots. Hotspots can be defined based on the
attributes of the part, so you can create hotspots based on part numbers,
material, date of delivery, etc.
Regional hotspots allow an administrator to define
rectangular regions on any PDF, image, or 2D CAD drawing. This is perfect for cases where the document
you’re using either doesn’t have text in it (a JPG or TIFF for example) or if
you want to define hotspots that don’t correspond to the text in the document.
There are lots of possible uses for AutoVue hotspots. A great demonstration of how our hotspot capabilities can help add context to enterprise data in the Energy sector can be
found in the following AutoVue movies:
Maintenance Planning in the Energy Sector - Watch it Now
Capital Construction Project Management in the Energy Sector - Watch it Now
Commissioning and Handover Process for the Energy Sector - Watch it Now
