What is the situation when a new data source has to be built for IAM, and what does building it require?
All parties agree the extension makes sense, but no data source for the information exists; building one is usually a larger project that needs clear content goals, sufficient resources and sufficient time.
This branch of the integration process is reached when the scope extension was approved, the data model extended, the data-protection basis is in place, and the answer to "Data source available?" is no. Nobody in the organisation maintains the information in a usable, reliable form.
Then the source has to be built. That is far more than a database table:
- Who collects and maintains the data (a department, a role)?
- From what evidence (copies of driving licences, certificates, a register)?
- How it is kept current (re-checks, expiry dates)?
- Which system holds it, and who operates it?
That is why it is "usually a larger project", and treated with project management:
- clear content goals (exactly which data, in what quality),
- sufficient resources (people, budget, tools),
- sufficient time.
Once the source exists, the flow rejoins the common ending: find the person responsible, conclude the data delivery agreement, set up the technical connection.
Go deeper:
Project management triangle (Wikipedia) — scope, resources and time as the constraints any such project must balance.
Data steward (Wikipedia) — the role that owns ongoing maintenance and quality of a data set.