Office Safety Auditing Story What am I trying to accomplish with this app Provide an easy to use application to conduct Office Safety Audits for large office facilities Context Charles is the Environmental, Health, and Safety Manager at his company. He oversees a campus that contains over 400 offices. In order to improve safety performance, he has instituted an audit program to ensure each office offers a safe working environment. While everyone generally does their best to comply with the company safety rules, he needs to periodically re-inspect each and every office twice a year. He currently uses an excel spreadsheet for each office to serve as a checklist. Keeping track of which offices have been audited and which ones still have open issues is complicated. Conducting audits is further hampered by getting access to offices when they have meetings or are out on vacation. The native SAP transaction is designed for complex audit needs and is more than what is needed for this specific application. Segmentation Office Management Targeting Environmental, Health and Safety Positioning Office Safety Audit Page 1
We would like to simplified user interface to only show needed fields so that casual users can conduct office safety assessments. Able to consume on a mobile device as the auditor visits each office to avoid any use of paper forms. Persona Charles Keep everyone safe 25 Year experience, College Ed. EOHS Manager Ensure safe operations zero accidents Oversee Safety programs Ensure proper procedures are in place Liaison with regulators and followed Manages Team Trains staff People taking shortcuts People not concerned about safety Easy to use tools Fast access to information Office Workers User Experience Journey Red dots signify pain points, Blue dots represent positive events. Office Safety Audit Page 2
Mock-Up A Design for the application was created using the Prototyping kit. One quick tip for using the tip is to ungroup the sample slides so that you can copy what you want. When Icons were not found in the kit, I used the UI5 Explored and took a screen capture of the needed icon or control. The left pane contains the offices that will be audited. The Occupant tab displays contact information about the occupant and his supervisor to assist in scheduling appointments or escalating corrective Action. The Standards tab provides an easy reference of the expectations for the office. It also has an icon to allow the user to create a finding right from this list When the add button is pressed a form to enter the finding will appear. Office Safety Audit Page 3
The Finding form will show up in place of the standards list once the Add button is pressed. Here the user can enter their finding. The Findings Tab contains each finding that was reported for the selected office. Office Safety Audit Page 4
Mock Data Mock Data was developed in Excel. I wrote a macro to export each sheet to json format. Web IDE Screen shots The Fiori Application was built based on the Master Detail Template where the Office table is the master table. In order to navigate to the Standards or findings for the office, a Navigation/Association from Office to Standards and Office to Standards was added to the edmx model. The Office table stores information about the occupant and supervisor. In order to change the photo of the employees the file name was also in database. I used nested grid objects to get the screen layout. Office Safety Audit Page 5
So the auditor can focus on the offices that still need to be audited, a filter option has been created to filter by the status field. Alternately the manager can filter by offices that have open findings. The activity popup was done using a XML fragment. Each office could in theory have different relevant standards. Perhaps different for an equipment room or stair area. Therefore, we used a navigation association to show only the standards for the currently selected audit. The + add button opens the screen to enter the new finding. Office Safety Audit Page 6
The new finding form is displayed by toggling the visibility of this form, with the standards table. The visibility of the save and cancel buttons are also controlled when the form is displayed. The Save button was not implemented as it would require an additional function in the data model. The findings button shows a complete list of all the findings for the selected office. This is a screen show of the Web IDE showing the project structure and the edmx file that was created with a text editor. Office Safety Audit Page 7