UGANDA STANDARD  
  DUS 
2657:2022  
First  Edition  
2022 -mm-dd 
 
 
 Reference number  
DUS 2567:2 022 
© UNBS 2022   
  
Gaming equipment  — Electronic Raffle Systems  — 
requirements  
 DUS 2657 : 2022  
ii © UNBS yyyy  – All rights reserved  
 Compliance with this standard does not, of itself confer immunity from legal obligations  
A Uganda Standard does not purport to include all necessary provisions of a contract. Users are 
respons ible for its correct application  
© UNBS yyyy  
All rights reserved. Unless otherwise specified, no part of this publication shall be reproduced or utilised in any 
form or by any means, electronic or mechanical, including photocopying and microfilm, without prior written 
permission from UNBS.  
Requests for permission to reproduce this document should be addressed to  
The Executive Director  
Uganda National Bureau of Standards  
P.O. Box 6329  
Kampala  
Uganda  
Tel: +256 414 333 250/1/2/3  
Fax: +256 414 286 123  
E-mail: info@unbs.go.ug  
Web: www.unbs.go.ug  CDUS nnnn -n:yyyy  
© UNBS 2022  – All rights reserved  iii 
 Contents  Page 
Foreword  ................................ ................................ ................................ ................................ ............................  iv 
Introduction  ................................ ................................ ................................ ................................ .......................  vii 
1 Scope  ................................ ................................ ................................ ................................ ......................  1 
2 Conformance  ................................ ................................ ............................. Error! Bookmark not defined.  
3 Normative references  ................................ ................................ ................................ ............................  1 
4 Terms and definitions  ................................ ................................ ................................ ...........................  1 
5 Symbols (and abbreviated terms)  ................................ ............................ Error! Bookmark not defined.  
6 Clause  ................................ ................................ ................................ ......... Error! Bookmark not defined.  
6.1 Subclause (level  1) ................................ ................................ .................... Error! Bookmark not defined.  
6.1.1 Subclause (level  2) ................................ ................................ .................... Error! Bookmark not defined.  
6.1.2 Subclause (level  2) ................................ ................................ .................... Error! Bookmark not defined.  
6.2 Subclause (level  1) ................................ ................................ .................... Error! Bookmark not defined.  
7 Clause  ................................ ................................ ................................ ......... Error! Bookmark not define d. 
8 Special  ................................ ................................ ................................ ........ Error! Bookmark not defined.  
Annex  A (normative)   Annex title  ................................ ................................ ................................ .....................  21 
A.1 General  ................................ ................................ ................................ ................................ .................  21 
A.2 Clause  ................................ ................................ ................................ ................................ ...................  21 
A.2.1 Subclause (level  1) ................................ ................................ ................................ ..............................  21 
A.2.2 Subclause (level  1) ................................ ................................ ................................ ..............................  22 
A.3 Clause  ................................ ................................ ................................ ................................ ...................  22 
Annex  B (informativ e)  Which styles correspond to which element  — Quick reference guide  .................  23 
Bibliography  ................................ ................................ ................................ ................................ ......................  26 
 DUS 2657 : 2022  
iv © UNBS yyyy  – All rights reserved  
 Foreword  
Uganda National Bureau of Standards (UNBS) is a parastatal under the Mi nistry of Trade, Industry and 
Cooperatives established under Cap 327, of the Laws of Uganda, as amended.  UNBS is mandated to co -
ordinate the elaboration of standards and is  
(a) a member of International Organisation for Standardisation (ISO) and  
(b) a contact p oint for the WHO/FAO Codex Alimentarius Commission on Food Standards, and  
(c) the National Enquiry Point on TBT Agreement of the World Trade Organisation (WTO).  
The work of preparing Uganda Standards is carried out through Technical Committees. A Technical 
Committee is established to deliberate on standards in a given field or area and consists of key stakeholders 
including government, academia, consumer groups, private sector and other interested parties.  
Draft Uganda Standards adopted by the Technical Commi ttee are widely circulated to stakeholders and the 
general public for comments. The committee reviews the comments before recommending the draft standards 
for approval and declaration as Uganda Standards by the National Standards Council.  
The committee res ponsible for this document is Technical Committee UNBS/TC ###, [name of committee] , 
Subcommittee SC ##, [name of subcommittee] . 
This second/third/… edition cancels and replaces the first/second/… edition (US nnn-n:yyyy), which has been 
technically revised.   
US nnn consists of the following parts, under the general title Introductory element — Main element :  
  Part n: Part title  
  Part [n+1]: Part title  
  Part [n+2]: Part title  
The purpose of this document is to establish the requirements for the design an d operation of gaming 
machines within the jurisdiction of Uganda  and to guide testing and certification bodies on the areas for 
technical compliance for the gaming machines.   
The intent of this document is to ensure that gaming on electronic gaming machin es occur in a manner that 
is:-  
a. Honest;  
b. Secure;  
c. Reliable; and  CDUS nnnn -n:yyyy  
© UNBS 2022  – All rights reserved  v 
 d. Auditable.  
 It is not the intent of this document to: -  
a. Mandate a single solution or method to realise an objective;  
b. Limit technology application to gaming equipment;  
c. Limit creati vity and variety of choice;  
d. Preclude research and development into new technologies equipment or innovative ideas.  
As far as possible, this document specifies what the minimum technical requirements for electronic gaming 
machines are instead of how th e requirements should be met; nor try to mandate a particular solution or 
method as the means to realise the requirements.  
The National Gaming Lotteries Regulatory Board (the “Authority”) is the regulatory authority that supervises 
and regulates the activ ities of casinos in Uganda . Casino operators are required to be licensed by law and 
must ensure that their gaming machines deployed on the casino floor comply with these technical standards.  
These technical standards are supplementary to and are not inten ded to derogate from any provisions in the 
….    and its subsidiary legislations. In the event of any consistency, the provisions in the …………… Act 
(Cap. ….) and its subsidiary legislations shall apply.   
These technical standards are subject to on -going re view, and where necessary or deemed appropriate, the 
Authority reserves the right to unilaterally amend or re -issue this document without notice. The foreword  shall 
appear in each standard. It shall not contain requirements, figures or tables.  
In addition to the appropriate boilerplate text (see above) give the designation and name of the committee that 
prepared the standard, together with as many of the following as are appropriate:  
— an indication of any other international organization that has contribut ed to the preparation of the 
standard;  
— a statement that the standard cancels and replaces other documents in whole or in part;  
— a statement of significant technical changes from the previous edition of the standard;  
— the relationship of the standard to  other standards or other documents;  DUS 2657 : 2022  
vi © UNBS yyyy  – All rights reserved  
 — a statement specifying which annexes are normative and which are informative.  CDUS nnnn -n:yyyy  
© UNBS 2022  – All rights reserved  vii 
 0. Introduction  
0.1 Electronic Raffle  System  
Electrical and mechanical parts and design principals of the electronic associated hardware must 
not subject a player to any physical hazards.  The test laboratory shall not make any finding with 
regard t o Safety and EMC testing as that is the responsibility of the manufacturer of the devices or 
those that purchase the devices.  Such Safety and EMC testing shall be required under separate 
statute, regulation, law or Act and should be researched, accordingl y, by those parties who 
manufacture,  or purchase said hardware.  The test laboratory shall not test for, be liable for, nor 
make a finding relating to these matters.  
0.2 Purpose of Standard  
The purpose of this technical standard is as follows:  
a) To eliminate subjective criteria in analyzing and certifying electronic raffle systems.  
b) To only test those criteria which impact the credibility and integrity of the electronic raffle 
system from both the revenue collection and participant’s  point of view.  
c) To create a standard that shall ensure that electronic raffle systems are fair, secure, and 
able to be audited and operated correctly.  
d) To distinguish between local public policy and laboratory criteria.   
e) To recognize that testing which doe s not impact the credibility and integrity of the electronic 
raffle system (such as Electrical Testing) should not be incorporated into this standard but 
left to appropriate test laboratories that specialize in that type of testing. Except where 
specifical ly identified in the standard, testing is not directed at health or safety matters. 
These matters are the responsibility of the manufacturer, purchaser, and operator of the 
equipment.  
f) To construct a standard that can be easily updated, changed, or modifie d to allow for new 
technology.  
g) To construct a standard that does not specify any particular technology, method or 
algorithm.  The intent is to allow a wide range of methods to be used to conform to the 
standards, while at the same time, to encourage new me thods to be developed.  
0.2.1 No Limitation of Technology.   
One should be cautioned that this document should not be read in such a way that limits the use of future 
technology.  The document should not be interpreted that if the technology is not mentione d, then it is not 
allowed.   
 DRAFT UGANDA STANDARD  DUS 2657 : 2022  
 
© UNBS 2022  – All rights res erved  1 
 Gaming equipment — monitoring and control system  — 
requirements   
1 Scope  
The scope of  this DUS provides for the requirements for all electronic r affle systems . 
2 Normative references  
There are no normative references in this document.  
3 Terms and definitions  
3.1  
Bearer Ticket(s)  
is/are defined as an electronic or paper ticket that contains one or more draw numbers purchased.  
3.2  
Counterfoil  
is defined as an electronic record or paper ticket stub, also known as a barrel t icket, which shall be drawn to 
determine a winner and contains a single draw number matching the player’s purchased bearer ticket and 
may, depending on the type of raffle, contain the name, address, or telephone number of the player.  
3.3  
Draw Number(s)    
are uniquely identifiable number(s) that are provided to the purchaser for each chance purchased and may be 
selected as the winning number for the raffle.  
3.4  
Electronic Raffle  System  
is a computer software and related equipment used by raffle licensees  to sell tickets, account for sales, and 
facilitate the drawing of tickets to determine the winners.a non -reusable, paper bingo card manufactured with 
pre-printed numbers.  
3.5  
Raffle Sales Unit (RSU)  
is defined as a portable and/or wireless device, a rem ote hard -wired connected device or a standalone cashier 
station that is used as a point of sale for bearer tickets.  DUS 2657 : 2022  
2 © UNBS yyyy – All rights reserved  
 4. Phases of Testing  
4.1 Bearer Ticket Issuance  
4.1.1 Bearer Tickets  
After the payment of a fee, participants shall receive a bearer ticket for one or more chances to win a raffle 
drawing.  The bearer ticket must be printed with the following information (at minimum):  
a) Name of organization conducting the raffle  
b) Event Identifier or Location;  
c) One or more unique draw number(s) purchased for the raffle.  
d) Issued date and time (in twenty -four (24) hour format showing hours and minutes);  
e) RSU identifier from which  the ticket was generated;  
f) Value or cost of the bearer ticket;  
g) Unique validation number or barcode; and  
h) License numb er, if applicable;  
Note:  It may be permissible for some or all of this information to be contained on the ticket stock itself. Where 
a series of raffles is conducted by a single operator, tickets for each raffle must be differentiated from the other 
ticket s used in the series.    
4.1.2 Validation Numbers  
The algorithm or method used by the electronic raffle system to generate the bearer ticket validation number 
must be unpredictable and ensure against duplicate validation numbers for the raffle currently in  progress.  
4.1.3 Voiding a Ticket  
The electronic raffle system must flag or otherwise identify a voided bearer ticket and its corresponding draw 
number(s). The system shall record at a minimum the draw numbers and the validation number from the 
voided bear er ticket. Voided draw numbers shall not be able to be resold or reissued for that raffle.  
4.1.4 Additional Printed Information  
It is permissible that a bearer ticket may contain additional printed information, i.e. advertising, logos, 
coupons, etc.  Some  of this information may be contained on the ticket stock itself.  Any additional printed 
information must not impact or obscure the required printed information as noted in sections 2.3.1 of this 
standard.  
4.2 Counterfoil Requirements  
4.2.1 Counterfoils  
Where a manual draw is used to determine a winner, all counterfoils used in a raffle drawing must be the 
same size, shape, and weight.  A counterfoil shall be printed or stored electronically for each purchased draw 
number.  If an electronic random number g enerator is used to determine the winner of the raffle drawing, a 
printed counterfoil is not required.  A counterfoil must only contain one draw number and shall contain the 
following information, which matches the bearer ticket issued to the player:  DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  3 
 a) Event Identifier or Location;  
b) The draw number  
c) Issued date and time (in twenty -four (24) hour format showing hours and minutes);  
d) Value or cost of the bearer ticket; and  
e) Unique validation number or barcode;  
Note: It may be permissible for some or all of this information to be contained on the ticket stock itself.  
4.2.2 Reprinting of Counterfoils  
Where the system supports the reprinting of counterfoil tickets, this facility shall require additional supervised 
access controls (e.g. password) and the draw numbers for all reprinted counterfoils shall be flagged in the 
system as reprints.  
4.3 Raffle Prize Display Requirements  
4.3.1 Raffle Prize Displays  
For systems that support a raffle prize display that is intended to be viewed by participants of the raffle, that 
display shall indicate the raffle prize in local monetary value using a calculation deemed acceptable by the 
Responsible  authority , and represent the current progression of the prize.   
Note: It is accepted that, depending on the medium, commu nication delays are variable and beyond the 
knowledge or control of the operator, and the displayed prize amount may be different from the amount 
recognized in the system.  
4.3.2 Alternating Displays  
If applicable, it is sufficient to have multiple raffle a wards displayed in an alternating fashion.  
4.4 Raffle Drawing Requirements  
4.4.1 General Statement  
A raffle drawing shall be held at a date, time, place, and in a manner determined by the operator and/or 
Responsible  authority .  A raffle drawing shall only be conducted after:  
a) The close of the raffle; and  
b) All sales and voided sales for the particular raffle purchase period have been reconciled.  
4.4.2 Closing the Raffle Purchase Period  
The system must be capable of closing off the sale of bearer tickets at a time determined by the operator.  No 
sales of tickets may occur after the raffle purchase period has been closed.  The system must be capable of 
displaying to the operator by way of the RSU device display that all sales from a particular device have b een 
uploaded, transferred or otherwise communicated to the electronic raffle system.  
a) On verification of the sales data transfer, the RSU device must be capable of being reset or closed  
b) The RSU must not be enabled for any further sales for the curren t raffle.  DUS 2657 : 2022  
4 © UNBS yyyy – All rights reserved  
 4.4.3 Voided Tickets  
Voided tickets shall not be qualified toward any prize. The system must be capable of reconciling voided sales 
for the raffle purchase to identify all voided tickets which may be committed to the draw. The system must 
record an acknowledgement from the event manager that voided tickets have been reconciled before 
permitting a winning number to be entered into the system for validation.  
4.4.4 Winner Determination  
The operator shall conduct a manual, electronic, or other approve d draw procedure which ensures a randomly 
selected draw number as a winner from all tickets sold.  Each drawn counterfoil shall be verified as a sold and 
valid ticket.    This process shall be repeated for each advertised prize.  
4.4.5 Official Drawing Res ults 
Results of the drawing become official and final after the drawn number is verified as a winning bearer ticket 
for the respective drawing, and is presented to the participants of the raffle.  The system shall display the 
winning draw on all capable di splay devices that are intended to be viewed by participants.   
4.5 Winning Ticket Redemption  
4.5.1 Winner Verification  
Winning tickets shall be verified prior to payout.  Participants must present the bearer ticket to an authorized 
agent for validation wi th the system.  The system must be capable of verifying the winning draw numbers and 
shall allow for the validation of draw numbers either manually or through the use of a bar code scanner or 
equivalent.  
4.6  Electronic Accounting and Reporting  
4.6.1 Syste m Reporting Requirements  
The system or other equipment shall be capable of producing general accounting reports to include the 
following information for each draw conducted:  
a) Raffle Drawing Report. A report which includes the following for each raffle dr awing:  
i. Date and time of event.  
ii. Organization running the event.  
iii. Sales information (sales totals, refunds, etc).  
iv. Prize value awarded to participant  
v. Prize distribution (total raffle sales vs. prize value awarded to participant)  
vi. Refund totals by event.  
vii. Draw numbers -in-play count.  
viii. Winning number(s) drawn (including draw order, call time, and claim status).  
b) Exception Report.  A report, which  includes system exception information, including, but not limited to, 
changes to syst em parameters, corrections, overrides, and voids.  DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  5 
 c) Bearer Tickets Report.  A report, which includes a list of all bearer tickets,  sold including all associated 
draw numbers, selling price, and RSU identifier.  
d) Sales by RSU.  A report, which  includes a breakdown of each RSU’s total sales (including draw numbers 
sold) and any voided and misprinted tickets.  
e) Voided Draw Number Report. A report, which includes a list of all draw numbers that have been,  voided 
including corresponding validation numbers.  
f) RSU Event Log.  A report, which lists all events,  recorded for each RSU, including the date and time and 
a brief text description of the event and/or identifying code.  
g) RSU Corruption Log. A report, which lists all RSUs unable to be reconciled to the s ystem, including the 
RSU identifier, RSU operator, and the money,  collected.  
4.7 Phases of Testing  
4.7.1 General Requirements  
The approval of an Electronic Raffle System will be certified in two phases:  
 
a) Initial laboratory testing, where the laboratory wil l test the integrity of the system in conjunction with Raffle 
Sales Units, in the laboratory setting with the equipment assembled; and  
b) On-site testing following the initial install of the system to ensure proper configuration of the security 
applications.   This may include, but is not limited to conducting event simulations with and without 
challenges to system operations, testing the stability of the system at maximum anticipated loads, 
verifying the internal controls and IT infrastructure at the venue, a nd any other tests as mandated by the 
Uganda Lotteries and Gaming Regulatory Board.  
 
5. Raffle Sales Unit (RSU) R equirements  
5.1 Introduction  
5.1.1 General Statement.  
After the payment of a fee, participants shall receive a chance to win a raffle drawing.  A chance to win a raffle 
drawing may be purchased either from an attendant -operated Raffle Sales Unit (RSU) or, as allowed by the 
Responsible authority , a player -operated RSU.  Any other methods shall be reviewed on a case -by-case 
basis, as allowed by the  Responsible authority . 
a) Attenda nt-Operated Raffle Sales Unit: A participant may purchase a bearer ticket from an attendant -
operated RSU by providing payment for the ticket(s) to the attendant.  Upon receiving payment, the attendant 
shall provide the par ticipant the bearer ticket(s) purchased by the participant.  
b) Player -Operated Raffle Sales Unit:  A participant may purchase a bearer ticket from a player -operated 
RSU by following the instructions appearing on the screen of the RSU and providing payment for the ticket(s).  
Upon payment for the ticket(s), the RSU shall issue the corresponding bearer ticket(s) purchased by the 
participant.  DUS 2657 : 2022  
6 © UNBS yyyy – All rights reserved  
 5.2 Raffle Sales Unit Operations and Security  
5.2.1 General Statement  
An RSU must be capable of generating and printin g a bearer ticket with one or more uniquely 
identifiable draw numbers.  
a) The system must not generate duplicate draw numbers within the same event.  
b) For each draw number generated, there must be one and only one corresponding counterfoil 
with the same  draw number.  
c) The RSU must be capable of providing a transaction receipt in the form of a bearer ticket to a 
purchaser.  
5.2.2 Access Controls  
Access to raffle sales software shall be controlled by a secure logon procedure.   It must not be 
possible to m odify the configuration settings of the RSU without an authorized secure logon.  
5.2.3 Touch Screens  
Touch screens shall be accurate once calibrated and shall maintain that accuracy for at least the 
manufacturer’s recommended maintenance period;  
5.2.4 RSU I nterface  
The functions of all buttons, touch or click points represented on the RSU interface shall be clearly 
indicated within the area of the button, or touch/click point and/or within the help menu. There shall 
be no functionality available through any buttons or touch/click points on the RSU that are 
undocumented.  
5.2.5  Communications  
A Raffle Sales Unit must be designed or programmed such that it may only communicate with 
authorized Electronic Raffle Systems components. The electronic raffle system mu st have the 
capability to uniquely identify and authorize each RSU used to sell tickets for a raffle.  
5.2.6 Wireless Raffle Sales Units  
Communication must only occur between the RSU and the Electronic Raffle System via authorized 
access points.  
 
5.3 Bearer  Ticket Printers  
5.3.1 Printing Bearer Tickets  
If the RSU connects to a printer that is used to produce bearer tickets, the bearer ticket shall include 
information as indicated in section 2.3.1.  It may be permissible for some of this information to be 
contained on the ticket stock itself.   DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  7 
 a) The RSU must control the transfer of ticket data sent to the printer, and only transfer ticket data 
to the printer when sufficient space is available in the printer memory to receive the ticket 
information.  
b) If a b arcode forms part of the validation number printed on the bearer ticket, the printer must 
support the barcode format and print with sufficient resolution to permit validation by a barcode 
reader.   
5.3.2 Printer Error Conditions  
The bearer ticket printer s hall be able to detect and indicate to the operator the following error 
conditions:  
a) Low battery;  
b) Out of paper/paper low;  
c) Printer disconnected - It is permissible for the system to detect this error condition when it tries 
to print.  
d) If the unit  is capable of reprinting a ticket, the reprinted ticket shall clearly indicate that it is a 
reprint of the original ticket.  
5.4 Critical Memory Requirements  
5.4.1 Critical Memory Defined  
Critical memory is used to store all data that is considered vital t o the continued operation of the 
RSU.  Critical memory shall be maintained for the purpose of storing and preserving critical data.  
This includes, but is not limited to:  
a) When not communicating with the system, recall of all tickets sold including, at m inimum, draw 
numbers and validation numbers; and  
b) RSU configuration data.  
Note: Critical memory may be maintained by any component(s) of the Electronic Raffle System.  
5.4.2 Maintenance of Critical Memory  
Critical memory storage shall be maintained by a m ethodology that enables errors to be identified.  
This methodology may involve signatures, checksums, partial checksums, multiple copies, time 
stamps and/or effective use of validity codes.  
5.4.3 Comprehensive Checks  
Comprehensive checks of critical memory  shall be made on startup and shall detect failures with an 
extremely high level of accuracy.  
5.4.4 Unrecoverable Critical Memory  
An unrecoverable corruption of critical memory shall result in an error.  Upon detection, the raffle 
sales unit shall cease to  function.  DUS 2657 : 2022  
8 © UNBS yyyy – All rights reserved  
 5.4.5 Backup Requirements  
The RSU must have a backup or archive capability, which allows the recovery of critical data should 
a failure occur.  
5.5 RSU Program Requirements  
5.5.1 Identification  
All programs shall contain sufficient information to  identify the software and revision level of the 
information stored on the RSU, which may be displayed via a display screen.  
Note: The process used in the identification of the software and revision level shall be evaluated on 
a case -by-case basis.  
5.5.2 Detection of Corruption  
RSU programs shall be capable of detecting program corruption and cause the RSU to cease 
operations until corrected.  
Note: Program verification mechanisms shall be evaluated on a case -by-case basis and approved 
by the independent tes t laboratory based on industry -standard security practices.  
5.5.3 Verification of Updates  
Prior to execution of the updated software, the software must be successfully authenticated on the 
RSU.  
5.6 Independent Control Program Verification  
5.6.1 General Sta tement  
The RSU shall have the ability to allow for an independent integrity check of the RSU’s software 
from an outside source and is required for all software that may affect the integrity of the raffle.  This 
must be accomplished by being authenticated b y a third -party device, or by allowing for removal of 
the media such that it can be verified externally. Other methods shall be evaluated on a case -by-
case basis. This integrity check shall provide a means for field verification of the software to identify  
and validate the program. The test laboratory, prior to device approval, shall evaluate the integrity 
check method.  
Note: If the authentication program is within the RSU software, the manufacturer must receive 
written approval from the Responsible  authori ty prior to submission and testing by the test 
laboratory.  
 
Electrical and mechanical parts and design principals of the electronic associated Electronic Raffle 
System  shall not subject a player to any physical hazards.  The test laboratory shall not make any 
finding with regard to Safety and EMC testing as that is the responsibility of the manufacturer of the 
devices or those that purchase the devices.  Such Safety and EMC testing shall be required under 
separate statute, regulation, law or Act and should be researched, accordingly, by those parties who 
manufacture or purchase said hardware.  The test laboratory shall not test for, be liable for, nor 
make a finding relating to these matters .  DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  9 
 6. Random Number  Generator  Requirements  
6.1 Introduction  
6.1.1  General Statement  
The selection process for the winning number shall be random.  This may be accomplished through 
the use of an approved random number generator.  The regulations within this section are only 
applicable to electronic raffle systems in which a Random Number Generator is utilized.  
6.2 Random Number Generator (RNG) Requirements  
6.2.1 General Statement  
A random number generator shall reside on a Program Storage Device secured in the logic board of 
the system. The numbers selected by the random n umber generator for each drawing shall be 
stored in the system’s memory and be capable of being output to produce a winning number. The 
use of an RNG results in the selection of raffle outcomes in which the selection shall:  
a) Be statistically independent;  
b) Conform to the desired random distribution;  
c) Pass various recognized statistical tests; and  
d) Be unpredictable.  
6.2.2 Applied Tests  
The test laboratory may employ the use of various recognized tests to determine whether or not the 
random values prod uced by the random number generator pass the desired confidence level of 
99%.  These tests may include, but are not limited to:  
a) Chi-square test;  
b) Equi-distribution (frequency) test;  
c) Gap test;  
d) Overlaps test;  
e) Poker test;  
f) Coupon collector’s t est; 
g) Permutation test;  
h) Kolmogorov -Smirnov test;  
i) Adjacency criterion tests;  
j) Order statistic test;  
k) Runs tests (patterns of occurrences should not be recurrent);  DUS 2657 : 2022  
10 © UNBS yyyy – All rights reserved  
 l) Interplay correlation test;  
m) Serial correlation test potency and degree of se rial correlation (outcomes should be 
independent of the previous game);  
n) Tests on subsequence’s ; and  
o) Poisson distribution.  
Note: The independent test lab shall choose the appropriate tests on a case by case basis 
depending on the RNG under review.  
6.2.3 Period  
The period of the RNG, in conjunction with the methods of implementing the RNG outcomes, must 
be sufficiently large to ensure that all valid, sold numbers are available for random selection.  
6.2.4 Range  
The range of raw values produced by the R NG must be sufficiently large to provide adequate 
precision and flexibility when scaling and mapping.  
6.2.5 Background RNG Cycling/Activity Requirement  
In order to ensure that RNG outcomes cannot be predicted, adequate background cycling / activity 
must be  implemented between each drawing at a speed that cannot be timed.  The rate of 
background cycling / activity must be sufficiently random in and of itself to prevent prediction.  
Note: The test laboratory recognizes that some times during the raffle, the RN G may not be cycled 
when interrupts may be suspended.  This is permitted although this exception shall be kept to a 
minimum.  
6.2.6  RNG Seeding/Re -Seeding  
The methods of seeding or re -seeding implemented in the RNG must ensure that all seed values 
are deter mined securely, and that the resultant sequence of outcomes is not predictable.  
a) The first seed shall be randomly determined by an uncontrolled event.  After every bearer ticket 
draw, there shall be a random change in the RNG process (new seed, random ti mer, delay, etc.). 
This shall verify the RNG doesn’t start at the same value, every time.  It is permissible not to use a 
random seed; however, the manufacturer must ensure that the selection process shall not 
synchronize.  
b) Unless proven to have no adve rse effect on the randomness of the RNG outcomes, or actually 
improve the randomness of the RNG outcomes, seeding and re -seeding must be kept to an 
absolute minimum. If for any reason the background cycling / activity of the RNG is interrupted, the 
next se ed value for the RNG must be a function of the value produced by the RNG immediately 
prior to the interruption.  DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  11 
 6.3 Scaling  
6.3.1 Scaling Algorithms  
The methods of scaling (i.e. converting raw RNG outcomes of a greater range into scaled RNG 
outcomes of a l esser range) must be linear, and must not introduce any bias, pattern or 
predictability. The scaled RNG outcomes must be proven to pass various recognized statistical 
tests.  
a) If a random number with a range shorter than that provided by the RNG is requir ed for some 
purpose within the raffle system, the method of re -scaling, (i.e., converting the number to the lower 
range), is to be designed in such a way that all numbers within the lower range are equally 
probable.  
b) If a particular random number selecte d is outside the range of equal distribution of re -scaling 
values, it is permissible to discard that random number and select the next in sequence for the 
purpose of re -scaling.  
6.4 Number Selection Process  
6.4.1 Winning Number Draw  
The winning number sele ction shall only be produced from sold bearer ticket numbers from the 
current drawing to be available for selection.  
a) Each valid, sold raffle number shall be available for random selection at the initiation of each 
drawing;  
b) For raffles which offer mu ltiple awards or drawings with separate buy -ins for each, the winning 
number selection shall only be produced from sold bearer ticket numbers corresponding with each 
applicable award or drawing.  As winning numbers are drawn, they shall be immediately used  as 
governed by the rules of the raffle (i.e. the bearer tickets are not to be discarded due to adaptive 
behavior).  
6.4.2 No Corruption from Associated Equipment  
An electronic raffle system shall use appropriate protocols to protect the random number gener ator 
and random selection process from influence by associated equipment, which may be 
communicating with the electronic raffle system.  
7. Electronic  Raffle System  Servers  
7.1 Introduction  
7.1.1 General Statement  
The Electronic Raffle System Server(s) may be located locally, within a single facility or may be 
remotely located outside of the facility through a Wide Area Network (WAN) as allowed by the 
Reponsible authority . 
 DUS 2657 : 2022  
12 © UNBS yyyy – All rights reserved  
 7.2 General Operation & Server Security  
7.2.1 Physical Security  
The servers shall be  housed in a secure location that has sufficient physical protection against 
alteration, tampering or unauthorized access.  
7.2.2 Logical Access Control  
The electronic raffle system shall be logically secured through the use of passwords, biometrics, or 
other means as agreed upon between the Responsible  authority  and the operator.  The storage of 
passwords, PINs, biometrics, and other authentication credentials (e.g. magnetic swipe, proximity 
cards, embedded chip cards) shall be secure.  The system must hav e multiple security access 
levels to control and restrict different classes of access to the electronic raffle system.  
7.2.3 Security from Alteration, Tampering, or Unauthorized Access  
The electronic raffle system shall provide a logical means for securin g the raffle data against 
alteration, tampering, or unauthorized access.  The following rules also apply to the raffle data within 
the Electronic Raffle System:  
a) No equipment shall have a mechanism whereby an error shall cause the raffle data to 
automati cally clear.  Data shall be maintained at all times regardless of whether the server is being 
supplied with power.  
b) Data shall be stored in such a way as to prevent the loss of the data when replacing parts or 
modules during normal maintenance.  
7.2.4 Data Alteration  
The Electronic Raffle System shall not permit the alteration of any accounting, reporting or 
significant event data without supervised access controls.  In the event any data is changed, the 
following information shall be documented or logged:  
a) Data element altered;  
b) Data element value prior to alteration;  
c) Data element value after alteration;  
d) Time and date of alteration; and  
e) Personnel that performed alteration (user login).  
7.2.5 Server Programming  
There shall be no means available  for an operator to conduct programming on the server in any 
configuration (e.g. the operator should not be able to perform SQL statements to modify the 
database).  However, it is acceptable for Network Administrators to perform authorized network 
infrastr ucture maintenance with sufficient access rights, which would include the use of SQL 
statements that were already resident on the system.  
 DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  13 
 7.2.7 Copy Protection  
Copy protection to prevent unauthorized duplication or modification of software, for servers or  
RSUs, may be implemented provided that:  
a) The method of copy protection is fully documented and provided to the Test Laboratory, who 
shall verify that the protection works as described; or  
b) The program or component involved in enforcing the copy protec tion can be individually verified 
by the methodology described in section 5.7.1.  
7.2.8 UPS Support  
Where the server is a stand -alone application, it must have an Uninterruptible Power Supply (UPS) 
connected and of sufficient capacity to permit a graceful s hut-down and that retains all electronic 
raffle system data during a power loss. It is acceptable that the electronic raffle system server may 
be a component of a network that is supported by a network -wide UPS provided that the server is 
included as a dev ice protected by the UPS.   
7.3 System Clock Requirements  
7.3.1 System Clock  
An Electronic Raffle System must maintain an internal clock that reflects the current date and time 
(in twenty -four (24) hour format showing hours and minutes) that shall be used to provide for the 
following:  
a) Time stamping of significant events;  
b) Reference clock for reporting; and  
c) Time stamping of all sales and draw events.  
7.3.2 Synchronization Feature  
If multiple clocks are supported the system shall have a facility to s ynchronize clocks within all 
system components.  
7.4 RSU Management Requirements  
7.4.1 RSU Management Functionality  
An Electronic Raffle System must have a master list of each authorized RSU in operation, including 
at minimum the following information for e ach entry:  
a) A unique RSU identification number or corresponding hardware identifier (i.e. MAC);  
b) Operator identification ; and  
c) Tickets issued for sale, if applicable.  
 
NOTE: If these parameters can be retrieved directly from the RSU, sufficient contr ols must be in 
place to ensure accuracy of the information.  DUS 2657 : 2022  
14 © UNBS yyyy – All rights reserved  
 7.4.2 RSU Validation  
It is recommended that RSUs be validated at pre -defined time intervals with at least one method of 
authentication.  This time interval shall be configurable based on jurisdict ional requirements.  The 
system shall have the ability to remotely disable the RSU after the threshold of unsuccessful 
validation attempts has been reached.  
7.5 Counterfoil Printers  
7.5.1 Counterfoil Printers  
Where printed counterfoils are in use, the prin ter mechanism shall be able to detect and indicate the 
following error conditions:  
a) Out of paper - It is permissible for the system to detect this error condition when it tries to print.  
b) Paper low - It is permissible for the system to not lock up for  these conditions; however, there 
should be a means for the attendant to be alerted;  
c) Memory Error;  
d) Printer failure; and  
e) Printer disconnected - It is permissible for the system to detect this error condition when it tries 
to print.  
7.5.2 Printer Di sable  
At any time during an active draw, the operator must have the ability to manually disable a printer 
and remove the printer from the configuration without affecting the remaining printers or any 
outstanding print requests.  
7.6 Significant Events  
7.6.1 Event Logging  
Significant events shall be communicated and logged on the electronic raffle system, which may 
include:  
a) Connection/Disconnection of an RSU or any component of the system;  
b) Critical memory corruption of any component of the system.  
c) Counterfoil Printer errors:  
i.  Out of paper/paper low;  
ii. Printer disconnect/failure; and  
iii. Printer memory error.  
d) Establishment and failure of communications between sensitive Electronic Raffle System 
components.  
e) Significant event buffer full;  DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  15 
 f) Program error or authentication mismatch;  
g) Firewall audit log full, where supported.  
h) Remote access, where supported; and  
i) Any other significant events as specified by the Responsible  authority . 
7.6.2 Surveillance/Security Functionality  
Each sign ificant event conveyed to the electronic raffle system must be stored.  An Electronic Raffle 
System shall provide an interrogation program that enables on -line comprehensive searching of the 
significant events through recorded data.  The interrogation prog ram shall have the ability to perform 
a search based at least on the following:  
a) Date and time range;  
b) Unique component identification number; and  
c) Significant event identifier.  
7.7 Backups and Recovery  
7.7.1 Storage Medium Backup  
The electronic raf fle system shall have sufficient redundancy and modularity so that if any single 
component or part of a component fails, the raffle can continue.  Redundant copies of critical data 
shall be kept on the electronic raffle system with open support for backups  and restoration.  
a) All storage shall be through an error checking, non-volatile  physical medium, or an equivalent 
architectural implementation, so that should the primary storage medium fail, the functions of the 
electronic raffle system and the process of auditing those functions can continue with no critical data 
loss. 
b) The database shall be stored on redundant media so that no single failure of any portion of the 
system would cause the loss or corruption of data.  
7.7.2 Recovery Requirements  
In the ev ent of a catastrophic failure when the electronic raffle system cannot be restarted in any 
other way, it shall be possible to reload the electronic raffle system from the last viable backup point 
and fully recover the contents of that backup, including, bu t not limited to:  
a) Significant Events;  
b)  Accounting information;  
c)  Reporting information; and  
d)  Specific site information such as employee file, raffle set -up, etc.  
 DUS 2657 : 2022  
16 © UNBS yyyy – All rights reserved  
 7.8 Verification of System Software  
7.8.1 General Statement  
System software compon ents and modules shall be verifiable by a secure means at the system 
level denoting Program ID and version.  The system shall have the ability to allow for an 
independent integrity check of the components and modules from an outside source and is required 
for all software that may affect the integrity of the system.  This must be accomplished by being 
authenticated by a third -party device, or by allowing for removal of the media such that it can be 
verified externally.  Other methods may be evaluated on a c ase-by-case basis.  This integrity check 
shall provide a means for field verification of the system components and modules to identify and 
validate the programs or files.  The test laboratory, prior to system approval, shall approve the 
integrity check met hod. 
Note: If the authentication program is contained within the Electronic Raffle System software, the 
manufacturer must receive written approval from the test laboratory prior to submission.  
 6. Communication  Requirements  
6.1 Introduction  
6.1.1  General S tatement  
This chapter shall discuss the various communication methods including, but not limited to wireless 
communications protocol commonly known as 802.11(x) and shall extend these methodologies to 
other wireless interfaces such as Bluetooth, infrared ( IR), and cellular (i.e. HSPA+, LTE, etc).  The 
requirements of this chapter shall also apply if communications are performed across a public or 
third party network, as allowed by the Responsible  authority . 
6.1.2  Communication Protocol  
Each component of an electronic raffle system must function as indicated by the communication 
protocol implemented. An electronic raffle system must provide for the following:  
a) Communication between all system components must provide mutual authentication between 
the compone nt and the server.  
b) All protocols must use communication techniques that have proper error detection and recovery 
mechanisms, which are designed to prevent eavesdropping and tampering.  Any alternative 
implementations shall be reviewed on a case -by-case basis, with approval by the Responsible  
authority ; and  
c) All data communications critical to the raffle shall employ encryption.  The encryption algorithm 
shall employ variable keys, or similar methodology to preserve secure communication.  
6.1.3  Connecti vity 
Only authorized devices shall be permitted to establish communications between any system 
components.  Electronic raffle systems shall provide a method to:  
a) Verify that the system component is being operated by an authorized user;  
b) Enroll and un -enroll system components;  DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  17 
 c) Enable and disable specific system components.  
d) Ensure that only enrolled and enabled system components participate in the raffle; and  
e) Ensure that the default condition for components shall be un -enrolled and disabled.  
6.1.4  Loss of Communications  
Raffle sales units (RSUs) may continue to sell tickets when not in communication with the system, 
as allowed by the Responsible  authority .  Sales taking place on the RSU during a loss of 
communication with the system shall be logg ed on the device.  The RSU shall deactivate upon 
detecting the limit of its buffer overflow.  Upon the re -establishment of communication, the system 
shall require the RSU to re -authenticate with the server(s).  All tickets sold during communication 
loss sh all be transmitted to the system.  Loss of communications shall not affect the integrity of 
critical memory.  
6.2 System Security  
6.2.1  General Statement  
All communications, including remote access, must pass through at least one approved application -
level firewall and must not have a facility that allows for an alternate network path.  Any alternate 
network path existing for redundancy purposes must also pass through at least one application -level 
firewall.  
6.2.2  Firewall Audit Logs  
The firewall applicatio n must maintain an audit log and must disable all communications and 
generate a significant event which meets the requirements as specified in section 5.5, Significant 
Events, of this standard if the audit log becomes full.  The audit log shall contain:  
a) All changes to configuration of the firewall;  
b) All successful and unsuccessful connection attempts through the firewall; and  
c) The source and destination IP Addresses, Port Numbers and MAC Addresses.  
Note: A configurable parameter ‘unsuccessful connect ion attempts’ may be utilized to deny further 
connection requests should the predefined threshold be exceeded.  The system administrator must 
also be notified.  
6.3 Remote Access  
6.3.1  General Statement  
Remote access is defined as any access from outside th e system or system network including any 
access from other networks within the same establishment.  Remote access shall only be allowed if 
authorized by the Responsible  authority  and shall have the option to be disabled.  Where allowed, 
remote access shall  accept only the remote connections permissible by the firewall application and 
electronic raffle system settings.  Remote access security shall be reviewed on a case -by-case 
basis, in conjunction with the implementation of the current technology and appro val from the 
Responsible  authority .  In addition, there shall be:  
 DUS 2657 : 2022  
18 © UNBS yyyy – All rights reserved  
 a) No unauthorized remote user administration functionality (adding users, changing permissions, 
etc.);  
b) No unauthorized access to any database other than information retrieval using exis ting 
functions; and  
c) No unauthorized access to the operating system.  
d) For systems using an electronic RNG, the electronic raffle system must immediately detect 
remote access.  
6.3.2  Remote Access Auditing  
The electronic raffle system must maintain an ac tivity log which updates automatically depicting all 
remote access information, to include:  
a) Log on name;  
b) Time and date the connection was made;  
c) Duration of connection; and  
d) Activity while logged in, including the specific areas accessed and cha nges that were made.  
6.4 Wide Area Network Communications  
6.4.1  General Statement  
Wide Area Network (WAN) communications are permitted as allowed by the Reponsible authority  
and shall meet the following requirements:  
a) The communications over the WAN are secured from intrusion, interference and eavesdropping 
via techniques such as use of a Virtual Private Network (VPN), encryption, etc; and  
b) Only functions documented in the communications protocol shall be used over the WAN.  The 
protocol specification s hall be provided to the Testing Laboratory.  
6.5 Wireless Network Communications  
6.5.1  General Statement  
Should a wireless communication solution be utilized, it is recommended to adhere to the following 
requirements  
a) Segregation of Networks. Networks us ed by the electronic raffle systems should be separate 
and not include other devices that are not part of the electronic raffle system.  
b) Service Set Identifier (SSID). The wireless network name (SSID) used to identify the wireless 
network should be hidde n and not broadcast.  
c) Media Access Control (MAC) Address Filtering. The wireless network should use MAC address 
filtering as means to validate whether or not a device may connect to the wireless network.   
d) Device Registration. The electronic raffle sy stem should use a device registration method as 
means to validate whether or not a device is an authorized device on the electronic raffle system.   DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  19 
  DUS 2657 : 2022  
20 © UNBS yyyy – All rights reserved  
  DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  21 
 Annex  A 
(normative)  
 
Annex title  
A.1 General  
Annexes  shall appear in the order in which they are cited i n the text. Each annex shall be designated by a 
heading comprising the word “Annex” followed by a capital letter designating its serial order, beginning with 
“A”, e.g. “Annex  A”. The annex heading shall be followed by the indication “(normative)” or “(info rmative)”, and 
by the title, each on a separate line. Numbers given to the clauses, subclauses, tables, figures and 
mathematical formulae of an annex shall be preceded by the letter designating that annex followed by a full -
stop. The numbering shall start afresh with each annex. A single annex shall be designated “Annex  A”. 
Normative annexes  give provisions additional to those in the body of the document. Their presence is 
optional. An annex’s normative status (as opposed to informative) shall be made clear  by the way in which it is 
referred to in the text, by an indication in the table of contents and under the heading of the annex.  
Informative annexes  give additional information intended to assist the understanding or use of the document. 
They shall not co ntain requirements, except as described in the following paragraph. Their presence is 
optional. An annex’s informative status (as opposed to normative) shall be made clear by the way in which it is 
referred to in the text, by an indication in the table of contents and under the heading of the annex.  
Informative annexes shall contain optional requirements. For example, a test method that is optional shall 
contain requirements but there is no need to comply with these requirements to claim compliance with the  
document.  
A.2 Clause  
A.2.1  Subclause (level  1) 
A.2.1.1  Subclause (level  2) 
A paragraph.  
A.2.1.1.1  Subclause (level  3) 
A paragraph.  
A.2.1.1.1.1  Subclause (level  4) 
A paragraph.  
A.2.1.1.1.2  Subclause (level  4) 
A paragraph.  
A.2.1.1.2  Subclause (level  3) 
A paragraph.  DUS 2657 : 2022  
22 © UNBS yyyy – All rights reserved  
 A.2.1.2  Subclause (level  2) 
A paragraph.  
A.2.2  Subclause (level  1) 
A paragraph.  
A.3 Clause  
A.3.1  A level  1 subclause without a title.  
A.3.1.1  A level  2 subclause without a title.  
A.3.1.1.1  A level  3 subclause without a title.  
A.3.1.1.1.1  A level  4 subclause without a title.  
A.3.1.1.1.2  A level  4 subclause without a title.  
A.3.1.1.2  A level  3 subclause without a title.  
A.3.1.2  A level  2 subclause without a title.  
A.3.2  A level  1 subclause without a title.  DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  23 
 Annex  B 
(informative)  
 
Which styles correspond to which element  — Quick reference guide  
Element  Style name  a 
Any element of text for which the correct style to use is not known with certainty or 
for which no other style of the template is suitable  Special  
Annex  heading, status and title  ANNEX  
Bibliography  reference entry  bibliography  
 title zzBiblio  
Clause  body of document  Heading  1* 
 annexes  a2 
Definition  Definition  
Displayed mathematical 
and chemical formulae  formula  Formula  
variables list  dl 
Example  Example  
Figure  footnote  Figure footnote  
 note Note  
 title Figure title  
Figure footnote  Figure footnote  
Footnote  reference  Footnote Reference*  
 text Footnote Text*  
Foreword  text Foreword  
 title zzForeword  
Index  entry  Index 1*  
 entry h eading  Index Heading*  
 “Index” title  zzIndex  
Introduction  text Normal*  
 title Introduction  
List ordered  level 1 List Number*  
  level 2 List Number  2* 
  level 3 List Number  3* 
  level 4 List Number  4* 
 unordered  level 1 List Continue*  
  level 2 List Continue  2* 
  level 3 List Continue  3* 
  level 4 List Continue  4* DUS 2657 : 2022  
24 © UNBS yyyy – All rights reserved  
 Element  Style name  a 
Normative reference  cross -reference to a normative reference defined in the 
“Normative references” clause  ExtXref  
in “Normative references” clause  RefNorm  
Note integrated in text, fi gures and tables  Note  
Paragraph  Normal*  
Subclause with title  annexes  level 1 a3 
  level 2 a4 
  level 3 a5 
  level 4 a6 
 body of text  level 1 Heading  2* 
  level 2 Heading  3* 
  level 3 Heading  4* 
  level 4 Heading  5* 
  level 5 Heading  6* 
Subclause  without title  level 1 p2 
 level 2 p3 
 level 3 p4 
 level 4 p5 
 level 5 p6 
Table  note Note  
 table footnote  See Table footnote.  
 text 9 pt (recommended)  Table text (9)  
  8 pt, for large tables  Table text (8)  
  7 pt, for very large tables  Table text (7) 
  10 pt (not recommended)  Table text (10)  
 title Table title  
Table footnote  identification letter of the table footnote  TableFootNoteXref  
 reference  TableFootNoteXref  
 text Table footnote  
Table of contents  “Contents” title  zzContents  
 entries  level 1 TOC  1* 
  level 2 TOC  2* 
  level 3 TOC  3* 
  level 4 TOC  4* 
  level 5 TOC  5* 
  level 6 TOC  6* 
  unnumbered elements  TOC  9* DUS 2567 : 2022  
© UNBS 2022  – All rights reserved  25 
 Element  Style name  a 
Term  cross -reference to a term defined in the “Terms and 
definitions” clause  Defterms  
 in the “Terms and definitions” cla use in a terminology 
document  Term(s)  
 reference number  TermNum  
a Style names marked with an asterisk are based on predefined Microsoft styles. These styles are recognized by the 
various linguistic versions of Word and their names shallbe translated auto matically into the language of the Word version 
which you are using. For these Microsoft styles, the user shallneed to derive the correspondence between the name displayed 
and that given in this table; for example, if the same document is opened using Engl ish and French versions of Word, text 
styled “Footnote Reference” in the English version is called “Appel de note” in the French version.  
 DUS 2657 : 2022  
26 © UNBS yyyy – All rights reserved  
 Bibliography  
[1] ISO ##### -#, General title — Part #: Title of part  
[2] ISO ##### -##:20##, General title — Part ##:  Title of part  
A Bibliography , if present, shall appear after the last annex. The drafting rules set out in ISO  690[11] shall be 
followed.  
The bibliography shall include  
— documents that are not publicly available,  
— documents which are only cited in an i nformative manner, and  
— documents which have merely served as bibliographic or background material in the preparation of the 
document.  
For online referenced documents, information sufficient to identify and locate the source shall be provided. 
Preferably,  the primary source of the referenced document should be cited, in order to ensure traceability. 
Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The 
reference shall include the method of access to the referenced document and the full network address, with 
the same punctuation and use of upper case and lower case letters as given in the source (see ISO 690-2[12]). US nnnn -n: yyyy  
© UNBS 2022  – All rights res erved  27 
 Certification marking  
Products that conform to Uganda standards shall be marked with U ganda National Bureau of Standards 
(UNBS) Certification Mark shown in the figure below.  
The use of the UNBS Certification Mark is governed by the Standards Act, and the Regulations made 
thereunder. This mark can be used only by those licensed under the ce rtification mark scheme operated by 
the Uganda National Bureau of Standards and in conjunction with the relevant Uganda Standard. The 
presence of this mark on a product or in relation to a product is an assurance that the goods comply with the 
requirements  of that standard under a system of supervision, control and testing in accordance with the 
certification mark scheme of the Uganda National Bureau of Standards. UNBS marked products are 
continually checked by UNBS for conformity to that standard.  
Further  particulars of the terms and conditions of licensing shall be obtained from the Director, Uganda 
National Bureau of Standards.  
 
 US nnnn -n: yyyy    
 
ICS nn.nnn.nn  
Price based on nn pages  
© UNBS yyyy– All rights reserved