1	Successful Systems Integration: What Does It Take? Three Forks, LLC
2	Overview What is integration? How do I determine my integration needs? What are the parts to a successful integration plan (Design, Testing & Tech Jargon)? Production & pratfalls Updates & maintenance Closing thoughts & questions
3	What is Integration? Good Question! Integration is the intelligent exchange of information in a managed manner between distinct systems Successful integration involves designing distinct interfaces to exchange data through precisely defined tools and consistent interfaces
4	What is an Interface? One or more processes that allow you to move information (data) from one system to another The complete package of one or more tools that allow a distinct set of data to to be moved between databases
5	What are the parts of an interface? Data Export Data Conversion / Transformation Data Transfer Data Import Error Checking / Correction
6	Example: What types of interfaces might you want to use with PowerFAIDS?
7	Designing your interfaces How do I make a plan to get what I want? One size doesn’t fit everyone There isn’t one single update that will just make it so Think automation early!
8	Big Picture / Little Picture Define the information you need Where is it stored? When do you need it? How often must this information be updated? How will you detect errors: …within the data? …within the process? Create a list of elements Annotate list: where the data resides Annotate list: how often the data needs to be updated Group elements by systems by frequency of update Annotate list: elements requiring conversion
9	Sample Interface Schema/Map
10	Resources for Interface Planning and Design System User Manuals Key words: Import, Export, Data Exchange, Interfaces, Integration Vendor Technical Support Resources Listservs Colleagues who have been there, done that Non-vendor-supplied export methods: Microsoft Access, other SQL compliant tools, ODBC interfaces Systems consultants (Three Forks)
11	Successful Interface Planning Discussion phase where ideas are exchanged Planning phase where a draft plan is created Review / comment stage where all of the interested parties provide input Development phase Testing phase Production phase Review and maintenance phase
12	Making the Plan Draft in detail Draw pictures! Pictures often ask leading questions
13	Making the Plan Formal Create a project outline that includes all of the steps that must be completed Add time dimensions to the outline Create an Executive Summary Know the costs Prepare to revise!
14	Making the Plan Useful Draft in detail! What elements of data do you need? What types of data are they? How can the data be grouped together? How often must the data be updated? What parts of this process can be automated? What are the automation options? Who will ensure that the process is running? To whom should the errors be reported?
15	Making the Plan - Terminology Information Terminology Batch Process / Interactive Scheduled Job Transaction / Overlay Web Services Streaming Data
16	A Little About Testing… Errors Happen! Testing is the process of ensuring that what you want to happen, happens more often than not. And when errors do happen, you know about it right away!
17	Testing Plans A well designed testing plan does two things: Ensures that the interface process will do what is expected when provided with proper input Trap all known errors and deviations from the anticipated user behavior Testing has two stages and a feedback loop The developer tests his/her code to ensure that given good input, you get well formatted output The end user tests to ensure usability, and “real world” practical use (acceptance testing) At each stage, comments regarding problems should be fed back to the developer(s) for reprogramming and retesting
18	Error Messages Well written error messages have two parts: Convey to the end-user that an error occurred and the severity of the error. Convey to the developer when, where and within what process the error occurred, for resolution
19	Models Financial Aid Interfaces to Other Campus Systems
20	Production Going live – what does that mean? Are we there yet? Another item to write…procedures It’s good if the developer will draft them… It’s very good if the end user spends half-day writing very detailed procedures
21	Updates & Maintenance In a perfect world… Plan for change Have an annual review Involve your IT staff Review all systems release notes for potential impact on interfaces Determine a maintenance schedule
22	Closing Thoughts Tips Start small Don’t try to develop interfaces that “do everything” Refer to manuals Ask your peers what has worked for them Provide reasonable time for design and testing Review progress early in production, and correct problems – DON’T LIVE WITH THEM! Plan for changes, enhancements and updates
23	Closing Thoughts Questions? Contact Information Stephen Peterson ThreeForks, LLC P O Box 182, Whitehall, MT 59759 speterson@threeforks.com (303) 378-1070