UW-Madison users will most commonly use the IICS Shared Orgs and Secure Agents, but in some cases business units need additional isolation and control afforded by stand-alone Sub-Orgs and/or Secure Agents. You may find guidance on whether a Sub-Org might be right for you in the [Shared Org vs. Sub-Org](shared-org-vs-sub-org.md) document.
Sub-Orgs and stand-alone Secure Agents have an additional cost that is not included in the centrally funded shared service offering. If you and the IICS team have determined that a Sub-Org or stand-alone Secure Agent is appropriate, we will help you estiblish payment during initial setup.
## Sub-Orgs
* Annual cost: $6,524
* Includes both a sandbox and production environment.
## Secure Agents
* Annual cost: $2,372
* Includes both a sandbox and production Secure Agent.
* Secure Agents do *not* need to be purchased for training; a limited trial is sufficient for that purpose.
## Licensing and Payment
To set up a Sub-Org or stand-alone Secure Agent, business units must provide a **funding string** to the IICS team. The cost will be transferred from our cost center by DoIT Financial Services through WISER.
Both Sub-Orgs and Secure Agents must be purchased prior to usage, and the license must be co-termed with UW's annual renewal. Due to the terms of our Informatica licenses, we are not able to "true up" the licenses at the time of renewal.
*IICS team: Coordinate procurement with [DoIT Purchasing](mailto:purchasing@doit.wisc.edu) and [Olga Turkina](mailto:oturkina@uwsa.edu) from UW System. Work with [Greg Newman](mailto:greg.newman@wisc.edu) to establish payment. Greg will need the funding string provided by the requesting business unit to establish the cost center transfer.*
@@ -71,4 +71,4 @@ Integration Platform Team might be able to help cover the extra cost. Please [co
Here are some recommendation when to use a sub-org:
- Sub-orgs can be used for isolating different environments such as `test`, `qa` or `prod`.
- If your integration requires more than few integration assets and connections, then a sub-org may be a better fit.
- If fine-grained authorization is needed within an sub-org, a user group can be applied to objects (e.g. assets, connections, secure agents) to limit access to a subset of sub-org users.
\ No newline at end of file
- If fine-grained authorization is needed within an sub-org, a user group can be applied to objects (e.g. assets, connections, secure agents) to limit access to a subset of sub-org users.
