Материал: Крючков Фундаменталс оф Нуцлеар Материалс Пхысицал Протецтион 2011

documents “on the fly”, in such form as acceptable for the given system and the browser. There is however one thing limiting to this. Some of the functions in the scenario are written in the VBScript language and are to be executed on the client computer, while the VBScript language is nowadays supportable only by the MS Internet Explorer browser. So when other platforms or another browser program is used in Windows systems, faults may occur.

Application and performance of the system

As mentioned earlier, the E/Z MAS has been designed for enterprises with a moderate NM accounting and control demand. The requirements specification for the E/Z MAS software is a much less voluminous document than its CoreMAS counterpart. It specifies the criteria to be looked at for the potential application at a enterprise as follows:

∙enterprise type – the system is intended for item h andling enterprises rather than for bulk handling ones;

∙number of transactions per month – the E/Z MAS is i ntended for enterprises with a minimum of 50–100 and a maximum of 1500–2000 transactions per month;

∙item type – the E/Z MAS is intended for enterprises with both static and dynamic type of items;

∙inventory dimensions – this parameter should be con sidered along with the type and the number of transactions per month. For example, an enterprise with 100000 static items and 100 transactions per month is the right candidate for the E/Z MAS installation. And an enterprise with the same number of items and 100000 transactions per month is the wrong one.

Here are some of the E/Z MAS features to mention:

∙the E/Z MAS can operate as a closed system or as an open system in a closed environment.

∙the E/Z MAS can operate both on a isolated computer and in a network with a dedicated database server.

∙the A&C system controls system logins by name and password, both of these not relating to the user parameters in the domain (unlike the CoreMAS) and verified by the system as such.

∙data can be databased using barcode devices and scales.

∙the E/Z MAS is available for operation immediately after the installation. At the same time, with all files being presentable to user, the system can be readily updated by adding functions.

357

E/Z MAS A&CS database design

The database tables can be grouped into a number of domains:

∙Users and right of access: Users, UserOp, Operation.

∙Enterprise: Enterprise, PhysLoc, MBA.

∙Material batch: Batch, BatchMat, MatType, PhysForm, ChemForm, Packaging, Quality.

∙Containers: ConInfo, ConType.

∙Transactions: ShipTrans, TransType, Trans, ConTrans, StatusType.

∙TIDs (seals): TIDTrans, TIDInfo, TIDTransType, TIDType.

∙Barcodes: BarcodeError, InvVerify, InvTrans, InvInfo.

∙Federal-level reports: UnitConversion, Classification.

∙A separate Log table not connected to any table is used to control logins by memorizing the URL from which the system was logged in.

The E/Z MAS system includes base tables from which data cannot be removed so that no data integrity be disturbed, e.g. physical location. These tables are filled in when the system begins operations and information can be only added thereto.

We shall discuss the key concepts and entities the E/Z MAS database contains.

The description of any material used in the database is based on the concept of material batch. The material type, weight, physical/chemical form and package are identified for each batch. Batches of material can arrive from beyond the site or result from processing of material.

The material of any batch is subject to distribution among containers. The system watches that the overall material weight be the same as that of the batch. The containerization concept is close to what was employed in the CoreMAS A&C system: no limited number of containers that could be placed one in another, application of seals and conformity of these to containers. The only difference of the containerization concept is that no material can exist in the E/Z MAS beyond the container. If it does (ingot metal, for example), the system creates a virtual container which expressly conforms to this part of material. The container may be empty.

Each container, unless it is in-transit (the same status exists in the CoreMAS), is matched by a location. If a container is contained or placed in another container, the location thereof has the NULL value and is identified via the location of the external container.

The location is identified in the database by a number of notions. The most general notion is enterprise. Enterprise for this database is only one

and it may receive only external shipments so these exist as names

358

(addresses). There is at least one MBA matching the enterprise. The number of material balance areas for enterprises is not limited. It is inside the MBA that the location is specified. There can be not less than one location while the maximum number of locations is not limited. The location may contain containers or be empty.

Finally, an important component of the database is users. Each user has a login and a password. Rules of access to MBAs and containers and rights to perform any function in or out of the MBA are specified for each user.

The E/Z MAS developers believe that such database arrangement is adapted the best to accounting of item material, though bulk material can also be accounted for.

Functionality of E/Z MAS

The E/Z MAS possesses all the functionality an NM A&C system is expected to have. The system keeps track of nuclear material using the inventory listing. The information on material in this listing is changed synchronously with the actual changes in the so-called near real time. This, naturally, suggests that the user enters the transaction data on a timely basis when the real action takes place.

Still, the system is not designed to control material physically; it does not control racks, doors or locks, and does not track down TIDs.

Five categories of the E/Z MAS functions can be identified:

1.Movement of containers.

2.Transfer of containers into or out of the enterprise.

3.Inventory-affecting operations.

4.Generation of reports.

5.Operation of statistical database tables.

More details on the system’s functionality are given in descriptions of the following operations.

∙Movements within MBAs – this function allows an aut horized user to move containers and the content thereof between different physical locations within one MBA. For this operation, the user identifies the MBA, selects the containers, defines the new location and orders the process to be started. Where the process runs routinely, the following transactions are implemented and logged: the one showing that the container has been moved and that indicating the container’s new location.

∙Movements between MBAs – this function exists in tw o forms: 1) containers are moved between different MBAs in one operation, and 2) material is moved between different MBAs in two steps in an in-transit

359

condition. The container shipment function can be performed by one user and the container receipt function by another user.

In both cases the user selects the original MBA, the container, the destination MBA and the physical location therein. In the second option, the user ships the container without giving the destination, the container being later put out of the in-transit condition at the destination point.

∙External transfers: shipments/receipts – this funct ion enables material receipts and shipments from and to beyond the site to be recorded.

When material is received, the authorized user can add a new container and the new material it contains to the system in such form as it has been received from another enterprise. It is exactly where the material’s physical appearance, chemical composition and form are identified and the material is linked to the container. In all other operations we deal with containers and not with material. It is also where the MBA to which the material is shipped, the number and composition of containers and the outside enterprise from which the material was received are identified.

When material is shipped, the user records the enterprise to which the material is shipped and the container or containers to be shipped.

∙Inventory change – this may involve a number of ope rations: correction of material parameters. This function enables the user to

modify the material weight and the elements and isotopes thereof. The user selects the MBA, the material type and the type of the correction to follow. One may change the material weight and update information on an element and an isotope in the material;

combination of materials into a new material; split of a material batch into two batches;

bulk separation – makes it possible for the user to record isotope separation operations.

∙Containerization – may involve the following operat ions: formation of a container not linked to material – e mpty container; placement of containers in another container;

withdrawal of containers from a container; movement of material between containers.

∙Physical inventory taking. This function helps the user to enter the physical inventory taking results with recorded observations. The checked container is labeled and the check results are entered in process.

∙Accounting of tamper indication devices (seals). The system enables the user to generate seals, update seals and be provided with reports on

360