+ All Categories
Home > Documents > Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

Date post: 16-Dec-2015
Category:
Upload: yahir-filley
View: 224 times
Download: 0 times
Share this document with a friend
Popular Tags:
61
ANSI/AIIM 21:2009 Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core
Transcript
Page 1: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

ANSI/AIIM 21:2009

Standard Recommended Practice - Strategy Markup Language - Part 1:

StratML Core

Page 2: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

INTRODUCTION StratML Definition, Focus, Intent & Status Related eGov Initiatives StratML Tools & Prototype Services Part 2, Performance Plans & Reports What StratML Can Do for You Needed Applications & Services How You Can Help

Page 3: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

DEFINITION Strategy Markup Language (StratML) Part 1

is an XML vocabulary and schema for the elements commonly contained in strategic plans.

StratML Part 2 will extend Part 1 to include the additional elements required for performance plans and reports.

Part 3 and perhaps additional parts will incorporate additional elements that, while not deemed essential, may add value to the core elements of strategic and performance plans.

Page 4: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

FOCUS & INTENT Although the initial focus has been on

the plans U.S. federal agencies are required to compile and maintain under the Government Performance and Results Act (GPRA), the intent is for StratML to be adopted as an international voluntary consensus standard for potential use by all organizations worldwide, as well as individuals who choose to lead mission/goal-directed lives.

Page 5: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

CONTENT & STATUS OF PART 1, STRATEGIC PLAN CORECore Elements

1. Organization

2. Mission

3. Vision

4. Value

5. Goal

6. Objective

7. Stakeholder

ANSI/AIIM StandardAnnouncementCross-promotion/

marketing

Prototypes Tools & services >500 StratML docs

Page 6: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

EGOV INITIATIVES President Obama’s Open Gov Directive Open Gov Brainstorming Data.gov eGov Act E-FOIA OMB Circular A-119 W3C eGov IG Open Gov Data Working

Draft

Page 8: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

TRANSPARENCY

What is government doing? Goals & objectives

In what form can the public readily find & use information? HTML, XML, StratML with style sheets, applications & intermediary services E-FOIA amendments Data.gov

How can the public provide feedback? StratML applications/services More mature, social networking focused on stakeholders, goals &

objectives

Page 9: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

PARTICIPATION

Public engagement ~ StratML applications Effectiveness ~ Measurable results, reported to

stakeholders Input to improve public participation ~ To what end?

More efficient/effective pursuit of .gov goals & objectives

Page 10: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

COLLABORATION

What is the “work of government”? Missions, goals & objectives

Innovative tools, methods & systems to cooperate ~ on What? Goals & objectives

How better to solicit public feedback? Mature social networking services by applying StratML

Page 11: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

OPEN GOV BRAINSTORMING WRAP-UP, BETH NOVECK

Page 12: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

OPEN GOV – 501(C)(3) NONPROFIT TAX-EXEMPT STATUS

Page 13: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

OPEN GOV DIALOGUE – ERICK GONZALEZ, ORACLE

Page 15: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

M-10-06OPEN FORMATS

StratML is an open format

Page 16: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

M-10-06 FEEDBACK ON OPEN GOV PLANS

Note: M-10-06 is available in StratML format with basic styling, including a hyperlinked table of context at http://xml.gov/stratml/crane/OGD.xml

The purposes of the StratML standard include facilitating stakeholder feedback on strategic goals and objectives, e.g., those to be documented in agency open gov plans. Agency open gov plans should be published in StratML format.

Page 17: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

DATA.GOV

Access to “high-value” datasets ~ Aligned with strategic goals/objectives Machine readable ~ CSV & XML (e.g., StratML) Catalog ~ by Stakeholder groups, goals & objectives

Page 18: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

EGOV ACT StratML will enable agencies to comply with the

provisions of subsections 202(b)(4) & (5) and 207(d) of the eGov Act, which respectively require agencies to: Work together to link their performance goals to key groups,

including citizens, businesses, and other governments, as well as internal Federal Government operations; and

Adopt open standards (e.g., StratML) enabling the organization and categorization of Government information in a way that is searchable electronically and interoperably across agencies.

“Key groups” = StakeholdersStratML = Open standard enabling queries interoperably across agencies

Page 19: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

E-FOIA AMENDMENTS … an agency shall provide [records] in any form or

format requested … if the record is readily reproducible by the agency in that form or format.

Each agency shall make reasonable efforts to maintain its records in forms or formats that are reproducible … 5 USC 55 (a)(3)(B)

XML (StratML) is machine readable and readily reproducible The StratML collection already includes the plans of

All of the cabinet-level agencies (but not the bureaus) Most of the smaller agencies (Small Agency Council

members)

Page 20: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

OMB CIRCULAR A-1196. What Is The Policy For Federal Use Of Standards?

All federal agencies must use voluntary consensus standards in lieu of government-unique standards … except where inconsistent with law or otherwise impractical.

7. What Is The Policy For Participation In Voluntary Consensus Standards Bodies?

Agencies must consult with voluntary consensus standards bodies … and must participate with such bodies in the development of voluntary consensus standards when consultation and participation is in the public interest and is compatible with their missions, authorities, priorities, and budget resourcesStratML ~ Is a voluntary consensus standard Can be used to document/share agency missions & goals/objectives (priorities) Is not government-unique StratML tools/services can make it very practical to useParticipation in standards development bodies should support agency objectives (as documented in StratML format)

Page 22: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

OPEN GOV – CTO CHOPRA @GOV 2.0 CONFERENCEAneesh Chopra, U.S. Chief Technology Officer … there must be a structured approach to open

government, including a schedule for the public release of government data in machine-readable formats.

… government agencies should engage the public in developing open government plans and publish their completed plans.

Information Week, September 9, 2009

StratML is a structured approach for releasing the data contained in strategic and performance plans in machine-readable format .

Eventually, more mature social networking technologies and services should facilitate engagement and feedback from stakeholders

On the plans of organizations whose missions, goals, and objectives are of interest to them. 

Page 23: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

STRATML TOOLS & SERVICE PROTOTYPES Documentation & Transformation Services – Drybridge

Technologies CAM Interactive Documentation – David Webber Authoring/Editing Tools

Adobe, Xopus, Business Web Software, XML <Simplicity>, Syntext & IC Tect

Tag Cloud – Strategi Consulting, Ari Knausenberger Atom Demonstration – Joe Carmel Basic Stylesheet – Crane Softwrights, Ken Holman Farsi Translations & StratML Transformation Portal – Pooyan

Zamanian Search Service – Mark Logic, Shashi Mudunuri Schema Design – Vision4Standards, Sylvia Webb

Page 24: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

SCHEMA DOCUMENTATION – DRYBRIDGE TECHNOLOGIES

Page 26: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

DRYBRIDGE TECHNOLOGIES

Page 27: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

CAM INTERACTIVE DOCUMENTATION – DAVID WEBBER

Page 28: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

STRATML FORMS During the development, piloting, proof-of-concept phase, more than

500 strategic plans were rendered in StratML format, using five different authoring/conversion tools, including: Microsoft InfoPath using this form Business Web Software AchieveForms Adobe PDF Fillable Form Xopus Form (Available in Spanish as well as English) Microsoft Word, with assistance from Ictect

Page 29: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

MS INFOPATH

Page 30: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

ACHIEVEFORMS - BUSINESS WEB SOFTWARE (FIRMSTEP)

Page 31: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

ADOBE PDF FILLABLE – ED CHASE

Page 32: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

XOPUS – LAURENS VAN DEN OEVER

Page 33: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

CHANGE.GOV PLAN – RAW (PLAIN TEXT) XML

Page 34: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

ALTOVA AUTHENTIC – XML <SIMPLICITY>

Page 35: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

STRATML SEARCH SERVICE – XML <SIMPLICITY>

Page 36: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

XML <SIMPLICITY>, KEITH MATTHEW

Page 37: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

SERNA – SYNTEXT, TIMOFEY FURYAEV & DARIA CHERNOVA

Page 39: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

MS WORD – IC TECT, PRADEEP JAIN

StratML Quick Start Guide for MS Word Users

Page 41: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

ATOM DEMO – JOE CARMEL

Page 44: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

STRATML TRANSFORMATION PORTAL – POOYAN ZAMANIAN

Page 45: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

QUICK SEARCH - MARK LOGIC, SHASHI MUDUNURI

Page 48: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

PART 2, PERFORMANCE PLANS & REPORTS Candidate Elements Simplified Graphics More Detailed Graphics

Page 49: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

PART 2, PERFORMANCE PLAN CANDIDATE ELEMENTS1) Stakeholder

At least one Stakeholder of the performer type must be identified, although the named performer may be an organizational role rather than a particular individual.

2) MetricAt least one Objective must be included and a Metric should be associated with it.

3) Outcome At least one desired Outcome should be specified, because no organization should exist

solely for self-serving purposes. 4) Output

The Outputs required to achieve the desired Outcome(s) should be specified. 5) Input

The Inputs required to produce Outputs should be specified. 6) Process

The Processes required to produce Outputs and Outcomes should be specified.

Page 50: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

PART 2, SIMPLIFIED GRAPHIC

InputsProcess

esOutputs

Processes

Outcomes

Performance Plans & Reports: The Value Chain

Page 51: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

INPUTS, PROCESSES, OUTPUTS & OUTCOMES

Input

Name Description Metrics

M ea surem ent

Dimens ion

Number of Units

M ea surem ent

Frequency

Output

Name Description Metrics

M ea surem ent

Dimens ion

Number of Units

M ea surem ent

Frequency

Process

Name Description Metrics

M ea surem ent

Dimens ion

Number of Units

M ea surem ent

Frequency

Outcome

Name Description Metrics

M ea surem ent

Dimens ion

Number of Units

M ea surem ent

Frequency

Page 52: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

METRICS

Metrics

Measurement Dimension

Unit Type

Number of Units

Number Type

Measurement Frequency

Time Unit Type

Number of Units

Page 53: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

THE ROAD AHEAD Intended Purposes / Needed

Applications How You Can Help

Page 54: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

INTENDED PURPOSES/NEEDED APPLICATIONS/SERVICES Facilitate the sharing, referencing, indexing, discovery, linking,

reuse, and analyses of the elements of strategic plans, including goal and objective statements as well as the names and descriptions of stakeholder groups and any other content commonly included in strategic plans.

Enable the concept of "strategic alignment" to be realized in literal linkages among goal and objective statements and all other records created by organizations in the routine course of their business processes.

Facilitate the discovery of potential performance partners who share

common goals and objectives and/or either produce inputs needed or require outputs produced by the organization compiling the strategic plan.

Facilitate stakeholder feedback on strategic goals and objectives.

Page 55: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

PURPOSES/APPLICATIONS/SERVICES (CONTINUED)

Facilitate updating and maintenance of  discrete elements of strategic plans without requiring review and approval of the entire plan through bureaucratic channels, thereby helping to make the strategic planning process more agile and responsive to stakeholder feedback and changing circumstances, thus helping to overcome the tendency of strategic plans to become outdated "shelfware".

Reduce the needless time, effort, inconsistencies, and delays associated with maintaining data redundantly in myriad "stovepipe" systems rather than referencing the authoritative sources.

Enable agencies to comply with the provisions of subsections 202(b)(4) & (5) and 207(d) of the eGov Act, which respectively require agencies to: Work together to link their performance goals to key groups, including citizens,

businesses, and other governments, as well as internal Federal Government operations; and

Adopt open standards (e.g., StratML) enabling the organization and categorization of Government information in a way that is searchable electronically and interoperably across agencies.

Page 56: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

WHAT WILL STRATML DO FOR ME? As a manager in an

organization, you will be able more efficiently and effectively to engage your employees, partners, and other stakeholders not only in crafting but also carrying out your strategic goals and objectives.

As an application developer or service provider, you will have the opportunity to leverage and extend the StratML to demonstrate your capabilities to more fully support your existing customers as well as to attract new customers. Having a standard vocabulary and schema for strategic plans will make it easier to develop such applications and services.

Page 57: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

WHAT WILL STRATML DO FOR ME? As a citizen and

tax payer, you will be able to more easily discover, comment on, and participate in the establishment of the goals and objectives of agencies whose missions are of particular interest to you.

As a volunteer and/or contributor to charitable organizations, you will be able to more easily discover those who share your values and are pusuing objectives you consider to be worthy of priority for your support.

Page 58: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

WHAT WILL STRATML DO FOR ME? As a customer or

investor, you will be able to review and provide feedback far more efficiently and effectively on the goals and objectives of companies that are truly customer focused and share their strategic plans openly.

To the degree that Part 2 is implemented and used, you will also be able to track and monitor the performance of organizations about whose goals you care.

Page 59: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

WHAT WILL STRATML DO FOR ME? In addition, Part 2 will enable

vendors to identify their products and services as inputs required to produce outputs desired by customers in order to achieve their objectives. At the same time, consumers will be able to identify the qualities of such products and services they deem to be important. The effect will be to revolutionize the advertising and marketing paradigm, putting consumers in control and vastly reducing the needless time, effort, and cost of bringing suppliers and consumers together in the marketplace.

Finally, as an individual who chooses to lead a mission/goal-directed life, you will be able far more efficiently and effectively to engage those who share your values in the pursuit of objectives you hold in common. In that respect, the current social networking technologies are a mere shadow of what such services can become when they implement the StratML standard and begin to enable focus on the accomplishment of objectives (achievement of results rather than merely what we look like, whom we know, or what we happen to be doing at the moment.

Page 60: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

HOW YOU CAN HELP Foster awareness of the StratML standard Help specify Parts 2 & 3 Encourage organizations to maintain their plans in

StratML Convert some plans yourself Encourage social networking sites to use StratML Develop StratML applications and services

Page 61: Standard Recommended Practice - Strategy Markup Language - Part 1: StratML Core.

MORE INFORMATION [email protected]

http://xml.gov/stratml/index.htm


Recommended