Transcript
Page 1: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

Creating Open Wide Area Workflow and eFolder standards

June 2006

David RR Webber

[email protected]

Joint Initiative Project Planning

Page 2: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

2

Envisioning Statement

World is facing new challenges that require rapid response capabilities at new levels and scale – environmental, health, food distribution, citizen services, military support logistics

Existing systems have challenge of supporting end-to-end tracking and collaborative workflow

Who is taking leadership role in this arena?

Page 3: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

3

Envisioning Key Factors

Interoperability – need end-to-end support, not fragments along pathways

Rapidly adaptable / deployable components for business users process support

Based on trusted proven open standards approach

Auditability and accountability

Process Metrics

Support for “dashboard” visibility tools, not just local view

Page 4: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

4

Opportunity Assessment

Existing events and response needs bring together national and international focus

Existing initiatives need better coordination and resources

Leverage open standards community work

Build from existing best-practice work on processes and information exchanges –

Lessons learned over past 15 years of workflow and business process need to be leveraged (eFolders + pre-cut process library)

Use of XML is entering a third phase

Increasing importance of open standards and open source to collaborative environments

Page 5: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

5

Transport

XML

Security

MoU/

Agreement

XML

Context

XMLContext

XML

Vocabulary

Alignment

eFolder

Collaboration

XML

State

Management

Core Technology - 12 Alignment Needs

Workflow

Process

XML

Transaction

Structure XML

(XSD)

Access Point API Content Process

Rules

PROCESS (how)

INFORMATION

(what)

Page 6: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

How does this fit to Navy

needs?Potential areas of

interest

What is driving the need?

If not now, when?

Page 7: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

7

Collaboration Roles and Steps

? How does this get done?

What are the overarching standards

that allow collaboration between the

disparate parts of the process not

just point operations?

http://www.onr.navy.mil/02/wawf/

Page 8: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

8

WAWF Use Cases?

From: https://wawf.eb.mil/

Page 9: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

9

Navy Merge (ERP project) - Use Cases?

http://www.gao.gov/highlights/d05858high.pdf

Page 10: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

10

Navy / CNIC - RAPID Use Cases?

CHRIMP workflow:

Page 11: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

11

Goals

Understand and enable core use case needs

Develop open public standards foundation

Provide clear direction for vendors and implementers

Create Community-of-Practice foundation

Provide focused deliverables over next 6 to 12 months

Develop formal specifications as OASIS and then ISO standards

Create real re-usable templates and examples

Page 12: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

12

What Does This Take?

Tasks / Level of Effort (LOE) estimates: Manage and support OASIS TC process – 1FTE for 4 months ( 10 hours a week for one year)

Phase 1 – Use case definition / scope / positioning Elapsed time - 3 months

Phase 2 – Specification Development – 2FTE for 4 months

Elapsed time 6 months

Phase 2 – Operational Pilots – TBD – each ~ 3FTE for 6 months.

Elapsed time 6 months (concurrently)

DeliverablesUse cases

Specifications

Working re-usable templates and components

Page 13: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

13

Some Candidate Deliverable Examples RAPID –

STARS-FL XML connector and workflow support

Packaging of standard interfacing (OASIS CAM) APIs - specify documentation Operational toolset Mapping to the UBL financial transactions

standards TBD ???

Page 14: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

14

Community of Interest

US Navy WAWF team

US Navy DON CIO team

OASIS BCM TC and EPR working group

OASIS BPM work on ebBP/BPSS and BPEL

Norway TOSS project team

Norway NIA involvement + Baltic area

Bravera – RAPID project tool vendor

DoD DFAS accounting services

IHE/XDS NIST work on secure document exchanges

ISO and CEN/ISSS

Page 15: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

Approach

Next Steps

Page 16: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

16

Action Items

Refine vision statement

Form action committee and support from Navy DON CIO

Establish DFAS commitment / support

Coordinate with OASIS and Norway

Coordinate initial meetings and public call through OASIS BCM TC infrastructure

Create Community of Interest site area (GSA resources?)

Create bi-weekly teleconference coordination

Define doable scope and XML needed and avoid “ocean boiling”

Page 17: Creating Open Wide Area Workflow and eFolder standards June 2006 David RR Webber david@drrw.net Joint Initiative Project Planning

17

Resources

http://www.oasis-open.org/committees/bcm

http://www.eprforum.no

http://www.eprforum.no/product.php/PSQA-Limited-

conferance-N/6/

http://www.eprforum.org

http://www.bravera.com

https://rapid.cnic.navy.mil


Top Related