Method and system for executing work orders

What is described is a method and a system for executing work orders. A first request for receiving a progress information on a work order is generated. A degree of violation between the work order and the progress information is calculated by comparing the work order and the progress information. A tolerance violation status is determined based upon the degree of violation. A second request is generated for receiving a content for the work order to resolve the tolerance violation status. The work order is updated based the content.

FIELD OF THE INVENTION

Embodiments of the invention generally relate to the field of supply network collaboration and more specifically to a method and a system for executing work orders.

BACKGROUND OF THE INVENTION

A collaboration system provides collaboration of business objectives in a supply chain network. Collaboration systems enable users to collaborate in the creation of documents and other electronic records. Collaboration technologies deliver the functionality for many entities to enhance common deliverable information. Such collaboration systems include telephone, e-mail, synchronous conferencing, instant messaging, faxing, voice mails, video conferencing, and the like. Collaboration tools facilitate and manage group activities. Examples of collaborative tools include electronic calendars, work flow systems, knowledge management, project management, online documents and the like.

Existing collaboration systems enable exchange of information between two or more entities such as suppliers and customers and altering one or more components of business process. Examples of business processes include development of an idea, creation of a design, outsourced production or the like. Suppliers and customers may want to closely integrate and co-ordinate with each other for a product development and production. The collaboration system helps entities integrate their business process and create additional value through integration. There is a need for the entities to react in sufficient time on components in a business process that are missing or products whose yield is low. Therefore, a system is required for providing a difference between an actual product specification and a required production process specification In addition, the system must enable the entities to negotiate on the specification and reach an agreement based upon the negotiation.

SUMMARY OF THE INVENTION

Embodiments of the invention are generally directed to a method and a system for executing work orders. A first request for receiving a progress information on a work order is generated. Multiple progress information updates are typically collected during production. A degree of violation between the work order and the progress information is calculated by comparing the work order and the progress information. A tolerance violation status is determined based upon the degree of violation. A specific request action is generated for receiving an updated progress information for the work order to resolve the tolerance violation status. The work order is updated based the content.

These and other benefits and features of embodiments of the invention will be apparent upon consideration of the following description of embodiments thereof, presented in connection with the following drawings in which like reference numerals are used to identify like elements throughout.

DETAILED DESCRIPTION

Embodiments of the invention are generally directed to a method and system for executing work orders. A first request for receiving a progress information on a work order is generated. A degree of violation between the work order and the progress information is calculated by comparing the work order and the progress information. A tolerance violation status is determined based upon the degree of violation. A second request is generated for receiving a content for the work order to resolve the tolerance violation status. The work order is updated based the content.

FIG. 1is a functional block diagram of system100for executing a work order according to one embodiment of the invention. Customer backend104is typically maintained by customer102and supplier backend108is typically maintained by supplier106. Collaboration system110generally helps collaboration between customer backend104and supplier backend108. In an embodiment, purchase order112is typically generated by customer102in customer backend104for a supply of goods or products from supplier106. Based on purchase order112, work order116is generated in collaboration system110. In an embodiment, multiple work orders may be generated for every purchase order112in collaboration system110. In an embodiment, work order116is generated for each item of purchase order112or each schedule line of purchase order112. Work order116is typically a collaboration object, generally a document including supply chain related information provided by customer102and supplier106. From a business perspective, work order116covers the functional needs of outsourced manufacturing requirements. In an embodiment, supplier106carries out a production of goods as prescribed by customer102before delivering the goods to customer102. Typically, work order116includes the following information:Production and delivery request from customer102to supplier106;Production and delivery confirmation from supplier106to customer102;Production and delivery agreement which is an agreed plan between customer102and supplier106;Production information including production steps which are also known as phases, attachments and parameters;Production progress actual data;Production outputs: yield, scrap, on-hold, reworked;Batch/Lot number assignment (planned and actual);Customer-specific and supplier-specific notes for textual communication; andProcess status information on requests, confirmations, phases and item.

The supply chain related information may include a work order item, a work order delivery, a production phase, a phase input and a phase output. The work order item may typically contain a partner identification information of customer102and supplier106, a goods recipient, and a location information. The partner may include customer102, supplier106and the goods recipient. The work order item also serves as an aggregation point for information of a work order delivery. The work order delivery may include information about ordered products, product quantities, delivery and shipping time. The work order delivery may be received as a request, a confirmation, an actual order and a projected order, or the like.

The production phase includes information about the required production steps, including a description and a duration of the production steps to be carried out by supplier106. Typically, the phase input includes information of a component material, a quantity to be used in each phase, and a point in time the production phase has to begin. The phase output includes information of a resulting product, a quantity resulting from a phase execution and a point in time when the product is received by customer102. The phase input and the phase output typically indicate a flow of materials through each phase in the production process. Work order116may also include a machine setting information, a product design details and a production process details. The delivery information in work order116is typically represented by a transport phase, where an input of the transport phase includes an information about shipping of a product and an output of the transport phase includes an information about delivery of the product. Typically, the phase input and the phase output may include a request phase input and a request phase output generally created by customer102, a confirmation phase input and a confirmation phase output generally created by supplier106, an actual phase input and an actual phase output generally reported by supplier102during executing the production of work order116by supplier106, and a projected phase input and a projected phase output generally calculated by collaboration system110based on the actual and the planned phase input and the planned phase output. The data in an agreed plan includes a combination of the inputs and outputs of the request phase and the confirmation phase.

Work order116typically allows grouping of the inputs and outputs of the request phase and the confirmation phase. A group of the inputs and the outputs resulting from the grouping is typically a production run. The production run generally allows representing a phased production where partial product quantities are produced at different times. For example, a work order item in work order116may produce a total quantity of ten products where the production of six products is started first and the production of the remaining four products is started at a later point in time.

Typically, progress information120includes an actual input data, an actual output data, an actual consumption of components and an available date of delivery of products by supplier106. Thus, progress information120is an actual data of work order116represented by an actual phase input and an actual phase output, typically indicating a flow of materials through out a production process. Based on progress information120, collaboration system110typically calculates the delivery quantities and the delivery date. Customer102at any instance may update work order116. Customer102may update work order116manually through a web user interface or through customer backend104. In an embodiment, on each updation of work order116by customer102, a negotiation of work order116takes place between supplier106and customer102. The result of the negotiation is typically the agreed plan.

Customer102proposes purchase order112. Purchase order112is typically created in customer backend104. Purchase order112is transmitted114to collaboration system110. Based on purchase order112, work order116is generated in collaboration system110. In an embodiment, work order116may be created based on a sub-contract order typically proposed by customer102. Collaboration system110may create a corresponding work order for the sub-contract order. In an embodiment, work order116is a result of negotiation between customer102and supplier106. A negotiation of work order116may include receiving suggestions from customer102and supplier106. Typically, the suggestions from customer102and supplier106include one or more changes in work order116and one or more changes in progress information120.

At the end of the negotiation, customer102and supplier106reach an agreement and an agreed work order or the agreed plan is generated. Progress information120is typically provided118by supplier backend108to collaboration system110. In an embodiment, a request is generated by collaboration system110for supplier backend108to provide118progress information120for work order116. In an embodiment, collaboration system110publishes work order116, which is visible to supplier106. Supplier106may provide progress information120on viewing work order116through a web user interface or automatically through supplier backend108.

Progress information120and work order116are compared and degree of violation122is calculated. Degree of violation122is calculated to determine a deviation of progress information120from work order116. Collaboration system110determines tolerance violation status124based upon degree of violation122. In an embodiment, a tolerance level for work order116is defined in collaboration system110. The tolerance level is usually a maximum allowed degree of violation122. Typically, a tolerance violation occurs if progress information120does not conform to the tolerance level of work order116. Tolerance violation status124is typically determined only if degree of violation122is above the tolerance level. Based upon a nature of violation and degree of violation122, tolerance violation status124may take one of the values including an actual quantity too high, an actual quantity too low, an actual completion too late, a projected quantity too high, a projected quantity too low, a projected completion too late and a projected completion too early.

Violation notice126is sent128to customer backend104by collaboration system110. Similarly, violation notice126is sent130to supplier backend108by collaboration system110. In an embodiment, violation notice126is published in collaboration system110, and an alert message is generated to notify tolerance violation status124. Violation notice126typically communicates degree of violation122to customer backend104and supplier backend108. In an embodiment, if degree of violation122violates the tolerance level for work order116, tolerance violation status124is sent by collaboration system110to customer backend104and supplier backend108.

A content request is typically generated by collaboration system110and sent to customer backend104and supplier backend108. The content request is usually sent to customer backend104and supplier backend108as extensible markup language (XML) messages. It will be appreciated that a variety of messages and other message formats may be used to implement the teachings of the invention as described herein. Furthermore, it is common in the art to speak of a message as being sent or received, in one form or another such as short message service (SMS) message and hypertext markup language (HTML) message. On receipt of the content request from collaboration system110, customer102may generate content132in customer backend104and send136to collaboration system110. On receipt of the content request from collaboration system110, supplier106may generate content134in supplier backend108and send138to collaboration system110. Content132and content134typically include suggestions to resolve tolerance violation status124. Typically, the suggestions from customer102and supplier106include a change in work order116and a change in progress information120. In an embodiment, a content update is generated in collaboration system100, and customer backend104and supplier backend108may respond to the content update. In an embodiment, content132,134may be updated based on a user requirement. In an embodiment, collaboration system110publishes tolerance violation status124, which is visible to customer102through customer backend104and to supplier106through supplier backend108. Customer102may generate content132in customer backend104and send136to collaboration system110. Supplier106may generate content134in supplier backend108and send138to collaboration system110. In an embodiment, customer102may provide content132to collaboration system110through a web user interface. Supplier106may provide content134to collaboration system110through a web server interface. Collaboration system110resolves140tolerance violation status124based upon content132,134and work order116is updated142with the changes suggested by customer102and supplier106.

Once work order116is updated, the production process is completed. Supplier106ships the products and provides144shipping notification146from supplier backend108to collaboration system110. Generally, shipping notification146is actual shipping information provided by supplier106including a shipping time, a shipping date, a shipping location and a shipping quantity. Once customer102receives the products, customer102provides150delivery information148from customer backend104to collaboration system110. Generally, delivery information150is actual delivery information provided by customer102including a delivery time, a delivery date, a delivery location and a delivery quantity. Based upon delivery information148, collaboration system110updates152shipping notification146. On the completion of the production run based on an updated work order, the products are shipped by supplier106on the shipping date, and are delivered to customer102on the delivery date.

FIG. 2is a flow diagram of a process for executing a work order according to an embodiment of the invention. In process block202, a first request is generated to receive a progress information on a work order. The work order is typically a document including supply chain related information provided by a customer and a supplier. The work order covers functional needs of outsourced manufacturing requirements. The first request is generated typically by a collaboration system for the supplier to provide the progress information. Typically, the progress information includes an actual input data, an actual output data, an actual consumption of components and an available date of delivery of products by the supplier. Thus the progress information is an actual data for the work order represented by actual phase input and actual phase output, typically indicating a flow of materials through out a production process. In an embodiment, the collaboration system awaits for the work order from the customer. The collaboration system publishes the received work order, which is visible to the supplier. The supplier may provide the progress information on viewing the work order through a web user interface or automatically through the supplier backend. In an embodiment, the collaboration system publishes the work order. The supplier and the customer may receive a message to inform the publication of the work order.

A degree of violation is calculated by comparing the work order with the progress information in process block204. Typically, the degree of violation is calculated to determine a deviation of the progress information from the work order. In process block206, a tolerance violation status is determined based on the degree of violation. Typically, a tolerance violation occurs if the progress information does not conform to a tolerance level of the work order. A tolerance violation status may take one of the values including an actual quantity too high, an actual quantity too low, an actual completion too late, a projected quantity too high, a projected quantity too low, a projected completion too late and a projected completion too early.

In process block208, a second request is generated to receive a content for the work order typically from the supplier and the customer to resolve the tolerance violation status. Typically, the second request is generally generated by the collaboration system to request the customer and the supplier for providing the content to resolve the tolerance violation status. The content generally includes suggestions to resolve the tolerance violation status. Typically, the suggestions from the customer and the supplier include a change of information in the work order, a change of information in the progress information, and the like. In process block210, the work order is updated based on the content. In an embodiment, the collaboration system determines the tolerance violation status, which is visible to the customer and the supplier through the web user interface. In an embodiment, the collaboration system publishes the tolerance violation status, which is visible to the customer through the customer backend and to the supplier through the supplier backend. The customer may generate the content in the customer backend and send the content to the collaboration system. The supplier may generate the content in the supplier backend and send the content to the collaboration system. In an embodiment, the customer may provide the content to the collaboration system through a web user interface. The supplier may provide the content to the collaboration system through a web server interface.

FIG. 3is a flow diagram of a process for executing a work order according to an embodiment of the invention. In process block302, a work order is negotiated typically between a customer and a supplier. The work order is typically a document including supply chain related information provided by the customer and the supplier. The work order covers functional needs of outsourced manufacturing requirements. The work order is typically negotiated between the customer and the supplier in a collaboration system. At the end of the negotiation, the customer and the supplier reach an agreement and an agreed work order is generated. The collaboration system generally helps collaboration between the customer and the supplier. In process block304, a request is generated for the supplier to provide a progress information of the work order. Typically, the progress information includes an actual input data, an actual output data, an actual consumption of the components and an available date of delivery of products by the supplier. Thus, the progress information includes the actual data of the work order represented by the actual phase input and the actual phase output, typically indicating a flow of materials through out a production process. In process block306, the progress information is received typically from the supplier. In process block308, a degree of violation is calculated by comparing the progress information with the work order. In an embodiment, a tolerance level for the work order is defined in the collaboration system. The tolerance level is usually a degree of maximum allowed violation. Typically, a tolerance violation occurs if the progress information does not conform to the tolerance level of the work order. Typically, the degree of violation is calculated to determine a deviation of the progress information from the work order. In decision block310, if the degree of violation exceeds the tolerance level, the process proceeds to process block320.

A tolerance violation status is determined from the degree of violation in process block320. Based upon a degree of violation, the tolerance violation status may take one of the values including an actual quantity too high, an actual quantity too low, an actual completion too late, a projected quantity too high, a projected quantity too low, a projected completion too late and a projected completion too early. In process block322, a content request is typically generated typically by the collaboration system for receiving a content from one or both of the customer and the supplier. In process block324, the content is received to resolve the tolerance violation status. The content generally includes suggestions to resolve the tolerance violation status. Typically, the suggestions from the customer and the supplier include a change in the work order and a change in the progress information to ensure that a changed work order and the changed progress information do not deviate from the defined violation level. In process block326, the work order is updated with the content. The process moves from process block326to process block302, where the work order is again negotiated.

In decision block310, if the degree of violation does not exceed the tolerance level, the process proceeds to process block311, where the production run is completed based upon an updated work order. The products are shipped typically by the supplier. In process block312, a shipping notification for the work order is received by the collaboration system, typically from the supplier. Generally, the shipping notification is actual shipping information provided by the supplier including a shipping time, a shipping date, a shipping location and a shipping quantity. In process block314, a delivery information for the work order is received by the collaboration system, typically from the customer. Generally, the delivery information is actual delivery information provided by the customer including a delivery time, a delivery date, a delivery location and a delivery quantity.

In process block316, the shipping notification is updated with the delivery information. In an embodiment, the delivery information is a goods receipt. Based upon the delivery information, the collaboration system updates the shipping notification. The products are shipped from the supplier on the shipping date, and are delivered to the customer on the delivery date in process block318. The products are typically shipped based on the completion of a production run based on an updated work order.

FIG. 4is a block diagram of system400for executing a work order according to an embodiment of the invention. System400includes memory402, comparator404, status determiner406, first request generator408, second request generator410, updating unit412and shipping unit414. According to one embodiment, memory402is typically connected to comparator404, status determiner406, first request generator408, second request generator410, and updating unit412. First request generator408is typically connected to comparator404and updating unit412. Comparator404is further connected to status determiner406. In addition, second request generator410is connected to status determiner406and updating unit412. Shipping unit414is connected to updating unit412.

First request generator408typically generates a request for receiving a progress information on a work order. The work order is typically a document including a supply chain related information provided by a customer and a supplier. The work order covers functional needs of outsourced manufacturing requirements. Typically, the progress information includes an actual input data and an actual output data, an actual consumption of the components, an available date of delivery of products by the supplier and the like. Thus, the progress information is an actual data of the work order represented by the actual phase input and the actual phase output, typically indicating a flow of materials through out a production process. First request generator408typically receives the progress information from a supplier backend. The work order is generally determined from a purchase order generated by a customer backend.

Comparator404typically calculates a degree of violation between the work order and the progress information by comparing the work order with the progress information. The degree of violation is calculated to determine a deviation of the progress information from the work order. Typically, a tolerance violation occurs if the progress information does not conform to a tolerance level of the work order. The tolerance level is usually a maximum allowed degree of violation.

Status determiner406typically determines a tolerance violation status based upon the degree of violation. In an embodiment, the tolerance violation status is determined only if the degree of violation is above the tolerance level. Based upon the degree of violation, the tolerance violation status may take one of the values including an actual quantity too high, an actual quantity too low, an actual completion too late, a projected quantity too high, a projected quantity too low, a projected quantity too late and a projected quantity too early. The tolerance violation status is typically communicated to the customer backend and supplier the backend. In an embodiment, the status determiner406determines the tolerance violation status, which is visible to the customer and the supplier through a web user interface.

Second request generator410typically generates a second request to receive a content for the work order to resolve the tolerance violation status. The request to receive a content is generally sent to the customer backend and the supplier backend. The content typically includes suggestions to resolve the tolerance violation status. The customer backend and the supplier backend on receipt of the second request typically generate and send the content to second request generator410. In an embodiment, the content may be updated by the customer backed and the supplier backend based on a user requirement.

Updating unit412typically updates the work order based upon the content received by the customer backend and the supplier backend. Memory402typically stores the progress information, the work order, the degree of violation, the tolerance violation status, the content provided by customer and supplier, a shipping notification and a delivery information.

Shipping unit414typically receives a shipping notification from the suppler backend. Shipping unit414also receives a delivery information from the customer backend. Based on the delivery information, the shipping notification is updated by shipping unit414. Generally, the shipping notification includes a shipping time, a shipping date, a shipping location, a shipping quantity, and the like. Generally, the delivery information includes a delivery time, a delivery date, a delivery location and a delivery quantity. In addition to updating the work order based upon the content, updating unit412also updates the shipping notification based upon the delivery information. On completion of a production run based on the updated work order, products are shipped from the shipping location on the shipping date, and are delivered to the delivery location on the delivery date.

The particular methods associated with embodiments of the invention are described in terms of computer software and hardware with reference to flowcharts. The methods to be performed by a computing device (e.g., an application server) may constitute state machines or computer programs made up of computer-executable instructions. The computer-executable instructions may be written in a computer programming language or may be embodied in firmware logic. If written in a programming language conforming to a recognized standard, such instructions can be executed on a variety of hardware platforms and for interface to a variety of operating systems. In addition, embodiments of the invention are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein. Furthermore, it is common in the art to speak of software, in one form or another (e.g., program, procedure, process, application, etc.), as taking an action or causing a result. Such expressions are merely a shorthand way of saying that execution of the software by a computing device causes the device to perform an action or produce a result.

Elements of the invention may also be provided as a machine-readable medium for storing the machine-executable instructions. The machine-readable medium may include, but is not limited to, flash memory, optical disks, CD-ROMs, DVD ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, or other type of machine-readable media suitable for storing electronic instructions. The invention may be downloaded as a computer program which may be transferred from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by way of a communication link (e.g., a modem or network connection).