Merge branch 'system-contact-branch' into 'master'

Added UW System org considerations and contact info

See merge request !65

README.md

@@ -15,6 +15,7 @@
 * [Secure Agents](./docs/secure-agent.md)
 * [EI Secure Agent](./docs/ei-secure-agent.md)
 * [Shared Orgs and Sub Orgs](./docs/shared-org-vs-sub-org.md)
+* [Madison and System IICS Orgs](./docs/madison-vs-system-iics.md)
 * [Get Help](./get-help.md)
 
 # Informatica Integration Cloud Services
@@ -45,15 +46,10 @@ The below diagram visualizes some of the iPaaS (IICS) capabilities.
 The diagram source can be found [here](https://www.lucidchart.com/documents/edit/dd614f97-9c7b-4164-8bd7-f9fac442c4c6/0_0).
 
 ## Documentation
+This repository is the documentation library for DoIT's offering of Informatica Intelligent Cloud Services (IICS). IICS is part of UW's Integration Hub, a collection of service offerings that enable data integration throughout the UW System. You can find more information about these service offerings in the [Integration Catalog](https://integratedata.wisc.edu/integration-catalog/).
 
-This GitLab repository is used as our temporary documentation library for DoIT's offering of Informatica Intelligent Cloud Services (IICS) as part of the first "minimum viable product" (MVP) release.
-For more information on the first release, [please see this blog post](./blog-posts/iics-mvp.md).
-Feel free to navigate this repository by browsing the files or using the links below.
-
-Please contact us (integration-platform@doit.wisc.edu) if you need additional help or if you weren't able to use the documentation to answer your question.
-Merge requests are welcome if you have suggestions for improving the documentation, but please send us an email if you prefer communicating directly.
-
-IICS is part of the infrastructure and services being delivered by the [Interoperability Initiative](https://interop.it.wisc.edu/).
+Please contact us [integration-platform@doit.wisc.edu](mailto:integration-platform@doit.wisc.edu) if you need additional help or if you weren't able to find answers to your questions in the documentation.
+Merge requests are welcome if you have suggestions for improving the documentation, or you may send us an email if you prefer communicating directly.
 
 ## Adding New Content
 Use [template.md](./template.md) to create new content.

docs/madison-vs-system-iics.md

+# Madison and System IICS Orgs
+
+IICS is available to all UW System institutions, but UW-Madison has its own IICS org and sub-orgs, funded by and intended for UW-Madison integrators. This document will help you determine if you should use the Madison IICS orgs or the UW System IICS orgs.
+
+Both Madison and System orgs have sub-orgs (or child-orgs) for business units or institutions that have specific needs beyond what's provided in the shared environments. See [Shared Orgs and Sub-Orgs](./docs/shared-org-vs-sub-org.md) for more information on sub-orgs.
+
+## Considerations
+
+- IICS is a tool used for data integration agnostic of source and target; it has no inherent data present in any of the orgs.
+- There are no functional differences between Madison and System IICS orgs, and both are licensed for equivalent connectors.
+- The [Secure Agents](./docs/secure-agent.md) associated with each org can be made to connect to any source or target with appropriate firewall changes.
+- Madison's shared IICS org and the support team that manages it are centrally funded for UW-Madison integrators and use cases.
+- The IICS org you choose should be based on the home institution of the use case(s), regardless of the source, target, or scope of data being integrated.
+- Cross-cutting use cases that span the System, e.g. for shared ERPs like Workday, should be housed in the System org.
+
+## Examples
+
+1. You are building an integration for a UW-Madison business unit whose application needs data about people and jobs from across UW System. You should use the UW-Madison IICS org and you will be supported by DoIT Enterprise Integration because your use case is for a UW-Madison business purpose. Despite the System-wide scope of the data you're integrating, Madison funds usage and support of IICS for you and your business unit.
+
+1. You work in a UW-Madison business unit (e.g. Enterprise Business Systems) but are doing work funded by and on behalf of UW System (e.g. building integrations for Workday). Because the use case is for a UW System-wide business purpose, you should use the UW System IICS org.
+
+1. Consider a circumstance in which UW-Madison decides to change our Integration Platform vendor. While we have no plans to do this today, the impact of that decision should be limited to the scope of UW-Madison use cases and business units, not System use cases (e.g. Workday or UW System data lakes). If such a change would impact the ability to provide services to other institutions or across UW System, then that integration use case should use UW System IICS org.
+
+## UW System IICS Contact and Support
+
+If you have determined that you should use the UW System IICS org, please contact [Justin Weidner](mailto:justin.weidner@wisconsin.edu). You may also obtain support from the UW System-wide Integration Platform Community of Practice by emailing [iPaaS-community-Practice@lists.wisconsin.edu](mailto:iPaaS-community-Practice@lists.wisconsin.edu).