Production or work order management is an important aspect of most (if not all) manufacturing businesses. One of the most critical aspects of such management is to ensure that the proper types and amount of materials or parts have been acquired or produced, and have been transported to the location or locations where they will be needed to be used as part of the overall manufacturing process. This may require management of multiple internal and external operations including inspections, material or part testing, material or part preparation prior to being suitable for use in the overall process, identification of the location/process step where the material or part is needed, sensing/tracking of certain parameters of the sub-processes to ensure that the overall process is being executed properly, etc. Production management may also include various aspects of cost tracking, cost management, and cost optimization. In addition, some or all of these steps or stages may occur within an overall Project Management process where the manufacturing process is managed within a larger group of tasks, sub-tasks and processes that may not be directly related to a manufacturing or assembly process. For example, material or part costs and transportation costs may be an important aspect of the total cost and/or cash flow projections for a larger project.
In order to provide users with more effective tools for managing the production process, various types of graphical representations of a bill of material/work order have been developed. One of these is a graphical “bill of materials”, which attempts to display to a user the relationships between the steps or stages of a process or sub-process and the materials/parts required at that stage.
However, in a traditional graphical bill of materials, even If the materials are attached to an operation or routing step, the structure doesn't display to the user how the duration of the operation affects the way the materials are consumed (such as in terms of rate of material consumption or amount consumed (or required to complete the process) at any time). Additionally, the material itself may affect the overall timeline to complete the manufacturing process if that material and its availability affect other operations and tasks. This may be important information needed to manage production, particularly if additional materials need to be obtained from another location or are the result of a previous processing stage. Further, even temporary changes to the assumed operational parameters of the material transit or production phases used to supply the material to the operation step being analyzed may have an impact on the output or parameters of the operation step. For example, where the manufacturing process is managed within a larger project, any delay may in turn delay the overall project and subsequent tasks and/or billing milestones.
Embodiments of the subject matter disclosed herein in accordance with the present disclosure will be described with reference to the drawings, in which:
Note that the same numbers are used throughout the disclosure and figures to reference like components and features.
The subject matter of embodiments disclosed herein is described here with specificity to meet statutory requirements, but this description is not necessarily intended to limit the scope of the claims. The claimed subject matter may be embodied in other ways, may include different elements or steps, and may be used in conjunction with other existing or future technologies. This description should not be interpreted as implying any particular order or arrangement among or between various steps or elements except when the order of individual steps or arrangement of elements is explicitly described.
Embodiments will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, exemplary embodiments by which the systems and methods described herein may be practiced. This systems and methods may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy the statutory requirements and convey the scope of the subject matter to those skilled in the art.
Among other things, the present subject matter may be embodied in whole or in part as a system, as one or more methods, or as one or more devices. Embodiments may take the form of a hardware implemented embodiment, a software implemented embodiment, or an embodiment combining software and hardware aspects. For example, in some embodiments, one or more of the operations, functions, processes, or methods described herein may be implemented by one or more suitable processing elements (such as a processor, microprocessor, CPU, controller, etc.) that are part of a client device, server, network element, or other form of computing or data processing device/platform and that is programmed with a set of executable instructions (e.g., software instructions), where the instructions may be stored in a suitable non-transitory data storage element. In some embodiments, one or more of the operations, functions, processes, or methods described herein may be implemented by a specialized form of hardware, such as a programmable gate array, application specific integrated circuit (ASIC), or the like. The following detailed description is, therefore, not to be taken in a limiting sense.
In some embodiments, the subject matter may be implemented in the context of a multi-tenant, “cloud” based environment (such as a mufti-tenant business data processing platform), typically used to develop and provide web services and business applications for end users. This exemplary implementation environment will be described with reference to
Modern computer networks incorporate layers of virtualization so that physically remote computers and computer components can be allocated to a particular task and then reallocated when the task is done. Users sometimes speak in terms of computing “clouds” because of the way groups of computers and computing components can form and split responsive to user demand, and because users often never see the computing hardware that ultimately provides the computing services. More recently, different types of computing clouds and cloud services have begun emerging.
For the purposes of this description, cloud services may be divided broadly into “low level” services and “high level” services. Low level cloud services (sometimes called “raw” or “commodity” services) typically provide little more than virtual versions of a newly purchased physical computer system: virtual disk storage space, virtual processing power, an operating system, and perhaps a database such as an RDBMS. In contrast, high or higher level cloud services typically focus on one or more well-defined end user applications, such as business oriented applications. Some high level cloud services provide an ability to customize and/or extend the functionality of one or more of the end user applications they provide; however, high level cloud services typically do not provide direct access to low level computing functions.
The ability of business users to access crucial business information has been greatly enhanced by the proliferation of IP-based networking together with advances in object oriented Web-based programming and browser technology. Using these advances, systems have been developed that permit web-based access to business information systems, thereby allowing a user with a browser and an Internet or intranet connection to view, enter, or modify business information. For example, substantial efforts have been directed to Enterprise Resource Planning (ERP) systems that integrate the capabilities of several historically separate business computing systems into a common system, with a view toward streamlining business processes and increasing efficiencies on a business-wide level. By way of example, the capabilities or modules of an ERP system may include (but are not required to include, nor limited to only including): accounting, order processing, time and billing, inventory management, retail point of sale (POS) systems, eCommerce, product information management (PIM), demand/material requirements planning (MRP), purchasing, content management systems (CMS), professional services automation (PSA), employee management/payroll, human resources management, and employee calendaring and collaboration, as well as reporting and analysis capabilities relating to these functions.
In a related development, substantial efforts have also been directed to integrated Customer Relationship Management (CRM) systems, with a view toward obtaining a better understanding of customers, enhancing service to existing customers, and acquiring new and profitable customers. By way of example, the capabilities or modules of a CRM system can include (but are not required to include, nor limited to only including): sales force automation (SFA), marketing automation, contact list, call center support, returns management authorization (RMA), loyalty program support, and web-based customer support, as well as reporting and analysis capabilities relating to these functions. With differing levels of overlap with ERP/CRM initiatives and with each other, efforts have also been directed toward development of increasingly integrated partner and vendor management systems, as well as web store/eCommerce, product lifecycle management (PLM), and supply chain management (SCM) functionality.
By way of overview, various embodiments as discussed herein are directed to systems, apparatuses, and methods for more effective visual representations of the factors and parameters involved in executing an overall process. Such a process may be a typically be a manufacturing process, but the process may be any in which materials and resources are used to produce an end product. In one embodiment, a computer-based system and computer-implemented method are directed to a generating a graphical representation or user interface that depicts a time-ordered sequence of sub-processes and parameters associated with those sub-processes. The parameters may include one or more of tasks, manufacturing processes, material consumed at a given time, material required to complete a process at a given time, the rate of material consumption at a given time, additional material needed (beyond that currently available to the process), availability of the additional material (based on current or near-current inventory levels, warehouse or storage locations), time to complete for a required inter-dependent related process or task, and the like. Such a system and method may take advantage of materials and resources that can be assembled in a list and associated with one or more time attributes.
In further embodiment, the systems and methods may be used for monitoring and/or controlling a manufacturing process, a transportation process, a production process, an assembly process, or any other suitable process, project, or task. In some embodiments, an implementation of the system and methods described herein may be used as part of, or in conjunction with, a multi-tenant business data processing platform. In such an embodiment, real-time or pseudo real-time business data may be provided to a data processor and then used as part of generating one or more elements of the visual display. Further, the processor may execute one or more instructions or routines that result in accessing information about events that may impact the monitored or controlled process, sub-processes, tasks, functions, or operations. These events or notifications may initiate a sub-process of the monitored or controlled process, or impact a parameter of a sub-process.
One featured aspect of various embodiments is the use of a central timeline during the design, build, use, simulation, and execution of the manufacturing process. In one embodiment, the timeline includes three sections that correspond to a time attributes of materials and resources that may be used in the process:
During the design process, tasks, materials, operations, or services are “dragged” onto the appropriate part of the timeline. In other embodiments, tasks, materials, operations, or services are automatically populated into a visual display of a process timeline based on a set of manufacturing instructions, bill of materials, or recipe. Operations, tasks, and services are ordered in the appropriate sequence from first to last/left to right, and materials that are required for a particular operation, task or service to be completed are attached by dragging them together.
In simulation mode, the tasks, operations or services that appear on the timeline are evaluated and automatically identified as being part of the critical path (this may also be the result of application of a rule set or condition, where the critical path is a term commonly used in project management to determine the sequence of events that must be completed in time for the overall project to be completed). However, in this case, a material can also be part of the critical path if the material's availability impacts the overall completion or timing of the manufacturing process.
In one embodiment, any task, material, operation, or service that is on the timeline will be “flagged” as critical and work orders, travelers, operators, vendors, and purchase orders that relate to critical path items are “flagged” or otherwise identified. In one embodiment, vendors will be notified automatically by email or through alerts pushed to the vendor portal when a purchase order is pending or placed for a critical path item. Updates to a critical path element that affect the completion date/availability (e.g., transactional information, vendor delivery updates, purchase order receipts, and the like) will automatically adjust the elements and processes displayed on the timeline.
As part of a project, multiple work orders can be grouped together to display a project timeline with a critical path. Additionally, in some embodiments, there is an ability to group less related or unrelated work orders into a schedule group that would also be the subject of a critical path timeline. In this way, some tasks, materials, operations, or services may appear as part of multiple schedule groups and appear on the critical path timeline in some, but not others. If a task, material, operation, or service appears on the timeline in any group/work order, it will be flagged as a critical path element. In one embodiment, the greater the number of timelines on which a task, material, operation, or service appears, the more critical it will become and the relative priority of that element will be increased.
For example, a CRM (customer relationship management) application may generate a notification of a new sale of a certain number of units of a product (or generate a query to the application), which then initiates the a set of sub-processes that determine the availability of the finished products, and if manufacturing or assembly is required, what materials or parts are needed, when during the overall process they are needed, where they are needed, and any other relevant operational parameters. The sub-processes may include ones that query or determine aspects of an ERP (enterprise resource planning) application or related data in order to determine inventory levels, material in transit, location of warehouses, and the like, as part of the overall planning and scheduling of the delivery of the units of product.
Other objects and advantages will be apparent to one of ordinary skill in the art upon review of the detailed description and the included figures.
Prior to discussing the embodiments,
The distributed computing service/platform (which may also be referred to as a multi-tenant business-data-processing platform) 108 may include multiple processing tiers, including a user interface tier 116, an application server tier 120, and a data storage tier 124. The user interface tier 116 may maintain multiple user interfaces 117, including graphical user interfaces and/or web-based interfaces. The user interfaces may include a default user interface for the service to provide access to applications and data for a user or “tenant” of the service (depicted as “Service UI” in the figure), as well as one or more user interfaces that have been specialized/customized in accordance with user specific requirements (e.g., represented by “Tenant A UI”, . . . , “Tenant Z UI” in the figure, and which may be accessed via one or more APIs). The default user interface may include components enabling a tenant to administer the tenant's participation in the functions and capabilities provided by the service platform, such as accessing data, causing the execution of specific data processing operations, and the like. Each processing tier shown in
Each tenant data store 126 may contain tenant-specific data that is used as part of providing a range of tenant-specific business services or functions, including but not limited to ERP, CRM, eCommerce, Human Resources management, payroll, and the like. Data stores may be implemented with any suitable data storage technology, including structured query language (SQL) based relational database management systems (RDBMS).
In accordance with one embodiment, the distributed computing service/platform 108 may be a multi-tenant and service platform 108 and may be operated by an entity in order to provide multiple tenants with a set of business related applications, data storage, and functionality. These applications and functionality may include ones that a business uses to manage various aspects of its operations. For example, the applications and functionality may include providing web-based access to business information systems, thereby allowing a user with a browser and an Internet or intranet connection to view, enter, process, or modify certain types of business information.
As noted, such business information systems may include an ERP system that integrates the capabilities of several historically separate business computing systems into a common system, with the intention of streamlining business processes and increasing efficiencies on a business-wide level. By way of example, the capabilities or modules of an ERP system may include (but are not required to include, nor limited to only including): accounting, order processing, time and billing, inventory management, retail point of sale (POS) systems, eCommerce, product information management (PIM), demand/material requirements planning (MRP), purchasing, content management systems (CMS), professional services automation (PSA), employee management/payroll, human resources management, and employee calendaring and collaboration, as well as reporting and analysis capabilities relating to these functions. Such functions or business applications are typically implemented by one or more modules of software code/instructions that are maintained on and executed by one or more servers 122 that are part of the platform's Application Server Tier 120.
Another business information system that may be provided as part of an integrated data processing and service platform is an integrated CRM system, which is designed to assist in obtaining a better understanding of customers, enhance service to existing customers, and assist in acquiring new and profitable customers. By way of example, the capabilities or modules of a CRM system can include (but are not required to include, nor limited to only including): sales force automation (SFA), marketing automation, contact list, call center support returns management authorization (RMA), loyalty program support, and web-based customer support, as well as reporting and analysis capabilities relating to these functions. In addition to ERP and CRM functions, a business information system/platform (such as element 108 of
Note that both functional advantages and strategic advantages may be gained through the use of an integrated business system comprising ERP, CRM, and other business capabilities, as for example where the integrated business system is integrated with a merchant's eCommerce platform and/or “web-store.” For example, a customer searching for a particular product can be directed to a merchant's website and presented with a wide array of product and/or services from the comfort of their home computer, or even from their mobile phone. When a customer initiates an online sales transaction via a browser-based interface, the integrated business system can process the order, update accounts receivable, update inventory databases and other ERP-based systems, and can also automatically update strategic customer information databases and other CRM-based systems. These modules and other applications and functionalities may advantageously be integrated and executed by a single code base accessing one or more integrated databases as necessary, forming an integrated business management system or platform.
The integrated business system shown in
Rather than build and maintain such an integrated business system themselves, a business may utilize systems provided by a third party. Such a third party may implement an integrated business system as described above in the context of a multi-tenant platform, wherein individual instantiations of a single comprehensive integrated business system are provided to a variety of tenants. However, one challenge in such multi-tenant platforms is the ability for each tenant to tailor their instantiation of the integrated business system to their specific business needs. In one embodiment, this limitation may be addressed by abstracting the modifications away from the codebase and instead supporting such increased functionality through custom transactions as part of the application itself. Prior to discussing additional aspects of custom transactions, additional aspects of the various computing systems and platforms are discussed next with respect to
In
The application layer 210 may include one or more application modules 211, each having one or more sub-modules 212. Each application module 211 or sub-module 212 may correspond to a particular function, method, process, or operation that is implemented by the module or sub-module (e.g., a function or process related to providing ERP, CRM, eCommerce or other functionality to a user of the platform). Such function, method, process, or operation may also include those used to implement one or more aspects of the inventive system and methods, such as for:
Generating a user interface to permit the user to construct a timeline illustrating one or more selected operations or processes, with the operations or processes typically being part of a manufacturing, assembly, product development, project or similar process;
Enabling the user to link or otherwise associate one or more of the selected operations or processes with a material, element, or sub-process that is needed in order to properly execute the operation or process;
Automatically or at the direction of the user, associating the material, element, or sub-process with one or more data records or parameters, where such data records or parameters may be evaluated, determined, calculated, or revised as a result of the operations of a business data processing platform;
Automatically calculate the importance of a task, material, operation or service based on how many timelines it appears on; and
Allowing a user to create a schedule group of otherwise unrelated (or loosely related) work orders and having a critical path timeline associated with that group to analyze how these orders interact and affect each other in terms of the overall schedule.
The application modules and/or sub-modules may include any suitable computer-executable code or set of instructions (e.g., as would be executed by a suitably programmed processor, microprocessor, or CPU), such as computer-executable code corresponding to a programming language. For example, programming language source code may be compiled into computer-executable code. Alternatively, or in addition, the programming language may be an interpreted programming language such as a scripting language. Each application server (e.g., as represented by element 122 of
The data storage layer 220 may include one or more data objects 222 each having one or more data object components 221, such as attributes and/or behaviors. For example, the data objects may correspond to tables of a relational database, and the data object components may correspond to columns or fields of such tables. Alternatively, or in addition, the data objects may correspond to data records having fields and associated services. Alternatively, or in addition, the data objects may correspond to persistent instances of programmatic data objects, such as structures and classes. Each data store in the data storage layer may include each data object. Alternatively, different data stores may include different sets of data objects. Such sets may be disjoint or overlapping.
A user of the merchant's system 352 may access data, information, and applications (i.e., business related functionality) using a suitable device or apparatus, examples of which include a customer computing device 308 and/or the Merchant's computing device 310. In one embodiment, each such device 308 and 310 may include a client application such as a browser that enables a user of the device to generate requests for information or services that are provided by system 352. System 352 may include a web interface 362 that receives requests from users and enables a user to interact with one or more types of data and applications (such as ERP 364, CRM 366, eCommerce 368, or other applications that provide services and functionality to customers or business employees).
Note that the example computing environments depicted in
As described herein, one or more of the functions, operations, processes, or methods used to implement an embodiment may be provided by an extension to an existing application, process, function, operation, etc. In such an implementation, aspects of the inventive display may be provided as an extension to the operations of a multi-tenant business data processing platform or other suitable data processing system.
In order to provide users with more effective tools for managing projects or tasks, various types of graphical representations of a project have been developed. One of these is a graphical “bill of materials”, which attempts to display to a user the relationships between the steps or stages of a process or sub-process and the materials/parts required at that stage.
However, a traditional graphical bill of materials, even If the materials are attached to an operation/routing step, doesn't display to the user how the duration of the operation affects the way the materials are consumed (such as in terms of rate or amount). This may be important information needed to manage a project, particularly if additional materials need to be obtained from another location or are the result of a previous processing stage. Further, even temporary changes to the assumed operational parameters of the material transit or production phases used to supply the material to the operation step being analyzed may have an impact on the output or parameters of the operation step.
By re-orienting a traditional bill of material/work order view with the finished goods on the right side and the materials and operations aligned based on time, possible conflicts and effects of late orders are easier to identify. This arrangement offers the ability to time the order/release of materials based on the timeline, not a specific operation.
When a user engages an exemplary method for timeline visualization of a process, a number of data points may be assembled such that a user can see a listing of possible items in an item list 401. The item list 401 may sometimes be called the “gutter” and may appear in any orientation in a visualization such as on the right side as shown in
Further, the items in the item list 401 may be resources 415 that may be consumed at a particular rate during a process. For example, resource A 422 may be solder that may be consumed during a manufacturing process. Further yet, the items in the item list 401 may be operations that comprise both raw materials and resources. For example, operation A 423 may be the operation of soldering a capacitor to a printed circuit board. Generally speaking, a material 410 may be an item that is needed for in order to begin a process or finish a process and a resource 415 may be an item needed during an operation of the process.
Items in the item list 401 may have attributes associated with time. In an embodiment, each item may have an attribute indicating that the item is needed for a particular process before the process starts. Further, each item may have an attribute indicating that the item is needed for a particular process after the process ends. Further yet, each item may have an attribute indicating that the item is needed for a particular process while the process is being carried out. These time attributes may be used in conjunction with a visual representation of a timeline 400. The timeline itself may have a number of time periods including a first time period 405 associated with before starting the process, a second time period 406 associated with during the process, and a third time period 407 associated with after the process ends. Each item in the item list 401 may have different attributes associated therewith for different processes. Thus, if a visualization is to be created for a specific process, a specific process-based set of attributes are used in conjunction with any items in the item list 401. Then, a user may generate a new bill of materials (BOM), through this interface that features the central timeline 400 along with the list of items 401.
In
In an embodiment, the system may automatically determine which item to show in the body of the timeline 400 (as opposed to below the timeline). Such a determination of which item is displayed in the timeline may be a function of lead time or availability. Items having the longest lead time or the longest delay prior to availability may appear in the timeline 400 as this item creates the most impact on the length of the timeline. An availability or lead-time of the particular item may vary if the item is a special order item or one not typically in inventory. This aspect of how and what to display makes it easier for the user to understand which materials could be constraints on the overall timeline 400 and a critical path for the process. Thus, in the embodiment shown in
In other embodiments, how an item is placed into a timeline 400 and what items are displayed in a timeline 400 may be a function of a number of different attributes. For example, current inventory amount may affect how and where the items are displayed. Further, an assigned level of importance may affect the overall display in a timeline. Further yet, an average cost of the item may also affect how the item is displayed with higher cost items making up a critical path in terms of costs for a process.
In the next view of this sequence,
In
In another embodiment, various items that may have already been associated with an operation may then be shown below the timeline. To this end, the item amongst all items associated with an operation may be shown ion the critical path portion of the second period 406 of the timeline 400. For example, in
The timeline/critical path can and typically will contain a combination of items, materials, operations, and services. Various items that appear in the critical path may also automatically generate specific system actions as a result of being identified as part of a critical path. In one embodiment, if an item appears in a critical path, an electronic notification can be generated and communicated internally to other users or systems or may be sent externally to vendors or partners to indicate the importance of any given element being completed/delivered in a timely manner. These notifications may be email, alert driven, or displayed in portals for ease of consumption. Further, such notifications may be a purchase order to a vendor or partner if inventory identifies a shortage of the needed item.
The method of
If the creator chooses to add a material to the timeline through the left-side branch at query 510, the material is added to the timeline at step 514. But then, the method may also check the availability of the material by accessing an inventory system at step 516 within the ERP system to determine whether sufficient inventory exists for the intended use in this process. At query 518, the inventory system answers that there is sufficient inventory in the YES branch such that the material is then displayed in the timeline as available at step 520. The method then loops back to the initial add query at step 510.
If the inventory system determines that the material is not sufficiently stocked, another series of steps may be invoked through the NO branch starting with displaying the material on the timeline as unavailable at step 522. Such a step may also include changing an aspect to the displayed material, such as a color or location (e.g., an available material may be shown in green while an unavailable item may be shown in red—a material close to being unavailable may be shown in yellow). In other embodiments, when available items are less than a specific threshold (e.g., enough to finish a manufacturing run) then, the items may be considered unavailable. In some cases, the threshold may be set to a number that is at least as many as required to fulfill an order under processing. In some other case, the number may be 50% of the required quantity to fulfill an order because a purchase order may be in place to acquire more items. In the latter case, the system may fulfill as much of a full order as possible using the available items. If the material is unavailable, another query may occur at step 524 wherein a determination is made about any need for additional materials required for the initially unavailable material. Such a situation may occur if the initial unavailable material is also a locally made materials that may require additional materials. If the unavailable material now shown in the timeline after step 522 requires an additional process, a secondary timeline may be created and displayed at step 526. The secondary timeline may be displayed at step 526 in connection with the initial timeline and in a temporal context (as generally shown in
If no additional materials are needed for the unavailable material via the query at step 524, then the material may need to be put on order. The method may then automatically generate a purchase order (via a communicatively coupled purchase order computing system) at step 528. This may involve an automatic generation of an electronic communication and an arrangement for financial remuneration to one or more external entities. The purchase order may also include a delivery deadline that is based on the process timeline at step 530. Further, the method may then continue here when the material is received and the timeline may be updated (or inventory may be may updated as well) at step 532. The method may loop back around to initial query 510.
In accordance with one embodiment, the system, apparatus, methods, processes, functions, and/or operations for enabling efficient configuration and presentation of a user interface to a user based on the user's previous behavior may be wholly or partially implemented in the form of a set of instructions executed by one or more programmed computer processors such as a central processing unit (CPU) or microprocessor. Such processors may be incorporated in an apparatus, server, client or other computing or data processing device operated by, or in communication with, other components of the system. As an example,
It should be understood that the present disclosures as described above can be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present disclosure using hardware and a combination of hardware and software.
Any of the software components, processes or functions described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, Javascript, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.
All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and/or were set forth in its entirety herein.
The use of the terms “a” and “an” and “the” and similar referents in the specification and in the following claims are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms “having,” “including,” “containing” and similar referents in the specification and in the following claims are to be construed as open-ended terms (e.g.; meaning “including, but not limited to,”) unless otherwise noted. Recitation of ranges of values herein are merely indented to serve as a shorthand method of referring individually to each separate value inclusively falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate embodiments and does not pose a limitation to the scope of the disclosure unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to each embodiment of the present disclosure.
Different arrangements of the components depicted in the drawings or described above, as well as components and steps not shown or described are possible. Similarly, some features and sub-combinations are useful and may be employed without reference to other features and sub-combinations. Embodiments have been described for illustrative and not restrictive purposes, and alternative embodiments will become apparent to readers of this patent. Accordingly, the present subject matter is not limited to the embodiments described above or depicted in the drawings, and various embodiments and modifications can be made without departing from the scope of the claims below.
This application claims the benefit of U.S. Provisional Application No. 62/145,321, entitled “System and Methods for Visualization of Supply Chain and Data Processing or Related Tasks and Events,” filed Apr. 9, 2015, which is incorporated by reference in its entirety herein for all purposes.
Number | Date | Country | |
---|---|---|---|
62145321 | Apr 2015 | US |