2.0 Business Process

Capture the business process that the application supports . This can be describe through a process diagram or a business capability model

The MEDEXIS report captures an assessment of each employees Occupational Health and Occupational Diseases across multiple countries/sites. This is reflected in the Annual Report, which each Solvay’ site has to prepare regarding the health of  their employees

• Report are available in different language
• Language of the health center (attribute of the health center)
• Accessible via Solia portal

Process Diagram

Occupational Health (OH) Annual reports are created manually for each country. There is no standardized OH Annual report for all countries but each country has its own layout.  

Some indicators have to develop in order to get possibility to do prevention in each health center.

OH Annual Reports will be created using BW.

Process Documentation:

3.0 Application Feature Overview

Information about the existent Workbooks and the respective BW queries.

Reports are executed via Solia portal. Each IVIEW contains Web Application containing one or more queries (contact to modify Solia links is Jose Cervera).

The Language of the report depends on the language of the healthcenter (C_HEALCTR-LANGU). 
This is defined in the customer exit (CMOD) of Bex variable V_HEALTHCTR_EXIT_0001.

Reports display data from current year to Current Year – 2.

List of queries

• Occupational Diseases of last 3 years
• Annual reports
• List of Annual Reports

• Data Management
• Audiometry (WHO) report example

4.0 Functional Specification

4.1 General Data/Calculations 

This section will approach the concepts/definitions that will be used in all the reports and required to understand the data from the reports.

Could be specific fields, closing activities, additional information to work and understand the reports.

• Employee can have only one health center during the same time (T7EHS00_PERHAL)
• Employee can have one or more GBU during the same time (PA9907 -ZZENG)
• Employee can have one or more segment

     during the same time (HRP1001)

GBU

Employee

Health center

SEG

Data Flow:

4.2 Process Detail 

4.2.1.  Report/Process Definition 

This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.

MVEHOH01: Particularity

• Get Indicators
• Protocols
• Vaccinations
• Aptitude advice (Restriction) 
• Medical Services

MVEHOH02: Examinations

• Gets Indicators
• Examination
• Audiometry Examination
• Respiratory Examination
• Vision Examination
• Clinic Examination
• Biometry Examination
• Vaccination by Examination

MVEHOH03: Diagnosis

• Gets Indicators related to the diagnosis in health center

MVEHOH04: Assignment  Employee

• Get Indicator
• Number of worker assigned to the health center
• Number of worker assigned to the GBU
• Number of worker assigned to the WorkArea

5.0 Non-functional Descriptions 

5.1 Usability

Usability is about the ease with which a User can learn to start using the solution and the ease with which they can use the system.  In addition to ease of learning and ease of use, usability also includes areas such as ease of recall, error avoidance and handling, accessibility among others e.g., 99% of metadata entry Users who have use the Maintenance Dashboard should be able to change filters, extract etc., when required.  Maintenance data will be centrally stored in the Google Cloud platform, which will be available to other applications e.g., and Dashboards if needed.

5.2 Regulatory Compliance

Software systems must comply with legal and regulatory e.g., GDPR requirements, this can change depending on country, organisation industry and / or region.  The software systems must be secure from unauthorized access.  The Maintenance Dashboard will comply with Solvay’s regulations and compliance e.g., access only granted to authorized Users.

5.3 Security

Security refers to essential aspects that assure a solution and its components will be protected against unauthorized access or malware attacks.  Important considerations related to security aspects of a system are User authentication, User authorization or User access privileges, data theft, malware attacks, data encryption, and maintaining audit trails, e.g., only Users with administrator access shall be able to create new accounts and assign data access privileges to the new accounts e.g.,

• All data will be encrypted in the dashboard
• Only authorised Users / Administrative Users will be able to access data.
• Maintenance data will be split between either SCO or ECO, and Users will only have authority to one Entity data.

5.4 Performance

Performance defines how fast a software system or a particular section of it responds to certain User actions under a certain workload.  In most cases, this metric explains how long a User must wait before the target operation happens e.g., the page renders, a transaction is processed, etc., given the overall number of Users now.  Performance requirements may describe background processes invisible to Users, e.g., backup and speed of data transfers. 

5.5 Reliability

Reliability is the ability of a solution or its component to perform its required functions without failure under predefined conditions for a specified time / period.  Reliability can possibly be specified in terms of average time system runs before failure occurs, percentage of operations completed successfully within a time / period, maximum acceptable failure probability, or number of failures within a period.  Reliability aspects are in reference to (but not limited to) evaluation of the system to be considered as reliable, classification of reliability defining failures vs. regular failures, and the impact of failure on business operations.  The Maintenance Dashboard will display data from the previous refresh of data.   

5.6 Scalability

Scalability refers to the degree to which a solution can evolve to handle increased amounts of work.  The increased amount of work could be in terms of the user base, transactions, data, network traffic, or other factors e.g., the system should be able to handle an additional load of a maximum of 5,000 Users every month for the next 6 months without any noticeable performance impacts.  

5.7 Compatibility

Interoperability is the degree to which the solution is compatible with other components.  It is a measure of how effectively the system interoperates with other software systems and how easily it integrates with external hardware devices.

Interoperability aspects to be discussed during elicitation are in reference to (but not limited to) software systems to be interfaced with along with data / messages to be exchanged and any standard data formats, hardware components to be integrated with, and any standard communication protocols to be followed e.g., Order Management system will push the order file into a secured file transfer protocol server from where it will be loaded into the system through a daily job.  To guarantee between Google Cloud platform and SAP BW Queries e.g., BW_QRY_MVPMOR01_0002, Solvay has introduced a new tool called Xtract (Xtract).

5.8 Availability

Availability is the degree to which the solution is operable and accessible when required. It is a measure of time during which the system is fully operational e.g., available for use and sometimes included as a Service Level Agreement (SLA) considering its criticality to the business, e.g., the system shall be at least 99% available on weekdays between 09:00 to 18:30 Central European Time (CET).

5.9 Refresh of the Data

Frequency, data, and time of the data refresh in the data product.