Home
Platforms
LLA.Nexus — Operations ERP LLA.SmartSkill — Learning & Training LLA.Lexora — Legal ERP LLA.Legal-AI — Legal AI LLA.e-contract — Digital Contracts LLA.Automation Hub — AI & Automation LLA.Infrastructure — Infrastructure LLA.Shipping — Logistics
Capabilities
System Consulting & Design AI & Automation Legal & Digital Compliance Distributor & Compensation Infrastructure & DevOps Logistics & API Integration By Industry
Projects
Legal
Legal & Compliance Solutions Security & Compliance Privacy Policy Terms of Use Cookie Policy
About LLA Insights Support
🇬🇧 English 🇻🇳 Tiếng Việt
Book a Consultation
QĐ 671 aligned software estimation

Software estimation is not just a number. It must be structured for bid-ready dossiers.

LLA.UCP Estimator helps PMs, IT procurement teams, and advisors produce Use Case Point estimates aligned with QĐ 671/QĐ-BTTTT, with explicit traceability for assumptions, technical factors, environmental factors, and final cost.

This page is rebuilt around real software-cost estimation workflows: smart intake, actor/use-case classification, UCP baseline, assumption governance, draft comparison, and direct handoff into Jira/Confluence. The generic integration visual is removed.

QĐ 671 Estimation standard · for regulated bid dossiers
4.8h Draft turnaround · from intake to first estimate
100% Assumption trace · with accountable ownership
Jira + Confluence Delivery handoff · to backlog and specs
LLA UCP Estimator
INTAKE
🧾 Project intake
👥 Actor classification
🧩 Use case complexity
CALCULATION
⚙️ TCF / EF factors
📐 UCP baseline
💵 Cost projection
GOVERNANCE
📚 Assumption registry
✅ Approval flow
🔗 Jira / Confluence
SOFTWARE COST ESTIMATION COMMAND CENTER

QĐ 671/QĐ-BTTTT-aligned UCP dossier with assumption governance

18 use cases · 7 actors · 26 assumptions · 4 draft versions · ⬤ Review-ready
QĐ 671
Reference framework
1.84
Technical factor
528
Normalized UCP
100%
Owned assumptions
UCP calculation lane
Complete input
Actor weighting24 AW
Use case weighting263 UW
TCF x EF1.84 x 1.09
Draft A82 bn VND
Draft B76 bn VND
Draft C71 bn VND
Assumption registry
Integration scopeNeeds sign-off
Internal team capacityOwner: PMO
Timeline baselineApproved
Approval and handoff flow
01. Draft estimate is reviewed by role.
02. Unclear assumptions are blocked before final sign-off.
03. Approved baseline is handed to Jira/Confluence.
Visual now matches UCP estimation context The hero mockup depicts a real software-estimation command centre: intake, actor/use-case classification, technical/environment factor board, assumption registry, draft comparison, and approval flow before dossier submission.

From intuition-based estimates to verifiable cost dossiers

LLA deploys UCP Estimator through a sequence: standardized intake, explainable UCP calculation, assumption governance, and dossier export for independent review. The goal is not a pretty number, but a defendable software-investment decision.

01

Capture structured intake

The system captures scope, project type, legal constraints, and delivery goals in a standardized intake form so the estimate does not start with missing context.

02

Calculate explainable UCP

Actors, use cases, technical factors, and environmental factors are quantified under QĐ 671 with explanations that procurement and review committees can challenge and validate.

03

Govern assumptions and drafts

Each assumption has ownership, status, and revision history; estimation drafts are comparable so teams can see budget and timeline impact clearly.

04

Handoff into delivery

After approval, scoped workloads and cost components are handed to Jira/Confluence so delivery teams execute against the same governed baseline.

The problem is not software. It is operational order.

01

The Reality

Vietnamese IT companies that bid on government software projects face a specific, recurring problem: their cost estimates must comply with QĐ 671/QĐ-BTTTT (Ministry of Information and Communications regulation), but most estimation tools are generic. The team manually applies UCP complexity coefficients in Excel, documents assumptions in a separate file, allocates staff in another spreadsheet, and reconciles everything before submission. When a procurement auditor asks for cost justification three months later, reconstructing the evidence takes days — and the original Excel is already two versions out of date.

02

Why It Matters

For Vietnamese government IT procurement, an estimate that cannot be traced to its UCP calculation, documented assumptions, and authorised approval is not just inconvenient — it is a compliance failure. Procurement regulations require evidence, not just numbers. For IT companies competing on both technical quality and commercial credibility, a robust, auditable estimation process is a competitive differentiator — and a protection against post-contract disputes.

03

LLA's Insight

The UCP methodology is not complicated. What makes it difficult is doing it consistently, documenting it completely, and maintaining the audit trail across project revisions, client negotiations, and regulatory reviews. LLA UCP Estimator encodes the methodology as a governed process — not a calculation shortcut. Every coefficient, every assumption, and every revision is recorded. The AI Intake module classifies functional requirements into UCP components, and the Atlassian integration delivers the approved estimate as Jira epics and Confluence specifications — closing the loop from costing to delivery.

Who this is built for

Government agencies, public-sector technology departments, IT project managers, and software procurement teams in Vietnam that need compliant cost estimates for software projects following Thông tư 04 and QĐ 671.

Modular ASP.NET Core services, PostgreSQL-backed operational records, role-based access, API-first integrations, and audit-ready workflows.

Pain points LLA designs around

Manual estimates in spreadsheets fail audit requirements under QĐ 671/QĐ-BTTTT

Use Case Points calculation is error-prone without a validated tool

Project budget submissions lack the breakdown required for government procurement

Cost assumptions are inconsistent across estimation sessions

From real problems to measurable outcomes

Each capability is designed around a specific operational problem - not a generic feature checklist.

🧮

UCP Calculation Engine per QĐ 671/QĐ-BTTTT

Problem

UCP calculation is done manually in Excel with individually maintained coefficient tables and no version control.

Outcome

Automated UCP calculation with configurable complexity coefficients, adjustment factors, and cost conversion rates — all traceable to QĐ 671/QĐ-BTTTT.

G Every calculation input, coefficient applied, and result is recorded in the audit log — satisfying procurement accountability requirements.
🤖

AI-Assisted Requirements Intake

Problem

Classifying functional requirements into UCP components is the most time-consuming step — done manually by a senior estimator.

Outcome

AI Intake module reads natural language requirements and suggests UCP functional component classifications — accelerating the most labour-intensive step.

G AI classification suggestions are recorded separately from human-approved classifications — maintaining clear accountability for the final estimate.
📋

Assumption Registry

Problem

Assumptions underlying the estimate are documented informally in the proposal document — or not at all.

Outcome

Every assumption is registered in the system with a rationale, risk level, and owner — before the estimate is submitted.

G Assumption registry is part of the permanent project record — available for procurement audit and post-contract review.
🔗

Atlassian Integration (Jira + Confluence)

Problem

Moving from an approved cost estimate to project execution requires manual re-entry of requirements into Jira and Confluence.

Outcome

Approved estimates generate Jira epics and Confluence specification documents automatically — eliminating re-entry and ensuring the delivery spec matches the priced scope.

G The link between estimate and delivery specification is maintained — scope changes are traceable from Jira back to the original cost estimate.
📊

Draft Compare and Version Control

Problem

Estimate revisions are managed in separate Excel files. Comparing versions requires manual side-by-side review.

Outcome

Draft Compare shows side-by-side differences between estimate versions — including changes to assumptions, UCP components, and cost totals.

G All estimate versions are retained with change history — providing a complete negotiation and revision trail.

Functional modules

Use Case Points (UCP) capture and weighting engine

Actor and use case complexity classification per UCP standard

Technical and environmental factor adjustment calculation

QĐ 671/QĐ-BTTTT compliant cost formula application

Effort-to-cost conversion with configurable rate tables

Exportable estimation report with audit trail for submission

Workflow control

Configurable operating workflows with status tracking and approval visibility.

Role-based access

Permissions designed for admins, managers, operators, reviewers, and external users.

API integration

Connects to ERP, CRM, payment, invoice, shipping, warehouse, document, and AI systems.

Audit-ready data

Tracks important actions, status changes, and operational records for review and reporting.

What teams actually see and use

These showcase panels are built from operating screens, workflows, demo data, and control evidence.

Use Case Points (UCP) capture and weighting engine

Actor and use case complexity classification per UCP standard

Technical and environmental factor adjustment calculation

QĐ 671/QĐ-BTTTT compliant cost formula application

Effort-to-cost conversion with configurable rate tables

Exportable estimation report with audit trail for submission

From current state to controlled operations

LLA does not begin with software configuration. LLA begins with operating model design.

01
01
Requirements Intake

Project requirements are captured using AI-assisted intake — natural language requirements are classified into UCP functional components automatically.

OK UCP component list with AI-suggested classifications
02
02
UCP Calculation

Use Case Points are calculated from the component classification with configurable complexity coefficients per QĐ 671/QĐ-BTTTT.

OK UCP total with coefficient documentation
03
03
Assumption Registry

All assumptions underlying the estimate — complexity factors, technology adjustments, risk provisions — are registered in the system with rationale.

OK Documented assumption registry for audit
04
04
Staff and Cost Allocation

HR allocation and cost rates are applied to convert UCP to monetary cost, including commission and overhead structure.

OK Complete cost breakdown with staff allocation
05
05
Approval and Delivery

Estimate is reviewed, compared against previous drafts, approved, and delivered as an Atlassian Spec Pack (Jira + Confluence).

OK Audit-ready approved estimate delivered to client

Sticky product storytelling driven by CMS data

Modules that map to real operating work

Use Case Points (UCP) capture and weighting engine

Actor and use case complexity classification per UCP standard

Technical and environmental factor adjustment calculation

QĐ 671/QĐ-BTTTT compliant cost formula application

Effort-to-cost conversion with configurable rate tables

Exportable estimation report with audit trail for submission

Example operating flow

01

Capture

Collect structured data, documents, roles, and required validation at the point work begins.

02

Route

Move requests through role-based workflows, approvals, assignments, and exception handling.

03

Integrate

Synchronize external services, files, payment, invoice, shipping, AI, or storage events through APIs.

04

Report

Provide dashboards, audit trails, exports, and management views that reflect the real operating state.

Use cases

Government software procurement cost submission

Internal IT project budget planning and approval

Independent verification of vendor cost estimates

Integration story

Vietnamese e-procurement systems

Project management and Jira for scope alignment

Document export for formal submission (PDF/Word)

ERP finance modules for approved project budget tracking

Security and deployment posture

Role-based permissions, audit logs, validation, secure file handling, approval workflows, and environment-based configuration.

Private cloud, VPS, Docker/Coolify, IIS, or hybrid deployment depending on the customer's security and infrastructure requirements.

Not standalone. Connected.

This platform is designed to connect with the broader LLA ecosystem and third-party systems.

Project Delivery

Jira / Atlassian

Approved estimates generate Jira epics and Confluence specifications for project execution.

LLA Platform

LLA ERP Core

Project cost records connected to the ERP operational and financial record.

LLA Platform

LLA Integration Gateway

External data connections for reference cost tables and regulatory coefficient updates.

LLA Platform

LLA Document & E-Contract Suite

Approved cost estimates issued as governed documents with e-signature capability.

From signature to live operations - a clear path

Each phase includes clear delivery gates, ownership, and control checkpoints so operations teams can track progress week by week.

Phase 1 — Setup (Week 1)

QĐ 671 coefficients configured, staff cost rates loaded, project templates set up.

Delivery milestone

Phase 2 — First Project (Weeks 2–3)

First real project estimated through the platform — AI intake, UCP calculation, assumption registry.

Delivery milestone

Phase 3 — Atlassian Integration (Week 4)

Jira and Confluence connection established and tested with spec generation.

Delivery milestone

Phase 4 — Team Adoption (Weeks 5–6)

All estimators trained. Historical projects migrated. Go-live for all new bids.

Delivery milestone

Specific outcomes by leadership role

Each function gets specific, measurable outcomes - not vague benefits.

CEO / Managing Director
Giám đốc Điều hành
  • Audit-ready estimates protect the company in procurement review and post-contract disputes.
  • Consistent estimation methodology reduces commercial risk from underpricing.
COO / Head of Operations
Giám đốc Vận hành
  • Estimation time reduced by AI-assisted requirement classification — the most time-consuming step.
  • Draft Compare eliminates manual version reconciliation during client negotiations.
Compliance / Legal
Tuân thủ & Pháp lý
  • Complete audit trail of every estimation decision — satisfying QĐ 671/QĐ-BTTTT procurement requirements.
  • Assumption registry documents every cost justification before submission.
CTO / Head of IT
Giám đốc Công nghệ
  • Atlassian integration eliminates re-entry of requirements from estimate to Jira — scope stays consistent.
  • All estimation artefacts in one governed system — no Excel files, no scattered assumptions documents.

A software project cost estimation tool built to the Vietnamese government standard QĐ 671/QĐ-BTTTT, applying Use Case Points methodology for accurate, audit-ready project budgets.

LLA designs this platform around auditability, role-based access, API integration, operational dashboards, bilingual-ready content, and deployment models that can run in private cloud, Docker/Coolify, IIS, or hybrid enterprise infrastructure.

Access control, audit, and compliance

LLA UCP Estimator maintains a full audit log of all estimation activities: requirement classification, coefficient selection, assumption registration, version creation, approval decision, and delivery. Staff allocation and cost rates are role-controlled. All changes require named user authorisation. The audit log is exportable for government procurement review and post-contract audit.

What makes LLA's delivery different

01

LLA UCP Estimator is built specifically for QĐ 671/QĐ-BTTTT — not adapted from a generic estimation tool.

02

LLA's AI Intake module classifies functional requirements into UCP components — accelerating the most labour-intensive estimation step.

03

LLA's Atlassian integration closes the loop from approved cost estimate to Jira epics and Confluence specifications.

04

LLA maintains a complete audit trail of every estimation decision — satisfying Vietnamese government procurement accountability requirements.

05

LLA has directly implemented government IT projects and understands the procurement accountability standard from the inside.

Questions customers usually ask

Can this be customized?

Yes. LLA uses the product foundation as a starting point, then adapts workflows, data fields, roles, integrations, and reports to the customer's operating model.

Can it be deployed privately?

Yes. LLA supports private deployment using Docker/Coolify, IIS, PostgreSQL, object storage, and customer-controlled infrastructure when needed.

Does it support bilingual content?

The architecture supports English and Vietnamese content, including translated entity slugs for public detail pages.

Design the system around your operation

LLA can adapt this platform to your workflows, integrations, compliance model, and deployment environment.

Book a Consultation →