A document specifying the system requirements approved by both the customer and the contractor
GENERAL INFORMATION
a) full name of the system and reference designation; b) subject code or contract reference (number); c) system developer and customer (user) and their company details; d) list of the reference documents used, who approved the documents and when; e) expected start and end dates (system development); f) information about the funding sources and procedures; g) a performance reporting procedure allowing to report to the Customer on the progress with the system (or its parts), as well as separate hardware or software modules.
PURPOSE OF THE SYSTEM AND WHY IT IS CREATED (DEVELOPED)
a) the purpose of the system (the application is to be specified: management, engineering, etc.) and a list of sites where the system will be deployed; b) why the system is created; For control systems, the control stations/points and control objects are to be specified additionally.
SITE DESCRIPTION
a) a brief description of the site or references to documents containing such information; b) information about the operation conditions and the environment. Note: For CAD systems, the key parameters and characteristics of design objects should be specified additionally.
SYSTEM REQUIREMENTS
a) general system requirements; b) functional requirements; c) support requirements. System requirements to be included in this section shall be defined by the type, purpose, features and operating environment of a particular system.
WORK SCOPE
a) пa list of documents per GOST 34.201 that are to be provided upon completion of particular stages and phases; b) вthe type of document examination and the applicable procedure (stage, phase, the scope of documentation to be checked, expert organization); c) a work plan aimed at ensuring the required level of system reliability (if necessary); d) a plan of metrological support for each stage of system development specifying deadlines and responsible entities (if necessary).
TESTING AND ACCEPTANCE PROCEDURE
a) the scope and methods of testing applicable to the system and its components (the tests applied should comply with the applicable regulations); b) general by-stage acceptance requirements: a list of participating organizations, the place and dates; acceptance certificate approval procedure; c) the status of the acceptance commission: a state commission, a ministerial commission, an inter-ministerial commission.
WORK SCOPE REQUIRED TO PREPARE THE SITE FOR THE SYSTEM COMMISSIONING
a) all the incoming information (compliant with the requirements set to the information and linguistic support) should be converted in the format processible by the computer; b) the changes that need to be implemented at site; c) an operating environment should be established that will ensure the system compliance with the requirements specified in the Statement of Work; d) necessary support departments and services should be established; e) staffing and training dates and procedure.
DOCUMENTATION REQUIREMENTS
a)a list of documents to be elaborated per GOST 34.201 and the applicable industry regulations that was agreed on by the system developer and the customer; a list of documents to be issued on media; microcopying requirements; b) тdocumentation requirements applicable to system components designed for cross-sectorial application per the Unified System for Design Documentation and the Unified System for Software Documentation; c) п If there are no state documentation standards applicable to system components, such documentation requirements shall be included additionally.
DEVELOPMENT SOURCES
here should be references given to feasibility studies, R&D reports, reference information on similar systems developed in-country and abroad, etc. that were used as the basis for the Statement of Work and that should be used for system development.
24/7
SUPPORT
EXPECT
RESULTS!
EVGENY KHRENOV
The head of industrial cyber physical systems department +7 (982) 300-01-31
