related to PDS operations and specifically FPS sale are manual in nature which lead to a lot of diversions as it is not possible to probe whether actual sale happened at FPS or not. The solution is to ensure the fair Last Mile Delivery of essential commodities. The solution lies in distributing the essential commodities using electronic device with biometric authentication of any member of beneficiary in order to restraint the diversion at the FPS level. FPSs provide the only touch point for the end beneficiary in the total Public Distribution System (PDS). Thus, having transparency in the functioning of FPS is critical for having greater transparency in the overall PDS value chain. Therefore, Component–II of the “End-to-End computerization of PDS - (FPS Automation)” involves electronic transactions at the FPS level. This automation provides a medium to record and transmit the transactions made at the FPS. FPS Automation also intends to authenticate the beneficiary to ensure that the commodity issuance is happening to the intended beneficiary by biometric authentication with UIDAI server. As per Chapter-V of the NFSA act, point no. 12 (2): “(b) application of information and communication technology tools including end-to-end computerization in order to ensure transparent recording of transactions at all levels, and to prevent diversion; (c) leveraging “aadhaar” for unique identification, with biometric information of entitled beneficiaries for proper targeting of benefits under this Act;” Further, as per Chapter – III of the Aadhaar (TARGETED DELIVERY OF FINANCIAL AND OTHER SUBSIDIES, BENEFITS AND SERVICES) Act, 2016, point no. 7: “The Central Government or, as the case may be, the State Government may, for the purpose of establishing identity of an individual as a condition for receipt of a subsidy, benefit or service for which the expenditure is incurred from, or the receipt therefrom forms part of, the Consolidated Fund of India, require that such individual undergo authentication, or furnish proof of possession of Aadhaar number or in the case of an individual to whom no Aadhaar number has been assigned, such individual makes an application for enrolment: Provided that if an Aadhaar number is not
FPSH1.3 Longitude lon double Longitude of FPS geographic location Longitude of FPS geographic location FPSH1.4 cc varchar(2) Device Company Code Y The list shall be released and updated as and when vendor devices are registered. Permissible value is numeric [0-9] FPSH1.5 mac varchar(64) MAC Id of the FPS device. Y Y Shall be either 48 or 64 bits. And has to be registered with Server. Permissible value is numeric [0-9] app_version ver varchar(5) Version of Distribution application Y Y xx.yy where xx is major and yy is minor version where x,y E [0-9) FPSH1.7 request_ts date with timestamp Date and timestamp when the request is made Y ddMMyyyyhhmmss format
Latitude lat double Latitude of FPS geographic location Latitude of FPS geographic location FPSH1.3 Longitude lon double Longitude of FPS geographic location Longitude of FPS geographic location FPSH1.4 cc varchar(2) Device Company Code Y The list be released and updated as and when vendor devices are registered. Permissible value is numeric [0-9] FPSH1.5 mac varchar(64) MAC Id of the FPS device. Y Y Shall be either 48 or 64 bits. And has to be registered with Server. Permissible value is numeric [0-9] FPSH1.6 app_version ver varchar(5) Version of Distribution application Y Y xx.yy where xx is major and yy is minor version where x,y E [0-9)
FPSBA.1 bio bio varchar(255) Encrypted authentication code in Xml format Y Y Symbols) FPSBA.2 mid mid varchar(14) Uniquely identifies the member with id. Y (0-9) FPSBA.3 sid sid varchar(42) Uniquely identifies the transaction Y (0-9 with Time stamp) FPSBA.4 uid uid varchar(12) Unique Aadhar number Y (0-9) FPSBA.5 txnid varchar(42) Unique Transaction id Y (0-9 with Time stamp) Beneficiary Authentication Acknowledgement (JSON): { " PDSReceiveBeneficiaryAuthentication Ack": [{ “fps”:””, “”req”:””, “acks”:””, “ackr”:””, “txnid”:””, "authcode": "", "mid": "", "uiderrcode": "", "uid": "", }] } Beneficiary Authentication Acknowledgement (Metadata): PDSA1
Longitude lon double Longitude of FPS geographic location Longitude of FPS geographic location FPSH1.4 cc varchar(2) Device Company Code Y The list shall be released and updated as and when vendor devices are registered. Permissible value is numeric [0-9] FPSH1.5 mac varchar(64) MAC Id of the FPS device. Y Y Shall be either 48 or 64 bits. And has to be registered with Server. Permissible value is numeric [0-9] FPSH1.6 app_version ver varchar(5) Version of Distribution application Y Y xx.yy where xx is major and yy is minor version where x,y E [0-9) FPSH1.7 request_ts reqts date with timestamp Date and timestamp when the request is made Y ddMMyyyyhhmmss format
Id Name xml tag name Length Purpose Unique? FPSD1.1 fps_id fps varchar(12) Fair Price shop Id : DDDDAAASSSSS Y Refer FPSH1.1 FPSD1.2 varchar Allocation Number with Timestamp Y Allocation number with timestamp FPSD1.3 txnid varchar(42) Sale transaction unique Id Y Y FPS ID(12) + Rc Id(12) + FPS Id - Refer FPSH1.1 RC Id - Refer PDSD1.2 DD - Date of Transaction MM - Month of Transaction YYYY - Year of Transaction hh - Hour of Transaction mm - Minutes of Transaction ss - seconds of Transaction .mmm - DOT delimiter for milliseconds followed by milliseconds FPSD1.4 txndate ddMMyyyy Date of transaction Y TRANSACTION DATE without timestamp rcno varchar(12) Ration Card number Y Refer PDSD1.1 FPSD1.6 rctype varchar Ration card Type on economic status of the family Y Refer PDSD1.2 FPSD1.7 Varchar(2) Commodity code for stock is received Y premissible value is numeric (0-99) . Refer ePDS Metadata Draft List Required
PDSH1.3 res integer Lot number of the response. It is an integer indicating a unique response number to each request id. This number will be same for all the batches of a lot. By default Lot Id is 1 Y (1,n) PDSH1.4 response_ts rests varchar(14) Timestamp of the response. It will vary with each batch Y Y ddmmyyyyhhmmsss format batch_id bid integer Batch ID of the response lot. Y is [0,9] reccnt integer Records in current batch. Y [0,9] totcnt integer Total records Y [0,9] PDS Data Download Data (PDSH1)(Metadata) Packet Data : PDSD1 Response form PDS Server for ReqCode = RCMD data Id Field Name xml tag name Length Purpose Unique? Range PDSD1.1 rcno varchar(12) 12 unique ration card number as in electronic PDS system Y Ration Card number of the beneficiary. It is unique for each beneficiary throughout India. PDSD1.2 rctype varchar(2) Card type indicating Economical status of a family Y Card type code for a family indicating economic status. PDSD1.3 member_id memid varchar(14) Member Id as in elctronic PDS Y Y Member Id is 12 digit Ration Card Id(PDSD1.1) + 2 digit sequence number of family member id.
PDSD1.4 memen varchar(99) Name of Member in English Y [a-z, A-Z] PDSD1.5 varchar(99) Name of Member in Local Language Y PDSD1.6 rel varchar(2) Relation of member with Head of Family. SELF means HOF Y Relation code PDSD1.7 age age integer Member age Y (0-120) PDSD1.8 member_uid uid varchar(12) UID number of Member Y Y 12 Aadhar number seeded and verified. PDSD1.9 mobile_no mob varcahr(10) Mobile Number Y Y Mobile number of Member Metadata of Entitlement Data: PDSD4 Packet Data : PDSD4 Response from PDS Server for ReqCode = ENT* Id Field Name xml tag name Length Purpose Unique? PDSD4.1 rcno varchar(12) 12 digit unique ration card number as in electronic PDS system Y Y Refer PDSD1.1
PDSD4.2 ano varchar Allocation Number Y Y [0-9] PDSD4.3 atype varchar(1) Allocation Type Y 0-Regular 1-Adhoc 2-Additional/Special PDSD4.4 comm_code varchar(2) Commodity Code Y premissible value is numeric (0-99) . Refer ePDS Metadata Draft List unit price uprice double Unit price of that commodity Y Up to 2 decimal places munit varchar(1) Measurement Unit Y [0-9] . Refer ePDS Metadata Draft List PDSD4.7 eqty double Entitled quantity for that commodity Y Up to 2 decimal places adate date Allocation date Y Date PDSD4.9 month month integer Y (1,12) year year integer Year Y [0-9]4 times card_type ctype smallint Card Type Y [0-9] unit_flag uflag varchar(1) Unit Flag Y Member based - m, Cardbased - c, Unit based
Appendix-B Preferable/Popular Matrix (Indicative) OS Type Device Type App Type App Mode Aadhaar Support Windows OS till 8.1 PC/Laptop Web Online Yes Linux OS PC/Laptop Web (HTML5.0/CSS3) Online Yes iOS iMac PC/Laptop Web (HTML5.0/CSS3) Online Not Available Linux OS Kernal6.0 PoS Native Online +Offline Yes Windows 10 PC/Tablet/PoS/Mobile Phone Native Online + Offline Yes Android Tablet/PoS/Mobile Native Online + Offline Yes iOS Tablet/Mobile Phone Native Online + Offline Not available
Appendix-F Detailed Functionalities Essential Functionality User Management: User management module shall enable registration process, FPS, management of password, User Access and Authorization Management. Following functionalities shall be covered under this module 1 Functional Requirements of User Management 1.1 Registration System must allow user to register FPS during/after installation of PoS software Facility to register the FPS Owner FPS shall be allowed to create other users (operators) [subject to approval of state government] Aadhaar number shall also be recorded for Aadhaar authentication 1.2 Access Control System provide role-based access for application modules 1.3 Password Management [may also be managed at PDS Server System shall allow textual password /biometric based login Biometric based login shall be done through Aadhaar authentication System allow a maximum of three/ configurable attempts to login. System shall allow the user to regenerate a lost password/reset password System shall encrypt the user passwords 1.4 Exceptions [subject to approval of state government] System shall allow limited functionality (like reports) to FPSs which are temporarily suspended User to be blocked beyond unsuccessful attempts Provision to be given for unblocking the user Biometric authentication to be enabled for user login if network connectivity is available Master Data and Entitlement download in case of occasionally online mode: For occasionally online mode, the input data for sales & receipts at FPS has to be downloaded to the PoS device in a secured and consistent manner. 2 Master Data and Allocation Download & Upload in offline mode 2.1 Master Data Download Data related to Ration card number and beneficiary shall be downloaded once in a month in PoS device for the FPS Downloading of master data not to be allowed if it is already stored for current allocation month Following data may be downloaded: FPS Details Commodity Master (only active commodities)
Appendix-G Suggested Report Formats Daily Status Report/ Monthly Status Report: (Monthly – For the Month of : ) (Daily – For the Date : ) For given range of dates (Date from : Date To: ) Commodity Quantity (In KG) Scheme Amount (In. Rs.) 3.0 AAY 6.00 Rice 3.5 AAY 10.50 Total Amount :Rs 16.50 Summary of Register FPS ID FPS Name Date as on Commodity Opening Balance in the beginning of Received Quantity during this month Quantity of Sale during this month Closing Balance (Balance as on date) Rice Wheat