M95494-19-Q-0005_-_Amendment_0002.docx

M9549419Q0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

PWS

PERFORMANCE WORK STATEMENT (PWS)

PROGRAMS AND RESOURCES DATA PLATFORM & ANALYSES

TABLE OF CONTENTS

1. BACKGROUND

The Deputy Commandant for Programs and Resources (DC P&R), as part of a broader strategy, requires advanced data and analytics capabilities to address key questions related to Planning, Programming, Budget and Execution (PPBE). DC P&R specifically requires (1) a proven strategic intelligence analytics platform that the Contractor will use to (2) aggregate, rationalize, analyze, and visualize Department of Defense (DoD), Marine Corps and publicly available data and information to provide decision support to senior leaders, and (3) a framework that includes training and education to replicate advanced analytic methods in order to assist the Marine Corps in developing a repeatable process (i.e., an organic Government capability built from training and education and integrated work between Government and vendor).

2. SCOPE

The Contractor shall conduct a series of analytic projects as outlined in Section 6. The goal of each project is to explore, rationalize, analyze, and visualize data, using data science and other advanced analytic techniques to understand resource execution and inform decision making across a number of domains. For all projects, the Contractor shall conduct a people, process, and technology assessment based on a framework that will be provided by the Government. The Marine Corps is currently developing this framework as part of the Data Cross-Functional Team efforts under the Deputy Commandant for Information. Delivery of the fully defined framework is anticipated in the April timeframe. A basic description of what the assessment will entail is included in Section 6.3.

3. OBJECTIVES

0. Employ a proven strategic intelligence analytics platform to aggregate, rationalize, analyze, and visualize DoD, Marine Corps and publicly available data and information.

0. Analyze DoD, Marine Corps and publicly available data and information employing advanced analytic ("Big Data") techniques for data storage, data processing (to include data cleansing), data mining, Machine Learning, rationalization, and visualization.

0. Employ a government-directed framework to analyze the data and information necessary to complete the analytic projects outlined in Section 6, as impacted by people, process, and technology.

0. Establish a framework for an organic Marine Corps capability:

0. Develop a framework for training and education to institutionalize advanced analytic methods and strategic intelligence platform use.

0. Employ a Contractor / Government teaming approach to ensure integrated process, efforts, and products that result in a documented framework.

0. Produce insights and recommended changes in support of PPBE process reform (improvements).

0. Define and document business rules used to store, process, mine, rationalize, visualize, and analyze all data and information for each project outlined in Section 6.

4. MANAGEMENT AND SECURITY OF UNCLASSIFIED ITEMS, SYSTEMS, INFORMATION, AND DATA

0. Security

0. Organization:

0. Security Classification: All work performed under this task order is "unclassified." A facility security clearance (FCL) is not required; therefore, DoD Contract Security Classification Specification, DD Form 254, does not exist. Pursuant to DoDM 5200.01 - Volume 4, Controlled Unclassified Information (CUI), the contractor shall safeguard any sensitive Government information.

0. Personnel:

1. Background Investigation: Prior to beginning performance on the contract, the contractor shall ensure their personnel (including administrative and subcontractor personnel) have obtained and can maintain favorable background investigations at the appropriate level(s) for access level required by this contract. Investigations are not necessarily required for personnel performing unclassified work who do not require access to Government installations/facilities and/or Government IT systems/IT resources.

1. PII/HIPPA Data: Contractor personnel will not be authorized to access classified information; however, may occasionally need to have knowledge of information that is confidential or sensitive in nature (i.e. PII/HIPAA). The contractor shall ensure all personnel are aware of their responsibility to safeguard privileged information.

1. Visitor Requests: All contractor personnel working on this PWS who need to access government spaces will require a visitor request submitted by the contract company via Joint Personnel Adjudication System (JPAS). If contractor personnel are not in JPAS, a Visitor Authorization Letter (VAL) on company letterhead must be submitted with the following information: company name, address, telephone number, assigned Commercial and Government Entity (CAGE) Code, contractor personnel(s) full name, full social security number (SSN), date of birth (DOB), place of birth (POB), citizenship status, contract number, and visit dates for the length of the contract.

1. Compliance: Contractor personnel must meet specific requirements in order to be granted these privileges and maintain these credentials. Compliance with all USMC communications regulations pertaining to network activities is mandatory. Failure to comply with security requirements will result in revocation of access privileges and personnel removal from work under this contract. FIPS PUB 201 is available at:

http://csrc.nist.gov/publications/fips/fips201-1/FIPS-201-1-chng1.pdf. The Office of Management and Budget (OMB) associated guidance, M-05-24 can be found at:

http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-24.pdf "

4.1.3 Mandatory Training: Specific contractor personnel (including subcontractors) shall complete mandatory training based on the access required and work site location. The contractor shall report individual personnel training status to the COR.

0. Without the prior written permission of the Contracting Officer, no items, created or provided expressly for this contract shall be used by the Contractor for any purpose other than those purposes that are in support of, or for performance under, this contract. The Contractor and its employees and subcontractors are obligated to protect from unauthorized use or disclosure all Government confidential or classified material and/or Government-owned proprietary and/or Personally Identifiable Information or Personal Privacy, items obtained in the course of performance under this contract, as long as such items remain proprietary, confidential, sensitive, or classified. Any information obtained in the course of duties, or the performance of services, under this contract including, but not limited to, information that may be made available for use that relates to the technical data, trade secrets, processes, operations, style of work, or apparatus, or to the technical data, statistical data, amount or source of any income, profits, losses, or expenditures of any person, firm, partnership, corporation, or association is included in this clause. Contract personnel shall not publish, divulge, disclose, or make known this information (hereinafter, singularly or collectively, included in “Items”) or any other Items created or provided expressly for this contract, in any manner, or to any extent not previously authorized in writing by the Contracting Officer or the COR. Moreover, when the Contractor’s need for any such Items ends as part of performance of duties under this contract, the Contractor shall promptly (within ten (10) business days) turn over and properly dispose of all Contractor-developed databases, analyses, studies, applications, information, data, and other items, and all associated intellectual property, completed or in progress, to the Government, if not already delivered, in accordance with Record’s Management Policies SECNAV M-5210.1 and SECNAV NOTICE 5210.

0. In the course of performance pursuant to this contract, the Contractor may access nonpublic data and information, including PPBE, proprietary, business sensitive, personally identifiable information (PII), and other pre-decisional data and information. In that event, the Contractor shall agree that it will not use or disclose any such data or information unless authorized by the Contracting Officer’s Representative (COR). The Contractor shall further agree that it will use its best efforts to ensure that its employees and others performing services under this contract will not use or disclose any such data or information unless authorized by the COR. The Contractor shall protect data and information in accordance with the Privacy Act of 1974 (5 U.S.C. 552a) and the Freedom of Information Act (5 U.S.C. 552, as amended). To that end, the Contractor shall agree that each of its employees and others performing duties under this contract will sign the NDA (Attachment B) for the contract award.

0. Data, Software and Intellectual Property Rights: All Items generated by the Contractor, including, but not limited to, research, reports, materials, briefs, presentations, processed information, processed data, model and simulation documentation, visualizations, diagrams, and general or analytical reports, created, generated, or produced under this requirement shall become the property of the U.S. Government/Marine Corps and not the Contractor, subcontractor, or individual author or researcher; therefore, the U.S. Government/Marine Corps shall have the irrevocable, royalty-free, worldwide right to use, modify, reproduce, perform, display, release, or disclose such Items, in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so. The contract will include DFARS 252.227-7015 Technical Data – Commercial Items.

0. The Marine Corps shall have unrestricted access and use of all work products and Deliverables upon delivery. The Contractor shall provide all deliverables in a version, format, and media used/useable and modifiable by the Marine Corps. Therefore, unless otherwise directed by the COR, the deliverable Items identified in this PWS shall be delivered in a media and an electronic format compatible with resources currently being used by the Marine Corps. Moreover, test and demonstration may be required as an additional task for models.

5. QUALIFICATIONS

For all qualifications, the Contractor shall possess significant experience conducting similar efforts, preferably within the Department of Defense (DoD).

0. The Contractor shall possess:

0. A proven platform – the ability to aggregate, rationalize, analyze, and visualize DoD, Marine Corps and publicly available data and information on a proven strategic intelligence analytics platform.

0. Advanced analytic capabilities – utilizing a proven strategic intelligence / data analytics platform (proven capability / turn-key) that leverages modern software for "Big Data" / large-scale data storage, data processing, data mining, Machine Learning techniques, rationalization, and visualization.

0. Training and education – the ability to provide a framework through training and education to replicate their analytic methods in order to create a Marine Corps organic capability.

0. The Contractor shall be able to process large-scale, structured and unstructured data and assess data quality. The Contractor shall possess experience employing Business Process Model Narratives/Notation (BPMN) to describe and understand business processes and associated information and data flows supporting assessment of data provenance, pedigree, and auditability.

0. Contractor must possess the ability to interact, provide advice, and coordinate with Marine Corps senior leadership and senior management at the various Marine Corps and other Service staff agencies.

0. Contractor must possess excellent analytic, project management, and strategic assessment skills.

0. Contractor must be proficient in multiple structured database management systems to include hierarchical, network, relational, and object-oriented.

0. Contractor must be proficient across multiple structured database management system types/vendors such as ORACLE, IBM, My Structured Query Language (MySQL), PostgreSQL, and SQLite.

0. Contractor must be proficient in applying a variety of modeling approaches to include: quantitative, qualitative, architectural, linear, non-linear, inductive reasoning, deterministic, stochastic, analogs, statistical, and network modeling.

0. Contractor must be proficient in data mining and data analysis techniques.

0. Contractor must be proficient in exploratory data analytics and artificial intelligence such as data wrangling/data munging, data mining, text analytics, machine learning, and graph analytics.

0. Knowledge is preferred in acquisition and non-acquisition program analysis (i.e., across appropriations such as procurement; research, development, test, and evaluation (RDT&E); operations and maintenance (O&M); manpower (military and civilian); and infrastructure).

0. Knowledge is preferred in programs covering manpower provision via appropriated funds and non-appropriated funds (military and civilian); full life cycle of military, civilian, and contractor personnel and programmatic implications; structure and processes; manpower models; challenges and strategies.

0. Familiarity with Technical Writing/Editing.

0. Knowledge of Data Science and data analysis software to include open source and vendor-supplied platforms (e.g., Anaconda, IBM Blue, Oracle Big Data).

0. Ability to securely handle PII.

6. PROJECT AREAS

0. The below tasks will be completed in the order they are listed while supporting parallel analytics when possible. The Contractor will provide primary analytic results in two forms: 1) briefs supported by visualizations and written reports; 2) related deliverables in electronic form and in a file format that can be read and managed by the Government to include:

0. Processed data and processed information,

0. Documented data model / schema and business rules used to store, process, mine, rationalize, visualize, and analyze all data and information,

0. Modeling and simulation documentation.

0. Results from all projects should:

0. Provide categorization of data with respect to Program Objective Memorandum (POM) and budget priorities, acquisition programs (where applicable) and capability portfolios.

0. Provide additional options for categorization of data to inform analytic methodologies and future data architecture and schemas.

0. The Contractor will provide an assessment, based on a government directed framework, which considers the actions necessary to obtain the data and information and the complete analyses as impacted by people, process, and technology for each of the five major analyses (Projects 1-5). This will be provided No Later Than (NLT) 10 months from the contract award date. Specifically, an assessment under the government-directed framework will include a Data Management Body of Knowledge (DMBOK)-framed look at how the following “As-Is” capabilities enable or inhibit the completion of Projects 1-5:

(a) Origination and Process and Provision

0. Data Infrastructure – Networks, hardware, storage, and security

0. Data Systems – System operations in support of line of business processes

0. Data Entry – Methods for data entry at headquarters and operating forces levels

0. Data Services – Provision of the data to users / customers and linkage to enterprise services

0. Data Owner – Functional Area Manager (FAM) / data manager

(b) Exploitation and Analysis

0. Data Subject Matter Experts (SMEs) – Resident knowledge on content in context

0. Data Scientists – Data wrangling, data mining, analysis

0. Data Analysts – Ability to connect data analytics to key questions

0. Data Visualization / Reporting – Business intelligence and internal / external reporting

0. Data-driven Decision-maker – Ultimate data customer at higher levels of management

0. Data Staging (Pre-Staging)

0. Pre-staging means that the Government has identified the required data (as anticipated), requested and obtained the data from the data / system owner, pre-processed the data to check for completeness and provenance / pedigree.

0. For Project 1, the data will be pre-staged by the Government to include Program Budget Information System (PBIS), and Standard Accounting, Budgeting, and Reporting System (SABRS).

0. For Projects 2-5, outside of PBIS and SABRS data, the data will NOT be pre-staged.

0. Projects: The five (5) projects are listed below. Projects 4 and 5 are Optional (Optional CLINs 0004 and 0005) and the Government reserves the right to exercise these projects depending on funding availability at award or throughout the POP.

Project 1: Track year of execution funds re-alignment for Operations and Maintenance (O&M) spend over past five (5) years. Project 1 will be completed NLT 3 months from the contract performance start date.

0. Identify, using detailed transactional data, how funds are moved within and even across all Line Items (e.g., 1A1A, 1A2A, etc.) during the year of execution so as to reveal decisions made in execution at the program level and below.

0. Include a focus on contract services:

1. Provide an assessment of contract service capabilities (leading to an estimate of dependencies and requirements) based on contract data from five prior fiscal years and currently awarded contracts. Provide the type of contract and funding used, including timeline for award where available.

1. Analyze contract spending and determine categorization framework(s) to inform strategic sourcing and category management of contracts.

1. Align and compare open-source contract spending data (USASpending.gov and Federal Procurement Data System (FPDS)) with authoritative accounting system data (O&M spending) in the Standard Accounting Budget Reporting System (SABRS).

1. Provide in-depth, text-based analysis of contract documents to determine other key data, not captured in standard data sources (e.g., FPDS and SABRS), that informs contract management.

1. Provide options to include data model / schema for categorizing the types of contract efforts ongoing and recommended prioritization of information and data collection for further analyses.

Project 2: Tracking and categorization of Information Technology (IT) spending for the past five (5) fiscal years. Project 2 will be completed NLT 4 months from the contract performance start date.

0. Identify, using detailed transactional data, how funding is spent on IT. Categorize spending based on data exploration without relying on constraints imposed by existing fiscal code constructs.

0. Compare and contrast the initial data exploration results with other models of IT spend / cost to include:

1. DoD’s Cost Decision (CODE) Framework

1. Technology Business Management (TBM) Model

1. Selective and Native Programming – IT (SNaP-IT)

0. Determine IT spend best estimate based on all referenced models / frameworks.

0. Assess which model (existing or new) optimizes capture of IT spending with respect to existing and potential programming constructs.

Project 3: Total workforce mix (Military / Civilian / Contractor) strategic workforce planning. Project 3 will be completed NLT 6 months from the contract performance start date.

0. Use modern data analytic techniques to combine structured and unstructured / text-based data to provide a unified picture of our Civilian and Contractor workforce. Data on Civilians is spread in non-authoritative fashion across multiple systems, and data on the Contractor workforce is often unavailable except as an estimate.

0. Analyze the alignment between documented requirements, position descriptions, and actual skillsets to determine how closely the workforce skills match the needs.

0. Assess how the Contractor workforce is supplementing both the Military and Civilian workforce, and where this indicates significant gaps in organic capabilities.

0. Associate O&M spending on Civilians by organization, Line Item, and program so as to better understand which programs are most impacted by Manage to Payroll (M-t-P) policies. This will likely require combining analysis of Civilian pay data with accounting data.

Project 4: Identification of Intermediate and Organizational (I/O) Consumable and Retail Secondary Repairables (SECREPs) Parts Funding Resource Requirements. Project 4 will be completed NLT 8 months from the contract performance start date.

0. Identify the I/O baseline funding required for the Marine Expeditionary Forces (MEFs) in order to inform full-funding requirements development as part of the Program Objective Memorandum (POM) process to include cost of I/O repair, exchange, and purchase. Include at a minimum the following: Calculate historical values and identify cost drivers for all echelons of maintenance below the Depot to include Supply Management Unit (SMU), Repairable Issue Point (RIP), Intermediate Maintenance Activity (IMA), and unit level.

0. Estimate Intermediate / Organizational (I/O) maintenance costs across the Future Years Defense Program (FYDP) and provide cost estimates for each end item along with impacts from non-Marine Corps suppliers such as the 4th Estate (Defense Logistics Agency (DLA)), and the Industrial Base (private industry): Estimate Future Demands at the SMU, RIP, IMA, and unit level:

1. Estimate demand for consumables and SECREPs across the FYDP.

1. Document the historical relationships between the Marine Corps, DLA, and private suppliers as they impact the resourcing requirements.

Project 5: Ammunition based on 2017 Front End Assessment (FEA) results and Audit findings. Project 5 will be completed NLT 9 months from the contract performance start date.

0. Identify and analyze structured and unstructured data / information inputs that inform training ammunition requirements and feed associated models/tools that produce ammunition resourcing and readiness levels. Specifically analyze the following:

0. Historic expenditures based on combat, testing, training events and cross-leveling due to Joint policy-driven asset stratification and Required Related Munitions Stock (RRMS).

0. Determine current and historical requirements and requirements drivers based on Training and Readiness (T&R) manual(s) and historical expenditures.

0. Explore alternate, data-driven methods to determine current and historical requirements and requirements drivers.

0. Identify ammunition inventory to include War Reserve Materiel Requirements (WRMR), pre-positioned stocks and other-Service held inventory.

7. DELIVERABLES

0. Project Kick-Off Meeting – the Contractor will coordinate with the COR to schedule an onsite Kick-off meeting no later than (NLT) one (1) week after contract award. The kick-off meeting will provide an overview of the project to Marine Corps personnel and other key staff identified by the COR. The kick-off meeting will also initiate a two-day needs assessment including requirements collection where the contractor will interview key staff identified by the COR.

0. Program Management Plan (PMP) - the Contractor will prepare a draft PMP for COR review five business days after conclusion of the needs assessment described above. The COR will provide comments, questions, and any recommended format changes to the PMP NLT ten (10) business days after receipt. The Contractor will deliver the final copy to the COR NLT two (2) business days from receipt of COR comments. The PMP will be the guiding document for meeting the requirements of the contract.

0. Monthly Status Report (MSR) – the Contractor shall provide MSRs detailing the following information:

0. Task information such as Contract number and Project number, client agency and location, brief task description.

0. Reporting Period information to include a narrative review of work accomplished during the reporting period and significant events, deliverable process, problem areas, anticipated activity for the next reporting period, description of any travel or unique services provided, and other relative information. These reports are quick and concise overviews of current progress and state of operations which include key tasks ongoing or complete with emphasis areas from the past month. In addition, the MSR will provide a tentative plan for the next month. The MSR is due to the COR NLT 5th business day following the end of the reported month.

0. Access to a proven strategic intelligence platform – the Contractor will use and enable the Marine Corps to use the Contractor’s proven strategic intelligence platform during the contract period to aggregate, rationalize, analyze, and visualize DoD, Marine Corps and publicly available data and information.

0. Analysis – the Contractor will analyze DoD, Marine Corps and publicly available data and information employing advanced analytic ("Big Data") techniques for data storage, data processing (to include data cleansing), data mining, Machine Learning, rationalization, and visualization. The Contractor will provide primary analytic results in two forms: 1) briefs supported by visualizations and written reports; and 2) related deliverables in electronic form and in a file format that can be read and managed by the Government:

0. Processed data and processed information,

0. Documented data model / schema and business rules used to store, process, mine, rationalize, visualize, and analyze all data and information,

0. Modeling and simulation documentation.

0. Project 1 will be completed NLT 3 months from the contract performance start date.

0. Project 2 will be completed NLT 4 months from the contract performance start date.

0. Project 3 will be completed NLT 6 months from the contract performance start date.

0. Project 4 will be completed NLT 8 months from the contract performance start date.

0. Project 5 will be completed NLT 9 months from the contract performance start date.

0. Assessment of People, Process, and Technology Framework – The Contractor will provide an assessment, based on a government directed framework, which considers the actions necessary to obtain the data and information and the complete analyses as impacted by people, process, and technology for each of the five major analyses (Projects 1-5). This will be provided No Later Than (NLT) 10 months from the contract performance start date. Specifically, an assessment under the government-directed framework will include a Data Management Body of Knowledge (DMBOK)-framed look at how the following “As-Is” capabilities enable or inhibit the completion of Projects 1-5:

1. Origination and Process and Provision

0. Data Infrastructure – Networks, hardware, storage, and security

0. Data Systems – System operations in support of line of business processes

0. Data Entry – Methods for data entry at headquarters and operating forces levels

0. Data Services – Provision of the data to users / customers and linkage to enterprise services

0. Data Owner – Functional Area Manager (FAM) / data manager

1. Exploitation and Analysis

0. Data Subject Matter Experts (SMEs) – Resident knowledge on content in context

0. Data Scientists – Data wrangling, data mining, analysis

0. Data Analysts – Ability to connect data analytics to key questions

0. Data Visualization / Reporting – Business intelligence and internal / external reporting

0. Data-driven Decision-maker – Ultimate data customer at higher levels of management

0. A framework for and actions to support an organic Marine Corps capability:

0. Document a framework for training and education to institutionalize advanced analytic methods and strategic intelligence platform use.

0. Employ Contractor / Government teaming approach to ensure integrated process, efforts, and products that result in a documented framework.

0. The documented training and education framework will be completed NLT 12 months from the contract award date.

0. Provide gaps and improvements assessment based on data-driven analysis – the Contractor shall provide insights and recommended changes to support PPBE process reform (improvements). The Contractor shall provide the gaps and improvements assessment in the form of a written report.

8. PLACE / PERIOD OF PERFORMANCE

Place: Performance will primarily take place at the Contractor’s facilities. The Contractor shall host the off-premise platform at their facilities. However, the Contractor shall provide ad hoc on-site support to engage with Government leads, SMEs, and analysts as required to complete any and all tasks. Any ad hoc on-site Contractor support shall abide by standard business hours unless coordinated.

Contract support personnel shall abide by the Office of Personnel Management’s inclement weather and dismissal procedures. Contract Support personnel are required to become familiar with office security procedures at each location.

Period: The anticipated period of performance for this effort with be one (1) year. All projects must be completed within this POP.

9. TRAVEL

0. Contractor personnel may be required to travel in performance of this performance work statement. Travel to other Government facilities or other contractor facilities may be required. All travel shall be approved by the COR prior to execution. Estimated locations include (but are not limited to) Marine Corps Base Quantico, VA; Charleston, SC; and Washington, DC.

0. The number of trips and types of personnel traveling shall be limited to the minimum necessary to accomplish work requirements. The purpose of this travel would be for enhancing strategic communication between stakeholders. Local travel will be required between various locations within the National Capital Region (NCR). Travel shall be coordinated with both the Contractor’s Program Manager and with the COR prior to travel occurring. All travel outside of the NCR shall have requirements (including plans, agenda, itinerary, or dates) pre-approved in writing by the Government. Any travel outside of the NCR under this contract must be specifically requested in writing by the Contractor and approved by the COR, prior to incurring any travel expense.

0. Travel Reimbursement: Travel will be paid on a cost reimbursable basis. The Contractor shall adhere to the following travel regulations (see FAR 31.205-46):

0. Federal Travel Regulations (FTR) – Prescribed by the General Services Administration, for travel in the contiguous United States.

0. Joint Travel Regulations (JTR), Volume 2, DoD Civilian Personnel, Appendix A. Prescribed by the Department of Defense for travel in Alaska, Hawaii, and outlying areas of the United States.

0. Department of State Standardized Regulations (DSSR) (Government Civilians, Foreign Areas), Section 925, "Maximum Travel Per Diem Allowances for Foreign Areas," prescribed by the Department of State for travel in areas not covered in the FTR or JTR.

0. The Contractor will not be reimbursed for travel expenses unless audited records for transportation contain evidence, such as original receipts, substantiating actual expenses incurred for travel.

0. The contract includes a not-to-exceed funding limitation for travel costs. When the Contractor expects total funding expended for reimbursable travel to reach 85 percent of the total funds available on the travel CLIN, the Contractor shall notify the Contracting Officer and the COR and any other Government official identified by the Contracting Officer. The notice shall state the estimated amount of additional funds required to continue performance for the period specified in the task order. The Contractor shall not exceed or incur costs that exceed the amount of funding stated on the reimbursable travel CLIN. The Government is not obligated to reimburse the Contractor for otherwise reimbursable travel in excess of the funded amount stated on the reimbursable travel CLIN.

0. The Contractor is not obligated to continue performance of any reimbursable work under this Contract or otherwise incur costs for reimbursable travel in excess of the funded amount stated on the reimbursable travel CLIN unless the Contracting Officer notifies the Contractor in writing that the funded amount stated under the applicable reimbursable travel CLIN has been increased. In the event notification is made orally, such notification shall be followed up in writing within two working days.

0. No notice, communication, or representation from any person other than the Contracting Officer shall affect the Government’s obligation to reimburse the Contractor.

0. Change orders shall not be considered an authorization to exceed the funded amount stated under the reimbursable travel CLIN unless they contain a statement expressly increasing the funded amount of that reimbursable CLIN by a sufficient amount to cover the change order.

10. EQUIPMENT AVAILABLE FOR CONTRACTOR USE

0. The Government will not provide computers / networks for hosting the contractor’s analytics platform. The Contractor is required to provide their own computers; their own strategic intelligence platform; and their own hosting environment.

0. The contractor shall specifically identify in their proposal the type, amount, and time frames required for any government resources beyond those listed below.

0. The government will provide needed standard operational procedures, regulations, manuals, texts, briefs, data, and other materials associated with the project, and the hardware/software noted throughout this solicitation.

0. The Government will make available, when required, access to secure workstations and telephones, and secure facilities for storage of classified material required or generated by Contractor personnel who have appropriate security clearances.

11. IDENTIFICATION OF CONTRACTOR EMPLOYEE(S)

0. ID Badges. Contractor personnel will be issued badges for building access and DoD access. Badges will be turned in at the end of the contract or upon separation of the employee from DoD. The Government will issue a Common Access Card (CAC) and other forms of DoD identification necessary to access DoD and other Government facilities.

0. Display of ID Badges. Contractor personnel shall wear these ID badges and ensure they are visibly displayed at all times when performing work under this contract to include attending Government meetings and conferences. Unless otherwise specified in the contract, each Contractor employee shall wear the ID badge in a conspicuous place on the front of exterior clothing and above the waist except when safety or health reasons prohibit such placement.

0. Answering Telephones. Contractor personnel shall identify themselves as Contractor employees when answering Government telephones.

0. Utilizing Electronic Mail. When prime Contractor or sub-contractor personnel send e-mail messages as a part of contract performance (or otherwise relating to contract matters), each sender shall include his/her name (both first and last names), e-mail address and the name of the individual’s company as part of his or her signature block. Under no circumstances will a contractor exercise any inherently government functions, to include adopting job titles that denote the authority to perform governmental functions or use of business cards with the same or similar information.

12. USES AND SAFEGUARDING OF INFORMATION

Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public.

13. ENTERPRISE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA)

The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this CLHDW Support Contract via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) S, Utilities ONLY;

(5) V, Freight and Shipping ONLY.

The Contractor is required to completely fill in all required data fields using the following web address: https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.

13. ORGANIZATIONAL CONFLICT OF INTEREST

In accordance with FAR 2.101(b), if the Contractor (and any subcontractors, consultants, or teaming partners) has or is currently providing support or anticipates providing support to any organization listed in scope of this contract that creates or represents an actual or potential organizational conflict of interest (OCI), the Contractor shall immediately disclose this actual or potential OCI in accordance with FAR Subpart 9.5. The Contractor is also required to complete and sign an Organizational Conflict of Interest Statement in which the Contractor (and any subcontractors, consultants, or teaming partners) agrees to disclose information concerning the actual or potential conflict with any proposal for any solicitation relating to any work in the contract. All actual or potential OCI situations shall be identified and addressed in accordance with FAR Subpart 9.5.

Attachment A: Removed Attachment B: Non-Disclosure Agreement (NDA) Attachment C: Past Performance Questionnaire

52.212-1 ADDENDUM

FAR 52.212-1 ADDENDUM

1. This is a FAR Part 12 procurement that uses FAR Part 13 Simplified Acquisition Procedures conducted under the FAR Subpart 13.5 Simplified Procedures for Certain Commercial Items (under $7.5M).

2. After receipt of quotes, the Government may, with or without notice, negotiate with and, if desired, seek quote revisions from as many or as few Quoters as it, in its discretion, deems appropriate. The Government will consider all quotes that are timely received and may consider late quotes. Failure of a quote to address any items listed in the attached submission package may make it unacceptable.

3. Quotes shall be submitted electronically using Microsoft Word / Excel / Adobe format to Cyndi Guthridge (cynthia.guthridge@usmc.mil). Quoters are advised that the Government may be unable to receive other types of electronic files (e.g., .zip files) or files in excess of eight (8) megabytes. Multiple emails should be numbered (e.g., Email 1 of 3) and attachments should be listed within the body of each email. It is the Quoter’s responsibility to ensure that Quotes are received by the due date and time listed on the SF1449 cover page.

4. Only the quote submitted in response to this solicitation will be evaluated, Quoters should make certain that their Quote is complete with regard to the information provided. Data previously submitted, or presumed to be known, e.g., previous projects performed for the Government, will not be considered in the evaluation unless that information is physically contained in the quote.

5. Quotes shall be submitted in three (3) separate files:

Volume (1): Price / Solicitation Documents Volume (2): Technical* Volume (3): Past Performance

*Volume (2) shall not contain any pricing information

6. Format Requirements

· 8.5 x 11 inch paper

· Single-spaced typed lines

· 1 inch margins on all sides

· No smaller than 12 point font, Times New Roman

· Graphs and drawings must be clear and legible

· No photographs or hyperlinks are permitted

· Microsoft Office compatible files are required

· Adobe files are acceptable

· Volume (2) shall not exceed 15 pages in length

· Volume (3) shall not exceed 4 pages in length (excluding Attachment (c))

· No page limit on Volume (1)

Each volume of the quote shall be clearly marked as to the volume number, the solicitation number, and the Contractor’s name. Pages shall be numbered consecutively within each volume showing volume and page. For example, page 9 of Volume I would be numbered I-9 and page 10 of Volume II would be numbered II-10.Quoters are advised that the Government may selectively verify any information provided in the quote.

SUBMISSION PACKAGE

The quote must demonstrate an understanding of and ability to meet all of the requirements set forth in the RFQ’s performance work statement (PWS). The Quoter shall provide sufficient detail to substantiate the validity of all statements. The Quoter shall demonstrate that the quote is in compliance with the requirements, terms, and conditions of the RFQ. Comprehensive responses to the requirements of the RFQ are required to enable the Government to evaluate the Quoter's understanding of and capability to accomplish the requirements of the PWS. Quotes shall contain the following:

Volume (1) Price and Solicitation Documents

(a) Price Quote:

0. Provide a firm-fixed-priced quote for all of the work required in the PWS via an Excel spreadsheet. Provide a breakdown of the total pricing to include the proposed labor categories, hours proposed, labor rates, and any other direct costs associated with completing this effort, separated out by project. Provide a breakdown for each deliverables cost under CLIN 0006. This is a firm-fixed-price effort; therefore, all labor rates and pricing totals must be inclusive of all overhead, G&A, profit, etc.

TRAVEL - In accordance with PWS Section 9, travel will be funded by the Government on a reimbursable basis when required. The Government has estimated the travel during each period of performance to be $50,000.00. Quoters shall use the Government estimated travel amount in their price quote.

0. Price quote must be consistent with data contained in the Technical part of the quote and consistent with the filled out CLINs in the solicitation. The price quote must support the level of resources required to complete the requirements of this effort. The Quoter shall provide sufficent price information to allow the Contracting Officer to determine the reasonabless of the proposed price.

(b) CLINs - The Quoter shall fill in the firm-fixed-price for each of the CLINs in the solicitation, which should match pricing included on their price quote. Quoters shall provide Unit Price; Unit of Issue; and Total Price for each CLIN.

(c) Solicitation Documents:

i. Quote Cover Letter. The following information shall be provided in the cover letter:

(1) The RFQ number: M95494-19-Q-0005

(2) Company Information. The name, address, DUNS number, CAGE Code, telephone number and Tax Identification Number (TIN) for the Quoter.

(3) Authorized Personnel. Provide the name, title, telephone number, and e-mail address of the company/division point of contact who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

(4) Terms of any express warranty.

(5) “Remit to” address, if different than mailing address.

(6) Acknowledgment of Solicitation Amendments (if applicable).

(7) Agreement with terms. A statement specifying the extent of agreement with all terms, conditions, and provisions included in the RFQ. Quoters are to clearly detail any exceptions taken and the rationale for the exceptions taken to the RFQ. Please note that exceptions taken to the RFQ may render the quote unacceptable to the Government.

(8) Quote expiration date (if applicable).

ii. Representations and Certifications - Quoter shall complete representations and certifications in their System for Award Management (SAM).

iii. Standard Form (SF) 1449 - Complete Blocks 17a and 30a-c of Page 1 of the Solicitation (signed and dated). Failure to do so may lead to rejection of the offer.

iv. Organizational Conflicts of Interest (OCI) - The Quoter shall disclose any potential or actual organizational conflicts of interest (OCIs) that your firm (to include subcontractors) may have with the requirements of the PWS/solicitation. Include a description of the OCI(s) and the action(s) taken, if any, to avoid, mitigate, or neutralize the OCIs. A negative response is required.

Volume (2) Technical Capabilities

There are three (3) parts to the technical capabilities volume: Scenario 1, Scenario 2, and a general methodology description.

· Scenario 1: This scenario is based on Project 1 from the PWS, which is pasted below for reference.

Project 1: Track year of execution funds re-alignment for Operations and Maintenance (O&M) spend over past five years. Project 1 will be completed NLT 3 months from the contract performance start.

0. Identify, using detailed transactional data, how funds are moved within and even across all Line Items (e.g., 1A1A, 1A2A, etc.) during the year of execution so as to reveal decisions made in execution at the program level and below.

0. Include a focus on contract services:

3. Provide an assessment of contract service capabilities (leading to an estimate of dependencies and requirements) based on contract data from five prior fiscal years and currently awarded contracts. Provide the type of contract and funding used, including timeline for award where available.

3. Analyze contract spending and determine categorization framework(s) to inform strategic sourcing and category management of contracts.

1. Align and compare open-source contract spending data (USASpending.gov and Federal Procurement Data System (FPDS)) with authoritative accounting system data (O&M spending) in the Standard Accounting Budget Reporting System (SABRS).

1. Provide in-depth, text-based analysis of contract documents to determine other key data, not captured in standard data sources (e.g., FPDS and SABRS), that informs contract management.

1. Provide options to include data model / schema for categorizing the types of contract efforts ongoing and recommended prioritization of information and data collection for further analyses.

Assumption: The data for this scenario is pre-staged[footnoteRef:1]. [1: Pre-staging means that the Government has identified the required data (as anticipated), requested and obtained the data from the data / system owner, pre-processed the data to check for completeness and provenance / pedigree.]

Response: Your response must include the following:

1. Methodology

0. Describe the process by which you would conduct the analysis.

0. Include diagram of process flow.

0. Include strategy to partner with Government Subject Matter Experts (SMEs).

1. Project deliverables timeline.

1. Description of how you would address the deliverables: 1) briefs supported by visualizations and written reports; and 2) related deliverables in electronic form and in a file format that can be read and managed by the Government to include:

2. Processed data and processed information,

2. Documented data model / schema and business rules used to store, process, mine, rationalize, visualize, and analyze all data and information,

2. Modeling and simulation documentation.

1. Strategy to conduct Data Management Body of Knowledge (DMBOK)-framed assessment of people, process, and technology on this topic. Involves assessment of the “As-Is” capabilities listed in PWS Section 6.3.

1. Proposed labor mix to address the scenario.

· Scenario 2: This scenario is based on Project 2 from the solicitation, which is pasted below for reference.

Project 2: Tracking and categorization of Information Technology (IT) spending for the past five fiscal years. Project 2 will be completed NLT 4 months from the contract award date.

0. Identify, using detailed transactional data, how funding is spent on IT. Categorize spending based on data exploration without relying on constraints imposed by existing fiscal code constructs.

0. Compare and contrast the initial data exploration results with other models of IT spend / cost to include:

1. DoD’s Cost Decision (CODE) Framework

1. Technology Business Management (TBM) Model

1. Selective and Native Programming – IT (SNaP-IT)

0. Determine IT spend best estimate based on all referenced models / frameworks.

0. Assess which model (existing or new) optimizes capture of IT spending with respect to existing and potential programming constructs.

Assumptions: Project 1 is underway so that PBIS and SABRS data are pre-staged. Any additional data for this scenario (beyond PBIS and SABRS) are NOT pre-staged[footnoteRef:2]. This scenario will require the contractor to engage with HQ and the Operational Force to identify and capture additional (i.e., beyond PBIS and SABRS) structured and unstructured data at the local level and HQ level along with open source and other contextual data / information on IT spend. The Government will have some knowledge of the additional data requirements, but not full knowledge, so engagement and exploratory work will be required to identify, obtain, and pre-process the data. [2: Pre-staging means that the Government has identified the required data (as anticipated), requested and obtained the data from the data / system owner, pre-processed the data to check for completeness and provenance / pedigree.]

Response: Your response must include the following:

1. Methodology

0. Describe the process by which you would conduct the analysis.

0. Include diagram of process flow.

0. Include strategy to partner with Government SMEs and between vendor and USMC / Government data owners.

1. Project deliverables timeline.

1. Description of how you would address the deliverables: 1) briefs supported by visualizations and written reports; and 2) related deliverables in electronic form and in a file format that can be read and managed by the Government to include:

2.…