Not to mention skynet would have been all over it. I cannot emphasize enough that we all need to read Tom Clancy books, yes all of them, it seems that boy knows alot more then the general populace and prints it off as fiction actually proves to be real. The events of today might as well be scripted by him.
Wel we might as well use the real terms instead of Skynet. And back then this would just be C4ISR. It is more than apparent that no one grasps the significance that I have posted actual diagram images of Ptech software that were from Ptech's website, showing that they used that software to do all of the battle command planning for Desert Storm in 1991 (which is very interesting because Ptech is plainly admitting that their own software existed BEFORE the company did, which is what I said in the Corbett interview. C4ISR is Command, Control, Communications, Computers, Intelligence, Surveillance, Reconnaissance.
The type of flight trajectory or combat operation/strategy/points of attack, etc that ANY aircraft whether Global Hawk or Tomahawk missile, is graphically represented in ptech's own diagrams. people do not understand this this software ENGINEERS WARFARE, IT FIGURES OUT HOW TO EXECUTE COMBAT OPERATIONS, TO EVERY MINUTE DETAIL, AND IT CAN CHANGE THEM IN REAL TIME, and where applicable, that DATA is FED to TROOPS and FORCES to act upon as they see fit, but it is the BRAINS behind everything today, it IS the basis for Future Combat Systems.
Reposted from here
The MIAA enables military information architects to create and maintain a structured, comprehensive, living "information back plane"--a set of integrated architecture models--that helps decision makers plan for and manage change in the information-related capabilities that are critical to the success of military operations and enterprises.
The MIAA creates and automatically enforces a consistent taxonomy (artifacts, interrelationships and rules) throughout all operational, system, and technical view products with domain-specific metamodels based on concepts and behavior rules adapted from the DoD C4ISR Architecture Framework, the CADM, and operational experience. The MIAA also incorporates the ability to organize architecture data according to Zachman, Boer and other architecture frameworks, and provides file-based interfaces to the Joint C4ISR Architecture Planning System (JCAPS) and powerful discrete event simulation capability (Design/CPN).
The Ptech Military Information Architecture Accelerator (MIAA) is based upon ideas and products outlined in the DoD C4ISR Architecture Framework, Version 2.1. That document is “intended to ensure that the architectures developed by the geographic and functional unified Commands, military Services, and defense Agencies are interrelatable between and among organizations’ operational, systems, and technical architecture views, and are comparable and integrateable across Joint and multi-national organizational boundaries.”
Ptech’s military architecture capability addresses these intentions, enabling military information architects to:
* construct fully integrated, interactive, C4ISR Architecture Framework-compliant models of the entire set of architectural data, and confirm the completeness and self-consistency of the data set
* conduct initial analyses of the data set or any subset thereof
* share both the model views and the analysis products among all stakeholders via web publishing and reporting
Our consultants can help you design and capture your architecture data within a single, concordant KnowledgeBase. This interactive, “living architecture” will enable you to represent and analyze data you have now, and will also form the basis for planning, assessing and managing future changes.”
The Ptech Military Information Architecture Accelerator rests upon a conceptual model which governs the behavior of the modeling environment. This conceptual model includes classes and associations arranged in a set of metamodels whose rules were adapted from C4ISR Architecture Framework, V. 2.1, CADM, and practical experience. Our object-oriented modeling environment allows you to capture and analyze data in a single concordant KnowledgeBase. All diagrams modeled in FrameWork are linked to each other through the metamodels that govern them and the objects they contain. In FrameWork, you can also attach subdiagrams to objects, providing as much “drill-down” capability as the architecture may require. Customized forms and reports augment the KnowledgeBase, offering text-based interfaces to the information. Taken together, these capabilities enable architects to slice and dice comprehensive, complex architecture data in a variety of ways.
Our Version 1.5 release supports modeling and reporting capabilities for:
Operational Products: OV-1, OV-2, OV-3, OV-4, OV-5, OV-6a, OV-6b, OV-6c,
System Products: SV-1, SV-2, SV-3, SV-4, SV-5, SV-6, SV-7, SV-8, SV-9, SV-10a, SV-10b, SV-10c
Technical Products: TV-1, TV-2
Other Products: AV-2
Upcoming Products include: OV-7 and SV-11
The current release represents a step along the path toward the final version, which will incorporate the essential and supporting DoD Architecture Framework products. Future releases will integrate these products, and maintain compatibility with prior versions.
Please contact us for the lastest versions
* AV-2 Report Templates
* Demonstrator KnowledgeBase
USAF SBIR 2000-116: Decision Support System for Command and Control Acquisition (Phase I)
* Created an interface between FrameWork and Design/CPN
* Enables users to take their architectures to a high-quality simulation and conduct sensitivity analyses to support executive decision makers
* Enables high-quality prediction of architecture performance and sensitivity analyses
JCAPS Interface development effort
* USSTRATCOM-funded effort to create two-way batch file interface between FrameWork and JCAPS repository
* Enables users to leverage unique capabilities of each system
Continuing Enterprise Architecture efforts in government & industry
* FEAF, TEAF, IRS AF, ITAA
* Will advance the theory and practical application of Information Architecture in general--should speed incorporation of specific additional capabilities
E-mail Our Support Staff
To report trouble or ask questions about the MIAA base extension, send a detailed email to:C4ISR_Support@ptechinc.com
Technical Architecture Products
CURRENTLY AVAILABLE TECHNICAL ARCHITECTURE PRODUCTS:
TV-1: Technical Architecture Profile Matrix
The TV-1 report enables analysis of the impact and timing of changing technologies on all systems. FrameWork gives you the ability to make internodal, intranodal and intrasystem perspectives.
TV-2: Standards Technology Forecast Matrix
The TV-2 report enables analysis of the impact and timing of changing standards on all systems. FrameWork gives you the ability to make internodal, intranodal and intrasystem perspectives.
Operational Architecture Products
CURRENTLY AVAILABLE OPERATIONAL ARCHITECTURE PRODUCTS:
OV-1: High-level Operational Concept Graphic
The OV-1 model diagram is intended to represent a general overview to the lines of communication in your architecture. In FrameWork, it is a fully integrated subset of the data that adds significant richness and value on its own, and functions as a gateway to the rest of your KnowledgeBase.
OV-2: Operational Node Connectivity Description
The OV-2 contains data on needlines and information exchanges between operational nodes. Through our forms interface, FrameWork allows you to enter one or more IERs per needline, as well as record specific characteristics for each IER. Our OV-2 model diagram also offers you the capability to organize operational nodes according to functional and process areas.
(Image not available)
OV-3: Operational Information Exchange Matrix
The OV-3 matrix reports on the IER specifications including media, quality, quantity, and direction, emphasizing the logical and operational characteristics. In FrameWork, the matrix is created through our code generation capability and output as a spreadsheet file.
OV-4: Command Relationships Chart
The OV-4 depicts relationships among organizations in your architecture. FrameWork supports Command, Coordination, and Internal Command relationship types, and also includes a feature designed to create user-defined relationships.
OV-5: IDEF-like Activity Model
The OV-5 describes activities and the exchange of information between those activities. In FrameWork, you can build activity hierarchies, and IDEF-like activity models, including ICOMs and external exchanges.
OV-6a: Operational Rules Model
The OV-6a captures business requirements and their relationshsips with operational activities in the form of structural assertions, action assertions and derivation assertions. FrameWork also allows you to relate rules to Guidance Statements and Information Exchanges.
OV-6b: Operational State Transition Description
The OV-6b describes the sequencing of activities in your operational architecture according to external or internal events, and business rules.
OV-6c: Operational Event/Trace Description
The OV-6c may be used in conjuction with the OV-6b to highlight a critical sequence of events. The OV-6c also incorporates operational nodes that must take action based on certain events within a specified time frame.
Most of the images for the following are unavailable, 2 were however.System Architecture Products
CURRENTLY AVAILABLE SYSTEM ARCHITECTURE PRODUCTS:
SV-1: System Interface Description
The System Interface Description behaves as an intermediary between operational and system views, showing generalized representations of communication pathways and networks. FrameWork gives you the ability to make internodal, intranodal and intrasystem perspectives.
SV-2: System Communications Description
While the Interfaces on the SV-1 represent logical constructs, the Links depicted on the SV-2 represent actual physical pathways between Systems. System and Link specifications such as status, classification, and interoperability level, are entered through supporting forms.
SV-3: System2 Matrix
The SV-3 matrix reports on the system-to-system interface relationships created on the SV-1. FrameWork creates the matrix through our code generation capability, whose output may be accessed through any spreadsheet application. Our matrix organizes systems according to their applicable functional and process areas.
SV-4: System Funtionality Description
The SV-4 depicts the data flows between system functions. In FrameWork, you can drill-down into the data flows to relate them with data exchanges and specific data elements. You may also use the SV-4 to depict system functionality hierarchies.
SV-5: Operational Activity to System Funtion Traceability Matrix
The SV-5 reports on interrelated leaf-level operational activities and system functions. In FrameWork, you can automatically generate the SV-5 matrix as a spreadsheet report, once all the associations between activities and system functions exist in your architecture.
SV-6: System Data Exchange Requirements Matrix
The SV-6 report is similar to the concept of the OV-3. It is a detailed report about all system data exchange requirements and the actual data exchanges that satisfy them.
SV-7: System Performance Parameters Matrix
The SV-7 report is a detailed report that expresses the hardware and software elements that make up systems along with the parameters against which the system or element's performance will be measured, and to record details about the measurement.
SV-8: System Evolution Discription Description
The SV-8 describes plans for modernizing an enterprise over time, capturing the sytems involved, the migration timeline and pertinent milestones.
SV-9: System Technology Forecast Matrix
The SV-9 report is a detailed spreadsheet of the impact and timing of changing technologies on selected systems.
SV-10a: System Rules Model
The SV-10a captures contraints of system design or implementation as they are related to system functions. These system rules may be structural assertions, action assertions or derivation assertions.
SV-10b: Systems State Transition Description
The SV-10b is the systems counterpart to the OV-6b. It describes events and states at the system level, and shows the sequencing of system functions.
SV-10c: Systems Event/Trace Description
The SV-10c extends the SV-10b to allow the tracing of a critical sequence of events. On the systems side, the SV-10c reflects the system aspects of the events described in the operational event/trace description.