EXHIBIT_C_-_Requirements_Document _Version_2.0_08.21.13.docx

REQUIREMENTS DOCUMENT

For

SECURITY FORCES QUALIFICATION AND CERTIFICATION MANAGEMENT TOOL

Version: 2.0

This page intentionally left blank.

SECURITY FORCES QUALIFICATION AND CERTIFICATION MANAGEMENT TOOL

Approval

Approval: ______________________________________

NAME AND DATE SANITIZED

Approval: ______________________________________

NAME AND DATE SANITIZED

Approval: ______________________________________

NAME AND DATE SANITIZED

Final Approval

Table of Contents: Page Number

1. Overview, Purpose, Scope, Assumptions and Constraints.

6. Figures

Change Record Page

1.0 Overview: This Requirements Document contains compliance, performance, and user requirements related to the Security Forces Qualification and Certification Management Tool for NW Security Forces (Navy and Marine) assigned to Strategic Weapons Facilities, Atlantic and Pacific (SWFLANT & SWFPAC). This effort supports manpower management for Marine Corps Security Force Battalions, Kings Bay and Bangor. The intent is to capitalize on existing software technologies to reduce the working load and man hours spent tracking, verifying security force qualifications and certifications, and watchbill generation.

1.1 Background: Marine Corps Security Force Battalions Kings Bay and Bangor assigned to Strategic Weapons Facilities, Atlantic and Pacific (SWFLANT & SWFPAC) have identified the need to eliminate or reduce recurring errors in the process of identifying and ensuring that qualified and Personnel Reliability Program (PRP) certified individuals stand post in accordance with references. The task of maintaining and managing accurate training, qualifications and certification data is complicated by having multiple entry processes and tools to track security personnel training and PRP information. As many as five separate information applications currently have to be maintained and tracked to verify security personnel qualifications.

The Security Forces need the ability to centralize, merge and automate these processes and tools, increase efficiencies by reducing replicated efforts, automate data merging, and provide single point auditing. In addition, centralized data management, entry and storage will reduce opportunity for human error and provide single source training reports and watch bill generation.

1.2 Purpose: The Security Forces Qualification and Certification Management Tool will provide Marine Corps Security Force Battalion (MCSFBn) leadership with a management tool to identify, track and assign individual security force member(s) qualifications for duties. Additionally, the software shall provide:

1.2.1. An application capable of generating an accurate security watchbill containing only qualified and Personnel Reliability Program (PRP) certified personnel. (KPP1)

1.2.2. An application that supports a web based configuration, accessible from remote sites. (KPP2)

1.2.3. An application capable of being hosted on or accessible from existing SSP hardware without the use of additional hardware or personnel. (KPP3)

1.2.4. An application that will provide senior leadership with an ability to conduct reviews of administrative, training and PRP status, monitor qualification timelines and objective qualifying evidence (OQE) of individual(s) qualifications and certifications. (KPP4)

1.2.5. An application that provides training department personnel with a single source for tracking, and verifying individual security force member training and qualification requirements. (KPP5)

1.1.6. An application that allows Watchbill Reviewing Officials (ROs) with a means to review and validate individual security force members for their assigned duties. (KPP6)

1.1.7 An application that will notify the chain of command via email when an individual’s PRP status changes. (KPP7)

1.3. Concept:

1.3.1 Concept definitions: The following definitions frame the operational concept of the Security Forces Qualification and Certification Management Tool as shown in example (figure 2).

1. Watchbill. The Watchbill is a schedule made to assign qualified personnel to a security watch (guard). See example (figure 1).

2. Operational Area (OA). The Operational Area is a section or designated area made up of posts, ECPs and other guard stations. An example of an Operational Area is an Armory. More than one Operational Area may be assigned to a watchbill.

3. Posts. Posts are areas of security assigned to an OA. Posts may be ECPs, Guard stations, guard towers, Sergeant of the Guard (SOG), Corporal of the Guard (COG), or Officer of the Day (OD). Multiple posts can be assigned to an OA. Post may be assigned to a watchbill independent of an OA. Post requirements will be a combination of PRP status, required JQRs and Other Training Requirements such as weapons qualifications.

4. Job Qualification Requirements (JQR). JQRs are a list of training requirements and On the Job Training (OJT) called Under Instruction Watches or UIs. A sentry has to accomplish these in order to stand that post. Individual JQR requirements will be signed by the supervisor and completed JQRs will be signed by unit Commanders. More than one JQR can be required per post. JQR can be assigned to multiple Posts.

5. Personnel Reliability Program (PRP). The PRP is a DoD program which requires training and evaluation to be conducted and certified by an official prior to an individual standing post. Personnel without current PRP status UP or green are not eligible to stand post.

6. Other Training requirements. Other training and certification will be required to stand post. These may include weapons, qualifications, drivers’ license, or other personnel training listed on the individual’s personal training page.

1.3.2 The Security Forces Qualification and Certification Management Tool will allow the creation of accurate watchbills (Figure 1) by mapping and tracking all training requirements, qualifications and certification and ensuring that individuals assigned to post are qualified to stand that post. Requirement and certification flow is outlined in the example provided in (Figure 2)

Figure 1

Figure 2

1.4. Assumptions and Constraints:

1.4.1. Assumptions:

The following assumptions were considered in developing requirements for the Security Forces Qualification and Certification Management Tool effort:

1. The Commanding Officer of the SWF and the Battalions are designated as PRP Reviewing Officials (RO).

2. The SWF and Battalion PRP officers are designated as the PRP Certifying Officials

3. The servers on which the application will be installed will be UNCLASSIFIED and reside on the government network.

4. All security forces assigned to a SWF/BN will be included in the application.

5. The application will be operated and maintained by SWF/BN security and training personnel.

1.4.2. Constraints:

The following constraints were considered in developing requirements for the Security Forces Qualification and Certification Management Tool effort:

1. There are limited numbers of user terminals in the battalion.

2. Replication of data that is managed in other sources is minimized to reduce work and potential errors.

1.5. Change Requests:

Any requests for changes to this document shall be submitted in writing to SP30. Change requests will be reviewed by all signatories and incorporated / rejected based on their recommendations.

2. Applicable Documents.

The following Specifications, standards, and handbooks form a part of this document to the extent specified in this requirements document.

2.1 References

Table 1

3. Requirements:

(T) Test – A verification method by which performance is measured through controlled application of a functional and/or environmental stimulus. The resulting quantitative measurements are evaluated to determine the degree of compliance.

(A) Analysis – A verification method that uses mathematical models, simulations, algorithms, or other scientific principles and procedures to provide evidence that stated requirements were met. It includes the assessment of accumulated data through reduction, interpolation, extrapolation, etc., or assessment of technical data of similar component units.

(D) Demonstration – A verification method generally used to observe the actual operation of items to provide evidence of functional and/or other expected outputs under specific scenarios.

(I) Inspection – A verification method used to determine conformance to specified requirements through examination of the item or associated documentation. Inspection is generally nondestructive and typically includes the use of visual, mechanical, and/or electrical measurements. The appropriate method to be used for each requirement is listed in the (QP) column in Table 2 using either T, A, D, or I. The verification of compliance of threshold requirements in this RD is a condition of acceptance by SP321 and 164. Verification of compliance with objectives is not required unless directed by SP321 and 164.

3.1 Key Performance Parameters (KPP)

KPP1

KPP2

KPP3

KPP4

KPP5

KPP6

KPP7

3.2 Application Access levels

3.3 General Application Requirements

3.4 Graphical User Interface (GUI)

5. User configuration page 6. JQR Definition 7. Approval/notification chain assignment 8. Watchbill generator 9. Watchbill viewer 10. Training/PRP summary 11. JQR Individual

3.5 Data

3.6 Personnel Reliability Program (PRP) Interface

3.7 Reports and Printing

3.8 Watchbill generation

3.9 Installation, Training and Support

3.10 Reliability

3.11 Maintainability

3.12 Expandability

3.13 Information Technology (IT) and Information Assurance (IA)

Table 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

4. Abbreviations and Acronyms:

5. Requirements Document Points of Contact:

Strategic Systems Programs:

NAME AND DATE SANITIZED

Marine Corps Security Force Regiment:

NAME AND DATE SANITIZED

Strategic Weapons Facility, Pacific Marine Corps Security Force Battalion, Pacific

NAME AND DATE SANITIZED

Marine Corps Security Forces Battalion, Atlantic image2.png image3.emf

Microsoft_Office_Excel_Worksheet1.xlsx Sheet1

Short Title Long Title

MIL-STD-498 Software Development and Documentation

SECNAVINST 5510.36A Department of the Navy (DON) Information Security Program (ISP) Instruction

SECNAV M5510.36 DON Information Security Program Manual

DODM S-5210.41-M Nuclear Weapons Security Manual

DODI 8552.01 Use of Mobile Code Technologies in DoD Information Systems

DODI 8500.2 Information Assurance (IA) Implementation

DODI 8551.1 Ports, Protocols, and Services Management (PPSM)

SECNAVINST S8126 Navy Nuclear Weapons Security

SSPINST 5239.12 SSP Information Assurance Program

SSPINST 5230.5 SSP IT Standard Products

Memorandum Designation of Department of the Navy (DON) Application and Database Management System (DADMS) as authoritative data source image4.emf image5.jpeg image1.jpeg