Database Application Linking and License Agreement by bho25192

VIEWS: 24 PAGES: 28

More Info
									                                                    Functional Evaluation Form
                                                                      Background

Until now, DIR has had no way to help its customers identify products by functionality. DIR's customers currently have to know which publishers make the
type of product they want, and find it through the "Publisher Index” in the DIR Store. DIR is now moving to increase the value of our commodity purchasing
services by enhancing the DIR Store to include a “Functional Index ”.

The Functional Index will include a list of “functional areas” identified by DIR and our customers as being high-priority. The addition of a Functional Index to
the DIR Store will help the customers find key software products by category, and to quickly identify the range of publishers and products offered within a
given functional area.

DIR is committed to making quality products available and easy to find to meet the needs of all sizes of agencies and customers, while fostering greater inter-
operability among the smallest and largest entities.


The Functional Index is intended to list only those products which meet statewide best-practice guidelines for interoperability and security. These guidelines
will be used as criteria in the evaluation process for publishers or resellers wishing to list their products on the Functional Index. See the Functional
Evaluation Form for detailed instructions on how to request that a software product under an active DIR contract be listed on the Functional Index.

Applying best-practice guidelines for statewide interoperability and security is critical as we move toward a greater reliance on shared and outsourced
services. Systems and databases must be inter-operable for State Agencies and other DIR customers to meet the needs of our growing constituent
populations.

In order to be listed on the Functional Index in the DIR Store, products must meet the statewide best-practice guidelines for interoperability and security in
software procurement and development, which include the following 5 criteria. These criteria will be used to select products for inclusion on the Functional
Index:
1. Software must run on at least one of the following Operating Systems: Windows, Unix, Linux, OS390, z/OS, z/Linux.
2. Software must work with at least one of the following Database Management Systems: Oracle, DB2, Teradata, and/or SQL Server.
3. Software must provide either an API and/or standards-based XML / Web Services interface.
4. Software must LDAP compliant for user-management.
5. Software must have application-level authorization for role-specific privileges.

There may also be additional functional requirements relevant to each functional area that will be used in the evaluation process for the Functional Index.
Each Functional Evaluation Form for each functional area will clearly indicate the criteria by which evaluations will be performed.

Once products are selected for inclusion on the Functional Index, vendors may be asked to complete a more detailed technical and architectural
questionnaire. Responses will be linked to the Functional Index listing of the product, and are intended to help our customers make purchasing choices
based not only on functionality, but on the best fit into their existing architecture and infrastructure.

In order to have a product listed on the Functional Index for any defined functional area, Publishers or resellers who currently have an active contract(s) with
DIR for those products must submit a Functional Evaluation Form to DIR.


                                                             5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
                                                 Functional Evaluation Form
                                                                    Instructions
       The Functional Evaluation Form may be completed at any time for any product that is currently under contract through DIR. List each product on
 1
       each relevant functional Area spreadsheet.

       There are 22 Functional Areas currently defined by DIR. In the future, additional Functional Areas will be identified, according to priority and
 2
       relevance as reported by our customers.

       Each Functional Area has a requirements spreadsheet, which should be completed by the contracted publisher or reseller vendor for the
 3
       applicable product(s). Each spreadsheet is structured so that the all relevant products may be listed for each Functional Area.

       "Publisher Index": All publishers currently under DIR contract are listed alphabetically in an index on the DIR Store. Individual products are not
 4     listed. The request to have one or more products also listed on the "Functional Index" (see below) will have no impact on the contract or on the
       "Publisher Index".

       "Functional Index": DIR is adding a "Functional Index" to the traditional DIR Store in 2007, (see background tab for more information). In order to
 5
       have a product listed on the Functional Index, a request must be sumbitted and evaluated by DIR.

       Each product listed on the Functional Evaluation Form will be evaluated for inclusion on the DIR Functional Index based on the Global Technical
 6     Requirements and the Functional Requirements. An answer of NO for a global technical requirement will result in exclusion from the DIR
       Functional Index, but will not affect the existing contract.

       There is some overlap between the Functional areas; in other words, there are similar or same requirements that are repeated in some Functional
       areas. They have been developed to reflect general industry norms and are not meant to be mutually exclusive. If your product addresses more
 6
       than one Functional area, you may list your product on all applicable Functional area spreadsheets, which will make it possible for your product to
       be listed in each relevant Functional Area.

       If the product is part of a suite of products, list the product individually and then indicate the suite to which the product in the column marked
 7
       "suites". This information is only given to help inform the customer.

       The Functional Index will list products, not custom solutions or systems integrations. Similarly, related services will not be listed on the Functional
 8
       Index at this time.

       While products may be listed in more than one functional area, DIR recommends that Functional Index requests are only made for products in
 9     functional areas for which the tool is genuinely and fully applicable. DIR reserves the right to validate the assertions made on the Functional
       Evaluation Form.


       If there are products which are normally bundled or packaged with products that directly address a functional area, they may be described in the
10
       comments field, especially if the ancillary product is required for the functionally-relevant product to function fully.


       Terms such as JSR168, WSRP, MVC Frameworks, Architectural Pattern, and other industry-standard terms can be defined by performing simple
Note
       internet searches.



                                                            5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
                                                                   Requirements For Functional Index

Note: All products must meet Global Technical Requirements in order to be listed on the DIR Functional Index. Additionally, each product will be evaluated
based on the functional requirements listed below for each functional area. Additional information may be requested for products which are approved for a
Functional Area. Answer questions about requirements on the individual Functional Area spreadsheets.

Global Technical Requirements
                                                            1.1.     Does Product run on at least one of the following Operating Systems: Windows, Unix, Linux, OS390, z/OS, z/Linux?
                                                            1.2.     Does Product work with at least one of the following Database Management Systems: Oracle, DB2, Teradata, and/or SQL Server?
                                                            1.3.     Does Product provide either an API and/or standards-based XML / Web Services interface?
1.Global Technical Requirements                             1.4.     Is Product LDAP compliant for user-management?
                                                            1.5.     Does Product have application-level authorization for role-specific privileges?


Functional Areas
Enterprise Governance Domain
                                                            2.1.1.    Does Product support user-defined and prioritized business and technology drivers, including hierarchical levels of strategic
                                                            objectives in multiple categories (e.g. business, technology, IT operations, enterprise workforce and finance)?
                                                            2.1.2.     Does Product allow for weighted strategies for mathematically derived priorities?
                                                            2.1.3.     Does Product allow for risk management to defined strategies, and must support quantitative risk scoring and risk management?
2.1.   Business and IT Strategy Development                 2.1.4.     Does Product allow for constraints to be defined and managed against defined strategies and associated with risks?
                                                            2.1.5 Does Product allow for strategies and constraints to be defined against operational business structures and set performance targets to
                                                            achieve them?


                                                            2.2.1.    Does Product support many-to-many relationships between projects and portfolios?
                                                            2.2.2.    Does Product support project- and portfolio-level resource management and/or matrixed resource management?
2.2.   Program and Project Portfolio Management             2.2.3.    Does Product support many-to-many relationships between projects or portfolios and organizational units or divisions?

                                                            2.3.1.     Does Product support consolidation and allocation of costs for unique services across user-defined organizational units and/or
                                                            divisions using user-defined pricing model?
                                                            2.3.2.     Does Product allow users to define multiple tiers of services with varying costs and capabilities?
                                                            2.3.3.     Does Product be able to manage and consolidate operational information regarding usage of managed services?
2.3.   Billing and Charge Back for IT Service Usage / UCE   2.3.4.     Does Product provide native, customizable usage and other metrics reporting for multiple audiences (business, IT, etc.)?
                                                            2.3.5.     Does Product provide state management of all services through discovery, provisioning and confirmation?
                                                            2.3.6.     Does Product provide a cost allocation capability normalized across all types and levels of asset while defining and managing cost
                                                            and business value over the lifecycle of the assets?


                                                            2.4.1.      Does product support custom, user-defined requirement types?
                                                            2.4.2.      Does product support custom, user-defined attributes, which can be associated with one or more requirement types?
                                                            2.4.3.      Does product support custom, user-defined values for each attribute. Value types must include single-select, multi-select (with user-
                                                            defined values) as well as text, date and numeric types?
                                                            2.4.4.      Does product support parent-child relationships within requirement types?
2.4.   Requirements Management                              2.4.5.      Does product support traceability between requirements?
                                                            2.4.6.      Does product include native, user-customizable reporting capabilities on all aspects of requirements (type, attributes, values, parent-
                                                            child, traceability , etc.)?
                                                            2.4.7.      Does product support multiple user-customizable views of requirements and associated data?
                                                            2.4.8.      Does product support multiple user-customizable views of traceability between requirement types?




                                                                                         5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
                                                       2.5.1.      Does product support creation of multiple user-defined record types for different types of change requests (business, project,
                                                       software, IT ops, etc.)?
                                                       2.5.2.      Does product support creation of multiple user-defined schemas for each record type. Each schema should allow for custom
                                                       attributes and values?
                                                       2.5.3.      Does product support user-based and activity-based change management through the unique change management workflow
                                                       schemas?
                                                       2.5.4.      Does product support custom, user-defined attributes, which can be associated with one or more change request record types?
                                                       2.5.5.      Does product support custom, user-defined values for each attribute. Value types must include single-select, multi-select (with user-
2.5.   Change Management
                                                       defined values) as well as text, date and numeric types?
                                                       2.5.6.      Does product support linking between unique records (of same or different change request record types)?
                                                       2.5.7.      Does product include native, user-customizable reporting capabilities on all aspects of change request records (type, attributes,
                                                       values, linked records, etc.)?
                                                       2.5.8.      Does product support multiple user-customizable views of change request records and associated data?
                                                       2.5.9.      Does product support audit-trail / history of all actions taken on all records?


                                                       2.6.1.     Does product support management and versioning of files, directories and other assets across the development lifecycle?
                                                       2.6.2.     Does product support automated individual workspace management?
                                                       2.6.3.     Does product support parallel development through automatic branching, merging and differencing?
                                                       2.6.4.     Does product support transparent, real-time access to files and directories?
2.6.   Configuration Management                        2.6.5.     Does product support leaving and returning to the network (disconnected usage)?
                                                       2.6.6.     Does product support customizable build and release management?
                                                       2.6.7.     Does product support local, remote and web access to Productity?


                                                       2.7.1.     Extract, Transform, Load (ETL) Technology: Does product support extract, transformation, and load of operational data into a
                                                       central data warehouse?
                                                       2.7.2.     Enterprise Information Integration (EII) Technology (on demand pull): Does product support user-creation of an integrated view of
                                                       the data residing in heterogeneous data sources with semantic mapping?
2.7.   Business Intelligence / Data Warehouse          2.7.3.     Enterprise Information Integration (EII) Technology (on demand push): Does product support user queries of the the integrated view
                                                       to access the integrated data from the heterogeneous sources at the near real time?
                                                       2.7.4.     Business Activity Monitoring (BAM) Technology: Does product populate the data warehouse with information at real time when pre-
                                                       defined business critical events happened in the operational systems?

Business Architecture Governance Domain
3.1.   Business Modeling and Management                3.1.1.     Does product provide the ability to visually model with Unified Modeling Language (UML) business patterns, models, processes,
                                                       organizations, workflows, etc?
                                                       3.1.2.     Does product provide the enterprise business planners the ability to define business structures associated with a business strategy?
                                                       3.1.3.     Does product enable the enterprise business planners to prioritize business structures based on strategies, risks and constraints
                                                       defined during strategy development?
                                                       3.1.4.     Does product enable the enterprise business planners to assign performance measures against the modeled business structures?
                                                       3.1.5.     Does product enable the enterprise business planners to model operational lifecycles for the business structures?
                                                       3.1.6.     Does product enable the enterprise business planners to assign cost parameters across the lifecycle of the modeled business
                                                       structures?




3.2.   Business Monitoring and Integrated Dashboards   3.2.1.     Does product provide out of the box dashboards that provide baseline metrics for defined strategies and modeled business
                                                       structures and their associated operational lifecycles?
                                                       3.2.2.     Does product provide ability to perform data mining and analysis in real time on performance measure which are linked across
                                                       business and IT enterprise models, including real time assessment of how performance is mapped to individual enterprise asset types
                                                       (including business structure elements) over operational life cycle?
                                                       3.2.3.     Does product provide the capability to for the Enterprise to set control points which will activate corrective action and hence decision
                                                       making if desired performance benchmarks are not meeting their targets?
                                                       3.2.4.     Does product provide ability to view aggregate data at the performance framework levels including Key Performance Indicators and
                                                       Service Level Agreements that are mapped across Business and IT?
                                                       3.2.5.     Does product provide ability to analyze project, program, or divisional level data rolled up into strategy and performance status
                                                       scorecards based on configurable metrics including financial, schedule, resource, scope and quality control?
                                                       3.2.6.     Does product provide ability to standardize metrics and monitor performance management portfolio of KPI’s and SLA’s?




                                                                                    5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
3.3.   Business Analysis and Transformation Management   3.3.1.     Does product allow the enterprise to set business and IT goals and targets and develop transformation roadmaps?
                                                         3.3.2.     Does product allow the enterprise to define interim maturity steps in the transformation roadmaps, and detail how these steps
                                                         provide for an eventual realization of an enterprise strategy?
                                                         3.3.3.     Does product allow the enterprise to define a transformation framework where all dimensions of a the enterprise performance and
                                                         strategy are mapped in an integrated framework?


3.4.   Business Services Portfolio Management            3.4.1.       Does product provide the ability to define business capabilities as services by aggregating and mapping different asset types?
                                                         3.4.2.       Does product provide a collaborative approach to business services portfolio development across the enterprise?
                                                         3.4.3.       Does product manage these business services within customizable services portfolios that are mapped to business and IT strategic
                                                         initiatives?

3.5.   Content Management                                3.5.1.    Does product include document library services (for example, check-in/checkout, version control and document-level security)?
                                                         3.5.2.    Does product include document-centric collaboration capabilities — document sharing, project team support, support for ad hoc,
                                                         threaded discussions regarding documents?
                                                         3.5.3.    Does product include workflow capabilities?
                                                         3.5.4.    Does product include records management capabilities?

3.6.   Business Process Outsourcing Management           3.6.1.     Does product allow for contract and service agreement mapping, regardless of what system or organizational unit is responsible for
                                                         the contract management (unique from the service and service performance management)?
                                                         3.6.2.     Does product allow for detailed service and service performance definition?
                                                         3.6.3.    Does product provide for the development of pricing/cost frameworks associated with the services?
                                                         3.6.4.     Does product provide for reporting against agreement status and performance framework?
                                                         3.6.5.     Does product provide for definition of all deliverables, milestones and schedules associated with the agreement?


Technical Architecture Governance Domain
4.1.   Technical Architecture Modeling and Management    4.1.1.    Does product include visual modeling design tool for software components?
                                                         4.1.2.    Does product include visual modeling design tool for architectural patterns?
                                                         4.1.3.    Does product include visual modeling design tool for architectural environments?
                                                         4.1.4.    Does product include library of searchable software components or asset browser for accessing reusable assets?
                                                         4.1.5.    Does product include inventory of searchable architectural patterns?
                                                         4.1.6.    Does product search engine offer capabilities ranging from simple keyword searches to advanced, model-based searches?
                                                         4.1.7.    Does product track assets and patterns at an organization-level and a project-level architecture?
                                                         4.1.8.    Does product integrate with leading modeling tools and integrated development environments?
                                                         4.1.9.    Does product support federated repositories ?
                                                         4.1.10. Does product provide a pre-populated and user editable library with content regarding best practices or standards for patterns,
                                                         products, architectures or other asset types. Simplified diagramming using free-form diagrams, topic diagrams, and browse diagrams?
                                                         4.1.11. Does product support UML Class diagram editing for Java, Enterprise Java Beans, and Database objects?
                                                         4.1.12. Does product include IE and IDEF diagram editor for Database objects (ER Modeling)?



4.2.   Application Portfolio Management                  4.2.1.      Does product include a taxonomy structure that is flexible and user customizable?
                                                         4.2.2.      Does product allow users to develop and maintain a comprehensive inventory of all applications?
                                                         4.2.3.     Does product include a flexible and user customizable model of standard application portfolio elements, including applications,
                                                         technical architecture, hardware, operating systems and their attributes?
                                                         4.2.4.      Does product allow for flexible user creation and customization of record types and attributes. Examples of records types and
                                                         attributes include: name, description, state, cost, user, owner, funding source, etc.)?
                                                         4.2.5.      Does product support storage and links for artifacts (e.g .doc, .xls, .pdf, URL)?
                                                         4.2.6.      Does product support versioning of portfolio elements?
                                                         4.2.7.      Does product have import/export capabilities (e.g. Excel, .csv, xml)?

4.3.   Business Services Registry                        4.3.1.   Does product include a taxonomy structure that is flexible and customizable?
                                                         4.3.2.   Does product support effective registry management including federated administration?
                                                         4.3.3.   Does product manage approval processes for the publication and discovery of services?
                                                         4.3.4.   Does product support versioning and lifecycle management of services?
                                                         4.3.5.   Does product support UDDI standards?
                                                         4.3.6.   Does product offer search capabilities ranging from simple keyword searches to advanced services searches?




                                                                                     5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
4.4.   Enterprise Service Bus                           4.4.1.   Does product ensure location transparency from the Client Application's perspective?
                                                        4.4.2.   Does product include version handling?
                                                        4.4.3.   Does product include service invocation monitoring and auditing?
                                                        4.4.4.   Does product be highly configurable and able to handle multiple test environments?
                                                        4.4.5.   Does product utilize an externalized configuration file for easy modification and scripting?
                                                        4.4.6.   Does product include web-services security?
                                                        4.4.7.   Does product include service registry services (either publish or push)?
                                                        4.4.8.   Does product include content based routing rules?
                                                        4.4.9.   Does product utilize synchronous and asynchronous communication?


IT Operations Governance Domain
5.1.   IT Asset Discovery                               5.1.1. Does product discover, catalog and version hardware and device names and components including but not limited to: CPU, RAM,
                                                        available and used storage, network and storage interfaces (initial discovery)?
                                                        5.1.2. Does product discover, catalog and version Operating System version and patch level (initial discovery)?
                                                        5.1.3. Does product discover, catalog and version software version and patch level (initial discovery)?
                                                        5.1.4. Does product discover, catalog and version custom software version and patch level (to the extent available; initial discovery)?
                                                        5.1.5. Does product discover, catalog and version new hardware and device installations (changes since last discovery)?
                                                        5.1.6. Does product discover, catalog and version new software installations (changes since last discovery)?
                                                        5.1.7. Does product discover, catalog and version configuration changes to hardware, devices, OS versions and patch levels, software
                                                        versions and patch levels, and custom software versions and patch levels (changes since last discovery)?
                                                        5.1.8. Does product work with both Windows and Unix servers at a minimum?
                                                        5.1.9. Are product discovery targets and discovery configuration customizable? (i.e. user must be able to limit and/or focus scope of
                                                        discovery)



5.2.   IT Asset Management                              5.2.1.      Does product manage data and metadata related to IT Assets?
                                                        5.2.2.      Does product allow for user-customizable taxonomy around IT Assets; specifically, product must allow users to edit / create and
                                                        define asset types and related metadata?
                                                        5.2.3.      Does product allow for traceability between Asset types and Assets?
                                                        5.2.4.      Does product include user-customizable views, analysis and reporting capabilities related to managed assets and metadata,
                                                        including traceability?

5.3.   Software License Management                      5.3.1.     Does product manage, catalog and report on software license inventories?


5.4.   IT Operations Strategy and Management Planning   5.4.1.     Does product facilitate development of IT operations strategies which are aligned with business and IT architecture strategy?
                                                        5.4.2.     Does product provide industry standard process, templates or guidelines for operational process change, reengineering,
                                                        improvement and cost reduction?
                                                        5.4.3.     Does product facilitate and support outsourcing strategies and execution?
                                                        5.4.4.     Does product provide industry standard process, templates or guidelines for key aspects of IT operations strategy and management
                                                        planning, including cost structures and asset utilization, user expectations and SLA’s, strategic account management?


5.5.   IT Monitoring and Management                     5.5.1. Does product allow user to monitor and report on availability of network, storage, and servers?
                                                        5.5.2. Does product allow user to monitor and report on performance and status data of the network, storage, and servers?
                                                        5.5.3. Does product allow user to monitor and report on transaction activities as it passes through the systems and applications: web
                                                        servers, application servers, directory servers, email servers, and database servers?
                                                        5.5.4. Does product allow user to monitor and report on response times for web servers, directory servers, database servers, network
                                                        interfaces?
                                                        5.5.5. Does product allow user to monitor and report on SLA-based performance monitoring to ensure end-user response time compliance?
                                                        5.5.6. Does product allow users to define and maintain rules for thresholds, situations, and alerts?
                                                        5.5.7. Does product provide automatic alerts (e.g. email, pager, etc.) for performance problems?
                                                        5.5.8. Does product provide ability to compare performance data with defined SLA requirements?
                                                        5.5.9. Does product store the collected data in database (CMDB) for long historical analysis and long-term planning?
                                                        5.5.10. Does product monitor the health of Java, .NET, VB, and C/C++ applications?
                                                        5.5.11. Does product detect and fix scalability issues before they affect end users?
                                                        5.5.12. Does product capture extensive forensics for application faults and helps IT staff unearth the root cause?




                                                                                     5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
2.1. Business - IT Strategy Development
Description


An Integrated solution framework that enables strategy lifecycle management across business and IT domains. The strategy framework should be able to support different industry strategy
frameworks including but not limited to Balanced Scorecard and Presidents Strategy Framework. The Solution should enable Enterprises to define strategy, visualize business operational
structures, and set performance benchmarks. Functionality supports development of strategy (business, technology and/or IT operations etc), which allows for traceability between defined
strategies and traceability to portfolios, projects, and assets, and which may be tracked within the same application or in other applications.



2.1.1.   Does Product support user-defined and prioritized business and technology drivers, including hierarchical levels of strategic objectives in multiple categories (e.g. business, technology, IT
operations, enterprise workforce and finance)?
2.1.2.    Does Product allow for weighted strategies for mathematically derived priorities?
2.1.3.    Does Product allow for risk management to defined strategies, and must support quantitative risk scoring and risk management?
2.1.4.    Does Product allow for constraints to be defined and managed against defined strategies and associated with risks?
2.1.5     Does Product allow for strategies and constraints to be defined against operational business structures and set performance targets to achieve them?


                                                                                                  Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                  requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                  Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each product which addresses this            If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                                  Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                          Additonal Comments (will
                                                                                                         1.1           1.2          1.3         1.4         1.5       2.1.1       2.1.2       2.1.3       2.1.4   2.1.5   not be scored)

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n         y/n         y/n        y/n     y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n         y/n         y/n        y/n     y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n         y/n         y/n        y/n     y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n         y/n         y/n        y/n     y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n         y/n         y/n        y/n     y/n    <optional comments>




                                                                                                       5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
2.2. Program and Project Portfolio Management
Description


Functional area supports both project and portfolio management, including all aspects of creating, monitoring and managing projects and portfolios.


2.2.1.    Does Product support many-to-many relationships between projects and portfolios?
2.2.2.    Does Product support project- and portfolio-level resource management and/or matrixed resource management?
2.2.3.    Does Product support many-to-many relationships between projects or portfolios and organizational units or divisions?


                                                                                                 Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                 requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                 Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each product which addresses this           If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                                 Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                     Additonal Comments (will
                                                                                                       1.1           1.2          1.3        1.4      1.5      2.2.1      2.2.2      2.2.3                           not be scored)

         <name of product>                                <name of suite or N/A>                        y/n           y/n          y/n        y/n     y/n        y/n        y/n        y/n                           <optional comments>

         <name of product>                                <name of suite or N/A>                        y/n           y/n          y/n        y/n     y/n        y/n        y/n        y/n                           <optional comments>

         <name of product>                                <name of suite or N/A>                        y/n           y/n          y/n        y/n     y/n        y/n        y/n        y/n                           <optional comments>

         <name of product>                                <name of suite or N/A>                        y/n           y/n          y/n        y/n     y/n        y/n        y/n        y/n                           <optional comments>




                                                                                                      5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
2.3. Billing and Charge Back for IT Service Usage / UCE
Description


Functional area supports allocation for Business and IT service usage across organizational units and/or divisions.



2.3.1.    Does Product support consolidation and allocation of costs for unique services across user-defined organizational units and/or divisions using user-defined pricing model?
2.3.2.    Does Product allow users to define multiple tiers of services with varying costs and capabilities?
2.3.3.    Does Product be able to manage and consolidate operational information regarding usage of managed services?
2.3.4.    Does Product provide native, customizable usage and other metrics reporting for multiple audiences (business, IT, etc.)?
2.3.5.    Does Product provide state management of all services through discovery, provisioning and confirmation?
2.3.6.    Does Product provide a cost allocation capability normalized across all types and levels of asset while defining and managing cost and business value over the lifecycle of the assets?



                                                                                                  Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                                  each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion
                                                                                                  on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given
List each product which addresses this            If product may be sold as part of a suite, give for each product, but are not required, and will not be used for evaluation purposes. Additional information may be requested for all
functional area:                                  Suite Name and explain if necessary             products which are selected for inclusion on the Functional Index.


                                                                                                                                                                                                                                          Additonal Comments (will
                                                                                                         1.1           1.2        1.3         1.4         1.5       2.3.1      2.3.2       2.3.3      2.3.4      2.3.5        2.3.6       not be scored)

         <name of product>                                  <name of suite or N/A>                       y/n           y/n         y/n         y/n        y/n         y/n        y/n         y/n        y/n        y/n          y/n       <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n           y/n         y/n         y/n        y/n         y/n        y/n         y/n        y/n        y/n          y/n       <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n           y/n         y/n         y/n        y/n         y/n        y/n         y/n        y/n        y/n          y/n       <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n           y/n         y/n         y/n        y/n         y/n        y/n         y/n        y/n        y/n          y/n       <optional comments>




                                                                                                               5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
2.4. Requirements Management
Description


Functional area supports user-defined requirement types, attributes, values, and traceability relationships.


2.4.1.     Does product support custom, user-defined requirement types?
2.4.2.     Does product support custom, user-defined attributes, which can be associated with one or more requirement types?
2.4.3.     Does product support custom, user-defined values for each attribute. Value types must include single-select, multi-select (with user-defined values) as well as text, date and numeric
types?
2.4.4.     Does product support parent-child relationships within requirement types?
2.4.5.     Does product support traceability between requirements?
2.4.6.     Does product include native, user-customizable reporting capabilities on all aspects of requirements (type, attributes, values, parent-child, traceability , etc.)?
2.4.7.     Does product support multiple user-customizable views of requirements and associated data?
2.4.8.     Does product support multiple user-customizable views of traceability between requirement types?


                                                                                                   Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                                   each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from
                                                                                                   inclusion on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments
List each product which addresses this             If product may be sold as part of a suite, give may be given for each product, but are not required, and will not be used for evaluation purposes. Additional information may be
functional area:                                   Suite Name and explain if necessary             requested for all products which are selected for inclusion on the Functional Index.

                                                                                                                                                                                                                                                      Additonal Comments (will
                                                                                                          1.1           1.2           1.3        1.4         1.5       2.4.1     2.4.2   2.4.3      2.4.4     2.4.5       2.4.6       2.4.7   2.4.8   not be scored)

          <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n      y/n     y/n        y/n        y/n         y/n        y/n     y/n    <optional comments>

          <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n      y/n     y/n        y/n        y/n         y/n        y/n     y/n    <optional comments>

          <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n      y/n     y/n        y/n        y/n         y/n        y/n     y/n    <optional comments>

          <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n         y/n        y/n      y/n     y/n        y/n        y/n         y/n        y/n     y/n    <optional comments>




                                                                                                                               5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
2.5. Change Management
Description


Change management is intended to include all aspects of scope, requirements, project and other types of change requests and change orders. Change management is the forum within which
proposals are made and decided for changes to existing requirements, projects/scope, services or applications. Change management is also the forum within which proposals are made for new
requirements, projects, services or applications. Change management is specifically distinct from configuration management in that the goal of change management is to arrive at a decision based
on a user-defined review/approval/decision process, and may or may not include task assignment and work completion validation. Functional area supports user-defined schemas for Change
Management, including multiple user-defined record types and user-defined automated workflow schemas for each record type.



2.5.1.    Does product support creation of multiple user-defined record types for different types of change requests (business, project, software, IT ops, etc.)?
2.5.2.    Does product support creation of multiple user-defined schemas for each record type. Each schema should allow for custom attributes and values?
2.5.3.    Does product support user-based and activity-based change management through the unique change management workflow schemas?
2.5.4.    Does product support custom, user-defined attributes, which can be associated with one or more change request record types?
2.5.5.    Does product support custom, user-defined values for each attribute. Value types must include single-select, multi-select (with user-defined values) as well as text, date and numeric
types?
2.5.6.    Does product support linking between unique records (of same or different change request record types)?
2.5.7.    Does product include native, user-customizable reporting capabilities on all aspects of change request records (type, attributes, values, linked records, etc.)?
2.5.8.    Does product support multiple user-customizable views of change request records and associated data?
2.5.9.    Does product support audit-trail / history of all actions taken on all records?



                                                                                                  Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                                  each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion
                                                                                                  on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given
List each product which addresses this            If product may be sold as part of a suite, give for each product, but are not required, and will not be used for evaluation purposes. Additional information may be requested for all
functional area:                                  Suite Name and explain if necessary             products which are selected for inclusion on the Functional Index.


                                                                                                                                                                                                                                                                  Additonal Comments (will
                                                                                                          1.1           1.2          1.3         1.4         1.5       2.5.1    2.5.2      2.5.3      2.5.4       2.5.5       2.5.6       2.5.7   2.5.8   2.5.9   not be scored)

          <name of product>                                  <name of suite or N/A>                       y/n            y/n          y/n        y/n         y/n         y/n      y/n        y/n        y/n         y/n          y/n       y/n     y/n     y/n    <optional comments>

          <name of product>                                  <name of suite or N/A>                       y/n            y/n          y/n        y/n         y/n         y/n      y/n        y/n        y/n         y/n          y/n       y/n     y/n     y/n    <optional comments>

          <name of product>                                  <name of suite or N/A>                       y/n            y/n          y/n        y/n         y/n         y/n      y/n        y/n        y/n         y/n          y/n       y/n     y/n     y/n    <optional comments>

          <name of product>                                  <name of suite or N/A>                       y/n            y/n          y/n        y/n         y/n         y/n      y/n        y/n        y/n         y/n          y/n       y/n     y/n     y/n    <optional comments>




                                                                                                                                    5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
2.6. Configuration Management
Description


Functional area supports versioning of files, directories and other assets across the development lifecycle.


2.6.1.    Does product support management and versioning of files, directories and other assets across the development lifecycle?
2.6.2.    Does product support automated individual workspace management?
2.6.3.    Does product support parallel development through automatic branching, merging and differencing?
2.6.4.    Does product support transparent, real-time access to files and directories?
2.6.5.    Does product support leaving and returning to the network (disconnected usage)?
2.6.6.    Does product support customizable build and release management?
2.6.7.    Does product support local, remote and web access to Productity?


                                                                                                    Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                                    each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion
                                                                                                    on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given
List each product which addresses this            If product may be sold as part of a suite,        for each product, but are not required, and will not be used for evaluation purposes. Additional information may be requested for
functional area:                                  give Suite Name and explain if necessary          all products which are selected for inclusion on the Functional Index.


                                                                                                                                                                                                                                                  Additonal Comments (will
                                                                                                        1.1          1.2          1.3        1.4         1.5       2.6.1      2.6.2      2.6.3       2.6.4      2.6.5        2.6.6        2.6.7   not be scored)

         <name of product>                                  <name of suite or N/A>                       y/n          y/n          y/n        y/n        y/n         y/n        y/n        y/n         y/n        y/n          y/n         y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n          y/n          y/n        y/n        y/n         y/n        y/n        y/n         y/n        y/n          y/n         y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n          y/n          y/n        y/n        y/n         y/n        y/n        y/n         y/n        y/n          y/n         y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n          y/n          y/n        y/n        y/n         y/n        y/n        y/n         y/n        y/n          y/n         y/n    <optional comments>




                                                                                                                     5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
2.7. Business Intelligence and Data Warehouse
Description


Functional area supports complex use and analysis of data from multiple heterogeneous data sources.


2.7.1.    Extract, Transform, Load (ETL) Technology: Does product support extract, transformation, and load of operational data into a central data warehouse?
2.7.2.    Enterprise Information Integration (EII) Technology (on demand pull): Does product support user-creation of an integrated view of the data residing in heterogeneous data sources with
semantic mapping?
2.7.3.    Enterprise Information Integration (EII) Technology (on demand push): Does product support user queries of the the integrated view to access the integrated data from the
heterogeneous sources at the near real time?
2.7.4.    Business Activity Monitoring (BAM) Technology: Does product populate the data warehouse with information at real time when pre-defined business critical events happened in the
operational systems?


                                                                                                 Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each requirement. NOTE: An
                                                                                                 answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR Functional Index. An answer of YES is an
List each products which addresses this          If product may be sold as part of a suite, give affirmative declaration that the requirement is met. Comments may be given for each product, but are not required, and will not be used for evaluation purposes.
functional area:                                 Suite Name and explain if necessary             Additional information may be requested for all products which are selected for inclusion on the Functional Index.


                                                                                                                                                                                                             Additonal Comments (will
                                                                                                       1.1           1.2         1.3         1.4        1.5       2.7.1       2.7.2      2.7.3     2.7.4     not be scored)

         <name of product>                                <name of suite or N/A>                        y/n          y/n          y/n        y/n         y/n        y/n         y/n        y/n       y/n     <optional comments>

         <name of product>                                <name of suite or N/A>                        y/n          y/n          y/n        y/n         y/n        y/n         y/n        y/n       y/n     <optional comments>

         <name of product>                                <name of suite or N/A>                        y/n          y/n          y/n        y/n         y/n        y/n         y/n        y/n       y/n     <optional comments>

         <name of product>                                <name of suite or N/A>                        y/n          y/n          y/n        y/n         y/n        y/n         y/n        y/n       y/n     <optional comments>




                                                                                                          5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
3.1. Business Modeling
Description

Functional area supports visual modeling and specification of business models, business processes and business pattern, as well as enterprise definition and analysis of business organizational
structures associated with a particular strategy or business driver, as well as development of business value scenarios with associated performance values and targets. Additionally, the modeled
business organizational structures should be able to be mapped to all other enterprise asset types including IT asset types.

3.1.1.    Does product provide the ability to visually model with Unified Modeling Language (UML) business patterns, models, processes, organizations, workflows, etc?
3.1.2.    Does product provide the enterprise business planners the ability to define business structures associated with a business strategy?
3.1.3.    Does product enable the enterprise business planners to prioritize business structures based on strategies, risks and constraints defined during strategy development?
3.1.4.    Does product enable the enterprise business planners to assign performance measures against the modeled business structures?
3.1.5.    Does product enable the enterprise business planners to model operational lifecycles for the business structures?
3.1.6.    Does product enable the enterprise business planners to assign cost parameters across the lifecycle of the modeled business structures?

                                                                                                  Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                                  each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion
                                                                                                  on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given
List each product which addresses this            If product may be sold as part of a suite, give for each product, but are not required, and will not be used for evaluation purposes. Additional information may be requested for all
functional area:                                  Suite Name and explain if necessary             products which are selected for inclusion on the Functional Index.

                                                                                                                                                                                                                                          Additonal Comments (will not be
                                                                                                        1.1           1.2          1.3        1.4         1.5       3.1.1      3.1.2       3.1.3      3.1.4      3.1.5        3.1.6       scored)

         <name of product>                                 <name of suite or N/A>                        y/n          y/n          y/n         y/n        y/n         y/n          y/n       y/n        y/n        y/n          y/n       <optional comments>

         <name of product>                                 <name of suite or N/A>                        y/n          y/n          y/n         y/n        y/n         y/n          y/n       y/n        y/n        y/n          y/n       <optional comments>

         <name of product>                                 <name of suite or N/A>                        y/n          y/n          y/n         y/n        y/n         y/n          y/n       y/n        y/n        y/n          y/n       <optional comments>

         <name of product>                                 <name of suite or N/A>                        y/n          y/n          y/n         y/n        y/n         y/n          y/n       y/n        y/n        y/n          y/n       <optional comments>




                                                                                                                     5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
3.2. Business Monitoring / Integrated Dashboards
Description

Functional area monitors the progress of Business and IT strategies and associated performance frameworks defined at multiple levels. This should be provided in the form of aggregated Business-
IT Dashboards providing clear quantitative indications of how current performance status compares with the defined performance targets.

3.2.1.      Does product provide out of the box dashboards that provide baseline metrics for defined strategies and modeled business structures and their associated operational lifecycles?
3.2.2.      Does product provide ability to perform data mining and analysis in real time on performance measure which are linked across business and IT enterprise models, including real time
assessment of how performance is mapped to individual enterprise asset types (including business structure elements) over operational life cycle?
3.2.3.      Does product provide the capability to for the Enterprise to set control points which will activate corrective action and hence decision making if desired performance benchmarks are not
meeting their targets?
3.2.4.      Does product provide ability to view aggregate data at the performance framework levels including Key Performance Indicators and Service Level Agreements that are mapped across
Business and IT?
3.2.5.      Does product provide ability to analyze project, program, or divisional level data rolled up into strategy and performance status scorecards based on configurable metrics including
financial, schedule, resource, scope and quality control?
3.2.6.      Does product provide ability to standardize metrics and monitor performance management portfolio of KPI’s and SLA’s?


                                                                                                  Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                                  each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on
                                                                                                  the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for
List each product which addresses this            If product may be sold as part of a suite, give each product, but are not required, and will not be used for evaluation purposes. Additional information may be requested for all
functional area:                                  Suite Name and explain if necessary             products which are selected for inclusion on the Functional Index.


                                                                                                                                                                                                                                           Additonal Comments (will
                                                                                                         1.1           1.2          1.3         1.4         1.5       3.2.1       3.2.2      3.2.3      3.2.4   3.2.5        3.2.6         not be scored)

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n        y/n         y/n         y/n        y/n       y/n      y/n          y/n         <optional comments>

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n        y/n         y/n         y/n        y/n       y/n      y/n          y/n         <optional comments>

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n        y/n         y/n         y/n        y/n       y/n      y/n          y/n         <optional comments>

         <name of product>                                  <name of suite or N/A>                        y/n           y/n          y/n         y/n        y/n         y/n         y/n        y/n       y/n      y/n          y/n         <optional comments>




                                                                                                                 5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
3.3. Business and IT Transformation Management
Description

Functional area develops enterprise targets and associated transition roadmaps for a particular business or technology strategy. The roadmaps should provide milestones at multiple levels in time
and other dimensions that enable an analysis of the business and IT transition toward targets, and performance progress against those targets.

3.3.1.    Does product allow the enterprise to set business and IT goals and targets and develop transformation roadmaps?
3.3.2.    Does product allow the enterprise to define interim maturity steps in the transformation roadmaps, and detail how these steps provide for an eventual realization of an enterprise
strategy?
3.3.3.    Does product allow the enterprise to define a transformation framework where all dimensions of a the enterprise performance and strategy are mapped in an integrated framework?

                                                                                                 Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                 requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                 Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each product which addresses this           If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                                 Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                     Additonal Comments (will
                                                                                                       1.1           1.2          1.3        1.4         1.5       3.3.1      3.3.2       3.3.3                      not be scored)

         <name of product>                                 <name of suite or N/A>                       y/n           y/n          y/n        y/n         y/n        y/n         y/n        y/n                      <optional comments>

         <name of product>                                 <name of suite or N/A>                       y/n           y/n          y/n        y/n         y/n        y/n         y/n        y/n                      <optional comments>

         <name of product>                                 <name of suite or N/A>                       y/n           y/n          y/n        y/n         y/n        y/n         y/n        y/n                      <optional comments>

         <name of product>                                 <name of suite or N/A>                       y/n           y/n          y/n        y/n         y/n        y/n         y/n        y/n                      <optional comments>




                                                                                                     5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
3.4. Business Services Portfolio Management
Description

Functionality to define, change and manage the business capabilities of an enterprise as a set of services. This construct of business services portfolio development will enable the enterprise to
link all asset types to one or more business services.

3.4.1.     Does product provide the ability to define business capabilities as services by aggregating and mapping different asset types?
3.4.2.     Does product provide a collaborative approach to business services portfolio development across the enterprise?
3.4.3.     Does product manage these business services within customizable services portfolios that are mapped to business and IT strategic initiatives?

                                                                                                  Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                  requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                  Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each product which addresses this            If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                                  Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                     Additonal Comments (will
                                                                                                         1.1           1.2          1.3        1.4         1.5       3.4.1       3.4.2       3.4.3                   not be scored)

         <name of product>                                 <name of suite or N/A>                         y/n           y/n          y/n        y/n         y/n        y/n         y/n         y/n                   <optional comments>

         <name of product>                                 <name of suite or N/A>                         y/n           y/n          y/n        y/n         y/n        y/n         y/n         y/n                   <optional comments>

         <name of product>                                 <name of suite or N/A>                         y/n           y/n          y/n        y/n         y/n        y/n         y/n         y/n                   <optional comments>

         <name of product>                                 <name of suite or N/A>                         y/n           y/n          y/n        y/n         y/n        y/n         y/n         y/n                   <optional comments>




                                                                                                       5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
3.5. Content Management
Description


This functional area facilitates enterprise content management, including document management, web content management, document / content workflow and content repository.


3.5.1.    Does product include document library services (for example, check-in/checkout, version control and document-level security)?
3.5.2.    Does product include document-centric collaboration capabilities — document sharing, project team support, support for ad hoc, threaded discussions regarding documents?
3.5.3.    Does product include workflow capabilities?
3.5.4.    Does product include records management capabilities?

                                                                                               Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                               requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                               Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each product which addresses this         If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                               Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                  Additonal Comments (will
                                                                                                    1.1          1.2         1.3        1.4         1.5      3.5.1      3.5.2        3.5.3    3.5.4               not be scored)

         <name of product>                              <name of suite or N/A>                      y/n           y/n         y/n        y/n        y/n        y/n        y/n         y/n       y/n               <optional comments>

         <name of product>                              <name of suite or N/A>                      y/n           y/n         y/n        y/n        y/n        y/n        y/n         y/n       y/n               <optional comments>

         <name of product>                              <name of suite or N/A>                      y/n           y/n         y/n        y/n        y/n        y/n        y/n         y/n       y/n               <optional comments>

         <name of product>                              <name of suite or N/A>                      y/n           y/n         y/n        y/n        y/n        y/n        y/n         y/n       y/n               <optional comments>




                                                                                                  5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
3.6. Business Process / IT Outsourcing Management
Description

This functional area is related to but distinct from Contract Management in that it focuses on the operational end of services management, such as SLA’s. Functional area enables definition,
tracking and management of agreements between entities for outsourcing of services. Product should enable service chain management focusing on performance of the different service types,
agreed upon by the two or more entities based on defined enterprise performance benchmarks.

3.6.1. Does product allow for contract and service agreement mapping, regardless of what system or organizational unit is responsible for the contract management (unique from the service and
service performance management)?
3.6.2. Does product allow for detailed service and service performance definition?
3.6.3. Does product provide for the development of pricing/cost frameworks associated with the services?
3.6.4. Does product provide for reporting against agreement status and performance framework?
3.6.5. Does product provide for definition of all deliverables, milestones and schedules associated with the agreement?

                                                                                                 Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                 requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                 Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each products which addresses this          If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                                 Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                    Additonal Comments (will
                                                                                                      1.1          1.2          1.3        1.4        1.5       3.6.1       3.62       3.6.3     3.6.4     3.6.5    not be scored)

        <name of product>                                <name of suite or N/A>                       y/n           y/n         y/n         y/n        y/n        y/n        y/n         y/n      y/n        y/n    <optional comments>

        <name of product>                                <name of suite or N/A>                       y/n           y/n         y/n         y/n        y/n        y/n        y/n         y/n      y/n        y/n    <optional comments>

        <name of product>                                <name of suite or N/A>                       y/n           y/n         y/n         y/n        y/n        y/n        y/n         y/n      y/n        y/n    <optional comments>

        <name of product>                                <name of suite or N/A>                       y/n           y/n         y/n         y/n        y/n        y/n        y/n         y/n      y/n        y/n    <optional comments>




                                                                                                     5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
4.1. Technology Architecture Modeling and Management
Description


Functional area includes modeling and managing software assets and architectural patterns to promote reuse. (Not a configuration management or build management product.)


4.1.1.    Does product include visual modeling design tool for software components?
4.1.2.    Does product include visual modeling design tool for architectural patterns?
4.1.3.    Does product include visual modeling design tool for architectural environments?
4.1.4.    Does product include library of searchable software components or asset browser for accessing reusable assets?
4.1.5.    Does product include inventory of searchable architectural patterns?
4.1.6.    Does product search engine offer capabilities ranging from simple keyword searches to advanced, model-based searches?
4.1.7.    Does product track assets and patterns at an organization-level and a project-level architecture?
4.1.8.    Does product integrate with leading modeling tools and integrated development environments?
4.1.9.    Does product support federated repositories ?
4.1.10. Does product provide a pre-populated and user editable library with content regarding best practices or standards for patterns, products, architectures or other asset types?
4.1.11. Does product support UML Class diagram editing for Java, Enterprise Java Beans, and Database objects, in order to specify designs as preparation for forward-engineering of code?
(tool does not have to include forward- or reverse-engineering of code)
4.1.12. Does product include IE and IDEF diagram editor for Database objects (ER Modeling)?


                                                                                               Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                               each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from
                                                                                               inclusion on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments
List each product which addresses this         If product may be sold as part of a suite, give may be given for each product, but are not required, and will not be used for evaluation purposes. Additional information may be
functional area:                               Suite Name and explain if necessary             requested for all products which are selected for inclusion on the Functional Index.


                                                                                                                                                                                                                                                                                 Additonal Comments (will
                                                                                                   1.1          1.2          1.3        1.4          1.5      4.1.1     4.1.2       4.1.3      4.1.4       4.1.5       4.1.6      4.1.7   4.1.8   4.1.9   4.1.10 4.1.11 4.1.12   not be scored)

           <name of product>                               <name of suite or N/A>                   y/n          y/n          y/n        y/n          y/n       y/n       y/n         y/n        y/n         y/n         y/n       y/n     y/n     y/n     y/n     y/n    y/n    <optional comments>

           <name of product>                               <name of suite or N/A>                   y/n          y/n          y/n        y/n          y/n       y/n       y/n         y/n        y/n         y/n         y/n       y/n     y/n     y/n     y/n     y/n    y/n    <optional comments>

           <name of product>                               <name of suite or N/A>                   y/n          y/n          y/n        y/n          y/n       y/n       y/n         y/n        y/n         y/n         y/n       y/n     y/n     y/n     y/n     y/n    y/n    <optional comments>

           <name of product>                               <name of suite or N/A>                   y/n          y/n          y/n        y/n          y/n       y/n       y/n         y/n        y/n         y/n         y/n       y/n     y/n     y/n     y/n     y/n    y/n    <optional comments>




                                                                                                                                               5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
4.2. Application Portfolio Management
Description

Functional area provides an application knowledge base that serves as the vehicle to collect application inventory, application-related artifacts and application metrics to help govern and
manage application activity.

4.2.1.      Does product include a taxonomy structure that is flexible and user customizable?
4.2.2.      Does product allow users to develop and maintain a comprehensive inventory of all applications?
4.2.3.      Does product include a flexible and user customizable model of standard application portfolio elements, including applications, technical architecture, hardware, operating systems and
their attributes?
4.2.4.      Does product allow for flexible user creation and customization of record types and attributes. Examples of records types and attributes include: name, description, state, cost, user,
owner, funding source, etc.)?
4.2.5.      Does product support storage and links for artifacts (e.g .doc, .xls, .pdf, URL)?
4.2.6.      Does product support versioning of portfolio elements?
4.2.7.      Does product have import/export capabilities (e.g. Excel, .csv, xml)?


                                                                                                    Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                                    each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion
                                                                                                    on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given
List each products which addresses this           If product may be sold as part of a suite,        for each product, but are not required, and will not be used for evaluation purposes. Additional information may be requested for all
functional area:                                  give Suite Name and explain if necessary          products which are selected for inclusion on the Functional Index.

                                                                                                                                                                                                                                                    Additonal Comments
                                                                                                        1.1           1.2          1.3        1.4         1.5       4.2.1      4.2.2       4.2.3      4.2.4      4.2.5        4.2.6         4.2.7   (will not be scored)

         <name of product>                                  <name of suite or N/A>                       y/n          y/n          y/n         y/n        y/n         y/n        y/n           y/n      y/n        y/n          y/n          y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n          y/n          y/n         y/n        y/n         y/n        y/n           y/n      y/n        y/n          y/n          y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n          y/n          y/n         y/n        y/n         y/n        y/n           y/n      y/n        y/n          y/n          y/n    <optional comments>

         <name of product>                                  <name of suite or N/A>                       y/n          y/n          y/n         y/n        y/n         y/n        y/n           y/n      y/n        y/n          y/n          y/n    <optional comments>




                                                                                                                 5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
4.3. Business Services Registry
Description


Functional area provides standards-based means for publishing and discovering reusable business services.


4.3.1.   Does product include a taxonomy structure that is flexible and customizable?
4.3.2.   Does product support effective registry management including federated administration?
4.3.3.   Does product manage approval processes for the publication and discovery of services?
4.3.4.   Does product support versioning and lifecycle management of services?
4.3.5.   Does product support UDDI standards?
4.3.6.   Does product offer search capabilities ranging from simple keyword searches to advanced services searches?


                                                                                                 Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for
                                                                                                 each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion
                                                                                                 on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given
List each product which addresses this           If product may be sold as part of a suite, give for each product, but are not required, and will not be used for evaluation purposes. Additional information may be requested for all
functional area:                                 Suite Name and explain if necessary             products which are selected for inclusion on the Functional Index.

                                                                                                                                                                                                                                         Additonal Comments (will not
                                                                                                       1.1          1.2          1.3         1.4        1.5       4.3.1       4.3.2      4.3.3       4.3.4      4.3.5        4.3.6       be scored)

          <name of product>                               <name of suite or N/A>                       y/n            y/n         y/n        y/n         y/n        y/n         y/n        y/n         y/n        y/n          y/n       <optional comments>

          <name of product>                               <name of suite or N/A>                       y/n            y/n         y/n        y/n         y/n        y/n         y/n        y/n         y/n        y/n          y/n       <optional comments>

          <name of product>                               <name of suite or N/A>                       y/n            y/n         y/n        y/n         y/n        y/n         y/n        y/n         y/n        y/n          y/n       <optional comments>

          <name of product>                               <name of suite or N/A>                       y/n            y/n         y/n        y/n         y/n        y/n         y/n        y/n         y/n        y/n          y/n       <optional comments>




                                                                                                             5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
4.4. Enterprise Service Bus
Description

An Enterprise Service Bus (ESB) is a middleware infrastructure based on web services standards that simplifies the integration and flexible reuse of business components using a service-
oriented architecture via an event-driven and XML-based messaging engine (the bus). An ESB supports the goals of service orientation by making it easy to dynamically connect, mediate and
control services and their interactions.

4.4.1.   Does product ensure location transparency from the Client Application's perspective?
4.4.2.   Does product include version handling?
4.4.3.   Does product include service invocation monitoring and auditing?
4.4.4.   Does product be highly configurable and able to handle multiple test environments?
4.4.5.   Does product utilize an externalized configuration file for easy modification and scripting?
4.4.6.   Does product include web-services security?
4.4.7.   Does product include service registry services (either publish or push)?
4.4.8.   Does product include content based routing rules?
4.4.9.   Does product utilize synchronous and asynchronous communication?


                                                                                                        Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No
                                                                                                        for each requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from
                                                                                                        inclusion on the DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments
List each product which addresses this             If product may be sold as part of a suite,           may be given for each product, but are not required, and will not be used for evaluation purposes. Additional information may
functional area:                                   give Suite Name and explain if necessary             be requested for all products which are selected for inclusion on the Functional Index.

                                                                                                                                                                                                                                                                Additonal Comments (will not be
                                                                                                           1.1           1.2         1.3        1.4        1.5       4.4.1      4.4.2       4.4.3      4.4.4      4.4.5      4.4.6      4.4.7   4.4.8   4.4.9   scored)

           <name of product>                                  <name of suite or N/A>                        y/n          y/n          y/n        y/n        y/n        y/n        y/n         y/n        y/n        y/n        y/n       y/n     y/n     y/n    <optional comments>

           <name of product>                                  <name of suite or N/A>                        y/n          y/n          y/n        y/n        y/n        y/n        y/n         y/n        y/n        y/n        y/n       y/n     y/n     y/n    <optional comments>

           <name of product>                                  <name of suite or N/A>                        y/n          y/n          y/n        y/n        y/n        y/n        y/n         y/n        y/n        y/n        y/n       y/n     y/n     y/n    <optional comments>

           <name of product>                                  <name of suite or N/A>                        y/n          y/n          y/n        y/n        y/n        y/n        y/n         y/n        y/n        y/n        y/n       y/n     y/n     y/n    <optional comments>




                                                                                                                                   5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
5.1. IT Asset Discovery
Description


Functional area supports discovery of desktop, network, and server/data center hardware and software assets and their attributes.


5.1.1. Does product discover, catalog and version hardware and device names and components including but not limited to: CPU, RAM, available and used storage, network and storage interfaces
(initial discovery)?
5.1.2. Does product discover, catalog and version Operating System version and patch level (initial discovery)?
5.1.3. Does product discover, catalog and version software version and patch level (initial discovery)?
5.1.4. Does product discover, catalog and version custom software version and patch level (to the extent available; initial discovery)?
5.1.5. Does product discover, catalog and version new hardware and device installations (changes since last discovery)?
5.1.6. Does product discover, catalog and version new software installations (changes since last discovery)?
5.1.7. Does product discover, catalog and version configuration changes to hardware, devices, OS versions and patch levels, software versions and patch levels, and custom software versions and
patch levels (changes since last discovery)?
5.1.8. Does product work with both Windows and Unix servers at a minimum?
5.1.9. Are product discovery targets and discovery configuration customizable? (i.e. user must be able to limit and/or focus scope of discovery)

                                                                                                  Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                  requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                  Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product,
List each product which addresses this           If product may be sold as part of a suite,       but are not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are
functional area:                                 give Suite Name and explain if necessary         selected for inclusion on the Functional Index.

                                                                                                                                                                                                                                                                      Additonal Comments (will
                                                                                                      1.1           1.2         1.3          1.4       1.5       5.1.1         5.1.2        5.1.3        5.1.4        5.1.5        5.1.6      5.1.7   5.1.8   5.1.9   not be scored)

           <name of product>                                <name of suite or N/A>                     y/n          y/n             y/n      y/n       y/n         y/n          y/n          y/n          y/n           y/n          y/n       y/n     y/n     y/n    <optional comments>

           <name of product>                                <name of suite or N/A>                     y/n          y/n             y/n      y/n       y/n         y/n          y/n          y/n          y/n           y/n          y/n       y/n     y/n     y/n    <optional comments>

           <name of product>                                <name of suite or N/A>                     y/n          y/n             y/n      y/n       y/n         y/n          y/n          y/n          y/n           y/n          y/n       y/n     y/n     y/n    <optional comments>

           <name of product>                                <name of suite or N/A>                     y/n          y/n             y/n      y/n       y/n         y/n          y/n          y/n          y/n           y/n          y/n       y/n     y/n     y/n    <optional comments>




                                                                                                                                    5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
5.2. IT Asset Management
Description

Functional area supports management of hardware and software assets and their attributes. Solution area may also include other enterprise assets, such as projects, applications, strategies, etc.,
such as in “enterprise architecture modeling tools.”


5.2.1.    Does product manage data and metadata related to IT Assets?
5.2.2.    Does product allow for user-customizable taxonomy around IT Assets; specifically, product must allow users to edit / create and define asset types and related metadata?
5.2.3.    Does product allow for traceability between Asset types and Assets?
5.2.4.    Does product include user-customizable views, analysis and reporting capabilities related to managed assets and metadata, including traceability?

                                                                                                  Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                  requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                  Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each product which addresses this            If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                                  Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                      Additonal Comments (will
                                                                                                        1.1          1.2          1.3         1.4        1.5       5.2.1       5.2.2      5.2.3       5.2.4           not be scored)

         <name of product>                                 <name of suite or N/A>                       y/n           y/n          y/n         y/n        y/n         y/n        y/n         y/n       y/n            <optional comments>

         <name of product>                                 <name of suite or N/A>                       y/n           y/n          y/n         y/n        y/n         y/n        y/n         y/n       y/n            <optional comments>

         <name of product>                                 <name of suite or N/A>                       y/n           y/n          y/n         y/n        y/n         y/n        y/n         y/n       y/n            <optional comments>

         <name of product>                                 <name of suite or N/A>                       y/n           y/n          y/n         y/n        y/n         y/n        y/n         y/n       y/n            <optional comments>




                                                                                                      5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
5.3. Software License Management
Description


Functional area supports management of software licenses and related attributes.



5.3.1.    Does product manage, catalog and report on software license inventories?


                                                                                                Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each product which addresses this          If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                                Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                    Additonal Comments (will
                                                                                                    1.1          1.2          1.3        1.4        1.5       5.3.1                                                 not be scored)

         <name of product>                               <name of suite or N/A>                      y/n          y/n          y/n        y/n        y/n        y/n                                                 <optional comments>

         <name of product>                               <name of suite or N/A>                      y/n          y/n          y/n        y/n        y/n        y/n                                                 <optional comments>

         <name of product>                               <name of suite or N/A>                      y/n          y/n          y/n        y/n        y/n        y/n                                                 <optional comments>

         <name of product>                               <name of suite or N/A>                      y/n          y/n          y/n        y/n        y/n        y/n                                                 <optional comments>




                                                                                                  5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
5.4. IT Operations Strategy and Management Planning
Description

Functional area supports capabilities for setting IT operations goals and strategies in support of both business mission and IT architecture strategies, as well as providing predictive analysis and
planning for capacity needs and impacts relative to the IT operations strategy.


5.4.1.       Does product facilitate development of IT operations strategies which are aligned with business and IT architecture strategy?
5.4.2.       Does product provide industry standard process, templates or guidelines for operational process change, reengineering, improvement and cost reduction?
5.4.3.       Does product facilitate and support outsourcing strategies and execution?
5.4.4.       Does product provide industry standard process, templates or guidelines for key aspects of IT operations strategy and management planning, including cost structures and asset
utilization, user expectations and SLA’s, strategic account management?

                                                                                                   Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                   requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the DIR
                                                                                                   Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each product, but are
List each product which addresses this             If product may be sold as part of a suite, give not required, and will not be used for evaluation purposes. Additional information may be requested for all products which are selected for
functional area:                                   Suite Name and explain if necessary             inclusion on the Functional Index.

                                                                                                                                                                                                                       Additonal Comments (will
                                                                                                          1.1            1.2          1.3         1.4        1.5        5.4.1       5.4.2       5.4.3   5.4.4          not be scored)

         <name of product>                                  <name of suite or N/A>                         y/n           y/n           y/n        y/n         y/n         y/n         y/n         y/n    y/n           <optional comments>

         <name of product>                                  <name of suite or N/A>                         y/n           y/n           y/n        y/n         y/n         y/n         y/n         y/n    y/n           <optional comments>

         <name of product>                                  <name of suite or N/A>                         y/n           y/n           y/n        y/n         y/n         y/n         y/n         y/n    y/n           <optional comments>

         <name of product>                                  <name of suite or N/A>                         y/n           y/n           y/n        y/n         y/n         y/n         y/n         y/n    y/n           <optional comments>




                                                                                                        5df93c93-9fda-4ba8-9862-e353f4e7999b.xls
5.5. IT Monitoring and Management
Description

Functional area supports capabilities for setting IT operations goals and strategies in support of both business mission and IT architecture strategies, as well as providing predictive analysis and
planning for capacity needs.

5.5.1. Does product allow user to monitor and report on availability of network, storage, and servers?
5.5.2. Does product allow user to monitor and report on performance and status data of the network, storage, and servers?
5.5.3. Does product allow user to monitor and report on transaction activities as it passes through the systems and applications: web servers, application servers, directory servers, email servers,
and database servers?
5.5.4. Does product allow user to monitor and report on response times for web servers, directory servers, database servers, network interfaces?
5.5.5. Does product allow user to monitor and report on SLA-based performance monitoring to ensure end-user response time compliance?
5.5.6. Does product allow users to define and maintain rules for thresholds, situations, and alerts?
5.5.7. Does product provide automatic alerts (e.g. email, pager, etc.) for performance problems?
5.5.8. Does product provide ability to compare performance data with defined SLA requirements?
5.5.9. Does product store the collected data in database (CMDB) for long historical analysis and long-term planning?
5.5.10. Does product monitor the health of Java, .NET, VB, and C/C++ applications?
5.5.11. Does product detect and fix scalability issues before they affect end users?
5.5.12. Does product capture extensive forensics for application faults and helps IT staff unearth the root cause?

                                                                                                     Global and Functional Area Requirements: See Requirements Worksheet for listing of all requirements. Answer Yes or No for each
                                                                                                     requirement. NOTE: An answer of NO for a global technical requirement (1.1-1.5) will result in disqualification from inclusion on the
                                                                                                     DIR Functional Index. An answer of YES is an affirmative declaration that the requirement is met. Comments may be given for each
List each product which addresses this            If product may be sold as part of a suite,         product, but are not required, and will not be used for evaluation purposes. Additional information may be requested for all products
functional area:                                  give Suite Name and explain if necessary           which are selected for inclusion on the Functional Index.

                                                                                                                                                                                                                                                                                            Additonal Comments (will
                                                                                                         1.1           1.2          1.3         1.4         1.5        5.5.1        5.5.2        5.5.3   5.5.4        5.5.5      5.5.6       5.5.7   5.5.8   5.5.9   5.5.10 5.5.11 5.5.12   not be scored)

           <name of product>                                  <name of suite or N/A>                      y/n           y/n          y/n         y/n        y/n          y/n          y/n          y/n     y/n         y/n         y/n        y/n     y/n     y/n     y/n     y/n    y/n    <optional comments>

           <name of product>                                  <name of suite or N/A>                      y/n           y/n          y/n         y/n        y/n          y/n          y/n          y/n     y/n         y/n         y/n        y/n     y/n     y/n     y/n     y/n    y/n    <optional comments>

           <name of product>                                  <name of suite or N/A>                      y/n           y/n          y/n         y/n        y/n          y/n          y/n          y/n     y/n         y/n         y/n        y/n     y/n     y/n     y/n     y/n    y/n    <optional comments>

           <name of product>                                  <name of suite or N/A>                      y/n           y/n          y/n         y/n        y/n          y/n          y/n          y/n     y/n         y/n         y/n        y/n     y/n     y/n     y/n     y/n    y/n    <optional comments>




                                                                                                                                                   5df93c93-9fda-4ba8-9862-e353f4e7999b.xls

								
To top