News Global Reconnaissance Information System



Document Number: GRIS-VDD

Revision: -

Date: 21 August 1996

VERSION DESCRIPTION DOCUMENT

FOR THE

GRIS CSCI v2.3

CONTRACT NO. N00039-95-C-0029

CDRL SEQUENCE NO. A023

Sponsor:

Ms. Anita Washington

Space and Naval Warfare Systems Command

2451 Crystal Drive, CPK5

Arlington VA 22245-5200

Prepared by:

PRC Inc.

1500 PRC Drive

McLean, VA 22102

TABLE OF CONTENTS

1 SCOPE 1-1

1.1 IDENTIFICATION 1-1

1.2 SYSTEM OVERVIEW 1-1

1.3 DOCUMENT OVERVIEW 1-1

2 REFERENCED DOCUMENTS 2-1

2.1 GOVERNMENT DOCUMENTS 2-1

2.2 NON-GOVERNMENT DOCUMENTS 2-1

3 VERSION DESCRIPTION 3-1

3.1 INVENTORY OF MATERIALS RELEASED 3-1

3.2 INVENTORY OF CSCI CONTENTS 3-1

3.3 CLASS I CHANGES INSTALLED 3-3

3.4 CLASS II CHANGES INSTALLED 3-3

3.5 ADAPTATION DATA 3-3

3.6 INTERFACE CAPABILITY 3-3

3.7 BIBLIOGRAPHY OF REFERENCE DOCUMENTS 3-3

3.8 SUMMARY OF CHANGE 3-3

3.9 INSTALLATION INSTRUCTIONS 3-6

3.10 POSSIBLE PROBLEMS AND KNOWN ERRORS 3-7

4 NOTES 4-1

4.1 GLOSSARY 4-1

4.2 ACRONYMS 4-1

1 SCOPE

1.1 IDENTIFICATION

This Version Description Document (VDD) identifies and describes the submission of the Global Command and Control System (GCCS) Reconnaissance Information System (GRIS) Computer Software Configuration Item (CSCI) Version 2.3.

1.2 SYSTEM OVERVIEW

GRIS provides automated support in planning, scheduling reporting, and monitoring reconnaissance activities under the Sensitive Reconnaissance Operations (SRO) program. GRIS maintains a near real-time status of all SRO missions and provides immediate on-line retrieval of mission, track, and message data. To accomplish this, GRIS provides automatic real-time capture and processing of Reconnaissance Information Processing System (RIPS) format messages, and maintains a mission and track database containing schedule and resultant information. GRIS is used to generate and release the outgoing SRO messages to the Automated Digital Network (AUTODIN) and provides on-line query and report capabilities detailing message, mission status, and scheduling information. It is used to maintain current Track Dictionary data and to generate the master copy of each new dictionary or set of change pages.

1.3 DOCUMENT OVERVIEW

This document contains information on the changes in the GRIS CSCI v2.3 release. Section 1 provides a system identification and overview, and an overview of this document. Section 2 contains a list of documents referenced in this report. Section 3 defines the version of GRIS and identifies changes made since the previous release. Section 4 provides a glossary and list of acronyms.

2 REFERENCED DOCUMENTS

2.1 GOVERNMENT DOCUMENTS

a. Specifications

None

b. Standards

None

c. Other Publications

1. Data Item Description, Version Description Document, DI-MCCR-80013A, Approval date 880229.

2.2 NON-GOVERNMENT DOCUMENTS

a. Specifications

None

b. Standards

None

c. Other Publications

(1) Global Command and Control System (GCCS) Reconnaissance Information System (GRIS) System/Segment Specification (SSS), CDRL A010, Rev.: Final, dated 28 April 1995.

(2) Operators Manual (OM) for the GRIS CSCI v2.2l, CDRL A033, Document Number: 250512, Rev.:-, Notice 1, dated 19 June 1995.

(3) Software Test Description for GRIS, CDRL A017, Document Number 250522, Rev.:-, dated 30 May 1995.

(4) System Administrator Manual (SAM) for GRIS, Rev.: -, Dated 21 August 1996.

3 VERSION DESCRIPTION

3.1 INVENTORY OF MATERIALS RELEASED

3.1.1 Physical Media

The GRIS CSCI v2.3 is delivered on 8mm tape. The tape was created on 20 August 1996 on a SUN Sparc 10 using the SUN Solaris 2.3 Operating System (OS). The tape was created using the tar relative '.' pathing method with the command "tar cvs GRIS". The software is unclassified. Only the runtime environment is delivered.

3.1.2 Associated Documentation

This VDD accompanies the GRIS v2.3 delivery. In addition, a System Administration Manual (SAM) is delivered as a replacement to the Installation Instructions dated 27 October, 1995.

3.1.3 Non-Delivered Documents

None

3.2 INVENTORY OF CSCI CONTENTS

Only the run-time files delivered with the GRIS 2.3 segment. The software is composed of Data files, and Executables and COE files.

Scripts

SegDescrip

data

help

progs

uid

./Scripts:

GRIS_info.csh

GRIS_warn.csh

amhs

check_oracle

elaboration_message

fixit

initialize

out_msg

patch_trans

pro_inc

rrprint

run_application

terminate

./SegDescrip:

Comm.deinstall

Community

DEINSTALL

Hardware

Menus

ModName

PostInstall

PreInstall

ReleaseNotes

ReqrdScripts

Requires

Security

SegType

VERSION

Validated

./data:

MASTER

Profiles

local

menus

pixmaps

prefs

./data/Profiles:

LaunchDesc.GRIS

LaunchList.GRIS

Profiles.GRIS

./data/local:

LOG_INIT

print

./data/local/print:

./data/menus:

Menu.GRIS

./data/pixmaps:

gris.img

./data/prefs:

BREAK

GRIS

MSN_MONITOR

STARTUP

STATUS

./help:

Addressee_Detail

Code_Detail

Code_Geographic_Area_Code_Index

Code_Icao_Code_Index

Code_Index

Code_Program_Code_Index

Code_Purpose_Code_Index

Code_Track_Code_Index

Databases

Error_Message

Finder_Query

General

Incoming_Message_Detail

Incoming_Message_Detail_1

Incoming_Message_Index

Incoming_Message_Query

Maintenance_Index

Maintenance_Query

Message_Lock_Detail

Message_Lock_Query

Messages

Misc

Mission_Cancellation_Query

Mission_Detail

Mission_Graph

Mission_History_Index

Mission_Index

Mission_Query

Mission_Recap_Query

Mission_Recap_Report

Mission_Report

Mission_Report.dml

Mission_Report.ovv

Monitor

Monitors

News

Nickname_Detail

Nickname_Index

Outgoing_Message_Detail

Outgoing_Message_Query

Password_Detail

Print

Status_Log_Index

System

Text_Detail

Track_Detail

Track_Dictionary_Index

Track_Dictionary_Query

Track_Dictionary_Report

Track_Event_Detail

Track_Event_Index

Track_Index

Track_Orbit_Detail

Track_Orbit_Index

Track_Query

Track_Report

Track_Track_Code_Index

./progs:

GRIS_amp

GRIS_break_driver

GRIS_driver

GRIS_load_data

GRIS_mission_monitor_driver

GRIS_navigate

GRIS_status_driver

GRIS_status_log_monitor_driver

mparter

run_amp

run_break

run_gris

run_load_data

run_mission_monitor

run_navigate

run_status

run_status_log_monitor

./uid:

break_uil.uid

gris_uil.uid

mission_monitor.uid

status_log_monitor.uid

status_uil.uid

3.3 CLASS I CHANGES INSTALLED

No Class I changes were installed in this release.

3.4 CLASS II CHANGES INSTALLED

GRIS v2.3 provides enhancements and fixes requested by GRIS end users.

3.5 ADAPTATION DATA

No changes were made to the site-unique data.

3.6 INTERFACE CAPABILITY

GRIS contains three external interface requirements (XIF-010 through XIF-030). The changes from 2.2.11 to 2.3 do not affect the GCCS AMHS for GRIS. As such, PRC believes that JITC re-testing of the GRIS CSCI is not required.

3.7 BIBLIOGRAPHY OF REFERENCE DOCUMENTS

GRIS v2.3 is delivered with this VDD. Three support documents, the Operators Manual, Software Test Description and a System Administrators Manual exist.

3.8 SUMMARY OF CHANGE

CHANGES TO GRIS V2.3 SINCE V2.2.11 include:

1. Added help on message error diagnostics to Incoming Message Detail. Help on

specific errors can be accessed by pressing the More button inside the

Incoming Message Detail help. Also, if you reprocess a message and a red

error message stating that the message contains errors pops up, you can get

the same specific information by pressing the Help button on the error

window (just like for outgoing messages).

2. Added Delete button to Mission Detail History to enable a mission to be

backtracked to a given state by simply deleting the item immediately

following the desired state.

3. Fixed Track Event and Orbit Index to renumber items after an item has been

deleted. Also, deleting a track event will renumber the items under Orbits

(because they refer to events). You will not see the renumbering unless

you leave the Track Event or Orbit Index and reenter.

4. Added a message sectionalizer to the back end of GRIS to sectionalize any

outgoing message over 400 lines long.

5. Made confirmation screens configurable. You can turn them off by setting

CONFIRMATION_ON in the config file to FALSE.

6. Made reprocessing on save configurable. If PROCESS_ON_SAVE in the config

file is set to TRUE, Incoming Message Detail will reprocess a message when

you hit the Save button. If it is FALSE, the Save button only saves the

edited message, and you have to press Process to reprocess it.

7. Made replacing vs. adding of revised, reprocessed, and retransmitted

messages configurable. If KEEP_LATEST_MESSAGE_ONLY in the config file is

set to TRUE, revising, reprocessing, or retransmitting a message will always

overwrite the old one. If it is FALSE, revising, reprocessing, or

retransmitting will overwrite only a revised message; if the original

message was anything else, a new message will be added.

8. The user config file (e.g. config.GCCS) is now checked before the project

config vile (viz. config), so default config values placed in the project

config file will be picked up if they are absent from the user config file

or if the user config file doesn't exist at all.

9. Added this screen.

10. Added a Mission Schedule Message.

11. Changed Fresh Milk terminology to Daily Schedule.

12. If there are no frequencies in the Frequency code table, the Consolidated

SRO message will not print them.

13. Replaced the Log from the Mission Query Menu with proper log format.

14. Made the following improvements to the Daily Mission Log:

a. not breaking on DEFAULT HOUR/MINUTE - fixed

b. actual times not getting reinitialized - fixed

c. multi-day report breaking on scheduled takeoff time only - fixed

d. STATUS moved to the second line

e. report made less than 80 columns wide, so it can be printed in portrait

mode.

15. Changed message while searching databases to 'Operation is x% complete'.

To get this message, you must have the MONITOR trigger turned on. Added

this message to database dumps, purges, and reorganizes also.

16. Made database more robust so you won't get a Write_Before_Read error on a

purge if you erroneously have duplicate records in the database.

17. Removed logic added in 2.2.9 which flagged RECON 3 messages for missions

with a different nickname from their tracks. This was incompatible with

mixed plate tracks.

18. Fixed a bug introduced into 2.2.9 in the Daily Mission Log: a non-null ACT

value would be echoed for all subsequent missions whose ACT value was null.

19. Fixed the Track Summary portion of the Monthly Mission Recap Report and the

Statistical Summary Message, so that tracks would appear only once per

program.

20. Changed AMP not to check ATD set against ATA (which has not been set yet),

because on a Relaunch it would be later than the former ATA, and so would be

flagged as an error.

21. Added break capability. Breaks are configurable by changing the 'breaks'

file located in the local directory.

22. Made it possible to configure the system so that query selections would be

persistent on return from query.

23. Reformatted Mission History (2 lines with item number).

24. Fixed a bug in remark storage: if a remark was greater than 67 characters,

only the characters after 67 were being stored in the Mission Database.

25. Added stand-alone RECON template generator. It depends on the recon table,

and validates each message token as entered. It is also connected to the

help file facility.

26. Added an error message for RECON 2 message events with event of TO or LN and

a lat-long location, or with event other than TO or LN and an ICAO location.

27. Fixed a bug in RECON 2 message processing: track time was not getting set.

28. Moved all files created at run time to the gris data directory.

29. Made outgoing messages sensitive to JJJ and HHMM in header (for Julian

dates and times).

30. Transmitting an outgoing message now goes through same code as retransmitted

incoming messages (viz. the headers and footers are updated).

31. !MSNDATA set changed to MANDATORY in recon table.

32. GRIS will raise Code_List_Too_Small when trying to construct a Consolidated

SRO Summary Message if there is only one frequency in the Frequency code

table, because the same frequency cannot be used twice in a row.

33. Changed Track Report to print all 0's for null area time. This situation

can only occur in data from the WWMCCS system, as GRIS will not allow null

area times to be entered either via AMP or interactively.

34. Migrated GRIS to Oracle.

35. Fixed outgoing messages to update Julian date and time.

37. Added messages to differentiate between a spawned job failure and a timeout

while waiting for the spawned job to finish.

38. Added version release number on the main window.

39. Dimmed Reorganize and Dump selections on the maintenance window.

40. Changed format of archive dumps to JSSC format.

41. Made 1MSNDATA set mandatory for all RECON 3 messages.

42. Changed mission result to override Deviation with Abort Complete/Incomplete.

But Deviation will still override As Scheduled.

43. Fixed vertical expansion of Mission History that was occurring after

deleting an item.

44. Made AMP warning messages to be displayed a configurable number of times,

so they will not go on forever.

45. Added a dump of the user config file to startup.

46. Added an AMP log, which contains a time stamp the message DTG and the

message state.

3.9 INSTALLATION INSTRUCTIONS

See the System Administrators Guide for. The following are reprinted from the ReleaseNotes:

1. Contact the GRIS user before installing the segment.

2. Determine where it makes sense to install GRIS.

3. Only install GRIS where it is NEEDED. DO NOT INSTALL GRIS ON EVERY CLIENT!

Typically, there will only be ONE user.

To fully install this release, the following must occur:

1. Install the GRIS segment.

2. If the defaults are not satisfactory, have the site GRIS user set initial

data values in the /h/GRIS/data/global/values/config file to appropriate values

for the database sizes, etc.

3. For those sites converting from a WWMCCS RIS, they need to furnish a

dump of their WWMCCS databases (track db and mission db) in the ascii WWMCCS

dump format.

4. Run PostInstall to move the databases to the global data area and

install the AMP cron job. The cron job can be found under

/h/data/global/gris/amp, called "amp_cron". It must be installed manually.

Determine who it makes sense to own this cron and install it as that user.

Use the command "crontab /h/data/global/gris/amp/amp_cron", PROVIDED

that the user does not have any other cronjobs. Check first with the

"crontab -l" command. If cronjobs exist, then edit the amp_cron into

the cron table manually.

5. Run GRIS_load_data_jcs or GRIS_load_data_pac ( depending on which site

GRIS is being installed at) on the WWMCCS database dumps mentioned in step 3.

You will need the AMHS_CLT client to be installed on the GRIS client.

6. GRIS is configured for the following userids: GCCS. If any

other userid is used, the file /h/GRIS/data/MASTER can be modified. Contact

the GRIS Maintenace POC.

3.10 POSSIBLE PROBLEMS AND KNOWN ERRORS

NONE

4 NOTES

4.1 GLOSSARY

4.2 ACRONYMS

ACOM U.S. Atlantic Command

AMHS Automated Message Handling System

AUTODIN Automated Digital Network

CDRL Contract Data Requirement List

CENTCOM U.S. Central Command

CM Configuration Management

CNO Chief of Naval Operations

COE Common Operating Environment

CSCI Computer Software Configuration Item

DISA Defense Information Systems Agency

EUCOM U.S. European Command

GCCS Global Command and Control System

GRIS GCCS Reconnaissance Information System

JMAS Joint Mission Application System

JRC Joint Reconnaissance Center

KPL Known Problems List

NCCS Navy Configuration Control System

OM Operators Manual

OS Operating System

PACOM U.S. Pacific Command

PARMIS PACOM Reconnaissance Information System

RIPS Reconnaissance Information Processing System

ROD Reconnaissance Operations Division

SOUTHCOM U.S. Southern Command

SPAWAR Space and Naval Warfare Systems Command

SPRs Software Problem Reports

SPS Software Product Specification

SRO Sensitive Reconnaissance Operations

SRS Software Requirement Specifications

VDD Version Description Document

WWMCCS Worldwide Military Command and Control System