Well, PROC INFOMAPS is an underlying tool that consultants use to generate complex information map based on a data-driven definition (often coming from Excel files). You don't use the procedure directly, there exist quite complex wrapper scripts that take care of all aspects of the infomap generation (using "proc infomaps" as a core) - source definitions, table relations, columns, custom attributes etc. I heard one such script is being used in SAS, and we in T1A have built a similar script for our consultants.
It is possible to use the same tool for a simple column addition to an existing informap, however I don't think the process can be fully automated. You'll have to go to CI Studio to refresh a business context anyway, and I don't think it is a good idea to do so while other users are in the systems and campaigns may be running. So, if you only need to add one new column, the programmatic solution using proc infomaps might not be easier than adding the same column manually through SAS Information Map Studio.
There is another way however, which may or may not be beneficial in different circumstances.
If the model scores are added to the data mart in a vertical (narrow) table: "CUSTOMER_ID", "MODEL_NAME", "SCORE_VALUE", it is possible for the users to define calculated items that extract one model value at a time:
max(case when <<MODEL_NAME>> = "MY MODEL 123" then <<SCORE_VALUE>> else NULL end)
Numeric calculated items with an aggregation function behave as measures, so get aggregated over a data set (group by subject ID), that's why it should work.
The process of defining such calculated items is still manual, but at least it can be delegated to the end-users. This may be helpful in certain circumstances (not always through).
-------
Dmitriy Alergant, Tier One Analytics