Xeneural
XEN DEPLOYMENT

A go-live with every responsibility in writing.

Four stages, six deliverables and a team that accompanies the first weeks of operation. This page describes what the entity receives, for the technical area.

Write to XeneuralSee the deliverables
  1. 01

    Assessment

    Xeneural reviews with the entity the processes that enter XEN and delivers a written plan for the first phase, with scope, owners and dates.

  2. 02

    Configuration

    Entity structure, executing units, departments, roles, catalogs and documents. Here it is defined who can see and approve what.

  3. 03

    Migration and testing

    Loading the existing information and validating it against the entity's current figures, before anyone stops using their previous system.

  4. 04

    Accompanied operation

    The first weeks run with the team that did the implementation alongside, not with a generic help desk.

Defined scopes

Every entity and every executing unit keeps its information and its accesses.

Deliverables in writing

Residency, roles, retention, migration, verification and support.

Validation before operating

Migrated information is checked against current figures.

EVERY ENTITY IN ITS SCOPEEntity, executing units and departments.
Main entity
Budget holder, budget and resolutionsCommittees and officers with signing authorityConsolidated history of the entity
Executing unit
Its departments and its staffIts files and work ordersIts approvals, visible to the budget holder
The active entity defines the scope; the budget holder reads its units' data, never the other way around.
WHO CAN DO WHAT

Permissions reflect the entity's responsibilities.

Configuration defines who records, who reviews and who approves in each module. Agents work with the permissions of the officer who authorizes them.

  • Entity structure, executing units and departments.
  • Officers and roles with a scope defined per module.
  • Access review with the entity before operating.
My companyMain
Permissions by departmentWhat each role can view, record and approve inside the entity.
Main entity · Headquarters
LogisticsPurchase orders, warehouse and assets.
RQAMCV
Main entity
Access by module
ModuleViewRecordApprove
Budget
Logistics
Assets
Staff
Treasury
Permissions apply within the active entity.
THE SIX DELIVERABLES

What does the entity receive in writing?

Six documents that are part of the deployment.

Data residency

The region where the entity's data resides, fixed in the data processing agreement.

Role model

Roles, approvers and scope per module for each department, as configured.

Retention and restore

Continuous backups, retention period and the point-in-time recovery procedure.

Migration scope

Catalogs, balances and history that enter XEN, with the cutoff date and the origin of each piece of data.

Verification criteria

The figures the migration is validated against and the officer who signs off.

Support

Xeneural staff and service channels during the first weeks of operation.

ASSISTANCE WITH OVERSIGHT

Agents prepare. The officer signs.

Xeni and the agents summarize files, assemble comparison tables and prepare orders. No award, payment or commitment moves forward without the approval of the officer the regulation designates.

Every decision carries officer, date and document

The history keeps who approved, when and on which file. It is not edited and it exports for the oversight body.

History of a purchase orderToday
  1. Purchasing agent prepared OC-0522Logistics · 2 pumps · Hidrobombas Andinas
    09:12
  2. Head of Logistics approvedMain entity · from Xeni
    09:28
  3. Budget committed the spendCertification 2026-0341 · $92,500
    09:41
Agent, officer and document in the same history.
Technical area questions

What IT asks before a deployment.

Residency, migration, access and backups.