PMS320
- 格式:pdf
- 大小:2.41 MB
- 文档页数:39
AIPS/GAITS Surface
Problem Cause Solution
-- Lack of integration across applications & data sources -- Lack of data for decision making -- Duplication of data, applications, & work -- Data sources were developed as stovepipes (proprietary data & interface standards) & by different natural process owner -- Integrate processes through a unified data environment -- Process Reengineering – better flow of information between processes tracked in Use Cases -- Less admin work & overhead (increased efficiency) -- Better program/acquisition management (efficient spending)
Integrated Suite of Applications
Enterprise Integration
Virtual SYSCOM processes are nonEnterprise to redundant, high Enterprise velocity, automated, & achieving internal seamless. Real time process integration and Integrated information visibility extending focus Enterprise outside of the reaching a high level enterprise of process & systems integration
Operations data is a mix of relational data (30%) & content (70%)
Operations data
Operations Data - Doctrine - Operations - Training - Mission Programmatic - Schedule - Cost - Contracts Product Data - Specifications - Features - Requirements
FMPMIS CNOB/TLS Surface LCRS-FMP AMPS CVN TAMS Subs
10
The Integrated Digital Environment Concept
11
What is an IDE?
/ide/learning_modules/ide/what_is_an_ide.htm
7
Benefits
Issues within the Data Problem
• What data should be shared between global external sources & organic local sources? • Do we understand the different needs between relational & content data? How should we manage our relational & content data?
Concept
Start Production
End Production
Retire
4
POR Over Time
-The Slope of the Line can be controlled by processes concerning Speed to Market - The depth of detail for the POR depends on our Supply Chain Management Processes - Our processes for Customer Satisfaction (like HSI & Training) determine user effectiveness for the POR
• • • • • Multiple Databases Multiple Applications Common Data Elements Not Shared Proprietary Data Elements Duplicate Efforts
6
Causes of the Data Problem
Process Enterprise moving towards a process focus, breaking down silos
What is the Navy Data Environment
15
Our Recent Past
No Connection between databases
PROTOTYPE
x
PRODUCTION
x
LONG LEAD EQUIPMENT PURCHASED FOR INSTALL
+ 5 YEARS
+ 4 YEARS
+ 3 YEARS
+ 2 YEARS
+1 YEAR
EXECUTION
9
Possible Solutions
• Connect All Databases (Many Translators) • Create One Standardized Database (Modify Applications & Inflexible) • Create Connections from All Databases to an Integrated Database (NDE)
CONCEIVE DEVELOP INTEGRATE INSTALL MAINTAIN & DISPOSE
PO R
X
PO
R
Technology Change
V1 .0
V1 .1
X
1 Year 2 Years 3 Years 4 Years
5
Now
TIME
The Navy’s Data Problem
FMPMIS CNO Avails SPAWAR IDB/TLS LCRSFMP CVN TAMS Subs AIPS/ GAITS Surface AMPS
Multiple Applications working with multiple databases
FMPMIS CNO Avails
SPAWAR IDB/TLS
Programmatic data Programmatic data Product data Product data
Product data is a mix of relational data (70%) & content (30%) Programmatic data is a mix of relational data (80%) & content (20%)
8
PRODUCT & PROGRAMMATIC RELATIONAL DATA TIMELINE
! "
100%
75%
OTHER MATERIAL FINALIZED
50%
C3 PRODUCT IS A DESIRE IN POM, WITH ONLY GENERAL CAPABILITIES
25%
Enterprise Data Management with the
Navy Data Environment
Paul Shaw
22 April 2004
1
Federal Enterprise Architecture Framework
"Interoperability begins at the data level, not the systems level, have a common language, common tagging. Data is our most important product." Brig. Gen. Mike Ennis, Marine Corps Dir. of Intelligence
2
The Data Problem for Enterprise Architecture
3
The Lifecycle Nature of POR Data
As a POR goes through its lifecycle, the amount & Sample: nature of its data transitions over time
12
Integration Progression
Process Enterprise Integrated Enterprise
Virtual ERP Enterprise Solutions Suite of Navy Enterprise Portal
ENTERPRISE VISIBILITY
Fragmented Enterprise
User Interface
Portals Applications
Integrated Data Environment