Equiviq Modules

Description

Most organizations have plenty of information. The challenge is connecting it.

Employee information lives in one system. Customer records live in another. Assets are tracked in spreadsheets, service requests arrive through several channels, and the procedure someone needs is somewhere in a shared drive. Each system holds part of the story. People spend their time finding the rest.

Equiviq brings those relationships together. People sit at the center, connected to the organizations they work with, the assets they use, the services they need, the work being performed, and the knowledge that supports it.

The modules have distinct purposes, but they share context. That means less repeated entry, fewer disconnected records, and a clearer understanding of who needs what and who is responsible for making it happen.

People: The Center of Every Relationship

Every business activity involves people: employees, customers, prospects, partner representatives, vendor personnel, and others who interact with your organization.

Equiviq starts with the person and connects them to their relationships. A person is more than a contact attached to a company or a name entered on a ticket.

People and Organizations have a many-to-many relationship. One organization can have many people, and one person can be associated with multiple organizations. That reflects how businesses actually operate.

For example, an outsourced IT specialist may support several companies. An executive may work across multiple subsidiaries. A customer representative may be responsible for several businesses, with a different email address for each.

Equiviq allows those associations to exist around one person record, with the appropriate organization context. Sharing a person across organizations does not mean granting unrestricted access to those organizations’ information; relationships and access serve different purposes.

TIP

Instead of duplicating a person every time they appear in another company’s records, Equiviq connects that person to the relevant organizations. Teams can understand who they are working with and which company a particular interaction concerns. The benefit is straightforward: fewer duplicate identities, less confusion, and relationships that survive organizational changes.

Organizations: Structure for Your Business and Its Relationships

Organizations gives structure to the companies and entities your business works within and alongside.

That includes internal companies and subsidiaries, partners, customers, prospects, vendors, and regulatory agencies. These relationships have different purposes, but they all belong in the broader picture of how your organization operates.

Company hierarchies help represent a parent business and its related companies. Connections to People establish who works with each organization. Connections to other modules provide context for its assets, services, work, and knowledge.

For a business with multiple companies, this structure matters. Teams need to know which company owns an asset, which customer a request concerns, and which vendor supports a service. A familiar company name alone is rarely enough.

TIP

Organizations provides a common structure across the platform instead of leaving every department to maintain its own company list. The customer in a service request, the vendor associated with an asset, and the organization connected to a person can be understood within the same relationship model. That reduces the detective work required when information crosses departmental or company boundaries.

Assets: Visibility Beyond the Equipment Spreadsheet

Assets provides comprehensive tracking for physical and virtual assets, including dedicated sections for telecommunications, licensing, and real estate.

That scope recognizes that business assets extend well beyond laptops and servers. A telecommunications circuit, software entitlement, virtual resource, or property can be just as important to operations as the equipment sitting in an office.

Connecting assets to People and Organizations helps establish ownership and responsibility. Connecting them to Work and Knowledge gives teams a way to understand the requests, issues, and supporting information associated with them.

When someone reports a problem, the asset record should help explain what is involved. It should not send the team searching for a separate spreadsheet maintained by someone who left last year.

TIP

Assets brings different asset categories into a connected operational structure while preserving the dedicated sections those categories need. Plugins and integrations can support discovery and synchronization with connected systems, reducing reliance on someone remembering to update an inventory manually. The result is a more useful view of what exists, who it relates to, and where it matters.

Products & Services: The Foundation for Distributing Work

Products & Services defines what your organization provides and supports. The service catalog turns those offerings into recognizable requests that people can select and teams can act on.

It is the center of how work is distributed: what is being requested, who should handle it, and how important it is.

A payroll question, an access request, and a telecommunications outage require different expertise and different handling. Asking the person submitting the request to understand your internal department structure is a reliable way to start a ticket in the wrong place.

The service catalog gives people a clearer entry point. Its configuration helps determine the responsible department or team and the priority and service expectations associated with the request.

TIP

The catalog connects the request to how the organization delivers the service. It does more than collect a subject line and place another item in a general queue. That helps teams receive work with meaningful context and gives customers and employees a more consistent way to ask for help.

Work: Connected Requests, Actions, and Outcomes

Work brings together tickets, tasks, incidents, and projects.

Each serves a different purpose. A ticket captures a request or individual issue. A task represents an action that needs to be completed. An incident connects a broader disruption to the people and requests it affects. A project organizes a larger body of work.

These distinctions help teams coordinate without losing the individual person’s experience. Several people may report the same outage, but each still needs communication and follow-through. Connecting their tickets to an incident preserves that context while allowing the broader issue to be managed together.

Work also connects back to the service being delivered, the organization involved, relevant assets, and supporting knowledge.

TIP

Work carries those relationships with it instead of requiring an agent to reconstruct the story from emails, inventory tools, and company records. Defined ownership and assignment history help make responsibility visible as work moves between people and teams. For customers, that means less repetition. For teams, it means fewer handoffs where the context disappears.

Knowledge: Clear Separation Between Rules, Methods, and Help

Knowledge separates information into three areas:

• Policies establish expectations, requirements, and organizational rules.
• Processes & Procedures explain how internal work should be performed.
• Guides & Resources provide practical assistance, reference material, and answers for the intended audience.

That separation makes it easier to understand what an article is asking the reader to do. A policy establishes a requirement. A procedure explains the steps. A guide helps someone understand or use something.

Knowledge can also be connected to the organizations, products, services, and work it supports, with visibility appropriate to its audience.

TIP

Knowledge is part of the operational picture instead of a separate document collection that people must remember to search. The information supporting a service or activity can be organized around that context. Teams spend less time explaining the same thing repeatedly, and readers have a clearer path to the information they need.

Plugins & Integrations: Keeping Information Connected

Every Equiviq module supports plugins and integrations to extend functionality and connect with other systems.

Depending on the integration and its configuration, those connections can synchronize records, discover assets, connect communication channels, or add capabilities relevant to your environment.

This is central to how Equiviq works. A connected platform loses much of its value if people must spend their day copying information into it.

Plugins and integrations help bring information into the shared relationship model, where it can support other activities. A synchronized person record becomes useful beyond a directory. A discovered asset becomes useful beyond an inventory. A connected communication channel becomes part of the work being handled.

TIP

Integration supports the relationships between modules, alongside the needs of each individual module. The goal is to reduce repeated maintenance and keep operational context available where people need it.

What This Looks Like in Practice

Consider an employee requesting access to a service used by one company in a larger business group.

People identifies the employee. Organizations establishes which company the request concerns. The service catalog identifies the requested service and helps direct the work to the appropriate team with the right importance. Work tracks the request and the actions needed to complete it. Assets provides relevant licensing or resource context. Knowledge supplies the applicable policy, procedure, or user guide.

Configured plugins and integrations can supply or synchronize supporting information along the way.

Each module contributes part of the answer. The person handling the request can work from connected context instead of assembling it manually.

That is the purpose of Equiviq: give people a clearer understanding of their responsibilities, give organizations visibility across their operations, and reduce the gaps where work and information get lost.

Everything connected. Nothing overlooked.