Where the data comes from
The primary discovery source is the official dataset Izsludinātie iepirkumi (e-konkursi) published through the Latvian Open Data Portal. EIS Monitor resolves its dataset metadata and reads the available yearly CSV resources.
A secondary enrichment layer reads public procurement cards and document references from the Electronic Procurement System. It can add scope, requirements, qualification, procedure metadata and public document links when the source exposes them.
How records are normalized
Source rows are merged into one procurement-level record using the procurement identifier. Lots and related source rows remain attached to that record rather than appearing as unrelated market entries.
- 1Discover
Resolve official dataset resources for the configured year range.
- 2Parse
Read source fields and group rows belonging to the same procurement.
- 3Normalize
Map source-specific names and formats into a stable canonical schema.
- 4Compare
Compare the incoming canonical record with the stored current state.
- 5Publish
Update the current view, retain meaningful change events and refresh public views.
What counts as a change
Change detection compares normalized business fields, not raw CSV formatting. This prevents source ordering or presentation differences from being reported as market events.
The procurement has not appeared in the stored current state before.
One or more monitored business fields differ from the previous canonical record.
No monitored business field changed during the run.
Public detail or document evidence improved without changing the discovery-layer business record.
The dashboard change windows aggregate real New and Changed events observed during runs inside the selected 1-day, 1-week, 1-month or 1-year window.
Lifecycle and Work Type classifications
Lifecycle labels are analytical navigation categories derived from public status and stage fields. They are not replacements for the original Latvian source wording, which remains visible on procurement details.
Work Type uses the stored source value when available. Otherwise a deterministic rule set examines scope prefixes, the main and additional CPV descriptions, and title keywords. IT-related evidence can refine a general supply or service record into the IT category.
Why detail coverage varies
Public EIS detail pages are enriched selectively and in bounded batches. A failed or delayed enrichment never removes the canonical discovery record.
Eligible for periodic refresh every 7 days.
Eligible for refresh every 30 days inside the recent-close window.
No periodic refresh unless another trigger requires it.
New records, materially changed records and records missing important detail can also be prioritized. As a result, two procurements discovered at the same time may have different document or enrichment coverage.
How provenance is preserved
Where structured facts are extracted or projected from documents, EIS Monitor can retain the source kind, source reference, observation time and confidence alongside the resulting field. Procurement detail pages expose this field-level provenance when it exists.
Document-derived facts may update the canonical record only through the analysis pipeline. The evidence remains linked so a user can challenge the interpretation rather than treating an extracted value as unexplained truth.
Where deterministic extraction, RAG and AI are used
Document processing starts with download, conversion, structural chunking and deterministic extractors. Configured model-assisted extractors can then add structured candidates. A candidate is stored as a fact only after schema, evidence and confidence validation; material projected values retain document, chunk, page, excerpt, extractor and analysis references where available.
A procurement-specific RAG index can reuse the processed chunks for cited chat and quality analysis. The index is refreshed from content and configuration identity rather than treated as a second authoritative record. Chat history is private to the signed-in user.
Reviews tender material readiness, delivery predictability and verification controls from the tender author’s perspective.
Privately reviews fit, commercial attractiveness, participation risk and conflicting requirements against the requesting supplier’s optional profile.
Missing document or profile evidence stays unknown. It is not automatically scored as a confirmed defect or mismatch.
Configured model, token usage and provider cost are recorded against the active price card; historical operations are not repriced.
How accounts, roles and notifications affect the view
Public market data remains available without an account. Google sign-in enables favorites, in-app notifications, account export/deletion and private chat. Buyer and Supplier capabilities are additive: one account may hold either or both, while administrative authorization remains a separate allowlist.
Favorites can follow a procurement, buyer or supplier. Notifications are created only from persisted new or changed events. Email delivery is disabled by default and occurs only after explicit opt-in; an email failure does not remove the in-app notification.
Supplier preferences and supplier-perspective assessments are user-scoped. Operational telemetry records route/job status, timing, tokens and cost, but must not include chat text, supplier profiles, authentication tokens or private document content.
What the product does not guarantee
- Completeness and timing depend on the public source systems and their published fields.
- Participants, awards, contracts and documents are shown only when publicly exposed and successfully processed.
- Monitoring timestamps describe when EIS Monitor observed data, not necessarily when the source organisation made the underlying decision.
- Automated parsing and document extraction can be incomplete or incorrect and should be checked against the source evidence.
- AI assessments and chat depend on the documents successfully processed and the configured model; a confident answer can still be incomplete.
- Supplier fit cannot be confirmed when the private supplier profile or tender evidence is silent; those cases are shown as unknown.
- Amounts and lifecycle metrics depend on available currency, estimate and contract fields; missing values are not silently treated as known values.
- Costs in different currencies are not converted unless an explicit exchange-rate source is configured.
- EIS Monitor does not provide legal advice and must not replace official procurement notices or documents.
Questions or correction requests can be sent to [email protected] with the procurement identifier and source link.