GBOSS_Task_Order_0003_PWS_FINAL.docx

PERFORMANCE WORK STATEMENT

FOR

GBOSS PROGRAM MANAGEMENT AND ACQUISITION SUPPORT

(TEAM GBOSS)

TASK ORDER 0003 EXHIBIT C

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) Ground Based Operational Surveillance System (G-BOSS) Team in the following competencies; Program Management, Administration, Financial Management, Logistics, and Engineering. Successful Performance of this task order will require interfacing with a multitude of personnel from multiple government and Contractor agencies, such as but not limited to: Naval Surface Warfare Center, Crane, IN; Naval Surface Warfare Center, Dahlgren, VA; Marine Corps Combat Development Center (MCCDC); Headquarters Marine Corps, operational U.S. Marine Corps units; U.S. Army Terrestrial Sensors Program Office; Science Applications International Corporation; et cetera.

1.1. Background

Within the G-BOSS team, there is currently one Integrated Product Teams (IPT), which manages the Heavy, Medium and Light G-BOSS variants. Activities conducted by the G-BOSS team include the research and development, test and evaluation, procurement, fielding, and sustainment of USMC G-BOSS employed by the Marine Corps. This effort will be supported by multiple appropriations and budget lines.

The G-BOSS Team is dedicated to delivering integrated and interoperable force protection capabilities to the Marine operating forces in order to accomplish their war-fighting mission. G-BOSS is committed to developing modular and scalable force protection system capabilities, which provide our operating forces with a smaller, more adaptable footprint, capable of responding to any crisis environment. G-BOSS is also responsible for providing materiel solutions for urgent war fighting requirements. Additionally, the G-BOSS MCSC team is a key stakeholder and participant in the Joint development, procurement, and fielding of future G-BOSS variants. The team implements innovative acquisition solutions and maximizes knowledge, technology, and the industrial base by collaborating with 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 G-BOSS Team organizational chart and program schedule are provided as enclosures to assist the Contractors in the delineation of tasks. The G-BOSS program is an Acquisition Category IV-Monitor (ACAT-IV) Marine Corps program that is currently in the Operations and Support phase. Upcoming major program milestones for the next five years include a system fielding to garrison Marine Corps units during FY17 and a significant research, development, test, and evaluation effort during FY18-19 to support a technical refresh of system components during FY18-20. This technical refresh effort may require significant coordination with the U.S. Army Terrestrial Sensors Program Office.

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 (B007). Details of the Offeror’s transition plan should include a schedule of events regarding staffing, 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 G-BOSS Organizational/Program structure is provided as Enclosures, and shall be considered to adequately address this Task Order PWS.

3.1. GBOSS Program Management and General Support This effort will support the current GBOSS Portfolio of systems within their current and future acquisition phases. For purposes of estimating the support requirements, the vendor shall be required to review all required acquisition documentation for at least one ACAT-IV (M) program in accordance with the DoD 5000 series publications and Attachment 1, each quarter. Additionally, the Contractor will be required to support at a minimum of one major fielding decision per year and at a minimum of one Milestone Acquisition Decision per year.

3.1.1. The Contractor shall organize (B001), attend meetings and IPT discussions as required, at least 10 meetings or IPTs per month. No local travel costs will be reimbursed. The venue for the meetings shall be provided by the Contractor in the event government-provided office space is not available.

3.1.2. The Contractor shall provide meeting space in the proximity of Stafford, VA for at least 2 meetings or IPTs per month. No local travel costs will be reimbursed.

3.1.3. The Contractor shall write and submit meeting minutes (B002) and agendas (B003) for all meetings in support of GBOSS.

3.1.4. The Contractor shall update and maintain the PM Fact Book with the GBOSS portfolio of systems.

3.1.5. The Contractor shall update and maintain the contents of the GBOSS portfolio of systems Marine Corps Enterprise Information Technology Systems (MCEITS) SharePoint sites for each program and competency area.

3.1.6. The Contractor shall update and maintain the GBOSS portfolio of systems in TOPIC sites.

3.1.7. The Contractor shall develop and maintain Program Management Review, Interim Progress Review, and Decision Review briefs.

3.1.8. The Contractor shall prepare acquisition decision briefs and presentation material.

3.1.9. The Contractor shall receive, distribute, compile, review, and submit all tasks sent to the GBOSS team via the Department of the Navy Tasking, Records, and Consolidated Knowledge Enterprise Repository (DON TRACKER) system.

3.1.10. The Contractor shall write, submit, draft, collect and track responses and update the GBOSS portfolio of systems Risk Management Plans.

3.1.11. The Contractor shall assist in the identification and tracking of GBOSS program risks.

3.1.12. The Contractor shall participate in Risk Management Working Groups and Review Boards.

3.1.13. The Contractor shall develop, review and update the GBOSS 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.14. The Contractor shall write and submit a monthly status report (B004).

3.1.15. The Contractor shall write and submit conference or meeting agendas (B003).

3.1.16. The Contractor shall update, review, and manage the Government data repository for program documentation, briefs, and presentations.

3.1.17. The Contractor shall write and submit trip reports.

3.1.18. 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.19. The Contractor shall apply a comprehensive and meticulous review of any acquisition documentation identified in, but not limited to, Attachment 1.

3.1.20. The Contractor shall provide administrative and technical review of final draft versions of documentation listed in, but not limited to, Attachment 1 (B005).

3.1.21. The Contractor shall provide an individual to assist in the development and maintenance of the Integrated Master Schedule (IMS) and Integrated Master Plan for each program and competency within the GBOSS portfolio of systems, using the current MCSC approved version of Microsoft Project. At a minimum, the GBOSS IMS will be required to be updated weekly (B006).

3.1.22. The Contractor shall review and comment on the engineering documentation in support of the acquisition milestone cycle for both systems and software.

3.1.23. The Contractor shall update and maintain a schedule, which identifies all development and support tasks, System Engineering (SE) Technical reviews, Milestone Assessment Team (MAT) events, Independent Logistics Assessments (ILAs) events, Technical Readiness Assessments (TRA) events, and Operational Test Readiness Review (OTRR) events. These items shall be incorporated into the GBOSS IMS.

3.1.24. The Contractor shall develop a Program Management correspondence tracking system in SharePoint.

3.1.25. The Contractor shall develop, monitor, track, and update the GBOSS Work Breakdown Structure (WBS).

3.1.26. The Contractor shall develop a Program Management correspondence tracking system in SharePoint.

Deliverables 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 (IMS)

3.2. GBOSS 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 GBOSS Team:

3.2.1. The Contractor shall maintain engineering knowledge and assist in the development of documentation that supports the GBOSS Systems Engineering Technical Process and Systems Engineering Technical Management Process IAW DoD 5000-series Acquisition polices, Department of the Navy systems engineering policies, and other applicable MARCORSYSCOM guidance. Documentation includes, but is not limited to Systems Engineering Plans; Program Environmental, Safety and Health Evaluations; Safety documentation; Test and Evaluation Strategies; Requirement Traceability Matrixes; Cybersecurity Assurance Strategies; Information Support Plans, and Architecture Views.

3.2.2. 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 acquisition guidance, the Contractor shall assist the appropriate competency in the drafting of Statutory and regulatory acquisition documentation listed in, but not limited to, Attachment 1.

3.2.3. The Contractor shall review and comment on Engineering Change Proposals requests for configuration and provide technical data management support.

3.2.4. The Contractor shall participate and assist in the development of documents necessary for System Engineering working groups and IPTs.

3.2.5. The Contractor shall provide Systems Engineering input to the program’s IMS.

3.2.6. The Contractor shall provide technical advice concerning overall T&E activities and test programs.

3.2.7. The Contractor shall assist in the development of GBOSS Test & Evaluation (T&E) documentation in accordance with the U.S. Marine Corps Integrated T&E Handbook and Program Manager (PM) T&E policy and Standard Operating Procedures (SOPs).

3.2.8. The Contractor shall support the T&E Working-level Integrated Product Team (WIPT) by collaborating with stakeholders to define, develop, and maintain the test strategy, plans, and schedule.

3.2.9. The Contractor shall document all system requirements verification and test results in the Requirements Traceability Matrix (RTM).

3.2.10. The Contractor shall provide RTM input following test report completion for each test event.

3.2.11. The Contractor shall support all Test Coordination and Test Readiness Review (TRR) meetings and activities.

3.2.12. The Contractor shall perform post-test data reduction and analysis.

3.2.13. The Contractor shall assist the GBOSS team in ensuring all applicable T&E guidance is incorporated into GBOSS T&E activities.

3.2.14. The Contractor shall review and comment on all test plans, procedures, and test reports including attending adjudication sessions ensuring final product adequacy.

3.2.15. The Contractor shall develop and monitor the programs’ Environmental, Safety, and Occupational Health (ESOH) process.

3.2.16. The Contractor shall collect and file all required safety documentation in safety binders for all the GBOSS 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.3. GBOSS Financial Management.

3.3.1. The Contractor shall assist in the drafting and reviewing of financial specific documentation and briefs in support of the GBOSS Financial Management and Program Management competencies. The scope of this task includes, but is not limited to Funding Action Requests, Tri Annual Reviews, Staffer Briefs, Budget Execution Leadership Team (BELT) Briefs, Service Requirements Review Board Database Request, Command Planning and Resource Allocations, inserting data into the Acquisition Financial Information Database (A-FID) Microsoft Access based system, and Procurement Request Builder documents. Additionally, the Contractor will assist in the tracking of the expenditures, obligations, and awards of funds, across the GBOSS portfolio.

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 portfolio, requiring familiarization with the DoD and MCSC financial databases, processes, and systems.

3.4. GBOSS Logistics 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 GBOSS Team Logistician:

3.4.1. The Contractor shall communicate logistics requirements to the GBOSS team and support both internal and external program meetings.

3.4.2. The Contractor shall maintain and share knowledge of Acquisition Logistics in support of various ACAT programs and information needed to support Independent Logistics Assessments and Milestone Decisions.

3.4.3. The Contractor shall 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. The Contractor shall 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 GBOSS variants.

3.4.5. The Contractor shall develop Diminishing Manufacturing Sources and Material Shortages (DMSMS) Plans and perform DMSMS analysis for all GBOSS 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 GBOSS systems.

3.4.6. The Contractor shall provide required information for Logistics Requirements and Funding Summary (LRFS) to support the GBOSS inputs to the DoD financial management process.

3.4.7. The Contractor shall develop accurate and complete intent to field messages, material fielding announcements, and other Naval Messages related to logistics.

3.4.8. The Contractor shall develop required documentation for the Depot Source of Repair (DSOR) process to support DSOR requests to HQMC.

3.4.9. The Contractor shall request s Table of Authorized Materiel Control Number (TAMCN) and Item Designator (ID) using appropriate forms for new and existing GBOSS variants.

3.4.10. The Contractor shall maintain and share knowledge of the 12 Elements of Logistics and apply them in the acquisition process to support new and existing GBOSS variants.

3.4.11. The Contractor shall maintain and share, with the GBOSS Team, comprehension of Provisioning, Logistics Management Information (LMI) data and Source, Maintenance & Recoverability (SM&R) code processes required to support new and existing GBOSS variants.

3.4.12. The Contractor shall draft, update and submit Item Unique Identification (IUID) Plans in support of the GBOSS portfolio of systems.

3.4.13. The Contractor shall update and maintain the IUID registry in order assist the Government in validating that IUID information is accurate and complete.

3.4.14. The Contractor shall draft, update, and submit New Equipment Training Packages, to include New Equipment Training Plans, Lesson Plans, Instructor Guides, and Student Outlines. 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 GBOSS systems.

3.4.15. The Contractor shall remain knowledgeable of sustainment activities and their, integration with each Competencies (Program Management, Systems Engineering, Finance, Contracting, Test and Evaluation, Requirements Management, etc.) to support new and existing GBOSS variants.

3.4.16. The Contractor shall have knowledge 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 GBOSS variants.

3.4.17. The Contractor shall support the GBOSS Team Logistician in drafting, reviewing, and updating new and existing acquisition Logistics documentation listed in, but not limited to, Attachment 1.

3.4.18. The Contractor shall assist the Government in conducting Levels of Repair Analysis (LORA) in order to determine the most cost effective levels of repairing GBOSS equipment.

3.4.19. The Contractor shall 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.20. The Contractor shall attend logistics meetings during the development of Product Support Strategies and shall develop, update, and maintain Life Cycle Sustainment Plans in support of GBOSS programs.

3.4.21. The Contractor shall 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.22. The Contractor shall develop, update and maintain Component Lists (SL-3) for GBOSS systems. The Contractor shall notify the Government when SL-3s are posted to the USMC Technical Publications website.

3.4.23. The Contractor shall develop, maintain, and review Operator and Maintenance Technical Manuals in support of GBOSS systems. Technical Manuals will be reviewed every other year (minimum) in order to ensure that they are current and shall updated as required by the Government

3.4.24. The Contractor shall review and monitor the program Failure Reporting, Analysis, and Corrective Action System (FRACAS). Additionally, the Contractor will analyze and provide FRACAS data in the form of a FRACAS Report.

3.4.25. Draft Corrosion Control and Implementation Plans.

3.4.26. Conduct Job and Task Analyses (JTA).

3.4.27. Collect data for the Maintenance Task Analyses (MTA).

3.4.28. Assist the GBOSS Team Logistician by tracking total asset visibility and accountability.

3.4.29. 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.30. Provide a dedicated equipment specialist in Albany, GA to support the GBOSS program capable of completing the following tasks:

3.4.30.1. Collecting, analyzing, interpreting, and developing specialized information for GBOSS programs for use on life cycle management decisions.

3.4.30.2. Analyzing, reviewing, and submitting Provisioning Technical Data (PTD) utilizing the LSA 036 format and Marine Interactive Computer Aided Provisioning System (MICAPS).

3.4.30.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.30.4. Formatting and developing Technical Instructions and Validating and Verifying installation procedures.

3.4.30.5. Maintain thorough understanding of the Albany Publication website and the Total Force Structure Management System (TFSMS) to support new and existing GBOSS.

3.5 GBOSS Configuration Management. 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 GBOSS team:

3.5.1 The Contractor shall 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 GBOSS 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 regarding acquisition of design documentation in order to provide technical editing to the design documentation handbook and training package for use by program management teams, 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. GBOSS Program MEF Support. Not applicable, at this time.

3.7. GBOSS Training Support. Not applicable, at this time.

3.8. GBOSS Test and Evaluation (T&E) Support. Not applicable, at this time.

3.9. GBOSS Warehouse Storage and Support. Not applicable, at this time.

3.10. GBOSS Cybersecurity Support. Not applicable, at this time.

3.11. GBOSS Field Service Representative 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 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 .

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 GBOSS Contractor support team is as follows:

NSWC Crane, Indiana

I MEF, Camp Pendleton, CA

II MEF, Camp Lejeune, NC

III MEF, Camp Hansen, Okinawa, Japan

Albany, GA

Quantico, VA

5. Security.

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)

7. Enclosures.

Attachment 1: ACAT_III_IV_AAP_Document_Listing.xlsx Exhibit : CDRL (s) 1423 Enclosure A: GBOSS Organizational Chart Enclosure B: GBOSS Program Schedule

Enclosure A GBOSS Organizational Chart

Enclosure B GBOSS Program Schedule

GBOSS Program Analyst

GBOSS Test and Evaluation Engineer

GBOSS Financial Management Specialist

GBOSS Systems Engineer

GBOSS Logistician image1.emf