Exhibit_4d_TRAP_RTM.xls

XLS spreadsheet 79 KB Posted Mar 5, 2014

Attached to: TFITS Consolidated Systems Integrator (TCSI)
Solicitation number: M67854-14-R-4802
Issued by: United States Marine Corps

About this file

From the source

Exhibit 4d_Amend 0001

View the file

Other files

File	Type	Posted
RFP_M67854-17-R-7802_Amend_00001.docx	DOCX document	May 19, 2017
Exhibit_2c__TRAP_Software_Development_PWS_Amend_0001.docx	DOCX document	Mar 5, 2014
Exhibit_2b__TRAP_PDSS_PWS_Amend_0001.docx	DOCX document	Mar 5, 2014
Attachment_7_DD254__Amend_0001.pdf	PDF	Mar 5, 2014
M67854-14-R-4802_Amend_01.doc	DOC document	Mar 5, 2014
Exhibit_8_The_SUPPLEMENT_TO_GUIDEBOOK_for_Acquisition_of_Naval_Intensive_Systems_Amend_0001.PDF	PDF	Mar 5, 2014
M67854-14-R-4802_conformed_Amend_01.doc	DOC document	Mar 5, 2014
Exhibit_2a__TRAP_Transition_PWS_Amend_0001.docx	DOCX document	Mar 5, 2014
Exhibit_9_The_Marine_Corps_Systems_Command_Technical_Review_Handbook_Amend_0001.pdf	PDF	Mar 5, 2014
Attachment_4a__Post_Award_Orientation_and_Planning_PWS_Amend_0001.docx	DOCX document	Mar 5, 2014
Exhibit_10__Industry_Questions_and_Answers_Amend_0001.xlsx	XLSX spreadsheet	Mar 5, 2014
Attachment_1_SI_Consolidation_PWS_Amend_0001.docx	DOCX document	Mar 5, 2014
Attachment_7_DD254_draft_M14-R-4802_Updated.pdf	PDF	Feb 20, 2014
Exhibit_7-_Past_Performance_Questionnaire.docx	DOCX document	Feb 11, 2014
Exhibit_4c_TRAP_SLA.docx	DOCX document	Feb 11, 2014
Exhibit_3d_TFITS_Requirements_Management_Plan.pdf	PDF	Feb 11, 2014
Exhibit_6-_Past_Performance_Statement.docx	DOCX document	Feb 11, 2014
Attachment_1_SI_Consolidation_PWS_Final_.docx	DOCX document	Feb 11, 2014
Exhibit_4a_TRAP_CITDB.xlsx	XLSX spreadsheet	Feb 11, 2014
Attachment_3_TFITS_SI_Overarching_Quality_Assurance_Surveillance_Plan_(QASP)x.docx	DOCX document	Feb 11, 2014
M67854-14-R-4802_RFP.pdf	PDF	Feb 11, 2014
Exhibit3f_TFITS_STES.pdf	PDF	Feb 11, 2014
Exhibit4b_TRAP_Contingency_Plan.docx	DOCX document	Feb 11, 2014
Exhibit_2c__TRAP_Software_Development_PWS_Final_.docx	DOCX document	Feb 11, 2014
Attachment_4a_Enclosure_1_DD_2875_SAAR_MC_MCCDC_MCBQ.pdf	PDF	Feb 11, 2014
Exhibit_3c_TFITS_Performance_Measurement_Plan.pdf	PDF	Feb 11, 2014
Exhibit_3e_TFITS_Risk_Management_Plan.pdf	PDF	Feb 11, 2014
Exhibit_3a_TFITS_SEP.pdf	PDF	Feb 11, 2014
Exhibit_3b_TFITS_CMP.pdf	PDF	Feb 11, 2014
Attachment_4a_Enclosre_2_LName_FName_Combined_SAAR_9_Sept_2013.pdf	PDF	Feb 11, 2014
Exhibit_2b__TRAP_PDSS_PWS_Final_.docx	DOCX document	Feb 11, 2014
Exhibit_2a__TRAP_Transition_PWS_Final_.docx	DOCX document	Feb 11, 2014
Exhibit_5_Planned_Systems_to_Consolidate.pdf	PDF	Feb 11, 2014
Exhibit_1_Navy_Small_Business_Subcontracting_Plan_Goals.pdf	PDF	Feb 11, 2014
Attachment_4a__Post_Award_Orientation_and_Planning_PWS_Final.docx	DOCX document	Feb 11, 2014
Attachment__7_DD254_draft.pdf	PDF	Feb 11, 2014

Show all 36

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Field Definitions

Field	Field Definition
Requirement ID	Unique Identification
Source Requirment	Text taken from original source document.
Single Leaf Requirement	Single statement that meets requirement rules: unique, testable, measurable, actionable, design-independent
Requirement Type	Functional or Non-functional Requirement
Owner	Owner of the requirement.
Source Requirement	Original source (document, person, etc) of the requirement
CDD Section	Section in the TRAP CDD version 1.0 where the requirement resides
Priority	Requirement Priority (if applicable)
Status	Current status of requirement (TBD)
Derived From Requirement Number	Source Requirement Number - used when a new requirement is created from another requirement
System (Sys)

Service (Svc)

Process (Proc)	Identifies the capability the requirement provides - i.e. - will the requriement create a process or a physical solution
	Server / Workstation	Magnitude of the capability requried - does the requirement reference a server solution, or a single workstation
	Capability Objective	Documents the specific functionality as listed in the "Capability Objectives List" Tab that this requirement is addressing
	Change in Requirement	Used to document changes in the requirement
	Rationale for Change	Used to document the reason for changing the requirement
	Project Objective (KPP)	Program Capability or Key Performance Parameter (KPP) the requirement is addressing - Attributes or performance characteristics considered most essential for an efective military capability
	KSA	Key System Attribute - An attribute or characteristic considered crucial in support of achieving a balanced solution/approach to a key performance parameter (KPP) or some other key performance attribute deemed necessary by the sponsor.
	Threshold	The requirement for the minimum performance allowed by the Government to pass to production
	Objective	The requirement for the preferred performance allowed by the Government to pass to production
	TRAP Applicable	Details if this requirement is applicable to the TRAP POR
	User Groups	Names who will be the ultimate end-user of the feature
	SDS Section	The section of the System Design Specification that the SDS Statement where the requirement resides
	System Design Specification Statement	System Design requirements text
	A	Analysis - Method of testing via paper analysis
	E	Examination - Method of testing via observation
	D	Demonstration - Method of testing via a demonstration that proves requirements are met
	DT	Development Test - System developers reviewing and testing in development/test region that requirements are met
	Verification Results	Results of Development Testing
	OT	Operational Test - MCOTEA reviewing and testing in real-world environment that requirements are met
	Validation Results	Results of MCOTEA Testing

TRAP RTM

TRAP

Verification

Validation

Analysis (A)

Examination (E)

Demonstration (D)

Development Test (DT)

Verification Results

Operational Test (OT)

Validation Results

Met

Met with Exception (MWE)

Requirement ID

Requirements

System Specifciation (Threshold)

System Specfication (Objective)

Engineering Design

Authoritative Source

Requirement Type

Specified or Derived

Derivation Rationale

MOE / MOP

Use CASE

Verification Results

Validation Results

Comments

TRAP System Design

Application

The TRAP shall be accssble from the NIPRNET

T=O

Consolidated Brief TRAP

Functional

Specified TRAP Performance & Characteristics

N/A

Connectivity from NIPRNET

The TRAP shall be accessible from the SIPRNET

T=O

Consolidated Brief TRAP

Functional

Specified TRAP Performance & Characteristics

N/A

Connectivity from SIPRNET

The system shall be designed to support a minimum of 170 source lines of code (SLOC) per Funtion/Feature Point

The system shall be designed to support a minimum of 204 source lines of code (SLOC) per Funtion/Feature Point

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

The system shall be designed to support a minimum of 180 Function/Feature Points

The system shall be designed to support a minimum of 216 Function/Feature Points

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

The System Recovery Time Objective (RTO) is ≤24 hours

The System Recovery Time Objective (RTO) is <3 hours

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

Disaster Recovery Plan Test

The System Recovery Point Objective (RPO) is ≤1 hour

The System Recovery Point Objective (RPO) is <30 minutes

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

Disaster Recovery Plan Test

Database

The system database shall support a minimum of 5 tables

The system database shall support a minimum of 6 tables

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

The system database shall support a minimum of 22 fields per table

The system database shall support a minimum of 27 fields per table

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

The system database shall be capable of scaling to a minimum of 260GB in size

The system database shall be capable of scaling to a minimum of 312GB in size

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

Hardware

The hardware supporting the system shall be capable of supporting 400 concurrent TRAP Super Users and 3400 TRAP Basic Users without any system component exceeding 80% utilization

The hardware supporting the system shall be capable of supporting 500 concurrent TRAP Super Users and 4500 TRAP Basic Users without any system exceeding 80% utilization

Consolidated Brief TRAP

Functional

Derived

N/A

TRAP

TRAP Operations (Application)

Cyber Security

Accreditation

The TRAP shall be compliant with the Information Assurance requirements including availability, integrity, authentication, confidentiality, and non-repudiation, and issuance of an Interim Authorization to Operate (IATO) or Authorization To Operate (ATO) by the Designated Accrediting Authority (DAA).

T=O

Consolidated Brief TRAP

Non-Functional

Derived

Statuatory Requirement to C&A all IT equipment and applications that operate in support of the Government

DAA Authorization to Operate and Connect (ATO/C)

Review of the TRAP, and supporting Systems, ATO/C

IAVA Support

The TRAP shall maintain compliance with all DoD/USMC directed patching requirements (commonly referred to as IAVA's) that apply to the system, ≤30 days of the IAVA release.

The TRAP shall maintain compliance with all DoD/USMC directed patching requirements (commonly referred to as IAVA's) that apply to the system, ≥48 hours prior to the compliance deadline required per the IAVA release

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

Trouble Ticket Resolution

Oracle Critical Patch Update Support

The TRAP shall be patched quarterly with applicable Oracle Critical Patch Updates

T=O

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

Trouble Ticket Resolution

Vendor Patch Support

The TRAP shall be patched quarterly with all applicable vendor patches

T=O

TRAP Performance & Characteristics

Functional

Derived

System maintenance will ensure all IA requirements are met for annual review basis, and ensure appropriate functionality of the system.

Trouble Ticket Resolution

Development Support

A minimum of two (2) defects, if identifed, within TRAP Application Code shall be resolved monthly

A minimum of three (3) defects, if identifed, within TRAP Application Code shall be resolved monthly

TRAP Performance & Characteristics

Functional

Specified TRAP Performance & Characteristics

N/A

Trouble Ticket Resolution

TRAP Operations (Incident Management)

Service Desk Capabilities

E-mail Access

Access to .mil Email (Unclass)

T=O

Consolidated Brief TRAP

Functional

Derived

Service Desk will need access to E-mail services to support day to day business operations and communications.

Email domain is .mil

Web Access

Access to Web (Unclass)

T=O

Consolidated Brief TRAP

Functional

Derived

Service Desk will need to provide email services to support day to day business operations and communications.

Active HTTP connection via Web Browser

Telephone Access

All TRAP personnel will have Access to Voice Communications

T=O

Consolidated Brief TRAP

Functional

Derived

Vocie required for Service Desk ability to make/receive phone calls and service requests. Utilizing data infrastrucutre would reduce cost to build cabling infrastructure.

Dial Tone

Call Transfer

TRAP Service Desk will have ability to transfer voice calls to TRAP System Administrators

T=O

Consolidated Brief TRAP

Functional

Derived

Transfer of phone calls between TRAP support personnel is required to enable passing tickets as outlined within the Consolidated Brief TRAP

Time to transfer call

Voice Mailbox

All TRAP Service Desk phone numbers (desk and mobile) shall have a voicemail capability

T=O

Consolidated Brief TRAP

Functional

Derived

Transfer of phone calls to voicemail when not answered, or busy, is required to capture service requests as outlined within the Consolidated Brief TRAP

Calls are transferred to voicemail

Voice System Capacity

Telephone system will be able to handle all TRAP personnel using system continuously.

T=O

Consolidated Brief TRAP

Functional

Derived

Vocie required for TRAP support personnel ability to make/receive phone calls and service requests, after normal business hours

Active voice connections at all support personnel desks.

Afterhours Telephone Access

The TRAP Service Desk shall be reachable via telephone after normal operating hours

T=O

Dial Tone on designated mobile phone(s)

Desktop App Support

Microsoft Office Word

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Word Document

Microsoft Office Excel

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Excel Spreadsheet

Microsoft Office Powerpoint

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Powerpoint presentation

Microsoft Office Outlook

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Email Client

Microsoft Office Project

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Project File

Microsoft Internet Explorer

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Web Site Access

Mozilla Firefox

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Web Site Access

Microsoft Windows Operating System (OS) Support

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Microsoft OS

Printer/Scanner support

T=O

Consolidated Brief TRAP

Functional

Derived

Required for Tier 1 support to TRAP users.

Printed paper

Metrics to Capture

Number of Calls

Total # of calls per day, week, month

T=O

Consolidated Brief TRAP

Functional

Derived

Metrics will enable service improvement of TRAP Service Desk.

Number of Calls

Review of Trouble Ticket Metrics

Number of Incidents

Incidents by Severity Level

T=O

Consolidated Brief TRAP

Functional

Derived

Metrics will enable service improvement of TRAP Service Desk.

Number of Incidents

Review of Trouble Ticket Metrics

Age of Tickets

Currently average ticket age in hours:minutes and current number of ticketsopen and close

T=O

Consolidated Brief TRAP

Functional

Derived

Metrics will enable service improvement of TRAP Service Desk.

Age of Tickets

Review of Trouble Ticket Metrics

Average Time to Close

Average time to close tickets

T=O

Consolidated Brief TRAP

Functional

Derived

Metrics will enable service improvement of TRAP Service Desk.

Average Time to Close

Review of Trouble Ticket Metrics

TRAP Service Desk Key System Attributes (KSAs)

Sevice Desk Call Resolution Rate (First Call)

≥0.85 for calls received during core business hours with an overal resolution rate of ≥0.85

≥0.93.75 for calls received during core business hours with an overal resolution rate of ≥0.80

TRAP Performance & Characteristics

Non-Functional

Derived

N/A

Resolution Rate

Review of Trouble Ticket Metrics

Average Call Duration

≤8 min

<4 min

TRAP Performance & Characteristics

Non-Functional

Specified TRAP Performance & Characteristics

N/A

Call Duration

Review of Trouble Ticket Metrics

Call Agent Utilization.

≥0.95

>0.99

TRAP Performance & Characteristics

Non-Functional

Derived

N/A

Agent Utilization

Review of Trouble Ticket Metrics

Call Abandon Rate.

≤0.02

<0.01

TRAP Performance & Characteristics

Non-Functional

Specified TRAP Performance & Characteristics

N/A

Abandon Rate

Review of Trouble Ticket Metrics

Incident Management Operations / Ticketing

Ticket Assignment

Ability to assign tickets using ticketing tool

T=O

TRAP Performance & Characteristics

Non-Functional

Derived

Trouble Ticket

Review of Help Desk Standard Operating Procedures, Daily Operations, and Trouble Ticket Log

Ticket Opening

TRAP support personnel and users can open their own tickets

T=O

TRAP Performance & Characteristics

Non-Functional

Derived

Trouble Ticket

Review of Help Desk Standard Operating Procedures, Daily Operations, and Trouble Ticket Log

Ticket Visibility

All tickets are visible by the TRAP Service Desk

T=O

TRAP Performance & Characteristics

Non-Functional

Derived

Trouble Ticket

Review of Help Desk Standard Operating Procedures, Daily Operations, and Trouble Ticket Log

Ticket Input Methods

Inputs into the Incident Mgt process will include SIPRNET and NIPRNET Email

T=O

TRAP Performance & Characteristics

Non-Functional

Derived

Trouble Ticket

Review of Help Desk Standard Operating Procedures, Daily Operations, and Trouble Ticket Log

Inputs into the Incident Mgt process will include Voice Communications (Unclassified)

T=O

TRAP Performance & Characteristics

Non-Functional

Derived

Trouble Ticket

Review of Help Desk Standard Operating Procedures, Daily Operations, and Trouble Ticket Log

Training

ITIL Foundations

All support personnel will have:

ITIL Foundations

ITIL Practitioner for TRAP Service Desk Manager/Program Manager

Consolidated Brief TRAP

Functional

Derived

ITIL Certification

Review of support personnel training certifications

TRAP Training

All support personnel will be trained on the use of the TRAP

T=O

Consolidated Brief TRAP

Functional

Derived

TRAP Training Complete

Review of support personnel training certifications

Hours of Operation

Service Desk will be operational from 0700-1900 EST Monday through Friday, including Government Holidays

T=O

Consolidated Brief TRAP

Functional

Derived

Service Desk will be operational from 0700-1900 EST Monday through Friday, including Government Holidays

Help Desk is reachable via phone and E-mail between 0700-1900EST Monday through Friday.

sysadmin:

The first word in this block is to match the color (Met, MWE, Not Met, NYE) per MCOTEA's definitions for Met, MWE, Not Met, or NYE. After that, provide the details behind the color…basically provide the answer to why the color is what it is. These come directly from the MCOTEA test report. You can summarize the MCOTEA results here to describe the details. If the Por has not yet had a MCOTEA test event, these blocks will be blank.

Version Control

Version	Date	Name	Action
1.0	20-Oct-13	Godfrey Engineer	Initial RTM Draft Document Published

Authoritative Sources

Authoritative Documents	Version	Date
1. Consolidated Brief TRAP	1	10/15/13

Sheet1

File details come from the government source that posted it. Updated Nov 14, 2017.