Common use of SCHEDULE AND MILESTONES Clause in Contracts

SCHEDULE AND MILESTONES. In Table 2.1, Schedule of Milestones, the following information must be supplied: • List of all milestones for this project • Expected completion dates. Identify any dependencies on actions that are outside of the project’s control or State that there are none. Project Start must be the first milestone, and Project End must be the last milestone. Note that projects should be staged and milestones identified so that at least one milestone is completed during each quarter of the overall project. Each milestone should also be tracked in the quarterly progress reports. In this FY 2014 Expanded CVISN Project Plan, the milestone dates are understood to be estimates; as the project proceeds, the estimated milestone completion dates should be updated in the quarterly progress reports. Examples of milestones include: • Vendor selection (if needed) • Stakeholder input • Requirements gathering/analysis completed • Conceptual design completed • Detailed design completed • Development/testing systems in place • Software iteration ‘n’ ready for integration testing • Functional testing performed • Interoperability testing performed • Final acceptance testing performed • Operations and maintenance plans identified • Production systems in place • “Go-live”. In addition, identify any dependencies on actions that are outside of the project’s control (e.g., legislative change). Table 3.1: Schedule of Milestones Milestone Expected Completion Date Project Start 7/18/2014 Begin Stakeholder Input 7/21/2014 Requirements Gathering/Analysis Completed 10/31/2014 Detailed Design Completed 6/30/2015 Software Development/Upgrades Complete 11/30/2015 Final Acceptance Testing Performed 12/31/2015 Project Acceptance 1/31/2016 Go Live 2/28/2016 Project End 2/28/2016

SCHEDULE AND MILESTONES. In Table 2.1, Schedule of Milestones, the following information must be supplied: • List of all milestones for this project • Expected completion dates. Identify any dependencies on actions that are outside of the project’s control or State that there are none. Project Start must be the first milestone, and Project End must be the last milestone. Note that projects should be staged and milestones identified so that at least one milestone is completed during each quarter of the overall project. Each milestone should also be tracked in the quarterly progress reports. In this FY 2014 Expanded CVISN Project Plan, the milestone dates are understood to be estimates; as the project proceeds, the estimated milestone completion dates should be updated in the quarterly progress reports. Examples of milestones include: • Vendor selection (if needed) • Stakeholder input • Requirements gathering/analysis completed • Conceptual design completed • Detailed design completed • Development/testing systems in place • Software iteration ‘n’ ready for integration testing • Functional testing performed • Interoperability testing performed • Final acceptance testing performed • Operations and maintenance plans identified • Production systems in place • “Go-live”. In addition, identify any dependencies on actions that are outside of the project’s control (e.g., legislative change). Table 3.12.1: Schedule of Milestones Milestone Expected Completion Date Project Start 7/18/2014 7/1/2015 Begin Stakeholder Input 7/21/2014 Requirements Gathering/Analysis Completed 10/31/2014 Detailed Design Completed 6/30/2015 Software Development/Upgrades Complete 11/30/2015 Procurement Process 7/01/2015 Issue Purchase Order 7/15/2015 Vendor Programming 8/1/2015 Functional / Final Acceptance Testing Performed 12/31/2015 acceptance 8/2/2016 Project Acceptance 1/31/2016 Go Live 2/28/2016 8/10/2016 Project End 2/28/20168/15/2016

SCHEDULE AND MILESTONES. In Table 2.15.1, Schedule of Milestones, the following information must be supplied: • List of all milestones for this project • Expected completion dates. Identify any dependencies on actions that are outside of the project’s control or State that there are none. Project Start must be the first milestone, and Project End must be the last milestone. Note that projects should be staged and milestones identified so that at least one milestone is completed during each quarter of the overall project. Each milestone should also be tracked in the quarterly progress reports. In this FY 2014 2012 Expanded CVISN Project Plan, the milestone dates are understood to be estimates; as the project proceeds, the estimated milestone completion dates should be updated in the quarterly progress reports. Examples of milestones include: • Vendor selection (if needed) • Stakeholder input • Requirements gathering/analysis completed • Conceptual design completed • Detailed design completed • Development/testing systems in place • Software iteration ‘n’ ready for integration testing • Functional testing performed • Interoperability testing performed • Final acceptance testing performed • Operations and maintenance plans identified • Production systems in place • “Go-live”. In addition, identify any dependencies on actions that are outside of the project’s control (e.g., legislative change). Table 3.15.1: Schedule of Milestones Milestone Expected Completion Date Project Start 7/18/2014 7/1/2012 Begin Stakeholder Input 7/21/2014 input 7/1/2012 Requirements Gatheringgathering/Analysis Completed 10/31/2014 analysis completed 7/15/2012 Detailed Design Completed 6/30/2015 design completed 8/1/2012 Begin Procurement Process 9/1/2012 NTP Issued 10/15/2012 Software Development/Upgrades Development Complete 11/30/2015 11/15/2012 Unit Testing complete 11/22/2012 Equipment Installation 12/1/2012 Final Acceptance Testing Performed 12/31/2015 acceptance testing performed 2/1/2013 Project Acceptance 1/31/2016 4/1/2013 Pilot Period Complete/ System Go Live 2/28/2016 7/1/2013 Project End 2/28/20167/1/2013 There are no dependencies on actions that are outside of the project’s control.