1 / 15

VIPR Overview

VIPR Overview. September 2008. Automate Pre-Season Instruments Across the Business Lifecycle. Generate Priority List. Evaluate. Prepare. Solicit. Inspect. Award. Dispatch. Contract Admin. Evaluate. Pay. Report. Close. For Best Value. Performance. IBS. Mods.

jonesw
Download Presentation

VIPR Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VIPR Overview September 2008

  2. Automate Pre-Season Instruments Across the Business Lifecycle Generate Priority List Evaluate Prepare Solicit Inspect Award Dispatch Contract Admin Evaluate Pay Report Close For Best Value Performance IBS Mods Electronic Data Flow Scope: • An Acquisition Management System (not Fire Ops or Finance) • All preseason incident procurement instruments • All aviation contracts paid on an FS-6500-122 (not end product) • Not: incident sign-ups, cooperator / land use agreements

  3. Incident Business Solutions (IBS) ISuite VIPR ROSS IBDB at the ASC FFIS Pre-season Solicitations & Awards Dispatch resources at incidents Manage Incident Resources Payment Work Process Make Payments ESB Priority Dispatch Table ABS DOI Payment Processes Aircraft contracts Payment for Aircraft

  4. USDA FS NPS BIA USFWS DOI FEMA NASF VIPR Stakeholder Community Todd Repass Washington, DC Hallie Locklear, BLMBoise, ID Glenn Haggstrom Washington, DC DeputyS&PF DeputyBus Ops Julie Whaley, BLMBoise, ID CFO CIO Jim Hubbard Washington, DC Jesse KingWashington, DC Vaughn Stokes Washington, DC Hank KashdanWashington, DC Matt DeLong, DOI/AMDBoise, ID Tom Harbour Washington, DC Barb Loving, DOI/OWFCWashington, DC FinanceOperations Finance Systems Security EGov BAO AQM FAMInteragencyNIFC Doug NashArlington, VA John KingArlington, VA Tah YangArlington, VA Ron Hooper Arlington, VA Karren Alexander Arlington, VA Donna Carmical Albuquerque, NM Karyn WoodBoise, ID Ken Adee Portland, OR Cliff Berg Arlington, VA Mike Grube Asheville, NC Tanya Sharratt Vancouver, WA Neal Hitchcock Boise, ID Craig Kirby Ogden, UT Jim Damato Arlington, VA Leigh Armstrong Albuquerque, NM ASC Incident Finance Mary Szymoniak Boise, ID Formatta Chris Glover Atlanta, GA Jeff Park Albuquerque, NM Cheryl MolisBoise, ID Marylea Lockard Albuquerque, NM Policy &System Operations Laurie LewandowskiArlington, VA Ron Wester Arlington, VA NICC AQM NIFC SystemsBranch Policy Branch Chuck Wamack, BLMBoise, ID NWCG FESSAA Larry Bowser Fort Collins, CO Sue PrentissBoise, ID Byron Brown Arlington, VA Cheryl EmchEugene, OR Ron Schilz Missoula, MT FEWT Sarah Clore Arlington, VA ROSS EaTIS Jon Skeels Golden, CO Laurie Sonju Missoula, MT Terry Kiele Fort Collins, CO Contract EquipmentTask Group Susan Shirts Golden, CO Shane LaValley Missoula, MT VIPR Dick Reynolds Clovis, CA Laura SmyrlFort Collins, CO

  5. AQM Systems 3 Year Plan EERA Database Use of EaTIS in R1, R5, R6 CBA Tool for Non-EaTIS Regions November 2008:Deploy VIPR 1.0 Development of VIPR Version 1.0 VIPR 1.0Change Control Board VIPR-ROSS Integration:Timeline is proposed, not confirmed Dispatch Feasibility Study • Address Deferred Requirements: • Aviation • National Contracts • DOI / BLM Use of EAV until VIPR delivers aviation functionality

  6. VIPR Progress: Requirements Review and Approval Mid-Mgt Review & Briefing to Senior Mgt AQM FESSAA Team StakeholderCommunities Expert SMEs 2007 2008 Aviation Contracting Officers NationalContractsTeam (NIFC) Finance Dispatch Equipment ContractingOfficers Inspectors &PerformanceEvaluators Joint Application Development Sessions: Validation & Development

  7. VIPR Plan: Design and Development Project Management • IRB Approved • Charter Signed Initial Risk Analysis (C&A) OMB-300 VIPR Design Team Assembled Application Hosting Environment SecureCAP 2007 2008 2009 Sprint 1 Admin Module Sprint 5VendorModule Sprint 3 COModule Sprint 7 Sprint 9 Sprint 4 COModule Sprint 6 Sprint 8 Sprint 2 Admin Module VIPR Dev TeamDesign/Development

  8. VIPR Plan: Prepare to Go Live Assess for Success FinalGo/No GoAssessment Go/No GoAssessment Go/No GoAssessment Go/No GoAssessment Help DeskTraining 2008 EaTIS Offline FinalIntegrationTesting Beta Testing Data Migration into VIPR Testing

  9. VIPR 1.0 Go / No Go September

  10. VIPR Go / No Go August

  11. VIPR Proposed Plan: Deployment and Training Buffer Week: Allow for delays, issues System Live Nationwide Regions 3, 8, 9 Regions 1, 5, 6 Regions 2, 4 Internal Training Holiday Break 2008 2009 Regions 8, 9 Region 1 Region 2 Region 4 Region 5 Region 3 Usage Region 6 Vendors in regions with open solicitations

  12. Requirements Delivery and Traceability • Design Collateral (Use Cases, Screen Prototypes) • Development Collateral (Class Diagrams, Data Models) • Test Collateral (Test Plans, Successful Test Reports) Business Requirement 1 Feature 1 Set of working functionality Sprint 1 Design Develop Test Feature 2 Business Requirement 2 Feature 3 Non-Critical Defects and Enhancement Requests: Logged and will be done in some future Sprint Critical Defects Feature 4 Business Requirement 3 • Design Collateral (Use Cases, Screen Prototypes) • Development Collateral (Class Diagrams, Data Models) • Test Collateral (Test Plans, Successful Test Reports) Feature 5 Sprint 2 Design Develop Test Set of working functionality Response to Changing Business Need

  13. Waterfall vs. Agile: Deliver! Waterfall Agile Design Develop Test Deliver Design Develop Test Working functionality Sprint 1 Working functionality Sprint 2 Working functionality Sprint 3 Deliver All functionality delivered at one time • Business sees the working functionality for everything at one time—no opportunity for input throughout project life cycle • If issues during development or test, go back to Design phase—requires a lot of rework • Will have working functionality at end of each Sprint • Multiple releases of working software ensures collaboration with the Business throughout the project life cycle • If issues during development or test, can address in future Sprint

  14. VIPR Architecture

  15. Need more information? • VIPR Websites Internal: http://fsweb.wo.fs.fed.us/aqm/vipr/ Public: http://www.fs.fed.us/business/incident/vipr.php • Larry Bowser, Executive Project Manager lbowser@fs.fed.us • Laura Smyrl, Project Manager lsmyrl@fs.fed.us

More Related