| | 1 | = Strawman transition timeline = |
| | 2 | |
| | 3 | ''This timeline identifies candidate milestones and elements of a transition plan. It is intended to be illustrative for planning and discussion purposes, not to set forth a final or complete plan.'' |
| | 4 | |
| | 5 | '''Fall 2015 milestones''' (outcomes of planning process) |
| | 6 | * Identify governance and administrative organizational models. |
| | 7 | * Identify financial model and estimated operating budgets. |
| | 8 | * Identify refresh and repair policies and priorities. |
| | 9 | |
| | 10 | '''Spring 2016 milestones''' |
| | 11 | * Governance / administrative leadership recruitment (Winter – Spring 2016) |
| | 12 | |
| | 13 | '''Summer 2016 milestones''' |
| | 14 | * First meetings / organizational kickoffs of governance and/or administrative organization(s). (Spring or summer 2016) |
| | 15 | * Detailed budget, including candidate specific sources of revenue, key expense allocations – e.g., hardware refresh costs, anticipated operations staffing and/or contracting costs. |
| | 16 | * Based on available funds and community priorities, publish initial refresh schedule, and issue initial RFPs. |
| | 17 | |
| | 18 | '''Fall 2016 milestones''' |
| | 19 | * Secure initial revenue commitments. |
| | 20 | * Receive proposals and select suppliers. |
| | 21 | * Initial activity transitions from GPO to new organization(s). |
| | 22 | |
| | 23 | '''Spring 2017 milestones''' |
| | 24 | * Secure ongoing revenue commitments. |
| | 25 | |
| | 26 | '''Fall 2017 milestones''' |
| | 27 | * Finalize transition. |
