Improving Your Business Processes Through SharePoint. Ian Palangio, Microsoft Milan Gross, Synergy

Transcription

1 Improving Your Business Processes Through SharePoint Forms and Workflow Ian Palangio, Microsoft Milan Gross, Synergy

2 XML Data is Good for Systems

3 Integratewiththe Hardest System ERP? CRM? Payroll? Procurement?

4 Forms: The De-facto Human Integration to XML Data

5 Office System = Form Solution that ALL People can Easily/Quickly Use

6 InfoPath Revealed! Smart Client and Browser SQL, ERP, CRM, TLA

7 MS Expense InfoPath Form Demo

8 Form Server A Regular SharePoint Application Forms for the Masses

9 Fill Formsin Any Browser and Operating System Internet Explorer Firefox Designed once! Same experience in Internet Explorer, Firefox, Safari, Netscape and the InfoPath rich client

10 Embed Forms in Web Applications like SharePoint Use workflow forms to add and configure a workflow. Form to interact with workflow Form to configure workflow settings Use workflow forms to complete tasks or interact with a workflow.

11 Student Enrolment Form Demo

12 InfoPath Designer A Design Tool for Everyone

13 Design Forms in Familiar Word Like Tool

14 InfoPath has a Form Design Environment to Suit All C# VB.NET Rules Formulas Data Validation Data Connections Conditional Formatting Most Form Development Does Not Need Code XSD, Web Service, Database

15 Form Design Environment for Hard Core Developers

16 Over 1 Million Developers

17 InfoPath Embeds in Visual Studio InfoPath views View all at once! Managed code InfoPath design tasks Solution files and resources InfoPath Designer InfoPath data source

18 Process and Data Management The Workflow Process is the Exciting Part!

19 Process Definition Many Options SharePoint Designer for IT Pro Out-of-the-Box Solutions (with customisation) for End User Visual Studio and Workflow SDK for Developer Custom Form Actions Notification Exception Handling Routing and Approval Review Approval Signature collection Collect Feedback LOB Integration Industry specific processes Purchase orders Product lifecycle mgmt Custom Tracking Apps Service Requests Asset Tracking Tracking Applications Issue tracking Document Processes Spec Review Weekly Status Report Office Server Features List Moderation Publishing Process Document Expiration Most Process Development Does Not Need Code Structured with Roles Ad Hoc

20 End User Experience Forms Based Process DP World Process Platform Demo

21 Global Ports Connecting Global Markets

22 Damaged Container Reports The Problem CONSISTENCY The existing manual reporting system for damaged shipping containers was not only inefficient, it was also inconsistent across sites. This made it difficult to reconcile reports between terminals. DUPLICATION / MISSING DATA Users would fill out a paper based form, and then details of the report plus supporting photographs to each other between terminals, and with head office. These reports would then be forwarded to more people again, wasting network and resources, and not offering a complete single source of truth EXPOSURE As it was not easy to reconcile reports, there was a potential risk that a client could make multiple claims for the one damage incident.

23 Damaged Container Reports The Solution Microsoft Office SharePoint Server 2007, with Microsoft InfoPath 2007 and Form Services. CONSOLIDATION This combination has allowed IT to provide a web based form that ensures all reports for all terminals are produced in a consistent manner. It also ensures there is only 1 instance of information regarding a report, and it is easily searchable. MANAGEMENT BENEFITS An added benefit of this solution is that head office management have ready access to the reports for all terminals, and the risk of reports being misplaced has been removed. OPERATIONAL The operational teams have been quick adopters of this solution, as they see the benefits not only in providing more visibility to management, but also in reducing the amount of time spent completing paperwork.

24 Damaged Container Reports The Solution WORKFLOWS NintexWorkflow 2007 was chosen as the workflow development interface. It allows end users to manage their own workflows, making changes as required. It greatly reduces the workflow development time, as there is no need for IT be involved in simple changes. This makes great sense, as it is the business units, and not IT, who best understand the workflows used by the business. NEXT STEPS Development of the next phase of this reporting process has already commenced. Included in the next release will be some enhanced reporting, and also integration with new Enterprise LOB applications.

25 SP World Workflow Process Maps Travel Request Approval Software Request and Packaging Container Damage Tracking

26

27

28

29

30 The Solution Demonstration of the End Result

31 Office System Gives People the Form Processing Experience they Need

32 Thank You