FY09 Tactical Plans for Information Systems

1
FY09 Tactical Plans forInformation Systems

• Igor Mandrichenko
• 9/24/2008

2
FY09 Tactical Plan for Information Systems

• Relevant Strategic Plan(s)
• Central Services Strategic Plan
• Databases and Applications Strategic Plan
• Tactical Plan Leader Matt Arena
• Organizational Unit home LSCS/DBI

3
FY09 Tactical Plan Strategies and Goals

• Tactical Plan Strategies
• In cooperation with other groups and departments
  of Computing Division, participate in development
  and support of applications needed to improve the
  efficiency of the Division while avoiding
  duplication of functionality provided by other
  parts of the Laboratory
• Identify business processes bottlenecks and apply
  focused effort to eliminate them
• Implement ITIL practices into all stages of our
  project lifecycle
• Develop expertise in a set of software tools that
  help end users with little or no programming
  skills create simple applications. Provide
  technical and consulting help to the users who
  are developing their application using the tool
  set.
• Consistently apply common development approaches
  and software tools to increase efficiency of
  application development and support

4
FY09 Tactical Plan Strategies and Goals

• Tactical Plan Goals
• Provide the Computing Division and the Laboratory
  with automated procedures to reduce paperwork and
  increase functionality though automated workflow
• Provide application developers with methods
  access infrastructure databases
• Develop and support administrative applications
  that support the scientific community
• Introduce SharePoint or similar framework as
  Labs information sharing and communication
  platform.

5
FY09 Tactical Plan Objectives

• Improvements of technology base
• Search for workflow application development
  framework to replace AlphaFlow
• Introduce SharePoint (or similar technology) as
  an information exchange framework
• Search and implement more efficient technologies
  for web applications development

6
FY09 Tactical Plan Objectives (continued)

• Provide support for Labwide business processes
• Assist in the effort to transition to ITIL and
  ISO 20000 standards. Participate in
  implementation of
• Service Desk
• Asset Management
• Configuration Management Database
• Change Management
• Support the ESH Sections database applications
• Support the MISCOMP infrastructure database
  applications
• Support the efforts to automate Account
  Management
• Participate and facilitate development and
  support of workflow applications such as eTravel,
  New Hire.

7
FY09 Tactical Plan Objectives (continued)

• Provide support for the Laboratorys scientific
  activities
• Provide support to maintain DocDB in its current
  state
• Search for alternative document/content
  management systems that scale to the Laboratorys
  and broader scientific user communitys
  requirements.
• Provide support and development for InDiCo
  developed at CERN
• Provide support and maintenance for the SPMS
  conference management software.

8
FY09 Tactical Plan Objectives (continued)

• Provide support for CDs existing infrastructure
  database applications.
• Re-design the CD Effort Reporting system to
  interface with the Labs OTL system (FTL)
• Migrate the Budget Input database to Oracle and
  integrate it with the existing infrastructure
  data.

9
FY09 Tactical Plan Objectives (continued)

• Develop new applications and integrate existing
  applications with Microsoft Office SharePoint
  platform.
• Train developers in SharePoint framework
• Provide interfaces for SharePoint portals to
  access existing applications and databases.
• Develop new applications in the SharePoint
  framework.
• Participate in design and development of Lab
  Intranet Portal, project and personal pages
• Improve the efficiency of the Divisions internal
  business processes
• Have project leaders complete ITIL training.

10
FY09 Tactical Plan Past Action Items

• Workflow Aplications
• We had several meetings with potential
  stakeholders for workflow projects
• We identified several classes of workflow
  applications which are needed by CD and the Lab
• We developed strategic approach for workflow
  management application development based on the
  following principles
• Develop expertise in one or more existing
  workflow management software packages
• Actively participate in development of complex
  applications
• Provide expert help and limited development
  resources to end users who will be developing
  simple applications mostly themselves

11
Project Activity Microsoft Office SharePoint
Implementation

• Goals Related to this Activity from Tactical
  Plan
• 1. Increase efficiency and facilitate
  collaboration and communication in the Lab as an
  organization
• New, High
• 2. Implement SharePoint as IT application
  framework that supports Lab-wide information
  management architecture
• New, High
• 3. Improve efficiency of IT application
  development, deployment and support and decrease
  effort needed to deploy web-based applications
• New, Medium
• 4. Empower and enable application development by
  end users
• New, Medium

• Key Milestones
• Implement SharePoint
• Design CD and Lab intranet portals
• Produce MyPage development guidelines and
  documentation
• Integrate several existing applications with
  SharePoint
• http//sharepoint.fnal.gov/cdprojects/SP_Project/d
  efault.aspx
• Metrics, if any applicable (may be none for some
  Project Activities)
• Issues and Risks (specific to this activity,
  includes allocation impact)
• Need buy-in from users community, new technology,
  lack of pre-existing expertise

12
Project Activity ITIL Implementation

• Goals Related to this Activity from Tactical
  Plan
• 1. Work with consultants on ITIL implementation
• New, High

• Key Milestones
• Implement Asset Management DB
• Implement or deploy Configuration Management DB
• Implement or deploy Change Management System
• Implement or deploy Service Desk
• Issues and Risks (specific to this activity,
  includes allocation impact)
• ITIL is not so familiar to our staff, and its
  implementation will require adoption of different
  practices and standards

13
Project Activity Account Management

• Goals Related to this Activity from Tactical
  Plan
• 1. Design and develop comprehensive account
  management system following ITIL standards
• New, High

• Key Metrics
• Milestones, if any applicable (may be none for
  some Service Activities)
• Produce project scope document
• Collect requirements
• Design and develop account management system
• Issues and Risks (specific to this activity,
  includes allocation impact)
• Development must be done in close cooperation
  with other organizations
• Priorities and resource allocations must be in
  sync

14
Project Activity Workflow Applications

• Goals Related to this Activity from Tactical
  Plan
• 1. Search and adopt one or more Workflow
  Management software tools
• New, High
• 2. Participate in development and support of new
  workflow applications, e.g.
• eTravel
• New Hire
• New, High
• 3. If necessary, migrate some existing
  applications to new framework(s)
• New, High

• Key Milestones
• Find and adopt Workflow Management tools
• Develop expertise in the tools
• Metrics, if any applicable (may be none for some
  Project Activities)
• Issues and Risks (specific to this activity,
  includes allocation impact)
• Set of software tools should cover wide range of
  relevant use cases
• The tools must well integrate into IT
  infrastructure (e.g. SharePoint)

15
Project Activity Effort Reporting and Budget
Input Conversion

• Goals Related to this Activity from Tactical
  Plan
• 1. Integration of Effort Reporting system with
  Fermilabs Time and Leave (FTL) system.
• New, High
• 2. Continue support of Effort Reporting and
  Budget Input processes
• Existing, High

• Key Milestones
• Re-design of the database to meet the
  requirements of integration with Fermilabs Time
  and Leave (FTL) system.
• Complete migration of the applications to Oracle
• Issues and Risks (specific to this activity,
  includes allocation impact)
• Conversion of Access-based application to Oracle
  is tedious and non-trivial task
• All project activities have to be closely
  coordinated with financials group which works
  according to well-defined and inflexible time
  table

16
Service Activity ESH Applications

• Goals Related to this Activity from Tactical
  Plan
• 1. Continue development and support of ESH
  applications
• Existing, Medium
• 2. Migrate applications to strong authentication
  methods (KCA, LDAP)
• Existing, High

• Key Metrics
• Application downtime
• Milestones, if any applicable (may be none for
  some Service Activities)
• Implementation of KCA or LDAP authentication
  mechanisms
• Issues and Risks (specific to this activity,
  includes allocation impact)
• Strong authentication methods have to be accepted
  by users

17
Service Activity MISCOMP Applications

• Goals Related to this Activity from Tactical
  Plan
• 1. Continue development and support of MISCOMP
  applications
• Existing, Medium
• 2. Implement ITIL structure components based on
  MISCOMP, e.g. Asset Management DB, etc.
• New, High
• 3. Implement strong authentication methods
• Existing, High

• Key Metrics
• Application downtime
• Milestones, if any applicable (may be none for
  some Service Activities)
• Implement Asset Management DB
• Implement strong authentication methods for
  MISCOMP applications
• Issues and Risks (specific to this activity,
  includes allocation impact)
• Support and users acceptance of strong
  authentication infrastructure

18
Service Activity DocDB

• Goals Related to this Activity from Tactical
  Plan
• 1. Continue support of DocDB software
• Existing, Medium

• Key Metrics
• Promptness of user support, bug fixes
• Issues and Risks (specific to this activity,
  includes allocation impact)
• Issue is that we are not authors of DocDB, and we
  are not really familiar with the code

19
Service Activity Content Management System

• Goals Related to this Activity from Tactical
  Plan
• 1. Find a replacement for Plone as a CMS
• New, High

• Key Metrics
• Milestones, if any applicable (may be none for
  some Service Activities)
• Search and propose CMS which would satisfy CD and
  Lab needs
• SharePoint seems to be very good candidate
• Issues and Risks (specific to this activity,
  includes allocation impact)
• CMS needs to integrate well into Lab and CD IT
  infrastructure

20
Service Activity InDiCo

• Goals Related to this Activity from Tactical
  Plan
• 1. Continue support of InDiCo in collaboration
  with CERN
• Existing, Medium

• Key Metrics
• Application downtimes, promptness of responses to
  user requests
• Issues and Risks (specific to this activity,
  includes allocation impact)
• Any bug fixes or new features have to be accepted
  by CERN

21
Service Activity SPMS

• Goals Related to this Activity from Tactical
  Plan
• 1. Continue support of SPMS
• Existing, Medium

• Key Metrics
• Application downtime, promptness of responses to
  user requests

22
Service Activity insert name(1 slide per
service activity in the Tactical Plan)

• Brief oral description to provide context.
• Goals Related to this Activity from Tactical
  Plan
• 1. Goal 1
• Identify if new or existing goal, and relative
  priority. Indicate status or priority in separate
  color/fonts.
• 2. Goal 2
• Identify if new or existing goal, and relative
  priority. Indicate status or priority in separate
  color/fonts.
• 3. Goal 3
• Identify if new or existing goal, and relative
  priority. Indicate status or priority in separate
  color/fonts.

• Key Metrics
• List metrics here
• What is it? (tickets clear per month, service
  uptime, service request response time,)
• Goal level planned vs actual. Impact high
  or low, felt by whom, if level not met
• URL of online presentation of metrics
• Milestones, if any applicable (may be none for
  some Service Activities)
• Issues and Risks (specific to this activity,
  includes allocation impact)
• List Issues and Risks

23
Project Activity insert name(1 slide per
project activity in the Tactical Plan)

• Brief oral description to provide context.
• Goals Related to this Activity from Tactical
  Plan
• 1. Goal 1
• Identify if new or existing goal, and relative
  priority. Indicate status or priority in separate
  color/fonts.
• 2. Goal 2
• Identify if new or existing goal, and relative
  priority. Indicate status or priority in separate
  color/fonts.
• 3. Goal 3
• Identify if new or existing goal, and relative
  priority. Indicate status or priority in separate
  color/fonts.

• Key Milestones
• List key milestones and associated deliverables
  here
• What is it? When planned vs actual.
  Impact high or low, felt by whom, if date not
  met.
• URL that shows project progress towards
  milestones
• Metrics, if any applicable (may be none for some
  Project Activities)
• Issues and Risks (specific to this activity,
  includes allocation impact)
• List Issues and Risks

24
FY09 Resource Request, Preliminary Allocation
25
Preliminary Allocation (explanation)

• ITIL Implementation
• Conferences, Work Shops, etc. 32000
• BMC Software Maintenance 53000
• Tel-Alert Annual Support 13552
• BMC ITSM Training 30000
• Workflow
• AgilePoint initial 85000
• Support 17000
• MISCOMP
• Decision One 36300
• Crystal Reports 21780
• Miscelleneous Software 44000
• Hardware replacement 25000

26
Impact of Preliminary Allocation

• Prelimib

27
Template Guidance (not part of the presentation)

• Activity Activity Level 1 or lower explicitly
  listed in Tactical Plan
• Activities have been classified in Tactical Plans
  as either being more Project-like or Service-like
• Projects finite defined lifetime, defined
  deliverable. Includes RD work.
• A.k.a Upgrades,
• Services same operation or task repeatedly.
• A.k.a. Operations, Maintenance, Support,
• Whether an activity is a project or service
  determines which format slide to use later.
• Terminology
• Obligation Budget Allocated budget. This may
  differ from the budget request.
• YTD Obligations Fully incurred expenses. Does
  not include RIPs, Req.s in CD, etc.
• Current FY08 Forecast Estimate of all
  obligations to be incurred by the end of FY08.
• MS Equipment Operating. Operating includes
  Travel, Material Purchases, Professional Services
  (contractors), Maintenance (licenses), and Other.
• RIP Requisitions in Progress