1 / 87

Technical Reference Model ( Information Technology Standards ) July 2004

Technical Reference Model ( Information Technology Standards ) July 2004. Technical Reference Model.

xander-riddle
Télécharger la présentation

Technical Reference Model ( Information Technology Standards ) July 2004

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

E N D

Presentation Transcript

  1. TechnicalReference Model( Information Technology Standards ) July 2004

  2. Technical Reference Model • The technology layer of the GSA enterprise architecture describes the infrastructure needed to support the applications that are necessary for GSA to fulfill its mission. This layer of the architecture is comprised of the physical hardware and software components in place throughout the enterprise. The technology layer utilizes a classification system called the Technical Reference Model adapted to break the technology components down into manageable segments. • The Technical Reference Model is a taxonomy and structure that provides 1) a consistent set of service areas and interface categories and relationships used to address interoperability and open system issues, 2) conceptual entities that establish a common vocabulary to better describe, compare, and contrast systems and components, and 3) an aid for identifying, comparing, and selecting existing and emerging standards and their relationships. The present five existing service areas are the User Environment, Application Services, Data Services, Integration Services, andInfrastructure Services. Each service area contains sets of technologies/services and each set of technologies contains multiple technology sub-sets that contain specific components /standards. • GSA’s technical standards are expressed as a series of technology components or “bricks”. The bricks provide a convenient standard way to depict the components that fall within the technology sub-sets. The Standards Profileis a listing that contains all of the current GSA IT standards.

  3. GSA Technical Reference Model User Environment End-User Software End-User Utilities End-User Hardware Data Services Application Services Application Server Software Datawarehouse and Business Intelligence Application Development Environment s Data Management Database Technologies Application Systems Integration Services Interchange Technologies Application Integration Collaboration Middleware Infrastructure Services Operating Systems Storage Wireless IT Security Data Center Environment Application Server Hardware Network Infrastructure Infrastructure Management Directory Services Electronic Messaging Voice

  4. GSA Service Areas and Sets of Technologies User Environment End-User Software End-User Utilities End-User Hardware Service Area Data Services Application Services Application Server Software Datawarehouse and Business Intelligence Application Development Environment s Data Management Database Technologies Application Systems Integration Services Interchange Technologies Communications Application Integration Middleware Technology Set Infrastructure Services Operating Systems Wireless IT Security Storage Data Center Environment Electronic Messaging Network Infrastructure Application Server Hardware Infrastructure Management Directory Services Voice

  5. GSA Sub-Sets of Technologies and Components Technology Set Infrastructure Services Operating Systems IT Security Data Center Environment Storage Wireless Infrastructure Management Network Infrastructure Application Server Hardware Electronic Messaging Directory Services Voice Technology Sub-Set (Service) Operating Systems Enterprise Server OS Application Server OS Desktop OS Technology Components (Contains Specific Standards) Enterprise Server OS IBM AIX v4.3.3 Sun Solaris v8 MS Server OS

  6. Application View of Technologies Used User Environment Hardware Software Utilities Data Services Application Services Datawarehouse and Business Intelligence Application Systems Database Technologies Application Server Software Integration Services Middleware Interchange Infrastructure Services Data Center Environment Operating Systems Storage Security Network Infrastructure Infrastructure Management Directory Services • An application combines some or all of our technical components. • For example - an application wherein a user creates a report from data contained in a datawarehouse would use many but not all of the components in these technical sets.

  7. GSA Architectural “BRICK” Format • Definition: • GSA Approved Standard – Any product or technical standard in use that has been approved by the ITAPC. • GSA Tactical Direction – Planned direction for a product or technical standard approved by the ITAPC for use in the next two (2) years. • GSA Strategic Direction – Anticipated direction for a product or technical standard approved by the ITAPC for use in the next two (2) to five (5) years. • In Containment – Any product or technical standard in use that is not a ITAPC / GSA Approved Standard or does not have a ITAPC / GSA Approved Waiver, must be placed in containment. A product or technical standard in containment my continue to be used, however, no new purchases should be made and every effort should be made to replace it with the GSA Approved Standard. Include the product/technical standard name, date placed into containment, and a projected retirement date. • Retired – Do Not Use.Replace immediately with a GSA Approved Standard. Include the product/technical standard name and date that it is to be removed from inventory. • GSA Approved Waivers and Additional Supporting Information – Any notes that are necessary including GSA Approved Waivers and the date the waiver was approved.

  8. Brick Layout for Information Technology Standards Author: C. Bowers, 202-501-3831 ITAPC Approved; MMM YYYY GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) In Containment (Product / Date /Projected Retirement) Retired (Product / Date) GSA Approved Waivers and Additional Supporting Information CIO POC: C. Bowers Responsible Group: Desktop Subcommittee

  9. Technical Reference Model Index(Information Technology Standards) • SERVICE AREA SERVICES ITAPC APPROVED • User Environment:Intel Server, Laptop, and Desktop HardwareApril2004 • Thin ClientApril2004 • Personal ProductivityJune 2004 • Desktop UtilitiesApril2004 • Web BrowserApril2004 • Application Services:Application Technologies Sep 2003 • WEB Hosting InfrastructureApr 2003 • Digital Document Technology April2004

  10. Technology Architecture Index (cont’d)(Information Technology Standards) • SERVICE AREA SERVICES ITAPC APPROVED • Data Services:Database Management SystemsApril2004 • Data WarehousingApril2004 • Business Intelligence ToolsJuly 2003 • Integration Services:EAI (Intra-Enterprise)Jul 2003 • EAI (Web Services)Jul 2003 • Workgroup Computing April2004 • Remote AccessApril2004 • Personal Digital Assistant April 2004 • Infrastructure Services:Desktop Operating SystemApril2004 • Application/Data Server Operating SystemsApril2004 • Network Operating System April2004

  11. Technology Architecture Index (cont’d)(Information Technology Standards) • SERVICE AREA SERVICES ITAPC APPROVED • Infrastructure Services (cont’d):Wide Area Network TopologyApril2004 • Wide Area Network HardwareApril2004 • Structured Cabling/LAN TopologyApril2004 • Directory ServicesApril2004 • Information Technology SecurityJuly2004 • Electronic MessagingApril2004 • Storage ManagementApril2004 • Enterprise-wide Resource Management Pending • Wireless LANs Pending • Voice over Internet Protocol (VoIP)April2004 • Knowledge ManagementApril2004 • Customer Relationship ManagementApril2004

  12. Intel Server, Laptop, and Desktop Hardware • Definition: • Machinery and equipment associated with application servers, laptop and desktop personal computing devices. A server or personal computer is composed of both hardware and software. The software provides the instructions, and the hardware performs the processing. • GSA has an agency-wide Blanket Purchase Agreement (BPA) for purchase of computer hardware. The goal of the BPA is to remain current with the needs of the agency.In GSA all server, laptop, and desktop personal computers are to be procured from the BPA unless an exception is specifically granted. • Any exception to procuring servers, laptops, and desktop personal computers outside of the BPA requires a waiver from the OCIO before procurement.

  13. Intel Server, Laptop, and Desktop Hardware Author: E. Reynolds, 202 501 4423 ITAPC Approved – April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Direction as dictated by BPA (http://hwbpa.gsa.gov) Direction as dictated by BPA (http://hwbpa.gsa.gov) Direction as dictated by BPA (http://hwbpa.gsa.gov) In Containment (Product / Date /Projected Retirement) Retired (Product / Date) Servers: Anything over 4 years old / retire at 5 years Laptops: Anything over 3 years old / retire at 4 years Desktops: Anything over 3 years old / retire at 4 years Servers: Anything over 5 years old Laptops: Anything over 4 years old Desktops: Anything over 4 years old GSA Approved Waivers and Additional Supporting Information • The BPA is the agency wide vehicle for purchase of computer hardware. The goal of the BPA is to remain current with the needs of the agency. As such, the BPA offerings should indicate the baseline and strategic/tactical direction of the desktop hardware. • The above “In Containment” and “Retired” timeframes refer to primary hardware • Follow-up – Tablet PCs – add requirements to the new BPA CIO POC: L. Neifert Responsible Group: End-User Computing Division, OCIO

  14. Thin Client • Definition: Server-centric, not device-centric • Thin Client: What It Is • A thin-client application is a logical construct, not a physical one. Thin-client desktop computing is server-centric. The applications are executed on the server and do not require client-resident installation; the graphical user interface and some application logic may be rendered to the client. • Thin-client desktop computing also includes browser and Java-based applications where the applications are centralized on servers, but some of the presentation logic and some application logic may be distributed to the client. • Thin Client: What It Is Not • A common misperception is that a thin-client application is device-centric and requires a thin-client device, like a Windows terminal. Thin-client applications do not require a thin-client device. Choice of desktop device is secondary. The typical thin-client device is a PC configured with “fat client” applications and with access to thin-client applications. If enterprises are deploying a true thin-client device, all the applications must be deployed as thin-client applications.

  15. Thin Client ITAPC Approved: April 2004 Author: K. Rice, 202-501-0496 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Windows 2003 Terminal Services Metaframe Presentation Server Windows 2000 Terminal Services Metaframe Presentation Server Metaframe Presentation Server Longhorn Terminal Services In Containment (Product / Date /Projected Retirement) Retired (Product / Date) Metaframe 1.8 – June 2005 (retirement) Windows NT 4 TSE (as of January 2004) / June 2005 GSA Approved Waivers and Additional Supporting Information Some GSA organizations are not interested in upgrading beyond Metaframe 1.8 but concur in placing it in containment. NT4 TSE is no longer sold, and support stopped in January 2004 from Microsoft. Metaframe 1.8 is no longer sold but LIMITED support still exists. CIO POC: C. Bowers Responsible Group: Desktop Subcommittee

  16. Personal Productivity • Definition: • Technology for enabling personal productivity, such as the desktop Office Suite including word processing, spreadsheets, and presentation preparation. This also includes all other personal productivity software that the ITAPC has approved as GSA Standards and is included on the official GSA Desktop Image.

  17. Personal Productivity Author: K. Rice 202 501 0496 ITAPC Approved: June 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Microsoft Office 2003 MS Project 2003; Visio 2003; Microsoft Office 2003 MS Project 2003; Visio 2003; Microsoft Office X MS Project X; Visio X; In Containment (Product / Date /Projected Retirement) Retired (Product / Date) All earlier versions of MS Office, except MS Access 97 are retired as of 10/01/01. Access 97 retired as of 1/1/03 MS Project 97 and any earlier MS Project applications as of 10/1/01. Office 2000 to be placed in containment on 9/13/04 GSA Approved Waivers and Additional Supporting Information • The personal productivity suite has long been connected with the current desktop operating system. As such, the personal productivity suite closely mirrors the desktop operating brick. • An approved exception is the use of WordPerfect and Lotus 1-2-3 for communication with certain external agencies. CIO POC: C. Bowers Responsible Group: Desktop Subcommittee

  18. Desktop Utilities • Definition: • Technology for enabling personal productivity besides the desktop Office Suite. This includes all other personal productivity software that the ITAPC has approved as GSA Standards. It also contains the standards for handheld devices.

  19. Desktop Utilities Author: K. Rice 202 501 0496 ITAPC Approved: April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Misc: Real Player X; Win Zip X ; Windows Media Player Handheld Synchronization:: Palm Pilot (Palm Desktop, EasySync, Intellisync) ; Windows CE (ActiveSync); Blackberry (Blackberry Desktop Software, WIC) ; Lotus EasySync Document Viewer: AutoCad VoloViewer, Visio Viewer X, Adobe Acrobat Reader X Misc: Real Player G2; Win Zip 9.0; Windows Media Player Handheld Synchronization: Palm Pilot (Palm Desktop, EasySync, Intellisync) ; Windows CE (ActiveSync); Blackberry (Blackberry Desktop Software, WIC); Lotus EasySync Document Viewer: AutoCad VoloViewer, Visio Viewer 2003, Adobe Acrobat Reader 6.x Misc: Real Player X; Win Zip X ; Windows Media Player Handheld Synchronization:: Palm Pilot (Palm Desktop, EasySync, Intellisync) ; Windows CE (ActiveSync); Blackberry (Blackberry Desktop Software, WIC) ; Lotus EasySync Document Viewer: AutoCad VoloViewer, Visio Viewer 2003, Adobe Acrobat Reader 6.x In Containment (Product / Date /Projected Retirement) Retired (Product / Date) All previous versions of Real Player, Win Zip, and Visio as of 1/01/03. Inovie Team Center as of 10/1/01; GSA Approved Waivers and Additional Supporting Information Desktop utilities were previously shown as part of the Personal Productivity “brick”, they are ITAPC approved GSA Standards. Inclusion of Visio and Project Management on this brick will be revisited in the next FY. Follow-up – research FTP capabilities and utilities – Possible solution: WS FTP CIO POC: C. Bowers Responsible Group: Desktop Subcommittee

  20. Web Browser • Definition: • A software program on a client system used to locate and display Hypertext Markup Language (HTML) documents on an intranet or the Internet. Browsers are most often used to access World Wide Web pages. Most browsers can display graphics and photographs as well as text, and can present multi-media information, including sound and video, which may require additional applets called plug-ins. Netscape Navigator and Microsoft Internet Explorer are examples of browsers.

  21. Web Browser ITAPC Approved: April 2004 Author: K. Rice 202 501 0496 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) MS Internet Explorer 6.0 MS Internet Explorer 6.X MS Internet Explorer X.X In Containment (Product / Date /Projected Retirement) Retired (Product / Date) MS IE 5.x placed in containment (effective 15 Jun 2003) All versions of Netscape (effective Nov 2000). All versions of IE before 5.0 (effective 15 Jun 2002). GSA Approved Waivers and Additional Supporting Information • Currently, the web browser is heavily dependant on the OS in which it operates. Currently IE does the best job with the standard GSA OS and is widely accepted in the www environment. Netscape can only be used with an approved waiver from the Desktop Standards Subcommittee. • An approved exception is for developers to use other browsers to support external clients. CIO POC: C. Bowers Responsible Group: Desktop Subcommittee

  22. Application Technologies • Definition: • This element focuses on the specification for the tools and languages associated with the development of new applications, both large (enterprise) and smaller (workgroup). Such applications may or may not involve WEB access.

  23. Application Technologies Author: C. Bowers, 202-501-3831 ITAPC Approved; Apr 2003 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Languages C++; C# PERL;Java: Java Script HTML; XML; Tools -MS Visual StudioNET; -J-Builder; Eclipse; -WSAD* -Oracle Development Suite -Lotus Domino Designer - Business Objects Designer / SDK Tools MS Visual Studio.Net; J-Builder; Oracle Development Suite ; Business Objects Designer / SDK Languages Java; Java Script, PERL; C#, C++; HTML; XML; Tools MS Visual Studio.NET; J-Builder Oracle Development Suite Business Objects Designer Business Objects SDK SAP Enterprise Lotus Domino Designer Languages PERL HTML; CGI; Java; Java Script; C++; C;XML; In Containment (Product / Date /Projected Retirement) Retired (Product / Date) APC: Clipper, 9/11/03 Power-J, 9/11/03 PowerBuilder; 9/11/03 / May 2008 COBOL; May 2004 / May 2010 Visual Basic 6 & earlier; May 2004 / 2007 GSA Approved Waivers and Additional Supporting Information This brick was de-conflicted (compared) to the Web Hosting brick to eliminate redundancy on 9/8/2003. *WSAD = Websphere Solution Application Development Follow-up – determine which Oracle and SAP development tools are being used within GSA Follow-up – determine the decision to explicitly use or not use Visual Basic .NET Follow-up – determine the usage of PERL Follow-up – look for consolidation opportunities with J-Builder, WSAD and Oracle J-Developer Follow-up – determine future strategic direction regarding development in Java vs. .NET – Where and how each is used. Follow-up – Lotus -- evaluation and reassessment in conjunction with collaboration platforms by May 2006. A separate and earlier decsion could be made about LotusScript and @function use before deciding on environment, since IBM’s direction is to deprecate these development languages. Follow-up – determine positioning of C/C++ and its usage CIO POC: C. Bowers Responsible Group: Enterprise Architecture Subcommittee, OCIO

  24. Web Hosting Infrastructure • Definition: • Technologies and infrastructure elements associated with development and support of web-based applications and electronic commerce as it pertains to web server and application server capabilities. Examples include Web Hosting Services, Enterprise Information Portals, Application servers. • Web content management (WCM) infrastructure is the core platform for enabling related technologies such as personalization, multi-channel output, and e-commerce. Adoption of WCM is a prerequisite for a competitive global Web site and enterprise portals for all but trailing-edge enterprises.

  25. Web Hosting Infrastructure ITAPC Approved – Author: Mark Kaprow (202) 501-2886 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Netscape Enterprise Server 3.x, iPlanet 4.x; Sun One Web Server 6.x Oracle 8i Enterprise Edition IBM Lotus Domino 5.x, 6.x Microsoft IIS 4.x, 5.x Apache 1.3.x, 2.0.x Analog 5.x, Zeus 4.x Broadvision 7.x Verity Ultraseek 4.x, 5.x Webtrends 6.x, J2EE ColdFusion 5.x Sun One Web Server 6.x Oracle 9iAS / 10g Enterprise Edition IBM Lotus Domino 6.x MS IIS 5.x, Apache 2.x, Zeus 4.x Verity Ultraseek 6.x Verity Response, Verity K2 Webtrends 7.x Broadvision 7.x Weblogic J2EE ColdFusion MX Sun One Web Server Oracle Enterprise Edition IBM Lotus Domino 7.x Microsoft IIS, Apache, Zeus Verity Ultraseek Verity Response, Verity K2 Webtrends, Broadvision Weblogic Web Services; J2EE ColdFusion X In Containment (Product / Date /Projected Retirement) Retired (Product / Date) O’Reilly Website (1999) Live-Wire Connect (2000) Aria (Fall 2002) Domino 4.x (April 2003) Webtrends 5.x (March 2004) Netscape Enterprise Server 3.x (2002 / September 2004) Analog 4.x (January 2003 / September 2005) Verity Ultraseek 4.x (March 2004 / September 2004) IBM Lotus Domino 5.x (March 2004 / December 2004) Microsoft IIS 4.x (April 2003 / September 2004) iPlanet 4.x (April 2003 / December 2006) Apache 1.3.x (April 2003 / September 2008) Broadvision 6.x (October 2003 / October 2004) GSA Approved Waivers and Additional Supporting Information For clarification - Netscape Enterprise Server became iPlanet in version 4.x and then Sun One Web Server 6.x when it changed vendors. Follow-up - need to develop a strategic direction and consolidation approach. Potential categories within the standards above include web servers, application servers, web site measurement, search, content management CIO POC: Sally Perry Responsible Group: IOA Division, OCIO

  26. Digital Document Technology • Definition: • This element has evolved into Integrated Document Management (IDM) software. It is a type of middleware for organizing electronic documents; managing content; enabling secure access to documents and unstructured data; routing documents and automating related tasks; and facilitating document distribution. IDM products provide functionality for storing, locating, and retrieving information throughout the document's life cycle; i.e., from the time it is created to the time it is archived to offline storage media. Many current IDM vendors and products take this life-cycle approach by addressing the following processes: authoring/creation, review and approval, distribution, and archiving.

  27. Digital Document Technology Author: K. Rice, 202-501-0496 ITAPC Approved; April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Documentum; Adobe Acrobat Lotus Notes (.nsf); Internet Quorum (Correspondence Tracking) Lasherfishe Documentum; Adobe Acrobat Lotus Notes (.nsf); Internet Quorum (Correspondence Tracking) Lasherfishe Documentum; Adobe Acrobat Lotus Notes (.nsf); Internet Quorum (Correspondence Tracking) Lasherfishe In Containment (Product / Date /Projected Retirement) Retired (Product / Date) Adobe Acrobat 5.x / May 2004 / May 2005 Adobe Acrobat 4.x as of 10/01/01 GSA Approved Waivers and Additional Supporting Information • Requirement of the Paperwork Elimination Act. File formats are governed by Draft OAD 1820.2 “Managing Electronic Records.” • As the need arises – determine specific GSA requirements for specifying standards for content management and records management • Follow-up – Notes/.nsf evaluation and reassessment in conjunction with collaboration platforms by May 2006 CIO POC: C. Bowers Responsible Group: Desktop Subcommittee

  28. Knowledge Management • Definition: • A discipline that promotes a collaborative and integrated approach to the creation, capture, organization, access and use of an enterprise’s information assets. This includes databases, documents and, most important, the un-captured, tacit expertise and experience of individual workers. • The Gartner KM Process Framework defines five KM activities: • Create: The activities that result in new knowledge. • Capture: The activities that enable capture and representation of tacit knowledge in explicit form, thereby moving knowledge from the individual and making it available across the enterprise. • Organize: The activities that classify and categorize knowledge for storage and retrieval purposes. This includes maintenance of knowledge data as well as the indices, maps and processes that manage it. • Access: The activities through which knowledge is disseminated to or requested by users • Use: The application of knowledge to work activities, decisions and opportunities. Use is recursive, i.e., it generates feedback that affects the other activities, and this feedback may be injected into the KM process through any of the other four activities.

  29. Knowledge Management Author: C. Bowers, 202-501-3831 ITAPC Approved; April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) In Containment (Product / Date /Projected Retirement) Retired (Product / Date) GSA Approved Waivers and Additional Supporting Information • There is no current GSA ITAPC approved standard for Knowledge Management • Any GSA Service of Staff Office considering development of a Knowledge Management System must present their proposed system to the ITAPC for approval and possible acceptance as a GSA Information Technology Standard CIO POC: C. Bowers Responsible Group: Enterprise Architecture Office, OCIO

  30. Customer Relationship Management • Definition: • Customer Relationship Management - CRM refers to the concept of moving ownership of the customer up to the enterprise level and away from individual departments and/or lines of business (LOBs). These departments/LOBs are still responsible for customer interactions, but the enterprise is responsible for the customer. • To accomplish CRM, the enterprise brings automation to each customer touch point (i.e., initiatives in sales force automation, the Internet, point of sale, and call/contact centers are all pieces of CRM, but they are not substitutes for it).CRM is: • composed of tactics, processes and behaviors; • not a technology; technology is the enabler of strategy, tactics, processes, and skill sets. • the technology is implemented tactically. • an initiative that causes fundamental changes in the organizational structure — from departmental/LOB (internal) to functional (customer) view. • very public: it is centered around your customer and anything that “goes wrong” becomes visible very quickly.

  31. Customer Relationship Management Author: C. Bowers, 202-501-3831 ITAPC Approved; April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) • Siebel Enterprise Server V7.0.4; • Actuate e.reporting • Firstlogic • Fulcrum • Visual Mining • Customer Profile System (CPS) Siebel Analytics V7.5/3GS; SAP Customer Profile System (CPS) SAP Customer Profile System (CPS) Siebel X In Containment (Product / Date /Projected Retirement) Retired (Product / Date) GSA Approved Waivers and Additional Supporting Information Follow-up – Is SAP going to be used (strategic direction) – what types of CRM functions will be used in SAP? Follow-up – clarify CPS’ role in relation to Siebel Follow-up – clarify status, direction, and location (where in brick) for the use of Actuate e.reporting, Firstlogic, Fulcrum, and Visual Mining CIO POC: C. Bowers Responsible Group: Enterprise Architecture Office, OCIO

  32. Database Management Systems • Definition: • A Database Management System (DBMS) is a program (software package) that enables end-users or application programmers to create and access data in a database. The DBMS manages user requests (and requests from other programs) so that users and other programs are free from having to understand where the data is physically located on storage media and, in a multi-user system, who else may also be accessing the data. In handling user requests, the DBMS ensures the integrity of the data (that is, making sure it continues to be accessible and is consistently organized as intended) and security (making sure only those with access privileges can access the data). A DBMS manages data in databases rather than files in file systems.

  33. Database Management Systems Author: C. Bowers, 202-501-3831 ITAPC Approved: April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) MySQL; Oracle DB; MS SQL Server; Netweaver; Notes*; Sybase; DMSII Desktop: MS Access MySQL; Oracle; MS SQL Server; Netweaver; Notes*; Sybase; DMSII Desktop: MS Access MySQL; Oracle; MS SQL Server; Netweaver; Notes*; Sybase; DMSII Desktop: MS Access In Containment (Product / Date /Projected Retirement) Retired (Product / Date) Oracle 8.x, 2004; FoxPro, 2004 Progress, May 2004 / May 2006 GSA Approved Waivers and Additional Supporting Information *Not suitable for high volume transactions – not relational. Follow-up – Notes as a database – evaluation and reassessment in conjunction with collaboration platforms and electronic messaging by May 2006 CIO POC: C. Bowers Responsible Group: Enterprise Architecture Division, OCIO

  34. Data Warehousing • Definition: • A storage architecture designed to hold data extracted from transaction systems, operational data stores and external sources. The warehouse then combines that data in an aggregate, summary form suitable for enterprise-wide data analysis and reporting for predefined business needs. The five components of a data warehouse are production data sources, data extraction and conversion, the data warehouse database management system, and data warehouse administration. • Note: for our purposes, Business Intelligence is treated as a separate architecture element.

  35. Data Warehousing Author: C. Bowers, 202-501-3831 ITAPC Approved: April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) DBMS: See DBMS standard Extract, Transformation, Load (ETL) tool: Informatica Power Center 6.0, SAP, ADT Data Modeling: System Architect, AllFusion Data Modeling Suite (previously known as Erwin) Metadata Management: Informatica, Advantage Data Transformer Enterprise Metadata Edition (ADT EME) DBMS: See DBMS standard ETL: Informatica Power Center, SAP, Advantage Data Transformer (ADT) Data Modeling: System Architect, AllFusion Data Modeling Suite Metadata Management: Informatica; Oracle, ADT EME DBMS: See DBMS standard Extract, Transformation, Load (ETL) tool: Informatica Power Center 6.0, SAP, ADT Data Modeling: System Architect, AllFusion Data Modeling Suite (previously known as Erwin) Metadata Management: Informatica, Advantage Data Transformer Enterprise Metadata Edition (ADT EME) In Containment (Product / Date /Projected Retirement) Retired (Product / Date) DecisionBase(CA); (May, 2004/May, 2005) Sybase inbuilt; (May, 2004/May, 2005) DTS for SQL Server; (May, 2004/May, 2005) Sybase PowerDesigner for DW (May, 2004/May, 2005) Oracle8 all versions -- Dec., 2003 (for data warehousing) GSA Approved Waivers and Additional Supporting Information CIO POC: C. Bowers Responsible Group: Enterprise Architecture Division, OCIO

  36. Business Intelligence Tools • Definition: • An interactive process for exploring and analyzing structured, domain-specific information (often stored in data warehouses) to discern trends or patterns, thereby deriving insights and drawing conclusions. The BI process includes communicating findings and effecting change. Domains include customers, suppliers, products, services and competitors. Has the following attributes: web-enabled multidimensional analysis; data transformation capability; data integration capability; support Oracle & Access & SQL Server; provide ODBC & SQL & DB2 interfaces; suited to both Windows and UNIX environments; provide download capability to Excel.

  37. Business Intelligence Tools Author: C. Bowers, 202-501-3831 ITAPC Approved: GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Pilot Bus. Analyzer (M); PilotWorks (GPM); Oracle Discover Tools (QR); Oracle BI Beans (M); URSA (QR); Business Objects (QR); (Crystal Reports (QR)) Oracle Discover Tools (QR); Oracle BI Beans (M); Business Objects (QR); Crystal Reports (QR); PilotWorks (GPM); Oracle Discover Tools (QR); URSA (QR); (for Unisys ClearPath) Business Objects (QR); (Crystal Reports (QR)) In Containment (Product / Date /Projected Retirement) Retired (Product / Date) CA Decision Base, 12 Jun 2003; Hyperion, 12 Jun 2003; Pilot Decision Support Suite, 30 Nov 03 Pilot Business Analyzer (M); PilotWorks (GPM); (status TBD) Primavera (pending evaluation) GSA Approved Waivers and Additional Supporting Information Conference Notes: Primavera, wInsight &Dekker are leading EVM tools. See “Task2GSA EVM Tool Survey.” – need to establish EVM vendor PilotWorks -- Pilot is specializing in organizational performance management. It is the only web-enabled PM system with drill to supporting stats. It won the Intelligent Enterprise Readers' Choice Award as the "Best Business Performance Monitoring & Management Environment.“ (QR) Query Resource, (EVM) Earned Value Management Note: Crystal Reports purchased by Business Objects, which will result in a combined tool set in the future CIO POC: C. Bowers Responsible Group: Enterprise Architecture Division, OCIO

  38. Enterprise Application Integration (EAI)(Intra-Enterprise Middleware) Author, G.Thomas • Definition: • Traditional EAI oriented middleware includes Application Servers and MOM tools. Application Servers encapsulate presentation controllers, business logic, and resource tier data access. MOM tools are typically used for operational data store synchronization, and synchronous request/reply or asynchronous pub/sub application to application integration. • Together, these tools provide a framework that includes components to handle the data movement and data transformation within business processes, and the specific adapters that provide access to the information residing in particular applications or other data sources. • The goal of EAI is to allow a company to manage integration as one system rather than trying to administer ‘point to point’ middleware scattered about the enterprise's IT infrastructure. • EAI is in flux as Application Server and MOM vendors repurpose their tools to incorporate technologies that facilitate long running, transaction oriented workflows that span enterprise boundaries, which leads to the next ‘Middleware – Web Services’ Brick.

  39. Enterprise Application Integration (EAI) (Intra-Enterprise Middleware) Author: G.Thomas, 202-219-1979 ITAPC Approved; Jul 2003 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Native SQL API; JDBC; Sybase Enterprise Portal/ EAS; Open A ODBC; Open A JDBC; DQ Broker; Tuxedo; Oracle 9iAS/Portal • Commercial: BEA WebLogic; IBM WebSphere; MS.NET; Sybase Enterprise Portal/ EAS; Tuxedo; Oracle 9iAS/10g/Portal • Open Source: • JBOSS, Tomcat Enterprise Service Bus (ESB) is a standards-based integration backbone that combines messaging, Web services, transformation and intelligent routing to reliably connect and coordinate the interaction of hundreds of application endpoints spanning a global organization. In Containment (Product / Date /Projected Retirement) Retired (Product / Date) Oracle Application Server; Platinum - June 2002 Retrievalware - June 2003 GSA Approved Waivers and Additional Supporting Information • Emphasis should be placed on event driven asynchronous (non-blocking) messaging using the JMS standard in J2EE with XSD payloads so that they may be later deployed via Web service protocols that will secure and reliably route, transform and choreograph message sequences on the externalized ESB. Internally, interoperability with existing EIS systems should be based on JCA. • Follow-up (URGENT) – consider rationalization between this brick, the WEB Hosting brick and the Web Services brick (Possible bricks include Application Server Platforms, EAI Protocols, Content Oriented Website, etc.) • Follow-up (URGENT) – consider the strategy around application server platforms and how much platform functionality GSA needs. – vendors considered should include Oracle, IBM, Microsoft, Sybase, BEA and JBOSS (Open Source). CIO POC: C. Bowers Responsible Group: Enterprise Architecture Office, OCIO

  40. Enterprise Application Integration (EAI) (Web Services) Author, G.Thomas • Definition: • Web Services support the extension of traditional EAI Application Servers and MOM queues as Enterprise Service Bus technologies, which implements a Service Oriented Architecture (SOA) that is the foundation for an IT infrastructure framework based on a logical Publish/Find/Bind/Execute processing model. • SOA emphasizes trans-enterprise interoperability of loosely coupled distributed components whose orchestrated XML message choreographies use open Internet standard transports and protocols. Web Services open standards are the foundation for SOA, moving the focus of IT interoperability from applications to message streams. • The WS-I standards (also part of the TRM) include the basic Web Service standards that make the ‘publish-find-bind’ paradigm possible. Publishers are providers who expose application component interfaces to be discovered or found by component consumers via a component registry, whereupon they can bind to and execute the services listed based on establishing a contractual agreement of their roles in the message sequencing. • OASIS and IBM/MS are driving the set of specifications that are emerging as the SOA/ESB Platform, based on Web Services technologies. Web Service deployment gives rise to a complementary set of Orchestration and QoS Management tools for ESB technologies, which is an emerging and rapidly evolving market space.

  41. Enterprise Application Integration (EAI) (Web Services) Author: G.Thomas, 202-219-1979 ITAPC Approved; Jul 2003 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) • WS-I Basic Profiles • UDDI, (ebXML RIM, WSIL) • WSDL • SOAP • XML/XSD WS-I Extended Profiles Sonic ESB FOSS – JBOSS/Apache SOIP FOSS In Containment (Product / Date /Projected Retirement) Retired (Product / Date) GSA Approved Waivers and Additional Supporting Information • Emphasis should be placed on WS-* stack that externalizes a JMS backbone, implemented with Free and Open Source Software (FOSS). • Follow-up (URGENT) – consider rationalization between this brick, the WEB Hosting brick and the EAI (Intra-Enterprise) brick (see comment on EAI -- Intra-Enterprise Middleware brick) • Follow-up – consider a brick at a standards level as well as an architecture/product level CIO POC: C. Bowers Responsible Group: Enterprise Architecture Office, OCIO

  42. Workgroup Computing • Definition: • This element is a broad one that encompasses applications that deliver capability for group collaboration and light workflow. Much of this functionality (e.g., message transfer agents, directory, gateways, e-mail clients, collaborative tasks, scheduling) is now combined in comprehensive “GroupWare” packages like Microsoft Exchange or Lotus Notes Domino. • Another way to think of this is to roll up to a higher level category: collaborative computing. This generally includes the four elements of: • GroupWare/Collaboration tools Messaging/directory services Electronic document management/workflow E-mail/calendaring/scheduling • Because document management, e-mail/calendar/schedule have been covered elsewhere, this brick will cover only workflow and groupware/collaboration.

  43. Workgroup Computing ITAPC Approved: April 2004 Author: Paul Butler (202) 219-0382 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) IBM Lotus Notes 5.x & 6.x (client) IBM Lotus Domino 5.x & 6.x (server) IBM Lotus SameTime 2.x & 3.x (6.x)* IBM Lotus QuickPlace 2.x & 3.x (6.x)* Accessible FormNet 2.x IBM Lotus Notes 6.x (client) IBM Lotus Domino 6.x (server) IBM Lotus Instant Messaging 6.x* IBM Lotus Web Conferencing 6.x* IBM Lotus Team Workplace 6.x* Accessible FormNet 2.x IBM Lotus Notes 7.x (client) IBM Lotus Domino 7.x (server) IBM Lotus Instant Messaging* IBM Lotus Web Conferencing* IBM Lotus Team Workplace* Accessible FormNet In Containment (Product / Date /Projected Retirement) Retired (Product / Date) Surfer (October 2001) IBM Lotus Notes 4.6.x (client) (June 2003) IBM Lotus Domino 4.6.x (server) (June 2003) IBM Lotus Notes 5.x (March 2004 / December 2004) IBM Lotus Domino 5.x (March 2004 / December 2004) IBM Lotus SameTime 2.x (December 2003 / December 2004) IBM Lotus QuickPlace 2.x (December 2003 / December 2004) GSA Approved Waivers and Additional Supporting Information • IBM Lotus Software has rebranded several of its products. IBM Lotus Quickplace is now referred to as IBM Lotus Team Workplace and IBM Lotus Sametime has been divided into two pieces known as IBM Lotus Instant Messaging (IM/Awareness) and IBM Lotus Web Conferencing. Also, future releases of Notes/Domino extended products, which includes Quickplace and Sametime, are being synchronized with the Domino release numbering scheme to maintain version coordination among products. The above name and numbering changes apply to all future releases of 3.x and above. • Follow-up – evaluation and reassessment of collaboration platforms by May 2006 CIO POC: Sally Perry Responsible Group: IOA Division, OCIO

  44. Remote Access • Definition: • Remote access is the ability to log on to a network from a distant location. Generally, this requires a computer, a modem and remote access software to allow the computer to dial into the network over a telephone line. Remote access can promote productivity and cut costs., employees can retrieve corporate information and use E-mail when they are traveling. • Any employee that works outside the office and uses wide-area networks (WANs) to connect back to a business office to coexist with office counterparts, is also engaged in remote access. The definition applies regardless of the type of network and end connection used, i.e., public switched telephone network, ISDN, value-added network, generic digital subscriber line (xDSL), frame relay, asynchronous transfer mode (ATM), cable modem, private circuit, public Internet, or partner extranet. The definition applies to anyone who formally works in the enterprise supply chain, including employees, partners, customers, suppliers and contractors.

  45. Remote Access ITAPC Approved: April 2004 Author: Dianne Phillips, 202,219-2114 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Cisco AS5350; VPN/ NG FP3; VPN NG , Application Intelligence (AI) R55; Cisco AS5350; Virtual Private Network (VPN) Next Generation (NG ) FP3. Cisco AS5350; VPN/NG/AI R55; In Containment (Product / Date /Projected Retirement) Retired (Product / Date) VPN NG / September 2004 /Retirement is dependant on Testing ,LAN Admin and end-user migration. GSA Approved Waivers and Additional Supporting Information • Follow-up – VPN Smart Gate used by the local area backbone network (discussion/additional detail to be reviewed) • This brick is focused on remote access security • Follow-up – consider expanding standards to include policy or other standards to address other hardware and connectivity. For example, it could set preferred connectivity service providers. CIO POC: G. McNerney Responsible Group: Internetworking Division OCIO

  46. Personal Digital Assistant (PDA) Devices • Definition: • Wireless PDA -- devices that synchronize wirelessly via the cellular network or other wireless networks. • Wired PDA – devices that synchronize via desktop or laptop computer

  47. Personal Digital Assistant (PDA) Devices Author: K. Rice, 202-501-0496 ITAPC Approved; April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Wireless PDA: PBS supported Blackberry devices Wired PDA: Any PalmOS, Windows CE devices Wireless PDA: PBS supported Blackberry devices Wired PDA: Any PalmOS, Windows CE devices Wireless PDA: PBS supported Blackberry devices Wired PDA: Any PalmOS, Windows CE devices In Containment (Product / Date /Projected Retirement) Retired (Product / Date) GSA Approved Waivers and Additional Supporting Information Wireless PDA -- devices that synchronize wirelessly via the cellular network or other wireless networks. Wired PDA – devices that synchronize via desktop or laptop computer The office of the Chief Information Officer (OCIO) and the Federal Technology Service (FTS), are the only two organizations authorized to operate servers to support non-standard and experimental wireless PDA services. Requests for a waiver of this policy must be addressed to the OCIO. CIO POC: C. Bowers Responsible Group: Desktop Subcommittee

  48. Desktop Operating Systems • Definition: • The main control program that runs a “normal office desktop computer” and sets the standard for running desktop application programs. It is the first program loaded when the computer is turned on, and it resides in memory at all times. An operating system is responsible for functions such as memory allocation, managing programs and errors, and directing input and output. It may be developed by the computer vendor or by a third-party independent software vendor.

  49. Desktop Operating System Author: K. Rice 202 501 0496 ITAPC Approved: April 2004 GSA Strategic Direction (2 to 5 Years) GSA Approved Standard (Current) GSA Tactical Direction (Next 2 Years) Windows 2000 and Windows XP Future versions of Microsoft (Longhorn) Windows XP In Containment (Product / Date /Projected Retirement) Retired (Product / Date) Windows ME, Windows 98, MS NT 4.0 are retired effective 1 Oct 2001 Windows 2000 / 13 Sept 2004 / End of product support GSA Approved Waivers and Additional Supporting Information • Other platforms such as MAC OS should only be deployed with a waiver from the Desktop Standards Subcommittee. • This brick applies to GFE including GFE home use. • Follow-up -- set projected retirement for Windows 2000. CIO POC: C. Bowers Responsible Group: Desktop Subcommittee

  50. Application/Data Server Operating System • Definition: • The main control program running on an Application Server or Data Server that sets the standard for running application programs or DBMSs. It is the first program loaded when the server is turned on, and it resides in memory at all times. The operating system is responsible for functions such as memory allocation, managing programs and errors, and directing input and output. It may be developed by the server vendor or by a third-party independent software vendor.

More Related