SOURCES SOUGHT
D -- DLA Enterprise Architecture (EA) Tool Suite Capabilities and Functional Requirements
- Notice Date
- 1/9/2015
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Defense Logistics Agency, DLA Acquisition Locations, DLA Contracting Services Office - Philadelphia, 700 Robbins Avenue, Philadelphia, Pennsylvania, 19111-5096, United States
- ZIP Code
- 19111-5096
- Solicitation Number
- 15-0001
- Point of Contact
- Brian Dudek, Phone: 2157375872, James T. Smith, Phone: 215.737.2713
- E-Mail Address
-
brian.dudek@dla.mil, James.T2.Smith@dla.mil
(brian.dudek@dla.mil, James.T2.Smith@dla.mil)
- Small Business Set-Aside
- N/A
- Description
- This is a Defense Logistics Agency (DLA) Contracting Services Office Sources Sought only. Contractors are requested to read and respond to the below and the attached requirements. All responses should be submitted in writing to DCSO-Philadelphia point of contact James Smith (james.t2.smith@dla.mil) no later than 12:00 noon local time, on 23 January 2015. The purpose of this source sought notice is to gain knowledge of potential sources who can meet the desired capabilities and system functionality for the DLA Enterprise Architecture (EA) Tool Suite. This sources sought is for informational and planning purposes only and does not constitute a solicitation for bid or proposals. It is not to be interpreted as a commitment by the Government. This sources sought notice contains the most current information available and will be the only information provided by the DLA. Any responses received may be used as market research to determine an acquisition strategy. Contractors who believe they possess the demonstrated expertise and experience adequate to perform diligently are encouraged to submit a statement of their capabilities (Capability Statement) and specific commercial off the shelf (COTS) products that could meet the requirements in the attached draft PWS (Attachment 1). The NAICS code for this draft PWS is 511210. Please specify your business size when responding to this Sources Sought Notice. ATTACHMENT 1: DLA Enterprise Architecture (EA) Tool Suite Capabilities and Functional Requirements Summary/Background: DLA currently has multiple architecture and portfolio management tools/databases without analytical/visualization capability, which is needed to discover and see the relationships among IT assets and architecture data across the Agency. The general characteristics of the desired application/tool include: IT governance, decision making, architecture integration, architecture modeling, analytical visualization, asset management and portfolio management. More specifically, the Enterprise Architecture (EA) Tool Suite would be comprised of three integrated components: (1) Information Technology (IT) Registry for IT assets and portfolio management, (2) architecture modeling and repository for building and storing data as specified in the DoD Architecture Framework (DoDAF) Meta-model (DM2) and (3) a visual analytics component for analyzing information from the IT Registry, EA Repository, and other data sources across Defense Logistics Agency (DLA). The tool must visually show the connections and relationships of each type of data, based on organizational use cases, in support of strategic-level IT asset decision-making. Detailed Functional and Technical Requirements: DLA has developed a solution architecture that describes the capabilities provided by the desired EA Tool Suite, and the required system functionality for supporting activities performed in developing and maintaining the Enterprise Architecture and IT portfolio. These are listed below: Capabilities: The EA Tool Suite must provide the following capabilities to DLA (note numbers listed below are hierarchical). C1 Standardized Suite of EA Tools - Ability to provide a standardized suite of tools to meet specific user methodology needs in support of the complete architectural lifecycle. All tools within the repository are available to all subscribers, regardless of organization. C1.1 Centralized and Authoritative IT Asset Metadata - Ability to provide a central repository where metadata about all IT assets can be stored, searched, and accessed. C1.2 Centralized Architecture Data and Administration - Ability to provide a standardized methodology to create architecture models. This includes the ability to store architecture models in a central repository. C1.3 IT Asset and Architecture Data Visualization and Simulation - Ability to collect IT data from various sources, represent it in a standard structured way, and provide the ability to temporarily manipulate the data to discover potential impacts. Functional Requirements: The EA Tool Suite must support the following Functional Requirements: F1 Fully support DODAF (DM2)/ Physical Exchange Schema (PES) and Business Process Modeling Notation (BPMN) (current version), version control of models and objects, and the ability to establish relationships between any items stored within the tool suite. F2 Support various types of change/impact/risk/what-if analysis, and consume data from DLA's existing analytical tools and data sources. F3 Provide role base access which limits ability to create, read, update, delete for the various areas of the repository and for various workflows. F4 Provide multiple options for reporting and exporting files to various formats. F5 Provide workflow capabilities (i.e., automated and manually-triggered notifications). F6 Provide ability to manage users and licenses within the software. Technical Requirements: Tool must support the following technical requirements (note numbers listed below are hierarchical). S0 Provide enterprise architecture functionality. S1 Provide IT registry capabilities. S1.1 Set up the IT registry. S1.1.1 Indicate mandatory versus required attributes. S1.1.2 Create custom attributes. S1.1.3 Establish relationships between attributes. S1.1.4 Indicate when a piece or set of data hasn't been reviewed in X period of time. S1.2 Enter data into the IT registry. S1.2.1 Create IT asset records. S1.2.2 Update IT asset records. S1.2.3 Establish relationships between records. S1.2.4 Create portfolios where IT assets are grouped. S1.3 Search the IT registry. S1.3.1 View and sort registry information in various ways (by system name, vendor, investment cost, etc.). S1.3.2 Merge results across the entire registry database. S1.3.3 Create custom queries without requiring coding. S1.3.4 Aggregate information to create summaries. S1.3.5 View IT asset roadmaps (e.g., Gantt chart). S1.4 Support DoD investment reporting. S1.4.1 Provide interface to allow feed of investment records from the DITMR into the DoD IT Portfolio Registry (DITPR). S2 Provide architecture model repository capabilities. S2.1 Store architecture models and artifacts. S2.1.1 Store models that are created using supported modeling languages. S2.1.2 Link to models and other relevant documentation that is stored elsewhere and built with unsupported/ non-native modeling languages. S2.2 Support standard modeling languages, methods, and techniques (i.e., BPMN, DM2, Entity Relationship Diagram (ERD), etc.) for model creation. S2.2.1 Create and edit all models as outlined within DODAF 2.0. S2.2.2 Create and edit process models within BPMN 2.0. S2.2.3 Validate/error-check models in accordance with architecture principles and rules. S2.2.4 Lock models while allowing view access by other users. S2.2.5 Lock objects while allowing view access by other users. S2.2.6 Ensure locked-down models do not get updated even if the objects used within them gets updated. S2.2.7 Allow editing/opening of more than one model at a time. S2.2.8 Support data reuse/check for duplicate objects/check if object name already exists. S2.2.9 Define relationships between models. S2.2.10 Define relationships between models and other items. S2.2.11 Define relationships between objects. S2.2.12 Define relationships between objects and other items. S2.2.13 Provide traceability back to requirements/ goals. S2.2.13.1 Enter IT goals. S2.2.13.2 Link IT goals to each other within a hierarchy. S2.2.13.3 Link IT goals to other objects. S2.2.14 Provide version management. S2.2.14.1 Allow multiple versions of an object. S2.2.14.2 Allow multiple versions of a model. S2.2.14.3 Compare versions of models within the repository. S2.2.14.4 Compare versions of objects within the repository. S2.2.14.5 Present conflicts on imports and merges. S2.2.14.6 Support migration of individual objects/models through development phases. S2.2.14.7 Support resolution of migration conflicts during migration of multiple releases. S2.2.14.8 Support versioning of requirements, history of requirement changes, etc. S2.2.14.9 Ensure compliance to defined meta-model at all levels. S2.2.14.10 Ensure approval of all involved/responsible users for certain objects (i.e., systems) when changes are proposed. S2.2.15 Provide navigation traceability through related models. S2.2.16 Support fit-for-purpose model generation. S2.2.17 Allow generation of models or objects in any order. S2.2.18 Create and edit data models using ERD. S2.3 Visualize models. S2.3.1 Visualize models based on role-based filters. S2.3.2 Configure/ Customize visualization of model objects. S2.3.3 Zoom in and out of models. S2.4 Support customization. S2.4.1 Create new model types, beyond DODAF, ERD and BPMN. S2.4.2 Create new relationships. S2.4.3 Create new attributes. S2.4.4 Support scripting to customize/extend functionality (i.e., viewing or reporting needs). S2.5 Support enterprise architecture program timeline capabilities. S2.5.1 Support timeline marking of objects (i.e., objects valid from __ to __). S2.5.2 Support different stages of existence of objects (i.e., under discussion, valid, operational, discarded). S2.5.3 Produce time-related output (show architecture at any specific, freely-chosen date). S2.5.4 Support current, intermediate, and future states of the architecture. S2.5.5 Indicate when a model hasn't been reviewed in X period of time. S3 Provide visual analytics capabilities. S3.1 Support change/impact/what-if analysis. S3.2 Support gap analysis. S3.3 Support simulation of use cases. S3.4 Support traceability up and down DLA's meta-model. S3.5 Provide a database of design patterns and customizable solutions that can be searched to offer possible solutions. S3.6 Consume data from multiple sources (architecture, portfolio, databases, etc.). S3.7 Support DLA's existing analytical tools (Business Objects, SAS, direct SQL connection). S3.8 Indicate risks and dependencies across a variety of categories (schedule, budget, system dependencies). S3.9 Show the relationship/dependencies between a problem space (e.g., a requirement) and a solution (e.g., system, service, infrastructure). S3.10 Support the creation of custom views, reports, queries. S3.11 Create dashboards. S3.12 Dynamically change a view (e.g., from bar chart to pie graph) without having to re-run the report. S3.13 Provide capability maps (e.g., asset forecasting). S4 Performance and availability for all three tools. S4.1 Support remote access across a VPN. S4.2 Support multi-tasking (having more than one item open) within the tool. S4.3 Support users with different read/write/delete permissions. S4.4 Employ a single, integrated authoritative database that is shared across all tools/ capabilities. S5 Provide security for all three tools. S5.1 Provide user security. S5.1.1 Define access rights. S.5.1.1.1 Establish roles based on the need for read, write, or delete access control down to the object level. S5.1.2 Provide role-based user management. S5.1.2.1 Predefine different roles or types of users. S5.1.2.2 Create/ manage a user account, associated with an available license. S5.1.2.3 Assign a user account to a role. S5.1.2.4 Adjust user permissions as-needed at the folder, model, and object levels. S5.1.2.5 Delete a user account, dis-associating it from a license. S5.1.2.6 Support option to define custom user profiles. S5.1.3 Authenticate user via Common Access Card (CAC). S5.1.4 Manage user accounts and licenses within the tool. S5.2 Provide tool security. S5.2.1 Stamp all object/model changes with a non-editable time-user stamp. S5.2.2 Protect direct data sources at-rest. S6 Navigate all three tools. S6.1 Provide a non-technical, user-friendly interface, appropriate for the variety of users that will use the tool. S6.2 Create custom interfaces for different users. S6.3 Enforce policy that all objects used in diagrams are stored in a database. S6.4 Navigate between the graphical tool and database. S6.5 Support searches for both structured and unstructured information. S6.5.1 Navigate, search, and filter by object type. S6.5.2 Navigate, search, and filter by name. S6.5.3 Navigate, search, and filter by associations/ relationships. S6.5.4 Navigate, search, and filter by attributes. S6.5.5 Navigate, search, and filter by custom fields. S7 Import data into all three tools. S7.1 Interface with other databases programs (e.g., Oracle, SQL). S7.2 Import formatted data (e.g., XML, CSV). S7.3 Import data directly from ARIS. S7.4 Import data directly from ERwin. S7.5 Import models and diagrams from other tools (e.g., Microsoft Visio, Microsoft Excel). S8 Export/ publish/ report (i.e., models, reports, documentation) from all three tools into formats for viewing outside of the tool. S8.1 Export using industry-standard formats. S8.1.1 Export to PDF. S8.1.2 Export to HTML format, including diagrams. S8.1.3 Export to XML format. S8.1.4 Export to CSV format. S8.1.5 Export to Microsoft Office formats. S8.1.5.1 Export to Microsoft Word. S8.1.5.2 Export to Microsoft Excel. S8.1.5.3 Export to Microsoft PowerPoint. S8.1.5.4 Export to Microsoft Visio. S8.2 Export information using out-of-the box layouts. S8.3 Export information to customized, user-defined layouts. S8.3.1 Produce management summaries. S8.3.2 Generate reports for information within specific date ranges. S8.3.3 Schedule the running of reports either directly or via interface with scheduling programs. S8.4 Preview documents prior to export. S8.5 Support mass export of models, such as SharePoint, network drive or intranet site. S9 Support governance process for all three tools. S9.1 Has Certificate of Net worthiness from DoD. S9.2 Support external accountability audits. S9.3 Manage meta-model. S9.3.1 Support DLA's meta-model. S9.3.2 Auto-generate an Enterprise Metadata Dictionary. S9.4 Ability to federate with DOD repositories. S9.5 Provide workflow capabilities. S9.6 Provide configuration management of elements stored within the tool. S10 Support users and administrators within all three tools. S10.1 Provide user support. S10.1.1 Display online help documentation. S10.1.2 Support a community sharing board for users to share their experiences and questions. S10.1.3 Provide automated spell checking. S10.1.4 Support find-and-replace. S10.2 Provide implementation support. S10.2.1 Support initial data load/transfer from DLA systems that are being retired. S10.2.2 Support on-going direct compatibility with, or ease of transferring data to, existing DLA systems. S10.2.3 Export detailed log messages for administrators when an error occurs. S11 Support Section 508 Compliance for all three tools.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DLA/J3/DSCP-PB/15-0001/listing.html)
- Place of Performance
- Address: DLA-HQ, Fort Belvoir, Virginia, 22060, United States
- Zip Code: 22060
- Zip Code: 22060
- Record
- SN03612737-W 20150111/150109234302-9ff3c7988660247934f9aed2238740f3 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |