RepoProTM is an easy-to-use, generic repository
management application that enables organizations to centrally store
and manage their asset information - including related metadata and
relationships. It serves as an ideal solution in key repository
management areas, such as Service Library, Application Portfolio
Registry, and Source Code Module Registry.
RepoProTM has an intuitive user interface designed to
help users find information with ease and accuracy. In a nutshell,
it:
-
Enables its users to effectively visualize and manage
relationships between assets
-
Supports easy discovery of information through its browse and
search features
-
Provides an Import/Export as Excel feature, which helps manage
information contained in the RepoProTM repository
- Is API supported and provides a REST interface
-
Supports guest-level access, whereby guest users can avail
read-only access
-
RepoProTM does not ship with any predefined assets and
relationships
For publishing information, RepoProTM is designed for:
- Enterprise Architects
- Service and API developers
- Architects
- Application Managers
For consuming information, RepoProTM is designed for:
-
Project teams – Developers, Designers, Project Managers, QA,
Operations, etc
- Third-party partners (in a controlled manner)
- Other business units
The search feature in RepoProTM allows the user to search
for assets based on Asset Types, Taxonomies, and Tags. The quick
search allows wildcard search based on keywords. Advanced Search
allows you to perform specific searches that traverse relationships
and dependencies. Both options are easy to use and allow you to save
the search queries for future faster searches.
RepoProTM has evolved from service engagements in the
digital asset management space. It is designed by service engineers
who experienced needs over time in terms of what a centralized
repository should be like to fully support an evolving Application
Inventory model. This is what makes our repository management tools
unique as they are made by practitioners for practitioners.
-
RepoProTM is built on the API-first approach. All the
product capabilities are available as APIs that make it easier to
be deployed as a headless solution with a 100% custom-built UI
solution on top.
-
Designed for ease of use and configurability, the data model of
RepoProTM provides a dynamic schema. This makes it
versatile, as it can be used in many contexts; such as Service
Library, Enterprise Architecture Repository, CMDB (Configuration
Database), Generic Asset Repository for Admin Teams, Network
Element Repository, etc.
-
Highly granular access control designed for Enterprises to have
higher control on data visibility.
To use RepoProTM as an end-user, there are no special
skills required.
RepoProTM enables you to define your entity types,
attributes, relationships, and rules.
-
Define and maintain Asset Types with meta-data parameters grouped
into categories and version-able Asset Types
- Support for Derived Attributes and Derived Computations
-
Define Relationships between Asset Types with support for four
types of Asset Relationships with associated semantics.
The metadata model along with the relationship structure and types
are illustrated in the following diagram:
A Relationship identifies a dependency or connectivity between two
Asset Types, which can be related to each other in a hierarchical or
non-hierarchical way.
RepoProTM allows you to define Relationships in the
following types:
If two Asset Types are related to each other in a non-hierarchical
way, they can have an Association or Classification type of
Relationship.
- Classification
- Association
Hierarchical Relationships exist when Relationships create a
hierarchical, parent-child Relationship between Asset Types to
represent products and services comprising multiple components.
An Asset Instance is like the “object” in object-oriented languages
and bases itself on the blueprint defined for the Asset Type. Each
Asset Instance has different values for each Property. Based on the
Relationships defined between Asset Types, the concerned Asset
Instances can instantiate the Relationships. A taxonomy is used to
classify Asset types for categorizing and organizing instances based
on your functional or organizational domain.
RepoProTM supports the following Parameter Types:
-
Text: Used to represent textual values. The user can specify the
maximum length for a Text Parameter type.
-
Rich Text: Use Rich Text Parameter Types for text-based values.
- File: Used to attach files to the Asset Instances
- Date: Use Date Parameter Type for date values
-
List: There are four types of lists supported by the system
-
Custom List - where the user provides the list values (max.
5000 characters)
-
Asset List – user can map the parameter to any of the Asset
Types
-
Native User List - where the list is populated with the names
of native users
-
LDAP User List - where the list is populated with the names of
LDAP users
-
Derived Attribute - Allows the user to extract the value of an
attribute using the attribute names, or the Overview, Asset
Instance version ID, Asset Instance name using macros from a
related Asset Instance.
-
Derived Computation - Allows the user to find the count of
Relationships based on the Relationship chain.
RepoProTM manages access permissions for logged-in users
through Roles mapped to user functions. User functions for assigning
roles are pre-defined in RepoProTM and include the
following:
- Manage Assets
- Manage Taxonomy
- Manage Relationships
- Manage Roles
- Manage Groups
- Manage Users
Roles are assigned to groups. When users are added to groups, they
inherit the roles defined by the group.
Yes, the Filter option allows you to filter data based on meta-data
parameter values of Asset Types. It provides an interface to define
and store filter criteria.
Custom Search allows the user to search based on your custom
requirements. Based on specific needs, we provide add-ons with
optimized functionality to fulfill requirements that otherwise would
be complex to query/search from the UI. Quick search is based on
keywords/tags that can be used out of the box.
Users can subscribe to change notifications on Asset Types, Asset
Instances, and Taxonomies. All the changes made to the subscribed
Asset (including the creation of an Asset Instance, changes to
Categories, Parameters, renaming the Asset Type, deleting the Asset
Type) are notified by mail to the user.
Users can be authenticated through a built-in user store, or via an
organization’s enterprise directory such as Active Directory based
on LDAP protocol.