Presentation Template
Upcoming SlideShare
Loading in...5
×
 

Presentation Template

on

  • 724 views

 

Statistics

Views

Total Views
724
Views on SlideShare
724
Embed Views
0

Actions

Likes
0
Downloads
7
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Convergence: EMC->Documentum, IBM->FileNet, Oracle->Stellent Consolidation: OpenText->Artesia (DAM), IXOS (BPM), Hummingbird->Red Dot
  • Salesforce.com acquired Koral, a CM vendor “ Content-centric” is Forrester’s description for transactional, business and persuasive content

Presentation Template Presentation Template Presentation Transcript

  • 2007 OCITA <<Technology Are>> Domain Team Meeting 1 Insert Date Here
  • Welcome <<Insert Executive Sponsor Name Here>> <<Insert Executive Sponsor Title Here>>
  • Introductions
    • Name
    • Organization and role
    • Favorite vacation destination?
      • <<Or other icebreaker question>>
  • Purpose and Objectives Today’s Meeting
    • Purpose
      • Understand <<insert technology here>> market
    • Objectives
      • Understand Domain Team process
      • Discuss the <<insert technology here>> functionality
      • Review analyst perspectives on the current state of the market
      • Review RFI process
  • Agenda
    • 1:00-1:20 Introductions
    • 1:20-1:50 Domain Team Process Overview
    • 1:50-2:10 What is <<insert technology here>> ?
    • 2:10-2:25 Break
    • 2:25-3:00 State of the Industry
    • 3:00-3:30 RFI Process
    • 3:30-4:00 Close
  • Ground Rules
    • Be on time
    • Be objective, constructive and open-minded
      • No technology “religious wars”
    • Respect others’ viewpoints
    • Decisions are made according to the 70% solution rule
  • Logistics
    • NIH Portal
      • <<Insert hyperlink here>>
    • Enterprise Architecture Website
      • http://enterprisearchitecture.nih.gov/
    • Email
      • [email_address]
    NIH OCITA Liaison: Ms. Helen Schmitz Domain Team Liaison: <<Insert domain team POC Name>> Email: <<Insert domain team POC Email>> Phone: <<Insert domain team POC Phone #>>
    • Subscribe to the EA LISTSERV:
      • http://list.nih.gov/archives/enterprise_architecture.html
    • Industry analysts:
      • Forrester – http://www.forrester.com
      • Gartner – http://www.gartner.com
      • <<insert other relevant industry analysts here>>
  • Domain Team Process Overview
  • Technology Architecture consists of…
    • Patterns
      • Design ideas that can be reused and leveraged across NIH.
      • http://enterprisearchitecture.nih.gov/ArchLib/Guide/WhatIsPattern.htm
    • Bricks
      • NIH standards that specify products, technologies, or protocols in use or planned, as well as those earmarked to be retired or contained.
      • http://enterprisearchitecture.nih.gov/ArchLib/Guide/WhatIsBrick.htm
  • Domain Teams
    • Temporary working group comprised of IC representatives
    • Established to develop enterprise architecture artifacts within a specific domain of the NIH Enterprise Architecture
    • Ensures cross-NIH representation, consensus, and alignment with Federal acquisition and procurement requirements, such as the Federal Acquisitions Regulations (FAR)
  • Domain Team Activities
  • Why Are We Conducting This Domain Team?
    • <<Insert reasons for conducting this domain team here>>
  • 2007 <<Insert technology here>> Domain Team Roadmap Meeting 2 Objectives: Update RFI Prioritization of Evaluation Criteria Meeting 2 06/07/07 3D12 Meeting 4 Objectives: Analysis of RFI Analysis of Bricks - Review and Iterate Meeting 4 06/28/07 3D12 Meeting 5 Objectives: Conclusion - Overview of Work Done to Date Review executive presentation Meeting 5 TBD TBD Kickoff (2hrs): Introductions Overview of Enterprise Architecture Meeting 1 Objectives: State of Industry Overview Review Independent Research Meeting 1 05/31/07 3D12 Meeting 3 Objectives: Patterns - Review and Iterate Current <<insert technology here>> Patterns Meeting 3 06/14/07 3D12 Homework: Review Current <<insert technology here>> Service Pattern Homework: Review Current <<insert technology here>> Brick Homework: Review RFI Update dates and room numbers Identify Need for Standard Establish Domain Team Conduct Domain Team Run Approval Process Publicize Results
  • Context Setting - What is <<insert technology here>>? The next five or six slides should be used to introduce the technology that is under investigation, including the major functional components of the technology and the business value that may be derived from its use.
  • Background and Definitions
    • Insert background and definition information
  • Why do we need <insert technology name>?
    • Describe the NIH business case for this technology
  • Why do we need <insert technology name>?
    • Describe the component parts or technologies of this technology area
  • Break
  • Context Setting - State of the Industry The next five or six slides should be used to explain the technology market for the technology being investigated. It should include the history of the market, the evolution of the market to today, and both current and future market trends.
  • Evolution of the Market Document Management
    • <Technolog> has existed as a market for over ## years
    • Technology solutions to meet this need have historically gelled around different types of software markets:
  • Current Market Trends
    • With this many product segments, the <technology> market is _____________
    • Many vendors are rapidly including functionality traditionally associated with other product segments
    • Analysts see the following market trends:
      • Market trend
      • Market trend
  • Current Market/Technology Challenges and Limitations
  • Future Market Trends
  • Summary
  • RFI Review
  • Request for Information (RFI)
    • Definition
    • An RFI is a request to a potential seller/service provider to:
      • Determine what products and services are available in the marketplace
      • Know the capability and strengths of a seller in terms of offerings
      • An RFI is NOT an invitation to bid and is not binding
    • Why Issue an RFI?
    • To broaden the potential sources of information for developing recommendations
    • To understand data beyond the technologies, i.e. pricing models, contract vehicles
  • RFI Process Domain team defines and weighs decision criteria Evaluated responses are used as an input to recommen-dations Responses are evaluated using decision criteria Domain team finalizes RFI Draft RFI is written RFI is released Draft RFI is written
  • Homework
    • RFI consists of two documents:
      • Microsoft Word document outlining how to respond to the RFI
      • Excel spreadsheet containing functional and technical self-evaluation criteria
    • Download and review both in preparation for next week
      • The RFI will be on the portal for download on Date .
    • Sign the Conflict of Interest Statement
  • Domain Team Roadmap Meeting 2 Objectives: Update RFI Prioritization of Evaluation Criteria Meeting 2 06/07/07 3D12 Meeting 4 Objectives: Analysis of RFI Analysis of Bricks - Review and Iterate Meeting 4 06/28/07 3D12 Meeting 5 Objectives: Conclusion - Overview of Work Done to Date Review executive presentation Meeting 5 TBD TBD Kickoff (2hrs): Introductions Overview of Enterprise Architecture Meeting 1 Objectives: State of Industry Overview Review Independent Research Meeting 1 05/31/07 3D12 Meeting 3 Objectives: Patterns - Review and Iterate Current <<insert technology here>> Patterns Meeting 3 06/14/07 3D12 Homework: Review Current <<insert technology here>> Service Pattern Homework: Review Current <<insert technology here>> Brick Homework: Review RFI Identify Need for Standard Establish Domain Team Conduct Domain Team Run Approval Process Publicize Results
  • Next Steps
    • Send email containing portal hyperlink <<owner>> <<due date>>
    • Post draft RFI to portal <<owner>> <<due date>>
    • Download draft RFI for review <<owner>> <<due date>>
    • Post comments to portal <<owner>> <<due date>>
  • Thank you.
  • Backup Slides