X

AutoVue Visualization solutions are designed for today’s information sharing and collaboration challenges.

Recent Posts

Oracle AutoVue VueLink for Oracle WebCenter Content 21.0.1 - Now Available

Oracle’s AutoVue VueLink 21.0.1 for Oracle WebCenter Content (WCC) provides an interface between Oracle WCC Server 12c and Oracle AutoVue versions 21.0.1 and 21.0.2.  This VueLink is not compatible with other versions of WCC or AutoVue. This interface enables users to add powerful visualization and collaboration capabilities to Oracle WCC clients. Updates in this Release: - Major Change: Due to the removal of Java Applet support from most Web browsers, the AutoVue Client is launched as a separate application and window through Java Web Start. - Use of Content Integration Suite replaced with Remote Intradoc Client (RIDC) API. - Previous releases of the VueLink for UCM used the ContentFolio component to support XRef functionality. In this release, XRefs can also be configured through the “Related Content” facility, which is part of the base functionality provided by the records management (RM) component. For the latest versions of Oracle AutoVue and Oracle WebCenter Content that have been certified with this VueLink, see the certification matrix on My Oracle Support:   For additional information about the product, go to the AutoVue Documentation Web site on the Oracle Technology Network at https://www.oracle.com/technetwork/documentation/autovue-091442.html  

Oracle’s AutoVue VueLink 21.0.1 for Oracle WebCenter Content (WCC) provides an interface between Oracle WCC Server 12c and Oracle AutoVue versions 21.0.1 and 21.0.2.  This VueLink is not compatible...

AutoVue for Agile 21.0.2 is Now Available!

Oracle is pleased to announce the availability of Oracle’s AutoVue for Agile Enterprise Visualization 21.0.2, a minor release within the 21 product family. It includes a “Technology refresh”, meaning there has been a number of third-party libraries updated, and AutoVue now compiles with Visual Studio 2015/GCC 4.9.x (C++11). As of AutoVue for Agile 21.0.1, AutoVue Client is a Java application that can be started through the Java Web Start framework (for A9 - 9.3.6), This allows AutoVue to run in browsers that no longer support Java Applets (The user still needs to have the Java runtime environment installed). However for this release, AutoVue 21.0.2, a  new communication mechanism between AutoVue Client and browsers has been added - Rendez-vous communication (HTTP and HTTPS protocols) this eliminates the need for the localhost certificate in SSL mode. • New Format Support * SolidWorks 2017 and 2018 AutoCAD 2018 and 2019 AutoCAD Mechanical 2018 and 2019 Inventor 2017, 2018 Catia V5-6 R2016 (R26), R2017 (R27) and R2018 (R28) SolidEdge ST9 and ST10 Creo 4.0 and 5.0 Unigraphics 11.0 and 12.0 3D files Parasolid (new in 21.0.2) STEP compressed (*.stpz) Cadence suite 17.2 Allegro Orcad Capture Cadence projects *Some formats were already added as part of Roll up patches (RUPs) on the AutoVue 21.0.1 release In this release, support has been extended to the following Operating System:     Windows Server 2016 Agile A9 – 9.3.5.8 or 9.3.6.8 are needed to run AutoVue for Agile 21.0.2   Click here to read about the latest features and their corresponding benefits for AutoVue Click here to access the latest AutoVue Format Support Sheet  

Oracle is pleased to announce the availability of Oracle’s AutoVue for Agile Enterprise Visualization 21.0.2, a minor release within the 21 product family. It includes a “Technology refresh”, meaning...

AutoVue 21.0.2 is Now Available!

Oracle is pleased to announce the availability of Oracle’s AutoVue Enterprise Visualization 21.0.2, a minor release within the 21 product family. It includes a “Technology refresh”, meaning there has been a number of third-party libraries updated, and AutoVue now compiles with Visual Studio 2015/GCC 4.9.x (C++11). As of AutoVue 21.0.1, AutoVue Client is a Java application that can be started through the Java Web Start framework, This allows AutoVue to run in browsers that no longer support Java Applets (The user still needs to have the Java runtime environment installed). However for this release, AutoVue 21.0.2, a  new communication mechanism between AutoVue Client and browsers has been added - Rendez-vous communication (HTTP and HTTPS protocols) this eliminates the need for the localhost certificate in SSL mode. • New Format Support * SolidWorks 2017 and 2018 AutoCAD 2018 and 2019 AutoCAD Mechanical 2018 and 2019 Inventor 2017, 2018 Catia V5-6 R2016 (R26), R2017 (R27) and R2018 (R28) SolidEdge ST9 and ST10 Creo 4.0 and 5.0 Unigraphics 11.0 and 12.0 3D files Parasolid (new in 21.0.2) STEP compressed (*.stpz) Cadence suite 17.2 Allegro Orcad Capture Cadence projects *Some formats were already added as part of Roll up patches (RUPs) on the AutoVue 21.0.1 release In this release, support has been extended to the following Operating System: Windows Server 2016 Click here to read about the latest features and their corresponding benefits for AutoVue Click here to access the latest AutoVue Format Support Sheet

Oracle is pleased to announce the availability of Oracle’s AutoVue Enterprise Visualization 21.0.2, a minor release within the 21 product family. It includes a “Technology refresh”, meaning there has...

AutoVue Enterprise Visualization

AutoVue and AutoVue for Agile 21.0.1.6 Rollup Patch is Available

We are happy to announce the availability of a new AutoVue and AutoVue for Agile Rollup Patch (RUP) for release 21.0.1. This RUP adds support for: •        Creo 5.0 files. •        AutoCAD 2019 files. •        AutoCAD Mechanical 2019 files. •        Catia V5-6 R2018 files. •        Unigraphics NX12 3D files. Also in this RUP •       Due to a known security flaw Jetty 6 was disabled in AutoVue This is the sixth Rollup Patch for AutoVue 21.0.1. Please note that RUP6 is not a cumulative patch. It requires 21.0.1.4 (RUP4) or 21.0.1.5 (RUP5) to work properly. The RUPs:  21.0.1.1, 21.0.1.2 and 21.0.1.3 are already included in RUP4 and RUP5. You do not need to install them. Also, you do not have to install 21.0.1.4 (RUP4) if you already have 21.0.1.5 (RUP5) installed. You can go from RUP 4 to 6 without installing RUP 5, if the RUP 5 functionally is not needed. This RUP is immediately available for AutoVue users under maintenance. With the release of this sixth AutoVue RUP, Oracle continues to demonstrates its ongoing commitment to providing its customers with up-to-date format support needed for their business practices. For more information about AutoVue 21.0.1.4 Rollup Patch, please consult the following Knowledge Management Note on My Oracle Support: Doc ID 2235039.1  

We are happy to announce the availability of a new AutoVue and AutoVue for Agile Rollup Patch (RUP) for release 21.0.1. This RUP adds support for: •        Creo 5.0 files. •        AutoCAD 2019 files.• ...

AutoVue Enterprise Visualization

AutoVue Log errors when installed on Linux

I have seen in the past few months a recurring issue when trying to use the AutoVue server on Linux 7. The problem is that once all the pre-requisites are installed and the AutoVue server is starting properly, there are still errors in the AutoVue log (log4j-roll.log). The errors seen to all point to missing fonts: FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSansNarrow-BoldItalic.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSansNarrow-Bold.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSansNarrow-Italic.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSansNarrow-Regular.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSans-BoldItalic.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSans-Bold.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSans-Italic.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSans-Regular.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSerif-BoldItalic.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSerif-Bold.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSerif-Italic.ttf FreeType: couldn't open face /usr/share/fonts/liberation/LiberationSerif-Regular.ttf Now it’s easy to actually get rid of these errors simply by download the missing fonts from the web and making sure to place them in the “/usr/share/fonts/liberation” folder. Restarting the AutoVue server afterwards should show no errors in the log file related to fonts. Of course this issue is now documented and can be found by looking at Note 2303591.1.

I have seen in the past few months a recurring issue when trying to use the AutoVue server on Linux 7. The problem is that once all the pre-requisites are installed and the AutoVue server is...

Changes in Watermark handling between AutoVue 20.2.3 and AutoVue 21.0.0

Hi all, This is a somewhat old change now, but we’ve started getting some questions about it, so I thought it was worth describing in a bit more detail.  In AutoVue 20.2.3 and earlier, watermark text was drawn as a filled-in, transparent text, but starting in 21.0.0 we switched to drawing the watermarks as non-transparent, outlined text.    The reasons for this are a little subtle, but I wanted to explain it in more detail here.    Due to limitations in how Java processes data for printing, in order for the transparent filled text to be printed properly, we had to convert the area around the watermark from a vector into a raster, and the raster was often at a low enough resolution that the contents of the document was blurry, and often lighter in colour than the other parts of the document    The image above is our standard AutoCAD sample file, printed in AutoVue 2.2.3 with a watermark – compare what 0.7664 in the bottom left looks like, compared to 6.7388 in the upper right.      Depending on the scale of the document and the size of the features, sometimes this is more noticeable, and sometimes you can barely see it – but in most cases there is a at least some degree of degradation of the image around the water mark. I hope that clarifies what the benefits are of the new way of handling watermarks! The above image shows what the same document and a similar watermark looks like in AutoVue 21.0.0 0 – the watermark is perhaps a little harder to read when it crosses thick lines on the drawing, but the details of the drawing itself are preserved.   

Hi all, This is a somewhat old change now, but we’ve started getting some questions about it, so I thought it was worth describing in a bit more detail.  In AutoVue 20.2.3 and earlier, watermark text...

Administrivia

Scrolling or Zooming with the Mouse Wheel in AutoVue

I've heard a few questions on this lately, so I thought it would be a good idea to summarize the status of things here.  Since AutoVue supports multiple different types of documents, it isn't necessarily always clear what the desired behaviour of the scroll wheel should be.In general, our assumption is for what is traditionally thought of as a 'document' (i.e. something that you generally start reading at the top of the document and read towards the bottom), the scroll wheel on your mouse should scroll you through the document.   However, if you are viewing a drawing or a 3D model, then the scroll wheel should zoom in and out, to make it easier to zoom in to see the details of a particular area of interest, and then zoom out again.This is generally clear when dealling with formats like MS Word, AutoCAD, or Creo - however it becomes a lot less clear with some formats like PDF - since a PDF file could be either.  The PDF could be created by converting or scanning an MS word document, or by doing a print to PDF of an AutoCAD drawing.  Unfortunately there's no way for AutoVue to know how the PDF is intended to be used.In AutoVue, we've implemented a middle-ground solution for pdf files - if the file has multiple pages, we assume is it a document intended to be read from the top, and the mouse-wheel scrolls through the document.  If it's a single page, we assume it's a drawing and the mouse-wheel zooms in and out.   Note that if you are in a document where the mouse-wheel is scrolling through the document, you can change to the zooming behaviour by holding control down while using the mouse-wheel.

I've heard a few questions on this lately, so I thought it would be a good idea to summarize the status of things here.  Since AutoVue supports multiple different types of documents, it...

Tips and Techniques

AutoVue Testing Guide for User Acceptance Testing (UAT) and System Integration Testing (SIT)

User Acceptance Testing (UAT) and Systems Integration Testing (SIT) are two key activities in an AutoVue deployment. Performing UAT allows the users to try AutoVue in a realistic environment, and sign off on the deployment meeting their business needs. SIT allows the systems integrator to validate the configuration of the solution and is useful for catching problems specific to the deployment environment or users’ business processes. In order to maximize the usefulness of UAT and SIT, it is important that the tests meet certain criteria. In general the set of tests should aim to: Cover as much of the users’ day to day business process as possibleMimic the production environment as closely as possibleUse data (designs and markups) that will actually be used in production Meeting these criteria will ensure that any problems specific to the users’ business process, production environment, or design data will be caught early in the deployment process, allowing sufficient time to respond to these problems before deploying AutoVue in the production environment. The AutoVue Testing Guide explains what should be considered when planning UAT and SIT for AutoVue. It briefly covers how to fit UAT and SIT into your deployment process. Then it goes through some of the features of AutoVue, and what types of tests need to be performed to cover these features. Finally, some sample scenarios are given to demonstrate how tests should be built around the users’ business processes as a whole, as opposed to performing isolated tests. It is strongly recommended that anyone who is planning on deploying AutoVue, plan SIT and UAT into their deployment process and follow the advice listed in the AutoVue Testing Guide for creating these test plans. For the latest version of the AutoVue Testing Guide, please refer to the AutoVue documentation stored on the Oracle Technology Network (OTN) website: http://www.oracle.com/technetwork/documentation/autovue-091442.html

User Acceptance Testing (UAT) and Systems Integration Testing (SIT) are two key activities in an AutoVue deployment. Performing UAT allows the usersto try AutoVue in a realistic environment, and sign...

Enterprise Visualization

AutoVue in the browser *without* Applets

As you may have seen - one of the big features in our latest 21.0.1 release of AutoVue is that we can now support AutoVue in browsers without Applet support.   Chrome removed support for Applets a while ago, and Firefox is about to, so this is a pretty important capability to allow people to continue using AutoVue as part of a web environment.  What we did in AutoVue 21.0.1 is to add support for something called the Java Web Start Framework - which allows browsers to easily run java applications.  Using this framework, the AutoVue client can be run as a separate application outside the browser, which provides a higher degree of security, and will work with browsers without applet support. For the end-user the experience will be pretty similar to previous versions of AutoVue - you can click on a document or model in their browser, and the AutoVue client will launch and display the appropriate document or client.   If you are developing integrations or extensions to AutoVue you will need to do some additional work - the way AutoVue is launched with Java Web Start is somewhat different, and communication with the AutoVue client is also somewhat changed.   Instead of directly calling java APIs in the AutoVue client from Javascript, you use a javascript API we provide that will then pass the messages to the client running outside the browser.   You can still extend the AutoVue client by adding new classes, but you will need to update the Java Web Start launcher to include your code. For more information about how to launch AutoVue with Java Web Start, refer to the "AutoVue Installation and Configuration Guide" - especially sections 5 and appendix H.    For more information on how to use AutoVue APIs with Java Web Start, refer to Part II of the "API Guide". All documents can be found at this link: http://www.oracle.com/technetwork/documentation/autovue-091442.html  One final note - the AutoVue Client applet continues to be supported in AutoVue 21.0.1, so you can continue to work with it until you switch to the Java Web Start environment - However, the applet support is deprecated and will be removed in a future release of AutoVue, so we encourage you to start working with the Java Web Start version as soon as you can. If you have any questions, let us know below!

As you may have seen - one of the big features in our latest 21.0.1 release of AutoVue is that we can now support AutoVue in browsers without Applet support.   Chrome removed support for Applets a...

Tips and Techniques

Comparing performance between AutoVue 21 and earlier releases

Hi all,  One of the things we've talked about here before is the new 3D engine that we included in our last major release - AutoVue 210.0.   One of the big improvements this new engine enabled is some pretty substantial performance improvements when loading 3D files - especially when loading the native files directly (i.e. without a streaming file generated).   For large Creo or ProE assemblies, this should be *very* noticeable - we've seen cases where 21 loaded files in half the time or even better - but across the board you should in general see a 20 to 30% speed up. However, an important thing to note is that there are also some pretty major fidelity improvements in AutoVue 21.0.0.   We have had a few cases where customers have complained that their files were loading more slowly in AutoVue 21 - however, when we looked at the earlier version of AutoVue we saw that it wasn't fully loading the file.  AutoVue 21 appeared to be slower because it was actually processing a lot more data than the older versions, and providing a much more complete version of the assembly. If you are seeing cases where AutoVue 21 appears to not be as fast as earlier versions --- take a close look at the results.  Maybe you are also getting a much more complete view than you were in the past.  Oh - and before I forget - Happy Thanksgiving to those of you in the US! 

Hi all,  One of the things we've talked about here before is the new 3D engine that we included in our last major release - AutoVue 210.0.   One of the big improvements this new engine enabled is some...

Tips and Techniques

Customisation Approaches with AutoVue

There are a number of different ways that AutoVue can be customised to better serve user's needs, and I've occasionally talked to people who weren't clear on what the best approach was for what they were trying to accomplish.   I'm going to talk about a few of the more popular approaches here, and give you a few pointers about where to find additional information:  1:  Add new menu items or toolbar items to AutoVue:   This is done by creating what we call a 'Custom VueAction' - which is basically a chunk of java code that can be invoked by a new menu item or toolbar item in AutoVue.   The java code can use the AutoVue APIs to access information about the files that are loaded, trigger actions like showing or hiding parts, or creating markup entities, and can easily automate lots of tasks.   Dan covered this in more detail in a previous post, and there is a good KM note with more details: KM Note 2151550.1  2: Make parts of drawings or models interactive:  This is done by creating what we call 'Hotspots' - with a technique we call Augmented Business Visualization.   The idea here is to allow users to click on parts of drawings or models and trigger actions or retrieve information - for instance creating a change order, or retrieving information on a part.  We've done a few posts on this in the past, and there is a working sample you can find as KM note 1472899.1  3: Allow users to access files stored in a content repository:  This is done using our Integration SDK (ISDK), which can create integrations that allow AutoVue to reach into a repository to find files, get associated metadata and related files, and store annotations back into the repository.   This can be very useful when you have a 'home grown' repository of data and need to allow AutoVue to get access to it.  The ISDK is provided as a separate installer with AutoVue, and when you install it, you'll get the libraries needs as well as an example integration that shows you how things work.   More can be found on our documentation page - look for 'AutoVue Integration SDK' documentation for the release you are working with.  Hope this summary is useful!    Warren 

There are a number of different ways that AutoVue can be customised to better serve user's needs, and I've occasionally talked to people who weren't clear on what the best approach was for what they...

Administrivia

User defined views in AutoVue

Last year I wrote about a feature that I felt was underutilizedin AutoVue: Real-Time Collaboration with AutoVue. Today I want to write aboutanother feature that is underutilized and maybe misunderstand. User definedviews. Recently a customer wrote me to tell me how user defined viewswere great but the fact that he had to redo them each session was annoying andtime consuming. First let me review what a user defined view is. In AutoVue,under the view tab, users are able to create views of the model that best fits theirneeds, they can rotate the model, explode it out, make certain pieces transparent,etc. Many of these views can be made during a session and by “clicking” on one ofthe views the model is brought back to that position. For more information on User defined views and other AutoVuefeatures and functionality see our user guide.  In the image below I have created 2 User views, Exploded andTransparency, I can switch between these or any of the pre-set views in theview tab. Here is what the user who wrote to me did not realize, youcan create user defined views in Markup mode and save them as part of a markup.As shown in image 2. This means that you only need to create a certain viewonce, save it and it will remain a part of that markup associated with thatfile. This feature makes it easy to save a specific “view” of amodel that can be user again and again for a variety of reasons.

Last year I wrote about a feature that I felt was underutilized in AutoVue: Real-Time Collaboration with AutoVue. Today I want to write aboutanother feature that is underutilized and maybe...

Tips and Techniques

Uploading assemblies and other multi-part CAD documents (Xrefs) in AutoVue 21.0.0

Hi all, I wanted to give a quick overview of one of the changes in AutoVue 21.0.0 that I've heard a few questions around.  Many complex CAD documents span multiple files - there will be a base document (often called an assembly in 3D CAD), and a series of associated files that we broadly call external references or Xrefs (often referred to as Parts or sub-assemblies in 3D CAD).  The way these Xrefs are handled when uploading a file from local disk (not when integrated into a system like Agile, P6 or Web Center Content) has changed in AutoVue 21.0.0, and I'll give you some additional details on that here. In earlier versions of AutoVue there was a mechanism in place that allowed the AutoVue server to request missing Xrefs from the AutoVue client.  The way it worked was that if the user did a 'file open' on a file named 'Assembly1.asm' from their local hard drive, it would get copied to the AutoVue server and processed.  If during that processing it found that it needed a file named 'Part1.prt', the server would tell the client, and the client would search the local filesystem for a file named Part1.prt, and if found, it would copy that file to the AutoVue server.   That process would repeat until all of the associated subassemblies and parts were copied to the server.  This process has a couple of problems: Performance is problematic, since the copying of files happens as a series of separate transfers, with some processing of the file in between There is a risk of unexpected results.  The algorithm used to find files on the client side was pretty good, but there was a risk that if the files and folders were not set up the way we expected that we might find *some other* local file named "Part1.prt",  and the user might see the wrong part in the model. As a result, starting with AutoVue 21.0.0, this mechanism of finding and uploading local Xrefs has been removed, and our recommendation is that if you need to open a file with Xrefs from a local file system, that you do it by creating a zip file containing the base file and all Xrefs, and then opening the file through the zip file.    This ensures that AutoVue gets all of the right Xrefs, and improves performance by sending all of the files in single transfer. To reiterate - this only impacts files coming directly from the user's local filesystem - if you are integrated into a content management system, and are opening a file from that system, it will take care of providing all of the associated Xref files to the  AutoVue server for you automatically, and this change will not impact you.  If you have any questions about this change, feel free to ask below! Warren 

Hi all, I wanted to give a quick overview of one of the changes in AutoVue 21.0.0 that I've heard a few questions around.  Many complex CAD documents span multiple files - there will be a base document...

Administrivia

AutoVue for Agile 21.0.0 is Now Available!

We are pleased to announce the availability of Oracle’s AutoVue for Agile Enterprise Visualization 21.0.0, a major release within the 21 product family, on the Oracle Software Delivery Cloud. With this 21.0.0. release, Oracle delivers it’s next generation 3D visualization framework in AutoVue for Agile, providing best-in-class support for core 3D formats and boasting significant 3D performance and fidelity improvements. AutoVue for Agile release 21.0.0 also includes view handling improvements specific to Model-Based Engineering and continues to deliver on usability enhancements.  Agile 9.3.5 customers will also benefit from improvements related to the creation and access of AutoVue markups in the context of Oracle’s Agile workflows. AutoVue for Agile release 21.0.0 includes the following new capabilities and improvements:  New Format Support AutoVue for Agile 21.0.0 includes support for the following new formats: SolidWorks 2015 and 2016 Creo 3.0 Inventor 2015 and 2016 AutoCAD 2015 and  2016 Catia V5-6R2013 (R23), V5-6R2014 (R24) and V5-6R2015 (R25) SolidEdge ST7and SST8 JT 10.0 Unigraphics NX 8.5, 9, and 10 (3D only) Note:The AutoVue for Agile customers are provided the following formats supported in the 21.0.0.1 patch within the 9.3.5 installer: AutoCAD 2016, AutoCAD Mechanical 2-D 2016, Autodesk Inventor 2016, CATIA V5-6R2015, SolidWorks 2015 SP2 and above for 2D files, SolidWorks 2016**To enable support for SolidWorks 2016 2D, customers need to download GA Patch 22518352 from ARU. Improved view handling for Model Based Enterprise (MBE) Support for Combined Views (PMI visibility, cut views) in Creo Improved support for Product and manufacturing information (PMI).  To learn more about AutoVue and MBE see our blog post “Model Based Enterprise - An Introduction” Simplified access and creation of AutoVue markups in Agile 9.3.5   Launch AutoVue directly in markup mode from the new Change Affected files tab, eliminating unnecessary clicks. Easily see and access AutoVue markups related to specific Affected Files regardless of the file version, revision and the associated workflow. Easily navigate through multiple files directly from within the AutoVue client using AutoVue’s Multi-content feature. New Platform Support Server: Oracle Linux server 7.X and up Client: Windows 8.1+ Click here to read about the latest features and their corresponding benefits. Click here to access the latest AutoVue Format Support Sheet.

We are pleased to announce the availability of Oracle’s AutoVue for Agile Enterprise Visualization 21.0.0, a major release within the 21 product family, on the Oracle Software Delivery Cloud.With this...

Administrivia

A Browser Page with the Link "http://jdl.sun.com/webapps/.." When using IE 11 and launching AutoVue Applet from Agile PLM

When opening a file in AutoVue from Agile Product Life Cycle Management (PLM) with Internet Explorer 11, an additional browser window with the link: http://jdl.sun.com/webapps/getjava/BrowserRedirect?locale=en&host=java.com is launched. The AutoVue Applet page opens fine and displays the file correctly.  The root cause of this additional page is that the Agile code suggests a JVM update and queries for that URL. It has this specific code inside the agile page (which can be viewed by reviewing the source page of the AutoVue Applet page)if(windowsIE=="Microsoft Internet Explorer" {....else {var time = new Date();var newWindowName = time.getTime();myWindow = window.open("http://jdl.sun.com/webapps/getjava/BrowserRedirect?locale=en&host=java.com",newWindowName);myWindow.alert("Please Install Java Runtime Environment"; The above code is causing this annoying extra page to pop up aside from AutoVue Applet page.  Support has logged Bug 22049068 with Oracle Agile PLM development team to resolve this issue but as a workaround users can use the following possible workarounds depending on their requirements: Use Firefox browser instead of Internet Explorer (IE) 11. Use an earlier IE Version than 11. Configure IE 11 to use "Enterprise Mode" as specified in the following page: https://technet.microsoft.com/en-us/library/dn640699.aspx

When opening a file in AutoVue from Agile Product Life Cycle Management (PLM) with Internet Explorer 11, an additional browser window with the link: http://jdl.sun.com/webapps/getjava/BrowserRedirect?l...

Tips and Techniques

Support for Creo Combined Views in AutoVue 21

Hi all, I wanted to say a little bit about one of the new features in the recently released AutoVue 21: support for Creo's 'Combined Views' capability.   Combined views are a pretty key feature when working with Model Based Designs (MBD) - you can see a bit of background on this here: https://blogs.oracle.com/enterprisevisualization/entry/model_based_enterprise_an_introduction  - when building an MBD in Creo, it is very common to add views that capture a particular aspect of the model that will be important for some aspect of the product's process - assembly, maintenance etc.   The combined view feature in Creo allows you to create views that substantially filter down what is shown to the user - hiding parts that aren't relevant, hiding PMI information that isn't relevant, even doing a cut through the model to show exactly the part of the model that is relevant. In previous releases of AutoVue, all that we supported was the camera viewpoint for these views - so you would see that entire model and all PMIs, but from the correct view port.   This makes it very hard to see what was intended by the designer. In AutoVue 21, we support all of the aspects of the combined view, so you will see the model just as it was intended in Creo. This will be very valuable for anyone working in a model based enterprise - but will also be useful for many other users of Creo. Happy visualizing!

Hi all, I wanted to say a little bit about one of the new features in the recently released AutoVue 21: support for Creo's 'Combined Views' capability.   Combined views are a pretty key feature when...

Administrivia

AutoVue 21.0.0 is Now Available!

We are pleased to announce the availability of Oracle’s AutoVue Enterprise Visualization 21.0.0, a major release within the 21 product family, on the Oracle Software Delivery Cloud. With this 21.0.0. release, Oracle delivers AutoVue’s next generation 3D visualization framework, providing best-in-class support for core 3D formats and boasting significant 3D performance and fidelity improvements. AutoVue release 21.0.0 also includes view handling improvements specific to Model-Based Engineering and continues to deliver on usability enhancements AutoVue release 21.0.0 includes the following new capabilities and improvements:  New Format Support AutoVue 21.0.0 includes support for new versions of popular 3D and 2D CAD formats SolidWorks 2015 Creo 3.0 Inventor 2015 AutoCAD 2015 Catia V5-6R2013 (R23) and V5-6R2014 (R24) SolidEdge ST7 JT 10.0 Unigraphics NX 8.5, 9 and 10 (3D only) AutoCAD 2015 Improved view handling for Model Based Enterprise (MBE): Support for Combined Views (PMI visibility, cut views) in Creo Improved support for Product and manufacturing information (PMI). To learn more about AutoVue and MBE see our blog post “Model Based Enterprise - An Introduction” New Platform Support Server: Oracle Linux server 7.X and up Client: Windows 8.1+ Click here to read about the latest features and their corresponding benefits. Click here to access the latest AutoVue Format Support Sheet.

We are pleased to announce the availability of Oracle’s AutoVue Enterprise Visualization 21.0.0, a major release within the 21 product family, on the Oracle Software Delivery Cloud. With this 21.0.0....

Tips and Techniques

Controlling Headers, Footers and Watermarks when Printing

Hi all, We've had a few requests for this via support recently, so I thought it would be useful to share here how you can control the appearance of headers, footers and watermarks for AutoVue users when they print. As a refresher - AutoVue allows the addition of headers, footers and/or watermarks when printing, and each of these can include attributes from the repository where the files are stored, such as approval status, when it was last modified, etc. Under normal conditions, the user can set each of these interactively when printing a document. However, there are INI options that can be set server-wide to provide defaults for each of these, *and* the user can be disallowed from changing these settings in cases where every document that is printed must have standard information added to them. More information about the INI options to set up headers, footers and watermarks can be found in sections 9.8 and 9.9 of the Viewing/Configuration Guide (the 20.2.3 version can be found here: http://docs.oracle.com/cd/E60531_03/otn/pdf/E60462_01.pdf ) The key is that after you have set up the headers, footers and watermarks to contain the information you want them to, you can add "DISABLEWATERMARKS=1" and/or "DISABLEHEADERS=1" to the "[PRINTOPTIONS]" section of the allusers.ini file. Note that 'DISABLEHEADERS' actually disables both headers and footers. Happy Printing!

Hi all, We've had a few requests for this via support recently, so I thought it would be useful to share here how you can control the appearance of headers, footers and watermarks for AutoVue...

Enterprise Visualization

INSO Increases Healthcare Support Service Quality and Efficiency at San Giuseppe Hospital with AutoVue 2D Professional

INSO sistemi per le infrastrutture sociali S.p.A. is aleading international general contractor that provides engineering,construction, and related services to the healthcare, manufacturing, andservice sectors. The organization delivers complex projects—such as hospitalsor industrial and commercial buildings—from planning through construction andmaintenance. Having contributed significantly to the Italian healthcare network for morethan 20 years, INSO was contracted to extend and restructure San GiuseppeHospital in Empoli, a project that encompassed 42,000 square meters of buildingspace and included the addition of 398 new hospital beds, medical equipment andfurniture, as well as a sterilization station. In addition, INSO manages allmaintenance, cleaning and laundry services, and catering, for San GiuseppeHospital in Empoli, both with in-group resources as well as in partnership withexternal providers – such as Blue System Srl. INSO wanted to ensure high quality hospital support servicesin the San Giuse Hospital of Empoli to reduce their impact on the hospital’score business—patient care. With this in mind, they integrated Oracle’s AutoVue2D Professional with Oracle WebCenter Portal, creating an easy-to-navigate 2Dmap of the entire hospital, where users can drill down into each ward todetermine status of various supplies—such as fresh laundry and sterilegloves—and ensure timely replacements. Through the combined usage of Oracle’sWebcenter Portal and AutoVue, they managed to reduce the number of service requestsfrom San Giuseppe Hospital staff—such as hospital laundry and cateringservices—by 40% by clarifying questions upfront with OracleAutoVue 2D Professional ability to capture audit trail of decisions, changes,and approvals for compliance. Click hereto read more about INSO’s success story. 

INSO sistemi per le infrastrutture sociali S.p.A. is a leading international general contractor that provides engineering, construction, and related services to the healthcare, manufacturing, andservic...

Tips and Techniques

Diagnosing File Display Issues in AutoVue

File display issues are one of the most common issues that an AutoVue user may be faced with. With the wide array of file formats that AutoVue supports, and the large differences between the formats and their features, there are many different types of display issues that may occur.It is important to be able to efficiently diagnose file display issues to determine the root cause. Is the issue related to the user's AutoVue configuration, to the files themselves, or is it potentially a limitation within AutoVue?Common examples of file display issues include, Blank display (either fully blank or partially missing), incorrect display (position, rotation, colors, views, hatching, sizing, etc.), "Unsupported File Format" error message, incorrect display of text/fonts and incorrect display of LineStyles.There are several key steps that you can take to quickly diagnose file display issues, for example verifying that the file format that you are trying to view is supported by AutoVue and ensuring that your file format is supported by the version of AutoVue that is being used. These quick troubleshooting tips and others are explained in details in following knowledge article Note 789417.1 in My Oracle Support. 

File display issues are one of the most common issues that an AutoVue user may be faced with. With the wide array of file formats that AutoVue supports, and the large differences between the formats...

Enterprise Visualization

Model Based Enterprise - An Introduction

I've seen more discussion lately about Model Based Enterprise (MBE) and Model Based Design, and I thought it might be useful to talk a little bit here about what it is.  I'm going to start out with an overview of what MBE is today, and we'll talk about the role AutoVue plays in a future post.  Traditionally a lot of organizations have used 2D drawings to define the formal requirements of their products, and to drive communication with suppliers and partners - even when the design processes were done in 3d.    A lot of internal processes such as manufacturing and maintenance were also driven from 2D drawings.    This required engineers to develop both 2D drawings and 3D models for their products, which is complicated, and increases the cost pretty substantially.  Model Based Enterprise is the idea of driving all of these processes and communication directly from the 3D models.   This seems like a pretty great idea, so perhaps the question is: why isn't everyone doing it already?   There are a number of challenges to this however - the first is ensuring that all of the information people need can really be captured in the 3D models in a way that it can be shared internally.   In many orgs the manufacturing and maintenance people are pretty used to getting what they need as 2d drawings printed on paper - transitioning to providing them with a 3D model in digital form, and training them on how to use that, can be quite expensive.  There are a few general approaches to MBE - one common approach is to pick a relatively rich 3D CAD format such as Creo, and use the native CAD data as the model that is the basis for everything.   Another approach is to go with a neutral format that can maintain both the 3D model and all associated data, such as JT or 3D PDF.  In both cases, it's critical to provide a simple, easy to use way to let everyone in the organization get access to the 3D data that they need - which is where AutoVue comes into the picture...  But we'll talk more about that the future. For more information on MBE - check out http://model-based-enterprise.org/

I've seen more discussion lately about Model Based Enterprise (MBE) and Model Based Design, and I thought it might be useful to talk a little bit here about what it is.  I'm going to start out with an...

Tips and Techniques

Configuring Single Sign-On (SSO) for an Integrated AutoVue Environment

A common topic that our Support team receives from customers is the topic of single sign-on (SSO). Specifically, customers are interested in implementing SSO for their AutoVue environment such that users' authorization to open files from a back-end system (e.g. DMS, PLM, ERP, etc) into AutoVue is automatically handled without the user having to re-authenticate.While the overall configuration process for SSO may be somewhat complex, the AutoVue-specific aspects are extremely straightforward, and can be summarized as follows: The user must have their web browser configured to accept cookies. The AutoVue applet must be configured to forward the correct cookies (the ones required for SSO) to the AutoVue server. That's it. No additional SSO-specific configuration is required on the AutoVue client or server. The AutoVue server automatically includes the cookies when communicating the integration component (e.g. the VueLink, or AutoVue ISDK-based integration), and it's up to the network administrator to ensure that all components between the AutoVue server and the integration component are configured correctly to enable SSO.For more info regarding SSO configuration and troubleshooting for AutoVue – including a particular limitation of AutoVue's SSO capabilities with regards to the 'HttpOnly' flag – please refer to KM Note 1990144.1 in the My Oracle Support portal.

A common topic that our Support team receives from customers is the topic of single sign-on (SSO). Specifically, customers are interested in implementing SSO for their AutoVue environment such that...

Tips and Techniques

"Guided Resolution" (Interactive Troubleshooting) Flow available for AutoVue Client/Server Connection Issues

Our Oracle Support team has enabled "Guided Resolution" Flows for various products such that when you create a Service Request (SR) for a specific problem type you will see a specific set of questions that guide you through to a targeted solution. When logging a new SR for the AutoVue Client/Server Deployment Issues -> "Client/Server Connection Issues" Problem Type on any of the following products: Oracle AutoVue Office Oracle AutoVue 2D Professional Oracle AutoVue 3D Professional Oracle AutoVue EDA Professional Oracle AutoVue Electro-Mechanical Professional the Guided Resolution will be triggered and you will see screens similar to the screens below:You respond to the prompts to come to one or more solutions or to a Data Collection.You can see all of the selections and the solution. You may also change the edit button to change your selection on any level.Some options lead to Data CollectionYou may give feedback on the Guided Resolution using the Give Feedback buttonIf for some reason you aren't able to locate the right solution there is still the Next button to log an SR as usual, but the good news is that your answers will automatically be recorded in the SR and this information will be used to help us understand your issue further and to help us improve our tool.We hope you enjoy using these new tools and that you find your solutions faster than ever!

Our Oracle Support team has enabled "Guided Resolution" Flows for various products such that when you create a Service Request (SR) for a specific problem type you will see a specific set of questions...

Enterprise Visualization

Merging the Desktop and Mobile Metaphors

I am somewhat ashamed to admit that my cellphone is almost two years old - in the tech world that's almost as bad as still using smoke signals to communicate.  Despite that, my cellphone (a Samsung Galaxy S4 for those keeping score) is more powerful than (and has a much higher resolution display than) most of the computing devices I've used through-out my professional career.  That makes it perhaps unsurprising that Microsoft announced yesterday  Continuum - their intention to bring together the desktop and mobile 'metaphors' into a single device.   The idea is simple (and was in fact also proposed by Ubuntu as part of their 'Ubuntu Touch' solution back in 2013) - your phone becomes your only computing device.  If you are sitting at a desk you connect it to a keyboard/mouse/display or perhaps a laptop-like keyboard/trackpad/display clamshell, and you get get your familiar 'desktop' metaphor, but when you disconnect and use the cellphone by itself you get the same data, files, etc - but with a UI that makes sense on a 5" screen, rather than a 20" screen.What does this mean for enterprise visualization?  Instead of providing separate environments for phones, tablets and desktop/laptops, enterprise visualization systems will be able to provide solutions that morph from a phone UI - suitable for taking a photo of a problem found while onsite for instance - to a tablet UI - suitable for reviewing a change request while on the train - to a desktop UI - suitable for doing detailed design reviews, measurements, etc.   There will be huge advantages to being able to carry your entire computing environment around in your pocket - the photo you took of a problem while onsite will be right there when you are sitting at your desk creating a detailed change request, and the notes you took during a design meeting yesterday will be right there if you want to refer to them while on the train.  Of course, you may also be able to use Microsoft's Hololens to see a full-on 'holographic' display of the data off your cell phone while on the train - but that is starting to sound like it comes straight out of a sci-fi novel...

I am somewhat ashamed to admit that my cellphone is almost two years old - in the tech world that's almost as bad as still using smoke signals to communicate.  Despite that, my cellphone (a Samsung...

Administrivia

Real-Time Collaboration With AutoVue

I have been working with AutoVue for more than 15 years now and when I first started talking to customers, way back when, about what features they would like to see added to AutoVue many said they would like to be able to share what they see on their screen when using AutoVue with others. I remember one person I met at a trade show telling me this feature alone would save him the time and expense of a monthly trip to Texas from his New York office to review CAD files with his people there. For him and others like him, who needed to share their data in real time, we came up with AutoVue’s Real-Time Collaboration tool or RTC. This has been a part of AutoVue for a number of years now and, in my opinion, I think it is still under-utilized by our customers, and that is a shame because RTC can help organizations to connect everyone securely via the web, be it employees, partners, suppliers or customers, they can communicate as if they were in the same room, even if they are located on the other side of the world. They can  share ideas, inspect and markup documents, assign action items, and resolve design issues, all in real-time. Because of this, users can streamline communication, drive innovation, and expedite document and design reviews throughout the product or asset lifecycle without ever setting foot in the same room. Exactly what that gentleman from New York was looking for all those years ago. AUTOVUE REAL-TIME COLLABORATION FEATURES: • Simultaneous viewing and markup of documents via the web• Identify contributors feedback with color-coded markups and chat• Create an audit trail and capture session information• Investigate areas of a document privately during a session using Unlock View• Show Tracker Window allows unlocked participants to track the common view in a separate• Pause sessions and resume them at a later time Here are 2 users that can be thousands of miles apart but they can see the same information on their screen and see each other’s comments, in real time, and of course everything is saved for future reference  Read more about AutoVue Real-Time Collaboration Here Watch a video that features  Real-Time Collaboration: Visual Decision making within the Supply Chain

I have been working with AutoVue for more than 15 years now and when I first started talking to customers, way back when, about what features they would like to see added to AutoVue many said they...

General Info

Understanding the Event Framework in the AutoVue API

When designing and developing custom solutions using the AutoVue API, it’s crucial to understand not only the core “VueBean” component but also the event framework that the VueBean uses for notifying of and listening for different types of events. There are various types of events depending on the use-case, for example: File-related events (e.g. file open/close, page load completed, etc) View-related events (e.g. user clicked mouse, user modified configuration options, etc) Markup-related events (e.g. markup open/close, markup entity added/removed, etc) Model-related events (e.g. entity added/removed, user entered specific mode, etc) If your custom AutoVue solution involves sequences of actions against files, file contents, markups, and so on, handling of the appropriate events is important for ensuring that your custom code is synchronized – For example that you don’t start adding markup entities to a page of a drawing before that page has finished loading.For more details on the event framework, refer to the AutoVue API Developer’s Guide for your particular version of AutoVue (available on the OTN website). For details regarding the individual events themselves, refer to the AutoVue API Javadocs included in the AutoVue installation (within the \docs folder). If you have questions that aren't answered through the docs and Javadocs, feel free to post in the AutoVue Integrations Forum.

When designing and developing custom solutions using the AutoVue API, it’s crucial to understand not only the core “VueBean” component but also the event framework that the VueBean uses for notifying...

Enterprise Visualization

HoloLens - "Holographic" Visualization?

I've been thinking a bit lately about the 'HoloLens' technology that Microsoft announced at the end of January (http://www.microsoft.com/microsoft-hololens) - and how it could apply to enterprise visualization.   If you haven't read any of the reports from people use have tried the system out, I'd suggest checking those out as well as Microsoft's information on it.   http://arstechnica.com/gadgets/2015/01/hands-on-with-hololens-making-the-virtual-real/ and http://www.engadget.com/2015/01/21/microsoft-hololens-hands-on/ might be good options.I've been intrigued by 'Augmented Reality' for a while now, but it seems like Microsoft may be on the way to providing a really solid solution for mixing 3D visualizations and the real world.   I haven't been able to try one myself yet, but from the reports of people who have, they were able to see well-defined, well-detailed 3D models accurately overlaid on the real-world images in front of them - and tracking well and accurately as you moved your head and body around.  This is very different from most of the existing augmented reality systems, and sounds much more compelling than something like Google Glass.This could open up some pretty interesting scenarios for enterprise visualization.   One of the examples Microsoft uses on their site is actually a product design example, showing a blending of a real product with some 'virtual' parts.   I can't think of a better way to review proposed design changes to a product than being able to see those changes overlaid on top of the current model of the product.The technology also enables hand tracking - so you would be able to interact with the model as well.   Perhaps reaching out and tapping on a component and then speaking your comment out-loud would be enough to start a change request process.Of course, Microsoft hasn't announced a firm release date for this technology, so I think it will be a while before we see this being used in enterprise visualization environments - but it's the first time I've seen something that looks like it could convincingly replace a traditional keyboard/mouse/monitor for some enterprise visualization tasks.

I've been thinking a bit lately about the 'HoloLens' technology that Microsoft announced at the end of January (http://www.microsoft.com/microsoft-hololens) - and how it could apply to enterprise...

Administrivia

AutoVue for Agile 20.2.3 is Now Available!

Oracle’s AutoVue for Agile Enterprise Visualization 20.2.3, a minor release within the 20.2 product family, is now available on the Oracle Software Delivery Cloud. AutoVue for Agile release 20.2.3 includes the following new capabilities and improvements: New Format Support AutoVue for Agile 20.2.3 includes support for new Office, MCAD and ECAD formats. New Platform Support •    Java SE 8 and higher Java Virtual Machine (JVM)•    Windows Server 2012PDF Improvements for Package & Label Management Workflows:•    Substantially faster rendering for complex PDF files: Files that include complex gradient fills will see a substantial increase in rendering performance with AutoVue for Agile 20.2.3•    Support for Overprinting Fills: This is a feature in PDF and Adobe Illustrator that allows the creation of very specific effects when printing the resulting document. AutoVue for Agile 20.2.3 adds support for this feature, allowing users to easily complete their review  Performance improvements When using AutoVue for Agile with Agile 9.3.4 •    Please see What’s New in AutoVue for Agile 20.2.3  for details•    Learn more about Agile 9.3.4  hereOther features Include•    Usability Improvements•    Security ImprovementsNote: AutoVue For Agile 20.2.3 is certified with Agile 9.3.4, 9.3.3, 9.3.2, 9.3.1.x, 9.3.0.xClick here to read about the latest features and their corresponding benefits. Click here to access the latest AutoVue for Agile Format Support Sheet.

Oracle’s AutoVue for Agile Enterprise Visualization 20.2.3, a minor release within the 20.2 product family, is now available on the Oracle Software Delivery Cloud.AutoVue for Agile release 20.2.3...

Tips and Techniques

Setting up the ABV Sample with Agile 9.3.3

Hello all,As we wrap up things towards the end of the year, I wanted to talk a little bit about how you can set up our Augmented Business Visualization sample PX with Agile 9.3.3.   If you are running Agile 9.3.3, and are using Agile EC to manage your 3D CAD data, it is quite simple to set it up so that users can create new ECRs or ECOs directly from the 3D view in AutoVue.   There are a couple of constraints around the sample PX - for example, you need to have the CAD connector configured so that the part, design and CAD file name all have the same name - but the PX is relatively easy to extend if this doesn't apply in your environment.If your 9.3.3 system matches the constraints of the PX, all that is needed is to copy the PX file into the Agile extension folder - Once the PX is installed, you will be able to right click on any part in your 3D models, and create an ECR or ECO - and have the current assembly and the part you selected added as an affected item to the new object.You can see what this looks like in action in a video on our youtube channel with the link below: There is a whitepaper that describes in more detail how the PX sample works, and gives advice on how to set it up and extend it if necessaryThe sample PX and the whitepaper can be found on OTN: http://docs.oracle.com/cd/E49948_05/otn/doclist.html  - the specific links are Whitepaper  and PX Sample I'll close with wishing you all a happy holiday season whatever holiday you may choose to celebrate, and a happy new year!   We'll talk again in 2015!

Hello all,As we wrap up things towards the end of the year, I wanted to talk a little bit about how you can set up our Augmented Business Visualization sample PX with Agile 9.3.3.   If you are running...

Administrivia

Times and dates now confirmed for Enterprise Visualization Sessions at the Oracle Value Chain Summit, January 26-28, 2015

Attend Two Must See Visualization Sessions in the PLM and Cross-Value Chain Pillars Leverage CAD Design Integration for IP Management with Engineering Collaboration and Visualization Product companies often struggle with the generation, control and use of CAD-authored documents and IP in tandem with PLM. Learn how Agile customers can streamline their engineering design and document management processes by leveraging their engineering tool environments for document generation and release to PLM. Hear how customers who have implemented Agile's Engineering Collaboration and Enterprise Visualization tools use Agile Product Collaboration for document management and control and Enterprise Visualization for universal document access and review.Date:               Tuesday, January 27, 2015Time:              3:45 p.m.–4:45 p.m. Customer Speaker: Marty Kret, Director, Engineering Services, Pacific Scientific Oracle Speakers: Celine Beck, Sr. Manager, Product Management/Strategy, Oracle                              Warren Baird, Principal Product Manager, Oracle                              Lance Conard, Principal Sales Engineer, Oracle                              John Loechli, Senior Product Manager, Oracle  Oracle Fusion: Pioneering the Consumerization of the Enterprise The enterprise application world is changing. Social, mobility, cloud, big data and consumer apps are all generating higher user experience demands and expectations. Join this session to see how Oracle's current and future innovations in user experience combine the best from the consumer and enterprise worlds to create the consumerization of the enterprise. Explore business data in the same way you navigate social networks and mapping services. Manipulate information, define business rules and create ad hoc reports graphically. Define what's most important to you, and have it at your fingertips. Do all this from Oracle’s applications’ highly intuitive and context-aware user experience platform.Date:             Tues. Jan. 28, 2015Time:            1:30 p.m.–2:30 p.m. Speakers: Thierry Bonfante, Senior Director, AutoVue and Visualization Development                 Rozita Naghshin, Sr. Principal Product Manager-VIN, Oracle                  Celine Beck, Sr. Manager, Product Management/Strategy, Oracle Drop by the Enterprise Visualization/Fusion Visual Information pod in the exhibit hall to  see the latest in Visualization technology from Oracle.  See the Agenda for the Value Chain summit here.

Attend Two Must See Visualization Sessions in the PLM and Cross-Value Chain Pillars Leverage CAD Design Integration for IP Management with Engineering Collaboration and VisualizationProduct companies...

Tips and Techniques

Analyzing AutoVue’s File Load Time Performance

As organizations continue to increase their volume of digital content, migrate business processes to software-driven frameworks, and expand the complexities of the underlying software/hardware architectures, system performance becomes an increasingly important success factor. In the world of AutoVue, the most important aspect of performance is file load time – the time it takes from when the user clicks “Open” or “View in AutoVue” to when the file is displayed and the user can start working with it. There are many factors involved in file load time, including: Deployment architecture Specifications of each node Configuration of each node Network performance System load Customizations/extensions Etc. A proactive approach to performance tuning requires expert understanding of the network and all involved nodes (e.g. load balancers, firewalls, proxy servers, application servers, DMS/PLM systems, AutoVue servers, client machines, etc) as well as load-testing prior to go-live. In addition to proactive planning, many customers identify the need to continue performance tuning after go-live, as the usage patterns evolve. Dissecting the performance bottlenecks of file load time requires collecting various information including configuration settings and log files. In order to provide general guidelines for this process, our Support team authored a 2-part troubleshooting whitepaper which is published in the My Oracle Support knowledge base: Note 1595727.1 - AutoVue Client/Server Performance Troubleshooting Guide -Part I- Note 1605087.1 - AutoVue Client/Server Performance Troubleshooting Guide -Part II- I highly recommend this read for any AutoVue admins and SIs interested in file load time performance analysis – whether it be during pre-go-live planning stages, or during ongoing system maintenance.

As organizations continue to increase their volume of digital content, migrate business processes to software-driven frameworks, and expand the complexities of the underlying...

Enterprise Visualization

Enable Collaborative Product Development

Increasing rates of globalization and outsourcing, as well asrapidly-changing competitive environments have changed the landscape forcompanies and created new organizational complexities that oblige them tostreamline their product development processes. Companies like Alkan,GLOBALFOUNDRIESand SigmaTronInternational who have taken advantage of enterprise visualization solutionslike Oracle AutoVue integrated with PLM like Oracle Agile PLM have been able tospeed up time to market, streamline operational efficiency and boost innovationby enabling collaborative product development. AutoVue for Agile enables companies to easily extend the reach of productinformation and related CAD designs stored in Agile PLM to non engineeringteams. By facilitating access to CAD data, teams typically underrepresentedduring the innovation process can easily participate and contribute feedback onproduct data early in the development cycle maximizing innovation andproductivity. Users can easily capture and communicate comments, suggestions andproposed changes directly within the context of designs. Communication with external parties can also be optimized throughoutthe NPI / NPD process without jeopardizing critical intellectual property.Critical product designs can be made accessible to suppliers through Agile PLMand viewed in AutoVue for Agile, without leaving the Agile PLM server. No localcopies are being created while files are being viewed in AutoVue by externalparties, ensuring that critical IP remains under your control. Thus, Alkan, a leadingaeronautical equipment manufacturer in France, uses Oracle AutoVue for Agile tomanage ITAR compliance by ensuring only authorized personnel have viewingrights to certain, sensitive defense-related documents (click hereto read the complete story). It is also possible to use AutoVue for Agile to protectsensitive information by restricting access to certain comments and redlinesadded in AutoVue. This way, you can ensure that suppliers only have access tothe information you want them to see and have access to in order to supportyour business operations. To learn more, check out our videoon the Oracle AutoVue Youtube Channel

Increasing rates of globalization and outsourcing, as well as rapidly-changing competitive environments have changed the landscape forcompanies and created new organizational complexities that...

Enterprise Visualization

SigmaTron International Automates Workflow, Shortens Engineering Change-Order Sign-Offs by Four Days

SigmaTron International Inc. is a contract manufacturer of printed circuit boards (PCBs), wiring assemblies, and turn-key electronic products, serving original equipment manufacturers (OEMs) in the telecommunications, appliance, industrial, fitness, medical, and aviation sectors. The company has industry-certified manufacturing plants in the United States, Mexico, China, and Vietnam. At any time, SigmaTron is processing and managing information on several thousand assemblies, with tens of thousands of components, over seven manufacturing sites.SigmaTron’s customers look to the company to help accelerate their times to market. As such, the company must be able to effectively collaborate with its clients, including managing documentation for and changes to the very complex and often highly-customized products it manufactures. Sharing product information with the various stakeholders in the engineering and manufacturing process is essential.After acquiring multiple companies, SigmaTron began to struggle with integrating various silos of electronic-product documentation, spanning multiple continents. The company had been using Oracle’s Agile Product Collaboration in one facility to effectively track engineering change orders (ECOs) for its high-tech telecom and medical-industry customers. It looked to expand use of the solution to new locations to facilitate product lifecycle management across the growing enterprise.To establish a single system of record for all electronics product information, SigmaTron upgraded its Agile Product Collaboration and extended the implementation to two other manufacturing sites. With the upgraded solution, SigmaTron improved manufacturing efficiency and its ability to adapt and customize products to meet specific customer requirements. With improved product data transparency and collaboration across borders, SigmaTron now has more flexibility in scheduling production across various manufacturing facilities—which helps it to better balance production. The company is also benefitting from prebuilt integration between Oracle’s AutoVue enterprise-visualization solutions and Agile Product Collaboration—facilitating document review and supporting real-time collaboration, while reducing reliance on physical documents. Click here to read the complete story

SigmaTron International Inc. is a contract manufacturer of printed circuit boards (PCBs), wiring assemblies, and turn-key electronic products, serving original equipment manufacturers (OEMs) in thetele...

Administrivia

Times and dates now confirmed for AutoVue and Fusion Visualization Sessions at Oracle OpenWorld 2014

Be sure to check out the various AutoVue and Fusion Visualization activities atOracle OpenWorld 2014 AutoVue and Fusion Visualization Sessions: CON8380 - Design Document Management andVisualization with Agile Product Lifecycle Management. Clickhere for full session description. Speakers: Devendra Singh - Vice President Product Development, Oracle                   Thierry Bonfante - Senior Director Product Development, Oracle Date:        Thurs Oct. 2, 2014      Time:        11:30 am - 12:15pm                          Location:  Westin Market Street, Franciscan II CON8286 - Pioneeringthe Consumerization of the Enterprise . Clickhere for full session description. Speakers: Thierry Bonfante  - Senior Director Product Development, Oracle                    Celine Beck  - Sr. Manager Product Management / Strategy, Oracle Date:        Thurs Oct. 2, 2014                             Time:        9:00 am - 9:45am                           Location:  Westin Market Street, Franciscan I OtherActivities: MTE8360 - Meet the Supply Chain Management Experts Drop by and meet the Enterprise Visualization experts along with other expertsin all aspects of the supply chainSpace is limited, and preregistration is recommended. Clickhere for more information Date:        Wed, Oct 01, 2014                            Time:        2:45 pm - 3:30 pm                          Location:  Westin Market Street - Metropolitan III

Be sure to check out the various AutoVue and Fusion Visualization activities at Oracle OpenWorld 2014 AutoVue and Fusion Visualization Sessions: CON8380 - Design Document Management andVisualization...

Tips and Techniques

Enhance AutoVue's Performance with streaming files

Performance is a critical issue for most users of AutoVue - They need to be able to access documents, drawings and models to do their work, and they don't want to be watching a 'Loading' bar move when they could be approving a change request or adding a comment to a new design.There are a number of factors that can influence the final performace that users get with AutoVue - but this post will focus on one of the most important items:  Effective use of AutoVue's Streaming Files.Streaming files are a long-standing feature of AutoVue (they were originally called 'metafiles', and you may still occasionally hear someone refer to them that way) - they are a single, self-contained file that contains a 'pre-processed' visual representation of a document, drawing or model, plus a collection of attribute data.   The idea is that when AutoVue has read the native file(s) - for instance a Creo 2 assembly - it creates a streamlined form of the same data in a single file, that can be read much more quickly than the original data.For large 3D models, loading from streaming file can have a huge impact on performance - we've seen Creo 2 assemblies that were over 2 gb in size, where the native data took about 1.5 hours to load in AutoVue (and over 10 hours to load in Creo 2) but from streaming file it loaded in AutoVue in around 2 minutes.   This isn't necessarily typical, and for smaller assemblies you might "only" get a factor of 5-10x speed up - but it will still be a *very* substantial speed up.   Non-3D formats will also often get a big boost from this as well, although the speed-ups may be more like 2-5x.   PDF is an exception where you often will not see a major improvement, as well as raster formats like Tiff, and AutoVue does not generate streaming files for these formats out of the box.If you are using AutoVue with Agile, you can configure pre-generation of streaming files for all models checked in through Engineering Collaboration - For other documents and drawings what will generally happen is that AutoVue will load from the native file the first time, and will save the Streaming file in Agile so that subsequent views are done from the streaming file.To tell whether streaming files are in use is very easy - just go the the 'File->Properties' menu item - at the bottom of the 'File Properties' tab you will see it say "Loaded From Streaming File" if a streaming file was used for the current session.Ensuring that streaming files are properly configured is one of the best ways to get a quick performance boost for users of AutoVue.I'll talk about other aspects of performance in future posts.  Until then - if you have specific questions around performance or any other topic, just let us know in the comments section below!

Performance is a critical issue for most users of AutoVue - They need to be able to access documents, drawings and models to do their work, and they don't want to be watching a 'Loading' bar move when...

Tips and Techniques

New Automated Data Collection Utility for Troubleshooting AutoVue Client/Server Issues

The process of troubleshooting issues with AutoVue Client/Server Deployment (for example, users suddenly unable to connect to the AutoVue server) sometimes requires collection and analysis of specific files from the AutoVue server. Such files may include log files, property files, and user profile files.Historically, the collection of these files was a manual process. Recently, however, the Oracle Support team released a new automated data collection utility called “AVCollect” (short for “AutoVue Collect”) to simplify this task. The tool is a lightweight Java-based application that runs directly from a Jar file, and collects the abovementioned files as well as the timestamps of the AutoVue server runtime libraries. This automated approach speeds up the data collection process and ensures that the correct files are gathered.Future enhancements to the utility are underway, including the ability to collect the AutoVue server diagnostics output, system-level info, and so on. For now, make sure your AutoVue server administrators download and familiarize themselves with our first release of the AVCollect tool via the following knowledge base document:Note 1677441.1 - Using the AVCollect Tool to Automatically Collect AutoVue Server Log Files and Configuration Files And as always, if you have any additional suggestions for the tool, feel free to share them through the AutoVue MOS Community.

The process of troubleshooting issues with AutoVue Client/Server Deployment (for example, users suddenly unable to connect to the AutoVue server) sometimes requires collection and analysis of specific...