Transaction execution in multi-tier computing environments

Within a multi-tier computing environment having a plurality of computing nodes, a first node accesses a data object encapsulating values. Thereafter, the first node generates node specific messages for each of a plurality of tiered nodes in the multi-tier computing environment relating to a transaction. The node specific messages encapsulate at least a portion of the values in the accessed data object and are respectively based on access visibility information associated with each such node. Thereafter, the first node transmits the corresponding node specific messages to each of the plurality of tiered nodes. The first node, in response to the transmitted node specific messages, receives data comprising a plurality of responses in response to the receipt of the node-specific messages. The first node then orchestrates with the plurality of tiered nodes, completion of the transaction by transmitting messages to select nodes of the plurality of tiered nodes.

TECHNICAL FIELD

The subject matter described herein relates to the execution of transactions with a multi-tier computing environment.

BACKGROUND

Computing environments are becoming increasingly complex with diverse and sometimes hierarchical computing nodes interacting with each other to effect transactions. These complexities can limit the types of transactions that can be completed and/or the efficiencies of such transactions.

SUMMARY

In one aspect within a multi-tier computing environment having a plurality of computing nodes, a first node accesses a data object encapsulating values. Thereafter, the first node generates node specific messages for each of a plurality of tiered nodes in the multi-tier computing environment relating to a transaction. The node specific messages encapsulate at least a portion of the values in the accessed data object and are respectively based on access visibility information associated with each such node. The multi-tier computing environment can be arranged such that at least a portion of the tiered nodes do not communicate directly with each other. Thereafter, the first node transmits the corresponding node specific messages to each of the plurality of tiered nodes. The first node, in response to the transmitted node specific messages, receives data comprising a plurality of responses in response to the receipt of the node-specific messages. The first node then orchestrates with the plurality of tiered nodes, completion of the transaction by transmitting messages to select nodes of the plurality of tiered nodes characterizing responses from other nodes for which the select nodes are not in direct communication.

The plurality of computing nodes can form a hierarchy in which the first node is a root node. Alternatively, the plurality of computing nodes can form a hierarchy in which the first node is a child node.

The first node can communicate with the plurality of tiered nodes using a uniform data transport protocol. Alternatively, the first node can communicate with a first subset of the plurality of tiered nodes using a first data transport protocol, and can communicate via a different, second subset of the plurality of tiered nodes using a different, second data transport protocol.

The generating can be based, for example, on pre-determined access visibility information associated with each of a plurality of fields within an initial message generated by the first node and the initial message is modified to result in the node specific messages.

In addition, in some variations, a second node in the multi-tier computing environment can access a second data object encapsulating values. The second node can generate node specific messages for each of a second plurality of tiered nodes in the multi-tier computing environment relating to a subset of the transaction. The node specific messages encapsulate at least a portion of the values in the accessed second data object and respectively are based on access visibility information associated with each such node. The second node can then transmit the corresponding node specific message to each of the second plurality of tiered nodes, the corresponding node specific message. The second node, in response to the transmitted node specific messages, can receive data including a plurality of responses in response to the receipt of the node-specific messages. The second node can then orchestrate, with the second plurality of tiered nodes, completion of the subset of the transaction by transmitting messages to select nodes of the second plurality of tiered nodes characterizing responses from other nodes for which the select nodes are not in direct communication.

The values can be associated with a purchase order for manufacture of goods and/or provision of services and the responses can relate to the manufacture of goods and/or the provision of services, and the completion of the transaction can pertain to fulfillment of the purchase order.

The current subject matter provides many technical advantages. For example, the current subject matter provides a computing environment that provides end-to-end visibility and collaboration in a multi-tier computing environment while, at the same time, reducing computing resource consumption and providing more efficient data flow. In particular, this visibility allows users to proactively manage volatile demand and to link product design, manufacturing, and fulfillment within a supply chain. Moreover, the coordinated computing environment with a shared planning and execution layer as described herein allows for advanced operational analytics about demand patterns, operations, and customer service requirements. Still further, the current subject matter enables for real-time data access across multiple computing nodes within a manufacturing computing environment which, in turn, allows for more optimal synchronization of aspects of a transaction such as supply and demand.

DETAILED DESCRIPTION

FIG. 1is a system diagram100illustrating a multi-tier computing environment that includes a plurality of nodes110-150. Each node110-150can comprise a computing device having one or more data processors and memory storing instructions for execution by the processor(s). In addition, each node110-150can include a network interface for allowing it to communicate over networks to other nodes110-150. In some cases, a node110-150can include or otherwise incorporate a database, while, in other variations, the node110-150can be in communication with a remote and separate database.

As is noted inFIG. 1, the nodes110-150are arranged such that a first node110is in communication with all of the other nodes120-150while, only a subset o the other nodes,140,150communicate with each other. For purposes of this document, the term multi-tier refers to a computing environment in which not all nodes are in direct communication. However, the first node110of the multi-tier environment can be arranged to orchestrate various actions amongst the other nodes120-150to collectively effect completion of a transaction. This orchestration can be accomplished for example, by the first node110sending messages that are tailored to node types for the other nodes120-150.

The multi-tier computing environment ofFIG. 1can operate in a multi-layer computing architecture.FIG. 2is a diagram200illustrating an example multi-tier architecture including a presentation tier210, an application tier220, and a data tier230that can be executed across multiple nodes110-150(e.g., a client-server architecture, etc.). Each of these tiers210,220,230can, in some cases, be implemented by separate and distinct nodes110-150(e.g., client devices in the presentation tier210, servers in the application tier220, and databases in the data tier230, etc.) and, in other cases, be implemented by a single node110-150.

The presentation tier210can execute a topmost layer in the multi-tier architecture which can be referred to, for example, as a presentation layer, which in turn, can, for example, execute user interface functionality (e.g., data presentation, interaction with graphical user interfaces, etc.). The presentation tier210can directly communicate with the application tier220and indirectly communicate with the data tier230via the application tier220and translate tasks from both tiers220,230for user interaction.

The application tier220can include an application layer that includes logic to initiate queries to the data tier230, to process results from the data tier230for ultimate presentation at the presentation tier210, and to handle other data coordination and manipulation activities.

The data tier230can include data persistence mechanisms (database servers, file shares, etc.) and a data access layer that encapsulates the persistence mechanisms and exposes the data. The data access layer can provide an interface to the application tier220that exposes methods of managing the stored data without exposing or creating dependencies on the data storage mechanisms. Avoiding dependencies on the storage mechanisms allows for updates or changes without the application tier220clients being affected by or even aware of the change.

With reference to diagram300, at300, the first node110can access a data object within the multi-layered computing architecture that works in conjunction with the data access layer230and the application layers220to transport data to the other nodes120-150in an effort to effect the transaction. The multi-tier environment is arranged such that at least a portion of the tiered nodes120-150do not communicate directly with each other. This data object encapsulates values which are used to effect the transaction. Thereafter, at320, the first node110generates node specific messages for each of a plurality of tiered nodes (i.e., nodes120-150) in the multi-tier computing environment relating to a transaction. The node specific messages can encapsulate at least a portion of the values in the accessed data object and respectively can be based on access visibility information associated with each such node120-150. This access visibility information can be based, for example, on node type or other classifications for the nodes120-150. In some cases, these classifications can change or otherwise be determined using, for example, a rules engine which determines which values to send to which of the other nodes120-150based, for example, on the state of the transaction, the type of transaction or other factors.

Subsequently, at330, the first node110transmits, to each of the plurality of tiered nodes120-150, the corresponding node specific message. The node specific messages convey information pertaining to the transaction and can, in some cases, be used to complete or otherwise effect a portion of the transaction by consumption at the receiving node120-150.

In response to the transmitted node specific messages, at340, the first node110receives data comprising a plurality of responses in response to the node-specific messages. In some cases, these responses are sent in response to triggers occurring at the respective nodes120-150. The triggers can, for example, relate to completion or other status information regarding aspects of the transactions. For example, completion of a computer-implemented task at one of the nodes120-150.

Using these responses, the first node110, at350, orchestrates completion of the transaction with the plurality of tiered nodes by transmitting messages to select nodes of the plurality of tiered nodes120-140characterizing responses from other nodes for which the select nodes are not in direct communication.

It will be appreciated that more than one node can orchestrate completion of the transaction and/or completion of a subset of the transaction. While the foregoing describes the first node110as being on a top tier and being able to coordinate with all other nodes120-150, it will be appreciated that other arrangements are available in which nodes110-150can communicate with each other on a peer to peer basis. For example, an arrangement can be provided such that the first node110does not communicate with node140but, rather, node140can only communicate with node150. For example, node140can send redirect data to node150that it receives from the first node110either complete (e.g., a carbon copy) or partial.

The data exchange amongst the nodes110-150can take or otherwise utilize varying data transport protocols. In some cases, the data is transported in cXML format while in other variations different transport protocols are used. Still further, arrangements are possible in which a node (e.g. the first node, etc.) communicates with some nodes using a first data transport protocol and communicates with other nodes using a different, second data transport protocol.

The multi-tier computing environment can be used for a variety of different applications in which a transaction is to be completed using a plurality of different computing nodes, some of which do not communicate with each other. One example is in connection with contract manufacturing. Contract manufacturing, also known as outsource manufacturing, is a type of manufacturing in which a company relies on the skills of specialist manufacturers to produce one or more components of a final product (i.e., the transaction). Ultimately, the supply chain manager or main manufacturer is in charge of bringing the different components made by component manufacturers together and preparing a final product for delivery. Because contract manufacturers often do not play a role in the manufacture of an entire product and only need to focus on one area, the use of the multi-tier environment as provided herein can provide enhanced cost-effectiveness and scalability.

The current subject matter provides technical advantages which, in turn, allow for increased visibility to allows users to proactively manage volatile demand and to link product design, manufacturing, and fulfillment within a supply chain. Moreover, the coordinated multi-tiered computing environment with a shared planning and execution layer as described herein allows for advanced operational analytics about demand patterns, operations, and customer service requirements. Still further, the current subject matter enables for real-time data access across multiple computing nodes within a manufacturing computing environment which, in turn, allows for more optimal synchronization of supply and demand.

FIG. 4is a diagram400of a two tier computing environment used in connection with a forecasting process. Initially, an OEM node410transmits first data to a tier one supplier node420that characterizes a forecast of finished product (e.g., product name, product type, product components, completion date, etc.). In parallel or in sequence, the OEM node410transmits second data to a tier two supplier node430that also characterizes a forecast of finished product (e.g., product name, product type, product components, completion date, etc.). With such an arrangement, the tier one supplier node420does not communicate with the tier two supplier node430. The tier two supplier node430can subsequently transmit third data to the OEM node410that indicates that the tier two supplier node430commits to providing components specified in the second data according to restrictions specified in the second data. The OEM node410then sends fourth data to the first tier supplier node420characterizing that the first tier supplier node can then proceed to manufacture the product specified in the first data. In such an implementation, the OEM node410orchestrates completion of a product (i.e., a transaction in this example) by forecasting and coordinating availability of components from the first tier supplier node420and the second tier supplier node430.

FIG. 5is a diagram500illustrating another multi-tier computing environment including a plurality of nodes505,515,525,535in a multi-tier computing environment. The first node505can generate and transmit data502comprising a purchase order and transmit data characterizing such purchase order to a second node515. The data502can be generated by accessing a data object encapsulating certain values. The first node505can, for example, be an ERP system or other system of an original equipment manufacturer (OEM). The second node515can be, for example, a computing system associated with a tier N supplier. The first node505can, in response, transmit data504including at least a subset of the values encapsulated in the data object to the third node525. The third node525can, for example, be a tier N−1 supplier. The data504can, for example be a complete copy of the data502or it can be a variation of the data502that is tailored specific to the third node525(i.e., data504can only include information relating to components provided by the tier N−1 supplier). Subsequently, the first node505can transmit data506to the fourth node535that can, for example, also include values encapsulated in the business object. The fourth node535can, for example, be a computing system associated with a logistics provider that, in turn, can be used to orchestrate transportation of components needed by the various nodes505,515,525as part of a transaction.

In some cases, the values encapsulated in the data object can be modified. The first node515can automatically, in response to the modification of the values in the data object, generate and transmit data508comprising a purchase order modification and transmit data characterizing such purchase order modification to a second node515. The data510can be generated by accessing the data object encapsulating certain values. Subsequently, the first node505can transmit data510including at least a subset of the values (including at least one modified value) encapsulated in the data object to the third node515. The data510can, for example be a complete copy of the data508or it can be a variation of the data508that is tailored specific to the third node525(i.e., data510can only include information relating to components provided by the tier N−1 supplier). Later, the first node505can transmit data512to the fourth node535that can, for example, also include modified values (e.g., values associated with quantities, delivery dates, etc.) encapsulated in the business object.

The second node515, at some later point, can transmit data514to the first node505that encapsulates data that confirms the purchase order. The first node505, in parallel or subsequently, can transmit data516to the third node525that also encapsulates data confirming at least a portion of the purchase order (i.e., the third node525may not have full visibility into the end product, etc.). The first node505can then transmit data518to the fourth node535characterizing confirmation of at least a portion of the purchase order. These confirmations can be used, for example, to execute aspects of the transaction such as transmitting data to complete components, update inventories, and/or to arrange for transportation logistics.

The second node515, at some later point, can transmit data520to the first node505that encapsulates data that specifies an advance shipment notice (ASN); namely a date on which the product will be transported to a facility associated with the first node. The first node505, in parallel or subsequently, can transmit data522to the third node525that also encapsulates data specifying at least a portion of the ASN (i.e., the third node525may not have full visibility into the end product, etc.). The first node505can then transmit data524to the fourth node535characterizing confirmation of at least a portion of the ASN. These notices can be used, for example, to execute aspects of the transaction such as transmitting data to complete components, update inventories, and/or to arrange for transportation logistics.

After the product(s) has been shipped, the third node can transmit data526to the first node505encapsulating data requesting and/or confirming receipt of goods. In addition, the fourth node535can transmit data528encapsulating a confirmation of the shipment of the product(s).

In some scenarios, one or more of the data transmissions associated with the second and third nodes515,525are triggered in response to consumption of goods at a site associated with a particular node515,525. For example, a computer-controlled inventory management system can automatically, without human intervention, identify when a particular components has been consumed, and as a result, data encapsulating a notification or other related message can be transmitted to another node within the computing environment to facilitate completion of the transaction. The consumption information can be implemented, using for example, a column-oriented in-memory database system that, in turn, can be used to provide real-time visibility into the availability of various components and the like.

Messages pertaining to subcontracting (e.g., interactions between the second node515and the third node525) can take various forms including. Some example fields can include, one or more those included in Table 1 below.

TABLE 1LevelFieldDescriptionItemItemCategoryA code defining how a material is procuredBuyerBatchIDAn identifier from buyer to identify the material/goodsproduced in a single manufacturing runSupplierBatchIDAn identifier from supplier to identify the material/goodsproduced in a single manufacturing runProductionDateDate on which when a batch of material/goods is producedExpirationDateDate on which when a batch of material/goods becomesexpiredOriginCountryCodeCountry of origin for a batch of material/goodsComponentComponentIDAn identifier for a subcontracting component within theprocurement processDescriptionComponent descriptionStandardIDA standardized identifier for a component, and theidentification scheme is managed by an agencyBuyerPartIDAn identifier for a component assigned by buyerSupplierPartIDAn identifier for a component assigned by supplierBuyerBatchIDAn identifier from buyer to identify the material/goodsproduced in a single manufacturing runSupplierBatchIDAn identifier from supplier to identify the material/goodsproduced in a single manufacturing runProductRevisionIDA sequential number that is assigned when changes are madeto a componentRequirementDateDate on which when a component is requiredQuantityAn amount of components in a unit of measurementUnitOfMeasureUnit of which a quantity is accounted for and expressedProperty ValuationAn element carrying a value that can be assigned tocharacteristics, such as property values pertaining to currencyamounts, quantities, or dates, etc. It can include the propertyto be valued and the associated values.