A regular product flow in Discrete Manufacturing involves receiving an order, manufacturing it based on a standard design that exists, shipping and invoicing it. However, an ETO (Engineer-To-Order) flow involves a lot more activities before the order could be shipped. These processes run through almost all the departments of the organizations starting with Quoting, Sales Engineering, Product Engineering, Supplier Collaboration, Manufacturing, Quality, Costing, Logistics and Finance. These activities lead to many handoffs between then departments and iterative interactions which make the ETO cycle time very high.<\/p>\n
Some of the typical challenges associated with a typical \u2018Engineer To Order\u2019 are the following:<\/p>\n
\u00b7\u00a0 \u00a0 The overall lead time of manufacturing an ETO product is quite high as it involves a significant amount of engineering and design for each ETO order. Once the specifications regarding the product \/ Bills Of Material and requested special features are finalized, the Engineering team has to do research, experiments, and prototyping, etc to revert with the feedback on feasibility.<\/p>\n
\u00b7\u00a0 \u00a0 The Pricing, Costing and delivery promise date is dependent on components under engineering. For upfront pricing and Order confirmation without knowledge of the final product\u2019s cost may cause a reduced margin if the cost goes higher than estimates.<\/p>\n
\u00b7\u00a0 \u00a0 Lack of visibility to the final product’s components and operational needs until research, and engineering is completed which in turn is required to confirm whether the customer expectation can be met.<\/p>\n
\u00b7\u00a0 \u00a0 Downstream process of procuring the new components in ETO environment typically require lot more time for the new components \/ parts with Suppliers during quotation process and require close communication and exchange of inquiries and feedback with Procurement Dept, Engineering, Suppliers, CSR and in turn with Customer.<\/p>\n
\u00b7\u00a0 \u00a0 Huge Technical and operational Information flow is involved.\u00a0 Products need a lot of data gathering relevant to different aspect of BOM, Drawings, Engineering of the product, operational instructions (temperature and pressure at specific operation etc), outside processing, technical specifications (e.g., painting color, number of coats), tagging, packaging and so on, depending on specifications.<\/p>\n
\u00b7\u00a0 \u00a0Demand forecast of new components are usually not available and may not be predictable for future purchases.<\/p>\n
\u00b7\u00a0 \u00a0 Higher Testing \/ Quality Control needs for a product being manufactured first time; the testing cycles may go for more iterations increasing total lead time of the finished good as well as the expense of carrying out this exercise.<\/p>\n
\u00b7\u00a0 \u00a0 The Change Orders need further To and Fro communication with the Customer and Internal departments with high volume of data exchange, new action items (e.g., re-engineering) etc leading to further lapse of time.<\/p>\n
\u00b7\u00a0 \u00a0 Real time tracking of the Order is difficult due to above mentioned reasons.<\/p>\n
\u00b7\u00a0 \u00a0 There is a lot of close collaboration required with Engineering Department for quoting and Sale of ETO based products. The Sales Quote or the Order needs to be verified and confirmed by assigned Engineers before order booking in terms of feasibility, possible variations, and other necessary inputs. This in turn increases the workload on Engineers unpredictably as against the predetermined set of work on the ongoing projects.<\/p>\n
In order to address these typical aspects of the Engineer to Order business, Infosys has designed a Oracle SaaS based solution for our ETO customers. Some key features of the solution are the following:<\/p>\n
\u00b7\u00a0 \u00a0 A tightly integrated Configure, Price and Quote tool that allows customers the ability to configure and price products that are built to specifications. This is integrated with Order Management to seamlessly create the ETO orders with the required details.<\/p>\n
\u00b7\u00a0 \u00a0 Provision to capture ETO requirements for a component at any level of the product.<\/p>\n
\u00b7\u00a0 \u00a0 A mechanism to allow engineers to review the ETO quotes, and then accept, reject, or seek further clarification from the CSR and the customer regarding the requirements to confirm the feasibility.<\/p>\n
\u00b7\u00a0 \u00a0 The entire product configuration along with the technical information, operational instructions captured, flows to the concerned departments or external parties (Customer or suppliers). After the quote is finalized and accepted, the same quote is as-is converted to Sales Order. This way no information is missed in this entire process.<\/p>\n
\u00b7\u00a0 \u00a0 Automatic generation of the initial ETO product and its base BOM makes the process quick and provides early order entry and visibility to manufacturing and planning.<\/p>\n
\u00b7\u00a0 \u00a0 Online collaboration with External and Internal parties, real time Transactional data updates available among different systems (e.g. in Oracle Sourcing) which helps with speeding the quote process as well as timely decision making on procurement of Bill Of Material components, Outside processing services etc needed for manufacturing.<\/p>\n
\u00b7\u00a0 \u00a0 In line with the above-mentioned benefits, the manual errors in requirement gathering are reduced. The accuracy of information collected from customer improves, in turn helps in more accurate pricing, costing and estimation of delivery promise date to the customer.<\/p>\n
\u00b7\u00a0 \u00a0 PLM (Product Lifecycle Management) module is well designed to support product development for items or parts right from inception, design through efficient documentation, capturing requirements, Engineering Change Orders and quality workflows. This module is integrated across other Supply Chain Management modules in Oracle Cloud applications and seamlessly integrated with Computer Added design systems.<\/p>\n
\u00b7\u00a0 \u00a0 Document Repositories, Summary of information, Tracking and Tracing capabilities throughout end-to-end Order flow and Product Lifecycle management.<\/p>\n
\u00b7\u00a0 \u00a0 Different Dashboards (seeded and customizable) could be developed as per Business needs which help drill down information from macro to micro level.<\/p>\n
\u00b7\u00a0 \u00a0 Reporting capabilities of Oracle SaaS is useful to have information related to product specifications, Operational instructions to print or send to concerned departments or external parties.<\/p>\n
\u00b7\u00a0 \u00a0 Performance tracking of different entities e.g., Suppliers, products or parts quality issue capture etc are critical for improvements and critical decision making to streamline the processes.<\/p>\n
\u00b7\u00a0 \u00a0 Online concurrence and approvals can be taken on change orders.<\/p>\n
The ETO process, as explained, involves activities that span across various departments and in the process could introduce errors and delays. The Infosys solution around ETOs attempts to provide an orchestrated solution that contains necessary automation, process framework, integration and tracking needed for managing the ETO business.<\/p>\n","protected":false},"excerpt":{"rendered":"
A regular product flow in Discrete Manufacturing involves receiving an order, manufacturing it based […]<\/p>\n","protected":false},"author":299,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[71],"tags":[],"coauthors":[153],"class_list":["post-1340","post","type-post","status-publish","format-standard","hentry","category-oracle-saas-cloud"],"acf":[],"_links":{"self":[{"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/posts\/1340","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/users\/299"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/comments?post=1340"}],"version-history":[{"count":10,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/posts\/1340\/revisions"}],"predecessor-version":[{"id":1573,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/posts\/1340\/revisions\/1573"}],"wp:attachment":[{"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/media?parent=1340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/categories?post=1340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/tags?post=1340"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/coauthors?post=1340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}