The Electronic Certification for Import & Export
[pic]
Table of Contents
1. INTRODUCTION 3
1.1 PURPOSE 3 1.1.1 INTENDED AUDIENCE 3
1.2 SCOPE OF WORK 3
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS 4
1.4 REFERENCES 6
1.5 OVERVIEW 7
2. OVERALL DESCRIPTION 9
2.1 PRODUCT PERSPECTIVE 9 2.1.1 KNOWLEDGE MANAGEMENT APPLICATION 9 2.1.2 SYSTEM INTERFACES :- 10 2.1.3 USER INTERFACES:- 11 2.1.4 HARDWARE INTERFACES 11 2.1.5 SOFTWARE INTERFACES 11 2.1.6 COMMUNICATIONS INTERFACES 12 2.1.7 MEMORY CONSTRAINTS 12 2.1.8 OPERATIONS 12 2.1.9 SITE ADAPTATION REQUIREMENTS 12
2.2 PRODUCT FUNCTIONS(CURRENT AS IS BUSINESS PROCESSES) 13 2.2.1 ANIMAL QUARANTINE CERTIFICATION PROCEDURES 13 2.2.2 PLANT QUARANTINE CERTIFICATION PROCEDURES 35
2.3 PRODUCT FUNCTIONS( TO BE WORK FLOW) 41 2.3.1 THERE WOULD BE THREE MODULE OF THE ANIMAL QUARANTINE CLEARANCE APPLICATION 41 2.3.2 PLANT QUARANTINE CERTIFICATION PROCEDURE 53 2.3.3 THERE ARE VARIOUS FUNCTIONALITIES IN THESE MODULE, COMMON FUNCTIONALITIES ARE GIVEN BELOW: 56
2.4 USER CHARACTERISTICS 57
2.5 CONSTRAINTS 57
2.6 ASSUMPTIONS AND DEPENDENCIES 58
3. SPECIFIC REQUIREMENTS 59
3.1 SOFTWARE PRODUCT FEATURES 59 3.1.1 ACTORS 59 3.1.2 COMMON USE CASES 60 3.1.3 SYSTEM ADMINISTRATOR 72
3.2 ANIMAL QUARANTINE 77 3.2.1 SIP & AQIS ACTIVITIES USE CASES 77 3.2.2 FAQ 111 3.2.3 MASTER USE CASES 124
3.3 PERFORMANCE REQUIREMENTS 163 3.3.1 SCALABILITY REQUIREMENTS 163 3.3.2 RESPONSE TIME 163
3.4 SOFTWARE SYSTEM ATTRIBUTES 163 3.4.1 USABILITY 163 3.4.2 INTERNAL / INTRANET USERS 163 3.4.3 INTERNET USERS 164 3.4.4 RELIABILITY 164 3.4.5 AVAILABILITY 164 3.4.6 SECURITY 164 3.4.7 MAINTAINABILITY 165 3.4.8 PORTABILITY 165 3.4.9 LANGUAGE SUPPORT 165 3.4.10 INTEROPERABILITY 165
3.5 LOGICAL DATABASE REQUIREMENTS 166 3.5.1 DATA STORE: USER_ MASTER 166 3.5.2 DATA STORE: ROLE MANAGEMENT_ MASTER 166 3.5.3 DATA STORE: AQIS (IMPORT/EXPORT) CERTIFICATION FOR LSP_MASTER 166 3.5.4 DATA STORE: AQIS (IMPORT/EXPORT) CERTIFICATION FOR LS/PET ANIMAL _MASTER 168 3.5.5 DATA STORE: SANITARY IMPORT PERMIT_MASTER 169 3.5.6 DATA STORE: VETERINARY HEALTH/ZOO SANITARY CERTIFICATE (LIVESTOCK)(EXPORT) _ MASTER 171 3.5.7 DATA STORE: PROVISIONAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK(IMPORT_ MASTER 171 3.5.8 DATA STORE: FINAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK PRODUCT(IMPORT) _ MASTER 172 3.5.9 DATA STORE: FINAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK (IMPORT) _ MASTER 172 3.5.10 DATA STORE: CERTIFICATE OF HEALTH FOR EXPORT OF PET ANIMAL _ MASTER 173 3.5.11 DATA STORE: NOC FOR IMPORT OF PET ANIMAL _ MASTER 173 3.5.12 DATA STORE: DEPORTATION/DESTRUCTION OF CONSIGNMENT_ MASTER 173 3.5.13 DATA STORE: PINCODE_ MASTER 174 3.5.14 DATA STORE: GRIEVANCE_ MASTER 174 3.5.15 DATA STORE: GRIEVANCE MANAGEMENT_ MASTER 174 3.5.16 DATA STORE: SMS _MASTER 174 3.5.17 DATA STORE: COUNTRY_MASTER 175 3.5.18 DATA STORE: NPPO_MASTER 175 3.5.19 DATA STORE: SEAPORT_MASTER 175 3.5.20 DATA STORE: AIRPORT_MASTER 175 3.5.21 DATA STORE: PRE-DEFINED DISEASE FOR TESTING & SAMPLE _MASTER 175 3.5.22 DATA STORE: DEPARTMENT_MASTER 176 3.5.23 DATA STORE: ANIMAL CATEGORY_MASTER 176 3.5.24 DATA STORE: DESIGNATION_MASTER 176 3.5.25 DATA STORE: BREED_MASTER 176
3.6 OTHER REQUIREMENTS 176 3.6.1 BACKUP 176 3.6.2 RECOVERY 176 3.6.3 DATA RETENTION 176 3.6.4 CUSTOMER/USER TRAINING 177 3.6.5 AUDIT TRAIL 177
4. ANNEXURE 178
4.1 ANNEXURE (1 to 39) IN ONE FOLDER 178
4.2 ANNEXURE 40: ADDRESSES OF PLANT / ANIMAL QUARANTINE OFFICES 178
4.3 ANNEXURE 41: MESSAGE STRUCTURE OF CUSTOM INTEGRATION FOR PQIS 178
INTRODUCTION
1 PURPOSE
The purpose of this document is to provide:
• Detail the AS-IS and To-Be processes. • The document that becomes an input for design document. • A reference document for designer, developers and tester. • Detail document to understand requirement of E-certification for Livestock / Livestock Products based on requirement received from Ministry of Agriculture. • To understand manual procedures, constraints, assumptions & dependencies etc. for e-certification of livestock & livestock product as well as integration requirement of PQIS with stakeholders & custom. • Details related to automated electronic certification for import & export (PQIS, AQIS) services into the umbrella of CAP (Central Agriculture Portal).
1 INTENDED AUDIENCE
The intended audiences for this document are:
• Department of Agriculture and Cooperation, Ministry of Agriculture • PSC Issuing Authorities • Importers and Exporters of Agriculture produce, Livestock & Fisheries within the country • Animal Quarantine and Certification Services Station • Customs Department • Director General of Foreign Trade, Department of Commerce, Ministry of Commerce • Agricultural & Processed Food Products Export Development Authority (APEDA) • Marine Products Export Development Authority (MPEDA) • Vegetable Fruit Promotion Council, Export Promotion Councils • Export Commodity Board • Food Safety and Standards Authority of India (FSSAI) • Analysts, designers, developers, testers and auditors for the automated systems to be developed. • All relevant users, who would want references regarding the system.
2 SCOPE OF WORK
The scope of the document is to identify the software requirement specification relating to:- • Automated workflow based application for various quarantine activities taken up by Animal Quarantine Station. • Issuance of electronic certificate to Importer/Exporter • Integration of PQIS with Customs department and to develop the search option with other stakeholder to check/view authenticity of certification data • The various information which will be available are as follow on AQIS web page:- o Certification procedure o Inspection authorities o Fees and charges o Quarantine requirements o Detail of prohibited items (Animal quarantine order) o Restricted & Free Livestock / Livestock Product • Online payment facility for application fee and inspection fee etc. • SMS alerts for status of Application to Importer/Exporter. • Database on country wise phyto sanitary requirements. • Entire value chain of agriculture commodity to be linked for single point of information. • Our study is to identify a provision to develop application capturing PSC number in case when export consignment is returned. • To identify the possibility of translating the phyto sanitary condition of foreign countries language into English using Google translator or other translation facilities available on internet. • Mechanism for grievance management with regards to e-certification of Importer/Exporter within the central government framework.
3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
|AC |Assistant Commissioner |
|AD |Active Directory |
|Admin |Administrator |
|ADDL |Animal Disease Diagnostic Laboratory |
|AGM |Assistant General Manager |
|APEDA |Agricultural And Processed Food Export Development Authority |
|AQC |Animal Quarantine Certificate |
|AQCS |Animal quarantine Certification Service |
|AQIS |Animal Quarantine Information System |
|BOE |Bill of Exchange |
|BOS |Bill of Shipment |
|CAP |Central Agriculture Portal |
|CD |Compact Disk |
|CDB |Coconut Development Board |
|CSS |Cascading Style Sheet |
|DADF |Department of Animal Husbandry, Dairying & Fisheries |
|DC |Deputy Commissioner |
|DDG |Deputy Director General |
|DGFT |Director General Of Foreign Trade |
|DMI |Directorate of Marketing and Inspection |
|DOH |Department of Horticulture |
|DOB |Date of Birth |
|DPPQS |Directorate of Plant Protection Quarantine & Storage |
|DAC |Directorate of Agriculture Cooperation |
|DT |Director Trade |
|ECB |Export Commodity Board |
|EIC |Export Inspection Council |
|FAQ |Frequently Asked Question |
|FDC |Fishery Development Commissioner |
|FK |Foreign Key |
|FPI |Food Processing Industries |
|FSSAI |Food Safety & Standard Authority of India |
|FY Division |Fishery Division |
|GIS |Graphic Information System |
|GP Stock |Grand Parental Stock |
|GUI |Graphical user Interface |
|HOD |Head of Department |
|HSADL |High Security Animal Disease lab |
|I/E |Importer / Exporter |
|IEC |Import/Export code |
|IP |Import Permit |
|IRO |Import Release order |
|IT |Information Technology |
|ITC-HS Code |Indian Trade Certification based on Harmonized System Code |
|JD |Joint Director |
|JS |Joint Secretary |
|K.G |Kilogram |
|LAN |Local Area Network |
|LS |Livestock |
|LSP |Livestock Product |
|L.T |Liter |
|LH Division |Live Husbandry Division |
|MIS |Management Information System |
|MPEDA |Marine Product Export Development Authority |
|NBPGR |National Bureau of Plant Genetic Resources |
|NeGP |National e-Governance Program |
|NIC |National Informatics Centre |
|NOC |No Objection Certificate |
|NPPO |National Plant Protection Organization |
|NPQS |National Plant Quarantine Station |
|OS |Operating System |
|PK |Primary Key |
|PP |Plant Protection |
|PQS |Plant Quarantine Station |
|PSC |Phyto Sanitary Certificate |
|S.No. |Serial Number |
|SIP |Sanitary Import permit |
|SMS |Short Message Service |
|SO |Section Officer |
|SRS |Software Requirement Specification |
|SSL |Secure Socket Layer |
|URL |Uniform Resource Locator |
4 REFERENCES
Delhi, NCR • Dr. A K Choubey, NIC • Mr. Shahid Hassan, NIC • Dr.S K Dutta, Assistant Commissioner(Trade), NIC • Mr. Raman, Trade Department, NIC • Dr. R K Gupta, Assistant Commissioner (AH Department), NIC • Mr. Siddiqui,Research Officer(Fishery Department) • Mr. DDK Sharma joint director (PP), PQS, Faridabad • Mr. Raman Malik, Arbro Pharmaceuticals • Dr. J P Singh, NPQS • Mr. Adesh Mohan, FSSAI, Delhi • Mr. Sunil Kumar (Sectary), APEDA, Delhi • Mr. MP Vijay (AGM), APEDA, Delhi • Dr. Mandilk, EIC • Dr. Vijay Kumar Teotia, Quarantine Officer, Animal Quarantine, Delhi States: Assam: • Study Report on Electronic Certification of Exports & Imports prepared by D.I.O, Dhubri Himanchal Pradesh • Mr. B.S. Negi, Directorate of Horticulture, Shimla • Mr. Kishore Chand Azad, Senior Marketing Officer,Shimla Jharkhand: • Officer from Plant Protection Division, Ranchi Madhya Pradesh • Dr. Nagarajan, Senior Scientist, High Security Animal Decease Lab, Bhopal. • Dr. Sandeep Bhatia, Senior Scientist, High Security Animal Decease Lab, Bhopal. Karnataka • Mr. Manickam, Deputy Director, Plant Pathology, Bangalore • Ms.Roopa, Director of Agriculture, Plant Pathology department, Bangalore. Maharastra • Mr. Shiv Sagar Verma, Deputy Director (PP), PQS, Mumbai • Dr. Sahdeo D. Bhosale, Quarantine Officer, Animal Quarantine, Mumbai Kerala • Mrs. Usha Singh (Systems Analyst, MPEDA Cochin)
• Mr. Ajithan (Upper Divisional Clerk, PQS)
• Dr. Ramani GopalaKrishnan (Deputy Director, CDB Cochin)
• Mr. Vasanth Kumar (Statistical Investigator, CDB Cochin)
• Mrs. M. Priya (Statistical Assistant)
• Mr. Jnanadevan (Deputy Director (Marketing), Cashew & Cocoa Development) WEB Source • http://plantquarantineindia.nic.in; http://plantquarantineindia.org • http://ppqs.gov.in; http://dadf.gov.in • www.hpsamb.nic.in Documents • Presentation, DPR and document shared by NIC
5 OVERVIEW
Plant Quarantine Certification Service
Export or Import certification (PSC/IP/IRO) is essential for agriculture commodity to ensure that the commodity which coming to India or going out of India is free from pests and diseases.
Plant Quarantine is mandatory for import of any plant material under the provisions of destructive insect & pests act 1914.
Plant Quarantine Certification Service is already operational since 2011 and its website is http://plantquarantineindia.nic.in .
Animal Quarantine Certification Service
The purpose of the Animal Quarantine and certification (AQC) is to prevent the ingress of livestock and poultry exotic to India as per provisions of livestock importation Act, 1898.
The Electronic Certification for Import & Export Will Lead to:-
• Reduce the technical personnel’s time in entering the application details in the system.
• Reduce the process time of the application.
• Optimize the employee’s performance.
• Provide status update on export/import certification applications.
• Provide information on export/import certification procedure.
As of now the information dissemination process runs manually. The Ministry of Agriculture came up with the plan under NeGP plan to integrate various components and systems which can talk and handshake to each other to make the whole process run with seamless manner.
Overall information system flow:
[pic]
Diagram 1: Overall information system
OVERALL DESCRIPTION
1 PRODUCT PERSPECTIVE
1. Automation of existing manual backend processes of Animal Quarantine Certification (AQC) for issuance of SIP and Quarantine clearance certificate for Import/Export to decrease the lead time in processing applications and to provide most up to date information on a. Sanitary Import Permit to Importer b. Issuance of Animal Quarantine Certificate for Export c. Issuance of Animal Quarantine Certificate for Import 2. Information on Fee/Charges of Treatment/Lab/Inspection 3. Information exchange from the stake holders to get the required information. 4. Enable online payment facility 5. Mechanism for grievance management with regards to a specific activity / process within the central government framework. 6. SMS Based alerts and information dissemination. 7. Information on restricted and free products 8. Integration of PQIS application with Customs to exchange information & to develop search option with other stake holders. Apart from the transactional system mentioned above, following are the other categories the system will have:
1 KNOWLEDGE MANAGEMENT APPLICATION
1 CONTENT MANAGEMENT
|S.No. |Web Application Content |Sub Content |
|1. |About Live Stock Importation Act |Service Charter, Client Satisfaction Survey, Animal |
| | |Quarantine Organization Chart, Feedback |
|2. |Exports |Export inspection & certification procedure, Time schedules|
| | |for clearance, Fee & charges, Circular issued to export |
| | |certifying authority. |
|3. |Laws |Laws related to Livestock/Livestock Product |
|4. |Import |Animal order & amendments, Issuance of the sanitary import |
| | |permit, Import inspection & clearance, Procedure of |
| | |quarantine inspection, Time schedules for clearance, Fee & |
| | |charges, List of Livestock /LSP Division to require Animal |
| | |Quarantine clearance, Sampling & health certificate request|
| | |form |
|5. |Contact us |All the office addresses |
|6. |Related link |All the general users, importer/exporter would click on the|
| | |related link to get the information about all the |
| | |stakeholders available on the AQIS web page through |
| | |hyperlink. |
2 DATABASE MANAGEMENT
|S No. |Sub Content |
|1. |Database on requirements for import & export of Livestock /LSP |
|2. |Database of AQC notified laboratories |
|3. |Database on importer & exporter |
|5. |Database on commodity, country & port |
|6. |Providing access of PSC to NPPO of other countries |
|7. |FAQ on export & import procedure for Livestock /LSP & related government schemes |
|8. |Resolution of personalized queries |
3 SMS MANAGEMENT
|1. |SMS alert sent to exporter or importer after scrutiny of document in case of deficiency (IP/PSC/SIP/AQC) |
|2. |SMS based information for IP/PSC issued or rejected in case of PQIS and NOC/Provisional AQC /Final AQC issued or rejected |
| |in case of AQIS. |
4 PAYMENT GATEWAY INTEGRATION
|S.No. |Payment online ------- through payment gateway --------- Availability of services online 24 X 7 ( 99.9%) uptime |
|1. |The payment gateway would be used by the Importer / Exporter Importer |
| |To make payment for import / export certification like IP, PSC, AQC, SIP. This will facilitate the payment to be made|
| |through net banking, debit card, credit card, cash and draft |
2 SYSTEM INTERFACES :-
The system shall so be designed in such a manner that there should be linkages with other existing systems. The automated application shall be a web based application / interface which will be incorporated with features like certificate generation with the facility of viewing them online. These results shall be made available in CAP for quick dissemination of results. Besides this, there will also be push SMS’s to the different stakeholders informing them about the various information’s within the system
[pic]Diagram 2: System Interface
3 USER INTERFACES:-
Web based Graphical User Interface (GUI) will be provided. Portal will be completely menu driven and user friendly. The GUI consists of the various Input forms, output screens along with the help files provided as per the requirement.
[pic] Diagram 3: User Interface
4 HARDWARE INTERFACES
No specific hardware interface would be required for this application.
The following hardware interfaces are required to access the portal:
Computer System: any x86 based computer
Printer: A Laser Printer will be needed to take the various outputs of the system time to time.
5 SOFTWARE INTERFACES
At Client End: Base OS: Any Windows/Linux based operating system or any other system having graphical user interface based Operating System
Browser: Internet Explorer 6.0 or above, Mozilla Firebox, Google Chrome or Opera
At Server End: Base OS – Will be decided later at the development stage Framework - Will be decided later at the development stage
Technology Platform – Will be decided later at the development stage
Database - Will be decided later at the development stage
Browser – Internet Explorer 6.0 or above
2.1.6 COMMUNICATIONS INTERFACES
The Application will work on Local Area Network (LAN) or Internet also. Along with this, the system will interact with the SMS Gateway server to push SMS to different stakeholders and emails servers also to send the automated emails generated from the system to various stakeholders of the system
2.1.7 MEMORY CONSTRAINTS
The proposed system will be suitably performed on any system. However, lower primary memory will not debar the system from running but performance might not reach up to expected level.
There is no such need in major secondary memory availability, so it is not constrained.
2.1.8 OPERATIONS
During the course of application usage, general user including CAP users will not be required perform any operation other than system features. Applications and portals will be hosted at Data Centre in secured government domain. Normal maintenance operations such as backup will be scheduled and automated and will be looked into by the system administrators in case of any recovery is to be done. User initiations not needed. No additional data processing operations by the users would be required except the system interactive options.
2.1.9 SITE ADAPTATION REQUIREMENTS
The application proposed will be developed as a web based application. For running the application the computer system having a basic GUI based Operating System and browsers will be required as minimum requirements along with internet connectivity.
Skilled manpower along with data entry operators at various locations like centre, states and other offices at different level will be required to upload and update the information/data.
2 PRODUCT FUNCTIONS(CURRENT AS IS BUSINESS PROCESSES)
The existing information on e-certification to Exporter/ Importer linkage:
[pic] Diagram 4: E-certification to Exporter/ Importer linkage
1 ANIMAL QUARANTINE CERTIFICATION PROCEDURES
The major objective of the Animal Quarantine and certification Station (AQCS) is to prevent the ingress of livestock and poultry exotic to India as per provisions of livestock importation Act, 1898. It is essential to obtain the appropriate NOC from this body prior to transport of pets- dogs and cats, live chicks and other livestock products through air travel or sea route. [pic]
Diagram 5: Certificate Issuance Authorities
Trade Division: This division does the process for issuing SIP which is requiring for importing of livestock product.
Animal Quarantine Station: This station does the process for issuing quarantine certification for importing as well as exporting of LS & LSP.
There are three categories of LS/LSP under the Stock Importation Act 1898
1. Free 2.Restricted and 3. Prohibited
1. Free Category: There are Livestock’s/Livestock Products which are free to import into India from other countries for which sanitary import permit is required.
2. Restricted Category: There are Livestock’s/Livestock Products which are restricted, the import into India of these products shall be allowed only against a license issued by DGFT.
3. Prohibited Category: The department of Animal Husbandry and Dairying has banned the import of Livestock’s/Livestock Products from selected countries due to the outbreak of virus or disease.
The following processes are being followed by DADF and Animal Quarantine Certification Station manually
1. Issuance of Sanitary import permit (being issued from DADF) a. Issuance of SIP: Case 1 (Meeting Case) b. Issuance of SIP: Case 2 (Fast Track Case) c. Issuance of SIP: Case 3 (On-file Case) 2. Collection of fee/charges for treatment/lab/vaccination from Importer/Exporter 3. Issuance/Rejection of Animal Quarantine Certificate in case of Import for a. Livestock b. Livestock Product c. Pet Animal (Dog/Cat) 4. Issuance/Rejection of Animal Quarantine Certificate in case of Export for a. Livestock b. Livestock Product c. Pet Animal (Dog/Cat)
Existing Process of each section has been described below:
1 ISSUANCE OF SANITARY IMPORT PERMIT:
This section contains the work flow that how an importer can get the Sanitary import permit for Livestock Product from DADF.
The Sanitary import permit shall be issued by DADF for import of livestock product and for livestock; license will be issued from DGFT & verified by DADF. The import permit shall lay down the specific condition that will have to be fulfilled in respect of consignment, including pre shipment certification and quarantine checks. The permit shall also specify the post – import requirements with regard to quarantine inspections, sampling & testing. The import permit issued shall be valid for a period of six month. There are two type of forms which importer has to fill depends upon the use of import product.
Form A: - Application for permit to import livestock products for personal consumption.
Form B: - Application for permit to import livestock product for trading/Marketing.
There are three Cases for Issuance of SIP
[pic]
Diagram 6: Type of SIP
1 Issuance of SIP Process (Meeting case)
• Application along with documents sent to section officer for scrutiny if all the relevant documents are attached then section officer forwards the application to AC trade for verification. • If all the relevant documents are not attached with the application then section officer sends back the application to the importer. • AC trade verifies all the documents and sent it to the divisional head for comments. • If the application is for Dairy Product then the application will go to Dairy division and LH Division • If the application is for Meat feather, GP stock then the application will to LH division. • If the application is for fishing items then the application will go to FY division. • Each department process the application • Dairy division • Agenda received from trade division by asst. commissioner. • Comments prepared by asst. commissioner. • Comments sent to technical officer for input if any. • Comments sent to DDG for approval. • If not approved correction made by AC and comment finalized. • If approved final comment will be discussed in meeting with trade division. • LH division • Agenda received from trade division by asst. commissioner. • Comments prepared by ass. Commissioner. • Comments sent to deputy commissioner for input if any. • Comment sent to JS for input if any. • Comment sent to JS divisional head for approval. • If not approved correction made by AC trade and comment finalized. • If approved final comment will be discussed in meeting with trade division. • FY division • Agenda received from trade division by fishery research officer • Comments prepared by fishery research officer. • Comments sent to fishery development commissioner for input if any. • Comment sent to JS divisional head for approval. • If not approved correction made by AC trade and comment finalized. • If approved final comment will be discussed in meeting with trade division.
• After receiving comments from all the divisions, AC trade will call the meeting with all the divisional head and puts agenda. • If JS trade approves the agenda then application sends back to AC trade for signature • After signature of AC trade SIP issued to the importer. • If JS Trade not approved the agenda/comments on SIP then letter issued to importer with reason for not issuing the SIP.
Work Flow for Issuance of Sanitary Import Permit: Case-1 (Meeting Case)
[pic] Diagram 7: Meeting Case
2 Issuance of SIP Process (Fast Track)
• Application along with documents sent to section officer for scrutiny if all the relevant documents are attached then section officer forwards the application to AC Trade for verification. • If all the relevant documents are not attached with the application then section officer sends back the application to the importer. • AC Trade verifies all the documents & sends it to Director Trade for approval. • If Director Trade approves then approved application sends back to AC Trade for signature. • After signature AC Trade issues SIP to the importer. • If Director Trade not approved the application/document then letter issued to importer with reason for not issuing the SIP.
Work Flow for Issuance of Sanitary Import Permit: Case-2 (Fast Track)
[pic] Diagram 8: Fast Track
Fast Track process items are as follows:
1. Fish Feed 2. Fish Food 3. Whey Protein 4. Cheese 5. Hilsa 6. Bovine Serum
3 Issuance of SIP Process (On File)
• Application along with documents sent to section officer for scrutiny if all the relevant documents are attached then section officer forwards the application to AC Trade for verification. • If all the relevant documents are not attached with the application then section officer sends back the application to the importer. • AC Trade verifies all the documents & sends it to divisional head for comments. • If the application is for Dairy Product then the application will go to Dairy division and LH Division both • If the application is for Meat feather, GP stock then the application will to LH division. • If the application is for fishing items then the application will go to FY division. • Each department process the application Dairy division • Agenda received from trade division by asst. commissioner. • Comments prepared by asst. Commissioner. • Comments sent to technical officer for input if any. • Comment sent to DDG for approval. • If not approved correction made by AC Trade and comments finalized. • If DDG approved then final comments will be discussed in meeting with trade division.
LH division • Agenda received from trade division by asst. commissioner. • Comments prepared by asst. Commissioner. • Comments sent to deputy commissioner for input if any. • Comment sent to JC for input if any. • Comment sent to JS (divisional head) for approval. • If JS approved then final comments will be discussed in meeting with trade division. • If not approved correction made by AC and comments finalized
FY division • Comments prepared by fishery research officer. • Comments sent to fishery development commissioner for input if any. • Comment sent to JS (divisional head) for approval. • If approved final comments will be discussed in meeting with trade division. • If not approved correction made by AC Trade and comment finalized • After receiving comments from all the divisions, AC Trade will call the meeting with all the divisional head and puts agenda.
• Director trade receives comments from all divisional heads if he approves then approved application/document sends back to AC Trade for signature. • After signature of AC trade SIP issued to the importer. • If Director Trade not approved the application/document then letter issued to importer with reason for not issuing the SIP.
Work Flow for Issuance of Sanitary Import Permit: Case-3(On file)
[pic] Diagram 9: On File
Suggestions:
• Post import condition should be computerized this will improve the time & speed of the process. It will eliminate the process of internal file movement within the department.
• Back and forth movement of the file should be there in the application to undo the wrong movement of file.
Animal Quarantine Certification Station:
Animal Quarantine Certification Station does certification process for quarantine clearance of Livestock, Livestock Product & Pet Animal in case of Import & Export.
[pic] Diagram 10: AQCS
There is no fee/charge for Issuance of SIP or AQCS certification. Fee for treatment/lab/vaccination if required during the quarantine certification process for livestock/livestock product will be paid by the Importer/Exporter. In case of livestock, 30 days observation fee at quarantine station has to pay by the Importer. Example: for a horse the observation fee is Rs. 250 per day per horse. Similarly the observation fee may vary, depends on the livestock. In case of livestock treatment/vaccination at quarantine station if required will be paid by the Importer/Exporter. In case if Lab test is required for sample of livestock/livestock product then Importer/Exporter has to pay the Lab fee to the quarantine officer by Cheque and the payment will be made when the sample is taken.
2 ISSUANCE OF ANIMAL QUARANTINE CLEARANCE CERTIFICATE IN CASE OF IMPORT
No Objection Certificate for import of companion animals (only pet dogs and cats) into India. Import of animals (birds, mammals, fish or reptiles) or animal products ( meat-raw or processed- skin, hoof, feather, shuttlecock, buttons etc.) other than the above including laboratory animals will necessitate the procurement of an import license/sanitary import permit from a competent authority(DGFT)/ AQCS prior to issuance of the NOC from the AQCS.
1 Import of Livestock
This section contains the work flow that how an importer can get the Animal Quarantine Certificate for Livestock from AQCS.
• First information: the importer or his/her authorized representative should contact the animal quarantine officer in advance about the intended import consignment. • The details pertaining to the same must be physically submitted to the office of the AQCS on a prescribed format of the office along with photocopies of the following o Veterinary certificate/ Health certificate of the animal issued only by the designated veterinary officer of the exporting country confirming the health status of the animal and its fitness for the export/ travel. This certificate should be only in English (or bilingual with one language as English). o Details of vaccination. o Copies of the passport and travel ticket of the owner of the animal. • After satisfactory verification of the above documents, the AQCS office will issue the NOC for import of the animal consignment which needs to be carried physically along with the animal. • On arrival at Sea port/ Airport, the importer will report to the quarantine officer with the original copies of all the above listed documents for obtaining a provisional Quarantine Clearance Certificate which will be issued upon satisfactory verification of the documentation and the physical health of the animal. • After quarantine clearance from custom, the quarantine officer will bring the livestock/animal to the quarantine station for 30 days for health observation, and importer has to pay the fee for 30 days observation to quarantine station.
• On satisfactory completion of 30 days of home quarantine, the importer must contact the AQCS office for final clearance of the animal from the quarantine angle.
Work Flow of Animal Quarantine Certification for Livestock in Case of Import:
[pic]
Diagram 11: As-Is of AQC for Livestock Import
Documents to be attached along with the application for advance NOC/Clearance of Livestock: 1) DGFT License, if any. 2) SIP, if any. 3) Testing fee & accommodation charges, if any. 4) Custom related documents. 5) Advance copy of Official Health Certificate from the Country of Origin as per the Indian Health Protocol.
2 Import of Livestock Product
This section contains the work flow that how an importer can get the Animal Quarantine Certificate for Livestock Product from AQCS. Livestock products include meat and meat products of different types that comprise fresh, chilled and frozen meat as well as tissue or organs of poultry, pig, sheep and goat. It also consists of egg and egg powder; milk and milk goods; pet foods of animal origin and embryos, ova or semen of cows, sheep and goats. No livestock product may be imported into India without a valid sanitary import permit. All livestock products with valid sanitary import permits may be brought into India only through seaports or airports where Animal Quarantine and Certification Services Stations are situated. These stations are located in the cities of Delhi, Mumbai, Kolkata and Chennai. When livestock products arrive at the checkpoint, they will be checked by the Officer-in-charge of the Animal Quarantine and Certification Services Station or any other veterinary officer duly approved by the Department Of Animal Husbandry and Dairying.
• Application filled along with documents sent to quarantine officer for scrutiny if all the relevant documents are attached, NOC issued before lifting the livestock from the country of origin.
• If all the relevant documents are not attached with the application then quarantine officer sends back the application to importer with reason for not granting NOC.
• As per the import guidelines/conditions of the country all the health related documents will be checked by the quarantine officer.
• If all the relevant document & guidelines/conditions are met, issue of AQC clearance certificate release with or without sampling/testing
• If all the relevant document & guidelines/conditions are not met then deportation / destruction of livestock product as per case (whichever required).
• If with sampling / testing is required then sampling is taken from the consignment for testing and AQC issued to the importer. • If the consignment is not require sampling / testing or not require quarantine clearance then • AQC issued to the importer after examination of paper and consignment.
Work Flow of Animal Quarantine Certification for Livestock Product in Case of Import:
[pic] Diagram 12: As-Is of AQC for Livestock product Import
Documents to be attached along with the application for Clearance of Livestock Products: 1) DGFT License, if any. 2) SIP, if any. 3) Testing fee if any. 4) Custom related documents. 5) Advance copy of Official Health Certificate from the Country of Origin as per the Indian Health Protocol. 6) Examination and sampling.
3 Import of Pet Animal (Dog / Cat)
• First information: the importer or his/her authorized representative should contact the animal quarantine officer in advance about the intended import consignment. • The details pertaining to the same must be physically submitted to the office of the AQCS on a prescribed format of the office along with photocopies of the following • Veterinary certificate/ Health certificate of the animal issued only by the designated veterinary officer of the exporting country confirming the health status of the animal and its fitness for the export/ travel. This certificate should be only in English (or bilingual with one language as English). • Pet passport with details of vaccination. • Copies of the passport and travel ticket of the owner of the animal.
• After satisfactory verification of the above documents, the AQCS will issue the NOC for import of the animal consignment before lifting the animal from the country of origin, which needs to be carried physically along with the animal.
• If Documents are incomplete during verification then NOC will not be issued to importer with reason. • On arrival at airport, the importer will report to the quarantine officer with the original copies of all the above listed documents for obtaining a provisional Quarantine Clearance Certificate which will be issued upon satisfactory verification of the documentation and the physical health of the animal. • On satisfactory completion of 30 days of home quarantine, the importer must contact the AQCS for final clearance of the animal from the quarantine angle. • Final quarantine health certificate issued to the importer.
Work Flow of Animal Quarantine Certification for Pet Animal (Dog / Cat) in Case of Import:
[pic]
Diagram 13: As-Is of AQC for Pet Animal Import
3 ISSUANCE OF ANIMAL QUARANTINE CERTIFICATE IN CASE OF EXPORT
This section contains the work flow that how an Exporter can get the Animal Quarantine Certificate for Livestock from AQCS.
The major objective of the Animal Quarantine and certification Station (AQCS) is to prevent the ingress of livestock and poultry exotic to India as per provisions of livestock importation Act, 1898. It is essential to obtain the appropriate clearance from this body prior to transport of pets- dogs and cats, live chicks and other livestock products through air travel or sea route.
1 export of Livestock
Health Certificate/ Export fitness Certificate on standard format or as is required by the importing country – within the jurisdiction of this office – towards facilitation of export of live animal as per the international requirements. • Application filled along with documents sent to quarantine officer for scrutiny/check all relevant documents are attached, as per the export guidelines/norms of India.
• If all the relevant documents are not attached with the application then quarantine officer sends back the application to the exporter with reason for not granting AQC health certificate communicated to the exporter.
• If all the relevant document & guidelines/norms are met, then quarantine officer will see the requirement when AQC health certificate is to be issued, after quarantine observation & testing or without quarantine observation & testing as per the protocol of importing country and exporting norms of India.
• If with quarantine observation & testing is require then o Quarantine observation done and sample taken for testing o Sample sent to lab for testing • If test report is OK then AQC health certificate issued to the exporter and if test report is not satisfactory then exporter will be informed through a letter with reason for not granting AQC health certificate • If without quarantine observation & testing is require then o After examination of the documents & health of livestock, AQC health certificate will be issued to the exporter.
Work Flow of Animal Quarantine Certification for Livestock in Case of Export:
[pic] Diagram 14: As-Is of AQC for Livestock Export
Documents to be attached along with the application for Certification of Livestock: 1) DGFT License, if any. 2) Testing fee & accommodation charges, if any. 3) Custom related documents. 4) Copy of Official Health requirement of importing Country. 5) Other applicable norms of India.
2 export of Livestock Product
This section contains the work flow that how an Exporter can get the Animal Quarantine Clearance Certificate for Livestock Product from AQCS.
• Application filled along with documents sent to quarantine officer for scrutiny/check all relevant documents are attached, as per the export guidelines/norms of India.
• If all the relevant documents are not attached with the application then quarantine officer sends back the application to the exporter with reason for not granting AQC health certificate communicated to the exporter.
• If all the relevant document & guidelines/norms are met, then quarantine officer will see the requirement when AQC health certificate is to be issued, after quarantine observation & testing or without quarantine observation & testing as per the protocol of importing country and exporting norms of India.
• If with quarantine & testing is require then o Sample taken for testing and registration done as per the protocol and exporting norms of India o Sample sent to lab for testing • If test report is OK and other records are satisfactory then AQC health certificate issued to the exporter and if test report is not satisfactory then exporter will be informed through a letter with reason for not granting AQC health certificate • If without quarantine & testing is require then o After inspection of consignment / representative samples and examination of the documents, AQC health certificate will be issued to the exporter.
Work Flow of Animal Quarantine Certification for Livestock Product in Case of Export:
[pic]
Diagram 15: As-Is of AQC for Livestock Product Export Documents to be attached along with the application for Certification of Livestock Products: 1) DGFT License, if any. 2) Testing, if any. 3) Custom related documents. 4) Copy of Official Health requirement of importing Country. 5) Other applicable norms of India.
Note: In Case of pet animal (Dog/Cat), any person can bring / carry less than or equal to two pet animals from other country into India for personal purpose in case of import/export.
3 export of Pet Animal (Dog / Cat)
• The exporter must contact the AQCS before the expected date of export with the completed application form and the following documents/information. o Health record of the animal (pet passport) with vaccination details and scrum antibody profile (if applicable) o Copy of import license and export permit ( if applicable) o Copy of health and Zoo sanitary requirements of the importing country of the requirements as mutually agreed upon. o Travel ticket and a copy of the passport of the owner of the pet. • Or as per the SIP of the importing country testing/inspection/vaccination done • If testing/inspection/vaccination report is satisfactory then • AQC health certificate will be issued to the exporter else reason for not granting AQC health certificate is communicated to the exporter.
Work Flow of Animal Quarantine Certification for Pet Animal (Dog / Cat) in Case of Export:
[pic] Diagram 16: As-Is of AQC for Pet Animal Export
As-Is of Mumbai: In case of Animal Quarantine, they are following the same process of import and export as followed by Delhi office only the different formats are being used by them to issue AQC.
Formats from Mumbai are attached in the Annexure number- 14, 15, 6,17,19,20,21,22,36
As-Is of Bangalore: There is no Animal quarantine office in Bangalore, they directed to Chennai office for any kind of information related to animal quarantine.
As-Is of Madhya Pradesh: HSADL lab, Bhopal is Animal quarantine test lab; they are using their own software to generate lab test reports for AQCS and importer. Test reports are being sending to AQCS/importer via email/hard copy. Our scope is identifying if any linkage can be developed to see HSADL lab test report if required by AQCS, which can be done only when they are using any application.
Customs Department: Central Board of Excise and Customs (CBEC) is a part of the Department of Revenue under the Ministry of Finance, Government of India. It gives the custom clearance for import/export of livestock/ livestock product/plant/plant material.
MPEDA: The Marine Products Export Development Authority (MPEDA) was constituted in 1972 under the Marine Products Export Development Authority Act 1972 (No.13 of 1972). The role envisaged for the MPEDA under the statute is comprehensive - covering fisheries of all kinds, increasing exports, specifying standards, processing, marketing, extension and training in various aspects of the industry. MPEDA functions under the Ministry of Commerce, Government of India and acts as a coordinating agency with different Central and State Government establishments engaged in fishery production and allied activities. They shared these two websites: www.MPEDA.com , www.empeda.nic.in
DGFT: Directorate General of Foreign Trade is a government organization in India responsible for the formulation of Exim guidelines and principles for Indian importers and Indian exporters of the country. Before 1991, DGFT was known as the Chief Controller of Imports & Exports (CCI&E).
Some of the major functions of DGFT and its regional offices through out the country are as follows:
• To implement the Exim Policy or Foreign Trade Policy of India by introducing various schemes and guidelines through its network of DGFT regional offices thought-out the country. DGFT perform its functions in coordination with state governments and all the other departments of Ministry of Commerce and Industry, Government of India.
• To Grant Exporter Importer Code Number (IEC) to Indian Exporter and Importers. IEC Number is a unique 10 digit code required by the traders or manufacturers for the purpose of import and export in India. DGFT IEC Codes are mandatory for carrying out import export trade operations and enable companies to acquire benefits on their imports/exports, Indian customs, export promotion council’s etc in India.
• DGFT permits or regulate Transit of Goods from India or to countries adjacent to India in accordance with the bilateral treaties between India and other countries.
• To promote trade with neighboring countries.
• To grant the permission of free export in Export Policy Schedule 2.
• DGFT also play an important role in controlling DEPB Rates.
• Setting standard input-output norms is also controlled by the DGFT.
• Any changes or formulation or addition of new codes in ITC-HS Codes are also carried out by DGFT (Directorate General of Foreign Trade).
FSSAI: Issues the food safety license to importer as per the standard mention on their website, without the license any importer will not be able to apply for SIP.
NPQS & FSSAI both require search option/ web service to verify the certificate issued by them.
AQCS: This body regulates the export of Livestock & Livestock products from Animal Quarantine facilities. It is essential to obtain the appropriate permits from this body prior to transport of pets- dogs and cats, live chicks and other livestock products through air travel.
FPI: The Ministry of Food Processing Industries, set up in July 1988, is the main central agency of the Government responsible for developing a strong and vibrant food processing sector.
The functions of the Ministry can be broadly classified under policy support and development activities:
a) Formulation and implementation of policies for food processing sector with overall national priorities and objectives.
b) Facilitating creation of conducive environment for healthy growth of the food-processing sector.
c) Promoting rationalization of tariffs and duties relating to food processing sector.
DADF: Department of Animal Husbandry Dairying & Fisheries (DADF) is responsible for matters relating to livestock production, preservation, protection and improvement of stocks, dairy development. The main focus of the department is on: a) Preservation & Protection of livestock through provision of health care. b) Strengthening of central livestock farms (Cattle, Sheep and Poultry). c) Expansion of aquaculture in fresh, brackish water, welfare of fisher folk, etc.
According to the TO-BE process all the stakeholders will be integrated through search option & custom will be integrated by web services/ftp. The URL of all the stake holders will be in related link option on AQIS webpage to directly access.
2 PLANT QUARANTINE CERTIFICATION PROCEDURES
1. Plant/Plant material application PQIS is fully operational and have been issued approximately 2 lacs PSC through the PQIS application (e-certification) till date, its web site is http://plantquarantineindia.nic.in .
Specific Variations in Processes & Formats :
As-Is of Mumbai: They are using PQIS application in Plant Quarantine office. Formats from Mumbai are attached in the Annexure number- 6, 7, 8,9,10,11,12,13
National Plant Quarantine Service: NPQS is also using the PQIS application & requires integration of their running application with custom to share BOE (Bill of Entry) to verify all the import items.
As-Is of Bangalore: PQIS application is being used in plant quarantine office Bangalore.
Referred these two websites. 1. http://plantquarantineindia.org/ 2. http://plantquarantineindia.nic.in/PQISMain/Default.aspx
In PSC issuing authority office, manual process is being followed for issuances of phyto sanitary certificate. As-Is Cochin:
Common Concern None of the department was informed about the NeGP project. 2. There are few stakeholders of PQIS from where the inputs have been taken during the requirements gathering for integration of PQIS application with the stakeholders. The stakeholders, their functions and how the PQIS can be linked/integrated to its stakeholders are studied, are given below:
.
APEDA: Main function is to do the registration of exporter for which they issued RCMC number to them. This is valid for 5years.
They do testing for rice & grapes as per importing country requirements, because without testing certificate issued by APEDA exporter can not export the goods to other country. Apart from grapes & rice they issue the certificate for peanut, pomegranate, ground nut & for plant product.
The entire certificate issued by them through online application except meat plant certificate which is being issued manually. The certificate (RCAC) issued by them is valid for 3 months.
NPQS require search option/ web service on APEDA application to verify RCMC & RCAC certificates issued by them. RCAC format is attached in the annexure- 33
EIC: Issues health certificate for following six products basmati rice, fish, honey, milk products, poultry meat & egg products for Europe, Russia, Vietnam and Bangladesh as per government mandate. Exporter should attach the EIC health certificate issued by EIC with PSC before exporting his goods to other country.
NPQS require search option/ web service to verify certificate data issued by EIC.
ARBRO pharmaceuticals: is testing laboratory, which does testing & enters test report data on APEDA application.
Similarly, through APEDA search option we can authenticate the certificate issued by laboratory. Coconut Development Board
They provided the website:
1. http://www.coconutboard.nic.in
Cashew-nut and Cocoa Development
They provided the website:
1. http://www.dccd.gov.in all info available here.
Cashew Export Promotion Council
They provided the website: http://cashewindia.org Pesticide Residue Lab (Ultra Lab Bangalore): This Ultra lab does Pesticide Residue Analysis of different agriculture commodities
PSC issuing Authority:- PSC issuing authority is part of PQS department. They are authorized by the department to issue the PSC certificate on their behalf.
PQS: Directorate of Plant Protection, Quarantine & Storage, Department of Agriculture & Cooperation has recently got developed a web portal http://plantquarantineindia.nic.in for on-line registration of Exporters and Importers of agricultural commodities seeking the following services:-
• Issuance of Import Permit • Issuance of Import Release Order • Issuance of Phytosanitary Certificate
NBPGR: The National Bureau of Plant Genetic Resources has its Headquarters at New Delhi Objectives of NBPGR • To plan, organize, conduct and coordinate exploration and collection of indigenous and exotic plant genetic resources. • To undertake introduction, exchange and quarantine of plant genetic resources. To characterize, evaluate, document and conserve crop genetic resources and promote their use, in collaboration with other national organizations. • To develop information network on plant genetic resources. • To conduct research, undertake teaching and training, develop guidelines and create public awareness on plant genetic resources.
DMI: The Directorate of marketing and inspection implements the agricultural marketing programs of the Union Government under the supervision and control of Union Ministry of Agriculture. It aims at bringing integrated development of marketing of agricultural and allied produce in the country. It is headed by Agricultural Marketing Adviser to the Government of India (AMA). It maintains a close liaison between Central and State Governments through its Branch Head office at Nagpur, 11 Regional Offices and 37 sub-offices spread all over the country. It has a network of 22 Regional Agmark Laboratories with Central Agmark Laboratory at Nagpur as apex laboratory.
DPPQS: Director The Directorate of Plant Protection, Quarantine & Storage established under Department of Agriculture & Co-operation of Ministry of Agriculture, Government of India.
The ongoing activities assigned under the scheme include: • To issue import permits (IP) with additional declarations and special conditions to facilitate safe imports of agricultural products. • To undertake quarantine inspection and laboratory testing of plants and plant material to ensure freedom from exotic pests. • To undertake phytosanitary certification (for issuance of Phytosanitary Certificates (PSCs); 150 Nos. of Officers from Central/ State/ UT Governments have been authorized for this purpose. • To undertake fumigation/disinfestations/disinfections of commodities to control infestation/infection. • To undertake certification of post-entry quarantine facilities and inspection of imported growing plants and plant material; 41 Nos. of Inspection Authorities have been designated. • To support Export market access for India’s Agriculture products from the phytosanitary point of view. • To facilitate safe global trade in agriculture by assisting the producers and exporters by providing a technically competent and reliable phytosanitary certificate system to meet the requirements of trading partners. • To provide Grants-in-aid to Designated Inspection Authorities to meet the travel expenses and also to State PSC issuing authorities for equipping them with minimal equipments required for export inspection/certification. • Granting approval/accreditation of Treatment providers in line with the requirement of ISPM-15 As-Is of Himanchal Pradesh: Steps to be followed for the Import of planting material in Himanchal Pradesh
As per guidelines of the new Policy on seed development, 1988, Government of India, Ministry of Agriculture, Department of Agriculture & Cooperation, the certain categories are eligible to import the seeds and planting materials including Department of Horticulture of the state Governments/ Growers of vegetable & flowers and the same should be got registered with the Director of Horticulture of the state Government. All imports of seeds and plant material will require a permit granted by the Plant Protection Advisor to the Government of India, which will be issued within the minimum possible time frame. All import of seeds and planting materials, etc. will be allowed freely subject to EXIM Policy guidelines and the requirements of the Plants, Fruits and Seeds (Regulation of import into India) Order, 1989 as amended from time to time.
I. Registration with the Department of Horticulture, Himanchal Pradesh as Importer. The following procedure is followed by the importer for registration with the department of Horticulture for the import of planting material: • Submission of the Application form along with o Revenue record of the possession of land (Titima/ Jacaranda/ Lease Deed minimum 10 year) o Copy of invoice/ reservation of plant material/ confirmation letter from the nursery from which the farmer is interested to import the plant material.
[pic] Diagram 17: As-Is of Himanchal Pradesh in case of Import
APPLICATION FOR REGISTRATION UNDER PARA 4.4.4 OF THE NEW POLICY ON SEED DEVELOPMENT OF
GOVERNMENT OF INDIA
1. Name of the Grower : 2. Complete Postal Address: 3. Details of the Land Holding: (Documentary evidence in support of the same has to be produced). 4. Details of the Fruit Crops Grown in the last three years:
|S.No |crop |year – 1 |year – 2 |year - 3 |
|1 | | | | |
|2 | | | | |
|3 | | | | |
5. Details of Flowers/Ornamental Plants grown during the last three years:
|S.No |crop |year – 1 |year – 2 |year - 3 |
|1 | | | | |
|2 | | | | |
|3 | | | | |
6. Details of the values of fruits and flowers sold in the last three years : Value (In Rupees)
|items |year – 1 |year – 2 |year – 3 |
|(a) Fruits | | | |
|1. | | | |
|2. | | | |
|3. | | | |
|Flowers | | | |
|1. | | | |
|2. | | | |
|3. | | | |
7. Details of the Planting Material imports if any handled earlier :
8. Particulars of the Imports Planned Now :
|country |farm/company/nursery |crop |name of variety |quantity |
| | | | | |
|Total : | | | | |
9. Details of the PEQ Facilities Proposed to be established/already available
I hereby certify that all the above particulars are true, correct and complete.
Signature of the Importer/Applicant
Date:
Place:
According to the TO-BE process all the stakeholders will be integrated through search option & custom will be integrated by web services/ftp. The URL of all the stake holders will be in related link option on PQIS webpage to directly access.
3 PRODUCT FUNCTIONS( TO BE WORK FLOW)
1 THERE WOULD BE THREE MODULE OF THE ANIMAL QUARANTINE CLEARANCE APPLICATION
1) Issuance of Sanitary Import Permit 2) Issuance of Animal Quarantine Certificate (AQC) for LS/LSP/Pet Animal in case of Import. 3) Issuance of Animal Quarantine Certificate (AQC) for LS/LSP/ Pet Animal in case of Export.
These three modules can further be divided into: 1. Issuance of Sanitary import permit (being issued from DADF) a. Issuance of SIP: Case 1 (Meeting Case) b. Issuance of SIP: Case 2 (Fast Track Case) c. Issuance of SIP: Case 3 (On-file Case) 2. Issuance/Rejection of Animal Quarantine Certificate in case of Import for a. Livestock b. Livestock Product c. Pet Animal (Dog/Cat) 3. Issuance/Rejection of Animal Quarantine Certificate in case of Export for a. Livestock b. Livestock Product c. Pet Animal (Dog/Cat)
1 ISSUANCE OF SIP
1 Issuance of SIP (Case 1: Meeting Case)
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select SIP from the available links • Application (Form A or Form B) will be filled and submitted along with required documents online. The application will be available in the inbox of section officer. • The section officer will receive the form (In original) along with the required documents (hard copy). Scrutiny of the form with all the documents will be done by the section officer and forwarded to AC trade for verification. • If all the relevant documents are not attached with the application then section officer will make the application deficient and the application moves to the importer inbox. Importer will receive the form and can edit and re-submit the form. • AC trade verifies all the documents, prepares agenda and sent it to the various divisions for comments. • If the application is for Dairy Product then the application will go to Dairy division and LH Division • If the application is for Meat feather, GP stock then the application will to LH division. • If the application is for fishing items then the application will go to FY division. • Each department process the application
Dairy division 1) Assistant commissioner receives the application from the trade division and prepares the comments. 2) Forward to DDG for approval of Comments. 3) DDG may forward the application to AC for either modify the comments or approves the comments. 4) AC (Dairy) will forward to AC (Trade) after the approval from DDG.
• LH division 1) Application received from trade division by asst. commissioner. 2) Comments prepared by asst. Commissioner. 3) Forwards to JS for approval of Comments 4) JS may forward the application to AC for either modify the comments or approves the comments. 5) AC (LH) will forward to AC (Trade) after the approval from JS.
• FY division • Application received from trade division by fishery research officer • Comments prepared by fishery research officer. Forwards to JS for approval of Comments JS may forward the application to AC for either modify the comments or approves the comments. • AC (LH) will forward to AC (Trade) after the approval from JS. • After receiving comments from all the divisions, AC trade puts agenda in a meeting with JS trade. • If JS trade approves the agenda then application sends back to AC trade for signature and issuance of SIP importer, SIP issued to importer. • If JS Trade not approved the agenda/comments on SIP then letter issued to importer with reason for not issuing the SIP.
[pic]
Diagram 18: To-Be of SIP (Case 1: Meeting Case)
2 Issuance of SIP Process (Case 2: Fast Track)
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select SIP from the available links • Application (Form A or Form B) will be filled and submitted along with required documents online. • Section officer will receive the form along with the required documents. Scrutiny of the form with all the documents will be done by the section officer and forwarded to AC trade for verification. • If all the relevant documents are not attached with the application then section officer sends back the application to the importer. Importer will receive the form and can edit and re-submit • AC Trade verifies all the documents & sends it to Director Trade for approval. • If Director Trade approves then approved application sends back to AC Trade for signature. AC forwards the application to SO/DPC to issue the certificate. • SIP issued to importer. • If Director Trade not approved the application/document then letter issued to importer with reason for not issuing the SIP.
[pic] Diagram 19: To-Be of SIP Process (Case 2: Fast Track)
3 Issuance of SIP Process (Case 3: On-file)
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select SIP from the available links • Application (Form A or Form B) will be filled and submitted along with required documents online. The application will be available in the inbox of section officer. • The section officer will receive the form (In original) along with the required documents (hard copy). Scrutiny of the form with all the documents will be done by the section officer and forwarded to AC trade for verification. • If all the relevant documents are not attached with the application then section officer will make the application deficient and the application moves to the importer inbox. Importer will receive the form and can edit and re-submit the form. • AC trade verifies all the documents, prepares agenda and sent it to the various divisions for comments. • If the application is for Dairy Product then the application will go to Dairy division and LH Division • If the application is for Meat feather, GP stock then the application will to LH division. • If the application is for fishing items then the application will go to FY division. • Each department process the application
Dairy division 1) Assistant commissioner receives the application from the trade division and prepares the comments. 2) Forward to DDG for approval of Comments. 3) DDG may forward the application to AC for either modify the comments or approves the comments. 4) AC (Dairy) will forward to AC (Trade) after the approval from DDG.
LH division 5) Application received from trade division by asst. commissioner. 6) Comments prepared by asst. Commissioner. 7) Forwards to JS for approval of Comments 8) JS may forward the application to AC for either modify the comments or approves the comments. 9) AC (LH) will forward to AC (Trade) after the approval from JS.
FY division • Application received from trade division by fishery research officer • Comments prepared by fishery research officer. Forwards to JS for approval of Comments JS may forward the application to AC for either modify the comments or approves the comments. • AC (LH) will forward to Director (Trade) after the approval from JS. • After receiving comments from all the divisions, Director Trade either approves or rejects the application. • If Director Trade approves, then application sends back to AC trade for signature and issuance of SIP to importer, SIP issued to importer. • If Director Trade not approved the application then letter issued to importer with reason for not issuing the SIP
[pic] Diagram 20:To-Be of SIP (Case 3: On-file)
Common Process Flow for AQIS & PQIS:
There are few common steps for users who want to use AQIS or PQIS application: • User will type CAP URL on browser to come on the home page of CAP • User will select/click links (AQIS/PQIS) available • User will fill and submit the application for user id and password • Verification of I/E code will be done by the system administrator of the respective applications • Login id will be enabled after verification of I/E code • Now user will login AQIS/PQIS respectively
[pic] Diagram 21: Common Process Flow for AQIS & PQIS
Note: In case of Livestock, importer will directly apply for animal quarantine certificate at AQCS with license from DGFT
2 ANIMAL QUARANTINE CERTIFICATION PROCEDURE
1 Import of Livestock
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select LS from the available links LS/ pet animal • Importer will submit application for NOC for lifting LS along with the relevant documents • A unique reference number will be issued to importer • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then NOC issued to importer and an SMS sent to importer for issuance of NOC • If application along with the documents attached is not satisfactory then importer informed with reason for not granting NOC through e-mail and an SMS sent to importer for rejection of NOC • After arrival, importer will submit application for Provisional AQC along with the relevant documents(BOE) • Verification of NOC along with the documents attached is done by the quarantine officer • Sample taken and sent to lab for testing if required • Provisional quarantine certificate issued • Payment (online/Cheque/dd/cash) made by the importer for observation/testing as per prevailing norms in case of LS. • Payment information received by quarantine officer • On receiving the sample and completing the test, lab incharge entered the report and sends to Quarantine officer. • If lab report is OK. Then quarantine certificate is issued and a copy of AQC sent to importer via-email and SMS sent to importer for issuance of final AQC. If lab report is not satisfactory deportation order is issued. • SMS sent to importer for deportation.
[pic] Diagram 22: To-Be of AQC for Livestock Import
2 Import of Livestock Product
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQCS application • Importer will submit application for Provisional AQC along with the relevant documents • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then NOC issued to importer for custom clearance and an SMS sent to importer for issuance of NOC • If application along with the documents attached is not satisfactory then importer informed with reason for not granting NOC through e-mail and an SMS sent to importer for rejection of NOC • Sample taken and sent to lab for testing if required • Provisional quarantine certificate issued • Payment (online/Cheque/dd/cash) made by the importer for testing as per prevailing norms in case of LS if required. • Payment information received by quarantine officer • On receiving the sample and completing the test, lab incharge entered the report and sends to Quarantine officer. • If lab report is OK. Then quarantine certificate is issued and a copy of AQC sent to importer via-email and SMS sent to importer for issuance of final AQC. If lab report is not satisfactory destruction order is issued. • SMS sent to importer for destruction.
[pic] Diagram 23: To-Be of Livestock product Import
3 Import of Pet Animal (Dog/Cat)
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select Pet Animal from the available links LS/ pet animal • Importer will submit application for NOC along with the relevant documents • A unique reference number will be issued to importer • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then NOC issued to importer and an SMS sent to importer for issuance of NOC • If application along with the documents attached is not satisfactory then importer informed with reason for not granting NOC through e-mail and an SMS sent to importer for rejection of NOC • Importer will submit application for Provisional AQC along with the relevant documents • Verification of NOC along with the documents attached is done by the quarantine officer • Sample taken and send to lab if required • Provisional quarantine certificate issued • Payment (online/Cheque/dd/cash) made by the importer for testing/ Vaccination as per prevailing norms in case of LS if required. • Payment information received by quarantine officer • On receiving the sample and completing the test, lab incharge entered the report and sends to Quarantine officer. • Final quarantine certificate issued after 30 days of provisional quarantine certificate issued, a copy of AQC sent to importer via-email and SMS sent to importer for issuance of final AQC
[pic] • Diagram 24: To-Be of Pet Animal Import
3 ANIMAL QUARANTINE CERTIFICATION PROCEDURE
1 Export of Livestock
• Exporter will type CAP URL on browser to come on the home page of CAP • Exporter will select/click AQIS from the available links • Exporter will login into the AQIS application • Exporter will select LS from the available links LS/ Pet Animal • Exporter will submit application for AQC along with the relevant documents • A unique reference number will be issued to Exporter • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then with or without quarantine testing requirement checked • If LS not required any quarantine testing then AQC health certificate issued and a copy of AQC health certificate sent to exporter via e-mail • If LS is required quarantine testing then sample taken and sent to lab for testing • Exporter will receive information through system for making payment for testing • Payment (online/Cheque/dd/cash) made by the exporter for testing • Lab receives sample for testing • Quarantine officer receives lab report • If lab report is satisfactory then AQC health certificate issued and alert is issued If lab report is not satisfactory then export will receive an SMS for rejection of AQC • If lab report is satisfactory then Exporter submits request for custom clearance • LS released based on AQC • Exporter can print or download the AQC.
[pic] Diagram25: To-Be of AQC for Livestock Export
2 Export of Livestock Product
• Exporter will type CAP URL on browser to come on the home page of CAP • Exporter will select/click AQIS from the available links • Exporter will login into the AQIS application • Exporter will select LSP from the available links LS/ LSP • Exporter will submit application for AQC along with the relevant documents • A unique reference number will be issued to Exporter • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then with or without quarantine testing requirement checked • If LSP not required any quarantine testing then inspection of consignment and representative sample checked and AQC issued • If LSP is required quarantine testing then sample taken and sent to lab for testing • Exporter will receive information through system for making payment for testing • Payment (online/Cheque/dd/cash) made by the exporter for testing • Information of receiving payment to exporter will be sent through SMS as well as e-mail • Lab receives sample for testing • Quarantine officer receives lab report • If lab report is satisfactory then AQC issued and a copy of AQC sent to exporter via e-mail • If lab report is not satisfactory then export will receive an SMS for rejection of AQC • If lab report is satisfactory then Exporter submits request for custom clearance • LSP released based on AQC • Exporter can print or download the AQC.
[pic] Diagram 26: To-Be of AQC for Livestock Product Export
3 export of Pet Animal (Dog/Cat)
• Exporter will type CAP URL on browser to come on the home page of CAP • Exporter will select/click AQIS from the available links • Exporter will login into the AQIS application • Exporter will select Pet Animal from the available links LS/ Pet Animal • Exporter will submit application for AQC along with the relevant documents • A unique reference number will be issued to Exporter • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then lab testing or vaccination requirement checked • If LS not required any lab testing then vaccination done and AQC health certificate issued and a copy of AQC health certificate sent to exporter via e-mail • If LS is required quarantine testing then sample taken and sent to lab for testing • Exporter will receive information through system for making payment for testing • Payment (online/Cheque/dd/cash) made by the exporter for testing • Information of receiving payment to exporter will be sent through SMS as well as e-mail • Lab receives sample for testing • Quarantine officer receives lab report • If lab report is satisfactory then AQC health certificate issued and a copy of AQC health certificate sent to exporter via e-mail • If lab report is not satisfactory then export will receive an SMS for rejection of AQC • If lab report is satisfactory then Exporter submits request for custom clearance • LS(Pet Animal) released based on AQC • Exporter can print or download the AQC health certificate
[pic] Diagram 27: To-Be for Export of Pet Animal
2 PLANT QUARANTINE CERTIFICATION PROCEDURE
1 IMPORT CERTIFICATION: (Already Implemented)
Importer will type URL on browser to get into the CAP home page; once the importer reached on the CAP home page he/she will have option to select/click from the available links PQIS & AQIS. Importer will select PQIS from the available links then he/she will be on PQIS home page.
Import Permit (IP) • Importer will log into the PQIS application, he/she will fill and submit the application • Scrutiny will be done by the Scrutiny officer • If all the relevant documents are attached then Workflow for approval process starts. • If all the documents are not attached then Scrutiny officer will deficient/Reject the application • Message sent to importer for rejection of IP • Payment (online/Cheque/dd/cash) made by the importer • Information of Issuance of IP will be sent through email.
Import Release Order (IRO) • Application for IRO filled and submitted by the Importer for issuance of IRO • Scrutiny of the application/documents done by the Scrutiny officer • If all the relevant documents are attached then Workflow for approval process starts. • If all the documents are not attached then Scrutiny officer will reject the application • Payment (online/Cheque/dd/cash) made by the importer • Duty officer assign inspector for inspection • Inspection done and report submitted to the duty officer • If inspection report is OK • If testing required then sample taken and sent to lab for testing • If test report is OK then IRO issued and a copy of IRO sent to importer • IRO issued to the importer • If test report is not satisfactory then application rejected for IRO and importer informed with reason. • Email sent to importer for rejection of IRO. • Customs Informs in advance for PQ clearance
Customs Integration with PQIS:
• Structure of Message to be exchanged: Annexure – 4.41 enclosed • Process of Message Exchange:
o Customs will provide Id & password to PQS to access the Ice-Gate for accessing the message on import on daily basis.
o This will be used in generating MIS report only for import.
• Development is under progress.
[pic] Diagram 28: To-Be of PQIS Import Certification
2 EXPORT CERTIFICATION
Importer will type URL on browser to get into the CAP home page; once the importer reached on the CAP home page he/she will have option to select/click from the available links PQIS & AQIS. Importer will select PQIS from the available links then he/she will be on PQIS home page. • Exporter will log into the PQIS application, he/she will fill and submit the application • Scrutiny will be done by the Scrutiny officer • If all the relevant documents are attached then Workflow for approval process starts • A message through e-mail sent to exporter for making payment for Issuance of PSC • If all the documents are not attached then Scrutiny officer will reject the application • Payment (online/Cheque/dd/cash) made by the exporter. • Duty officer assign inspector for inspection • Inspection done and report submitted to the duty officer • If inspection report is not satisfactory then testing or treatment require • If testing required then sample taken and sent to lab for testing • If inspection report is OK • PSC issued to the exporter • If test report is not satisfactory then application rejected for PSC and exporter informed with reason. • Email sent to exporter for rejection of PSC
[pic] Diagram 29: To-Be of PQIS Export Certification
3 THERE ARE VARIOUS FUNCTIONALITIES IN THESE MODULE, COMMON FUNCTIONALITIES ARE GIVEN BELOW:
1. User & Role management 2. Registration of Importer/Exporter 3. E-payment 4. Scrutiny/Checking/verification of documents 5. Approval of documents by authorized person 6. Status tracking 7. Sending sample to Lab for testing 8. Receiving test report from Lab 9. Issuance of certificate(s) • SIP issued to Importer • In case of Animal Quarantine for Import of Livestock and Pet Animal, three certificates issued to Importer (NOC for lifting, Provisional Certificate and Final Quarantine Clearance Certificate) • In case of Animal Quarantine for Import of Livestock Product, two certificates issued to Exporter (NOC / Final Quarantine Clearance Certificate) 10. Grievance Redressal 11. SMS Management 12. E-mail management 13. Printing.
4 USER CHARACTERISTICS
Application will be part of CAP primarily used by the Exporters, Importers, PSC Issuing Authorities, Duty Officer/ Inspection Authority and Administrator from NIC. Apart from these users, some of the reports can be viewed by other Central Line Ministries/Departments and also the common man for the purpose of social audit.
|User |Characteristics |
|Exporter |Computer Savvy |
| |Well versed with internet |
|Importer |Computer Savvy |
| |Well versed with internet |
|PSC Issuing Authority |Computer Savvy |
| |Well versed with internet |
|Duty Officer |Computer Savvy |
|/Inspection Authority |Well versed with internet |
|NIC Admin. |Computer Savvy |
| |Well versed with internet |
|General User |Computer Savvy |
| |Well versed with internet |
5 CONSTRAINTS
• This will be an internet based application which will be designed, developed and centrally hosted in NIC’s Data Centre. • The users will be accessing the software application using various connectivity scenarios. • Database on Phyto-sanitary conditions for Import of Livestock & Livestock Product and mapping of HS code need to be authenticated & updated by DADF. • Providing access of PSC to NPPO of other countries, it is only possible when all other countries are agreed • Translating the phyto sanitary condition of foreign country language into English using Google translator not possible because it will change the meaning of the document.
6 ASSUMPTIONS AND DEPENDENCIES
• Master Data preparation and entry into AQIS application by DADF • Network infrastructure and development tools are available for development team for testing, implementation & integration as per schedule. • Changes, if any should be reported within the stipulated time frame for incorporation in the SRS. Any changes not in the approved SRS will be treated as change request, with financial implications. • NIC should allow extension of project schedule and enhancement of project cost, in case requirements are changed at a later stage in the project.
SPECIFIC REQUIREMENTS
1 SOFTWARE PRODUCT FEATURES
The functional requirement of the proposed PQIS/AQIS is describe below in term of use case. A use case may be defined as a particular activity that an actor can perform. An actor is a user with a specific role. The following table gives a brief description of each use case field in the use case that follow.
3.1.1 ACTORS
1 SUPER ADMIN
A user who has been assigned the Super Admin type has access to the Super Admin Area for all activities installed on the website and to the tools used to configure these activities. A super admin in this case can be a nominated person by NIC. (Further information regarding the selection of a supper admin can also be decided on the basis of the input received during the field visit).
2 ADMIN
A sysop (an abbreviation of system operator) is an administrator of a multi-user computer system, such as an online service virtual community. It may also be used to refer to administrators of other Internet-based network services. In respect to this portal a system admin will be a person who will be authorized to perform the activities related with updating the site information, authenticating various users by administrating the registration and acknowledgement of registration.
3 APPROVER
A person who approves the application/roles /rights other actors AQIS User /SIP User/ General Users AQIS User /SIP User/ General Users those who will be using the portal for various agro met advisory related services. Nodal Officer for Grievance Redressal
4 EXPORTER
A person who will make his user id on AQIS web portal and applied for E-certification
5 IMPORTER
A person who will make his user id on AQIS web portal and applied for E-certification
2 COMMON USE CASES
This sub-section describes the use cases, which would be available to the actor belonging to any role. Refer to diagram-30 for a diagrammatic representation of the relationships between actor and among different use cases. The set of common use cases are:
• Log in • Logout • Change Password • Forget Password • Forget User ID • Attach Documents • Drop Documents • Auto Trigger • Manual Trigger
Each of these use cases is described below in more detail
|S.No. |Actor |Responsibility |
|1. |AQIS/SIP User |Login/Logout/Change password/Forget password/ Forget user id |
[pic]
Diagram 30: Common Use Cases
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.1.2.1 |Log In |This use case is used to Log In to AQIS|AQIS/SIP Users |
|UC 3.1.2.2 |Log Out |This use case would allow the actor to |AQIS/SIP Users |
| | |logout of AQIS Application to which he/| |
| | |she is already logged in. | |
|UC 3.1.2.3 |Change Password |This use case is used to change the |AQIS/SIP Users |
| | |existing password for AQIS User. | |
|UC 3.1.2.4 |Forget User ID |This use case is used for Forget User |AQIS/SIP Users |
| | |Id. | |
|UC 3.1.2.5 |Forget Password |This use case is used for Forget |AQIS/SIP Users |
| | |Password. | |
|UC 3.1.2.6 |Attach Documents |A person/agency that is uploading any |AQIS/SIP Users |
| | |document on the system. | |
|UC 3.1.2.7 |Drop Attachment |This use case allows the actor to |AQIS/SIP Users |
| | |delete or drop a file attachment that | |
| | |is associated with an item. | |
|UC 3.1.2.8 |Auto Trigger |This use case is for alert system |System Users of AQIS/SIP |
|UC 3.1.2.9 |Manual Trigger |This use case is for alert system |All System Users of AQIS/SIP |
| | |which should be functioning when manual| |
| | |commands are given | |
1 LOG IN
|UC 3.1.2.1 |Log In |
|Version: |00 |
|Context: |This use case is used to Log In to AQIS |
|Priority: |High |
|Frequency: |As and when actor want to login into AQIS application .AQIS (Internal & External) users enter his/her user-id|
| |and password to access the application. |
|Primary Actor: | AQIS/SIP Users |
|Preconditions: |User shall click on the link available on CAP. |
| |Select the application AQIS. |
|Basic Flow |1. System presents the actor an interface to enter user name and password: |
| |2. Actor shall enter user id and password. |
| |3. Actor instruct to Log In into system. |
| |4. On Successful login User shall reach at Home page of AQIS. |
|Alternative Flow: |Invalid User ID or Password: If actor enters wrong user id or password then system will display “Invalid |
| |Login”. Actor shall acknowledge the message. System will return back to Pre Condition. |
| |Actor is already login: If Actor chooses to invoke multiple instances. System will display a message “Already|
| |Log In”. |
| |Actor attempt to login with wrong User id and Password at least 3 times: System will display the message |
| |“Your Account is temporary blocked”. |
| |Actor Clicks on reset link: System will clear the user id and password. |
| |Actor can directly visit the application. Of PQIS/AQIS by typing URL on browser. |
|Post Condition: |Actor shall successfully login into system. |
| |Actor will access the information from AQIS as per defined role. |
|Special Requirements: |Form field shall be verified from both client and server end. |
|Unresolved Issues: | |
2 LOG OUT
|UC 3.1.2.2 |Log Out |
|Version: |00 |
|Context: |This use case would allow the actor to logout of AQIS Application to which he/ she is already logged in. |
|Priority: |High |
|Frequency: |As and when user Log In into AQIS |
|Primary Actor: |AQIS/SIP Users |
|Preconditions: |Actor is logged into AQIS application over the web. |
|Basic Flow |1. Actor shall click on the logout link. |
| |2. System will display a message “You have successfully logout.” |
| |3. System will return back to Home Page. |
|Alternative Flow: |1. Actor chooses to Close the browser window : |
| |a. System displays the message, “The currently logged in user was logged out. Thanks for using AQIS package. |
| |b. The System would close the AQIS package. |
| |2. If the actor is already logged in into AQIS package and System times out the actor: The system logs out |
| |the actor whenever the actor tries to click any option. The System returns back to the Home page. |
|Post Condition: |1. Actor shall successfully logout and brought to the Home Page. |
|Special Requirements: | |
|Unresolved Issues: | |
3 CHANGE PASSWORD
|UC 3.1.2.3 |Change Password |
|Version: |00 |
|Context: |This use case is used for existing password for AQIS |
|Priority: |High |
|Frequency: |As and when actor wants to change his/ her password. |
|Primary Actor: |AQIS/SIP Users |
|Preconditions: |Actor shall login in to AQIS using UC 3.1.2.1. |
|Basic Flow |1. Actor shall instruct the system to change password. |
| |2. Actor shall enter the old password. |
| |3. Actor shall enter the new password and again enter the confirmed new password. |
| |4. Actor shall instruct to change password. |
| |5. System will display a message “Your Password has been modified.” |
| |6. System will return back to Home Page. |
|Alternative Flow: |1. The actor attempts to save the changed password without specifying the Old Password: |
| |The System would respond with a message, “Please enter a password for the user”. |
| | |
| |2. The actor attempts to save the changed password without specifying the New Password: |
| |The System would respond with a message, “Please enter a confirmation password for the user”. |
| | |
| |3. The actor attempts to save the changed password without specifying the Confirm Password: |
| |The System would respond with a message, “Please enter a confirmation password for the user”. |
| | |
| |4. The length of the new password is less than 8 characters: |
| |The system would respond with the message, “The length of the password should be greater than 8 characters”. |
| |The length of the new password is greater than 12 characters. |
| |The System would respond with the message, “The length of the password cannot be greater than 12 characters”.|
| | |
| |5. The New Password is same as Old Password: |
| |The System would respond with the message, “The new password you have entered is same as old password. Please|
| |enter a different value for new password”. |
| |The New Password is same as Previous old Password |
| |The System would respond with a message, “New Password cannot be same as previous old password”. |
| | |
| |6. Confirm Password is different from New Password: |
| |The System would respond with the message, “Confirm Password should be same as New Password”. |
| |7. The New Password is not a Strong Password: |
| |The System would respond with a message, “Please correct the problem (s) with your new password. Strong |
| |Passwords must include at-least one number and special character.” |
|Post Condition: |1. Actor shall successfully logout and brought to the Home Page. |
|Special Requirements: | |
|Business Rules |1. The length of the new password should be greater than 8 and less than 12 characters. |
| |2. Old Password, New Password and Confirm Password fields are Mandatory. |
| |3. Confirm Password should be same as New Password. |
| |4. The New Password should include at-least one number and one special character. |
| |5. The New Password should not be same as the Old Password & Previous Old Password. |
|Unresolved Issues: | |
4 FORGET PASSWORD
|UC 3.1.2.4 |Forget Password |
|Version: |00 |
|Context: |This use case is used for Forget Password of AQIS. |
|Priority: |High |
|Frequency: |As and when actor forget his password of AQIS application. |
|Primary Actor: |AQCS/SIP Users |
|Preconditions: |User has clicked on the link available at AQIS for Forget Password. |
|Basic Flow |1. System presents the actor an interface to enter user name and email id: |
| |2. Actor shall enter user id and email id. |
| |3. System will send the new password at registered email id of user. |
| |Use Case Ends. |
|Alternative Flow: | 1. Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before search details. And if found then |
| |display the alert messages corresponding to related field. |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |Actor shall successfully get the password. |
|Special Requirements: |Form field shall be verified from both client and server end. |
|Unresolved Issues: | |
5 FORGET USER ID
|UC 3.1.2.5 |Forget User ID |
|Version: |00 |
|Context: |This use case is used for Forget User ID of AQIS. |
|Priority: |High |
|Frequency: |As and when actor forget his/her user id of AQIS application |
|Primary Actor: |AQIS/SIP Users |
|Preconditions: |User has clicked on the link available at AQIS for Forget User ID. |
|Basic Flow |1. System presents the actor an interface to enter email id: |
| |2. Actor shall enter email id. |
| |3. System will send the forget user id at email id of user. |
| |Use Case Ends. |
|Alternative Flow: | 1. Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before search details. And if found then |
| |display the alert messages corresponding to related field. |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |Actor shall successfully get the User id. |
|Special Requirements: |Form field shall be verified from both client and server end. |
|Unresolved Issues: | |
6 ATTACH DOCUMENTS
|UC 3.1.2.6 |Attach Documents |
|Version: |00 |
|Context: |This use case allows the actor to add a new attachment to an item. The attached file format and size limit would |
| |be governed by the system parameters set in the AQIS application from where the Add attachment has been invoked by|
| |the actor. |
| |The file to be attached may be located anywhere in a network of systems to which the actor’s system is connected. |
|Priority: |High |
|Frequency: |Medium |
|Actors: |A person/agency that is uploading any document on the system. |
|Trigger: |The actor chooses to add an attachment. |
|Pre-conditions: |Actor had logged into the AQIS application and has chosen to Add attachment in a specific application module. |
| | |
| |Actor can upload only PDF file in the AQIS application. |
|Post conditions: |The Attachments will take effect only if the user confirms the operation from which this use case was called. |
| |If the user confirms the uploaded attachments by submitting, then linkages of the uploaded files with the item |
| |will be created and saved in the respective AQIS application database. |
| |The uploaded attachments usage would then be governed by the business rules/Use cases of the respective AQIS |
| |applications. |
|Normal Flow: |Actor Actions |System Responses |
| | |System would display the Allowed File Type(s) which can be |
| |Actor enters the Title of the attachment. |uploaded by the actor, along with File Upload Limit, as |
| | |defined in the System Parameter of the respective AQIS |
| | |application. |
| | |The standard Operating System dialogue Window (which displays |
| |Actor navigates through the list of files and |the list of files currently available on the local machine) is|
| |folders and selects the file to be uploaded. |displayed. The window also provides option to select a file |
| | |available on another system which may be connected to the |
| |Actor chooses to upload. Actor chooses to upload |local system, invariably in a LAN |
| |the allowed file type and file size is within the |The file selected for attachment is scanned for any virus at |
| |upload Limit. |the time of upload and if the virus can’t be removed, the file|
| | |is not uploaded to the server. The actor is informed with the|
| |The actor may choose to drop the attachment, if |message: "The selected file could not be uploaded as it was |
| |required, using Drop Attachment use case. |virus infected and could not be cleaned. Pl. selects another |
| | |file". |
| | |The file is uploaded to the system from which Add Attachment |
| | |was invoked |
| | |Once the file is successfully uploaded, the system displays |
| | |the message “File was attached successfully.” |
|Alternative Flow |The actor may repeat steps 1 to 10 as many times as required |
|Exceptional Flow |Network connection breaks while uploading file to |The actor is brought back to the Pre condition. |
| |the PES system if the system is on a network. |The actor will have to begin the file upload operation all |
| | |over again from Step 1. |
| |If, the Confirm button is clicked without entering | |
| |the title |The system would respond with the message “ field |
| |In Step 5 of normal flow, if actor chooses: |cannot be left blank. Please enter the Title.” |
| |Selected File Type is not under the list defined in|On Save, System would prompt the error message as “File Type |
| |Allowed File Type(s), |not allowed for upload,” Actor can then choose to browse a |
| | |different file type. |
| | | |
| | |On Save, System would prompt the error message as “File |
| |Sum total of File sizes of all the file |Size(s) has exceeded the Upload Limit,” Actor can then choose |
| |attachments exceeds the Upload Limit, |to browse a different file(s). |
| | | |
| | |The system would respond with the message: "The selected file |
| |The file attachment selected for uploading is virus|could not be uploaded as it was virus infected and could not |
| |infected and the system is not able to clean it. |be cleaned. Pl. selects another file". |
|Includes: |None |
|other use case id | |
|UI: |Required |
|required/not required | |
|Priority: |High |
|Low/medium/high | |
|Frequency of Use: |Frequent |
|Continuous/ frequent/ | |
|medium/ less/ rare | |
|Business Rules: |There may be more than one file attached to an item. |
| |Title of the attachment is a Mandatory field and should not be left blank. |
| |Document name & its location should be save in the database. |
|Special Requirements: |In case the connection breaks while uploading the file, the upload process will have to begin all over again. |
| |However, if technology permits, it will be preferred, if the system resumes the file upload from the point where |
| |the connection was lost. |
|Assumptions: |None |
|Dependency: |Extends |
| |All Use Case(s) which involve forms/pages with Add Attachment Option. |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Notes and Issues: |None |
7 DROP ATTACHMENT
|UC 3.1.2.7 |Drop Attachment |
|Version: |00 |
|Context: |This use case allows the actor to delete or drop a file attachment that is associated with an item. |
|Priority: |High |
|Frequency: |Medium |
|Actors: |A person/agency that is dropping any document from the system. |
|Trigger: |The actor chooses to drop one or more attached files. |
|Pre-conditions: |Actor had logged into AQIS application and has chosen to Drop attachment in a specific application module, provided at |
| |least one file is attached with the item. |
|Post conditions: |The dropped files will be removed from the CAP application only if the user confirms the dropping of attachments by |
| |submitting the changes. |
| |All linkages of the item with the dropped attachments are removed from the application. |
| |Actor Actions |System Responses |
| | | |
| |Actor confirms the drop operation. |The System displays the message “Proceed with dropping the |
| | |selected files?” to confirm the drop operation. |
| | | |
| | |The selected files are marked as dropped. |
|Alternative Flow |None |
|Exceptional Flow |None |
|Includes: |None |
|other use case id| |
|UI: |Required |
|required/not | |
|required | |
|Priority: |High |
|Low/medium/high | |
|Frequency of Use:|Rare |
|Continuous/ | |
|frequent/ medium/| |
|less/ rare | |
|Business Rules: |The attachment will not get dropped, if it is the only element that constitutes the item. |
|Special |None |
|Requirements: | |
|Assumptions: |None |
|Dependency: |Extends |
| |All Use Case(s) which involve forms/pages with Drop Attachment Option |
| |Is Extended By |
| |None. |
| |Uses |
| |Login |
|Notes and Issues:|None |
8 AUTO TRIGGER
|UC 3.1.2.8 |Auto Trigger |
|Version: |00 |
|Context: |This use case is for alert system |
|Priority: |High |
|Frequency: |High |
|Actors: |System |
|Trigger: |Message from other use cases where auto trigger is being called. |
|Pre-conditions: |Message should comply with the alert system’s interface |
|Post conditions: |1. On success, Trigger mail / message sent to the respective stakeholders as received from the use case. |
| |2. On failure, retries until success or drops the message and table is updated |
|Basic Flow: |Actor Actions |System Responses |
| |Actor reads the message and the details shall |System will display the message with the details containing time |
| |contain; |stamp, target mail id, mobile number and sends the message to |
| |-time stamp |target |
| |-target mail id and mobile no | |
| |-message | |
| | | |
| |Stores the details in the table | |
| |Sends the message to target | |
|Includes: |None |
|other use case id | |
|UI: |Required |
|required/not required | |
|Priority: |High |
|Low/medium/high | |
|Frequency of Use: |Continuous |
|Continuous/ frequent/ medium/| |
|less/ rare | |
|Business Rules: |1. Should try for 24 hrs before dropping the message or as per system admin policy |
| |2. All acknowledgements could be auto-erased as per system admin policies |
|Special Requirements: |None |
|Assumptions: |None |
|Dependency: |Extends |
| |All the use cases where auto trigger is being called, |
| | |
| |Is Extended By |
| |None |
| | |
| |Uses |
| |Login |
|Notes and Issues: |None |
9 MANUAL TRIGGER
|UC 3.1.3.9 |Manual Trigger |
|Version: |00 |
|Context: |This use case is for alert system which should be functioning when manual commands are given |
|Priority: |High |
|Frequency: |Medium |
|Actors: |All system users |
|Trigger: |Actor clicks on the link available for alert |
|Pre-conditions: |Actor logs on to the system based on the credentials assigned. |
|Post conditions: |1. On success, Trigger mail / message sent to the respective stakeholders as received from the use case. |
| |2. On failure, retries until success or drops the message and table is updated |
|Basic Flow: |Actor Actions |System Responses |
| |Actor selects SMS / Mail |Captures the details and displays confirmation dialogue |
| |Actor types the message and the details shall contain;|Stores the details in the table |
| |- purpose |Sends the message to target |
| |-message | |
| |-target (other system users / registered business | |
| |users) | |
| |Clicks submit | |
|Includes: |None |
|other use case id | |
|UI: Required/not required |Required |
|Priority: |High |
|Low/medium/high | |
|Includes: |None |
|other use case id | |
|Business Rules: |1. Should try for 24 hrs before dropping the message or as per system admin policy |
| |2. All acknowledgements could be auto-erased as per system admin policies |
| |3. Based on role the system should allow / restrict sending SMS to other officers. |
| |4. Only registered dealers/farmers/manufacturers list will be available to send SMS |
|Special Requirements: |None |
|Assumptions: |None |
|Dependency: |Extends |
| |Use cases where any alert could be generated |
| | |
| |Is Extended By |
| |None |
| | |
| |Uses |
| |Login |
|Business Rules: |1. Should try for 24 hrs before dropping the message or as per system admin policy |
| |2. All acknowledgements could be auto-erased as per system admin policies |
| |3. Based on role the system should allow / restrict sending SMS to other officers. |
| |4. Only registered dealers/farmers/manufacturers list will be available to send SMS |
3 SYSTEM ADMINISTRATOR
• User Creation (Create /Edit) • Role Creation ( Add New/Edit/Delete) • User Management (Add New/Edit/Activate/Deactivate)
[pic] Diagram 31: System Administrator
| No. |Actor |Responsibility |
|1 |System Administrator |To Create Internal and External User |
|2 |System Administrator |To Create role for Internal and External User |
|3 |System Administrator |To Manage users |
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.1.3.1 |User Creation |This use case is for Creating, |System Administrator |
| | |editing users(Internal & | |
| | |External) from web by the system| |
| | |administrator | |
|UC 3.1.3.2 |Role Creation |This use case is for adding, |System Administrator |
| | |editing or deleting | |
| | |user(Internal & External) roles | |
| | |from master table | |
|UC 3.1.3.3 | User Management |This use case is for adding, |System Administrator |
| | |editing, activate/ deactivate | |
| | |user group from master table | |
2 USER CREATION
|UC 3.1.3.1 |User Creation |
|Version: |00 |
|Context: |This use case is for Creating or editing users from the web. |
|Priority: |High |
|Frequency: |High |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |System presents the Actor list of Users with the option of add, edit |
| |If Actor shall instruct to add the user. |
| |• System presents an interface with the following options: |
| |login |
| |Category( Internal or External User) |
| |Category ( Section officer, AC trade, JS trade, Director trade, quarantine officer ,Importer, Exporter) |
| |Name of the officer |
| |category (Importer/Exporter or both /NPPO/Stakeholders |
| |Importer/Exporter Name |
| | |
| |For external user |
| |IE Code |
| |NPPO country Name |
| |NPPO code |
| |Stakeholders Name |
| |Address |
| |Residential Address |
| |Contact No. |
| |Departmental Email ID |
| |Alternate Email ID |
| |Date of Birth |
| |Select Question |
| |Secret Answer |
| |Retype Password |
| |Type the code shown |
| |Register |
| |Clear |
| |Home |
| |Try from a new code |
| | |
| |If it is Internal user following detail would be displayed on the screen to actor : |
| |Login |
| |Name of employee |
| |Designation |
| |Address |
| |Residential Address |
| |Employee Code |
| |Contact No. |
| |Departmental Email id |
| |Alternate Email id |
| |DOB |
| |Register |
| |Clear |
| |Home |
| |Actor shall enter the user details and instruct to store into system. |
| |If Actor wants to edit the user. |
| |Actor selects the particular user to be edited and presses edit. |
| |System shows the user contents with editable access. |
| |Edits the content (Add- to enter new details /Modify- edit the current details). |
| |Actor shall instruct to update the table. |
| |The Use Case Ends. |
|Alternative Flow: |1. Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before save the forms details. And if found then|
| |display the alert messages corresponding to related field. |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
| |3. Actor will verify the details of the users & enable their user id |
| |Password: - Auto generated password will be delivered at their Email id & information on SMS. |
| |One PDF file will be generated for record purpose. |
|Post Condition: |Database is updated and mail trigger to respective person with consolidated information details. |
| |The system shall generate application reference number and thrown a message to the applicant. |
| |An SMS indicating the registration is complete will be sent to the recipient mobile. |
| |Table shall be updated. |
|Special Requirements: |I/E code issued by DGFT to importer/exporter would be displayed in our system for verification through web |
| |services. In case of internal users LDAP will be used |
|Unresolved Issues: | |
3 ROLE CREATION
|UC 3.1.3.2 |Role Creation |
|Version: |00 |
|Context: |This use case is for adding, editing or deleting user roles from master table |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |System presents the Actor list of Roles (if already exist) or blank page with the option of add, edit and delete|
| |If Actor shall instruct to add the role. |
| |• System presents an interface with the following options: |
| |Role ID: Actor shall define the unique role id. |
| |Role Name: Actor shall define the name of the role. |
| |Role Description: Actor shall describe the user’s role. |
| |Update: If require actor shall update any option |
| |Actor shall enter the role details and instruct to store into system. |
| |If Actor wants to edit the Role. |
| |Actor selects the particular role to be edited and instructs to edit. |
| |System shows the role contents with editable access. |
| |Edits the content (Add- to enter new details /Modify- edit the current details). |
| |Actor shall instruct to update the table. |
| |If Actor wants to delete the role. |
| |Checks the particular/multiple role to be deleted and instruct to delete. |
| |The Use Case Ends. |
|Alternative Flow: |1. Invalid data or left blank any required field. |
| | |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found then|
| |display the alert messages corresponding to related field. |
| | |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |Database is updated and mail trigger to respective person with consolidated information details. |
| |The system shall generate application reference no and thrown a message to the applicant. |
| |An SMS indicating the registration is complete will be sent to the recipient mobile. |
| |Table shall be updated. |
|Special Requirements: | |
|Unresolved Issues: | |
4 USER MANAGEMENT
|UC 3.1.3.3 |User Management |
|Version: |00 |
|Context: |This use case is for adding, editing, activate/ deactivate or freeze the user and user roles from master table |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |System presents the Actor list of users (if already exist) or blank page with the option of add, edit and delete|
| |If Actor shall instruct to add the role. |
| |• System presents an interface with the following options: |
| |User ID: Actor shall select the User ID fro existing list of User ID. |
| |Role ID: Actor shall define the name of the role. |
| |Level’s of User’s Role: This field comes from Role Creation table. |
| |State/ District Name: Actor shall enter the state/ district where the User has posted in case only range or |
| |district level user. |
| |Actor shall enter the user management details and instruct to store into system. |
| |If Actor wants to edit the Role. |
| |Actor selects the particular user to be edited. |
| |System shows the role contents with editable access. |
| |Edits the content (Add- to enter new details /Modify- edit the current details). |
| |Actor shall instruct to update the table. |
| |If Actor wants to activate/ deactivate the user. |
| |Checks the particular/multiple role to be activated / deactivated and instruct to activate/ deactivate. |
| |If Actor wants to Freeze the role. |
| |Checks the particular user to be frozen and instruct to freeze the user. |
| |The Use Case Ends. |
|Alternative Flow: |1. Invalid data or left blank any required field. |
| | |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found then|
| |display the alert messages corresponding to related field. |
| | |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |1. Tables should be updated. |
|Special Requirements: | |
|Unresolved Issues: | |
2 ANIMAL QUARANTINE
1 SIP & AQIS ACTIVITIES USE CASES
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.2.1.1 |Enter Data For SIP |The use case is to enter the data for applying SIP|Importer |
|UC 3.2.1.2 |Application Scrutiny & Verification For SIP|This use case describes the process of scrutiny of|Section Officer |
| | |documents & approval. | |
|UC 3.2.1.3 |Application Forward to AC Trade |This use case describes the process of agenda |AC Trade |
| | |preparation & forwarding the application to | |
| | |respective division. | |
|UC 3.2.1.4 |Receiving Application For Comments by |This use case describes the process of receiving |AC Dairy division , AC LH |
| |Divisional AC/FRO |application by divisional AC/FRO &preparing the |division , FRO FY |
| | |comment on each application. |division |
|UC 3.2.1.5 |Application Forward to TO/FDC/DC along with|This use case explains the process of reviewing |TO/FDC/DC |
| |Comments |the comments & put the remarks if any. | |
|UC 3.2.1.6 |Receiving Application along with Comments |This use case explains the comment received by |Divisional Heads |
| |by Divisional Heads |divisional heads. | |
|UC 3.2.1.7 |Application Forward to AC/FRO |This use case describes the process of forwarding |AC/FRO |
| | |the application to AC/FRO if correction required. | |
|UC 3.2.1.8 |Application Forward to TO/FDC/DC along with|This use case describes the process of reviewing |TO/FDC/DC |
| |Comments |the application again after making the necessary | |
| | |correction by AC/FRO | |
|UC 3.2.1.9 |Receiving Application along with Comments |This use case explains the process of inputting |Divisional Heads |
| |by Divisional Heads |the remarks if any to the corrective application | |
| | |forwarded by TO/FDC/DC | |
|UC 3.2.1.10 |Application Approval For SIP |This use case describes the process of final |JS Trade/Director Trade |
| | |approval of application by respective approval |for approval |
| | |head. |SO/AC for updating status|
| | | |after meeting |
|UC 3.2.1.11 |Issuance of SIP |This use case describes the final issuance of SIP |Section officer/AC trade |
| | |by AC Trade. | |
|UC 3.2.1.12 |Common Process Flow for AQIS/PQIS Login. |This use case describes the login process to |AQIS/PQIS Users |
| | |AQIS/PQIS application. | |
|UC 3.2.1.13 |Entry Certification Data for AQC. |This use case is to enter the data for applying |Importer/ Exporter |
| | |e-certification of AQC for Livestock/ Pet Animal /| |
| | |Livestock Product. | |
|UC 3.2.1.14 |Verification & Approval/ Rejection of AQC |This use case is to describe the process of |Quarantine Officer |
| |Application |scrutiny/verification of documents/ application & | |
| | |approval or rejection for AQC application. | |
|UC 3.2.1.15 |Enter Provisional AQC Certification Data |This use case is to enter the data for applying of|Importer |
| | |Provisional (AQC) for Livestock/ Pet Animal / | |
| | |Livestock Product. | |
|UC 3.2.1.16 |Verification & Approval/ Rejection/ |This use case is to describe the process of |Quarantine Officer |
| |Issuance of Provisional AQC |scrutiny/verification of documents/ application & | |
| | |approval, rejection or issuance of Provisional | |
| | |AQC. | |
|UC 3.2.1.17 |Make Payment for Lab |This use case is used to Make Payment for Lab |Importer/Exporter/Quaranti|
| |testing/Quarantine/Vaccination |testing/Quarantine/Vaccination |ne officer |
|UC 3.2.1.18 |Payment Gateway |A payment gateway facilitates the transfer of |Importer/Exporter |
| | |information between a payment portal (such as a | |
| | |website and mobile phone) and the Front End | |
| | |Processor or acquiring bank. | |
|UC 3.2.1.19 |Sample Collection & Sending to Lab for |This use case is to describe the process of |Quarantine Officer |
| |Testing |collecting sample for testing and sending to lab | |
| | |for testing | |
|UC 3.2.1.20 |Receiving Sample and Sending Report to |This use case is to describe the process of |Testing Lab Officer |
| |Quarantine Officer |receiving samples at lab and sending report to | |
| | |quarantine officer | |
|UC 3.2.1.21 |Sample Test Result |This use case is to specify the result of tested |Testing Lab Officer |
| | |samples. | |
|UC 3.2.1.22 |Receiving and Verification of Test Report |This use case is to describe the process of |Quarantine Officer |
| |From Lab |receiving test report from lab. | |
|UC 3.2.1.23 |NPPO Access to view PSC/AQC. |This use case explains the process of viewing the |NPPO |
| | |PSC/AQS number by NPPO for verification. | |
|UC 3.2.1.24 |Updating Rejection of PSC/AQC by NPPO |This use case describes the process that how NPPO |NPPO |
| | |of other countries update the data of rejected | |
| | |PSC/AQC. | |
|UC 3.2.1.25 |Grievance Management |This use case explains the flow to submit the |Importer/Exporter |
| | |complaint. | |
|UC 3.2.1.26 |View Grievance Redressal |This use case would describe the |Importer/Exporter |
| | |Process to view the grievances. | |
|UC 3.2.1.27 |Grievance Redressal System |This use case would describe the |Nodal Officer |
| | |way to address the grievances | |
|UC 3.2.1.28 |MIS/Report |This use case provides all the different reports |HOD |
| | |required by NIC. | |
|UC 3.2.1.29 |Master data Management |This use case is for adding, editing or deleting |System administrator |
| | |contents from master table | |
1 ENTER DATA FOR SIP
|UC 3.2.1.1 |Enter data for SIP |
|Version: |00 |
|Context: |The use case is to enter the data for applying SIP. |
|Priority: |High |
|Frequency: |As and when user wants to import the livestock Product. |
|Primary Actor: |Importer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |In case of Livestock actor shall apply for import License from DGFT office. This is out of scope of this SRS.|
| |Actor shall have all the details related to import of LSP. |
| |Actor shall apply for one product (HS Code) in one application. |
|Basic Flow |1. Actor instructs the system for issuance of Sanitary Import Permit. |
| |2. System presents the actor an interface to enter details related to Form A, Form B |
| |SIP of LSP for trading & marketing (Form B): - Name and address of importers, Exact des. Of livestock |
| |Products with Indian trade classification, ITC (HS) code, FSSAI certificate number, Detail of Livestock from |
| |whom it is produced, number of packages, Total weight/volume Name & address. Of producer, Name & address. Of |
| |consignor, Country & locality in which Livestock Product produces, Country from which importer into India, |
| |Foreign port of shipment, Name of airport/seaport/land custom station(entry point),Declaration ,Others |
| |SIP of LSP for personal use(Form A):-Name & exact description of live-stock-product to be imported, |
| |Description of the consignment and quantity, Name & address of consignor, Name & address of importer, ITC(HS)|
| |code, Country & locality in which produced, Country from which imported into India, Foreign port of shipment |
| |, Approximate date of arrival of the consignment in India, Name of point of entry in India ,Declaration, |
| |others |
| |Mandatory field :- Name & address of importer, Name & address of consigner, Name & address of the producer, |
| |Country & locality in which Livestock Product produces, foreign port of shipment, Name of airport/sea port |
| |(entry point), FSSAI certificate number. |
| |3. System captures the input and updates the database. |
| |4. One reference number will be generated by the system & displayed on the screen. |
| |5. Through this reference number all the transaction will be processed further. |
|Alternative Flow: |1. Invalid data or left blank any required field. |
| | |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found |
| |then display the alert messages corresponding to related field. |
| | |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |1. Data shall be saved in the database. |
| |2. Actor shall successfully logout and brought to the Home Page. |
| | |
|Special Requirements: | |
|Unresolved Issues: | |
2 APPLICATION SCRUTINY & VERIFICATION FOR SIP
|UC 3.2.1.2 |Application Scrutiny & Verification for SIP |
|Version: |00 |
|Context: |This use case describes the process of scrutiny of documents & approval. |
|Priority: |High |
|Frequency: |As and when user wants to import the livestock Product. |
|Primary Actor: | Section officer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records or application using the use case “ Enter the data for SIP” |
| |Actor will select one record at a time to verify the details. |
| |Actor will choose one of the following options. |
| |If approved, click on APPROVRD button. |
| |If rejected, click on Rejected button. |
| | |
| |After APPROVED in above mention cases application will forwarded to AC trade. |
| | |
| |If rejected: - Actor will entered the reason of rejection & press the submit button. Automated information |
| |along with the reason sent to importer on their registered e-mail id or on register mobile no through SMS |
| |gateway. |
| | |
| |If deficiency: - Actor will forward the application to importer for deficiency removal & resubmission. |
| |Application forward to AC trade. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Special Requirements: | |
|Unresolved Issues: | |
3 APPLICATION RECEIVED BY AC Trade
|UC 3.2.1.3 |Application Received By AC Trade |
|Version: |00 |
|Context: |This use case describes the process of agenda preparation & forwarding the application to respective |
| |division. |
|Priority: |High |
|Frequency: |As and when user wants to import the livestock Product |
|Primary Actor: | AC Trade |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records or application using the use case “ Application Scrutiny & Verification for |
| |SIP” |
| |System will prompt the actor to specify the following details: |
| |Title of agenda |
| |Agenda number |
| |Name of the farm |
| |Remarks |
| |Unit name: Dairy division , LH division ,FY division |
| |Product name |
| |Comment of the concerned units |
| |Recommendation of the committee |
| | |
| |After specify all the details, the actor will click Save & Submit |
| | |
| |2. Actor may add multiple agendas choosing ADD more option available on the screen. |
| | |
| | |
| |After preparing the Agenda for Meeting or Onfile case, Actor will forward the application as per the |
| |condition to concerned AC/FRO. if application is for the below items: |
| |Fish Feed |
| |Fish Food |
| |Whey Protein |
| |Cheese |
| |Hilsa |
| |Bovine Serum |
| | |
| |Then it will be processed as fast track. Otherwise actor will select the Meeting or On file case. |
| |Actor will click on FORWARD button. |
| |The forwarded application will go to the respective divisional AC/FRO inbox. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Special Requirements: | |
|Business Rule: |The application of Dairy division will forwarded to dairy division & LH division. |
| |LH division application will forward to LH division. |
| |FY division application will forward to FY division. |
|Unresolved Issues: | |
3.2.1.4 RECEIVING APPLICATION FOR COMMENTS BY DIVISIONAL AC/ FRO
|UC 3.2.1.4 |Receiving Application for Comments by Divisional AC/FRO |
|Version: |00 |
|Context: |This use case describes the process of receiving application by divisional AC/FRO &preparing the comment on |
| |each application. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: | AC Dairy division , AC LH division , FRO FY division |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by AC Trade to AC Dairy division, AC LH division, FRO FY division of |
| |application using the use case “Application Received by AC /FRO”. |
| |Actor will select one application. |
| |Actor will prepare the comments for respective division. |
| |Actor will forward the application along with comments to TO/FDC/DC respectively. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
3.2.1.5 APPLICATION RECEIVED BY TO/FDC/DC ALONG WITH COMMENTS
|UC 3.2.1.5 | Application Received by TO/FDC/DC Along with Comments |
|Version: |00 |
|Context: |This use case explains the process of reviewing the comments & put the remarks if any. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: | TO/FDC/DC |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by AC Dairy division to TO Dairy division, AC LH division to DC LH |
| |division, FRO FY division to FDC Fishery division of application using the use case “Receiving Application |
| |for Comments by Divisional AC/FRO”. |
| |Actor will select one application. |
| |Actor will review the put the remarks/Input if any. |
| |Actor will forward the application along with correction in the comments if any to divisional head |
| |respectively. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: |It is suggested that reference of appropriate formats as applicable may be included as one of the condition |
| |in the SIP. |
|Business Rule: | |
|Unresolved Issues: | |
| | |
3.2.1.6 RECEIVING APPLICATION ALONG WITH COMMENTS BY DIVISIONAL HEADS
|UC 3.2.1.6 |Receive Application along with comments by Divisional Heads |
|Version: |00 |
|Context: |This use case explains the comment received by divisional heads. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: |Divisional Heads |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by TO Dairy division, DC LH division, FDC Fishery division to Divisional|
| |heads of respective division of application using the use case “Application Received by TO/FDC/DC Along With |
| |Comments”. |
| |Actor will select one application. |
| |Actor will review the comments & put the remarks/Input if any. |
| |Actor will forward the application to respective divisional AC/FRO if correction required. |
| |If correction not required application will forward in (Meeting case) to JS Trade, in (On File case) & (Fast |
| |Track) to Director Trade. |
| | |
| | |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
3.2.1.7 APPLICATION RECEIVED BY AC /FRO
|UC 3.2.1.7 |Application Received by AC /FRO |
|Version: |00 |
|Context: |This use case describes the process of forwarding the application to AC/FRO if correction required. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: |AC/FRO |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by Divisional heads of respective division to AC/FRO if correction |
| |required in application of using the use case “Receiving Application Along With Comments by Divisional heads”.|
| |Actor will select one application. |
| |Actor will do the necessary correction in the comments. |
| |Actor will again forward the application to TO Dairy division, FDC Fishery division, DC LH division. For |
| |review. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
3.2.1.8 APPLICATION RECEIVED BY TO/FDC/DC ALONG WITH COMMENTS
|UC 3.2.1.8 | Application Received by TO/FDC/DC Along with Comments |
|Version: |00 |
|Context: |This use case describes the process of reviewing the application again after making the necessary correction by |
| |AC Trade. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: | TO/FDC/DC |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by AC/FRO to TO Dairy division, DC LH division, FDC Fishery division of |
| |application using the use case “Application Received by AC /FRO”. |
| |Actor will select one application. |
| |Actor will review the updated application and put the remarks/input if any. |
| |Actor will forward the application along with correction in the comments if any to divisional head respectively. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: |The application of Dairy division will forwarded to dairy division & LH division. |
| |LH division application will forward to LH division. |
| |FY division application will forward to FY division. |
|Unresolved Issues: | |
| | |
3.2.1.9 RECEIVING APPLICATION ALONG WITH COMMENTS BY DIVISIONAL HEADS
|UC 3.2.1.9 |Receiving Application along with Comments by Divisional Heads |
|Version: |00 |
|Context: |This use case explains the process of inputting the remarks if any to the corrective application forwarded by |
| |TO/FDC/DC. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: |Divisional Heads |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by TO Dairy division, DC LH division, FDC Fishery division to Divisional |
| |heads of respective division of application using the use case” Application Received by TO/FDC/DC Along With |
| |Comments”. |
| |Actor will select one application. |
| |Actor will review the correction made in the comments & put the remarks/input if any. |
| |Actor will forward the application in (Meeting case) to JS Trade & in (On File case) to Director Trade. |
| | |
| | |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
3.2.1.10 APPLICATION APPROVAL FOR SIP
|UC 3.2.1.10 |Application Approval For SIP |
|Version: |00 |
|Context: |This use case describes the process of final approval of application by respective approval head. |
|Priority: |High |
|Frequency: |As and when user call the meeting for discussion on comments. |
|Primary Actor: | JS Trade/Director Trade for approval |
| |SO/AC for updating status after meeting |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |Report will be generated comprising comments received from various divisional head against the sent applications.|
| |This report can be utilized by AC trade for preparing agenda with the JS trade & other divisional heads. |
|Basic Flow |All the applications against which comments have been given by different divisional heads will be displayed here.|
| | |
| |If it is meeting case actor would be JS trade and if it is on file case actor would be director trade/AC Trade. |
| | |
| |In fast track case actor would directly come to this window after UC 3.1.2.1. |
| | |
| |Actor would update the status of application after meeting as well as select the post import condition as |
| |applicable. |
| | |
| |The actor could select one application each time. |
| | |
| |Once the actor selects the application, depending upon the discussions held in the meeting actor may accept or |
| |reject the application by choosing the respective link available on the screen. |
| |An SMS alert to be sent to the respective importer about the acceptance or rejection of the application. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |The PDF will be available for download & print. |
| |The accepted or rejected application will be available to the AC trade for issuing SIP or discard the |
| |application. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
11 ISSUANCE OF SIP
|UC 3.2.1.11 |Issuance of SIP |
|Version: |00 |
|Context: |This use case describes the final issuance of SIP by AC Trade. |
|Priority: |High |
|Frequency: |As and when user call the meeting for discussion on comments. |
|Primary Actor: |Section officer/AC trade |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |The accepted or rejected applications sent by Section officer will be displayed to the actor will the following |
| |details. |
| |Application reference number |
| |Application date |
| |Application status. |
| | |
| |The may select one or multiple applications to generate the SIP. |
| |Only the applications with “accepted” status would be enabled for selection |
| |The actor will click on the generate SIP link available on the screen to generate Sip’s in pre PDF defined |
| |format. |
| |Actor will take the signature from the A/C trade on approved Sip’s. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |The PDF will be available for download & print. |
| |The generated Sip’s will be sent to the importer on their registered email id. |
| |The status of application will be changed in the database as rejected or accepted and importer/exporter may |
| |search the status of applications on the home page of AQIS applications using the application reference number |
|Special Requirements: |Application number should be printed on the SIP certificate. |
|Business Rule: | |
|Unresolved Issues: | |
12 COMMON PROCESS FOLW FOR AQIS/PQIS LOGIN
|UC 3.2.1.12 |Common Process Flow for AQIS/PQIS Login |
|Version: |00 |
|Context: |This use case describes the login process to AQIS/PQIS application. |
|Priority: |High |
|Frequency: |As and when user call the meeting for discussion on comments. |
|Primary Actor: |AQIS/PQIS Users |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |Actor will type CAP URL on browser to come on the home page of CAP. |
| | |
| |Actor will select / click on link AQIS/PQIS available. |
| | |
| |Actor will fill and submit the application of user id & password. If internal user will directly reached to the |
| |AQIS/PQIS Home page. |
| | |
| |If External user then Verification of I/E code will be done by the system administrator of respective |
| |application. |
| | |
| |Login id will be enabled by system administrator after verification of I/E Code. |
| | |
| |Now actor will login AQIS/PQIS respectively. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: | |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
13 ENTER CERTIFICATION DATA FOR AQC
|UC 3.2.1.13 |Enter Certification Data for AQC |
|Version: |00 |
|Context: |This use case is used to enter the information for AQC certification |
|Priority: |High |
|Frequency: |As and when user wants to export or import the Livestock / Pet Animal / Livestock Product. |
|Primary Actor: |Importer/Exporter |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Actor shall have all the details related to Import/Export of Livestock / Pet Animal /LSP. |
|Basic Flow |1. Actor instructs the system for e-certification of Import/Export |
| |2.Actor will select the role:- Importer / Exporter |
| |3. Actor will select the product: - Livestock/Pet animal/Livestock Product. |
| |4. System presents the actor an interface to enter details related to e- certification in Four conditions. |
| |If importer is applying for Livestock / Pet animal. |
| |If importer is applying for livestock product. |
| |If exporter is applying for Livestock / Pet animal. |
| |If exporter is applying for Livestock product. |
| | |
| |5. If importer is applying for Livestock / pet animal. The system would prompt the actor to specify following |
| |details. |
| | |
| |Livestock/Pet animal:-Product, Applied To, Exporter name, Importer name, Exporter address, Importer address, SIP|
| |number/DGFT license number, Purpose of export/import, Date/mode, Health certificate, DOB, Colour, Country of |
| |origin, PP number /Microchip number, number of livestock with number of packages, Rabies/vaccination, |
| |vaccination date, validity, Batch number, Country & place of embarkation, Country & place of disembarkation, |
| |Documents:- Health cert., Ticket if any, SIP/DGFT license, Imp./Exp. Declaration, Lab letter/report, |
| |Invoice/packaging list, BOE, Charges if any. |
| | |
| |6. If importer is applying for Livestock product. The system would prompt the actor to specify following |
| |details. |
| | |
| |LSP:-Product, Applied To, Exporter name, Importer name, Exporter address, Importer address, I/E License. number |
| |/DGFT license number, SIP, Name of LSP, Quantity/weight/volume/kg/L.T., Number of packages, Custom seal number |
| |/ date BOE, Date of import/export, Shipping/airways bill number /date, Invoice number & date, Country of origin,|
| |Post of loading, Country of Import/export, Post of unloading, Container number, Date/means of conveyance, Plant |
| |registration number, Purpose of import/export, Health certificate number & date Lab report number & date |
| |Document attach:- Import/Export License, SIP ,Health certificate, Fumigation cert./Test report, Invoice number, |
| |Airways bill number, Imp/Exp declaration, others, charges if any |
| | |
| |7. If exporter is applying for Livestock / pet animal. The system would prompt the actor to specify following |
| |details. |
| | |
| |Livestock/Pet animal:-Product, Applied To, Exporter name, Importer name, Exporter address, Importer address, SIP|
| |number/DGFT license number, Purpose of exp./imp., Date/mode, Health certificate, DOB, Colour, Country of origin,|
| |PP number /Microchip number, number of livestock with number of packages, Rabies/vaccination, vaccination date, |
| |validity, Batch number, Country & place of embarkation, Country & place of disembarkation, |
| |Documents:- Health cert., Ticket if any, SIP/DGFT license, Imp./Exp. Declaration, Lab letter/report, |
| |Invoice/packaging list, BOE, Charges if any. |
| | |
| |8. If exporter is applying for Livestock product. The system would prompt the actor to specify following |
| |details. |
| | |
| |LSP:-Product, Applied To, Exporter name, Importer name, Exporter address, Importer address, I/E License. number |
| |/DGFT license number, SIP, Name of LSP, Quantity/weight/volume/kg/L.T., Number of packages, Custom seal number |
| |/ date BOE, Date of import/export, Shipping/airways bill number /date, Invoice number & date, Country of origin,|
| |Post of loading, Country of Import/export, Post of unloading, Container number, Date/means of conveyance, Plant |
| |registration number, Purpose of import/export, Health certificate number & date Lab report number & date |
| |Document attach:- Import/Export License, SIP ,Health certificate, Fumigation cert./Test report, Invoice number, |
| |Airways bill number, Imp/Exp declaration, others, charges if any |
| | |
| |Mandatory field :- Product, Applied To, Importer/Exporter Name, Importer/Exporter Address, Country to |
| |Import/export, county of origin, Means of conveyance, number of packages/containers, Port of unloading/loading, |
| |Invoice number, Inspection date, Place of inspection, Purpose of export / import. |
| |3. System captures the input and updates the database. |
|Alternative Flow: |Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found then|
| |display the alert messages corresponding to related field. |
| |Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |1. Data shall be saved in the database & application number will be generated. |
| |2. Actor shall successfully logout and brought to the Home Page. |
|Business Rule: | 1. If actor will select Pet animal in case of export/ import then quantity cannot be equal to or more than|
| |two. |
|Special Requirements: | 2. If actor will select Pet animal in case of export/ import then quantity cannot be equal to or more than|
| |two. |
|Unresolved Issues: | |
14 VERIFICATION & APPROVAL/ REJECTION OF AQC APPLICATION
|UC 3.2.1.14 |Verification & Approval / Rejection of AQC Application |
|Version: |00 |
|Context: |This use case is to describe the process of scrutiny/verification of documents/ application & approval or |
| |rejection for AQC. |
|Priority: |High |
|Frequency: |As and when user wants to export or import the Livestock / Pet Animal / Livestock Product. |
|Primary Actor: |Quarantine Officer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records or application using the use case “Enter Certification Data for AQC”. |
| |Actor will select one record at a time to verify. |
| |Actor will choose one of the following option |
| |If approved, click on APPROVRD button. |
| | |
| |If the application is for import then NOC issued and |
| |If the application is for export then AQC health certificate will be issued |
| |If rejected: - In case of import or export the application will be rejected and reasons of rejection/ |
| |testing/vaccination if required, will be entered. Automated information along with the reason sent to |
| |importer/exporter to their registered email-id or on registered mobile number through SMS gateway |
| | |
| |In case of export the system will prompt to forward it either for lab testing or vaccination. |
| | |
| |If Deficiency: - Actor will forward the application to importer/exporter for deficiency removal and |
| |resubmission. |
| |4. In this case the Actor will specify remarks if any |
| |5. If Actor has approved the application then system will generate the NOC in PDF format and an e-mail will be |
| |sent to his/her registered e-mail id and an SMS to his/her registered mobile number. |
| |6. If Actor approves the application the system will generate the AQC health certificate in PDF format to |
| |exporter. |
|Alternative Flow: |Cancel If Actor cancels the form then system will reach at home page. |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Data shall be saved in the database. |
| |2. Actor shall successfully logout and brought to the Home Page. |
| |3. The PDF will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
15 ENTER PROVISIONAL AQC CERTIFICATION DATA
|UC 3.2.1.15 |Enter Provisional Certification Data |
|Version: |00 |
|Context: |This use case is to enter the data for applying of Provisional Quarantine Clearance for Livestock/ Pet Animal / |
| |Livestock Product. |
|Priority: |High |
|Frequency: |As and when user wants to get the provisional quarantine clearance of Livestock / Pet Animal / Livestock Product.|
|Primary Actor: |Importer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Actor shall have NOC from the AQIS |
|Basic Flow |Actor instructs the system for provision quarantine clearance |
| |Certification. |
| |Actor will select the product: - Livestock/Pet animal/Livestock Product. |
| |System presents the actor an interface to enter details related to provision quarantine clearance certification. |
| |Livestock: file number, date, detail of consignment- country of origin, flight number, date of import, bill of |
| |entry number, address of importer, name of importer, detail of livestock-serial number, name, tag number, breed, |
| |sex, age, colour |
| |Livestock Product: file number, date, detail of consignment- country of origin, flight number, date of import, |
| |bill of entry number, address of importer, name of importer, detail of livestock-serial number, name, tag number,|
| |breed, sex, age, colour, detail of livestock product- serial number, product name, ITC(HS) code, number of |
| |packages/ total weight in KG/ volume |
| |Actor will click on the save and submit button |
| |System captures the input and update the database |
|Alternative Flow: |Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found then |
| |display the alert messages corresponding to related field. |
| |Cancel If Actor cancels the form then system will reach at home page. |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Data shall be saved in the database. |
| |2. Actor shall successfully logout and brought to the Home Page. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
16 VERIFICATION & APPROVAL/ REJECTION /ISSUANCE OF PROVISIONAL AQC
|UC 3.2.1.16 |Verification & Approval/ Rejection /Issuance of Provisional AQC |
|Version: |00 |
|Context: |This use case is to describe the process of scrutiny/verification of documents/ application & approval, |
| |rejection or issuance for Provisional AQC. |
|Priority: |High |
|Frequency: |As and when user wants to get Provisional AQC for livestock/ Pet Animal / Livestock Product. |
|Primary Actor: |Quarantine Officer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Sample taken for lab testing |
|Basic Flow |System will display the records or application which have been entered using the use case “ Enter Provisional |
| |Certification Data for AQC” |
| |Actor will select one record at a time to verify. |
| |System will prompt the actor first to select the number of sample and then the test requirement or vaccination |
| |requirement from the list displaying test name & the vaccination names specified in the master table. |
| |If the actor has selected the test requirement the system will prompt the actor to select the testing lab name |
| |from the list displaying the labs name specified in the master table. |
| |After selecting the test requirement or vaccination requirement as well as the lab name system will |
| |automatically update the fee column (as specified in the master table) depending upon the number of samples. |
| |Actor will choose one of the following option |
| |If approved & pet animal or livestock then click on APPROVRD button, Provisional quarantine certificate issued |
| |in PDF format. |
| |If it is non pet livestock, actor will select the quarantine observation for 30 days automated information sent |
| |to importer as well as provisional quarantine certificate will be generated by the system in PDF format and sent|
| |to importer e-mail and SMS on his/her registered e-mail and mobile number. |
| |If Rejected, click on rejected button application will be rejected and deportation order will be issued, |
| |information sent to importer on registered email –id or register mobile number. |
|Alternative Flow: |Cancel If Actor cancels the form then system will reach at home page. |
| |Form close if actor clicks on the close button. |
|Post Condition: |Data shall be saved in the database. |
| |Actor shall successfully logout and brought to the Home Page. |
| |After issuance of provisional certificate to livestock, it will be kept under observation for 30 days at |
| |quarantine station and importer has to pay fee for per LS per day for 30 days. |
| |The PDF will be available for download & print |
|Business Rule: | |
|Special Requirements: |BOE issued by custom to importer would be captured and displayed. |
|Unresolved Issues: | |
| | |
17 MAKE PAYMENT FOR LAB TESTING/QUARANTINE/ VACCINATION
|UC 3.2.1.17 |Make payment for Lab Testing/Quarantine/ Vaccination |
|Version: |00 |
|Context: |This use case is to describe the process of making the payment for various Testing/Quarantine/ Vaccination. |
|Priority: |High |
|Frequency: |As and when user wants to make the payment. |
|Primary Actor: |Importer/Exporter/Quarantine officer |
|Preconditions: |1. Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |2. Provisional quarantine certificate should be issued to the importer/exporter. |
| |3. Actor should have received the information from quarantine office regarding making the payment either in case|
| |of lab testing or for quarantine observation. |
| |5. The person/agency must have Debit/Credit Card/ net banking for online transactions. |
|Basic Flow |1.System will prompt the actor to select one of the option for which he/she want to make the payment: |
| |Pay for Lab testing |
| |Pay for vaccination |
| |Pay for quarantine observation |
| |2. Depending upon the above selected option system will the display the list of record received from AQCS |
| |department using the “Verification & approval / rejection / issuance of provisional AQC” use case. |
| |3.After that actor will select the payment mode: |
| |Online payment:- for online payment, the actor could choose one of following options: |
| | |
| |Internet Banking |
| |Debit Card |
| |Credit Card |
| |The system will navigate actor to the use case payment gateway to make payment online. |
|Alternative Flow: |If actor select the Mode of Payment as Cheque the system will prompt to the specify following details: |
| |Cheque No. |
| |Cheque date |
| |Cheque deposit In: Bank name |
| |If actor select bank, the system will prompt the actor to select the bank name from the drop down enlisting all |
| |the |
| |Central/State/Cooperative/Private bank specified in the database. Select name of the bank in which the Cheque |
| |was deposited. |
| | |
| |If actor selects mode of Payment as DD, the system will prompt to specify following details: |
| |DD issuing bank name |
| |actor select bank, the system will prompt the actor to select the bank name from the drop down enlisting all the|
| |Central/State/Cooperative/Private bank specified in the database. Select name of the bank in which the |
| |Cheque was deposited. |
| |DD No. |
| |DD Date |
| |Payable at: Account Holder name |
| |The system will prompt the actor to specify the Amount of the test fee / vaccination fee / observation fee paid.|
| | |
| |If the actor chooses the Cash mode of Payment he/she would be required to specify the amount only. |
| | |
| |In this use case quarantine officer will update the payment if it is through cash / Cheque / DD. |
| | |
| |Cancel If Actor cancels the form then system will reach at home page. |
| | |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Data shall be saved in the database. |
| |2. Actor shall successfully logout and brought to the Home Page. 3. After issuance of provisional certificate to|
| |livestock, it will be kept under observation for 30 days at quarantine station and importer has to pay fee for |
| |per LS per day for 30 days. |
| | |
| | |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
| | |
Overview: Payment gateway facilitates the actor to deposit there fees through online transactions like internet banking, debit card or credit card. Payment gateway works as a bridge between the sender’s bank account and the recipient bank accounts.
18 PAYMENT GATEWAY
|UC 3.2.1.18 |Payment Gateway |
|Version: |00 |
|Context: |A payment gateway facilitates the transfer of information between a payment portal (such as a website and mobile|
| |phone) and the Front End Processor or acquiring bank. |
|Priority: |High |
|Frequency: |As and when actor wants to make payment |
|Primary Actor(s) |Importer / Exporter |
|Trigger: |The actor selects the option available as select Internet Banking/Debit Card/Credit Card options |
|Pre conditions: |The user must be registered on the AQIS. He must be logged in, and should have permissions to access ISS and |
| |making online payments for various transactional activities. |
| |The person/agency must be registered with their banks for availing online transactions facility. |
| |The person/agency must have Debit/Credit Card for online transactions. |
|Post conditions: |After successful transactions, the system will generate payment receipt details, shown to the actor on the |
| |screen. The actor could print the Payment Receipt. |
| |On successful transactions, the deposited amount should be stored in ISS database. |
|Input: |Debit Card Details |
| |Credit Card Details |
| |Internet Banking Details |
|Output: |Successful Payment Transfer |
|Normal Flow: |Actor Actions |System Responses |
| | | |
| |The actor clicks on the option “Online Payments”. |The System will prompt the actor to specify following |
| | |details to communicate ISS system with the Payment |
| | |Gateway’s API: |
| |The actor may choose one of the following options: |Unique Application id |
| |Save |Amount being Paid |
| |Submit |Applicant Name |
| | |Recipient Account No |
| |Save: The actor may click on the save option to save |Recipient Account Name |
| |the recorded details |The system will navigate the ISS application to the |
| | |selected bank’s Payment Gateway. |
| |Submit: The clicks on the Submit option to finally | |
| |submit details to the bank’s payment gateway. | |
|Alternative Flow: |None |
|Exceptional Flow: |None |
|Includes: | |
|other use case id | |
|UI: required/not required |Required |
|Priority: Low/medium/high |High |
|Frequency of Use: |Medium |
|Continuous/ frequent/ medium/ | |
|less/ rare | |
|Business Rules: |All details are mandatory to specify. |
| |Minimum amount to be specified for transaction must be 1 Rs. |
| |There should be a mechanism to access the API of payment gateway. |
|Exceptions: |None |
|Special Requirements: |None |
|Assumptions: |The actor is registered either on AQIS and access the application/service through single sign on. |
| |Hardware like computer/laptop system and network connection is available to the actor. |
| |The actor is having a valid mobile number. |
| |Actor is having an internet banking access, debit card and credit card |
|Dependency: |None |
|Notes and Issues: |None |
| |. |
19 SAMPLE COLLECTION AND SENDING TO LAB FOR TESTING
|UC 3.2.1.19 |Sample Collection and Sending to Lab for Testing |
|Version: |00 |
|Context: |This use case is to describe the process of sample collection, vaccination and sample sending to lab for testing|
|Priority: |High |
|Frequency: |As an when sample sent to lab for testing. |
|Primary Actor: |Quarantine Officer/ Testing Lab |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Sample taken for lab testing or vaccination |
|Basic Flow |System will prompt the actor to specify the following details: |
| | |
| |Select : Testing or vaccination or both required |
| |If vaccination required( case 1) |
| |System presents the actor an interface to enter details related to vaccination of LS/ Pet Animal |
| |Vaccine name, validity of vaccine, vaccine for “ name of disease” , vaccination done from, veterinary doctor’s |
| |name, veterinary hospital name |
| |Detail of the livestock: Name, tag number, breed, sex, colour, site of vaccination, date of vaccination |
| |Actor will click on the save and submit button |
| |System captures the input and update the database |
| | |
| |In case if testing required( case 2) |
| |Sample Collection |
| | |
| |Actor shall instruct the system for entering sample data. |
| | |
| |System presents the actor with an interface with listing of form with the important fields : |
| |File number, date of sample taken, date of sending, testing for “ name of disease” , AQCS address where sample |
| |taken, quarantine officer’s name, importer name, mobile number of quarantine officer |
| |5.If both testing & vaccination require( in case of LS/Pet Animal) |
| | |
| |6. The user would be required to specify the testing required detail & vaccination required detail. |
| | |
| |The user would be specify the remarks if required. |
| |The actor inputs all above mentioned details from collected sample. |
| |Actor instructs to save data and reference number is generated. |
| |System captures the input and update the database |
| |Actor shall dispatch the sample to lab. |
| | |
|Alternative Flow: |Invalid Data System will check for any invalid data before saving. If data is not valid, system halts processing|
| |and no data will be saved and system will ask to enter the data again. |
| | |
| |Cancel If Actor cancels the form then system will reach at home page. |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Database is updated and mail trigger to respective person with consolidated information details. |
| |The system shall generate application reference no and thrown a message to the applicant. |
| |Actor can print details reports using system. |
| |Sample send to AQC lab, Bhopal, Madhya Pradesh, in case of import and authorized lab across India in case of |
| |export. |
| |Actor shall successfully logout and brought to the Home Page. |
|Business Rule: | |
|Special Requirements: |Mandatory fields, validation done from client and server both end. |
| |Quarantine officer shall receive the sample report |
|Unresolved Issues: | |
20 RECEIVING SAMPLE AND SENDING REPORT TO QUARANTINE OFFICER
|UC 3.2.1.20 |Receiving Sample and Sending Report to Quarantine Officer |
|Version: |00 |
|Context: |This use case is to describe the process of receiving sample at lab and sending test report to quarantine |
| |officer |
|Priority: |High |
|Frequency: |As and when sample sent to lab for testing |
|Primary Actor: |Testing Lab officer. |
|Preconditions: |Actor shall receive sample data. As when actor login to the application system would show the details of |
| |samples. |
|Basic Flow |1.Actor shall log into his system using use case UC 3.1.2.1 |
| |2.System will display the sample records sent be AQCS officer to the testing lab using use case “Sample |
| |collecting and sending to lab for testing” |
| |3.System will display the records uploaded by the qauarantine officer with the details File number,Date of |
| |Sample taken & date of Sample sending. |
| |4.The actor may choose one record. As the actor select the record the system will diplay the following details. |
| |File number, date of sample taken, date of sending, testing required , AQCS address where sample taken, |
| |quarantine officer’s name, importer name, mobile number of quarantine officer |
| |Detail of the livestock: Name, tag number, breed, sex, colour, site of vaccination, date of vaccination |
| |5.Actor will Accept the sample or either Reject the sample by choosing the respective links availble on the |
| |screen. |
| |6.As an actor accept the sample a “sample registeration number” will be sent to the AQCS officer as well as to |
| |importer. |
| |7.If the actor reject the sample, the rejected sample details will be sent to the AQCS officer. |
|Alternative Flow: |Invalid Data System will check for any invalid data before saving. If data is not valid, system halts processing|
| |and no data will be saved and system will ask to enter the data again. |
| | |
| |Cancel If Actor cancels the form then form will close |
| |Form close if actor clicks on the close button. |
|Post Condition: |Database is updated and mail trigger to respective person with consolidated information details. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
21 SAMPLE TEST RESULT
|UC 3.2.1.21 |Sample Test Result |
|Version: |00 |
|Context: |This use case is to specify the result of tested samples. |
|Priority: |High |
|Frequency: |As and when sample get tested. |
|Primary Actor: |Testing Lab officer. |
|Preconditions: |Actor should have accepted the sample. |
|Basic Flow |1.Actor shall log into his system using use case UC 3.1.2.1 |
| |2. Actor will select the record for which he/she wants to update the test result. |
| |3. System will display the following information in read only mode as specified in the system. |
| |File no., Reference no./ Sample registration number , Nature of sample received. |
| |4.Actor will enter the following details: |
| |Tested code |
| |Test Result |
| | |
| |5.Actor will click on the Save & Subbmit button. |
| |6.The test report result will be available for accessed to the AQCS officer. |
|Alternative Flow: | |
|Post Condition: |1. Database is updated and mail trigger to respective person with consolidated information details. |
| |2. The PDF format will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
|UC 3.2.1.15 |Sample Test Result |
|Version: |00 |
|Context: |This use case is to specify the result of tested samples. |
|Priority: |High |
|Frequency: |As and when sample get tested. |
|Primary Actor: |Testing Lab officer. |
|Preconditions: |Actor should have accepted the sample. |
|Basic Flow |1.Actor shall log into his system using use case UC 3.1.2.1 |
| |2. Actor will select the record for which he/she wants to update the test result. |
| |3. System will display the following information in read only mode as specified in the system. |
| |File no., Reference no. / Sample registration number, Nature of sample received. |
| |4.Actor will enter the following details: |
| |Tested code |
| |Test Result |
| | |
| |5. Actor will click on the Save & Submit button. |
| |6. The test report result will be available for accessed to the AQCS officer. |
|Alternative Flow: | |
|Post Condition: |1. Database is updated and mail trigger to respective person with consolidated information details. |
| |2. The PDF format will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
22 RECEIVING AND VERIFICATION OF TEST REPORT FROM LAB
|UC 3.2.1.22 |Receiving and Verification of Test Report from Lab |
|Version: |00 |
|Context: |This use case is to describe the process of receiving test report from lab. |
|Priority: |High |
|Frequency: |As and when test report received from Lab. |
|Primary Actor: |Quarantine Officer |
|Pre-condition | |
|Basic Flow |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |System will instruct the actor to select the records: |
| |Lab tested / vaccination records |
| |Under observation records. |
| |If actor will select lab tested/vaccination then, System will display the sample records sent be Testing lab |
| |officer to the quarantine officer using use case “Sample test result” |
| |System will display the records uploaded by the testing lab officer with the details File number,reference |
| |number , nature of sample received,Tested,Result. |
| |If actor will select the under observation then, System will dipaly the recods of all the consignment which was |
| |kept under observation by quarantine officer. |
| |If test report result shows negative /observation satisfied, then actor will issue in case of import “Quarantine|
| |clearance certificate “in case of export “Animal quarantine health certificate” by clicking on the link generate|
| |certificate. |
| |If test report result shows positive/ observation not satisfied, then in case of import “ destruction order will|
| |be issued “ in case of export “rejection of consignment” the status of the application will change as |
| |destruction of consignment or rejection of consignment. |
| |The test report result will be available for access to the Importer/Exporter |
|Alternative Flow: |Invalid Data System will check for any invalid data before saving. If data is not valid, system halts processing|
| |and no data will be saved and system will ask to enter the data again. |
| | |
| |Cancel If Actor cancels the form then form will close |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Database is updated and mail trigger to exporter/importer with a copy of certificate |
| |Actor can print certificate/ test repots using system. |
| |Actor shall successfully sent certificates |
| |The PDF will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
23 NPPO ACCESS TO VIEW PSC/AQC
|UC 3.2.1.23 |NPPO Access to View PSC/AQC |
|Version: |00 |
|Context: |This use case explains the process of viewing the PSC/AQS number by NPPO for verification. |
|Priority: |High |
|Frequency: |As and when test report received from Lab. |
|Primary Actor: |NPPO |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |Actor shall log into AQIS application to view AQC over the web using UC 3.1.2.1.and already running application |
| |of PQIS to view PSC. |
| |Actor will click on the link “View PSC/AQC” |
| |System would prompt the user to enter specific details. |
| |PSC/AQC Application Number: |
| | |
| |Actor will click on the “SEARCH” option. |
| |System will fetch the records on the basis of details entered by actor. |
|Alternative Flow: |Invalid Input: If actor enters wrong information of I/E Code, BOS Number, PSC Number then system will display “No|
| |Data Exist”. Actor shall acknowledge the message. System will return back to Pre Condition. |
|Post Condition: |1. Database is updated and mail trigger to exporter/importer with a copy of certificate |
| |Actor can print certificate/ test repots using system. |
| |Actor shall successfully sent certificates |
| |The PDF will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
24 UPDATING REJECTION OF PSC/AQC BY NPPO
|UC 3.2.1.24 |Updating Rejection of PSC/AQC By NPPO |
|Version: |00 |
|Context: |This use case describes the process that how NPPO of other countries gives information of the rejected PSC/AQC. |
|Priority: |High |
|Frequency: |As and when sample get tested. |
|Primary Actor: |NPPO |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Animal Quarantine Certification Station & Plant Quarantine Station would provide the user id & password to other |
| |country NPPO of their application |
|Basic Flow | Actor shall log into AQIS application to update the rejection of AQC over the web using UC 3.1.2.1.and to update|
| |the rejection of PSC log in to already running application PQIS. |
| | |
| |Actor will click on “update remarks” |
| | |
| |System would prompt the user to enter specific details. |
| |Application Number: |
| |Rejection Reason |
| | |
| |Actor will click on the Save & Submit button. |
| |System captures the input and update the database |
| |AQCS Officer / PQIS Officer would view the rejected AQC/PSC by pulling the report from their system. |
|Alternative Flow: | |
|Post Condition: |1. Database is updated and mail trigger to respective person with consolidated information details. |
| |2. The PDF format will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
25 GRIEVANCE MANAGEMENT
|UC 3.2.1.25 |Grievance Management |
|Use Case Name |Capture Grievance Redressal Management System data |
|Actor(s) |Importer/Exporter |
|Description |The grievance management process relates to the capture, processing and answering upon grievances fed into the |
| |system by the Importer/Exporter. |
|Pre Conditions |The Actor should Sign In to PQIS/AQIS applications via CAP. |
| |Actor is registered into PQIS/AQIS portal through user management. |
| |Actor should register his/her grievances with pertaining to his/her application number. |
|Triggers |Actor invokes grievance redressal option presented by the PQIS/AQIS. |
|Basic Flow |Grievance Data Capture |
| |The system presents with an interface on which actor selects the service / grievance from a list of Services for|
| |which he or she has to Register the Grievance against their application number. |
| |When the actor does not see the intended service in the list, ‘Others’ option is selected and on selecting this,|
| |a text area for free text writing is appeared where actor can enter their intended services/grievances. |
| |The actor selects service type from a list option and also fills in an area specified for Summary of the |
| |Grievance that he/She is willing to Register. |
| |Other information includes: |
| |Any Wish to receive notification through email or mobile phone |
| |Mobile number – numeric, optional |
| |Email ID - optional |
| |User instructs to save data into the system. |
| |The system proceeds to save data. Before saving following actions are performed : |
| |Proper area of services is chosen. |
| |Service type is properly mentioned |
| |In case other is mentioned, the detail on this area is specified. |
| |Grievance detail is not blank. |
| |Use case ends. |
|Alternative Flows |A Senior Body will also be provided with the Status of the Grievance, when it has been answered or it is |
| |pending. Depending upon the time duration of answering the queries necessary action will be taken. |
| |Exit condition |
| |Actor chooses to cancel the current operation, the system does not proceed and no data is processed. Use case |
| |ends. |
| |Log out |
| |Actor chooses to log out from the current operation, the interface grievance redressal disappears and no data is|
| |processed. The control goes to the portal home page. Use case ends. |
|Post Conditions |AT BF 1 : |
| |The system processes data, data saved into the backend database. |
| |System generates a Grievance ID and notifies user. Actor will receive a notification in SMS or email about their|
| |grievance acknowledgement. |
| |At AF 2,3 : |
| |Home page is displayed. |
|Exceptions |None |
|Priority |High |
|Business Rules |The PQIS/AQIS shall display Labels/Help text in simple language specific to the practice so that the User does |
| |not find any difficulty in understanding the fields that are to be selected while entering a particular query. |
|Relationships |Extends |
| |Main page of the PQIS/AQIS. |
| |Is Extended By |
| |None. |
| |Uses |
| |Login, if the actor has logged in to the portal. |
| |Id, provided in the previous login, in case the User has already registered a Grievance. |
|Special Requirements |Input can be entered in English. |
| |The reply in the same language in which it will be entered. |
| |The text f grievance is not to exceed 1000 characters. |
26 VIEW GRIEVANCE REDRESSAL
|UC 3.2.1.26 |View Grievance Redressal |
|Actor(s) |Importer/Exporter |
|Description |The grievance management process relates to the viewing the grievances fed into the system by the |
| |importer/exporter |
|Pre Conditions |The Actor has entered the Grievance and has been provided the Grievance id. The Grievance has been sent to the |
| |Elected Body for Review. |
|Triggers |Actor enters the id assigned to him through the PQIS/AQIS. |
|Basic Flow |Grievance View |
| |The system presents with an interface on which actor can enter the Id that was provided earlier on |
| |Registration. |
| |Other information includes: |
| |Any Wish to receive notification through email or mobile phone |
| |Mobile number – numeric, optional |
| |Email ID - optional |
| |User instructs to save data into the system. |
| |The system proceeds to save data. Before saving following actions are performed : |
| |Proper area of services is chosen. |
| |Service type is properly mentioned |
| |In case other is mentioned, the detail on this area is specified. |
| |Grievance detail is not blank. |
| |Use case ends. |
|Alternative Flows |The PQIS/AQIS will also be linked with External Database like the other stake holders like APEDA, EIC & MPEDA |
| |etc. This will assist the importer/exporter. |
| |A Senior Body will also be provided with the Status of the Grievance, when it has been answered or it is |
| |pending. Depending upon the time duration of answering the queries necessary action will be taken. |
| |Exit condition |
| |Actor chooses to cancel the current operation, the system does not proceed and no data is processed. Use case |
| |ends. |
| |Log out |
| |Actor chooses to log out from the current operation, the interface grievance redressal disappears and no data |
| |is processed. The control goes to the portal home page. Use case ends. |
|Post Conditions |AT BF 1 : |
| |The system processes data, data saved into the backend database. |
| |System generates a Grievance ID and notifies user. Actor will receive a notification in SMS or email about |
| |their grievance acknowledgement. |
| |At AF 2,3 : |
| |Home page is displayed. |
|Exceptions |None |
|Priority |High |
|Business Rules |The AQIS/PQIS shall display Labels/Help text in simple language specific to the practice so that the User does |
| |not find any difficulty in understanding the fields that are to be selected while entering a particular query. |
|Relationships |Extends |
| |Main page of the PQIS/AQIS. |
| |Is Extended By |
| |None. |
| |Uses |
| |Login, if the actor has logged in to the portal. |
| |Id, provided in the previous login, in case the User has already registered a Grievance. |
|Special Requirements |Input can be entered in English |
| |The reply in the same language in which it will be entered. |
| |The text for grievance is not to exceed 1000 characters. |
|Assumptions |The query will directly post to PQIS/AQIS portal via CAP. |
27 GRIEVANCE REDRESSAL SYSTEM
|UC 3.2.1.27 |Grievance Redressal System |
|Actor(s) |Nodal Officer |
|Description |This use case would describe the way to address the grievances |
|Pre Conditions |The Actor has entered the Grievance and has been provided the Grievance id. The Grievance has been sent to the |
| |Nodal Officer for Review & redressal |
|Triggers | |
|Basic Flow |Grievance Redressal |
| |The system presents with an interface on which actor click on the grievance redressal system to view the all fed|
| |grievance by the importer/exporter with their application number. |
| |Actor will select one application. |
| |Actor would now put the remark or solution in the TEXT coloum. |
| |Actor would now click on the SAVE & Submit button. remarks is updated in the database. |
| |Messages will trigger to the applicant. |
| |As notification through email or mobile phone |
| |Mobile number – numeric, optional |
| |Email ID - optional |
| |User instructs to save data into the system. |
| |Use case ends. |
|Alternative Flows |The PQIS/AQIS will also be linked with External Database like the other stake holders like APEDA, EIC & MPEDA |
| |etc. This will assist the importer/exporter. |
| |A Senior Body will also be provided with the Status of the Grievance, when it has been answered or it is |
| |pending. Depending upon the time duration of answering the queries necessary action will be taken. |
| |Exit condition |
| |Actor chooses to cancel the current operation, the system does not proceed and no data is processed. Use case |
| |ends. |
| |Log out |
| |Actor chooses to log out from the current operation, the interface grievance redressal disappears and no data is|
| |processed. The control goes to the portal home page. Use case ends. |
|Post Conditions |AT BF 1 : |
| |The system processes data, data saved into the backend database. |
| |System generates a Grievance ID and notifies user. Actor will receive a notification in SMS or email about their|
| |grievance acknowledgement. |
| |At AF 2,3 : |
| |Home page is displayed. |
|Exceptions |None |
|Priority |High |
|Business Rules |The AQIS/PQIS shall display Labels/Help text in simple language specific to the practice so that the User does |
| |not find any difficulty in understanding the fields that are to be selected while answering a particular query. |
|Relationships |Extends |
| |Main page of the PQIS/AQIS. |
| |Is Extended By |
| |None. |
| |Uses |
| |Login, if the actor has logged in to the portal. |
| |Id, provided in the previous login, in case the User has already registered a Grievance. |
|Special Requirements |Input can be entered in English |
| |The reply in the same language in which it will be entered. |
| |The text for grievance is not to exceed 1000 characters. |
|Assumptions |The query will directly post to PQIS/AQIS portal via CAP. |
28 MIS REPORT
|UC 3.2.1.28 |MIS Report |
|Version: |00 |
|Context: |This use case is for generation of MIS report from master table which will be sent to higher authority for |
| |decision making. |
|Priority: |HIGH |
|Frequency: |Frequent |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow: |System presents the Actor list of master tables with the option of select |
| |System presents a list of master table to actor. Actor shall select one, two or all of the tables from the master |
| |table given below: |
| |Application Status(Issued/Pending) |
| |Country wise report for AQS |
| |Pending Report for SIP |
| |Date of Application |
| |Location of Applying Certification |
| |Country of Import/Export |
| |Approving Authority |
| |Validity of Certificate |
| |List of stakeholders |
| |Type of Applicant (Importer/Exporter) |
| |State |
| |District |
| |Location for Issuing Certificate |
| |ITC (HS) Code |
| |Purpose of Lab Testing samples (Import/Export) |
| |Lab Test Name |
| |Tenders |
| |List of restricted or free Livestock/Livestock Product |
| |List of Livestock/Livestock Product refused registration |
| |List of designated inspectors |
| |List of vaccination/ Disease/ Test |
| |List of AQCS issuing public officers |
| |Actor shall view/print the detail data of the selected table(s) from the master table. |
| |If Actor shall instruct to add/delete tables in the report. |
| |Actor checks the particular table to be added/ deleted and presses add/delete. |
| |System shows the table contents with add/delete access. |
| |Add/Delete table in the report. |
| |Actor shall instruct to add/delete the table in the MIS report. |
| |The Use Case Ends. |
|Alternative Flow: | |
|Post Condition: |Tables should be updated. |
| |Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before view the forms details. And if found then |
| |display the alert messages corresponding to related field. |
| |Cancel If Actor cancels the form then system will reach at home page. |
| |Duplicate Entry: System shall check at the time of updating data, there shall exist same data in the table. If |
| |same data does not exist in database then the System displays a message “data changed.” |
|Special Requirements: |Mandatory fields, validation done from client and server both end. |
|Business Requirement | |
|Unresolved Issues: | |
29 MASTER DATA MANAGEMENT
|UC 3.2.1.29 |Master Data Management |
|Version: |00 |
|Context: |This use case is for adding, editing or deleting contents from master table |
|Priority: |HIGH |
|Frequency: |Frequent |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow: |System presents the Actor list of master tables with the option of add, edit and delete |
| |If Actor shall instruct to add the master table. |
| |• Will add a master table (if there is any feature updated to the application in future then the master table to be|
| |created for support) |
| |System presents a list of master table to actor. Actor shall select the one of the master table from the below |
| |given list: |
| |Approving Authority |
| |Registration Agency |
| |Validity of Certificate |
| |Type of Certificate (SIP,AQC) |
| |Licensing Issuing Agencies |
| |Type of inputs |
| |Product Code – input Wise |
| |List of stakeholders |
| |Type of Applicant (Importer/Exporter) |
| |State |
| |District |
| |Location for Issuing Certificate |
| |ITC (HS) Code |
| |Office Type |
| |Office Details |
| |Block |
| |Local Body Code |
| |Designation |
| |Certificate Format |
| |Fee Criteria |
| |Fee Structure |
| |Home Page Information |
| |Purpose of Lab Testing samples (Import/Export) |
| |Lab Test Name |
| |Certified Parameters for quality testing |
| |Purpose of Issuing Certificate |
| |Importer & Exporter for e- certification |
| |Tenders |
| |List of restricted or free Livestock/Livestock Product |
| |List of Livestock/Livestock Product refused registration |
| |List of designated inspectors |
| |List of vaccination/ Disease/ Test |
| |Disease Category |
| |List of AQCS issuing public officers |
| |Laws |
| |Standards |
| |Notify point of entry |
| |List of Country |
| |Actor shall enter the details as per provided fields and instruct to save the data. |
| |If Actor shall instruct to edit the master table. |
| |Actor checks the particular table to be edited and presses edit. |
| |System shows the table contents with editable access. |
| |Edits the content (Add/Modify). |
| |Actor shall instruct to update the table. |
| |The Use Case Ends. |
|Alternative Flow: | |
|Post Condition: |Tables should be updated. |
| |Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before save the forms details. And if found then |
| |display the alert messages corresponding to related field. |
| |Cancel If Actor cancels the form then system will reach at home page. |
| |Duplicate Entry: System shall check at the time of updating data, there shall not exist same data in the table. If |
| |same data is exist in database then the System displays a message “Duplicate data not allowed.” |
|Special Requirements: |Mandatory fields, validation done from client and server both end. |
|Business Requirement | |
|Unresolved Issues: | |
2 FAQ
• View Manage FAQ Page • Manage FAQ (View/ Create/Modify/Delete) • View Manage FAQ Category Page • Manage FAQ Category (View/ Create/Modify/Delete)
[pic] Diagram 31: FAQ Use Cases
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.2.2.1 |View Manage FAQ Page |This use case is used to view |Actor with the Assigned role of FAQ Manager |
| | |manage FAQ page | |
|UC 3.2.2.2 |View FAQ |This use case is used to view |Importer/Exporter/General users/FAQ Manager |
| | |FAQ page | |
|UC 3.2.2.3 |Add FAQ |This use case is used to add FAQ|Actor with the Assigned role of FAQ Manager |
|UC 3.2.2.4 |Modify FAQ |This use case is used to modify |Actor with the Assigned privilege of FAQ Manager |
| | |FAQ | |
|UC 3.2.2.5 |Delete FAQ |This use case is used to delete |Actor with the Assigned privilege of FAQ Manager |
| | |FAQ | |
|UC 3.2.2.6 |View FAQ Category |This use case is used to view |Actor with the Assigned privilege of FAQ Category|
| | |FAQ Category |Manager |
|UC 3.2.2.7 |Add FAQ Category |This use case is used to add FAQ|Actor with the Assigned privilege of FAQ Category|
| | |Category |Manager |
|UC 3.2.2.8 |Modify FAQ Category |This use case is used to modify |Actor with the Assigned privilege of FAQ Category|
| | |FAQ Category |Manager |
|UC 3.2.2.9 |Delete FAQ Category |This use case is used to delete |Actor with the Assigned privilege of FAQ Category|
| | |FAQ Category |Manager |
1 VIEW MANAGE FAQ PAGE
|UC 3.2.2.1 |View Manage FAQ Page |
|Version: |00 |
|Context: |This use case would allow the actor to manage FAQ in the system. The FAQ will be related to a FAQ category in |
| |the specific AQIS application. |
| | |
| |Actor would have the following options under Manage FAQ: |
| |Manage FAQ/Queries: |
| |• View FAQ |
| |• Add FAQ |
| |• Modify FAQ |
| |• Delete FAQ |
| |• Answer Queries |
| |Manage FAQ Categories: |
| |• View FAQ Category |
| |• Add FAQ Category |
| |• Modify FAQ Category |
| |• Delete FAQ Category |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned role of FAQ Manager |
|Preconditions: |User must be registered at AQIS via CAP. |
| |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |User should be authenticated by system and set his/her states as Login. |
|Basic Flow: |1. The actor instructs the system to “Manage FAQ”. |
| |2. System presents an interface with following options: |
| |a. Manage FAQ/Queries: |
| |View FAQ |
| |Add FAQ |
| |Modify FAQ |
| |Delete FAQ |
| |Answer Queries |
| | |
| |b. Manage FAQ Categories: |
| |View FAQ Category |
| |Add FAQ Category |
| |Modify FAQ Category |
| |Delete FAQ Category |
| |3. Actor instructs to close the link. |
| |4. System will close the form. |
| | |
| |The use case ends. |
|Alternative Flow: |Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |Actor successfully views the Manage FAQ page. |
| |If the actor clicks the Close link, then the system would respond with the message, “Do you wish to close the |
| |form? If the Actor confirms, then system would close the form and the actor would be brought back to Main |
| |Screen; otherwise, the actor would be brought back to where the actor was before clicking the Close link. |
|Special Requirements: | |
|Business Rules | |
|Dependency |Extends |
| |View AQIS application |
| |or |
| |View AQIS application |
| |Is Extended By |
| |1. View FAQ |
| |2. Add FAQ |
| |3. Modify FAQ |
| |4. Delete FAQ |
| |5. Answer Queries |
| |6. View FAQ Category |
| |7. Add FAQ Category |
| |8. Modify FAQ Category |
| |9. Delete FAQ Category |
| | |
| |Uses |
| |Login |
2 VIEW FAQ
Overview: The Frequently Asked Questions and their answers will be published on the Homepage of the service and the AQIS. The Importer/Exporter can find the answers of their questions related to different sub-services/subjects in the View FAQ section of the Home Page or they can submit new query by clicking on the available link.
|UC 3.2.2.2 |View FAQ |
|Version: |00 |
|Context: |This use case would allow the actor to view FAQ list. |
| |In case actor is FAQ Manager, he/she would be able to do the following activities: |
| |• Add FAQ |
| |• Modify FAQ |
| |• Delete FAQ |
| |• View Query Responses |
| |In this, Importer/Exporter would be able to submit their queries related to any service/sub service/subject. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Importer/Exporter /FAQ Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |User should be authenticated by system and set his/her states as Login. |
| |Actor is viewing the FAQ list. |
| |Or in case actor is FAQ manager, he/she will be viewing the FAQ list and would be having the option to add an |
| |FAQ, modify or delete an FAQ. |
|Basic Flow: |1. General users is viewing the FAQ list on the Service Home Page/ AQIS |
| |2. System would display the list of FAQ on the screen, with each question displayed as hyperlink |
| |3. Actor clicks on the question hyperlink |
| |4. System displays the answers of the questions specified by the FAQ Manager in the System |
| |5. Similarly each question in the FAQ list can be clicked by the actor to view the answer as required by |
| |him/her. |
| |6. Actor may also add a new Query, if it is not available in the FAQ list by clicking on the Add New Query link.|
| |Refer Add New Query use case. |
| | |
| |The use case ends. |
|Alternative Flow: |FAQ manager or actor is logged in and is viewing the FAQ list: |
| |System would display the list of FAQ on the screen, with each question displayed as hyperlink. |
| |The actor clicks on the question hyperlink to view the answer of the question. |
| |Actor can also choose to Modify FAQ or Delete FAQ displayed on the list. |
| |Actor may Add FAQ in the list. |
|Post Condition: |Actor successfully views the View FAQ list on the AQIS portal or specific AQIS Service/ application. |
| |Added FAQ by the Citizen actor will be forwarded to the respective service/sub service/subject matter expert for|
| |giving responses and an e-mail will also be thrown to the subject matter expert’s registered e-mail address. |
| |An FAQ reference number will be generated by the System and an SMS will be delivered on the Importer/Exporter & |
| |General users registered mobile number |
| |The replied FAQs will be added to the database and will be displayed on the View FAQ Page. |
|Special Requirements: | |
|Business Rules |In case user is viewing the FAQ through AQIS portal, only FAQs of the available AQIS service/sub service to the |
| |user (i.e. as per his/her user privileges) would be available for managing in the list. |
| |In case user is viewing the FAQ list through the specific AQIS application, then FAQ of only that AQIS |
| |service/sub service would be displayed to him/her. |
| |FAQ manager of specific AQIS service/sub service should be able to View/Add/Modify/Delete FAQ of his/her |
| |respective AQIS service/sub service. |
| |While FAQ manager of AQIS portal should be able to View/ Add/Modify/Delete FAQ of all AQIS service/sub service. |
|Dependency |Extends |
| |View Manage FAQ list |
| |Is Extended By |
| |1. Add FAQ |
| |2. Modify FAQ |
| |3. Delete FAQ |
| |4. Add New Query |
| |Uses |
| |Login |
3 ADD FAQ
Overview: The System provides a provision to the actor to add FAQs. Similarly citizens like farmer will have the provision to add FAQs.
|UC 3.2.2.3 |Add FAQ |
|Version: |00 |
|Context: |This use case allow actor to Add FAQ in the system. |
| |FAQ would be added under a specific AQIS Service/Sub Service and under a specific FAQ Category. Refer Add FAQ |
| |category use case. |
| |FAQ once added would be available to the General users for viewing and to FAQ manager for further modification |
| |and deletion. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned role of FAQ Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ manager. |
| |Actor is viewing the Manage FAQ list and clicks on Add FAQ. |
|Basic Flow: |The Actor shall instruct to Add FAQ. |
| |System captures the following mandatory parameters to add a new FAQ : |
| |AQIS application/ SIP Sub Service name – Actor selects the AQIS application/ SIP Sub service name from the drop |
| |box list of AQiS application names/ SIP sub services names under which FAQ is to be added |
| |FAQ Category - Actor selects the desired FAQ category from the system provided drop box list of available FAQ |
| |category. |
| |FAQ text – Actor enters the question text of the FAQ Text. |
| |FAQ Answer Text - Actor enters the answer text of the FAQ. |
| |The actor could either Save or publish the data. |
| |If Actor shall instruct to save data. |
| |The System responds with the message,” FAQ was successfully added in the system.” |
| |If Actor shall instruct to publish link |
| |The data will be saved in the database and would be displayed in the View FAQ list on the AQIS/Service Home |
| |Page. |
| |The use case ends. |
|Alternative Flow: |Actor is answering a query through Answer Query Use case and chooses to Add the query to the FAQ list: |
| |System captures the 1a and 1b of the normal flow steps and |
| |adds the query answered by him/her in the system as the FAQ. |
| |Refer Answer Query Use Case. |
| |Actor attempts to submit without selecting the ‘AQIS/SIP Service/Sub service name’: |
| |System displays the message “Please select the AQIS/SIP Service/Sub Service name”. |
| |Actor attempts to submit without selecting the ‘FAQ Category’: |
| |System displays the message “Please select the FAQ category”. |
| |Actor attempts to submit without entering the ‘FAQ text’ |
| |System displays the message “Please enter value in FAQ text.” |
| |Actor attempts to submit without entering the ‘FAQ Answer text’ |
| |System displays the message “Please enter value in FAQ Answer text.” |
|Post Condition: |Actor successfully Add the FAQ on the specific AQIS/SIP |
| |Service/Sub service and specific FAQ category. |
| |Successfully Published FAQ would be available to the |
| |General Citizen for viewing and to the FAQ manager of the |
| |respective AQIS Service/ Sub service and AQIS portal. |
| |Only Saved FAQs will be available for further modification |
| |and deletion. |
| | |
|Special Requirements: | |
|Business Rules |All AQIS/SIP Service/Sub Service names would be available in the drop box. |
| |All FAQ category names as available in the system would be available in the FAQ category name drop box. |
| |Depending upon the selected Service/Sub service, the FAQ Category name drop box values would be displayed. |
| |FAQ manager of specific Service/Sub service should be able to Add/modify/delete FAQ of his/her respective |
| |Service/Sub service. |
| |Authorized actor will be allowed to publish the FAQs. |
| |While FAQ manager of AQIS portal should be able to Add/modify/delete FAQ of any AQIS Service/Sub service. |
|Dependency |Extends |
| |View Manage FAQ Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
4 MODIFY FAQ
Overview: The System provides a provision to the actor to add FAQs. Similarly citizens like farmer will have the provision to add FAQs.
|UC 3.2.2.4 |Modify FAQ |
|Version: |00 |
|Context: |This use case allows actor to Modify a FAQ available in the system. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ manager. |
| |Actor is viewing the Manage FAQ list and clicks on Modify FAQ. |
|Basic Flow: |1. The Actor shall instruct to Manage FAQ. |
| |2 System would allow actor to modify the following mandatory parameters, as added by the actor while adding the |
| |new FAQ. Refer Add FAQ use case: |
| |a. AQIS Service/Sub Service name |
| |b. FAQ Category |
| |c. FAQ text |
| |d. FAQ Answer Text3. The actor could either Save or publish the data. |
| |4. If Actor shall instruct to save data. |
| |The System responds with the message,” FAQ was successfully added in the system.” |
| |5. If Actor shall instruct to publish link |
| |The data will be saved in the database and would be displayed in the View FAQ list on the AQIS/Service Home |
| |Page. |
| |The use case ends. |
|Alternative Flow: |1. No FAQ available in the system: |
| |System displays the message as “Currently No FAQ is Available.” |
| |2. Actor attempts to submit without selecting the ‘AQIS Service/Sub service name’: |
| |System displays the message “Please select the AQIS Service/Sub Service name”. |
| |3. Actor attempts to submit without selecting the ‘FAQ Category’: |
| |System displays the message “Please select the FAQ category”. |
| |Actor attempts to submit without entering the ‘FAQ text’ |
| |System displays the message “Please enter value in FAQ text.” |
| |Actor attempts to submit without entering the ‘FAQ Answer text’ |
| |System displays the message “Please enter value in FAQ Answer text.” |
|Post Condition: |Actor successfully modifies the FAQ. |
| |Successfully Modified and Published FAQ would be available to the General users for viewing and to the FAQ |
| |manager of respective SAP Service/Sub service and AQIS portal for further modification and deletion. |
|Special Requirements: | |
|Business Rules |All red asterisk mark fields are mandatory to specify. |
| |Service/Sub Service names would be available in the drop box. |
| |All FAQ category names as available in the system would be available in the FAQ category name drop box. |
| |Depending upon the selected Service/Sub Service, the FAQ Category name drop box values would be displayed. |
| |FAQ manager of specific Service/Sub Service should be able to Add/modify/delete FAQ of his/her respective |
| |Service/Sub Service. |
| |While FAQ manager of AQIS portal should be able to Add/modify/delete FAQ of any AQIS application. |
|Dependency |Extends |
| |View Manage FAQ Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
5 DELETE FAQ
Overview: The System provides a provision to the actor to delete existing FAQs.
|UC 3.2.2.5 |Delete FAQ |
|Version: |00 |
|Context: |This use case allows actor to Delete a FAQ available in the system. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ manager. |
| |Actor is viewing the Manage FAQ list and clicks on Delete FAQ. |
|Basic Flow: |1. The Actor shall instruct to Delete FAQ. |
| |System displays the confirmation message “Do really wish to Delete this FAQ?” with yes or no option. In case |
| |actor selects yes, system deletes the FAQ and displays the message “FAQ was successfully deleted.” In case actor|
| |selects No, system returns to the pre condition. |
| |The use case ends. |
|Alternative Flow: |1. No FAQ available in the system: |
| |System displays the message as “Currently No FAQ is Available.” |
|Post Condition: |Actor successfully deletes the FAQ. |
| |Successfully Deleted FAQ is removed from FAQ List as available on View FAQ list page |
|Special Requirements: | |
|Business Rules |FAQ manager of specific Service/Sub service should be able to delete FAQ of his/her respective |
| |service/sub-service. |
| |While FAQ manager of AQIS portal should be able to delete saved FAQ of any AQIS service/sub service. |
| |To delete a published FAQ, actor should un-publish that record and then delete it. |
| |If the FAQ added by the citizen/farmer is still pending to the expert advisor for its acceptance or rejection, |
| |it’ll not be allowed to be deleted. |
|Dependency |Extends |
| |View Manage FAQ Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
6 VIEW FAQ CATEGORY
Overview: The System provides a provision to the actor to View FAQ Categories existing FAQs.
|UC 3.2.2.6 |View FAQ Category |
|Version: |00 |
|Context: |This use case would allow the actor to view FAQ Category list. |
| |In actor would be able to do the following activities: |
| |• View FAQ Category |
| |• Add FAQ Category |
| |• Modify FAQ Category |
| |• Delete FAQ Category |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Category Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| | |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ Category manager. |
| |Actor is viewing the Manage FAQ list and clicks on View FAQ Category List. |
|Basic Flow: |1. Actor chooses to View FAQ Category List. |
| |2. System would display the list of FAQ Category on the screen. |
| |3. Actor can choose to : |
| |View FAQ Category |
| |Add FAQ Category |
| |Modify FAQ Category |
| |Delete FAQ Category |
| |The use case ends. |
|Alternative Flow: |No FAQ Category is available in the system, |
| |System displays the message as “Currently No FAQ Category is Available.” |
|Post Condition: |1. Actor successfully views the View FAQ Category list on the AQIS portal or specific Service/Sub Service. |
|Special Requirements: | |
|Business Rules |FAQ Category manager of specific Service/Sub service should be able to View FAQ Category list of his/her |
| |respective service/sub service. |
| |While FAQ Category manager of AQIS portal should be able to View FAQ Category list belonging to all AQIS |
| |services/ applications. |
|Dependency |Extends |
| |View Manage FAQ page |
| |Is Extended By |
| |1. View FAQ Category |
| |2. Add FAQ Category |
| |3. Modify FAQ Category |
| |4. Delete FAQ Category |
| |Uses |
| |Login |
7 ADD FAQ CATEGORY
Overview: The System provides a provision to the actor to Add FAQ Categories existing FAQs.
|UC 3.2.2.7 |Add FAQ Category |
|Version: |00 |
|Context: |This use case allows actor to Add FAQ Category in the system. |
| |FAQ Category would be added under a specific AQIS Service/Sub Service. |
| |FAQ category once added would be available to the FAQ manager while adding new FAQ in the system. Refer Add FAQ.|
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Category Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ Category manager. |
| |Actor is viewing the FAQ Category List |
|Basic Flow: |1. The Actor shall instruct to Add FAQ Category. |
| |2. System captures the following mandatory parameters to add a new FAQ Category : |
| |a. AQIS Service/Sub Service name – Actor selects the service/ sub service name from the drop box list of |
| |services/sub services names under which FAQ Category would be added. |
| |b. FAQ Category Name - Actor enters the FAQ category name to be added in the system. |
| |c. FAQ Recipient email(s) – Actor enters the email(s) of the officials to whom the email should be triggered by |
| |the system in case query against them which would be added by the general Citizen on the AQIS portal or specific|
| |AQIS application. Actor may add more than one email address separating each email id with a comma. Refer Add |
| |Query use case. |
| |4. If Actor shall instruct to save data. |
| |The System responds with the message,” FAQ Category was successfully added in the system.” |
| |The use case ends. |
|Alternative Flow: |1. No FAQ Category is available in the system, |
| |System displays the message as “Currently No FAQ Category is Available.” |
| |2. Actor attempts to submit without selecting the ‘AQIS Service/Sub service name’: |
| |System displays the message “Please select the AQIS Service/Sub Service name”. |
| |3. Actor attempts to submit without selecting the ‘FAQ Category Name’: |
| |System displays the message “Please select the FAQ category Name”. |
| |4. Actor attempts to submit without entering the ‘FAQ Recipient email(s)’: |
| |System displays the message “Please enter value in FAQ Recipient email(s).” |
|Post Condition: |Actor successfully views the View FAQ Category list on the AQIS portal or specific Service/Sub Service. |
|Special Requirements: | |
|Business Rules |FAQ Category manager of specific Service/Sub service should be able to View FAQ Category list of his/her |
| |respective service/sub service. |
| |While FAQ Category manager of AQIS portal should be able to View FAQ Category list belonging to all AQIS |
| |services/ applications. |
|Dependency |Extends |
| |View FAQ Category List |
| |Is Extended By |
| |Add FAQ |
| |Uses |
| |Login |
8 MODIFY FAQ CATEGORY
Overview: The System provides a provision to the actor to add FAQs. Similarly citizens like farmer will have the provision to add FAQs.
|UC 3.2.2.8 |Modify FAQ Category |
|Version: |00 |
|Context: |This use case allows actor to Modify FAQ Category in the system. |
| |FAQ Category would be added under a specific AQIS Service/Sub Service. |
| |FAQ category once modified would be available to the FAQ manager while adding new FAQ in the system. Refer Add |
| |FAQ. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Category Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |This use case allows actor to Modify FAQ Category in the system. |
| |FAQ Category would be added under a specific AQIS Service/Sub Service. |
| |FAQ category once modified would be available to the FAQ manager while adding new FAQ in the system. Refer Add |
| |FAQ. |
|Basic Flow: |1. The Actor shall instruct to Manage FAQ category. |
| |2. System would allow actor to modify the following mandatory parameters, as added by the actor while adding the|
| |new FAQ Category. Refer Add FAQ Category use case: |
| |a. AQIS Service/Sub Service name |
| |b. FAQ Category Name |
| |c. FAQ Recipient email(s) |
| |d. The actor may add more than one email address separating each email id with a comma. Refer Add Query use |
| |case. |
| |4. Actor shall instruct to save data. |
| |The System responds with the message,” FAQ was Category successfully added in the system.” |
| | |
| |The use case ends. |
|Alternative Flow: |1. No FAQ available in the system: |
| |System displays the message as “Currently No FAQ Category is Available.” |
| |2. Actor attempts to submit without selecting the ‘AQIS Service/Sub service name’: |
| |System displays the message “Please select the AQIS Service/Sub Service name”. |
| |3. Actor attempts to submit without selecting the ‘FAQ Category Name’: |
| |System displays the message “Please select the FAQ category Name”. |
| |Actor attempts to submit without entering the ‘FAQ Recipient email(s)’: |
| |System displays the message “Please enter value in FAQ Recipient email(s).” |
| |Actor attempts to modify a FAQ category which has one or more FAQ attached to it: |
| |System displays the warning message “One or more FAQ exists under the selected FAQ category. Do you still wish |
| |to proceed?” System would proceed only on actor’s confirmation. |
|Post Condition: |Actor successfully modifies the FAQ Category under the specific AQIS Service/Sub Service. |
| |Successfully modified FAQ Category would be available in the FAQ category drop box while adding a new FAQ. Refer|
| |Add FAQ use case. |
| |Successfully modified FAQ Category would be available to the respective AQIS Service/Sub Service and AQIS portal|
| |FAQ Category Manager for further modification and deletion. |
|Special Requirements: | |
|Business Rules |FAQ Category manager of specific AQIS Service/Sub Service application should be able to modify FAQ Category |
| |under his/her respective service/sub service only. |
| |While FAQ Category manager of AQIS portal should be able to modify FAQ Category under any AQIS Service/ Sub |
| |service. |
| |The existing FAQ should be automatically remapped with the modified FAQ category. |
|Dependency |Extends |
| |View FAQ Category List |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
9 DELETE FAQ CATEGORY
Overview: The System provides a provision to the actor to Delete FAQ Categories existing FAQs.
|UC 3.2.2.9 |Delete FAQ Category |
|Version: |00 |
|Context: |This use case allows actor to Delete FAQ Category in the system. |
| |FAQ Category would be added under a specific AQIS Service /Sub Service. |
| |FAQ Category once Deleted would be removed from the View FAQ Category list and would not be available to the |
| |citizen to view. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Category Manager |
|Preconditions: |Actor shall log into AQCS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ Category manager. |
| |Actor is viewing the FAQ Category List. |
|Basic Flow: |1. The Actor shall instruct to Delete FAQ Category. |
| |System displays the confirmation message “Do really wish to Delete this FAQ Category?” with yes or no option. In|
| |case actor selects yes, system deletes the FAQ Category and displays the message “FAQ Category was successfully |
| |deleted.” In case actor selects No, system returns to the pre condition. |
| |The use case ends. |
|Alternative Flow: |1. No FAQ available in the system: |
| |System displays the message as “Currently No FAQ is Available.” |
|Post Condition: |Actor successfully deletes the FAQ Category. |
| |Successfully Deleted FAQ Category is removed from FAQ Category List as available on View FAQ Category list page.|
| |FAQ category, under which FAQ has been available in the View FAQ use case, will not be allowed to be deleted. In|
| |this case to delete FAQ category, FAQ under is need to be deleted |
|Special Requirements: | |
|Business Rules |FAQ Category manager of specific AQIS service/sub service should be able to delete FAQ Category as available |
| |under his/her respective service/sub service. |
| |While FAQ Category manager of AQIS portal should be able to delete FAQ Category of any AQIS service/sub service.|
| |System should not allow the deletion of FAQ category which has one or more FAQ attached with it |
|Dependency |Extends |
| |View FAQ Category List |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
3 MASTER USE CASES
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.2.3.1 |Manage Country |This use case is to describe the process to manage|System Administrator |
| | |the Country details | |
|UC 3.2.3.2 |Manage NPPO Details |This use case is to describe the process to manage|System Administrator |
| | |the NPPO details | |
|UC 3.2.3.3 |Manage Departments |This use case is to describe the process to manage|System Administrator |
| | |the Department details | |
|UC 3.2.3.4 |Manage Products |This use case is to describe the process to manage|System Administrator |
| | |the product details | |
|UC 3.2.3.5 |Manage Samples |This use case is to describe the process to manage|System Administrator |
| | |the sample details | |
|UC 3.2.3.6 |Manage Airport Name |This use case is to describe the process to manage|System Administrator |
| | |Airport Name | |
|UC 3.2.3.7 |Manage Seaport Name |This use case is to describe the process to manage|System Administrator |
| | |Seaport Name | |
|UC 3.2.3.8 |Manage Test Details |This use case is to describe the process to manage|System Administrator |
| | |Test Details | |
|UC 3.2.3.9 |Manage Colour Details |This use case is to describe the process to manage|System Administrator |
| | |Colour Details | |
|UC 3.2.3.10 |Manage Animal Category |This use case is to describe the process to manage|System Administrator |
| | |Animal Category | |
|UC 3.2.3.11 |Manage Animal Breed |This use case is to describe the process to manage|System Administrator |
| | |Animal Breed | |
|UC 3.2.3.12 |Manage SIP Condition Product wise |This use case is to describe the process to manage|SIP user with the assigned|
| | |the condition to issue SIP. |privilege to add |
| | | |condition. |
1 MANAGE COUNTRY
|UC 3.2.3.1 |Manage Country |
|Version: |00 |
|Context: |This use case is to describe the process to manage the Country details |
|Priority: |High |
|Frequency: |As and when require |
|Primary Actor(s) |AQIS user with the assigned privilege to add country details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Country->Country |
| |Details. |
|Normal Flow |The System will prompt the actor to specify following country details: |
| |Country Name and Country Code: The actor would select name of the country along with country code being |
| |displayed in the list available for selection. The displayed list will enlist all the Country Names along with |
| |their codes for selection. |
| |The actor could add multiple countries being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected country details. |
| |The actor may click the Edit button to edit the selected country details. |
| |The actor may click the Delete button to delete the selected country details. |
| |The actor may click the View button to view the saved country details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Country Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Country Details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All information related to the country details would be stored in the database with status set to save. |
| |c. The saved country details would be available for further modification through the Modify button. |
| |d. The country details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in|
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank country details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save country details when no country has been selected from the list. |
| |The System would respond with a message, “No country name has been selected. Please select at least one country |
| |to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception occurs |
| |when the actor saves the Country Details without selecting any country. |
| |The actor attempts to edit the country details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the country details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the country details when the country name with the same Country Code already exists |
| |in the System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Country Name and Country Code |
| |System would display a default list of Country Names and Country Codes. |
| |Country Details, which have already been used in the application, should not be available to select for |
| |deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
2 MANAGE NPPO DETAILS
|UC 3.2.3.2 |Manage NPPO Details |
|Version: |00 |
|Context: |This use case is to describe the process to manage the NPPO details |
|Priority: |High |
|Frequency: |Medium |
|Primary Actor(s) |AQIS user with the assigned privilege to manage NPPO details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add NPPO details under the option available in Master Entry -> Manage NPPO details->NPPO |
| |Details. |
|Normal Flow |The System will prompt the actor to specify following details: |
| |NPPO Name: The actor would specify NPPO Name. |
| |NPPO Code: The actor would specify code of the specified NPPO. |
| |The actor could add multiple NPPO details using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the specified NPPO details. |
| |The actor may click the Edit button to edit the selected NPPO details. |
| |The actor may click the Delete button to delete the selected NPPO details. |
| |The actor may click the View button to view the saved NPPO details. |
| |At any point of time, actor clicks the Clear button to discard the details entered till then or clicks the Close|
| |button to close the NPPO Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “NPPO Details saved successfully” and the actor would be brought |
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the NPPO would be stored in the database with status set to save. |
| |c. The saved NPPO details would be available for further modification through the Modify button. |
| |d. The NPPOI details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in|
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank NPPO details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save NPPO details without specifying NPPO Name. |
| |The System would respond with a message, “Please specify NPPO Name”. Click OK to continue. The actor would be |
| |brought back to Pre Condition. The exception occurs when the actor saves the NPPO Details form without NPPO |
| |Name. |
| |The actor attempts to save NPPO details without specifying NPPO Code. |
| |The System would respond with a message, “Please specify NPPO Code”. Click OK to continue. The actor would be |
| |brought back to Pre Condition. The exception occurs when the actor saves the NPPO Details form without |
| |specifying NPPO Code. |
| |The actor attempts to edit the NPPO details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the NPPO details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the NPPO details when the NPPO Code already exists in the System. |
| |The System would respond with the message, “NPPO Details with the same NPPO Code already exists”. |
|Business Rules |Following Fields are mandatory to define:- |
| |NPPO Name |
| |NPPO Code |
| |NPPO Code should be unique within the System. |
| |NPPO Details, which have already been used in the application, should not be available to select for deletion. |
| |Maximum Permissible length for the field NPPO Name should not exceed 75 characters including alphabets (a-z), |
| |numbers (0-9) and special charters & - / () _, *: |
| |Maximum Permissible length for the field NPPO Code should not exceed 20 characters including alphabets (a-z), |
| |numbers (0-9) and special charters & - / () _, * : |
| |The system should restrict the insertion/typing of non-permissible characters. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
3 MANAGE DEPARTMENT
|UC 3.2.3.3 |Manage Department |
|Version: |00 |
|Context: |This use case is to describe the process to manage department name |
|Priority: |High |
|Frequency: |Medium |
|Primary Actor(s) |AQIS user with the assigned privilege to manage department details in the system. |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to specify department details under the option available in Master Entry -> Manage |
| |Department->Department Details. |
|Normal Flow |The System will prompt the actor to specify following details: |
| |Department Name: The actor would specify name of the Dairy/LH/Fishery department. |
| |Department Code: The actor would specify name of the Dairy/LH/Fishery department Code. |
| |The actor could add multiple department names using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the specified department details. |
| |The actor may click the Edit button to edit the selected department name. |
| |The actor may click the Delete button to delete the selected department name. |
| |The actor may click the View button to view the saved department name. |
| |At any point of time, actor clicks the Clear button to discard the details entered till then or clicks the Close|
| |button to close the Department Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Department name saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All specified information related to the department would be stored in database with status set to save. |
| |c. The saved details would be available for further modification through the Modify button. |
| |d. The saved details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in|
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank Department details form; otherwise, |
| |the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save Department details without specifying Department Name. |
| |The System would respond with a message, “Please specify Department Name”. Click OK to continue. The actor would|
| |be brought back to Pre Condition. The exception occurs when the actor saves the Department Details form without |
| |Department Name. |
| |The actor attempts to edit the Department details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the Department details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the Department details when Department Name already exists in the System. |
| |The System would respond with the message, “Department Details with the same Department Name already exists”. |
|Business Rules |Following Fields are mandatory to define:- |
| |Department Name |
| |Department Code |
| |Department Name should be unique within the System. |
| |Department Name, which has already been used in the application, should not be available to select for deletion.|
| |Maximum Permissible length for the field Department Code should not exceed 75 characters including alphabets |
| |(a-z), numbers (0-9) and special charters & - / () _, *: |
| |The system should restrict the insertion/typing of non-permissible characters. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
4 MANAGE PRODUCTS
|UC 3.2.3.4 |Manage Products |
|Version: |00 |
|Context: |This use case is to describe the process to manage the products for the AQIS and SIP. |
|Priority: |High |
|Frequency: |Medium |
|Primary Actor(s) |AQIS user with the assigned privilege to manage product details in the system. |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to specify product details under the option available in Master Entry -> Manage |
| |Products->Product Details. |
|Normal Flow |The System will prompt the actor to specify following details: |
| |Product Name: The actor would specify name of the Product Name. |
| |Sub-Product Name: The actor would specify name of the Sub-Product Name. |
| |Product Category: The actor would select Product Category from the list displaying three categories i.e. |
| |Dairy/LH/Fishery. The actor could select one option from the list. |
| |Product Code: The actor would specify ITC (HS) Code as product code. |
| |Sub-Product Code: The actor would specify ITC (HS) code as product code. |
| |Product Quantity (In KG/TN/MT): The actor would specify quantity of the product. |
| |Unit: The actor would select unit of the quantity from the list enlisting units specified in Manage Unit use |
| |case. |
| |Product Volume (in Cubic): The actor would specify Volume of the product. |
| |The actor could add multiple products using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the specified product details. |
| |The actor may click the Edit button to edit the selected product details. |
| |The actor may click the Delete button to delete the selected product details. |
| |The actor may click the View button to view the saved product details. |
| |At any point of time, actor clicks the Clear button to discard the details entered till then or clicks the Close|
| |button to close the Product Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Product details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All specified information related to the product would be stored in database with status set to save. |
| |c. The saved details would be available for further modification through the Modify button. |
| |d. The saved details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in|
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank Product details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save Product details without specifying any of the mandatory fields like Product Name, |
| |Product Code, Product Category, Product Quantity etc. |
| |Corresponding to the unspecified field, the System would respond with a message, “Please specify Product Name”. |
| |Or |
| |“Please specify Sub-Product Name”. |
| |Or |
| |“Please specify Product Code”. |
| |Or |
| |“Please specify Sub-Product Code”. |
| |Or |
| |“Please specify Product Category”. |
| |Or |
| |“Please specify Product Quantity”. |
| |The actor attempts to save Product details without specifying Product Name. |
| |The System would respond with a message, “Please specify Product Name”. Click OK to continue. The actor would be|
| |brought back to Pre Condition. The exception occurs when the actor saves the Product Details form without |
| |specifying Product Name. |
| |The actor attempts to edit Product details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete Product details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save Product details when Product Code already exists in the System. |
| |The System would respond with the message, “Product Details with the same Product Code already exists”. |
|Business Rules |Following Fields are mandatory to define:- |
| |Product Name |
| |Sub-Product Name |
| |Product Code |
| |Product Sub-Code |
| |Product Category |
| |Product Quantity |
| |Product Code should be unique within the System. |
| |Product details, which have already been used in the application, should not be available to select for |
| |deletion. |
| |Maximum Permissible length for the field Product Name should not exceed 75 characters including alphabets (a-z),|
| |numbers (0-9) and special charters & - / () _, *: |
| |The system should restrict the insertion/typing of non-permissible characters. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
5 MANAGE SAMPLES
|UC 3.2.3.5 |Manage Samples |
|Version: |00 |
|Context: |This use case is to manage samples taken for testing |
|Priority: |High |
|Frequency: |Medium |
|Primary Actor(s) |AQIS user with the assigned privilege to manage sample details in the system. |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to specify sample details under the option available in Master Entry -> Manage |
| |Samples->Sample Details. |
|Normal Flow |The System will prompt the actor to specify following details: |
| |Sample Code: The actor would code of the sample. |
| |Sample Description: The actor would specify sample description, if any. |
| |Product Category: The actor would select product category of the sample drawn from the list enlisting product |
| |categories specified in product category master. |
| |Product Code: Depending on the selected product category, the actor would select product code from the list |
| |enlisting product codes. |
| |Product Sub-Code: Depending on the selected product, the actor would select Sub-product code from the list |
| |enlisting product codes. |
| |The actor could add multiple samples using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the specified sample details. |
| |The actor may click the Edit button to edit the selected sample details. |
| |The actor may click the Delete button to delete the selected sample details. |
| |The actor may click the View button to view the saved sample details. |
| |At any point of time, actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Sample Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Sample details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All specified information related to the product would be stored in database with status set to save. |
| |c. The saved details would be available for further modification through the Modify button. |
| |d. The saved details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered |
| |in the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the |
| |System would clear the form details and the actor would be presented with a blank Sample details form; |
| |otherwise, the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save Product details without specifying any of the mandatory fields like Sample Code, |
| |Sample Description, Product Category, Product Code etc. |
| |Corresponding to the unspecified field, the System would respond with a message, “Please specify Sample Code”. |
| |Or |
| |“Please specify Sample Description”. |
| |Or |
| |“Please specify Product Code”. |
| |Or |
| |“Please specify Sub-Product Code”. |
| |Or |
| |“Please specify Product Category”. |
| | |
| |The actor attempts to save Sample details without specifying Sample Code. |
| |The System would respond with a message, “Please specify Sample Code”. Click OK to continue. The actor would be|
| |brought back to Pre Condition. The exception occurs when the actor saves Sample Details form without specifying|
| |Sample Code. |
| |The actor attempts to save Sample details without specifying Sample Description. |
| |The System would respond with a message, “Please specify Sample Description”. Click OK to continue. The actor |
| |would be brought back to Pre Condition. The exception occurs when the actor saves Sample Details form without |
| |specifying Sample Description. |
| |The actor attempts to save Sample details without specifying Product Category. |
| |The System would respond with a message, “Please specify Product Category”. Click OK to continue. The actor |
| |would be brought back to Pre Condition. The exception occurs when the actor saves Sample Details form without |
| |specifying Product Category. |
| |The actor attempts to save Sample details without specifying Product Code. |
| |The System would respond with a message, “Please specify Product Code”. Click OK to continue. The actor would |
| |be brought back to Pre Condition. The exception occurs when the actor saves Sample Details form without |
| |specifying Product Code. |
| |The actor attempts to edit Sample details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete Sample details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save Sample details when Sample Code already exists in the System. |
| |The System would respond with the message, “Sample Details with the same Sample Code already exists”. |
|Business Rules |Following Fields are mandatory to define:- |
| |Sample Code |
| |Sample Description |
| |Product Category |
| |Product Code |
| |Sub- Product Code |
| |Sample Code should be unique within the System. |
| |Sample details, which have already been used in the application, should not be available to select for |
| |deletion. |
| |Maximum Permissible length for the field Sample Code should not exceed 15 characters including alphabets (a-z),|
| |numbers (0-9) and special charters & - / () _, *: |
| |Maximum Permissible length for the field Sample Description should not exceed 150 characters including |
| |alphabets (a-z), numbers (0-9) and special charters & - / () _, *: |
| |The system should restrict the insertion/typing of non-permissible characters. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
6 MANAGING AIRPORT NAME
|UC 3.2.3.6 |Manage Airport Name |
|Version: |00 |
|Context: |This use case is for managing Airport Name |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add Airport name details. |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS/SIP application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add airport details under the option available in Master Entry -> Manage airport |
| |detail->airport name Details. |
|Normal Flow |The System will prompt the actor to specify following airport details: |
| |Airport Name and Airport Code: The actor would select name of the airport along with airport code being displayed|
| |in the list available for selection. The displayed list will enlist all the Airport Names along with their codes |
| |for selection. |
| |The actor could add multiple airports name & code being required to deal with AQIS application using “Add More” |
| |button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected airport name & code details. |
| |The actor may click the Edit button to edit the selected airport name & code details. |
| |The actor may click the Delete button to delete the selected airport name & code details. |
| |The actor may click the View button to view the saved airport name & code details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Airport Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Airport Details saved successfully” and the actor would be brought|
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the Airport details would be stored in the database with status set to save. |
| |c. The saved airport details would be available for further modification through the Modify button. |
| |d. The airport details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank airport name details form; otherwise, |
| |the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details|
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save airport name & code details when no airport name & code has been selected from the |
| |list. |
| |The System would respond with a message, “No airport name has been selected. Please select at least one airport |
| |name to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception |
| |occurs when the actor saves the airport name Details without selecting any airport. |
| |The actor attempts to edit the airport name & code details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the airport name & code details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the airport name & code details when the airport name with the same airport Code |
| |already exists in the System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |airport Name and airport Code |
| |System would display a default list of Airport Names and Airport Codes. |
| |Airport name Details, which have already been used in the application, should not be available to select for |
| |deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
7 MANAGE SEAPORT NAME
|UC 3.2.3.7 |Manage Sea Port Name |
|Version: |00 |
|Context: |This use case is for managing Seaport Name |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add sea port details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Sea Port->Sea |
| |port Details. |
|Normal Flow |The System will prompt the actor to specify following country details: |
| |Sea Port Name and Sea Port Code: The actor would select name of the sea port along with sea port code being |
| |displayed in the list available for selection. The displayed list will enlist all the Sea Port Names along with|
| |their codes for selection. |
| |The actor could add multiple sea port being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected sea port details. |
| |The actor may click the Edit button to edit the selected sea port details. |
| |The actor may click the Delete button to delete the selected sea port details. |
| |The actor may click the View button to view the saved sea port details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Sea port Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Sea Port Details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All information related to the sea port details would be stored in the database with status set to save. |
| |c. The saved sea port details would be available for further modification through the Modify button. |
| |d. The sea port details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered |
| |in the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the |
| |System would clear the form details and the actor would be presented with a blank seaport details form; |
| |otherwise, the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save sea port details when no sea port name has been selected from the list. |
| |The System would respond with a message, “No country name has been selected. Please select at least one country|
| |to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception occurs |
| |when the actor saves the Country Details without selecting any country. |
| |The actor attempts to edit the sea port name details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the sea port details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the Sea Port details when the sea port name with the same Sea port Code already |
| |exists in the System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |(a)Sea Port Name and Sea port Code |
| |2. System would display a default list of Sea Port Names and Sea Port Codes. |
| |3. Sea Port Details, which have already been used in the application, should not be available to select for |
| |deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
8 MANAGING TEST DETAILS
|UC 3.2.3.8 |Managing Test Details |
|Version: |00 |
|Context: |This use case is for managing Test Details |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add test details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Test->Test |
| |Details. |
|Normal Flow |The System will prompt the actor to specify following country details: |
| |Test Name and Test Code: The actor would select name of the Test along with Test code being displayed in the |
| |list available for selection. The displayed list will enlist all the Test Names along with their codes for |
| |selection. |
| |The actor could add multiple Test being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected Test details. |
| |The actor may click the Edit button to edit the selected Test details. |
| |The actor may click the Delete button to delete the selected Test details. |
| |The actor may click the View button to view the saved Test details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the|
| |Close button to close the Test Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Test Details saved successfully” and the actor would be brought|
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the test details would be stored in the database with status set to save. |
| |c. The saved test details would be available for further modification through the Modify button. |
| |d. The test details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered |
| |in the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the |
| |System would clear the form details and the actor would be presented with a blank country details form; |
| |otherwise, the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save test details when no test has been selected from the list. |
| |The System would respond with a message, “No test name has been selected. Please select at least one test to |
| |save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception occurs |
| |when the actor saves the Country Details without selecting any test. |
| |The actor attempts to edit the test details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the test details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the test details when the test name with the same test Code already exists in the |
| |System. |
| |The System would respond with the message, “Test Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Test Name and Test Code |
| |System would display a default list of Test Names and Test Codes. |
| |Test Details, which have already been used in the application, should not be available to select for deletion.|
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
9 MANAGE COLOUR DETAILS
|UC 3.2.3.9 |Manage Colour details |
|Version: |00 |
|Context: |This use case is for managing Colour Details |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add colour details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Colour->Colour |
| |Details. |
|Normal Flow |The System will prompt the actor to specify following colour details: |
| |Colour Name and Colour Code: The actor would select name of the colour along with colour code being displayed in |
| |the list available for selection. The displayed list will enlist all the colour Names along with their codes for |
| |selection. |
| |The actor could add multiple colours being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected colour details. |
| |The actor may click the Edit button to edit the selected colour details. |
| |The actor may click the Delete button to delete the selected colour details. |
| |The actor may click the View button to view the saved colour details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Colour Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Colour Details saved successfully” and the actor would be brought |
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the colour details would be stored in the database with status set to save. |
| |c. The saved colour details would be available for further modification through the Modify button. |
| |d. The colour details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank country details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details |
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save colour details when no colour has been selected from the list. |
| |The System would respond with a message, “No colour name has been selected. Please select at least one colour to |
| |save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception occurs when |
| |the actor saves the Colour Details without selecting any colour. |
| |The actor attempts to edit the colour details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the colour details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the colour details when the colour name with the same Country Code already exists in |
| |the System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Colour Name and Colour Code |
| |System would display a default list of Colour Names and Colour Codes. |
| |Colour Details, which have already been used in the application, should not be available to select for deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
10 MANAGING ANIMAL CATEGORY
|UC 3.2.3.10 |Managing Animal Category |
|Version: |00 |
|Context: |This use case is for managing Animal Category |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add Animal category details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Animal |
| |Category->Animal Details. |
|Normal Flow |The System will prompt the actor to specify following animal details: |
| |Animal Name and Animal Code: The actor would select name of the animal along with animal code being displayed in |
| |the list available for selection. The displayed list will enlist all the Animal Names along with their codes for |
| |selection. |
| |The actor could add multiple animals being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected animal details |
| |The actor may click the Edit button to edit the selected animal details. |
| |The actor may click the Delete button to delete the selected animal details. |
| |The actor may click the View button to view the saved animal details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Animal Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Animal Details saved successfully” and the actor would be brought |
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the animal details would be stored in the database with status set to save. |
| |c. The saved animal details would be available for further modification through the Modify button. |
| |d. The animal details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank animal details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details|
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save animal details when no animal detail has been selected from the list. |
| |The System would respond with a message, “No Animal name has been selected. Please select at least one animal |
| |name to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception |
| |occurs when the actor saves the Animal Details without selecting any animal. |
| |The actor attempts to edit the animal details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the animal details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the animal details when the animal name with the same animal Code already exists in |
| |the System. |
| |The System would respond with the message, “Animal Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Animal Name and Animal Code |
| |System would display a default list of Animal Names and Animal Codes. |
| |Animal Details, which have already been used in the application, should not be available to select for deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
11 MANAGING ANIMAL BREED CATEGORY
|UC 3.2.3..11 |Managing Animal Breed Category |
|Version: |00 |
|Context: |This use case is for managing Animal Breed Category |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add Breed details |
|Secondary Actor(s) |None |
|Pre Conditions | |
| |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Breed |
| |category->Breed Details. |
|Normal Flow |The System will prompt the actor to specify following breed details: |
| |Breed Name and Breed Code: The actor would select name of the Breed along with breed code being displayed in the |
| |list available for selection. The displayed list will enlist all the Breed Names along with their codes for |
| |selection. |
| |The actor could add multiple Breeds being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected breed details. |
| |The actor may click the Edit button to edit the selected breed details. |
| |The actor may click the Delete button to delete the selected breed details. |
| |The actor may click the View button to view the saved breed details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the breed Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Breeds Details saved successfully” and the actor would be brought |
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the breed details would be stored in the database with status set to save. |
| |c. The saved breed details would be available for further modification through the Modify button. |
| |d. The breed details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank breed details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details|
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save breed details when no breed has been selected from the list. |
| |The System would respond with a message, “No breed name has been selected. Please select at least one breed name |
| |& code to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception |
| |occurs when the actor saves the breed Details without selecting any breed. |
| |The actor attempts to edit the breed details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the breed details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the breed details when the breed name with the same breed Code already exists in the |
| |System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Breed Name and Breed Code |
| |System would display a default list of Breed Names and Breed Codes. |
| |Breed Details, which have already been used in the application, should not be available to select for deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
12 MANAGING SIP CONDITION (PRODUCT WISE)
|UC 3.2.3..12 |Managing SIP Condition (Product Wise) |
|Version: |00 |
|Context: |This use case is to describe the process to manage the condition to issue SIP. |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |SIP user with the assigned privilege to add condition. |
|Secondary Actor(s) |None |
|Pre Conditions | |
| |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add condition details under the option available in Master Entry -> Manage condition product|
| |wise category->Condition Details. |
|Normal Flow |The System will prompt the actor to specify following Condition details: |
| |Condition Detail and Condition Code (HS code): The actor would select detail of the Condition along with |
| |Condition code being displayed in the list available for selection. The displayed list will enlist all the |
| |Condition Detail along with their codes for selection. |
| |The actor could add multiple Condition being required to deal with SIP application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected condition details. |
| |The actor may click the Edit button to edit the selected condition details. |
| |The actor may click the Delete button to delete the selected condition details. |
| |The actor may click the View button to view the saved condition details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the condition Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Condition Details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All information related to the condition details would be stored in the database with status set to save. |
| |c. The saved condition details would be available for further modification through the Modify button. |
| |d. The condition details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank condition details form; otherwise, the|
| |actor would be brought back to where actor was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details|
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where actor was before clicking the Close button. |
|Exceptions |The actor attempts to save condition details when no condition has been selected from the list. |
| |The System would respond with a message, “No condition name has been selected. Please select at least one |
| |condition name & code to save record”. Click OK to continue. The actor would be brought back to Pre Condition. |
| |The exception occurs when the actor saves the condition Details without selecting any condition. |
| |The actor attempts to edit the condition details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the condition details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the condition details when the condition detail name with the same Code already exists|
| |in the System. |
| |The System would respond with the message, “Condition Details already exists. Please select another condition”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Condition Detail and Condition Code |
| |System would display a default list of Condition Detail and Condition Codes. |
|Relationships |Extends |
| |SIP Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
3 PERFORMANCE REQUIREMENTS
1 SCALABILITY REQUIREMENTS
Scalability refers to the how the proposed system will be scaled up with need and time. In the current scenario, there will be average 100,000 application users of the system at central, state and village level. At any point of time, no more than 25,000 simultaneous application users would be expected in the system. At any point of time, the software should support a peak load of 25000 concurrent users.
2 RESPONSE TIME
The response time should be as follows: Response time will be 5-10 seconds for any request from the client depending on the network traffic and bandwidth between client & server system. Any number of simultaneous users will be able to use the system. 5-10 second: For user operation on data (for e.g. sorting of data in a column) or (5 to 50 records per page up to max of 100,000 records) 10-20 second: For user awaiting response from the system upon executing a transaction (for e.g. a query/update). 1 minute – Unacceptable response time. The SMS alerts to reach the users mobile in an acceptable time limit from the SMS gateway/applications. Ideally it is within 120 Seconds from information trigger, from central server to national jurisdiction.
4 SOFTWARE SYSTEM ATTRIBUTES
1 USABILITY
The Screens should be designed for ease of use by non technical users who do not have any computer knowledge. The GUI design shall be intuitive and task-based without any superfluous design. The design should adopt the following principles:
• Use relative font size so that a user can easily change overall font size from the browser interface. • Text equivalents should be given for all graphics. • Application should function even if Java script, CSS and Frames are turned off.
2 INTERNAL / INTRANET USERS
In this category, the users belong to AQIS Department employees, Administrators and officials. All these users shall be provided with a user-id and password on the Directory services (AD) server. These users connect through LAN (10/100 Mbps) and have to pass through the policies set on the Internal Firewall, get authenticated through the AD server and only authorized users get connected to the Web server/Application server. Through the application, access to the Database server is provided. No user can directly access the Database server.
3 INTERNET USERS
In this category, the users are Importer & Exporter, Citizens etc. These users are “Anonymous” users and they connect to the application through Internet. These users have to connect over the internet through the Router and pass through the policies set on it as well as on the External Firewall. Once they pass through the External Firewall, they land on the Portal server; login as “anonymous” and pass through the policies set on the AD server, and then get connected to either the Web server or Application server as per the requested service. The application connects to the Database server for all data storage/retrieval activities.
4 RELIABILITY
It is expected that there shall not be any bug and the system shall be tested on end cases to offer user a quality and reliable package. It is made reliable by providing the list of values for some of the mandatory parameters to minimize the errors in data entry that will provide consistent results from the system. Integrity of data will also be maintained while saving and updating the details.
5 AVAILABILITY
AQIS application shall be up and running and must be available 24x7 and any one should be able to connect to it from anywhere. It should trap all errors and prevent users from accessing unauthorized areas of the application. In case of application or a hardware failure, the system should re-initiate immediately. In case of a possible hardware failure or corruption of database the system administrator should immediately restore the backup.
6 SECURITY
The system should have protection against
• Unauthorized creation/modification of data - through user name and password authentication as defined for relevant user groups. • Unauthorized viewing of data - through user name and password authentication as defined for relevant user groups. • The software should adhere to security guidelines, standards and policies prescribed by NIC’s Security Division and should be audited & certified for compliance to these standards by Security Division before it is hosted in Production Environment. • The software should be protected against any unauthorized access to the software. • System Administrator should moderate for the audio and video contents those are uploaded into the system to check any objectionable information is not uploaded. • Configuration is secured with firewalls in place. Secure communication over SSL. • Zero Data Loss: Data base server with clustering and back up with stand by server in case of failure will ensure No data loss. • Authentication/Authorization: Assuming that application will have Single Sign On login feature; where user once logged in, will not have to login again to use other integrated application. • The users will have different functional options
7 MAINTAINABILITY
In order to ensure maintainability of the application, the following should be ensured:
• The application will be designed and developed using Open Source Tools and Technologies. Software Code must be modular and well documented • All the artifacts related to the software such as code, design document, User Manual etc. should be well documented and self-explanatory for any programmer to understand. Detailed documentation shall be available at each stage for easy comprehensions of the application system. • All documents shall be prepared as per the defined documentation standards. The system administrator shall take regular back up of the database
8 PORTABILITY
The software will be hosted/installed in Linux RHEL 5 and above OS based server and will be accessed through Windows (XP) based machines using I.E 6.0 or above OR Mozilla 3.5.11 or above browsers.
9 LANGUAGE SUPPORT
• AQIS/SIP will support the entry and display of:
o All Indian scripts such as Hindi, English
o The application will store data using Unicode representation.
• Unicode font file & keyboard manager/driver should be available.
10 INTEROPERABILITY
The software will interoperate with other software applications which are being developed under National e-Governance Program, Mission Mode Project, in particular Central Agriculture Portal and with custom for information exchange. The following are the likely points of information exchange/reconciliation:
• BOE/BOS issued by custom
• AQC issued by AQCS department.
5 LOGICAL DATABASE REQUIREMENTS
1 DATA STORE: USER_ MASTER
|Data Element |Description |O/M |Remarks |
|User ID |Numeric |M |12,PK |
|I/E Code |Numeric |M |12 |
|NPPO Code |Numeric |M |12,FK |
|NPPO Country Name |Character |M |Abcd |
|User Category |Character |M |Abcd |
|Internal |Character |M |Abcd |
|External |Character |M |Abcd |
|User Name |Character |M |Abcd |
|Designation |Character |M |Abcd |
|Employee Code |Numeric |M |12 ,FK |
|User DOB |Numeric |M |12 |
|Office Address |Alpha-Numeric |O |12 abcd |
|Residential Address |Alpha-Numeric |M |12 abcd |
|E-mail ID |Alpha-Numeric |M |abcd@nic.com |
|Alternate E-mail ID |Alpha-Numeric |O |abcd@nic.com |
|Mobile Number |Numeric |M |12 |
|Phone Number |Numeric |M |12 |
|Fax Number |Numeric |M |12 |
|State |Character |M |abcd |
|City |Character |M |abcd |
|District |Character |M |abcd |
|Pin Code Number |Numeric |M |6 |
|Allow SMS |Boolean |M |True/False |
|Select Question Type |Character |M |abcd |
|Select Answer |Character |M |abcd |
|Password |Alpha-Numeric |M |12 abcd |
|Confirm Password |Alpha-Numeric |M |12 abcd |
2 DATA STORE: ROLE MANAGEMENT_ MASTER
|Data Element |Description |O/M |Remarks |
|Role ID |Numeric |M |For Departmental User Only, PK |
|Role Name |Character |M |For Departmental User Only, FK |
|Role Description |Character |M |For Departmental User Only |
3 DATA STORE: AQIS (IMPORT/EXPORT) CERTIFICATION FOR LSP_MASTER
AQCS (Import/Export) Certification for LSP Form (Annex-24)
|Data Element |Description |O/M |Remarks |
|Product Code |Numeric |M |I/E select from the list of the product like apple, |
| | | |orange, PK |
|Product Name |Character |M |Abcd |
|Product Category |Numeric |M |12 |
|Applied To |Character |M |Abcd |
|Exporter Name |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Mobile No. |Numeric |M |12 |
|Telephone No. |Numeric |M |12 |
|Fax No. |Numeric |M |12 |
|SIP Number/DGFT License Number |Alphanumeric |M |12 Abcd |
|SIP Validity |Date |M |DD/MM/YYYY |
|Name Of LSP |Character |M |Abcd |
|LSP Quantity |Numeric |M |Abcd |
|Purpose of Import/Export |Character |M |Abcd |
|Custom Seal No |Numeric |M |12 |
|Custom Date |Date |M |DD/MM/YYYY |
|Date Of Import/Export |Date |M |DD/MM/YYYY |
|Shipping/Airway Bill No |Alphanumeric |M |12 Abcd |
|Shipping/Airway Bill Date |Date |M |DD/MM/YYYY |
|Health Certificate No |Numeric |M |12 |
|Health Certificate Date |Date |M |DD/MM/YYYY |
|Country of origin |Character |M |Abcd |
|Number of Packages |Alphanumeric |O |12 Abcd |
|Container No |Alphanumeric |O |12 Abcd |
|Post of loading |Character |M |Abcd |
|Post of unloading |Character |M |Abcd |
|Date/Means of Conveyance |Character |M |Abcd |
|Plant registration number |Alphanumeric |M |12 Abcd |
|Invoice Number |Alphanumeric |M |12 Abcd |
|Invoice Date |Date | |DD/MM/YYYY |
|Lab Report No |Alphanumeric |M |12 Abcd |
|Lab Report Name |Date | |DD/MM/YYYY |
|Declaration |Character |M |Abcd |
|Verification By The Quarantine Officer (Official Purpose) |
|Checking The Documents Attached |Boolean | |Yes/No |
|SIP If Any |Boolean | |Yes/No |
|Importer/Exporter License If Any |Boolean | |Yes/No |
|Health Certificate |Boolean | |Yes/No |
|Fumigation Certificate/Test Report|Boolean | |Yes/No |
|Invoice |Boolean | |Yes/No |
|Airway/Shipping Bill No |Boolean | |Yes/No |
|Bill Of Entry No |Boolean | |Yes/No |
|Plant registration copy |Boolean | |Yes/No |
|Laboratory Letter/Report |Boolean | |Yes/No |
|Importer/Exporter Declaration |Boolean | |Yes/No |
|Others If any |Boolean | |Yes/No |
|Charges If Any |Boolean | |Yes/No |
|Decision |
|Fit For Clearance |Boolean | |Yes/No |
|Unfit For Clearance On Account |Character | |Abcd |
|Of(Detail Overleaf) | | | |
|Temporarily Unclear On Account Of |Character | |Abcd |
|(Detail Overleaf) | | | |
4 DATA STORE: AQIS (IMPORT/EXPORT) CERTIFICATION FOR LS/PET ANIMAL _MASTER
AQIS (Import/Export) Certification for LS/Pet Animal Form (Annex-23) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|Animal Id |Numeric |M |12, PK |
|Animal Name |Character |M |Abcd |
|Sex Of Animal |Character |M |Abcd |
|Animal Breed |Character |M |Abcd, FK |
|Expected Date Of Import/Export |Date |M |DD/MM/YYYY |
|Exporter Name |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Mobile No |Numeric |M |12 |
|Telephone NO |Numeric |M |12 |
|Fax No |Numeric |M |12 |
|Mode |Character |M |Abcd |
|SIP Number/DGFT License Number |Alphanumeric |M |12 Abcd |
|SIP/DGFT License Validity |Date |M |DD/MM/YYYY |
|Purpose of Import/Export |Character |M |Abcd |
|Date Of Import/Export |Date |M |DD/MM/YYYY |
|Shipping/Airway Bill No |Alphanumeric |M |12 Abcd |
|Shipping/Airway Bill Date |Date |M |DD/MM/YYYY |
|Health Certificate No |Numeric |M |12 |
|Health Certificate Date |Date |M |DD/MM/YYYY |
|Country of origin |Character |M |Abcd |
|Color |Character |M |Abcd |
|Number Of Livestock |Numeric |M |12 |
|PP NO/Microchip No |Alphanumeric |O |12 Abcd |
|Rabies Vaccination |Character |M |Abcd |
|Rabies Vaccination Date |Date |M |DD/MM/YYYY |
|Batch No |Alphanumeric |M |12 Abcd |
|Country Of Embarkation |Character |M |Abcd |
|Place Of Embarkation |Character |M |Abcd |
|Country Of Disembarkation |Character |M |Abcd |
|Place Of Disembarkation |Character |M |Abcd |
|Number of Packages |Alphanumeric |O |12 Abcd |
|Date/Means of Conveyance |Character |M |Abcd |
|Invoice Number |Alphanumeric |M |12 Abcd |
|Invoice Date |Date |M |DD/MM/YYYY |
|Lab Report No |Alphanumeric |M |12 Abcd |
|Lab Report Name |Date |M |DD/MM/YYYY |
|Declaration |Character |M |Abcd |
|Verification By The Quarantine Officer (Official Purpose) |
|Checking The Documents Attached |Boolean | |Yes/No |
|SIP/DGFT License If Any |Boolean | |Yes/No |
|Importer/Exporter Declaration |Boolean | |Yes/No |
|Health Certificate |Boolean | |Yes/No |
|Invoice No |Boolean | |Yes/No |
|Bill Of Entry No |Boolean | |Yes/No |
|Laboratory Letter/Report |Boolean | |Yes/No |
|Others If any |Boolean | |Yes/No |
|Ticket No If Any |Numeric | |12 |
|Charges If Any |Boolean | |Yes/No |
|Decision |
|Fit For Clearance |Boolean | |Yes/No |
|Unfit For Clearance On Account Of(Detail |Character | |Abcd |
|Overleaf) | | | |
|Temporarily Unclear On Account Of (Detail |Character | |Abcd |
|Overleaf) | | | |
5 DATA STORE: SANITARY IMPORT PERMIT_MASTER
FORM A(Annex-31)
|Data Element |Description |O/M |Remarks |
|Name And Exact Description Of Livestock(s) |Alphanumeric |M |12 Abcd |
|Product To Be Imported | | | |
|I/E Code |Alphanumeric |M |12 Abcd |
|Name Of Consigner |Character |M |Abcd |
|Address Of Consigner |Alphanumeric |M |12 Abcd |
|Address Of importer |Alphanumeric |M |12 Abcd |
|Name Of Importer |Character |M |Abcd |
|Country Of Produced |Character |M |Abcd |
|Locality Of Produced |Character |M |Abcd |
|ITC(HS) code |Numeric |M |12, FK |
|Total weight/volume |Alphanumeric |M |12 Abcd |
|Country & locality in which Livestock Product |Alphanumeric |M |12 Abcd |
|produces | | | |
|Foreign port of shipment |Alphanumeric |M |12 Abcd |
|Name of airport/sea port/land custom station |Character |M |Abcd |
|Approximate date of arrival of the consignment |Alphanumeric |O | |
|in India | | | |
|Name of point of entry in India |Character |M |Abcd |
|Declaration |Character |M |Abcd |
|Authorize Agent No |Alphanumeric |M |12 Abcd |
|Authorize Agent Name |Alphanumeric |M |12 Abcd |
|Authorize Agent Address |Alphanumeric |M |12 Abcd |
|Place |Character |M |Abcd |
|Date |Date |M |DD/MM/YYYY |
|Reference No |Alphanumeric |M |System Generate |
|SIP NO Issue |Alphanumeric |M |For Departmental User Only, PK |
FORM B(Annex-32)
|Data Element |Description |O/M |Remarks |
|Name And Exact Description Of Livestock(s) |Alphanumeric |M |12 Abcd, FK |
|Product with Indian Trade Classification | | | |
|(Harmonized System)-ITC(HS) code | | | |
|I/E Code |Alphanumeric |M |12 Abcd |
|Name Of Consigner |Character | |Abcd |
|Address Of Consigner |Alphanumeric |M |12 Abcd |
|Address Of importer |Alphanumeric |M |12 Abcd |
|Name Of Importer |Character | |Abcd |
|Country Of Produced |Character | |Abcd |
|Locality Of Produced |Character | |Abcd |
|Total weight/volume |Alphanumeric |M |12 Abcd |
|Country & locality in which Livestock Product |Alphanumeric |M |12 Abcd |
|produces | | | |
|Foreign port of shipment |Alphanumeric |M |12 Abcd |
|Name of airport/sea port/land custom station |Character | |Abcd |
|Catalogue Of Livestock Products Producer |Upload | |Attached |
|Establishing Identity Of the Livestock | | | |
|Products/Material To be Imported | | | |
|Details Of Livestock From Whom it Is Produced |Character | |Abcd |
|Name of point of entry in India |Character | |Abcd |
|No Of Packages |Alphanumeric |M |12 Abcd |
|Declaration |Character | |Abcd |
|Authorize Agent No |Alphanumeric |M |12 Abcd |
|Authorize Agent Name |Alphanumeric |M |12 Abcd |
|Authorize Agent Address |Alphanumeric |M |12 Abcd |
|Place |Character |M |Abcd |
|Date |Date |M |DD/MM/YYYY |
|Reference No |Alphanumeric | |System Generate |
|SIP NO Issue |Alphanumeric | |For Departmental User Only, PK |
6 DATA STORE: VETERINARY HEALTH/ZOO SANITARY CERTIFICATE
(LIVESTOCK)(EXPORT) _ MASTER
Veterinary Health/Zoo Sanitary Certificate for Livestock Product (Export) (Annex-1) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Declared Port Of Loading |Character |M |Abcd |
|Product ID |Character |M |Abcd, FK |
|Product Name |Character |M |Abcd |
|Gross Weight |Numeric |M |12 |
|No. of Packages |Numeric |M |12 |
|Exporting Country Name |Character |M |Abcd |
|Importing Country Name |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Exporter Name |Character |M |Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Mobile No |Numeric |M |12 |
|Telephone NO |Numeric |M |12 |
|Health Attestation |Alphanumeric |M |12 Abcd |
|AQC Health Certificate No. |Alphanumeric |M |PK |
7 DATA STORE: PROVISIONAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK(IMPORT_ MASTER
Provisional Quarantine Clearance Certificate for Livestock (Import) (Annex-2) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Country of Origin |Character |M |Abcd |
|Tag No. |Numeric |O |12 |
|Name of Livestock |Character |M |Abcd |
|Breed Code |Character |M |Abcd, FK |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
|Date of Import |Date |M |DD/MM/YYYY |
|Bill of Entry No. |Alpha-Numeric |M |12 Abcd |
|Flight No. |Alpha-Numeric |O |12 Abcd |
|Provisional AQC No. |Alpha-Numeric |M |PK |
8 DATA STORE: FINAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK PRODUCT(IMPORT) _ MASTER
Final Quarantine Clearance Certificate for Livestock Product (Import) (Annex-5) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|SIP No. |Alpha-Numeric |M |12 Abcd, FK |
|Validity |Date |M |DD/MM/YYYY |
|Country of Origin |Character |M |Abcd |
|Livestock Product Name |Character |M |Abcd |
|No. of Packages |Numeric |M |12 |
|Net Weight |Numeric |M |12 |
|Invoice No. |Character |M |Abcd |
|Invoice Date |Character |M |Abcd |
|Date of Import |Date |M |DD/MM/YYYY |
|Bill of Entry No. |Alpha-Numeric |M |12 Abcd |
|Airway Bill No. |Alpha-Numeric |M |12 Abcd |
|Importer Name |Character |M |Abcd |
|Exporter Name |Character |M |Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Port Of Embarkation |Character |M |Abcd |
|Final AQC No. |Alpha-Numeric |M |PK |
9 DATA STORE: FINAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK (IMPORT) _ MASTER
Final Quarantine Clearance Certificate for Livestock (Import) (Annex-30) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Country of Origin |Character |M |Abcd |
|Tag No. |Numeric |O |12 |
|Name of Livestock |Character |M |Abcd |
|Breed Code |Character |M |Abcd, FK |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
|Date of Import |Date |M |DD/MM/YYYY |
|Importer Name |Character |M |Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Certificate No. |Alpha-Numeric | |For Departmental User Only, PK |
10 DATA STORE: CERTIFICATE OF HEALTH FOR EXPORT OF PET ANIMAL _ MASTER
Certificate of Health for Export of Pet Animal (Annex-28) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Exporting Country Name |Character |M |Abcd |
|Animal Category |Character |M |Abcd |
|Tag No. |Numeric |O |12 |
|Name of Livestock |Character |M |Abcd |
|Breed Code |Character |M |Abcd, FK |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
|Date of Travel |Date |M |DD/MM/YYYY |
|Exporter Name |Character |M |Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Flight No. |Alpha-Numeric |M |12 Abcd |
|Vaccination Name |Character |M |Abcd |
|Date of Vaccination |Date |M |DD/MM/YYYY |
|Validity of Vaccination |Date |M |DD/MM/YYYY |
|Serial No./Batch of Vaccine |Alpha-Numeric |M |12 Abcd |
|Certificate No. |Alpha-Numeric | |For Departmental User Only, PK |
11 DATA STORE: NOC FOR IMPORT OF PET ANIMAL _ MASTER
NOC for Import of Pet Animal (Annex-26)
The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|I/E Code |Alpha-Numeric |M |PK |
|Date |Date |M |DD/MM/YYYY |
|Exporting Country Name |Character |M |Abcd |
|Importing Country Name |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Animal Category |Character |M |Abcd |
|Tag No./Micro Chip No. |Numeric |O |12 |
|Name of Animal |Character |M |Abcd |
|Breed |Character |M |Abcd |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
12 DATA STORE: DEPORTATION/DESTRUCTION OF CONSIGNMENT_ MASTER
Annex-35
|DATA ELEMENT |DESCRIPTION |O/M |REMARKS |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Country of Origin |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Animal Category |Character |M |Abcd |
|Tag No./Micro Chip No. |Numeric |O |12 |
|Name of Animal |Character |M |Abcd |
|Breed Code |Character |M |Abcd, FK |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
|Livestock Product Name |Character |M |Abcd |
|No. of Packages |Numeric |M |12 |
|Net Weight |Numeric |M |12 |
|Gross Weight |Numeric |M |12 |
|Bill of Entry No. |Alpha-Numeric |M |12 Abcd |
13 DATA STORE: PINCODE_ MASTER
|Data Element |Description |O/M |Remarks |
|Pin code |Numeric |M |6 |
|City |Character |M |Abcd |
|Address |Alpha-Numeric |M |12 Abcd |
|District |Character |M |Abcd |
14 DATA STORE: GRIEVANCE_ MASTER
|Data Element |Description |O/M |Remarks |
|Grievance Id |Alpha-Numeric |M |12, PK |
|Grievance type |Character |M |Abcd |
15 DATA STORE: GRIEVANCE MANAGEMENT_ MASTER
|Data Element |Description |O/M |Remarks |
|Id |Alpha-Numeric |M |12 abcd, PK |
|Name |Character |M |Abcd |
|Mobile No |Numeric |M |12 |
|Email_id |Character |M |abcd |
|State_id |Numeric |M |12 |
|District_id |Numeric |M |12 |
|Grievance_type |Numeric |M |12 |
|Grievance_details |Character |M |abcd |
|Submission_date |Date |M |DD/MM/YYYY |
16 DATA STORE: SMS _MASTER
|Data Element |Description |O/M |Remarks |
|SMS Id |integer |M |12 abcd, PK |
|SMS Details |Character |M |Abcd |
|User_id |integer |M |12 |
|Date |Date |M |DD/MM/YYYY |
|SMS Details |Character |M |Abcd |
|SMS Time |Time |M |HH/MM/SS |
17 DATA STORE: COUNTRY_MASTER
|Data Element |Description |O/M |Remarks |
|Country Name |Character |M | |
|Country Code |Numeric |M |PK |
18 DATA STORE: NPPO_MASTER
|Data Element |Description |O/M |Remarks |
|NPPO Name |Character |M | |
|NPPO Code |Numeric |M |PK |
| | | | |
19 DATA STORE: SEAPORT_MASTER
|Data Element |Description |O/M |Remarks |
|Port Name |Character |M |Abcd |
|Port Code |Numeric |M |12, PK |
|Country Code |Numeric |M |12, FK |
|City Code |Numeric |M |12 |
|District Code |Numeric |M |12 |
20 DATA STORE: AIRPORT_MASTER
|Data Element |Description |O/M |Remarks |
|AirPort Name |Character |M |Abcd |
|AirPort Code |Numeric |M |12, PK |
|Country Code |Numeric |M |12 |
|City Code |Numeric |M |12 |
|District Code |Numeric |M |12 |
21 DATA STORE: PRE-DEFINED DISEASE FOR TESTING & SAMPLE _MASTER
|Data Element |Description |O/M |Remarks |
|Disease ID |Numeric |M |12, PK |
|Disease Name |Character |M |Abcd |
|LSP/LS name |Character |M |Abcd |
|Lab ID |Numeric |M |12 |
|Lab Name |Character |M | Abcd |
|Lab Address |Alpha-Numeric |M |12 Abcd |
|Sample |
|Sample No. |Numeric |M |12, PK |
|Product Code(ITC-HS) |Numeric |M |12, FK |
|Product Name |Character |M |Abcd |
|Reference No. |Alpha-Numeric |M |12 Abcd |
|Date of Sample |Date |M |DD/MM/YYYY |
|No. of Sample |Numeric |M |12 |
|Result |Boolean |M |Yes/No |
22 DATA STORE: DEPARTMENT_MASTER
|Data Element |Description |O/M |Remarks |
|Department Name |Character |M |Abcd |
|Department Code |Numeric |M |12, PK |
23 DATA STORE: ANIMAL CATEGORY_MASTER
|Data Element |Description |O/M |Remarks |
|Category Name |Character |M |Abcd |
|Category Code |Numeric |M |12, PK |
24 DATA STORE: DESIGNATION_MASTER
|Data Element |Description |O/M |Remarks |
|Designation Name |Character |M |Abcd |
25 DATA STORE: BREED_MASTER
|Data Element |Description |O/M |Remarks |
|Breed Name |Character |M |Abcd |
|Breed Code |Numeric |M |12, PK |
|Breed Colour |Character |M |Abcd |
|Breed Quantity |Numeric |M |12 |
Note: For State, City & District _master software is being developed under National e Panchayat Mission Mode Project at Panchayati Raj Division by the name of “Local Government Directory”.
6 OTHER REQUIREMENTS
This section lists the other non-functional requirement related to installation/un-installation /upgrades of AQIS application. A non-technical person shall be able to setup and run the AQCS application.
1 BACKUP
An automated and scheduled data backup mechanism shall be provided which will write a backup of the data to one of the system’s disks. From there, the backup date can be manually written to CD or tape if required. The data backup should cover data held in a database and any data held outside of the database such as files uploaded through the software.
2 RECOVERY
A simple manual data recovery procedure will be provided to recover the data from a data backup when required by the system administrator. The data backup will be used to recover the data in the event of a disk corruption or database corruption.
3 DATA RETENTION
The latest data on the Server will be kept for the seasons of the two calendar years. The data for more than five years is to be backed up on to a CD and remove from the Server.
4 CUSTOMER/USER TRAINING
It is proposed that NIC will conduct a training program for 5 days at NIC, HQ to fully train selected AQIS Administrator on the installation, use, backup, recovery, plan creation/updation and problem diagnosis. These Administrators will become “AQCS Master Trainers (also known as Trainers of Trainers) who will then train AQIS users in the use of the software. (Consultation with NIC require on this point)
5 AUDIT TRAIL
The Software shall offer a comprehensive report on the user actions (changes made with time stamp) through audit trail and will be maintained in log server in identified government domain.
ANNEXURE
1 ANNEXURE (1 to 39) IN ONE FOLDER
2 ANNEXURE 40: ADDRESSES OF PLANT / ANIMAL QUARANTINE OFFICES
3 ANNEXURE 41: MESSAGE STRUCTURE OF CUSTOM INTEGRATION FOR PQIS
-----------------------
CONTENT MANAGEMENT
References: Animal Quarantine Certification Service The purpose of the Animal Quarantine and certification (AQC) is to prevent the ingress of livestock and poultry exotic to India as per provisions of livestock importation Act, 1898.
Table of Contents
1. INTRODUCTION 3
1.1 PURPOSE 3 1.1.1 INTENDED AUDIENCE 3
1.2 SCOPE OF WORK 3
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS 4
1.4 REFERENCES 6
1.5 OVERVIEW 7
2. OVERALL DESCRIPTION 9
2.1 PRODUCT PERSPECTIVE 9 2.1.1 KNOWLEDGE MANAGEMENT APPLICATION 9 2.1.2 SYSTEM INTERFACES :- 10 2.1.3 USER INTERFACES:- 11 2.1.4 HARDWARE INTERFACES 11 2.1.5 SOFTWARE INTERFACES 11 2.1.6 COMMUNICATIONS INTERFACES 12 2.1.7 MEMORY CONSTRAINTS 12 2.1.8 OPERATIONS 12 2.1.9 SITE ADAPTATION REQUIREMENTS 12
2.2 PRODUCT FUNCTIONS(CURRENT AS IS BUSINESS PROCESSES) 13 2.2.1 ANIMAL QUARANTINE CERTIFICATION PROCEDURES 13 2.2.2 PLANT QUARANTINE CERTIFICATION PROCEDURES 35
2.3 PRODUCT FUNCTIONS( TO BE WORK FLOW) 41 2.3.1 THERE WOULD BE THREE MODULE OF THE ANIMAL QUARANTINE CLEARANCE APPLICATION 41 2.3.2 PLANT QUARANTINE CERTIFICATION PROCEDURE 53 2.3.3 THERE ARE VARIOUS FUNCTIONALITIES IN THESE MODULE, COMMON FUNCTIONALITIES ARE GIVEN BELOW: 56
2.4 USER CHARACTERISTICS 57
2.5 CONSTRAINTS 57
2.6 ASSUMPTIONS AND DEPENDENCIES 58
3. SPECIFIC REQUIREMENTS 59
3.1 SOFTWARE PRODUCT FEATURES 59 3.1.1 ACTORS 59 3.1.2 COMMON USE CASES 60 3.1.3 SYSTEM ADMINISTRATOR 72
3.2 ANIMAL QUARANTINE 77 3.2.1 SIP & AQIS ACTIVITIES USE CASES 77 3.2.2 FAQ 111 3.2.3 MASTER USE CASES 124
3.3 PERFORMANCE REQUIREMENTS 163 3.3.1 SCALABILITY REQUIREMENTS 163 3.3.2 RESPONSE TIME 163
3.4 SOFTWARE SYSTEM ATTRIBUTES 163 3.4.1 USABILITY 163 3.4.2 INTERNAL / INTRANET USERS 163 3.4.3 INTERNET USERS 164 3.4.4 RELIABILITY 164 3.4.5 AVAILABILITY 164 3.4.6 SECURITY 164 3.4.7 MAINTAINABILITY 165 3.4.8 PORTABILITY 165 3.4.9 LANGUAGE SUPPORT 165 3.4.10 INTEROPERABILITY 165
3.5 LOGICAL DATABASE REQUIREMENTS 166 3.5.1 DATA STORE: USER_ MASTER 166 3.5.2 DATA STORE: ROLE MANAGEMENT_ MASTER 166 3.5.3 DATA STORE: AQIS (IMPORT/EXPORT) CERTIFICATION FOR LSP_MASTER 166 3.5.4 DATA STORE: AQIS (IMPORT/EXPORT) CERTIFICATION FOR LS/PET ANIMAL _MASTER 168 3.5.5 DATA STORE: SANITARY IMPORT PERMIT_MASTER 169 3.5.6 DATA STORE: VETERINARY HEALTH/ZOO SANITARY CERTIFICATE (LIVESTOCK)(EXPORT) _ MASTER 171 3.5.7 DATA STORE: PROVISIONAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK(IMPORT_ MASTER 171 3.5.8 DATA STORE: FINAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK PRODUCT(IMPORT) _ MASTER 172 3.5.9 DATA STORE: FINAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK (IMPORT) _ MASTER 172 3.5.10 DATA STORE: CERTIFICATE OF HEALTH FOR EXPORT OF PET ANIMAL _ MASTER 173 3.5.11 DATA STORE: NOC FOR IMPORT OF PET ANIMAL _ MASTER 173 3.5.12 DATA STORE: DEPORTATION/DESTRUCTION OF CONSIGNMENT_ MASTER 173 3.5.13 DATA STORE: PINCODE_ MASTER 174 3.5.14 DATA STORE: GRIEVANCE_ MASTER 174 3.5.15 DATA STORE: GRIEVANCE MANAGEMENT_ MASTER 174 3.5.16 DATA STORE: SMS _MASTER 174 3.5.17 DATA STORE: COUNTRY_MASTER 175 3.5.18 DATA STORE: NPPO_MASTER 175 3.5.19 DATA STORE: SEAPORT_MASTER 175 3.5.20 DATA STORE: AIRPORT_MASTER 175 3.5.21 DATA STORE: PRE-DEFINED DISEASE FOR TESTING & SAMPLE _MASTER 175 3.5.22 DATA STORE: DEPARTMENT_MASTER 176 3.5.23 DATA STORE: ANIMAL CATEGORY_MASTER 176 3.5.24 DATA STORE: DESIGNATION_MASTER 176 3.5.25 DATA STORE: BREED_MASTER 176
3.6 OTHER REQUIREMENTS 176 3.6.1 BACKUP 176 3.6.2 RECOVERY 176 3.6.3 DATA RETENTION 176 3.6.4 CUSTOMER/USER TRAINING 177 3.6.5 AUDIT TRAIL 177
4. ANNEXURE 178
4.1 ANNEXURE (1 to 39) IN ONE FOLDER 178
4.2 ANNEXURE 40: ADDRESSES OF PLANT / ANIMAL QUARANTINE OFFICES 178
4.3 ANNEXURE 41: MESSAGE STRUCTURE OF CUSTOM INTEGRATION FOR PQIS 178
INTRODUCTION
1 PURPOSE
The purpose of this document is to provide:
• Detail the AS-IS and To-Be processes. • The document that becomes an input for design document. • A reference document for designer, developers and tester. • Detail document to understand requirement of E-certification for Livestock / Livestock Products based on requirement received from Ministry of Agriculture. • To understand manual procedures, constraints, assumptions & dependencies etc. for e-certification of livestock & livestock product as well as integration requirement of PQIS with stakeholders & custom. • Details related to automated electronic certification for import & export (PQIS, AQIS) services into the umbrella of CAP (Central Agriculture Portal).
1 INTENDED AUDIENCE
The intended audiences for this document are:
• Department of Agriculture and Cooperation, Ministry of Agriculture • PSC Issuing Authorities • Importers and Exporters of Agriculture produce, Livestock & Fisheries within the country • Animal Quarantine and Certification Services Station • Customs Department • Director General of Foreign Trade, Department of Commerce, Ministry of Commerce • Agricultural & Processed Food Products Export Development Authority (APEDA) • Marine Products Export Development Authority (MPEDA) • Vegetable Fruit Promotion Council, Export Promotion Councils • Export Commodity Board • Food Safety and Standards Authority of India (FSSAI) • Analysts, designers, developers, testers and auditors for the automated systems to be developed. • All relevant users, who would want references regarding the system.
2 SCOPE OF WORK
The scope of the document is to identify the software requirement specification relating to:- • Automated workflow based application for various quarantine activities taken up by Animal Quarantine Station. • Issuance of electronic certificate to Importer/Exporter • Integration of PQIS with Customs department and to develop the search option with other stakeholder to check/view authenticity of certification data • The various information which will be available are as follow on AQIS web page:- o Certification procedure o Inspection authorities o Fees and charges o Quarantine requirements o Detail of prohibited items (Animal quarantine order) o Restricted & Free Livestock / Livestock Product • Online payment facility for application fee and inspection fee etc. • SMS alerts for status of Application to Importer/Exporter. • Database on country wise phyto sanitary requirements. • Entire value chain of agriculture commodity to be linked for single point of information. • Our study is to identify a provision to develop application capturing PSC number in case when export consignment is returned. • To identify the possibility of translating the phyto sanitary condition of foreign countries language into English using Google translator or other translation facilities available on internet. • Mechanism for grievance management with regards to e-certification of Importer/Exporter within the central government framework.
3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
|AC |Assistant Commissioner |
|AD |Active Directory |
|Admin |Administrator |
|ADDL |Animal Disease Diagnostic Laboratory |
|AGM |Assistant General Manager |
|APEDA |Agricultural And Processed Food Export Development Authority |
|AQC |Animal Quarantine Certificate |
|AQCS |Animal quarantine Certification Service |
|AQIS |Animal Quarantine Information System |
|BOE |Bill of Exchange |
|BOS |Bill of Shipment |
|CAP |Central Agriculture Portal |
|CD |Compact Disk |
|CDB |Coconut Development Board |
|CSS |Cascading Style Sheet |
|DADF |Department of Animal Husbandry, Dairying & Fisheries |
|DC |Deputy Commissioner |
|DDG |Deputy Director General |
|DGFT |Director General Of Foreign Trade |
|DMI |Directorate of Marketing and Inspection |
|DOH |Department of Horticulture |
|DOB |Date of Birth |
|DPPQS |Directorate of Plant Protection Quarantine & Storage |
|DAC |Directorate of Agriculture Cooperation |
|DT |Director Trade |
|ECB |Export Commodity Board |
|EIC |Export Inspection Council |
|FAQ |Frequently Asked Question |
|FDC |Fishery Development Commissioner |
|FK |Foreign Key |
|FPI |Food Processing Industries |
|FSSAI |Food Safety & Standard Authority of India |
|FY Division |Fishery Division |
|GIS |Graphic Information System |
|GP Stock |Grand Parental Stock |
|GUI |Graphical user Interface |
|HOD |Head of Department |
|HSADL |High Security Animal Disease lab |
|I/E |Importer / Exporter |
|IEC |Import/Export code |
|IP |Import Permit |
|IRO |Import Release order |
|IT |Information Technology |
|ITC-HS Code |Indian Trade Certification based on Harmonized System Code |
|JD |Joint Director |
|JS |Joint Secretary |
|K.G |Kilogram |
|LAN |Local Area Network |
|LS |Livestock |
|LSP |Livestock Product |
|L.T |Liter |
|LH Division |Live Husbandry Division |
|MIS |Management Information System |
|MPEDA |Marine Product Export Development Authority |
|NBPGR |National Bureau of Plant Genetic Resources |
|NeGP |National e-Governance Program |
|NIC |National Informatics Centre |
|NOC |No Objection Certificate |
|NPPO |National Plant Protection Organization |
|NPQS |National Plant Quarantine Station |
|OS |Operating System |
|PK |Primary Key |
|PP |Plant Protection |
|PQS |Plant Quarantine Station |
|PSC |Phyto Sanitary Certificate |
|S.No. |Serial Number |
|SIP |Sanitary Import permit |
|SMS |Short Message Service |
|SO |Section Officer |
|SRS |Software Requirement Specification |
|SSL |Secure Socket Layer |
|URL |Uniform Resource Locator |
4 REFERENCES
Delhi, NCR • Dr. A K Choubey, NIC • Mr. Shahid Hassan, NIC • Dr.S K Dutta, Assistant Commissioner(Trade), NIC • Mr. Raman, Trade Department, NIC • Dr. R K Gupta, Assistant Commissioner (AH Department), NIC • Mr. Siddiqui,Research Officer(Fishery Department) • Mr. DDK Sharma joint director (PP), PQS, Faridabad • Mr. Raman Malik, Arbro Pharmaceuticals • Dr. J P Singh, NPQS • Mr. Adesh Mohan, FSSAI, Delhi • Mr. Sunil Kumar (Sectary), APEDA, Delhi • Mr. MP Vijay (AGM), APEDA, Delhi • Dr. Mandilk, EIC • Dr. Vijay Kumar Teotia, Quarantine Officer, Animal Quarantine, Delhi States: Assam: • Study Report on Electronic Certification of Exports & Imports prepared by D.I.O, Dhubri Himanchal Pradesh • Mr. B.S. Negi, Directorate of Horticulture, Shimla • Mr. Kishore Chand Azad, Senior Marketing Officer,Shimla Jharkhand: • Officer from Plant Protection Division, Ranchi Madhya Pradesh • Dr. Nagarajan, Senior Scientist, High Security Animal Decease Lab, Bhopal. • Dr. Sandeep Bhatia, Senior Scientist, High Security Animal Decease Lab, Bhopal. Karnataka • Mr. Manickam, Deputy Director, Plant Pathology, Bangalore • Ms.Roopa, Director of Agriculture, Plant Pathology department, Bangalore. Maharastra • Mr. Shiv Sagar Verma, Deputy Director (PP), PQS, Mumbai • Dr. Sahdeo D. Bhosale, Quarantine Officer, Animal Quarantine, Mumbai Kerala • Mrs. Usha Singh (Systems Analyst, MPEDA Cochin)
• Mr. Ajithan (Upper Divisional Clerk, PQS)
• Dr. Ramani GopalaKrishnan (Deputy Director, CDB Cochin)
• Mr. Vasanth Kumar (Statistical Investigator, CDB Cochin)
• Mrs. M. Priya (Statistical Assistant)
• Mr. Jnanadevan (Deputy Director (Marketing), Cashew & Cocoa Development) WEB Source • http://plantquarantineindia.nic.in; http://plantquarantineindia.org • http://ppqs.gov.in; http://dadf.gov.in • www.hpsamb.nic.in Documents • Presentation, DPR and document shared by NIC
5 OVERVIEW
Plant Quarantine Certification Service
Export or Import certification (PSC/IP/IRO) is essential for agriculture commodity to ensure that the commodity which coming to India or going out of India is free from pests and diseases.
Plant Quarantine is mandatory for import of any plant material under the provisions of destructive insect & pests act 1914.
Plant Quarantine Certification Service is already operational since 2011 and its website is http://plantquarantineindia.nic.in .
Animal Quarantine Certification Service
The purpose of the Animal Quarantine and certification (AQC) is to prevent the ingress of livestock and poultry exotic to India as per provisions of livestock importation Act, 1898.
The Electronic Certification for Import & Export Will Lead to:-
• Reduce the technical personnel’s time in entering the application details in the system.
• Reduce the process time of the application.
• Optimize the employee’s performance.
• Provide status update on export/import certification applications.
• Provide information on export/import certification procedure.
As of now the information dissemination process runs manually. The Ministry of Agriculture came up with the plan under NeGP plan to integrate various components and systems which can talk and handshake to each other to make the whole process run with seamless manner.
Overall information system flow:
[pic]
Diagram 1: Overall information system
OVERALL DESCRIPTION
1 PRODUCT PERSPECTIVE
1. Automation of existing manual backend processes of Animal Quarantine Certification (AQC) for issuance of SIP and Quarantine clearance certificate for Import/Export to decrease the lead time in processing applications and to provide most up to date information on a. Sanitary Import Permit to Importer b. Issuance of Animal Quarantine Certificate for Export c. Issuance of Animal Quarantine Certificate for Import 2. Information on Fee/Charges of Treatment/Lab/Inspection 3. Information exchange from the stake holders to get the required information. 4. Enable online payment facility 5. Mechanism for grievance management with regards to a specific activity / process within the central government framework. 6. SMS Based alerts and information dissemination. 7. Information on restricted and free products 8. Integration of PQIS application with Customs to exchange information & to develop search option with other stake holders. Apart from the transactional system mentioned above, following are the other categories the system will have:
1 KNOWLEDGE MANAGEMENT APPLICATION
1 CONTENT MANAGEMENT
|S.No. |Web Application Content |Sub Content |
|1. |About Live Stock Importation Act |Service Charter, Client Satisfaction Survey, Animal |
| | |Quarantine Organization Chart, Feedback |
|2. |Exports |Export inspection & certification procedure, Time schedules|
| | |for clearance, Fee & charges, Circular issued to export |
| | |certifying authority. |
|3. |Laws |Laws related to Livestock/Livestock Product |
|4. |Import |Animal order & amendments, Issuance of the sanitary import |
| | |permit, Import inspection & clearance, Procedure of |
| | |quarantine inspection, Time schedules for clearance, Fee & |
| | |charges, List of Livestock /LSP Division to require Animal |
| | |Quarantine clearance, Sampling & health certificate request|
| | |form |
|5. |Contact us |All the office addresses |
|6. |Related link |All the general users, importer/exporter would click on the|
| | |related link to get the information about all the |
| | |stakeholders available on the AQIS web page through |
| | |hyperlink. |
2 DATABASE MANAGEMENT
|S No. |Sub Content |
|1. |Database on requirements for import & export of Livestock /LSP |
|2. |Database of AQC notified laboratories |
|3. |Database on importer & exporter |
|5. |Database on commodity, country & port |
|6. |Providing access of PSC to NPPO of other countries |
|7. |FAQ on export & import procedure for Livestock /LSP & related government schemes |
|8. |Resolution of personalized queries |
3 SMS MANAGEMENT
|1. |SMS alert sent to exporter or importer after scrutiny of document in case of deficiency (IP/PSC/SIP/AQC) |
|2. |SMS based information for IP/PSC issued or rejected in case of PQIS and NOC/Provisional AQC /Final AQC issued or rejected |
| |in case of AQIS. |
4 PAYMENT GATEWAY INTEGRATION
|S.No. |Payment online ------- through payment gateway --------- Availability of services online 24 X 7 ( 99.9%) uptime |
|1. |The payment gateway would be used by the Importer / Exporter Importer |
| |To make payment for import / export certification like IP, PSC, AQC, SIP. This will facilitate the payment to be made|
| |through net banking, debit card, credit card, cash and draft |
2 SYSTEM INTERFACES :-
The system shall so be designed in such a manner that there should be linkages with other existing systems. The automated application shall be a web based application / interface which will be incorporated with features like certificate generation with the facility of viewing them online. These results shall be made available in CAP for quick dissemination of results. Besides this, there will also be push SMS’s to the different stakeholders informing them about the various information’s within the system
[pic]Diagram 2: System Interface
3 USER INTERFACES:-
Web based Graphical User Interface (GUI) will be provided. Portal will be completely menu driven and user friendly. The GUI consists of the various Input forms, output screens along with the help files provided as per the requirement.
[pic] Diagram 3: User Interface
4 HARDWARE INTERFACES
No specific hardware interface would be required for this application.
The following hardware interfaces are required to access the portal:
Computer System: any x86 based computer
Printer: A Laser Printer will be needed to take the various outputs of the system time to time.
5 SOFTWARE INTERFACES
At Client End: Base OS: Any Windows/Linux based operating system or any other system having graphical user interface based Operating System
Browser: Internet Explorer 6.0 or above, Mozilla Firebox, Google Chrome or Opera
At Server End: Base OS – Will be decided later at the development stage Framework - Will be decided later at the development stage
Technology Platform – Will be decided later at the development stage
Database - Will be decided later at the development stage
Browser – Internet Explorer 6.0 or above
2.1.6 COMMUNICATIONS INTERFACES
The Application will work on Local Area Network (LAN) or Internet also. Along with this, the system will interact with the SMS Gateway server to push SMS to different stakeholders and emails servers also to send the automated emails generated from the system to various stakeholders of the system
2.1.7 MEMORY CONSTRAINTS
The proposed system will be suitably performed on any system. However, lower primary memory will not debar the system from running but performance might not reach up to expected level.
There is no such need in major secondary memory availability, so it is not constrained.
2.1.8 OPERATIONS
During the course of application usage, general user including CAP users will not be required perform any operation other than system features. Applications and portals will be hosted at Data Centre in secured government domain. Normal maintenance operations such as backup will be scheduled and automated and will be looked into by the system administrators in case of any recovery is to be done. User initiations not needed. No additional data processing operations by the users would be required except the system interactive options.
2.1.9 SITE ADAPTATION REQUIREMENTS
The application proposed will be developed as a web based application. For running the application the computer system having a basic GUI based Operating System and browsers will be required as minimum requirements along with internet connectivity.
Skilled manpower along with data entry operators at various locations like centre, states and other offices at different level will be required to upload and update the information/data.
2 PRODUCT FUNCTIONS(CURRENT AS IS BUSINESS PROCESSES)
The existing information on e-certification to Exporter/ Importer linkage:
[pic] Diagram 4: E-certification to Exporter/ Importer linkage
1 ANIMAL QUARANTINE CERTIFICATION PROCEDURES
The major objective of the Animal Quarantine and certification Station (AQCS) is to prevent the ingress of livestock and poultry exotic to India as per provisions of livestock importation Act, 1898. It is essential to obtain the appropriate NOC from this body prior to transport of pets- dogs and cats, live chicks and other livestock products through air travel or sea route. [pic]
Diagram 5: Certificate Issuance Authorities
Trade Division: This division does the process for issuing SIP which is requiring for importing of livestock product.
Animal Quarantine Station: This station does the process for issuing quarantine certification for importing as well as exporting of LS & LSP.
There are three categories of LS/LSP under the Stock Importation Act 1898
1. Free 2.Restricted and 3. Prohibited
1. Free Category: There are Livestock’s/Livestock Products which are free to import into India from other countries for which sanitary import permit is required.
2. Restricted Category: There are Livestock’s/Livestock Products which are restricted, the import into India of these products shall be allowed only against a license issued by DGFT.
3. Prohibited Category: The department of Animal Husbandry and Dairying has banned the import of Livestock’s/Livestock Products from selected countries due to the outbreak of virus or disease.
The following processes are being followed by DADF and Animal Quarantine Certification Station manually
1. Issuance of Sanitary import permit (being issued from DADF) a. Issuance of SIP: Case 1 (Meeting Case) b. Issuance of SIP: Case 2 (Fast Track Case) c. Issuance of SIP: Case 3 (On-file Case) 2. Collection of fee/charges for treatment/lab/vaccination from Importer/Exporter 3. Issuance/Rejection of Animal Quarantine Certificate in case of Import for a. Livestock b. Livestock Product c. Pet Animal (Dog/Cat) 4. Issuance/Rejection of Animal Quarantine Certificate in case of Export for a. Livestock b. Livestock Product c. Pet Animal (Dog/Cat)
Existing Process of each section has been described below:
1 ISSUANCE OF SANITARY IMPORT PERMIT:
This section contains the work flow that how an importer can get the Sanitary import permit for Livestock Product from DADF.
The Sanitary import permit shall be issued by DADF for import of livestock product and for livestock; license will be issued from DGFT & verified by DADF. The import permit shall lay down the specific condition that will have to be fulfilled in respect of consignment, including pre shipment certification and quarantine checks. The permit shall also specify the post – import requirements with regard to quarantine inspections, sampling & testing. The import permit issued shall be valid for a period of six month. There are two type of forms which importer has to fill depends upon the use of import product.
Form A: - Application for permit to import livestock products for personal consumption.
Form B: - Application for permit to import livestock product for trading/Marketing.
There are three Cases for Issuance of SIP
[pic]
Diagram 6: Type of SIP
1 Issuance of SIP Process (Meeting case)
• Application along with documents sent to section officer for scrutiny if all the relevant documents are attached then section officer forwards the application to AC trade for verification. • If all the relevant documents are not attached with the application then section officer sends back the application to the importer. • AC trade verifies all the documents and sent it to the divisional head for comments. • If the application is for Dairy Product then the application will go to Dairy division and LH Division • If the application is for Meat feather, GP stock then the application will to LH division. • If the application is for fishing items then the application will go to FY division. • Each department process the application • Dairy division • Agenda received from trade division by asst. commissioner. • Comments prepared by asst. commissioner. • Comments sent to technical officer for input if any. • Comments sent to DDG for approval. • If not approved correction made by AC and comment finalized. • If approved final comment will be discussed in meeting with trade division. • LH division • Agenda received from trade division by asst. commissioner. • Comments prepared by ass. Commissioner. • Comments sent to deputy commissioner for input if any. • Comment sent to JS for input if any. • Comment sent to JS divisional head for approval. • If not approved correction made by AC trade and comment finalized. • If approved final comment will be discussed in meeting with trade division. • FY division • Agenda received from trade division by fishery research officer • Comments prepared by fishery research officer. • Comments sent to fishery development commissioner for input if any. • Comment sent to JS divisional head for approval. • If not approved correction made by AC trade and comment finalized. • If approved final comment will be discussed in meeting with trade division.
• After receiving comments from all the divisions, AC trade will call the meeting with all the divisional head and puts agenda. • If JS trade approves the agenda then application sends back to AC trade for signature • After signature of AC trade SIP issued to the importer. • If JS Trade not approved the agenda/comments on SIP then letter issued to importer with reason for not issuing the SIP.
Work Flow for Issuance of Sanitary Import Permit: Case-1 (Meeting Case)
[pic] Diagram 7: Meeting Case
2 Issuance of SIP Process (Fast Track)
• Application along with documents sent to section officer for scrutiny if all the relevant documents are attached then section officer forwards the application to AC Trade for verification. • If all the relevant documents are not attached with the application then section officer sends back the application to the importer. • AC Trade verifies all the documents & sends it to Director Trade for approval. • If Director Trade approves then approved application sends back to AC Trade for signature. • After signature AC Trade issues SIP to the importer. • If Director Trade not approved the application/document then letter issued to importer with reason for not issuing the SIP.
Work Flow for Issuance of Sanitary Import Permit: Case-2 (Fast Track)
[pic] Diagram 8: Fast Track
Fast Track process items are as follows:
1. Fish Feed 2. Fish Food 3. Whey Protein 4. Cheese 5. Hilsa 6. Bovine Serum
3 Issuance of SIP Process (On File)
• Application along with documents sent to section officer for scrutiny if all the relevant documents are attached then section officer forwards the application to AC Trade for verification. • If all the relevant documents are not attached with the application then section officer sends back the application to the importer. • AC Trade verifies all the documents & sends it to divisional head for comments. • If the application is for Dairy Product then the application will go to Dairy division and LH Division both • If the application is for Meat feather, GP stock then the application will to LH division. • If the application is for fishing items then the application will go to FY division. • Each department process the application Dairy division • Agenda received from trade division by asst. commissioner. • Comments prepared by asst. Commissioner. • Comments sent to technical officer for input if any. • Comment sent to DDG for approval. • If not approved correction made by AC Trade and comments finalized. • If DDG approved then final comments will be discussed in meeting with trade division.
LH division • Agenda received from trade division by asst. commissioner. • Comments prepared by asst. Commissioner. • Comments sent to deputy commissioner for input if any. • Comment sent to JC for input if any. • Comment sent to JS (divisional head) for approval. • If JS approved then final comments will be discussed in meeting with trade division. • If not approved correction made by AC and comments finalized
FY division • Comments prepared by fishery research officer. • Comments sent to fishery development commissioner for input if any. • Comment sent to JS (divisional head) for approval. • If approved final comments will be discussed in meeting with trade division. • If not approved correction made by AC Trade and comment finalized • After receiving comments from all the divisions, AC Trade will call the meeting with all the divisional head and puts agenda.
• Director trade receives comments from all divisional heads if he approves then approved application/document sends back to AC Trade for signature. • After signature of AC trade SIP issued to the importer. • If Director Trade not approved the application/document then letter issued to importer with reason for not issuing the SIP.
Work Flow for Issuance of Sanitary Import Permit: Case-3(On file)
[pic] Diagram 9: On File
Suggestions:
• Post import condition should be computerized this will improve the time & speed of the process. It will eliminate the process of internal file movement within the department.
• Back and forth movement of the file should be there in the application to undo the wrong movement of file.
Animal Quarantine Certification Station:
Animal Quarantine Certification Station does certification process for quarantine clearance of Livestock, Livestock Product & Pet Animal in case of Import & Export.
[pic] Diagram 10: AQCS
There is no fee/charge for Issuance of SIP or AQCS certification. Fee for treatment/lab/vaccination if required during the quarantine certification process for livestock/livestock product will be paid by the Importer/Exporter. In case of livestock, 30 days observation fee at quarantine station has to pay by the Importer. Example: for a horse the observation fee is Rs. 250 per day per horse. Similarly the observation fee may vary, depends on the livestock. In case of livestock treatment/vaccination at quarantine station if required will be paid by the Importer/Exporter. In case if Lab test is required for sample of livestock/livestock product then Importer/Exporter has to pay the Lab fee to the quarantine officer by Cheque and the payment will be made when the sample is taken.
2 ISSUANCE OF ANIMAL QUARANTINE CLEARANCE CERTIFICATE IN CASE OF IMPORT
No Objection Certificate for import of companion animals (only pet dogs and cats) into India. Import of animals (birds, mammals, fish or reptiles) or animal products ( meat-raw or processed- skin, hoof, feather, shuttlecock, buttons etc.) other than the above including laboratory animals will necessitate the procurement of an import license/sanitary import permit from a competent authority(DGFT)/ AQCS prior to issuance of the NOC from the AQCS.
1 Import of Livestock
This section contains the work flow that how an importer can get the Animal Quarantine Certificate for Livestock from AQCS.
• First information: the importer or his/her authorized representative should contact the animal quarantine officer in advance about the intended import consignment. • The details pertaining to the same must be physically submitted to the office of the AQCS on a prescribed format of the office along with photocopies of the following o Veterinary certificate/ Health certificate of the animal issued only by the designated veterinary officer of the exporting country confirming the health status of the animal and its fitness for the export/ travel. This certificate should be only in English (or bilingual with one language as English). o Details of vaccination. o Copies of the passport and travel ticket of the owner of the animal. • After satisfactory verification of the above documents, the AQCS office will issue the NOC for import of the animal consignment which needs to be carried physically along with the animal. • On arrival at Sea port/ Airport, the importer will report to the quarantine officer with the original copies of all the above listed documents for obtaining a provisional Quarantine Clearance Certificate which will be issued upon satisfactory verification of the documentation and the physical health of the animal. • After quarantine clearance from custom, the quarantine officer will bring the livestock/animal to the quarantine station for 30 days for health observation, and importer has to pay the fee for 30 days observation to quarantine station.
• On satisfactory completion of 30 days of home quarantine, the importer must contact the AQCS office for final clearance of the animal from the quarantine angle.
Work Flow of Animal Quarantine Certification for Livestock in Case of Import:
[pic]
Diagram 11: As-Is of AQC for Livestock Import
Documents to be attached along with the application for advance NOC/Clearance of Livestock: 1) DGFT License, if any. 2) SIP, if any. 3) Testing fee & accommodation charges, if any. 4) Custom related documents. 5) Advance copy of Official Health Certificate from the Country of Origin as per the Indian Health Protocol.
2 Import of Livestock Product
This section contains the work flow that how an importer can get the Animal Quarantine Certificate for Livestock Product from AQCS. Livestock products include meat and meat products of different types that comprise fresh, chilled and frozen meat as well as tissue or organs of poultry, pig, sheep and goat. It also consists of egg and egg powder; milk and milk goods; pet foods of animal origin and embryos, ova or semen of cows, sheep and goats. No livestock product may be imported into India without a valid sanitary import permit. All livestock products with valid sanitary import permits may be brought into India only through seaports or airports where Animal Quarantine and Certification Services Stations are situated. These stations are located in the cities of Delhi, Mumbai, Kolkata and Chennai. When livestock products arrive at the checkpoint, they will be checked by the Officer-in-charge of the Animal Quarantine and Certification Services Station or any other veterinary officer duly approved by the Department Of Animal Husbandry and Dairying.
• Application filled along with documents sent to quarantine officer for scrutiny if all the relevant documents are attached, NOC issued before lifting the livestock from the country of origin.
• If all the relevant documents are not attached with the application then quarantine officer sends back the application to importer with reason for not granting NOC.
• As per the import guidelines/conditions of the country all the health related documents will be checked by the quarantine officer.
• If all the relevant document & guidelines/conditions are met, issue of AQC clearance certificate release with or without sampling/testing
• If all the relevant document & guidelines/conditions are not met then deportation / destruction of livestock product as per case (whichever required).
• If with sampling / testing is required then sampling is taken from the consignment for testing and AQC issued to the importer. • If the consignment is not require sampling / testing or not require quarantine clearance then • AQC issued to the importer after examination of paper and consignment.
Work Flow of Animal Quarantine Certification for Livestock Product in Case of Import:
[pic] Diagram 12: As-Is of AQC for Livestock product Import
Documents to be attached along with the application for Clearance of Livestock Products: 1) DGFT License, if any. 2) SIP, if any. 3) Testing fee if any. 4) Custom related documents. 5) Advance copy of Official Health Certificate from the Country of Origin as per the Indian Health Protocol. 6) Examination and sampling.
3 Import of Pet Animal (Dog / Cat)
• First information: the importer or his/her authorized representative should contact the animal quarantine officer in advance about the intended import consignment. • The details pertaining to the same must be physically submitted to the office of the AQCS on a prescribed format of the office along with photocopies of the following • Veterinary certificate/ Health certificate of the animal issued only by the designated veterinary officer of the exporting country confirming the health status of the animal and its fitness for the export/ travel. This certificate should be only in English (or bilingual with one language as English). • Pet passport with details of vaccination. • Copies of the passport and travel ticket of the owner of the animal.
• After satisfactory verification of the above documents, the AQCS will issue the NOC for import of the animal consignment before lifting the animal from the country of origin, which needs to be carried physically along with the animal.
• If Documents are incomplete during verification then NOC will not be issued to importer with reason. • On arrival at airport, the importer will report to the quarantine officer with the original copies of all the above listed documents for obtaining a provisional Quarantine Clearance Certificate which will be issued upon satisfactory verification of the documentation and the physical health of the animal. • On satisfactory completion of 30 days of home quarantine, the importer must contact the AQCS for final clearance of the animal from the quarantine angle. • Final quarantine health certificate issued to the importer.
Work Flow of Animal Quarantine Certification for Pet Animal (Dog / Cat) in Case of Import:
[pic]
Diagram 13: As-Is of AQC for Pet Animal Import
3 ISSUANCE OF ANIMAL QUARANTINE CERTIFICATE IN CASE OF EXPORT
This section contains the work flow that how an Exporter can get the Animal Quarantine Certificate for Livestock from AQCS.
The major objective of the Animal Quarantine and certification Station (AQCS) is to prevent the ingress of livestock and poultry exotic to India as per provisions of livestock importation Act, 1898. It is essential to obtain the appropriate clearance from this body prior to transport of pets- dogs and cats, live chicks and other livestock products through air travel or sea route.
1 export of Livestock
Health Certificate/ Export fitness Certificate on standard format or as is required by the importing country – within the jurisdiction of this office – towards facilitation of export of live animal as per the international requirements. • Application filled along with documents sent to quarantine officer for scrutiny/check all relevant documents are attached, as per the export guidelines/norms of India.
• If all the relevant documents are not attached with the application then quarantine officer sends back the application to the exporter with reason for not granting AQC health certificate communicated to the exporter.
• If all the relevant document & guidelines/norms are met, then quarantine officer will see the requirement when AQC health certificate is to be issued, after quarantine observation & testing or without quarantine observation & testing as per the protocol of importing country and exporting norms of India.
• If with quarantine observation & testing is require then o Quarantine observation done and sample taken for testing o Sample sent to lab for testing • If test report is OK then AQC health certificate issued to the exporter and if test report is not satisfactory then exporter will be informed through a letter with reason for not granting AQC health certificate • If without quarantine observation & testing is require then o After examination of the documents & health of livestock, AQC health certificate will be issued to the exporter.
Work Flow of Animal Quarantine Certification for Livestock in Case of Export:
[pic] Diagram 14: As-Is of AQC for Livestock Export
Documents to be attached along with the application for Certification of Livestock: 1) DGFT License, if any. 2) Testing fee & accommodation charges, if any. 3) Custom related documents. 4) Copy of Official Health requirement of importing Country. 5) Other applicable norms of India.
2 export of Livestock Product
This section contains the work flow that how an Exporter can get the Animal Quarantine Clearance Certificate for Livestock Product from AQCS.
• Application filled along with documents sent to quarantine officer for scrutiny/check all relevant documents are attached, as per the export guidelines/norms of India.
• If all the relevant documents are not attached with the application then quarantine officer sends back the application to the exporter with reason for not granting AQC health certificate communicated to the exporter.
• If all the relevant document & guidelines/norms are met, then quarantine officer will see the requirement when AQC health certificate is to be issued, after quarantine observation & testing or without quarantine observation & testing as per the protocol of importing country and exporting norms of India.
• If with quarantine & testing is require then o Sample taken for testing and registration done as per the protocol and exporting norms of India o Sample sent to lab for testing • If test report is OK and other records are satisfactory then AQC health certificate issued to the exporter and if test report is not satisfactory then exporter will be informed through a letter with reason for not granting AQC health certificate • If without quarantine & testing is require then o After inspection of consignment / representative samples and examination of the documents, AQC health certificate will be issued to the exporter.
Work Flow of Animal Quarantine Certification for Livestock Product in Case of Export:
[pic]
Diagram 15: As-Is of AQC for Livestock Product Export Documents to be attached along with the application for Certification of Livestock Products: 1) DGFT License, if any. 2) Testing, if any. 3) Custom related documents. 4) Copy of Official Health requirement of importing Country. 5) Other applicable norms of India.
Note: In Case of pet animal (Dog/Cat), any person can bring / carry less than or equal to two pet animals from other country into India for personal purpose in case of import/export.
3 export of Pet Animal (Dog / Cat)
• The exporter must contact the AQCS before the expected date of export with the completed application form and the following documents/information. o Health record of the animal (pet passport) with vaccination details and scrum antibody profile (if applicable) o Copy of import license and export permit ( if applicable) o Copy of health and Zoo sanitary requirements of the importing country of the requirements as mutually agreed upon. o Travel ticket and a copy of the passport of the owner of the pet. • Or as per the SIP of the importing country testing/inspection/vaccination done • If testing/inspection/vaccination report is satisfactory then • AQC health certificate will be issued to the exporter else reason for not granting AQC health certificate is communicated to the exporter.
Work Flow of Animal Quarantine Certification for Pet Animal (Dog / Cat) in Case of Export:
[pic] Diagram 16: As-Is of AQC for Pet Animal Export
As-Is of Mumbai: In case of Animal Quarantine, they are following the same process of import and export as followed by Delhi office only the different formats are being used by them to issue AQC.
Formats from Mumbai are attached in the Annexure number- 14, 15, 6,17,19,20,21,22,36
As-Is of Bangalore: There is no Animal quarantine office in Bangalore, they directed to Chennai office for any kind of information related to animal quarantine.
As-Is of Madhya Pradesh: HSADL lab, Bhopal is Animal quarantine test lab; they are using their own software to generate lab test reports for AQCS and importer. Test reports are being sending to AQCS/importer via email/hard copy. Our scope is identifying if any linkage can be developed to see HSADL lab test report if required by AQCS, which can be done only when they are using any application.
Customs Department: Central Board of Excise and Customs (CBEC) is a part of the Department of Revenue under the Ministry of Finance, Government of India. It gives the custom clearance for import/export of livestock/ livestock product/plant/plant material.
MPEDA: The Marine Products Export Development Authority (MPEDA) was constituted in 1972 under the Marine Products Export Development Authority Act 1972 (No.13 of 1972). The role envisaged for the MPEDA under the statute is comprehensive - covering fisheries of all kinds, increasing exports, specifying standards, processing, marketing, extension and training in various aspects of the industry. MPEDA functions under the Ministry of Commerce, Government of India and acts as a coordinating agency with different Central and State Government establishments engaged in fishery production and allied activities. They shared these two websites: www.MPEDA.com , www.empeda.nic.in
DGFT: Directorate General of Foreign Trade is a government organization in India responsible for the formulation of Exim guidelines and principles for Indian importers and Indian exporters of the country. Before 1991, DGFT was known as the Chief Controller of Imports & Exports (CCI&E).
Some of the major functions of DGFT and its regional offices through out the country are as follows:
• To implement the Exim Policy or Foreign Trade Policy of India by introducing various schemes and guidelines through its network of DGFT regional offices thought-out the country. DGFT perform its functions in coordination with state governments and all the other departments of Ministry of Commerce and Industry, Government of India.
• To Grant Exporter Importer Code Number (IEC) to Indian Exporter and Importers. IEC Number is a unique 10 digit code required by the traders or manufacturers for the purpose of import and export in India. DGFT IEC Codes are mandatory for carrying out import export trade operations and enable companies to acquire benefits on their imports/exports, Indian customs, export promotion council’s etc in India.
• DGFT permits or regulate Transit of Goods from India or to countries adjacent to India in accordance with the bilateral treaties between India and other countries.
• To promote trade with neighboring countries.
• To grant the permission of free export in Export Policy Schedule 2.
• DGFT also play an important role in controlling DEPB Rates.
• Setting standard input-output norms is also controlled by the DGFT.
• Any changes or formulation or addition of new codes in ITC-HS Codes are also carried out by DGFT (Directorate General of Foreign Trade).
FSSAI: Issues the food safety license to importer as per the standard mention on their website, without the license any importer will not be able to apply for SIP.
NPQS & FSSAI both require search option/ web service to verify the certificate issued by them.
AQCS: This body regulates the export of Livestock & Livestock products from Animal Quarantine facilities. It is essential to obtain the appropriate permits from this body prior to transport of pets- dogs and cats, live chicks and other livestock products through air travel.
FPI: The Ministry of Food Processing Industries, set up in July 1988, is the main central agency of the Government responsible for developing a strong and vibrant food processing sector.
The functions of the Ministry can be broadly classified under policy support and development activities:
a) Formulation and implementation of policies for food processing sector with overall national priorities and objectives.
b) Facilitating creation of conducive environment for healthy growth of the food-processing sector.
c) Promoting rationalization of tariffs and duties relating to food processing sector.
DADF: Department of Animal Husbandry Dairying & Fisheries (DADF) is responsible for matters relating to livestock production, preservation, protection and improvement of stocks, dairy development. The main focus of the department is on: a) Preservation & Protection of livestock through provision of health care. b) Strengthening of central livestock farms (Cattle, Sheep and Poultry). c) Expansion of aquaculture in fresh, brackish water, welfare of fisher folk, etc.
According to the TO-BE process all the stakeholders will be integrated through search option & custom will be integrated by web services/ftp. The URL of all the stake holders will be in related link option on AQIS webpage to directly access.
2 PLANT QUARANTINE CERTIFICATION PROCEDURES
1. Plant/Plant material application PQIS is fully operational and have been issued approximately 2 lacs PSC through the PQIS application (e-certification) till date, its web site is http://plantquarantineindia.nic.in .
Specific Variations in Processes & Formats :
As-Is of Mumbai: They are using PQIS application in Plant Quarantine office. Formats from Mumbai are attached in the Annexure number- 6, 7, 8,9,10,11,12,13
National Plant Quarantine Service: NPQS is also using the PQIS application & requires integration of their running application with custom to share BOE (Bill of Entry) to verify all the import items.
As-Is of Bangalore: PQIS application is being used in plant quarantine office Bangalore.
Referred these two websites. 1. http://plantquarantineindia.org/ 2. http://plantquarantineindia.nic.in/PQISMain/Default.aspx
In PSC issuing authority office, manual process is being followed for issuances of phyto sanitary certificate. As-Is Cochin:
Common Concern None of the department was informed about the NeGP project. 2. There are few stakeholders of PQIS from where the inputs have been taken during the requirements gathering for integration of PQIS application with the stakeholders. The stakeholders, their functions and how the PQIS can be linked/integrated to its stakeholders are studied, are given below:
.
APEDA: Main function is to do the registration of exporter for which they issued RCMC number to them. This is valid for 5years.
They do testing for rice & grapes as per importing country requirements, because without testing certificate issued by APEDA exporter can not export the goods to other country. Apart from grapes & rice they issue the certificate for peanut, pomegranate, ground nut & for plant product.
The entire certificate issued by them through online application except meat plant certificate which is being issued manually. The certificate (RCAC) issued by them is valid for 3 months.
NPQS require search option/ web service on APEDA application to verify RCMC & RCAC certificates issued by them. RCAC format is attached in the annexure- 33
EIC: Issues health certificate for following six products basmati rice, fish, honey, milk products, poultry meat & egg products for Europe, Russia, Vietnam and Bangladesh as per government mandate. Exporter should attach the EIC health certificate issued by EIC with PSC before exporting his goods to other country.
NPQS require search option/ web service to verify certificate data issued by EIC.
ARBRO pharmaceuticals: is testing laboratory, which does testing & enters test report data on APEDA application.
Similarly, through APEDA search option we can authenticate the certificate issued by laboratory. Coconut Development Board
They provided the website:
1. http://www.coconutboard.nic.in
Cashew-nut and Cocoa Development
They provided the website:
1. http://www.dccd.gov.in all info available here.
Cashew Export Promotion Council
They provided the website: http://cashewindia.org Pesticide Residue Lab (Ultra Lab Bangalore): This Ultra lab does Pesticide Residue Analysis of different agriculture commodities
PSC issuing Authority:- PSC issuing authority is part of PQS department. They are authorized by the department to issue the PSC certificate on their behalf.
PQS: Directorate of Plant Protection, Quarantine & Storage, Department of Agriculture & Cooperation has recently got developed a web portal http://plantquarantineindia.nic.in for on-line registration of Exporters and Importers of agricultural commodities seeking the following services:-
• Issuance of Import Permit • Issuance of Import Release Order • Issuance of Phytosanitary Certificate
NBPGR: The National Bureau of Plant Genetic Resources has its Headquarters at New Delhi Objectives of NBPGR • To plan, organize, conduct and coordinate exploration and collection of indigenous and exotic plant genetic resources. • To undertake introduction, exchange and quarantine of plant genetic resources. To characterize, evaluate, document and conserve crop genetic resources and promote their use, in collaboration with other national organizations. • To develop information network on plant genetic resources. • To conduct research, undertake teaching and training, develop guidelines and create public awareness on plant genetic resources.
DMI: The Directorate of marketing and inspection implements the agricultural marketing programs of the Union Government under the supervision and control of Union Ministry of Agriculture. It aims at bringing integrated development of marketing of agricultural and allied produce in the country. It is headed by Agricultural Marketing Adviser to the Government of India (AMA). It maintains a close liaison between Central and State Governments through its Branch Head office at Nagpur, 11 Regional Offices and 37 sub-offices spread all over the country. It has a network of 22 Regional Agmark Laboratories with Central Agmark Laboratory at Nagpur as apex laboratory.
DPPQS: Director The Directorate of Plant Protection, Quarantine & Storage established under Department of Agriculture & Co-operation of Ministry of Agriculture, Government of India.
The ongoing activities assigned under the scheme include: • To issue import permits (IP) with additional declarations and special conditions to facilitate safe imports of agricultural products. • To undertake quarantine inspection and laboratory testing of plants and plant material to ensure freedom from exotic pests. • To undertake phytosanitary certification (for issuance of Phytosanitary Certificates (PSCs); 150 Nos. of Officers from Central/ State/ UT Governments have been authorized for this purpose. • To undertake fumigation/disinfestations/disinfections of commodities to control infestation/infection. • To undertake certification of post-entry quarantine facilities and inspection of imported growing plants and plant material; 41 Nos. of Inspection Authorities have been designated. • To support Export market access for India’s Agriculture products from the phytosanitary point of view. • To facilitate safe global trade in agriculture by assisting the producers and exporters by providing a technically competent and reliable phytosanitary certificate system to meet the requirements of trading partners. • To provide Grants-in-aid to Designated Inspection Authorities to meet the travel expenses and also to State PSC issuing authorities for equipping them with minimal equipments required for export inspection/certification. • Granting approval/accreditation of Treatment providers in line with the requirement of ISPM-15 As-Is of Himanchal Pradesh: Steps to be followed for the Import of planting material in Himanchal Pradesh
As per guidelines of the new Policy on seed development, 1988, Government of India, Ministry of Agriculture, Department of Agriculture & Cooperation, the certain categories are eligible to import the seeds and planting materials including Department of Horticulture of the state Governments/ Growers of vegetable & flowers and the same should be got registered with the Director of Horticulture of the state Government. All imports of seeds and plant material will require a permit granted by the Plant Protection Advisor to the Government of India, which will be issued within the minimum possible time frame. All import of seeds and planting materials, etc. will be allowed freely subject to EXIM Policy guidelines and the requirements of the Plants, Fruits and Seeds (Regulation of import into India) Order, 1989 as amended from time to time.
I. Registration with the Department of Horticulture, Himanchal Pradesh as Importer. The following procedure is followed by the importer for registration with the department of Horticulture for the import of planting material: • Submission of the Application form along with o Revenue record of the possession of land (Titima/ Jacaranda/ Lease Deed minimum 10 year) o Copy of invoice/ reservation of plant material/ confirmation letter from the nursery from which the farmer is interested to import the plant material.
[pic] Diagram 17: As-Is of Himanchal Pradesh in case of Import
APPLICATION FOR REGISTRATION UNDER PARA 4.4.4 OF THE NEW POLICY ON SEED DEVELOPMENT OF
GOVERNMENT OF INDIA
1. Name of the Grower : 2. Complete Postal Address: 3. Details of the Land Holding: (Documentary evidence in support of the same has to be produced). 4. Details of the Fruit Crops Grown in the last three years:
|S.No |crop |year – 1 |year – 2 |year - 3 |
|1 | | | | |
|2 | | | | |
|3 | | | | |
5. Details of Flowers/Ornamental Plants grown during the last three years:
|S.No |crop |year – 1 |year – 2 |year - 3 |
|1 | | | | |
|2 | | | | |
|3 | | | | |
6. Details of the values of fruits and flowers sold in the last three years : Value (In Rupees)
|items |year – 1 |year – 2 |year – 3 |
|(a) Fruits | | | |
|1. | | | |
|2. | | | |
|3. | | | |
|Flowers | | | |
|1. | | | |
|2. | | | |
|3. | | | |
7. Details of the Planting Material imports if any handled earlier :
8. Particulars of the Imports Planned Now :
|country |farm/company/nursery |crop |name of variety |quantity |
| | | | | |
|Total : | | | | |
9. Details of the PEQ Facilities Proposed to be established/already available
I hereby certify that all the above particulars are true, correct and complete.
Signature of the Importer/Applicant
Date:
Place:
According to the TO-BE process all the stakeholders will be integrated through search option & custom will be integrated by web services/ftp. The URL of all the stake holders will be in related link option on PQIS webpage to directly access.
3 PRODUCT FUNCTIONS( TO BE WORK FLOW)
1 THERE WOULD BE THREE MODULE OF THE ANIMAL QUARANTINE CLEARANCE APPLICATION
1) Issuance of Sanitary Import Permit 2) Issuance of Animal Quarantine Certificate (AQC) for LS/LSP/Pet Animal in case of Import. 3) Issuance of Animal Quarantine Certificate (AQC) for LS/LSP/ Pet Animal in case of Export.
These three modules can further be divided into: 1. Issuance of Sanitary import permit (being issued from DADF) a. Issuance of SIP: Case 1 (Meeting Case) b. Issuance of SIP: Case 2 (Fast Track Case) c. Issuance of SIP: Case 3 (On-file Case) 2. Issuance/Rejection of Animal Quarantine Certificate in case of Import for a. Livestock b. Livestock Product c. Pet Animal (Dog/Cat) 3. Issuance/Rejection of Animal Quarantine Certificate in case of Export for a. Livestock b. Livestock Product c. Pet Animal (Dog/Cat)
1 ISSUANCE OF SIP
1 Issuance of SIP (Case 1: Meeting Case)
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select SIP from the available links • Application (Form A or Form B) will be filled and submitted along with required documents online. The application will be available in the inbox of section officer. • The section officer will receive the form (In original) along with the required documents (hard copy). Scrutiny of the form with all the documents will be done by the section officer and forwarded to AC trade for verification. • If all the relevant documents are not attached with the application then section officer will make the application deficient and the application moves to the importer inbox. Importer will receive the form and can edit and re-submit the form. • AC trade verifies all the documents, prepares agenda and sent it to the various divisions for comments. • If the application is for Dairy Product then the application will go to Dairy division and LH Division • If the application is for Meat feather, GP stock then the application will to LH division. • If the application is for fishing items then the application will go to FY division. • Each department process the application
Dairy division 1) Assistant commissioner receives the application from the trade division and prepares the comments. 2) Forward to DDG for approval of Comments. 3) DDG may forward the application to AC for either modify the comments or approves the comments. 4) AC (Dairy) will forward to AC (Trade) after the approval from DDG.
• LH division 1) Application received from trade division by asst. commissioner. 2) Comments prepared by asst. Commissioner. 3) Forwards to JS for approval of Comments 4) JS may forward the application to AC for either modify the comments or approves the comments. 5) AC (LH) will forward to AC (Trade) after the approval from JS.
• FY division • Application received from trade division by fishery research officer • Comments prepared by fishery research officer. Forwards to JS for approval of Comments JS may forward the application to AC for either modify the comments or approves the comments. • AC (LH) will forward to AC (Trade) after the approval from JS. • After receiving comments from all the divisions, AC trade puts agenda in a meeting with JS trade. • If JS trade approves the agenda then application sends back to AC trade for signature and issuance of SIP importer, SIP issued to importer. • If JS Trade not approved the agenda/comments on SIP then letter issued to importer with reason for not issuing the SIP.
[pic]
Diagram 18: To-Be of SIP (Case 1: Meeting Case)
2 Issuance of SIP Process (Case 2: Fast Track)
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select SIP from the available links • Application (Form A or Form B) will be filled and submitted along with required documents online. • Section officer will receive the form along with the required documents. Scrutiny of the form with all the documents will be done by the section officer and forwarded to AC trade for verification. • If all the relevant documents are not attached with the application then section officer sends back the application to the importer. Importer will receive the form and can edit and re-submit • AC Trade verifies all the documents & sends it to Director Trade for approval. • If Director Trade approves then approved application sends back to AC Trade for signature. AC forwards the application to SO/DPC to issue the certificate. • SIP issued to importer. • If Director Trade not approved the application/document then letter issued to importer with reason for not issuing the SIP.
[pic] Diagram 19: To-Be of SIP Process (Case 2: Fast Track)
3 Issuance of SIP Process (Case 3: On-file)
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select SIP from the available links • Application (Form A or Form B) will be filled and submitted along with required documents online. The application will be available in the inbox of section officer. • The section officer will receive the form (In original) along with the required documents (hard copy). Scrutiny of the form with all the documents will be done by the section officer and forwarded to AC trade for verification. • If all the relevant documents are not attached with the application then section officer will make the application deficient and the application moves to the importer inbox. Importer will receive the form and can edit and re-submit the form. • AC trade verifies all the documents, prepares agenda and sent it to the various divisions for comments. • If the application is for Dairy Product then the application will go to Dairy division and LH Division • If the application is for Meat feather, GP stock then the application will to LH division. • If the application is for fishing items then the application will go to FY division. • Each department process the application
Dairy division 1) Assistant commissioner receives the application from the trade division and prepares the comments. 2) Forward to DDG for approval of Comments. 3) DDG may forward the application to AC for either modify the comments or approves the comments. 4) AC (Dairy) will forward to AC (Trade) after the approval from DDG.
LH division 5) Application received from trade division by asst. commissioner. 6) Comments prepared by asst. Commissioner. 7) Forwards to JS for approval of Comments 8) JS may forward the application to AC for either modify the comments or approves the comments. 9) AC (LH) will forward to AC (Trade) after the approval from JS.
FY division • Application received from trade division by fishery research officer • Comments prepared by fishery research officer. Forwards to JS for approval of Comments JS may forward the application to AC for either modify the comments or approves the comments. • AC (LH) will forward to Director (Trade) after the approval from JS. • After receiving comments from all the divisions, Director Trade either approves or rejects the application. • If Director Trade approves, then application sends back to AC trade for signature and issuance of SIP to importer, SIP issued to importer. • If Director Trade not approved the application then letter issued to importer with reason for not issuing the SIP
[pic] Diagram 20:To-Be of SIP (Case 3: On-file)
Common Process Flow for AQIS & PQIS:
There are few common steps for users who want to use AQIS or PQIS application: • User will type CAP URL on browser to come on the home page of CAP • User will select/click links (AQIS/PQIS) available • User will fill and submit the application for user id and password • Verification of I/E code will be done by the system administrator of the respective applications • Login id will be enabled after verification of I/E code • Now user will login AQIS/PQIS respectively
[pic] Diagram 21: Common Process Flow for AQIS & PQIS
Note: In case of Livestock, importer will directly apply for animal quarantine certificate at AQCS with license from DGFT
2 ANIMAL QUARANTINE CERTIFICATION PROCEDURE
1 Import of Livestock
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select LS from the available links LS/ pet animal • Importer will submit application for NOC for lifting LS along with the relevant documents • A unique reference number will be issued to importer • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then NOC issued to importer and an SMS sent to importer for issuance of NOC • If application along with the documents attached is not satisfactory then importer informed with reason for not granting NOC through e-mail and an SMS sent to importer for rejection of NOC • After arrival, importer will submit application for Provisional AQC along with the relevant documents(BOE) • Verification of NOC along with the documents attached is done by the quarantine officer • Sample taken and sent to lab for testing if required • Provisional quarantine certificate issued • Payment (online/Cheque/dd/cash) made by the importer for observation/testing as per prevailing norms in case of LS. • Payment information received by quarantine officer • On receiving the sample and completing the test, lab incharge entered the report and sends to Quarantine officer. • If lab report is OK. Then quarantine certificate is issued and a copy of AQC sent to importer via-email and SMS sent to importer for issuance of final AQC. If lab report is not satisfactory deportation order is issued. • SMS sent to importer for deportation.
[pic] Diagram 22: To-Be of AQC for Livestock Import
2 Import of Livestock Product
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQCS application • Importer will submit application for Provisional AQC along with the relevant documents • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then NOC issued to importer for custom clearance and an SMS sent to importer for issuance of NOC • If application along with the documents attached is not satisfactory then importer informed with reason for not granting NOC through e-mail and an SMS sent to importer for rejection of NOC • Sample taken and sent to lab for testing if required • Provisional quarantine certificate issued • Payment (online/Cheque/dd/cash) made by the importer for testing as per prevailing norms in case of LS if required. • Payment information received by quarantine officer • On receiving the sample and completing the test, lab incharge entered the report and sends to Quarantine officer. • If lab report is OK. Then quarantine certificate is issued and a copy of AQC sent to importer via-email and SMS sent to importer for issuance of final AQC. If lab report is not satisfactory destruction order is issued. • SMS sent to importer for destruction.
[pic] Diagram 23: To-Be of Livestock product Import
3 Import of Pet Animal (Dog/Cat)
• Importer will type CAP URL on browser to come on the home page of CAP • Importer will select/click AQIS from the available links • Importer will login into the AQIS application • Importer will select Pet Animal from the available links LS/ pet animal • Importer will submit application for NOC along with the relevant documents • A unique reference number will be issued to importer • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then NOC issued to importer and an SMS sent to importer for issuance of NOC • If application along with the documents attached is not satisfactory then importer informed with reason for not granting NOC through e-mail and an SMS sent to importer for rejection of NOC • Importer will submit application for Provisional AQC along with the relevant documents • Verification of NOC along with the documents attached is done by the quarantine officer • Sample taken and send to lab if required • Provisional quarantine certificate issued • Payment (online/Cheque/dd/cash) made by the importer for testing/ Vaccination as per prevailing norms in case of LS if required. • Payment information received by quarantine officer • On receiving the sample and completing the test, lab incharge entered the report and sends to Quarantine officer. • Final quarantine certificate issued after 30 days of provisional quarantine certificate issued, a copy of AQC sent to importer via-email and SMS sent to importer for issuance of final AQC
[pic] • Diagram 24: To-Be of Pet Animal Import
3 ANIMAL QUARANTINE CERTIFICATION PROCEDURE
1 Export of Livestock
• Exporter will type CAP URL on browser to come on the home page of CAP • Exporter will select/click AQIS from the available links • Exporter will login into the AQIS application • Exporter will select LS from the available links LS/ Pet Animal • Exporter will submit application for AQC along with the relevant documents • A unique reference number will be issued to Exporter • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then with or without quarantine testing requirement checked • If LS not required any quarantine testing then AQC health certificate issued and a copy of AQC health certificate sent to exporter via e-mail • If LS is required quarantine testing then sample taken and sent to lab for testing • Exporter will receive information through system for making payment for testing • Payment (online/Cheque/dd/cash) made by the exporter for testing • Lab receives sample for testing • Quarantine officer receives lab report • If lab report is satisfactory then AQC health certificate issued and alert is issued If lab report is not satisfactory then export will receive an SMS for rejection of AQC • If lab report is satisfactory then Exporter submits request for custom clearance • LS released based on AQC • Exporter can print or download the AQC.
[pic] Diagram25: To-Be of AQC for Livestock Export
2 Export of Livestock Product
• Exporter will type CAP URL on browser to come on the home page of CAP • Exporter will select/click AQIS from the available links • Exporter will login into the AQIS application • Exporter will select LSP from the available links LS/ LSP • Exporter will submit application for AQC along with the relevant documents • A unique reference number will be issued to Exporter • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then with or without quarantine testing requirement checked • If LSP not required any quarantine testing then inspection of consignment and representative sample checked and AQC issued • If LSP is required quarantine testing then sample taken and sent to lab for testing • Exporter will receive information through system for making payment for testing • Payment (online/Cheque/dd/cash) made by the exporter for testing • Information of receiving payment to exporter will be sent through SMS as well as e-mail • Lab receives sample for testing • Quarantine officer receives lab report • If lab report is satisfactory then AQC issued and a copy of AQC sent to exporter via e-mail • If lab report is not satisfactory then export will receive an SMS for rejection of AQC • If lab report is satisfactory then Exporter submits request for custom clearance • LSP released based on AQC • Exporter can print or download the AQC.
[pic] Diagram 26: To-Be of AQC for Livestock Product Export
3 export of Pet Animal (Dog/Cat)
• Exporter will type CAP URL on browser to come on the home page of CAP • Exporter will select/click AQIS from the available links • Exporter will login into the AQIS application • Exporter will select Pet Animal from the available links LS/ Pet Animal • Exporter will submit application for AQC along with the relevant documents • A unique reference number will be issued to Exporter • Scrutiny of application along with the documents attached is done by the quarantine officer • If OK then lab testing or vaccination requirement checked • If LS not required any lab testing then vaccination done and AQC health certificate issued and a copy of AQC health certificate sent to exporter via e-mail • If LS is required quarantine testing then sample taken and sent to lab for testing • Exporter will receive information through system for making payment for testing • Payment (online/Cheque/dd/cash) made by the exporter for testing • Information of receiving payment to exporter will be sent through SMS as well as e-mail • Lab receives sample for testing • Quarantine officer receives lab report • If lab report is satisfactory then AQC health certificate issued and a copy of AQC health certificate sent to exporter via e-mail • If lab report is not satisfactory then export will receive an SMS for rejection of AQC • If lab report is satisfactory then Exporter submits request for custom clearance • LS(Pet Animal) released based on AQC • Exporter can print or download the AQC health certificate
[pic] Diagram 27: To-Be for Export of Pet Animal
2 PLANT QUARANTINE CERTIFICATION PROCEDURE
1 IMPORT CERTIFICATION: (Already Implemented)
Importer will type URL on browser to get into the CAP home page; once the importer reached on the CAP home page he/she will have option to select/click from the available links PQIS & AQIS. Importer will select PQIS from the available links then he/she will be on PQIS home page.
Import Permit (IP) • Importer will log into the PQIS application, he/she will fill and submit the application • Scrutiny will be done by the Scrutiny officer • If all the relevant documents are attached then Workflow for approval process starts. • If all the documents are not attached then Scrutiny officer will deficient/Reject the application • Message sent to importer for rejection of IP • Payment (online/Cheque/dd/cash) made by the importer • Information of Issuance of IP will be sent through email.
Import Release Order (IRO) • Application for IRO filled and submitted by the Importer for issuance of IRO • Scrutiny of the application/documents done by the Scrutiny officer • If all the relevant documents are attached then Workflow for approval process starts. • If all the documents are not attached then Scrutiny officer will reject the application • Payment (online/Cheque/dd/cash) made by the importer • Duty officer assign inspector for inspection • Inspection done and report submitted to the duty officer • If inspection report is OK • If testing required then sample taken and sent to lab for testing • If test report is OK then IRO issued and a copy of IRO sent to importer • IRO issued to the importer • If test report is not satisfactory then application rejected for IRO and importer informed with reason. • Email sent to importer for rejection of IRO. • Customs Informs in advance for PQ clearance
Customs Integration with PQIS:
• Structure of Message to be exchanged: Annexure – 4.41 enclosed • Process of Message Exchange:
o Customs will provide Id & password to PQS to access the Ice-Gate for accessing the message on import on daily basis.
o This will be used in generating MIS report only for import.
• Development is under progress.
[pic] Diagram 28: To-Be of PQIS Import Certification
2 EXPORT CERTIFICATION
Importer will type URL on browser to get into the CAP home page; once the importer reached on the CAP home page he/she will have option to select/click from the available links PQIS & AQIS. Importer will select PQIS from the available links then he/she will be on PQIS home page. • Exporter will log into the PQIS application, he/she will fill and submit the application • Scrutiny will be done by the Scrutiny officer • If all the relevant documents are attached then Workflow for approval process starts • A message through e-mail sent to exporter for making payment for Issuance of PSC • If all the documents are not attached then Scrutiny officer will reject the application • Payment (online/Cheque/dd/cash) made by the exporter. • Duty officer assign inspector for inspection • Inspection done and report submitted to the duty officer • If inspection report is not satisfactory then testing or treatment require • If testing required then sample taken and sent to lab for testing • If inspection report is OK • PSC issued to the exporter • If test report is not satisfactory then application rejected for PSC and exporter informed with reason. • Email sent to exporter for rejection of PSC
[pic] Diagram 29: To-Be of PQIS Export Certification
3 THERE ARE VARIOUS FUNCTIONALITIES IN THESE MODULE, COMMON FUNCTIONALITIES ARE GIVEN BELOW:
1. User & Role management 2. Registration of Importer/Exporter 3. E-payment 4. Scrutiny/Checking/verification of documents 5. Approval of documents by authorized person 6. Status tracking 7. Sending sample to Lab for testing 8. Receiving test report from Lab 9. Issuance of certificate(s) • SIP issued to Importer • In case of Animal Quarantine for Import of Livestock and Pet Animal, three certificates issued to Importer (NOC for lifting, Provisional Certificate and Final Quarantine Clearance Certificate) • In case of Animal Quarantine for Import of Livestock Product, two certificates issued to Exporter (NOC / Final Quarantine Clearance Certificate) 10. Grievance Redressal 11. SMS Management 12. E-mail management 13. Printing.
4 USER CHARACTERISTICS
Application will be part of CAP primarily used by the Exporters, Importers, PSC Issuing Authorities, Duty Officer/ Inspection Authority and Administrator from NIC. Apart from these users, some of the reports can be viewed by other Central Line Ministries/Departments and also the common man for the purpose of social audit.
|User |Characteristics |
|Exporter |Computer Savvy |
| |Well versed with internet |
|Importer |Computer Savvy |
| |Well versed with internet |
|PSC Issuing Authority |Computer Savvy |
| |Well versed with internet |
|Duty Officer |Computer Savvy |
|/Inspection Authority |Well versed with internet |
|NIC Admin. |Computer Savvy |
| |Well versed with internet |
|General User |Computer Savvy |
| |Well versed with internet |
5 CONSTRAINTS
• This will be an internet based application which will be designed, developed and centrally hosted in NIC’s Data Centre. • The users will be accessing the software application using various connectivity scenarios. • Database on Phyto-sanitary conditions for Import of Livestock & Livestock Product and mapping of HS code need to be authenticated & updated by DADF. • Providing access of PSC to NPPO of other countries, it is only possible when all other countries are agreed • Translating the phyto sanitary condition of foreign country language into English using Google translator not possible because it will change the meaning of the document.
6 ASSUMPTIONS AND DEPENDENCIES
• Master Data preparation and entry into AQIS application by DADF • Network infrastructure and development tools are available for development team for testing, implementation & integration as per schedule. • Changes, if any should be reported within the stipulated time frame for incorporation in the SRS. Any changes not in the approved SRS will be treated as change request, with financial implications. • NIC should allow extension of project schedule and enhancement of project cost, in case requirements are changed at a later stage in the project.
SPECIFIC REQUIREMENTS
1 SOFTWARE PRODUCT FEATURES
The functional requirement of the proposed PQIS/AQIS is describe below in term of use case. A use case may be defined as a particular activity that an actor can perform. An actor is a user with a specific role. The following table gives a brief description of each use case field in the use case that follow.
3.1.1 ACTORS
1 SUPER ADMIN
A user who has been assigned the Super Admin type has access to the Super Admin Area for all activities installed on the website and to the tools used to configure these activities. A super admin in this case can be a nominated person by NIC. (Further information regarding the selection of a supper admin can also be decided on the basis of the input received during the field visit).
2 ADMIN
A sysop (an abbreviation of system operator) is an administrator of a multi-user computer system, such as an online service virtual community. It may also be used to refer to administrators of other Internet-based network services. In respect to this portal a system admin will be a person who will be authorized to perform the activities related with updating the site information, authenticating various users by administrating the registration and acknowledgement of registration.
3 APPROVER
A person who approves the application/roles /rights other actors AQIS User /SIP User/ General Users AQIS User /SIP User/ General Users those who will be using the portal for various agro met advisory related services. Nodal Officer for Grievance Redressal
4 EXPORTER
A person who will make his user id on AQIS web portal and applied for E-certification
5 IMPORTER
A person who will make his user id on AQIS web portal and applied for E-certification
2 COMMON USE CASES
This sub-section describes the use cases, which would be available to the actor belonging to any role. Refer to diagram-30 for a diagrammatic representation of the relationships between actor and among different use cases. The set of common use cases are:
• Log in • Logout • Change Password • Forget Password • Forget User ID • Attach Documents • Drop Documents • Auto Trigger • Manual Trigger
Each of these use cases is described below in more detail
|S.No. |Actor |Responsibility |
|1. |AQIS/SIP User |Login/Logout/Change password/Forget password/ Forget user id |
[pic]
Diagram 30: Common Use Cases
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.1.2.1 |Log In |This use case is used to Log In to AQIS|AQIS/SIP Users |
|UC 3.1.2.2 |Log Out |This use case would allow the actor to |AQIS/SIP Users |
| | |logout of AQIS Application to which he/| |
| | |she is already logged in. | |
|UC 3.1.2.3 |Change Password |This use case is used to change the |AQIS/SIP Users |
| | |existing password for AQIS User. | |
|UC 3.1.2.4 |Forget User ID |This use case is used for Forget User |AQIS/SIP Users |
| | |Id. | |
|UC 3.1.2.5 |Forget Password |This use case is used for Forget |AQIS/SIP Users |
| | |Password. | |
|UC 3.1.2.6 |Attach Documents |A person/agency that is uploading any |AQIS/SIP Users |
| | |document on the system. | |
|UC 3.1.2.7 |Drop Attachment |This use case allows the actor to |AQIS/SIP Users |
| | |delete or drop a file attachment that | |
| | |is associated with an item. | |
|UC 3.1.2.8 |Auto Trigger |This use case is for alert system |System Users of AQIS/SIP |
|UC 3.1.2.9 |Manual Trigger |This use case is for alert system |All System Users of AQIS/SIP |
| | |which should be functioning when manual| |
| | |commands are given | |
1 LOG IN
|UC 3.1.2.1 |Log In |
|Version: |00 |
|Context: |This use case is used to Log In to AQIS |
|Priority: |High |
|Frequency: |As and when actor want to login into AQIS application .AQIS (Internal & External) users enter his/her user-id|
| |and password to access the application. |
|Primary Actor: | AQIS/SIP Users |
|Preconditions: |User shall click on the link available on CAP. |
| |Select the application AQIS. |
|Basic Flow |1. System presents the actor an interface to enter user name and password: |
| |2. Actor shall enter user id and password. |
| |3. Actor instruct to Log In into system. |
| |4. On Successful login User shall reach at Home page of AQIS. |
|Alternative Flow: |Invalid User ID or Password: If actor enters wrong user id or password then system will display “Invalid |
| |Login”. Actor shall acknowledge the message. System will return back to Pre Condition. |
| |Actor is already login: If Actor chooses to invoke multiple instances. System will display a message “Already|
| |Log In”. |
| |Actor attempt to login with wrong User id and Password at least 3 times: System will display the message |
| |“Your Account is temporary blocked”. |
| |Actor Clicks on reset link: System will clear the user id and password. |
| |Actor can directly visit the application. Of PQIS/AQIS by typing URL on browser. |
|Post Condition: |Actor shall successfully login into system. |
| |Actor will access the information from AQIS as per defined role. |
|Special Requirements: |Form field shall be verified from both client and server end. |
|Unresolved Issues: | |
2 LOG OUT
|UC 3.1.2.2 |Log Out |
|Version: |00 |
|Context: |This use case would allow the actor to logout of AQIS Application to which he/ she is already logged in. |
|Priority: |High |
|Frequency: |As and when user Log In into AQIS |
|Primary Actor: |AQIS/SIP Users |
|Preconditions: |Actor is logged into AQIS application over the web. |
|Basic Flow |1. Actor shall click on the logout link. |
| |2. System will display a message “You have successfully logout.” |
| |3. System will return back to Home Page. |
|Alternative Flow: |1. Actor chooses to Close the browser window : |
| |a. System displays the message, “The currently logged in user was logged out. Thanks for using AQIS package. |
| |b. The System would close the AQIS package. |
| |2. If the actor is already logged in into AQIS package and System times out the actor: The system logs out |
| |the actor whenever the actor tries to click any option. The System returns back to the Home page. |
|Post Condition: |1. Actor shall successfully logout and brought to the Home Page. |
|Special Requirements: | |
|Unresolved Issues: | |
3 CHANGE PASSWORD
|UC 3.1.2.3 |Change Password |
|Version: |00 |
|Context: |This use case is used for existing password for AQIS |
|Priority: |High |
|Frequency: |As and when actor wants to change his/ her password. |
|Primary Actor: |AQIS/SIP Users |
|Preconditions: |Actor shall login in to AQIS using UC 3.1.2.1. |
|Basic Flow |1. Actor shall instruct the system to change password. |
| |2. Actor shall enter the old password. |
| |3. Actor shall enter the new password and again enter the confirmed new password. |
| |4. Actor shall instruct to change password. |
| |5. System will display a message “Your Password has been modified.” |
| |6. System will return back to Home Page. |
|Alternative Flow: |1. The actor attempts to save the changed password without specifying the Old Password: |
| |The System would respond with a message, “Please enter a password for the user”. |
| | |
| |2. The actor attempts to save the changed password without specifying the New Password: |
| |The System would respond with a message, “Please enter a confirmation password for the user”. |
| | |
| |3. The actor attempts to save the changed password without specifying the Confirm Password: |
| |The System would respond with a message, “Please enter a confirmation password for the user”. |
| | |
| |4. The length of the new password is less than 8 characters: |
| |The system would respond with the message, “The length of the password should be greater than 8 characters”. |
| |The length of the new password is greater than 12 characters. |
| |The System would respond with the message, “The length of the password cannot be greater than 12 characters”.|
| | |
| |5. The New Password is same as Old Password: |
| |The System would respond with the message, “The new password you have entered is same as old password. Please|
| |enter a different value for new password”. |
| |The New Password is same as Previous old Password |
| |The System would respond with a message, “New Password cannot be same as previous old password”. |
| | |
| |6. Confirm Password is different from New Password: |
| |The System would respond with the message, “Confirm Password should be same as New Password”. |
| |7. The New Password is not a Strong Password: |
| |The System would respond with a message, “Please correct the problem (s) with your new password. Strong |
| |Passwords must include at-least one number and special character.” |
|Post Condition: |1. Actor shall successfully logout and brought to the Home Page. |
|Special Requirements: | |
|Business Rules |1. The length of the new password should be greater than 8 and less than 12 characters. |
| |2. Old Password, New Password and Confirm Password fields are Mandatory. |
| |3. Confirm Password should be same as New Password. |
| |4. The New Password should include at-least one number and one special character. |
| |5. The New Password should not be same as the Old Password & Previous Old Password. |
|Unresolved Issues: | |
4 FORGET PASSWORD
|UC 3.1.2.4 |Forget Password |
|Version: |00 |
|Context: |This use case is used for Forget Password of AQIS. |
|Priority: |High |
|Frequency: |As and when actor forget his password of AQIS application. |
|Primary Actor: |AQCS/SIP Users |
|Preconditions: |User has clicked on the link available at AQIS for Forget Password. |
|Basic Flow |1. System presents the actor an interface to enter user name and email id: |
| |2. Actor shall enter user id and email id. |
| |3. System will send the new password at registered email id of user. |
| |Use Case Ends. |
|Alternative Flow: | 1. Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before search details. And if found then |
| |display the alert messages corresponding to related field. |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |Actor shall successfully get the password. |
|Special Requirements: |Form field shall be verified from both client and server end. |
|Unresolved Issues: | |
5 FORGET USER ID
|UC 3.1.2.5 |Forget User ID |
|Version: |00 |
|Context: |This use case is used for Forget User ID of AQIS. |
|Priority: |High |
|Frequency: |As and when actor forget his/her user id of AQIS application |
|Primary Actor: |AQIS/SIP Users |
|Preconditions: |User has clicked on the link available at AQIS for Forget User ID. |
|Basic Flow |1. System presents the actor an interface to enter email id: |
| |2. Actor shall enter email id. |
| |3. System will send the forget user id at email id of user. |
| |Use Case Ends. |
|Alternative Flow: | 1. Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before search details. And if found then |
| |display the alert messages corresponding to related field. |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |Actor shall successfully get the User id. |
|Special Requirements: |Form field shall be verified from both client and server end. |
|Unresolved Issues: | |
6 ATTACH DOCUMENTS
|UC 3.1.2.6 |Attach Documents |
|Version: |00 |
|Context: |This use case allows the actor to add a new attachment to an item. The attached file format and size limit would |
| |be governed by the system parameters set in the AQIS application from where the Add attachment has been invoked by|
| |the actor. |
| |The file to be attached may be located anywhere in a network of systems to which the actor’s system is connected. |
|Priority: |High |
|Frequency: |Medium |
|Actors: |A person/agency that is uploading any document on the system. |
|Trigger: |The actor chooses to add an attachment. |
|Pre-conditions: |Actor had logged into the AQIS application and has chosen to Add attachment in a specific application module. |
| | |
| |Actor can upload only PDF file in the AQIS application. |
|Post conditions: |The Attachments will take effect only if the user confirms the operation from which this use case was called. |
| |If the user confirms the uploaded attachments by submitting, then linkages of the uploaded files with the item |
| |will be created and saved in the respective AQIS application database. |
| |The uploaded attachments usage would then be governed by the business rules/Use cases of the respective AQIS |
| |applications. |
|Normal Flow: |Actor Actions |System Responses |
| | |System would display the Allowed File Type(s) which can be |
| |Actor enters the Title of the attachment. |uploaded by the actor, along with File Upload Limit, as |
| | |defined in the System Parameter of the respective AQIS |
| | |application. |
| | |The standard Operating System dialogue Window (which displays |
| |Actor navigates through the list of files and |the list of files currently available on the local machine) is|
| |folders and selects the file to be uploaded. |displayed. The window also provides option to select a file |
| | |available on another system which may be connected to the |
| |Actor chooses to upload. Actor chooses to upload |local system, invariably in a LAN |
| |the allowed file type and file size is within the |The file selected for attachment is scanned for any virus at |
| |upload Limit. |the time of upload and if the virus can’t be removed, the file|
| | |is not uploaded to the server. The actor is informed with the|
| |The actor may choose to drop the attachment, if |message: "The selected file could not be uploaded as it was |
| |required, using Drop Attachment use case. |virus infected and could not be cleaned. Pl. selects another |
| | |file". |
| | |The file is uploaded to the system from which Add Attachment |
| | |was invoked |
| | |Once the file is successfully uploaded, the system displays |
| | |the message “File was attached successfully.” |
|Alternative Flow |The actor may repeat steps 1 to 10 as many times as required |
|Exceptional Flow |Network connection breaks while uploading file to |The actor is brought back to the Pre condition. |
| |the PES system if the system is on a network. |The actor will have to begin the file upload operation all |
| | |over again from Step 1. |
| |If, the Confirm button is clicked without entering | |
| |the title |The system would respond with the message “ field |
| |In Step 5 of normal flow, if actor chooses: |cannot be left blank. Please enter the Title.” |
| |Selected File Type is not under the list defined in|On Save, System would prompt the error message as “File Type |
| |Allowed File Type(s), |not allowed for upload,” Actor can then choose to browse a |
| | |different file type. |
| | | |
| | |On Save, System would prompt the error message as “File |
| |Sum total of File sizes of all the file |Size(s) has exceeded the Upload Limit,” Actor can then choose |
| |attachments exceeds the Upload Limit, |to browse a different file(s). |
| | | |
| | |The system would respond with the message: "The selected file |
| |The file attachment selected for uploading is virus|could not be uploaded as it was virus infected and could not |
| |infected and the system is not able to clean it. |be cleaned. Pl. selects another file". |
|Includes: |None |
|other use case id | |
|UI: |Required |
|required/not required | |
|Priority: |High |
|Low/medium/high | |
|Frequency of Use: |Frequent |
|Continuous/ frequent/ | |
|medium/ less/ rare | |
|Business Rules: |There may be more than one file attached to an item. |
| |Title of the attachment is a Mandatory field and should not be left blank. |
| |Document name & its location should be save in the database. |
|Special Requirements: |In case the connection breaks while uploading the file, the upload process will have to begin all over again. |
| |However, if technology permits, it will be preferred, if the system resumes the file upload from the point where |
| |the connection was lost. |
|Assumptions: |None |
|Dependency: |Extends |
| |All Use Case(s) which involve forms/pages with Add Attachment Option. |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Notes and Issues: |None |
7 DROP ATTACHMENT
|UC 3.1.2.7 |Drop Attachment |
|Version: |00 |
|Context: |This use case allows the actor to delete or drop a file attachment that is associated with an item. |
|Priority: |High |
|Frequency: |Medium |
|Actors: |A person/agency that is dropping any document from the system. |
|Trigger: |The actor chooses to drop one or more attached files. |
|Pre-conditions: |Actor had logged into AQIS application and has chosen to Drop attachment in a specific application module, provided at |
| |least one file is attached with the item. |
|Post conditions: |The dropped files will be removed from the CAP application only if the user confirms the dropping of attachments by |
| |submitting the changes. |
| |All linkages of the item with the dropped attachments are removed from the application. |
| |Actor Actions |System Responses |
| | | |
| |Actor confirms the drop operation. |The System displays the message “Proceed with dropping the |
| | |selected files?” to confirm the drop operation. |
| | | |
| | |The selected files are marked as dropped. |
|Alternative Flow |None |
|Exceptional Flow |None |
|Includes: |None |
|other use case id| |
|UI: |Required |
|required/not | |
|required | |
|Priority: |High |
|Low/medium/high | |
|Frequency of Use:|Rare |
|Continuous/ | |
|frequent/ medium/| |
|less/ rare | |
|Business Rules: |The attachment will not get dropped, if it is the only element that constitutes the item. |
|Special |None |
|Requirements: | |
|Assumptions: |None |
|Dependency: |Extends |
| |All Use Case(s) which involve forms/pages with Drop Attachment Option |
| |Is Extended By |
| |None. |
| |Uses |
| |Login |
|Notes and Issues:|None |
8 AUTO TRIGGER
|UC 3.1.2.8 |Auto Trigger |
|Version: |00 |
|Context: |This use case is for alert system |
|Priority: |High |
|Frequency: |High |
|Actors: |System |
|Trigger: |Message from other use cases where auto trigger is being called. |
|Pre-conditions: |Message should comply with the alert system’s interface |
|Post conditions: |1. On success, Trigger mail / message sent to the respective stakeholders as received from the use case. |
| |2. On failure, retries until success or drops the message and table is updated |
|Basic Flow: |Actor Actions |System Responses |
| |Actor reads the message and the details shall |System will display the message with the details containing time |
| |contain; |stamp, target mail id, mobile number and sends the message to |
| |-time stamp |target |
| |-target mail id and mobile no | |
| |-message | |
| | | |
| |Stores the details in the table | |
| |Sends the message to target | |
|Includes: |None |
|other use case id | |
|UI: |Required |
|required/not required | |
|Priority: |High |
|Low/medium/high | |
|Frequency of Use: |Continuous |
|Continuous/ frequent/ medium/| |
|less/ rare | |
|Business Rules: |1. Should try for 24 hrs before dropping the message or as per system admin policy |
| |2. All acknowledgements could be auto-erased as per system admin policies |
|Special Requirements: |None |
|Assumptions: |None |
|Dependency: |Extends |
| |All the use cases where auto trigger is being called, |
| | |
| |Is Extended By |
| |None |
| | |
| |Uses |
| |Login |
|Notes and Issues: |None |
9 MANUAL TRIGGER
|UC 3.1.3.9 |Manual Trigger |
|Version: |00 |
|Context: |This use case is for alert system which should be functioning when manual commands are given |
|Priority: |High |
|Frequency: |Medium |
|Actors: |All system users |
|Trigger: |Actor clicks on the link available for alert |
|Pre-conditions: |Actor logs on to the system based on the credentials assigned. |
|Post conditions: |1. On success, Trigger mail / message sent to the respective stakeholders as received from the use case. |
| |2. On failure, retries until success or drops the message and table is updated |
|Basic Flow: |Actor Actions |System Responses |
| |Actor selects SMS / Mail |Captures the details and displays confirmation dialogue |
| |Actor types the message and the details shall contain;|Stores the details in the table |
| |- purpose |Sends the message to target |
| |-message | |
| |-target (other system users / registered business | |
| |users) | |
| |Clicks submit | |
|Includes: |None |
|other use case id | |
|UI: Required/not required |Required |
|Priority: |High |
|Low/medium/high | |
|Includes: |None |
|other use case id | |
|Business Rules: |1. Should try for 24 hrs before dropping the message or as per system admin policy |
| |2. All acknowledgements could be auto-erased as per system admin policies |
| |3. Based on role the system should allow / restrict sending SMS to other officers. |
| |4. Only registered dealers/farmers/manufacturers list will be available to send SMS |
|Special Requirements: |None |
|Assumptions: |None |
|Dependency: |Extends |
| |Use cases where any alert could be generated |
| | |
| |Is Extended By |
| |None |
| | |
| |Uses |
| |Login |
|Business Rules: |1. Should try for 24 hrs before dropping the message or as per system admin policy |
| |2. All acknowledgements could be auto-erased as per system admin policies |
| |3. Based on role the system should allow / restrict sending SMS to other officers. |
| |4. Only registered dealers/farmers/manufacturers list will be available to send SMS |
3 SYSTEM ADMINISTRATOR
• User Creation (Create /Edit) • Role Creation ( Add New/Edit/Delete) • User Management (Add New/Edit/Activate/Deactivate)
[pic] Diagram 31: System Administrator
| No. |Actor |Responsibility |
|1 |System Administrator |To Create Internal and External User |
|2 |System Administrator |To Create role for Internal and External User |
|3 |System Administrator |To Manage users |
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.1.3.1 |User Creation |This use case is for Creating, |System Administrator |
| | |editing users(Internal & | |
| | |External) from web by the system| |
| | |administrator | |
|UC 3.1.3.2 |Role Creation |This use case is for adding, |System Administrator |
| | |editing or deleting | |
| | |user(Internal & External) roles | |
| | |from master table | |
|UC 3.1.3.3 | User Management |This use case is for adding, |System Administrator |
| | |editing, activate/ deactivate | |
| | |user group from master table | |
2 USER CREATION
|UC 3.1.3.1 |User Creation |
|Version: |00 |
|Context: |This use case is for Creating or editing users from the web. |
|Priority: |High |
|Frequency: |High |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |System presents the Actor list of Users with the option of add, edit |
| |If Actor shall instruct to add the user. |
| |• System presents an interface with the following options: |
| |login |
| |Category( Internal or External User) |
| |Category ( Section officer, AC trade, JS trade, Director trade, quarantine officer ,Importer, Exporter) |
| |Name of the officer |
| |category (Importer/Exporter or both /NPPO/Stakeholders |
| |Importer/Exporter Name |
| | |
| |For external user |
| |IE Code |
| |NPPO country Name |
| |NPPO code |
| |Stakeholders Name |
| |Address |
| |Residential Address |
| |Contact No. |
| |Departmental Email ID |
| |Alternate Email ID |
| |Date of Birth |
| |Select Question |
| |Secret Answer |
| |Retype Password |
| |Type the code shown |
| |Register |
| |Clear |
| |Home |
| |Try from a new code |
| | |
| |If it is Internal user following detail would be displayed on the screen to actor : |
| |Login |
| |Name of employee |
| |Designation |
| |Address |
| |Residential Address |
| |Employee Code |
| |Contact No. |
| |Departmental Email id |
| |Alternate Email id |
| |DOB |
| |Register |
| |Clear |
| |Home |
| |Actor shall enter the user details and instruct to store into system. |
| |If Actor wants to edit the user. |
| |Actor selects the particular user to be edited and presses edit. |
| |System shows the user contents with editable access. |
| |Edits the content (Add- to enter new details /Modify- edit the current details). |
| |Actor shall instruct to update the table. |
| |The Use Case Ends. |
|Alternative Flow: |1. Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before save the forms details. And if found then|
| |display the alert messages corresponding to related field. |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
| |3. Actor will verify the details of the users & enable their user id |
| |Password: - Auto generated password will be delivered at their Email id & information on SMS. |
| |One PDF file will be generated for record purpose. |
|Post Condition: |Database is updated and mail trigger to respective person with consolidated information details. |
| |The system shall generate application reference number and thrown a message to the applicant. |
| |An SMS indicating the registration is complete will be sent to the recipient mobile. |
| |Table shall be updated. |
|Special Requirements: |I/E code issued by DGFT to importer/exporter would be displayed in our system for verification through web |
| |services. In case of internal users LDAP will be used |
|Unresolved Issues: | |
3 ROLE CREATION
|UC 3.1.3.2 |Role Creation |
|Version: |00 |
|Context: |This use case is for adding, editing or deleting user roles from master table |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |System presents the Actor list of Roles (if already exist) or blank page with the option of add, edit and delete|
| |If Actor shall instruct to add the role. |
| |• System presents an interface with the following options: |
| |Role ID: Actor shall define the unique role id. |
| |Role Name: Actor shall define the name of the role. |
| |Role Description: Actor shall describe the user’s role. |
| |Update: If require actor shall update any option |
| |Actor shall enter the role details and instruct to store into system. |
| |If Actor wants to edit the Role. |
| |Actor selects the particular role to be edited and instructs to edit. |
| |System shows the role contents with editable access. |
| |Edits the content (Add- to enter new details /Modify- edit the current details). |
| |Actor shall instruct to update the table. |
| |If Actor wants to delete the role. |
| |Checks the particular/multiple role to be deleted and instruct to delete. |
| |The Use Case Ends. |
|Alternative Flow: |1. Invalid data or left blank any required field. |
| | |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found then|
| |display the alert messages corresponding to related field. |
| | |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |Database is updated and mail trigger to respective person with consolidated information details. |
| |The system shall generate application reference no and thrown a message to the applicant. |
| |An SMS indicating the registration is complete will be sent to the recipient mobile. |
| |Table shall be updated. |
|Special Requirements: | |
|Unresolved Issues: | |
4 USER MANAGEMENT
|UC 3.1.3.3 |User Management |
|Version: |00 |
|Context: |This use case is for adding, editing, activate/ deactivate or freeze the user and user roles from master table |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |System presents the Actor list of users (if already exist) or blank page with the option of add, edit and delete|
| |If Actor shall instruct to add the role. |
| |• System presents an interface with the following options: |
| |User ID: Actor shall select the User ID fro existing list of User ID. |
| |Role ID: Actor shall define the name of the role. |
| |Level’s of User’s Role: This field comes from Role Creation table. |
| |State/ District Name: Actor shall enter the state/ district where the User has posted in case only range or |
| |district level user. |
| |Actor shall enter the user management details and instruct to store into system. |
| |If Actor wants to edit the Role. |
| |Actor selects the particular user to be edited. |
| |System shows the role contents with editable access. |
| |Edits the content (Add- to enter new details /Modify- edit the current details). |
| |Actor shall instruct to update the table. |
| |If Actor wants to activate/ deactivate the user. |
| |Checks the particular/multiple role to be activated / deactivated and instruct to activate/ deactivate. |
| |If Actor wants to Freeze the role. |
| |Checks the particular user to be frozen and instruct to freeze the user. |
| |The Use Case Ends. |
|Alternative Flow: |1. Invalid data or left blank any required field. |
| | |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found then|
| |display the alert messages corresponding to related field. |
| | |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |1. Tables should be updated. |
|Special Requirements: | |
|Unresolved Issues: | |
2 ANIMAL QUARANTINE
1 SIP & AQIS ACTIVITIES USE CASES
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.2.1.1 |Enter Data For SIP |The use case is to enter the data for applying SIP|Importer |
|UC 3.2.1.2 |Application Scrutiny & Verification For SIP|This use case describes the process of scrutiny of|Section Officer |
| | |documents & approval. | |
|UC 3.2.1.3 |Application Forward to AC Trade |This use case describes the process of agenda |AC Trade |
| | |preparation & forwarding the application to | |
| | |respective division. | |
|UC 3.2.1.4 |Receiving Application For Comments by |This use case describes the process of receiving |AC Dairy division , AC LH |
| |Divisional AC/FRO |application by divisional AC/FRO &preparing the |division , FRO FY |
| | |comment on each application. |division |
|UC 3.2.1.5 |Application Forward to TO/FDC/DC along with|This use case explains the process of reviewing |TO/FDC/DC |
| |Comments |the comments & put the remarks if any. | |
|UC 3.2.1.6 |Receiving Application along with Comments |This use case explains the comment received by |Divisional Heads |
| |by Divisional Heads |divisional heads. | |
|UC 3.2.1.7 |Application Forward to AC/FRO |This use case describes the process of forwarding |AC/FRO |
| | |the application to AC/FRO if correction required. | |
|UC 3.2.1.8 |Application Forward to TO/FDC/DC along with|This use case describes the process of reviewing |TO/FDC/DC |
| |Comments |the application again after making the necessary | |
| | |correction by AC/FRO | |
|UC 3.2.1.9 |Receiving Application along with Comments |This use case explains the process of inputting |Divisional Heads |
| |by Divisional Heads |the remarks if any to the corrective application | |
| | |forwarded by TO/FDC/DC | |
|UC 3.2.1.10 |Application Approval For SIP |This use case describes the process of final |JS Trade/Director Trade |
| | |approval of application by respective approval |for approval |
| | |head. |SO/AC for updating status|
| | | |after meeting |
|UC 3.2.1.11 |Issuance of SIP |This use case describes the final issuance of SIP |Section officer/AC trade |
| | |by AC Trade. | |
|UC 3.2.1.12 |Common Process Flow for AQIS/PQIS Login. |This use case describes the login process to |AQIS/PQIS Users |
| | |AQIS/PQIS application. | |
|UC 3.2.1.13 |Entry Certification Data for AQC. |This use case is to enter the data for applying |Importer/ Exporter |
| | |e-certification of AQC for Livestock/ Pet Animal /| |
| | |Livestock Product. | |
|UC 3.2.1.14 |Verification & Approval/ Rejection of AQC |This use case is to describe the process of |Quarantine Officer |
| |Application |scrutiny/verification of documents/ application & | |
| | |approval or rejection for AQC application. | |
|UC 3.2.1.15 |Enter Provisional AQC Certification Data |This use case is to enter the data for applying of|Importer |
| | |Provisional (AQC) for Livestock/ Pet Animal / | |
| | |Livestock Product. | |
|UC 3.2.1.16 |Verification & Approval/ Rejection/ |This use case is to describe the process of |Quarantine Officer |
| |Issuance of Provisional AQC |scrutiny/verification of documents/ application & | |
| | |approval, rejection or issuance of Provisional | |
| | |AQC. | |
|UC 3.2.1.17 |Make Payment for Lab |This use case is used to Make Payment for Lab |Importer/Exporter/Quaranti|
| |testing/Quarantine/Vaccination |testing/Quarantine/Vaccination |ne officer |
|UC 3.2.1.18 |Payment Gateway |A payment gateway facilitates the transfer of |Importer/Exporter |
| | |information between a payment portal (such as a | |
| | |website and mobile phone) and the Front End | |
| | |Processor or acquiring bank. | |
|UC 3.2.1.19 |Sample Collection & Sending to Lab for |This use case is to describe the process of |Quarantine Officer |
| |Testing |collecting sample for testing and sending to lab | |
| | |for testing | |
|UC 3.2.1.20 |Receiving Sample and Sending Report to |This use case is to describe the process of |Testing Lab Officer |
| |Quarantine Officer |receiving samples at lab and sending report to | |
| | |quarantine officer | |
|UC 3.2.1.21 |Sample Test Result |This use case is to specify the result of tested |Testing Lab Officer |
| | |samples. | |
|UC 3.2.1.22 |Receiving and Verification of Test Report |This use case is to describe the process of |Quarantine Officer |
| |From Lab |receiving test report from lab. | |
|UC 3.2.1.23 |NPPO Access to view PSC/AQC. |This use case explains the process of viewing the |NPPO |
| | |PSC/AQS number by NPPO for verification. | |
|UC 3.2.1.24 |Updating Rejection of PSC/AQC by NPPO |This use case describes the process that how NPPO |NPPO |
| | |of other countries update the data of rejected | |
| | |PSC/AQC. | |
|UC 3.2.1.25 |Grievance Management |This use case explains the flow to submit the |Importer/Exporter |
| | |complaint. | |
|UC 3.2.1.26 |View Grievance Redressal |This use case would describe the |Importer/Exporter |
| | |Process to view the grievances. | |
|UC 3.2.1.27 |Grievance Redressal System |This use case would describe the |Nodal Officer |
| | |way to address the grievances | |
|UC 3.2.1.28 |MIS/Report |This use case provides all the different reports |HOD |
| | |required by NIC. | |
|UC 3.2.1.29 |Master data Management |This use case is for adding, editing or deleting |System administrator |
| | |contents from master table | |
1 ENTER DATA FOR SIP
|UC 3.2.1.1 |Enter data for SIP |
|Version: |00 |
|Context: |The use case is to enter the data for applying SIP. |
|Priority: |High |
|Frequency: |As and when user wants to import the livestock Product. |
|Primary Actor: |Importer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |In case of Livestock actor shall apply for import License from DGFT office. This is out of scope of this SRS.|
| |Actor shall have all the details related to import of LSP. |
| |Actor shall apply for one product (HS Code) in one application. |
|Basic Flow |1. Actor instructs the system for issuance of Sanitary Import Permit. |
| |2. System presents the actor an interface to enter details related to Form A, Form B |
| |SIP of LSP for trading & marketing (Form B): - Name and address of importers, Exact des. Of livestock |
| |Products with Indian trade classification, ITC (HS) code, FSSAI certificate number, Detail of Livestock from |
| |whom it is produced, number of packages, Total weight/volume Name & address. Of producer, Name & address. Of |
| |consignor, Country & locality in which Livestock Product produces, Country from which importer into India, |
| |Foreign port of shipment, Name of airport/seaport/land custom station(entry point),Declaration ,Others |
| |SIP of LSP for personal use(Form A):-Name & exact description of live-stock-product to be imported, |
| |Description of the consignment and quantity, Name & address of consignor, Name & address of importer, ITC(HS)|
| |code, Country & locality in which produced, Country from which imported into India, Foreign port of shipment |
| |, Approximate date of arrival of the consignment in India, Name of point of entry in India ,Declaration, |
| |others |
| |Mandatory field :- Name & address of importer, Name & address of consigner, Name & address of the producer, |
| |Country & locality in which Livestock Product produces, foreign port of shipment, Name of airport/sea port |
| |(entry point), FSSAI certificate number. |
| |3. System captures the input and updates the database. |
| |4. One reference number will be generated by the system & displayed on the screen. |
| |5. Through this reference number all the transaction will be processed further. |
|Alternative Flow: |1. Invalid data or left blank any required field. |
| | |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found |
| |then display the alert messages corresponding to related field. |
| | |
| |2. Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |1. Data shall be saved in the database. |
| |2. Actor shall successfully logout and brought to the Home Page. |
| | |
|Special Requirements: | |
|Unresolved Issues: | |
2 APPLICATION SCRUTINY & VERIFICATION FOR SIP
|UC 3.2.1.2 |Application Scrutiny & Verification for SIP |
|Version: |00 |
|Context: |This use case describes the process of scrutiny of documents & approval. |
|Priority: |High |
|Frequency: |As and when user wants to import the livestock Product. |
|Primary Actor: | Section officer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records or application using the use case “ Enter the data for SIP” |
| |Actor will select one record at a time to verify the details. |
| |Actor will choose one of the following options. |
| |If approved, click on APPROVRD button. |
| |If rejected, click on Rejected button. |
| | |
| |After APPROVED in above mention cases application will forwarded to AC trade. |
| | |
| |If rejected: - Actor will entered the reason of rejection & press the submit button. Automated information |
| |along with the reason sent to importer on their registered e-mail id or on register mobile no through SMS |
| |gateway. |
| | |
| |If deficiency: - Actor will forward the application to importer for deficiency removal & resubmission. |
| |Application forward to AC trade. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Special Requirements: | |
|Unresolved Issues: | |
3 APPLICATION RECEIVED BY AC Trade
|UC 3.2.1.3 |Application Received By AC Trade |
|Version: |00 |
|Context: |This use case describes the process of agenda preparation & forwarding the application to respective |
| |division. |
|Priority: |High |
|Frequency: |As and when user wants to import the livestock Product |
|Primary Actor: | AC Trade |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records or application using the use case “ Application Scrutiny & Verification for |
| |SIP” |
| |System will prompt the actor to specify the following details: |
| |Title of agenda |
| |Agenda number |
| |Name of the farm |
| |Remarks |
| |Unit name: Dairy division , LH division ,FY division |
| |Product name |
| |Comment of the concerned units |
| |Recommendation of the committee |
| | |
| |After specify all the details, the actor will click Save & Submit |
| | |
| |2. Actor may add multiple agendas choosing ADD more option available on the screen. |
| | |
| | |
| |After preparing the Agenda for Meeting or Onfile case, Actor will forward the application as per the |
| |condition to concerned AC/FRO. if application is for the below items: |
| |Fish Feed |
| |Fish Food |
| |Whey Protein |
| |Cheese |
| |Hilsa |
| |Bovine Serum |
| | |
| |Then it will be processed as fast track. Otherwise actor will select the Meeting or On file case. |
| |Actor will click on FORWARD button. |
| |The forwarded application will go to the respective divisional AC/FRO inbox. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Special Requirements: | |
|Business Rule: |The application of Dairy division will forwarded to dairy division & LH division. |
| |LH division application will forward to LH division. |
| |FY division application will forward to FY division. |
|Unresolved Issues: | |
3.2.1.4 RECEIVING APPLICATION FOR COMMENTS BY DIVISIONAL AC/ FRO
|UC 3.2.1.4 |Receiving Application for Comments by Divisional AC/FRO |
|Version: |00 |
|Context: |This use case describes the process of receiving application by divisional AC/FRO &preparing the comment on |
| |each application. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: | AC Dairy division , AC LH division , FRO FY division |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by AC Trade to AC Dairy division, AC LH division, FRO FY division of |
| |application using the use case “Application Received by AC /FRO”. |
| |Actor will select one application. |
| |Actor will prepare the comments for respective division. |
| |Actor will forward the application along with comments to TO/FDC/DC respectively. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
3.2.1.5 APPLICATION RECEIVED BY TO/FDC/DC ALONG WITH COMMENTS
|UC 3.2.1.5 | Application Received by TO/FDC/DC Along with Comments |
|Version: |00 |
|Context: |This use case explains the process of reviewing the comments & put the remarks if any. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: | TO/FDC/DC |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by AC Dairy division to TO Dairy division, AC LH division to DC LH |
| |division, FRO FY division to FDC Fishery division of application using the use case “Receiving Application |
| |for Comments by Divisional AC/FRO”. |
| |Actor will select one application. |
| |Actor will review the put the remarks/Input if any. |
| |Actor will forward the application along with correction in the comments if any to divisional head |
| |respectively. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: |It is suggested that reference of appropriate formats as applicable may be included as one of the condition |
| |in the SIP. |
|Business Rule: | |
|Unresolved Issues: | |
| | |
3.2.1.6 RECEIVING APPLICATION ALONG WITH COMMENTS BY DIVISIONAL HEADS
|UC 3.2.1.6 |Receive Application along with comments by Divisional Heads |
|Version: |00 |
|Context: |This use case explains the comment received by divisional heads. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: |Divisional Heads |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by TO Dairy division, DC LH division, FDC Fishery division to Divisional|
| |heads of respective division of application using the use case “Application Received by TO/FDC/DC Along With |
| |Comments”. |
| |Actor will select one application. |
| |Actor will review the comments & put the remarks/Input if any. |
| |Actor will forward the application to respective divisional AC/FRO if correction required. |
| |If correction not required application will forward in (Meeting case) to JS Trade, in (On File case) & (Fast |
| |Track) to Director Trade. |
| | |
| | |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
3.2.1.7 APPLICATION RECEIVED BY AC /FRO
|UC 3.2.1.7 |Application Received by AC /FRO |
|Version: |00 |
|Context: |This use case describes the process of forwarding the application to AC/FRO if correction required. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: |AC/FRO |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by Divisional heads of respective division to AC/FRO if correction |
| |required in application of using the use case “Receiving Application Along With Comments by Divisional heads”.|
| |Actor will select one application. |
| |Actor will do the necessary correction in the comments. |
| |Actor will again forward the application to TO Dairy division, FDC Fishery division, DC LH division. For |
| |review. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
3.2.1.8 APPLICATION RECEIVED BY TO/FDC/DC ALONG WITH COMMENTS
|UC 3.2.1.8 | Application Received by TO/FDC/DC Along with Comments |
|Version: |00 |
|Context: |This use case describes the process of reviewing the application again after making the necessary correction by |
| |AC Trade. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: | TO/FDC/DC |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by AC/FRO to TO Dairy division, DC LH division, FDC Fishery division of |
| |application using the use case “Application Received by AC /FRO”. |
| |Actor will select one application. |
| |Actor will review the updated application and put the remarks/input if any. |
| |Actor will forward the application along with correction in the comments if any to divisional head respectively. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: |The application of Dairy division will forwarded to dairy division & LH division. |
| |LH division application will forward to LH division. |
| |FY division application will forward to FY division. |
|Unresolved Issues: | |
| | |
3.2.1.9 RECEIVING APPLICATION ALONG WITH COMMENTS BY DIVISIONAL HEADS
|UC 3.2.1.9 |Receiving Application along with Comments by Divisional Heads |
|Version: |00 |
|Context: |This use case explains the process of inputting the remarks if any to the corrective application forwarded by |
| |TO/FDC/DC. |
|Priority: |High |
|Frequency: |As and when user receive the application for comments. |
|Primary Actor: |Divisional Heads |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records sent by TO Dairy division, DC LH division, FDC Fishery division to Divisional |
| |heads of respective division of application using the use case” Application Received by TO/FDC/DC Along With |
| |Comments”. |
| |Actor will select one application. |
| |Actor will review the correction made in the comments & put the remarks/input if any. |
| |Actor will forward the application in (Meeting case) to JS Trade & in (On File case) to Director Trade. |
| | |
| | |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |1. The submitted detail will forward to the AC trade. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
3.2.1.10 APPLICATION APPROVAL FOR SIP
|UC 3.2.1.10 |Application Approval For SIP |
|Version: |00 |
|Context: |This use case describes the process of final approval of application by respective approval head. |
|Priority: |High |
|Frequency: |As and when user call the meeting for discussion on comments. |
|Primary Actor: | JS Trade/Director Trade for approval |
| |SO/AC for updating status after meeting |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |Report will be generated comprising comments received from various divisional head against the sent applications.|
| |This report can be utilized by AC trade for preparing agenda with the JS trade & other divisional heads. |
|Basic Flow |All the applications against which comments have been given by different divisional heads will be displayed here.|
| | |
| |If it is meeting case actor would be JS trade and if it is on file case actor would be director trade/AC Trade. |
| | |
| |In fast track case actor would directly come to this window after UC 3.1.2.1. |
| | |
| |Actor would update the status of application after meeting as well as select the post import condition as |
| |applicable. |
| | |
| |The actor could select one application each time. |
| | |
| |Once the actor selects the application, depending upon the discussions held in the meeting actor may accept or |
| |reject the application by choosing the respective link available on the screen. |
| |An SMS alert to be sent to the respective importer about the acceptance or rejection of the application. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |The PDF will be available for download & print. |
| |The accepted or rejected application will be available to the AC trade for issuing SIP or discard the |
| |application. |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
11 ISSUANCE OF SIP
|UC 3.2.1.11 |Issuance of SIP |
|Version: |00 |
|Context: |This use case describes the final issuance of SIP by AC Trade. |
|Priority: |High |
|Frequency: |As and when user call the meeting for discussion on comments. |
|Primary Actor: |Section officer/AC trade |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |The accepted or rejected applications sent by Section officer will be displayed to the actor will the following |
| |details. |
| |Application reference number |
| |Application date |
| |Application status. |
| | |
| |The may select one or multiple applications to generate the SIP. |
| |Only the applications with “accepted” status would be enabled for selection |
| |The actor will click on the generate SIP link available on the screen to generate Sip’s in pre PDF defined |
| |format. |
| |Actor will take the signature from the A/C trade on approved Sip’s. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: |The PDF will be available for download & print. |
| |The generated Sip’s will be sent to the importer on their registered email id. |
| |The status of application will be changed in the database as rejected or accepted and importer/exporter may |
| |search the status of applications on the home page of AQIS applications using the application reference number |
|Special Requirements: |Application number should be printed on the SIP certificate. |
|Business Rule: | |
|Unresolved Issues: | |
12 COMMON PROCESS FOLW FOR AQIS/PQIS LOGIN
|UC 3.2.1.12 |Common Process Flow for AQIS/PQIS Login |
|Version: |00 |
|Context: |This use case describes the login process to AQIS/PQIS application. |
|Priority: |High |
|Frequency: |As and when user call the meeting for discussion on comments. |
|Primary Actor: |AQIS/PQIS Users |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow |Actor will type CAP URL on browser to come on the home page of CAP. |
| | |
| |Actor will select / click on link AQIS/PQIS available. |
| | |
| |Actor will fill and submit the application of user id & password. If internal user will directly reached to the |
| |AQIS/PQIS Home page. |
| | |
| |If External user then Verification of I/E code will be done by the system administrator of respective |
| |application. |
| | |
| |Login id will be enabled by system administrator after verification of I/E Code. |
| | |
| |Now actor will login AQIS/PQIS respectively. |
|Alternative Flow: |1. Cancel If Actor cancels the form then system will reach at home page. |
|Post condition: | |
|Special Requirements: | |
|Business Rule: | |
|Unresolved Issues: | |
13 ENTER CERTIFICATION DATA FOR AQC
|UC 3.2.1.13 |Enter Certification Data for AQC |
|Version: |00 |
|Context: |This use case is used to enter the information for AQC certification |
|Priority: |High |
|Frequency: |As and when user wants to export or import the Livestock / Pet Animal / Livestock Product. |
|Primary Actor: |Importer/Exporter |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Actor shall have all the details related to Import/Export of Livestock / Pet Animal /LSP. |
|Basic Flow |1. Actor instructs the system for e-certification of Import/Export |
| |2.Actor will select the role:- Importer / Exporter |
| |3. Actor will select the product: - Livestock/Pet animal/Livestock Product. |
| |4. System presents the actor an interface to enter details related to e- certification in Four conditions. |
| |If importer is applying for Livestock / Pet animal. |
| |If importer is applying for livestock product. |
| |If exporter is applying for Livestock / Pet animal. |
| |If exporter is applying for Livestock product. |
| | |
| |5. If importer is applying for Livestock / pet animal. The system would prompt the actor to specify following |
| |details. |
| | |
| |Livestock/Pet animal:-Product, Applied To, Exporter name, Importer name, Exporter address, Importer address, SIP|
| |number/DGFT license number, Purpose of export/import, Date/mode, Health certificate, DOB, Colour, Country of |
| |origin, PP number /Microchip number, number of livestock with number of packages, Rabies/vaccination, |
| |vaccination date, validity, Batch number, Country & place of embarkation, Country & place of disembarkation, |
| |Documents:- Health cert., Ticket if any, SIP/DGFT license, Imp./Exp. Declaration, Lab letter/report, |
| |Invoice/packaging list, BOE, Charges if any. |
| | |
| |6. If importer is applying for Livestock product. The system would prompt the actor to specify following |
| |details. |
| | |
| |LSP:-Product, Applied To, Exporter name, Importer name, Exporter address, Importer address, I/E License. number |
| |/DGFT license number, SIP, Name of LSP, Quantity/weight/volume/kg/L.T., Number of packages, Custom seal number |
| |/ date BOE, Date of import/export, Shipping/airways bill number /date, Invoice number & date, Country of origin,|
| |Post of loading, Country of Import/export, Post of unloading, Container number, Date/means of conveyance, Plant |
| |registration number, Purpose of import/export, Health certificate number & date Lab report number & date |
| |Document attach:- Import/Export License, SIP ,Health certificate, Fumigation cert./Test report, Invoice number, |
| |Airways bill number, Imp/Exp declaration, others, charges if any |
| | |
| |7. If exporter is applying for Livestock / pet animal. The system would prompt the actor to specify following |
| |details. |
| | |
| |Livestock/Pet animal:-Product, Applied To, Exporter name, Importer name, Exporter address, Importer address, SIP|
| |number/DGFT license number, Purpose of exp./imp., Date/mode, Health certificate, DOB, Colour, Country of origin,|
| |PP number /Microchip number, number of livestock with number of packages, Rabies/vaccination, vaccination date, |
| |validity, Batch number, Country & place of embarkation, Country & place of disembarkation, |
| |Documents:- Health cert., Ticket if any, SIP/DGFT license, Imp./Exp. Declaration, Lab letter/report, |
| |Invoice/packaging list, BOE, Charges if any. |
| | |
| |8. If exporter is applying for Livestock product. The system would prompt the actor to specify following |
| |details. |
| | |
| |LSP:-Product, Applied To, Exporter name, Importer name, Exporter address, Importer address, I/E License. number |
| |/DGFT license number, SIP, Name of LSP, Quantity/weight/volume/kg/L.T., Number of packages, Custom seal number |
| |/ date BOE, Date of import/export, Shipping/airways bill number /date, Invoice number & date, Country of origin,|
| |Post of loading, Country of Import/export, Post of unloading, Container number, Date/means of conveyance, Plant |
| |registration number, Purpose of import/export, Health certificate number & date Lab report number & date |
| |Document attach:- Import/Export License, SIP ,Health certificate, Fumigation cert./Test report, Invoice number, |
| |Airways bill number, Imp/Exp declaration, others, charges if any |
| | |
| |Mandatory field :- Product, Applied To, Importer/Exporter Name, Importer/Exporter Address, Country to |
| |Import/export, county of origin, Means of conveyance, number of packages/containers, Port of unloading/loading, |
| |Invoice number, Inspection date, Place of inspection, Purpose of export / import. |
| |3. System captures the input and updates the database. |
|Alternative Flow: |Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found then|
| |display the alert messages corresponding to related field. |
| |Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |1. Data shall be saved in the database & application number will be generated. |
| |2. Actor shall successfully logout and brought to the Home Page. |
|Business Rule: | 1. If actor will select Pet animal in case of export/ import then quantity cannot be equal to or more than|
| |two. |
|Special Requirements: | 2. If actor will select Pet animal in case of export/ import then quantity cannot be equal to or more than|
| |two. |
|Unresolved Issues: | |
14 VERIFICATION & APPROVAL/ REJECTION OF AQC APPLICATION
|UC 3.2.1.14 |Verification & Approval / Rejection of AQC Application |
|Version: |00 |
|Context: |This use case is to describe the process of scrutiny/verification of documents/ application & approval or |
| |rejection for AQC. |
|Priority: |High |
|Frequency: |As and when user wants to export or import the Livestock / Pet Animal / Livestock Product. |
|Primary Actor: |Quarantine Officer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |System will display the records or application using the use case “Enter Certification Data for AQC”. |
| |Actor will select one record at a time to verify. |
| |Actor will choose one of the following option |
| |If approved, click on APPROVRD button. |
| | |
| |If the application is for import then NOC issued and |
| |If the application is for export then AQC health certificate will be issued |
| |If rejected: - In case of import or export the application will be rejected and reasons of rejection/ |
| |testing/vaccination if required, will be entered. Automated information along with the reason sent to |
| |importer/exporter to their registered email-id or on registered mobile number through SMS gateway |
| | |
| |In case of export the system will prompt to forward it either for lab testing or vaccination. |
| | |
| |If Deficiency: - Actor will forward the application to importer/exporter for deficiency removal and |
| |resubmission. |
| |4. In this case the Actor will specify remarks if any |
| |5. If Actor has approved the application then system will generate the NOC in PDF format and an e-mail will be |
| |sent to his/her registered e-mail id and an SMS to his/her registered mobile number. |
| |6. If Actor approves the application the system will generate the AQC health certificate in PDF format to |
| |exporter. |
|Alternative Flow: |Cancel If Actor cancels the form then system will reach at home page. |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Data shall be saved in the database. |
| |2. Actor shall successfully logout and brought to the Home Page. |
| |3. The PDF will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
15 ENTER PROVISIONAL AQC CERTIFICATION DATA
|UC 3.2.1.15 |Enter Provisional Certification Data |
|Version: |00 |
|Context: |This use case is to enter the data for applying of Provisional Quarantine Clearance for Livestock/ Pet Animal / |
| |Livestock Product. |
|Priority: |High |
|Frequency: |As and when user wants to get the provisional quarantine clearance of Livestock / Pet Animal / Livestock Product.|
|Primary Actor: |Importer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Actor shall have NOC from the AQIS |
|Basic Flow |Actor instructs the system for provision quarantine clearance |
| |Certification. |
| |Actor will select the product: - Livestock/Pet animal/Livestock Product. |
| |System presents the actor an interface to enter details related to provision quarantine clearance certification. |
| |Livestock: file number, date, detail of consignment- country of origin, flight number, date of import, bill of |
| |entry number, address of importer, name of importer, detail of livestock-serial number, name, tag number, breed, |
| |sex, age, colour |
| |Livestock Product: file number, date, detail of consignment- country of origin, flight number, date of import, |
| |bill of entry number, address of importer, name of importer, detail of livestock-serial number, name, tag number,|
| |breed, sex, age, colour, detail of livestock product- serial number, product name, ITC(HS) code, number of |
| |packages/ total weight in KG/ volume |
| |Actor will click on the save and submit button |
| |System captures the input and update the database |
|Alternative Flow: |Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before save the form’s detail. And if found then |
| |display the alert messages corresponding to related field. |
| |Cancel If Actor cancels the form then system will reach at home page. |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Data shall be saved in the database. |
| |2. Actor shall successfully logout and brought to the Home Page. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
16 VERIFICATION & APPROVAL/ REJECTION /ISSUANCE OF PROVISIONAL AQC
|UC 3.2.1.16 |Verification & Approval/ Rejection /Issuance of Provisional AQC |
|Version: |00 |
|Context: |This use case is to describe the process of scrutiny/verification of documents/ application & approval, |
| |rejection or issuance for Provisional AQC. |
|Priority: |High |
|Frequency: |As and when user wants to get Provisional AQC for livestock/ Pet Animal / Livestock Product. |
|Primary Actor: |Quarantine Officer |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Sample taken for lab testing |
|Basic Flow |System will display the records or application which have been entered using the use case “ Enter Provisional |
| |Certification Data for AQC” |
| |Actor will select one record at a time to verify. |
| |System will prompt the actor first to select the number of sample and then the test requirement or vaccination |
| |requirement from the list displaying test name & the vaccination names specified in the master table. |
| |If the actor has selected the test requirement the system will prompt the actor to select the testing lab name |
| |from the list displaying the labs name specified in the master table. |
| |After selecting the test requirement or vaccination requirement as well as the lab name system will |
| |automatically update the fee column (as specified in the master table) depending upon the number of samples. |
| |Actor will choose one of the following option |
| |If approved & pet animal or livestock then click on APPROVRD button, Provisional quarantine certificate issued |
| |in PDF format. |
| |If it is non pet livestock, actor will select the quarantine observation for 30 days automated information sent |
| |to importer as well as provisional quarantine certificate will be generated by the system in PDF format and sent|
| |to importer e-mail and SMS on his/her registered e-mail and mobile number. |
| |If Rejected, click on rejected button application will be rejected and deportation order will be issued, |
| |information sent to importer on registered email –id or register mobile number. |
|Alternative Flow: |Cancel If Actor cancels the form then system will reach at home page. |
| |Form close if actor clicks on the close button. |
|Post Condition: |Data shall be saved in the database. |
| |Actor shall successfully logout and brought to the Home Page. |
| |After issuance of provisional certificate to livestock, it will be kept under observation for 30 days at |
| |quarantine station and importer has to pay fee for per LS per day for 30 days. |
| |The PDF will be available for download & print |
|Business Rule: | |
|Special Requirements: |BOE issued by custom to importer would be captured and displayed. |
|Unresolved Issues: | |
| | |
17 MAKE PAYMENT FOR LAB TESTING/QUARANTINE/ VACCINATION
|UC 3.2.1.17 |Make payment for Lab Testing/Quarantine/ Vaccination |
|Version: |00 |
|Context: |This use case is to describe the process of making the payment for various Testing/Quarantine/ Vaccination. |
|Priority: |High |
|Frequency: |As and when user wants to make the payment. |
|Primary Actor: |Importer/Exporter/Quarantine officer |
|Preconditions: |1. Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |2. Provisional quarantine certificate should be issued to the importer/exporter. |
| |3. Actor should have received the information from quarantine office regarding making the payment either in case|
| |of lab testing or for quarantine observation. |
| |5. The person/agency must have Debit/Credit Card/ net banking for online transactions. |
|Basic Flow |1.System will prompt the actor to select one of the option for which he/she want to make the payment: |
| |Pay for Lab testing |
| |Pay for vaccination |
| |Pay for quarantine observation |
| |2. Depending upon the above selected option system will the display the list of record received from AQCS |
| |department using the “Verification & approval / rejection / issuance of provisional AQC” use case. |
| |3.After that actor will select the payment mode: |
| |Online payment:- for online payment, the actor could choose one of following options: |
| | |
| |Internet Banking |
| |Debit Card |
| |Credit Card |
| |The system will navigate actor to the use case payment gateway to make payment online. |
|Alternative Flow: |If actor select the Mode of Payment as Cheque the system will prompt to the specify following details: |
| |Cheque No. |
| |Cheque date |
| |Cheque deposit In: Bank name |
| |If actor select bank, the system will prompt the actor to select the bank name from the drop down enlisting all |
| |the |
| |Central/State/Cooperative/Private bank specified in the database. Select name of the bank in which the Cheque |
| |was deposited. |
| | |
| |If actor selects mode of Payment as DD, the system will prompt to specify following details: |
| |DD issuing bank name |
| |actor select bank, the system will prompt the actor to select the bank name from the drop down enlisting all the|
| |Central/State/Cooperative/Private bank specified in the database. Select name of the bank in which the |
| |Cheque was deposited. |
| |DD No. |
| |DD Date |
| |Payable at: Account Holder name |
| |The system will prompt the actor to specify the Amount of the test fee / vaccination fee / observation fee paid.|
| | |
| |If the actor chooses the Cash mode of Payment he/she would be required to specify the amount only. |
| | |
| |In this use case quarantine officer will update the payment if it is through cash / Cheque / DD. |
| | |
| |Cancel If Actor cancels the form then system will reach at home page. |
| | |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Data shall be saved in the database. |
| |2. Actor shall successfully logout and brought to the Home Page. 3. After issuance of provisional certificate to|
| |livestock, it will be kept under observation for 30 days at quarantine station and importer has to pay fee for |
| |per LS per day for 30 days. |
| | |
| | |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
| | |
Overview: Payment gateway facilitates the actor to deposit there fees through online transactions like internet banking, debit card or credit card. Payment gateway works as a bridge between the sender’s bank account and the recipient bank accounts.
18 PAYMENT GATEWAY
|UC 3.2.1.18 |Payment Gateway |
|Version: |00 |
|Context: |A payment gateway facilitates the transfer of information between a payment portal (such as a website and mobile|
| |phone) and the Front End Processor or acquiring bank. |
|Priority: |High |
|Frequency: |As and when actor wants to make payment |
|Primary Actor(s) |Importer / Exporter |
|Trigger: |The actor selects the option available as select Internet Banking/Debit Card/Credit Card options |
|Pre conditions: |The user must be registered on the AQIS. He must be logged in, and should have permissions to access ISS and |
| |making online payments for various transactional activities. |
| |The person/agency must be registered with their banks for availing online transactions facility. |
| |The person/agency must have Debit/Credit Card for online transactions. |
|Post conditions: |After successful transactions, the system will generate payment receipt details, shown to the actor on the |
| |screen. The actor could print the Payment Receipt. |
| |On successful transactions, the deposited amount should be stored in ISS database. |
|Input: |Debit Card Details |
| |Credit Card Details |
| |Internet Banking Details |
|Output: |Successful Payment Transfer |
|Normal Flow: |Actor Actions |System Responses |
| | | |
| |The actor clicks on the option “Online Payments”. |The System will prompt the actor to specify following |
| | |details to communicate ISS system with the Payment |
| | |Gateway’s API: |
| |The actor may choose one of the following options: |Unique Application id |
| |Save |Amount being Paid |
| |Submit |Applicant Name |
| | |Recipient Account No |
| |Save: The actor may click on the save option to save |Recipient Account Name |
| |the recorded details |The system will navigate the ISS application to the |
| | |selected bank’s Payment Gateway. |
| |Submit: The clicks on the Submit option to finally | |
| |submit details to the bank’s payment gateway. | |
|Alternative Flow: |None |
|Exceptional Flow: |None |
|Includes: | |
|other use case id | |
|UI: required/not required |Required |
|Priority: Low/medium/high |High |
|Frequency of Use: |Medium |
|Continuous/ frequent/ medium/ | |
|less/ rare | |
|Business Rules: |All details are mandatory to specify. |
| |Minimum amount to be specified for transaction must be 1 Rs. |
| |There should be a mechanism to access the API of payment gateway. |
|Exceptions: |None |
|Special Requirements: |None |
|Assumptions: |The actor is registered either on AQIS and access the application/service through single sign on. |
| |Hardware like computer/laptop system and network connection is available to the actor. |
| |The actor is having a valid mobile number. |
| |Actor is having an internet banking access, debit card and credit card |
|Dependency: |None |
|Notes and Issues: |None |
| |. |
19 SAMPLE COLLECTION AND SENDING TO LAB FOR TESTING
|UC 3.2.1.19 |Sample Collection and Sending to Lab for Testing |
|Version: |00 |
|Context: |This use case is to describe the process of sample collection, vaccination and sample sending to lab for testing|
|Priority: |High |
|Frequency: |As an when sample sent to lab for testing. |
|Primary Actor: |Quarantine Officer/ Testing Lab |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Sample taken for lab testing or vaccination |
|Basic Flow |System will prompt the actor to specify the following details: |
| | |
| |Select : Testing or vaccination or both required |
| |If vaccination required( case 1) |
| |System presents the actor an interface to enter details related to vaccination of LS/ Pet Animal |
| |Vaccine name, validity of vaccine, vaccine for “ name of disease” , vaccination done from, veterinary doctor’s |
| |name, veterinary hospital name |
| |Detail of the livestock: Name, tag number, breed, sex, colour, site of vaccination, date of vaccination |
| |Actor will click on the save and submit button |
| |System captures the input and update the database |
| | |
| |In case if testing required( case 2) |
| |Sample Collection |
| | |
| |Actor shall instruct the system for entering sample data. |
| | |
| |System presents the actor with an interface with listing of form with the important fields : |
| |File number, date of sample taken, date of sending, testing for “ name of disease” , AQCS address where sample |
| |taken, quarantine officer’s name, importer name, mobile number of quarantine officer |
| |5.If both testing & vaccination require( in case of LS/Pet Animal) |
| | |
| |6. The user would be required to specify the testing required detail & vaccination required detail. |
| | |
| |The user would be specify the remarks if required. |
| |The actor inputs all above mentioned details from collected sample. |
| |Actor instructs to save data and reference number is generated. |
| |System captures the input and update the database |
| |Actor shall dispatch the sample to lab. |
| | |
|Alternative Flow: |Invalid Data System will check for any invalid data before saving. If data is not valid, system halts processing|
| |and no data will be saved and system will ask to enter the data again. |
| | |
| |Cancel If Actor cancels the form then system will reach at home page. |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Database is updated and mail trigger to respective person with consolidated information details. |
| |The system shall generate application reference no and thrown a message to the applicant. |
| |Actor can print details reports using system. |
| |Sample send to AQC lab, Bhopal, Madhya Pradesh, in case of import and authorized lab across India in case of |
| |export. |
| |Actor shall successfully logout and brought to the Home Page. |
|Business Rule: | |
|Special Requirements: |Mandatory fields, validation done from client and server both end. |
| |Quarantine officer shall receive the sample report |
|Unresolved Issues: | |
20 RECEIVING SAMPLE AND SENDING REPORT TO QUARANTINE OFFICER
|UC 3.2.1.20 |Receiving Sample and Sending Report to Quarantine Officer |
|Version: |00 |
|Context: |This use case is to describe the process of receiving sample at lab and sending test report to quarantine |
| |officer |
|Priority: |High |
|Frequency: |As and when sample sent to lab for testing |
|Primary Actor: |Testing Lab officer. |
|Preconditions: |Actor shall receive sample data. As when actor login to the application system would show the details of |
| |samples. |
|Basic Flow |1.Actor shall log into his system using use case UC 3.1.2.1 |
| |2.System will display the sample records sent be AQCS officer to the testing lab using use case “Sample |
| |collecting and sending to lab for testing” |
| |3.System will display the records uploaded by the qauarantine officer with the details File number,Date of |
| |Sample taken & date of Sample sending. |
| |4.The actor may choose one record. As the actor select the record the system will diplay the following details. |
| |File number, date of sample taken, date of sending, testing required , AQCS address where sample taken, |
| |quarantine officer’s name, importer name, mobile number of quarantine officer |
| |Detail of the livestock: Name, tag number, breed, sex, colour, site of vaccination, date of vaccination |
| |5.Actor will Accept the sample or either Reject the sample by choosing the respective links availble on the |
| |screen. |
| |6.As an actor accept the sample a “sample registeration number” will be sent to the AQCS officer as well as to |
| |importer. |
| |7.If the actor reject the sample, the rejected sample details will be sent to the AQCS officer. |
|Alternative Flow: |Invalid Data System will check for any invalid data before saving. If data is not valid, system halts processing|
| |and no data will be saved and system will ask to enter the data again. |
| | |
| |Cancel If Actor cancels the form then form will close |
| |Form close if actor clicks on the close button. |
|Post Condition: |Database is updated and mail trigger to respective person with consolidated information details. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
21 SAMPLE TEST RESULT
|UC 3.2.1.21 |Sample Test Result |
|Version: |00 |
|Context: |This use case is to specify the result of tested samples. |
|Priority: |High |
|Frequency: |As and when sample get tested. |
|Primary Actor: |Testing Lab officer. |
|Preconditions: |Actor should have accepted the sample. |
|Basic Flow |1.Actor shall log into his system using use case UC 3.1.2.1 |
| |2. Actor will select the record for which he/she wants to update the test result. |
| |3. System will display the following information in read only mode as specified in the system. |
| |File no., Reference no./ Sample registration number , Nature of sample received. |
| |4.Actor will enter the following details: |
| |Tested code |
| |Test Result |
| | |
| |5.Actor will click on the Save & Subbmit button. |
| |6.The test report result will be available for accessed to the AQCS officer. |
|Alternative Flow: | |
|Post Condition: |1. Database is updated and mail trigger to respective person with consolidated information details. |
| |2. The PDF format will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
|UC 3.2.1.15 |Sample Test Result |
|Version: |00 |
|Context: |This use case is to specify the result of tested samples. |
|Priority: |High |
|Frequency: |As and when sample get tested. |
|Primary Actor: |Testing Lab officer. |
|Preconditions: |Actor should have accepted the sample. |
|Basic Flow |1.Actor shall log into his system using use case UC 3.1.2.1 |
| |2. Actor will select the record for which he/she wants to update the test result. |
| |3. System will display the following information in read only mode as specified in the system. |
| |File no., Reference no. / Sample registration number, Nature of sample received. |
| |4.Actor will enter the following details: |
| |Tested code |
| |Test Result |
| | |
| |5. Actor will click on the Save & Submit button. |
| |6. The test report result will be available for accessed to the AQCS officer. |
|Alternative Flow: | |
|Post Condition: |1. Database is updated and mail trigger to respective person with consolidated information details. |
| |2. The PDF format will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
22 RECEIVING AND VERIFICATION OF TEST REPORT FROM LAB
|UC 3.2.1.22 |Receiving and Verification of Test Report from Lab |
|Version: |00 |
|Context: |This use case is to describe the process of receiving test report from lab. |
|Priority: |High |
|Frequency: |As and when test report received from Lab. |
|Primary Actor: |Quarantine Officer |
|Pre-condition | |
|Basic Flow |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |System will instruct the actor to select the records: |
| |Lab tested / vaccination records |
| |Under observation records. |
| |If actor will select lab tested/vaccination then, System will display the sample records sent be Testing lab |
| |officer to the quarantine officer using use case “Sample test result” |
| |System will display the records uploaded by the testing lab officer with the details File number,reference |
| |number , nature of sample received,Tested,Result. |
| |If actor will select the under observation then, System will dipaly the recods of all the consignment which was |
| |kept under observation by quarantine officer. |
| |If test report result shows negative /observation satisfied, then actor will issue in case of import “Quarantine|
| |clearance certificate “in case of export “Animal quarantine health certificate” by clicking on the link generate|
| |certificate. |
| |If test report result shows positive/ observation not satisfied, then in case of import “ destruction order will|
| |be issued “ in case of export “rejection of consignment” the status of the application will change as |
| |destruction of consignment or rejection of consignment. |
| |The test report result will be available for access to the Importer/Exporter |
|Alternative Flow: |Invalid Data System will check for any invalid data before saving. If data is not valid, system halts processing|
| |and no data will be saved and system will ask to enter the data again. |
| | |
| |Cancel If Actor cancels the form then form will close |
| |Form close if actor clicks on the close button. |
|Post Condition: |1. Database is updated and mail trigger to exporter/importer with a copy of certificate |
| |Actor can print certificate/ test repots using system. |
| |Actor shall successfully sent certificates |
| |The PDF will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
23 NPPO ACCESS TO VIEW PSC/AQC
|UC 3.2.1.23 |NPPO Access to View PSC/AQC |
|Version: |00 |
|Context: |This use case explains the process of viewing the PSC/AQS number by NPPO for verification. |
|Priority: |High |
|Frequency: |As and when test report received from Lab. |
|Primary Actor: |NPPO |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
|Basic Flow |Actor shall log into AQIS application to view AQC over the web using UC 3.1.2.1.and already running application |
| |of PQIS to view PSC. |
| |Actor will click on the link “View PSC/AQC” |
| |System would prompt the user to enter specific details. |
| |PSC/AQC Application Number: |
| | |
| |Actor will click on the “SEARCH” option. |
| |System will fetch the records on the basis of details entered by actor. |
|Alternative Flow: |Invalid Input: If actor enters wrong information of I/E Code, BOS Number, PSC Number then system will display “No|
| |Data Exist”. Actor shall acknowledge the message. System will return back to Pre Condition. |
|Post Condition: |1. Database is updated and mail trigger to exporter/importer with a copy of certificate |
| |Actor can print certificate/ test repots using system. |
| |Actor shall successfully sent certificates |
| |The PDF will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
24 UPDATING REJECTION OF PSC/AQC BY NPPO
|UC 3.2.1.24 |Updating Rejection of PSC/AQC By NPPO |
|Version: |00 |
|Context: |This use case describes the process that how NPPO of other countries gives information of the rejected PSC/AQC. |
|Priority: |High |
|Frequency: |As and when sample get tested. |
|Primary Actor: |NPPO |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |Animal Quarantine Certification Station & Plant Quarantine Station would provide the user id & password to other |
| |country NPPO of their application |
|Basic Flow | Actor shall log into AQIS application to update the rejection of AQC over the web using UC 3.1.2.1.and to update|
| |the rejection of PSC log in to already running application PQIS. |
| | |
| |Actor will click on “update remarks” |
| | |
| |System would prompt the user to enter specific details. |
| |Application Number: |
| |Rejection Reason |
| | |
| |Actor will click on the Save & Submit button. |
| |System captures the input and update the database |
| |AQCS Officer / PQIS Officer would view the rejected AQC/PSC by pulling the report from their system. |
|Alternative Flow: | |
|Post Condition: |1. Database is updated and mail trigger to respective person with consolidated information details. |
| |2. The PDF format will be available for download & print. |
|Business Rule: | |
|Special Requirements: | |
|Unresolved Issues: | |
25 GRIEVANCE MANAGEMENT
|UC 3.2.1.25 |Grievance Management |
|Use Case Name |Capture Grievance Redressal Management System data |
|Actor(s) |Importer/Exporter |
|Description |The grievance management process relates to the capture, processing and answering upon grievances fed into the |
| |system by the Importer/Exporter. |
|Pre Conditions |The Actor should Sign In to PQIS/AQIS applications via CAP. |
| |Actor is registered into PQIS/AQIS portal through user management. |
| |Actor should register his/her grievances with pertaining to his/her application number. |
|Triggers |Actor invokes grievance redressal option presented by the PQIS/AQIS. |
|Basic Flow |Grievance Data Capture |
| |The system presents with an interface on which actor selects the service / grievance from a list of Services for|
| |which he or she has to Register the Grievance against their application number. |
| |When the actor does not see the intended service in the list, ‘Others’ option is selected and on selecting this,|
| |a text area for free text writing is appeared where actor can enter their intended services/grievances. |
| |The actor selects service type from a list option and also fills in an area specified for Summary of the |
| |Grievance that he/She is willing to Register. |
| |Other information includes: |
| |Any Wish to receive notification through email or mobile phone |
| |Mobile number – numeric, optional |
| |Email ID - optional |
| |User instructs to save data into the system. |
| |The system proceeds to save data. Before saving following actions are performed : |
| |Proper area of services is chosen. |
| |Service type is properly mentioned |
| |In case other is mentioned, the detail on this area is specified. |
| |Grievance detail is not blank. |
| |Use case ends. |
|Alternative Flows |A Senior Body will also be provided with the Status of the Grievance, when it has been answered or it is |
| |pending. Depending upon the time duration of answering the queries necessary action will be taken. |
| |Exit condition |
| |Actor chooses to cancel the current operation, the system does not proceed and no data is processed. Use case |
| |ends. |
| |Log out |
| |Actor chooses to log out from the current operation, the interface grievance redressal disappears and no data is|
| |processed. The control goes to the portal home page. Use case ends. |
|Post Conditions |AT BF 1 : |
| |The system processes data, data saved into the backend database. |
| |System generates a Grievance ID and notifies user. Actor will receive a notification in SMS or email about their|
| |grievance acknowledgement. |
| |At AF 2,3 : |
| |Home page is displayed. |
|Exceptions |None |
|Priority |High |
|Business Rules |The PQIS/AQIS shall display Labels/Help text in simple language specific to the practice so that the User does |
| |not find any difficulty in understanding the fields that are to be selected while entering a particular query. |
|Relationships |Extends |
| |Main page of the PQIS/AQIS. |
| |Is Extended By |
| |None. |
| |Uses |
| |Login, if the actor has logged in to the portal. |
| |Id, provided in the previous login, in case the User has already registered a Grievance. |
|Special Requirements |Input can be entered in English. |
| |The reply in the same language in which it will be entered. |
| |The text f grievance is not to exceed 1000 characters. |
26 VIEW GRIEVANCE REDRESSAL
|UC 3.2.1.26 |View Grievance Redressal |
|Actor(s) |Importer/Exporter |
|Description |The grievance management process relates to the viewing the grievances fed into the system by the |
| |importer/exporter |
|Pre Conditions |The Actor has entered the Grievance and has been provided the Grievance id. The Grievance has been sent to the |
| |Elected Body for Review. |
|Triggers |Actor enters the id assigned to him through the PQIS/AQIS. |
|Basic Flow |Grievance View |
| |The system presents with an interface on which actor can enter the Id that was provided earlier on |
| |Registration. |
| |Other information includes: |
| |Any Wish to receive notification through email or mobile phone |
| |Mobile number – numeric, optional |
| |Email ID - optional |
| |User instructs to save data into the system. |
| |The system proceeds to save data. Before saving following actions are performed : |
| |Proper area of services is chosen. |
| |Service type is properly mentioned |
| |In case other is mentioned, the detail on this area is specified. |
| |Grievance detail is not blank. |
| |Use case ends. |
|Alternative Flows |The PQIS/AQIS will also be linked with External Database like the other stake holders like APEDA, EIC & MPEDA |
| |etc. This will assist the importer/exporter. |
| |A Senior Body will also be provided with the Status of the Grievance, when it has been answered or it is |
| |pending. Depending upon the time duration of answering the queries necessary action will be taken. |
| |Exit condition |
| |Actor chooses to cancel the current operation, the system does not proceed and no data is processed. Use case |
| |ends. |
| |Log out |
| |Actor chooses to log out from the current operation, the interface grievance redressal disappears and no data |
| |is processed. The control goes to the portal home page. Use case ends. |
|Post Conditions |AT BF 1 : |
| |The system processes data, data saved into the backend database. |
| |System generates a Grievance ID and notifies user. Actor will receive a notification in SMS or email about |
| |their grievance acknowledgement. |
| |At AF 2,3 : |
| |Home page is displayed. |
|Exceptions |None |
|Priority |High |
|Business Rules |The AQIS/PQIS shall display Labels/Help text in simple language specific to the practice so that the User does |
| |not find any difficulty in understanding the fields that are to be selected while entering a particular query. |
|Relationships |Extends |
| |Main page of the PQIS/AQIS. |
| |Is Extended By |
| |None. |
| |Uses |
| |Login, if the actor has logged in to the portal. |
| |Id, provided in the previous login, in case the User has already registered a Grievance. |
|Special Requirements |Input can be entered in English |
| |The reply in the same language in which it will be entered. |
| |The text for grievance is not to exceed 1000 characters. |
|Assumptions |The query will directly post to PQIS/AQIS portal via CAP. |
27 GRIEVANCE REDRESSAL SYSTEM
|UC 3.2.1.27 |Grievance Redressal System |
|Actor(s) |Nodal Officer |
|Description |This use case would describe the way to address the grievances |
|Pre Conditions |The Actor has entered the Grievance and has been provided the Grievance id. The Grievance has been sent to the |
| |Nodal Officer for Review & redressal |
|Triggers | |
|Basic Flow |Grievance Redressal |
| |The system presents with an interface on which actor click on the grievance redressal system to view the all fed|
| |grievance by the importer/exporter with their application number. |
| |Actor will select one application. |
| |Actor would now put the remark or solution in the TEXT coloum. |
| |Actor would now click on the SAVE & Submit button. remarks is updated in the database. |
| |Messages will trigger to the applicant. |
| |As notification through email or mobile phone |
| |Mobile number – numeric, optional |
| |Email ID - optional |
| |User instructs to save data into the system. |
| |Use case ends. |
|Alternative Flows |The PQIS/AQIS will also be linked with External Database like the other stake holders like APEDA, EIC & MPEDA |
| |etc. This will assist the importer/exporter. |
| |A Senior Body will also be provided with the Status of the Grievance, when it has been answered or it is |
| |pending. Depending upon the time duration of answering the queries necessary action will be taken. |
| |Exit condition |
| |Actor chooses to cancel the current operation, the system does not proceed and no data is processed. Use case |
| |ends. |
| |Log out |
| |Actor chooses to log out from the current operation, the interface grievance redressal disappears and no data is|
| |processed. The control goes to the portal home page. Use case ends. |
|Post Conditions |AT BF 1 : |
| |The system processes data, data saved into the backend database. |
| |System generates a Grievance ID and notifies user. Actor will receive a notification in SMS or email about their|
| |grievance acknowledgement. |
| |At AF 2,3 : |
| |Home page is displayed. |
|Exceptions |None |
|Priority |High |
|Business Rules |The AQIS/PQIS shall display Labels/Help text in simple language specific to the practice so that the User does |
| |not find any difficulty in understanding the fields that are to be selected while answering a particular query. |
|Relationships |Extends |
| |Main page of the PQIS/AQIS. |
| |Is Extended By |
| |None. |
| |Uses |
| |Login, if the actor has logged in to the portal. |
| |Id, provided in the previous login, in case the User has already registered a Grievance. |
|Special Requirements |Input can be entered in English |
| |The reply in the same language in which it will be entered. |
| |The text for grievance is not to exceed 1000 characters. |
|Assumptions |The query will directly post to PQIS/AQIS portal via CAP. |
28 MIS REPORT
|UC 3.2.1.28 |MIS Report |
|Version: |00 |
|Context: |This use case is for generation of MIS report from master table which will be sent to higher authority for |
| |decision making. |
|Priority: |HIGH |
|Frequency: |Frequent |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow: |System presents the Actor list of master tables with the option of select |
| |System presents a list of master table to actor. Actor shall select one, two or all of the tables from the master |
| |table given below: |
| |Application Status(Issued/Pending) |
| |Country wise report for AQS |
| |Pending Report for SIP |
| |Date of Application |
| |Location of Applying Certification |
| |Country of Import/Export |
| |Approving Authority |
| |Validity of Certificate |
| |List of stakeholders |
| |Type of Applicant (Importer/Exporter) |
| |State |
| |District |
| |Location for Issuing Certificate |
| |ITC (HS) Code |
| |Purpose of Lab Testing samples (Import/Export) |
| |Lab Test Name |
| |Tenders |
| |List of restricted or free Livestock/Livestock Product |
| |List of Livestock/Livestock Product refused registration |
| |List of designated inspectors |
| |List of vaccination/ Disease/ Test |
| |List of AQCS issuing public officers |
| |Actor shall view/print the detail data of the selected table(s) from the master table. |
| |If Actor shall instruct to add/delete tables in the report. |
| |Actor checks the particular table to be added/ deleted and presses add/delete. |
| |System shows the table contents with add/delete access. |
| |Add/Delete table in the report. |
| |Actor shall instruct to add/delete the table in the MIS report. |
| |The Use Case Ends. |
|Alternative Flow: | |
|Post Condition: |Tables should be updated. |
| |Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before view the forms details. And if found then |
| |display the alert messages corresponding to related field. |
| |Cancel If Actor cancels the form then system will reach at home page. |
| |Duplicate Entry: System shall check at the time of updating data, there shall exist same data in the table. If |
| |same data does not exist in database then the System displays a message “data changed.” |
|Special Requirements: |Mandatory fields, validation done from client and server both end. |
|Business Requirement | |
|Unresolved Issues: | |
29 MASTER DATA MANAGEMENT
|UC 3.2.1.29 |Master Data Management |
|Version: |00 |
|Context: |This use case is for adding, editing or deleting contents from master table |
|Priority: |HIGH |
|Frequency: |Frequent |
|Primary Actor: |System Administrator |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Basic Flow: |System presents the Actor list of master tables with the option of add, edit and delete |
| |If Actor shall instruct to add the master table. |
| |• Will add a master table (if there is any feature updated to the application in future then the master table to be|
| |created for support) |
| |System presents a list of master table to actor. Actor shall select the one of the master table from the below |
| |given list: |
| |Approving Authority |
| |Registration Agency |
| |Validity of Certificate |
| |Type of Certificate (SIP,AQC) |
| |Licensing Issuing Agencies |
| |Type of inputs |
| |Product Code – input Wise |
| |List of stakeholders |
| |Type of Applicant (Importer/Exporter) |
| |State |
| |District |
| |Location for Issuing Certificate |
| |ITC (HS) Code |
| |Office Type |
| |Office Details |
| |Block |
| |Local Body Code |
| |Designation |
| |Certificate Format |
| |Fee Criteria |
| |Fee Structure |
| |Home Page Information |
| |Purpose of Lab Testing samples (Import/Export) |
| |Lab Test Name |
| |Certified Parameters for quality testing |
| |Purpose of Issuing Certificate |
| |Importer & Exporter for e- certification |
| |Tenders |
| |List of restricted or free Livestock/Livestock Product |
| |List of Livestock/Livestock Product refused registration |
| |List of designated inspectors |
| |List of vaccination/ Disease/ Test |
| |Disease Category |
| |List of AQCS issuing public officers |
| |Laws |
| |Standards |
| |Notify point of entry |
| |List of Country |
| |Actor shall enter the details as per provided fields and instruct to save the data. |
| |If Actor shall instruct to edit the master table. |
| |Actor checks the particular table to be edited and presses edit. |
| |System shows the table contents with editable access. |
| |Edits the content (Add/Modify). |
| |Actor shall instruct to update the table. |
| |The Use Case Ends. |
|Alternative Flow: | |
|Post Condition: |Tables should be updated. |
| |Invalid data or left blank any required field. |
| |Application will check the invalid data or left blank any field before save the forms details. And if found then |
| |display the alert messages corresponding to related field. |
| |Cancel If Actor cancels the form then system will reach at home page. |
| |Duplicate Entry: System shall check at the time of updating data, there shall not exist same data in the table. If |
| |same data is exist in database then the System displays a message “Duplicate data not allowed.” |
|Special Requirements: |Mandatory fields, validation done from client and server both end. |
|Business Requirement | |
|Unresolved Issues: | |
2 FAQ
• View Manage FAQ Page • Manage FAQ (View/ Create/Modify/Delete) • View Manage FAQ Category Page • Manage FAQ Category (View/ Create/Modify/Delete)
[pic] Diagram 31: FAQ Use Cases
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.2.2.1 |View Manage FAQ Page |This use case is used to view |Actor with the Assigned role of FAQ Manager |
| | |manage FAQ page | |
|UC 3.2.2.2 |View FAQ |This use case is used to view |Importer/Exporter/General users/FAQ Manager |
| | |FAQ page | |
|UC 3.2.2.3 |Add FAQ |This use case is used to add FAQ|Actor with the Assigned role of FAQ Manager |
|UC 3.2.2.4 |Modify FAQ |This use case is used to modify |Actor with the Assigned privilege of FAQ Manager |
| | |FAQ | |
|UC 3.2.2.5 |Delete FAQ |This use case is used to delete |Actor with the Assigned privilege of FAQ Manager |
| | |FAQ | |
|UC 3.2.2.6 |View FAQ Category |This use case is used to view |Actor with the Assigned privilege of FAQ Category|
| | |FAQ Category |Manager |
|UC 3.2.2.7 |Add FAQ Category |This use case is used to add FAQ|Actor with the Assigned privilege of FAQ Category|
| | |Category |Manager |
|UC 3.2.2.8 |Modify FAQ Category |This use case is used to modify |Actor with the Assigned privilege of FAQ Category|
| | |FAQ Category |Manager |
|UC 3.2.2.9 |Delete FAQ Category |This use case is used to delete |Actor with the Assigned privilege of FAQ Category|
| | |FAQ Category |Manager |
1 VIEW MANAGE FAQ PAGE
|UC 3.2.2.1 |View Manage FAQ Page |
|Version: |00 |
|Context: |This use case would allow the actor to manage FAQ in the system. The FAQ will be related to a FAQ category in |
| |the specific AQIS application. |
| | |
| |Actor would have the following options under Manage FAQ: |
| |Manage FAQ/Queries: |
| |• View FAQ |
| |• Add FAQ |
| |• Modify FAQ |
| |• Delete FAQ |
| |• Answer Queries |
| |Manage FAQ Categories: |
| |• View FAQ Category |
| |• Add FAQ Category |
| |• Modify FAQ Category |
| |• Delete FAQ Category |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned role of FAQ Manager |
|Preconditions: |User must be registered at AQIS via CAP. |
| |Actor shall log into AQIS application over the web using UC 3.1.2.1. |
| |User should be authenticated by system and set his/her states as Login. |
|Basic Flow: |1. The actor instructs the system to “Manage FAQ”. |
| |2. System presents an interface with following options: |
| |a. Manage FAQ/Queries: |
| |View FAQ |
| |Add FAQ |
| |Modify FAQ |
| |Delete FAQ |
| |Answer Queries |
| | |
| |b. Manage FAQ Categories: |
| |View FAQ Category |
| |Add FAQ Category |
| |Modify FAQ Category |
| |Delete FAQ Category |
| |3. Actor instructs to close the link. |
| |4. System will close the form. |
| | |
| |The use case ends. |
|Alternative Flow: |Cancel If Actor cancels the form then system will reach at home page. |
|Post Condition: |Actor successfully views the Manage FAQ page. |
| |If the actor clicks the Close link, then the system would respond with the message, “Do you wish to close the |
| |form? If the Actor confirms, then system would close the form and the actor would be brought back to Main |
| |Screen; otherwise, the actor would be brought back to where the actor was before clicking the Close link. |
|Special Requirements: | |
|Business Rules | |
|Dependency |Extends |
| |View AQIS application |
| |or |
| |View AQIS application |
| |Is Extended By |
| |1. View FAQ |
| |2. Add FAQ |
| |3. Modify FAQ |
| |4. Delete FAQ |
| |5. Answer Queries |
| |6. View FAQ Category |
| |7. Add FAQ Category |
| |8. Modify FAQ Category |
| |9. Delete FAQ Category |
| | |
| |Uses |
| |Login |
2 VIEW FAQ
Overview: The Frequently Asked Questions and their answers will be published on the Homepage of the service and the AQIS. The Importer/Exporter can find the answers of their questions related to different sub-services/subjects in the View FAQ section of the Home Page or they can submit new query by clicking on the available link.
|UC 3.2.2.2 |View FAQ |
|Version: |00 |
|Context: |This use case would allow the actor to view FAQ list. |
| |In case actor is FAQ Manager, he/she would be able to do the following activities: |
| |• Add FAQ |
| |• Modify FAQ |
| |• Delete FAQ |
| |• View Query Responses |
| |In this, Importer/Exporter would be able to submit their queries related to any service/sub service/subject. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Importer/Exporter /FAQ Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |User should be authenticated by system and set his/her states as Login. |
| |Actor is viewing the FAQ list. |
| |Or in case actor is FAQ manager, he/she will be viewing the FAQ list and would be having the option to add an |
| |FAQ, modify or delete an FAQ. |
|Basic Flow: |1. General users is viewing the FAQ list on the Service Home Page/ AQIS |
| |2. System would display the list of FAQ on the screen, with each question displayed as hyperlink |
| |3. Actor clicks on the question hyperlink |
| |4. System displays the answers of the questions specified by the FAQ Manager in the System |
| |5. Similarly each question in the FAQ list can be clicked by the actor to view the answer as required by |
| |him/her. |
| |6. Actor may also add a new Query, if it is not available in the FAQ list by clicking on the Add New Query link.|
| |Refer Add New Query use case. |
| | |
| |The use case ends. |
|Alternative Flow: |FAQ manager or actor is logged in and is viewing the FAQ list: |
| |System would display the list of FAQ on the screen, with each question displayed as hyperlink. |
| |The actor clicks on the question hyperlink to view the answer of the question. |
| |Actor can also choose to Modify FAQ or Delete FAQ displayed on the list. |
| |Actor may Add FAQ in the list. |
|Post Condition: |Actor successfully views the View FAQ list on the AQIS portal or specific AQIS Service/ application. |
| |Added FAQ by the Citizen actor will be forwarded to the respective service/sub service/subject matter expert for|
| |giving responses and an e-mail will also be thrown to the subject matter expert’s registered e-mail address. |
| |An FAQ reference number will be generated by the System and an SMS will be delivered on the Importer/Exporter & |
| |General users registered mobile number |
| |The replied FAQs will be added to the database and will be displayed on the View FAQ Page. |
|Special Requirements: | |
|Business Rules |In case user is viewing the FAQ through AQIS portal, only FAQs of the available AQIS service/sub service to the |
| |user (i.e. as per his/her user privileges) would be available for managing in the list. |
| |In case user is viewing the FAQ list through the specific AQIS application, then FAQ of only that AQIS |
| |service/sub service would be displayed to him/her. |
| |FAQ manager of specific AQIS service/sub service should be able to View/Add/Modify/Delete FAQ of his/her |
| |respective AQIS service/sub service. |
| |While FAQ manager of AQIS portal should be able to View/ Add/Modify/Delete FAQ of all AQIS service/sub service. |
|Dependency |Extends |
| |View Manage FAQ list |
| |Is Extended By |
| |1. Add FAQ |
| |2. Modify FAQ |
| |3. Delete FAQ |
| |4. Add New Query |
| |Uses |
| |Login |
3 ADD FAQ
Overview: The System provides a provision to the actor to add FAQs. Similarly citizens like farmer will have the provision to add FAQs.
|UC 3.2.2.3 |Add FAQ |
|Version: |00 |
|Context: |This use case allow actor to Add FAQ in the system. |
| |FAQ would be added under a specific AQIS Service/Sub Service and under a specific FAQ Category. Refer Add FAQ |
| |category use case. |
| |FAQ once added would be available to the General users for viewing and to FAQ manager for further modification |
| |and deletion. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned role of FAQ Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ manager. |
| |Actor is viewing the Manage FAQ list and clicks on Add FAQ. |
|Basic Flow: |The Actor shall instruct to Add FAQ. |
| |System captures the following mandatory parameters to add a new FAQ : |
| |AQIS application/ SIP Sub Service name – Actor selects the AQIS application/ SIP Sub service name from the drop |
| |box list of AQiS application names/ SIP sub services names under which FAQ is to be added |
| |FAQ Category - Actor selects the desired FAQ category from the system provided drop box list of available FAQ |
| |category. |
| |FAQ text – Actor enters the question text of the FAQ Text. |
| |FAQ Answer Text - Actor enters the answer text of the FAQ. |
| |The actor could either Save or publish the data. |
| |If Actor shall instruct to save data. |
| |The System responds with the message,” FAQ was successfully added in the system.” |
| |If Actor shall instruct to publish link |
| |The data will be saved in the database and would be displayed in the View FAQ list on the AQIS/Service Home |
| |Page. |
| |The use case ends. |
|Alternative Flow: |Actor is answering a query through Answer Query Use case and chooses to Add the query to the FAQ list: |
| |System captures the 1a and 1b of the normal flow steps and |
| |adds the query answered by him/her in the system as the FAQ. |
| |Refer Answer Query Use Case. |
| |Actor attempts to submit without selecting the ‘AQIS/SIP Service/Sub service name’: |
| |System displays the message “Please select the AQIS/SIP Service/Sub Service name”. |
| |Actor attempts to submit without selecting the ‘FAQ Category’: |
| |System displays the message “Please select the FAQ category”. |
| |Actor attempts to submit without entering the ‘FAQ text’ |
| |System displays the message “Please enter value in FAQ text.” |
| |Actor attempts to submit without entering the ‘FAQ Answer text’ |
| |System displays the message “Please enter value in FAQ Answer text.” |
|Post Condition: |Actor successfully Add the FAQ on the specific AQIS/SIP |
| |Service/Sub service and specific FAQ category. |
| |Successfully Published FAQ would be available to the |
| |General Citizen for viewing and to the FAQ manager of the |
| |respective AQIS Service/ Sub service and AQIS portal. |
| |Only Saved FAQs will be available for further modification |
| |and deletion. |
| | |
|Special Requirements: | |
|Business Rules |All AQIS/SIP Service/Sub Service names would be available in the drop box. |
| |All FAQ category names as available in the system would be available in the FAQ category name drop box. |
| |Depending upon the selected Service/Sub service, the FAQ Category name drop box values would be displayed. |
| |FAQ manager of specific Service/Sub service should be able to Add/modify/delete FAQ of his/her respective |
| |Service/Sub service. |
| |Authorized actor will be allowed to publish the FAQs. |
| |While FAQ manager of AQIS portal should be able to Add/modify/delete FAQ of any AQIS Service/Sub service. |
|Dependency |Extends |
| |View Manage FAQ Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
4 MODIFY FAQ
Overview: The System provides a provision to the actor to add FAQs. Similarly citizens like farmer will have the provision to add FAQs.
|UC 3.2.2.4 |Modify FAQ |
|Version: |00 |
|Context: |This use case allows actor to Modify a FAQ available in the system. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ manager. |
| |Actor is viewing the Manage FAQ list and clicks on Modify FAQ. |
|Basic Flow: |1. The Actor shall instruct to Manage FAQ. |
| |2 System would allow actor to modify the following mandatory parameters, as added by the actor while adding the |
| |new FAQ. Refer Add FAQ use case: |
| |a. AQIS Service/Sub Service name |
| |b. FAQ Category |
| |c. FAQ text |
| |d. FAQ Answer Text3. The actor could either Save or publish the data. |
| |4. If Actor shall instruct to save data. |
| |The System responds with the message,” FAQ was successfully added in the system.” |
| |5. If Actor shall instruct to publish link |
| |The data will be saved in the database and would be displayed in the View FAQ list on the AQIS/Service Home |
| |Page. |
| |The use case ends. |
|Alternative Flow: |1. No FAQ available in the system: |
| |System displays the message as “Currently No FAQ is Available.” |
| |2. Actor attempts to submit without selecting the ‘AQIS Service/Sub service name’: |
| |System displays the message “Please select the AQIS Service/Sub Service name”. |
| |3. Actor attempts to submit without selecting the ‘FAQ Category’: |
| |System displays the message “Please select the FAQ category”. |
| |Actor attempts to submit without entering the ‘FAQ text’ |
| |System displays the message “Please enter value in FAQ text.” |
| |Actor attempts to submit without entering the ‘FAQ Answer text’ |
| |System displays the message “Please enter value in FAQ Answer text.” |
|Post Condition: |Actor successfully modifies the FAQ. |
| |Successfully Modified and Published FAQ would be available to the General users for viewing and to the FAQ |
| |manager of respective SAP Service/Sub service and AQIS portal for further modification and deletion. |
|Special Requirements: | |
|Business Rules |All red asterisk mark fields are mandatory to specify. |
| |Service/Sub Service names would be available in the drop box. |
| |All FAQ category names as available in the system would be available in the FAQ category name drop box. |
| |Depending upon the selected Service/Sub Service, the FAQ Category name drop box values would be displayed. |
| |FAQ manager of specific Service/Sub Service should be able to Add/modify/delete FAQ of his/her respective |
| |Service/Sub Service. |
| |While FAQ manager of AQIS portal should be able to Add/modify/delete FAQ of any AQIS application. |
|Dependency |Extends |
| |View Manage FAQ Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
5 DELETE FAQ
Overview: The System provides a provision to the actor to delete existing FAQs.
|UC 3.2.2.5 |Delete FAQ |
|Version: |00 |
|Context: |This use case allows actor to Delete a FAQ available in the system. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ manager. |
| |Actor is viewing the Manage FAQ list and clicks on Delete FAQ. |
|Basic Flow: |1. The Actor shall instruct to Delete FAQ. |
| |System displays the confirmation message “Do really wish to Delete this FAQ?” with yes or no option. In case |
| |actor selects yes, system deletes the FAQ and displays the message “FAQ was successfully deleted.” In case actor|
| |selects No, system returns to the pre condition. |
| |The use case ends. |
|Alternative Flow: |1. No FAQ available in the system: |
| |System displays the message as “Currently No FAQ is Available.” |
|Post Condition: |Actor successfully deletes the FAQ. |
| |Successfully Deleted FAQ is removed from FAQ List as available on View FAQ list page |
|Special Requirements: | |
|Business Rules |FAQ manager of specific Service/Sub service should be able to delete FAQ of his/her respective |
| |service/sub-service. |
| |While FAQ manager of AQIS portal should be able to delete saved FAQ of any AQIS service/sub service. |
| |To delete a published FAQ, actor should un-publish that record and then delete it. |
| |If the FAQ added by the citizen/farmer is still pending to the expert advisor for its acceptance or rejection, |
| |it’ll not be allowed to be deleted. |
|Dependency |Extends |
| |View Manage FAQ Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
6 VIEW FAQ CATEGORY
Overview: The System provides a provision to the actor to View FAQ Categories existing FAQs.
|UC 3.2.2.6 |View FAQ Category |
|Version: |00 |
|Context: |This use case would allow the actor to view FAQ Category list. |
| |In actor would be able to do the following activities: |
| |• View FAQ Category |
| |• Add FAQ Category |
| |• Modify FAQ Category |
| |• Delete FAQ Category |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Category Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| | |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ Category manager. |
| |Actor is viewing the Manage FAQ list and clicks on View FAQ Category List. |
|Basic Flow: |1. Actor chooses to View FAQ Category List. |
| |2. System would display the list of FAQ Category on the screen. |
| |3. Actor can choose to : |
| |View FAQ Category |
| |Add FAQ Category |
| |Modify FAQ Category |
| |Delete FAQ Category |
| |The use case ends. |
|Alternative Flow: |No FAQ Category is available in the system, |
| |System displays the message as “Currently No FAQ Category is Available.” |
|Post Condition: |1. Actor successfully views the View FAQ Category list on the AQIS portal or specific Service/Sub Service. |
|Special Requirements: | |
|Business Rules |FAQ Category manager of specific Service/Sub service should be able to View FAQ Category list of his/her |
| |respective service/sub service. |
| |While FAQ Category manager of AQIS portal should be able to View FAQ Category list belonging to all AQIS |
| |services/ applications. |
|Dependency |Extends |
| |View Manage FAQ page |
| |Is Extended By |
| |1. View FAQ Category |
| |2. Add FAQ Category |
| |3. Modify FAQ Category |
| |4. Delete FAQ Category |
| |Uses |
| |Login |
7 ADD FAQ CATEGORY
Overview: The System provides a provision to the actor to Add FAQ Categories existing FAQs.
|UC 3.2.2.7 |Add FAQ Category |
|Version: |00 |
|Context: |This use case allows actor to Add FAQ Category in the system. |
| |FAQ Category would be added under a specific AQIS Service/Sub Service. |
| |FAQ category once added would be available to the FAQ manager while adding new FAQ in the system. Refer Add FAQ.|
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Category Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ Category manager. |
| |Actor is viewing the FAQ Category List |
|Basic Flow: |1. The Actor shall instruct to Add FAQ Category. |
| |2. System captures the following mandatory parameters to add a new FAQ Category : |
| |a. AQIS Service/Sub Service name – Actor selects the service/ sub service name from the drop box list of |
| |services/sub services names under which FAQ Category would be added. |
| |b. FAQ Category Name - Actor enters the FAQ category name to be added in the system. |
| |c. FAQ Recipient email(s) – Actor enters the email(s) of the officials to whom the email should be triggered by |
| |the system in case query against them which would be added by the general Citizen on the AQIS portal or specific|
| |AQIS application. Actor may add more than one email address separating each email id with a comma. Refer Add |
| |Query use case. |
| |4. If Actor shall instruct to save data. |
| |The System responds with the message,” FAQ Category was successfully added in the system.” |
| |The use case ends. |
|Alternative Flow: |1. No FAQ Category is available in the system, |
| |System displays the message as “Currently No FAQ Category is Available.” |
| |2. Actor attempts to submit without selecting the ‘AQIS Service/Sub service name’: |
| |System displays the message “Please select the AQIS Service/Sub Service name”. |
| |3. Actor attempts to submit without selecting the ‘FAQ Category Name’: |
| |System displays the message “Please select the FAQ category Name”. |
| |4. Actor attempts to submit without entering the ‘FAQ Recipient email(s)’: |
| |System displays the message “Please enter value in FAQ Recipient email(s).” |
|Post Condition: |Actor successfully views the View FAQ Category list on the AQIS portal or specific Service/Sub Service. |
|Special Requirements: | |
|Business Rules |FAQ Category manager of specific Service/Sub service should be able to View FAQ Category list of his/her |
| |respective service/sub service. |
| |While FAQ Category manager of AQIS portal should be able to View FAQ Category list belonging to all AQIS |
| |services/ applications. |
|Dependency |Extends |
| |View FAQ Category List |
| |Is Extended By |
| |Add FAQ |
| |Uses |
| |Login |
8 MODIFY FAQ CATEGORY
Overview: The System provides a provision to the actor to add FAQs. Similarly citizens like farmer will have the provision to add FAQs.
|UC 3.2.2.8 |Modify FAQ Category |
|Version: |00 |
|Context: |This use case allows actor to Modify FAQ Category in the system. |
| |FAQ Category would be added under a specific AQIS Service/Sub Service. |
| |FAQ category once modified would be available to the FAQ manager while adding new FAQ in the system. Refer Add |
| |FAQ. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Category Manager |
|Preconditions: |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
| |This use case allows actor to Modify FAQ Category in the system. |
| |FAQ Category would be added under a specific AQIS Service/Sub Service. |
| |FAQ category once modified would be available to the FAQ manager while adding new FAQ in the system. Refer Add |
| |FAQ. |
|Basic Flow: |1. The Actor shall instruct to Manage FAQ category. |
| |2. System would allow actor to modify the following mandatory parameters, as added by the actor while adding the|
| |new FAQ Category. Refer Add FAQ Category use case: |
| |a. AQIS Service/Sub Service name |
| |b. FAQ Category Name |
| |c. FAQ Recipient email(s) |
| |d. The actor may add more than one email address separating each email id with a comma. Refer Add Query use |
| |case. |
| |4. Actor shall instruct to save data. |
| |The System responds with the message,” FAQ was Category successfully added in the system.” |
| | |
| |The use case ends. |
|Alternative Flow: |1. No FAQ available in the system: |
| |System displays the message as “Currently No FAQ Category is Available.” |
| |2. Actor attempts to submit without selecting the ‘AQIS Service/Sub service name’: |
| |System displays the message “Please select the AQIS Service/Sub Service name”. |
| |3. Actor attempts to submit without selecting the ‘FAQ Category Name’: |
| |System displays the message “Please select the FAQ category Name”. |
| |Actor attempts to submit without entering the ‘FAQ Recipient email(s)’: |
| |System displays the message “Please enter value in FAQ Recipient email(s).” |
| |Actor attempts to modify a FAQ category which has one or more FAQ attached to it: |
| |System displays the warning message “One or more FAQ exists under the selected FAQ category. Do you still wish |
| |to proceed?” System would proceed only on actor’s confirmation. |
|Post Condition: |Actor successfully modifies the FAQ Category under the specific AQIS Service/Sub Service. |
| |Successfully modified FAQ Category would be available in the FAQ category drop box while adding a new FAQ. Refer|
| |Add FAQ use case. |
| |Successfully modified FAQ Category would be available to the respective AQIS Service/Sub Service and AQIS portal|
| |FAQ Category Manager for further modification and deletion. |
|Special Requirements: | |
|Business Rules |FAQ Category manager of specific AQIS Service/Sub Service application should be able to modify FAQ Category |
| |under his/her respective service/sub service only. |
| |While FAQ Category manager of AQIS portal should be able to modify FAQ Category under any AQIS Service/ Sub |
| |service. |
| |The existing FAQ should be automatically remapped with the modified FAQ category. |
|Dependency |Extends |
| |View FAQ Category List |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
9 DELETE FAQ CATEGORY
Overview: The System provides a provision to the actor to Delete FAQ Categories existing FAQs.
|UC 3.2.2.9 |Delete FAQ Category |
|Version: |00 |
|Context: |This use case allows actor to Delete FAQ Category in the system. |
| |FAQ Category would be added under a specific AQIS Service /Sub Service. |
| |FAQ Category once Deleted would be removed from the View FAQ Category list and would not be available to the |
| |citizen to view. |
|Priority: |HIGH |
|Frequency: |Medium |
|Primary Actor: |Actor with the Assigned privilege of FAQ Category Manager |
|Preconditions: |Actor shall log into AQCS application over the web using UC 3.1.2.1 |
| |The actor must have access to the application domain and should be logged into the AQIS Portal or specific AQIS |
| |Service/Sub-service as FAQ Category manager. |
| |Actor is viewing the FAQ Category List. |
|Basic Flow: |1. The Actor shall instruct to Delete FAQ Category. |
| |System displays the confirmation message “Do really wish to Delete this FAQ Category?” with yes or no option. In|
| |case actor selects yes, system deletes the FAQ Category and displays the message “FAQ Category was successfully |
| |deleted.” In case actor selects No, system returns to the pre condition. |
| |The use case ends. |
|Alternative Flow: |1. No FAQ available in the system: |
| |System displays the message as “Currently No FAQ is Available.” |
|Post Condition: |Actor successfully deletes the FAQ Category. |
| |Successfully Deleted FAQ Category is removed from FAQ Category List as available on View FAQ Category list page.|
| |FAQ category, under which FAQ has been available in the View FAQ use case, will not be allowed to be deleted. In|
| |this case to delete FAQ category, FAQ under is need to be deleted |
|Special Requirements: | |
|Business Rules |FAQ Category manager of specific AQIS service/sub service should be able to delete FAQ Category as available |
| |under his/her respective service/sub service. |
| |While FAQ Category manager of AQIS portal should be able to delete FAQ Category of any AQIS service/sub service.|
| |System should not allow the deletion of FAQ category which has one or more FAQ attached with it |
|Dependency |Extends |
| |View FAQ Category List |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
3 MASTER USE CASES
|Use Case No. |Functionality |Description |Actor(s) |
|UC 3.2.3.1 |Manage Country |This use case is to describe the process to manage|System Administrator |
| | |the Country details | |
|UC 3.2.3.2 |Manage NPPO Details |This use case is to describe the process to manage|System Administrator |
| | |the NPPO details | |
|UC 3.2.3.3 |Manage Departments |This use case is to describe the process to manage|System Administrator |
| | |the Department details | |
|UC 3.2.3.4 |Manage Products |This use case is to describe the process to manage|System Administrator |
| | |the product details | |
|UC 3.2.3.5 |Manage Samples |This use case is to describe the process to manage|System Administrator |
| | |the sample details | |
|UC 3.2.3.6 |Manage Airport Name |This use case is to describe the process to manage|System Administrator |
| | |Airport Name | |
|UC 3.2.3.7 |Manage Seaport Name |This use case is to describe the process to manage|System Administrator |
| | |Seaport Name | |
|UC 3.2.3.8 |Manage Test Details |This use case is to describe the process to manage|System Administrator |
| | |Test Details | |
|UC 3.2.3.9 |Manage Colour Details |This use case is to describe the process to manage|System Administrator |
| | |Colour Details | |
|UC 3.2.3.10 |Manage Animal Category |This use case is to describe the process to manage|System Administrator |
| | |Animal Category | |
|UC 3.2.3.11 |Manage Animal Breed |This use case is to describe the process to manage|System Administrator |
| | |Animal Breed | |
|UC 3.2.3.12 |Manage SIP Condition Product wise |This use case is to describe the process to manage|SIP user with the assigned|
| | |the condition to issue SIP. |privilege to add |
| | | |condition. |
1 MANAGE COUNTRY
|UC 3.2.3.1 |Manage Country |
|Version: |00 |
|Context: |This use case is to describe the process to manage the Country details |
|Priority: |High |
|Frequency: |As and when require |
|Primary Actor(s) |AQIS user with the assigned privilege to add country details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Country->Country |
| |Details. |
|Normal Flow |The System will prompt the actor to specify following country details: |
| |Country Name and Country Code: The actor would select name of the country along with country code being |
| |displayed in the list available for selection. The displayed list will enlist all the Country Names along with |
| |their codes for selection. |
| |The actor could add multiple countries being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected country details. |
| |The actor may click the Edit button to edit the selected country details. |
| |The actor may click the Delete button to delete the selected country details. |
| |The actor may click the View button to view the saved country details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Country Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Country Details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All information related to the country details would be stored in the database with status set to save. |
| |c. The saved country details would be available for further modification through the Modify button. |
| |d. The country details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in|
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank country details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save country details when no country has been selected from the list. |
| |The System would respond with a message, “No country name has been selected. Please select at least one country |
| |to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception occurs |
| |when the actor saves the Country Details without selecting any country. |
| |The actor attempts to edit the country details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the country details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the country details when the country name with the same Country Code already exists |
| |in the System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Country Name and Country Code |
| |System would display a default list of Country Names and Country Codes. |
| |Country Details, which have already been used in the application, should not be available to select for |
| |deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
2 MANAGE NPPO DETAILS
|UC 3.2.3.2 |Manage NPPO Details |
|Version: |00 |
|Context: |This use case is to describe the process to manage the NPPO details |
|Priority: |High |
|Frequency: |Medium |
|Primary Actor(s) |AQIS user with the assigned privilege to manage NPPO details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add NPPO details under the option available in Master Entry -> Manage NPPO details->NPPO |
| |Details. |
|Normal Flow |The System will prompt the actor to specify following details: |
| |NPPO Name: The actor would specify NPPO Name. |
| |NPPO Code: The actor would specify code of the specified NPPO. |
| |The actor could add multiple NPPO details using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the specified NPPO details. |
| |The actor may click the Edit button to edit the selected NPPO details. |
| |The actor may click the Delete button to delete the selected NPPO details. |
| |The actor may click the View button to view the saved NPPO details. |
| |At any point of time, actor clicks the Clear button to discard the details entered till then or clicks the Close|
| |button to close the NPPO Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “NPPO Details saved successfully” and the actor would be brought |
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the NPPO would be stored in the database with status set to save. |
| |c. The saved NPPO details would be available for further modification through the Modify button. |
| |d. The NPPOI details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in|
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank NPPO details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save NPPO details without specifying NPPO Name. |
| |The System would respond with a message, “Please specify NPPO Name”. Click OK to continue. The actor would be |
| |brought back to Pre Condition. The exception occurs when the actor saves the NPPO Details form without NPPO |
| |Name. |
| |The actor attempts to save NPPO details without specifying NPPO Code. |
| |The System would respond with a message, “Please specify NPPO Code”. Click OK to continue. The actor would be |
| |brought back to Pre Condition. The exception occurs when the actor saves the NPPO Details form without |
| |specifying NPPO Code. |
| |The actor attempts to edit the NPPO details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the NPPO details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the NPPO details when the NPPO Code already exists in the System. |
| |The System would respond with the message, “NPPO Details with the same NPPO Code already exists”. |
|Business Rules |Following Fields are mandatory to define:- |
| |NPPO Name |
| |NPPO Code |
| |NPPO Code should be unique within the System. |
| |NPPO Details, which have already been used in the application, should not be available to select for deletion. |
| |Maximum Permissible length for the field NPPO Name should not exceed 75 characters including alphabets (a-z), |
| |numbers (0-9) and special charters & - / () _, *: |
| |Maximum Permissible length for the field NPPO Code should not exceed 20 characters including alphabets (a-z), |
| |numbers (0-9) and special charters & - / () _, * : |
| |The system should restrict the insertion/typing of non-permissible characters. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
3 MANAGE DEPARTMENT
|UC 3.2.3.3 |Manage Department |
|Version: |00 |
|Context: |This use case is to describe the process to manage department name |
|Priority: |High |
|Frequency: |Medium |
|Primary Actor(s) |AQIS user with the assigned privilege to manage department details in the system. |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to specify department details under the option available in Master Entry -> Manage |
| |Department->Department Details. |
|Normal Flow |The System will prompt the actor to specify following details: |
| |Department Name: The actor would specify name of the Dairy/LH/Fishery department. |
| |Department Code: The actor would specify name of the Dairy/LH/Fishery department Code. |
| |The actor could add multiple department names using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the specified department details. |
| |The actor may click the Edit button to edit the selected department name. |
| |The actor may click the Delete button to delete the selected department name. |
| |The actor may click the View button to view the saved department name. |
| |At any point of time, actor clicks the Clear button to discard the details entered till then or clicks the Close|
| |button to close the Department Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Department name saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All specified information related to the department would be stored in database with status set to save. |
| |c. The saved details would be available for further modification through the Modify button. |
| |d. The saved details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in|
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank Department details form; otherwise, |
| |the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save Department details without specifying Department Name. |
| |The System would respond with a message, “Please specify Department Name”. Click OK to continue. The actor would|
| |be brought back to Pre Condition. The exception occurs when the actor saves the Department Details form without |
| |Department Name. |
| |The actor attempts to edit the Department details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the Department details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the Department details when Department Name already exists in the System. |
| |The System would respond with the message, “Department Details with the same Department Name already exists”. |
|Business Rules |Following Fields are mandatory to define:- |
| |Department Name |
| |Department Code |
| |Department Name should be unique within the System. |
| |Department Name, which has already been used in the application, should not be available to select for deletion.|
| |Maximum Permissible length for the field Department Code should not exceed 75 characters including alphabets |
| |(a-z), numbers (0-9) and special charters & - / () _, *: |
| |The system should restrict the insertion/typing of non-permissible characters. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
4 MANAGE PRODUCTS
|UC 3.2.3.4 |Manage Products |
|Version: |00 |
|Context: |This use case is to describe the process to manage the products for the AQIS and SIP. |
|Priority: |High |
|Frequency: |Medium |
|Primary Actor(s) |AQIS user with the assigned privilege to manage product details in the system. |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to specify product details under the option available in Master Entry -> Manage |
| |Products->Product Details. |
|Normal Flow |The System will prompt the actor to specify following details: |
| |Product Name: The actor would specify name of the Product Name. |
| |Sub-Product Name: The actor would specify name of the Sub-Product Name. |
| |Product Category: The actor would select Product Category from the list displaying three categories i.e. |
| |Dairy/LH/Fishery. The actor could select one option from the list. |
| |Product Code: The actor would specify ITC (HS) Code as product code. |
| |Sub-Product Code: The actor would specify ITC (HS) code as product code. |
| |Product Quantity (In KG/TN/MT): The actor would specify quantity of the product. |
| |Unit: The actor would select unit of the quantity from the list enlisting units specified in Manage Unit use |
| |case. |
| |Product Volume (in Cubic): The actor would specify Volume of the product. |
| |The actor could add multiple products using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the specified product details. |
| |The actor may click the Edit button to edit the selected product details. |
| |The actor may click the Delete button to delete the selected product details. |
| |The actor may click the View button to view the saved product details. |
| |At any point of time, actor clicks the Clear button to discard the details entered till then or clicks the Close|
| |button to close the Product Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Product details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All specified information related to the product would be stored in database with status set to save. |
| |c. The saved details would be available for further modification through the Modify button. |
| |d. The saved details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in|
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank Product details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save Product details without specifying any of the mandatory fields like Product Name, |
| |Product Code, Product Category, Product Quantity etc. |
| |Corresponding to the unspecified field, the System would respond with a message, “Please specify Product Name”. |
| |Or |
| |“Please specify Sub-Product Name”. |
| |Or |
| |“Please specify Product Code”. |
| |Or |
| |“Please specify Sub-Product Code”. |
| |Or |
| |“Please specify Product Category”. |
| |Or |
| |“Please specify Product Quantity”. |
| |The actor attempts to save Product details without specifying Product Name. |
| |The System would respond with a message, “Please specify Product Name”. Click OK to continue. The actor would be|
| |brought back to Pre Condition. The exception occurs when the actor saves the Product Details form without |
| |specifying Product Name. |
| |The actor attempts to edit Product details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete Product details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save Product details when Product Code already exists in the System. |
| |The System would respond with the message, “Product Details with the same Product Code already exists”. |
|Business Rules |Following Fields are mandatory to define:- |
| |Product Name |
| |Sub-Product Name |
| |Product Code |
| |Product Sub-Code |
| |Product Category |
| |Product Quantity |
| |Product Code should be unique within the System. |
| |Product details, which have already been used in the application, should not be available to select for |
| |deletion. |
| |Maximum Permissible length for the field Product Name should not exceed 75 characters including alphabets (a-z),|
| |numbers (0-9) and special charters & - / () _, *: |
| |The system should restrict the insertion/typing of non-permissible characters. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
5 MANAGE SAMPLES
|UC 3.2.3.5 |Manage Samples |
|Version: |00 |
|Context: |This use case is to manage samples taken for testing |
|Priority: |High |
|Frequency: |Medium |
|Primary Actor(s) |AQIS user with the assigned privilege to manage sample details in the system. |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to specify sample details under the option available in Master Entry -> Manage |
| |Samples->Sample Details. |
|Normal Flow |The System will prompt the actor to specify following details: |
| |Sample Code: The actor would code of the sample. |
| |Sample Description: The actor would specify sample description, if any. |
| |Product Category: The actor would select product category of the sample drawn from the list enlisting product |
| |categories specified in product category master. |
| |Product Code: Depending on the selected product category, the actor would select product code from the list |
| |enlisting product codes. |
| |Product Sub-Code: Depending on the selected product, the actor would select Sub-product code from the list |
| |enlisting product codes. |
| |The actor could add multiple samples using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the specified sample details. |
| |The actor may click the Edit button to edit the selected sample details. |
| |The actor may click the Delete button to delete the selected sample details. |
| |The actor may click the View button to view the saved sample details. |
| |At any point of time, actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Sample Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Sample details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All specified information related to the product would be stored in database with status set to save. |
| |c. The saved details would be available for further modification through the Modify button. |
| |d. The saved details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered |
| |in the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the |
| |System would clear the form details and the actor would be presented with a blank Sample details form; |
| |otherwise, the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save Product details without specifying any of the mandatory fields like Sample Code, |
| |Sample Description, Product Category, Product Code etc. |
| |Corresponding to the unspecified field, the System would respond with a message, “Please specify Sample Code”. |
| |Or |
| |“Please specify Sample Description”. |
| |Or |
| |“Please specify Product Code”. |
| |Or |
| |“Please specify Sub-Product Code”. |
| |Or |
| |“Please specify Product Category”. |
| | |
| |The actor attempts to save Sample details without specifying Sample Code. |
| |The System would respond with a message, “Please specify Sample Code”. Click OK to continue. The actor would be|
| |brought back to Pre Condition. The exception occurs when the actor saves Sample Details form without specifying|
| |Sample Code. |
| |The actor attempts to save Sample details without specifying Sample Description. |
| |The System would respond with a message, “Please specify Sample Description”. Click OK to continue. The actor |
| |would be brought back to Pre Condition. The exception occurs when the actor saves Sample Details form without |
| |specifying Sample Description. |
| |The actor attempts to save Sample details without specifying Product Category. |
| |The System would respond with a message, “Please specify Product Category”. Click OK to continue. The actor |
| |would be brought back to Pre Condition. The exception occurs when the actor saves Sample Details form without |
| |specifying Product Category. |
| |The actor attempts to save Sample details without specifying Product Code. |
| |The System would respond with a message, “Please specify Product Code”. Click OK to continue. The actor would |
| |be brought back to Pre Condition. The exception occurs when the actor saves Sample Details form without |
| |specifying Product Code. |
| |The actor attempts to edit Sample details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete Sample details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save Sample details when Sample Code already exists in the System. |
| |The System would respond with the message, “Sample Details with the same Sample Code already exists”. |
|Business Rules |Following Fields are mandatory to define:- |
| |Sample Code |
| |Sample Description |
| |Product Category |
| |Product Code |
| |Sub- Product Code |
| |Sample Code should be unique within the System. |
| |Sample details, which have already been used in the application, should not be available to select for |
| |deletion. |
| |Maximum Permissible length for the field Sample Code should not exceed 15 characters including alphabets (a-z),|
| |numbers (0-9) and special charters & - / () _, *: |
| |Maximum Permissible length for the field Sample Description should not exceed 150 characters including |
| |alphabets (a-z), numbers (0-9) and special charters & - / () _, *: |
| |The system should restrict the insertion/typing of non-permissible characters. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
6 MANAGING AIRPORT NAME
|UC 3.2.3.6 |Manage Airport Name |
|Version: |00 |
|Context: |This use case is for managing Airport Name |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add Airport name details. |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS/SIP application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add airport details under the option available in Master Entry -> Manage airport |
| |detail->airport name Details. |
|Normal Flow |The System will prompt the actor to specify following airport details: |
| |Airport Name and Airport Code: The actor would select name of the airport along with airport code being displayed|
| |in the list available for selection. The displayed list will enlist all the Airport Names along with their codes |
| |for selection. |
| |The actor could add multiple airports name & code being required to deal with AQIS application using “Add More” |
| |button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected airport name & code details. |
| |The actor may click the Edit button to edit the selected airport name & code details. |
| |The actor may click the Delete button to delete the selected airport name & code details. |
| |The actor may click the View button to view the saved airport name & code details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Airport Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Airport Details saved successfully” and the actor would be brought|
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the Airport details would be stored in the database with status set to save. |
| |c. The saved airport details would be available for further modification through the Modify button. |
| |d. The airport details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank airport name details form; otherwise, |
| |the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details|
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save airport name & code details when no airport name & code has been selected from the |
| |list. |
| |The System would respond with a message, “No airport name has been selected. Please select at least one airport |
| |name to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception |
| |occurs when the actor saves the airport name Details without selecting any airport. |
| |The actor attempts to edit the airport name & code details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the airport name & code details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the airport name & code details when the airport name with the same airport Code |
| |already exists in the System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |airport Name and airport Code |
| |System would display a default list of Airport Names and Airport Codes. |
| |Airport name Details, which have already been used in the application, should not be available to select for |
| |deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
7 MANAGE SEAPORT NAME
|UC 3.2.3.7 |Manage Sea Port Name |
|Version: |00 |
|Context: |This use case is for managing Seaport Name |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add sea port details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Sea Port->Sea |
| |port Details. |
|Normal Flow |The System will prompt the actor to specify following country details: |
| |Sea Port Name and Sea Port Code: The actor would select name of the sea port along with sea port code being |
| |displayed in the list available for selection. The displayed list will enlist all the Sea Port Names along with|
| |their codes for selection. |
| |The actor could add multiple sea port being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected sea port details. |
| |The actor may click the Edit button to edit the selected sea port details. |
| |The actor may click the Delete button to delete the selected sea port details. |
| |The actor may click the View button to view the saved sea port details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Sea port Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Sea Port Details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All information related to the sea port details would be stored in the database with status set to save. |
| |c. The saved sea port details would be available for further modification through the Modify button. |
| |d. The sea port details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered |
| |in the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the |
| |System would clear the form details and the actor would be presented with a blank seaport details form; |
| |otherwise, the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save sea port details when no sea port name has been selected from the list. |
| |The System would respond with a message, “No country name has been selected. Please select at least one country|
| |to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception occurs |
| |when the actor saves the Country Details without selecting any country. |
| |The actor attempts to edit the sea port name details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the sea port details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the Sea Port details when the sea port name with the same Sea port Code already |
| |exists in the System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |(a)Sea Port Name and Sea port Code |
| |2. System would display a default list of Sea Port Names and Sea Port Codes. |
| |3. Sea Port Details, which have already been used in the application, should not be available to select for |
| |deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
8 MANAGING TEST DETAILS
|UC 3.2.3.8 |Managing Test Details |
|Version: |00 |
|Context: |This use case is for managing Test Details |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add test details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Test->Test |
| |Details. |
|Normal Flow |The System will prompt the actor to specify following country details: |
| |Test Name and Test Code: The actor would select name of the Test along with Test code being displayed in the |
| |list available for selection. The displayed list will enlist all the Test Names along with their codes for |
| |selection. |
| |The actor could add multiple Test being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected Test details. |
| |The actor may click the Edit button to edit the selected Test details. |
| |The actor may click the Delete button to delete the selected Test details. |
| |The actor may click the View button to view the saved Test details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the|
| |Close button to close the Test Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Test Details saved successfully” and the actor would be brought|
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the test details would be stored in the database with status set to save. |
| |c. The saved test details would be available for further modification through the Modify button. |
| |d. The test details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered |
| |in the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the |
| |System would clear the form details and the actor would be presented with a blank country details form; |
| |otherwise, the actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered |
| |details in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then |
| |the System would discard the entered details and close the form and the actor would be brought back to Pre |
| |Condition; otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save test details when no test has been selected from the list. |
| |The System would respond with a message, “No test name has been selected. Please select at least one test to |
| |save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception occurs |
| |when the actor saves the Country Details without selecting any test. |
| |The actor attempts to edit the test details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the test details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the test details when the test name with the same test Code already exists in the |
| |System. |
| |The System would respond with the message, “Test Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Test Name and Test Code |
| |System would display a default list of Test Names and Test Codes. |
| |Test Details, which have already been used in the application, should not be available to select for deletion.|
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
9 MANAGE COLOUR DETAILS
|UC 3.2.3.9 |Manage Colour details |
|Version: |00 |
|Context: |This use case is for managing Colour Details |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add colour details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Colour->Colour |
| |Details. |
|Normal Flow |The System will prompt the actor to specify following colour details: |
| |Colour Name and Colour Code: The actor would select name of the colour along with colour code being displayed in |
| |the list available for selection. The displayed list will enlist all the colour Names along with their codes for |
| |selection. |
| |The actor could add multiple colours being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected colour details. |
| |The actor may click the Edit button to edit the selected colour details. |
| |The actor may click the Delete button to delete the selected colour details. |
| |The actor may click the View button to view the saved colour details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Colour Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Colour Details saved successfully” and the actor would be brought |
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the colour details would be stored in the database with status set to save. |
| |c. The saved colour details would be available for further modification through the Modify button. |
| |d. The colour details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank country details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details |
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save colour details when no colour has been selected from the list. |
| |The System would respond with a message, “No colour name has been selected. Please select at least one colour to |
| |save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception occurs when |
| |the actor saves the Colour Details without selecting any colour. |
| |The actor attempts to edit the colour details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the colour details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the colour details when the colour name with the same Country Code already exists in |
| |the System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Colour Name and Colour Code |
| |System would display a default list of Colour Names and Colour Codes. |
| |Colour Details, which have already been used in the application, should not be available to select for deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
10 MANAGING ANIMAL CATEGORY
|UC 3.2.3.10 |Managing Animal Category |
|Version: |00 |
|Context: |This use case is for managing Animal Category |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add Animal category details |
|Secondary Actor(s) |None |
|Pre Conditions |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Animal |
| |Category->Animal Details. |
|Normal Flow |The System will prompt the actor to specify following animal details: |
| |Animal Name and Animal Code: The actor would select name of the animal along with animal code being displayed in |
| |the list available for selection. The displayed list will enlist all the Animal Names along with their codes for |
| |selection. |
| |The actor could add multiple animals being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected animal details |
| |The actor may click the Edit button to edit the selected animal details. |
| |The actor may click the Delete button to delete the selected animal details. |
| |The actor may click the View button to view the saved animal details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the Animal Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Animal Details saved successfully” and the actor would be brought |
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the animal details would be stored in the database with status set to save. |
| |c. The saved animal details would be available for further modification through the Modify button. |
| |d. The animal details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank animal details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details|
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save animal details when no animal detail has been selected from the list. |
| |The System would respond with a message, “No Animal name has been selected. Please select at least one animal |
| |name to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception |
| |occurs when the actor saves the Animal Details without selecting any animal. |
| |The actor attempts to edit the animal details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the animal details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the animal details when the animal name with the same animal Code already exists in |
| |the System. |
| |The System would respond with the message, “Animal Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Animal Name and Animal Code |
| |System would display a default list of Animal Names and Animal Codes. |
| |Animal Details, which have already been used in the application, should not be available to select for deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
11 MANAGING ANIMAL BREED CATEGORY
|UC 3.2.3..11 |Managing Animal Breed Category |
|Version: |00 |
|Context: |This use case is for managing Animal Breed Category |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |AQIS user with the assigned privilege to add Breed details |
|Secondary Actor(s) |None |
|Pre Conditions | |
| |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add country details under the option available in Master Entry -> Manage Breed |
| |category->Breed Details. |
|Normal Flow |The System will prompt the actor to specify following breed details: |
| |Breed Name and Breed Code: The actor would select name of the Breed along with breed code being displayed in the |
| |list available for selection. The displayed list will enlist all the Breed Names along with their codes for |
| |selection. |
| |The actor could add multiple Breeds being required to deal with AQIS application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected breed details. |
| |The actor may click the Edit button to edit the selected breed details. |
| |The actor may click the Delete button to delete the selected breed details. |
| |The actor may click the View button to view the saved breed details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the breed Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Breeds Details saved successfully” and the actor would be brought |
| |back to Step 1 of the Normal Flow. |
| |b. All information related to the breed details would be stored in the database with status set to save. |
| |c. The saved breed details would be available for further modification through the Modify button. |
| |d. The breed details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank breed details form; otherwise, the |
| |actor would be brought back to where she was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details|
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where she was before clicking the Close button. |
|Exceptions |The actor attempts to save breed details when no breed has been selected from the list. |
| |The System would respond with a message, “No breed name has been selected. Please select at least one breed name |
| |& code to save record”. Click OK to continue. The actor would be brought back to Pre Condition. The exception |
| |occurs when the actor saves the breed Details without selecting any breed. |
| |The actor attempts to edit the breed details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the breed details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the breed details when the breed name with the same breed Code already exists in the |
| |System. |
| |The System would respond with the message, “Country Details already exists. Please select another country”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Breed Name and Breed Code |
| |System would display a default list of Breed Names and Breed Codes. |
| |Breed Details, which have already been used in the application, should not be available to select for deletion. |
|Relationships |Extends |
| |AQIS Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
12 MANAGING SIP CONDITION (PRODUCT WISE)
|UC 3.2.3..12 |Managing SIP Condition (Product Wise) |
|Version: |00 |
|Context: |This use case is to describe the process to manage the condition to issue SIP. |
|Priority: |High |
|Frequency: |Rare |
|Primary Actor(s) |SIP user with the assigned privilege to add condition. |
|Secondary Actor(s) |None |
|Pre Conditions | |
| |Actor shall log into AQIS application over the web using UC 3.1.2.1 |
|Triggers |The actor chooses to add condition details under the option available in Master Entry -> Manage condition product|
| |wise category->Condition Details. |
|Normal Flow |The System will prompt the actor to specify following Condition details: |
| |Condition Detail and Condition Code (HS code): The actor would select detail of the Condition along with |
| |Condition code being displayed in the list available for selection. The displayed list will enlist all the |
| |Condition Detail along with their codes for selection. |
| |The actor could add multiple Condition being required to deal with SIP application using “Add More” button. |
| |After specifying all the mandatory details, the actor may choose one of the following options: |
| |Save |
| |Edit |
| |Delete |
| |View |
| |The actor may click the Save button to save the selected condition details. |
| |The actor may click the Edit button to edit the selected condition details. |
| |The actor may click the Delete button to delete the selected condition details. |
| |The actor may click the View button to view the saved condition details. |
| |At any point of time, the actor clicks the Clear button to discard the details entered till then or clicks the |
| |Close button to close the condition Details form. |
|Alternative Flows |None |
|Post Conditions |1.If the actor clicked the Save button, & if all the mandatory fields have been entered, then |
| |a. The System would respond with the message, “Condition Details saved successfully” and the actor would be |
| |brought back to Step 1 of the Normal Flow. |
| |b. All information related to the condition details would be stored in the database with status set to save. |
| |c. The saved condition details would be available for further modification through the Modify button. |
| |d. The condition details would be available for deletion through the Delete button. |
| |2. If the actor clicks the Clear button, then the System would respond with the message, “All details entered in |
| |the form would be lost. Do you wish to clear the form?” If the actor responds in affirmative, then the System |
| |would clear the form details and the actor would be presented with a blank condition details form; otherwise, the|
| |actor would be brought back to where actor was before clicking the Clear button. |
| |3. If the actor clicks the Close button, then the System would respond with the message, “All the entered details|
| |in the form would be lost. Do you wish to close the form?” If the actor responds in affirmative, then the System |
| |would discard the entered details and close the form and the actor would be brought back to Pre Condition; |
| |otherwise, the actor would be brought back to where actor was before clicking the Close button. |
|Exceptions |The actor attempts to save condition details when no condition has been selected from the list. |
| |The System would respond with a message, “No condition name has been selected. Please select at least one |
| |condition name & code to save record”. Click OK to continue. The actor would be brought back to Pre Condition. |
| |The exception occurs when the actor saves the condition Details without selecting any condition. |
| |The actor attempts to edit the condition details without selecting any record. |
| |The System would respond with the message, “Please select record to modify it”. |
| |The actor attempts to delete the condition details without selecting any record. |
| |The System would respond with the message, “Please select record to delete it”. |
| |The actor attempts to save the condition details when the condition detail name with the same Code already exists|
| |in the System. |
| |The System would respond with the message, “Condition Details already exists. Please select another condition”. |
|Business Rules |Following Fields are mandatory to define:- |
| |a. Condition Detail and Condition Code |
| |System would display a default list of Condition Detail and Condition Codes. |
|Relationships |Extends |
| |SIP Menu Page |
| |Is Extended By |
| |None |
| |Uses |
| |Login |
|Special Requirements |None |
|Assumptions |None |
3 PERFORMANCE REQUIREMENTS
1 SCALABILITY REQUIREMENTS
Scalability refers to the how the proposed system will be scaled up with need and time. In the current scenario, there will be average 100,000 application users of the system at central, state and village level. At any point of time, no more than 25,000 simultaneous application users would be expected in the system. At any point of time, the software should support a peak load of 25000 concurrent users.
2 RESPONSE TIME
The response time should be as follows: Response time will be 5-10 seconds for any request from the client depending on the network traffic and bandwidth between client & server system. Any number of simultaneous users will be able to use the system. 5-10 second: For user operation on data (for e.g. sorting of data in a column) or (5 to 50 records per page up to max of 100,000 records) 10-20 second: For user awaiting response from the system upon executing a transaction (for e.g. a query/update). 1 minute – Unacceptable response time. The SMS alerts to reach the users mobile in an acceptable time limit from the SMS gateway/applications. Ideally it is within 120 Seconds from information trigger, from central server to national jurisdiction.
4 SOFTWARE SYSTEM ATTRIBUTES
1 USABILITY
The Screens should be designed for ease of use by non technical users who do not have any computer knowledge. The GUI design shall be intuitive and task-based without any superfluous design. The design should adopt the following principles:
• Use relative font size so that a user can easily change overall font size from the browser interface. • Text equivalents should be given for all graphics. • Application should function even if Java script, CSS and Frames are turned off.
2 INTERNAL / INTRANET USERS
In this category, the users belong to AQIS Department employees, Administrators and officials. All these users shall be provided with a user-id and password on the Directory services (AD) server. These users connect through LAN (10/100 Mbps) and have to pass through the policies set on the Internal Firewall, get authenticated through the AD server and only authorized users get connected to the Web server/Application server. Through the application, access to the Database server is provided. No user can directly access the Database server.
3 INTERNET USERS
In this category, the users are Importer & Exporter, Citizens etc. These users are “Anonymous” users and they connect to the application through Internet. These users have to connect over the internet through the Router and pass through the policies set on it as well as on the External Firewall. Once they pass through the External Firewall, they land on the Portal server; login as “anonymous” and pass through the policies set on the AD server, and then get connected to either the Web server or Application server as per the requested service. The application connects to the Database server for all data storage/retrieval activities.
4 RELIABILITY
It is expected that there shall not be any bug and the system shall be tested on end cases to offer user a quality and reliable package. It is made reliable by providing the list of values for some of the mandatory parameters to minimize the errors in data entry that will provide consistent results from the system. Integrity of data will also be maintained while saving and updating the details.
5 AVAILABILITY
AQIS application shall be up and running and must be available 24x7 and any one should be able to connect to it from anywhere. It should trap all errors and prevent users from accessing unauthorized areas of the application. In case of application or a hardware failure, the system should re-initiate immediately. In case of a possible hardware failure or corruption of database the system administrator should immediately restore the backup.
6 SECURITY
The system should have protection against
• Unauthorized creation/modification of data - through user name and password authentication as defined for relevant user groups. • Unauthorized viewing of data - through user name and password authentication as defined for relevant user groups. • The software should adhere to security guidelines, standards and policies prescribed by NIC’s Security Division and should be audited & certified for compliance to these standards by Security Division before it is hosted in Production Environment. • The software should be protected against any unauthorized access to the software. • System Administrator should moderate for the audio and video contents those are uploaded into the system to check any objectionable information is not uploaded. • Configuration is secured with firewalls in place. Secure communication over SSL. • Zero Data Loss: Data base server with clustering and back up with stand by server in case of failure will ensure No data loss. • Authentication/Authorization: Assuming that application will have Single Sign On login feature; where user once logged in, will not have to login again to use other integrated application. • The users will have different functional options
7 MAINTAINABILITY
In order to ensure maintainability of the application, the following should be ensured:
• The application will be designed and developed using Open Source Tools and Technologies. Software Code must be modular and well documented • All the artifacts related to the software such as code, design document, User Manual etc. should be well documented and self-explanatory for any programmer to understand. Detailed documentation shall be available at each stage for easy comprehensions of the application system. • All documents shall be prepared as per the defined documentation standards. The system administrator shall take regular back up of the database
8 PORTABILITY
The software will be hosted/installed in Linux RHEL 5 and above OS based server and will be accessed through Windows (XP) based machines using I.E 6.0 or above OR Mozilla 3.5.11 or above browsers.
9 LANGUAGE SUPPORT
• AQIS/SIP will support the entry and display of:
o All Indian scripts such as Hindi, English
o The application will store data using Unicode representation.
• Unicode font file & keyboard manager/driver should be available.
10 INTEROPERABILITY
The software will interoperate with other software applications which are being developed under National e-Governance Program, Mission Mode Project, in particular Central Agriculture Portal and with custom for information exchange. The following are the likely points of information exchange/reconciliation:
• BOE/BOS issued by custom
• AQC issued by AQCS department.
5 LOGICAL DATABASE REQUIREMENTS
1 DATA STORE: USER_ MASTER
|Data Element |Description |O/M |Remarks |
|User ID |Numeric |M |12,PK |
|I/E Code |Numeric |M |12 |
|NPPO Code |Numeric |M |12,FK |
|NPPO Country Name |Character |M |Abcd |
|User Category |Character |M |Abcd |
|Internal |Character |M |Abcd |
|External |Character |M |Abcd |
|User Name |Character |M |Abcd |
|Designation |Character |M |Abcd |
|Employee Code |Numeric |M |12 ,FK |
|User DOB |Numeric |M |12 |
|Office Address |Alpha-Numeric |O |12 abcd |
|Residential Address |Alpha-Numeric |M |12 abcd |
|E-mail ID |Alpha-Numeric |M |abcd@nic.com |
|Alternate E-mail ID |Alpha-Numeric |O |abcd@nic.com |
|Mobile Number |Numeric |M |12 |
|Phone Number |Numeric |M |12 |
|Fax Number |Numeric |M |12 |
|State |Character |M |abcd |
|City |Character |M |abcd |
|District |Character |M |abcd |
|Pin Code Number |Numeric |M |6 |
|Allow SMS |Boolean |M |True/False |
|Select Question Type |Character |M |abcd |
|Select Answer |Character |M |abcd |
|Password |Alpha-Numeric |M |12 abcd |
|Confirm Password |Alpha-Numeric |M |12 abcd |
2 DATA STORE: ROLE MANAGEMENT_ MASTER
|Data Element |Description |O/M |Remarks |
|Role ID |Numeric |M |For Departmental User Only, PK |
|Role Name |Character |M |For Departmental User Only, FK |
|Role Description |Character |M |For Departmental User Only |
3 DATA STORE: AQIS (IMPORT/EXPORT) CERTIFICATION FOR LSP_MASTER
AQCS (Import/Export) Certification for LSP Form (Annex-24)
|Data Element |Description |O/M |Remarks |
|Product Code |Numeric |M |I/E select from the list of the product like apple, |
| | | |orange, PK |
|Product Name |Character |M |Abcd |
|Product Category |Numeric |M |12 |
|Applied To |Character |M |Abcd |
|Exporter Name |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Mobile No. |Numeric |M |12 |
|Telephone No. |Numeric |M |12 |
|Fax No. |Numeric |M |12 |
|SIP Number/DGFT License Number |Alphanumeric |M |12 Abcd |
|SIP Validity |Date |M |DD/MM/YYYY |
|Name Of LSP |Character |M |Abcd |
|LSP Quantity |Numeric |M |Abcd |
|Purpose of Import/Export |Character |M |Abcd |
|Custom Seal No |Numeric |M |12 |
|Custom Date |Date |M |DD/MM/YYYY |
|Date Of Import/Export |Date |M |DD/MM/YYYY |
|Shipping/Airway Bill No |Alphanumeric |M |12 Abcd |
|Shipping/Airway Bill Date |Date |M |DD/MM/YYYY |
|Health Certificate No |Numeric |M |12 |
|Health Certificate Date |Date |M |DD/MM/YYYY |
|Country of origin |Character |M |Abcd |
|Number of Packages |Alphanumeric |O |12 Abcd |
|Container No |Alphanumeric |O |12 Abcd |
|Post of loading |Character |M |Abcd |
|Post of unloading |Character |M |Abcd |
|Date/Means of Conveyance |Character |M |Abcd |
|Plant registration number |Alphanumeric |M |12 Abcd |
|Invoice Number |Alphanumeric |M |12 Abcd |
|Invoice Date |Date | |DD/MM/YYYY |
|Lab Report No |Alphanumeric |M |12 Abcd |
|Lab Report Name |Date | |DD/MM/YYYY |
|Declaration |Character |M |Abcd |
|Verification By The Quarantine Officer (Official Purpose) |
|Checking The Documents Attached |Boolean | |Yes/No |
|SIP If Any |Boolean | |Yes/No |
|Importer/Exporter License If Any |Boolean | |Yes/No |
|Health Certificate |Boolean | |Yes/No |
|Fumigation Certificate/Test Report|Boolean | |Yes/No |
|Invoice |Boolean | |Yes/No |
|Airway/Shipping Bill No |Boolean | |Yes/No |
|Bill Of Entry No |Boolean | |Yes/No |
|Plant registration copy |Boolean | |Yes/No |
|Laboratory Letter/Report |Boolean | |Yes/No |
|Importer/Exporter Declaration |Boolean | |Yes/No |
|Others If any |Boolean | |Yes/No |
|Charges If Any |Boolean | |Yes/No |
|Decision |
|Fit For Clearance |Boolean | |Yes/No |
|Unfit For Clearance On Account |Character | |Abcd |
|Of(Detail Overleaf) | | | |
|Temporarily Unclear On Account Of |Character | |Abcd |
|(Detail Overleaf) | | | |
4 DATA STORE: AQIS (IMPORT/EXPORT) CERTIFICATION FOR LS/PET ANIMAL _MASTER
AQIS (Import/Export) Certification for LS/Pet Animal Form (Annex-23) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|Animal Id |Numeric |M |12, PK |
|Animal Name |Character |M |Abcd |
|Sex Of Animal |Character |M |Abcd |
|Animal Breed |Character |M |Abcd, FK |
|Expected Date Of Import/Export |Date |M |DD/MM/YYYY |
|Exporter Name |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Mobile No |Numeric |M |12 |
|Telephone NO |Numeric |M |12 |
|Fax No |Numeric |M |12 |
|Mode |Character |M |Abcd |
|SIP Number/DGFT License Number |Alphanumeric |M |12 Abcd |
|SIP/DGFT License Validity |Date |M |DD/MM/YYYY |
|Purpose of Import/Export |Character |M |Abcd |
|Date Of Import/Export |Date |M |DD/MM/YYYY |
|Shipping/Airway Bill No |Alphanumeric |M |12 Abcd |
|Shipping/Airway Bill Date |Date |M |DD/MM/YYYY |
|Health Certificate No |Numeric |M |12 |
|Health Certificate Date |Date |M |DD/MM/YYYY |
|Country of origin |Character |M |Abcd |
|Color |Character |M |Abcd |
|Number Of Livestock |Numeric |M |12 |
|PP NO/Microchip No |Alphanumeric |O |12 Abcd |
|Rabies Vaccination |Character |M |Abcd |
|Rabies Vaccination Date |Date |M |DD/MM/YYYY |
|Batch No |Alphanumeric |M |12 Abcd |
|Country Of Embarkation |Character |M |Abcd |
|Place Of Embarkation |Character |M |Abcd |
|Country Of Disembarkation |Character |M |Abcd |
|Place Of Disembarkation |Character |M |Abcd |
|Number of Packages |Alphanumeric |O |12 Abcd |
|Date/Means of Conveyance |Character |M |Abcd |
|Invoice Number |Alphanumeric |M |12 Abcd |
|Invoice Date |Date |M |DD/MM/YYYY |
|Lab Report No |Alphanumeric |M |12 Abcd |
|Lab Report Name |Date |M |DD/MM/YYYY |
|Declaration |Character |M |Abcd |
|Verification By The Quarantine Officer (Official Purpose) |
|Checking The Documents Attached |Boolean | |Yes/No |
|SIP/DGFT License If Any |Boolean | |Yes/No |
|Importer/Exporter Declaration |Boolean | |Yes/No |
|Health Certificate |Boolean | |Yes/No |
|Invoice No |Boolean | |Yes/No |
|Bill Of Entry No |Boolean | |Yes/No |
|Laboratory Letter/Report |Boolean | |Yes/No |
|Others If any |Boolean | |Yes/No |
|Ticket No If Any |Numeric | |12 |
|Charges If Any |Boolean | |Yes/No |
|Decision |
|Fit For Clearance |Boolean | |Yes/No |
|Unfit For Clearance On Account Of(Detail |Character | |Abcd |
|Overleaf) | | | |
|Temporarily Unclear On Account Of (Detail |Character | |Abcd |
|Overleaf) | | | |
5 DATA STORE: SANITARY IMPORT PERMIT_MASTER
FORM A(Annex-31)
|Data Element |Description |O/M |Remarks |
|Name And Exact Description Of Livestock(s) |Alphanumeric |M |12 Abcd |
|Product To Be Imported | | | |
|I/E Code |Alphanumeric |M |12 Abcd |
|Name Of Consigner |Character |M |Abcd |
|Address Of Consigner |Alphanumeric |M |12 Abcd |
|Address Of importer |Alphanumeric |M |12 Abcd |
|Name Of Importer |Character |M |Abcd |
|Country Of Produced |Character |M |Abcd |
|Locality Of Produced |Character |M |Abcd |
|ITC(HS) code |Numeric |M |12, FK |
|Total weight/volume |Alphanumeric |M |12 Abcd |
|Country & locality in which Livestock Product |Alphanumeric |M |12 Abcd |
|produces | | | |
|Foreign port of shipment |Alphanumeric |M |12 Abcd |
|Name of airport/sea port/land custom station |Character |M |Abcd |
|Approximate date of arrival of the consignment |Alphanumeric |O | |
|in India | | | |
|Name of point of entry in India |Character |M |Abcd |
|Declaration |Character |M |Abcd |
|Authorize Agent No |Alphanumeric |M |12 Abcd |
|Authorize Agent Name |Alphanumeric |M |12 Abcd |
|Authorize Agent Address |Alphanumeric |M |12 Abcd |
|Place |Character |M |Abcd |
|Date |Date |M |DD/MM/YYYY |
|Reference No |Alphanumeric |M |System Generate |
|SIP NO Issue |Alphanumeric |M |For Departmental User Only, PK |
FORM B(Annex-32)
|Data Element |Description |O/M |Remarks |
|Name And Exact Description Of Livestock(s) |Alphanumeric |M |12 Abcd, FK |
|Product with Indian Trade Classification | | | |
|(Harmonized System)-ITC(HS) code | | | |
|I/E Code |Alphanumeric |M |12 Abcd |
|Name Of Consigner |Character | |Abcd |
|Address Of Consigner |Alphanumeric |M |12 Abcd |
|Address Of importer |Alphanumeric |M |12 Abcd |
|Name Of Importer |Character | |Abcd |
|Country Of Produced |Character | |Abcd |
|Locality Of Produced |Character | |Abcd |
|Total weight/volume |Alphanumeric |M |12 Abcd |
|Country & locality in which Livestock Product |Alphanumeric |M |12 Abcd |
|produces | | | |
|Foreign port of shipment |Alphanumeric |M |12 Abcd |
|Name of airport/sea port/land custom station |Character | |Abcd |
|Catalogue Of Livestock Products Producer |Upload | |Attached |
|Establishing Identity Of the Livestock | | | |
|Products/Material To be Imported | | | |
|Details Of Livestock From Whom it Is Produced |Character | |Abcd |
|Name of point of entry in India |Character | |Abcd |
|No Of Packages |Alphanumeric |M |12 Abcd |
|Declaration |Character | |Abcd |
|Authorize Agent No |Alphanumeric |M |12 Abcd |
|Authorize Agent Name |Alphanumeric |M |12 Abcd |
|Authorize Agent Address |Alphanumeric |M |12 Abcd |
|Place |Character |M |Abcd |
|Date |Date |M |DD/MM/YYYY |
|Reference No |Alphanumeric | |System Generate |
|SIP NO Issue |Alphanumeric | |For Departmental User Only, PK |
6 DATA STORE: VETERINARY HEALTH/ZOO SANITARY CERTIFICATE
(LIVESTOCK)(EXPORT) _ MASTER
Veterinary Health/Zoo Sanitary Certificate for Livestock Product (Export) (Annex-1) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Declared Port Of Loading |Character |M |Abcd |
|Product ID |Character |M |Abcd, FK |
|Product Name |Character |M |Abcd |
|Gross Weight |Numeric |M |12 |
|No. of Packages |Numeric |M |12 |
|Exporting Country Name |Character |M |Abcd |
|Importing Country Name |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Exporter Name |Character |M |Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Mobile No |Numeric |M |12 |
|Telephone NO |Numeric |M |12 |
|Health Attestation |Alphanumeric |M |12 Abcd |
|AQC Health Certificate No. |Alphanumeric |M |PK |
7 DATA STORE: PROVISIONAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK(IMPORT_ MASTER
Provisional Quarantine Clearance Certificate for Livestock (Import) (Annex-2) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Country of Origin |Character |M |Abcd |
|Tag No. |Numeric |O |12 |
|Name of Livestock |Character |M |Abcd |
|Breed Code |Character |M |Abcd, FK |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
|Date of Import |Date |M |DD/MM/YYYY |
|Bill of Entry No. |Alpha-Numeric |M |12 Abcd |
|Flight No. |Alpha-Numeric |O |12 Abcd |
|Provisional AQC No. |Alpha-Numeric |M |PK |
8 DATA STORE: FINAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK PRODUCT(IMPORT) _ MASTER
Final Quarantine Clearance Certificate for Livestock Product (Import) (Annex-5) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|SIP No. |Alpha-Numeric |M |12 Abcd, FK |
|Validity |Date |M |DD/MM/YYYY |
|Country of Origin |Character |M |Abcd |
|Livestock Product Name |Character |M |Abcd |
|No. of Packages |Numeric |M |12 |
|Net Weight |Numeric |M |12 |
|Invoice No. |Character |M |Abcd |
|Invoice Date |Character |M |Abcd |
|Date of Import |Date |M |DD/MM/YYYY |
|Bill of Entry No. |Alpha-Numeric |M |12 Abcd |
|Airway Bill No. |Alpha-Numeric |M |12 Abcd |
|Importer Name |Character |M |Abcd |
|Exporter Name |Character |M |Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Port Of Embarkation |Character |M |Abcd |
|Final AQC No. |Alpha-Numeric |M |PK |
9 DATA STORE: FINAL QUARANTINE CLEARANCE CERTIFICATE FOR LIVESTOCK (IMPORT) _ MASTER
Final Quarantine Clearance Certificate for Livestock (Import) (Annex-30) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Country of Origin |Character |M |Abcd |
|Tag No. |Numeric |O |12 |
|Name of Livestock |Character |M |Abcd |
|Breed Code |Character |M |Abcd, FK |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
|Date of Import |Date |M |DD/MM/YYYY |
|Importer Name |Character |M |Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Certificate No. |Alpha-Numeric | |For Departmental User Only, PK |
10 DATA STORE: CERTIFICATE OF HEALTH FOR EXPORT OF PET ANIMAL _ MASTER
Certificate of Health for Export of Pet Animal (Annex-28) The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Exporting Country Name |Character |M |Abcd |
|Animal Category |Character |M |Abcd |
|Tag No. |Numeric |O |12 |
|Name of Livestock |Character |M |Abcd |
|Breed Code |Character |M |Abcd, FK |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
|Date of Travel |Date |M |DD/MM/YYYY |
|Exporter Name |Character |M |Abcd |
|Exporter Address |Alpha-Numeric |M |12 Abcd |
|Flight No. |Alpha-Numeric |M |12 Abcd |
|Vaccination Name |Character |M |Abcd |
|Date of Vaccination |Date |M |DD/MM/YYYY |
|Validity of Vaccination |Date |M |DD/MM/YYYY |
|Serial No./Batch of Vaccine |Alpha-Numeric |M |12 Abcd |
|Certificate No. |Alpha-Numeric | |For Departmental User Only, PK |
11 DATA STORE: NOC FOR IMPORT OF PET ANIMAL _ MASTER
NOC for Import of Pet Animal (Annex-26)
The system shall provide for the following data elements
|Data Element |Description |O/M |Remarks |
|File No. |Alpha-Numeric |M |12 Abcd |
|I/E Code |Alpha-Numeric |M |PK |
|Date |Date |M |DD/MM/YYYY |
|Exporting Country Name |Character |M |Abcd |
|Importing Country Name |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Animal Category |Character |M |Abcd |
|Tag No./Micro Chip No. |Numeric |O |12 |
|Name of Animal |Character |M |Abcd |
|Breed |Character |M |Abcd |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
12 DATA STORE: DEPORTATION/DESTRUCTION OF CONSIGNMENT_ MASTER
Annex-35
|DATA ELEMENT |DESCRIPTION |O/M |REMARKS |
|File No. |Alpha-Numeric |M |12 Abcd |
|Date |Date |M |DD/MM/YYYY |
|Country of Origin |Character |M |Abcd |
|Importer Name |Character |M |Abcd |
|Importer Address |Alpha-Numeric |M |12 Abcd |
|Animal Category |Character |M |Abcd |
|Tag No./Micro Chip No. |Numeric |O |12 |
|Name of Animal |Character |M |Abcd |
|Breed Code |Character |M |Abcd, FK |
|Sex |Character |M |Abcd |
|Age |Character |M |Abcd |
|Colour |Character |M |Abcd |
|Livestock Product Name |Character |M |Abcd |
|No. of Packages |Numeric |M |12 |
|Net Weight |Numeric |M |12 |
|Gross Weight |Numeric |M |12 |
|Bill of Entry No. |Alpha-Numeric |M |12 Abcd |
13 DATA STORE: PINCODE_ MASTER
|Data Element |Description |O/M |Remarks |
|Pin code |Numeric |M |6 |
|City |Character |M |Abcd |
|Address |Alpha-Numeric |M |12 Abcd |
|District |Character |M |Abcd |
14 DATA STORE: GRIEVANCE_ MASTER
|Data Element |Description |O/M |Remarks |
|Grievance Id |Alpha-Numeric |M |12, PK |
|Grievance type |Character |M |Abcd |
15 DATA STORE: GRIEVANCE MANAGEMENT_ MASTER
|Data Element |Description |O/M |Remarks |
|Id |Alpha-Numeric |M |12 abcd, PK |
|Name |Character |M |Abcd |
|Mobile No |Numeric |M |12 |
|Email_id |Character |M |abcd |
|State_id |Numeric |M |12 |
|District_id |Numeric |M |12 |
|Grievance_type |Numeric |M |12 |
|Grievance_details |Character |M |abcd |
|Submission_date |Date |M |DD/MM/YYYY |
16 DATA STORE: SMS _MASTER
|Data Element |Description |O/M |Remarks |
|SMS Id |integer |M |12 abcd, PK |
|SMS Details |Character |M |Abcd |
|User_id |integer |M |12 |
|Date |Date |M |DD/MM/YYYY |
|SMS Details |Character |M |Abcd |
|SMS Time |Time |M |HH/MM/SS |
17 DATA STORE: COUNTRY_MASTER
|Data Element |Description |O/M |Remarks |
|Country Name |Character |M | |
|Country Code |Numeric |M |PK |
18 DATA STORE: NPPO_MASTER
|Data Element |Description |O/M |Remarks |
|NPPO Name |Character |M | |
|NPPO Code |Numeric |M |PK |
| | | | |
19 DATA STORE: SEAPORT_MASTER
|Data Element |Description |O/M |Remarks |
|Port Name |Character |M |Abcd |
|Port Code |Numeric |M |12, PK |
|Country Code |Numeric |M |12, FK |
|City Code |Numeric |M |12 |
|District Code |Numeric |M |12 |
20 DATA STORE: AIRPORT_MASTER
|Data Element |Description |O/M |Remarks |
|AirPort Name |Character |M |Abcd |
|AirPort Code |Numeric |M |12, PK |
|Country Code |Numeric |M |12 |
|City Code |Numeric |M |12 |
|District Code |Numeric |M |12 |
21 DATA STORE: PRE-DEFINED DISEASE FOR TESTING & SAMPLE _MASTER
|Data Element |Description |O/M |Remarks |
|Disease ID |Numeric |M |12, PK |
|Disease Name |Character |M |Abcd |
|LSP/LS name |Character |M |Abcd |
|Lab ID |Numeric |M |12 |
|Lab Name |Character |M | Abcd |
|Lab Address |Alpha-Numeric |M |12 Abcd |
|Sample |
|Sample No. |Numeric |M |12, PK |
|Product Code(ITC-HS) |Numeric |M |12, FK |
|Product Name |Character |M |Abcd |
|Reference No. |Alpha-Numeric |M |12 Abcd |
|Date of Sample |Date |M |DD/MM/YYYY |
|No. of Sample |Numeric |M |12 |
|Result |Boolean |M |Yes/No |
22 DATA STORE: DEPARTMENT_MASTER
|Data Element |Description |O/M |Remarks |
|Department Name |Character |M |Abcd |
|Department Code |Numeric |M |12, PK |
23 DATA STORE: ANIMAL CATEGORY_MASTER
|Data Element |Description |O/M |Remarks |
|Category Name |Character |M |Abcd |
|Category Code |Numeric |M |12, PK |
24 DATA STORE: DESIGNATION_MASTER
|Data Element |Description |O/M |Remarks |
|Designation Name |Character |M |Abcd |
25 DATA STORE: BREED_MASTER
|Data Element |Description |O/M |Remarks |
|Breed Name |Character |M |Abcd |
|Breed Code |Numeric |M |12, PK |
|Breed Colour |Character |M |Abcd |
|Breed Quantity |Numeric |M |12 |
Note: For State, City & District _master software is being developed under National e Panchayat Mission Mode Project at Panchayati Raj Division by the name of “Local Government Directory”.
6 OTHER REQUIREMENTS
This section lists the other non-functional requirement related to installation/un-installation /upgrades of AQIS application. A non-technical person shall be able to setup and run the AQCS application.
1 BACKUP
An automated and scheduled data backup mechanism shall be provided which will write a backup of the data to one of the system’s disks. From there, the backup date can be manually written to CD or tape if required. The data backup should cover data held in a database and any data held outside of the database such as files uploaded through the software.
2 RECOVERY
A simple manual data recovery procedure will be provided to recover the data from a data backup when required by the system administrator. The data backup will be used to recover the data in the event of a disk corruption or database corruption.
3 DATA RETENTION
The latest data on the Server will be kept for the seasons of the two calendar years. The data for more than five years is to be backed up on to a CD and remove from the Server.
4 CUSTOMER/USER TRAINING
It is proposed that NIC will conduct a training program for 5 days at NIC, HQ to fully train selected AQIS Administrator on the installation, use, backup, recovery, plan creation/updation and problem diagnosis. These Administrators will become “AQCS Master Trainers (also known as Trainers of Trainers) who will then train AQIS users in the use of the software. (Consultation with NIC require on this point)
5 AUDIT TRAIL
The Software shall offer a comprehensive report on the user actions (changes made with time stamp) through audit trail and will be maintained in log server in identified government domain.
ANNEXURE
1 ANNEXURE (1 to 39) IN ONE FOLDER
2 ANNEXURE 40: ADDRESSES OF PLANT / ANIMAL QUARANTINE OFFICES
3 ANNEXURE 41: MESSAGE STRUCTURE OF CUSTOM INTEGRATION FOR PQIS
-----------------------
CONTENT MANAGEMENT
References: Animal Quarantine Certification Service The purpose of the Animal Quarantine and certification (AQC) is to prevent the ingress of livestock and poultry exotic to India as per provisions of livestock importation Act, 1898.
You May Also Find These Documents Helpful
-
P2.1 Analysing the impact including the risks of introducing the system of e- commerce system to a new Hotel (Zodiac Lake Hotel, London)…
- 773 Words
- 4 Pages
Good Essays -
India has banned the import of animal tested cosmetics the ban comes in the form of Rule 135-B that states, "Prohibition of import of cosmetics tested on animals. - No cosmetic that has been tested on animals after the commencement of Drugs and Cosmetics (Fifth Amendment) Rules, 2014 shall be imported into the country"(India). I don 't believe that people would want to be used for testing new products to see what type of allergies or adverse effects these new products could cause, nor would they want their family members to be tested against their will. So why is it okay for animals to be tested on? I feel animals should have rights too and do not deserve to be treated bad. One commercial I cannot watch is the one about dogs and animals in the pound that were saved. First of all the commercial starts with music that reaches my emotions and it makes me think of ways to help prevent the import of these…
- 838 Words
- 4 Pages
Good Essays -
The Assessment and Qualifications Alliance (AQA) is a company limited by guarantee registered in England and Wales (company number 3644723) and a registered charity (registered charity number 1073334).…
- 870 Words
- 19 Pages
Satisfactory Essays -
Due to recertification requirements, employer personnel policy, and laboratory licensure requirements, participation in a continuing education (CE) program of some sort is necessary. But should that be the only reason - simply to fulfill an obligation?…
- 1480 Words
- 6 Pages
Powerful Essays -
Technology can add many positive factors to a company but it can also add negative factors if it is not approached in the right way. A manager wants to be able to introduce technology to their employees in a positive way to avoid failure whenever technology is presented. Technology can help a company set good communications skills, keep track of what employees are doing via the internet and telephones to assure employees and being productive. Technology can also help set fourth ethical standards and a guideline as well making employees aware of what is expected from the company beforehand. In this essay, I will be discussing how companies can use technology to help set and manage ethical standards and guidelines. I will also discuss how this can shape the type of work environment or culture a company promotes. Additionally, I will discuss how using technology to perform human resources functions affects company culture. Many people within a company must work together when it comes to technology because it affects everyone within an organization.…
- 1597 Words
- 7 Pages
Good Essays -
Billings, D. M., & Halsted, J. A. (2009). Teaching in nursing: A guide for faculty (3rd ed.).…
- 2212 Words
- 9 Pages
Powerful Essays -
In the given case, the Federal Trade Commission claimed that Texas Surgeons Independent Practice Association(IPA) of 26 general surgeons in the Austin, Texas and six competing medical practice groups who are the members of this association (the respondents), Texas Surgeons P.A. ("Texas Surgeons"), Austin Surgeons, P.L.L.C. ("AS"), Austin Surgical Clinic Association, P.A. ("ASCA"), Bruce McDonald & Associates, P.L.L.C. ("BM&A"), Capital Surgeons Group, P.L.L.C. ("CSG"), Central Texas Surgical Associates, P.A. ("CTSA"), and Surgical Associates of Austin, P.A. ("SAA"), violated Section 5 of the Federal Trade Commission Act, 15 U.S.C. § 45 by engaging in unlawful act of price fixing.…
- 1009 Words
- 5 Pages
Better Essays -
The workplace can be a very dynamic place; there are so many different people with all kinds of personalities. Because there are so many different personalities, there are different needs of safety which can create obstacles in the organization. This is where the Human Resource Department comes into play, they make sure that the needs of all employees are met and that they are working in a safe environment. Litigation has taken the place of common sense and compassion within organizations over the past years. Litigation has become a main priority and the Department of Labor, Equal Employment Opportunity Commission, the Americans with Disabilities Act of 1990 and also the Department of Homeland Security all have been regulating this. Although some may disagree that litigation has created a more structured work environment, there are a lot that would say it has. Litigation has balanced out the differences in the workplace.…
- 854 Words
- 3 Pages
Good Essays -
Department of Justice. (2009). The American with disabilities act of 1990, as amended. Retrieved from http://www.ada.gov/statute.html…
- 1186 Words
- 5 Pages
Better Essays -
Organizations whether it is big or small, abide by the federal law that regulates employment practices in the United States. One of the biggest roles that human resources department is responsible for, is to implement such practices within the organization to prevent future lawsuits.…
- 487 Words
- 2 Pages
Satisfactory Essays -
In today’s job market, it is very competitive for even the most basic of jobs so additional certification could give you an edge over the competition. Almost all jobs require some kind of knowledge in IT and without proper certification; your skills cannot be formally recognized. Any kind of IT certification you acquire will not only increase your earning potential but shows employers your willingness to learn new skills.…
- 517 Words
- 3 Pages
Good Essays -
US Customs and Border Protection is the largest law enforcement agency in the United States. There are more than 46,000 sworn federal agents and officers operating at 328 ports of entry throughout the country. CBP officers and agents primary mission is to prevent terrorists and any type of terrorist weapons from entering into the United States. CBP is also responsible for protection our borders from any and all individuals, drugs and other contraband trying to enter our borders illegally. On any typical day CBP welcomes nearly 1 million visitors, screens more than 67,000 cargo containers, and arrests more than 1,100 individuals and seizes nearly 6 tons of illicit drugs. Under the authority granted by the Immigration and Nationality Act (INA), as amended, a CBP officer may question, under oath, any person coming into the United States to determine his or her admissibility. A CBP Officer also has authority to search without warrant the person and effects of any person seeking admission, when there is reason to believe that grounds of exclusion exist.…
- 488 Words
- 2 Pages
Good Essays -
I could have saved a lot of time and lessen a number of mistakes. Whether you manage a large or small Fleet many of the challenges are the same and shouldn’t be a factor in your decision to pursue the CPFC certification. Having tackled about every topic this program covers, one of the benefits I didn’t expect was the rewarding feeling as I went through the study guides affirming many past decisions while reinforcing management philosophies. It also was a reminder of area’s to re-evaluate.…
- 1022 Words
- 5 Pages
Satisfactory Essays -
The engineering sector is the largest segment of the overall Indian industrial sector. India has a strong engineering and capital goods base. The important groups within the engineering industry include machinery & instruments, primary and semi finished iron & steel, steel bars & rods, non-ferrous metals, electronic goods and project exports. The engineering sector employs over 4 million skilled and semi-skilled workers (direct and indirect).…
- 18493 Words
- 74 Pages
Satisfactory Essays -
3.1 The Board in consultation with the metropolitan/district assemblies shall give recognition/permit to certain facilities to be used as slaughter houses/slabs. 3.2 Location of the Abattoir or Slaughter slab – where the facility was put up without any permission from the Board and the conditions are found to pose a food safety risk to the consumer, the place shall be closed down and the operators sanctioned accordingly. 3.4 All Abattoirs shall be routinely inspected using the following criteria;…
- 513 Words
- 3 Pages
Satisfactory Essays