Technology Portfolio

BDNA & Troux




Analyze your environment and IDENTIFY the technologies important to your organization

Provide list of technologies to iVision and get an XML extract with lifecycle information from technopedia




Use the Troux out of the box functionality import technopedia information in your Troux environment




Use Troux InSight to visualize and report on the technology landscape of your organization

Technology Portfolio

Home/Solutions/Technology Portfolio
Technology Portfolio 2017-05-24T18:42:28+00:00

How does it work?

A simple, yet effective way to incorporate lifecycle data for all your technologies (hardware and software) from BDNA Technopadia catalog directly into your TrouxSource Plantform.

Following a 4-step process, the data from rich Technopedia catalog is fully integrated within the TrouxSource Platform without any metamodel customization. Visualization and reports within Troux Navigate and Troux InSight offer views for Cybersecurity Rick Management, IT Assets Management, IT Standards Management and License Management and License Management.

Many organizations have implemented some procedures and processes for managing the technology lifecycle information within their organization. These processes are often manual (slow and prone to errors), resource intensive, and do NOT allow the organization to effectively use the technology portfolio information for risk management and planning. iVision’s TPM solution aims to elevate an organization’ existing processes by automating the management of the technologies’ lifecycle information, an activity that is often time-consuming and resource intensive. At the same time, iVision’s solution offers better data quality through the integration of the BDNA technopedia catalog.

Do you want to eliminate the cost and reduce the effort of maintaining a list of technologies across your enterprise?

  • Have the Technology information support informed decisions with BDNA & Troux
  • Data-as-a-Service for Enterprise Portfolio Management
  • iVision’s DaaS is the only available service offering that provides access to the wealth of information for technologies and their lifecycles from the BDNA Technopedia catalog directly within the Troux Enterprise Architecture Repository. With no setup, no additional software installation, no additional hardware costs, no head-aches, iVision makes it simple to pull the data for required technologies from BDNA Technopedia into the Troux Enterprise Architecture Repository for reporting, analysis and visualization.

Let us show you how our solution will help your organization


Why Do I Need This?

If a consistent, high data quality list of technologies and their lifecycles is required by an organization, the iVision DaaS solution is the most cost-effective option available in the marketplace. Without the DaaS offering, an organization has to undertake a time-consuming, resource-intensive initiative that will, at best, yield results with a marginal degree of confidence of the Technology landscape within an organization.

What is included in the service offering?

iVision’s DaaS offering includes:

  • The BDNA Technopedia catalog information
  • Regular refresh of the data based on your needs
  • Troux compatible XML data formatted output

Frequently Asked Questions

How do we add more technologies to pull from the BDNA Technopedia catalog? 2017-05-24T18:57:20+00:00

The iVision TPM integration collector allows clients to specify new technology IDs from the BDNA Technopedia catalog that are then synched with the TrouxSource platform.  The iVision TPM integration collector does not provide a mechanism to search the BDNA Technopedia catalog to find which technology item to add to the iVision TPM integration collector.

A mechanism for the search feature can be developed with a service-engagement that would allow a role-based set of users access to search the full BDNA Technopedia catalog.  The development of a search interface that provides the advanced (or power) user with the ability to find products from the BDNA Technopedia and select the software product versions (or hardware product model) can be developed using a search interface similar to the illustration below:

The above illustration is a conceptual view of the search interface that can be built with a service engagement and not part of the iVision TPM integration collector.  The goal of the illustration is to show one possible option among many on using an ad-hoc interface to help power users go through the BDNA Technopedia catalog and find software products or hardware products.  The power user can search by the “tabs” for Versions, Products, Manufacturer, and Category for Software Product Versions.  For hardware product models, the search would be similar to the “tabs” slightly modified.  This conceptual search interface will allow the power users to search the BDNA Technopedia catalog, view the results of the search and narrow down the search results based on the various facets of the data.  The user can then select the results and “add” them (or save them) to the list of items that will be part of the list of data that gets extracted by the solution from BDNA Technopedia.  The search interface offers a flexible way to search the BDNA Technopedia catalog for the users to find the software products and hardware products of interest to the organization.

When matching the “homegrown” catalog items to the BDNA Technopedia catalog, where is the information of the Technopedia ID placed in TrouxSource? 2017-05-24T19:42:39+00:00

The iVision TPM integration collector reads the External ID field for each of the objects that are being synchronized between TrouxSource and the BDNA Technopedia catalog.  When a value from the “homegrown” technology catalog is matched with the BDNA Technopedia entry, the value of the BDNA Technopedia ID is placed in the External ID property for the Software Product Version or Hardware Product Model elements within the TrouxSource repository.

Once the items are matched from the client technology list to the Technopedia IDs, what else is required to sync the manufacturer lifecycle data? 2017-05-24T18:50:11+00:00

Once the list of technologies is identified from the client technology “homegrown” catalog to the BDNA Technopedia catalog, the list of IDs is configured within the iVision TPM integration collector.  From this point forward the iVision TPM integration collectors synch all the identified technologies from Technopedia into TrouxSource when it is executed.  The execution is done on-demand (as required) or on a schedule.

How does the iVision TPM integration collector work for companies that have their own technology portfolio developed over time? 2017-05-24T18:49:24+00:00

The TPM integration collector works by taking the information from the TrouxSource repository and comparing the information in the TrouxSource repository to the BDNA Technopedia Catalog.  The items compared between TrouxSource and BDNA Technopedia is provided in a list.  The list of technologies identified within the iVision TPM integration collector configuration is compared between the TrouxSource repository and the BDNA Technopedia catalog.  The list controls what items are synced.

With a specific list of technologies (Software Product Version or Hardware Product Model) that exists in the TrouxSource platform there are a few steps that are required to align and sync the lifecycle details between the TrouxSource repository and the BDNA Technopedia catalog:

  • Step 1) Identify from the list of software product versions or hardware product models within the TrouxSource repository that match the BDNA Technopedia catalog – this is done using a manual process (or through services engagement with iVision)
  • Step 2) As technologies are identified from the client specific technologies (software product versions or hardware product models), the BDNA Technopedia catalog IDs are tagged within the TrouxSource item record for the technologies
  • Step 3) The full list of BDNA Technopedia IDs for those items matched are configured in the iVision TPM integration collector which synchs the items from Technopedia to the TrouxSource platform

Step 1:  Preparing the data (not part of the iVision integration collector) – is illustrated below which shows the information of the “homegrown” technologies within the Troux Platform being matched with the corresponding technologies from within the Technopedia catalog:

This is a manual process and will be done outside the integration collector (or through services engagement with iVision).  For all particle purposes, this is a one-time match-up from the “homegrown” technology items to the Technopedia technology IDs.

Step 2:  Document within Troux the Technopedia ID – Once the mapping is completed for some (or all) “homegrown” technologies, the matching Technopedia ID is placed in the “External ID” property of the Troux repository.  The Technopedia ID is also added to a configuration file within the iVision integration collector.  Completed using a manual process (or through services engagement with iVision).

Step 3:  Technopedia Automated Synch – The collector will pull and sync all items that are configured within the collector configuration file and the data from BDNA Technopedia will be synchronized with Troux repository.  This is done via on-demand process (run when it’s required) or through a scheduled task.  This is essential the automated integration (no manual process required).

The step 3 process is done as often as required to refresh the Troux data with the lifecycle information from the BDNA Technopedia catalog.  More technology IDs can be configured as required in the iVision integration collector configuration file.  As more items are added to the configuration file within the integration collector, more data will be synchronized from Technopedia to Troux.  This process is illustrated below:

The “red” arrow for lifecycles is the integration collector.  It pulls from Technopedia the list of IDs that are in the integration collector’s configuration file and matches those items from Technopedia that is pulled with the “External ID” values in Troux to determine what needs to be updated, created or deleted.