The award represents an important milestone in Reva's continued growth in the U.S. federal market and creates a new channel for bringing enterprise technology, modernization, integration, and IT services to federal agencies.

About NASA SEWP VI​

Managed by NASA, SEWP is a Government-Wide Acquisition Contract (GWAC) used across the federal government to acquire information technology products, solutions, and services.

SEWP VI expands the program to address a broad range of evolving government technology needs, including cloud, cybersecurity, enterprise IT, engineering, consulting, and mission-support services.

The SEWP VI contracts provide a 10-year ordering period, creating a long-term vehicle through which federal agencies can procure technology and mission-focused IT capabilities.

Awarded in Category C – IT Mission-Based Services​

1RZT LLC was selected under Category C – IT Mission-Based Services.

Category C is particularly relevant to Reva and ZealRiver because it supports services that help federal organizations implement, integrate, modernize, operate, and support technology in alignment with agency missions.

The award creates opportunities for 1RZT to support initiatives ranging from enterprise modernization and cloud services to application integration, information management, and other mission-focused technology programs.

Combining the Strengths of Reva and ZealRiver​

The SEWP VI award builds on the complementary capabilities of Reva Solutions and ZealRiver Technologies through 1RZT LLC.

ZealRiver Technologies brings extensive experience supporting government and commercial technology programs, with capabilities spanning cloud engineering, infrastructure and systems management, configuration management, IT operations, risk management, and program management.

Reva Solutions brings specialized expertise in enterprise content management, digital workflows, application integration, and modernization, with experience across platforms including OpenText, ServiceNow, Box, and Microsoft technologies.

Together, the companies can combine federal delivery experience with specialized enterprise technology expertise to help agencies modernize systems, connect information with business processes, and deliver practical solutions for mission requirements.

Creating New Opportunities with Our Technology Partners​

SEWP VI also creates an important opportunity for Reva to expand how we work with our technology partners in the federal market.

Reva has built solutions and implementation expertise around leading enterprise platforms, particularly in enterprise content management, digital workflows, cloud content, application integration, and modernization.

Through 1RZT and SEWP VI, Reva can work with its technology partners to pursue federal opportunities where those platforms form part of a broader agency modernization or mission solution.

Looking Ahead​

The NASA SEWP VI award represents more than access to a new contract vehicle. It provides a long-term foundation for Reva, ZealRiver, and 1RZT to build new relationships across the federal market and pursue larger, mission-focused technology initiatives.

Reva looks forward to working with ZealRiver, our technology partners, and federal customers to deliver solutions that modernize enterprise systems, connect information with the applications where people work, and help agencies meet their evolving technology needs.

Documents are an essential part of many business processes—from employee and customer requests to case management, approvals, audits, contracts, and service delivery. But as organizations digitize these processes, they also need to consider where those documents should live, how they should be secured and governed, and how users can work with them without leaving the business application.

The Documents in Digital Workflows session brought together enterprise architecture and content management perspectives to discuss these considerations.

Speakers​

The session featured:

• Charles Bartley — Senior Executive Enterprise Architect, ServiceNow
• Eswar Eluri — Digital Transformation Architect, Founder & Principal Consultant, Reva Solutions
• Terry Mullally — General Manager, Reva Solutions

Documents Are Part of the Workflow — But Don't Always Belong in the Application​

Business applications increasingly provide the primary experience through which employees, customers, and service teams complete their work. Documents are often an integral part of those processes.

However, storing every document directly within the business application may not always be the right architectural approach.

Organizations need to consider requirements such as:

• Document volume and file size
• Security and access controls
• Sensitive or regulated content
• Records management and retention
• Search and metadata
• Storage and infrastructure requirements
• Scalability and long-term content growth

An effective architecture can allow the business application to manage the workflow and user experience while an enterprise content platform manages the documents and their associated governance requirements.

For users, the experience can remain seamless—the documents are available within the context of the business process even though the content may be managed outside the application itself.

What the Session Covered​

The discussion focused on three key areas:

Managing documents as part of digital workflows How documents can become part of the overall business process rather than being managed as disconnected files or separate repositories.

Design considerations when using documents Architectural considerations around how applications interact with enterprise content, including user experience, security, metadata, governance, and scale.

Managing large or sensitive files Strategies for handling content that may not be appropriate to store directly within the ServiceNow instance while still making that content accessible within ServiceNow-driven workflows.

Bringing Content and Workflow Together​

At Reva Solutions, much of our work sits at the intersection of enterprise content and business applications.

Our focus is on helping organizations create digital experiences where users can work with the documents they need within the context of their business process—while allowing the appropriate enterprise content platform to handle content storage, security, governance, and lifecycle requirements.

The goal is not simply to connect a document repository to an application. It is to design the overall experience so that content becomes a natural part of the digital workflow.

Continuing the Conversation​

The architectural questions discussed during this session continue to be relevant as organizations modernize their digital workflows.

They are becoming even more important as enterprises connect business applications, content platforms, automation, and AI. Where content lives, how it is governed, and how applications securely access it can have a significant impact on the scalability and effectiveness of the overall solution.

Watch the recorded session: Documents in Digital Workflows — ServiceNow Digital Services Forum

The challenge provided an opportunity to demonstrate innovative ways of extending the Documentum D2 Smart View SDK and connecting enterprise content with the applications and workflows where business users work.

Extending the Documentum D2 Experience​

For the challenge, Reva demonstrated an HR service delivery scenario that brought together Documentum D2 Smart View, ServiceNow, AI-assisted content research, and Documentum workflows.

The demonstration showed how organizations can extend the D2 user experience beyond traditional content access and enable content to participate more directly in business processes that span multiple enterprise applications.

The solution showcased several capabilities:

• AI-assisted policy research — HR agents working on cases in ServiceNow could use AI assistance to research relevant policy documents managed in Documentum, helping them find and understand the information needed to resolve an employee request.
• Content in the context of HR cases — Relevant Documentum content could be accessed as part of the ServiceNow case experience, reducing the need for HR agents to move between applications while investigating a request.
• Cross-application workflows — Activities initiated as part of an HR case could trigger processes across ServiceNow and Documentum, connecting the business case with the underlying content lifecycle.
• D2 review and editing workflows — When a policy document required review or modification, the process could transition into the Documentum D2 environment, where content owners could review, edit, and manage the document using Documentum workflows.

Connecting Cases, Content and AI​

The demonstration illustrated a broader enterprise content pattern.

A business process may begin in ServiceNow, the information needed to resolve it may reside in Documentum, AI can help users research and understand that information, and the resulting activity may identify content that needs to be reviewed or updated through a Documentum workflow.

Instead of treating these as separate applications and processes, the solution connects them into a more continuous experience.

For organizations with large repositories of policies, procedures, employee documents, contracts, and other governed content, this approach can make enterprise content more accessible within day-to-day business processes while allowing Documentum to continue managing the underlying content and its lifecycle.

Innovation Through the Smart View SDK​

Being selected as a finalist in the inaugural OpenText Documentum Smart View SDK Challenge recognizes Reva Solutions' work in exploring how Documentum can be extended beyond the repository experience.

The challenge solution demonstrates how the D2 Smart View SDK, ServiceNow, AI-assisted content research, and Documentum workflows can work together to create connected experiences spanning business applications and enterprise content.

See the Solution​

Watch Reva Solutions' Documentum Smart View for ServiceNow demonstration from the OpenText Documentum Smart View SDK Challenge.

Watch the Demonstration

The session focused on a practical question: as ServiceNow expands across the enterprise, how can organizations make the documents supporting those processes available to users while continuing to manage them within their enterprise content platform?

Beyond IT Service Management​

The webinar explored how the integration can support ServiceNow processes across multiple areas of the business, including:

• Employee Services and HR
• Legal Matter Management
• Customer Service
• Procurement Operations
• Field Service Management

Through these examples, Reva demonstrated how documents managed by OpenText can become part of the ServiceNow experience, giving users access to the information they need in the context of their work.

The session also discussed how organizations can maintain OpenText security, compliance, and content governance while extending access to content through ServiceNow.

Watch the Webinar​

Watch the recorded webinar to see OpenText Extended ECM for ServiceNow in action and explore examples of connecting content with ServiceNow business processes.

Due to Perceptive Contents’ document structure and organization, the traditional lift and shift process was deemed ineffective and we sought a different approach. In this blog, I will discuss the general architecture of migration projects and the considerations and decisions I had to make due to the unique characteristics of the system.

Standard migration architecture​

The first step to all migration projects is to perform a content inventory to identify the documents, files, and information that you want to move. Organizations must have a good understanding of the documents they want to transfer before the migration. Content discovery can be challenging as content could be stored in multiple places and have multiple owners with different priorities. Once the content has been identified, we can extract the content from the system.

During the content and metadata extraction stage, contents and metadata information are processed as shown in the above diagram. The document information needs to be cleansed to fit the Box’s limitation. Then the metadata needs to be transformed to the most fitting data type in Box. Data and contents are then uploaded to Box.

At last, the documents are validated by checking report files/database consisting of information on uploaded BoxFile and comparing the Box’s auto-generated SHA-1 hash value to SHA-1 of the local file to ensure the integrity of the data.

Perceptive Content​

Perceptive Content is a scalable content services platform that manages the entire content lifecycle, from capture to disposition. Consequently, the platform operates with its own document structure and organization and this makes integration of other systems difficult. For this reason, we were unable to implement a lift and shift approach for the cloud migration from Perceptive Content. The unique features of Perceptive Content and the considerations and decisions we made to overcome the issues are as follows.

Tool​

For the development, we considered between REST API and Perceptive iScript for extracting data from Perceptive Content. Perceptive Contents iScript is a custom automation engine that allows you to programmatically complete tasks, make decisions, and communicate with other systems from Perceptive Content. REST API offered endpoints that will simplify the development; however, we chose iScript over it due to the drawback of additional consumption costs.

Automated Naming and Automated Folding​

In Perceptive Content, drawers provide the first hierarchical level of organization for documents. A drawer is used to separate documents into logical categories. As shown in the image, each document is assigned to a drawer with no additional level of organization. Then, the user must filter with metadata to find the documents. As document names in Perceptive Contents are auto-generated unique ids, enforcing the lift and shift approach would result in a jumble of files impossible to identify.

Our solution to overcome this problem involves automated naming and folding of documents. Clients can define the name and path of the documents using existing metadata values. The file names and paths built during the extraction phase then are used to upload the file to its destination system.

Metadata​

Every document in Perceptive Content has five general properties fields, named field1, field2, and so on. Users can assign an alias to each field in each drawer to give meanings to the general properties. On the other hand, you can also map up to five custom properties to each document type, which is a document key that categorizes a document according to a predefined list of values. Also, the data types of Perceptive Content’s metadata were different from Box. For example, Box only allows a specific format (RFC3339) for date data type; whereas, it is stored as six digit integers consisting of years, months, and days in the originating system.

For our solution for migration metadata, we used a map to define the field names, values, and data type of value. This way, the client can only have the values that are relevant to their current workflows transferred and dispose of the outdated fields that are no longer in use. We first extracted the values from the system according to the name and patterns specified on the map, then transformed the values to the type that works with Box.

Multi-file document​

Perceptive Contents allows multi-file documents, a document containing several files with the metadata constituting one multi-file document. Each page of the document, except for files with TIF extensions, is a single file. As for the TIF files, multipage TIFF files are stored as separate pages to enable the preview feature in Perceptive Content.

When extracting the content, files are extracted page by page into separate files. TIF files are then merged to form a single multi-page file with external software. To keep all files from a document together, a naming scheme that includes the document title (or other unique combination of metadata fields) and a two-digit sequence number was used. This keeps files of the same document stay adjacent to each other when sorted in alphabetical order in Box.

Annotations​

Perceptive Contents allows end-users to add annotations to images. In this instance, the Customer chose to include migrating the annotations. Annotation was heavily used during the workflow to signify the approved step. Consequently, the annotations were burned into the images during the extraction process.

Conclusion​

Cloud migration is gaining popularity, but you must think about the benefits it brings to your company before following the trend. In this case, Cloud migration from Perceptive Contents to Box was not only to transfer contents from one place to another but also to standardize the files to make them compatible with other integration and to brace for later use.

Although Salesforce excels as a database platform, its content storing capabilities are limited. By integrating Salesforce with Box, we are able to extend the capabilities of content management within Salesforce.

We recently worked with a company to integrate seamless content management features into their permit application system. We created a system which allows users to not only access Box from Salesforce, but that also organizes Box folders in a hierarchical structure and provides custom notifications to internal users when files are uploaded.

The Problem​

Before we implemented our solution, our client faced problems with their content management process which reduced efficiency. The out of the box integration they were using with Box and Salesforce only provided a flat folder structure. This meant that folders were created for each record and only sorted by their object type, which lead to folders containing thousands of unorganized folders. Moreover, having a growing number of unsorted sub-folders under the same folder will eventually lead to errors in Box. In an attempt to solve this issue, employees would manually copy files from the unorganized folders over to a separate and more organized folder structure. Not only is this process time consuming, but it also lead to files being mismanaged and improperly organized.

Another issue that our client faced was needing to manually share access to Box folders with the permit applicant. This means that once a customer has submitted a permit application, they would need to wait for an employee to add them as a collaborator before they could begin uploading documents. As a result, this made the permit application process longer and more tedious for both internal and external users.

One of the biggest problems our client faced was not having organized notifications for files in Box. Without a proper notification system, employees would receive hundreds of notifications for files being uploaded to a smaller selection of permits. This meant that employees would be required to go through all of these notifications despite many of them being redundant. Moreover, there were no notifications for when a file was updated, causing confusion and miscommunication between customers and employees.

The Solution​

We built a custom solution to precisely meet the requirements of our client. We first extended the capabilities of the default Box Salesforce integration by making our own embedded element which can be used on the customer community page. This unified the customer experience on the community page so that customers would not have to switch between Salesforce and Box to upload documents and track their permit status. Then, we created a system which automatically generates Box folders to match Salesforce records. The Box folders are updated when Salesforce records are updated to keep consistency between the two platforms. We applied metadata to each folder and all the files which are uploaded to that folder, which allows internal users to search the entire folder structure by the metadata attributes. Some of the attributes we applied include permit number, site address, zip code and document purpose.

Our solution automatically shares the folders with the customer that applied for the permit. This addresses the issue with having to manually have an employee share the folder with applicants and significantly improved the speed that the permit applications can be processed. The permission levels of folders are adjusted to ensure that customers can only view their folders.

We implemented a notification system which sends notifications when new documents have been uploaded. Each notification provide a list of all the permits that customers have uploaded files to. They are sent out twice a day to prevent cluttered inboxes when users upload many documents at once. This format provides a well organized and easily manageable notification system to the employees.

The Outcome​

The software that we built for our client resulted in significant improvement of the the permit application process. In addition to integrating Box seamlessly into Salesforce for a unified experience, we also improved the customer experience, process efficiency, and file organization.

The customer experience was reformed into a more user friendly experience. Before, customers would have to work with Box and Salesforce separately in order to create permit applications and upload files to them. With our Box integration community plugin, users have everything they need to go through the permit application process on one website. This simplification decreased the overall rate of user error, which reduced the load on customer support and boosted the customers satisfaction. By implementing automatic folder sharing, customers can complete all of the required tasks for their application at once, which reduces the processes dependency on end users.

The increased efficiency of the permit application process was the most prominent result of our solution. We have eliminated the manual steps required to share a folder with customers, which removes the waiting period required after an application is submitted. Removing these manual, repetitive tasks also increased worker productivity and reduced the margin of error. We saw the same effect when we removed the need for workers to manually manage files by implementing our automatic file folder system.

The results of file organization were a benefit to everyone involved in the permit application process. For customers, we restricted upload and download permissions to ensure that documents were sorted accordingly. In addition, the automatically managed folder structure effectively centralizes the entire file management process to work on Salesforce, since it eliminates the need to use Box separately from Salesforce. Automated organization of files ensured that anyone who uploads or accesses content can do so quickly and efficiently.

This is where the real opportunity for automation and cost saving lies by streamlining the entire supplier invoice process starting with the electronic capture of incoming invoices. SharePoint Online platform provides comprehensive, flexible document management features to provide a view of relevant invoice data to both finance and non-finance staff with a standard Web browser.

Customer Benefits​

• Elimination of paper storage – Eliminate the need for physical paper storage. Digitize all documents and take advantage of records retention and storage capabilities.
• Vendor responsiveness – Quickly retrieve up-to-date, accurate vendor information and respond promptly to vendor inquiries.
• End-to-end management – Integrate all key processes, from receipt and approval to archiving and auditing, and provide complete visibility into the entire process.
• Streamlined work – Provide users with a streamlined user interface that offers seamless integration between data from ERP or LOB systems and full views of all supporting documentation.
• Control and compliance – Retain and archive documents in compliance with government and company policies.
• Storage of related documents such as payment packets, supporting documents, original and annotated versions, and many more for a comprehensive view of each transaction.
• AP users can view invoice documents from within the ERP application, JDEdwards. Non-AP users can use standard SharePoint online Portal.

Key Features and Implementation Details​

• Document sets to contain invoice and supporting documents
• Payment Packets to keep related Invoices
• Store annotated/redacted invoices
• Enable retention
• Store invoice history
• Secure confidential invoices

Conclusion​

Streamlining the invoice process does not only remove paper as a form of process and communication, but also makes Accounts Payable a more efficient and organized process. It introduces scalable technologies that can be leveraged across other lines of business. Moreover, it provides users access to invoices and related content anytime and anywhere, helping organizations increase their productivity.

Suppose you were the safety officer for a not-for-profit corporation responsible for the safe and efficient movement of cargo through various checkpoints. Your responsibilities include finding ways to simplify, improve, and implement health and safety measures across your organization. After meeting with the various stakeholders of this critical business process, you have decided it is time to perform a much-needed update to the health and safety protocol, starting with the Enterprise Health and Safety (EHS) application responsible for incident tracking and safety reporting.

After an organizational review and collaboration process, the Health and Safety team determined that the updated EHS application must be capable of the following:

• Access to real-time performance metrics, incidents, and interventions
• A simple, modern and intuitive EHS applications usable by both technical and non-technical users
• Intuitive and simple incident reporting accessible on:
  • Both mobile and desktop
  • In English or French
  • From any location
• Ability to enhance the Safety team’s productivity
• Up-to-date, accurate information available for reporting
• Generate positive outcomes while minimizing the need for extensive change management
• Provide an EHS application solution that leverages the company’s strategic document management (OpenText) and ERP (SAP) platforms.

After identifying the needs of the organization, the challenge became aligning both technical and non-technical stakeholders in a “Connected Workspace” that could accommodate incident tracking and safety reporting. This led to the selection of OpenText’s Extended ECM with Smart UI.

What did OpenText Extended ECM Smart UI deliver?​

• A modern, Intuitive and mobile-enabled UI with a mobile content server
• Configurable perspectives for landing pages and workspaces
• Extensive Reporting and dashboard capability using WebReports and Content Intelligence Widgets
• Easy to configure Workflows with Smart UI Webforms for review and approval along with storing supporting documents

Our Solution for EHS​

User Dashboard​

By using OpenText Content Suite 16 Perspectives, Reva Solutions was able to provide employees, supervisors/managers, executives and the safety team with a personalized user experience including their most relevant activities organized according to their role in the organization.

Additional features include:

• Custom Landing pages per user persona
• Custom and connected workspaces for display and storage of safety information
• Workflows with Smart UI forms for data entry, review, approval and document upload
• Integration with SAP SuccessFactors for Employee info/hierarchy

Incident Reporting and Connected Workspaces​

Through the Connect Incident Workspace, users are presented with a snapshot of critical information about a specific incident; in this case an incident and its related corrective measures and investigations. The user can now access the information they need to make quick, informed decisions by navigating the overview and document tabs.

Dashboards​

The Incident Chart automatically filters data across multiple regions to present meaningful information to managers and safety teams. Additional filters can be applied dynamically by the user.

Additional EHS reporting capabilities include:

• Overview snapshot for Safety team (total incidents, corrective measure, observations, safety meetings across the organization or by region/location)
• Incidents by region, incident type, location, department or other fields
• Corrective measures snapshot by location or type.
• Top 10 issues during observations and inspections

Conclusion​

Through Connected Workspaces and the Smart UI, the EHS solution provides a secure platform to support employees, supervisors and safety team members to collaborate and solve incidents across various regions and departments while limiting the need for IT intervention and paper-based systems. Additional benefits include:

• Automated organization of business content through pre-built templates and user-centered layouts
• Collection and distribution of information in Connect Workspace based on user roles
• Search and communication capabilities
• Increased productivity with access to custom charts and reports