1 / 19

Requirements for Standards & Commonality with Regard to

Requirements for Standards & Commonality with Regard to Knowledge Based Systems for Coalition Operations. Alice M. Mulvehill Ted Kral BBN Technologies BBN Technologies amm@bbn.com tkral@bbn.com. April 2002. Issues to be Addressed. How standards have been applied in the development of

nova
Download Presentation

Requirements for Standards & Commonality with Regard to

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements for Standards & Commonality with Regard to Knowledge Based Systems for Coalition Operations Alice M. Mulvehill Ted Kral BBN Technologies BBN Technologies amm@bbn.comtkral@bbn.com April 2002

  2. Issues to be Addressed • How standards have been applied in the development of • large decision support systems to date. • The lessons learned. • The degree and type of standardization required to support Coalition Operations.

  3. Observations: Case Studies • ARPI (ARPA Rome Planning Initiative) • JTF-ATD (Joint Task Force – Advanced Technology Demonstration) • ACOA (Adaptive Courses of Action) • JWIDs (Joint Warrior Interoperability Demonstration)

  4. ARPI • Emphasis on mixed-initiative planning • Standards • Development of a common environment for experimentation • Technical Integration Experiments (TIE) • Integrated Feasibility Demonstrations (IFD) • Common domain • Development of a Common Plan Representation

  5. JTF-ATD • Focused on the use of a common schema • Standards • Developed a distributed planning environment using • planning cells called Anchor Desks • - CORBA • - web based object servers • - common plan representation (common plan object) • Standards were developed and enforced through the JTF-ATD • reference architecture • Extensive usage of training and experimentation via • demonstrations and bootcamps (concentrated training)

  6. JTF Reference Architecture

  7. The ACOA Environment • The initial focus was to be able to rapidly adapt the COA • (Course of Action) to changing situations. • ACOA is based on a user-centric, iterative development philosophy

  8. The Cooperation Continuum

  9. Terminological Evolution

  10. Standardization Approach Common or Shared • architecture • plan representation • planning process • hardware • users • programming language • terminology Commonality is more important over time Commonality is less important over time

  11. Special Needs of Coalition Teams • Cognitive issues associated with culture • training • terminology • operational concepts • planning process

  12. Using Ontologies • Multinational coalition teams will require the establishment of some • standard operating ontology • Ontology mapping tools will be needed to facilitate entry of • new coalition members at varying levels of participation and trust

  13. Forming Coalitions • JWID as a case study for coalition planning • What is the role of similarity in team formation?

  14. Joint Warrior Interoperability Experiments (JWID)

  15. Technology Used in JWID • WWW • Collaborative planning tools • - whiteboards • - shared applications • - on-line chat • Coalition issues • - several countries formed a group early • - one country was a late joiner

  16. Observations from JWID • The following factors affect interoperability and distributed collaborative planning: • platform • speed and efficiency of I/O between functionally related systems • the impact of the network type on intercommunication • the impact of environmental issues on interoperability • collaboration between geographically distant systems • varying styles and level of human collaboration techniques • skill level of the operator Could these lessons learned be used to develop a set of standards to support multi-national coalition formation and development?

  17. Similarity Issues Regarding Team Formation • Determine how similar a new partner is to existing team members • Similarity can be assessed in terms of: • - culture • - technological sophistication • - planning style • - social practices • If the new member is very similar -- present with a common ontology or schema. • If the new member is very different -- develop a mapping • table to allow them to communicate with existing members. • Can Similarity Metrics be used to recommend team formation?

  18. Conclusion • The degree of standard requirements seems directly related to the degree of interoperability and integration desired. • The degree of partnership in a team influences interoperability and data sharing and can change over time. • Standards can have as big as impact as you desire.

  19. Recommendation • Adhere to a minimum essential policy with respect to standards placed on software systems. • Address the area of standards at the beginning of a program and do not ignore the issue or attempt to retrofit later. • Evaluate any Coalition impact that could be caused by differences in terminology and process exchange problem. • Examine issues associated with trust in partnership formation. • Since we cannot standardize the user set, perhaps we need to create a compensation through the software to allow people to transition from non-common to common environments.

More Related