Your SlideShare is downloading. ×
0
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
OTIS Business Requirements Consultation Summary
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

OTIS Business Requirements Consultation Summary

740

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
740
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Business Requirements OTIS 2.0 SWIS/LSP/SSIL Coordinators Meeting July 15, 2009
  • 2. Agenda
    • Background
    • Project Scope
    • Business Requirements
  • 3. Background
    • Since the year 2000, the OTIS system has been the information system supporting the SWIS program. In the recent years, OTIS has expanded to support the information needs of the Library Settlement Partnerships (LSP) and Settlement Services in LINC classes (SSIL) programs.
    • In light of the expanded services that OTIS is supporting, OCASI has been given the opportunity to update OTIS to OTIS 2.0. The updated functions will build on the previous work completed on SSCAN, OTIS 2.0 Pilot and your business requirements.
  • 4. Background
    • As we look at what might be developed, we need your input
    • Today is about gathering your business needs. Please focus on how you manage and use information – not on technology
    • Don’t be constrained by exactly how things work today – but also know that not everything you ask for will be delivered!
    • As we finalize what is developed, we will be setting up Working Groups - we may be back to you to ask for further participation
  • 5. Project Scope
    • To improve the current OTIS system in a multi-year phased approach to meet the business requirements of the settlement sector.
      • Phase 1:
      • Launch OTIS 2.0 by March 2010 to the existing OTIS 1.0 client group
      • Includes:
        • Updated OTIS 1.0 interface
        • Add basic Client Management System features
        • Reporting Enhanced
  • 6. Project Scope
    • Future phases
    • Features that could be developed by March 2010 but turned on only when approved/deemed necessary:
      • Client Profile enhanced
      • Reporting at the user level: counts, profiles, mapping
    • Features that could be developed after March 2010:
      • Full capability of client management system i.e. referral, scheduling and action plan
      • Extractible client profile that supports referral
  • 7. Your Business Requirements
    • In March 2010 Phase 1 includes:
        • Updated OTIS 1.0
        • Add basic Client Management System features
    • To plan for this we need to know your business requirements…
  • 8. Your Business Requirements
    • What works well?
      • Available online
      • Application support (Elena)
      • Captures key information for funders– reporting can be inaccurate due to multi counting.
      • Maintains client confidentiality (does not capture client names)
      • Reporting at school level
      • Able to capture information for service date vs. entry date (but report is by one date only)
  • 9. Your Business Requirements
    • What does not work well?
      • Lack of reporting ability
        • Can not report workshops easily
        • Managers unable to see reports the system generates
        • Ability to extract information for narrative report (parallel to narrative report)
        • Unable to report/ differentiate on number of visits, clients or families
        • Unable to report on number of clients served vs. benefitted
      • No data fields to capture information on school activities i.e. assemblies, outreach programs.
      • Total client numbers do not tally up accurately, this leads to confusion/ inaccuracy in reporting
      • System does not support different business needs between the programs (SWIS/LSP/SSIL)
        • Information currently captured is too detail for LSP services
        • Family as the core concept is problematic for LSP services
  • 10. Your Business Requirements
    • What functionalities do you need in the system?
      • Capture the data that the funder requires for accountability, be cautious with the detail of data captured
      • Capture data to support evaluation and planning and allow managers to generate dynamic reports
      • Allow staff to generate their own reports
      • Provide detail explanation of what the reporting data/numbers represent. System should be user friendly for new staff.
      • Allow client identifier to be at the individual level
      • Support services when offered by multiple programs i.e. SWIS and LSP
      • Reduce redundant data entry for repeat clients and allow to view client history. This minimizes data entry and allows staff to spend more time with client.
      • Customize data fields to use program vocabulary and capture relevant program data.
      • Capture dates when data is updated – smart dates for validation
      • Better search features – able to create, save and re-run search criteria
      • Better data exports
      • Consider using free text fields
      • Sensible timeouts
  • 11. Your Business Requirements
    • What functionalities are in the system that you don’t need?
      • Data that is captured but not used in reporting i.e. streamline form
    • What would be cool but possibly out of the question?
      • Able to capture case management notes
      • Applying data archiving policies (record retention policy for 7 years)
  • 12. Your business requirements
    • What does “basic client management” mean to you?
      • Capture the service history at the individual level.
      • Able to relate the an individual to a family and the services delivered to the family.
      • Capture future actions / referrals
      • Capture how the client found out about the service
    • What does “basic reporting “ mean to you?
      • Generate reports to meet funder requirements
      • Generate reports that support program management / planning
      • Generate reports for stakeholders i.e. school principles, community partners etc.
      • Dynamically create reports at the agency, program, worker etc level

×