WJLLWG 09-1 JLLIS CRB Items Revalidation for CRB 09-2

1. WJLLWG 09-1JLLIS CRB ItemsRevalidation forCRB 09-2 (as of 24 Aug 09) James Barr JLLIS Configuration Manager JS J7, Joint Lessons Learned Branch

2. Introduction • Rules of Engagement • Discuss the usability and functionality of each CRB proposal • Not a collaborative vote or group consensus • Shape the JLLIS for present and future • All COCOMs, CSAs, and Services are stakeholders and have one vote per CRB item • Voting Tool • Voting allows the JS to prioritization of resources • Prioritize votes from #1 to #26 • Vote “No” if the item is not in-line with the JLLP COP strategic direction

3. WJLLWG 09-1 CRB Proposals for Reassessment

4. 1 - Mobile JLLIS (6727) TTI: 160 hrs Definition: A Mobile-JLLIS for stand-alone computer capability with increased classification levels above Secret Purpose: USAF would like to have a Mobile JLLIS capability for collecting/storing observations for AF units that operate independently (and above the current SIPR classification level) AF Space Command and Air Combat Command would like to use JLLIS to keep track of their issues/lessons and to write AARs on stand-alone computers. Desired Results: Putting the JLLIS software on a stand-alone computer enables LL in the TS/SCI, Focal Point, SAP/SAR or higher realm. A stand-alone JLLIS database could be the answer to archiving L2s within the types of programs that require a level of security above SIPRNET. Agency Submitting item: USAF POC, Contact information: Mr Wayne Clark, DAF, YA-03, 703-588-8881, wayne.clark@pentagon.af.mil

5. 2 - Command JMETL Linkage (5090) TTI: 80 hrs Definition: Provides the ability to link JLLIS O&Rs to the commands’ JMETL Purpose: Currently, the ability exists to link the UJTL to JLLIS O&Rs. However, most units use a JMETL vice UJTL. JTIMS and DRRS also use a JMETL. Revisions to the JMETL in DRRS are migrated weekly to JTIMS. Linking O&Rs to a JMTEL vice UJTL would be more useful for the command by making more applicable information available for both assessment and readiness determinations. Desired results: The ability to link JMETL to the commands’ O&Rs Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil

6. 3 - Add IMS Issues to Joint Search (6385) TTI: 24hrs Definition: The ability to access Active IMS issues via Joint Search Purpose: To provide JLLIS users the ability to access Active IMS issues via Joint Search to enable them to gain from the knowledge gained by others through their issue resolution efforts Desired results: Active IMS issues accessible via Joint Search Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil Note: supersedes 3811

7. 4 - IMS Templates (5891) TTI: 24 hrs Definition: The ability to modify display of Collaboration and Resolution templates Purpose: Currently, when a user selects the option to apply anew template for issue resolution, the gatekeepers of that template are added to the top, while the original template and its gatekeepers comments are at the bottom. This is contrary to the chronological flow of completed work. Additionally, users may want to display all work completed either chronologically or functionally, requiring the ability to modify the display of templates utilized. Desired results: The ability to modify the display of all templates utilized in IMS to meet organizational needs Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil Note: supersedes 3768 and 5862

8. 5 - IMS at Tier 2 Level (4471) TTI: 40 hrs Definition: IMS available to Tier 2 CLMs Purpose: IMS provides a significant issue resolution capability. As such, it is recommended by NORAD and USNORTHCOM that IMS become the joint issue resolution standard. To be successful, all users of JLLIS, including Tier 2 CLMs, should have the ability to use the IMS. This will facilitate the natural progression from internal resolution to COCOM resolution to joint resolution by using the same program with different templates as required. Desired results/long range goal: IMS available to Tier 2 CLMS IMS adopted as joint issue resolution system Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil

9. 6 - Selecting Users for Access to Restricted Binder(5576) TTI: 40 hrs Definition: The ability to select multiple users, or a usersgroup, for access to a restricted binder Purpose: Currently, the creator of a restricted binder provides access to selected users one at a time -a considerable process when numerous users are to be added. The creator of the restricted binder should be able to select multiple users for accessat one time, or be able to create and add an entire user’sgroup (such as a team of SMEs within a Tier 2) Desired results: The ability to select multiple users at the same timefor access to a restricted binder, or to create (for routine use) user groups that can be added to theaccess of a restricted binder at one time Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil

10. 7 - Adding Binder Function to Reports Library (5741) TTI: 24 hrs Definition: Add Binder capability to Reports Library Purpose: Just as Binders have proved beneficial for the management of O&Rs, binders would provide similar benefit to the Reports Library. Currently, all reports are listed linearly, with the ability to sort alphabetically. However, this list becomes quite cumbersome as more reports are added/stored. The Binder function would enable reports to be “filed” under various titles, such as exercise name, function, mission area, etc Desired results: Add Binders capability to the Reports Library for effective filing and easier access Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil

11. 8 - Personalizing “My Binders” (5756) TTI: 40 hrs Definition: The ability for a user to select which binders are displayed and the order of their display Purpose: The use of Binders continues to grow. As such, a long list of Binders are displayed when selecting MyBinders, making it less effective. Users should be able to select which binders they want displayed, as well as thedisplay order. This would avoid confusion, particularly since many binders created by other users have the same or very similar names Desired results: User ability to manage display of Binders Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil Note: This issue also discussed in CMT#5576

12. 9 – Network Specific JLLIS (6388) TTI: 120 hrs • Definition: Network Specific JLLIS • Purpose: Capability to share lessons learned based on the network accessibility. JLLIS would be stood up on various coalition type networks such as CFE-A, CFE-K, CFE-J, for military bilateral networks etc and/or commercial networks for non-military and interagency participants. • Desired results/long range goal: Supports multinational and interagency lessons learned sharing. • Agency Submitting item: USPACOM • POC, Contact information: Gregg Sanders, 808-477-7767, gregory.sanders1.ctr@pacom.mil

13. 10 - Inter-visibility of O&Rs for Services & COCOMsTTI:155 hrs Definition: All Service O&R shared with COCOMS made viewable in their O&R Search and all applicable COCOM O&R shared are made visible in their O&R Search. Purpose: JLLIS needs to have a capability to share observations between Services/COCOMS. An observation sharing feature would allow a Tier-1 Administrator/Manager to view an observation sent forward to a Service or COCOM JLLIS site for status updates/coordination. Desired Results: Ability to display an O&R that has been “shared” between JLLIS master sites. O&Rs are viewable in an Observation Search in both the Service as well as COCOM master sites--regardless of which JLLIS master site the report is enters the system. Agency Submitting item: USAF POC, Contact information: Mr Wayne Clark, DAF, YA-03, 703-588-8881, wayne.clark@pentagon.af.mil

14. 11 – Tagged-Based Reviews of Knowledge Claims TTI: 480 hrs • Definition: Rated knowledge claims from a collection of actual user feedback to quantify and rank system knowledge claims. • Purpose: Each registered user in the system can rate items. Ratings can be placed in a form to associate a user to an item and that association has a numeric value of 1 to 5. Items can then display their average user rating. • Desired results: Actual users determine the best practices and ideas. Users are the relevant population to determine “Best Practices.” • Agency Submitting item: Joint Staff, J-7 • POC, Contact information: COL Rick Fenoli, 703-697-3665, richard.fenoli@js.pentagon.mil

15. 12 - Cascading/Multiple Role Authorities (5765) TTI: 800 hrs Definition: Role authorities are cumulative, starting with basic authorities of registered users and continuing to administrators Purpose: Currently, each role is separate and distinct from another. In many cases, authorizations at one level do not carry-over to the next higher level, but may need to. This creates the need to have multiple persons assigned in an organization to do many of the roles that are implicit in one person’s job description. One example is the difference between CLMs and Team Members – Team Members have access to Team Tools whereas CLMs do not; however, CLMs need access to IMS but cannot get it as they cannot select Team Tools. But changing CLMs to a role of Team Member then precludes the ability to edit Tier 2 O&Rs Desired results: Role authorities should be cumulative, or administrators should have the ability to multiple-designate specific role privileges for their CLMs Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil Note: coupled with 5083

16. 13 - Tier 2 Administrative Capabilities (4558) TTI: 800 hrs Definition: Tier 2 CLMs should have greater administrative capabilities, including the ability to create subordinate Tiers and modify drop down menus such as Event Names Purpose: One of the keys to the success of a joint lessons learned program is getting “buy-in” at the lowest levels. However, the administrators at the Tier 1 level are the only ones that can effect desired changes. Making the lessons learned tool more user-friendly at the lower levels would lead to greater participation throughout the unit. Tier 2 CLMs should have the ability to manage and modify (within reasonable limits) the tool to greater meet their specific needs Desired results: Lessons Learned tool that meets the needs of all users, particularly below the Tier 1 level Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil Note: includes CMT# 4560

17. 14 - Linking of Team Members to Tier 2 (5083) TTI: 800 hrs Definition: Team Members should be linked to Tier 2 vice Tier 1 Purpose: CLMs manage O&Rs for their respective Tier 2s. As such, they have access to all Pending O&Rs WITHIN THAT TIER 2 and have edit capability. However, Team Members differ in that they have access to ALL Pending O&Rs within the Tier 1. For CLMs to use Team Members as SMEs with current JLLIS capabilities, they would subsequentlyprovide access to Pending O&Rs outside their Tier 2.For Team Members to be used as SMEs within a Tier 2, access needs to be limited to the Tier 2 to which they belong Desired results: Team Members linked to Tier 2; CLMs have the ability to designate Team Members within their Tier 2 Agency submitting item: N-NC POC, Contact information: LtCol DeMorat, (719) 474-8337, David.DeMorat@northcom.mil

18. Questions / Comments?