Employee App “ETO-App”Software Requirements SpecificationV 2.1
Revisions HistoryRevisions Name Comments Date  (YYYY-MM-DD)
1 Shashank Raj Created draft version 2020-09-14
2 Shashank Raj Updated as per discussion: V2.0 2020-10-20
3 Shashank Raj Updated as per discussion: V2.1 2020-12-21
Related Documents Title Path 1 Employee App "ETO-App" Specification v1.4 https://asset1.basecamp.com/3018222/projects/
17593813/attachments/414283786/
EmployeeApp_Specification_en_29_07_2020_v1_4.pdf
2 Q and A_FuGenX_ETO.pdf https://asset1.basecamp.com/3018222/projects 
/17593813/attachments/417245793
/Q%20and%20A_FuGenX_ETO.pdf
3 2020-10-06_Screenshots.pdf https://asset1.basecamp.com/3018222/projects /17593813/attachments/417245794
/2020-10-06_Screenshots.pdf
4 Screenshots_Teams.pdf https://asset1.basecamp.com/3018222/projects /17593813/attachments/417574616
/Screenshots_Teams.pdf
5 ETO Employee App - Modification Requests https://asset1.basecamp.com/3018222/projects
/17593813/attachments/422856786/
ETO_Emp_App_SRS_Modification_Response.docx
Table of Contents
 TOC \o "1-3" \h \z \u Employee App “ETO-App” PAGEREF _Toc59468289 \h 1Software Requirements Specification PAGEREF _Toc59468290 \h 1Revisions History PAGEREF _Toc59468291 \h 11.Administrative Data PAGEREF _Toc59468292 \h 42.Customer Context and Justification PAGEREF _Toc59468293 \h 43.Scope PAGEREF _Toc59468294 \h 44.Functional Analysis PAGEREF _Toc59468295 \h 54.1 Teams PAGEREF _Toc59468296 \h 54.2 Roles: PAGEREF _Toc59468297 \h 54.2.1 Administrator Team: PAGEREF _Toc59468298 \h 54.2.2 Team Admin: PAGEREF _Toc59468299 \h 64.2.3 Team Members / Normal Users: PAGEREF _Toc59468300 \h 64.3 End Users: PAGEREF _Toc59468301 \h 64.4 Walls and Posting: PAGEREF _Toc59468302 \h 74.4.1 Walls PAGEREF _Toc59468303 \h 74.4.2 Posts: PAGEREF _Toc59468304 \h 74.5 Dashboards PAGEREF _Toc59468305 \h 104.5.1. Self-Dashboard / My Profile PAGEREF _Toc59468306 \h 104.5.2 Other Dashboards / Admin Section: PAGEREF _Toc59468307 \h 124.6 User Management - SAP Data Import &amp; Login PAGEREF _Toc59468308 \h 184.6.1 Import Users: PAGEREF _Toc59468309 \h 184.6.2 Create a User: PAGEREF _Toc59468310 \h 184.6.3 Generate initial login credentials: PAGEREF _Toc59468311 \h 194.6.4 Initial Login PAGEREF _Toc59468312 \h 194.6.5 Login PAGEREF _Toc59468313 \h 194.6.6 Login Expiration Time PAGEREF _Toc59468314 \h 194.6.7 Authentication for mobile app: PAGEREF _Toc59468315 \h 194.7 Calendar and Contacts PAGEREF _Toc59468316 \h 204.7.1 Calendar: PAGEREF _Toc59468317 \h 204.7.2 Contacts/Address book: PAGEREF _Toc59468318 \h 204.8 Recruitment Management PAGEREF _Toc59468319 \h 214.8.1 Add Recruitment Info: PAGEREF _Toc59468320 \h 214.9 Help &amp; Support PAGEREF _Toc59468321 \h 214.9.1 Support Type: PAGEREF _Toc59468322 \h 214.9.2 Contact Group Management: PAGEREF _Toc59468323 \h 224.9.3 Create a help ticket: PAGEREF _Toc59468324 \h 224.10 Google Maps view: PAGEREF _Toc59468325 \h 224.10.1 Locations of ETO Gruppe: PAGEREF _Toc59468326 \h 224.10.2 View list of office address: PAGEREF _Toc59468327 \h 224.10.3 View Plant Location on Google Map: PAGEREF _Toc59468328 \h 224.11 Links for SAP Fiori: PAGEREF _Toc59468329 \h 234.11.1 Send new Idea PAGEREF _Toc59468330 \h 234.12 Multiple Language Support PAGEREF _Toc59468331 \h 234.12.1 List of Required Languages: PAGEREF _Toc59468332 \h 234.12.2 Menus and Functions: PAGEREF _Toc59468333 \h 234.12.3 Translation Support for Posts: PAGEREF _Toc59468334 \h 234.12.4 Support for a New Language: PAGEREF _Toc59468335 \h 244.13 Search for Posts and Employees: PAGEREF _Toc59468336 \h 245.List of Reviewers PAGEREF _Toc59468337 \h 256.Approval PAGEREF _Toc59468338 \h 25

Administrative DataParameter Value
Customer ETO GRUPPE
Country Germany
Analysis baseline Employee App "ETO-App" Specification v1.4
Project Code Employee App
Customer Context and JustificationThe project “Employee App” called ETO-App enumerates to a web and mobile based applications, which should allow employees of ETO GRUPPE to use various features like Dashboards, Teams, Calendar, Contacts, Chat with other employees and publish news in a bulletin board. The vision also includes various facilities for top management, where they can control content or other important settings based on their roles.
ScopeThis functional analysis describes features which Employee App should have in order to enable ETO GRUPPE to use the basic employee management facilities, without the need of either a workstation or compulsory presence in the company premises for accessing. The layout should be more or less same as corporate design and detailed corporate identity of the ETO GRUPPE.
Functional Analysis4.1 TeamsA team is a group of people who can share similar type of content or functionality. 
For example: To share information on a topic among only intended employees or relevant people.
The application has total 9 predefined teams, 1 global (for entire organization) and rest 8 are based on locations for different requirements. 
Team ETO GRUPPE (all employees of ETO)
Team ETO Stockach (all employees from location Stockach)
Team ETO Nuremberg (all employees from location Nuremberg)
Team EKS Vaihingen/Enz (all employees from location EKS/Vaihingen)
Team ETO Wroclaw (all employees from location Poland)
Team ETO Kunshan (all employees from location China)
Team ETO Bengaluru (all employees from location India)
Team ETO Grand Rapids (all employees from location USA)
Team ETO San Luis Potosi (all employees from location Mexico)
4.2 Roles:There are multiple roles viz. Super Admin, Top Admin, Team Admin, Team Members.
4.2.1 Administrator Team:There is an Administrator Team, which consists of two types of Admins named "Super Admin" and "Top Admin". There may be only one Super Admin (Head of the Admins, viz. CEO) and many Top Admins (other corresponding authorities). Difference between Super Admin and Top Admin is that a Super Admin can create/manage Top Admins but Top Admins cannot create/manage other Top Admins. Rest all the features/rights are same for Super Admin and Top Admins.
4.2.1.1 Rights of Administrator Team:
Administrator Team (Super Admin and Top Admins) should be able to manage teams, walls, posts, dashboards, calendars, contacts, recruitments and contact groups for help. They can also add new users, add/assign members to a team, remove users, add or remove Team Admin.
4.2.2 Team Admin:A team is a group of people who can share similar type of content or functionality. Admin for a Team is called Team Admin. There may be one or more Team Admin in a team. Administrator Team can manage Team Admin.
4.2.2.1 Rights for Team Admin
A Team Admin can create contents/posts for a team. 
A Team Admin should also be able to assign role of Team Admin to one or more team members within a team. 
A Team Admin shall be able to send requests to Administrator Team for posting/removing content. The selected top admins or/and super admin should be able to confirm or reject the requests. Every requested Administrator Team Members should approve or reject the request. Reason of rejection (optional field) may be provided for later reference.
4.2.3 Team Members / Normal Users:Members of a Team are called Team Members. They are Normal Users (Employees) having least privilege. Apart from using other features of the application, generally they can read posts from all walls (of which they have been given access). There is one wall called "Social Wall" where they can also post a content. Every content must be approved by one or more Administrator Team Members ("Super Admin" and "Top Admin").
4.3 End Users:The application can be used by all active employees of the organization. It should support deletion of user data permanently as required when an employee leaves the organization.
4.4 Walls and Posting:4.4.1 WallsA wall is a center to exchange information or news etc. Employees of corresponding Team should be able to see content of the Wall.
By default, intent of a wall is to share information among members of a team. Intent of team is to group employees interested in specific set of information or location. Authorized Team Admin should be able to create a content for corresponding team. Only corresponding Team Members should be able to view content of those teams on the walls.
- The application should have 3 pre-defined walls: GRUPPE News, Location News and Social wall. 
- Users should be able to like and comment on any post of Location News and Social wall but not on GRUPPE News wall. 
- On "Social Wall" all corresponding users should be able to post content as well as like and comment.
- There shall be a wall/page related to "Canteen Menu". Entitled Team Admins should be able to upload a content as a PDF file. Entitled Team Members should be able to view the content. Users should not be able to like, or comment on the posts in this wall.
- There shall be a wall related to "Location Specific". Entitled Team Admins should be able to upload a content as a PDF file. The file may contain information about the plant location plan, fire escape plan, and work safety. Users should not be able to like, or comment on the posts in this wall.
- The administrator team shall be able to approve/disapprove or delete content on any of the walls.
4.4.2 Posts:A Post is a content or information to be shared within a team. It can contain Text, Images, PDF Files and video clips.
4.4.2.1 Create a Post:
A Post can be created by a Team Admin. To create a Post, Team Admin may have to provide Title of The Post, Body/Description of the Post, attachments (if any), List of approvers (one or more members of Administrator Team), Scheduled Post Date (to start display on a specific date, if preferred), Request to be Pinned.
A post can have more than one media files. There may be different media files in one post. There should not be maximum length of a post.
4.4.2.2 Approval of a Post
A Post should be approved by any one of the approvers (who were requested to approve) in order to be published. Approval from only one approver is sufficient. There is no need of getting approval from everyone. 
If rejected by any approver then it may not be published. Reason of rejection (optional field) may be provided for later reference.
4.4.2.3 Notification for Pending Approval:
Administrator Team should get notifications whenever a post is pending approval.
4.4.2.4 Content type of a Post:
A post should support following data:
Text-data
Image-data (also "multiple images") 
Embedded-Code 
Video-data and 
PDF-data
4.4.2.5 Preview a Post:
Team Admin and Administrator Team should be able to preview the content of a post before posting. Preview of a Post should be available only to the web-based application. Preview of the post is to understand how the post may appear in the "Mobile-Version" of the application. The preview may appear in a side space or a popup.
4.4.2.6 Like, Un-like and Comment:
All users should be able to like and comment on all posts on Location News and Social walls whose access has been provided to the user based on location.
4.4.2.6.1 Like a Post
A user can Like a Post to show his interest in the Post Content.
A user should be able to click on a Like Button for a Post to like it. Beside a Like button there should be number of people who have liked the post. 
4.4.2.6.2 Dislike a Post
A user can Dislike a Post if he dislikes the Post Content.
A user should be able to click on a Dislike Button for a Post to dislike it. Beside Dislike button there should be number of people who have disliked the post. 
4.4.2.6.3 View Comments of a Post
A user should be able to view comments on a Post made by users. Comments are single level. No user can give reply to other comments as a thread.
4.4.2.6.4 Comment a Post
A user can comment on a Post to share more info about the Post Content of Location News and Social wall. A comment needs no approval to be published. Users should not be able to like and comment on any post of GRUPPE News wall.
4.4.2.7 Posts of deleted user:
Posts (created by a user) should still be displayed even the user has been deleted from the system.
If the user has been removed from the system, the comments and posts of the user should remain intact. The username and photo shall be replaced with a default user photo and user name.
4.4.2.8 Notifications:
The application should be able to send notification via the "push notification" channel. The local device settings for app notifications may determine if the notification pops up. Users should have the possibility to mute notifications.
4.4.2.9 Delete a Post:
Only Administrator Team can delete a Post. 
A Team Admin can request Administrator Team to delete his post.
Type of Deletion of Post should be a soft delete. Therefore, a deleted post will still remain in the database though it will not be visible to users. 
4.4.2.10 Pin/Unpin posts
A Post can be pinned or un-pinned as per its importance and priority to be displayed in a wall. 
4.4.2.10.1 Pinned Post:
A Pinned Post is a post which would always come at the top of a particular wall as the first Post.
4.4.2.10.2 Pinning a Post
A Team Admin can request/suggest for a Post to be "Pinned" while creating a Post.
Only one post can be pinned at a time for each GRUPPE News, Location News and Social wall.
For Social wall, Administrator team members need to have facility to pin a post on “Social Wall” also. Only one post can be pinned at a time. End user/Employee should not be able to request for any post to be pinned.
4.4.2.10.3 Un-Pinning a Post
A Team Admin can request/suggest to Administrator Team for a Post to be "Un-Pinned".
Only Administrator Team can un-pin a post.
When a post becomes un-pinned then it should be listed as a general post based on its scheduled date and time or date of approval. A post should always be listed based on scheduled date (if exists). If scheduled date in not available then it should be listed based on date of approval.
4.4.2.11 Scheduling a Post
A post can be scheduled to appear on a wall on a specific time. If a Post is not scheduled specifically then it may appear in the wall as per the date of approval.
4.4.2.11.1 Request for Scheduling a Post
A Team Admin can request to schedule a Post while creating it. He can select a future date time for scheduling the Post. Posts for Social wall cannot be scheduled.
4.4.2.11.2 Approval for Scheduling a Post
Administrator Team can also approve a scheduled date/time of a Post while approving a Post. While approving a Post (to be published), the Post information may also contain requested scheduled time. 
4.5 DashboardsA Dashboard is a page where a user can view multiple key information as per his role.
4.5.1. Self-Dashboard / My ProfileHere the user should be able to view, add, modify or remove his information, as applicable.
All information related to an employee can be put into two buckets (Private and Public) as per their default access level.
4.5.1.1 Private Information
Information of an employee which is not shared with everyone in the organization is referred as his Private Information. It is visible to the logged in Employee and Administrator Team. It can be of two types:
4.5.1.1.1 Editable Private Information
The user shall be able to view, edit their personal details like telephone number, contact address, qualifications, certifications, emergency contact details. This content is private and editable by the user.
The user shall be able to upload documents like images, PDFs. These documents can be their public identification documents like passports, social security cards, insurance cards, etc. This content is private and is editable by the user.
4.5.1.1.2 Non-Editable Private Information
There is no private information which is non-editable.
4.5.1.2 Public Information
Information of an employee which is shared with everyone in the organization is referred as Public Information. Everyone can view this information. It may also be of two types:
4.5.1.2.1 Editable Public Information
The user shall be able to view, change, edit, and remove their own profile photo. This photo shall be visible to all users. This content is public and editable by the user.
4.5.1.2.2 Non-Editable Public Information
The user shall be able to view their name, designation, employee ID, official telephone number and company e-mail address. This content is public and shall not be editable by the user.
4.5.1.3 Modify Access Level
An employee can modify access level of his information from Private to Public.
4.5.1.3.1 Make an information Public
A Private information can be made Public if the user wants it to be visible and shared with other people.
There may be a checkbox or a button which helps an employee to make a particular information public.
It can again be made Private by the Employee, if needed.
4.5.1.3.2 Make an information Private
A Private Information which was made public by an employee, only that again be made Private.
i.e. Restoring its original access level.
An originally public information cannot be made Private.
Only an employee can change default access level of his information.
4.5.2 Other Dashboards / Admin Section:These dashboards or pages are mainly used for Administrative purposes by Team Admin and Administrator Team as applicable. There may also be some pages available to general users/employees to view.
4.5.2.1 Team Management:
Here Administrator Team, Team Admin and Employee use features related to Teams.
4.5.2.1.1 View list of Teams:
An Administrator Team member should be able to view list of all Teams.
A Team Admin should be able to view list of all Teams for which he is a Team Admin.
4.5.2.1.2 View Details of a Team:
An Administrator Team member should be able to view information related to all Teams.
A Team Admin should be able to view limited information of all Teams for which he is a Team Admin.
4.5.2.1.3 Create a team:
The application should have only 9 teams which should be pre-defined. Teams should not be created dynamically.
4.5.2.1.4 Add users to a team:
Only Administrator Team can add one or more users to a Team. An active employee from corresponding location can be added to a Team. 
4.5.2.1.5 Remove users from a team:
Only Administrator Team can remove one or more users from a Team.
When a user is removed from a team then he should lose access to corresponding wall from the list of his walls.
4.5.2.1.6 Add a new Team Admin:
There may be multiple Team Admins in a Team.
A Team Admin should be able to create another Team Admin from list of the team members.
Administrator Team can also create another Team Admin from list of the team members or by adding a new Team Member.
4.5.2.1.7 Remove a Team Admin:
There must be at least one Team Admin in a Team.
Only Administrator Team can remove a Team Admin from a Team. If there is only one Team Admin then Administrator Team should add another Team Admin before removing the first.
4.5.2.1.8 Remove a team:
The application has all required pre-defined teams therefore, they cannot be deleted by anyone.
4.5.2.2 Manage Posts:
Here Administrator Team, Team Admin and Employee use features related to Posts.
4.5.2.2.1 View list of Posts:
An Administrator Team member should be able to view list of all Posts.
A Team Admin should be able to view list of all Posts created for his team. It includes post created by him or other Team Admins of the team.
4.5.2.2.2 View Details of a Post:
An Administrator Team member should be able to view information related to all Posts.
A Team Admin should be able to view limited information of all Posts of his team. It includes post created by him or other Team Admins of the team.
4.5.2.2.3 Request for a new Post
A Team Admin can request for a Post. For approval, he needs to select one or more members of Administrator Team. Posts for Social Walls should have pre-defined approvers which should approve the posts to be published.
4.5.2.2.4 Request for an edited Post
A Team Admin can edit his Post and request again for approval. 
For approval, he needs to select one or more members of Administrator Team.
4.5.2.2.5 Approve request for a new or edited Post
Only Administrator Team can approve request for a new or edited Post. Every requested Administrator Team member needs to approve the request to make it effective.
4.5.2.2.6 Disapprove request for a new or edited Post
Only Administrator Team can disapprove request for a new or edited Post. Disapproval from any of the requested Administrator Team member makes it ineffective. Disapprover may provide his feedback as a reason or suggestion. The Team Admin may modify his request accordingly and try again.
4.5.2.2.7 Request to delete a Post
A Team Admin can request his Post to be deleted. An Employee can request for his Post to be deleted from Social Wall. 
For approval, he needs to select one or more members of Administrator Team.
4.5.2.2.8 Approve request for deletion of a Post
Only Administrator Team can approve request for deletion of a Post. Every requested Administrator Team member needs to approve the request to make it effective. When the request is approved and effective the post should be a soft delete. This means the post may remain stored in the database but will not be visible to that team.
4.5.2.2.9 Disapprove request for deletion of a Post
Only Administrator Team can disapprove request for deletion of a Post. Disapproval from any of the requested Administrator Team member makes it ineffective. Disapprover may provide his feedback as a reason or suggestion. The Team Admin may try again.
4.5.2.2.10 Delete a Post:
Only Administrator Team can delete a Post. The Administrator Team member can delete a post without a request as well as on a request. As soon as the last approver approves the request, the post gets deleted.
Deletion of post should be a soft delete. This means the post may remain stored in the database but will not be visible to that team.
4.5.2.3 Manage Users:
Here Administrator Team uses features related to Users and their accounts.
4.5.2.3.1 Create a user account:
Only Administrator Team can create an account of a user. Every user account must be unique.
4.5.2.3.2 Edit a user account:
A user can change all editable fields as described under Section "4.5.1. Self-Dashboard / My Profile". Administrator Team cannot edit an account of a user.
4.5.2.3.3 Block a user account:
Only Administrator Team can block account of a user. A blocked user may not be able to login. His posts and other information remain intact in the application as it is.
4.5.2.3.4 Delete a user account:
Only Administrator Team can delete account of a user. A deleted user may not be able to login. His posts/comments/likes/dislikes will appear with pseudo name and pseudo picture. His all other public and private information should be deleted permanently from the application.
4.5.2.4 Manage Emergency Contacts:
Here Administrator Team should be able to manage Emergency Contacts for the Organization. There may be multiple Emergency Contacts. This is a PDF file containing all Emergency Contacts for the Organization.
4.5.2.4.1 View list of Emergency Contacts:
Every user/employee should be able to see list and details of all Emergency Contacts for the Organization.
4.5.2.4.2 Add an Emergency Contact:
Only Administrator Team should be able to add an Emergency Contact for the Organization.
4.5.2.4.3 Edit an Emergency Contact:
Only Administrator Team should be able to edit an Emergency Contact for the Organization.
4.5.2.4.4 Delete an Emergency Contact:
Only Administrator Team should be able to delete an Emergency Contact for the Organization.
4.5.2.5 Manage Company Calendar
A Company Calendar is list of Holidays or important dates mentioned in a single PDF file. There is only one file containing company calendar for the organization including all locations.
4.5.2.5.1 View Company Calendars:
Every user/employee should be able to see list and details in Company Calendar for the Organization.
4.5.2.5.2 Add a Company Calendar:
Only Administrator Team should be able to add a Company Calendar for the Organization. He should be able to upload a PDF File as a Company Calendar for a selected Financial Year.
4.5.2.5.3 Edit a Company Calendar:
Only Administrator Team should be able to edit a Company Calendar for the Organization. He should be able to upload a PDF File as a Company Calendar. On file upload, previous file would be deleted permanently to be replaced by new Company Calendar.
4.5.2.5.4 Delete a Company Calendar:
Only Administrator Team should be able to delete a Company Calendar for the Organization.
4.5.2.6 Manage FAQ Document
An FAQ Document is a PDF file containing Frequently Asked Questions in multiple languages. 
There is only one FAQ document for the Organization. 
Here, the Administrator Team should be able to add or remove an FAQ Document.
4.5.2.6.1 View FAQ:
Every user/employee should be able to see list and details of all FAQ Document for the Organization.
4.5.2.6.2 Add an FAQ Document:
Only Administrator Team should be able to add an FAQ Document for the Organization. He should be able to upload a PDF File as an FAQ Document.
4.5.2.6.3 Edit an FAQ Document:
Only Administrator Team should be able to edit an FAQ Document for the Organization. He should be able to upload a PDF File as an FAQ Document. On file upload, previous file would be deleted permanently to be replaced by new FAQ Document.
4.5.2.6.4 Delete an FAQ Document:
Only Administrator Team should be able to delete an FAQ Document for the Organization.
4.5.2.7 Manage Company Policy Document
A Company Policy Document contains all or important Policies of the Organization in a PDF file in multiple languages.
There would be only one Company Policy Document for the Organization. It should appear under Settings Menu.
4.5.2.7.1 View Company Policy Document:
Every user/employee should be able to see Company Policy Document. He must provide his consent for the Policies to use the application. For any modification in the Policies, every employee must see the document and agree to the policies to continue use of the application.
4.5.2.7.2 Add a Company Policy Document:
Only Administrator Team should be able to add a Company Policy Document for the Organization. He should be able to upload a PDF File as a Company Policy Document for the Organization.
4.5.2.7.3 Edit a Company Policy Document:
Only Administrator Team should be able to edit a Company Policy Document for the Organization. He should be able to upload a PDF File as a Company Policy Document. On file upload, previous file would be deleted permanently to be replaced by new Company Policy Document.
4.5.2.7.4 Delete a Company Policy Document:
A Company Policy Document is required to be read by users to use the application. 
Therefore, a Company Policy Document should not be only deleted but replaced.
Please refer section "Edit a Company Policy Document" for more information.
4.5.2.8 Management Board
Management Board is a facility for all Employees to reach to CEO as an open forum.
There can be a form with a Text-area field (which can accommodate long text) and a Submit button. 
4.5.2.8.1 View posts/queries:
Every user/employee should be able to see all posts/queries from every employee and response from Management (CEO/Super Admin).
4.5.2.8.2 Add a post/query:
Every user/employee should be able to add/post a query on management board.
4.5.2.8.3 Edit a post/query:
No one should be able to edit a post/query on the management board.
4.5.2.8.4 Respond to a post/query:
Only “Super Admin” (CEO) should be able to respond to a query on the management board in his free time accordingly. In general, there may be a schedule for the same to respond on a particular day. ETO will confirm a schedule to respond questions on the management board. We will set the preferred time to respond accordingly.
4.5.2.8.5 Reminder to respond on posts:
ETO will confirm a schedule to respond questions on the management board. We will set the preferred time to send a reminder to respond accordingly.
The reminder email should be sent to “Super Admin” (CEO) to respond on queries on the management board accordingly.
4.5.2.9 Manage “Terms and Conditions” Document
A “Terms and Conditions” Document is a PDF file containing information in multiple languages. 
There is only one document for Terms and Conditions of the Organization. 
Here, the Administrator Team should be able to add or remove the “Terms and Conditions” Document.
4.5.2.9.1 View “Terms and Conditions” document:
Every user/employee should be able to see “Terms and Conditions” Document for the Organization.
4.5.2.9.2 Add a “Terms and Conditions” Document:
Only Administrator Team should be able to add a “Terms and Conditions” Document for the Organization. He should be able to upload a PDF File as a “Terms and Conditions” Document.
4.5.2.9.3 Edit a “Terms and Conditions” Document:
Only Administrator Team should be able to edit “Terms and Conditions” Document for the Organization. He should be able to upload a PDF File. On file upload, previous file would be deleted permanently to be replaced by new “Terms and Conditions” Document.
4.5.2.9.4 Delete a “Terms and Conditions” Document:
Only Administrator Team should be able to delete the “Terms and Conditions” Document for the Organization.
4.6 User Management - SAP Data Import &amp; LoginThere is an existing SAP-Backend application which has list of employees. The Employee App must import data from the SAP-Backend Application and create users.
4.6.1 Import Users:The application should import information/list of users from a CSV File over FTP. 
The file updates automatically from the SAP based on the time decided by ETO. Cycle of automatic updates will be set to ETO preferred time once decided.
4.6.2 Create a User:Administrator Team should be able to add new users, which are not fetched from the backend (SAP Application). They should also be able to control their access and association with one or more teams.
4.6.3 Generate initial login credentials:For every new user created or imported, the application should generate initial login credentials which should ideally be used for one-time. The employee should be asked to change his password when he logs in with initial one-time login credentials. On successful password reset the user should be able to see Company Policy (Terms and Conditions). He must also agree to the Company Policy (Terms and Conditions) to use the application.
4.6.4 Initial LoginOn successful initial login, employee should be asked to change his password when he logs in with system generated (one-time) initial login credentials. On successful password reset the user should be able to see Company Policy (Terms and Conditions). He must also agree to the Company Policy (Terms and Conditions) to use the application.
4.6.5 LoginAn active employee should be able to login to the application using (employee number or username) and password.
Alternatively, if it is not the first login and user has enabled biometric authentication (using FaceID or Fingerprint), then the user should be able to login with biometric authentication on the mobile application.
By default, mobile application users should be prompted to login using biometric authentication. They can also use a fall back based on password to login.
4.6.6 Login Expiration Time 
There should be default expiration time, after that period of inactivity, user should be logged-out automatically. As suggested, the login expiration time should be 15 minutes.
Therefore, the user should login again to use the application.
This setting should be editable by Administrator Team.
4.6.7 Authentication for mobile app:Authentication should be needed when mobile app comes from background to the foreground.
The biometric authentication like FaceID, Fingerprint or also password (can be device PIN) should be requested every time when the app comes from the background to the foreground. This should also happen for logged in user.
4.7 Calendar and ContactsThe calendar and contacts module shall enable users to synchronize activities as well as approach other users through the application.
4.7.1 Calendar:A Company Calendar is list of Holidays or important dates mentioned in a single PDF file. 
Please refer following section for more details: "4.5.2.5 Manage Company Calendar".
4.7.2 Contacts/Address book:Contacts/Address book is a list of all employees and their public information.
4.7.2.1 View Contacts:
Every employee should be able to view contact details of all employees of the organization.
4.7.2.2 Edit Contacts:
Only an employee can modify any editable information which belongs to him.
4.7.2.3 Delete Contacts: 
Only Administrator Team can delete a contact (employee or its details information)
4.7.2.4 Add Contacts:Only Administrator Team should be able to create/add new contact. A new contact can only be created which is not available through SAP-Backend Application. Please refer Section 4.6.2 Create a User for more information.
4.7.2.5 Sync Contacts:
The contacts should be imported periodically from SAP-Backend Application. The imported contact list should reflect accordingly. Please refer Section 4.6.1 Import Users for more information.
4.8 Recruitment ManagementThis is a feature mainly used for Recruitment purpose. It can be found in the navigation item “Employee Self Service”
4.8.1 Add Recruitment Info:Here Administrator Team should be able to manage requirement for recruitment. 
4.8.1.1 Create a requirement (Job) for recruitment:
Administrator Team should be able to create a requirement for recruitment by uploading PDF Files containing details of open positions. There may be a form with Recruitment Title and File upload field to upload recruitment details. 
4.8.1.2. View list of requirements:
All employees should be able to view list of title and PDF files for recruitments.
4.8.1.3. View Details of a requirement:
All employees should be able to view details of a requirement for recruitment by opening the PDF file.
4.8.1.4 Update a requirement:
Only Administrator Team should be able to Update a job requirement. They should be able to edit the Title and a new PDF file. On update new file replaces old file.
4.8.1.5 Delete a requirement:
Only Administrator Team should be able to Delete a requirement (for recruitment). On delete details about the requirement should be deleted permanently.
4.9 Help &amp; SupportTo get help and support on any issue or concern employees can reach to corresponding department. An employee should be able to create a ticket and share more information.
4.9.1 Support Type:While creating a help ticket, an employee needs to specify which type of support he wants. This is regarded as Support Type of the ticket. The Support Types should be pre-configured in the application.
4.9.2 Contact Group Management:This is a group of people responsible to help employees on their help tickets. Administrator Team should be able to configure Contact Groups for a Support Type. Every Support Type should have a Contact Group associated with it.
4.9.2.1 Create a Contact Group:
Administrator Team should be able to create/configure a Contact Group for each Support Type (HR/Finance/Network Admin etc.). 
4.9.2.2 Edit a Contact Group:
Administrator Team should be able to edit a Contact Group for a Support Type. 
4.9.2.3 Remove a Contact Group:
Administrator Team should be not be able to remove a Contact Group for a Support Type. They should be able to use “Edit a Contact Group”.
4.9.3 Create a help ticket:All employees should be able to create a help ticket. It may be a form with following fields: Support Type (HR/Finance/Network Admin), Subject, Description and upload a supporting document(optional). On submitting the form, corresponding contact group should receive an email with all information and handle the request accordingly.
4.10 Google Maps view:Employees should be able to view all ETO worldwide locations using Google Maps.
4.10.1 Locations of ETO Gruppe:ETO Gruppe has a worldwide presence (in multiple countries). All office address and locations should be pre-configured in the application. They should not be editable by any employee.
4.10.2 View list of office address:All employees should be able to view all office/plant address and corresponding locations. 
4.10.3 View Plant Location on Google Map:There should be a link "View in Google Map" for each of the locations. On click, the use should redirect to google maps and route them to Google Maps where he can view selected ETO plant location. The map can be used to find route from a location (his current location) to the selected ETO plant location.
4.11 Links for SAP Fiori:There should be a Link of "Employee Self Service" which leads to group of menus containing "Leave Management", "Travel Management", "Expense Management", "Recruitment", "Pay slips and Attendance", "Time Management", "Shift Planning", "Send new Idea", "Survey" and "Training". Except "Recruitment" all links should redirect user to a blank screen. 
They should be used to integrate the SAP FIORI UI5 design in the application. The implementation of this feature is currently out of the scope of this requirement.
4.11.1 Send new IdeaImplementation of "Send new Idea" can be integrated under Help &amp; Support section. We should create one more support type as "Send new Idea". 
All employees should be able to access "Send new Idea" feature. To use it, user should select Support Type "Send new Idea" (similar to other support types such as HR/Finance/Network Admin) and provide remaining information: Subject, Description and upload a supporting document(optional). On submitting the form, corresponding contact group should receive an email with all information and handle the idea accordingly.
4.12 Multiple Language SupportApplication should be able to support more than one language. The base language of the application should be English but it should also be able to support other languages as required.
4.12.1 List of Required Languages:The application should be able to support following 5 languages:
1. English 2. German 3. Polish 4. Chinese (Mandarin) 5. Spanish
4.12.2 Menus and Functions:The application should be able to present menus, functions and non-changeable text in the above-mentioned required languages.
4.12.3 Translation Support for Posts:All employees should be able to view a Post in another language, if required. There should be a feature to change a Post content in one of the above-mentioned required languages. To translate a text, external translator like Google Translate may be used.
4.12.4 Support for a New Language:The application should be able to support a new locale/language without building an entirely new application.
4.13 Search for Posts and Employees:There should be a Search Button which leads to Search Page where users should be able to search for Posted contents or employee information. User should also be able to search precisely with 4 targeted filters “GRUPPE News”, “Location News”, “Social wall” (posts from all 3 walls) and “Address Book” (Public information of all Employees). For Posts the search should be made based on Post Title, Description and Post Published Date and for Employees it should be based on Employee Id, Name, Email Id and Date of Joining of an Employee.
On search, results should appear based on relevance and date with limited information. User can click on any Post item to view complete post title and description as popup. Similarly, on click of any employee info other public info can be seen as popup. 
Just to inform that using Full text search may also increase load time. As requested, the full text search should also be possible within a post.

List of ReviewersRevisions Name of Reviewer Comments Date  (YYYY-MM-DD)
ApprovalI hereby declare to have read and understand the document and acknowledge its content meets the requirements. I understand that possible changes or extensions can lead to a new change request and additional quotation.
Date:
Name:
Company:
Signature: