Section 5.3

CITIS FUNCTIONALITY

CITIS Services and Functions

Printing Capabilities

The CITIS functionality can range from basic data interchange functions to extensive interactive capabilities. The program/project manager must specify which, if any, of the CITIS tailorable functions are desired in the SOW, CDRL and acquisition contract.

CITIS Services and Functions

Table 5-2 provides supplemental details on CITIS services and functions. Information provided includes potential problems, lessons learned, and other issues to consider when determining the CITIS requirements for the SOW, CDRL.

Table 5-2. CITIC Services and Functions - Supplemental Details
Service/Function	Considerations
CITIS Services:	Services Typically Required with CITIS
CITIS Managment Services
- Availiability & Accessibility	SOW requires advance notice of events affecting CITIS operation. SOW specifies hours of operation SOW can specify amount of notice required (hours, etc.) prior to each event
- Users Furnished Information (UFI)	SOW and NCoO should specify size, format, and content of UFI - advance notice of format and software tools used to create UFI is extremly important. SOW should specify which functions are required for UFI.
- Multi-user Access	SOW specifies the number of concurrent CITIS users. The greater the number of users, the slower will be the CITIS performance (speed). SOW can specify the acceptable level of degradation
- Electronic Mail	SOW can specify the number
- Data Dictionary	Intent of this requirement is to ensure that users can consistently and easilt locate data of intrest
- Interface Compatibility	May require extensive planning and can be difficult to satisfy because of the potentially large range of NATO/NATO nations users recieving systems. NATO/NATO nations may want to specify/select a limited number of receiving systems to reduce complexity of CITIS
- Communication Protocols	NATO/NATO nations are responsible for obtaining any waivers needed for use of a nonstandard protocol.
- Training Support	SOW specifies form(s) of training: documentation, contractor visits to CITIS user sites, number of training sessions , etc. Sow can specify frequency of CITIS training/documentation updates (e.g. after major system changes, every six months)
- Telephone Support	SOW specifies hours of telephone support (may be different from CITIS hours of operation) Telephone support most advantageous for large or varied groups of CITIS users.
- On-line Help
Data Configuration Managment	CITIS users will not be able to replace contractor or UFI data. SOW specifies user data access privilags (i.e., access to woking data - neither contractor nor NATO/NATO nations - is not granted unless specified in the SOW).
CITIS Security	Contractor should obtain written approval from cognizant security officer before including classified data in CITIS SOW can address protection of business sensitive or proprietary data by both contractory and the NATO/NATO nations
Access Controls
Contamination Control	Primary contamination control tyically provided by allowing only authorized users to access CITIS data SOW can require the contractor to scan all CITIS daat for virusse prior to incorporation or can specify intervals at which all CITIS databases are scanned
Data Item Index	SOW specifies any indexing elements
Data Exchange Standards	Include any COTS software formats when specifying data transfer methods
Core Functions :	Core functions automatically required with CITIS Core function tailoring should only be done after rigorous cost and effectiveness analyses
- Acknowledge	Can be provided via either E-Mail or CITIS capabilties Can be manually input, automatic confirmation by reiciving computer, etc.
- Approve or Disapprove	Can be provided via E-Mail or CITIS capabilities
- Comment	NATO/NATO nations may consider allowing use of E-Mail for this function
- Notice of Delivery	CAN be provided via E-Mail or CITIS capabilities
- Receive
- Search	SOW specifies any additional elements desired as search criteria (will be included in the data item index).
- Store	SOW should specify the lenght of time a data item will be stored/avaliable through CITIS Function allows users to request that short-term data be retained on CITIS past its normal lifetime
- View
Tailorable Functions	SOW specifies required tailorable functions.
- Applications	Can cause licensing problems NATO/NATO nations should identify and grant access to applications only to specific personnel (not everyone); number of personnel requireing access should be specified in SOW, if known
- Archive	SOW can spcify length of time between archival data request and avaliability of data on CITIS. SOW can specify whether data requester should be notified of data avaliability SOW can require creation of an archival data index. NATO/NATO nations should periodically review CITIS data to identify data to be archived (this should improve CITIS performance)
- Combine	Can cause data CM problems - SOW should specify disposition of combined data (how long to retain it, how to tag amd imdex it, how to notify CITIS administrators, etc.) CITIS must ensure that combination of data does not affect origional data files
- Download	SOW can specify maximum file size for data downloads to avoid telecommunications/network loading problems files larger than approx. 30 Mb are recommended for delivary via magnetic media. Max. download file size specification may be especially important if many CITIS user sites possess only limited CITIS access capability. If max. size is specified, SOW should specify how CITIS users can gain access to larger data files(e.g., on-line request for data on tape
- Edit	can cause data CM problems - requires same considerations as for the Combine function
- Forward	SOW should specify whether data will be forwarded to other CITIS users, non-CITIS users, or both Function is usefull for facilitating the review and approval/disapproval of data items
- Package	SOW must define this function - specifically: How should the package be stored? IS the package temporary or permanent? Is it accessible by all authorized CITIS user, and how can they be authorized? Must the other CITIS functions be able to act on the package?
- Query
- Sort
- User Groups	SOW should specify frequency and location of user group meetings SOW should specify disposition of information generated during the meetings SOW shouuld specify who is responsible for taking minutes and tracking action items User groups most beneficial with large numbers of varied CITIS users

Printing Capabilities

The ability of the CITIS to print file contents should be considered by the NATO/NATO nations and the contractor. Although the goal of CITIS and CALS in general is to migrate from paper-based information to digital formats, real-world practices indicate that paper is still a popular medium for information distribution. The program manager should determine whether CITIS users will be allowed to print portions of CITIS data without having to download the entire file to their computer. If this service is desired, the program manager needs to require the contractor to incorporate a printing capability into CITIS.

The NATO/NATO nations also needs to specify the desired print options such as printing out a specific range of pages or portion of a document in addition to printing the entire document. It is very important that the NATO/NATO nations include printing capability requirements in the contract so they can be appropriately priced, because the cost and effort to implement these capabilities may be significant. Printer compatibility issues cause problems for many information management programs because current technology can be fairly restrictive in terms of what types of files will print out correctly on various types of printers (e.g., non-Encapsulated PostScript files do not print well on PostScript printers).