AG-3144-S-14-0034_Attach_2_PR_ _SOO_v1_9_8_14.docx

Product Requirements and

Statement of Objectives for

MEGA Software, Licenses, Maintenance, and associated Consulting, Professional and Training Services

AG-3144-S-14-0034

Version 1.0 September 8, 2014

AG-3144-S-14-0034

Attachment 2

AG-3144-S-14-0034 Attachment 2 Product Requirements and Statement of Objectives

17 of 17 Version 1.6 June 19, 2014 Revision History

Contents

BACKGROUND

The United States Department of Agriculture (USDA) is the leading advocate for rural America. The Department supports rural communities and enhances quality of life for rural residents by improving their economic opportunities, community infrastructure, environmental health, and the sustainability of agricultural production. The common goal is to help create thriving rural communities where people want to live and raise families, and where the children have economic opportunities and a bright future.

USDA’s Information Technology (IT) mission is to enable citizens, employees, and partners to seamlessly access and exchange information and services to sustain, protect, and enrich the global food supply, strengthen the Agricultural commodity supply chain, improve land management and water quality, preserve our nation’s forests and wild lands, and promote U.S. rural prosperity, foreign trade and marketing.

The USDA Enterprise Architecture (EA) helps ensure IT investments align with the mission and goals of the Department. It defines how information and technology should support USDA’s strategic goals and benefit the business. EA helps to make the IT expenditures more effectively serve the mission and goals of the organization. It defines how information and technology support USDA’s strategic planning to benefit our business.

A well-documented, well-understood EA enables the organization to respond quickly to changes in the environment in which the organization operates. It serves as a ready reference that enables the organization to assess the impact of the changes on each of the EA components and ensures those components continue to operate smoothly through the changes.

For EAs to be useful and provide business value, their development, maintenance, and implementation should be managed effectively and supported by a highly functional EA repository. This document outlines the functional requirements for a comprehensive, robust EA repository to manage USDA Agency EA information.

Various component agencies and offices of the United States Department of Agriculture (USDA) entered into several, separate and duplicative contractual agreements for the provision of enterprise architecture software over the past several years. In order to reduce duplication and administrative costs, a single, consolidated solution is required. The purpose of this requirement is to consolidate and co-source these identical needs into a single solution. The USDA agencies and offices with these identical needs actively participated in the development of the requirements outlined in this document and are expected to use the resulting solution. Industry partners should understand that USDA's goal is to focus all possible USDA spend through consolidated and co-sourced solutions, where appropriate, in order to achieve the goal of reduced duplication and administrative costs.

PURPOSE

The purpose of this contract action is to reduce the number of contractual connections with a single vendor on software and services currently in-use and continued to be required by the USDA. This allows preferred and standardized pricing to be applied and benefited from across the enterprise.

SCOPE OF EFFORT

This acquisition includes commercially available enterprise architecture software, in which USDA component agencies and offices have already invested. The purpose of this acquisition is to enter into an enterprise software agreement that provides a reliable and easy means of access to this software, and to the support, training and consulting services necessary for continued successful use. This acquisition will also facilitate upcoming identical USDA investments, where appropriate.

STATEMENT OF OBJECTIVES - PRODUCTS

The following capabilities are required for our Enterprise Architecture Software Tools.

User Interface The tool will:

· Provide access through a single interface

· Be accessible through a web client

· Allow users to easily navigate through the material to find specific artifacts

· Provide a way for consistently naming and organizing artifacts

· Ensure artifacts/components can be easily viewed, used, and re-used

· Incorporate an easy to follow ‘‘process map’’ guiding the use of the tool

· Allow users to print documents, diagrams and reports they access or create

· Provide an online help guide

· Provide relevant out-of-the-box architecture models i.e., business, data, application, or technology

· Provide relevant out-of-the-box templates or patterns for constructs, which can be used to help ‘‘jump start’’ the modeling process

· Provide support for visualization modeling; e.g., drag-and-drop and lines that equate to links Repository/Content Management The tool will:

· Serve as a reliable source of enterprise level data and documents

· Be capable of representing basic attributes or information about each EA component, and the relationships between components

· Be capable of representing target architecture artifacts, and the relationships between the current and target environments

· Be capable of structuring materials into identifiable EA artifacts, compliant with the Federal Enterprise Architecture Framework (FEAF)

At a minimum, these artifact types shall include:

Analysis The tool will:

· Provide portfolio management capability; the ability to model and collect information on investments, systems, applications, etc., with insight into how investment funds are planned and spent

· Support a standard approach for planning, managing and governing an agencies’ IT project over its entire life cycle

· Connect business objectives and goals to capability, organization, processes, data, applications and infrastructure, in order to monitor and control them effectively

· Account for and link USDA, mission area, agency, and program goals, objectives, and performance metrics

· Provide access to EA data for processes such as Capital Planning and Investment Control (CPIC), program reviews, change impact analysis, and business case development

· Provide a mechanism for linking business requirements to the resulting enterprise architecture (requirements traceability) Reporting The tool will:

· Have the ability to document, query, and report by relevant business terms with the associated conceptual, logical, and physical representations

· Be able to represent architecture models and views in a way meaningful to non-technology architecture stakeholders

· Be able to create templates for the required OMB EA artifacts associated with strategic business services, data and information, applications, hosting infrastructure, and security

· Provide a semantic search for EA artifacts according to business and other terms. That search would discover glossaries, data models, EA artifacts, and reports associated with those terms.

· Allow users to create custom queries and reports

Interoperability The tool will:

· Be able to import and export data using a variety of sources and formats, including XML, CSV, PDF, JPG, Excel spreadsheets, Word documents, IDEF 0 and IDEF 1 diagrams, Visio, PowerDesigner

· Be capable of importing and exporting artifacts intact from other EA tools

· Support web-based and other kinds of applications on a variety of devices

· Be able to create and export conceptual, logical, and physical models as well as DLLs for use directly in other database solutions

· Have the ability to create business process models in BPMN and convert them to BPMS

· Be adaptable to centralized, federated, and cloud platforms that can share metamodels, metadata, data, and models with multiple agency users or multiple instances

· Support adaptors for connections to SAP Solman, PowerDesigner, and other EA applications.

· Support industry standard API’s

Standards The tool will provide support for:

· International metadata standards such as ISO/IEC 11179, ISO/FGDC metadata standard for geospatial data, and NIEM

· BPMN V2

· ER and/or UML data models, data flow, and application logic modeling

· FEAF and TOGAF frameworks and models.

· Relevant industry standards; e.g., XML, HTML

Simulation The tool will:

· Provide the ability to dynamically generate diagrams of ‘As Is’ and ‘To Be’ solution architectures from the data in the repository

· Be able to represent “what if” scenarios and enable decision making analysis

User access/Security

· Access and data will be managed under USDA compliant security protocols.

· eAuth level 1 users will be able to access specific EA information via web browsers.

· eAuth level 2 users will be able to access all the information from within USDA networks

· Data will be available only to authorized users, and will be password protected

· Ability to implement multiple role-based security for groups and individual users (assign read, write, and/or delete privileges to users and groups)

Workflow The tool will:

· Allow multiple users at multiple locations to work together to create, share and review content

· Support approvals, comments, and routing

Configuration Management The tool will:

· Provide version management capability

· Control and track updates to information, and provide the capability to authorize update rights by artifact, and/or user role

· Provide for a number of user roles and capabilities, including system administrator, read only access, update access, approver

· Control access to artifacts during updates, and indicate to other users the “lock-out” condition

· Support multiple databases, e.g. SQL Server and Oracle Customization The tool will:

· Support custom metamodels; e.g., the ability to configure and tailor models

· Support the ability to be extended or customized

· Support customizing of architecture component types and their attributes.

PRODUCT REQUIREMENTS

Products and Services The following MEGA products fulfill the objectives outlined in Section 4.0 and include the vendor’s HOPEX platform and associated modules, including maintenance.

Software Licenses:

Provide a licensing structure based on user licenses for Main Users or Contributors including:

· Web front-end capabilities

· HOPEX Explorer for access to the MEGA repository based on the user role

· Collaboration package

· Productivity package

1.1.1 HOPEX Modules, Descriptions and Features:

Customization of documentation templates (Word and HTML intranet portals).

Product integration tools for import/export, XML and API development.

Graphical modeling tool for customizing the metamodel, changing metamodel behavior, adding, changing, or deleting object attributes.

Customize Microsoft Word document generators with; Customize HTML generators Integrate the repository with external applications, such as Asset Management systems, Portfolio Management products, LDAP servers, and more.

• Mass importation through Excel spreadsheets

• Web form-based input

• Sample workflow for application inventory

• Application lifecycle and versions

• Deployment management and lifecycle

• Cost management

• APQC standard repository

• A unique database integrating all relationships between elements so that the information is stored in a structured way

• Complete cost analysis model

• Impact analysis and reporting based on multiple perspectives: cost, risks, technology, business strategy (optional), and user-based criteria

Testing Licenses Environments At no additional costs to USDA, the vendor will also provide Test Server and Back-up licensing.

Technical Support The vendor will provide technical support under the commercial terms provided to Government customers at no additional cost, including access to technical support cases and community technical discussions.

The support service must be available 9.00 am to 5.30 pm Monday to Friday ET, excluding Public Holidays, to all USDA maintained accounts and include technical support is available to USDA through an online community.

USDA Cross-Walk Mapping Current Software to HOPEX

Enterprise Architecture

MA-BPMN

TWK

TRT

MEGA Architecture on Anywhere MEGA Process BPMN Edition on Anywhere MEGA Teamwork MEGA TeamReport x

Functional Licenses

DES

MEGA Database Builder MEGA Designer x

Add-in

Add-on

HOPEX Platform Technical Users

MMS

PUB

MEGA Exchange MEGA Studio MEGA Publisher MEGA Web Editor (EOL - integrated with PUB) x

MEGA Repository Storage for Microsoft SQL Server

SQL

MEGA Repository for Oracle MEGA Repository for Microsoft SQL Server x

SQLA

Business Architecture

Information Architecture

IT Portfolio Management

SAP BluePrint

Governance, Risk & Compliance

Enterprise Risk Management

Operational Risk Management

Internal Control

Regulatory Compliance

Internal Audit

STATEMENT OF OBJECTIVES - SERVICES

Consulting, Professional Services

At additional cost, the vendor will provide consulting, professional services and training, as needed and ordered by the Contracting Officer.

The USDA requires consultant assistance to IT departments, business departments (including consulting for corporate functions like quality control, finance, and business processes), and system engineering departments to carry out effective enterprise governance projects as it relates to the use of MEGA solutions and modules.

The vendor should provide a complete list of resources and rates capable of being used to build-up fixed price project engagements defined at the task order level.

Training

The USDA requires training on MEGA products for individuals as well as group courses.

The vendor should provide a complete set of consulting and training services capabilities.