IdOps_PWS_TASK_ORDER_0002_PWS_FINAL_SLS_PKB.pdf

PERFORMANCE WORK STATEMENT

FOR

IDENTITY OPERATIONS PROGRAM MANAGEMENT AND ACQUISITION SUPPORT

(TEAM IDOPS)

TASK ORDER 0002: EXHIBIT B

1. Scope

This Task Order Performance Work Statement (PWS) sets forth the effort required by the Contractor to provide acquisition and program management support to the Marine Corps Systems Command

(MCSC) United States Marine Corps (USMC) Identity Operations

(IdOps) Team in the following competencies; Program Management, Administration, Financial Management, Logistics, and Engineering to include, but not limited to, curriculum development and

Biometrics trainer support. The IdOps Portfolio oversees the development, acquisition, and life cycle management of the

Identity Dominance System-Marine Corps (IDS-MC) Increment 1 and

Increment 2, the Biometric Enrollment and Screening Device

(BESD), and the Expeditionary Forensic Exploitation Capability

(EFEC) programs. Successful performance of this task order will require interfacing with a multitude of personnel from multiple external government and Contractor agencies, such as but not limited to: Space and Naval Warfare Center Atlantic, (SPAWAR)

Charleston, SC; Naval Surface Warfare Center, Dahlgren, VA; Army

Program Manager, Joint Personnel Identification; Marine Corps

Combat Development Center, Combat Development & Integration;

Head Quarters Marine Corps Intelligence Department; Head

Quarters Marine Corps Plans, Policies & Operations, Physical

Security; Marine Corps Intelligence Activity; et cetera.

1.1. Background

Within the IdOps Team, there are currently two Integrated

Product Teams (IPTs) organized along product lines, each led by a Program Analyst. Current programs managed by the

Biometrics IPT are the IDS-MC (Increments 1 and 2) and the

BESD, which provide a means to identify persons of interest encountered in the battle space. IDS-MC Increment 1 is an

Abbreviated Acquisition Program (AAP) in the Production and

Deployment Phase, and will replace the BESD AAP system in

FY17. IDS-MC Increment 2 seeks to enter the Acquisition

Framework post Milestone B, in the Engineering & Manufacturing

Development Phase.

The EFEC is currently managed by the Forensics IPT, which enables Marines to exploit evidence at sensitive sites and process latent fingerprints from weapons, crime scenes, and items of interest. The EFEC is seeking an AAP designation in

FY17. A current IdOps Team Organizational Chart and the IdOps portfolio schedules are included in Enclosures (1) and (2).

IDS-MC and EFEC will undergo a four-year technical refresh and equipment reset. Per the MCSC MAG, a new acquisition program may be required during each technical refresh effort.

Activities conducted by the IdOps Portfolio include the procurement, fielding, and sustainment of biometrics and forensics systems employed by the Marine Corps, as well as preparation and execution of any potential Urgent Universal

Needs Statement (UUNS) or new start programs requested by the

Marine Corps. This effort will be supported by multiple appropriations and budget lines.

The IdOps Team is dedicated to delivering integrated and interoperable force protection IdOps capabilities to the

Marine operating forces in order to accomplish their war-fighting mission. IdOps is committed to developing modular and scalable biometric and forensic capabilities, which provide our operating forces with a smaller, more adaptable footprint, capable of responding to any crisis environment.

IdOps is also responsible for providing materiel solutions for urgent war fighting requirements. Additionally, the IdOps team is a key stakeholder and participant in the overarching

Marine Corps Identity Operations community. The IdOps team implements innovative acquisition solutions and maximizes knowledge, technology, and the industrial base by collaborating with the Department of Defense Biometrics and

Forensics Enterprise, government, academic, and commercial organizations to achieve optimal integration and delivery of systems in support of the war-fighter.

The Contractor shall provide the detailed support described below in this PWS, in accordance with the MCSC Concept of

Operations, the MCSC Acquisition Guidebook, and the Defense

Federal Acquisition Guidebook. The nature of the support required under each Task Order depends on the acquisition stage of the particular programs within the IdOps Portfolio.

The IdOps Team organizational chart and program schedules are provided as enclosures to assist the Contractors in the delineation of tasks.

2. General Requirements.

The Contractor shall perform all tasks as outlined in this Task

Order. All deliverables shall be submitted to the Contracting

Officer’s Representative (COR). The COR is responsible for tracking and accepting all deliverables.

Contractors shall identify themselves as Contractor personnel and display distinguishing badges or other visible identification for meetings with Government personnel. If

Contractor personnel are introduced, it is their responsibility to ensure they are introduced as Contractor personnel.

Similarly, Contractor personnel shall display distinguishing badges or other visible identification that identifies them as

Contractor personnel whenever they are in 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 must provide a detailed transition plan demonstrating the offeror’s ability to rapidly acquire the program and systems knowledge necessary to minimize startup time and transition risk . Details of the Offeror’s transition plan should include a schedule of events regarding staffing, warehousing activities, training, and acquisition document control of required deliverables to meet the published program schedules. The offeror shall identify the level of experience of each key member of their proposal and how their experience relates to the requirements of this PWS.

3. Specific Requirements.

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

Non-disclosure agreements are required for all Contractors supporting this Task Order. The Contractor shall arrange all non-disclosure agreements necessary to interface with other

Contractors to accomplish the mission in support of this PWS in accordance with FAR 9.505-4. Copies of all non-disclosure agreements required for this contract shall be provided to the

Contracting Officer and COR.

The Contractor shall perform all tasks delineated below. The

IdOps Organizational/Program structure is provided as

Enclosures, and shall be considered to adequately address this

Task Order PWS.

3.1. IdOps Program Management and General Support. The

Contractor shall establish a management structure that ensures overall quality of deliverables and support to the IdOps team within their current and future acquisition phases, as well as any potential UUNS or new start programs. For purposes of estimating the support requirements, the vendor shall be required to develop and review all required acquisition documentation for at least one Abbreviated Acquisition program in accordance with the DoD 5000 and attachment 1, each quarter.

Additionally, the Contractor will be required to support a minimum of one major fielding decision per year and a minimum of one Milestone acquisition decision per year.

3.1.1. The Contractor shall organize, and attend, meetings

and IPT discussions as required, at least 20 meetings or IPTs per month. No local travel costs will be reimbursed. In addition, the Contractor shall write and submit meeting minutes

(B002) and agendas (B003).

3.1.2. The Contractor shall provide meeting space for at

least 2 meetings or IPTs per month.

3.1.3. The Contractor shall apply a comprehensive and

meticulous review of any acquisition documentation identified in, but not limited to, Attachment 1.

3.1.4. The Contractor shall provide a technical writer

review of final draft versions of documentation listed in, but not limited to, Attachment 1 (B005).

3.1.5. In the event there is no template available, the

Contractor shall draft correspondence in accordance with the most recent version of the Department of the Navy Correspondence

Manual.

3.1.6. The Contractor shall provide an individual to assist

in the development and maintenance of the Integrated Master

Schedules and Integrated Master Plans for each program and competency within the IdOps portfolio, using the current MCSC approved version of Microsoft Project. The Contractor shall provide innovative solutions to overlay schedules for portfolio management (B006).

3.1.7. The Contractor shall update and maintain a schedule, which identifies all development and support tasks, System

Engineering (SE) Technical Reviews (SETR), Milestone Assessment

Team (MAT) events, Independent Logistics Assessments (ILAs) events, Technical Readiness Assessments (TRA) events, and Test

Readiness Review (TRR) events. These items shall be incorporated into the integrated master schedule.

3.1.8. The Contractor shall update and maintain the PM Fact

Book with the IdOps portfolio of systems.

3.1.9. The Contractor shall update and maintain the contents

of the IdOps portfolio of systems Marine Corps Enterprise

Information Technology Systems (MCEITS) SharePoint sites for each program and competency area.

3.1.10. The Contractor shall update and maintain the IdOps

portfolio of systems in TOPIC sites.

3.1.11. The Contractor shall develop and maintain Program

Management Review, Interim Progress Review, and Decision Review briefs (B001).

3.1.12. The Contractor shall prepare briefs and presentation

material per designated templates.

3.1.13. The Contractor shall coordinate, distribute and

review the completion of the IdOps portfolio of systems taskers via the Department of the Navy Tasking, Records, and

Consolidated Knowledge Enterprise Repository (DON TRACKER) system.

3.1.14. The Contractor shall write, submit, draft, collect, and track responses and update the IdOps portfolio of systems

Risk Management Plans (B005).

3.1.15. The Contractor shall identify, track, and manage

programs’ risks.

3.1.16. The Contractor shall organize and participate in

Risk Management Working Groups and Review Boards.

3.1.17. The Contractor shall develop, review, and update the

IdOps portfolio of systems risk management program, risk registries, risk mitigation plans, and review all required acquisition program documentation for compliance with the PM

Risk Management Program.

3.1.18. The Contractor shall develop a Program Management

correspondence tracking system in SharePoint.

3.1.19. The Contractor shall write and submit a monthly

status report (B004).

3.1.20. The Contractor shall update, review, and manage the

Government data repository for program documentation, briefs, and presentations.

3.1.21. The Contractor shall write and submit trip reports.

Deliverables

CDRL B001 Presentation Material

CDRL B002 Conference Minutes

CDRL B003 Conference Agenda

CDRL B004 Contractor’s Progress, Status and Management Report

(CPS & MR)

CDRL B005 Technical Review of Final Draft

CDRL B006 Integrated Master Schedule

3.2. IdOps Engineering Acquisition Support. At no time will

the Contractor perform the work designated as inherently government work, nor will the Contractor ever be granted technical authority. With guidance and direction from the IdOps

Team:

3.2.1. The Contractor shall document the programs’

Environmental, Safety, and Occupational Health (ESOH) process, and draft the Safety statutory and regulatory acquisition documentation listed in, but not limited to, Attachment 1

3.2.2. The Contractor shall collect and file all required

safety documentation in safety binders for the IdOps Portfolio of systems. The Contractor shall coordinate the staffing of safety documents with the Marine Corps Systems Command Safety

Office for the Product Manager’s Environmental, Safety, and

Occupational Health (ESOH) Process.

3.2.3. In accordance with guidance provided by the most

current versions of MCSC Acquisition Guidebook, Department of

Defense Acquisition Guidebook, MCSC SETR Handbook (SIAT-HDBK-

001, 6 Aug 2014) approved templates or other form of authoritative MCSC acquisition guidance, the Contractor shall assist in the drafting of statutory and regulatory acquisition documentation listed in, but not limited to, Attachment 1.

3.2.4. The Contractor shall review and comment on the

engineering documentation in support of active programs and programs in sustainment. At a minimum, IMSs will be required to be updated for the IdOps Portfolio of systems monthly (B006).

3.2.5. The Contractor shall support the IdOps Team Engineer

as they conduct analysis, submit written reports, and provide recommendations on market research in support of Technology

Development Strategies. The Contractor shall support the Team

Engineer with the assembly of a written analysis report, and present technical data to support future engineering and design decisions.

3.2.6. The Contractor shall support the Team Engineer by

reviewing and providing written comments on Information Support

Plans (ISPs). When conducting the review, the Contractor shall ensure that ISPs are compliant with the CJCSI 6212.01 series, DODI 4630, and the Joint and Department of Defense Architecture

Framework (DODAF) architectural requirements.

3.2.7. The Contractor shall develop program Performance

Specifications (PSPEC) and Requirements Traceability Matrixes

(RTM) in accordance with the Team Engineer’s direction and MCSC guidance. The Contractor shall make use of Model Based Systems

Engineering methods to maintain traceability of requirements from the requirements to the PSPEC to the vendor derived requirements. The MBSE schema shall include the capability to record test results and will support generation of the RTM.

Deliverables

CDRL B006 Integrated Master Schedule

3.3 IdOps Financial Management.

3.3.1 The Contractor shall assist in the drafting and

reviewing of financial specific documentation and briefs. The scope of this task includes, but is not limited to Funding

Action Requests, Tri Annual Reviews, Staffer Briefs, BELT

Briefs, Service Requirements Review Board Database Request, Program Execution Plan, Command Planning and Resource

Allocations, inserting data into the Acquisition Financial

Information Database (A-FID) Microsoft Access based system, and

Procurement Request Builder documents.

3.3.2 The Contractor shall maintain FM knowledge, and

assist in the drafting and reviewing of financial specific documentation and briefs to assist in variance analyses, budget exhibit development/maintenance, spend plan and phasing plan development, execution reporting, and budget reconciliation.

3.3.3 The Contractor shall assist in the tracking of

the expenditures, obligations, and awards of funds, across the

IdOps portfolio, requiring familiarization with the DoD and MCSC financial databases, processes, and systems.

3.4 IdOps Logistics Support. At no time will the

Contractor perform the work designated as inherently government work, nor will the Contractor be granted technical authority.

With guidance and direction from the IdOps Team, the Contractor shall:

3.4.1 Communicate logistics requirements to IdOps Team

and support both internal and external program meetings.

3.4.2 Maintain and share knowledge of Acquisition Logistics

in support of various ACAT programs required to support an

Independent Logistics Assessments and Milestone Decisions.

3.4.3 Conduct an ongoing analysis of the USMC supply

system in order to ensure that equipment is fully supportable, cataloged, and that methods required to receive, store, transfer, issue and dispose of spares, repair parts and supplies are being performed IAW DoD 5000.02, the Defense Acquisition

Guidebook (DAG), MCSC Acquisition Guidebook (MAG), and DODI

4140.01 (DoD Supply Chain and Materiel Management Policy).

3.4.4 Maintain and share knowledge of Supply Chain

management implementation, sparing levels, reorder points, Just

In Time (JIT) process, and Total Quality Management (TQM) to support new and existing IdOps systems.

3.4.5 Develop Diminishing Manufacturing Sources and

Material Shortages (DMSMS) Plans and perform DMSMS analysis for all IdOps programs in order to identify and mitigates risks caused by DMSMS concerns. The Contractor shall conduct this analysis in order to identify potential issues that may result in extended long lead times, non-availability of supplies or parts, or system / part obsolescence for new and legacy IdOps systems.

3.4.6 Provide required information for Logistics

Requirements and Funding Summary (LRFS) to support the IdOps POM process, and assist the IdOps Team Logistician by conducting

LRFS quarterly.

3.4.7 Develop accurate and complete intent to field

messages, material fielding announcements, and other Naval

Messages related to logistics.

3.4.8 Develop required documentation for the Depot

Source of Repair (DSOR) process to support DSOR requests to

HQMC.

3.4.9 Request a Table of Authorized Materiel Control

Number (TAMCN) and Item Designator (ID) using appropriate forms for new and existing IdOps systems.

3.4.10 Maintain and share knowledge of the 12 Elements

of Logistics and apply them in the acquisition process to support new and existing IdOps systems.

3.4.11 Maintain and share, with the IdOps team, Comprehension of Provisioning, Logistics Management Information

(LMI) data and Source, Maintenance & Recoverability (SM&R) code processes required to support new and existing IdOps systems.

3.4.12 Draft, update and submit Item Unique

Identification (IUID) Plans in support of IdOps programs

3.4.13 Update and maintain the IUID registry in order

assist the Government in validating that IUID information is accurate and complete.

3.4.14 Draft, update, and submit New Equipment Training

Packages, to include New Equipment Training Plans, Lesson Plans, Instructor Guides, and Student Outlines (E001). The completion of this task will require a thorough understanding of the

Systems Approach to Training (SAT), curriculum development, Job and Task analysis, , and the development of training aids

(Computer based training, Quick reference cards, and Surrogate development) to support new and existing IdOps systems.

3.4.15 Remain knowledgeable of sustainment support

activities and their integration with each Competency (PM, FM, Contracts, SE) to support new and existing IdOps systems.

3.4.16 Maintain comprehension of Total Force Structure

Management System (TFSMS), Total Life-cycle Cost Tool-OST, and

Global Combat Support System – Marine Corps (GCSS-MC) to support new and existing IdOps systems.

3.4.17 Maintain knowledge of application of Sustainment

and Sustainment Management to support new and existing IdOps systems.

3.4.18 Support the IdOps Team Logistician in drafting, reviewing, and updating new and existing acquisition Logistics documentation listed in, but not limited to, Attachment 1.

3.4.19 Assist the Team Logistician in conducting Levels

of Repair Analysis (LORA) in order to determine the most cost effective levels of repairing IdOps equipment.

3.4.20 Perform weekly TFSMS reviews and updates, and

submit Table of Equipment Change Requests (TOECR) in order to ensure that MCSC responsible data fields remain current and up to date throughout the period of performance of this PWS.

3.4.21 Attend logistics meetings during the development

of Product Support Strategies and shall develop, update and maintain Life Cycle Sustainment Plans in support of IdOps programs.

3.4.22 Draft and revise Instructional Type (I-Type)

Publications (SI. TI, MI, LI, etc.) for Government review and approval. The Contractor shall notify the Government when the

I-Type Publications are posted to the USMC Technical

Publications website.

3.4.23 Develop, update and maintain Component Lists (SL-

3) for IdOps systems. The Contractor shall notify the

Government when SL-3s are posted t the USMC Technical

Publications website.

3.4.24 Develop, maintain, and review Operator and

Maintenance Technical Manuals in support of IdOps systems.

Technical Manuals will be reviewed every other year (minimum) in order to ensure that they are current and shall be updated as required by the Government.

3.4.25 Review and monitor the Failure Reporting, Analysis, and Corrective Action System (FRACAS). Additionally, the Contractor will provide the data from the analysis in the form of a FRACAS Report.

3.4.26 Draft Corrosion Control and Implementation Plans.

3.4.27 Conduct Job and Task Analyses (JTA).

3.4.28 Collect data for the Maintenance Task Analyses

(MTA).

3.4.29 Assist the IdOps Team Logistician by tracking

total asset visibility and accountability.

3.4.30 Be capable of participating as a member of the

fielding team, by traveling to fielding locations and assisting in the inventory and issue process.

3.4.31 Provide a dedicated equipment specialist at

Albany, GA to support the IdOps systems capable of completing the following task:

3.4.31.1 Collecting, analyzing, interpreting, and

developing specialized information for IdOps programs for use on life cycle management decisions.

3.4.31.2 Analyzing, reviewing, and submitting

Provisioning Technical Data (PTD) utilizing the LSA 036 format and Marine Interactive Computer Aided Provisioning System.

3.4.31.3 Participating in Provisioning Conferences

and provisioning publication projects, documenting findings to formulate a better understanding of the technical requirements and identification of tasks needed to implement corrective actions.

3.4.31.4 Formatting and developing Technical

Instructions and Validating and Verifying installation procedures.

3.4.31.5 Maintain thorough understanding of the

Albany Publication website and the Total Force Structure

Management System (TFSMS) to support new and existing IdOps systems.

3.5 Configuration Management Support. At no time will the

Contractor perform the work designated as inherently government work, nor will the Contractor ever be granted technical authority. With guidance and direction from the IdOps Team, the

Contractor shall:

3.5.1 The Contractor shall provide sufficient staff to

control the configuration of Documentation, to include but not limited to documents, procedures, baselines, and Standard

Operating Procedures in accordance with the configuration management plan.

3.5.2 The Contractor shall provide Configuration

Management (CM) support in the maintenance of CM Plans;

identification and tracking of hardware, software, and documentation; defining, documenting, and implementing change control processes in accordance with MCSC policies; and assist in the implementation of processes in accordance with the IdOps portfolio’s CM Plans – to include support to Engineering Change

Proposals.

3.5.3 The Contractor shall provide engineering

expertise and knowledge of defense standardization documents

(e.g., MIL-STD-961, MIL-STD-963 and MIL-STD-3100), ASME Y14 series standards on Engineering Drawing and Related

Documentation Practices and industry best practices on acquisition of design documentation to provide technical editing to the a design documentation handbook and training package for use by program management teams and to participate in drawing reviews and/or configuration audits.

3.5.4 The Contractor shall utilize Configuration Management

Professional as a software tool to track and manage configuration items.

3.6 IdOps Program MEF Support. Not applicable, at this

time.

3.7 IdOps Training Support

3.7.1 Maintain a thorough understanding of training and

have the ability to develop: training site requirements, Systems

Approach to Training (SAT), training development, Job and Task analysis, New Equipment Training (NET) schedules and briefs, and training aids (Computer based training, Quick reference cards) to support new and existing IdOps systems (D002, E001, E002).

3.7.2 The Contractor shall be capable of developing, maintaining, and presenting training Program of instruction

(POI) and lesson plans for the IdOps portfolio, to include interactive training.

3.7.3 The Contractor shall develop, maintain and

deliver operator and maintainer training instructions and New

Equipment Training for initial fielding, Engineering Changes, and/or delivery of new equipment to Marine Forces. International travel is required.

3.7.4 The Contractor shall provide inputs into the

IdOps systems Manpower, Personnel, and Training Analysis and

Manpower, Personnel and Training Plan during working groups.

Working Groups and IPTs are held as needed and not on any specific schedule. MPTA and P are developed by an agency that specializes in this effort.

Deliverables

CDRL D002 Status of Government Furnished Equipment (GFE) Report

CDRL E001 Training Materials

CDRL E002 Training Materials

3.8 IdOps Warehouse Storage and Support. Not applicable, at this time.

4. Facilities, Travel, and Other Direct Charges (ODCs).

4.1 Contractors Facilities. The contractor shall provide

the necessary resources and infrastructure to manage, perform and administer the task order. This task order will be performed at the Contractor’s facility. The Contractor facility must be located within 13 miles from the location being supported and must be capable of hosting Government meetings of

10 to 30 personnel. The facility shall include audio teleconferencing and briefing projection capability.

4.2 Travel and Other Direct Charges (ODCs). The Contractor

facilities described above and other expenses-such as laptop computers, cellular equipment/services and other items used to perform the task order-shall not be reimbursed as other direct costs (ODCs) unless specifically approved by the Contracting

Officer (KO). (Offeror proposals should not anticipate the KO approving such expenses as ODCs).

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

The Contractor shall provide meeting space for at least 2 meetings per month. However, the majority of meetings will occur at Marine Corps Systems Command or within the local vicinity of the National Capital Region. Anticipated “non-local” travel is reflected in each Team’s Task Order.

Travel to other Government facilities, field activities, Marine operating forces (U.S. and overseas) or other Contractor facilities may be required. All travel requirements (including plans, agenda, itinerary and dates) shall be pre-approved by the

Government COR or Alternate COR on a strictly cost reimbursable basis.

The Contractor shall make necessary travel arrangements for its employees after approval from the Government COR or Alternate

COR. Travel must be reimbursed in accordance with the Joint

Travel Regulation (JTR). Per Diem shall be per Government rates at http://www.defensetravel.dod.mil/site/perdiemCalc.cfm .

http://www.daps.dla.mil/dapsonline.html

When sufficient lead time allows, travel requests shall be submitted at least ten (10) working days in advance of the travel date. The request will include total cost and a break out of costs to include airfare, rental vehicle, per diem, mileage, parking, fuel and tolls. Travel requests will include the purpose of trip and why VTC or phone conversations would not meet the business requirement. If more than one traveler is travelling—sharing of rental vehicles is required.

Differing arrival and departure times will not justify separate rental vehicles. For rental cars carrying three or more travelers, larger vehicles may be authorized in advance. The

Government will reimburse economy lot parking. The Government will not reimburse valet parking.

The estimated travel requirements for the IdOps Contractor support team (2 people per trip) is as follows:

LOCATION

NUMBER OF TRIPS

ANTICIPATED IN

BASE PERFORMANCE

PERIOD

NUMBER OF TRIPS

ANTICIPATED IN

PERFORMANCE

PERIOD 2

NUMBER OF TRIPS

ANTICIPATED IN

PERFORMANCE 3

NUMBER OF TRIPS

ANTICIPATED IN

PERFORMANCE 4

NUMBER OF TRIPS

ANTICIPATED IN

PERFORMANCE 5

ESTIMATED

DURATION

SSC-A,

Charleston, SC

3 2 2 2 2 4 days

I MEF, Camp

Pendleton, CA

4 4 3 7 days

II MEF,

Camp

Lejeune, NC

4 4 3 7 days

III MEF,

Camp

Hansen, Okinawa, Japan

4 4 3 10 days

Dam Neck, VA

1 1 1 7 days

Ft Leonard

Wood, MO

1 1 1 7 days

Lackland

AFB, TX

1 1 1 7 days

Kuwait 2 2 2 10 days

Tampa, FL 1 1 1 1 2 5 days

5. 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 and a

Secret Document Safeguarding Level prior to classified performance at the contractor’s facility. 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. All Contractors performing on classified aspects of this contract shall have at minimum a current SECRET

Clearance. Classified involvement entails unescorted access into secure spaces and access to SECRET materials and/or systems

(e.g. SECRET Internet Protocol Router Network (SIPRNET) at

Government facilities. There will be SECRET products created and used at Government facilities under this contract.

Requests for Contractor SIPRNET accounts will be handled on a case-by-case basis and approved individually by the COR in accordance with Marine Corps Systems Command procedures and regulations.

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 MCSC Building access.

6. Contract Data Requirements List (CDRL)

CDRL# Deliverable

Description

PWS Paragraph

B001 Presentation

Material

3.1.11

B002 Conference

Minutes

3.1.1

B003 Conference

Agenda

3.1.1

B004 Contractor’s

Progress, 3.1.13

Status and

Management

Report (CPS

&MR)

B005 Technical

Review of

Final Draft

3.1.4

3.1.14

B006 Integrated

Master

Schedule

3.1.6

D002 Status of

Government

Furnished

Equipment

(GFE) Report

3.7.1

E001 Training

Materials

3.7.1

E002 Training

Materials

3.7.1

Enclosures.

Attachment 1: ACAT_III_IV_AAP_Document_Listing.xlsx

Exhibit: CDRL (s) 1423

Enclosure (1): IdOps Organizational Chart

Enclosure (2): IdOps Program Schedules

Enclosure (1)

Identity Operations Organizational Chart

Enclosure (2)

PM

Team Lead

Identity Operations (IdOps)

Program Analyst Program Analyst

BESD Program

Government

Key

IDS-MC Program

Sys Eng (SPAWAR) Sys Eng (SPAWAR)

IdOps Support Leads

MITRE

STE

Log (SPAWAR)

Finance Management

SPAWAR

Task Manager, SSA/SI

PA, SSA/SI

EFEC Program

Program Analyst Program Analyst (SPAWAR)

Log (SPAWAR)

Sys Eng (SPAWAR) Sys Eng (SPAWAR) Architect (SPAWAR)

IA (SPAWAR)

APMs

Sys Eng

T&E (SPAWAR)

Log

PSOH

Systems

Engineering

IA

T&E

Logistics

Finance

Contracts

IA (SPAWAR)

T&E (SPAWAR)

IA (SPAWAR)

Contracts Specialist

Identity Dominance System – Marine Corps Schedule

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

Operations & Support

FY17 FY22

Logistics

Supporting PoPS Gate

Template

Major Contract Events

Test & Evaluation

Cost

Information Assurance

*Will leverage Navy IA efforts to seek ATO reciprocity

As of: 19 Sep 2016

Fiscal Year FY16

Production &

Deployment

Quarter

Acquisition & Milestone

Events

Capabilities &

Requirements

Systems Engineering

FY20FY18 FY19 FY21

IDS-MC Fielding and Sustainment

PIR

MCHS/MCSELMS

Reciprocity ATO

Aware SW

Fielding Decision

Navy ATO

FCA

PRR

SVR

Reciprocity ATO

Quarterly IA Updates

Increment 2 Sustainment

Quarterly IA Updates

MPTP

FD

ILA

6.4

Env Test

Navy ATO

Update CARD Update CARD Update CARD Update

CARD

Update LCCE Update LCCE

Increment 2

RFP

Tech Refresh Contract

Increment 2 Testing (DT)

Increment 2 MS C Increment 2

FDD

Increment 2 Development

Increment 2 Fielding

MS C

ILA

FDD

ILA

PCA

FDD IOC

MDDR

TM V/V

NET

V/V

SVR-2

Env Test

TRRTRR

6.4

Quarterly IA TRR

Update

CARD

IOC

PIR

SSA Award

Update LCCE

6.5 6.5 6.3 6.4 6.5

Update LCCE

SSA Award SSA Award

SSA Award SSA Award

SRR

SFR CDR

PDR SVR

FCA

OT

LRIP

PCA

Expeditionary Forensic Exploitation Capability

Schedule

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

Major Contract Events *Note: MDA approval required prior to

RFP release.

Test & Evaluation *Note: Beyond LRIP Report applies only to DOT&E Oversight programs.

Cost

IA

*Note: Official strategy forthcoming

Quarter

Acquisition/Milestone Events

Supporting PoPs Gate Template

Capabilities/Requirements

Systems Engineering

Logistics

FY20 FY21 FY22

As of: 27 Sep 2016 Operations & Support

Fiscal Year FY16 FY17 FY18 FY19

6.5

LOC

Fielding Decision

EFEC Training

CLS

Op Yr

Sustainment Contract Award

OCO 18

Request

SI

SL-3

EFEC Sustainment/Disposal/Transition

MEF

Issue

6.5 6.5 6.5 6.5 6.5 6.5

Baseline

ECP002

Assets

Config Audit

Safety Release

PWS

SSP ITPRAS

TRR (ECP-002)

RFI

POM-19

FT-1

TRR (Equip Replace)

TEMP

FT-2 (Equip Replace)

RFP

Equip Replace Delivery

CDD

EFEC Sustainment

CCB

(ECP-002)

CCB (Equip Replace)

AAP

Designation

Software Maintenance

TRRs for Software Maintenance

NET Package Development

NIR (Equip Replace)

SEP

PSPEC

Increment 2 MDDR Increment 2

MS C

SRR

SFR CDR

PDR SVR

FCA

PCA

OT

CARD

LCCE

Increment 2

RFP

Inc 2 Contract Award

LRIP

Biometrics Enrollment Screening Device Schedule