- Home
- Get started
- Data requirements
Data requirements
Start withwhat you have
Five core data types. Minimum viable datasets. No perfect data required. Data quality is an outcome of planning, not a prerequisite.
Core data types
Everything you need
These five data types give aangine everything needed for portfolio planning.
Portfolio items
Demands & Projects
Resources
Teams & People
Resource plans
Capacity
Allocations
Assignments
Effort & actuals
Time Tracking
Resource options
Choose your resource model
Pick the level of detail that matches your current data and future needs.
Option A: Team + Headcount
Team name + number of people available. 20% effort to implement. Best if team composition is stable.
Example: “Mobile Team, 8 people”
Option B: Role-Based
Define roles (Senior Dev, QA, Designer). Assign people to roles. Track capacity by role per team.
Example: “3 Senior Devs, 2 Mid-level Devs, 1 QA”
Option C: Individual
Individual people with skills, availability, and capacity per person. Highest precision allocation.
Example: “John Smith (Senior Dev, 100% available)”
Excel / CSV
Export from your tool to CSV. Import directly into aangine. Fastest for pilot programs.
Report export
Most PPM tools have reporting. Export standard reports. We map to aangine data model.
API / OData
Direct API access. We handle authentication and data syncing. Real-time or batch.
Database query
Direct database access for on-premises tools. We write secure queries and schedule exports.
Data quality
Key principle: Data quality is an outcome, not a prerequisite
You don’t need perfect data. Start with estimates. Rough timelines. Team guesses.
Planning reveals what data you need to improve, and improves it continuously. The act of planning in aangine forces your organization to get better data — because bad data produces obviously bad plans.
Next step
Let’s evaluate your data
Share your current data structure and we’ll tell you how to get started.