Independently deployable
Deploy what the organization needs today. No application requires another to be installed, and a failure in one domain does not stop unrelated work.
We build the software, infrastructure, and security that institutions run on — and we own DICE™, the platform that holds all of it in one environment.
One department buys an application. Another builds spreadsheets. A third signs up for an online service. Documents sit on individual computers, separate databases appear, and different vendors own different pieces. The result is significant spending on technology without a technology environment.
KHARTALIUM starts from the opposite end: the organization first, the software second.
Organizations don't run on applications alone. They run on an entire ecosystem — servers, networks, data, users, devices, connectivity, cloud services, policies, and the people responsible for keeping all of it working. We treat those as parts of one environment, because that's how they fail and that's how they have to be fixed.
Digital Information & Communication Ecosystem. Start with the capabilities you need now and add to the same foundation as operations grow. Every application you add inherits the same identity, permissions, workflow and reporting — and none of them has to be installed for another to work.
Core is the shared ground every DICE application stands on. It knows the organization, its units, its people, and who is allowed to do what — so an application never has to invent its own answer to those questions.
A consolidated view across the whole environment, so authorized decision-makers can see activity, pending work, and trends without logging into five systems to assemble the picture themselves.
Deploy what the organization needs today. No application requires another to be installed, and a failure in one domain does not stop unrelated work.
Applications exchange information where it helps. Two systems can share data without becoming inseparable — either can be upgraded or replaced on its own.
Configured around your structure, responsibilities, and policies — not around one industry's assumptions.
Authorization and audit trails are part of the foundation, so responsibility for an action is always traceable.
Room to grow in users, locations, applications, information, and operational complexity.
Runs on-premises, privately hosted, in the cloud, or across a hybrid of the three.
Technology changes faster than institutions do. Components can be replaced without the information they hold being lost with them.
Your information, your systems, your decisions about where they live and who administers them.
Six families, one foundation. Each product has a clear job of its own and still belongs to the wider environment — implement one, or build out a family.
How the names work. A DICE-prefixed product is a standard platform application available to any organization. A named system — SIMS, DLMS, ACE, DOC JED, SCRiPT, FiNS — is built for one kind of institution, with its own structure, terminology and rules. Where a named system covers the same ground as a standard application, the entry says which one it corresponds to.
A complete financial environment for organizations that need accounting to be auditable as well as accurate. Transactions carry their authorization with them, so the trail from request to disbursement stays intact.
SECTOR VARIANTFiNS™ is the ecclesiastical version of this system — the same financial foundation, restructured around parish and diocesan accountability.
One record for each person, connected to the rest of the organization. Payroll, attendance, and personnel history draw on the same information rather than three separate versions of it.
Know what the organization owns, where it is, who is accountable for it, and what has happened to it. QR and barcode verification makes physical inventory a scan rather than a search.
NOT THE SAME ASThis covers capital assets that are held, assigned and depreciated. Consumable stock that moves daily belongs in DICE ICMS.
Institutional memory that stays findable. Documents are indexed, classified, access-controlled, and preserved — so a record filed today can still be produced and verified years from now.
Built for operations where stock moves constantly and accountability matters at every step: purchasing, production, storage, transfer, and branch supply held in one accountable chain. Suits restaurants, cafés, bakeries, retailers, commissaries, distributors, and warehouses.
NOT THE SAME ASThis covers consumable stock in motion. Capital assets that are held and depreciated belong in DICE Property & Asset.
The life of an order from creation to completion — customer, branch, product, or internal. Fulfilment draws on live inventory and settles against finance, so the same order isn't re-entered three times.
An ERP for firms that deliver projects rather than products. Budgets, drawings, manpower, materials and billing stay attached to the project they belong to — so cost-to-date and cost-to-complete are answerable at any point during the job, not reconstructed at the end of it.
RUNS ONDICE Core, alongside Finance & Accounting and Property & Asset — project costing sits on the same ledger rather than beside it.
Clinic operations and patient information in one controlled environment — registration, queueing, consultation, prescriptions, results and billing — with every record reachable only by the roles entitled to see it.
HANDLING OF PATIENT DATAPatient information is regulated. Access rules, retention periods and audit trails are configured to the clinic's own policy and its obligations under the Data Privacy Act.
Student, academic, and administrative information in one place, arranged the way a registrar and an administrator actually work. For schools, colleges, universities, training institutions, and educational networks.
Learning materials, activities, and academic services in a digital environment that shares its student and staff information with SIMS instead of duplicating it.
Registry management for sacramental, canonical, and historical records — including search across the registry, certificate issuance, archives, and authorized verification of a certificate after it leaves the office.
Handles the daily traffic of a chancery or parish office: bookings, requests, scheduling, and the service transactions that arrive at the counter and by phone.
Financial management adapted to how dioceses, parishes, and related institutions actually account for collections, remittances, and fund-level responsibility.
CORRESPONDS TODICE Finance & Accounting. Same financial engine, restructured for ecclesiastical fund accountability rather than commercial reporting.
Personnel management that reflects ecclesiastical structure — clergy, religious, and lay staff each carrying their own kind of assignment and record.
Inventory, property, and asset accountability across parishes and institutions, together with the supporting documentation each item needs.
CORRESPONDS TODICE Property & Asset, at parish and institution level. It is not a commissary or stock system — that is DICE ICMS.
Digital support for social-action programs, assistance, and relief operations — recording beneficiaries and distributions so programs can be accounted for and reported.
Cemetery administration and interment records, with the documentation and long-term retention this kind of register requires.
Periodic security checks tell you how things looked on the day someone looked. DICE Security is a working console for the four things a security team actually does — watch the environment, test it, understand what happened, and explain it to the people who decide what to do next.
Watch network and infrastructure activity and keep continuous visibility over the environment you are responsible for.
Examine authorized systems, infrastructure, and exposed services to find weaknesses before someone else does.
Pull the relevant technical evidence together in one place to understand an event, a suspicious pattern, or an incident.
Turn technical findings into assessments, management summaries, and client-ready documentation without rewriting them by hand.
DICE Security supports internal security operations and authorized professional engagements. Assessment methodology, detection logic, configurations, and defensive architecture are covered under engagement terms and are not published.
DICE doesn't impose one operating model. Each implementation is assembled from the modules that match how that organization is actually run.
Builds around finance, people, inventory, and the operational processes that move product out the door.
Emphasizes academic records, administration, and learning services, with finance and HR behind them.
Central oversight and consolidated reporting, with controlled local operations at each location.
Sacramental registers, parish services, ecclesiastical finance, and institutional records under diocesan structure.
Records, documents, finance, cybersecurity, and administrative services — the backbone functions, done properly.
Software is one layer. We also build and maintain the layers underneath it, and we can take on the work of connecting what you already have.
We design environments where software, infrastructure, networking, security, information, and the organization's own processes function together — so digital transformation is one initiative instead of a series of unrelated purchases.
Security work conducted under defined authorization and agreed scope — from an initial assessment through to monitoring, testing, and incident support when something goes wrong.
Enterprise software depends on infrastructure that holds up. We deploy and administer the computing, network, and storage environments the applications will run on, so both decisions are made together.
Most organizations already have years of investment in applications, databases, documents, and spreadsheets. Transformation rarely means throwing all of it away — it means assessing what's there, keeping what still earns its place, and planning the move for the rest.
Continuing administration, maintenance, monitoring, and technical support for the environment after it goes live — because the day of deployment is the beginning of the system's life, not the end of the project.
Control, connectivity, availability, and budget pull in different directions for every organization. Cloud has real advantages; so does infrastructure you can walk up to. We design for the requirement rather than defaulting to one answer.
Applications and infrastructure run inside an environment the organization owns and controls.
A dedicated hosted environment — managed infrastructure, still defined around your organization.
Cloud infrastructure where it gives a genuine operational or technical advantage.
Local infrastructure combined with selected hosted and cloud services.
We keep running the platform and infrastructure alongside you after deployment.
A structured sequence, agreed before it starts. You always know which stage you are in and what has to be true before the next one begins.
Understand the organization, its objectives, its current environment, and what it actually needs to do.
Map the processes, information, dependencies, and the places where the current way of working breaks down.
Agree the functional and technical shape of the solution before anyone writes code.
Build and configure the applications and services within the agreed scope.
Establish the servers, network, storage, and security the solution will depend on.
Verify functionality and integration under controlled conditions, not in production.
Your own representatives check the system against what was agreed, and sign off.
A controlled transition into live operation, with a defined fallback position.
Prepare the people who will use the system and the people who will administer it.
Agreed technical and operational assistance after go-live.
The environment keeps changing with the organization instead of freezing on launch day.
Where existing information is involved, preservation, verification, and operational continuity are treated as part of the scope. Data that has taken decades to accumulate does not get migrated on a hope.
Described by the shape of the work rather than by client name. Named references, scope and outcomes are provided in proposals, with the client's permission.
Canonical and sacramental registers, certificate issuance and verification, ecclesiastical finance, personnel, property and parish services — operating as one diocesan environment rather than seven office systems.
Commissary production, stock movement between branches, purchasing, ordering and fulfilment, settled against the financial ledger instead of reconciled by hand at month end.
Student and academic information, institutional administration and the records processes that surround them, with registrar workflows treated as the primary design constraint.
Servers, networking, secure connectivity, storage, backup and hybrid environments — specified, deployed and maintained alongside the applications they carry.
We work with established enterprise technologies and select them per project on technical suitability, interoperability, availability, and what the client needs to live with afterwards. Our aim is not to tie an organization to a single manufacturer.
Productivity, cloud, identity, and collaboration — including Azure and Microsoft 365.
Enterprise computing, servers, workstations, storage, and infrastructure.
Business routing, secure connectivity, VPN, and network edge technologies.
Managed networking, wireless infrastructure, switching, and centralized control.
Other enterprise platforms are introduced where they are the better fit for the implementation. These are technologies we deploy, configure and support — listing them indicates working capability, not a formal vendor partnership or endorsement. Our collaboration agreements are named separately, under Engagement.
The working rule: no single external dependency should ever become synonymous with your system. Credentials, configurations and data stay under the organization's control, components stay documented and replaceable, and a change of manufacturer, hosting provider or developer stays a project rather than a crisis.
Organizations that need more than another standalone application — usually because they have already tried that.
Needing finance, workforce, operations, and administration to work as one environment.
Central oversight with real operations running at every location.
Inventory, production, commissary, ordering, and fulfilment at daily volume.
Architectural, construction and engineering practices running cost-controlled projects.
Patient information, clinic operations and billing under regulated access control.
Schools, colleges, universities, training providers, and education networks.
Structured records, documents, workflows, and accountability as core business.
Responsible management of programs, resources, records, and services.
Dioceses, parishes, schools, ministries, social action, and cemeteries.
Visibility, assessment, authorized testing, investigation, and professional reporting.
Organizations differ in size, budget, and how they prefer to invest in technology. DICE engagements are structured accordingly. Pricing, licensing, and project terms are issued in a formal proposal.
You commission an agreed implementation under defined licensing, development, deployment, and support terms.
An initial implementation engagement, followed by recurring subscription services.
Selected DICE solutions delivered as a managed service, without on-site infrastructure.
For broader deployment across departments, branches, facilities, or other organizational units.
Software, infrastructure, security, administration, and support combined under one arrangement.
For complex institutional, multi-location, or strategic projects that don't fit a standard shape.
Technology and infrastructure collaboration that extends the capability and reach of the KHARTALIUM ecosystem.
Brunei-based collaboration supporting regional relationships and opportunities across Southeast Asia.
KHARTALIUM retains ownership, development, and direction of the DICE platform.
Most engagements start with a conversation about the systems you already have, what they cost you in duplicated effort, and which piece is worth fixing first. No obligation to replace anything.