What Are The Drone Anti-jamming Systems Technology?
Dh Government
1. Digital Harbor Enabling Composite Applications Delivering Integration to the Desktop August 2005 The Industry Leading Platform for Rich Internet Composite Applications
2.
3. Gartner Predicts the future of IT 2003 2005 2007 2009 Business Agility Applications Maze Composite Applications “ The Next Massive Wave of Innovation and Demand for IT will Start in 2007” - Gartner, September 2004 Gartner, 2004 Service-oriented application development accelerates Service software markets appear Composite development approach dominates Broad availability of ‘pure’ service-oriented application software Early fusion-capable applications Next-Gen Applications Broad availability of fused processes New capabilities drive massive process innovation
4.
5.
6. IT Modernization: Application Evolution Cross-Functional Fusion (Data, Processes) Unified Access Operator (Publish-Subscribe) Knowledge Worker Rich Context, Analytics & Collaboration End User Analytics End- User Integration Transform Operators into Knowledge Workers Portals Next-Gen Applications Smart Client (RIA)
7.
8. Barrier: Business Users are Trapped in An Applications Maze Current approaches lack the flexibility and ‘integrated environment’ that business users need to make effective knowledge based decisions What is needed is to insert Real-time Intelligence in the context of Business Process Trade Clearance Process CRM Warehouse Risk Warehouse New Account Process Analytic Stack Applications Stack Customer Analytics Risk Analytics New Account App Trade Exception App Operational Silos Account Product Transaction Billing Claims Communication Account Product Transaction Billing Claims Communication Business Users No analytic context Hardwired No process context Static data model Read-Only, Batch Action without Intelligence Non Actionable Intelligence
9. Composite Applications: A New Approach Fusion Smart Client Integration Applications Services Databases Fuse and Relate Disparate Information 2 1 Combine data from any source Present in an Interactive, Composite UI 3
10.
11. A Composite Application for Defense Intelligence RFI Map Equipment Resources Actor Other Tasks 1. Fuse services from multiple applications 2. Correlate information in context 3. Drill down in Real-Time 4. Ask questions across databases 5. Infer links across systems Other Tasks
12. Connect-the-Dots: Leverage Existing Systems to Build Systems of Systems Intelligence + Action = Real-time Decision Making Business Users Operational Silos Account Product Transaction Billing Claims Communication Account Product Transaction Billing Claims Communication CRM Warehouse Risk Warehouse New Account Process Straight-Through Processes Link disparate data models and processes into unified view Add information from related systems including apps and unstructured data Add semantics to transform static schema into a dynamic ontology Manage Context to enable 360° Interaction Composite Cross-Sell Composite Risk Management
13. Xaction Email AML HR Customer Technology: The PiiE™ Platform Composite UI (Smart Client) Present information to users in a real-time, interactive XML interface Composite Schema (Business Ontology) A Business Ontology describes the semantics of data relationships, workflow, and events Composite Queries (EII) Logically map multiple databases or web services as if they came from a single source
14. Types of Composite Apps : All Knowledge Applications Knowledge Integration is driven by what people do…everyday Case Management Dashboards Reports Planning & Forecasting Business Activity Monitoring Event Management
15.
16. Composite Application Architecture: What is Missing “ Currently, enterprises have no means of presenting correlated views of their data assets to end-users.” – Burton Group, 2003
17.
18. Composite Applications make information more valuable by helping users to “connect the dots” across systems Manufacturing Dashboard Analytic Simulation Environment Logistics Management Inventory Dashboard Customer Dashboard Intelligence Production Analysts Workbench Incident Management Mission Management Collections Management Examples: Composite Applications in Defense
19.
20.
21.
22.
Hinweis der Redaktion
This is what Digital Harbor does – Enable Composite Applications Key Takeaways: We link information from multiple systems We enable business users (who think in their jobs) to connect the dots and make real time decisions We have been recognized with several awards
2 points - 1) Here is our view of what we need to address and the scope of Mantas / SS 2) How is CCFSB covering all of this
2 points - 1) Here is our view of what we need to address and the scope of Mantas / SS 2) How is CCFSB covering all of this
To achieve this, Digital Harbor offers three new layers of technology. Starting at the bottom, we logically access information in many different sources. EII = Enterprise Information Integration. We leave the information where it physically resides and link to it. We can access data in databases, web services, XML documents, JMS messages, and other enterprise applications as if they came from one source. For instance, you may have customer data in two different databases (and it may be stored as cust_name and cust_id, but it is one concept, a “customer”). At the middle level is where a lot of the “magic” happens. Digital Harbor preserves the meaning of the underlying information and captures the relationships between things. For instance, we know what a customer is because we know that it is related to other things—other pieces of data like accounts and branches and advisors and exceptions, as well as information about processes (who approved the loan), rules (is it a large customer or small customer), and events (customer requests a new loan). We have a fancy name for this layer—called a “Business Ontology”—but it’s a very simple idea. Just like you have a schema in any one database that describes how Data A is related to Data B, a Business Ontology is like a schema across systems. And…since there is information in our processes, rules, and events, the Business Ontology links together those pieces of information as well. (For the technologists in the crowd, ontologies are a very hot topic in the industry, being led by Tim Berners-Lee who invented the internet and the W3C, where we participate in the 3 rd largest committee they have on OWL (ontology web language). ) Finally, as we’ve described in the compliance example, it isn’t enough to show the data side-by-side on a static screen. Users need to seamlessly and dynamically link between pieces of information that may originate in different physical systems at the bottom level. Our “Smart Client” is a composite interface that preserves the meaning of the information it displays, along with the relationships between things. It interoperates with portals and other web UIs, but because it is tied to the middle layer, it adds “intelligence” that they don’t have.
Big Idea Digital Harbor excels at integrating at the “system of systems” level. (Animate) Here we surround the surveillance applications and enterprise enable them.
2 points - 1) Here is our view of what we need to address and the scope of Mantas / SS 2) How is CCFSB covering all of this
So let’s look a an example of a composite application we built for a defense customer The first thing you’ll see is that the interface combines information from various stove-pipe applications together, all in one interface over the web. You’ll also notice that this composite application is very rich in functionality that you usually don’t see in static web solutions. In this example, the composite application is pulling information from an Oracle database, a Sybase database, a mapping server – such as ESRI, and a scheduling system. Click, Click What you see now is that as I click on a new piece of information from the Oracle database, the application automatically changes the information from the other data sources to match the information I just clicked on. This is automatic correlation because the objects know about each other. Click Click Now, you can drill down on any piece of information and get data related to that piece of information. For example, here, I clicked on the map and I automatically see an image that comes from yet another imagery system, that is associated to that image marker or lat/long. Click Click Now, let’s see the real power of the Ontology. Because every piece of information is related to each other, I can ASK questions about any piece of data. In this example here, I’m looking at the scheduling system and asking – who is the current person or actor responsible for this task? I get my answer – Buck. I can even go further and ask – what other tasks does Buck have on his plate. And I automatically get that. The key concept to grasp here is that the information is being fetch across multiple data sources and that the composite application developer never added this functionality in by coding. Users get this automatically through the ontology. Just in this example, you’re asking information from a workflow process while in runtime and combining it with relational data. That’s something today that requires an intensive amount of integration and coding by back-end developers that are not taking a composite application approach.
2 points - 1) Here is our view of what we need to address and the scope of Mantas / SS 2) How is CCFSB covering all of this
To achieve this, Digital Harbor offers three new layers of technology. Starting at the bottom, we logically access information in many different sources. EII = Enterprise Information Integration. We leave the information where it physically resides and link to it. We can access data in databases, web services, XML documents, JMS messages, and other enterprise applications as if they came from one source. For instance, you may have customer data in two different databases (and it may be stored as cust_name and cust_id, but it is one concept, a “customer”). At the middle level is where a lot of the “magic” happens. Digital Harbor preserves the meaning of the underlying information and captures the relationships between things. For instance, we know what a customer is because we know that it is related to other things—other pieces of data like accounts and branches and advisors and exceptions, as well as information about processes (who approved the loan), rules (is it a large customer or small customer), and events (customer requests a new loan). We have a fancy name for this layer—called a “Business Ontology”—but it’s a very simple idea. Just like you have a schema in any one database that describes how Data A is related to Data B, a Business Ontology is like a schema across systems. And…since there is information in our processes, rules, and events, the Business Ontology links together those pieces of information as well. (For the technologists in the crowd, ontologies are a very hot topic in the industry, being led by Tim Berners-Lee who invented the internet and the W3C, where we participate in the 3 rd largest committee they have on OWL (ontology web language). ) Finally, as we’ve described in the compliance example, it isn’t enough to show the data side-by-side on a static screen. Users need to seamlessly and dynamically link between pieces of information that may originate in different physical systems at the bottom level. Our “Smart Client” is a composite interface that preserves the meaning of the information it displays, along with the relationships between things. It interoperates with portals and other web UIs, but because it is tied to the middle layer, it adds “intelligence” that they don’t have.
Big Idea Digital Harbor excels at integrating at the “system of systems” level. (Animate) Here we surround the surveillance applications and enterprise enable them.
We’re an enterprise software company. Its typical in this forum to share financials at the end, but we’re somewhat atypical in that we have been around for 5 years, have revenues, have a product, and are cash flow positive…. Key Takeaways: We’ve been around We make real money, have real customers High profile individual investors are excited about us
Big Idea Digital Harbor excels at integrating at the “system of systems” level. (Animate) Here we surround the surveillance applications and enterprise enable them.
Digital Harbor got its start in 1997 in the Defense Intelligence world (NSA). The reason they turned to Digital Harbor is that they have enormous volumes of information (peda-bytes!), in different forms (data, documents, email, images, etc), and in different sources/silos. Their analysts needed to (in their words) “connect the dots” across these types and sources—to “compose a picture of the situation” so they could assess “risks” and “threats”. And while they had spent over $1B in the 90’s on traditional infrastructure technologies for integration, workflow, etc, they found, at the end of the day, that these solutions focused on the technical issues (the plumbing) but didn’t help users see links and relationships between pieces of information so they could make the right decisions. They needed a platform for composing information into a complete picture—a Composite Application.