PM_ISI_Consolidated_Support_PWS_(20151218).pdf

PDF 173 KB Posted

Attached to
Program Management Office Support
Solicitation number
M67854-16-R-4950
Issued by

About this file

PWS

View the file

Other files

Show all 13

On GovTribe

Work with this file

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

Text version

Attachment 1 - Performance Work Statement

For

Program Manager (PM) Information Systems & Infrastructure (IS&I)

Program Management Office (PMO) Support

1. Scope: The scope of this effort is to deliver portfolio management and analytic support, administrative and operations support, and core competency support within the areas of Program

Management, Logistics, Engineering, Contracts, and Financial Management within the Program

Manager, Information Systems & Infrastructure (PM IS&I) program management office (PMO). The requirements identified in this PWS will provide support to the following tiers of the PM IS&I organization:

- Tier 0: PM, Deputy Program Manager (DPM), and Assistant Program Managers. These are the leadership roles within PM IS&I.

- Tier 1: There are five (5) PdM offices in PM IS&I: Emergency Response Systems (ERS), Marine Corps Network and Infrastructure Services (MCNIS), Total Force Information

Technology Systems (TFITS), Information Technology Strategic Sourcing Initiatives

(ITSS), and Marine Corps Enterprise Information Technology Services (MCEITS). Each

Tier 1 consists of a Product Manager (PdM), Deputy Product Manager (DPdM), and functional area Competency Leads. These are the leadership roles within each of the five individual PdM offices, reporting to the higher PM-110 Tier 0 level.

- Tier 2: Twenty-two (22) PdM office Portfolio Managers, overseeing PdM office

Acquisition and Portfolio Management.

- Tier 3: PdM office Project Officers, managing Project-level Applications/Systems within the overarching Tier 2 structure.

2. Purpose: Each PdM office within PM IS&I develops and executes portfolio-wide technical and program strategies to obtain efficiencies and provide informed, strategic management, oversight, and execution of the individual projects contained therein. This effort will provide program management and logistics support to inform and enable these technical and program strategies. To this end, specific activities, bound by the requirements specified in sections 3 and 4 below, include employing best business practices and processes, preparing the program for successful milestone decisions, participating in Integrated Product Teams (IPTs), validating Systems Integrator (SI) Deliverables, planning and participating in Government testing and evaluation activities, and ensuring delivered capabilities are fully supportable.

Task Orders (TOs) will be issued based on the Contractor’s response to a Government need. Each

Request for Proposal (RFP) for TOs will contain the following aspects and parameters that are specifically tailored to the system requirements: Task Order PWS, to include Deliverables (and travel, if applicable), and Government Furnished Equipment and Information (if applicable).

3. Contract/Program Management

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

3.2. The Contractor shall organize and attend PdM office 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 office

Integrated Product Teams at the Product, Portfolio and project levels.

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

3.4. The Contractor shall report Contractor labor hours (including Sub-Contractor 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.

3.5. 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 Sub-Contractor. The Government will use this information to ensure the

Contractor's compliance with Federal Acquisition Regulation 52.219-14, Limitations on

Subcontracting.

Deliverable 0001: COR Quarterly Report

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

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

Deliverable 0002: Contract Management Plan (CMP)

3.8. 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 0003: Organizational Diagram

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

3.10. 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 0004: Monthly Status Report

3.11. 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 0005: Contract Final Report

3.12. During the performance of their duties, the Contractor will working closely with the

Government project teams and will be exposed to program and 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 system integration contracts.

4. Types of Support

The following are broken out for clarification of requirement. The Government intends to issue task statements based upon size and complexity that may include one or more of the following types of support.

4.1. Tier 0 Support (Program Management Office Level Support)

4.1.1. Strategic Planning & Technical Studies: PM IS&I requires technical expertise to support strategic planning and portfolio management efforts. These efforts require short term access to subject matter experts (SMEs) to conduct technical studies and provide recommendations and guidance to the support the development and execution of United

States Marine Corps (USMC) IT objectives. The Contractor shall provide access to subject matter experts (SME) in critical technology areas that are able to provide insight and recommendations specific to ongoing Marine Corps and IS&I initiatives at the IT professional level. The Contractor shall provide unlimited access to technical research and unmetered analyst inquiries for your technical team. Supplemental technical support is required across a wide range of technical and professional needs, to include:

- Application Platforms & Development

- Mobility support specific to the DoD

- Deployment and Management of Cloud Computing Services

- Security & Risk Management

- Data Center Management and Optimization

- Data Management

- Identity & Access Management

- Content & Collaboration

- Professional Effectiveness

The Contractor shall leverage research in the development of strategic plans and technical studies that provide advice on how to deploy specific IT related programs for information technology and data center staff. Requested deliverables shall include IT architecture documents that focus on application platforms, collaboration and content, cloud computing platforms and approaches, data management, data center management and optimization, identity management, mobility support within the DoD, security and risk management.

Deliverable 0006: Strategic Planning/Technical Studies Analysis and Reports

Deliverable 0007: Strategic Planning/Technical Studies Summary & Recommendations

Briefings

4.1.2. Assistant Program Manager (APM) and Tier 0 Technical Staff Support: The PM workload is assigned to the APMs in functional areas aligned with the DoD Acquisition

Framework across the initiation, development deployment, operations and disposal of programs and projects within the PM IS&I portfolio. The APMs are assisted by members of the technical staff who serve as subject matter experts in specific competency areas.

APM and technical staff support includes: program management, life cycle logistics, engineering, risk management, information assurance, contracting, and financial management.

The Contractor shall provide program management and acquisition support to functional roles assigned to the APMs and members of the technical staff that support PM IS&I.

The Contractor shall perform program/project management analysis, support, and coordination for multiple Acquisition Category (ACAT) and Abbreviated Acquisition

Programs (AAPs), as well as an assortment of managed and supported projects that are not established programs but require project management expertise and analysis. These programs and projects vary in scope and complexity across the PM IS&I portfolio. The

Contractor shall provide analysis of program/project documentation in support of APM-

PM efforts. Analysis of program/project documentation and supporting tasks requires an in-depth knowledge of the DoD 5000 Defense Acquisition Management System, in addition to DoN and Marine Corps Systems Command (MCSC) supplemental policies and regulations. The Contractor shall support and participate in Integrated Product

Groups (IPTs), industry, and government meetings as required. The Contractor shall support requirements such as the following, which include, but are not limited to:

- Draft, develop, review, and provide analysis of acquisition documentation in support of meeting program goals and objectives

- Ensure that documentation is in compliance with all mandatory DoD, DoN, and

MCSC policies, directives, and regulations

- Develop detailed process and documentation in accordance with the MCSC

Acquisition Guidebook and associated processes

- Provide detailed analysis and assessment within functional areas

- Record and disseminate meeting minutes and action items

- Support the APM staff in preparation for IPT efforts and

- Support the PM and his staff in the conduct of Milestone Assessment Team

(MAT) reviews

Deliverable 0008: Tier 0 Analysis and Reports

Deliverable 0009: Tier 0 Briefings

Deliverable 0010: Tier 0 Meeting Minutes

Deliverable 0011: Tier 0 Action Items

Deliverable 0012: Tier 0 Financial Execution Reports

Deliverable 0013: Tier 0 Contract Status/Summary Reports

Deliverable 0014: Project Management Review and Quad Chart Templates

Deliverable 0015: Standard Operating Procedures/Process Guides

4.1.3. Competency Management Support: The APMs provide expert advice, mentoring, and promote personnel career development within the competency areas of program management, life cycle logistics, contracting, financial management, and engineering.

The Contractor shall support the APMs in executing the competency hiring process (i.e.

scheduling interviews, maintaining the Table of Organization structure, and related tasks). The APM SharePoint portal consists of five (5) separate sub-sites. Each sub-site supports an individual competency/APM (program management, life cycle logistics, contracting, financial management, and engineering). The Contractor shall manage the

APM SharePoint portal which shall include, but is not limited to:

- Posting all competency-specific human resource planning, APM Milestone

Assessment Team (MAT) documentation, and training requirements for all PM IS&I personnel.

- Providing office management and administrative support to include management of

SharePoint Portal documentation, as well as upkeep and development of SharePoint folders, links to Department of Defense (DoD), Department of the Navy (DON), and

Marine Corps sites as deemed necessary.

- Enhance and update the APM SharePoint portal and sub-sites.

- Collect and manage updates to existing references and documentation and post relevant information to the APM SharePoint portal and sub-sites.

- Support APM business operations and provide direct support in gathering and reporting data.

4.2. Tier 1 Support (Product Management Office Level Support)

4.2.1. Tier 1 Program Management & Acquisition Support: The Contractor shall provide program management and acquisition support to the Tier 1 staff within the PdM office.

The Tier 1 staff consists of the PdM, DPdM, and Assistant Product Managers (APdMs) representing the following competencies: program management, logistics, engineering, contracting, and financial management. Support requires in depth knowledge of the DoD

5000 Defense Acquisition Management System, in addition to DoN and Marine Corps

Systems Command (MCSC) supplemental policies and regulations, in addition to expertise in risk and schedule management. The Contractor shall support and participate in Integrated Product Groups (IPTs), industry, and government meetings as required.

The Contractor shall support requirements such as the following, which include, but are not limited to:

- Attend, participate in, and organize Tier 1 staff meetings

- Capture and distribute of meeting minutes and action items

- Develop, track, and report against established funding execution metrics

- Develop and maintain PdM office briefs (to include Program Management

Review (PMR) templates and quad charts)

- Maintenance and modification of project level financial artifacts such as Spruill, belt, and inflow/outflow charts on a weekly basis to support Tier 1 and Tier 0 briefings to provide the PM/PdM with decision making information necessary for overall management.

- Update and maintain Standard Operating Procedures as required

- Coordinate program reviews

- Develop and update acquisition documentation in preparation for key milestones

(such as Acquisition Decision Memorandums and Acquisition Program

Baselines)

- Maintain the PdM Risk Management Plan

- Organize and attend the PdM Tier 1 risk management board and update the PdM

Risk Tracker

- Develop and submit meeting minutes for Monthly Risk management board

Meetings.

Deliverable 0016: Tier 1 Meeting Minutes

Deliverable 0017: Tier 1 Action Items

Deliverable 0018: Tier 1 Financial Execution Reports

Deliverable 0019: Tier 1 Contract Status/Summary Reports

Deliverable 0020: Tier 1 Risk Management Artifacts

Deliverable 0021: Integrated Master Schedules

4.2.2. Tier 1 Business Management & Analytic Support: The Contractor shall provide business management and analytic support to include financial risk assessments for scheduled events, impact of changes, preventative and corrective actions, and analysis of phasing/obligation Rates. Examples of potential support requirements include, but are not limited to:

- Draft, consolidate and submit Risk Assessment data for inclusion in Program

Management, Executive, and General Officer Reviews on a monthly basis.

- Consolidate and monitor all project inch stones at a portfolio level (Tier 1 and 2) for funding obligations and identify timelines are being met in accordance with the Office of the Secretary of Defense execution benchmarks

- Perform portfolio aggregate financial analysis and develop and submit the

Portfolio Financial Analytical Reports

- Monitoring on the status of portfolio funds within the in accordance with established Government processes and tool sets, and consolidating and analyzing changes to financial artifacts

- Review Program Objective Memorandum submissions for consistency across the portfolio and ensure the funding requested is consistent with the Project Cost

Estimates

- Administer and maintain the Microsoft SharePoint Site Collection

- Provide administrator and issue support for users of the SharePoint Portal

- Consolidate and submit the PdM Weekly Situation Report (SITREP) to PM IS&I

- Coordinate and track responses for Marine Corps Action Tracker System taskers

Deliverable 0022: Tier 1 Analysis and Reports

Deliverable 0023: Tier 1 Briefings

4.2.3. Cost Analysis Support: The Contractor shall support Command and PdM level cost analysis requirements. Types of deliverables and efforts required as a result of this support are:

- Coordinate with the Project Officers and submit annual updates to the Project

Cost Estimates

- Create, update, maintain, and deliver each Cost Analysis Requirements

Document (CARD) and Logistics Requirements and Funding Summary (LRFS)

- Create, update, maintain, and deliver the PLCCE on an annual basis

- Develop and present cost related briefings to the respective decision-making authorities at IPRs, Technical Review Boards, and Contract Review Boards

- Develop and deliver and maintain project cost models

Deliverable 0024: Cost Estimates (CARD/LRFS/PLCCE/POE)

Deliverable 0025: Cost Briefings

Deliverable 0026: Cost Models

4.3. Tier 2/Tier 3 Support (Project Level Support)

4.3.1. Program Management Support: The Contractor shall provide program management support at the project/program level. Specific examples of required support include:

- Review and provide comments on System Integrator Deliverables as defined in applicable contracts on a monthly basis

- Maintain PMRs and Quad Charts for PdM office projects/programs

- Draft, submit, and track documentation required to execute procurement of hardware and software

- Document, update, and track risks identified by the Tier 2 and Tier 3 Project

Managers

- Develop and maintain project-level Integrated Master Schedules (IMSs)

- Provide the IMS derived schedule and supporting data to Project Officers

- Update and confirm The Online Project Information Center (TOPIC) pages remain current by posting approved documents

- Update all project artifacts that feed the Assistant Secretary of the Navy, Research, Development, and Acquisition dashboard

- Update and maintain Project Probability of Programmatic Success (PoPS) assessments and develop PoPS core briefing charts

- Maintain and deliver the Acquisition Strategy/Acquisition Plan (ASAP), to include updating existing and drafting new ASAP

Deliverable 0027: Tier 2/3 Program Documentation (ASAP/APB)

Deliverable 0028: Probability of Program Success (PoPS) Briefs

Deliverable 0029: Tier 2/3 Integrated Master Schedules

4.3.2. Life Cycle Logistics Support: The Contractor shall provide life cycle logistics support at the project/program level. Specific examples of required support include:

- Maintain PdM office Item Unique Identification (IUID) compliance, plans in accordance with MARCORSYSCOM policy

- Develop and maintain Fielding, Deployment, Disposal, and Transition Plans

- Develop and maintain complete LCSPs for programs that qualify as an

Acquisition Category (ACAT) or Abbreviated Acquisition Program (AAP)

- Review and maintain Table of Authorized Material Control Number (TAMCN) and TAMCN data elements within the TFSMS

- Review and track System Integrator logistics deliverables such as User and

Training Manuals

- 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

- Forecast the requirement to replace or upgrade hardware or software items

- Continually support the ILA process for those programs that are required to complete the ILA process

- Conduct Manpower, Personnel and Training (MPT) analysis and/or draft and deliver Manpower Personnel and Training Plans

- Review and analyze training materials, updates to training, and tools used in support of training, as required, in support of system sustainment and upgrades

- Support the PdM office logistics personnel with Program and IPT support

Deliverable 0030: IUID Plan Review

Deliverable 0031: Fielding Plan

Deliverable 0032: Deployment Plan

Deliverable 0033: Transition Plan

Deliverable 0034: Disposal Plan

Deliverable 0035: LCSP

Deliverable 0036: Manpower Personnel and Training Plan

Deliverable 0037: Training Strategy

4.3.3. Systems Engineering Support: The Contractor shall provide systems engineering support at the project/program level. Specific examples of required support include:

- Document, consolidate, and manage all requirements baseline capabilities for projects and programs on a monthly basis

- Coordinate, develop agendas, capture meeting minutes, submit recommendations to System Engineering issues and update resolutions for all Systems Engineering

Technical Reviews (SETR)

- Review, and update Engineering Management plans (Systems Engineering Plan

(SEP), Configuration Management Plan (CMP), (Systems Test & Evaluation

Strategy (ST&ES), Performance Measurement Plan (PMP), and Requirements

Management Plan (RMP)

- Attend, provide input and recommendations on technical matters, develop agendas, and briefing information in all Engineering IPTs and Engineering

Review Boards (ERB)

- Review and comment on the list of Engineering Change Proposals in support of

ERBs

- Develop and maintain the Program Protection Plan (PPP), as applicable

- Develop and/or maintain the Programmatic Environment, Safety & Occupational

Health Evaluation, as applicable

- review and update Memorandums of Understanding (MOU), Memorandums of

Agreement (MOA) and Service Level Agreements (SLA)

- Review and analyze data provided by the SI, and provide recommended engineering process improvements for action at the project level

4.3.3.1. Architecture: The Contractor shall provide architecture at the project/program level. Specific examples of required support include:

- Develop and maintain PM IS&I Architecture Development Standard

Operating Procedures (SOPs) annually

- Update existing Department of Defense Architecture Framework (DoDAF) architectural artifacts based on approved ECPs

- Develop, submit, and maintain interoperability certification, testing, waivers, and legacy documents

- Develop and/or maintain the: Information Support Plan (ISP) /Tailored

ISP/eISP, DoDAF Views, Department of Navy (DON) Enterprise

Architecture Compliance Confirmation and Waiver Request, Architecture

Compliance and Requirements Traceability, or government equivalent tool, and Department of Defense (DoD) Information Technology Portfolio

Repository – DON

Deliverable 0038: DODAF Architectural Documents

Deliverable 0039: Interoperability Documents

4.3.3.2. Requirements Management: The Contractor shall support requirements management at the project/program level. Specific examples of required support include:

- Perform requirements and traceability analysis, Requirements Traceability

Matrix updates, System Design Specification (SDS) updates

- Assessment of derived requirements to verify consistency and testability on a quarterly basis

- Conduct requirements analysis to support development of ECPs for ERB, Configuration Control Board (CCB), and SETR processes

4.3.3.3. Test and Evaluation: The Contractor shall provide test and evaluation support at the project/program level. Specific examples of required support include:

- Develop agendas, briefing information, capture meeting minute, submit recommendations to Test and Evaluation (T&E) issues, and provide action item resolution in support of the T&E IPT on a monthly basis

- Update and maintain the T&E Strategy on an annual basis

- Review and provide recommendations for test plans and results in support of requirement and design reviews and testing

- Review and recommend changes to the T&E metrics

- Determine and document the test success criteria that will be used to decide whether the requirement has been met

- Perform analysis of Government Acceptance Test (GAT) results to validate delivery of requirements and to characterize system performance in accordance with the SDS

- Review the technical documentation in accordance with the SEP; providing and collecting comments; generating, performing, and managing technical action items and reporting for the PM IS&I SETR process

- Develop and submit plans and test cases to support GAT and/or regression testing associated with the enhancement and test cases to support regression testing

- Prepare memoranda, reports, meeting agendas, and meeting minutes in support of PM IS&I Project testing events

4.3.3.4. Configuration Management: The Contractor shall support configuration management requirements at the project/program level. Specific examples of required support include:

- Maintain and control COR approved SI Deliverables, Configuration Item

Technical Database (CITDB) and Configuration Management System for each project on a quarterly basis

- Manage, track, and coordinate with the SIs on project baselines and conduct

Physical Configuration Audits for Configuration Status Accounting for each project on a quarterly basis

- Manage, track, and coordinate with the SIs to conduct Functional

Configuration Audits for each Managed Project on a quarterly basis

- Update and maintain the CITDB for each project via the Government provided tool on a monthly basis

- Participate in the ERB for each project on a quarterly basis by generating a list of ECPs to be considered for Engineering assessment

- Track and review configuration items in support of the Configuration

Management process

4.3.3.5. Information Assurance: The Contractor shall provide information assurance support at the project/program level. All personnel assigned to the IA requirements shall have an active Secret level clearance, or be able to achieve one within 30 days of the beginning of the period of performance. Specific examples of required support include:

- Continually monitor IA C&A processes for systems and applications for compliance with current and future Marine Corps System Command

(MCSC), HQMC, DON, and DoD policies, directives, guidelines, and instructions

- Review and update applicable information assurance controls, using the currently approved DoD policy mandate, i.e. DoDI 851001, DoD

Information Assurance Certification and Accreditation Process (DIACAP) or

Defense Information Assurance Risk Management Framework

- Identify and integrate IA requirements into the PM IS&I SETR monthly

- Review and provide feedback regarding SI security architectures, network diagrams, ports, protocols, data flows, and accreditation boundaries for IA compliance as needed

- Develop White Papers in support of accreditation decisions

- Review and update MOUs, MOAs, and SLAs to ensure IA compliance

- Prepare an Information Assurance Strategy per project in support of Clinger

Cohen Act requirements

- Prepare PPPs for designated systems

4.3.3.6. Independent Verification and Validation (IV&V): The Contractor shall provide

IV&V support at the project/program level. Specific examples of required support include:

- Prepare the PM IS&I Project for IV&V test events via IA documentation updates, pre-assessment support, self-assessment result evaluation, Plan of

Action & Milestone (POA&M) review and maintenance, and verify vulnerability scans and Security Technical Implementation Guides (STIGs) are performed on system/applications in preparation for IV&V

- Ensure systems are compliant with the latest STIGs

4.3.3.7. Certification and Accreditation (C&A): The Contractor shall provide C&A support at the project/program level. Specific examples of required support include:

- Review project Privacy Impact Assessments annually and develop updated documentation

- Review and develop documentation for the C&A process such as System

Boundary Diagrams, C&A Communication Diagrams, Information

Assurance Vulnerability Management (IAVM) Implementation Plan SOP, List of Privileged Users, Signed Security Rules of Behavior/Acceptable Use

Policy for privileged users, and Ports/Protocols/Services, as needed

- Track annual IA training/DoD 8570 certificates for system privileged users/IA Work Force

- Track the progress of accreditation packages throughout the C&A process

- Maintain a comprehensive Information Assurance Vulnerability Alerts

(IAVA) management plan

- Capture, consolidate, and report on PM IS&I Performance Measurement Plan compliancy metrics on a monthly basis

4.3.3.8. Vulnerability Testing: The Contractor shall provide vulnerability test support at the project/program level. Specific examples of required support include:

- Conduct and review monthly vulnerability scans using the approved government tool and develop mitigation strategies for identified findings

4.3.3.9. Interoperability Support: The Contractor shall provide interoperability support at the project/program level. Specific examples of required support include:

- Participate in weekly IPT meetings and provide input on interoperability documentation, to include architecture diagrams and Interoperability Support

Plan (ISP)

4.3.3.10. FISMA Compliancy Support: The Contractor shall support FISMA compliancy requirements at the project/program level. Specific examples of required support include:

- Participate in Annual Security Reviews, Annual Security Control testing, and

Annual Contingency Plan testing in compliance with the FISMA

- Confirm FISMA required quarterly POA&Ms are posted to IA reporting tool

4.4. Administrative and Operations Staff Support

4.4.1. Administrative Support: The Contractor shall provide administrative support at the Tier

0 and Tier 1 levels. Administrative support functions require proficiency in the use of the

Microsoft Office Suite. Specific examples of required support include:

- Prepare, review, track and file official correspondence

- Prepare official messages using AMHS

- Review Defense Travel System authorizations and vouchers upon submission by

Government travelers

- Update and maintain personnel rosters monthly per organization

- Coordinate and schedule meetings. Prepare agendas, meeting minutes, and presentation materials for each meeting attendee

- Scan, shred, and fax documents

- Prepare an organizational command chronology and update monthly

- Pickup mail at the Marine Corps Systems Command mail room and deliver official Government mail to the intended addressee

- Maintain and organize electronic files via the organizational shared drive

- Upload documentation to the Marine Corps Systems Command VIPER portal and organizational SharePoint sites

- Prepare briefing slides and spreadsheets (financial, informational and narrative)

- Manage the organizational tracking database

- Submit morning reports via Marine-On-Line Maintain electronic calendars for the organization’s leadership

- Inventory, stock, and organize office supplies

- Prepare new hire welcome aboard packages and process new hire joins into the organization

- Develop and maintain email distribution lists via the Marine Corps global outlook mailbox

- Process in the completion of System Authorization Access Requests (SAAR) forms for Contractor access to Government systems

- Prepare and maintain an organizational chart and table of organization

4.4.2. Operations Support: The Contractor shall provide operations support at the Tier 0 and

Tier 1 levels. Operations support functions require proficiency in the use of the

Microsoft Office Suite. Specific examples of required support include:

- Process and submit facility requests

- Collect and consolidate responses and submit Marine Corps Action Tracking

System (MCATS) taskers to the appropriate Government representative

- Prepare forward deployment packages for government civilian, Contractor, and military personnel travel to the various combatant commanders’ area of responsibility

- Issue and record technical asset management records for individual information technology equipment

- Execute and administer the quarterly Consolidated Memorandum Report in support in an accurate and timely manner

- Develop, administer, and maintain SharePoint sites

- Maintain accurate and timely accountability and proof of compliance for personnel deploying to the various Combatant Commands

- Maintain and update the Urgent Universal Needs Statement (UUNS) data base tracker system on a weekly basis with the most current and relevant program information

- Assign document numbers for all Marine Corps Systems Command equipment shipped outside the continental United States

- Contact and coordinate with the USMC Air Clearance Authority (ACA) to ensure the MCSC Project Officer and/or Contractor receives the Transportation

Control and Movement Documents (TCMDs) and Military Shipping Labels

(MSLs) for each shipment

- Maintain accountability and in-transit visibility of all equipment being produced and shipped in direct support of Operation Enduring Freedom (OEF)

- Update and maintain the Marine Corps Systems Command deployed status report

- Assist in the coordination of training, display and other organizational events in support of various Government and industry functions

5. 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. Specific travel guidance will be provided per Task Order.

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

7. Common Access Card (CAC) 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.

8. Period of Performance: The expected ordering period for this ID/IQ consists of five consecutive twelve (12) month ordering periods.

9. Deliverables:

Deliverable Table:

0001: COR Quarterly Report

0002: Contract Management Plan (CMP)

0003: Organizational Diagram

0004: Monthly Status Report

0005: Contract Final Report

0006: Strategic Planning/Technical Studies Analysis and Reports

0007: Strategic Planning/Technical Studies Summary & Recommendations Briefings

0008: Tier 0 Analysis and Reports

0009: Tier 0 Briefings

0010: Tier 0 Meeting Minutes

0011: Tier 0 Action Items

0012: Tier 0 Financial Execution Reports

0013: Tier 0 Contract Status/Summary Reports

0014: Project Management Review and Quad Chart Templates

0015: Standard Operating Procedures/Process Guides

0016: Tier 1 Meeting Minutes

0017: Tier 1 Action Items

0018: Tier 1 Financial Execution Reports

0019: Tier 1 Contract Status/Summary Reports

0020: Risk Management Artifacts

0021: Tier 1 Integrated Master Schedules

0022: Tier 1 Analysis and Reports

0023: Tier 1 Briefings

0024: Cost Estimates (CARD/LRFS/PLCCE/POE)

0025: Cost Briefings

0026: Cost Models

0027: Tier 2/3 Program Documentation (ASAP/APB)

0028: Probability of Program Success (PoPS) Briefs

0029: Tier 2/3 Integrated Master Schedules

0030: IUID Plan Review

0031: Fielding Plan

0032: Deployment Plan

0033: Transition Plan

0034: Disposal Plan

0035: LCSP

0036: Manpower Personnel and Training Plan

0037: Training Strategy

0038: DODAF Architectural Documents

0039: Interoperability Documents

File details come from the government source that posted it. Updated .