# Presentation: 273852

## Cory Mickelson,JPL Enterprise Information Architecture 
9th NASA-ESA Workshop on Product Data Exchange
May 3, 2007
Cory.M.Mickelson@jpl.nasa.gov

- 9th NASA-ESA Workshop on Product Data Exchange
- May 3, 2007
- Cory.M.Mickelson@jpl.nasa.gov

- Developing Taxonomies to Enable Product Data Exchange

## A Glimpse of Our Team

- Cory Mickelson
- System Engineer, Programmer and Developer
- Capabilities: RDF/XML, Faceted Navigation, SQL, Perl, PHP, Java programming, web design, web content management; some experience with OWL/Ontology Design
- Jayne Dutra
- Taxonomist, Information Architect
- Capabilities: Search, web design, portal technology, web content management, knowledge management, information architecture, taxonomy development, metadata design
- Our Past Credits:
- Inside JPL Portal (home page including enterprise search), NASA Taxonomyand Core Metadata, JPL Engineering Taxonomy and Metadata Spec, Faceted navigation pilot for flight projects
- Current:
- Developing unified, enterprise-wide search using faceted navigation coupled with traditional keyword search. Part of a larger Enterprise Information Architecture

## Problem Statement: JPL Today

- Electronic
- Libraries

- Engineering
- Repositories

- E-Mail Archives

- Financial
- Data

- Parts
- Catalogues

- Problem
- Reporting

*What did I call it?*
*Where did I put it?*
*How do I find it?*

## The Solution: An Integrated Enterprise Information Architecture

- Integrated with business processes and best practices
- Based on institutional policies and a common architecture
*Independent* of any specific repository or technology
- Able to deal with harmonization of information according to a larger point of view
- Relevant and useful to our customers

- The Solution: An Integrated Enterprise Information Architecture

*Expressed with a shareable metadata specification*
*and its values (taxonomy)*

## Information Building Blocks

- An integrated information architecture is made up of several components:
- Common Metadata Specification
- Core Metadata Specification for JPL Information Objects
- Common language (Controlled vocabularies)
- By discipline, product, life cycle, process, etc.
- NASA Taxonomy, JPL Taxonomy, Partner Taxonomies
- Business Rules for data reconciliation

## Metadata Specifications

- Information Objects (a.k.a. Documents, Drawings, etc.) should share a **core** set of metadata attributes.
- Ex: Title, Content Type, Author, Date, Organization, Mission/Project, etc.
- Some of the fields are free text (e.g. title), but some should be controlled by a vocabulary: Mission/Project, Instruments, Subject, etc.
- Vocabulary control ensures uniformity of data, enabling automated search, collection, and later through Ontologies, reasoning.
- Need for controlled vocabularies lead to a Taxonomy...

## Core Metadata

- Specification
- Online

*Expressed with metadata and *
*its values *
*(taxonomy)*

## Developing A Tiered Taxonomy

- Enterprise Information Architecture is tiered, some tasks require more granularity in a vocabulary than others.
- Different domains require different, but not completely unique, vocabularies.
- To date, we have completed a (Flight) Project Taxonomy, and in progress on a Business Taxonomy.

- Enterprise Taxonomy

## JPL Enterprise Project Taxonomy Goals

- Provides vocabulary values for the appropriate metadata fields
- Designed to be relevant for a domain of users (communities of practice)
- Provides a classification scheme for identifying content
- A means for tagging content so it can be used and reused in different contexts
- Derived from JPL standard gold sources
- Vocabulary owners are Subject Matter Experts in their domains
- Discoverable with Service Oriented Architectures or Semantic Web technologies

- JPL Enterprise Project Taxonomy Goals

- Project
- Taxonomies
- (Products)

## Developing A Tiered Taxonomy

- Enterprise Information Architecture is tiered, some tasks require more granularity in a vocabulary than others.
- Different domains require different, but not completely unique, vocabularies.
- To date, we have completed a (Flight) Project Taxonomy, and in progress on a Business Taxonomy.

- Enterprise Taxonomy

## Work We’ve Already Completed:Metadata Core Spec for the Project Domain

- Create Lab wide information standards for engineering products
- Design and document a Lab wide information content model
- Improve information access and retrieval, including cross repository search
- Integrated with NASA metadata and taxonomy specs

- Work We’ve Already Completed:Metadata Core Spec for the Project Domain

- Deliverable
- JPL Core Metadata Specification for Project Documentation, v1.0
- Developed by a cross organizational team
- Delivered March, 2005

***Sponsored by the JPL Office of the CIO***

- Project
- Taxonomies
- (Products)

## JPL Flight 

- JPL Flight
- Project Engineering Taxonomy

- Project
- Taxonomies
- (Products)

## Adding Richness Over Time

- Metadata Core Specification was a top down effort

**Metadata and Taxonomy**
**Standards**

- Repository
- A

- Repository
- B

- Repository
- C

- Project
- Taxonomies
- (Products)

## Adding Richness Over Time

- Metadata Core Specification was a top down effort
- For the Phoenix Faceted Navigation Pilot, we validated and improved our initial effort, using  a bottom up approach

**Metadata and Taxonomy**
**Standards**

- Repository
- A

- Repository
- B

- Repository
- C

**Mappings and Filters**

- Project
- Taxonomies
- (Products)

## Validation: Faceted Navigation Prototype for Engineers

- Semantic Search/faceted navigation for Flight Projects
- JPL Engineering Domain
- Pilot funded by JPL Chief Engineer
- For flight teams on Phoenix and CloudSat missions
- Completed in 6 weeks
- Goal: Provide cross repository search from a single interface based on
- Relationships of information objects
- Life cycles – mission and content
- Task analysis for specific roles
- Engineering processes

- Project
- Taxonomies
- (Products)

## Phoenix

- Semantic Search
- Pilot
** **15,000 items
-  5 repositories
-  Tagged with JPL
-    Taxonomy facets
-  Unified search from
-   one interface
-  Faceted navigation
-    for intuitive info
-    discovery
-  Sponsored by the
-   JPL Chief Engineer

## Some Further Use Cases: Faceted Navigation Using Relationships

- Project Manager:
- “I’d like to check all documents needed to complete my Certification for Launch to see what state they’re in, no matter where they are.”
- Cognizant Engineer:
- “I’d like to see all problem failure reports on a sub-system I designed and flew 5 years ago so I can incorporate the lessons learned into my current mission.”
- Project Information Management Engineer:
- “I’d like to see the status of all Phase B documents that I need to prep for an upcoming gate review so I know we’re ready.”

- Project
- Taxonomies
- (Products)

## Developing A Tiered Taxonomy

- Enterprise Information Architecture is tiered, some tasks require more granularity in a vocabulary than others.
- Different domains require different, but not completely unique, vocabularies.
- To date, we have completed a (Flight) Project Taxonomy, and in progress on a Business Taxonomy.

- Enterprise Taxonomy

## Developing A Tiered Taxonomy

- Enterprise Information Architecture is tiered, some tasks require more granularity in a vocabulary than others.
- Different domains require different, but not completely unique, vocabularies.
- To date, we have completed a (Flight) Project Taxonomy, and in progress on a Business Taxonomy.

- Enterprise Taxonomy

## Work In the Financial Arena

- JPL Business Domain
- Term clarification for vocabulary used in financial reporting, work force planning, estimating and proposals

**Sample Vocabulary Problem Term: ****Project**
- Oracle project number – financial costing system
- IBF/NSM project number – NASA reference
- PRL project number – JPL flight project name

*How can we efficiently search for information about a “**project”?*

- Business
- Taxonomy
- (Work and $$)

## IA for the Business Domain

| Strategic Question | Metadata Elements |
| --- | --- |
| What work are we doing?
What type of business is it? |   Work Type
 Business Type
 Work ID/ Project Name |
| How did we acquire it? |  Competition Type |
| Who is funding the work?
Who are we delivering it to? |  Role (inc customer, sponsor, partner, line roles 
  and project roles) |
| Who is doing the work?
What capabilities does it take? |  Organization
 Competency, Capabilities
 Work description |
| What phase is it in?
Where is it taking place? |  Work State
 Work Maturation Level
 Implementation Mode |

- Describing Work for Forecasting and Strategic Planning

- Business
- Taxonomy
- (Work and $$)

## Work Already Completed:Metadata Working Group for Business Domain

- Create Lab wide information standards for business/work products
- Design a Lab wide business information content model
- Improve information access and retrieval, including cross repository search and reporting
- Identify “Gold Source” owners of data

- Deliverable
- JPL Core Metadata Specification for Business, alpha version
- Developed by a cross organizational team
- Delivered May, 2006
- Next steps: validation and assigned owners

- Work Already Completed:Metadata Working Group for Business Domain

- Business
- Taxonomy
- (Work and $$)

## JPL Business Taxonomy - Alpha

- More work continuing with Integrated
- Business team for validation and
- expansion

- Business
- Taxonomy
- (Work and $$)

## Developing A Tiered Taxonomy

- Enterprise Information Architecture is tiered, some tasks require more granularity in a vocabulary than others.
- Different domains require different, but not completely unique, vocabularies.
- To date, we have completed a (Flight) Project Taxonomy, and in progress on a Business Taxonomy.

- Enterprise Taxonomy

## Developing A Tiered Taxonomy

- Enterprise Information Architecture is tiered, some tasks require more granularity in a vocabulary than others.
- Different domains require different, but not completely unique, vocabularies.
- To date, we have completed a (Flight) Project Taxonomy, and in progress on a Business Taxonomy.

- Enterprise Taxonomy

## Work Force Metadata

- Collect and document attributes about people
- Some use cases
- Access management – who are you and what can you see?
- Targeted content delivery – what content helps you get your work done?
- Work force planning – what skill sets do you have that we can apply to work?
- IT Services – How can we provision you with the proper IT services?

- Work Force
- Taxonomy
- (People)

## But What Goes Where?

**An Engineer**
**Specialty is Electrical Engineering**
**Works on propulsion systems**
**Worked on projects X, Y, Z**
**Currently working on A **
**As a Cog E **
**On propulsion subsystem**
**Project is in Phase C**
**Has published papers on propulsion systems **

**Corresponding Taxonomy Facet**
**Competency**
**Capability**
**Topic or Subject Matter**
**Past Assignments**
**Current Assignment**
**Role**
**System/Subsystem**
**Project Phase**
**Topic or Subject Matter**

*We can codify and track certain attributes for re-use*

- Work Force
- Taxonomy
- (People)

## Matching Attributes for Peopleto Attributes for Content

**Attributes About People**
**Competency/Discipline **
**Subject Matter**
**Past Task Assignment - Role**
**Current Task Assignment - Role**
**Subsystem/WBS**
**Task Phase**
**Associations to objects as Author**
**       ****or Reader/Subscriber**

**Attributes About Info Objects**
**Objects related to a Competency**
**Interest in Subject Matter Areas**
**Objects associated with Role**
**Information on a Subsystem/WBS **
**Objects associated with a project phase**
**Information on project products**
**Information on technologies**

- Matching Attributes for Peopleto Attributes for Content

**People Metadata  **

**Project Metadata**

- Work Force
- Taxonomy
- (People)

## Using People Metadata for Targeted Content Delivery in Portals and Dashboards

- Make content available to delivery mechanisms using Service Oriented Architectures
- Data streams presented as services and available for consumption by workers in portals, dashboards and other devices

- UDDI Registry
- WSDL
- SOAP, etc

-  PORTALS

- Source A

- Source B

- Source X,
- Source Y, Etc.

- Work Force
- Taxonomy
- (People)

## Developing an Enterprise Taxonomy

**Project Taxonomy**
- Content Type
- Mission Phase
- Organization
- Document State
- Missions/Projects
- System/Subsystem

**Work Force Taxonomy**
- Organization
- Competency/Skills
- Capability
- Missions/Projects
- Role

**Business Taxonomy**
- Work Type
- Funding Mechanism
- Business Type
- Organization
- Acquisition Type
- Missions/Projects

- Enterprise Taxonomy

-  Organization
-  Mission/Projects
-  Other facets

- Work with Domain customers and Subject Matter Experts to develop metadata specifications and vocabularies that enable their business processes

## Summing Up

- Information sharing and reuse necessitates a common metadata model, which leads to a common vocabulary (taxonomy)
- Taxonomy developed using an iterative process that is tiered
- Direct connection between IA and use cases, business questions
- Metadata specification defined
- Taxonomy definition: Values expressed with controlled terms where appropriate
- Domain specific taxonomies add business value
- Transition points enable interoperability
- Look for patterns of usage tied to business process
- Integrate across domains and upward to a meta level
- Implement and validate
- Long term stewardship and configuration management

- Business
- Taxonomy

- Enterprise Taxonomy

- Work Force
- Taxonomy

- Project
- Taxonomies

## Thanks!Cory.M.Mickelson@jpl.nasa.gov Jayne.E.Dutra@jpl.nasa.gov

- Questions, Discussion

## JPL Enterprise Information Architecture Roadmap

- Enable intelligent search and discovery mechanisms

***Focus Areas***

**JPL Enterprise Information Architecture Roadmap**

**Design and Plan**
** ****Architecture**

**Define Common  Information  Model **

**Data **
**Retrieval**
**& Reporting**

** ****Dashboard and Reporting Capability for PRL, iBMS, **
**Work Force and Engineering Products**

**ID Gold Source Providers, Train, **
**Process Definition – iBMS, PRL **

**IA Principles and Use Cases**

**Domain**
**Vocabularies**

**Auto-population tool**

**Test SOA Concepts: **
**DS, PRL **

**Deploy IA Tools in Production Environment**

**Business Taxonomy, v 1**

**People Taxo, v 1**

**Project Taxo, v 2**

**Bus T, v 2**

**People T, v 2**

**Enterprise Taxonomy /**
**Long Term  Maintenance of**
**Domain Taxonomies**

**MD Standards in IT Systems**

- 172 Systems       Other Systems

**Gold Source Committee**

**Auto-population of versioned **
**Gold Source terms**

**                                        ****Semantic Browse For Projects**

**MSL/Div 31 Sem Browse**

**IA Reviews for New IT Systems**

- Seamark

- Schemalogic

**Deploy Metadata Catalog**

**2009**

**2008**

**2007**

**Enable and Deploy Integrated Search Architecture**

**Prototype MD Catalog**

***Goals***

***Benefits***

- Create a unified
- Enterprise Data
- Reference Model

*Foster customer and partner relationships *

- Align and
- improve
- data quality

- Seamless data discovery
- enables
- better work performance

- IT Taxonomy

- IT Portfolio Reporting

- Namespace Schema

- Increasing Maturity

**Design and **
**Build an **
**Infrastructure**
**For IA**

- Build & operate
- an infrastructure
- that enables
- seamless
- data interchange

- Robust data
- interoperability
- enhances
- good business
- decisions

**IA Governance **
**& Gold Source**
**Enablement **

- Create IA
- Governance
- framework
- Identify and
- enable Gold
- Source providers

- Establish
- Authoritative
- Sources of data
- Reduce
- duplication
- of effort

**Semantic Web Data Models**

## High Level IA Systems Architecture 

**Web Services Wrapper**

- High Level IA Systems Architecture

**UDDI**
**(phonebook of web **
**services)**

**Seamark****Server**

**SchemaLogic****Server**
**(Taxonomy Management)**

**Search/Reporting/Portal****Applications **

- Taxonomy

**Repositories**
**(Docushare, Rules!, PDMS, ...)**

**Metadata **
**Catalogue**
***Semantic ***
***Representations***

**LDAP Metadata**
**Catalogue**
***Semantic ***
***Representations ***

- Metadata
- Schemas

**WSDL**

**WSDL**

**WSDL**

**WSDL**

**RDF, RSS**

**XML, RDF, XMLS, OWL**

**RSS, XML, SOAP**

**XRBR**

**XML**

- 10/10/06

**Taxonomy **
**Pick Up**
**Point**

**XML**

## Information and IT Services Delivery by Mission (and Content) Life Cycle Based on Role 

- Leverage Mission Life Cycle
- What roles are active at each stage
- What IT services are needed at each phase of a mission
- What capabilities are most in use at each phase of a mission
- Example:
- Proposal Phase                  System Engineering Capability
- Activities 		Trade Studies, Model Building, Requirements Formulation
- IT Needs 		Document storage, simulation and visualization, traceability
- IT Apps 		Docushare, MBED, Cradle, CORE
- Other Proposal Phase roles and activity types:
- Project Managers – do planning
- Principal Investigators – formulate science definition goals
- Project Resource Administrators – create budget and schedules
*This is a very rich area for us to mine!*

## A view from the top . . . 

**Priority**

**Goal**

**Capabilities**

**Improve our ability to work more efficiently**

- Improve ability to store, archive, retrieve project information

- Enterprise
- Content
- Management

- Product Lifecycle Management

- Information
- Discovery and Retrieval

- Document Storage
- Web Content Management
- Records Management
- Work Flow

- Product Data Management
- Requirements Management
- Risk Management

- Cross Repository Retrieval
- External Partners Data Exchange
- Access Verification
- Export Compliance

**Processes**

**Technologies**

- Security: Authentication
- Metadata Standards

- Electronic Library - DocuShare
- Document Repository - Teamcenter Community
- Web Content - Rythmyx

- PDMS - Teamcenter Enterprise
- Requirements Repository – DOORS, Cradle, Core
- Risk Management - ARM

- Portals – Inside JPL, Teamcenter Community
- Search Engine – Google
- Problem Reporting - PFR/PRS
- Manufacturing/Inventory - iPICS

- Domain Taxonomies
- Schema Registries

**Common Information Infrastructure**

- Unique Object Identifiers

- A view from the top . . .

**IA work supports**
**many different **
**stakeholders**

## Unified Search for JPL Projects: Goal

- JPL Directory

- Docushare

- PDMS

- PRS

- External

- Project System Requirements v 2.0 (DOORS)
- Hardware Drawing - Parts v 1.0 – PDMS
- Hardware Drawing – Assemblies v 3.0 - PDMS
- ECR – PDMS
- ECR waivers – Team Center Community
- Problem Failure Report - PRS
- Associated Documentation - Docushare

- Resulting in integrated responses like this:

**Requires Semantic **
**Web technology and**
**Service Oriented **
**Architectures**
**To automate**

## Unified Search for JPL Projects: Goal

- JPL Directory

- Docushare

- PDMS

- PRS

- External

- Combinations of metadata...
- Project = Project XYZ
- Document State = Preliminary or Official
- Content Class = Controlled
- Business Purpose = Product Data
- Content Type = Appropriate Values
- Document Status = Lifecycle values

- Users would like to be able to find **related sets** of data. For example: “I want to see all of the released documents for my project that are required for system certification for flight”

- Query can be applied across multiple repositories...

## Taxonomy Packages Equivalencies for  Vocabularies That Change Over Time

- Taxonomy Packages Equivalencies for  Vocabularies That Change Over Time

-  MER A= Spirit,  MER B = Opportunity
-  MER A and MER B are types of Rovers
-  Rovers fall under the subject heading of
-   Robotics/Cybernetics

- Built into the back end
- and transparent to users

*Users don’t have to have special contextual knowledge *
*to find information items*

## Taxonomy Packages Equivalencies for  Vocabularies That Change Over Time

- Acronyms can be easily defined using Equivalent
- Terms or Synonyms in RDF

- Taxonomy Packages Equivalencies for  Vocabularies That Change Over Time

- MER A= Spirit,  MER B = Opportunity,
- MER A and MER B are types of Rovers
- and fall under the subject heading of
- Robotics/Cybernetics

- Built into the back end
- and transparent to users