Cross-Functional Flowchart

This purchase order processing UML activity diagram was created on the base of activity diagram from the software architecture documentation wiki of the Software Engineering Institute (SEI) of Carnegie Mellon University (CMU).
[wiki.sei.cmu.edu/ sad/ index.php/ Image:PurchaseOrderActivityDiagram.png]
"A purchase order (PO) is a commercial document and first official offer issued by a buyer to a seller, indicating types, quantities, and agreed prices for products or services. Acceptance of a purchase order by a seller forms a contract between the buyer and seller, so no contract exists until the purchase order is accepted. It is used to control the purchasing of products and services from external suppliers.
Creating a purchase order is typically the first step of the purchase to pay process in an ERP system." [Purchase order. Wikipedia]
This purchase order processing UML activity diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.

"Business process improvement (BPI) is a systematic approach to help an organization optimize its underlying processes to achieve more efficient results. ...
An organization is only as good as its processes. To be able to make the necessary changes in an organization, one needs to understand the key processes of the company. Rummler and Brache suggested a model for running a Process Improvement and Management project (PI&M), containing the following steps:
1. Identify the process to be improved (based on a critical business issue): The identification of key processes can be a formal or informal exercise. The management team might select processes by applying a set of criteria derived from strategic and tactical priorities, or process selection is based on obvious performance gaps. It is important is to select the process(es) which have the greatest impact on a competitive advantage or customer requirement.
2. Develop the objective(s) for the project based on the requirements of the process: The focus might be on quality improvement, productivity, cost, customer service or cycle time. The goal is however always the same; to get the key process under control.
3. Select the members of the cross-functional team: A horizontal (cross-functional) analysis is carried out by a team composed of representatives of all functions involved in the process. While a consultant or in-house staff person can do the job, the quality of the analysis and the commitment to change is far greater with a cross-functional team.
4. Document the current process by creating a flowchart or "organization map": Describe the process regarding the Organizational level, the Process level and the Job/ Performer level according to Rummler. Develop a cross-functional process map for the process.
5. Identify "disconnects" in the process: “Disconnections” are everything that inhibit the efficiency and effectiveness of the process. The identification should be categorized into the three levels: The Organizational level, the Process level and the Job/ Performer level.
6. Recommend changes (organizational, in the process or in its execution): Categorize and prioritize the main problems and possibilities, evaluate alternative solutions. Develop a cross-functional process map for the recommended process.
7. Establish process and sub-process measures: The process measures should reflect the objectives of the project.
8. Implement the improvements." [Business process improvement. Wikipedia]
The opportunity flow chart example "Replacing engine oil" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Cross-Functional Flowcharts solution from the Business Processes area of ConceptDraw Solution Park.