APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST...

61
Signature and date Inv. No. of dupl. Instead of inv. No. Signature and date Inv. No. sign. 2019 AGREED APPROVED BY CEO ООО "CRPT" _______________/ / ___________________ /A.V. Zakhozhiy/ _____ of _________ 2019. _____ of _________ 2019. ORDER MANAGEMENT STATION 3.0 Special software Software package "Web-interface Module" Operator's Manual RU 15861920.620111-01 34 01 Approval sheet

Transcript of APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST...

Page 1: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

Sig

natu

re a

nd d

ate

Inv.

No. of dupl.

Inste

ad o

f in

v.

No.

Sig

natu

re a

nd d

ate

Inv. N

o. sig

n.

2019

AGREED APPROVED BY CEO

ООО "CRPT" _______________/ / ___________________ /A.V. Zakhozhiy/

_____ of _________ 2019. _____ of _________ 2019.

ORDER MANAGEMENT STATION 3.0

Special software

Software package "Web-interface Module"

Operator's Manual

RU 15861920.620111-01 34 01

Approval sheet

Page 2: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

Sig

natu

re a

nd d

ate

Inv.

No. of dupl.

Inste

ad o

f in

v.

No.

Sig

natu

re a

nd d

ate

Inv. N

o. sig

n.

2019

APPROVED

RU 15861920.620111-01 34 01-LU

ORDER MANAGEMENT STATION 3.0

Special software

Software package "Web-interface Module"

Opeartor's Manual

RU 15861920.620111-01 34 01

Sheets 61

Page 3: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

2

RU 15861920.620111-01 34 01

ANNOTATION

This document "Order management station 3.0. Special software. Software package "Web-

interface Module". Opeartor's Manual" RU 15861920.620111-01 34 01 is intended for employees

operating information services provided via Web Interface Module software complex, a part of the

specialized software (SSW) of the "Order management station 3.0" automated system (OMS

AS 3.0). The document describes actions taken by users with the functional role of OMS Operator.

The document is developed in compliance with GOST 19.505-79 "Unified software documentation

system. Operator's manual".

This document uses the following designations:

1) Elements of the on-screen entry forms are designated as ‹Field›, ‹Button› or ‹Menu

item›;

2) PC keys are designated as [Key]. Combinations of simultaneously pressed keys are

designated as [Key1+Key2].

Page 4: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

3

RU 15861920.620111-01 34 01

CONTENTS

1. INTENDED USE OF THE PROGRAM 4 2. EXECUTION ENVIRONMENT 11 3. PROGRAM EXECUTION 13 4. MESSAGES TO OPERATORS 52 LIST OF TERMS 53

LIST OF ABBREVIATIONS 55 LIST OF PICTURES 56 LIST OF TABLES 59

Page 5: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

4

RU 15861920.620111-01 34 01

1. INTENDED USE OF THE PROGRAM

This specialized software is intended to enable the performance of the targeted OMS AS

3.0 functionalities including:

1) Placement of MC emission orders.

2) Application of MC.

3) Verification of MC application.

4) Aggregation of ready and packed products marked with identification tools (IT).

Page 6: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

5

RU 15861920.620111-01 34 01

1.1. Program structure

OM

S A

S 3

.0 a

rch

itec

ture

Pic

ture

1

Page 7: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

6

RU 15861920.620111-01 34 01

Picture 1 shows OMS AS 3.0 architecture as collections of the information services and

a set of technical tools (including computing, software and information tools) intended to enable

targeted system functionalities (see section 1).

OMS AS 3.0 comprises the following subsystems:

1) Visualization subsystem that provides information services to OMS AS 3.0 users.

2) Enquiries Receipt and Processing subsystem.

3) Configuration Management subsystem.

4) Interface with Allied Systems subsystem.

OMS AS 3.0 SSW comprises the following features:

1) As a part of Visualization subsystem:

− Web Interface software complex

2) As a part of Configuration Management subsystem:

− Devices Registry software complex.

− Economic Agents software complex.

− Users software complex.

− Enterprise Profile Management software complex.

− Emission Monitors software complex.

3) As a part of Enquiries Receipt and Processing subsystem:

− Order Management software complex.

− Aggregation Management software complex.

− Rejection Management software complex.

4) As a part of Interface with Allied Systems subsystem:

− Interface with ATPMS software complex.

− Interface with IS MP software complex.

− Interface with MC EM software complex.

Page 8: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

7

RU 15861920.620111-01 34 01

1.2. Interface with allied systems

1.2.1. General information

In the course of deployment, OMS AS 3.0 gets embedded into the technology

infrastructure of the economic agent. Picture 2 shows commercial use of OMS AS 3.0.

Co

mm

erc

ial u

se o

f O

MS

AS

3.0

Pic

ture

2

Page 9: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

8

RU 15861920.620111-01 34 01

In the course of operation, OMS AS 3.0, as part of an informational, communicational and

functional interface, performs data exchange with the allied systems listed in Table 1.

Table 1 List of allied systems

Legend Description

Informational and communicational interface

Information Gateway AS as a part of ATPMS (Inexto Gate)

The following interactions with Inexto Gate are implemented in OMS AS 3.0 Interface with Allied Systems subsystem:

− Interface between OMS AS 3.0 and Inexto Gate as part of processing the commercial orders for marking codes emission;

− Interface between OMS AS 3.0 and Inexto Gate as part of providing the emitted marking codes to be applied to the products;

− Interface between OMS AS 3.0 and Inexto Gate as part of processing the reports on the use of marking codes;

− Interface between OMS AS 3.0 and Inexto Gate as a part of processing the reports on aggregation;

− Interface between OMS AS 3.0 and Inexto Gate as a part of processing the reports on the retirement/rejection of marking codes;

The interface is implemented using open interfacing protocols (HTTP, REST), data exchange format is JSON.

Emission Monitor (EM) AS The following interactions with EM are implemented in OMS AS 3.0 Interface with Allied Systems subsystem:

− Interface between OMS AS 3.0 and EM as a part of providing the orders for marking codes emission;

− Interface between OMS AS 3.0 and EM as a part of receiving the emitted marking codes to be applied to the products;

− Interface between OMS AS 3.0 and EM as a part of providing the reports on the use of marking codes;

− Interface between OMS AS 3.0 and EM as a part of providing the reports on the retirement/rejection of marking codes;

The interface is implemented using the binary protocol, the protocol is defined by EM manufacturer.

Page 10: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

9

RU 15861920.620111-01 34 01

Legend Description

Track & Trace Information System for Marking and Monitor the Tobacco Products Circulation (IS MOTP) AS

The following interactions with IS MP are implemented in OMS AS 3.0 Interface with Allied Systems subsystem:

− Interface between OMS AS 3.0 and IS MP as part of providing the reports on the aggregation of marking codes;

− Interface between OMS AS 3.0 and IS MP as part of providing the reports on the retirement/rejection of marking codes;

The interface is implemented using open interfacing protocols (HTTP, REST), data exchange format is JSON

Data collection terminals (DCT) The following interactions with DCTs are implemented in OMS AS 3.0 Interface with Allied Systems subsystem:

− Interface between OMS AS 3.0 and DCTs as part of processing the reports on the retirement/rejection of marking codes;

The interface is implemented using open interfacing protocols (HTTP, REST), data exchange format is JSON.

Functional interface via Information Gateway AS

Enterprise Resource Planning (ERP) system

Receipt of commercial orders for marking codes emission from Enterprise Resource Planning (ERP) system is implemented as part of the interface between OMS AS 3.0 and Inexto Gate (part of PTM AS) in terms of processing commercial orders for marking codes emission;

Marking application system, part of ATPMS (Inexto LIZ)

Provision of emitted marking codes to be applied to the products is implemented in Inexto LIZ as a part of the interface between OMS AS 3.0 with Inexto Gate (part of ATPMS) in terms of provision of emitted marking codes to be applied to the products;

Aggregation stations, part of ATPMS (Inexto INEXPRESS /Fracture Code)

Receipt of reports on aggregation of marking codes from Inexto INEXPRESS/Fracture Code is implemented as a part of the interface between OMS AS 3.0 and Inexto Gate (part of ATPMS) in terms of processing the reports on aggregation; .

Page 11: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

10

RU 15861920.620111-01 34 01

Legend Description

Functional interface via Emission Monitor AS

Emission Server (ES) AS Submitting orders for the emission of marking codes to ES is implemented as a part of the interface between OMS AS 3.0 and EM within the context of provision of the orders for marking codes emission; Receipt of emitted marking codes from ES is implemented as part of the interface between OMS AS 3.0 and EM in terms of receipt of emitted marking codes to be applied to the products; Provision of the reports on the use of marking codes in ES and IS MP is implemented as a part of the interface between OMS AS 3.0 and EM in terms of provision of the reports on the use of marking codes; Provision of reports on the retirement/rejection of marking codes in ES and IS MP is implemented as a part of the interface between OMS AS 3.0 and EM in terms of provision of reports on the retirement/rejection of marking codes;

Page 12: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

11

RU 15861920.620111-01 34 01

2. EXECUTION ENVIRONMENT

2.1. PC pre-requisites

To operate information services provided by Web Interface Module software complex (part

of OMS AS 3.0), the following computing tools (CTs) must be used:

1) Individual user's CTs:

− AWP of a user having the functional role of OMS Operator (OMS Operator AWP), which

is a PC compliant with the recommended requirements to Microsoft Windows OS (8.1 or

higher) and NIC that provides information and communication link to OMS AS 3.0 HCS.

2.2. Software required for the functioning of the program

To operate information services provided by Web Interface Module software complex

(part of OMS AS 3.0), the following components of the general software (GSW) are required:

1) Microsoft Windows OS 8.1 or higher;

2) Web- browser:

− Mozilla Firefox 40 or higher.

− Internet Explorer 9 or higher.

− Google Chrome 37 or higher.

2.3. Requirements to personnel

OMS AS 3.0 SSW must be operated where OMS AS 3.0 HCS is deployed. Access to

information services provided by Web Interface Module software complex (part of OMS AS 3.0

SSW) is granted via information and communication links connecting OMS Operator AWP and

OMS AS 3.0 HCS.

The following users are granted access to operate information services provided by Web

Interface Module software complex (part of OMS AS 3.0 SSW):

1) experienced in PC operation and fully mastered to operate the Microsoft Windows OS

GUI and its functionalities;

Page 13: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

12

RU 15861920.620111-01 34 01

2) having skills in web surfing and fully mastered in operating GUI of one of the following

recommended web-browsers;

3) trained to operate OMS AS 3.0;

4) familiar with the intended use and basic operation principles of secure infrastructure

for marking codes emission.

To differentiate access to information services provided by Web Interface Module

software complex (part of OMS AS 3.0 SSW), the role model is used. Employee competency

levels must comply with the functional roles utilized by the model:

1) OMS Admin.

2) OMS Operator.

2.3.1. OMS Operator

OMS Operator must have sufficient knowledge and skills to perform the following tasks:

1) Creation and management of the commercial orders.

2) Maintaining the list of aggregation notifications.

3) Maintaining the list of the notifications on the retirement of rejected products by the

production department.

4) Configuring parameters for information and communication links to emission monitors.

2.3.2. OMS Admin

OMS Admin must have sufficient knowledge and skills to perform the following tasks:

1) Management of OMS AS 3.0 user accounts.

2) Configuring parameters for information and communication links to emission monitors.

3) Setup and configuration of end devices (client devices) parameters.

4) Entering and editing economic agents data.

5) Control over OMS server state.

Page 14: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

13

RU 15861920.620111-01 34 01

3. PROGRAM EXECUTION

3.1. Loading and starting the program

3.1.1. Starting the program

The program is loaded to RAM of the OMS Operator's AWP as JavaScript software

modules in the course of accessing information services provided by Web Interface Module

software complex (part of OMS AS 3.0 SSW).

To access information services of Web Interface Module software complex, OMS

Operator must:

1) Load web - browser to RAM using a Microsoft Windows OS functionality (OS Main

menu, Desktop Shortcut, OS taskbar, etc.);

2) In the address bar of the web -browser, enter the address to be requested from the

program developer.

3) Enter username and password into the on-screen login form (Picture 3) and press the

Login button. Users can view the entered password by clicking the eye icon in the right

area of the field.

Page 15: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

14

RU 15861920.620111-01 34 01

On-screen login form Picture 3

If the entered username and password are correct and valid, the browser window

shows the program homepage (Picture 4).

Page 16: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

15

RU 15861920.620111-01 34 01

Program homepage Picture 4

The on-screen login form (Picture 3) also contains ‹REST documentation› and ‹Swagger

documentation› hyperlinks. When you click on them, new web browser windows appear,

containing hypertext descriptions (Picture 5 and Picture 6) for the corresponding application

programming interfaces (API).

Page 17: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

16

RU 15861920.620111-01 34 01

REST API hypertext description Picture 5

Swagger API hypertext description Picture 6

Page 18: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

17

RU 15861920.620111-01 34 01

3.2. Program execution

3.2.1. Program main window

After entering the system, user gets access to the information services provided by the

user interface of the program homepage (Picture 4).

Program homepage consists of the following main elements (Picture 7):

1) Main menu (highlighted in red).

2) Data display area (highlighted in purple).

3) Information panel (highlighted in green).

Program homepage Picture 7

Page 19: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

18

RU 15861920.620111-01 34 01

Program homepage in the downsized browser window Picture 8

When the web browser window is downsized, the main menu and the information panel

disappear from the program homepage (Picture 8), and to display them on the screen again,

controls in the top corners of the homepage are used (Picture 9) – the control in the left top corner

(highlighted in red) is used to display the menu, the one in the right top corner (highlighted in

purple) is used to display the panel.

Controls to display the main menu or the information panel on the screen in the downsized browser window

Picture 9

Page 20: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

19

RU 15861920.620111-01 34 01

3.2.1.1. Main menu

Program main menu Picture 10

Program main menu (Picture 10) consists of the following items:

1) ‹Commercial orders› item.

2) ‹Rejection› item.

3) ‹Aggregation› item.

4) Display mode switch

Page 21: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

20

RU 15861920.620111-01 34 01

Display mode switch to Pop-up mode Picture 11

Display mode switch to Docked mode Picture 12

Main menu has two display modes: the Pop-up mode and the Docked mode. To switch

between them, a display mode switch is used (Picture 11 and Picture 12). When the Pop-up mode

is used, the menu only displays item icons (Picture 4), the entire menu displays when it's moused

over (Picture 13) and disappears when the cursor is taken away. In this case, the menu partially

overlaps the data display area.

Program main menu in Pop-up mode Picture 13

Page 22: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

21

RU 15861920.620111-01 34 01

When using the Docked mode, the entire menu displays all the time (Picture 14), and in

this case, the data display area moves to the right without overlapping the menu.

Program main menu in Docked mode Picture 14

Page 23: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

22

RU 15861920.620111-01 34 01

3.2.1.2. Data display area

The data display area is used to input and output the information relating to various

information services of Web Interface Module software complex.

The appearance of the data display area is defined by the selected main menu item (see

clause 3.2.1.1), however, in most cases it contains the tabular data display (Picture 15).

The appearance of the data display area with ‹Commercial orders› item selected Picture 15

3.2.1.3. Information panel

Information panel Picture 16

The information panel (Picture 16) contains the following elements:

1) ‹Swagger documentation› hyperlink; when it is clicked a new web browser window opens

containing the hypertext description for (Picture 6) this API.

2) ‹REST documentation› hyperlink; when it is clicked a new web browser window opens

containing the hypertext description for (Picture 5) this API.

3) ‹Operator› hyperlink intended for exiting the program (see subsection 3.3)

Page 24: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

23

RU 15861920.620111-01 34 01

3.2.2. General interface elements

3.2.2.1. Working with tables

To select data in the table, user must hover the mouse over the desired row which gets

highlighted with a dark grey bar (Picture 17).

Selecting a row in the table Picture 17

If the number of rows exceeds the visible part of the table, it is divided into pages, and

navigation across the pages is performed via the navigation panel (Picture 18) located in the left

bottom corner of the table.

Navigation panel of the table Picture 18

The navigation panel contains ‹<› and ‹>› buttons used to move to the previous or the

next page of the table, and the list of the table pages located between the buttons. The current

page is highlighted with the yellow box. You can single-click to move to the desired page.

Page 25: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

24

RU 15861920.620111-01 34 01

Row View window Picture 19

The user can single-click to open the window where you can view the table row (Picture

19) (in this case, the fields are non-editable), and close it by clicking the ‹Close› button.

‹Create› button for the table Picture 20

If adding rows to the table is available, ‹Сreate› button may be located above the table

(Picture 20).

Page 26: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

25

RU 15861920.620111-01 34 01

Clicking the ‹Create› button opens the window where the row can be added (Picture 21).

Add Row window Picture 21

The Add Row window contains fields to enter data into the new table row, as well as:

1) ‹Save› button; selecting the button adds a row with the data entered into the fields to

the table and closes the window.

2) ‹Close› button; selecting the button cancels adding the row and closes the window.

Page 27: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

26

RU 15861920.620111-01 34 01

3.2.2.2. Methods to fill in the fields

The following methods to fill in the fields are available:

1) A user can enter a value directly into the field.

2) Or, the user can enter a value into the field by selecting it from the drop-down list that

opens by clicking the ‹▼› button in the right area of the field (Picture 22).

Drop-down list with values Picture 22

3) The user can enter a value into the field by selecting it from the calendar (see

subclause 3.2.2.3).

4) The user can enter a value into the field by means of adjusting it using on-screen ‹▼›

and ‹▲› buttons (Picture 23).

Entering values using on-screen ‹▼› and ‹▲› buttons Picture 23

Page 28: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

27

RU 15861920.620111-01 34 01

3.2.2.3. Working with the calendar

To enter dates into various fields on on-screen forms of the program's information

services, a calendar may be used. The calendar window (Picture 24) appears when the

corresponding field is selected.

Calendar window Picture 24

When entering a date from the calendar, the user can:

1) Select the desired day of the month by single-clicking it. In this case, the selected date

is highlighted in yellow, and its value appears in the entry field (Picture 25).

Date entered using the calendar Picture 25

2) Select month using one of the following methods:

− Click the ‹ < › button to select the previous month or click the ‹ > › button to select the

next month.

Page 29: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

28

RU 15861920.620111-01 34 01

− Click the month name to display the list of months, and then click the desired month (in

this case, the month in which the previously entered date resides will be highlighted in

yellow (Picture 26)). After the month is selected, the calendar restores its normal view.

List of months (previously entered date resides in May) Picture 26

3) Select a year in the list of months using one of the following methods:

− Click the ‹ < › button to select the previous year or click the ‹ > › button to select the

next year.

− Click the year row to display the list of years, and then click the desired year (in this

case the year in which the previously entered date resides will be highlighted in yellow

(Picture 27)). After the year is selected, the calendar restores the list of months view.

List of years (previously entered date resides in 2019) Picture 27

Page 30: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

29

RU 15861920.620111-01 34 01

4) Select a decade in the list of years using one of the following methods:

− Click the ‹ < › button to select the previous decade or click the ‹ > › button to select the

next decade.

− Click the decade row to display the list of decades, and then click the desired decade

(in this case, the decade in which the previously entered date resides will be highlighted

in yellow (Picture 28)). After the decade is selected, the calendar restores the list of years

view.

List of decades (previously entered date resides in 2010-2019 decade) Picture 28

5) Select a century in the list of decades using one of the following methods:

− Click the ‹ < › button to select the previous century or click the ‹ > › button to select the

next century.

− Click the decade row to display the list of centuries, and then click the desired century

(in this case, the century in which the previously entered date resides will be highlighted

in yellow (Picture 29)). After the century is selected, the calendar restores the list of

decades view.

Page 31: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

30

RU 15861920.620111-01 34 01

List of centuries (previously entered date resides in 2000 century) Picture 29

Page 32: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

31

RU 15861920.620111-01 34 01

3.2.3. Working with information services

3.2.3.1. Working with the list of commercial orders

To work with the list of commercial orders: select ‹Commercial orders› in the main menu

(see clause 3.2.1.1), then the data display area (see subclause 3.2.1.2) shows the table

containing the list of commercial orders (Picture 30).

Table containing the list of commercial orders Picture 30

Window to view the commercial order (Picture 19) contains the ‹Close› button and blocks

of fields of goods items. The number of blocks in the commercial order view window corresponds

to the number of items in the order (Picture 31 and Picture 32).

Page 33: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

32

RU 15861920.620111-01 34 01

Commercial order view window, the block of fields of the first goods item is highlighted in purple

Picture 31

Commercial order view window, the block of fields of the second goods item is highlighted in green

Picture 32

Page 34: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

33

RU 15861920.620111-01 34 01

Each block of goods item fields contains the following elements:

6) The ‹ID› field that contains system ID of the order.

7) The ‹Goods GTIN› field that contains the ID of the current goods item.

8) The ‹Method of introduction of goods in circulation› field that defines the origin of goods

of the current item.

9) The ‹Number of MCs› field that contains the number of marking codes required for the

current item.

10) The ‹IT type› field that defines the method of marking codes application for the current

item.

11) The ‹Method of serial number creation› field.

12) The ‹Marking type› field that defines the place of marking code application for the

current item.

13) The ‹MC template› field that defines the group of goods for the current item.

New Commercial Order window Picture 33

To create new commercial order (Picture 33), fill the following elements:

1) The ‹Production order ID› field that is filled in using the direct entry method.

Page 35: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

34

RU 15861920.620111-01 34 01

Add Row button Picture 34

2) Fill the table of goods where rows are created using the Add Row button (Picture 34).

Window showing the added row in the table of goods Picture 35

The window that shows the added row in the table of goods (Picture 35) contains the

following elements:

Delete Row button Picture 36

Page 36: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

35

RU 15861920.620111-01 34 01

3) The Delete Row button that you can use to delete the current row from the table of

goods (Picture 36).

4) The ‹ID› field that is filled in automatically and non-editable.

5) The ‹Goos GTIN› field that is filled in using the direct entry method.

The drop-down list of the ‹Method of introduction of goods in circulation› field Picture 37

6) The ‹Method of introduction of goods in circulation› field that is filled in by selecting

items from the drop-down list (Picture 37).

7) The ‹Number of MCs› field that is filled in using on-screen ‹▼› and ‹▲› buttons.

Drop-down list of the ‹IT type› field Picture 38

8) The ‹IT type› field that is filled in by selecting items from the drop-down list (Picture

38).

9) The ‹Method of serial number creation› field that is filled in automatically and non-

editable.

Page 37: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

36

RU 15861920.620111-01 34 01

Drop-down list of the ‹Marking type› field Picture 39

10) The ‹Marking type› field that is filled in by selecting items from the drop-down list

(Picture 39).

Drop-down list of the ‹MC template› field Picture 40

11) The ‹MC template› field that is filled in by selecting items from the drop-down list

(Picture 40).

Button to view the table of goods for the selected order Picture 41

To view the table of goods for the selected order, click the corresponding button in the

left column of the table containing the list of commercial orders (Picture 41).

Page 38: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

37

RU 15861920.620111-01 34 01

The table containing the list of commercial orders. You can view the table of goods for the commercial order in the second row of the table

Picture 42

In the viewing mode of the table of goods for the commercial order (Picture 42) you get

access to the following controls to manage the commercial order:

Hide Table of Goods button Picture 43

1) The button that hides the table of goods (Picture 43).

Page 39: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

38

RU 15861920.620111-01 34 01

‹Close› button Picture 44

2) The ‹Close› button (Picture 44) that deleted the current commercial order from the

orders table.

‹Print› button Picture 45

3) The ‹Print› button (Picture 45) that displays the marking codes printout dialog box for

the current business order.

Marking codes printout dialog box Picture 46

The marking codes printout dialog box (Picture 46) contains the following elements:

Page 40: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

39

RU 15861920.620111-01 34 01

The drop-down list of the ‹Template› field Picture 47

− The ‹Template› field (Picture 47) that is filled in by selecting items from the drop-down

list. The field enables selecting an option to populate printing form with marking codes.

− Non-editable ‹GTIN› field.

− The ‹Quantity› field that is filled in using ‹▼› and ‹▲› on-screen buttons.

− The ‹Print› button that displays a standard web browser dialog box where you can select

parameters for saving marking codes as PDF.

− The ‹Close› button that closes marking codes printout dialog.

Page 41: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

40

RU 15861920.620111-01 34 01

3.2.3.2. Working with the list of notifications on retirement of products rejected by

production department

To work with the list of notification on the retirement of products rejected by the production

department, select ‹Rejection› item in the main menu (see clause 3.2.1.1), after which the data

display area (see subclause 3.2.1.2) shows the table containing the list of notification on the

retirement of the products rejected by production department (Picture 48).

The table with the list of notifications on retirement of products rejected by the production department

Picture 48

Page 42: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

41

RU 15861920.620111-01 34 01

Windows displaying list of notifications on the retirement of rejected products by the production department

Picture 49

Window to view notifications on retirement of products rejected by production department

(Picture 49) contains the following elements in addition to the ‹Close› button:

1) The ‹GTIN / Name› field containing ID and the name of the goods specified in the

notification.

2) The ‹QTY› field that contains the quantity.

3) The ‹Document number› field that contains the rejection notification number.

4) The ‹Document date› field that contains the rejection notification date.

5) The ‹Commercial order ID› field that contains ID of the commercial order for the goods

specified in the notification.

6) The ‹Reason for retirement› field that contains the reason for rejection.

7) The ‹Date and time of saving› field that specifies when the notification was created.

Page 43: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

42

RU 15861920.620111-01 34 01

8) The ‹Date and time synchronized with IS MP› field that specifies the date and the time

of synchronization with IS MP.

9) The ‹Taxpayer ID number› field that defines TIN for the economic agent that performed

rejection.

10) The ‹Address of retirement› field that specifies the location where the retirement of

goods was performed.

11) The ‹Commercial order ID› field

12) The ‹IS MP synchronization results› field that specifies the final outcome of

synchronization with IS MP.

13) The ‹Details› field that contains additional information about rejection.

Page 44: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

43

RU 15861920.620111-01 34 01

The window that displays the added row in the table containing the list of notifications on the retirement of the products rejected by production department.

Picture 50

The window that shows the added row in the table of goods (Picture 50) contains the

following elements:

1) The ‹Add code› field that is filled in using the direct entry method.

2) The ‹GTIN / Name› field that is filled in automatically and non-editable.

3) The ‹QTY› field that is filled in automatically and non-editable.

4) The ‹Document number› field that is filled in using the direct entry method.

5) The ‹Document date› field that is filled in by selecting the date from the calendar (see

subclause 3.2.2.3).

6) The ‹Production order ID› field that is filled in using the direct entry method.

Page 45: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

44

RU 15861920.620111-01 34 01

Drop-down list for the ‹Reason for retirement› field Picture 51

7) The ‹Reason for retirement› field that is filled in by selecting items from the drop-down

list (Picture 51).

8) The ‹Date and time of saving› field that is filled in automatically and non-editable.

9) The ‹Date and time of synchronizing with IS MP› that is filled in automatically and non-

editable.

10) The ‹Taxpayer ID number› field that is filled in using the direct entry method.

11) The ‹Address of retirement› field that is filled in using direct entry mode.

12) The ‹Commercial order ID› field that is filled in using direct entry mode

13) The ‹IS MP synchronization results› field that is filled in automatically and non-

editable.

14) The ‹Details› field that is filled in using the direct entry method.

Page 46: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

45

RU 15861920.620111-01 34 01

3.2.3.3. Working with the list of notifications on aggregation

To work with the list of notifications on aggregation, you must select the ‹Aggregation›

item in the main menu (see clause 3.2.1.1), after which the data display area (see subclause

3.2.1.2) shows the table containing the list of notifications on aggregation (Picture 52).

The table containing the list of notifications on aggregation Picture 52

Page 47: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

46

RU 15861920.620111-01 34 01

The window displaying notifications on aggregation Picture 53

The window displaying notifications on aggregation (Picture 53) contains the following

elements in addition to the ‹Close› button:

1) The ‹Aggregate MC› field

2) The ‹GTIN / Name› field containing ID and the name of the goods specified in the

notification.

3) The ‹QTY› field that contains the quantity

4) The ‹Production line number› field that defines the place where the goods specified in

the notification were manufactured.

Page 48: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

47

RU 15861920.620111-01 34 01

5) The ‹Commercial order ID› field that contains ID of the commercial order for the goods

specified in the notification.

6) The ‹Actually packed› field that contains the number of packed goods specified in the

notification.

7) The ‹Package capacity› field that specifies the number of products from the notification

that can be packed into a standard package.

8) The ‹Production line ID› field that defines the place of origin for the goods specified in

the notification.

9) The ‹Date and time of saving› field that specifies when the notification was created.

10) The ‹Date and time synchronized with IS MP› field that specifies the date and time of

synchronization with IS MP.

11) The ‹IS MP synchronization results› field that specifies the final outcome of

synchronization with IS MP.

12) The ‹Taxpayer ID number› field that defines TIN for the economic agent that

performed aggregation.

Page 49: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

48

RU 15861920.620111-01 34 01

The window displaying the added row in the table containing the list of notifications on aggregation Picture 54

To add the row to the table containing the list of notifications on aggregation, click the

‹Aggregation› button, which is located above the table. You'll see the window containing the

added row (Picture 54) and the following elements:

Clear Codes button Picture 55

1) The Clear Codes button (Picture 55).

Page 50: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

49

RU 15861920.620111-01 34 01

2) The ‹Aggregate MC› field that is filled in using the direct entry method.

3) The ‹Add code› field that is filled in using the direct entry method.

4) The ‹GTIN / Name› field that is filled in automatically and non-editable.

5) The ‹QTY› field that is filled in automatically and non-editable.

6) The ‹Production line number› field that is filled in using the direct entry method.

7) The ‹Production order ID› field that is filled in using the direct entry method.

8) The ‹Actually packed› field that is filled in using the direct entry method.

9) The ‹Package capacity› field that is filled in using the direct entry method.

10) The ‹Production line ID› field that is filled in using the direct entry method.

11) The ‹Date and time of saving› field that is filled in automatically and non-editable.

12) The ‹Date and time of synchronizing with IS MP› that is filled in automatically and

non-editable.

13) The ‹IS MP synchronization results› field that is filled in automatically and non-

editable.

14) The ‹Taxpayer ID number› field that is filled in using the direct entry method.

The ‹Re-aggregation› button Picture 56

Each table row that contains the list of the notifications on aggregation, contains the ‹Re-

aggregate› button in the last column. Clicking the button (Picture 56) opens the re-aggregate

window to display the corresponding notification (Picture 57).

Page 51: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

50

RU 15861920.620111-01 34 01

Notification re-aggregation window Picture 57

The interface of the notification re-aggregation window (Picture 57) is similar to the

window where you can add the row to the table containing the list of notifications on aggregation

(Picture 54),

Page 52: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

51

RU 15861920.620111-01 34 01

3.3. Completing program

To complete the program, click the ‹Operator› hyperlink in the right pane of the

information panel. After that, the pop-up menu appears where you must select ‹Exit account›

option (Picture 58).

‹Operator› hyperlink pop-up menu Picture 58

After you select the ‹Account exit› option, your program session is over, and an on-screen

login form appears (Picture 3). After that, you may close your web browser using any valid

method. No additional action is required to unload the program from OMS Operator AWP RAM.

Page 53: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

52

RU 15861920.620111-01 34 01

4. Messages to operators

4.1. Messages to operators transmitted via GUI

4.1.1. Information windows

If any errors occur in the course of program execution, the web browser window displays

a red pop-up window containing two message types:

1) Program entry error message (Picture 59).

Program entry error message Picture 59

2) System error message (Picture 60).

System error message Picture 60

Page 54: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

53

RU 15861920.620111-01 34 01

LIST OF TERMS

This document uses the following terms:

1) Computing tools (CTs) – PC (personal computer) or any other computing equipment

(mainframe, mini PC, micro PC, pocket PC, computer terminal).

2) Individual user's CTs – computing equipment that ensures:

− automation for the computing component of daily activities of the Customer's

employees;

− access to information services that provide automation for business workflow across

the Customer's company.

3) Multiple-access CTs – computing equipment intended for:

− arrangement of a computing platform that enables automation of Customer's business

workflow;

− controlling and configuring CTs that are part of the automated system;

− accumulation and processing of data used for automation of Customer's business

workflow.

4) General software – a collection of software components that provides CTs minimum

functionality:

− an environment to launch and operate the rest of the software components (operating

system);

− tools for working with structured data sets (DBMS);

− tools to access Internet resources (web browser);

− tools to publish CTs resources on the Internet (web server).

5) Specialized software – a collection of software components that are specifically

developed for this particular CT (not an "out-of-the-box SW").

Page 55: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

54

RU 15861920.620111-01 34 01

6) End devices – devices managed by the automated system directly (via information and

communication links) or indirectly (via the functional interface with the allied systems),

and intended to perform technological functions (printer, scanner, monitor, controller,

etc.).

Page 56: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

55

RU 15861920.620111-01 34 01

LIST OF ABBREVIATIONS

AWP Automated workplace AS Automated system ATPMS Automated technological process management system IS Information security IS MP Track & trace information system for marking products MC Marking code HCS Hardware components set LAN Local area network UAA Unauthorized access LAN Local area network ED End devices OS Operating system GSW General software SW Software HSC Hardware and software complex PC Personal computer OM Operations monitor EM Emission monitor AVP Anti-virus protection CT Computer tool IT Identification tools SCS Structured cabling system IPT Information protection tool SSW Specialized software NIT Network interface tools OMS Order management station ES Emission server ToR Terms of reference TC Test computer

Page 57: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

56

RU 15861920.620111-01 34 01

LIST OF PICTURES

Picture 1 ....................................................................................................................................... 5

Picture 2 ....................................................................................................................................... 7

Picture 3 ..................................................................................................................................... 14

Picture 4 ..................................................................................................................................... 15

Picture 5 ..................................................................................................................................... 16

Picture 6 ..................................................................................................................................... 16

Picture 7 ..................................................................................................................................... 17

Picture 8 ..................................................................................................................................... 18

Picture 9 ..................................................................................................................................... 18

Picture 10 ................................................................................................................................... 19

Picture 11 ................................................................................................................................... 20

Picture 12 ................................................................................................................................... 20

Picture 13 ................................................................................................................................... 20

Picture 14 ................................................................................................................................... 21

Picture 15 ................................................................................................................................... 22

Picture 16 ................................................................................................................................... 22

Picture 17 ................................................................................................................................... 23

Picture 18 ................................................................................................................................... 23

Picture 19 ................................................................................................................................... 24

Picture 20 ................................................................................................................................... 24

Picture 21 ................................................................................................................................... 25

Picture 22 ................................................................................................................................... 26

Picture 23 ................................................................................................................................... 26

Picture 24 ................................................................................................................................... 27

Picture 25 ................................................................................................................................... 27

Page 58: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

57

RU 15861920.620111-01 34 01

Picture 26 ................................................................................................................................... 28

Picture 27 ................................................................................................................................... 28

Picture 28 ................................................................................................................................... 29

Picture 29 ................................................................................................................................... 30

Picture 30 ................................................................................................................................... 31

Picture 31 ................................................................................................................................... 32

Picture 32 ................................................................................................................................... 32

Picture 33 ................................................................................................................................... 33

Picture 34 ................................................................................................................................... 34

Picture 35 ................................................................................................................................... 34

Picture 36 ................................................................................................................................... 34

Picture 37 ................................................................................................................................... 35

Picture 38 ................................................................................................................................... 35

Picture 39 ................................................................................................................................... 36

Picture 40 ................................................................................................................................... 36

Picture 41 ................................................................................................................................... 36

Picture 42 ................................................................................................................................... 37

Picture 43 ................................................................................................................................... 37

Picture 44 ................................................................................................................................... 38

Picture 45 ................................................................................................................................... 38

Picture 46 ................................................................................................................................... 38

Picture 47 ................................................................................................................................... 39

Picture 48 ................................................................................................................................... 40

Picture 49 ................................................................................................................................... 41

Picture 50 ................................................................................................................................... 43

Picture 51 ................................................................................................................................... 44

Page 59: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

58

RU 15861920.620111-01 34 01

Picture 52 ................................................................................................................................... 45

Picture 53 ................................................................................................................................... 46

Picture 54 ................................................................................................................................... 48

Picture 55 ................................................................................................................................... 48

Picture 56 ................................................................................................................................... 49

Picture 57 ................................................................................................................................... 50

Picture 58 ................................................................................................................................... 51

Picture 59 ................................................................................................................................... 52

Picture 60 ................................................................................................................................... 52

Page 60: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

59

RU 15861920.620111-01 34 01

LIST OF TABLES

Table 1 List of allied systems ....................................................................................................... 8

Page 61: APPROVED BY CEO of 2019. of 2019.€¦ · The document is developed in compliance with GOST 19.505-79 "Unified software documentation system. Operator's manual". This document uses

60

RU 15861920.620111-01 34 01

Revision record sheet

Sheet (page) numbers

Total sheets (pages) in the doc.

Document No. Accompanying

doc. ref. No. and date

Sign. Date Rev.

of modified of replaced of new of cance-lled