VOGO · Agent Configuration
The agent for configuring applications
The organisation, registers, documents, workflows, permissions and settings — configured for the client by the agent, from the approved requirements, with every change under control.
For implementing the VOGO eBS applications and for the changes after go-live. The administrator approves and is accountable.
- Configuration before code
- Every change recorded
- The administrator decides
Configuration, built from requirements and kept under control; the decision, the administrator's
What can be achieved through configuration is no longer written in code. The agent starts from the approved requirements and process models and turns them into registers, document types, workflows, roles and settings, with the same requirement codes, so every requirement has the setting that realises it.
Every configuration change has its request, approval and effect recorded; the production configuration can be compared at any time with the approved one.
What it states about a standard rests on that standard's sources, kept locally; what it cannot find there, it says openly.
Less code to maintain. Fewer forgotten settings. The same accountability, the administrator's.
The organisation
The organisational structure, the departments and the people, with their roles, the way the client works.
Registers and numbering
The incoming and outgoing registers, the numbering rules and what each registration requires.
Document types
The document classes and types, their fields, the filing plan and the retention periods.
Workflows
The AIAO workflows from the approved process models: the steps, who approves, the deadlines and the notifications.
Menus and permissions
Who sees what and who can do what, by role, on the principle of least privilege.
Settings and integrations
The application settings, email, signature, external services and the links with other systems.
Configuration under control
Every configuration change recorded, with who requested it, who approved it and what changed.
The administrator decides
The agent prepares and checks the configuration; approval and release to production remain the administrator's.
What it configures in the VOGO eBS applications
Registry
The incoming and outgoing registers, numbering, registration of received emails and the rules of each register.
Documents (ECM)
Document classes and types, the archival fonds, folders, templates and folder permissions.
AIAO
Workflows and automations, from the approved BPMN models.
The public portal
The services offered to citizens or clients, the forms and the field rules.
The AI assistant
The artificial intelligence providers, the keys and the rules of the in-app assistant.
Accounts and permissions
Users, sign-in, roles and permissions on menus and modules.
Menus and modules
Which modules each organisation has and what the menu of each role looks like.
Administration
The application and organisation settings, from the administration console.
The agent knows the documentation of each VOGO eBS module and configures by it, not by assumptions.
The frameworks it works by
ITIL 4 and ISO/IEC 20000-1
Service configuration and change management, following the recognised practices of IT services.
COBIT 2019
Governance and control of information and technology in the organisation.
ISO/IEC 27001, NIST and CIS
Information security and secure configuration of systems, following the public guidelines.
ISO 10007 and IEEE 828
Configuration management: identification, change control, status accounting and audit.
Configuration comes before code, and every change goes through approval before production — the same approach we use in our projects and our bids.
Frequently asked questions
Does it replace the administrator?
No. The agent prepares the configuration and checks it — registers, document types, workflows, permissions —, and the administrator approves it and releases it to production.
Does it start from analysis and design?
Yes. It configures according to the approved requirements and process models, with the same codes, so every requirement has the setting that realises it.
How are changes tracked?
Every configuration change is recorded, with its request, approval and effect, and can be redone or reverted in a controlled way.
What does it rely on when it cites a standard?
On the sources kept locally and on the documentation of the VOGO eBS applications. What is not in its sources, it says so; it does not fill gaps from memory.
Where is the data kept?
In the application and in the organisation's folder. Processing is based on the agreement between the organisation, VOGO and the provider of the artificial intelligence service.
See how VOGO Agent Configuration works
A 15-minute demo, on an example or on one of your organisation's projects.