RMP Simulation User Guide

Transcription

1 Richard Sorensen Kihomac DRDC CORA CR October 2011 Defence R&D Canada Centre for Operational Research and Analysis National Defence Défense nationale

2

3 Prepared By: Richard Sorensen Kihomac 5501 Backlick Road, Ste. 200 Springfield, VA Contractor's Document Number: Contract Project Manager: Marlene Perry, PWGSC Contract Number: W ES20/001/ZM CSA: Andrew Wind, Defence Scientist, The scientific or technical validity of this Contract Report is entirely the responsibility of the Contractor and the contents do not necessarily have the approval or endorsement of Defence R&D Canada. Defence R&D Canada CORA Contract Report DRDC CORA CR October 2011

4 Principal Author Original signed by Richard Sorensen Richard Sorensen MDA Approved by Original signed by Dr. R. E. Mitchell Dr. R. E. Mitchell Head Maritime and ISR OR Approved for release by Original signed by P. Comeau P. Comeau Chief Scientist Work completed under ARP 11hn, "Maritime Security Planning Tools and Analysis" The scientific or technical validity of this Contract Report is entirely the responsibility of the Contractor and the contents do not necessarily have the approval or endorsement of the Department of National Defence of Canada. Defence R&D Canada Centre for Operational Research and Analysis (CORA) Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2011 Sa Majesté la Reine (en droit du Canada), telle que représentée par le ministre de la Défense nationale, 2011

5 Abstract.. Through a contract, the higher level operational architecture surrounding the RMP was modeled in the CORE and CORESim software environment. The model extends from the input of data sources, through the processing steps, to the final products and their storage. This high level model provides a perspective which has never been documented in one place or been made available to all interested parties. The model provides a common framework for understanding and discussion. This document details a novel approach to run scenarios where the model inputs and/or decision points are varied using external configuration files. This approach eliminates the need to change the hard-coded values in the model for each scenario change and will be of interest to other CORESim modelers. Résumé... L architecture opérationnelle de haut niveau qui entoure le tableau de la situation maritime (TSM) a été modélisée, au moyen d un contrat, dans l environnement logiciel CORE et CORESim. Le modèle s étend de l entrée des sources de données aux produits finaux, en passant par le stockage et les étapes de traitement. Le modèle de haut niveau donne une perspective qui n a jamais été consignée en un seul endroit ou mise à la disposition des intéressés. Il fournit un cadre commun qui favorise la compréhension et la discussion. Le document décrit une méthode novatrice d exécution de scénarios qui permet de varier les entrées du modèle et les points de décision au moyen de fichiers de configuration externes. Cette méthode élimine le besoin de modifier les valeurs codées du modèle pour chaque changement de scénario et peut intéresser les autres modélisateurs qui utilisent CORESim. DRDC CORA CR i

6 This page intentionally left blank. ii DRDC CORA CR

7 Executive summary RMP Simulation : Richard Sorensen; DRDC CORA CR ; Defence R&D Canada CORA; October DRDC CORA provides support for the Recognized Maritime Picture (RMP) from its compilation, use, storage, and analysis. This support is possible through its relationships with IM groups that build and maintain the architecture, and the operations centres that manage and analyze the vessel tracks. Through a contract, the higher level operational architecture surrounding the RMP was modeled in the CORE and CORESim software environment. The model extends from the input of data sources, through the processing steps, to the final products and their storage. It identifies where various sources enter the architecture, how they are transferred between coasts, ships, & allies and from unclassified to classified networks. This report documents a novel approach to run scenarios where the model inputs and/or decision points are varied using external configuration files. This approach eliminates the need to change the hard-coded values in the model for each scenario change and will be of interest to other CORESim modelers. A separate complimentary document, the RMP Project Final Report 1, provides detail of the model s modules, their connections, and operational processes. That report includes views into the model including Operational Views 2, 3, and 5b. This high level model provides a perspective which has never been documented in one place or been made available to all interested parties. The model provides a common framework for understanding and discussion. A separate classified report will be published highlighting the architecture s strengths, deficiencies, and future plans that were determined as a result of developing the model. 1 Sorensen, R, RMP Project Final Report, Unclassified, DRDC CORA CR , July 2011 DRDC CORA CR iii

8 Sommaire... RMP Simulation : Richard Sorensen; DRDC CORA CR ; R & D pour la défense Canada CORA; Octobre RDDC CARO assure le soutien du tableau de la situation maritime (TSM), de la compilation à l analyse en passant par l utilisation et le stockage. Ce soutien s appuie sur ses relations avec les groupes de GI qui élaborent et maintiennent l architecture et avec les centres des opérations qui gèrent et analysent les pistes de vaisseaux. L architecture opérationnelle de haut niveau qui entoure le tableau de la situation maritime (TSM) a été modélisée, au moyen d un contrat, dans l environnement logiciel CORE et CORESim. Le modèle s étend de l entrée des sources de données aux produits finaux, en passant par le stockage et les étapes de traitement. Il décrit l entrée des diverses sources dans l architecture et le transfert des sources entre les côtes, les vaisseaux et les alliés et entre les réseaux classifiés et non classifiés. Le rapport décrit une méthode novatrice d exécution de scénarios qui permet de varier les entrées du modèle et les points de décision au moyen de fichiers de configuration externes. Cette méthode élimine le besoin de modifier les valeurs codées du modèle pour chaque changement de scénario et peut intéresser les autres modélisateurs qui utilisent CORESim. Un document complémentaire, le rapport définitif du projet du TMS 2, décrit les modules du modèle, leurs connexions et les processus opérationnels. Ce rapport comprend les vues du modèle, y compris les vues opérationnelles 2, 3 et 5b. Le modèle de haut niveau donne une perspective qui n a jamais été consignée en un seul endroit ou mise à la disposition des intéressés. Il fournit un cadre commun qui favorise la compréhension et la discussion. Un autre rapport classifié sera publié pour présenter les points forts, les faiblesses et les plans futurs qui émergent à la suite du développement du modèle. 2 Sorensen, R, RMP Project Final Report, non classifié, RDDC CARO CR , juillet 2011 iv DRDC CORA CR

9 Rev: 16 March 2011 Author(s) To be reached at: Rick Sorensen Phone: (801) ext Before using an uncontrolled copy of this document it is the responsibility of the reader to ensure that it is the current issue.

10 1 Document history Revision Version Date Authors Description Status Original 16 March 2011 Rick Sorensen Initial version Final 2 Acronyms and Terms List The Acronyms and Terms list contain common terminology or abbreviations used on the program and in conjunction with CORE. Acronym/Term CORE Definition Vitech Corporation systems engineering tool set Date: 3/16/2011, 10:07 PM Page 2 of 21

11 Table of Contents 1 Document history Acronyms and Terms List Purpose Scenario Development Excel entries Events DoTheExport macro Setup - Other Entries S1-Datapath.txt S2-DayTime.txt S3-SimDuration.txt Execution Results...18 Date: 3/16/2011, 10:07 PM Page 3 of 21

12 3 Purpose The RMP Simulation (aka the simulation ) is intended to provide users the capability to build scenarios centered on the simulated ingestion of source information from a wide variety of input sources and the subsequent processing of those items. The scenario inputs articulate: A set of input events, A starting day and time, and Duration of the simulation. Scenario execution provides three execution results. One file (R1.Results.Init.csv) is saved automatically to document the initialization results. The other two are transcripts that are saved in CSV format manually to allow post-processing in Excel. The first transcript is an initialization summary and event and clock times as the simulation executes. The second is a detailed analysis of simulation execution throughout the simulation. Date: 3/16/2011, 10:07 PM Page 4 of 21

13 Simulation Procedure Simulation execution consists of scenario development and subsequent model execution. Scenario development is the process of creating the set of input files required by the simulation. This is often done using an Excel workbook with individual worksheets dedicated to each of the input sources. Scenario development can also be accomplished by modifying a previous set of text input files. The potential for file format errors makes it far more prudent to generate new files from the Excel workbook. The simulation requires three text files, with specific names as follows: S1-Datapath.txt S2-DayTime.txt S3-SimDuration.txt The simulation also requires two event sets, one for each coast. East Coast event set: Master List.East.CSV E.Operator.Inputs.Low.CSV E.Other. .Sources.CSV E.PAL.CSV E.CP140.AIS.CSV E.Radar.Sat.2.CSV E.TC.NASP.CSV E.TELESTO.CSV E.AA1.CSV E.OSWEX.CSV E.CCG.Fleet.Show.CSV E.CCG.INNAV.CSV E.CCG.LRIT.CSV E.DOT.AIS.CSV E.AIS2GOLD.CSV E.Other.GCCS.GPNet.Sites.CSV E.CP140.CSV E.Formatted.Operational.Message.CSV E.US.GCCS.Sites.CSV E.MCCIS.CSV E.IBS.CSV E.Deployed.Naval.Units.CSV E.MPA.Bases.CSV E.MH.Bases.CSV Date: 3/16/2011, 10:07 PM Page 5 of 21

14 E.Operator.Inputs.High.CSV E.North.Bay.CSV E.Other.GCCS.CSNI.Sites.CSV West Coast event set: Master List.West.CSV W.Other. .Sources.CSV W.PAL.CSV W.CP140.AIS.CSV W.Trimble.Galaxy.CSV W.VTOS.CSV W.RADAR.SAT.2.CSV W.TC.NASP.CSV W.OSWEX.CSV W.Other.GCCS.GPNet.Sites.CSV W.AIS2GOLD.CSV W.CCG.INNAV.CSV W.CCG.LRIT.CSV W.DOT.AIS.CSV W.Operator.Inputs.Low.CSV W.CP140.CSV W.Formatted.Operational.Message.CSV W.Deployed.Naval.Units.CSV W.IBS.CSV W.MCCIS.CSV W.US.GCCS.Sites.CSV W.Operator.Inputs.High.CSV W.Other.GCCS.CSNI.Sites.CSV With the exception of S1-Datapath.txt, S2-DayTime.txt, and S3-SimDuration.txt, the files are usually developed in two Excel workbooks (East.Master.CSV_Save.xlsm and West.Master.CSV_Save.xlsm) and then generated directly from the Excel workbooks using the embedded macro DoTheExport. Date: 3/16/2011, 10:07 PM Page 6 of 21

15 4 Scenario Development Excel entries 4.1 Events Input events for simulation are normally created using two Excel workbooks, East.Master.CSV_Save.xlsm and West.Master.CSV_Save.xlsm. Each workbook contains separate tabs for each of the input sources, along with a list of the CSV files produced by the macro DoTheExport, which is also in the workbooks. The first sheet in each workbook is the listing of the files to be produced and appears as shown below. NOTE: The image here shows only a partial listing. When exported, this list is used during initialization to identify all of the associated input files to be used. It is important that the list of files on the tab Master List.East (or Master List.West ) be complete. The remaining tabs in each workbook are formatted as follows: The first row is the name of the source, and is also the internal dictionary name used by the simulation. This name must match the dictionary name used internally. The second (and all subsequent) row(s) are sets of three integers representing the time when an input event occurs for this source. The time is expressed in days, hours, and minutes, where the first entry (Column Date: 3/16/2011, 10:07 PM Page 7 of 21

16 A) is the number of days, the second entry (Column B) is the number of hours, and the third entry (Column C) is the number of minutes. In the example shown here, the set of input events is for the source E.OPERATOR.INPUTS.LOW, and consists of three entries. The first event is scheduled to occur at 0 days, 8 hours, and 1 minute. The second event occurs at 0 days, 8 hours, and 2 minutes, and the third event occurs at 0 days, 8 hours, and 3 minutes. In this example, simulation start time was initialized at 00:08:00, so the events above occur at 1 minute, 2 minutes, and 3 minutes, respectively, after the simulation starts. NOTE: Events scheduled to occur at 0 minutes after the simulation start are not processed. For typical scenario development, the user should enter the desired event time(s) in each tab of the workbooks, save the workbook, and then run the macro DoTheExport. 4.2 DoTheExport macro Once all of the worksheets have been filled in, the information can be copied and pasted into the appropriate files manually or the associated CSV files can be created using the DoTheExport macro. The macro is executed by first selecting the View tab at the top, between the Review and Add-Ins tabs. The result should appear as shown here: Date: 3/16/2011, 10:07 PM Page 8 of 21

17 Then, with the View tab selected, select Macros and a dialog box appears which looks like this: Date: 3/16/2011, 10:07 PM Page 9 of 21

18 Finally, highlight DoTheExport and select Run. A dialog box Export To Text File appears as shown here: Enter a, (comma, without the quotation marks) and click OK. Another dialog box appears, requesting the user to navigate to the folder where the output files are to be saved: Navigate to the desired location and click OK. The CSV files are created in the selected folder and the macro completes. Date: 3/16/2011, 10:07 PM Page 10 of 21

19 4.3 Setup - Other Entries A scenario includes three additional files, S1-Datapath.txt, S2-DayTime.txt, and S3-SimDuration.txt S1-Datapath.txt This file contains a single entry with the full path to the remainder of the initialization files, in the format as follows: C:\SMInputs\Initialization \ Below is a screenshot of an example: The file S1-Datapath.txt can be located wherever the user prefers, but the initialization files must be located at the path specified. These files are: All event initialization files: o 27 CSV files for East Coast o 23 CSV files for West Coast S2-DayTime.txt S3-SimDuration.txt Suggestion: keep S1-Datapath.txt and the remaining initialization files collocated so that all associated files for any given scenario are aggregated for further analysis and historical record keeping. Results files will be placed in the same folder as the initialization files S2-DayTime.txt This file contains two entries representing the starting day and clock time at initialization. The first entry is the day of the week and the second is the clock time (at initialization/simulation start) with the time in the format: hours:minutes. The example here initializes the simulation to start on Monday at 08:00. Date: 3/16/2011, 10:07 PM Page 11 of 21

20 4.3.3 S3-SimDuration.txt This is a single entry file with simulation duration time in the format: days:hours:minutes. This represents the clock time when the simulation should end. In the example shown below, the simulation is set to conclude at 08:05. When combined with the file S2-DayTime.txt shown above, this entry for S3-SimDuration.txt results in 5 minutes of simulated execution. Date: 3/16/2011, 10:07 PM Page 12 of 21

21 5 Execution This description assumes the user is knowledgeable in CORE and has the RMP model loaded. Start CORE Open the current project In the Project pane, select the class OperationalActivity In the Project pane, select the folder Integrated Architecture In the Elements pane, select RMP Integrated RMP Operational Architecture: Date: 3/16/2011, 10:07 PM Page 13 of 21

22 Under the Tools menu item, select Simulator o The Simulator Control Panel opens: NOTE: It is strongly recommended that the simulator output be turned off for long durations of execution. Do this by selecting [on the Simulator Control Panel] View, Show Timeline Elements, and in the resulting Timeline Elements dialog box, click on Uncheck All in the Functions pane. NOTE: If the simulation transcript (lower pane above) does not appear, turn it on by selecting View and Show Transcript. Date: 3/16/2011, 10:07 PM Page 14 of 21

23 On the Simulator Control Panel, select Control, Run o o Execution begins and the Open Data Path dialog box appears. Navigate to the appropriate folder, select the file S1-Datapath.txt, and click the Open button: o A CORESim Script Transcript window opens and initialization results are displayed, followed by execution processing of the scenario: Date: 3/16/2011, 10:07 PM Page 15 of 21

24 o o Depending on the length of the scenario SimDuration [simulated execution time] and the numbers of events to be processed, the simulation runs for seconds to many minutes. The simulation runs until current sim time equals SimDuration and it completes with the message: o o o Click OK Suggestion: Save the COREsim Script Transcript as a text file at this point so that all events are easy to correlate later. It provides a good summary of event times that can be used to process the more detailed and complex Simulator Transcript. Save the Simulator Transcript: Date: 3/16/2011, 10:07 PM Page 16 of 21

25 o On the Simulator control panel, select File, Save Transcript As, and in the resulting dialog box navigate to the desired location, edit the file name as desired, and select Save. At this point the scenario simulation is completed and the Simulator Control Panel can be closed or another scenario executed. Date: 3/16/2011, 10:07 PM Page 17 of 21

26 6 Results One results file is created (automatically) in CSV format and would normally be opened in Excel. R1.Results.Init.csv echoes the initialization data in the transcript. This information is used for confirmation and troubleshooting if unexpected results are found. R1.Results.Init.csv example: Date: 3/16/2011, 10:07 PM Page 18 of 21

27 CORESim Script Transcript is formatted identically to R1.Results.Init.csv except that it also contains evidence of the timestamps and events from execution. CORESim Script Transcript example: CORESim Simulator Transcript is formatted in comma separated variable (CSV) format which opens in Excel. It contains 9 columns of information as follows: Time: This is internal simulator time, not the simulator clock value setup during initialization and used by the simulation to insert events and end the simulation. Event ID: This is an internal identification value used by the simulator. Process ID: This is an internal identification from the simulator to reference the model structure. Event Name: This is an internal simulator value representing the state of an event. Construct ID: This is a numerical representation of the hierarchical model structure. Structure: CORE s naming of the model network structure. Number: This is the number value from the OperationalActivity elements, used to reference the activity. Name: The name of the OperationalActivity element. Date: 3/16/2011, 10:07 PM Page 19 of 21

28 Event Execution Data: This column is blank. CORESim Simulator Transcript example: Date: 3/16/2011, 10:07 PM Page 20 of 21

29 Points of Contact For questions or comments regarding this document and assistance is resolving issues, please one of the following: 1. Andrew Wind 2. Rick Sorensen Date: 3/16/2011, 10:07 PM Page 21 of 21

30

31 DOCUMENT CONTROL DATA (Security classification of title, body of abstract and indexing annotation must be entered when the overall document is classified) 1. ORIGINATOR (The name and address of the organization preparing the document. Organizations for whom the document was prepared, e.g. Centre sponsoring a contractor's report, or tasking agency, are entered in section 8.) 2. SECURITY CLASSIFICATION (Overall security classification of the document including special warning terms if applicable.) Kihomac 5501 Backlick Road, Ste. 200 Springfield, VA UNCLASSIFIED (NON-CONTROLLED GOODS) DMC A REVIEW: GCEC December TITLE (The complete document title as indicated on the title page. Its classification should be indicated by the appropriate abbreviation (S, C or U) in parentheses after the title.) RMP Simulation : 4. AUTHORS (last name, followed by initials ranks, titles, etc. not to be used) Richard Sorensen 5. DATE OF PUBLICATION (Month and year of publication of document.) October a. NO. OF PAGES (Total containing information, including Annexes, Appendices, etc.) 34 6b. NO. OF REFS (Total cited in document.) 1 7. DESCRIPTIVE NOTES (The category of the document, e.g. technical report, technical note or memorandum. If appropriate, enter the type of report, e.g. interim, progress, summary, annual or final. Give the inclusive dates when a specific reporting period is covered.) Contract Report 8. SPONSORING ACTIVITY (The name of the department project office or laboratory sponsoring the research and development include address.) Defence R&D Canada CORA 101 Colonel By Drive Ottawa, Ontario K1A 0K2 9a. PROJECT OR GRANT NO. (If appropriate, the applicable research and development project or grant number under which the document was written. Please specify whether project or grant.) ARP 11hn01 10a. ORIGINATOR'S DOCUMENT NUMBER (The official document number by which the document is identified by the originating activity. This number must be unique to this document.) 9b. CONTRACT NO. (If appropriate, the applicable number under which the document was written.) W ES20/001/ZM 10b. OTHER DOCUMENT NO(s). (Any other numbers which may be assigned this document either by the originator or by the sponsor.) DRDC CORA CR DOCUMENT AVAILABILITY (Any limitations on further dissemination of the document, other than those imposed by security classification.) Unlimited 12. DOCUMENT ANNOUNCEMENT (Any limitation to the bibliographic announcement of this document. This will normally correspond to the Document Availability (11). However, where further distribution (beyond the audience specified in (11) is possible, a wider announcement audience may be selected.)) Unlimited

32 13. ABSTRACT (A brief and factual summary of the document. It may also appear elsewhere in the body of the document itself. It is highly desirable that the abstract of classified documents be unclassified. Each paragraph of the abstract shall begin with an indication of the security classification of the information in the paragraph (unless the document itself is unclassified) represented as (S), (C), (R), or (U). It is not necessary to include here abstracts in both official languages unless the text is bilingual.) Through a contract, the higher level operational architecture surrounding the RMP was modeled in the CORE and CORESim software environment. The model extends from the input of data sources, through the processing steps, to the final products and their storage. This high level model provides a perspective which has never been documented in one place or been made available to all interested parties. The model provides a common framework for understanding and discussion. This document details a novel approach to run scenarios where the model inputs and/or decision points are varied using external configuration files. This approach eliminates the need to change the hard-coded values in the model for each scenario change and will be of interest to other CORESim modelers. L architecture opérationnelle de haut niveau qui entoure le tableau de la situation maritime (TSM) a été modélisée, au moyen d un contrat, dans l environnement logiciel CORE et CORESim. Le modèle s étend de l entrée des sources de données aux produits finaux, en passant par le stockage et les étapes de traitement. Le modèle de haut niveau donne une perspective qui n a jamais été consignée en un seul endroit ou mise à la disposition des intéressés. Il fournit un cadre commun qui favorise la compréhension et la discussion. Le document décrit une méthode novatrice d exécution de scénarios qui permet de varier les entrées du modèle et les points de décision au moyen de fichiers de configuration externes. Cette méthode élimine le besoin de modifier les valeurs codées du modèle pour chaque changement de scénario et peut intéresser les autres modélisateurs qui utilisent CORESim. 14. KEYWORDS, DESCRIPTORS or IDENTIFIERS (Technically meaningful terms or short phrases that characterize a document and could be helpful in cataloguing the document. They should be selected so that no security classification is required. Identifiers, such as equipment model designation, trade name, military project code name, geographic location may also be included. If possible keywords should be selected from a published thesaurus, e.g. Thesaurus of Engineering and Scientific Terms (TEST) and that thesaurus identified. If it is not possible to select indexing terms which are Unclassified, the classification of each should be indicated as with the title.) Functional Analysis; Systems Architecture; Recognized Maritime Picture (RMP); Global Command and Control System (GCCS); Global Positioning Warehouse (GPW); Regional Joint Operations Centre (RJOC); ARP 11hn "Maritime Security Planning Tools and Analysis"

33

34 DRDC CORA