chore(repo): checkpoint current capakraken implementation state
This commit is contained in:
@@ -6,7 +6,7 @@
|
||||
|
||||
## Goal
|
||||
|
||||
Extend Planarchy to support chargeability reporting with country-specific SAH (Standard Available Hours), FTE-based capacity, organizational hierarchy, utilization categories, client/WBS management, and a native chargeability report replacing the current Excel workflow.
|
||||
Extend CapaKraken to support chargeability reporting with country-specific SAH (Standard Available Hours), FTE-based capacity, organizational hierarchy, utilization categories, client/WBS management, and a native chargeability report replacing the current Excel workflow.
|
||||
|
||||
## Plan Documents
|
||||
|
||||
@@ -39,7 +39,7 @@ Derivation rules are configurable in admin (which countries map to which reporti
|
||||
Each project carries a utilization category (Chg, BD, MD&I, etc.). Hours assigned to a project inherit its category for reporting. Unassigned hours = SAH minus all categorized hours.
|
||||
|
||||
### Forecast chargeability = derived metric
|
||||
`forecastChg = hours on Chg projects / SAH`. No manual chargeability entry — it comes from what Planarchy already knows about assignments.
|
||||
`forecastChg = hours on Chg projects / SAH`. No manual chargeability entry — it comes from what CapaKraken already knows about assignments.
|
||||
|
||||
## Dependency Order
|
||||
|
||||
@@ -92,7 +92,7 @@ New fields on `Project`:
|
||||
## Open Questions
|
||||
|
||||
1. **Resource Type derivation rules**: The country→reporting-type mapping should be admin-configurable. Exact admin UI TBD.
|
||||
2. **Win Probability**: The Dispo file mentions it "should contain the value from MMS". Is this relevant for Planarchy? If so, it's a field on Project.
|
||||
2. **Win Probability**: The Dispo file mentions it "should contain the value from MMS". Is this relevant for CapaKraken? If so, it's a field on Project.
|
||||
3. **LCR/UCR**: Cost rate definitions are not yet available. Placeholder fields are included.
|
||||
4. **SAP import format**: What format do SAP period exports come in? CSV? API? Needs clarification for the import mechanism.
|
||||
5. **FTE history**: Currently single `fte` field. Monthly FTE tracking may be needed if contract changes happen mid-month.
|
||||
|
||||
Reference in New Issue
Block a user