Attachment_3_-_M67854-16-R-4805_ECP_PWSv1.pdf

Marine Corps Systems Command Program Manager

Information Systems & Infrastructure

Total Force Information Technology Systems (TFITS)

Marine Corps Training Information Management Systems (MCTIMS)

Engineering Change Proposal (ECP) Performance Work Statement

AugustMay 2016

Version 1

Marine Corps Training Information Management Systems Performance Work Statement ii

Table of Contents 1 Introduction

Purpose and Scope .......................................................................................................... 4 1.1 Background ..................................................................................................................... 4 1.2 TFITS Management Plans .............................................................................................. 5 1.3 Reserved .......................................................................................................................... 5 1.4 Reserved .......................................................................................................................... 5 1.5 Contractor Performance .................................................................................................. 5 1.6 Objectives ....................................................................................................................... 5 1.7

2 Transition (Reserved) 3 PDSS (Reserved) 4 Software Development

Software Development Plan (SDP). ............................................................................... 6 4.1 SDP Annexes .................................................................................................................. 7 4.2

5 Project Management Project Management (Reserved) ..................................................................................... 9 5.1 Task Management ........................................................................................................... 9 5.2 Performance Management ............................................................................................ 10 5.3 Contract Closeout (Reserved) ....................................................................................... 11 5.4

6 Configuration Management Plan (Reserved) 7 Integrated Master Schedule 8 Performance Standards 9 Applicable Documents and References 10 Deliverables and Schedule 11 Government Furnished Information and Equipment 12 Security Requirements 13 Common Access Cards 14 Place of Performance 15 Period of Performance 16 Travel and Other Direct Costs (ODC) 17 Appendix A – Acronyms 18 Appendix B – Engineering Change Proposals iii

List of Figures Figure 1: MCTIMS Modules

List of Tables Table 1: Key Milestones Table 2: Performance Standards Table 3: Program Documentation Table 4: System Documentation Table 5: TFITS Management Plans Table 6: Other Guidance & Standards Table 7: Deliverables

1 Introduction Purpose and Scope 1.1

The Product Manager, Total Force Information Technology Systems Product Office (PdM TFITS) provides acquisition oversight for a portfolio of USMC systems and has a requirement for limited Software Development for the Marine Corps Training Information Management System (MCTIMS) program. MCTIMS falls under the TFITS Headquarters, Sustainment, and Training (HST) Tier. The vendor shall provide system maintenance and performance upgrade services and logistics support for MCTIMS as defined in this Task Order PWS.

The scope of this Task Order PWS covers the full range of system maintenance and performance upgrade services. Services include program management, engineering and analysis, software development, configuration management, quality assurance, risk management, help desk, system and database administration, Information Assurance (IA), testing and evaluation, and logistics support.

Background 1.2

The MCTIMS is an automated, Common-Access-Card (CAC) enabled, web-based system that consists of individual modules that support individual and unit training, training standards, training development, curriculum management, training delivery, training management, training tracking, and recording of training completions for schools within Training and Education Command (TECOM). MCTIMS’ integrated management system supports end users throughout the Marine Corps by recording training for individual Marines and units against training standards identified in the Training and Readiness Manuals, Military Occupation Specialty (MOS) Manual and Formal School Program of Instruction.

MARADMIN 085/17 dated 18 February 2016, directs the utilization and standardization of the MCTIMS Unit Training/Individual Marine Management module across the total force.

MCTIMS supports 57 formal learning centers and training detachments and interfaces with other IT systems within the Marine Corps and with other services across the Department of Defense (DoD) to provide capabilities for all formal school management functions.

Additionally, MCTIMS provides objective training data to inform readiness assessments for units and for individual Marines executing doctrinal Unit Training Management (UTM) processes throughout the total force. MCTIMS must interface with the Defense Readiness Reporting System-Marine Corps (DRRS-MC), the Pre-deployment Training Program (PTP) Toolkit, and the Marine Corps Total Force System (MCTFS).

The MCTIMS application is currently hosted in the Marine Corps Information Technology Center (MCITC) in Kansas City, MO. The MCITC provides the hosting facility for the MCTIMS Production, Beta, and Training instances in a virtual environment.

Figure 1: MCTIMS Modules

TFITS Management Plans 1.3

Table 5Table 5 on page 13 identifies the TFITS management plans that provide overarching guidance for TFITS managed projects. These documents form the foundation for the baseline for TFITS common best business practices.

Reserved 1.4

Reserved 1.5

Contractor Performance 1.6

The contract shall be performed in accordance with this PWS and the Government’s Quality Assurance Surveillance Plan (QASP). Additionally, the contract shall be performed in accordance with the processes and standards in the Contractor’s Post Deployment Software Support (PDSS) Plan, Software Development Plan (SDP), Project Management Plan (PMP), and Quality Assurance Program Plan (QAPP).

Objectives 1.7

The PDSS and system maintenance and performance upgrades shall be performed, managed, and monitored to the Government’s price, schedule, and performance objectives, through an integrated and defined set of project processes tailored from Capability Maturity Model Integration (CMMI) Level III, or equivalent, or a higher set of standard project processes.

The MCTIMS system shall be available on a 24 hour basis, 7 days a week.

Accurate and complete system documentation (configuration baselines, technical documentation, information assurance documentation, user documentation, web-based training, etc.) updates, and any required certifications/accreditations shall precede the deployment of any capabilities where available in the government provided tool.

2 Transition (Reserved)

3 PDSS (Reserved)

4 Software Development (Deliverable E026) All software development initiatives impact the system baseline, and are governed by the ECP process as defined in the SDP and TFITS Management Plans. The SDP lays out the process required to develop, modify, or upgrade Government software and describes the details of each step along with any considerations that need to be addressed. The TFITS SEP defines the 4-octet ECP classification system that is used to assign ECPs as either a capability change, major change, minor change, or a maintenance change, and details how SETR process, as defined in the Marine Corps SETR Handbook, are tailored based on this classification level.

Software Development Plan (SDP). 4.1

The Contractor shall develop an SDP and execute a project-level system engineering process that addresses and coordinates with the processes, products, functions, and objectives described in the TFITS SEP. The Contractor shall provide an initial SDP and deliver an updated version as required. The Contractor shall continue to update the SDP to maintain alignment with this SEP. This SDP is considered a living document that will be updated as necessary to support evolving requirements and maturing products and processes. The SDP shall be updated with each system maintenance and performance upgrade. At a minimum, an update to the SDP will be reflected for each system maintenance and performance upgrade (classified as either an second octet/major or third octet/minor change) and new capability requirements (classified as a first octet capability change) shall ensure and provide the following in accordance with the specified level of SETR tailoring based in the ECP classification level:

• Describe how the SDP can produce supporting artifacts that are based on the recommended methodology in the Supplement to Guidebook for Acquisition of Naval Software Intensive Systems: Software Criteria and Guidance for Systems Engineering Technical Reviews; and TFITS Management Plans.; and the Marine Corps Systems Command Technical Review Handbook, v1.4 dated April 2009.

• Describe in the SDP specific Software Development areas where cost savings will be realized through reusability, reliability, and maintainability.

• Provide a strategy for integrating CM, Human Systems Integration, Logistics, and Cybersecurity into each stage of the software development process

At a minimum, the SDP shall provide the Contractor’s approach to:

4.1.1 Provide derived requirements, update Requirements Traceability Matrix (RTM). Table 7 Deliverable E001)

4.1.2 Design software, detailed in the System/Subsystem Design Description (SSDD). (Table 7 Deliverable E002)

4.1.3 Develop software, detailed in the Software Build Plan. (Table 7 Deliverable E003)

4.1.4 Test software, detailed in the Software Test Plan and System STP. (Table 7 Deliverable E004)

4.1.5 Deploy Software. (Table 7 Deliverable E005)

4.1.6 Data driven Department of Defense Architecture Framework (DoDAF) compliance views (as necessary per TO).

SDP Annexes 4.2

An annex to the overarching SDP shall be developed in response to each software development related TO. At a minimum, the annex for each System Enhancement (classified as either an second octet or major or third octet minor change) and New Capability Requirements (classified as a first octet capability change) TO shall ensure and provide the following in accordance with the specified level of SETR tailoring based on the ECP classification level:

4.2.1 Requirements Analysis Phase.

The key objective of the Requirements Analysis Phase is to transform the Government’s needs into a technical view of a required product that could deliver those needs. Efforts involve defining user needs and requirements in the context of planned user use environments and identified system characteristics to determine requirements for system functions.

At a minimum, the Contractor shall:

4.2.1.1 Elicit derived requirements.

4.2.1.2 Perform an iterative process of decomposing requirements into system functional requirements and establishing traceability.

4.2.1.3 Maintain traceability between the derived and Government-provided requirements.

4.2.1.4 Align requirements analysis efforts with MCSC acquisition requirements

(TFITS Management Plans and SETR process).

4.2.1.5 Provide documentation needed to support the MCSC SETR process for

System Requirements Reviews (SRR) and System Functional Reviews

(SFR).

4.2.1.6 Document the functional baseline.

4.2.2 System Design Phase

The objective for the System Design Phase is the on-time delivery of Government-approved documentation that provides the detailed design of each configuration item in the approved product baseline. The System Design phase produces a design that is based on the functional descriptions and products developed during the

Requirements Analysis phase. The design is reflected in the products developed and delivered by the Contractor.

At a minimum the Contractor shall:

4.2.2.1 Provide the Contractor’s design process including the use of design and modeling tools, analyses, and tradeoffs.

4.2.2.2 Align the Contractor’s process with the TFITS Management Plans and the MCSC SETR process for Preliminary and Critical Design Reviews (PDRs/CDRs).

4.2.2.3 Provide documentation needed to support the PDRs/CDRs.

4.2.2.4 Document the Allocated and Product baselines.

4.2.3 Development Phase

The prime objective for the Development Phase is the on-time delivery of a Government tested and accepted capability solution.

At a minimum the Contractor shall:

4.2.3.1 Develop, integrate, assemble and test capability.

4.2.3.2 Provide in-process reviews to the MCTIMS Government Project

Managers and staff personnel, Functional Advocates, and designated Government representatives. IPRs shall be conducted on a monthly basis at a time and place and in a format agreed to by the Government.

(Ref. Table 7 Deliverable E020) .

4.2.3.2 .

4.2.3.3 Align the Contractor’s process with the TFITS Management Plans and

MCSC SETR process for Test Readiness Review (TRR).

4.2.3.4 Provide documentation needed to support the MCTIMS TRR, and PRR.

Documents will be accepted and reviewed by the MCTIMS Government technical staff at least 2 days prior to the formal review. (Ref: IDIQ PWS Table 6: Deliverable 019).

4.2.3.5 Support Government Acceptance Testing, IV&V, Human System Integration (HSI) reviews and testing, code review, and cyber-penetration testing. (Ref: Table 7: Deliverable E006).)

4.2.4 Deployment Phase

The prime objective for the Deployment Phase is the deployment of the Government-accepted capability into the production environment in accordance with the established performance standards.

At a minimum the Contractor shall:

4.2.4.1 Document the Contractor’s deployment process.

4.2.4.2 Validate that all certifications and accreditations are in place prior to deployment.

4.2.4.3 Prepare the system user community to receive and use capability.

4.2.4.4 Warranty the software for three (3) months from any defects.

4.2.4.5 Coordinate and deliver the deployment package, including release notes, within the PDSS Release Management Process. (Ref: Table 7 Deliverable E008)

4.2.4.4

4.2.5 Reserved.

5 Project Management Project Management (Reserved) 5.1

Task Management 5.2

A Task Management Plan (TMP) shall be developed in response to each TO specific to each Task PWS. At a minimum, the Contractor task management efforts shall perform the following Task Management requirements:1

5.2.1 ECP Task Initiation.

5.2.2 ECP Resource coordination and management, to include:

5.2.2.1 TO Roles and responsibilities.

5.2.2.2 Individual Security Clearances.

5.2.2.2.1 The Contractor shall have, and provide evidence of, individual clearances of team members to the MCTIMS Project Manager as appropriate as part of the procedures to be allowed to perform work on the MCTIMS the work required to perform the TO.

Background checks are conducted as part of the application for a Common Access Card and military email address. Sections 12 and 13 of this PWS provide additional information for the individual security clearances.

5.2.2.2.1

5.2.2.2.2 The Contractor shall have, and provide evidence of, Cybersecurity certification as appropriate to perform a specific TO.

5.2.2.2.2 current Secret Clearances for all individuals performing on classified aspects of this contract who will be required to access Secret information. Secret access is required in order to attend meetings and perform daily work inside approved areas. Access to Secret data requires unescorted access into Secret spaces and access to Secret information and/or systems (e.g., SECRET Internet Protocol Router Network

(SIPRNET)).

5.2.2.2.3 The Contractor shall have, and provide evidence of

1 System specific needs will be described in the TO.

Formatted: Normal, No bullets or numbering

Cybersecurity certification as appropriate to perform a specific TO.

5.2.3 ECP Task Execution.

At a minimum, the Contractor for Task Execution shall:

5.2.3.1 Perform quality assurance in accordance with the QAPP.

5.2.3.2 Participate in Iidentifying and managinge risks and providing inputs and updates to the TFITS Risk Management Plan. as necessary.

5.2.3.3 Host and/or attend, provide agenda, provide meeting minutes, and participate in any ad hoc Working Groups, Integrated Product Teams (IPT), Technical reviews, Technical Interchange meeting, In Process Reviews (IPR), and/or any other system specific meetings to support the requirements of Task Orders. (REF: IDIQ PWS, Table 6 Deliverables 019 and 029)

5.2.3.4 Identify the tools, techniques, and methodologies that will be used in this task execution.

5.2.4 ECP Performance Management.

5.2.4.1 Provide a Weekly Status Report, as directed per TO IAW the Task Management Plan

5.2.4.1.1 Provide a Monthly Status Report (MSR) to include, at a minimum: All Priority 1 metrics from the TFITS Performance Measurement Plan, previous month’s activities, the status of the ECPs in process, to include updated risk register, upcoming activities, all incidents, summary of any service issues to include , problems, trends, schedule, progress towards the Pperformance Standard and Acceptable Qquality Levels (AQLs) and anticipated travel (with a justification for the travel). The status an metrics submitted for the MSR shall be in accordance with the TFITS Program Management easurement Plan. TOs that provide for more than one system shall provide one MSR for those systems, but with separate sections for each system.

5.2.5 ECP Task Closeout.

5.2.5.1 Provide orderly closeout of the ECP task order closeout including final delivery of any remaining Government products, hardware, software and preparation of a final report to include lessons learned and analysis of the task. (See IDIQ PWS Table 6 Deliverables 030)

Performance Management 5.3

The Contractor shall attend all Performance Evaluation Reviews (PER) convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The Contracting Officer (KO), COR, and other

Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the KO will apprise the Contractor of how the Government views the Contractor's performance and the Contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues.

Contract Closeout (Reserved) 5.4

6 Configuration Management Plan (Reserved)

7 Integrated Master Schedule.

The Contractor shall develop and maintain an overall MCTIMS IMS throughout the period of performance of the contract. The MCTIMS IMS shall provide information sufficient to the Government to demonstrate how the Contractor intends to manage the proposed effort:

At a minimum, the Contractor shall develop an IMS using Microsoft Project version 2010 compatible or a version otherwise approved by the government.

Table 1: Key Milestones Milestones Expected Date

• New Contract START

• Contract Kick-off Meeting

• Delivery Of MCTIMS Project IMS

• Baseline MCTIMS Project

• PDSS Transition complete

• Transition to Risk Management Framework

0 DAC

5 DAC

15 DAC

TBD

30 DAC

TBD

8 Performance Standards.

The Contractor shall be monitored against the performance standards and Acceptable Quality Levels described in the Table 2 below:

Table 2: Performance Standards (REF Table 7 ECP PWS Deliverable E007)

Performance Standard Methods of Surveillance Acceptable Quality Level

(AQL)

Timely delivery of specified deliverable

• MSR

• Deliverable Transmittals

95% of deliverables are delivered by the scheduled date

Successful completion of Government Acceptance Test

(GAT)

• GAT Integration & Test Scorecard and test Scripts

• SETR results

• Test reports/defect analysis

The software has no Severity 1 and 2 defects as defined in the TFITS System Test and Evaluation Strategy

Formatted: List Paragraph, Space Before: 0 pt, Bulleted + Level: 1 + Aligned at: 0" + Indent at: 0.25", Tab stops: 0.24", Left

Formatted: Font:

Performance Standard Methods of Surveillance Acceptable Quality Level

(AQL)

Successful completion of SETR reviews (SRR, SFR, PDR, CDR, TRR, PRR, PIR)

Review exit criteria

All critical RFAs are adjudicated within five business days

The software deploys on schedule • Updated IMS

• GAT Integration & Test

Scorecard

Software deployment is completed in accordance with the SI-developed and Government-approved IMS with no more than a five business day negative schedule variance.

Users know how to use system before change is deployed.

• Updated Training materials

• GAT Scorecard

Differences training should be part of the deployment package.

9 Applicable Documents and References

The following tables provide programmatic and technical information for the Contractor to consider in preparation of a response to this PWS.

Table 3: Program Documentation

Document / Reference Intended Use

SLA with Hosting Environment;

Operational Document MOC-033 MCEITS Service Level Agreement

Identifies agreements and coordination POCs with the system hosting environment

Interface Control Documents and/or System Interface Agreements

Documents the roles/responsibilities and data exchange information between this and other systems.

Risk Register Contains all risks.

ECP Tracker Database Government provided system that contains tracking of all system ECPs

Trouble Ticket Database Government provided system that contains all system Trouble Tickets.

Requirements Traceability Matrix Government requirements document.

Table 4: System Documentation

Document / Reference Intended Use

System Maintenance and Administration Manual

Describes the administrative functions to maintain the system

Configuration Item Technical Database Describes the hardware and software configuration items

Database Architecture Describes the system database architecture

User Manual Provides system Users with a quick reference to the tasks expected to be performed in the system.

Training Material Instructor training material to support classroom training

Test Scripts Set of instruction executed by a person to ensure the system is functioning correctly.

Table 5: TFITS Management Plans Document / Reference Intended Use

TFITS Systems Engineering Plan

(SEP)

Describes the systems engineering approach for TFITS projects.

TFITS Configuration Management Plan (CMP)

Describes the processes the TFITS Product Management Offices follow to define, document, implement, account for and audit changes to requirements and baselines, supporting processes and documents for each of the projects in its portfolio.

TFITS System Test & Evaluation Strategy (STES)

Defines the test & evaluation (T&E) approach for the TFITS Product Management Offices.

TFITS Requirements Management Plan

Defines the TFITS process of developing and maintaining requirements as well as controlling any changes to those requirements throughout the system life cycle.

TFITS Risk Management Plan

(RMP)

Provides guidance for implementing a risk management process, to assess the root cause of program risks, and to develop strategies to manage these throughout a systems’ lifecycle for TFITS projects.

TFITS Performance Measurement Plan

Provides all managed projects with a framework for reporting a set of core and specialized metrics to baseline system element performance and report a standardized set of Key Performance Indicators (KPIs) to stakeholders.

Table 6: Other Guidance & Standards

Document/Reference Intended Use

Federal Acquisition Regulation (FAR)

DoDD 5000.01/Defense Acquisition System Acquisition Guidance

MIL-HDBK-61/Configuration Management CM Guidance

MCSCO 4130.1/Configuration Management Policy CM Policy

Federal Information Security Management Act of 2014, 18 Dec 2014 Cybersecurity

National Defense Authorization Act current edition Cybersecurity

DoDI 8500.1, Cybersecurity, 3 March 2014 Cybersecurity

DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT),” 12 March 2014 Cybersecurity

DoD 8570.01-M, Information Assurance Workforce Improvement Program, Incorporating Change 3, 24 Jan 2012

Cybersecurity

National Institute of Standards and Technology Special Publication 800-39, “Managing Information Security Risk: Organization, Mission, and Information System View,” current edition

Cybersecurity

National Institutes of Standards and Technology Special Publication 800-53, “Security and Privacy Controls for Federal Information Systems and Organizations,” current edition Cybersecurity

NIST SP 800-53A, “Assessing Security and Privacy Controls in Federal Information Systems and Organizations: Building Effective Assessment Plans,” current edition Cybersecurity

Committee on National Security Systems Policy 22, “Policy on Information Assurance Risk Management for National Security Systems,” January 2012, as amended Cybersecurity

CNSSI No. 1253, Security Categorization and Control Selection for National Security Systems, 27 March 2014 Cybersecurity

CJCSI 6510.01F, Information Assurance (IA) and Support to Computer Network Defense Cybersecurity

Document/Reference Intended Use

(CND), 9 Feb 11

SECNAVINST 5000.2E, Department of the Navy Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System, 1 Sep 2011

Cybersecurity

SECNAVINST 5000.36A, Department of the Navy Information Technology Applications and Data Management, 19 December 2005 Cybersecurity

DoD Manual 5200.01 DoD Information Security Program; Overview, Classification, and Declassification, 24 Feb 2012 Cybersecurity

DoDI 5200.02, DoD Personnel Security Program (PSP), Incorporating Change 1, 9 Sep 2014 Cybersecurity

DoDD 8000.01, Management of the DoD Information Enterprise, 10 Feb 2009 Cybersecurity

MCO 5239.2B, Marine Corps Cybersecurity Program (MCCSP), 19 May 2015 Cybersecurity

DoDD 5400.11, DoD Privacy Program, 29 Oct 2014 Cybersecurity

SECNAV Instruction 5211.5E, Department of the Navy (DON) Privacy Program, 28 December 2005 Cybersecurity

Code Review Guidance: MARADMIN 657/13, Requirements for Network Security Source Code Review, 13 Dec 2013 Cybersecurity

United States Marine Corps (USMC) Enterprise Cybersecurity Directive (ECSD) 018, Marine Corps Certification and Accreditation Process, current version Cybersecurity

United States Marine Corps (USMC) Enterprise Cybersecurity Directive (ECSD) 011, Personally Identifiable Information Version 2.0, 30 November 2011 Cybersecurity

United States Marine Corps (USMC) Enterprise Cybersecurity Directive (ECSD) 021, Ports, Protocols, and Services Management version 1.0, 15 May 2012 Cybersecurity

United States Marine Corps (USMC) Enterprise Cybersecurity Directive (ECSD) 008, Secure Data Transfer Version 2.0, 17 December 2012 Cybersecurity

United States Marine Corps (USMC) Enterprise Cybersecurity Directive (ECSD) 026, Concept of Operations for Host Based Security System Version 1.0, 15 October 2012 Cybersecurity

Federal Information Security Management Act (FISMA) Cybersecurity, PII guidance

DoDI 5000.02/Operation of the Defense Acquisition System General Acquisition execution guidance

MIL-STD-881/Work Breakdown Structures Guidance on building WBS

IEEE/EIA 12207/Standard for Information Technology Software Life Cycle Processes Industry standard for Software Support

CJCSI 3170.01G/Joint Capabilities Integration and Development System Requirements guidance

MCSCO 5400.5/Naval SYSCOM Systems Engineering Policy SETR Guidance

10 Deliverables and Schedule.

All Deliverables shall be delivered to the Government’s electronic repository (SharePoint) with a notification to the Contracting Officer, Contracting Officer’s Representative, and the MCTIMS Project Manager.

Table 7: Deliverables

Deliverable Number

Deliverable Title

Format Date of first submission

Subsequent Submission

Inspection/Accep tance

PWS

Paragraph

E001 Requirements Traceability Matrix (RTM) updates

Government-provided

Final due 5 days before each SSR, SFR and contract closure.

Update for

PDR/CDR

and for contract closure.

Government COR Government Program Syetem engineer

4.1.1

E002 System/Subsys tem Design Description

Government-provided format

Draft prior to

PDR.

Final at CDR and contract closure.

Government COR Government Program Syetem engineer

4.1.2

E003 Software Build Plan

Government- Approved Contractor Format

Draft prior to

PDR.

Final at CDR and contract closure.

Government COR Government Program Syetem engineer

4.1.3

E004 Software Test Plan

Government- Approved Contractor Format

Draft prior to

PDR.

Final at CDR and contract closure.

Government COR Government Program Syetem engineer

4.1.4

E006 System/Softwa re Test Plan with Test Scripts

Government- Approved Contractor Format

Final at CDR. Updated at

TRR.

Government COR Government Program Syetem engineer

4.1.42.3.1.3 .4

E007 Integration & Test Scorecard (To include a summary to the Government)

Government- Approved Contractor Format

COB each day during all testing events

COB each day during all testing events;

(AKA:. Hot Wash)

Government COR Government Program Syetem engineer

Table 2

E008 Release Notes Government- Approved Contractor Format

At deployment N/A Government COR Government Program Syetem engineer

4.2.4.5

E020 Test Report and Defects

Government- Approved Contractor Format

Due at TRR. Update at

PRR.

MCTIMS

Government System Engineer’ Government COR and MCTIMS Government Project Manage

Table 2

E026 Software Development Plan (SDP) and updates

Government- Approved Contractor Format

60 days after Contract award.

(Draft provided as part of RFP response)

Each software maintenance and performance upgrades As required.

Government COR 4.1 4.2

Since it is difficult to predict when the need to create/update the artifact will occur, As Required is used.

11 Government Furnished Information and Equipment The Government will provide all of the source code, system documentation, system manuals, and web-based training source code. The Government provides the shared data environment where all MCTIMS Program information resides. The shared data environment includes repositories to support the MCTIMS Team’s configuration control process, baseline documentation, CITDB, action items, risk management, etc. The Marine Corps Information Technology Center (MCITC), in Kansas City provides the hosting facility for the MCTIMS Production, Beta, and Training instances in a virtual environment.

12 Security Requirements

The information provided to the contractor will be unclassified and/or sensitive unclassified information. The contractor is not required or expected to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance Levels. Any contractor personnel requiring access to U.S. Government sensitive unclassified information shall possess a completed background investigation (minimum of a NACI) for this Public Trust Position.

13 Common Access Cards

The Contracting Officers Representative (COR) will identify and approve those contractor employees performing on this contract that require Common Access Cards (CACs) in order to perform their job function. In accordance with Headquarters, United States Marine Corps issued guidance relative to Homeland Security Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a CAC. In order to meet the eligibility criteria, contractor employees requiring a CAC, must obtain and maintain a favorably adjudicated Personnel Security Investigation (PSI.) Prior to authorizing a CAC, the employee’s JPAS record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened.) The minimum acceptable investigation is a National Agency Check with Written Inquiries (NACI.) If a contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked.

Facility Security Officers (FSOs) are responsible for notifying the MCSC Security Director if any contractor performing on this contract receives an unfavorable adjudication after being issued a CAC. The FSO must also notify the MCSC Security Director of any adverse/derogatory information associated with the 13 Adjudicative Guidelines/Factors concerning any contractor issued a CAC, regardless of whether a JPAS Incident Report is submitted.

Each CAC is issued with a “ctr.usmc.mil” e-mail account that the individual contractor is responsible to keep active by logging in on a regular basis (at least twice a month), sending an e-mail and clearing any unneeded e-mails. Contractors are prohibited from “auto-forwarding” their .mil e-mail account to their .com e-mail account. If the ctr.usmc.mil e-mail account is not kept active, the G-6 will deactivate the account and CAC will lose its functionality.

Common Access Cards (CACs) will only be issued to those contractors supporting this contract that have been authorized by the COR. The COR will only authorize CACs for those contractors that meet current Homeland Security Presidential Directive – 12 (HSPD-12) criteria and have a definitive requirement.

If a contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they have also lost their eligibility to perform on MCSC contracts. CACs are not issued for convenience.

14 Place of Performance

The place of performance shall be as specified in the task order award.

15 Period of Performance

The period of performance shall be as specified in the task order award.

16 Travel and Other Direct Costs (ODC)

Any travel requires Government COR approval/authorization. Travel and ODCs associated with PDSS and software development will be on a cost only reimbursable basis. No fee shall be allowed for travel or ODC costs. The Contractor will be authorized travel expenses in accordance with FAR 31.205-46, consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. The Government expects the Contractor staff to be located within a reasonable commuting distance from Marine Corps Base Quantico. Any reimbursable travel incurred during the performance of the contract shall not include travel for day-to-day work activities.

17 Appendix A – Acronyms

Acronym Definition ADS Authoritative Data Source AQL Acceptable Quality Level ATO Authority to Operate CAC Common Access Card CDR Critical Design Review CITDB Configuration Item Tracking Database CM Configuration Management CMMI Capability Maturity Model Integration CMP Configuration Management Plan COR Contracting Officers Representative DoD Department of Defense ECP Engineering Change Proposal ERB Engineering Review Board FISMA Federal Information Security Management Act FRACAS Failure Reporting and Corrective Action System FSO Facility Security Officer GAT Government Acceptance Test HSI Human Systems Integration HSPD Homeland Security Presidential Directive HST Headquarters, Sustainment and Training IA Information Assurance ID/IQ Indefinite Delivery/Indefinite Quantity IMS Integrated Master Schedule IPR In Process Review IPT Integrated Product Team IT Information Technology ITIL Information Technology Infrastructure Library ITSCM IT Security Continuity Management JPAS Joint Personnel Adjudication System JTR Joint Travel Regulations KO Contract Officer MAC Mission Assurance Category MCEITS Marine Corps Enterprise Information Technology Services MCITC Marine Corps Information Technology Center MCO Marine Corps Order MCSC Marine Corps Systems Command MCTIMS Marine Corps Training Information Management System MSR Monthly Status Report NACI National Agency Check with Written Inquiries ODC Other Direct Costs PdM Product Manager

Acronym Definition PDR Preliminary Design Review PDSS Post Deployment Software Support PER Performance Evaluation Review PIR Post Implementation Review PMP Program Management Plan POA&M Program of Action and Milestones POC Point of Contact PRR Production Readiness Review PSI Personnel Security Investigation PWS Performance Work Statement QAPP Quality Assurance Program Plan QASP Quality Assurance Surveillance Plan RFA Request for Action RMF Risk Management Framework RMP Risk Management Plan SDP Software Development Plan SEP System Engineering Plan SETR Systems Engineering Technical Review SFR System Functional Review SIA System Interface Agreement SIPR Secure Internet Protocol Router SLA Service Level Agreement SRR System Requirements Review T&E Test and Evaluation TECOM Training and Education Command TFITS Total Force Information Technology Systems TMP Task Management Plan TO Task Order TRR Test Readiness Review USMC United States Marine Corps

18 Appendix B – Engineering Change Proposals

ECP No.

MCTIMS-0001

Upgrade systems interface with Navy’s Corporate Enterprise and Training Activity Resource (CeTARS)

REQUIREMENTS

Description: The existing MCTIMS-CeTARS systems interface needs to communicate through a web service at 30 minute intervals to enable more efficient, near real time registration and event processing.

• The MCITMS system shall enable web services to communicate on an on-demand basis.

• The MCITMS system shall enable real time (or near real time, 30 minute intervals), on demand web service transaction communication between MCTIMS and CeTARS system interfaces.

• The MCITMS system shall use a bi directional interface between CeTARS and MCTIMS.

• The MCITMS system shall exchange data, such as schedules and quota allocations, using Web Services (Port

443 with SSL encryption).

• The MCITMS system shall process schedule and quota updates to account for quotas with already confirmed

CeTARS reservations.

• The MCITMS system shall provide notification to Admin users upon receipt of new schedules, schedule changes, and quota allocation changes from CeTARS.

• The MCITMS system shall provide notification to Admin users when a course’s OSCN, OS Loc, or Course

Data Processing (CDP) codes loaded in Student Registrar no longer match the Navy CDP or Course Identification Number (CIN) codes in CeTARS.

In support of this ECP and proposed changes, the Contractor shall:

• Work with MCTIMS user advocates and TFITS Engineering staff to generate formal requirements statements and documentation showing proper parent/child relationships that define business rules applicable to this change.

• Conduct additional requirements analysis and decomposition to further define and identify system requirements with the user advocacy

• Conduct updates of the MCTIMS Oracle Database (11.2.0.4 and above) level application code, which is stored procedures, packages, functions, views, and triggers that are written in PL/SQL, to become compliant with new data formats from external interfaces .

• Conduct application development utilizing C#, ASP.Net, Java Script, HTML, XML and XSLT. Compiling into DLLs to add new features in MCTIMS application.

• Conduct development and update queries to the MCTIMS Report server module using Cognos Report Net.

• Update MCTIMS design documentation of system baselines, system documentation, user documentation and training documentation..

Stakeholders/User Groups: MCTIMS PMO, TECOM Functional Owners

Delivery Date: Priority:

Change Level: 3rd Octet SETRs Required: RR, DR, TRR,GAT, PRR and PIR Description of Higher Level Requirement:

The mission of CeTARS is to provide improved availability of training information, quota allocation data and real time student tracking to the Navy and Marine Corps training communities. The interface between CeTARS and MCTIMS is two-way. CeTARS and MCTIMS exchange data using Web Services (Port 443 with SSL encryption). This includes providing data to assist Sailors and Marines in career tracking and planning, and to quota managers for training seat allocation purposes. In turn, CeTARS contributes to the NETPDTC mission of providing the Naval Service and Marine Corps with quality products and services to support and enhance education, training, career development, and personnel advancement. CeTARS serves as the Navy’s authoritative data source for all Navy formal training courses assigned a Course Identification Number (CIN). It facilitates the collection, storage, modification, and retrieval of training information about the students attending Navy courses, as well as course-related data, and quota data for planning/execution of Navy training. In addition, CeTARS provides student and training information required by various echelons of the Navy and supports management and administration functions for Navy individual training sites, Learning Centers, TSCs/TSDs, NSTC/NPDC/CNATRA and all other Navy training commands including BUMED and SWIT.

ECP No.

MCTIMS-0002

Upgrade Task Master Module

REQUIREMENTS

Description: The Taskmaster Module provides the ability for authorized users to create, update, and delete mission specific task sets within the MCTIMS system. These task sets are used within the Unit Training Module and sent to the Defense Readiness Reporting System – Marine Corps (DRRS-MC). The upgrade of this module will consist of the following items:

• The MCTIMS system shall provide a function that will allow user to view specific task and standards in two Task Sets at a time

• The MCTIMS system shall have the ability to copy task data (with/without standards) between two Tasks Sets.

• The MCTIMS system shall have the ability to open a window where standards text can be inserted.

• The MCTIMS system shall have the ability to search for a training event from the T&R manual and/or UTM allowing link between the two.

• The MCTIMS system shall have the “train to all” column removed from the system.

• The MCTIMS system shall have a column for training events from the UTM to the “measure” text box.

• The MCTIMS system shall be able to have multiple print options for Task Set Reports.

• The MCTIMS system shall have a Task Master Task Set “History Report” (similar to History Report ability already developed and used within the Marine Corps Task List suite).

• The MCTIMS system shall Import UJTL “Conditions” List data file, for use within Task Master Module applications

In support of this ECP and proposed changes, the Contractor shall:

- Work with MCTIMS user advocates and TFITS Engineering staff to generate formal requirements statements and documentation showing proper parent/child relationships that define business rules applicable to this change.

- Conduct additional requirements analysis and decomposition to further define and identify system requirements with the user advocacy

- Conduct updates of the MCTIMS Oracle Database (11.2.0.4 and above) level application code, which is stored procedures, packages, functions, views, and triggers that are written in PL/SQL, to become compliant with new data formats from the DRRS-MC interfaces

- Conduct updates of specific database table fields from which the data is stored and retrieved within the MCTIMS Oracle Database (11.2.0.4 and above)

- Conduct application development utilizing C#, ASP.Net, Java Script, HTML, XML and XSLT. Compiling into DLLs to add new features in MCTIMS application.

- Update MCTIMS design documentation of system baselines, system documentation, user documentation and training documentation.

Stakeholders/User Groups: MCTIMS PMO, TECOM Functional Owners Delivery Date: Priority:

Change Level: 3rd Octet SETRs Required: RR, DR, TRR,GAT, PRR and PIR Description of Higher Level Requirement:

The MCTIMS Task Master module provides data to the Marine Corps Combat Development Center (MCCDC) to maintain the gold source record for Marine Corps Tasks (MCTs), Marine Corps Task Sets and the Marine Corps Task List (MCTL). The standards in Task Master are linked within MCTIMS to the Training & Readiness Manual and unit Training Management (UTM) and form the basis of a unit’s Mission Essential Task List (METL).

ECP No.

MCTIMS-0003

Student Management (SM) Module upgrade

REQUIREMENTS

Description: Incorporate the capability to identify TECOM trends, gaps and recommend solutions to support TECOM Performance Management efforts.

• Development of performance data requirements to track, collect, report, and analyze data.

• Assist in the development of the TECOM Performance Management authoritative data source reporting structure and access to enhance and leverage MCTIMS reports server capability to meet TECOM, DoN, and DoD performance reporting requirements.

• Identification of other Marine Corps Performance Management authoritative data source (ADS) systems and develop the necessary code to link those systems within the MCTIMS SR Module

In support of this ECP and proposed changes, the Contractor shall:

- Work with MCTIMS user advocates and TFITS Engineering staff to generate formal requirements statements and documentation showing proper parent/child relationships that define business rules applicable to this change.

- Conduct additional requirements analysis and decomposition to further define and identify system requirements with the user advocacy

- Conduct updates of the MCTIMS Oracle Database (11.2.0.4 and above) level application code, which is stored procedures, packages, functions, views, and triggers that are written in PL/SQL, to become compliant with new data formats from the identified Marine Corps Performance Management authoritative data sources.

- Conduct updates of specific database table fields from which the new authoritative data source (ADS) data will be stored and retrieved within the MCTIMS Oracle Database (11.2.0.4 and above)

- Conduct application and web development within MCTIMS Microsoft Internet Information Services (IIS) Web Server. The Web application, will be programmed in .Net which utilizes C#, ASP.Net, Java Script, HTML, XML and XSLT.

- Conduct updates to new automated system interfaces with MCTIMS to be encrypted using SFTP, Oracle ASO, or Web Services.

- Update MCTIMS design documentation of system baselines, system documentation, user documentation and training documentation.

Stakeholders/User Groups: MCTIMS PMO, TECOM Functional Owners

Delivery Date: Priority:

Change Level: 3rd Octet SETRs Required: RR, DR, TRR,GAT, PRR and PIR

Description of Higher Level Requirement:

The MCTIMS Student Management module provides the capability to manage class rosters, units and individual students for Marine Corps Formal Learning Centers and Marine Corps Detachments. This enables the efficient tracking of a student counseling, sick call attendance, PFT/CFT and transfer history. Reports may be created to include many common student data fields which are updated daily from Operational Data Store Enterprise (ODSE).

1.1.1 Reserved.