Table of
Contents
|
Table of Contents |
A mixture of Army soldiers, civilians, and contractors maintain the ASAS. The most important ASAS maintainer is the system operator. The ASAS operator preventive maintenance checks and services (PMCS) keep the system combat ready and ensure early detection of potential problems. Trained ASAS maintenance personnel, both military and contractor, support the operator when hardware or software components fails. Together, operators and maintenance personnel keep the ASAS operational and ready to support the unit's IEW mission.
| RESPONSIBILITIES |
Operators, unit maintenance personnel, and contractor logistics support (CLS) perform most maintenance for ASAS unique equipment. The exception are those line replaceable units (LRUs) and shop replaceable units (SRUs) having test program set (TPS) support. CLS provides maintenance on contractor-furnished equipment (CFE). Corps and division support commands base shop test facilities (BSTFs) perform maintenance on TPS supported items. Established Army logistics procedures and organizations support ASAS GFE. ASAS maintenance responsibilities can be broken down into the following areas.
ASAS operators perform PMCS and limited corrective maintenance of ASAS GFE and CFE. Operator PMCS consists primarily of running built-in tests (BITs), checking cable connections, and observing normal functions of equipment. The ASAS operator performs PMCS (visual inspection, test, cleaning, tightening, and minor adjustments); limited corrective maintenance (such as replacing filters); and calibration checks (using BIT diagnostics). Operators use system software alarms, notices, and operational diagnostic subsystems to fault-isolate equipment malfunctions. Operators may also reinstall the component after repairs by maintenance personnel.
Unit maintenance personnel use BITs to fault-isolate equipment malfunctions to the defective LRU. They remove the defective LRU and install spares to return the system to operational status. Authorized repairs are limited to items that are easily replaceable and do not require complex adjustment or system alignment after replacement such as knobs, exterior cable assemblies, and expendable antennas.
Contractor personnel perform troubleshooting and maintenance on all CFE LRUs and SRUs not supported by TPS. Army maintenance personnel are responsible for direct support level maintenance of ACE equipment (CCS, DPS, workstations, and SEE).
Repairs beyond field level maintenance (unit or contractor personnel at the Ml unit) capabilities for the equipment supported by TPS are evacuated to a designated Army maintenance activity at the sustainment level. Contractors will support single-source hardware at these facilities. Sustainment level maintenance support includes the rebuilding or overhaul of major assemblies and subassemblies. Maintenance personnel will sanitize and evacuate for repair or disposition any LRU or SRU that is not repairable at the field level in accordance with source maintenance recoverability (SMR) codes. These codes can be found on the unit authorized parts list.
HARDWARE MAINTENANCE |
ASAS maintenance has separate channels for hardware and software maintenance. To ease hardware maintenance planning at each level, all spare parts are categorized as LRU or SRU. LRUs are major items that maintenance personnel can easily replace onsite. Examples are keyboards, monitors, printers, cables, and removable hard drives. SRUs are items internal to an LRU and are sent to a shop for replacement or repair. Examples are printed circuit boards, internal power supplies, and internal wiring. ASAS hardware maintenance covers two categories of equipment: GFE and CFE.
GFE is standard Army equipment that is not ASAS specific. The operator does PMCS according to the applicable manuals which should already be familiar to equipment operators.
CFE is equipment that is ASAS specific. The operator still does PMCS. Unit and higher level maintenance requirements are handled as previously described in this chapter under Responsibilities.
SOFTWARE MAINTENANCE |
ASAS software maintenance is critical to effective unit operations. Under Army Maintenance Policies, software maintenance is considered a sustainment function within the responsibilities of unit maintenance. This sustainment function is performed for all ASAS equipment by the on-site FSSS personnel and the unit operators. The CECOM Software Engineering Directorate (SED), located at Fort Huachuca, AZ, is responsible for making ASAS software baseline changes which affect the operational capability of the system software. The CECOM SED maintains overall responsibility for managing, quality controlling, and configuration management (CM). CECOM SED also ensures that the multiple versions of software developed for the various subsystems of ASAS located worldwide meet the warfighters' critical mission requirements.
If during normal system operations the operator experiences a system failure. The operator will first attempt to eliminate any possibility of hardware problems. If system diagnostic procedures in the Operator Users Manual eliminate hardware as the related failure, the operator will attempt to focus the problem to a specific application of the software. If the failure can be corrected, the mission continues; if not, the operator will contact the on-site FSSS representative for assistance. Together they will attempt to recreate and verify the problem. If the problem cannot be corrected using standard system keystrokes, then a Software Problem Report (SPR) will be generated. This SPR is logged, then forwarded through the Regional Software Support Activity (RSSA), back to CECOM SED for action. If the unit decides that the software does not provide adequate functionality or capability, the unit must submit an SPR recommending what changes or enhancements should be made.
FIELD SOFTWARE SERVICES SUPPORT (FSSS) |
This section will discuss the FSSS concept implemented by CECOM SED. CECOM SED is responsible for providing Life Cycle Software Support (LCSS) for all IEW Mission Critical Defense Systems (MCDS) of which the ASAS program is a part. The concept for FSSS is implemented during the Post Deployment Software Support phase of the project's life. SED's mission is to provide dedicated on-site software support as well as to manage an RSSA for all ASAS equipment fielded. The primary role of FSSS is centralized around performing tasks which will sustain computer processing operations, both in garrison and field environments. The FSSS function is maintained until such time as Army personnel are routinely trained to perform those tasks which are executed by the FSSS representatives or until the system leaves the Army inventory.
FSSS is provided at two levels. The first level consists of dedicated on-site support at each ASAS fielded unit. For a specific period of time, two FSSS representatives are present to support the unit during the New Equipment Training Team (NETT) phase for equipment fielding until approximately 90 days following the departure of the NETT instruction. The primary purpose for the augmentation by FSSS personnel is to verify system operation during the initial fielding activities and to ensure operational effectiveness. At the end of the 90-day post-NETT period, the FSSS onsite support is reduced to one individual. The second level of support consists of augmentation from a regional base, the RSSA.
On-Site FSSS. SED has the mission to provide on-site contractor FSSS for each MI unit equipped with an ASAS. On-site FSSS personnel perform their functions using the supported unit's operational equipment. FSSS personnel serve as the liaison between the supported unit, the RSSA, and SED. A memorandum of agreement (MOA) between the unit and SED TFS provides a description of each organization's responsibilities in areas such as FSSS, security, logistical support, and administrative support. Agreements between the ASAS project manager, the US Army Training and Doctrine Command (TRADOC) system manager (TSM)-ASAS, and SED resulted in similar support being provided to the ASAS-Extended.
Regional FSSS. The RSSAs are at centrally located sites worldwide to augment and provide additional support to the FSSS site representative. Centralized support, as required, will provide--
The RSSA is staffed with FSSS representatives who have expert knowledge of each of the ASAS systems. The RSSA staff will also provide additional support for exercises and assist the on-site FSSS representative during vacation, sick leave, and emergency absences. Any exercise or contingency support will require as much prior notification and coordination with SED as possible.
RSSA facilities are located at the following five cities; Uijonjbu, Korea; Fort Huachuca, Arizona; Fort Hood, Texas; Fort Bragg, North Carolina; and Heidelberg, Germany. These sites focus their support on 20 field service sites. As additional units are fielded ASAS equipment, they will be assigned to an RSSA for the same regional support.
FSSS personnel will prepare and maintain backup media for system-specific databases and system executable disks. They will perform periodic file maintenance, to include purging, archiving, and restoring data. FSSS personnel will run various system and diagnostic routines to ensure proper system operations. If a system's media is determined to be corrupted or unusable, FSSS personnel follow established procedures to recover the media and correct the fault or will reinstall the baseline media having difficulty.
FSSS for the ASAS requires periodic (routine), emergency, and nonroutine tasks. Periodic tasks include file maintenance, table and database maintenance, periodic database backup and restoration, and system initialization. Emergency tasks involve operations to identify, isolate, and correct operating system failures or other perceived software faults. Nonroutine tasks may include reconfiguring hardware and software, in the event that nodes within the enclave are inoperable due to a power failure, disk failure, or other causes. Other tasks entail listing file and disk directories, executing operating system software diagnostics, and viewing file contents to assess system problems. FSSS personnel responsibilities are discussed below:
New Software Version Release and Upgrade Installation. For any release of software, whether initial, upgrade or corrective, the FSSS personnel will be primarily responsible to load the software and run verification and parameter checks prior to being loaded on any unit's operational equipment. The software will arrive at the unit as a package containing, as a minimum, the following:
User-Reported Problems Investigation. FSSS personnel will assist each unit in identifying and resolving operational software problems. FSSS personnel will verify faults identified by first ensuring the problem is not related to operator or hardware error. FSSS personnel will try to replicate the problem encountered by the operator to determine if a work-around is possible. If not, the FSSS field representative will contact the supporting RSSA and ask if the same problem has occurred with other unit locations. If so, the RSSA will instruct the FSSS field representative on how to fix the error. Only the RSSA is authorized to call other regional sites to inquire about the identified error, unless the problem is time critical to the unit mission. If the problem is new, and the RSSA is unable to find an immediate work-around, the unit, assisted by the FSSS field representative, will generate an SPR. Only the unit commander will determine how critical the problem is to the unit operational mission requirements. Based upon this decision, a level of priority will be given to the SPR and forwarded to the supporting RSSA. The RSSA will review the SPR for completeness and accuracy. The SPR will be logged in at the RSSA before being forwarded to SED, Fort Huachuca. (NOTE: No SPR will be forwarded through the system until the security classification of the SPR is determined. If the FSS or unit is not sure, the local SSO will make the call.) Once received by SED, Fort Huachuca, it will be placed within the SPR or CM process, from which a technical bulletin will be produced, if necessary.
Site-Specific Requirements. FSSS personnel will load site-specific databases such as TEXTA, electronic parameter listing (EPL), or MIIDS and IDB which are provided to the FSSS personnel by the unit. FSSS personnel will also assist each unit in developing, loading, and maintaining site-specific files, tables, and exercise data. FSSS personnel will also assist the unit operators when necessary in maintaining and preparing backup database copies in the event of database corruption or other catastrophic failures.
Exercise Support. FSSS personnel will support garrison and field activities on a scheduled, preapproved basis. During field exercises, assigned FSSS personnel will accompany the unit to the field, work a normal duty day, and return to private quarters; however, they will be expected to remain on-call during the remainder of the duty day in the event a problem occurs with the supported software. Supported commands will be furnished with telephone and beeper numbers for FSSS personnel to facilitate recall procedures. Each unit exercise is unique. FSSS support operations span the globe from Southeast Asia to Europe. Prior planning and coordination with the FSS representative is critical to ensuring that the RSSA and FSSS Operations Center (Fort Huachuca, AZ) can identify and commit the necessary personnel and create the support estimates required by the unit to plan resourcing. The FSSS Operations Plan maintained within the unit identifies specific unit and FSSS personnel responsibilities for exercise support.
Operator Training Assistance. FSSS personnel will assist the NETT, as necessary, during initial unit training. The FSSS personnel provide new software release training to unit personnel, addressing any functional or operational changes necessitated by software updates, software releases, or the issuance of a technical bulletin. FSSS personnel can be asked to assist with a unit's established sustainment training program. Commitment of the FSSS representative for this requirement will be based upon a time available basis and coordination with the RSSA for resource commitment.
Map Data Conversion. Map data requests are processed and currently requested for specific systems through specific agencies. For map data requests concerning the ASAS-ASW and the ASAS-RWS, requests must be sent to the Program Management Office-Integration Fusion (formerly PM ASAS). This office is located at HQDA, PM-intelligence Fusion, 1616 Anderson Road, McLean, VA 22102-1616. For requests for ASAS-SSW, requests must be sent directly to SED, Fort Huachuca. In the future, all map requests will be centralized, and new request procedures will be published. Once the new map data is received, the FSSS representative will load the data onto the respective ASAS system.
CM is a process for ensuring that development and changes to system software is managed, edited, enhanced, and delivered under close control. The control factor is required to facilitate universal development and to handle required changes. For this reason, system operators are given only limited access to the system software files affecting the operational use, while the FSSS representatives have access to a full range of system applications via a special code word. Within ASAS equipment, numerous standard VAX and UNIX management utilities and tool sets are not made available to the user but are to the FSSS representative. Improper access to the operating system or improper use of the tool sets can result in lost or destroyed files, modified or lost functionality, or complete system failure. Only trained personnel are permitted access into these operating environments. Such capability requires extensive knowledge of the hardware, the operating system architecture, and capabilities of the tool sets. For these reasons and security (DIA requirements), system integrity, and CM, unit operators are not granted privileges which permit access.
Application Software. New ASAS application software deliveries will be made to FSSS personnel at RSSA locations and, as appropriate, to ASAS systems at field locations. Each RSSA maintains a master copy of the baseline software under configuration control. RSSA personnel use the master copy to replace executable files which may become corrupted at unit sites and to attempt to replicate problem areas.
Data Files. Some default ASAS data files and tables are field-modifiable. The contents of those tables, files, and databases in the fielded system may not remain the same as those initially installed. The database files altered by the user will reflect actual unit requirements as the user makes adaptive changes based on daily operational activities. The FSSS personnel maintain the default configuration-controlled entities and field-modified entities, thus providing both system and site-specific configuration-protected files. The capability to provide either an initial release version or a site-adapted version of files and databases will be provided as a service for each unit.
Problems associated with ASAS operations, software functionality, or data and message processing are identified via an SPR. The SPR is the vehicle through which system anomalies and enhancements for SED maintained systems are implemented into the software baseline. The on-site FSSS personnel will be responsible for assisting military operators in reporting these problems and providing recommendations to resolve discrepancies. This process includes verifying the SPRs for accuracy and completeness, attempting to recreate the problem on the local system, and forwarding the SPR to SED's CM group at Fort Huachuca, AZ.
SPR Process. The process for all SPRs related to the ASAS program will follow the steps outlined within Figure 7-1. Unit personnel will generate an SPR by using the SPR Originator Form to report software problems, desired enhancements, or discrepancies between user documentation and the user operational software. Completed SPR forms are provided to the FSSS representative for verification and completeness. The FSSS representative will coordinate with the RSSA concerning the SPR and have it forwarded to SED Fort Huachuca, AZ.
The CM group at SED will assign a system specific CM SPR control number and log the SPR into the SPR tracking database. Software technical personnel review the SPR and submit an assessment for resolution to a Configuration Control Board (CCB) review. Periodic CCB meetings are conducted to review and prioritize each SPR. Emergency SPRs (those that have been identified by the unit commander as "seriously impacting mission accomplishment") are resolved first to ensure prompt action. SED chairs and is a voting member at the ASAS CCB, with voting members from the PMO IF, and a user representative (either the Intelligence Center [USAICS&FH] or the Intelligence and Security Command [INSCOM]).
When resolved, the SPR is integrated into the next scheduled software version release of the software system. If an immediate work-around for the SPR can be created, a technical bulletin is forwarded to the user unit for immediate implementation until a new software release is dropped. Timely and accurate feedback to users regarding the status of their SPRs, or other user problems, is of significant importance to SED. Each unit FSSS representative must be able to brief the unit commander or his designated representative on the SPR status for the unit. Software related information on technical bulletins, CCB meeting minutes, and user group meeting minutes are supplied to the unit (monthly) through the FSSS representative.
Technical Bulletin. Should an SPR identify a problem for which a temporary work-around can be implemented, a technical bulletin (TB) will be generated and issued. TBs may address training, documentation, and operational and functional issues. A technical bulletin will be developed, documented, and issued by the SED CM group, then forwarded to the FSSS Operations Center for distribution to each FSSS site for immediate loading.
FSSS personnel use the supported unit's ruggedized equipment to perform FSSS tasks. FSSS personnel perform routine, emergency, and nonroutine tasks using selected equipment or, if necessary, the unit's equipment in a nonoperational state. All equipment usage by FSSS personnel will be coordinated with the unit.
