The market sounding is intended to gather practical input from the private sector and help validate the proposed approach for the initial reusable-component projects before procurement and implementation.

Draft Terms of Reference (TORs) have been published for the initial set of components. Each TOR includes a request for vendor response.

Vendors are invited to review the relevant materials and submit their responses by 30 September 2026.

The response should help validate the proposed approach and identify practical considerations for implementation, including technical feasibility, delivery approach, maintenance and support, team capability, relevant experience and recommendations that could help shape the projects before procurement and implementation.

The market sounding is a non-binding exercise intended to gather informed market input. It does not constitute a formal procurement process or create any commitment on the part of ISAA or participating vendors.

See the market sounding

The initial set includes:

• Application & Case Management Framework

• API Integration Framework

• Evidence & Document Management Framework

• Notification Framework

• Audit & Activity History Framework

• User & Access Administration Framework

Detailed scope, requirements and expected deliverables are provided in the respective project Terms of Reference and technical specifications.

View the reusable-component project documents

The initial set is intended to establish the first foundation of the reusable-component ecosystem. Additional components may be introduced as further common needs are identified.

Vendors are asked to indicate any relevant Mendix certifications held by their organization or proposed team.

At this stage, Mendix certification is not a mandatory requirement. The information is being requested to help understand the level of relevant capability and experience currently available in the market.

As the LCNC ecosystem develops, certification requirements will be further defined.

The current market sounding process is expected to conclude in September 2026. The procurement process for the reusable-component projects is expected to proceed in October 2026.

Feedback received during the market sounding will help refine the technical, delivery and governance approach before procurement.

The initial reusable components are currently anticipated to be delivered by January 2027.

For the current Mendix-based projects, developed reusable components are expected to be published and managed through the designated private Mendix Marketplace.

Components should be packaged and documented so that the development teams can understand, configure, adopt and maintain them independently.

Detailed requirements covering packaging, documentation, versioning, publishing, release management are provided in the respective project Terms of Reference and will be further established through the applicable LCNC development and governance standards.

Reusable components developed under the initiative are owned by the State.

ISAA will progressively develop and publish common LCNC development and governance standards as the initiative advances.

These standards will address areas such as naming, component structure, documentation, security, testing, versioning, publishing and lifecycle management.

For the current Mendix-based projects, Mendix official guidance, naming conventions and established best practices should be followed wherever applicable until more specific initiative-level standards are published.

This depends on the purpose and defined scope of the individual component.

Where front-end functionality is necessary to provide the intended reusable capability, the relevant UI elements may form part of the component. Components focused primarily on backend or integration capabilities may have more limited UI requirements.

The applicable project Terms of Reference and technical specification should be treated as the primary reference for determining the functional and UI scope of each component.

Yes. Existing components from the Mendix Marketplace or other trusted sources may be considered where they are appropriate for the intended use case.

Use of an existing component does not remove the requirement to comply with applicable architecture, security, development and governance requirements.

The version and dependencies of any third-party component should be documented.

Before either Mendix or the third-party component is upgraded, compatibility should be reassessed and appropriate testing performed to confirm that the component continues to operate correctly.

More detailed requirements concerning long-term maintenance, support and responsibility for third-party dependencies will be established through the applicable governance and lifecycle standards.

The project Terms of Reference expect reusable components to be demonstrated in a working application and to include sufficient supporting material for other teams to understand and adopt them.

Each reusable-component project may initially use its own demonstration or sample application.

As the projects progress, common patterns may be identified and consolidated into a shared sample application or reusable template for future LCNC projects.

Mendix supports developing and running applications locally, allowing development and testing to take place in the developer’s local environment.

The staging and production environments have been provisioned and are ready for use.

Mendix provides the tools and platform capabilities required to support development, deployment and application delivery.

For detailed information please refer to the Mendix Knowledge Base / Documentation.

Maintenance, support and applicable Service Level Agreement requirements will form part of the contracting arrangements for the reusable-component projects.

The relevant contracts will define responsibilities for ongoing maintenance, support, issue resolution, upgrades, compatibility and agreed service levels.

Further lifecycle and governance requirements will be established as the reusable-component ecosystem develops.

For any questions:

• Initiative-related questions: astghik.ghevondyan@isaa.am, +37443276730

• Technical-related questions: davit.aleksanyan@isaa.am, +37493754539