Abstract
A method of transmitting data information electronically primarily between two units with the third intermediate unit. Primary unit 150 “VARe” processes received raw data information for validation; and primary unit 180 “USeR” transmits raw data information to be processed then receive back the processed data information, and other pertinent information; the intermediate unit 135 “PUMa” is the inventor of the software application designed to interface among VARe and various USeR devices. PUMa installs the software application online in the USeR unit and frequently checks VARe for any code changed, added, deleted, replaced, mutated and or permutated; then updates the USeR with accurate and valid data, algorithm and logical computation code for proper transaction and appropriate transmission of data information. The data information submitted by the USeR is checked and validated against the source code stored in VARe for an acceptance and approval or a rejection and disapproval of the transaction.
Claims
1. IECUSOFT software application system is designed, developed, and implemented to interface database systems to work in parallel and in conjunction among USeR (client) for data transmission; PUMa (maintenance server) for software installation and update; and VARe (database server) for validation, approval and release of goods purposes.
2. The interface system of claim 1, further comprising the USeR downloads the software application online from PUMa and installs it. PUMa momentarily updates the client after installation.
3. The interface system of claim 1, further comprising the USeR retrieves beforehand any pertinent data information from VARe, then transmits trade data information to VARe, first for certification then after for production.
4. The interface system of claim 1, further comprising VARe processes the trade data information transmitted, validates, then either approves the trade data and releases the goods or disproves the trade data.
5. The interface system of claim 1, further comprising PUMa constantly checks VARe for updates code data then processes the data and updates the USeR.
6. The interface system of claim 1, further comprising the USeR-VARe interface is a two way communication where the USeR transmits data and VARe validates, approves, and releases; the USeR-PUMa interface is a one way communication where PUMa installs and updates the client; and the VARe-PUMa interface is a one way communication where the PUMa downloads update data information from VARe then processes the data and updates the USeR.
7. IECUSOFT software application is a user-friendly, less work and time saving process. The USeR transmits and receives trade data information to and from VARe, but the USeR only receives software installation and updates data from PUMa. The client is a self-efficacy method to auto guide the USeR to complete the trade process and leads to a validation approval.
8. The self-efficacy method of claim 7, further comprising the client in conjunction with PUMa has a built-in database to auto populate the data in the field for the USeR as data are being filled out or entered.
9. The self-efficacy method of claim 7, further comprising the client in conjunction with PUMa has a record tracking capability to auto activate or auto deactivate subsequent records for the USeR as data are being filled out or entered.
10. The self-efficacy method of claim 7, further comprising the client in conjunction with PUMa incorporates a record and data checking ability to auto generate subsequent records with their respective data in the field for the USeR according to the previous records and the current record being filled out.
11. The self-efficacy method of claim 7, further comprising the client in conjunction with PUMa has a data monitoring capability to turn on and off current record's data fields; and to enable and disable future records' data fields. This reduces processing time for the USeR as data are being filled out or entered.
12. The self-efficacy method of claim 7, further comprising the client in conjunction with PUMa has a built-in data read/write competency to auto write data entry on appropriate CBP forms in their respective fields' location on the form.
13. IECUSOFT software application is a self-adjusting computation and an auto data populated system. VARe transmits the necessary raw data information to PUMa; PUMa processes the data then installs and updates the client. The client in conjunction with PUMa becomes an auto computational and auto populated system.
14. The auto computational system of claim 13, further comprising the client in conjunction with PUMa has built-in arithmetic capabilities that compute duty, fee, and tax automatically; the client is adapted to respond to any instant changes made in its data environment for update, recovery, and re-computation.
15. The auto computational system of claim 13, further comprising the client in conjunction with PUMa has an algorithmic computational capabilities to generate ‘entry numbers’ and computes the check digit automatically.
16. The auto computational system of claim 13, further comprising the client in conjunction with PUMa has a database sorting capability to automatically retrieve and display the required and needed data for computation: Rates, case numbers, items descriptions, manufacturer/suppliers information, duty Code etc. for proper computational for the selected formula, and data restrictions.
17. The auto computational system of claim 13, further comprising the client in conjunction with PUMa has a data correction ability to warn the USeR of any data entry error. It also automatically assorts and rearranges random data filled out in sequence or in logical order, at same time coverts lower case data entry to upper case as required before transmission. In addition the client in conjunction with PUMa has a front end validation to check the data entered for errors while typing and a back end validation to check and display the errors data after transmitting.
18. The auto computational system of claim 13, further comprising the client in conjunction with PUMa has a built-in data lookup capability to allow the USeR to select and narrow down the specific item of choice with a drop down arrow from a combo box that widen to provides an easy selection of items; and a content that shrunk to fit the content in a data field for full view purposes only.
Description
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING
[0015] The above features of this invention are described in the following detailed description and shown in the following drawings:
[0016] FIG. 1: Illustrates the PUMa, VARe, and USeR Interface Diagram;
[0017] FIG. 1a: Illustrates the PUMa Unit;
[0018] FIG. 1b: Illustrates the VARe Unit;
[0019] FIG. 1c: Illustrates the USeR Unit;
[0020] FIG. 2: Illustrates a Typical Transaction Configuration;
[0021] FIG. 2a: Illustrates the Software Logo Start-Up Icon;
[0022] FIG. 2b: Illustrates the ACE Customs APPS Detail;
[0023] FIG. 3: Illustrates the Entry Summary Transaction Configuration (ESTC);
[0024] FIG. 3a: Illustrates the Batch Control Identification record;
[0025] FIG. 3b: Illustrates the ACE Customs APPS;
[0026] FIG. 4: Illustrates an Entry Summary Transaction Configuration (ESTC);
[0027] FIG. 4a: Illustrates the Block Control Identification record;
[0028] FIG. 4b: Illustrates the Entry Summary Chapter input records
[0029] FIG. 5: Illustrates the Entry Summary Transaction Configuration (ESTC);
[0030] FIG. 5a: Illustrates the Entry Summary Header Control input record;
[0031] FIG. 5b: Illustrates the generated Window Errors;
[0032] FIG. 6: Illustrates the Entry Summary Transaction Configuration (ESTC);
[0033] FIG. 6a: Illustrates the Line Item Tariff/Value/Quantity Details input record;
[0034] FIG. 6b: Illustrates the Line Item Input records;
[0035] FIG. 7: Illustrates the Entry Summary Transaction Configuration (ESTC);
[0036] FIG. 7a: Illustrates the Entry Summary Grand Totals input record;
[0037] FIG. 7b: Illustrates the Entry Summary Chapter input records
[0038] FIG. 8: Illustrates the Entry Summary Transaction Configuration (ESTC);
[0039] FIG. 8a: Illustrates the Block Control Closing record;
[0040] FIG. 8b: Illustrates the Entry Summary Chapter input records
[0041] FIG. 9: Illustrates the Entry Summary Transaction Configuration (ESTC);
[0042] FIG. 9a: Illustrates the Batch Control Closing record;
[0043] FIG. 9b: Illustrates the ACE Customs APPS;
[0044] FIG. 9c: Illustrates the Company Logo Software Closing Icon;
DETAILED DESCRIPTION OF THE INVENTION
[0045] The following detailed description of the invention is NOT intended to be in competition with the existing software in the market but rather to provide a more affordable, user friendly, and fast processing CBP Software that will interface and communicate with the customs in a simple and efficient operating method for validation and release of goods; more specifically to implement a modern upgrade software design which is comparable and analogous to the new age technology.
[0046] The Software design intention and focus is to fill in the market void by providing the tools needed to adept and familiar customs users, as well as to inept or unskilled and unfamiliar customs amateur to navigate the CBP's procedural morass. And also to accommodate customs paper filing of the old age world to customs paperless filing of the new age technology.
[0047] FIG. 1 illustrates and defines the flow of data among different units operation: “PUMa, VARe, and USeR interface Diagram” 100. First a server 135 called “PUMa” Provides, Updates, Maintains and services the software system; second another server 150 called “VARe” Validates the data entry, Approves the transaction, and Releases the goods; and third a client 180 called “USeR” Utilizes the software, Sends and Receives data information. The arrows 190 depict the direction of the data flow between interfaced units. The flow of data in diagram 100 between VARe 150 and the USeR 180 is both ways “bidirectional”; the USeR 180 transmits data information to VARe 150 to be processed for validation and VARe 150 transmits back the processed data for approval and release of goods or for disapproval and rejection. The flow of data in diagram 100 between PUMa 135 and VARe 150 is one way “unidirectional”; PUMa 135 checks VARe 150 periodically for update and downloads the necessary data. The flow of data in diagram 100 between PUMa 135 and USeR 180 is also one way “unidirectional”; PUMa 135 installs the software system into USeR 180 client and updates the USeR 180 with new data code parameters downloaded from VARe 150.
[0048] Drawing sheet number 1/9, FIG. 1a displays a typical PUMa unit 135 constituting of various units capable of downloading data information from VARe unit 150, writing software codes, and uploading data code into USeR unit 180 for proper and legal transaction. FIG. 1b shows a symbolic VARe unit 150 composed of various data code to validate transaction data information for approval and release of goods or for disapproval and rejection. FIG. 1c represents an ordinary USeR unit 180 comprised of a personal computer (PC) or a laptop and or just any electronic devices having the same capabilities as a PC or laptop to perform a typical transaction: Transmit and receive data information.
[0049] Drawing sheet number 2/9: FIG. 2: “A Typical Transaction Configuration” 200 displays the software application transaction process and demonstrates a typical Entry Summary Chapter transmission configuration. To launch the software applications simply click or double click on IECUSOFT Icon 225 acronym for Import/Export CUstoms SOFTware, pronounced ‘iqsoft’. FIG. 2a: “IECUSOFT Logo” gives the user access to the main window FIG. 2b: “ACE Customs APPS” 270. Before performing any action the user should first click the RECEIVE button 230 to retrieve any data information that might be in the storage space to clear space for new data information. By clicking the RECEIVE button 230 removes the data information from the storage space and save them on a different location of the user choice upon installation of the software application. The END button 240 closes the software application operation (not VARe server 150 connection) and the SEND button 250 transmits the data information to VARe server 150. The Certification button 260 has two selections: Certification selection signals VARe server 150 to validate the data information for testing purpose only and Production selection signals VARe server 150 to validate the data information for live transaction.
[0050] Drawing sheet number 3/9, FIG. 3: “Entry Summary Transaction Configuration” 300 is a typical transaction process configuration starting first with the user identification header FIG. 3a: “Batch Control Header” 315. FIG. 3b: “ACE Customs APPS” displays the active and or enable button “Batch Control Header” 315 that signals the beginning of the transaction file; and it is used to identify the user and the sender/receiver of the data. Batch Control Header” 315 allows the user to select a chapter to file and only one type of application data can be processed within a typical batch control. The CLEAR button 333 deletes the entire data entry in a record rather than individual field data deletion and the SUBMIT button 360 transmits the entire data entry record to the USeR client before transmitting to VARe server for validation and approval. The date data field 350 is a date picker field feature that formats the date according to CBP format. The data element 370 is the name of the data field element and the red asterisk “*” symbol 340 after the data element symbolizes the data field element is mandatory. The data selection name 380 is the data selection item and places the selected data content in the data field 390. Some data fields 390 are editable and enable; some are not according to the nature of the data required. The data selection name 380 can be a combination of one, two, or three data selection name boxes; and while the software application is in running and or executable mode the data selection name 380 widens itself to fit the selection item content. Also by resting the cursor on a selected data name a definition of the name will appear. To make data element 370, data selection name 380, and data field 390 appropriately viewable in the layout window 315, abbreviations and acronyms 320 have been used to describe the data element name and to optimize the space suitably to fit data element 370, data selection name 380, data field 390, CLEAR & SUBMIT buttons inside the display window.
[0051] Drawing sheet number 4/9, FIG. 4: “Entry Summary Transaction Configuration” 400 is a typical import transaction records configuration followed secondly by a detail data identification header FIG. 4a: “Block Control Header” 450. “Block Control Header” 450 is used to identify the detail data to follow and also allows separating data into groups by location; once again only one type of application data is allowed to be processed within a typical block control. FIG. 4b: “Entry Summary Chapter” 405 provides record formats and specifies the unique identity of transaction information regarding item(s) being transacted. “Mandatory Records” 460 must be filed, “Conditional Records” 470 are required records only and only if the data entered in the mandatory record requires any or all conditional records to be filed, and “Optional Records” 480 are not conditioned by any means and it can be filled out by the user preference if it is needed for the transaction in process. Line Item 440 contains information regarding a single article or a component of an article. The software application writes and saves the data entered to the appropriate CBP Forms for later usage using the executable buttons: “Entry Summary Form 7501” 410 for import purposes, “Entry/Immediate Delivery Form 3461” 420 for both import/export purposes, and “Shipper's Export Declaration Form 7525V” 430 for export purposes. The CLOSE button 495 disposes the displayed window.
[0052] Drawing sheet number 5/9, FIG. 5: “Entry Summary Transaction Configuration” 500 is a typical transaction configuration that begins with an entry summary header control record FIG. 5a “Header Control” 540, a mandatory record consisting of information that applies to all items reported for the trade. The “Header Control” 540 is the most essential record of the Entry Summary Transaction Configuration Chapter 500; it carries out various operations that free the user from complex computations. The most important computations performed for the user is the check digit computation; the harmonized tariff schedule duty, fee, and tax calculations; and antidumping and countervailing duty. FIG. 6b “Error Window” 585 is a generated window launched as pop-up window to warn the user that the data entered is (are) invalid. It prompted the user to correct the information entered by providing the user with a hint such as data element is mandatory, data element must be numeric, data element length must be 3 or length must be no more than 9 and so on. The data information won't be submitted until the fields with the errors are corrected.
[0053] Drawing sheet number 6/9, the ellipsis symbol “ . . . ” 610 depicts that there are other required records but the description of this specification is intended to describe the essential records. FIG. 6: “Entry Summary Transaction Configuration” 600 is a typical transaction configuration that includes line item grouping FIG. 6b: “Line Item” 675, containing records needed to file data information about an article or a component of an article. FIG. 6a: “Tariff/Value/Quantity (TVQ) Detail” 630 is a mandatory line item record containing classification information of an article that reports a single tariff classification information at one time; it can be repeated for additional tariff classification information by clicking the NEXT button 650 after filling out all the necessary mandatory data fields in FIG. 6a: “Tariff/Value/Quantity (TVQ) Detail” 630 and its associated records 640 if required. The associated records 640 are defined to be the fee, tax, antidumping duty, countervailing duty, and Partner Government Agency. The associated records 640 are grayed out meaning deactivated; they are activated depending on the tariff classification associated to either one of the records. The tariff/value/quantity detail 630 is the most essential record of the tariff grouping; it performs the complex computation formula for tax, fee, and duty for the user, reducing the time consuming, and eliminating the hassle and the confusion of computing these data information. The data computed (fee, tax, duty and rates) are populating on the “Display Data” 620 fields from the USeR client. The “Display Data” 620 are more specific to any article or component description “ADD and CVD Description” 670 and any company in any country “Manufacturer/Supplier Name” 680 for concise and accurate computation. Each individual fees, taxes, and duties for all additional tariff classification information are added up automatically to the grand totals fee, tax, and Duty. The “Currency/Unit/Rate” 690 performs any currency conversion to US dollar currency and places the converted currency result in the Value of Goods Amount field data.
[0054] Drawing sheet number 7/9, FIG. 7: “Entry Summary Transaction Configuration” 700 is a typical transaction configuration that contains the total amount record for any particular transaction. FIG. 7b: “Entry Summary Chapter” 765 provides a total amount record so that individual fees, taxes, and duties for all tariff classification information are added up automatically, generated and populated with the total fee, tax, and duty values on the appropriate data field with the correct format in FIG. 7a: “Grand Totals” 720.
[0055] Drawing sheet number 8/9, FIG. 8: “Entry Summary Transaction Configuration” 800 is a typical transaction configuration that includes a block control trailer to signify the end of the data information. FIG. 8b: “Entry Summary Chapter” 855 provides a block control trailer record FIG. 8a: “Block Control Trailer” 810 to close the detail data information.
[0056] Drawing sheet number 9/9, FIG. 9: “Entry Summary Transaction Configuration” 900 is a typical transaction configuration that includes a batch control trailer to signify the end of the transaction file. FIG. 9b: “ACE Customs APPS” 945 provides a batch control trailer record FIG. 9a: “Batch Control Trailer” 990 to close the transaction data file and to submit the filed data to a local USeR client; this operation will activate the SEND button 960. Open the VPN (Virtual Private Network) and click on the SEND button 960 to transmit data information to VARe server 150; then click on the END button 930 to end the software application (IECUSOFT); the company logo FIG. 9c: “THAMANI Logo” 999 will appear for a few seconds to acknowledge that the trade has been completed.
[0057] While the software, system and method have been considered to be the most practical and effective embodiments, it is to be understood that the disclosure need not to be limited to the disclosed embodiments. It is intended to be included within the scope of the present invention to encompasses all such permutations, enhancements, modifications, equivalents, combinations, and improvements that fall within the true scope of the present invention defined in the description, drawings, figures, and claims. Although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation. Therefore, any person of ordinary skill in the pertinent art or science will recognize these traits or features without departing from the scope of the present invention.
