Task Management IPT Tasker Integration Service Pilot COI 12 January 2010

1. Task Management IPT Tasker Integration Service Pilot COI 12 January 2010 CDR Michael Kelly, michael.kelly@js.pentagon.mil JCS J65B 703-697-5966

2. Overview OSD Joint Staff • Organizations have task management systems on different networks that are not interoperable with each other. • In February, the VCJCS directed IT working group to recommend a task management capability that could be offered as an enterprise service. COCOMs Agencies Services Maj Coms Components JTFs Current: Email is the primary method of moving taskers between DoD organizations Goal: Interoperable task management using common policies and standards Units

3. EGB & Enterprise Solutions Process TIS DP 1 March 2009 TIS DP 2 May, 2009 TIS DP 3 December 17, 2009    Developing an Enterprise Task Management Capability

4. DP2: Recommended Course of Action Presented to the EGB for DP2 Choose “Best of Breed” of existing solutions Federate Existing Solutions: Recommended and Chosen Develop bridge to true enterprise solution/migration path Provide standard interface specification/ common vocabulary Leverage common information exchange requirements Develop requirements for traditional acquisition approach Status Quo

5. TIS Pilot: Federate Existing Solutions COA: Federate Existing Solutions: Recommended and Chosen Tasker Integration Service CML CML *Pilot tested on NIPR CML CML Standard Interface Standard Interface Standard Interface Standard Interface Taskers CRM/TMT Metastorm SACCP Navy AFDW Joint Staff WHS The TIS Supports GIG 2.0 – Joint Infrastructure

6. TIS Pilot COI structure Task Management COI/IPT (Joint Staff J6) • Promote & review COI activities • Resolve cross-COI discrepancies TIS Pilot Membership • Ensure appropriate participation • Act as primary COI POC • Track milestones & success criteria TIS Pilot COI (Joint Staff / WHS) Capability Design Development WG (Joint Staff / WHS) Governance WG (Joint Staff / AFDW) Vocabulary WG (AFDW / DoN CIO) • Scope: • Review SIDCCs architecture • Implement Pilot and Demonstration • Run Tests • Evaluate Pilot • Scope: • Define & implement high level COI capability roadmap and schedule milestones • Stand up Pilot WG as needed • Develop repeatable process to demonstrate COI products (e.g, COI vocabulary) • Synchronize COI products with core enterprise services (e.g., NCES) • Act as primary COI POC • Track milestones & success criteria • Capture Lessons Learned • Scope: • Develop/Refine community vocabulary that is necessary to support the TIS pilot

7. Objective: To prove a concept and test to evaluate the feasibility and value of a federated task integration service for the DoD. Goal 1: Evaluate feasibility of a decentralized/federated approach for task management in the DoD community. Goal 2: Evaluate organizational agility within a service oriented architecture construct. Goal 3: Determine technical feasibility of a decentralized approach for enterprise task management. TIS Pilot Objective and Goals Implement DP2 Recommendation: Leverage Standard Integrated Document Control and Coordination System (SIDCCS) Efforts

8. Pilot Test Schedule https://www.intelink.gov/wiki/TIS_Pilot

9. TIS: Common Vocabulary/ Interface Post-TIS Pilot Pre-TIS Pilot TIS Common Interface Language/Vocabulary Sys C Sys G Sys C Sys G 28 interfaces Sys D Sys H Sys D Sys H Sys A Sys E Sys I Sys K Sys A Sys E Sys I Sys K Sys B Sys F Sys J Sys L Sys B Sys F Sys J Sys L 28 interfaces needed for system-to-system connectivity. No common/ interface language to permit data sharing. Each system has its own language, but shares data via a single, common/interface language. TIS pilot established an interface language for all tasker systems. • Each system defined its own vocabularies and data schemas • Systems unable to electronically share info without human interaction • Objective: to evaluate the feasibility of a federated task integration service for DoD • Goal 1:Success…Developed integration requirements & functionality. • Goal 2:Success…Established community-accepted task management workflow. • Goal 3:Success…Established and verified technical proof-of-concept The TIS COI Supports GIG 2.0 - Common Policies and Standards

10. Common Data Model and Vocabulary Technical and functional definitions SIDCCS vocabulary needs modification Operational Use Cases Need clearly defined operational business rules SIDCCS use case list not comprehensive Supporting Attached Documents Document encoding procedures need standardization Document flow process needs to be explicitly defined Pilot Lessons Learned

11. DP3 Decisions • Approve technical architecture and entry into Phase IV of the ESD&G Process • Direct IPT to complete Enterprise Solution Funding Approach • Direct IPT to complete Enterprise Solution Governance Details • Approve Washington Headquarters Services to serve as initial Implementation Agent YES NO  

12. COI Phases 5. Develop Services 7. Migrate Solutions 1. Define Objective 2. Establish Team 3. Develop POA&M 4. Assign Metrics 6. Document Results • Document results/LL • ------------------- • Test Report • Test Plan • Integration Guide • LOE questionnaire • TIS Handbook • CONOPS (draft) • Pilot Outbriefs • Adopt and adhere to “Spirals” and develop a POA&M • ------------------- • Project schedules for Phase III-Pilot and Phase IV • Spirals reflected EGB phases and Decision Points • Define and capture metrics for each spiral • ------------------ • Pilot testing goals established • Develop data and/or web services, that are discoverable ,exposable to unanticipated users • ------------------- • Registered Pilot artifacts • COI Directory • MDR • Service Registry • Forge.Mil • Pilot: technical demo • Develop a plan for migrating technical solutions from the pilot effort into an operational environment supporting operational users • ------------------- • Implementation Plan • IOC development • Phase IV work • Transition- funding • Governance • Collaboratively define a concise objective and vision, including any requirements, processes, use cases, policies • -------------------- • Objective and goals defined • Timeline scoped within tight boundaries • Defined use cases • Establish team with strong leadership and effective partnership • ------------------- • COI has strong participation from IPT and Pilot members • Use of wiki • DCO, dial in • Support of VCJCS • MOU • Charter

13. Task Management COI: Update Task Management COI (Co Chairs: JS / WHS) • Scope: • Preside over COI meetings • Adjudicate COI conflicts • Coordinate with the Implementation Agent • POA&M • Primary external POCs • Monitor and assist COI working groups Initial Implementation Agent: WHS Governance WG Leads: JS / WHS Technical Implementation WG Lead: Mr. Carl Vercio - WHS Business Rules/Functional Process WG (Leads: JS / WHS) • Scope: • Ensure DoD & Industry Standards are followed • Represent COI on CCB • Establish Policy (with Implementation Agent) • Define Metrics • Work with Implementation Agent on SLAs • Work with Implementation Agent on Life-cycle Policies • Maintain Presence in Enterprise Registries • Maintain COI Charter • Ensure Intelink Wiki for COI is maintained • Record and distribute meeting minutes • Scope: • Define TIS Vocabulary • Modify TIS Vocabulary (including the definitions of extensions) • Develop and refine architecture products • Scope: • Identify Business Rules/Functional Processes • Define/Design Required Architecture Products (with Implementation Agent and Joint Staff) • Conduct TEMs • Requirements Gathering • Define Reporting Requirements • Define User Assistance Requirements including Help and Training

14. Questions CDR Mike Kelly, J65B https://www.intelink.gov/wiki/Task_Management_IPT