210 likes | 315 Views
BNL Key Workflows. Interlab 2009 November 17, 2009 Courtney Patterson Information Technology Division/Quality Management Office. Agenda. Background Current Problems Solution Requirements Workflow Solution Demo Next Steps Questions/Comments. Background: What is SBMS?.
E N D
BNL Key Workflows Interlab 2009 November 17, 2009 Courtney Patterson Information Technology Division/Quality Management Office
Agenda • Background • Current Problems • Solution Requirements • Workflow Solution • Demo • Next Steps • Questions/Comments
Background: What is SBMS? • Web-based system of institutional policies and procedures. • Management System which provides • A Requirements management process. • A Content development and management process. • Roles Management. • Content Delivery tool
SBMS Hierarchy • Policies; • highest-level statements of BNL philosophy for conducting business. • Standards of performance; • performance expectations by which BNL carries out its policies. • Management System Descriptions; • Summary of high-level lab-wide operating processes.
SBMS Hierarchy • Subject Areas; • Most common vehicle used to translate requirements into how work should be done. • BNL Manual; • Same function as SA but in old format. • Program Description; • Steering document developed when required by clients, regulations, or the management system to further describe operations.
SBMS Hierarchy • Facility Use Agreements; • Identifies the operating requirements, roles and responsibilities for all aspects of our facilities. • Interim Procedures • Used when a procedure needs to be disseminated quickly. They have an expiration date. • Lessons Learned • Documentation of experiences at BNL and other sites for the purpose of sharing in order to emulate good practices, avoid risky / poor practices.
1stProblem • Employees find SBMS challenging. • Information overload. • Navigation between procedures is difficult. • Procedures are hard to read. • Difficult to understand what they need to do.
SBMS’s Main Delivery Format 1 2 3 4
2nd problem • Procedures are stove-piped. • Lab wide business process != Management System Procedures. • Difficult to understand the “big” Lab wide business processes.
High level Solution Requirements • Deliver procedures in a Workflow format • Simplicity (for end users) • Simple user interface • No training required (intuitive) • Re-use • Extends the current SBMS data/information • Reuse current resources/infrastructure • Hardware resources • Software resources
High level Solution Requirements • BPMN compliant. • Ability to share workflows with other Labs. • Ability to integrate with any BPMN compliant software • Budget friendly.
Workflow Solution • Web-based process modeling/presentation tool. • Integrates directly into our current infrastructure • Built using .NET/CFML/MS SQL Server • Multi-phase approach. • First phase • Present workflows. • Second phase • Manage workflows. • Third phase • Automate workflows.
Workflow Solution cont. • Relatively inexpensive • Total of $3695 (Layout engine) • Designed with extendibility in mind • Supports .net thick client, web and mobile apps. • Possibility of pushing workflows to mobile devices • Supports silverlight applications • Supports WPF applications
Demo • Browsing a workflow • Administrating a workflows
Where do we go from here • Workflow change management tools/procedures • Archiving • Versioning • Publishing controls • Optimization • Visual • Printing • Speed • Usability
Future • Automation using a workflow engine eg; • Windows Workflow Foundation • Skelta Workflow.NET • Intrafinity workflow • Home-brewed solution