Technical Standards Profile -20100721 - BidNet



Technical Standards Profile

Enterprise Architecture Office Standards

|Document Status: |APPROVED |

|Document Author: |Michael Birmingham |

|EAO Approver: |Mark Delaplane |

|CIO: |Bob Lanouette |

|Version |8.0 |

|Publish Date |5/3/2017 |

Table of Contents

TECHNICAL STANDARDS PROFILE 3

APPLICATIONS 4

Workgroup Computing 15

DATA / DBMS 19

ELECTRONIC COMMERCE 21

HARDWARE PLATFORMS 23

Mobile Computing 27

INFRASTRUCTURE 28

INTEGRATION (EAI) 35

SECURITY 38

SYSTEMS MANAGEMENT 43

WIRELESS 49

Assistive Technologies 50

TECHNICAL STANDARDS PROFILE

Revised: 10/29/2012

|Definitions |

|Current (0-12 months) |

|Target (12-24 months) |

|Emerging (24-48 months) |

| |

|Standard: |

|Currently approved protocol, product or service.  Assures the best alignment with agency direction and architecture and |

|provides the most efficient use of agency resources. |

|The agency has set a target to migrate to these technologies within the Tactical planning time frame, i.e. 12-24 months.  If a |

|technology is listed in this category, then an approved migration plan is in place. Once implemented, items in this category |

|will shift to the "Current" column. |

|New projects may be able to use these technologies if migration plans coincide with project plans. Seek EAO guidance before |

|making a commitment to using these technologies. |

|These are the emerging trends, products, services or strategies that the agency expects to emerge as viable technologies within|

|the Strategic planning horizon, i.e. 24-48 months. However, because these are generally immature technologies, their status is|

|not certain and they may prove unacceptable for further investment. |

| |

|These may be good candidates for R&D or non-production prototypes, but DO NOT plan to incorporate these technologies into |

|production systems. Any use of these technologies, even for R&D purposes, requires EAO approval. |

| |

|Exception: |

|An acceptable alternative to the standard under certain conditions.  EAO approval is required before acquisition or use. |

| |

| |

| |

|Contain: |

|A product or service currently in use but may be replaced in the near future.  Should not be used for new system development. |

|Any investments beyond routine maintenance must be approved by the EAO. |

| |

| |

| |

|Retire: |

|Technology identified for replacement. No further investments will be approved. |

| |

| |

| |

|Strategy: |

|Strategies, guidelines and best practices that provide further guidance for the appropriate use of the technology. |

| |

| |

APPLICATIONS

|Data Exchange | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |FTP and SFTP (Tumble Weed) | | |

| |IBM Integration Bus | | |

| |IBM Data Power Gateway | | |

| |IBM Business Process Management | | |

| |WSFTP | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |XML is widely embraced as the industry standard. L&I has adopted XML for data and content interchange and |

| |will implement this standard for all new systems. |

|Client Interface - Browser (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Primary Browser (W10): | | |

| |Microsoft IE 11 | | |

| |Secondary Browsers (W10): | | |

| |Google Chrome | | |

| |Microsoft Edge | | |

| |Companion Device (iOS): | | |

| |Safari | | |

|Exception: |Windows Forms Applications | | |

| |FireFox | | |

|Contain: | | | |

|Retire: |MS IE 6 | | |

| |MS IE 8 | | |

| |MS IE 9 | | |

| |MS IE 10 | | |

|Strategy: |Internally, application interfaces are standardized across the agency using adaptive designs around |

| |HTML5 and CSS3. Applications are written to a browser interface and are as vendor independent as |

| |possible. Browser-based client is preferred but Windows Client (Win32) are acceptable in accordance |

| |with the Enterprise Application Non-Functional Requirements Checklist. |

| | |

| |Externally, applications are written to a browser interface and are as vendor independent as possible. |

| |Applications are tested with browser version listed in the Web Presentation Standards. |

| | |

| |For supported agency browser clients, standardize on at least two different browsers. The primary |

| |browser will support all legacy applications as a priority and newly developed applications, if |

| |possible. The secondary browsers will support all newly developed applications as a priority and |

| |legacy applications, if possible. |

| | |

| |Currently, Internet Explorer 11 is the agency’s primary browser until legacy dependencies within in |

| |applications are refactored. Google Chrome and Microsoft Edge are secondary browsers. Safari is the |

| |standard browser for iOS devices. |

|Business Tier Languages |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |COBOL (mainframe) | | |

| |Natural (mainframe) | | |

| |C# | | |

| |Java 1.8 | | |

|Exception: | | | |

|Contain: |Visual Basic | | |

| |Java 1.6 | | |

| |Java 1.7 | | |

|Retire: |Delphi | | |

|Strategy |Standardize the development environment to take advantage of reusable code, leverage developer skills, |

| |and minimize support and training expenses. New web application projects (starting in July 2015) are to |

| |use C# as primary development language for .NET Applications. |

|Application Frameworks (AppDev & Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |.NET Framework 4.5.2 |.NET Framework 4.6 |.NET Framework 4.6.1 |

| |Java 1.8 | | |

|Exception: | | | |

|Contain: |.NET Framework 4.5 | | |

| |NET Framework 3.5, 4.0 | | |

| |Java 1.6 | | |

| |Java 1.7 | | |

|Retire: |NET Framework 2.0 | | |

|Strategy |Distributed Application Framework Development is standardized around the Microsoft .NET Framework and |

| |Java which is managed code programming model for building applications on Windows clients, servers, and |

| |mobile or embedded devices. |

|Web-centric Applications |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |.NET Framework 4.5.2 |Java 1.8 |.NET Framework 4.6.1 |

| |Enterprise Library |.NET Framework 4.6 | |

| | | | |

| |HTML5 | | |

| |CSS3 | | |

| |XML | | |

| |JavaScript | | |

| |ADA accessibility | | |

| |Web Facing Service - Internal(see strategy | | |

| |below) | | |

|Exception: | | | |

|Contain: |.NET Framework 4.5 | | |

| |XHTML 1.0 transitional | | |

| |CGI | | |

| |COM / COM+ | | |

| |ISAPI | | |

| |Java 1.6 | | |

| |Java 1.7 | | |

| |VBScript (server side) | | |

| |ActiveX (server side) | | |

|Retire: | | | |

|Strategy |Write applications to work with all agency supported browsers and to comply with ADA accessibility rules|

| |identified in the Web Presentation Standards. |

| | |

| |Keep external applications as thin as possible with a minimal amount of client-side processing. |

| |Client-side scripting can be used to enhance the end-user’s experience and performance, i.e. client-side|

| |caching. However, if the end-user has disabled the browser script function, the application’s essential|

| |functions must continue to operate or gracefully notify the user of an alternative method of completing |

| |the action. |

| | |

| |Java applets and plug-ins are strongly discouraged and client-side ActiveX is prohibited on external |

| |apps. Do not require external clients to download or install helper apps or other executable code |

| |beyond what is commonly available and supported by third-parties, e.g. Adobe Acrobat Reader. Pure HTML |

| |is the safest; Cascading Style Sheets should be used and should be thoroughly tested with all targeted |

| |browsers and the W3C CSS Validator. Business logic should be written as .NET assemblies. Business logic|

| |should not be coded in ASP script or SQL Stored Procedures. |

|Web User Interface Design |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |MS Visual Studio .NET 2013 Ultimate |Visual Studio 2015 |Visual Studio "15" |

| |Edition | | |

| |WebSphere Portal Server Framework | | |

| |Adobe Dreamweaver CS5 | | |

| |MS Expression Web 4.0 | | |

| |WS-RP 2.0 Portlets | | |

| |JSR-286 Portlets | | |

|Exception: | | | |

|Contain: |MS Visual Studio .NET 2008 and 2012 | | |

| |Ultimate Edition | | |

| |Dreamweaver MX 2004 (Internet) | | |

| |Contribute 2.0 (Internet) | | |

| |Adobe Dreamweaver CS4 | | |

|Retire: |JSR-168 Portlets | | |

|Strategy |Standardize the development environment to take advantage of reusable models and templates, leverage |

| |developer skills, and minimize support and training expenses. MS Expression Web Designer is used for web |

| |content development and application user interface development in accordance with development guidelines. |

| | |

| |Application user interfaces are an architectural component subject to architectural review. Application user|

| |interface architecture and design must allow for integration with the agency’s portal framework for reusable|

| |delivery in accordance with the agency’s portal development standards and guidelines. |

|Disconnected Client-Server Applications | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |MS Visual Studio Team System 2012 |MS Visual Studio Team System 2015 |Git |

| |Ultimate Edition (for .NET) |Professional | |

| |Maxenso/Natclipse (for Natural) | | |

| |Eclipse (for Java) | | |

|Exception: | | | |

|Contain: |• MS Visual Studio Team System 2008 | | |

| |Enterprise | | |

|Retire: | | | |

|Strategy |Standardizing on a single architecture that integrates well with the enterprise can reduce the complexities |

| |of disconnected application development. To function in the “occasionally connected computing” environment, |

| |message queuing, local data cache, and/or synchronization should be employed. |

| |Application user interfaces are an architectural component subject to architectural review. Application user|

| |interface architecture and design must allow for integration with the agency’s portal framework for reusable|

| |delivery in accordance with the agency’s portal development standards and guidelines. |

|Software Components | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |.NET 4.5 Assemblies |.Net 4.5.2 Assemblies |Java 1.8 (for SOA Services) |

| |Java 1.6 (for SOA Services) |Java 1.7 (for SOA Services | |

|Exception: | | | |

|Contain: |.Net 2.0, 3.5, 4.0 Assemblies | | |

| |.NET Enterprise Services (COM+) | | |

|Retire: |DCOM (HTTP Tunnel) | | |

|Strategy |Applications should be segmented into logical layers in order to simplify maintenance and leverage reusable |

| |services. Business logic will be assessed as part of the agency’s SOA governance to determine if the |

| |business logic should be implemented as SOA services or built as application components. Business logic is |

| |not to be coded in ASP script, client side java script, or stored procedures. |

|Integrated Development Environment | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |MS Visual Studio Team System 2013 |MS Visual Studio Team System 2015 |Visual Studio in the Cloud |

| |Ultimate Edition |Professional |Visual Studio "15" |

| |Eclipse | | |

| |Maxenso/Natclipse | | |

| |IBM Integration Designer (IID) 8.5 | | |

| |Rational Application Developer (RAD) | | |

| |8.5 | | |

| |IBM Operational Decision Manager | | |

| |(ODM) 8.5 | | |

|Exception: | | | |

|Contain: |MS Visual Studio 2008, 2012 Ultimate | | |

| |Edition | | |

| |Embarcadero Delphi | | |

|Retire: |WebSphere Integration Developer (WID)| | |

| |for Business Processes for WebSphere | | |

| |Process Server | | |

|Strategy |Standardize the development environment to take advantage of reusable models and templates, leverage |

| |developer skills, and minimize support and training expenses. Microsoft development tools are preferred for|

| |distributed application. Business logic will be assess according to the agency’s SOA Governance process to |

| |determine if the logic should be developed as an SOA service. |

|Software Source Control | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |MS Team Foundation Server 2012 |MS Team Foundation Server 2015. |TFS in the Cloud |

| |SubVersion Collabnet 4.0 | |Git |

|Exception: |TortoiseSVN | | |

|Contain: |MS Team Foundation Server (TFS) 2008 | | |

|Retire: |Visual Source Safe | | |

|Strategy |TFS Source Code repository is used for source code control for .NET applications. Java-based applications |

| |use Subversion (SVN). The guidance for using SVN can be found in the Java Development Environment Roadmap. |

|Enterprise Application Architecture Modeling (Client Computing) | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Visio 2016 (32bit) | |Visio 365 |

| |Visual Studio (current version) | | |

|Exception: |Visio 2016 (64bit) | | |

|Contain: | | | |

|Retire: |Rational Rose | | |

| |Power Designer | | |

| |Visio 2010 | | |

| |Visio 2013 | | |

|Strategy |When publishing Visio drawings, distribute as .PDF to allow broad compatibility. Specific diagrams such as |

| |a technology component diagram, deployment view diagram, behavior view diagram, and sequence diagram are to|

| |be included in the solution architecture documentation for an enterprise application using Visio. |

|Enterprise Business Architecture Modeling (Client Computing) | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Visio 2016 (32bit) | |Visio 365 |

|Exception: |Visio 2016 (64bit) | | |

|Contain: | | | |

|Retire: |Visio 2010 | | |

| |Visio 2013 | | |

|Strategy |Microsoft Visio is the standard for Enterprise Business Architecture Modeling. |

|Enterprise Technology Architecture Modeling (Client Computing) | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Visio 2016 (32bit) | |Visio 365 |

|Exception: |Visio 2016 (64bit) | | |

|Contain: | | | |

|Retire: |Visio 2010 | | |

| |Visio 2013 | | |

|Strategy |Microsoft Visio is the standard used Enterprise Technology Architecture Modeling. |

|Defect Tracking | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |MS Team Foundation Server 2012 |MS Team Foundation Server 2015 | |

| |SubVersion Collabnet 4.0 | | |

|Exception: |TortoiseSVN | | |

|Contain: | | | |

|Retire: | | | |

|Strategy | |

|Performance Testing |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Microfocus’ QALoad |Microfocus’ Silk Performer | |

| |SOAPUI | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |QALoad is used for performance testing by comparing metrics provided by QALoad’s performance monitoring |

| |capability for different runs of an application. It uses Vantage Agents in conjunction with QALoad. NOTE: |

| |The vendor has deprecated QALoad and will be replacing it with another product in the near future. |

| | |

| |SOAP UI is used for web service testing. It provides a client testing harness to exercise web services. As a|

| |client testing harness is used as part of the testing suite to perform performance testing runs. |

|Load (stress) Testing |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Microfocus QALoad | | |

| |Application Vantage | | |

| |SOAP UI | | |

| |Microfocus’ Silk Performer | | |

| |Visual Studio (current version) with | | |

| |Team Foundation Server (current | | |

| |version) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |SOAP UI is used for web service testing. It provides a client testing harness to exercise web services. As a|

| |client testing harness is used as part of the testing suite to perform load testing runs. |

|Functional (Unit) Testing |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Visual Studio (current version) with | | |

| |Team Foundation Server (current | | |

| |version) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |Visual Studio in conjunction with Team Foundation Server provides the framework for performing test-driven |

| |development using Visual Studio’s logging, tracing, assertion, and unit test projects. |

|Business Rules | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |IBM Operational Decision Manager | | |

| |(ODM) 8.5 | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |WebSphere ILOG Business Rules Engine | | |

|Strategy |Business Rules will be governed & used according the L&I Business Rules Governance guide. |

|Business Orchestration and Workflow (BPM) | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |WebSphere Business Process Manager | | |

| |(BPM) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |WebSphere Process Server (WPS) | | |

|Strategy |Used to create automated business processes that span people, workflows, applications, systems and |

| |platforms. WPS provides service mediation and orchestration capabilities for web services. |

|Document Workflow | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |IBM FileNet P8 Case Foundation | | |

| |(“re-branded” from previous BPM | | |

| |product” | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |Current Enterprise IDM & ORION applications do not use workflow software, relying on code frameworks, SQL |

| |stored procedures, & application system database tables for automated rules-based document & work item |

| |routing to work position & group roles. |

| |Applications that need to include a document workflow process as part of the application functionality will |

| |use FileNet P8 BPM to facilitate the document workflow. SILAS is an example of an application that is using |

| |this standard. |

| |Current IBM FileNet P8 server processing capacity is not sufficient for full agency enterprise support, P8 |

| |servers need additional CPU, memory, & storage plus major software version upgrades. |

|Enterprise Application Reporting Service |

|(Service used by enterprise applications to meeting reporting requirements) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Business Objects XI |SQL Reporting | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Crystal Enterprise Reporting Service | | |

|Strategy | |

|Integrated Document Management (IDM) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |IBM FileNet Image Services | | |

| |IBM FileNet P8 Content Manager | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |Documents stored as part of an applications data set will store the documents in one of the IBM FileNet IDM or|

| |ECM repositories. |

| |IBM FileNet Image Services support ORION for Workers Compensation business programs & Enterprise IDM for other|

| |& future programs. |

| |IBM FileNet Image Services provides a compliant electronic records management repository for static |

| |non-modifiable legal artifact documents, with appropriate performance & server capacity for online case file |

| |review response time. Current Image Services IDM applications use the following key products: |

| |IBM FileNet Image Services (IDM repository) w/SQL Server |

| |FileNet Integral SDS (document storage) with MSAR (Magnetic Storage Archival & Retrieval using WaTech Shared |

| |SAN storage for fast online retrieval) & CSAR (Centera Storage Archival & Retrieval using WaTech EMC Centera |

| |storage for non-modifiable legal archival copy) |

| |FileNet HPII (High Performance Image Import for importing indexed IDM case file documents staged by Kofax |

| |Capture & custom IDM application services) |

| |FileNet IDM Web Services & Desktop (API, services, & ActiveX viewer plug-in for Image Services integration |

| |with custom IDM applications) |

| |* Proof-of-concept in progress to replace ActiveX viewer with Image Services licensed HTML5 web browser |

| |compliant IBM Daeja ViewONE Virtual viewer thru IBM WebSphere Application Server hosted IBM Content Navigator |

| |web client. |

| |Custom IDM web applications & services using VB .NET plus Snowbound RasterMaster .NET 64-bit SDK for document |

| |file format conversion with TIFF, PDF, AFP mainframe, & Office/Outlook documents. |

| |Kofax Capture & Kofax Transformation Module w/SQL Server & agency compatible paper & microfiche scanners |

| |(scan/import documents, QA & index to case file of primary system of record, & stage for import to Image |

| |Services) |

| |Primera Bravo 4102 XRP Disc Publisher & PTBurn SDK (CD & DVD publishing burn & label media for IDM case file |

| |copy) |

| |OpenText RightFax (now enterprise platform that continues to support inbound & outbound fax of IDM case file |

| |documents) |

| |IBM FileNet P8 Content Manager provides an effective electronic records management repository for SILAS, ESCH |

| |documents, & Workers Compensation Structured Settlements, but is currently only set up for light use and not |

| |leveraging available Records Management component. Current IBM FileNet P8 server processing capacity is not |

| |sufficient for full agency enterprise support, P8 servers need additional CPU, memory, & storage plus major |

| |software version upgrades. |

| |Enterprise Service interfaces for use by applications are to be used for application to interact with one of |

| |the IBM FileNet platforms. |

|Service Repository | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |WebSphere Service Registry & | | |

| |Repository (WSRR) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |Service Repository maintains records of all Business capabilities identified for automation, service |

| |interface specifications, service interfaces, service schemas, service level definition artifacts and WSDLs.|

| |It is the repository to be interrogated by business analysts during strategic and tactical planning and cost|

| |estimation to determine services available for use in creating new applications. |

|Service Registry | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |WebSphere Service Registry & | | |

| |Repository (WSRR) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |WebSphere Application Server native | | |

| |UDDI service | | |

|Strategy |Used as the registry for deployed service end-point definitions to be use by consuming applications at |

| |run-time. |

Workgroup Computing

|Electronic Mail |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |CTS Shared Mail Service (MS |CTS Shared Mail Service (MS |Cloud based – Office 365 |

| |Exchange 2010) |Exchange 2016) | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |CTS will manage our Enterprise Email servers with Exchange. |

|Calendaring and Scheduling |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |CTS Shared Mail Service (MS |CTS Shared Mail Service (MS |Cloud based – Office 365 |

| |Exchange 2010) |Exchange 2016) | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |CTS will manage our Enterprise Email servers with Exchange. |

|Collaboration |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |SharePoint 2013 |Microsoft SharePoint Online | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |Move to Share SharePoint and deprecate all others. Push to educate users to use links to documents in |

| |e-mail rather than sending documents themselves. |

|Document Centric Workflow |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |SharePoint 2013 |Microsoft SharePoint Online | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |Move to SharePoint and begin using SharePoint Workflow to control document centric processes or |

| |workflow based on lists or status tracking. |

|Document Publishing |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |SharePoint 2013 |Microsoft SharePoint Online | |

|Exception: |eGain – Knowledge Management | | |

| |platform replacing OLRS system | | |

| |used primarily for Industrial | | |

| |Insurance “knowledge content” | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |This should be a specific instance of a Document Centric Workflow. |

|Search |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |SharePoint 2010 (Collaboration |Google Search Appliance (Web | |

| |Documents) |Content and databases) | |

| |WCI Search for (Composite | | |

| |Application Search) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |A federated search model is our desired direction. Further assessment will be done after SharePoint is|

| |brought in to manage workgroup documents. |

|Records Management |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |IBM FileNet P8 |SharePoint 2013 |Microsoft SharePoint Online |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |Assessment will be done to determine if and when SharePoint can be used for Records Management |

| |Current IBM FileNet P8 server processing capacity is not sufficient for full agency enterprise support,|

| |P8 servers need additional CPU, memory, & storage plus major software version upgrades. Also, although |

| |IBM FileNet P8 Records Management component installed, current business programs in P8 are not using |

| |it. |

| | |

| |Technically, IDM & Document Management in regards to records management of static legal artifacts |

| |should be separate from “Workgroup Computing” ECM which primarily involves collaboration & publishing |

| |of agency information & knowledge with some potentially becoming a legal artifact tied to a specific |

| |record set. Proposed change in Applications section from “Document and Image Storage” to “Integrated |

| |Document Management/IDM”. |

|Document Management (for Workgroup Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |SharePoint |SharePoint 2013 |Microsoft SharePoint Online |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |SharePoint is our target direction for Workgroup Computing Document Management functions. Assessments |

| |will be done to determine which functionality and timing can be implemented. |

| |At this time, SharePoint does not look viable for IDM Applications until concerns for performance, |

| |operations, & governance are addressed. |

|Enterprise Reporting Service |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Microsoft Business Intelligence | | |

| |(SSRS, and other SharePoint based | | |

| |functionality) | | |

|Exception: |SAS for Fraud Detection | | |

|Contain: |Hyperion | | |

|Retire: | | | |

|Strategy |The desired direction is to deprecate Hyperion and migrate to the Microsoft BI Suite. |

|Optical Character Recognition |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy |No current standard. Eventually needed to support both Workgroup Computing Document Management & |

| |Integrated Document Management (IDM) of digitized text image documents to capture, index, & retain for |

| |full text search of any document within the constraints of authorization & confidentiality. |

|Electronic Forms (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Adobe Acrobat | | |

| |Word | | |

|Exception: | | | |

|Contain: |InfoPath | | |

|Retire: | | | |

|Strategy | (NOTE: January 31, 2014, Microsoft announced plans to discontinue InfoPath)This strategy is based on the |

| |following classification system adopted by the E-Forms Subcommittee of the Customer Advisory Board (CAB). |

| |LEVELS OF ELECTRONIC FORMS |

| |1. Print on demand |

| |2. Fill and print |

| |3. Interface with (lookup and update) a back-end database. |

| |4. Route the form to another user. |

| |5. Enable digital signature attachment or other legal requirements |

| |6. E-commerce (secure financial transactions) |

| | |

| |Levels 1: Adobe Acrobat is the industry defacto standard and is the recommended format for this level e-form.|

| | |

| | |

| |Levels 2: Word is the agency defacto standard and is the recommended format for this level e-form. |

| | |

| |Levels 3, 4 & 6: Agency Standard Web Development Tools are the approved choice. (Please see the |

| |“Applications” section of this document for more information.) |

|Office Automation Software (Client Computing) | |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Office 2016 (32bit) | |Office 365 |

|Exception: |Office 2016 (64bit) | | |

|Contain: | | | |

|Retire: |Office 2010 | | |

| |Office 2013 | | |

|Strategy |Office automation software will use an integrated suite in order to leverage common training and support |

| |resources as well as take advantage of reduced licensing costs. |

DATA / DBMS

|Database Management Systems |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |SQL Server 2012 R2 |SQL Server ? |Access 2016 |

| |Access 2010 (Single-user/local |(not listing SQL Server in Target |MS Dynamics |

| |workstation) |& Emerging might imply Access is | |

| | |agency target fro all database’s?)| |

| | |Access 2013 | |

| | |MongoDB (for PC laptop mobile | |

| | |applications) | |

|Exception: |SQL Express | | |

|Contain: |ADABAS (Mainframe) | | |

| |VSAM | | |

| |FASTPlus | | |

| |DB2 | | |

|Retire: |SQL Server 2008 | | |

| |MSDE (Desktop) | | |

|Strategy: |MS SQL Server is the agency’s strategic database management system and will be used for new development. |

| |MS Access is appropriate only for single-user desktop applications. |

| | |

| |Contained products will continue in production for several more years, but plans are being made to |

| |migrate to a strategic platform. Products may continue to be used to maintain and enhance their |

| |respective applications, but significant new investments must be approved by I.S. management. |

|Data Warehouse |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |SQL Server 2012 | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |SQL 2008 R2 | | |

|Strategy: | |

|MetaData Repository |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Rochade w/ WEB Access and Rochade |SQL Server 2012 | |

| |Browser | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |ROAccess | | |

|Strategy: | |

|Data Extraction, Transformation and Load |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |SQL Server Integration Services | | |

| |2012 | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Business Data Replication |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Adabas Reptor | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |In general, data replication is not recommended unless it is for caching purposes and the “owning” system|

| |maintains control over updates. |

|Data Hygiene (Cleansing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

ELECTRONIC COMMERCE

|Credit Card Verification and Payment Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Verifone (FrontCounter Credit Card| | |

| |Processing) | | |

| |Official Payments (Internet | | |

| |Payment Service) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |TPI | | |

| |CyberSource (shared DIS Service) | | |

|Strategy: |A client solution using Verifone APIs was developed and deployed in 2011. This is to be used by any |

| |solution that requires “front counter” credit card support….the ability to process credit cards for |

| |walk-in customers to L&I field offices. |

| | |

| |The Internet Payment Service was created with Official Payments and the backend processing service. All |

| |web-based solutions that require credit card processing capabilities use the Internet Payment Service. The|

| |service includes a user interface to present payment options for the client applications. |

|Data Interchange (EDI) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |No formal EDI standard is currently being used. Data exchanges use simple FTP transfers. XML and secure |

| |Internet access is being targeted for applications that have traditionally used EDI. |

| |

|Electronic Funds Transfer |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Internet Payment Service | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |The in-house developed Internet Payment Service provides support for electronic funds transfer. |

|Electronic Checks |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Internet Payment Service | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |The in-house developed Internet Payment Service provides support for electronic checks. |

HARDWARE PLATFORMS

|Mainframe |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |IBM S/390 | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Mainframe services hosted by DIS. There are plans to migrate from a mainframe based environment to a distributed |

| |server computing environment. |

|Midrange |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | RISC based servers no longer exist within L&I |

|Network Server |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |X86 Intel | |Virtual Cloud Servers |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Consolidate servers as much as possible to simplify administration. Use server hardware that is reliable, |

| |fault-tolerant and designed for multi-user network environments. Virtual Cloud Servers should be considered viable|

| |for future server acquisitions. |

|Primary Device - Desktop Computer (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Dell Optiplex 7050 (2017) |7th Gen processor |8th Gen processor |

|Exception: |Macintosh | | |

|Contain: |Dell Optiplex 7040 (2016) | | |

| |Dell Optiplex 7030 | | |

| |Dell Optiplex 7020 | | |

| |Dell Optiplex 7010 | | |

|Retire: |Dell Optiplex 790 and earlier. | | |

|Strategy: |The Desktop computer is for users or functions that have no mobility requirements (e.g. Training rooms, Front |

| |Counter PC’s, etc.). Desktop computers are considered a primary device and is replaced on a 4 yr. lease cycle. |

| |Desktop Standards: |

| |OS Support: Windows 10 64-bit OS |

| |Processor: Intel i5 dual core processor (7th Generation) |

| |Memory: 8 GB RAM |

| |Storage: 500 Gb SSD |

| |Attachments Included: |

| |Built-in optical drive (DVD r/w): |

| |24” Flat screen monitor (not touch) |

| |Microphone and Audio Jacks |

| |Min 4 USB 3.0 connections |

| |Other: |

| |Can support dual monitors |

| |Can support bluetooth |

| |Support VPro |

| |Can support WiDi |

| |Can support Discreet Graphics card |

| |Field Serviceable |

| | |

| |Macintosh computers are allowed by exception for special purposes only. |

|Primary Device - Laptop Computer (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Dell Lattitude 7470 |7th Gen processor |8th Gen processor |

|Exception: |MacBook | | |

|Contain: |Dell Lattitude 5450 | | |

| |Dell Lattitude 5440 | | |

| |Dell Lattitude 6430 | | |

|Retire: |Dell Lattitude 6420 | | |

| |Dell Lattitude 6410 | | |

|Strategy: |The Laptop computer is considered a primary device and is Intel based running Windows OS and replaced on a 3 yr. |

| |cycle. The Purpose for the Laptop computer is for users with mobility needs and sturdiness is more important than|

| |size (These devices meet hardening standards). |

| | |

| |Laptop Standards: |

| |OS Support: Windows 10 64-bit OS |

| |Processor: Intel i5 dual core processor (7th Generation) |

| |Memory: 8 GB RAM |

| |Storage: 250 Gb SSD |

| |Attachments Included: |

| |14” Flat screen monitor (touch enabled) |

| |Integrated WebCam |

| |Fingerprint Reader |

| |Microphone and Audio Jacks |

| |Min 4 USB connections (min 2 USB 3.0) |

| |Other: |

| |Field Serviceable |

| |Supports Bluetooth |

| |Supports WiFi |

| |Supports VPro |

| |Supports WiDi |

| |Mil-Std-810G rated |

| |Backlit Keyboard |

| |Docking Station that can support dual monitors |

| | |

| |MacBook computers are allowed by exception for special purposes only. |

|Primary Device - Convertible Computer (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |HP Elitebook |7th Gen processor |8th Gen processor |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |The Convertible computer is considered a primary device and is Intel based running Windows OS and replaced on a 3 |

| |yr. cycle. The Purpose for the Convertible computer is for users with mobility needs and size is more important |

| |than sturdiness. |

| | |

| |Convertible Standards: |

| |OS Support: Windows 10 64-bit OS |

| |Processor: Intel i5 dual core processor (7th Generation) |

| |Memory: 8 GB RAM |

| |Storage: 250 Gb SSD |

| |Attachments Included: |

| |Converts to tablet mode |

| |10-12”” Flat screen monitor (touch enabled) |

| |Integrated WebCam |

| |Fingerprint Reader |

| |SD Card Reader |

| |Microphone and Audio Jacks |

| |Min 4 USB connections (min 2 USB 3.0) |

| |Other: |

| |Field Serviceable |

| |Supports Bluetooth |

| |Supports WiFi |

| |Supports Cellular Mobile Broadband |

| |Supports VPro |

| |Supports WiDi |

| |Mil-Std-810G rated |

| |Docking Station that can support dual monitors |

| | |

| |The Tablet/Convertible computer is currently considered a companion device. Develop this hardware platform as a |

| |primary device with the implementation of Windows 10. Continue to support iOS iPad as a companion device. |

|Mass Storage |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Server-based (LAN) |WaTech Storage – Hosted |CTS Storage Managed Services |

| |Storage Array, NAS, SAN. |Services – |Solid State |

| |NetApp ( Network Appliance ) |Storage Array, NAS, SAN. |Cloud services |

| | |NetApp | |

|Exception: |Centera (EMC) | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | Cloud Services (AWS, Azure) will play a bigger role in storage as storage costs continue to decline. Disaster |

| |Recovery is using cloud based storage with SunGard in PA. |

|Operating Systems (NetOps/Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |MVS (mainframe) |Windows Server -2016 |Companion Devices – Windows 10 |

| |Windows 2008 Unified Data Storage (NAS) | |(64 bit) |

| |Windows Server 2008 and 2012 | | |

| |Primary Devices: Windows 10 (64bit) | | |

| |Companion Devices - iOS | | |

| |WADS Workstations: Windows 10 (64bit) | | |

|Exception: |OSX | | |

|Contain: |Primary Devices: Windows 7 (32bit) | | |

| |WADS Workstations: Windows 7 (64bit) | | |

|Retire: |Windows 8.1 | | |

|Strategy: |Operating systems for all networked devices are standardized across the enterprise. |

| |Because of the rapid adoption of new client operating systems, a policy of “managed diversity” is practiced, i.e. |

| |operating systems will be maintained at compatible versions, but will not all be at the same revision level. |

Mobile Computing

|Mobile Device Management (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |AirWatch (CTS Service) | |MS InTune |

|Exception: | | | |

|Contain: | | | |

|Retire: |McAfee EMM | | |

|Strategy: |Have all Mobile devices provisioned and controlled through a Central service. |

|Mobile Application Development Platform (MADP) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Verivo |TBD | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Visual Studio | | |

|Strategy: | |

|Mobile Multimedia Production |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | |TBD | |

|Exception: |iMovie (iPhone and iPad) with | | |

| |tripod and microphone | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Limited use for eLearning, OHR, Public Affairs and Communications projects |

|Smart Phone (Companion device) (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Apple iPhone (iOS) | |Windows 10 capable Smart Phone |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |The target audience for these devices is for employees requiring Phone, Mail, and Calendar capabilities |

| |while away from their workstation. The Smart Phone is not a primary device and will not replace the primary|

| |device. |

| | |

| |Continue to support Apple iPhones as a companion device for phone, mail, and calendaring. |

INFRASTRUCTURE

|Virtual Machine Technology |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |VMware 6.0 |Vmware Supported |MS Hyper-V |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Backup Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Commvault |Disk to Disk copy |Virtual Tape Libraries |

| |Veeam |Replication |Cloud Backup Services |

| | |CTS Backup services | |

| | |Cloud services for storage and or | |

| | |backup and Disaster Recovery | |

| | |MS DPM 2012 | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Servers are increasingly being converted from physical to virtual servers. We are backing up virtual |

| |servers using Veeam and physical servers use Commvault. |

| | |

| | |

|Bandwidth |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |1000Mb – Desktop | |1Gig WAN links for field offices |

| |100Mb – WAN Node Sites to Remote | |40 to 100 Gig core to core and to |

| |10Gb – Server | |server |

| |10Gb – Switch to Switch | | |

| | | | |

| |1Gig – HQ to WaTech | | |

| |MPLS WAN | | |

| |10Gb – Virtual Host server and | | |

| |iSCSI storage arrays | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |New applications and technologies such as virtual servers, virtual desktops, storage area networks (SAN), |

| |voice over IP, e-learning, video conferencing and virtual meetings will require higher bandwidth. Will need|

| |to increase bandwidth as needed. |

|Caching Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |None | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Directory Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Microsoft Active Directory | | |

| |IBM RACF | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Strategic Vendor = Microsoft - Consolidate network directories to a single standards compliant directory |

| |service. Microsoft Active Directory will be the backbone of a statewide directory service, which will |

| |enhance inter-agency data sharing. LNI’s strategic direction is to standardize on Active Directory and to |

| |participate in the statewide directory service. |

| | |

| |Active directory configuration is to be limited to LDAP standards compliant capabilities to ensure the |

| |broadest possible directory services integration across systems. |

|Firewall Services (ISSO/Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |WaTech hosted Fortinet solution |Web Application Firewall |Application firewalls |

| |Client – McAfee HIPS Firewall | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Checkpoint | | |

|Strategy: |L&I will comply with all state and federal laws and regulations concerning the privacy and security of |

| |medical and other personal information. The firewall secures and controls access to the L&I network, |

| |including intranet web content. |

|Full Disk Encryption (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |McAfee Endpoint Encryption | |Microsoft BitLocker |

| |(Primary Devices) | |Intel Disk Encryption |

| |iOS integrated disk encryption | | |

| |(Companion Devices) | | |

|Exception: |Microsoft BitLocker | | |

|Contain: | | | |

|Retire: |Safeboot | | |

|Strategy: |McAfee Endpoint Encryption is currently deployed as our Enterprise disk encryption product. McAfee |

| |Endpoint Encryption standard is 128-bit AES. |

|Power Management – Workstation (Client Computing) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |System Center Configuration Manager |System Center Configuration Manager – | |

| |2012 |Current Branch | |

|Exception: | | | |

|Contain: |Verdiem Surveyor | | |

|Retire: | | | |

|Strategy: |System Center Configuration Manager 2012 is the power management product for agency workstations. |

|Load Balancing Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | |Procure Load balancing product for the|F5 equipment |

| | |virtual sever environment | |

|Exception: |Barracuda Load Balancer | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |High availability and 24/7 operation will require some type of web balancing technology. Examples are DNS |

| |round robin or Cisco SLB (server load balancing) switching. Any load balancing service must be tightly |

| |integrated with the application development effort to ensure compatibility. Coordinate any new load balancing|

| |service with the EAO to request an ACP Exception request. |

| | |

| |There are no requirements for LBS at the current time. |

|Local Area Network – including Wireless (Wi-Fi) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Layer 2/3 Ethernet Switching |Policy-based intelligent networking |Software Defined Networks (SDN) |

| |Cisco Chassis based (core) |Research other commodity network | |

| |Cisco Stackable based |vendors for Ethernet switching | |

| |(access/closet switches) |products (enhanced features, reduce | |

| |Aerohive – Wi-Fi (Wi-Fi is an |costs etc). | |

| |extension of Ethernet) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Strategic Vendor: Cisco. Standardize the infrastructure to improve reliability and reduce integration |

| |problems. Cisco is the agency’s strategic networking partner. Aerohive (Wi-Fi wireless access points) |

|Protocols |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |TCP/IP v4 |TCP/IP V6 | |

| |EIGRP (Routing) |SIP for IP communications | |

| |SNMP | | |

| |MPLS (Multi Protocol Label | | |

| |Switching) WAN routing | | |

| |ICMP | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |SDLC | | |

| |HDLC | | |

| |SNA | | |

|Strategy: |Standardize on a single routable internetworking protocol, i.e. TCP/IP, to facilitate interoperability and |

| |to reduce integration and problem solving. |

|Remote Access |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |F5 VPN (DIS) |Explore Aerohive VPN Solution |Microsoft Direct Access |

| |Citrix Metaframe /ICA | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Juniper SSL VPN | | |

|Strategy: |Provide a secure remote access technology that allows our users to perform the majority of their business |

| |needs from anywhere on any client. |

|Traffic Management |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |QoS Layer 2 |Review End-to-end QoS for all | |

| |QoS (quality of service layer 3) |applications/services on the network | |

| |MPLS (multi protocol label |(policy based networking) | |

| |switching) on the SGN |One to many video broadcast | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |High bandwidth application delivery must be managed to prevent overloading the network infrastructure and |

| |adversely impacting mission critical applications. IP Multicast has proven to be unreliable to field |

| |offices requiring new technologies to bypass our WAN service QoS ensures mission critical applications |

| |receive priority. |

| |The agency needs to start the process of reviewing all current and newly implemented applications and |

| |services for QoS settings (policy-based networking) |

|SSL Accelerator Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |None | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |May be required if L&I develops a dedicated credit card processing server. |

|Storage Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Server-based (LAN) |Storage System, Ethernet, iSCSI, NFS, |WaTech Storage Managed Services |

| |Storage System, Ethernet, iSCSI, |CIFS, Hyper converge infrastructure |for production applications |

| |NFS, CIFS | |Solid State |

| | | |Cloud Service Providers |

|Exception: |Centera (EMC) (DIS) | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |LAN servers utilize NetApp and HP NAS or external storage. iSCSI Network RAID 5 (across nodes) is now |

| |standard. ACP was completed. |

| | |

| |We are using Network Appliance for our storage solution and HP NAS. The environment has tier one, two , and |

| |three type storage. Tier one is only flashpool for tier two and three storage type. SSD is tier one, SAS is |

| |tier two and SATA is tier three. We will look at tier one all flask filers for future high performance disk |

| |requirements. |

|Topology |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Switched Ethernet (LAN) | | |

| |(MPLS WAN) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Continue using switched Ethernet for LAN technology, and MPLS for WAN. Increase speeds (Bandwidth) when |

| |required by users and supported by equipment vendors. |

|Wide Area Network |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |WaTech Backbone (MPLS) for all |40 – 100 Mb Links (field |Wireless WAN connectivity |

| |WAN Connections |offices) |(possibly for redundant circuits |

| |Cisco ASIC’s based Layer 2/3 | |or production circuits) |

| |Switches (L&I Tumwater HQ to CTS)| | |

| |10 Mb Link (field offices) | | |

| |100 Mb Link(field offices) | | |

| |S-MON for connectivity from TumHQ| | |

| |to WaTech SGN | | |

| |Cisco ASIC’s based Layer 2/3 | | |

| |Switches field offices to CTS | | |

| |backbone (MPLS) | | |

|Exception: | | | |

|Contain: |T1 serial connectivity from each | | |

| |field office to CTS Backbone | | |

| |(MPLS) | | |

|Retire: | | | |

|Strategy: |Continue using Cisco & CTS as strategic vendors. |

INTEGRATION (EAI)

|Integration Broker (Message Broker) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |IBM WebSphere Business Integration | | |

| |IBM Integration Bus | | |

| |IBM Transformation Extender | | |

|Exception: | | | |

|Contain: |Microsoft Transaction Server | | |

| |SAGA EntireX (ADABAS) | | |

| | | | |

|Retire: |MS BizTalk | | |

|Strategy: |Message brokering service is provided by IBM Websphere Business Integration Message Broker (formerly MQ |

| |Integrator). The broker provides transformation and intelligent routing services and relies on WebSphere MQ|

| |(formerly MQ Series) for message transport. |

| | |

| |SAGA EntireX is contained to supporting legacy ASP (web) and COM applications to ADABAS. Use will diminish |

| |as legacy applications are migrated to the standard environment. |

| | |

| |Microsoft BizTalk will continue to be used as needed for specialized purposes, but will interface to the |

| |standard EAI services for integration with other internal systems. |

|Message Format |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |REST (JSON) | | |

| |SOAP (XML) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |XML messages (a.k.a. Web Services) use primarily canonical forms and are transported and managed by the EAI |

| |infrastructure. This provides a robust, reliable and secure Web Services infrastructure internal to the L&I |

| |network. |

| | |

| |** XML Web Services will be use for application integration external to the agency as standards mature, |

| |especially security. |

|Message Transport |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |IBM MQ | | |

| |Web Services (HTTP) | | |

| |EAI | | |

|Exception: |Microsoft MSMQ | | |

|Contain: | | | |

|Retire: |Remoting | | |

|Strategy: |IBM MQ is the standard message transport product. Microsoft MQ will be used within Microsoft server |

| |applications as required, but will interface to the standard EAI infrastructure for application integration.|

|Middleware – Data Access |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |ADO .NET | | |

| |ODBC .NET | | |

| |OLE DB .NET | | |

| |JDBC | | |

| |Entity Framework | | |

|Exception: | | | |

|Contain: |ODBC | | |

| |OLE DB, Sybase Open Client, COM/DCOM, ADO | | |

| |BDE | | |

|Retire: | | | |

|Strategy: |Microsoft ADO .NET services will be used to access strategic DBMS platforms. XML will play an important |

| |role as a standard data exchange format. |

|Work Flow - Business Process Management |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |WebSphere Process Server | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Work Flow – Business Process Activity Monitoring |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | |IBM WebSphere Business | |

| | |Integration Monitor | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Business Process Activity Monitoring displays real-time information to allow decisive business performance |

| |management and optimization. |

SECURITY

| Authentication Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |RACF - UID/PW (mainframe) |WAP/WTLS (Wireless) |S2ML (Internet XML) |

| |MS Windows – UID/PW (LAN) |WS-Security (Web Services) |AuthXML (Internet XML) |

| |UNIX - UID/PW (mid-range) |CTS Hosted Internal Certificate |XKMS (Internet XML) |

| |Sybase (mid-range) |Authority |XML Signatures (Internet) |

| |Fortress – UID/PW (Internet | |S2ML: Security Services Markup |

| |Standard Authentication) | |Language |

| |Secure Access Washington (SAW) | |XKMS: XML Management Key Services |

| |Secure Agency Enabled Portal (SEAP)| | |

| |w/ MFA and KBA | | |

| |SSL (server authentication) | | |

| |Shiva VPN - Secure ID Token (Remote| | |

| |Access) | | |

| |Citrix – Secure ID Token (Remote | | |

| |Access) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Utilize a single strong authentication (logon) mechanism per application |

| | |

| |Single Sign On |

|Digital Certificates / Non-Repudiation |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |DST Digital Certificate – X.509 v3 |All WA State Certified CA’s – X.509| |

| |ID Certify Digital Certificate – |v3 | |

| |X.509 v3 | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Strategic Vendors: Digital Signature Trust (DST), CTS. DST is the only Certificate Authority authorized |

| |to provide digital certificates to state customers. Digital Certificates are required for authentication |

| |through the CTS Transact Washington service, which provides authentication and encryption for web |

| |applications. |

| Authorization/Access Control Services |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Shared Security Service (Selected Web |Expand Shared Security Service to |Network Quarantine Service. |

| |apps) |all external and internal Web apps.|S2ML (Internet XML) |

| |RACF (mainframe) |Tivoli Security Policy Manager is | |

| |Natural Security (mainframe) |identified as the replacement for | |

| |LINIIS rules & programs (mainframe) |the Shared Security Service | |

| |SAGA Middleware (mainframe) |Microsoft Network Policy Server | |

| | |(Radius) | |

| |MS Windows ACLs (LAN) | | |

| | | | |

| |Secure Access Washington – LDAP Directory| | |

| |(Internet) | | |

| |WaTech SEAP Services | | |

| |Fortress anonymous – LDAP Directory | | |

| |(Internet) | | |

| |F5 remote access | | |

| |Fortinet Firewall | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Sybase rules & programs (mid-range) | | |

| |Fortress2 – LDAP Directory (Internet) | | |

|Strategy: |Develop one model for file level access control (e.g. mid-range “Web Security”) |

| |Build on the capability of Windows Active Directory to simplify and improve access control to internal |

| |applications |

|Data & Message Integrity |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |DST Digital Certificate – X.509 v3 | | |

| |(Internet) | | |

| |SSL Message Authentication Codes | | |

| |(Internet) | | |

| |IPSec (network) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Currently using web-based mail interface encrypted with SSL. Will most likely migrate to standard S/MIME |

| |system in next 12 months. |

|Confidentiality |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |DST Digital Certificates – X.509 v3|SSL 2/3 Encryption – 128 Bit |XML Encryption |

| |(Internet) |minimum (Internet) | |

| |SSL 2/3 Encryption (Internet) |N2H2 Proxy Server (Internet) | |

| |Secure Computing Internet Content |WAP-WTLS (Wireless) | |

| |Filtering Proxy Server (Internet) | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Use DIS Secure Access services. SSL encryption provided through Transact Washington service or the |

| |Fortress reverse proxy server. |

|Auditing |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |RACF Logs (mainframe) | | |

| |CICS Logs (mainframe) | | |

| |MS Windows Event Logs (LAN) | | |

| |UNIX Event Logs (mid-range) | | |

| |SQL Server Logs (application) | | |

| |DataPower | | |

| |Shared LogService | | |

| |WaTech hosted RSA Security | | |

| |Analytics (SIEM) | | |

|Exception: | | | |

|Contain: |AmberPoint | | |

|Retire: |Axent ESM (mid-range) | | |

|Strategy: | |

|Operational Integrity & Security Administration |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Trend Micro ScanMail (Email virus | | |

| |detection) | | |

| |McAfee ePolicy Orchestrator | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |All desktop and laptop computers will be provided with virus scanning software. Email is scanned at the |

| |server. |

|Monitoring & Testing |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Tripwire (Web environment Intrusion|Intrusion Detection-Monitor |Intrusion Prevention System |

| |Detection -CTS) |Software (Network) |Vulnerability Management System |

| | |Network Vulnerability Scanner | |

| | |(Qualys) | |

| | |Event Correlation System | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Axent ESM (mid-range) | | |

|Strategy: |The network is actively monitored for intrusions. Vulnerabilities are proactively identified, tracked and |

| |remediated. |

|Transaction Security |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | |WS-Security Web Services Protocol | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

SYSTEMS MANAGEMENT

|Disaster Recovery |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | | |Cloud Service |

| | | |CTS Service |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Help Desk |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Front Range HEAT | |MS Service Desk |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Operations Management |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |System Center Configuration Manager|SCCM Ops Manager | |

| |Insight Manager | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Performance Monitoring and Tuning |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Dynatrace APM |Dynatrace Products | |

| |DataPower | | |

| |QA Load? | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |AmberPoint | | |

|Strategy: |Compuware was renamed to Dynatrace. Currently version 6.3 |

| | |

| |DataPower is used for runtime web service performance monitoring. |

|Storage Management |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |NetApp Manager, Veeam One |NetApp Products | |

| | |Veeam One | |

| | |Solarwinds | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Telecommunications |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

VOICE SERVICES

|Voice Systems (PBX ) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |AVAYA’s Communication Manager |CEBP (Communication Enabled Business |Move all telephone endpoints |

| |Avaya System Manager |Process) |from H323 to SIP |

| |Avaya Session Manager (SIP Protocol)|Replace all TDM telephones in the |Move all PSTN trunks from |

| |WAN/LAN Convergence (VoIP) |Tumwater HQ building with physical IP|TDM/PRI to SIP |

| |Avaya One X Communicator standard |phones and or IP softphones | |

| |softphone for Teleworkers Only |Avaya oneX communicator Standard | |

| | |Softphones available agency wide (in | |

| | |office and Teleworkers) | |

| | |Avaya one x agent softphone available| |

| | |agency wide for call center staff | |

| | |(internal office and Teleworker | |

| | |staff) | |

| | |Move physical PBX servers to the | |

| | |virtual environment | |

| | |Review feasibility of moving the | |

| | |agencies PSTN trunking from PRI to | |

| | |SIP | |

| | |Review multiple cloud service vendors| |

| | |for telecommunications services | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Avaya 4600 series IP phones | | |

|Strategy: |Stay with Avaya’s communication manager as the agencies enterprise voice call control application. All |

| |newly purchased Voice technologies should be IP based and utilize VoIP. Avoid the purchase of TDM voice |

| |equipment, purchases of this type of equipment is through the exception process only. |

|Automated Call Distribution systems (ACD) / Call Management System (CMS) (MIS) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

| |Avaya Converged ACD and MIS Systems |Continue deploying and using our | |

|Standard | |strategic vendor’s (AVAYA) converged | |

| | |ACD and MIS systems with the | |

| | |possibility of migrating all L&I’s | |

| | |ACD and MIS to single vendor’s | |

| | |converged voice system. | |

| | |Review multiple cloud service | |

| | |providers for ACD and CMS services | |

|Exception | | | |

|Contain | | | |

|Retire | | | |

|Strategy: |Continue deploying and using our strategic vendor’s (AVAYA) converged ACD and MIS systems. |

| Voicemail |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | |TCP/IP Integration | |

| |Avaya Aura Messaging with SIP |Unified Communication | |

| |integration to the PBX | | |

| |Application Servers are now on |Review multiple cloud service | |

| |virtual servers |providers for voicemail services | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Upgrade current voice mail enterprise hardware and software as needed to maintain supportability and |

| |compatibility. |

|Interactive Voice Response IVR |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Avaya’s Experience Portal (EP) |Speech recognition |Video content in Experience |

| |Avaya IDE for development environment |Migrate the predictive dialer to |Portal applications |

| |VXML and CCXML |the EP / POM | |

| |SOAP and WSDL |Use POM for texting and emailing | |

| |Proactive Outreach Manager (POM) |(reminders for IME) | |

| |TTS Text to speech Lumenvox | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Predictive Dialer | | |

|Strategy: |All new IVR application will be deployed in the Experience Portal environment. Migrate all existing IVR |

| |applications to Experience Portal, retire contained IVR environment. |

|Cabling infrastructure Voice & Data |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Voice & Data converged cabling: | | |

| |CommScope Systimax hardware | | |

| |UTP Cable CAT 6 | | |

| |Fiber cable 10G speeds and above | | |

| |UTP Cable TIA/EIA 606 labeling | | |

| |standard | | |

|Exception: |T1 Shielded cabling | | |

|Contain: |Voice only | | |

| |CommScope Systimax hardware | | |

| |UTP CAT 5 | | |

|Retire: | | | |

|Strategy: |Follow Industry Voice and Data cabling standards through the EIA-TIA. The EIA-TIA standards will be phased|

| |in for new building wiring installs. Existing building wiring additions will match what is already |

| |installed if possible. If not able to match existing cabling, new additions must have the same or better |

| |capabilities. Use fiber cabling for all connectivity when 10Gbps or above is needed |

|Video Conferencing/Multimedia Services |

|Current |Target (12-24 months) |Emerging (24-48 months) | |

|Standard: |Group Video conferencing Skype for |No Change | | |

| |Business | | | |

| |L&I’s data network used as transport | | | |

| | | | | |

| |Multimedia | | | |

| |Kontiki webcaster (live broadcasts) | | | |

| |Kontiki MediaCenter (internal VOD) | | | |

| |YouTube (external VOD) | | | |

|Exception: | | | | |

|Contain: | | | | |

|Retire: |Polycom IP Viewstation | | | |

| |Locally-stored VOD instances | | | |

|Strategy: |Expand Webcaster services to more locations outside of auditorium. | |

| |Migrate all internal video content to MediaCenter for two years before moving to State Digital Archives. | |

| Building paging systems |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Valcom multizone paging systems. | | |

|Exception: | | | |

|Contain: | | | |

|Retire: |Bogen | | |

|Strategy: |Stay with Valcom as vendor for all paging components. |

|Telephone Headsets |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Plantronics PC compatible Savi series| | |

|Exception: | | | |

|Contain: | | | |

|Retire: |GN Netcom | | |

|Strategy: |Our Wired and Wireless headsets strategic partner is identified as Plantronics. This vendor is able to meet |

| |our agencies headset needs. Having multiple headset vendors creates problems for troubleshooting and spare |

| |part inventory. |

| Softphone headsets |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Plantronics wireless USB 400 series | | |

| |headsets | | |

| |Plantronics Hub client integration | | |

|Exception: |Wired (UC) Unified Communications | | |

| |Plantronics | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Our Wired and Wireless headsets strategic partner is identified as Plantronics. This vendor is able to meet |

| |our agencies headset needs. Having multiple headset vendors creates problems for troubleshooting and spare |

| |part inventory. |

WIRELESS

|Wireless Application Development (see Mobile Application Development) |

| |

|Wireless Application Gateway (WAG) |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: | | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

|Wireless Client (see Hardware Platforms) |

|Wireless Data Service |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |GPRS (Cellular) |GPRS/EDGE (Cellular) |W-CDMA (UMTS) |

| |(e.g. AT&T, T-Mobile) | |Wi-Max (WLAN) |

| |802.11x (WLAN/Wi-Fi) | | |

|Exception: |CDMA 2000 | | |

| |(e.g. Verizon, Sprint) | | |

|Contain: | | | |

|Retire: |CDPD (AT&T) | | |

|Strategy: |GPRS is the current standard and is available through a DIS contract with AT&T. |

| | |

| |W-CDMA (Wideband Code-Division Multiple-Access) UMTS (Universal Mobile Telecommunications System) should |

| |eventually emerge as the third generation (3G) standard, but carriers are implementing different 2.5G |

| |technologies during the migration. AT&T is now offering 2.5G service in Washington State but coverage is very|

| |limited. GPRS (General Packet Radio Service) compatible equipment is required. |

| | |

| |Identify all possible radio frequencies to use for Wireless technologies and reserve them for future use. |

| | |

| |Do not deploy wireless technology without consulting with the EAO. |

Assistive Technologies

|Hearing impaired |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |Washington Relay Telecommunications| | |

| |Relay Service | | |

|Exception: |TTY service | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: |Washington Relay which is a free service provided by the Washington State Office of the Deaf and Hard of |

| |Hearing (ODHH) ensuring equal communication access to the telephone service for people who are deaf, |

| |deaf-blind, hard of hearing and speech disabled. |

| | |

| |This service allows hearing callers to communicate with deaf, hard of hearing, deaf-blind and speech disabled |

| |relay users and vice versa through specially trained relay operators. |

| | |

| |Calls can be made to anywhere in the world, 24 hours a day, 365 days a year with no restrictions on the |

| |number, length, or type of calls. All calls are strictly confidential and no records of any conversations are |

| |maintained. If TTY is needed by staff it can be implemented as an exception. |

| A Multilingual Solutions over the Telephone |

|Current |Target (12-24 months) |Emerging (24-48 months) |

|Standard: |CTS Language Link | | |

|Exception: | | | |

|Contain: | | | |

|Retire: | | | |

|Strategy: | |

-----------------------

.

.

.

.

.

.

.

.

.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download