Circular No. 16/2024/TT-BTTTT provides detailed provisions on the implementation, supervision, and acceptance of projects investing in IT applications; determines service quality requirements and special contents of IT service leasing contracts. It applies to entities implementing IT investment projects funded by state budget funds.

CIRCULAR

Detailed provisions on the implementation, supervision, and acceptance work for information technology application investment projects; determination of service quality requirements and special contents of service leasing contracts for customized information technology services.

On the basis of Law on Information Technology June 29, 2006;

Decree No. 73/2019/ND-CP September 5, 2019 Government Decree No. 73/2019/ND-CP on management of information technology application investment using state budget funds;

Decree No. 82/2024/ND-CP July 10, 2024 Government Decree No. 82/2024/ND-CP amending and supplementing certain articles of Government Decree No. 73/2019/ND-CP dated September 5, 2019 on management of information technology application investment using state budget funds; 73/2019/ND-CP September 5, 2019 Government Decree No. 73/2019/ND-CP on management of information technology application investment using state budget funds;

Decree No. April 19, 2022 of the Government dated July 26, 2022, of the Government stipulating the functions, tasks, powers, and organizational structure of the Ministry of Information and Communications;

At the request of the Director of the National Digital Transformation Agency,

The Minister of Information and Communications issues this Circular detailing the implementation, supervision, and acceptance work for information technology application investment projects; determination of service quality requirements and special contents of service leasing contracts for customized information technology services.

PART I

GENERAL PROVISIONS

Article 1. Scope of Regulation

This Circular details the implementation, supervision, and acceptance work for information technology application investment projects; determination of service quality requirements and special contents of service leasing contracts for customized information technology services as stipulated in Government Decree No. 73/2019/ND-CP dated September 5, 2019 on management of information technology application investment using state budget funds (referred to as Government Decree No. 73/2019/ND-CP) (amended and supplemented by Government Decree No. 82/2024/ND-CP dated July 10, 2024 amending and supplementing certain articles of Government Decree No. 73/2019/ND-CP dated September 5, 2019 on management of information technology application investment using state budget funds (referred to as Government Decree No. 82/2024/ND-CP)), including:

1. Implementation, supervision, and acceptance work for information technology application investment projects as stipulated in Clause 5, Article 32 of Government Decree No. 73/2019/ND-CP (amended and supplemented in Clause 23, Article 1 of Government Decree No. 82/2024/ND-CP).

2. Determination of quality requirements for customized information technology services as stipulated in Clause 3, Article 54 of Government Decree No. 73/2019/ND-CP (supplemented in Point b, Clause 32, Article 1 of Government Decree No. 82/2024/ND-CP).

3. Special contents of service leasing contracts for customized information technology services as stipulated in Clause 5, Article 52 of Government Decree No. 73/2019/ND-CP (amended and supplemented in Clause 30, Article 1 of Government Decree No. 82/2024/ND-CP).

Article 2. Applicability

This Circular applies to the subjects specified in Article 2 of Government Decree No. 73/2019/ND-CP.

Chapter II

CONTENTS OF IMPLEMENTATION, SUPERVISION, AND ACCEPTANCE WORK FOR INFORMATION TECHNOLOGY APPLICATION INVESTMENT PROJECTS

Section 1. IMPLEMENTATION AND SUPERVISION OF IMPLEMENTATION WORK

Article 3. Basic activities in implementation and supervision of implementation work

1. Conducting implementation work and maintaining implementation activity logs.

2. Conducting supervision of implementation work and maintaining supervision activity logs.

3. Supervising the authors of detailed design organizations and individuals.

Article 4. Implementation work

The contractor shall carry out the following tasks (including the main contractor in the case of a mixed tender package):

1. Prepare a detailed implementation schedule before commencing work in accordance with the project implementation progress management regulations stipulated in Article 33 of Decree No. 73/2019/NĐ-CP.

2. Establish a quality management system appropriate to the scale of implementation (if required by the project owner), specifying the responsibilities of each department and individual during the implementation process.

3. Allocate manpower and equipment for implementation in accordance with the contract.

4. For procurement, construction, installation, information system setup, hardware configuration, material and equipment calibration, and commercial software and widely-used software (including widely-used software modified or supplemented with certain functions, features, performance)

a) Transport and hand over the information systems, hardware, materials, equipment, commercial software, and widely-used software to the project owner in accordance with the contract; notify the project owner of transportation, storage, and preservation requirements (if applicable);

b) Provide the project owner with certificates, certifications, relevant information, and documentation concerning the information systems, hardware, materials, equipment, commercial software, and widely-used software as prescribed by the contract and approved detailed design;

c) Organize the inspection of the quality, quantity, and types of information systems, hardware, materials, equipment, commercial software, and widely-used software before handing them over to the project owner;

d) Repair or replace information systems, hardware, materials, equipment, commercial software, and widely-used software that do not meet quality requirements under the contract;

đ) Carry out construction, installation, configuration, setting up information systems, hardware, materials, equipment, installing commercial software, widely-used software, and trial operation of information systems, equipment, hardware, commercial software, and widely-used software.

5. For development, upgrading, expansion of internal software, databases

a) Determine requirements;

b) Analyze and develop plans for developing, upgrading, expanding internal software;

c) Program and write code;

d) Conduct internal testing of the software by the implementing contractor;

đ) Install internal software and databases.

6. Create databases; standardize and convert data for database creation; enter data; provide training on usage and management for staff; support, manage, operate, and perform other implementation tasks as specified in the contract and approved detailed design.

7. Address and rectify errors and defects arising during the implementation process (if any).

8. Report to the project owner on progress, quality, and volume according to the agreement in the contract and any urgent requests from the project owner.

9. Coordinate with the project owner and related units during the supervision of implementation, testing, trial operation, acceptance, and handover processes.

10. Request the project owner to conduct acceptance work.

11. Perform other tasks as stipulated in the signed contract.

In cases where the project owner implements the work themselves, depending on the scope of the project, the level of quality requirements, or actual conditions, the project owner decides to select and implement the above tasks in accordance with regulations, ensuring quality and effective management of project implementation.

Article 5. Establishment of Implementation Work Logs

1. The implementation work logs shall be established by the implementing contractor to describe the situation of work and reflect the information exchanged between the project owner, the implementing contractor, detailed design organizations, and other related parties. 2. The implementation work logs must be consistent with the detailed progress schedule specified in Clause 1 of Article 4 of this Circular, recorded on a daily basis for procurement, construction, installation of information systems, hardware, material adjustment, equipment calibration, and commercial software installation, commonly used software; recorded according to milestones for internal software development, expansion, upgrade, database implementation, bound into volumes, numbered, and stamped with the seal of the implementing contractor.

3. The contents of the implementation work logs include the following basic information:

a) List of deployment staff (positions and responsibilities of each person) of the implementing contractor and the supervising authorizing entity (if any);

b) Progress of the implementation activities on a daily basis for procurement, construction, installation of information systems, hardware, commercial software installation, commonly used software; progress of the implementation activities according to milestones for internal software development, expansion, upgrade, database implementation;

c) Detailed description of incidents, malfunctions, violations, discrepancies, other issues arising during the implementation process and measures taken to address them (if any);

d) Requests from the project owner; suggestions from the implementing contractor, detailed design preparation entities (if any), implementation supervision entities (if any);

đ) Opinions on resolving issues arising during the implementation process from all related parties (if any).

4. The implementation work logs shall be established according to Model No. 1 and Model No. 1.1 in Appendix I issued together with this Circular.

Article 6. Implementation of Supervision of Deployment Activities

1. For investment projects during the implementation of construction, installation of information systems, hardware, commercial software installation, commonly used software, material adjustment, and equipment calibration, the system of supervision of deployment activities must be implemented in accordance with Article 32 of Decree No. 73/2019/NĐ-CP (amended and supplemented at Clause 23 of Article 1 of Decree No. 82/2024/NĐ-CP). The project owner shall either conduct the supervision themselves or hire organizations or individuals to perform it (referred to collectively as the supervision entity). The main tasks of the supervision activity are stipulated in this Article.

2. In cases where mixed tender packages are applied:

a) The main contractor is responsible for organizing quality management and supervising the deployment for their own work and that of subcontractors; inspecting the deployment work carried out by subcontractors; fulfilling other responsibilities assigned by the project owner in accordance with the signed contract; the main contractor shall either conduct the supervision themselves or hire qualified consulting firms to supervise one, several, or all aspects stipulated in this Article, which must be specified in the contract between the main contractor and the project owner. If the main contractor conducts both deployment and supervision, they must establish an independent supervision department separate from the direct deployment department;

b) The project owner is responsible for checking and urging the implementation of agreed-upon quality management activities in the contract; inspecting the deployment supervision conducted by the main contractor.

3. Checking the conditions for deployment

a) Ensuring the availability of deployment sites and relevant technical factors;

b) Ensuring the existence of signed deployment contracts;

c) Ensuring the approval of detailed design documents;

d) Ensuring the presence of detailed implementation schedules established by the implementing contractor;

đ) Ensuring safety operation measures, fire prevention, and explosion protection measures (if applicable);

e) Preparing inspection records for deployment conditions.

4. Checking the suitability of the implementing contractor's capacity compared to the contract

a) Inspecting the deployment workforce of the implementing contractor at the site to ensure compliance with the workforce committed in the contract and the tasks assigned to them;

b) Inspecting the quality management system as specified in Clause 2 of Article 4 of this Circular (if applicable);

c) Inspecting the funding allocation of the implementing contractor to fulfill the contract as committed by the contractor (if mentioned in the contract);

d) Inspecting other capacity requirements stated in the deployment contract;

đ) Preparing inspection records for the suitability of the implementing contractor's capacity compared to the contract.

5. Checking the suitability of materials, equipment, hardware, and software before construction, installation, and installation

a) Inspecting the quantity and physical appearance of materials, equipment, hardware; verifying proof of copyright (if applicable) for commercial software (legality, quantity); verifying proof of commonly used software;

b) Inspecting certificates of origin (CO), manufacturer's quality certificates (CQ), and other relevant documents for materials, equipment, hardware as stipulated in the deployment contract before implementation;

c) Inspecting technical parameters of materials, equipment, hardware against the information in the contract and detailed design documents before implementation;

d) When there is suspicion regarding materials, equipment, hardware, or software, the deployment supervision entity must collaborate with the project owner to directly inspect the materials, equipment, hardware, and software installed in the project. If the materials, equipment, hardware, or software do not comply with the approved detailed design, the deployment supervision entity will cooperate with the project owner to request the implementing contractor to remove them from the implementation area;

đ) Preparing inspection records for materials, equipment, hardware, and software before construction, installation, and installation.

6. Supervision during the implementation process

6. Supervision during the implementation process

a) Inspect and supervise the contractor's implementation process at the project site. The inspection results must be recorded in the implementation supervision logbook;

b) Check the protection of materials, equipment, hardware, and software installed, set up, or installed within the project's area, zone, or location (if applicable). In case of damage, malfunction, or impact on the area, zone, or location, the implementation supervision unit shall report to the project owner to request the contractor to prepare a site record according to Model No. 3 of Appendix I issued with this Circular;

c) Coordinate with relevant parties to resolve any issues or occurrences during the implementation process (if any);

d) Propose the project owner to organize adjustments to the detailed design when errors or unreasonable aspects of the detailed design are discovered;

đ) Participate in acceptance and handover of project products or work items;

7. Supervise the volume of implementation

a) Supervise the implementation volume according to the implementation contract and approved detailed design;

b) Confirm the implementation volume completed by the contractor and compare it with the approved detailed design. If there are changes in volume compared to the contract and detailed design, report to the project owner for review and approval procedures. The approved change volume is the basis for acceptance of work volume, payment, and settlement;

8. Supervise the progress of implementation

a) Monitor and supervise the detailed progress of implementation;

b) Propose to the project owner, contractor, and related parties to adjust the detailed schedule and overall implementation progress if the implementation progress is delayed in certain stages;

c) Propose the project owner to impose penalties and require the contractor to compensate for losses caused by delayed implementation according to the agreement in the contract between the project owner and the contractor;

9. Supervise changes during the implementation process (if any).

During the implementation process, if unreasonable factors or new elements appear that would affect the project's investment quality, implementation progress, implementation measures, and investment effectiveness without changing the detailed design, the implementation supervision unit shall report to the project owner and propose the contractor to prepare a site record according to Model No. 3 of Appendix I issued with this Circular;

10. Other contents of implementation supervision as stipulated in the implementation supervision contract (if any);

11. Prepare the Implementation Supervision Result Report.

The implementation supervision unit is responsible for preparing the Implementation Supervision Result Report to submit to the project owner. The main content of the Implementation Supervision Result Report is according to Model No. 2.2 of Appendix I issued with this Circular;

Article 7. Maintain the Implementation Supervision Logbook

1. The Implementation Supervision Logbook is established by the implementation supervision unit to describe activities during the implementation supervision process and reflect information exchanged and confirmed between the project owner, the implementation supervision unit, and other related parties;

2. The Implementation Supervision Logbook must be recorded daily in accordance with the implementation progress and bound into volumes, numbered, and stamped with the seal of the implementation supervision unit;

3. The content of the Implementation Supervision Logbook includes the following basic items:

a) List of staff participating from the implementation supervision unit (position and responsibilities of each person) and the authorizing supervision unit (if any);

b) Content, development, and results of the implementation supervision situation corresponding to each implementation item of the contractor;

c) Deviations in the implementation process compared to the implementation contract, detailed design files, specifying the cause, accompanied by corrective measures (if any); proposals, recommendations (if any);

d) Site records prepared during the implementation supervision process are part of the content of the Implementation Supervision Logbook and cannot be separated;

4. The Implementation Supervision Logbook is established according to Model No. 2 and Model No. 2.1 of Appendix I issued with this Circular.

Article 8. Implementation of Author Supervision

1. Organizations and individuals responsible for detailed design shall implement author supervision.

2. Contents of implementing author supervision

a) Explain and clarify detailed design documents upon request from the project owner, contractor, or implementation supervision unit.

b) Cooperate with the project owner when requested to resolve issues and arising matters related to design during implementation, adjust designs to fit actual implementation conditions, address unreasonable aspects in design according to the project owner's requirements; provide comments on implementation work logs and implementation supervision logs regarding supervision contents.

c) Coordinate with the implementation supervision unit to promptly notify the project owner and recommend measures to handle situations where the contractor's implementation does not comply with approved designs.

d) Participate in acceptance when requested by the project owner. In cases where products or project works do not meet acceptance conditions, timely written opinions must be sent to the project owner.

đ) Prepare reports on the results of author supervision. Organizations and individuals responsible for detailed design shall prepare reports on the results of author supervision to submit to the project owner. The main content of the Report on the Results of Author Supervision follows Model No. 2.3 of Appendix I issued together with this Circular.

Section 2. ACCEPTANCE WORK

Article 9. Basic Procedures in Acceptance Work

1. Conduct testing or trial operation before organizing product or project work acceptance.

a) For commercial equipment, hardware, software, and commonly used software, the contractor shall take the lead and cooperate with the project owner to organize trial operations.

The content of trial operations follows the guidance in Appendix No. 1 of Appendix II issued together with this Circular. The results of trial operations are compiled into reports by the contractor.

b) For internal software, depending on quality requirements and actual conditions, the project owner shall consider and decide to apply testing or trial operation methods and bear responsibility for their decisions. The content of trial operations for internal software follows the guidance in Appendix No. 2 of Appendix II issued together with this Circular. During the trial operation process of internal software, the project owner needs to control software quality based on non-functional requirements using the contractor's internal test result report. The results of trial operations for internal software are compiled into reports by the project owner.

The content and results of testing follow the guidance in Appendix No. 3 of Appendix II issued together with this Circular. Testing results are compiled into reports by the project owner (if conducted internally) or an independent testing unit (if hired).

2. Implement product or project work acceptance activities in accordance with regulations.

Article 10. Acceptance of Completed Products and Works

1. Requirements for accepted products and works

a) Products or works are fully completed in terms of quantity, quality, progress, and contractual and approved detailed design requirements.

b) Products or works have been tested or trial operated and meet quality requirements stipulated in Article 34 of Decree No. 73/2019/NĐ-CP and Article 9 of this Circular.

2. The project owner and relevant units shall agree on the content, time, and location of acceptance. Acceptance results are recorded in minutes following Model No. 6 of Appendix I issued together with this Circular.

Based on post-acceptance files and documents, the project owner is responsible for compiling a list of completion files for archival purposes and storing and preserving project files and documents in accordance with archival laws. The list of completion files for archival purposes follows Appendix III issued together with this Circular.

SPECIFYING QUALITY REQUIREMENTS FOR INFORMATION TECHNOLOGY SERVICES CONTRACTS AND SPECIAL CONTENTS AS PER CUSTOMER REQUIREMENTS

Chapter III

DETERMINATION OF QUALITY REQUIREMENTS FOR INFORMATION TECHNOLOGY SERVICES AND SPECIFIC CONTENTS OF CUSTOMIZED INFORMATION TECHNOLOGY SERVICE LEASE CONTRACTS

Section 1. DETERMINING QUALITY REQUIREMENTS FOR SERVICES

Article 11. Determining Quality Requirements for Services

1. Quality requirements for services shall be determined based on criteria, including:

a) Functional criteria;

b) Operational performance criteria;

c) Information security and data safety criteria;

d) Non-functional criteria;

đ) Customer satisfaction criteria;

e) Service management criteria.

2. The quality requirement criteria specified in Clause 1 of this Article shall be guided by Appendix IV issued together with this Circular.

3. For each specific service rental plan, based on the particular requirements of the agency or unit, the main party renting the service shall consider and select to apply some or all of the criteria stipulated in this Article and supplement or update other criteria (if necessary).

Section 2. SPECIAL CONTENTS OF INFORMATION TECHNOLOGY SERVICE RENTAL CONTRACTS AS PER SPECIFIC REQUIREMENTS

Article 12. Scope of Supply Requirements

1. Technical requirements for the service in the service rental contract shall be determined corresponding to each stage during the contract implementation period, consistent with the service quality requirements in the approved rental plan.

Quality control of the service corresponding to each stage during the contract implementation period and serving as the basis for acceptance of service supply results as prescribed in Article 13 of this Circular.

2. Other requirements in the service rental contract

a) Requirements and procedures for transferring information and data generated during the service rental period

The main party renting the service and the service provider shall agree and unify the requirements, tasks, and procedures for transferring information and data generated during the service rental period to the main party renting the service, including: After the rental period ends, the service provider must transfer all information and data generated during the rental period to the main party renting the service according to the agreed plan in the contract; methods, tools, tasks, procedures, and roles and responsibilities of each party during the transfer process; plans for statistics, classification, inspection, and determination of the status of information and data before transfer; plans for data storage, backup, and recovery before transfer; plans for inspecting the status of information and data after transfer; plans for inspecting and reconciling data after transfer; plans for deleting information and data related to the main party renting the service from systems at the service provider after transfer; commitments of the service provider after transfer; other requirements regarding the transfer of information and data generated during the service provision; other transfer requirements related (if any);

b) Requirements for ensuring information security and data safety

The main party renting the service and the service provider shall agree and unify the requirements for ensuring information security in accordance with laws on information security, and the requirements for ensuring data quality and safety in accordance with laws on data;

c) The main party renting the service and the service provider shall agree and unify the requirements concerning copyright, intellectual property rights related to the service, and other requirements depending on the nature, characteristics, requirements, and actual needs of the service provided under the contract and in accordance with laws on copyright and intellectual property.

Article 13. Quality Control of Services and Acceptance of Service Provision Results

1. Quality control of information technology services during the service provision preparation phase

a) Services to be put into use under the contract must undergo quality control. The quality control process for information technology services during the service provision preparation phase shall be carried out by the service procurement entity through testing or trial operation, or other inspection methods corresponding to each specific criterion in the service procurement contract.

The results of the quality control of services serve as the basis for acceptance and handover of services to be put into use. Documents serving as the basis for acceptance include: Test result reports or trial operation reports; Inspection and evaluation result reports (if applicable); Other relevant minutes and documents.

b) The service procurement entity and the service provider shall agree and sign an acceptance and handover record for information technology services to be put into use according to Model No. 1 of Appendix V issued together with this Circular as the basis for officially putting the service into use.

2. Quality control of information technology services during the service procurement phase

a) Services during the service procurement phase under the contract must undergo quality control. The service procurement entity shall organize the monitoring and supervision of the service provision process by the service provider and the inspection and evaluation of service quality during the service procurement phase.

The inspection and evaluation of service quality shall be conducted through surveys, collection, analysis, and assessment of feedback from organizations and individuals using the service or periodic and spot checks on the service provision system and the service provider to assess service quality based on specific criteria determined or combined forms.

The service provider has the responsibility to provide services and report on the service provision results during the service procurement phase to the service procurement entity periodically or at random as agreed in the contract.

b) The results of the quality control of services serve as the basis for accepting the service provision results.

3. Acceptance of service provision results

a) The service procurement entity and the service provider shall agree and sign an acceptance record for the results of information technology service provision according to Model No. 5 of Appendix V issued together with this Circular as the basis for payment as agreed in the contract.

b) Documents serving as the basis for acceptance include: Service provision result reports established by the information technology service provider according to Model No. 2 of Appendix V issued together with this Circular; Information technology service quality control result reports established by the service procurement entity according to Model No. 3 of Appendix V issued together with this Circular; Minutes of information and data transfer formed during the service provision process (if applicable) according to Model No. 4 of Appendix V issued together with this Circular; Other relevant minutes and documents.

Article 14. Timeframe and Implementation Plan of the Information Technology Service Procurement Contract

1. The contract implementation period runs from the date the contract becomes effective until all parties fulfill their obligations as agreed in the contract. It is divided into the following phases:

a) Service provision preparation period: Starting from the date the contract becomes effective. It includes: The time taken by the service provider to build and develop the service; Testing or trial operation time; Training and guidance time for service usage (if applicable).

b) Service procurement period: Starting from the date of acceptance and handover of the service for use until the end of the service procurement period.

c) Transfer period and fulfillment of other obligations: Starting from the transfer commencement date. It includes the time for transferring information and data formed during the service provision process and the time for the service provider to complete other obligations and responsibilities as agreed in the service procurement contract.

2. Implementation plan of the information technology service procurement contract

The service provider is responsible for preparing the implementation plan of the service procurement contract for the service procurement entity to review and confirm. The plan content shall include at least the following items:

a) The sequence and time schedule for performing tasks in each main phase of the service procurement contract as stipulated in Clause 1 of this Article.

b) Milestones for completing and handing over work, key products, and reports from the service provider according to the contract implementation progress.

Article 15. Payment of Contracts for Information Technology Services

The principal contracting party and the service provider shall agree in the contract on the number of payments, payment periods/stages, payment dates, payment methods, payment deadlines, payment documentation, and payment conditions. Among these, the payment periods/stages and payment dates must be consistent with the method of determining the cost of leasing services in the approved leasing plan or adjusted approval (if applicable).

Chapter IV

IMPLEMENTING PROVISIONS

Article 16. Effectiveness and Transitional Provisions

1. This Circular takes effect from February 14, 2025, and replaces the following Circulars:

a) Circular No. 23/2020/TT-BTTTT dated September 9, 2020, issued by the Minister of Information and Communications, stipulating special contents of contracts for leasing information technology services funded by state budget funds;

b) Circular No. 24/2020/TT-BTTTT dated September 9, 2020, issued by the Minister of Information and Communications, stipulating the implementation, supervision, and acceptance of information technology application projects funded by state budget funds.

2. For information technology investment application projects and individual leasing plans for information technology services approved before the effective date of Decree No. 82/2024/NĐ-CP, subsequent steps shall be carried out according to the regulations on implementation, supervision during implementation, project acceptance, determination of service quality requirements, and special contents of contracts for leasing individual information technology services at the time of approval.

Article 17. Implementation Organization

1. State agencies, organizations, and individuals participating in or related to activities applying information technology using state budget funds are responsible for implementing this Circular.

2. During the implementation process, if any issues arise or difficulties occur, relevant agencies, organizations, and individuals should report them to the Ministry of Information and Communications (National Digital Transformation Agency) for review, guidance, and resolution./.

ANNEX I

LIST OF DOCUMENTATION FORMS FOR IMPLEMENTATION, SUPERVISION, AND ACCEPTANCE OF INFORMATION TECHNOLOGY APPLICATION PROJECTS
(Attached to Circular No. 16/2024/TT-BTTTT dated December 30, 2024, issued by the Minister of Information and Communications)

Form No. 1. Cover of Implementation Work Diary

IMPLEMENTATION WORK DIARY

VOLUME NUMBER:...

1. Project Name:..............................................................................................

2. Name of Component:......................................................................................................

3. Deployment Location:.............................................................................................

4. Project Sponsor: ............................................................................................................

Representative's Full Name: ...

5. Project Management Board or Consulting Management Organization: .....................

Representative's Full Name: ...

6. Contractor Implementing: Full Name of Responsible Person: ...............................................................................................

7. Supervision Unit (if any):

Full Name of Responsible Person: ................................................

8. Detailed Design Organization or Individual:

9. Deployment Information...............................

Implementation Contract Number: ... Date...

Contracted Start Date:... Actual Start Date...

Contracted End Date:... Actual End Date...

This volume contains:... pages, numbered sequentially from 01 to...

Full Name, Signature of the Person Responsible for Implementation Work, Managing the Implementation Work Diary:

Nguyen Van A Signature:

Full Name, Signature of the Person Responsible for Supervision Work (if any):

Nguyen Van B Signature:

..., Date... Month... Year...

Content of Implementation Work Diary ¹

I. Implementation Work Content

Implementation Time

Form No. 2. Cover of Supervision Work Diary

.........................................................................................................................................

.........................................................................................................................................

.........................................................................................................................................

.........................................................................................................................................

SUPERVISION WORK DIARY

4. Project Sponsor

VOLUME NUMBER:...

1. Project Name: ....................................................................................................................

2. Name of Component:..............................................................................................................

3. Deployment Location: ......................................................................................................

5. Project Management Board or Consulting Management Organization (if any):: ..................................................................................................................

Representative's Full Name: ...

6. Implementing Contractor:...................................

Representative's Full Name: ...

Full Name of Responsible Person: ................................................................................................

7. Supervision Unit:

Full Name of Responsible Person: ... .............................................................................

9. Supervision Information

9. Deployment Information .................................................................................

Supervision Contract Number: ... Date...

Contracted Start Date:... Actual Start Date...

Contracted Supervision Start Date:... Actual Supervision Start Date...

Contracted Completion Date:... Actual Completion Date...

Contracted Supervision Completion Date:... Actual Supervision Completion Date...

Full Name, Signature of the Person Responsible for Supervision Work, Managing the Supervision Work Diary:

Full Name, Signature of the Person Responsible for Implementation Work, Managing the Implementation Work Diary:

supervision work

Full Name, Signature of the Person Responsible for Supervision Work (if any):

Content of Supervision Work Diary ³

I. Supervision Work Implementation Content

Supervision Time

Form No. 2. Cover of Supervision Work Diary

...................................................................................................................................

...................................................................................................................................

...................................................................................................................................

...................................................................................................................................

..., Date... Month... Year...

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

REPORT ON SUPERVISION RESULTS

To: Project Sponsor

General Project Information

1. - Project Name.

- Component or Work Name.

- Sponsor Name.

- Deployment Location.

- Implementing Contractor Name.

- Detailed Design Organization or Individual Name.

- Supervision Unit Name (in case of hired supervision).

2. Supervision Content

- Conditions for Implementation.

- Suitability of the Implementing Contractor's capacity compared to the contract.

- Suitability of materials, equipment, hardware, software before installation, setup, and configuration.

- Supervision content during implementation.

- Supervision content of implemented quantities.

- Content of supervision on the volume of implementation.

- Content of progress monitoring.

- Content of monitoring changes during implementation (if any).

- Other contents according to the supervision contract for implementation work (if any).

3. Conclusions and recommendations.

4. Attached documents.

- Implementation monitoring logbook.

- Related minutes.

REPRESENTATIVE OF THE AUTHORITY, UNIT.
MONITORING IMPLEMENTATION WORK.
(Sign, write full name, position and stamp)

Model No. 2.3. Report on the results of author supervision.

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

REPORT ON SUPERVISION RESULTS

REPORT ON THE RESULTS OF AUTHOR SUPERVISION.

General Project Information

1. - Project Name.

- Component or Work Name.

- Sponsor Name.

- Deployment Location.

- Implementing Contractor Name.

- Detailed Design Organization or Individual Name.

- Supervision Unit Name (in case of hired supervision).

2. Supervision Content

- Conditions for Implementation.

- Results of implementing the contents explained and clarified in the detailed design documentation.

- Results of coordinating with the project owner to resolve issues and emerging matters related to design during implementation.

- Adjustments made to the design to align with actual implementation.

- Results of addressing unreasonable aspects of the design as requested by the project owner.

- Results of coordinating with the implementation work monitoring unit to promptly inform the project owner and recommend measures when non-compliance with approved designs is detected from the contractor's implementation.

- Results of other contents implemented by the organization or individual supervising the author according to the project owner's requirements during implementation and monitoring (if any).

3. Conclusions and recommendations.

4. Attached documents.

- Related minutes.

REPRESENTATIVE OF THE ORGANIZATION, INDIVIDUAL SUPERVISING THE AUTHOR.
(Sign, write full name, position and stamp)

Model No. 3. Field Minutes.

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

..., day... month... year...

FIELD MINUTES.

PROJECT:..............................

I. Participants:

1. Representative of the project owner:

- Mr./Ms.:... Position:...

2. Representative of the implementation work monitoring unit:

- Mr./Ms.:... Position:...

3. Representative of the organization or individual responsible for detailed design (if any):

- Mr./Ms.:... Position:...

4. Representative of the contractor:

- Mr./Ms.:... Position:...

5. Representative of other relevant units (if any):

- Mr./Ms.:... Position:...

II. Time, location, and implementation item:

(Specify time, location, and implementation item clearly)

III. Contents:

(Contents of the field minutes as required by this Circular)

IV. Opinions, recommendations, proposals (if any) of the parties involved.

...................................................................................................................................

...................................................................................................................................

...................................................................................................................................

The parties directly preparing this record are responsible under the law for its contents. This record is prepared in ... (in writing) copies, all having equal legal value, ... retains ... copy, ... retains ... copy, ... retains ... copy, .../.

Model No. 4. Inspection Record.

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

REPORT ON SUPERVISION RESULTS

INSPECTION RECORD <NAME OF THE INSPECTION OBJECT>

PROJECT:..............................

I. Inspection Object

(Specify the inspection object: inspecting implementation conditions/inspecting the suitability of the contractor's capacity/inspecting materials, equipment, software, etc.)

II. Participants:

1. Representative of the project owner:

- Mr./Ms.:... Position:...

2. Representative of the implementation work monitoring unit:

- Mr./Ms.:... Position:...

3. Representative of the organization or individual responsible for detailed design (if related to author supervision):

- Mr./Ms.:... Position:...

4. Representative of the contractor:

- Mr./Ms.:... Position:...

5. Representative of other relevant units (if any):

- Mr./Ms.:... Position:...

III. Time and Location of Inspection:

Start: ..., day ... month ... year ...

End: ..., day ... month ... year ...

At:...

IV. Contents:

(Contents of the record as specified in this Circular).

V. Opinions, Recommendations, Proposals (if any) of the Parties:

...................................................................................................................................

...................................................................................................................................

...................................................................................................................................

The parties directly participating in preparing this record are responsible for its contents. This record is prepared in ... (in writing) copies, all having equal legal value, ... retains ... (one) copy, ... retains ... (one) copy,.../.

Briefly describe technical improvements, production processes, raw materials, designs; new technology applications such as automation, digitalization, clean technology; management, marketing, distribution solutions; products winning awards or certifications related to innovation…):…Model No. 5. Technical Acceptance Record.

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

..., day ... month ... year ...

ACCEPTANCE RECORD. <NAME OF THE ACCEPTANCE OBJECT>

PROJECT:...............................

I. Acceptance Object

(Specify the acceptance object such as: installation, system installation, equipment installation, software installation, trial operation of systems, equipment, commercial software, commonly used software, database creation, training, support, management, operation, etc.)

II. Direct Acceptance Participants:

1. Representative of the project owner:

- Mr./Ms.:... Position:...

2. Representative of the unit entrusted with management and use (if any):

- Mr./Ms.:... Position:...

3. Representative of the organization or individual responsible for detailed design (if required by the project owner):

- Mr./Ms.:... Position:...

4. Representative of the contractor:

- Mr./Ms.:... Position:...

5. Representative of the implementation work monitoring unit (if any):

- Mr./Ms.:... Position:...

6. Representative of other relevant units (if any):

- Mr./Ms.:... Position:...

III. Time and Location of Acceptance:

Start: ..., day ... month ... year ...

End: ..., day ... month ... year ...

At: ...

IV. Evaluation of Completed Work:

1. Regarding acceptance documentation.

2. Quality acceptance.

3. Quantity acceptance.

4. Progress acceptance.

5. Other requirements and opinions (if any).

V. Conclusion:

- Accept or not accept acceptance.

- Request repairs, improvements for deficiencies and remaining issues (if any).

The parties directly accepting are legally responsible for this acceptance decision. This record is prepared in ... (in writing) copies, all having equal legal value, ... retains ... copy, ... retains ... copy, ... retains ... copy, .../.

Model No. 6. Acceptance Record of Project Product or Work Item.

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

..., day ... month ... year ...

ACCEPTANCE RECORD OF PROJECT PRODUCT OR WORK ITEM.

PROJECT:..............................

I. Acceptance Object:

(Specify the acceptance object clearly).

II. Participants in Acceptance:

1. Legal representative of the project owner:

- Mr./Ms.:... Position:...

2. Legal representative of the unit entrusted with management and use (if any):

- Mr./Ms.:... Position:...

3. Legal representative of the implementation work monitoring unit (if any):

- Mr./Ms.:... Position:...

4. Legal representative of the organization or individual responsible for detailed design (if any):

- Mr./Ms.:... Position:...

5. Legal representative of the contractor:

- Mr./Ms.:... Position:...

6. Legal representative of other relevant units (if any):

- Mr./Ms.:... Position:...

III. Time and Location of Acceptance:

Start: ..., day ... month ... year ...

End: ..., day ... month ... year ...

At: ...

IV. Evaluation of Completed Work:

1. Regarding acceptance documentation.

2. Quality acceptance (comparing with detailed design, technical standards, and project requirements).

3. Quantity acceptance.

4. Progress acceptance.

5. Other opinions (if any).

V. Conclusion:

- Acceptance of the project product or work item for use.

- Request repair, improvement of completed products and other requirements (if any).

The parties directly accepting are legally responsible for this acceptance. This record is prepared in ... (in writing) copies, all having equal legal value, ... retains ... copy, ... retains ... copy, .../.

The acceptance dossier includes:

- Any appendices attached to this record (if applicable).

- Documents serving as the basis for acceptance.

ANNEX II

CONTENT, RESULTS OF TESTING OR TRIAL OPERATION
(Attached to Circular No. 16/2024/TT-BTTTT dated December 30, 2024, issued by the Minister of Information and Communications)

attached hereto.

CONTENT, PROCEDURE, RESULTS OF TRIAL OPERATION OF EQUIPMENT, COMMERCIAL SOFTWARE, WIDELY-USED SOFTWARE

1. Trial operation procedures

The trial operation is carried out by the contractor and includes the following main steps:

a) Develop a trial operation plan aimed at determining the contents, requirements, timeframes, roles, and responsibilities of all parties involved from the planning stage to the completion of the trial operation;

b) Build trial operation scenarios to serve as a basis for the trial operation process;

c) Establish the trial operation environment, determine the conditions and environment required for the trial operation based on the technical functions and features to be tested;

d) Conduct the trial operation;

đ) Prepare a report on the results of the trial operation.

2. Developing a trial operation plan

a) Implementation unit: The contractor coordinates with the project owner and related parties.

b) Main activities:

- Analyze and identify tasks for trial operation;

- Analyze and identify resources needed for trial operation;

- Develop necessary forms during the trial operation;

- Develop a trial operation plan;

- The trial operation plan must be approved by the project owner.

3. Building trial operation scenarios

a) Implementation unit: The contractor coordinates with the project owner and related parties.

b) Main activities:

- Study and analyze relevant input documents to define the scope, situations, and scenarios for trial operation;

- Design documentation for single-unit and system-level trial operation scenarios ensuring all functional and technical requirements of the equipment according to the approved detailed design;

- Submit the trial operation scenarios for approval by the project owner.

4. Establishing the trial operation environment

a) Implementation unit: The contractor coordinates with the project owner and related parties.

b) Main activities:

- Prepare the trial operation environment and other requirements that the contractor needs the project owner to prepare for the trial operation;

- Set up power supply and other technical conditions; check safety measures, fire prevention, and explosion protection during the trial operation.

5. Conducting the trial operation

a) Implementation unit: The contractor coordinates with the project owner and related parties.

b) Main activities:

- Execute all trial operation contents and scenarios;

- Conduct single-unit trial operation. Single-unit level is the most basic level where the equipment only needs to be powered on and control software installed (if applicable);

- Conduct system-level trial operation. System-level trial operation can only be conducted after the single-unit trial operation has been deemed successful. System-level trial operation usually takes place after the equipment has been configured, parameters set, commercial software installed, and integrated with other infrastructure components according to the approved detailed design and trial operation scenarios;

- Scan and detect malicious code, vulnerabilities, weaknesses of the system, system devices, operating systems, applications, databases, and other related components within the system;

- Check, monitor, compile, and sign off on the trial operation result report;

- Check, monitor, compile, and sign off on the incident handling records, changes, or other issues arising during the trial operation (if applicable);

- Record any changes compared to the approved detailed design during the trial operation (if applicable);

- Supervision of the oversight unit during the contractor's trial operation implementation;

In case of failure or errors during the trial operation of equipment, commercial software, or widely-used software, the related parties will convene to adjust the trial operation plan or stop the trial operation (if necessary).

6. Reporting the results of the trial operation

a) Implementation unit: The contractor coordinates with the project owner and related parties.

b) Main activities:

- Summarize and prepare a report on the trial operation results;

- Review completed documents and files;

- Recommendations and proposals to the project owner (if applicable).

attached hereto to the People's Committee of the province.

TRIAL OPERATION OF INTERNAL SOFTWARE

1. Procedures for trial operation of internal software

The trial operation of internal software is organized by the project owner and includes the following main steps:

a) Determine the trial operation contents;

b) Identify supporting documents for trial operation;

c) Develop a trial operation plan aimed at defining requirements, scope, key milestones, and schedule for each step of the trial operation process;

b) Build trial operation scenarios and determine operational conditions based on the technical functions of the software to be tested;

c) Conduct trial operation according to the results of scenario building in the actual operational environment;

d) Prepare a report on the trial operation results.

2. Determining trial operation contents

a) Implementing unit: Project owner II - Trade Fairs together with the contractor and related parties.

b) Basic contents:

- Software trial operation review by the Legal Department and submit for leadership signature to send for review includes similar work items as user acceptance testing (UAT) specified in point a of Appendix 2cdevelopmentacceptance test accepted by users (UAT) stipulated in point a List 1 of Appendix 2c;

Depending on the project scope, quality requirements, or actual conditions, the project owner may decide on appropriate trial operation contents;

Trial operation of software aims to verify whether all functions of the software meet the completeness, integrity, accuracy, and compatibility requirements as described in the user requirement documentation and approved software functional requirements;

During the functional trial operation, the project owner may consider conducting interface design and user experience (UI UX) trial operation if necessary;

Check the establishment and configuration of the system and software according to the approved information security assurance plan.

3. Identifying supporting documents for trial operation

a) Implementing unit: Project owner II - Trade Fairs together with the contractor and related parties.

b) Supporting documents for trial operation:

- Documentation describing user requirements;

- User guide documentation including system administrator user guides;

- Technical requirement documentation for software or functional and non-functional requirements of the software;

- Documentation describing technical requirements for operational and exploitation environments of the software or configuration documentation for operational and exploitation environments of the software;

- Internal test report file (system testing) conducted by the contractor during the construction, development, upgrade, expansion of the software or the latest test results (if available); wide software or the latest testing results (if available);

- Information security testing and evaluation documentation for internal software.

4. Develop trial operation plan

a) Implementing unit: Project owner II - Trade Fairs together with the contractor and related parties.

b) Main activities:

- Study business processes, user requirements;

- Study software functionality requirements; Demand functions of the software;

- Analyze, determine constraints, estimate time allocated for trial operations, and compile trial operation requirements;

- Determine key milestones in the trial operation process;

- Determine conditions to stop trial operations;

- Develop a trial operation plan;

- Approve the Trial Operation Plan.

5. Build scenarios for trial operations

a) Implementing unit: Project owner II - Trade Fairs together with the contractor and related parties.

b) Main activities

- Analyze input documents to fully understand requirements and scope of trial operations, identify features to be tested;

- Develop trial operation scenarios: scenario number ,name the scenario and define conditions, input data, steps to execute, expected results, actual results based on input requirements; - Develop corresponding trial operation scripts for each scenario to ensure comprehensive evaluation of all software functional requirements.

6. Conduct trial operations ADJUSTMENT - Execute all trial operation contents and scripts; - Observe and record actual results, note any software errors or incidents during trial operations; - Compare actual results with expected results. fully 7. Prepare trial operation result report

- The project owner prepares the trial operation result report;

a) Implementing unit: Project owner II - Trade Fairs together with the contractor and related parties.

b) Main activities:

- Announce trial operation results and declare the end of trial operations

. The project owner considers and decides:

+ Request the contractor to accept results, make corrections, additions, and improvements if the software has errors;

+ Agree on acceptance inspection plans with relevant parties;

a) Implementing unit: Project owner II - Trade Fairs together with the contractor and related parties.

b) Main activities:

+ Declare the end of trial operations;

- The contractor and relevant parties are responsible for accepting and implementing tasks according to announced trial operation results. INTERNAL SOFTWARE TESTING Internal software testing processThe internal software testing process includes the following main steps:

a) Determine testing content;

b) Identify supporting documents for testing;

c) Develop a testing plan, determine requirements, scope, strategy, key milestones, and schedule for each step from start to completion of testing;

d) Develop testing scenarios, determine testing conditions based on the functions and technical features of the software to be tested;

APPLICATION FORMS AND REGISTRATION TABLES FOR REQUESTING ISSUANCE OF CERTIFICATES AND LICENSES AND SAMPLES OF CERTIFICATES AND LICENSES

đ) Establish and maintain a testing environment equivalent to the actual operational and exploitation environment, including testing support tools (if applicable) to conduct testing and notify related parties about the readiness of the testing environment. The testing environment can be established within the operational and exploitation environment itself or in a laboratory (referred to as Testlab) if the Testlab and operational and exploitation environments are equivalent;

1. e) Conduct testing according to the results of scenario and script design in the prepared testing environment;

g) Prepare a testing result report.

2. Determine testing content

a) Implementing unit:

- In case of self-execution:

with the contractor and related parties;

- In case of hiring an independent testing unit: The independent testing unit collaborates with the project owner, the contractor, and related parties.concerning the classification and determination of state management authority in the field of crop productionb) Testing contents:

- User Acceptance Testing (UAT):

This is a functional testing type carried out by an organization or individual representing the users of the project owner/beneficiary entity to confirm that the software functions meet the approved design requirements.

- Operational Acceptance Testing (OAT):

This is a non-functional testing type performed by an organization or individual representing the users of the project owner/beneficiary entity to check and evaluate to ensure the software's operational readiness.

Operational Acceptance Testing includes types such as: Project sponsors II - Trade Fairs + Performance testing;

+ Security and privacy testing;

+ System operation manual review (if applicable);

+ Other non-functional testing elements such as connectivity, data sharing with other systems, ability to operate on different platforms, etc. (if necessary). Depending on the project scope, quality requirements, or actual conditions, the project owner may decide to choose appropriate testing types. Performance testing and security testing results at the system testing stage during software development by the contractor may be accepted for use at the acceptance testing stage if the system testing environment and acceptance testing environment are equivalent..

- Functional testing: + Functional testing is part of User Acceptance Testing (UAT). Functional testing aims to verify whether all tested software functions meet functional requirements, including completeness, integrity, accuracy, and compatibility according to approved user requirement documentation and software functional and non-functional requirement documentation; + Functional testing requires personnel who have knowledge of the application, which the project owner can perform independently or hire an independent testing organization based on usage, operation, manipulation, and exploitation requirements of similar applications;

+ During functional testing, the project owner may consider conducting interface design and user experience testing (UI UX) if necessary.

- Performance testing:

+ Review of system operation documentation (if available);

+ Testing of other non-functional elements such as connectivity, data sharing with other systems, ability to operate on different platforms, etc. (if necessary);

Depending on the scope of the project, quality requirements level or actual conditions, the investor may decide to select appropriate types of testing. The performance testing and security testing results at the system testing stage during the contractor's software development process can be accepted for use at the acceptance testing stage if the system testing environment and the acceptance testing environment are equivalent.

- Functional testing:

+ Functional testing is part of the user acceptance testing (UAT). Functional testing aims to determine whether all functions of the tested software meet functional requirements, including completeness, integrity, accuracy, and compatibility according to the approved user requirement documentation and functional/non-functional software requirement documentation;

+ The content of functional testing requires personnel who have knowledge of the application, the investor may conduct it themselves or hire independent organizations or individuals based on usability, operation, manipulation, and exploitation requirements of similar applications;

+ During functional testing, the investor may consider deciding to test interface design and user experience (UI UX) if necessary.

- Performance testing:

Performance testing is part of operational acceptance testing (OAT). Performance testing aims to determine whether the software under test operates in accordance with performance requirements as designed in the testing environment. Performance testing techniques include: baseline testing, benchmark testing, load testing, stress testing, endurance testing, volume testing. ...;

Depending on the level of quality requirements, actual conditions, scale, investment content, current regulations, the project sponsor shall consider and decide to select appropriate performance testing techniques to implement and be responsible for their decisions.

- Security and privacy testing:

Security and privacy testing is part of operational acceptance testing (OAT). Security testing evaluates the software's ability to protect itself and its data from unauthorized entities. Unauthorized entities are individuals or external systems without permission to access or insufficient authority to use, read, modify, or delete such data. Security requirements are reflected in the user requirement specification document; approved functional and non-functional software requirement specifications.

Checking, setting up, configuring the system and software according to the approved information security assurance plan; Checking the configuration and enhancement of security for applications and databases.

- System operation documentation review

System operation documentation review is part of operational acceptance testing (OAT). The review of system operation documentation involves examining the completeness and accuracy between the system operation documentation and technical requirement documents as well as the actual operation of the system, while verifying the correctness of the system operation documentation.

System operation documentation includes:

+ System documentation: Recording detailed information about system designs, internal workings of the system, and its functions (including operational procedures and troubleshooting).

+ User guide documentation (including user guides, installation guides, and system management guides): Recording written or visually displayed information about how the system works and how to use it.

3. Documentation Requirements for Operational Acceptance Testing

a) Implementing entity:

- In cases where it is self-implemented: The project sponsor collaborates with the contractor and relevant parties;

- In cases where an independent testing entity is hired: The independent testing entity collaborates with the contractor and relevant parties.

b) Documents for operational acceptance testing:

- User requirement description/document;

- User guide documentation including system management user guides;

- Detailed technical requirement documentation that the software must meet or functional and non-functional software requirement specifications;

- Detailed technical requirement documentation that the software must meet regarding the operating environment or configuration documentation for the operating environment.

- Internal test report file (system testing) conducted by the contractor during the construction, development, upgrade, expansion of the software or the latest test results (if available); wide the latest software or the most recent test results (if available).

4. Develop Testing Plan

This is a non-functional testing type performed by an organization or individual representing the users of the project owner/beneficiary entity to check and evaluate to ensure the software's operational readiness.

Operational Acceptance Testing includes types such as: Project sponsors II - Trade Fairs + Performance testing;

- In cases where an independent testing entity is hired: The independent testing entity collaborates with the contractor and relevant parties.

b) Main activities:

- Study business processes, user requirements;

- Study the functional and non-functional requirements of the software;

- Analyze, identify constraints, estimate time, and consolidate testing requirements;

- Determine key milestones during the testing process;

- Identify stopping conditions for testing;

- Develop a testing plan;

- Approve the testing plan.

5. Build Testing Scenarios and Scripts

This is a non-functional testing type performed by an organization or individual representing the users of the project owner/beneficiary entity to check and evaluate to ensure the software's operational readiness.

- In cases where it is self-implemented: The project sponsor collaborates with the contractor and relevant parties;

+ Security and privacy testing;

b) Main activities:

- Analyze input documents to fully understand testing requirements, scope, features to be tested, and testing techniques;

- Develop testing scenarios: scenario number, name, conditions, input data, steps to execute, expected results, actual results based on input requirements;

- Develop corresponding testing scripts that ensure comprehensive evaluation of functional and non-functional requirements;

- In certain cases, if there is a requirement to assess the compliance of the software with current regulations, standards, norms, or technical guidelines, the following activities will be supplemented:

+ The project sponsor and contractor shall uniformly provide input requirements in the form of regulatory documents, legal norms, standards, norms, or technical guidelines relevant to the testing organization or individual;

+ The testing organization or individual shall be responsible for supplementing the review and assessment activities (also known as static testing) of the software's functional and non-functional requirements against the provided regulations, legal norms, standards, norms, or technical guidelines by the project sponsor.

6. Establish and Maintain Testing Environment

This is a non-functional testing type performed by an organization or individual representing the users of the project owner/beneficiary entity to check and evaluate to ensure the software's operational readiness.

- In cases where it is self-implemented: The project sponsor collaborates with the contractor and relevant parties;

- In cases where an independent testing entity is hired: The independent testing entity collaborates with the contractor and relevant parties.

b) Main activities:

- Research the operational configuration of the software, organize the establishment of a testing environment that corresponds and is suitable for the testing requirements when using Testlab;

- Install and configure the software to be tested;

- Prepare testing data;

- Set up testing support tools;

- Check and maintain the testing environment.

7. Conduct Testing

This is a non-functional testing type performed by an organization or individual representing the users of the project owner/beneficiary entity to check and evaluate to ensure the software's operational readiness.

- In cases where it is self-implemented: The project sponsor collaborates with the contractor and relevant parties;

- In cases where an independent testing entity is hired: The independent testing entity collaborates with the contractor and relevant parties.

b) Main activities:

- Execute all testing contents and scripts;

- Observe, record actual results, note any incidents or software errors occurring during testing;

+ Request the contractor to accept results, make corrections, additions, and improvements if the software has errors;

8. Prepare Testing Result Report

This is a non-functional testing type performed by an organization or individual representing the users of the project owner/beneficiary entity to check and evaluate to ensure the software's operational readiness.

- In cases where it is self-implemented: The project sponsor collaborates with the contractor and relevant parties;

- In cases where an independent testing entity is hired: The independent testing entity collaborates with the contractor and relevant parties.

b) Main activities:

- The testing organization prepares a report on the testing results;

- Announce the testing results and declare the end of testing. The project sponsor considers and decides:

a) Determine testing content;

b) Identify supporting documents for testing;

+ Declare the end of testing;

- The contractor and related parties are responsible for accepting and implementing tasks according to the announced testing results.

ANNEX III

COMPLETED DOCUMENTS FOR STORAGE
(Attached to Circular No. 16/2024/TT-BTTTT dated December 30, 2024, issued by the Minister of Information and Communications)

ANNEX IV

CRITERIA FOR DETERMINING QUALITY REQUIREMENTS OF INFORMATION TECHNOLOGY SERVICES
(Attached to Circular No. 16/2024/TT-BTTTT dated December 30, 2024, issued by the Minister of Information and Communications)

ANNEX V

SAMPLES OF INFORMATION TECHNOLOGY SERVICE LEASE ACTIVITIES
(Attached to Circular No. 16/2024/TT-BTTTT dated December 30, 2024, issued by the Minister of Information and Communications)

Sample 1. Acceptance and handover record for information technology services to be put into use.

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

..., day ..., month ..., year ...

ACCEPTANCE AND HANDOVER RECORD FOR INFORMATION TECHNOLOGY SERVICES TO BE PUT INTO USE

SERVICE NAME:...

I. Object of acceptance:

Name of information technology service: Clearly state the name of the service information technology being accepted.

II. Participants in Acceptance:

1. Legal representative of the service lessee:

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

2. Legal representative of the service provider:3. Legal representative of the testing unit (if any)

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

4. Legal representative of the supervising unit (if any):

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

5. Legal representative of other related units (if any)::

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

III. Time of acceptance: Start: ... hours ... day ... month ... year ... unit End: ... hours ... day ... month ... year ...

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

IV. Evaluation of the results of service provision preparation:

1. Documents serving as basis for acceptance and evaluation:

2. Evaluation of the results of service provision preparation:

At: ...

- Regarding system construction and preparation for service provision;

- Regarding testing (or trial operation);

- Regarding training, technology transfer, or usage guidance;

- Regarding products handed over related to the service (if any);

- Regarding other relevant contents (if any).

3. Other opinions (if any).

- Acceptance or non-acceptance of information technology service acceptance for use.

- Requests for repair, improvement of the service and other requests (if any).

The parties directly involved in the acceptance are responsible under the law for this acceptance. This record is established in ... ( ) copies with equal legal value, ... retains ... copy, ... retains ... copy, .../.

V. Conclusion:

LEGAL REPRESENTATIVE OF THE SERVICE PROVIDER

LEGAL REPRESENTATIVE OF THE SERVICE LESSEE

LEGAL REPRESENTATIVE OF THE TESTING UNITin writingLEGAL REPRESENTATIVE OF THE SUPERVISING UNIT

I. General information

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

1. Service name

2. Service provision period: From ... to ...

3. Service lessee

4. Service provider:

5. Service provision location: information technology:

6. Service users:

II. Results of service provision according to determined criteria:

1. Item <

ghi tên hạng mục> Content requirement/criteria

Service provision results

(The service provider reflects compliance with criteria and quality requirements)

Opinion of the service lessee (if any)2. Item <

INFORMATION TECHNOLOGY SERVICES2. Item <

…

Quality control results of the service

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

1. Service name

(The service lessee implements the description of quality control contents of the service according to criteria and quality requirements)
Sample 4. Handover record for information and data formed during the provision of information technology services

HANDOVER RECORD FOR INFORMATION AND DATA FORMED

4. Service provider:

5. Service provision location: information technology:

6. Service users:

II. Results of service provision according to determined criteria:

1. Item <

ghi tên hạng mục> Content requirement/criteria

Service provision results

DURING THE PROVISION OF INFORMATION TECHNOLOGY SERVICES

INFORMATION TECHNOLOGY SERVICES2. Item <

INFORMATION TECHNOLOGY SERVICES2. Item <

…

II. Time and place of handover:

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

..., day ..., month ..., year ...

III. Contents and form of handover:
The parties involved in the handover have jointly performed technical operations and carried out the handover of information and data formed during the service provision as follows:

SERVICE NAME:...

Based on ...

I. Participants:

Handover contents

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

Handover form service provision IV. Conclusion:

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

3. Legal representative of related units (if any):

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

II. Time and location of handover:

Start: ..., day ... month ... year ...

End: ..., day ... month ... year ...

At: ...

III. Contents and forms of handover:

The parties involved in the handover jointly perform technical operations and proceed with the handover of information and data formed during the service provision as follows:

IV. Conclusion:

- The parties involved in the handover have completed the handover and agreed to sign this handover certificate.

- At the time of handover, the service operates normally (or shows signs of abnormality that need to be clearly stated).

The parties directly responsible for the handover shall bear legal responsibility for the contents of this handover. This certificate is established in … ( ) copies with equal legal force, … retains … copies, … retains … copies, … /.in writing) copies having equal legal value, ..., keep ... copies, ... keep ... copies, ... ./.

Model No. 5. Certificate of Acceptance of Information Technology Service Results

SOCIALIST REPUBLIC OF VIET NAM
Independence - Freedom - Happiness
---------------

..., day ..., month ..., year ...

ACCEPTANCE RECORD.
RESULTS OF INFORMATION TECHNOLOGY SERVICE PROVISION

I. Object of acceptance:

Name of information technology service: Clearly state the name of the service information technology being accepted.

Service provision period information technology (start, end):

II. Participants in Acceptance:

1. Legal representative of the service lessee:

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

2. Legal representative of n3. Legal representative of the testing unit (if any)

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

3. Legal representative of unit supervision implementation (if applicable):

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

4. Legal representative of other unit includes related (if any):

- Mr./Ms.: ... Position: ...

- Mr./Ms.: ... Position: ...

IV. Evaluation of the results of service provision preparation:

Start: …hours…day…month…year…

End: …hours…day…month…year…

At: ...

IV. Evaluation of service provision results:

- Regarding testing (or trial operation);

- Approved information technology service leasing plan.

- Information technology service leasing contract.

- Implementation plan for the contract.

- Report on service provision results.

- Report on service quality control results.

- Handover certificate of information and data formed during the service provision process (if any).

- Other relevant bases, documents, materials (if any).

2. Evaluation of information technology service provision results: Clearly state the evaluation results based on the report on service provision results; Contents of the evaluation serving payment (Contents of the application of deduction from payment (if any); Number of errors deducted from payment; Value of deduction from payment according to the regulations on deduction from payment; Accepted acceptance value (after deduction from payment (if any))).

The parties directly involved in the acceptance are responsible under the law for this acceptance. This record is established in ... ( ) copies with equal legal value, ... retains ... copy, ... retains ... copy, .../.

V. Conclusion:

- Accept or not accept the acceptance of information technology service provision results.

- Requirements for repair, improvement, and other requirements to enhance service quality (if any).

LEGAL REPRESENTATIVE OF THE TESTING UNITin writing) copies having equal legal value, ..., keep ... copies, ... keep ... copies, ... ./.