Dependency-chain index (CPL)
CPLCPLCritical path length. The total coordination weight of the longest chain of dependencies in the model. NovusLens reports it as index points, not elapsed time. helps you find the chain of dependencies where coordination may deserve attention. A dependency is a link between teams or services that need something from one another.
Example. Sales depends on Finance, and Finance depends on Data. If the first link is BufferedBufferedA handoff that takes more than one day and up to four days. It adds 1 point to the dependency-chain index. (1 point) and the second is RigidRigidA handoff that takes more than four days. It adds 3 points to the dependency-chain index. (3 points), this chain totals 4 index pointsIndex pointsThe unit of the dependency-chain index. Index points are structural weights, not hours or money, and every answer and what-if reports the index in them.. NovusLens compares the chains in the selected model and shows the one with the largest total.
LooseLooseA handoff that takes about one day or less. It adds 0.5 points to the dependency-chain index. links contribute 0.5 points, Buffered links 1 and Rigid links 3. These are structural weights: 4 points does not mean four hours or £4 of cost. Every answer and every what-ifWhat-ifA scenario that changes one or more dependencies in the model and reports the result. A what-if changes nothing in the records, and its result is indicative. reports the index in index points, never in hours. Measured handoffHandoffWork or information passed from one team or service to another. Its measured or stated completion time determines the dependency class. times help classify the links; read those times separately.
What to do. Open the highlighted chain on the map. Ask the teams where a handoff causes difficulty, then check the records supporting each link before exploring a change. A lower index can indicate less coordination burden in the model; it is not a delivery forecast.
The told and current-evidence views can identify different chains. Read the coverage beside the result: “3 of 5 couplingsCouplingA link where one team or service depends on another. Its Loose, Buffered or Rigid class describes the time needed for a handoff. measured” means two links still lack measurements. Unknown dependencies are excluded and counted, so incomplete coverage can hide a more demanding chain.