Cab booking public process - Collaboration BPMN 2.0 diagram

The Collaborative business process diagram depicts interactions between customer, travel agent and cab driver, which are defined as a sequence of activities, and represent the message exchange during a cab booking process.
"Business process modeling is used to communicate a wide variety of information to a wide variety of audiences. BPMN is designed to cover this wide range of usage and allows modeling of end-to-end business processes to allow the viewer of the Diagram to be able to easily differentiate between sections of a BPMN Diagram. There are three basic types of sub-models within an end-to-end BPMN model: Private (internal) business processes, Abstract (public) processes, and Collaboration (global) processes...
Collaboration (global) processes.
A collaboration process depicts the interactions between two or more business entities. These interactions are defined as a sequence of activities that represent the message exchange patterns between the entities involved. Collaboration processes may be contained within a Pool and the different participant business interactions are shown as Lanes within the Pool. In this situation, each Lane would represent two participants and a direction of travel between them. They may also be shown as two or more Abstract Processes interacting through Message Flow. These processes can be modeled separately or within a larger BPMN Diagram to show the Associations between the collaboration process activities and other entities. If the collaboration process is in the same Diagram as one of its corresponding private business process, then the activities that are common to both processes can be associated." [Business Process Model and Notation. Wikipedia]
The BPMN 2.0 (Business Process Model and Notation) collaboration diagram example "Cab booking public process" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.

"Logistics is the management of the flow of goods between the point of origin and the point of consumption in order to meet some requirements, for example, of customers or corporations. The resources managed in logistics can include physical items, such as food, materials, animals, equipment and liquids, as well as abstract items, such as time, information, particles, and energy. The logistics of physical items usually involves the integration of information flow, material handling, production, packaging, inventory, transportation, warehousing, and often security. The complexity of logistics can be modeled, analyzed, visualized, and optimized by dedicated simulation software. The minimization of the use of resources is a common motivation in logistics for import and export." [Logistics. Wikipedia]
The BPMN 2.0 (Business Process Model and Notation) diagram example "Logistics" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.

"An issue tracking system (also ITS, trouble ticket system, support ticket, request management or incident ticket system) is a computer software package that manages and maintains lists of issues, as needed by an organization. Issue tracking systems are commonly used in an organization's customer support call center to create, update, and resolve reported customer issues, or even issues reported by that organization's other employees. An issue tracking system often also contains a knowledge base containing information on each customer, resolutions to common problems, and other such data. An issue tracking system is similar to a "bugtracker", and often, a software company will sell both, and some bugtrackers are capable of being used as an issue tracking system, and vice versa. Consistent use of an issue or bug tracking system is considered one of the "hallmarks of a good software team".
A ticket element, within an issue tracking system, is a running report on a particular problem, its status, and other relevant data. They are commonly created in a help desk or call center environment and almost always have a unique reference number, also known as a case, issue or call log number which is used to allow the user or help staff to quickly locate, add to or communicate the status of the user's issue or request.
These tickets are so called because of their origin as small cards within a traditional wall mounted work planning system when this kind of support started. Operators or staff receiving a call or query from a user would fill out a small card with the user's details and a brief summary of the request and place it into a position (usually the last) in a column of pending slots for an appropriate engineer, so determining the staff member who would deal with the query and the priority of the request." [Issue tracking system. Wikipedia]
The BPMN 2.0 (Business Process Model and Notation) diagram example "Trouble ticket system" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.

"The vision of BPMN 2.0 is to have one single specification for a new Business Process Model and Notation that defines the notation, metamodel and interchange format but with a modified name that still preserves the "BPMN" brand. The features include:
(1) Aligning BPMN with the business process definition meta model BPDM to form a single consistent language.
(2) Enabling the exchange of business process models and their diagram layouts among process modeling tools to preserve semantic integrity.
(3) Expand BPMN to allow model orchestrations and choreographies as stand-alone or integrated models.
(4) Support the display and interchange of different perspectives on a model that allow a user to focus on specific concerns.
(5) Serialize BPMN and provide XML schemes for model transformation and to extend BPMN towards business modeling and executive decision support." [Business Process Model and Notation. Wikipedia]
The BPMN 2.0 (Business Process Model and Notation) diagram example "Booking process" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.

The vector stencils library "Swimlanes" contains 20 swimlane shapes for drawing business process diagrams (BPMN 2.0) using the ConceptDraw PRO diagramming and vector drawing software.
"Swim lanes are a visual mechanism of organising and categorising activities, based on cross functional flowcharting, and in BPMN consist of two types: (1) Pool. Represents major participants in a process, typically separating different organisations. A pool contains one or more lanes (like a real swimming pool). A pool can be open (i.e., showing internal detail) when it is depicted as a large rectangle showing one or more lanes, or collapsed (i.e., hiding internal detail) when it is depicted as an empty rectangle stretching the width or height of the diagram. (2) Lane. Used to organise and categorise activities within a pool according to function or role, and depicted as a rectangle stretching the width or height of the pool. A lane contains the flow objects, connecting objects and artifacts." [Business Process Model and Notation. Wikipedia]
The example "Design elements - Swimlanes BPMN 2.0" is included in the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.

This BPMN (Business Process Model and Notation) diagram sample shows the order processing workflow.
"In business or commerce, an order is a stated intention, either spoken or written, to engage in a commercial transaction for specific products or services. From a buyer's point of view it expresses the intention to buy and is called a purchase order. From a seller's point of view it expresses the intention to sell and is referred to as a sales order. When the purchase order of the buyer and the sales order of the seller agree, the orders become a contract between the buyer and seller.
Within an organization, the term order may be used to refer to a work order for manufacturing, a preventive maintenance order, or an order to make repairs to a facility.
In many businesses, orders are used to collect and report costs and revenues according to well-defined purposes. Then it is possible to show for what purposes costs have been incurred." [Order (business). Wikipedia]
The business process modeling diagram example "Order process - BPMN 2.0 diagram" was designed using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Model and Notation solution from the Business Processes area of ConceptDraw Solution Park.