Ausspc 2010 Presentation Building Lob Solutions With Share Point 2010
•Descargar como PPT, PDF•
0 recomendaciones•366 vistas
This document discusses using SharePoint 2010 to build line of business (LOB) solutions that focus on business processes and content management. It provides an example of an occupational health and safety (OHS) scenario and how SharePoint could be used to manage the incident reporting process. Key aspects include using workflows to automate tasks and notifications, managing documents and metadata, and measuring performance metrics to track outcomes and benefits over time. It emphasizes an iterative process approach with stakeholder involvement and monitoring outcomes to continuously improve the solution.
![Building Line of Business Solutions Using SharePoint 2010 ECM Technology ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Similar a Ausspc 2010 Presentation Building Lob Solutions With Share Point 2010
Similar a Ausspc 2010 Presentation Building Lob Solutions With Share Point 2010 (20)
Más de Simon Rawson
Más de Simon Rawson (6)
Último
Último (20)
Ausspc 2010 Presentation Building Lob Solutions With Share Point 2010
- 4. Highly Successful Projects Process Effectiveness v Efficiency – LOB Focussed
- 12. Managed Innovation / Suggestions ACTION Suppliers Staff Customers Business Partners
- 15. Thank you to our Sponsors
Notas del editor
- Opening slide please include
- Provocations: All content should be process-centric The future of site orientation is not social. Facebook only will be a disaster. Conversations are a means to an end. What percentage of a corporation’s activities are driven by altruism or self-actualisation vs make a profit? So its dollars which make a difference, and business processes are all about making them (ie. maximise revenue) or conserving them (effectiveness and efficiency – note that effectiveness should pretty much always be first) Social interactions about a company are driven by one of two things: Ethical positioning OR questions about products and services. Reputation is primarily built around quality and consistency. All of these things are process outcomes. Conversations are a process.
- You need a purpose and focus for any ECM implementation. Without purpose and focus you cannot get stakeholder buy in nor meaningful collective action leading to an outcome. Criteria for inclusion is meeting or exceeding initial expectations, and a consensus opinion of success. Note that only 5% of highly successful projects Data drawn from a survey of 90+ projects in 83 companies.
- In this example there are 2 workflows at play: The workflow associated with reporting and managing incidents Content approval associated with checking in new or revised policies into Sharepoint document libraries The incident reporting workflow is by far the more complex. The last point on this slide – orientation on ongoing improvement, is important, and something which can be done in every organisation and just about every workflow. The incident investigation process results in recommendations. We could observe cynically many of these would just sit on the shelf. A logical extension to the workflow is managing recommendations, explicitly approving or rejecting each in turn. The same principle can be applied to any process, if you provide the ability for participants to make suggestions for improvement, which are then explicitly reviewed and either accepted or rejected.