GTA Update. CIO Council March 17, 2008. RFQC Issued 10 Days Early. Early completion shows team’s focus and dedication RFQC requested proposals for two streams Infrastructure: data centers, mainframes, servers, PCs, laptops Managed network services: state’s wide area network
CIO CouncilMarch 17, 2008
This is transformational change
If you are not involved now, an agency with similar requirements is involved
Many processes will change
Enterprise agencies working with GTA to ensure success
Office of Planning and Budget
State Personnel Administration
State IT Expenditures and Priorities
Services for Georgians
Service Management Organization (SMO)
March 17, 2008
What Happens to Operations?
Enterprise Disaster Recovery
Enterprise Service Solutions
To manage the relationship between GTA and infrastructure providers to ensure business receives quality, cost effective, reliable and scaleable infrastructure services
To leverage the best practice technologies and processes from the infrastructure service providers to drive change in enterprise functions
External Service Providers
Functional View into the processes of the SMO
Governance and Oversight
Organization Structure(Roles and Responsibilities)
Operational and ManagementProcesses
Critical Success Factors
What is driving the creation of the SMO?
What are guiding principles for the SMO?
What does the SMO need to accomplish?
What is needed for the SMO to be successful?
How will success be measured?
What is the mandate of the SMO function?
How should the SMO be funded and how should it recover its costs?
What governance bodies will be required to ratify decisions and resolve escalated issues?
What are the key processes that the SMO executes in order to exercise its mandate?
Based on the organizational construct, what job roles are required to execute the processes?
People & Skills
How does the SMO interact with other functions within the enterprise & with external providers when executing its core processes?
How should the SMO be organized in order to execute these processes in an efficient manner?
Header: GTA, Discipline Name, Process Name
Process name, process no., release date, version
Author, reviser, approver
Process owner, title
2. Entry Criteria/Catalyst event
3. Included in process
4. Outside of process
7. Exit Criteria
8. Related Contract Terms and Conditions
9.Retained Records and Disposition
10. Process Flowcharts
11. Visio 2003 Document Embedding
12. Document List
15. Definitions (may be put in the process aid, if one is used)
16. Revision Control
Footer: Company Confidential, Page Number (of pages), revision number, revision date
Independent Verification and Validation:Project Assurance Process
March 17, 2008
IV&V is an “insurance policy” for Project Risk
Primary Reporting to:
Provides Advice & Council to:
Provides Recommendations to:
Reports to, as needed:
GTA Executive Director
GTA EPMO Director
GTA Engagement Manager
Enterprise Critical Project Review Panel
Standard Practices drive efficient and
Current “Pain Points”
One Size Fits All
We are considering a New Approach
Assessment > Assurance > Accountability
A Gauge of Project Risk
When available, via online self-assessment tool
Beta version of Procurement Self-Assessment Tool reviews: