PATS_Task_Order_-_Exhibit_D_TO_PWS.docx

12 May 2015 Exhibit D Task Order Performance Work Statement For Product Manager (PdM) Total Force Information Technology Systems (TFITS) Program Analytical Technical Support (PATS)

Scope:

The scope of this effort is to deliver consolidated Program Management and Logistics support for Projects and Portfolios within Product Manager (PdM) Total Force Information Technology Systems (TFITS).

TFITS supports 28 major Projects (Applications/Systems) organized into three Main Portfolios of systems or Tier 2s (See Appendix B - TFITS Organization Chart):

· Manpower Operation Systems (MOS)

· Warfighting, Planning, and Analysis (WPA)

· Headquarters Marine Corps (HQMC) Sustainment and Training (HST)

TFITS has categorized each Project requiring support into two defined segments: Managed and Supported. There are 23 Managed and 5 Supported Projects (See Appendix B – TFITS Project Descriptions). The following definitions are provided for clarification:

1) Managed: TFITS has control of all funding required for end-to-end life cycle acquisition sustainment. Full support of Program Management, Cost Analysis, Engineering, Information Assurance, and Logistics is required.

2) Supported: TFITS has limited programmatic authority of the Project. This includes Joint Projects that require United States Marine Corps (USMC) certification and accreditation, fair share funding, and Configuration Management support.

The number of projects managed by TFITS is expected to change on a year to year basis and the Contractor should be prepared to support the addition of two to three new programs/projects annually.

The requirements identified in this PWS will provide support to the following tiers of the TFITS organization:

1) Tier 1: PdM, Deputy Product Manager (DPdM), and functional area Competency Leads. These are the leadership roles within PdM TFITS, reporting to the higher PM-110 Tier 0 level.

2) Tier 2: Three (3) TFITS Portfolio Managers, overseeing TFITS Acquisition and Portfolio Management: MOS; WPA; and HST.

3) Tier 3: TFITS Project Managers (PjM), managing Project level Applications/Systems within the overarching Tier 2 structure.

The required Logistics support includes facilitating sustained operations to include support strategies, acquisition documents, products, and agreements, asset management, technical documentation, and training support.

Purpose:

This Task Order is intended to deliver Project Management and Logistics support. The Task Order Matrix (Attachment 2) and the Task Order Historical Level of Effort (Exhibit A) identifies the anticipated support required by each project and historical support estimates.

Reserved

General Requirements:

All deliverables shall be submitted to the Contracting Officer’s Representative (COR) who will be responsible for deliverable tracking and acceptance.

The Contractor shall organize and attend TFITS meetings within 10 miles driving distance of the Quantico Corporate Center located at 1000 Corporate Drive, Stafford, Virginia. Contractor personnel shall attend regular meetings with stakeholders in the general vicinity of Marine Corps Base Quantico and as far away as the Pentagon. Contractor personnel are expected to be physically present at numerous meetings each week in support of PdM TFITS Integrated Product Teams at the Product, Portfolio and project levels.

Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

The Contractor shall report Contractor labor hours (including Subcontractor labor hours) required for performance of services provided under this contract for the United States Marine Corps via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

1) W, Lease/Rental of Equipment;

2) X, Lease/Rental of Facilities;

3) Y, Construction of Structures and Facilities;

4) S, Utilities ONLY;

5) V, Freight and Shipping ONLY.

The Contractor shall submit to the Contracting Officer's Representative quarterly reports showing the total amount of labor costs incurred under this task order, broken out for the Prime Contractor and each Subcontractor. The Government will use this information to ensure the Contractor's compliance with Federal Acquisition Regulation 52.219-14, Limitations on Subcontracting.

Deliverable A0001: COR Quarterly Report

During the performance of their duties, the Contractor will work closely with the Government project teams and be exposed to project level data. All Contractor personnel supporting this contract will be required to sign and submit a U.S. MARINE CORPS SUPPORT CONTRACTOR NON-DISCLOSURE AGREEMENT (INDIVIDUAL) and may be ineligible to compete in future associated project support contracts.

Specific Requirements:

Tier 1 Program Management Support:

1.1.1 Within five (5) working days of task order award, the Contractor shall organize and attend a kick off meeting.

1.1.2 Within 30 days of task order award, the Contractor shall develop and maintain a contract management plan.

Deliverable P0001: Contract Management Plan (CMP)

1.1.3 Within 30 days of initial award, the Contractor shall develop and submit a diagram of the company organizational chart depicting the personnel directory with the positions and matrix of support. Once developed, the diagram shall be maintained on a quarterly basis.

Deliverable P0002: Organizational Diagram

The Contractor shall conduct quarterly In-process Reviews that address an overall assessment of contract status, project review, program risk, status of funds, status of vacancies, schedules, completed deliverables, and concerns.

The Contractor shall prepare and submit a Monthly Status Report (MSR) by the fifth (5th) calendar day, for the preceding month of performance, throughout the contract period of performance. The MSR shall cover monthly accomplishments, status of deliverables, planned activities for the next month, status of invoicing and billing, updated risk list and any other items that need the Government’s attention. The Contractor shall collect and report on the performance metrics associated with deliverable and schedule completion. The final format for the report shall be coordinated between the Government and Contractor. At a minimum the MSR shall include:

· Contract Number

· Invoicing Period (start and end dates)

· List of accomplishments during the period by task/deliverable

· Contract issues and risks ranked by severity

· Contract Line Item Number status

· Rationale for deviations from schedule with mitigation plan

· Any other significant issues (schedule, technical, resource, etc.) with proposed resolution

Deliverable P0003: Monthly Status Report

Contract Final Report - The Contractor shall deliver a contract final report summarizing the entire period of performance. The report shall include a summary of all MSRs delivered. The report shall include all contract accomplishments, deviations from plan with background information, and lessons learned from contract activities (what has been experienced, and process improvement recommendations). The Contractor shall provide with the final report a complete set of indexed contract documentation, including the closed contract.

Deliverable P0004: Contract Final Report

The Contractor shall organize and attend Tier 1 Weekly Meetings within 10 miles driving distance of the Quantico Corporate Center located at 1000 Corporate Drive, Stafford, Virginia. Network and power connections for each attendee are required. Presentation equipment must be available for use to include, but not limited to projectors, televisions, monitors, and conference capable telephones.

The Contractor shall develop, submit, and deliver meeting minutes for Tier 1 Weekly Meetings within two (2) working days following the meeting.

Deliverable P0005: Tier 1 Meeting Minutes

Reserved

The Contractor shall update and maintain the Program Management Review (PMR) and Quad Chart templates to ensure compliance with Tier 0 as well as Tier 1 requirements on a monthly basis.

Deliverable P0006: Project Management Review and Quad Chart Templates

Reserved

The Contractor shall attend and brief their program support status at the weekly TFITS Tier 1, highlighting the support being provided at the Tier 1, Tier 2, and Tier 3 levels in order to reallocate resources if necessary based on PdM priorities.

The Contractor shall develop and deliver reports capturing personnel utilization metrics on a monthly basis to ensure personnel resources are being assigned to PdM TFITS priorities.

Deliverable P0007: Status Slides for TFITS Briefings

The Contractor shall coordinate and review TFITS Program Management Reviews for proper formatting and sequence prior to briefing the Tier 0 and Tier 1 on a monthly basis.

Reserved

The Contractor shall update and maintain the TFITS Standard Operating Procedures for USMC IT Procurement Process, Department of Defense Information Technology Portfolio Repository – Department of the Navy (DITPR-DoN), and standard spend plan execution process in order to standardize the business process within TFITS on a quarterly basis.

Deliverable P0008: Standard Operating Procedures (SOP)

The Contractor shall update and maintain TFITS Acquisition Decision Memorandums and Acquisition Program Baselines for each Project on an annual basis.

The Contractor shall review current and prepare additional required Project artifacts to support Clinger Cohen Act compliance, across supporting competencies on an annual basis.

Tier 2 & 3 Program Management Support: Be advised that work on the Total Force Structure Management System (TFSMS) and the Defense Readiness Reporting System – Marine Corps (DRRS-MC) programs may involve the review of documents up to the NATO Secret Level.

The Contractor shall review and provide comments on System Integrator deliverables as defined in applicable contracts on a monthly basis.

The Contractor shall maintain PMRs and Quad Charts for TFITS Managed Projects, and Quad Charts for TFITS Supported Projects on a monthly basis.

The Contractor shall draft, submit, and track all Shopping Cart orders and Information Technology Requests using the Information Systems and Infrastructure Shopping Cart and Information Technology Procurement Request Review/Approval System within TFITS. It is estimated that 150 IT Procurements will need to be conducted annually. The TFITS IT Request Tracker shall be updated on a weekly basis.

Deliverable S0001: Shopping Cart Order and IT Request Tracker

The Contractor shall participate, develop and submit agenda and meeting minutes, submit recommendations to Project issues, provide updates and resolution to action items in coordination with the PjM for the weekly Tier 2 and Tier 3 Integrated Product Teams (IPTs).

Deliverable S0002: Tier 2 & 3 Meeting Minutes

The Contractor shall obtain and maintain access to Architecture Compliance and Requirements Traceability Tool, as well as update each Project record annually.

The Contractor shall document, update, and track Project risks identified by the Tier 2 and Tier 3 Project Managers on a monthly basis, to be briefed at the TFITS Tier 1 Meeting and maintained in the ISI Risk Tracker on SharePoint.

Deliverable S0003: Risk Tracker

The Contractor shall continually maintain Project-level Integrated Master Schedules (IMSs) in a government Microsoft Project/Microsoft Project Server 2013 in order to provide a consolidated view of key project events at the portfolio and TFITS levels. The schedules will also be used to help project the TFITS supply/demand to ensure appropriate resources are assigned/reassigned based on PdM TFITS priorities.

Deliverable S0004: Integrated Master Schedules

The Contractor shall provide the IMS derived schedule and supporting data to PjMs for inclusion in the TFITS Quad Chart on a monthly basis. This chart shows current resources, project schedule, key milestone events, and highlights any staffing issues.

The Contractor shall verify TFITS Projects are registered in Department of Navy Application and Database Management System (DADMS) DITPR-DON and review/update DITPR-DON records for Federal Information Security Management Act (FISMA) reporting and non-tier annual reviews to support OSD mandates.

The Contractor shall validate and track any software implemented is registered and approved for Marine Corps use in DADMS in sync with quarterly system upgrades.

The Contractor shall update and confirm The Online Project Information Center (TOPIC) pages remain current by posting approved programmatic, schedules, contracts, test, requirements, logistics, project images, briefs, and safety documents to TOPIC based on the predefined document categories within on a semi-annual basis.

The Contractor shall update all project artifacts that feed the Assistant Secretary of the Navy, Research, Development, and Acquisition dashboard on a quarterly basis.

The Contractor shall update and maintain Project Probability of Programmatic Success (PoPS) assessments on a quarterly basis.

The Contractor shall update the Independent Logistics Assessment (ILA) Checklist respective to the Program Management competency on an annual basis.

For Joint Forces Requirement Generator (JFRG) Modernization and Theater Medical Information Program only The Contractor shall maintain and deliver the Acquisition Strategy/Acquisition Plan (ASAP), to include updating existing and drafting new Plan on an annual basis.

Deliverable: S0005 – UPDATED TFITS ASAP

The Contractor shall draft the Marine Corps Systems Command (MCSC) Core Briefing Package required to support new gate decision meetings. There will be an estimated two Core Briefing Packages, across TFITS Programs each year.

The Contractor shall provide one new Core Brief as required by the Tier 1 For DRRS-MC the Contractor shall update the existing Core Briefing Package.

For JFRG Modernization the Contractor shall update the exiting Core Briefing Package.

For TFSMS the Contractor shall update the existing Core Briefing Package.

Deliverable S0006: MCSC CORE BRIEF

The Contractor shall maintain the TFITS Consolidated System Integration Contract Invoice Tracker for timeliness of deliverables against contractual requirements on a monthly basis.

The Contractor shall draft Business Case Analyses (BCAs) in support of TFITS contract modifications. It is estimated that TFITS will draft 10 BCAs per year.

Logistics Support:

The Contractor shall maintain the 8 TFITS Item Unique Identification (IUID) compliance, plans in accordance with MARCORSYSCOM policy.

Deliverable S0007: IUID Plan Review

The Contractor shall develop and maintain TFITS Fielding, Deployment, Disposal, and Transition Plans. TFITS will require up to 10 plans per year.

The Contractor shall develop the JFRG Fielding, Deployment, Disposal, and Transition Plans.

Deliverable S0008: Fielding Plan Deliverable S0009: Deployment Plan Deliverable S0010: Transition Plan Deliverable S0011: Disposal Plan

The Contractor shall develop and maintain a complete Life Cycle Sustainment Plans (LCSPs) for programs with an Acquisition Category (ACAT) or Abbreviated Acquisition Program (AAP) designation, for programs that are in the process of receiving an ACAT or AAP designation and or as directed.

The Contractor shall update and maintain the TFSMS LCSP Deliverable S0012: LCSP

The Contractor shall annually review and maintain Table of Authorized Material Control Number (TAMCN) and TAMCN data elements within the TFSMS for the programs that have been assigned TAMCN.

The Contractor shall review and track System Integrator logistics deliverables such as User and Training Manuals on a monthly basis, comments will be recorded on a Comment Resolution Matrix (CRM).

Deliverable S0013: CRM

The Contractor shall monitor and record within the Configuration Item Technical Database (CITDB) all hardware warranty and software assurance statuses for each HW and SW item under this contract.

Deliverable S0014: Updated CITDB

The Contractor shall forecast the requirement to replace or upgrade any hardware or software item that is within 12 months of the projected End of Life / End of Service or end of warranty support / end of software assurance. The Contractor shall submit an Engineering Change Proposal (ECP) for each item that requires replacement or upgrade in accordance with the TFITS CM plan. This deliverable should be delivered with in the first 60 days after contract award, and annually thereafter.

Deliverable S0015: ECPS that support end of life/end of service or end of warranty support/end of software assurance.

The Contractor shall ensure that any major upgrades to hardware or software for a program is documented in the programs IMS.

The Contractor shall continually support the ILA process for those programs that are required to complete the ILA process. This task includes coordinating and conducting meetings, collecting data, and the assembly of the various reports and products required to support the ILA process.

Reserved

The Contractor shall develop and maintain Training strategies as required for programs in sustainment.

Deliverable S0017 Training Strategy

The Contractor shall review and analyze training materials, updates to training, and tools used in support of training, as required, in support of system sustainment and upgrades.

The Contractor shall support with attendance and participate in all TFITS Tier 3 programs IPTs.

The Contractor shall support the TFITS logistics personnel with Program and IPT support.

The Contractor shall support a weekly Log IPT, the Contractor shall coordinate an agenda and publish meeting minutes for each meeting.

Facilities, Other Direct Costs (ODCs), and Travel Requirements:

Work efforts in support of this task effort will be accomplished at the Contractor’s facilities. This task will require the Contractor to provide a suitable infrastructure to manage program requirements (document library, databases, web site) throughout the course of performance to support the scope of activities. Such facilities are not reimbursed as ODCs. Laptops, cellular equipment/services, and other items of convenience are not reimbursable as ODCs.

All Government printing requirements MUST be done by or through the local Document Automation and Production Service (DAPS, now called DLA Document Services) http://www.daps.dla.mil/dapsonline.html.

All work is expected to be completed by personnel residing within the local commuting area and any travel necessary to complete the work is expected to be included within the Task Order’s Fixed Firm Price. While travel may be required to support the requirements of this Task, (See Table 1), travel is expected to be limited. Travel shall be handled in accordance with the Joint Federal Travel Regulations, at the direction and approval of the COR. Unauthorized travel, or travel not coordinated with the COR shall not be reimbursed. Additionally, travel costs in excess of the CLIN funded value shall not be reimbursed, unless changed by mutual agreement of the parties through a contract modification.

Table 1: Proposed Travel

Security Requirements:

This contract will require the Contractor to have a Secret Facility Clearance and will require certain Contractors to obtain and maintain classified access eligibility. The Contractor shall have a valid Secret Facility Clearance prior to classified performance. The prime Contractor and all sub-Contractors (through the prime Contractor) shall adhere to all aspects of DoD Directive 5220.22-M. All personnel identified to perform on this contract shall maintain compliance with Department of Defense, Department of the Navy, and Marine Corps Information and Personnel Security Policy to include completed background investigations (as required) prior to classified performance. This contract shall include a DoD Contract Security Classification Specification (DD Form 254) as an attachment. The Contractor shall notify the Government (written notice) within twenty-four hours of any Contractor personnel added or removed from the contract that have been granted classified access, issued a Common Access Card and/or MarCorSysCom Building access.

Common Access Card (CAC) Requirements:

7.1 The COR will identify and approve those Contractor employees performing on this contract that require 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 Joint Personnel Adjudication System (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. If a Contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked.

7.2 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.

7.3 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.

7.4 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 (HSPD-12) criteria and have a definitive requirement.

7.5 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. Such individuals must be replaced on the contract as soon as possible; not to exceed 30 calendar days unless otherwise coordinated and approved by the COR. CACs are not issued for convenience.

7.6 All contract support requiring administrative access to IT systems shall have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. This does not apply to contract support working administrative tasks. The Contractor shall meet the applicable information assurance certification requirements, including-

1. DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; IAT level III or IAM Level II or higher preferred and

2. Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.

Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing cyber security functions.

Applicable Documents / References:

The following documents provide essential programmatic information that needs to be considered in the Contractor’s proposal and deliverables.

Contractor Management Documentation

Systems Engineering Documentation

Other Guidance & Standards

ALPS-GDBK-001 Marine Corps Systems Command Item Unique Identification Implementation Guidebook 24 Nov 14

MIL/DoD/SECNAV Guidance/Requirements

Deliverables List