PLM for the Equipment Manufacturer

MOONBAE SONG: Hi, everyone. I'm very excited to share a PLM case study that I experienced. This session is about PLM for the display equipment manufacturer. This company name is H& Iruja and it is one of the global leading companies in the flexible OLED SPUTTER. We have two main sections. One part that I'm going to present is the overall understanding of the customer, project scope, and what we did. Then Doohyun my colleague will explain the implementation in detail.

This is company information of Iruja. Iruja is one of HN Group's subsidiaries for 160 employees. And as you can see, Iruja uses our solution for 3D design and [INAUDIBLE] also manages CAD data using ports. The main product consists of two product families, CLUSTER SPUTTER and IN-LINE SPUTTER, as is shown on the right.

What do you think about the product? It looks very complicated and it looks very difficult to manage. Yes, it is very difficult. And I want to tell business challenges of the customers.

You're saying this kind of product development way is ETO-- Engineering To Order. This field has unique characteristics and challenges. It's good to understand the challenges before we start. Firstly, delivery is more important than anything else.

It's directly related to money. If they don't deliver on time, the impact would be very huge. Therefore it's very important to manage whether the development is on time or not.

And design engineers engage not only in design itself in this industry, but also in purchasing, quality, and production as well. So they have to work efficiently. Without efficiency, they will go to hell, actually. And each designer should carry out several projects. It is a huge burden because as I said, engineers are also involved in other disciplines such as purchasing, quality, and production.

And the product in this area is mostly unique because it is engineered to order. After getting orders, then they start their job. So Iruja is relatively more manual work than mass production product because it is hard to automate from uniqueness. So there are strong demand for how to work efficiently and feasibility of development progress, and finally remove rework from data inconsistency.

And we are talking about business challenges in this field and this company also has a number of issues from these characteristics. First of all, product development management is difficult. Standard development process isn't there. Therefore, it's harder to know the progress transparently.

And we don't know why change has occurred and what to do with it. So that's why the same problem could happen repeatedly. And finally, the BOM is extracted from CAD, and it is then managed in single database. It is stored in each engineer's computer with an Excel formula. So the wrong data-- which means is not latest one. It could be old one. That data could be delivered to the post process, such as production or purchase. So the key success factor for this project are efficiencies of the work and feasibility of product development and data integrity.

So we have defined this very important area from understanding the issues. First one is the product development and design and collaboration area. From these three areas, there are four main scopes of this project-- dashboard for the product development, and project management, and change management, and finally CAD data management.

This is the application point of view. So as you can see, the legacy system interface is just out of scope for this project. But we discussed about this for the right direction for the ERP interface for next scope.

This project was planned for 12 weeks. The first step was to upgrade it to synchronize with the PLM. It's kind of a mandatory work in case of using an old version of Vault.

And also PLM-- for the whole task, the PLM solution training is the next step. And I want to emphasize it is PLM training. Because understanding PLM solutions by customers is very, very important. I think real PLM implementation can start after understanding.

If your customers understand the PLM solution, requirements could be changed a lot. For your requirement can be not easily defined, have to understand. So without understanding, it makes the project difficult and it could be delayed, and it could impact on project quality. So we have to consider PLM solution understanding of customers seriously.

And the training should touch real use cases-- not just a simple function training. We cannot say customers understand the PLM solution without use cases. And for minimizing the risk, the only-- just one product development project was targeted. This is our first project in [INAUDIBLE] so we plan to test all the functions with this simple target project, and make a soft landing when we expand to other disciplines.

And now I will briefly explain what we do, but don't worry. It is brief. Doohyun will explain in detail-- very detailed. And this is our project approaches. The project starts from AS-IS analysis, and TO-BE design, gap analysis, and based on that analysis, to be implemented and test and go right. That's very typical in the procedure.

But when we conducted the project, the gap analysis is kind of different. Because we already have a solution which is well made, and then we have to do gap analysis between customer requirements and solution functions. And the difference is that it's OOTB based. This project is OOTB approach.

So what's OOTB? OOTB is Out Of The Box. You can use right away the solution if the requirement is aligned with our solution. So we did the gap analysis.

If there are no gaps, we can configure a solution and you can use it. And you can test it-- very simple. But if there are gaps, then we have to find out the alternative way. So if there are alternative ways, we can agree to use that alternative way and then configure configuration.

It's the same as, no gap procedures. But if there is no alternatives, then we have to customize. But this is the next project. [INAUDIBLE] our approach to minimize the risk.

And [INAUDIBLE] about the dashboard. We define product classifications, so we manage products systematically, and you can easily search products and see the progress. Sort of the-- you know, this management.

And this also is linked to the project. So you can see the detailed progress, and see the deliverables as well. So you can easily know what did in the project. And you can see also the know-how of the project.

And also this feature links to BOM. So [INAUDIBLE] is possible without solid CAD solutions. So you can also do this [INAUDIBLE] through the viewer.

So product development process is transparently monitored, and easily search product deliverables. Then we can reuse product know-how. That's the very big benefit.

Next one is about project management. Each task in product development is managed by change process as well, because it is related in the systems. And for product management, we define standard WBS-- Work Breakdown Structure. Work breakdown structure has a schedule and has deliverables. So this is the key item to define.

And also this could be different with the product. So with this project, we target one project and one product, and then standard [INAUDIBLE] WBS for that product. And also manage project deliverables based on this WBS. So we can easily track the deliverables.

And we can keep data integrity because we-- every data-- when every data is changed, it is managed by a change process. So we can easily know the right-- latest one. Through this project management, we can use project know-how and leverage these when we conduct a similar project. That's a very nice, very big benefit, to conduct a new project.

And this is about change management. Change requests can come from various disciplines such as design, department [INAUDIBLE] and production and customer quality but it should be verified by a process and recorded for the next changes verification.

And if we make a decision to change the whole task [INAUDIBLE] we manage it with the change process, and distribute it to right person and on the right time. Then we can keep the latest data such as BOM, drawings, and documents. So we can reduce unnecessary work through this change process.

The last will need CAD data management. [INAUDIBLE] product based on units that you see. There are tens of-- many, many units. And then if a design needs done, we can see product level BOM list automatically, and model as well in PLM. So there is no manual tasks to integrate all you need, which can prevent manual errors. And it is also for product reliability so engineers can design easily and accurately.

For this management, we standardized revision rule, numbering rules, and also part and BOM attributes as well. This should be done for CAD data management. [INAUDIBLE]. It should be considered in the best.

And also it should be considered, not just the giant part. This data should be used in cultures, production, and other disciplines as well. So when we standardize the data, we should consider other disciplines [INAUDIBLE]. This is all for me, and from now, Doohyun will explain details of implementation. Doohyun?

DOOHYUN KIM: Thank you, Moonbae, that was impressive. Hello, everyone. I'm Doohyun Kim, working for design and manufacturing industry in Autodesk Korea as a solution engineer. I'm so glad to be here and I would like to share some technical stuff which was applied to PLM implementation project for Iruja.

Firstly I am going to introduce a cloud-based configurable PLM solution called Fusion 360 Manage from Autodesk, for attendees who are not familiar to the product, then going to talk about PLM implementation project for the customer user, focusing on what we have performed. And I would like to share some lessons we learned from the project with tips and references.

The first thing I would like to talk about in this session is PLM. PLM stands for Product Lifecycle Management. It is defined as a strategy for connecting your people, process, and data across the entire product lifecycle for a central source of information by Autodesk. I believe most of the attendees here know what a PLM is.

Some of you are already using PLM currently. Some of you are thinking about implementing in the near future, or some of you may want to replace it with something new and cool solution. Whichever the circumstances we are in, there is common stuff in PLM value proposition presentation performed by a solution engineer like me.

The benefits of PLM have always been promising. There are a lot of PLM solutions around this world, like Solidity experience from [INAUDIBLE] system, Team Center from Siemens, Windchill from PTC, and more. But the benefits of PLM from various solutions are similar to each other.

What kind of benefits have you been told with implementing PLM? You will have automated workflows. Sharing product data across departments is going to be easy. You will have a better visibility in product development process.

Product development cycles are going to be shortened. You can manage BOM and change process with traceability. The supplier collaboration will be effective with the quality management and lower costs. You will have faster time to market, running standardized business processes with enterprise collaboration.

Actually, those benefits are turned out to be true by implementing PLM for the last 20 years. Most of the customers agree that those benefits are real, whether they are big or small, and no matter what kind of PLM solutions they are using. But I also believe that some of the customers are struggling with using and managing PLM systems.

So the way we have been implementing PLM-- let's call it traditional PLM-- is on premise. The typical process implementing traditional PLM system would be-- you need a physical PLM server, which is expensive because the server will be accessed by all the stakeholders from enterprise. An expensive machine needs to be set up and managed by a specialized person.

And then you need to install and configure the PLM solution. The database also needs to be installed and configured. Network settings and performance check is also required.

Then you need to talk about product lifecycle and development process with the consultant, and they need to be standardized to be [INAUDIBLE] into PLM system. All the management areas like project, product, part, BOM, change, quality, and supplier management need to be discussed. At this stage, the customer has no idea how their requirements will be realized.

With this consulting result, PLM experts discuss how to realize customer's requirements with PLM. Some of the requirements can be covered with out-of-the-box features, and some of them need to be customized. At this stage, the customer still has no idea how their requirements will be realized until it is published.

Training individuals for the PLM system, including customized features, is lengthy. Most of the customers are not familiar to the PLM system. They may not agree to the standardized product development process. They may raise additional requirements during the end user training, and they may bring unexpected use cases. These errors used to happen in traditional PLM implementation process.

All these kind of iterative processes may let customers down and make them think it is difficult to adopt. Once the PLM system is adopted, customers need to think about upgrades. New requirements have been raised from the end users, some additional process standardization activities are needed, and more features that make end users happy, and some bugs need to be fixed. This is time consuming and costly upgrades.

Then how about the PLM solution from Autodesk? Autodesk has a cloud-based [INAUDIBLE] PLM called Vision 360 Manage.

[VIDEO PLAYBACK]

- The benefits of product lifecycle management have always been promising, but traditional PLM systems require extensive consulting. They are expensive, training is lengthy, and getting up and running often takes too much away from getting today's work done.

[SIGHS]

Fusion 360 Manage helps you avoid all of that with instant-on PLM that's easy to use, and accessible any time anywhere, from a browser or mobile device. We give you the flexibility to start today and expand tomorrow with a PLM platform that adapts to your business. Included are core PLM apps that are easy to configure to your specific requirements. Rather than starting from scratch, these apps include out-of-the-box workflows that you simply tailor to your needs.

A simple change of category here, another change here, and you're all set. Now you can better improve your new product development process, better manage change orders, bill of materials, supplier collaboration, and product quality. Start with one process at a time and easily expand as you need. Fusion 360 Manage simplifies everyday tasks and improves collaboration.

And with its open API, Fusion 360 Manage integrates easily with other business systems, such as ERP, CRM, and PDM. It's everything you need in a single PLM platform that connects your people, processes, and data across departments and geographies. Realize the benefits of PLM today and spend more time reaching your business goals with Fusion 360 Manage.

[END PLAYBACK]

DOOHYUN KIM: PDM-- Product Data Management-- is designed for managing engineering data to enable concurrent engineering. The product data management capability is focused on managing drawings, models, and assemblies, with metadata and related libraries. Those data are usually generated by the engineers during the product development process, and they expect full coverage of their CAD design tool's capabilities. So I can say a seamless integration between engineering tools and PDM is the key capabilities.

Autodesk has the best PDM solution called Vault Professional. Vault Professional is tightly integrated in Autodesk products, and it provides a central repository for any engineering data. As I mentioned in the key capabilities of PDM in the previous slide, the seamless integration in the user interface of Inventor reduces data management efforts for engineers to a minimum.

PLM is focusing on a different area from PDM is doing. It is designed for managing the product lifecycle end to end, from early concepts through engineering, and production to services. PLM connects people, data, processes, and is a system to provide transparency and traceability. It is for all the stakeholders from enterprise, so it should be easy to use with automated processes which make a business workflow efficient. So I can say simplicity, accessibility, and flexibility are the key capabilities of PLM.

Autodesk has a cloud-based configurable PLM called Vision 360 Manage in this cloud. So core PLM processes are provided with a default configuration and ready to use, which enables customers to start quickly in short time to value. And it is configurable, and you can adjust business processes to your needs. Or even adding a new business processes definition is possible with graphical administration utilities.

Vault Professional is an on-premise PDM solution providing seamless integration in engineering tools. Fusion 360 Manage is cloud-based, configurable PLM solution providing simplicity, accessibility, and flexibility to all the stakeholders from enterprise. Vault Professional provides an integrated CAD user interface and local file storage for best performance. It is located in the network, so it maximizes data management performance and meets your data security policy.

Fusion 360 Manage is a cloud on the internet. So it provides the flexible accessibility to not only internal stakeholders but also outside ones like customers, suppliers, and design subcontractors. Those two solutions can be connected and integrated. So using these two different, but connected, solutions, we will maximize values of each solutions like killing two birds with one stone.

I have talked about the values from PDM and PLM [INAUDIBLE] and how to maximize them connecting together. Now it's time to talk about Fusion 360 Manage and PLM implementation project for the customer Iruja. User has been using Vault Professional as a PDM system for around 10 years. They are very satisfied with the features provided by Vault Professional, and wanted to keep the values in their product development process. And they also wanted to expand the values of PDM in enterprise level, with less changes as possible.

So how did we start? I hope you remember some weaknesses of traditional PLM-- expensive hardware, extensive consulting, training is lengthy, difficult to adopt, time consuming, and costly upgrades. Cloud-based configurable PLM, Fusion 360 Manage, needs to be accessed with a different implementation starting point, from one of the traditional PLMs. The first thing we performed was having a Fusion 360 Manage class to let customer get familiar to the solution.

It is a cloud solution, so default configuration and business processes are already there. All we need to do is change the customer default configuration and business processes so the customer can understand what kind of values can be delivered with PLM. This makes the customer understand how Fusion 360 Manage works and let them be on the same page with the other product members, and also makes the customer describe their requirements in a reasonable and practical way.

After that, we show the customer BOM transporting capability from Vault Professional to Fusion 360 Manage, localization, field and section configuration, little scripting, workflow configuration, and security settings were performed. Let me show them in the following slides.

Fusion 360 Manage provides the default business processes in default configuration as shown here. It includes PPM-- Product Portfolio Management-- product development, change management, NPI-- New Product Introduction-- supply chain collaboration, and quality management. These default business processes also include standardized workflows, which can be used in common manufacturing companies like Iruja. As you can guess, some of the default business processes can be acceptable, some of them needs to be configured, and some of them are not needed for now, considering customer's business circumstances. But we decided to have all the classes to let them feel the value of Fusion 360 Manage.

The default business processes consist of some standard workspaces. It's not easy to explain what the workspaces are and how they work, but I hope you take away that those workspaces contain and manage the necessary information, and connected to each other for the traceability, which is one of the key values of PLM. PPM-- Product Portfolio Management-- contains and manages products and information. Products workspace connects to the Checklist workspace, which let users know what kind of conditions are needed and to be checked. Those checklists comes from checklist template for reusability.

Our product categories, lines, and portfolios help a customer organize their various products and access them intuitively. NPI-- New Product Introduction-- contains and manages project information. New projects can be created easily from project template, which contains timeline of phases, tasks, and data reviews. Project workspace is connected to the product workspace, so you can access a related product for a project, and vice versa.

Product development is to manage document and BOM information, and is also connected to product workspace, so user can access BOM information from the product workspace. Change management is for document and BOM change process, focusing on providing traceability about why, who, what, and when the change has been performed. Supply chain collaboration and quality management business processes also consist of proper workspaces and provide connections to other ones for their own purpose.

[VIDEO PLAYBACK]

- How do you reduce inefficiencies, increase productivity, and get better results from your product development processes? With better data management and better process management. Product Data Management gives everyone access to the right data at the right time all within a centralized system. So you can control design processes, reduce errors, and improve productivity throughout your entire organization.

Product Lifecycle Management enables companies to get better products to market faster, helping streamline new product introductions, share up-to-date BOM information across your organization in real time, enhance supplier engagement and participation, and close the gaps in change management and quality issues. Integrated PDM and PLM work together to keep everyone on the same page to overcome complex development challenges, cohesively manage the many moving parts of the product lifecycle. So you can do more with your product data, from early design concept through engineering to production and service.

Get rid of bottlenecks. Connect your people, processes, and data across the entire product lifecycle. Get to market faster.

[END PLAYBACK]

DOOHYUN KIM: You know, it's not easy to make users understand Fusion 360 Manage with a single internal class. There were several iterative classes for customers' better understanding. So the customer is getting familiar to Fusion 360 Manage, and they were on the same page with the other project members.

That was the time that the customer is ready to discuss how PLM should be implemented. Customers started to talk about their product development process, considering Fusion 360 Manage architecture, in reasonable and practical ways. And they could make a decision that which business processes can be used as it is, which one needs to be configured, and which one is not necessary for them. So the customer and project members came to an agreement of PLM project coverage, as marked in red-- the dotted line here.

I believe you remember the value of using Vault Professional and Fusion 360 Manage together. Vault Professional is an on-premise PDM, maximizing performance and security, and Fusion 360 Manage is a cloud PLM maximizing accessibility and flexibility. To connect those two solutions, we decide to use PowerPLM and PowerJobs products from a company called Cool Orange. Cool Orange provides various products of software tools and plug-ins for Autodesk PDM and PLM.

PowerPLM and PowerJobs are products connecting Vault Professional to Fusion 360 Manage, which enables transferring BOM information. They provide a super quick and easy configuration with high flexibility based on PowerShell technology and libraries. We have configured this product to transport BOM information, including image, metadata, structure, and attachment, with auto-generated viewable files once the items from Vault Professional were released.

I should say using this product from Cool Orange is just one of the options you can have. Vault Professional and Fusion 360 Manage provide their own APIs, so you have other options if [INAUDIBLE] of. But I'd like to recommend you use those commercial products to get technical and system medical support from the company.

Localization-- I believe this is not an interesting topic to Western guys, but Korea is located in Asia and localization is necessary to Korean users. Fortunately, Fusion 360 Manage provides a critical interface for administration and localization, which is easy and intuitive. All you need to do is go into Workspace Manager in Administrative menu, and find the fields or tabs, and renaming them in local language or another name you want. This applies to user interface immediately, so you can see the result without pending.

Field and section configuration-- Fusion 360 Manage provides default fields commonly used in manufacturing industries. But it doesn't mean all the fields are necessary. Some fields should be added, some fields should need to be removed or relocated. I want you to think about what would be the typical process to make this happen in traditional PLM.

To add a new field, developer usually needs to create database field, connects to PLM, design user interface, create additional code for visibility, heritability, and default value, test on PLM's server, debug and release. This can be done by simple configuration in Fusion 360 Manage. Adding fields can be done by clicking Add Field button in Item Detail Information tab of Workspace Manager. This critical tool lets administrator set name, type, visibility, editability, and default value with the effectiveness conditions.

You can also remove or hide the existing field, and relocate them with a simple drag and drop operation. Section is a container field feature organize them to make the user easy to recognize, and provides advanced options to control accessibility. There are more administration tools in Fusion 360 Manage Workspace Manager, which enables administrator to save resources, efforts, and time.

There was a mutual agreement that this PLM implementation project is for running based on default configuration. But you know, the customer changes. Once the customer starts to understand how Fusion 360 Manage works, then the requirements from the customer [INAUDIBLE] used to be more specific. This slide shows that one of their requirements, which is the simplest one.

In Product workspace, end user is expected to type in main drawing number field in four digits, which consists of two-digit year and two-digit of a serial number. And there is another field called Manufacturing Year in four digits, like 2017. Customer doesn't want to put year information twice and wants to have some automated functionality. End user types in main drawing number field in four digits, hit the Save button, and wants to get the manufacturing year field in four digit.

Fusion 360 Manage provides a JavaScript editor in web browser, and this requirement has been realized successfully by adding simple few lines of code. I'm not a developer but a solution engineer, and don't have computer language experience, especially in JavaScript. But it was doable, looking into similar code provided by the default configuration. You may need a JavaScript expert for more complicated functionalities, but this case showed how Fusion 360 Manage provides ease of development environment.

There are some workspaces running with workflows. A workflow represents work process, carrying on item's maturity from one specific state to another. It consists of states and transitions which is triggering necessary actions with the conditions. Fusion 360 Manage provides a workflow editor which enables administrator to make it easy.

All you need to do is drawing some states and connecting them, defining some actions with the conditions that you want, just like drawing rectangles and arrows in PowerPoint. I would like to remind you that commonly used workflows in manufacturing industries are already provided with default configurations. Iruja had reviewed the default workflows and found that most of them are acceptable.

Of course, there were some workflows Iruja wanted to configure. The customer has a specific maturity state of a product, and wanted to apply them in Product Workspace workflow. There were some tricky parts, but it was fairly easy to make it happen because the Workflow Editor provides all the necessary tools and default workflows [INAUDIBLE].

Users, groups, roles, and permissions-- they are all about access control. All the menus, fields, sections, and buttons of Fusion 360 Manage are controlled by permissions. You can create some roles that consist of specific permissions. Those roles can be applied to specific groups, and the groups consist of users.

It sounds tricky, but you will recognize that this is the most efficient way of designing access control. You can apply some permissions to a specific role or creating, modifying, adding, viewing, and deleting for each type of tabs, including specialized ones. User has typical organization of team manager, leaders, and members. Users are assigned to a dedicated group, and roles were defined and applied to the groups. Fusion 360 Manage is designed for ease of management for access control.

All right, lessons learned. Fusion 360 Manage PLM implementation project for Iruja is the first lighthouse one in Korea. Autodesk Korea, our business partner, and the customer didn't have enough experience for this project. So there were some trial and errors and lessons we learned. I would like to share them with you.

Process innovation consulting is the key to successful PLM project. Process innovation-- it sounds big, but it's focusing on process standardization activities that you perform in your company. It brings the implicit processes up to the table and makes them explicit ones, which can be agreed by all the stakeholders in enterprise.

These activities can be done by having iterative and deep-diving discussions between customers and project members. The PLM implementation project is for melting the standardized processes in the system. You will be facing a lot of complaints and objections from end users without this process innovation consulting.

Customer's understanding of Fusion 360 Manage is very important. That is the reason we had the iterative classes for their better understanding of product and features. Better understanding puts the customer on the same side with [INAUDIBLE] members, and this will lead to successful PLM project.

You need to raise a key person with administration capability. PLM is a long journey and there is no finish line. The customer's business environment are changing continuously, companies trying to grow and expand their business areas.

Those changes cause customers additional requirements which need to be realized at existing system. Fusion 360 Manage provides efficient and good enough administration features which let the key person manage PLM. PLM implementation projects can be closed in a specific period, but sustainable and continuous management is required.

I cannot say this is the best practice, but I would like to share some tips I got from this project. Classes for customer-- the more, the better. I use the plural noun-- classes.

Fusion 360 Manage provides a lot of features and functionalities-- more than you think it does. I do not expect customers will fully understand with a single class. Be patient and iterative.

There are many and various types of fields to contain and manage information, but some of them is not easy to understand, the reason of their existence. You may want to delete them, but I recommend you hide them. Some filters are used to contain temporary information, and some of them are used by a script. If you delete them instead of hiding, this will occur unexpected errors. Of course, you may delete them when you fully understand what those fields are used by, but you should hide them if you're not sure.

There are also a lot of scripts provided by default configuration. You don't need to understand them all, but you need to know where the scripts are. Fusion 360 Manage provides reporting features in Dashboard it shows current status in graphical way by combining data from various fields. If you have something to show in Dashboard, you may think about creating additional fields which will be used just for it.

Security settings and access control is one of the most important items that administrators need to be focused on. Improper security setting and access control will cause, not only the building sensitive information to improper person, but also sending notification mail to a person who doesn't have a right to do. I recommend you do the security setting in second half of the project. You will need to double check the security setting on every change unless you do in the second half of the project.

There are some references you may want to take a look. Vault PLM is a product that consists of Vault professional and Fusion 360 Manage. You can get more information about this product with the link here.

Fusion 360 Manage provides developer scripting guide with nice and easy content. And there was another AU 2020 content, explaining how PowerPLM and PowerJobs works to connect and transfer BOM information from Vault Professional to Fusion 360 Manage. The other two links are here, for product configuration from Cool Orange.

All right, this is all I prepared for my session. Thank you for your time and attention. Please feel free to contact us if you have any questions. Over to you, Moonbae.

MOONBAE SONG: Great job, Doohyun. Thank you very much. Now I want to tell next plan. We did a pilot project with one target product and one target development project. [INAUDIBLE] limited to pilot project team with those codes. And we focused on setting up basic infrastructure for PLM. So standardization of data process are the key of this project.

And next project is for stabilization of PLM, and also expanding to other organizations and more function as well. So supplier collaboration and quality management will be followed. And also, Autodesk has MES solution in production [INAUDIBLE] and also various other solutions in factory. So we will continuously go together for user success.

That's all for this session. Thanks for attending this session. And if you have any questions, send an email to Doohyun and me. Thank you. Thank you very much.