Line 1: |
Line 1: |
| + | ICANN's '''Engineering & Information Technology''' ('''E&IT''') department is the foundational "service provider" for ICANN. The E&IT team uses an integrative, collaborative process to gather demands for systems and prioritize work. Twice a year, senior leaders in ICANN org evaluate their respective function's current and future E&IT-related project demands. Projects include optimizing computer, network, and storage infrastructure, custom-coding fit-for-purpose software systems, and optimizing the infrastructure for such systems.<ref>[https://www.icann.org/en/blogs/details/a-peek-into-the-icann-org-engineering-factory-and-an-update-on-czds-5-11-2020-en A peek into ICANN Org's Engineering "Factory," ICANN Blogs]</ref> |
| | | |
| + | ==Frozen Delivery Pipeline Process== |
| + | The list of IT demands is managed via the following process. Feedback is gathered from each team, project proposals are aligned with ICANN's strategies, and cross-functional dependencies and impacts and community input are considered to prioritize requests. This process leads to a priority list of E&IT demands for each function within ICANN org. The projects are considered in light of community-reviewed and ICANN Board-approved budgets and the E&IT department’s capacity for each upcoming semester (January-June or July-December). The resulting list is called the “Frozen Delivery Pipeline,” which is then reviewed and approved by ICANN Senior Vice Presidents and the ICANN CEO. |
| + | |
| + | ==E&IT Workstreams== |
| + | The E&IT department has seven workstreams: |
| + | # Community Engagement: supporting [[Engagement]] with the ICANN community. |
| + | # Community Collaboration: working on tools and websites used by ICANN org, [[SO]]s, and [[AC]]s, such as the [[Information Transparency Initiative]] (ITI). |
| + | # Contracted Parties: supporting transactional work with [[registries]] and [[registrars]] |
| + | # Technical Services: the systems used by ICANN org and/or community to ensure contracted parties meet contractual obligations, such as [[Service Level Agreement Monitoring]] (SLAM), Zone File Access, and [[CZDS]] |
| + | # IANA Services: systems for performing the IANA functions, including root zone management. |
| + | # [[:Category:ICANN Staff]] Services: for the ICANN org, including Enterprise Resource Planning (ERP) functions for [[HR]] and [[Finance]], Intranet, email, and phone systems |
| + | # IT Infrastructure: systems and services such as Zoom, data centers, cloud, information security, and ICANN Managed Root Servers ([[IMRS]]). |
| + | |
| + | ==E&IT Roles== |
| * SVP, Engineering and Chief Information Officer (CIO): [[Ashwin Rangan]] | | * SVP, Engineering and Chief Information Officer (CIO): [[Ashwin Rangan]] |
| | | |
Line 33: |
Line 48: |
| * Software Engineer 2 | | * Software Engineer 2 |
| * Technical Lead, Software Engineering | | * Technical Lead, Software Engineering |
− |
| |
− |
| |
| | | |
| * Salesforce Engineer 2- Salesforce | | * Salesforce Engineer 2- Salesforce |
Line 49: |
Line 62: |
| * Senior Cryptographic Key Manager | | * Senior Cryptographic Key Manager |
| * Cryptographic Key Manager | | * Cryptographic Key Manager |
| + | |
| + | ==References== |
| + | |
| | | |
| [[Category:ICANN Organization]] | | [[Category:ICANN Organization]] |