JSF Digital Product Data
JSF Digital Product DataJim Hollenbach, Simulation Strategies, Inc.JSF Modeling Information Sources Action Team25 June 2002Ref: JSF02-0294, 7517DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
VISIONBE THE MODEL ACQUISITION PROGRAM FOR JOINTSERVICE AND INTERNATIONAL COOPERATIONDEVELOP AND PRODUCE AN AFFORDABLE NEXTGENERATION STRIKE FIGHTER WEAPON SYSTEMAND SUSTAIN IT WORLDWIDEDISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.
LOCKHEED MARTINMULTI-SERVICE DESIGNCTOLCVRoll NozzleLift Fan3-BearingSwivelDuctSTOVL3DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
SYSTEM DEVELOPMENT ANDDEMONSTRATION (SDD) SCHEDULECY0102FY0102030304040505060607070808First FlightFirst Engineto Test0909101011111212Initial Operational CapabilityConventionalTake Off/LandUSMCUSAFSDD StartUSNUKSTOVLCVBLOCK 1 Basic warfighter capability Flight qualified Interdiction, limited air-to-air JDAM/AIM-120Preliminary CriticalDesignDesignReviewReviewBlock 1 CapabilityDevelopment & Flight TestBLOCK 2 Interdiction, limited air-to-air Close air support &destruction of enemy airdefenses Additional bombs qualifiedBlock 2 CapabilityDevelopment & Flight TestBLOCK 3 Threshold compliant JSF w/ key weapons All JSF missions Additional missiles/bombs qualifiedBlock 3 CapabilityDevelopment & Flight TestLow Rate Initial Production Start4DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
GOVERNMENT & INDUSTRYPARTNERSHIP Lockheed Martin provides a Distributed Product Description (DPD)of the Joint Strike Fighter Includes all authoritative information needed to represent the JSF’soperational performance, logistical characteristics, and cost Spans the engineering, engagement, mission, and campaign levels Government provides the simulation environment in which theDPD-based JSF will operate Threat systems, friendly systems, logistics resources and infrastructure, Blue& Red C4I, multi-spectral databases, terrain & atmosphere representationsGovernment and Industry willform a closer M&S partnershipthan ever before!5DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Simulation Based Acquisition (SBA):Shared Info is the Hub of IPPD(JSF M&S Support Plan Fig. 5-3)Concept DevelopmentFunctional DesignJ O I N T S T R I K ESystemRequirementsJoint Strike FighterFIGHTERSection 1ScopeSystem ThreatAssessmentReportC4I Support PlanSection 2ApplicableDocumentsSection Section 4PerformanceSection 5VerificationPackagingJORDSection 6NotesJMSModels & SimulationsCost, Schedule &Program alEngineeringDemonstration /P r o d u c t i o n U&p g r a d eManufacturingValidation& D e v e l o p m eDnetp l o y m eandntReplacen t1000MGMT10010JSF DPD& othershared info(e.g., threats)Physical & InfoSystem DesignLogicalJan Apr Jul OctManufacturingLogicalWING/TAILFILLETSLIFT/ FANENGINEAIRFIELDTAILHOOKENGINEDistributed NetworksMission Planning,WargamingAVIONICSAUTONOMIC BATTLEFIELDJSF STRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Components of theJSF M&S Toolset(JSF M&S Support Plan Fig. 5-1)Strike WarfareCollaborative Environment(SWCE) ToolsetEngineering & ManufacturingCollaborative Environment(EMCE) Toolset7DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Consistent, AuthoritativeInformation Sources Are Vital To ensure M&S-derived answers are correct– Establish validity by tracing analyses back to authoritative information– Verify JSF meets requirements– Reduce the confusion and bad analysis that arise if operating on wrongor logically inconsistent information To conserve resources, improve efficiency– Avoid having to repeatedly find, produce and/or translate the sameinformation– Provide more timely analyses, resulting in shorter decision cycle timesand more efficient systems engineering– Avoid the costs of correcting mistakes discovered late in program8DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
JSF SBA Implementation TeamSBA Implementation CouncilMission SystemsM&S working groupAssociated work groupsV&V Action TeamQuality control/risk reductionM&S User Action TeamFunctional needs& processesAnalysisTrainingTestM&S Tools Action TeamSoftware applicationsModeling InformationSources Action TeamAuthoritative data9DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Modeling Information Sources Action TeamPrimary Deliverables Electronic access to all information needed forrepresentations in SWCE and EMCE tools Accompanying glossaries and metadata toconvey information lineage and guide its use Training and technical support10DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Paths to System Representations(refinement of JSF MSSP Figure 5-5)(Federate)executeSoftware representation within another’s tool (e.g., ESAMS)Develop asoftware componentCompileInput data setsLoadModel or simulationmodified to representa battlespaceSystem representation as a dedicated application (e.g., JSF Virtual Simulator)Develop a simulationapplicationInput data setsAuthoritative infoin its original formModel or simulationinitialized to representa minformationInput data setsLoadInformation inapplication-specificformCompileModel or simulationdeveloped to representa systemLoad(Federate)executeDIFsInformation mapping, translation, pre-processingData-driven system representation in another’s tool (e.g., Thunder, JIMM)ExecutableapplicationsDISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited11
Information Types Parametric data Algorithms Software code Publications Subject Matter Expert knowledgeInitial focus has been on parametric data12DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Data Characterization Regardless of its subject, data may be characterized by its:– Trustworthiness: “authoritative” or “non-authoritative”– Evidence in the real world: “empirical” or “derived”– Context dependency: “context-independent” or “context-dependent”– Granularity: “primitive” or “aggregated”– Structure: “atomic” or “complex”– Source (relative to the enterprise): “external” or “internal” Above characterizations are orthogonal– A data element could be described by any combination13DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
AggregatedSimplistic View of Data Inputs JSF data sources Threat data sources Friendly data sourcesCampaignlevelM&S toolsMission-levelM&S tools Natural environmentdata sourcesPrimitiveEngagement-levelM&S toolsEngineering-levelM&S tools14DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
dAggregatedCampaignMissionEngagementtat dadenpen ved-de deritext rnallyCon InteCoExt ntexern t-ially ndPrimor i epeitiventerna ndelly g ntene datrate aA More Complete PictureEngineeringNormally some preprocessing(e.g., smoothing, adjustment) asdata is moved between tools15DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
An Example Thread ADSIMGIANTJSF Virtual SimulatorASMMIL OSAICSHAZAMCOVARTENGINEERINGFASTGENMODTRANFLIR 92SPIRITSPGEN 4CATIAACQUIRENASTRANACADRationalRose16DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Implications Much “authoritative data” will be internally generated– and hence most subject to outside skepticism LM and JSFPO must have a shared understanding ofthe analysis process and what organizations/tools willbe regarded as the authoritative source– requiring revisions to normal procedures17DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Information Flow(Logical Depiction)E-mail alerts, downloadsvia web(browsers,e-mail, FTP) orother meansBrowsing, download requestsUsersModels & Simulations(authoring & analysis)MNSORDConceptEngineeringP H A S E E x p l o r aDtei mo no&n sMt raantui of naDPc/raetonupddrluUiocntpygi gmo rnea &nd etD e f i n i tValidationion& D e v e l oRp empelna tc en t100010 100JSF Authoritative Modeling Information Database (JAMID)Modeling InformationSource Repository(e.g., RAS)Operationalcontext(scenarios,doctrine, TJan Apr Jul OctOther militarysystems(threat, friendly)ASDBInteractions(Pd , Pk,etc.)JSFColor key:JSFPO providedLM providedDPDExternal (to JSF) Source Documents and Databases(from intel agencies, other program offices, NIMA, etc.)18DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Operational Context DB Scope(Enterprise-wide standards for analysis; in priority order) Scenarios––––– Mission GroupsMissionsVignettes (created by JSFPO)Use Cases (created by JSF IPTs)– Initiating inputs, required actions, MOPsNatural environment conditions– Road to warBlue TPFDOrders of battle (UOB, EOB, etc.)Geographic areaInfrastructure targets, locationTime of day, weatherConcept of Operations (CONOPS)Force doctrineTacticsRules of engagement (ROE)Firing doctrineInfrastructure lay down (other than targets)Not in Operational Context DB:– Study-specific archives Input data sets Raw execution outputs Discretionary analystdecisions– e.g., Blue mission routes– System C&P data Context independent Context dependent (e.g., Pk)– Natural environment instancedata (MSEDB)– Infrastructure C&P (MSEDB)19DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Modeling Information Life CycleJSF changesholding tankJAMID v N 1(developmental)ConceptEngineeringP H ADS eEfxi npValidationil toDiroeanmt i o&Mnn s&at nenn t&n tReplace101000100MGMTJan Apr Jul OctJSFInteractions(Pd , Pk,etc.)ProgramOfficesIntelCentersNIMA,DTRA,NRO, etc.JSFPO,JFCOM,DoD, etc.Blue system C&PinformationThreat C&PinformationNaturalenvironment &infrastructureC&P actionsmilitary(P , P ,etc.)systemsd l StudyspecificarchivesDISTRIBUTION STATEMENT A: Approved forPublic Release; distribution is unlimitedJSFcontrolboardsSmoothed / analyzed resultsDesignchangeMOMsRelevant information(data in tool-specific form)Analyst actionStudy-specificinput datasets& software codeJAMID Repository (RAS)MNSORDTranslation services (mapping, semantics/syntax)Update cycle AJAMIDVersion N Trigger: New JSF baselineJSF(baseline)(batch update of JSF &all other instance data)Authoring tools(e.g., architecture, CAD)Individual JSFdesign changesStructure & scopeupdates due to tool changesRaw M&S resultsAnalysis tools(e.g., models, simulations)MNSORDP H ACS oEnx cpel opDrt eamt i oEnnns&tgri anPteireUoornpdi /ung crgtaido ne &D e f i nValidationition &M a naDunedfvpaRecl elotopuyplrmami nceegenn tn t101000100MGMTJan Apr Jul OctUpdate Cycle BTrigger: SWCE/EMCEchange decisionsJAMID InformationModel changes
Information Modeling Challenges21DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
M&S Tool Data Engineering Process(DMSO’s Reverse Engineering for Data Integration and Sharing (REDIS) process, simplified)ReverseEngineeringModel 1data FilesModel 2data FilesModel 3data FilesModel 4data FilesModel 1Model 2Model 3Model 4Information Information Information InformationModelModelModelModel Model nData FilesModel eeringSubject Area Information ModelData InterchangeFormat specsData DictionaryIntegrated Databases22DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
DPD Architecture Is Represented in UMLas a Collection of Layered ModelsAir System Model(UML object model)XML DIFAir SystemViewsXML SchemaRASClientAir System Capability Modelfor simulation input andmodel derivation traceabilityinstanceDPD Meta Model(UML Class model)Data formattingdriven by XSLT rulesencodingGraph Model(UML Class model)XML SchemaRASServerencodingData Storage Model(UML Class model)RDB SchemaDatabaseServerDatabase programmingand connectors23DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
JAMID Development Strategy Integrated development– Consistent information models for DPD, ASDB, etc.– Consistent user interface, procedures, training, etc.– Common distribution infrastructure (RAS, LM VPN)– Coordinated CM, update procedures, metadata, etc. Spiral development– A series of builds, prioritized per program needs Information to support an increasing number ofrepresentations, in increasing numbers of tools,interfaced to an increasing number of organizations– Brawler datasets will be first cycle Various classification levels, as appropriate24DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Summary Breaking new ground to achieve major improvements Big change to how we do business Incremental delivery of capability, incremental changesfor users Requires careful planning and management The jury’s out on whether we’ll succeed- but we’re taking bets25DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Back-UpsDISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
MIS AT Members Action Team Leader: JSFPO MS&A military officer or government civilian[Maj Steve Bishop, USAF] JSFPO Team Technical Lead [Jim Hollenbach, Simulation Strategies] Lockheed Martin Team Technical Lead [Dr. Henson Graves, LM DPDArchitect] LM DPD/RAS Project Manager [Russ Campbell, LM] ASDB Project Manager [Steve Hix, Paradigm Technologies] JSF weapons information representative [Curtis Erickson, AAC/ENMI Orion Technologies] Natural/civil environment representative [Floyd Adagio, Orion Networking] JSF Threat Working Group representative [Tim Armstrong, Veridian] Operational context representative [Roman Marzak, Veridian Engineering] DMSO representative [Roy Scrudder, ARL UT] Other representatives as approved by the SBA Implementation Council27DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Shared Responsibilities During SDDThe Government will:The SDD contractor shall:Establish and maintain a Strike WarfareCollaborative Environment in which the DPD-basedJSF representations will operate, that spans thecollaboration focus areas of mission effectivenessanalysis, autonomic logistics analysis, engineeringand manufacturing analysis and cost analysisEstablish and manage an Engineering andManufacturing Collaborative EnvironmentProvide configuration-managed versions of a JSFSWCE Suite of Models and SimulationsDevelop, populate, and manage the JSF DPD, which,as a minimum, shall provide, via a DIF, all the JSFinformation needed to represent the JSF in the SWCEand the EMCE SoM&S.Develop, maintain, and manage the configuration ofa library of SWCE boxed sets. Develop translationsand Digital System Models (DSMs) not provided bythe WSC.Develop the software that may be necessary toconvert DPD information into the form needed toinitialize or configure an individual model orsimulation for that portion of the SWCE SoM&S thatthe WSC uses. This shall include translations andJSF Digital System Models.Provide an Authoritative Systems Database (ASDB)which is accessible through the JSF ResourceAccess SystemDevelop and maintain a web-based JSF ResourceAccess System(JSF M&S Support Plan Table 1-1)DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited28
HardDimensions ofInformation CoherencyTemporal coherence–The extent to which the data being used for different toolsand sites has the same time stampOrganizational coherence–The extent to which all JSF Enterprise organizations areusing the same set of databasesLayer (tier, level, stratum) coherenceVery Hard–The extent to which all the information at a given level ofgranularity (e.g., engagement level) is logically consistentGranularity coherence–The extent to which the information at different levels ofabstraction is logically consistent29DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Context Dependency “Context-independent” data– Entity attributes that remain stable regardless of its environment– Examples: structure, weight, radar signal, cost “Context-dependent” data– Conditional attributes (“it depends”)– Determined by: How the system is employed The characteristics of its natural environment Interactions with other systems– Examples: Speed, range, turn performance Radar, IR and visual signatures Engagement range, Ps, Pk, exchange ratio, targets killed30DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Current JSF Definitions(initial attempt at DPD implementation)DPDSystem rep coded in software in another’s tool (e.g., ESAMS)Develop asoftware componentDSMCompileInput data setsLoadModel or simulationmodified to representa battlespaceSystem rep in own dedicated application (e.g., SAF, simulators)Develop a simulationapplicationInput data setsAuthoritative infoin its original form(Federate)executeInput data setsModel or simulationinitialized to representa mationabout tionsCompileModel or simulationdeveloped to representa systemLoad(Federate)executeDIFsInformation mapping, translation, pre-processingSystem rep data driven in another’s tool (e.g., Thunder, JIMM)Executableapplications31DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
Interactions with other Action Teams Identify representations of interest (User AT) Identify SWCE & EMCE tool information types (Tools AT) Identify authoritative sources for derived information (User AT) Define data quality documentation to support VV&A (V&V AT) Define metadata templates (User AT) Capture security, network and user interface needs (User AT) Plan JAMID/RAS user training and support (User AT) Establish user feedback for JAMID QA (User AT, V&V AT) Define threat data fill/update process (Threat Working Group)Action Teams must work together32DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited
JSF control boards JSF changes holding tank Individual JSF design changes S s a Study-specific archives NIMA, DTRA, NRO, etc. Program Offices Intel Centers JSFPO, JFCOM, DoD, etc. Threat C&P information Operational context information Natural environment & infrastructure C&P information Blue s
JSF has nothing to do with JSP per se. JSF works with JSP through a JSP tag library bridge. However, the life cycle of JSF is very different from the life cycle of JSP. Facelets fits JSF much better than JSP because Facelets was designed with JSF in mind, whereas integrating JSF and JSP has
JSF includes a set of predefined UI components, an event-driven programming model, and the ability to add third-party components. JSF is designed to be extensible, easy to use, and toolable. This refcard describes the JSF development process, standard JSF tags, the JSF expressi
Building JavaServer Faces Applications 7 JSF – A Web Framework JSR 127 – JSF specification v1.1 JSF 1.2 in progress (JSR 252) JSP 2.1 (JSR 245) will align with JSF JSF spec lead was the Struts architect JavaServer Faces technology simplifies building user interfaces for JavaServer
NOTE: Both JSF and Struts developers implement web pages with JSP custom tags. But Struts tags generate HTML directly, whereas JSF tags rep-resent a component that is independent of the markup technology, and a renderer that generates HTML. That key difference makes it easy to adapt JSF
Nov 07, 2006 · Introducing Java Server Faces (JSF) to 4GL Developers Page 5 Before JSF It is difficult to see how far JSF has raised the bar for Java web application UIs without first being aware of the development experience (or lack of) that was the catalyst for the simpler UI component b
JSF One / Rich Web Experience Sep 2008 JSF Event Handling h:commandButton action “#{ReportCtrl.save}” Generates an event when pressed save() is a method on a managed bean JSF calls ReportController.save() Can also define action listeners associated with other components in the form Example: AccountSearc
What is JSF? Java Server Faces Java specification for building component-based user interfaces for web applications. It gives you the tools to communicate with java backing beans. JSF has all the javascript behind the scenes, creates the endpoints from JSF managed beans, and wires it all together. Agility. D
The Asset Management Strategy is aligned to other key policies including, but is not limited to: Allocations Policy, Procurement Strategy, Repairs and Maintenance Policy, Estate Management Policy, Adaptations Policy, and Rent and Service Charge Policy. The AMS is also aligned to the current relevant legislation and statutory requirements outlined within each Policy. In .
