User Tools

Site Tools


contract_approval_elevation_rules

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
contract_approval_elevation_rules [2019/04/02 13:10] – created adam.brusselbackcontract_approval_elevation_rules [2025/02/12 17:43] (current) tina.robles
Line 1: Line 1:
 **__Contract Approval Elevation Rules__** **__Contract Approval Elevation Rules__**
  
-Multiple approval elevation levels can be created, and each level can have its own max ratemax percent, or min price for each quantity range.+Multi-Tiered Approval Elevation System: 
 + 
 +The contract management system supports a sophisticated, multi-level approval elevation structure: 
 + 
 +Multiple Approval Tiers: 
 +  * The system accommodates various levels of approval authority 
 +  * Each tier can be customized to reflect different organizational hierarchies or approval requirements 
 + 
 +Tier-Specific Thresholds: For each approval level, customizable parameters can be establishedincluding: 
 +  * Maximum rate 
 +  * Maximum percentage 
 +  * Minimum price 
 + 
 +Quantity Range Specificity: 
 +  * These thresholds can be further refined based on specific quantity ranges 
 +  * This allows for granular control over approval requirements based on contract volume or scale 
 + 
 +This tiered system enables: 
 + 
 +  * Precise control over approval workflows 
 +  * Alignment of approval authority with contract value or complexity 
 +  * Efficient routing of contracts to appropriate decision-makers based on predefined criteria 
  
 Each approval elevation level can be tied to specific spots in the approval hierarchy. Each approval elevation level can be tied to specific spots in the approval hierarchy.
 ----- -----
  
-When creating an approval elevation level, the following must be specified:+Configuring Approval Elevation Levels:
  
-  * For the entire level, is the quantity threshold going to use the estimated quantity on a per-product, or per-contract basis? +When establishing an approval elevation level, the following parameters must be defined:
-  * For each (or all) product(s), what UOM the following options will be specified in: +
-    * Quantity range  +
-      * Max rate numeric for this specific quantity range - This one covers fixed rate $ contracts only +
-      * Minimum price for this specific quantity range - This one covers fixed price $ contracts only +
-      * Max rate percent for this specific quantity range - This one covers fixed rate % contracts only+
  
-There can be as many non-overlapping quantity ranges per-product as necessary. One or more of the max rate numeric, max rate percent, or min price can be specified.+Quantity Threshold Basis: 
 +  * Specify whether the quantity threshold applies on a per-product or per-contract basis for the entire level
  
-If a product is on a contract for a type that is not specifiedthe entire contract will not auto approve.+Product-Specific Parameters: For each product (or globally), define: 
 +  * Unit of Measure (UOM) for subsequent specifications 
 +  * Quantity range parameters 
 +  * Threshold values within each quantity range: Maximum rate (numeric) - Applicable to fixed rate $ contracts, Minimum price - Applicable to fixed price $ contractsMaximum rate (percentage) - Applicable to fixed rate % contracts
  
-Any contract with lumpsums will not auto approve. +Additional Configuration Details: 
 +  * Multiple non-overlapping quantity ranges can be specified per product as needed 
 +  * One or more threshold values (max rate numeric, max rate percent, or min price) can be defined for each range
  
 +Automatic Approval Restrictions:
 +  * Contracts containing products with undefined threshold types will not qualify for automatic approval
 +  * Contracts including lump sum items are excluded from automatic approval processes
  
-Example of Minimum Price Approval Elevation Rules: 
  
-{{:pasted:20190402-095952.png}}+Example of Minimum Price Approval Elevation Rules:
  
 +{{:pasted:20190402-133316.png}}
contract_approval_elevation_rules.1554210658.txt.gz · Last modified: 2019/04/02 13:10 by adam.brusselback