Transcript for "What's New in Canvas Envision": Hi, everyone, and thank you so much for joining us today. In this session, instead of walking through a list of new features, I wanna show you how all of these capabilities come together into one connected workflow. And that workflow is really the story you will see here from knowledge to execution. Most manufacturers already have a huge amount of valuable knowledge. You have PDFs, CAD, you have PLM data, you have videos, images, and, of course, all that knowledge that lives in the heads of your experienced people. The challenge usually isn't that the knowledge doesn't exist. The challenge is turning all that knowledge into something visual, consistent, and easy to maintain, and most importantly, useful to the person actually doing in the shop floor. So today, we're going to follow that journey. We will start with the knowledge you already have. We will create with AI and standardize with templates, layouts, and then enrich that content with context and move into execution and then close a look with usage and improvement insights. And I'm going to show you quite a bit of the actual product along the way, so it's not gonna be just a PowerPoint slides, in this webinar. And at the end, we will also cover some of the additional highlights from our InVision 6.2 version that we recently launched in September. Please feel free to submit, any of your questions in the chat as we go. I have a great team here who can help answer them along the way as I present. So before, I jump into new, features and functionalities in Envision, For those who, doesn't know Envision, I wanna quickly introduce our platform. At its core, Envision is a web application platform that connects engineering knowledge to the point of work in the shop floor. On the left is the information you already have. You have CAD, three d models. You have PLM, documents, images, videos, and, the expert knowledge that goes into the Canvas InVision platform. In the middle, you have the three connected InVision experiences. Creator is where the content is built and, altered by your creators, and you have portal where that content is managed, published, and controlled. And the operator is where the person doing the work consumes that information, where the contact is interactive and they have digital experience. And EV is part of the authoring workflow. It helps you to turn existing knowledge into content rather than forcing authors to start over from a clean slate. And when we expand the picture, this is where the platform story gets a little bit more interesting because the goal isn't, to create another isolated application. InVision can work with the systems you already have in the organization. You can connect InVision to PLM, MES, QMS, or any other systems like ERP in your organization. You have APIs and SDKs. And from a deployment perspective, we have options like, Azure or AWS cloud services, private cloud, as well as on premise... On premises deployment. Now let's look at, the new InVision experience. Each part of InVision now has its own clear identity and color. Creator is blue where the authors create the content. The portal is red where teams manage and publish the content, and operator is teal where the person doing the work views and follows the instructions. Colors makes it easy to know where you are, but all three experiences are still connected by the same content and workflow. So this is where our story really begins. We are not really starting from a blank page, and I think this is incredibly important because when people hear AI authoring, there can be assumption that we are asking AI to invent the process. This is not what you really want. Your organization already knows how to build the product. You already have PDFs, images, engineering data, and years, sometimes decades of travel... Decades of travel knowledge. So the question is, how do we use that information more effectively? Instead of recreating the content manually, we want to transform it. And I'm going to start with probably the most common example of existing knowledge in manufacturing, the PDF. So a PDF may contain valuable information, but a PDF is still fundamentally aesthetic document. So let's see what happens when we give that existing knowledge to Eevee. In this example, I'm starting with an existing Barachio, robotic arm document as an assembly instruction, and we will watch the workflow here. So we'll watch the workflow here in this video, and I'm gonna show you how, we're not building the 20 pages manually. We're gonna ask Evie to understand the source, identify the assembly steps, bring the visuals across from the PDF to Envision document, and help us to create a structured interactive instructional content. So let me play the video here. We open the browser. So here's, is it is it our document that we're attaching to Eevi? And we're telling Eevi simply to create interactive instructions for this robot arm using the attached, quick start guide as the source. And Eevee is going to start parsing that information and basically will build each step for us in our envision environment. This processing prompt us some... With some questions in terms of, what type of information should include, who is this documentation will be addressed to, and also, some more information depending on the PDF that you're feeding into Eevi. And it's processing that information further and basically going through each page, and it's building as it goes and processes that information. And the authors can see the progress, while in the... While Evie is working, on that. So here, we're going to ask further, editing to Eevee simply like changing the text sizes to 32 in this example, of the header. And as you can see, it will go through and process each page to adjust the title for us. So we'll further ask to add an annotation mask, which is a magnifying functionality in InVision, and to add that into areas that visually hard to understand for the operators, and it will add that to our content where it is needed, and it will analyze that information for us. As you see, it added to the pages, individually where it needs them. This is the operator view of this of this documentation that it created for us every page, and then operator can navigate through our, page navigation gadget inside of InVision. And we will also see at the end, how an operator can go to a specific page if needed a more clear understanding of of a step that they thought they were following. Once we, once we create faster the content with EV, the next question becomes, how do we keep that con... Content consistent across all the documentation we have also across the organization? And that brings us to templates that we recently introduced. Templates templates allows teams to define the structure once, like company branding, any kind of standard structure that they use in the organization, safety information, tools, and any kind of, the quality information that they need into... In the content that they use. So faster altering doesn't mean, less control, but with the templates, we can make this more efficient and standardized. So let me play this video in the browser in the full screen again. Here we can see all the templates that are already built in in Canvas and Vision. You can also build your own template with specific, settings like you see in the in the dialogue box. And once that's done, you can save your documentation as a document from the template, and then that extension of EVTPL is gonna become an EV... InVision documentation. EVTPL is gonna become an EV doc, and now you have the title of your document. And the templates can be stored in a template center. We have a template center in the in the portal that you could see all the templates that you have inside of your organization. A template can tell Otter what the page should look like, but we also wanted to go one step further with the layout objects. Here is a look of, UI that shows the home ribbon, how those layout objects can be found. You have the text layout object and the content layout object that can contain three d models, images, and other content you have in in your document. We also have prompt, objects that Eevee can read and understand which object should go where in your documentation. So now that Eevee has, its structure, the next thing is to feed Eevee with the context. The... Because the quality of AI output is heavily dependent on the information it gets. And that context doesn't have to be only text or PDFs. Eevi can also work with three d models, and videos as well as images and processes that information for you to add into your digital work instructions. So this next example, I really like... We're challenging Eevee to build, work instructions directly from an engineering model, and make it digital work instructions for the, for the operators. So let's play the video, and I will walk through, how it works. So this is a demo model that we're gonna use in this example. Here, I'm prompting Evie with, one of our workflow agents create step by step instructions from a three d model. Evie is asking me to import that model into Envision, And here, I'm selecting the related information that I need with that model, and the model comes inside of Envision. And Eb prompts me to some questions on how it should use that three d model inside of my content. And you have options to choose from, while answering those questions. Obviously, you wanna QC your model. You wanna understand your design data before, but it starts analyzing that information. If the order you need to change in the MBOM, that's an... Also an option that in... DB asks you, you have that option to do so. It's gonna be processing that information for us. And you see, it will create that 13, steps from this assembly, one by one, reading and understanding the assembly information. And then, obviously, you have an option to change and edit anything that you want. And further, in this new release, we have an option to create animation using these views, directly by a v... Directly by Eevee. And, I'm prompting, Eevee to create, assembly animation in this case, and it's going to be, creating for us. So here is the operator view of this model created, of these instructions created by this model, page by page. And as you see, the operator can interact with each view as they go and, look and understand this information, these instructions. And at the end, we will also see the animations that has been created by Eevee. You can customize these animations inside of InVision by basically editing the animation, by using the animation feature inside of InVision too. So when we feed the information to Eevee, like PDF or three d models, there is an interesting problem that comes with the AI. Sometimes AI simply doesn't understand the information that we're feeding or it doesn't have enough information. And when that happens, I would much rather Evie to ask than guess that information. And that's the idea behind prompt, which is that we recently built in Canvas InVision. So, let me play the video, here while I go through, the prompt widgets as well. Let's just open that in the browser too. So here, three d instructions, feeding the three d model, and Evie is prompting with questions, to... For us to decide on the outcome instead of guessing the work that is going to be doing. And in this case, who's the audience that is gonna read the instructions, what type of layout they should use. You could still leave it to Eevee to decide, but you have an option to, pick and choose from. And this specific example is asking how do we wanna treat, the each view. Is it, exploded? Is it zoom feature, or is it a, ghosted background? You have options to choose, as well. And here, like we saw in the previous example, the order of the assembly, as an author, you have a full say in the order of your assembly that the EV is going to build for you. It's a small interaction, but concept... Conceptually, it's a big shift. Instead of, you know, black box AI, we're creating a collaborative, alternative experience with EV. And everything we talk about with AI is meant to accelerate the offering in InVision. However, we also added lots of creator features in our recent releases. There are two important ones that I wanna share in this webinar. The first one is a three d view to timeline that helps you to create animations faster. Another one is prebuilt safety symbols that could help you to standardize your documentation and share throughout the organization. So let me play the first video, so I can walk you through each step. Let me just put this in browser and open the big screen. Oh, sorry. It's playing already. So here, we're gonna see a new three d model that is already imported into Canvas Envision, and the author is creating, different three d views, basically using the three d edit features inside of Canvas and Vision. So we're gonna create an exploded view, moving some parts, and some translated views, capturing those with the three d view... In the three d view... Three d views pane. One by one. And once the sequence is built that we wanted to, create inside of Canvas InVision, now we can drag and drop those views into the timeline... Animation timeline to create animations. So Envision, is going to look at those views from different perspectives that you have in your timeline and simulate between those views and create the animations for the authors to, to see. And, obviously, you see that you have all the functionalities in here to edit this animation, but it gives you that first quick animation that you could see, without any efforts, and then go back to here. And now we're gonna see the safety symbols. Let me put this in the browser and then play this in the bigger screen. And the visual content isn't only about three d. Sometimes the fastest way to communicate something is a symbol, the operator recognizes instantly. So here, I'm going to show you how we have built in, symbols inside of Canvas and Vision now. So instead of hunting, through other systems, for the right safety graphic, I can search the... If I... Available ISO symbols right here in the... Inside of Canvas Envision, and then you can, place them directly into your instructions, where it has the context. So here, some examples that you see the creator can search and place them into their their content. And then this gives the operator a familiar visual signal, without interrupting their workflow. And sometimes that visual cue communicates the next action faster, than another paragraph ever could. So this is very important visual information that we built inside of Canvas and Vision in this new release. Now we move to execution, and this is where work instruction becomes much more important than something you simply read on the shop floor. Because in the real world, we sometimes need the operator to do something before continuing to next step. Confirm readiness, enter measurement, basically record a serial number or acknowledge something like a PPE, or any kind of tracking some information, or track how long a step takes, can take. And that's where the gadgets come in that we introduced this year. Let me play the video so I can walk through the features. Here, the instruction begins with the readiness check. The operator has to confirm the required tools before they can, move forward. Here, we have the data capture, basically getting the tool information. Here we have ordering parts directly from your BOM, and, any kind of feedback or questions you have in the documentation can be also stored, for the supervisors or managers to know from the shop floor. This basically closes the digital feedback loop, inside of your organization. Here is another example, that is collecting data, from the shop floor, and this can be stored inside of our, inside of your, Canvas InVision portal. Or you can use our webhooks to connect to other systems like MES or ERP. Here, we're using the stopwatch, basically taking... Trying to see how long a step can take. Another friction here that can confirm, for the operator. And then here is basically, that helps operator to see how long that epoxy is going to take, for them. And, ideally, right at the moment when they need it instead of searching through, without navigating through a complex, document. This is why we built, search directly into, the operator experience. Here you can see a simple word search, result highlighted in yellow. And, here is a more advanced part search that you could see, more options like high... Highlighting different colors and as well as, using a case sensitive, options in this, search section. And then finally, we need to close the loop. It's one thing to publish, the content, but another, thing to know whether actually people are using it. With the usage dashboard we introduced recently, admins of those workspaces can understand how the vision is being used across the organization. They can see, where... Which content is being viewed, where the adoption is growing, what is, what is being frequently used and what isn't. And, obviously, that insight becomes valuable, for reasons. It helps teams to understand adoption. It can help identify where additional training may be needed on the shop floor and which content needs to be approved. And over time, it gives you a feedback loop between the content you're creating and what is actually happening at the point of work. So the workflow doesn't really end with execute. It becomes back around to improve. I spent most of today, on the capabilities that, tells bigger story in terms of the workflow, but there are other improvements we added in 6.2, that just came out, a couple of weeks ago that I wanna mention. First of all, MFA, now can be enforced at the workspace level by the admins. That gives them stronger control over authentication. And we also continued, simplifying the SSO, making access easier for enterprise users. There are improvements around automatic child part matching, which is particularly helpful when you're working with larger updates and sub assemblies to match those parts, during the import or during the update. And now we support, PLM, number search to, find, documents using the identifiers. They're already recognized from engineering systems, like, like, PLM. We also added a public center URL, giving organizations a single, point for approved public content. And, finally, the, we are continuously, improving our three d import performance during the import by the creators and as well as the consumptions by the operators, in the shop floor. And if you like to learn more about any of these features, I will drop the release notes and links in the chat. But if you like to, deep dive... If you like to have a deep if you like to have a deep dive, just let me know. We will be happy to set up a... Just let us know. We'll be happy to set up a session and walk you through, each one of these features more in detail. So I wanna come back to where I started. This is not really a separate feature webinar. This is one connected workflow. We begin with the knowledge, the information that is already existed across your organization. We use AI and our altering tools to create fast, efficient, interactive digital work instructions. We use templates and layouts to standardize that content to make it easy to create and easy to, standardize while inside of your organization. And we give Eevee additional context to enrich, that document, either three d's, videos, or any other additional information we have in the organization. We deliver clear interactive guidance so people, operators, can execute to work, right, first time. And then we use that information that comes, that comes back continuously to improve. And that's the bigger idea behind, what we're building with Canvas Envision in each build, in each release. And with that, thank you so much for your time and, for all the great questions you asked during the webinar. See you next time.