1. Attachment O Enterprise Architecture Solution AssessmentContact Info & Purpose (vendor version) The purpose of the EA Solution Assessment is to document architectural details of proposed IT solutions in order to determine compatibility with the overall SOM architecture. MDIT/SOM activities which require an Assessment include: the purchase of new licenses, contracting for software development services, purchase of new software components, installation of new software components, the purchase of new hardware components or the use of MDIT staff resources on any project beyond the design phase. All vendor proposals and new contracts must be accompanied by an Assessment, documenting the architectural details of the proposed solution. Vendor should complete all areas except where indicated. Vendor Version 2.2 Solution/Project NameData Warehouse Platform RFP Name/Number Date Submitted Vendor Name Vendor City and State Vendor Phone No. Vendor eMail Replacement, including installation and implementation, of a A brief description of the replacement for the States current data warehouse (to include proposed solution andthe hardware platform, system operating software, system business purpose/process. (please keep the description maintenance, and migration services). Migration services from brief) the existing platform to the new platform. Maintenance for thenew platform. Additional description of the solution and business purpose. (please expand the row as much as needed)Page 1 of 11 EASA (vendor) version 2.2

2. Attachment OSelectEnterprise Architecture Solution Assessment all thatArchitecture Overview (vendor version)apply Vendor: the technologies listed below are standards used by the State of Michigan.(vendor Utilization of existing technology for new solutions is encouraged. Check the left column if complete)the technology can be used with the solution being proposed. Add comments as needed. 1Server/Application Hosting CommentsInternally HostedExternally HostedInternally & Externally Hosted 2User Interface TypeComments (e.g. version or release)BrowserCitrixClientMobile BrowserMobile ClientTerminalOther (explain =>) 3Supported Browsers (internet)CommentsInternet Explorer 6.x (intranet)Firefox 3.0.x (internet)Chrome 3.0 (internet)Safari 4.x (internet)Other (explain =>) 4Data Exchange InterfaceComments (e.g. version or release)EDI (industry protocol)Flat File (private protocol)Web ServiceXMLOther (explain =>) 5System AccessCommentsInternal (SOM)External (public)External (authorized)Mixed (internal-external) 6User AccessCommentsInternetIntranetLocal Government (LGNet)Public facing internetKiosk terminalVendor NetVPNOther (explain =>) (continued) Page 2 of 11EASA (vendor) version 2.2 3. Attachment OSelectEnterprise Architecture Solution Assessment all that Architecture Overview (continued)apply Vendor: the technologies listed below are standards used by the State of Michigan.(vendor Utilization of existing technology for new solutions is encouraged. Check the left column if complete)the technology can be used with the solution being proposed. Add comments as needed. 7Data Classification CommentsNon-sensitiveSensitive w/ personal ID infoSensitive w/ no personal ID infoNot classifiedOther (explain =>) 8PCI-DSS Compliance Needed?CommentsYesNo 9Data Audit Trail Implementation CommentsApplication CodeDatabase Audit FilesDatabase TriggersStored ProceduresOther (explain =>)10IT Services (Centers of Excellence) Commentsx86 VirtualizationAddress VerificationBusiness Objects ReportingExtract Transform Load (ETL)Citrix Virtualization11Enterprise Data Storage CommentsSANCAS / NASInternal DiskOther (explain =>)12Database (RDBMS)CommentsMS SQL Server 2008MySQL 5.1Oracle 11gTeraData A28V2R6.2 / 12.0Other (explain =>) (continued) Page 3 of 11EASA (vendor) version 2.2 4. Attachment OSelectEnterprise Architecture Solution Assessment all that Architecture Overview (continued)apply Vendor: the technologies listed below are standards used by the State of Michigan.(vendor Utilization of existing technology for new solutions is encouraged. Check the left column if complete)the technology can be used with the solution being proposed. Add comments as needed.13Database Modeling Tools CommentsErwin 7.xMSSQL Server Mgmt Studio (match db)MySQL Workbench (match db)Oracle Designer (match db)TeraData Utilities (match db)Other (explain =>)14Development Framework Comments.NET Framework 3.5Java J2EE 5.xOther (explain =>)15Development PlatformCommentsEclipse 3.xHibernate 3.xIBM Websphere Integration Developer 6.xMicrosoft SilverLight Expression 2.xMicrosoft Visual Studio 2008Oracle JDeveloper 11gSpring 2.5Struts 2.xXML Spy 2009Other (explain =>)16Development LanguageCommentsASP .NETCSS Level 2Microsoft C#Microsoft VB.NetJavaJavaScriptJDK 6.xPHP 5.2Other (explain =>) (continued) Page 4 of 11EASA (vendor) version 2.2 5. Attachment OSelectEnterprise Architecture Solution Assessment all that Architecture Overview (continued)apply Vendor: the technologies listed below are standards used by the State of Michigan.(vendor Utilization of existing technology for new solutions is encouraged. Check the left column if complete)the technology can be used with the solution being proposed. Add comments as needed.17Markup languagesCommentsHTML 4.xXML Schema 1.1XSLT 2.0XHTML 2.018Presentation (Web) Server CommentsApache HTTPD 2.2.xIBM Websphere IHS 6.1Microsoft IIS 7.0Other (explain =>)19Application ServerComments.NET Framework 3.5IBM WebSphere 6.1JBoss 5.xOracle C4JOther (Explain)20HW Platform CommentsDellHPIBMSunx86 VirtualizationOther (explain =>)21Server OS CommentsLinux Redhat Enterprise Server 5.xLinux SUSE Enterprise 10.xMicrosoft Windows 2008Unix HPUX 11i v3Unix Sun Solaris 10.xVMWare vSphere 4Other (explain =>) (continued) Page 5 of 11EASA (vendor) version 2.2 6. Attachment OSelectEnterprise Architecture Solution Assessment all that Architecture Overview (continued)apply Vendor: the technologies listed below are standards used by the State of Michigan.(vendor Utilization of existing technology for new solutions is encouraged. Check the left column if complete)the technology can be used with the solution being proposed. Add comments as needed.22Document Management CommentsEMC Documentum 6.5FileNet Content Services 5.4FileNet Document Mgmt P8HP TrimPaperPort 10MS SharePoint Server 2007 EEOther (explain =>)23Centralized PrintingCommentsDMB consolidated print centerOther (explain =>)24Testing Tools CommentsJunit 4.xLoadRunner 9.xMicrosoft Team Foundation SystemQuick Test Pro 10.xSelenium 1.xOther (explain =>)25Identity Management (network) CommentsActive Directory 2008Other (explain =>)26Identity Management (application) CommentsIBM TivoliNovell e-Dir 8.8.xOther (explain =>)27Project ManagementCommentsClarity 12.0MS Project 2007Other (explain =>) (continued) Page 6 of 11EASA (vendor) version 2.2 7. Attachment OSelectEnterprise Architecture Solution Assessment all that Architecture Overview (continued)apply Vendor: the technologies listed below are standards used by the State of Michigan.(vendor Utilization of existing technology for new solutions is encouraged. Check the left column if complete)the technology can be used with the solution being proposed. Add comments as needed.28Requirements GatheringCommentsCompuware Optimal Trace 5.xMicrosoft OfficeMicrosoft VisioSUITE/SEM templatesRational Requisit Pro 7.1Serena Dimensions 2009 R1.xOther (explain =>)29Design ToolsCommentsMicrosoft VisioMSSQL Server Mgmt Studio (match db)Rational Rose 7.0Serena Prototype Composer 2009 R1.xOther (explain =>)30Version Control CommentsMicrosoft Team Foundation SystemSerena Dimensions (PVCS Mgr) 2009 R1.xSubversion 1.6Other (explain =>)31Message Queuing CommentsApache Active MQ 5.3IBM Websphere MQ 6.x, 7.xOther (explain =>)32Business IntegrationCommentsJBoss SOA 4.3Websphere Message Broker 6.x, 7.xOther (explain =>) (continued) Page 7 of 11EASA (vendor) version 2.2 8. Attachment OSelectEnterprise Architecture Solution Assessment all that Architecture Overview (continued)apply Vendor: the technologies listed below are standards used by the State of Michigan.(vendor Utilization of existing technology for new solutions is encouraged. Check the left column if complete)the technology can be used with the solution being proposed. Add comments as needed.33Database ToolsCommentsDBArtisan 8.6Infosphere Information Svr v8.1MSSQL Server Mgmt Studio (match db)MySQL Workbench (match db)Oracle Developer Suite (match db)Oracle Enterprise Manager (match db)Oracle SQL Developer (match db)TeraData Utilities (match db)Other (explain =>)34Reporting Tools CommentsActivePDF 2009ActiveReports 4.0Crystal Reports XI R2, 2008Crystal Xcelsius 2008Crystal Reports for Eclipse 2.xMSSQL Reporting Services (match db)Oracle Reports (match db)Other (explain =>)35End-User ToolsCommentsBusiness Objects (BO) XI R2, 3.xOracle Discoverer (match db)Other (explain =>)36Deployment ToolsCommentsMicrosoft Team Foundation System 2008Serena Dimensions CM Mover 2009, 2.3Other (explain =>) (continued) Page 8 of 11EASA (vendor) version 2.2 9. Attachment OSelectEnterprise Architecture Solution Assessment all that Architecture Overview (continued)apply Vendor: the technologies listed below are standards used by the State of Michigan.(vendor Utilization of existing technology for new solutions is encouraged. Check the left column if complete)the technology can be used with the solution being proposed. Add comments as needed.37Build Tools CommentsApache Ant 1.7.1Apache Maven 2.1.xMicrosoft Team Foundation System 2008Serena Dimensions CM Builder 2009 R1.xOther (explain =>)38Job SchedulersCommentsBL/Sched 5.2Tidal Enterprise Scheduler 5.3.1 & 6.0UC4 Global 5.0UC4 Op Mgr 6.0 & 8.0Other (explain =>)39GIS TechnologiesCommentsArcIMS 9.3ArcGIS Server 9.3ArcSDE 9.3Erdas ADE Rel. 2ER Mapper Image Server 7.2Oracle Spatial (match db)Oracle MapView (match db)Other (explain =>)40Issue & Defect Tracking CommentsBugzilla 3.2.5 & 3.4.2Clear Quest Chg Mgmt Suite 7.5Microsoft Team Foundation System 2008Serena Mashup Composer 2009 R1.xOther (describe =>) Page 9 of 11EASA (vendor) version 2.2 10. Attachment OEnterprise Architecture Solution AssessmentDisaster Planning (Section to be completed by SOM) Business continuity requirements. Describe below The business requirement(s) that determine the amount of time and the operational availability of the application to the end-user. Select Availability Requirement Category Availability Requirement is divided into three Only different levels. These levels define the continuous service availability requirements of Onethe application. Based on the following definitions, please indicate the level of (1)availability required for this Business Function / Application.Urgent - Business Function / Application outage has potential to cause loss of life or risk ofinjury to a citizen. 99.99% availability (