RQ Tracking allows RQs to be query/formula calculated, with access to the resource's context. KPIs (e.g. Key Performance Indicators)
are prime examples of TRQs. TRQ requirement considerations include:
- TRQs (“Tracking Resource Qualities”) are resource attributes (e.g. RQs) with valid formulas
- On selected events or schedules, TRQ “metrics” formulas calculate “actual” quality values
- TRQ formulas can access resource context, including attributes and availablesemantics
- Infrastructure mode supports all types that map to Strings (e.g. application managed)
- Semantics mode operation provides specific type and format support and validation
- Constraints, with scheduling support can be defined and enforced as required
- Any resource can have any number of tracking qualities, at any point in time
- Formula factor attributes can also be added as required
- Dedicated XML-namespaces require specification
A department resource can have a TRQ called “Performance” that, when invoked, traverses all the department's resources, in
structured order, calculating the latest performance for each and cumulating to a relative value, mapped to a more natural:
1 of 5 or 1 of ten appreciations, like “ok, improving”, for the TRQ value, for example.
The query-formula can use any other attributes as goals, estimates, capabilities, value, or invoke other attributes' formulas
(e.g. predicates, TRQs). If the resource has constraints formulas, they are checked and cleared first and, in any case, every
operation is defined for entitlement secure resource environments).
There are various tracking patterns where sub-resource cumulations and nested queries are naturally supported by recursive
resources. I/O and process triggering are also common. With open entitlement and no specified constraint, complex interlinked
tracking can be developed.