(Pre-Solic) 20161205 - Industry Day - Pre-Solic Conference Slides.pptx

Advanced Analytics Technical Solution MCSC – IAS FoS

Solicitation N65236-16-R-0001

Industry Day 5 December 2016 Statement A: Approved for public release (2 Dec 2016)

USMC / PMMI / IAS FoS Overview Statement A: Approved for public release (2 Dec 2016)

USMC Title 10 Responsibilities The Marine Corps … shall be organized to include not less than three combat divisions and three air wings, and such other land combat, aviation, and other services as may be organic therein.

The Marine Corps shall be organized, trained, and equipped to provide fleet marine forces of combined arms, together with supporting air components, for service with the fleet in the seizure or defense of advanced naval bases and for the conduct of such land operations as may be essential to the prosecution of a naval campaign.

In addition, the Marine Corps shall provide detachments and organizations for service on armed vessels of the Navy, shall provide security detachments for the protection of naval property at naval stations and bases, and shall perform such other duties as the President may direct. However, these additional duties may not detract from or interfere with the operations for which the Marine Corps is primarily organized.

The Marine Corps shall develop, in coordination with the Army and the Air Force, those phases of amphibious operations that pertain to the tactics, technique, and equipment used by landing forces.

The Marine Corps is responsible, in accordance with integrated joint mobilization plans, for the expansion of peacetime components of the Marine Corps to meet the needs of war

Key Marine Principles All Marines receive basic infantry training

Marine Officers are trained to serve as platoon commanders

Enlisted Marines Receive Marine Corps Combat Skills Training

Marine Philosophy: “Centralized planning, decentralized execution”

Commanders Intent Allows For Flexibility Of Execution

Delegate responsibility to the lowest level

Initiative and autonomy expected of junior Marines

Key Locations

Quantico Camp Lejeune Air Station Beaufort

Air Station New River

Recruit Depot Parris Island

Camp Pendleton Air Station Miramar Recruit Depot San Diego 1st Marine Brigade Kaneohe Air Station Marine Forces Reserve HQ Logistics Base Albany MCB Twenty-nine Palms

HQMC

Logistics Base Barstow Mountain Warfare Center Bridgeport Air Station Yuma

Air Station Cherry Point

Support Activity Kansas City

* Over 40 Inspector-Instructor(I&I) Units with Marine Reserve Units throughout the country in every state

Key Locations

MAGTF Elements

Aviation Combat Element

(ACE)

Ground

(GCE)

Command Element

(CE)

Logistics

(LCE)

MAGTF Capabilities

Mid-Intensity Conflict

Humanitarian Assistance Disaster Relief Joint Forcible Entry Counterinsurgency

Theater Security Cooperation

Marine Expeditionary Force

(MEF)

NEOs

Security Cooperation SP MAGTF

Crisis Response ……Contingency Ops Major Combat Operations Partner and Prevent Marine Expeditionary Brigade

(MEB)

Marine Expeditionary Unit

(MEU)

USMC Tactical Intelligence 0231: the hub of the USMC Intel Process Overall Purpose: Reduce commander’s uncertainty of the operational environment and provide for force protection Intel Disciplines:

Human Intelligence Signals Intelligence Geospatial Intelligence Measurement & Signature Intelligence Open Source Intelligence Analytic Process:

Filter, Record, Evaluate Analyze, Synthesize, Estimate

PMM-112 Marine Intelligence

Program Manager Marine Intelligence Mission: Equip and sustain our Marine Forces with timely, capable, and cost effective intelligence capabilities for current and future expeditionary and crisis-response operations.

Vision: "To deliver right, relevant, and ready intelligence capabilities to the Operating Forces.“ Right: we provide appropriate solutions that support the capability required Relevant: we deliver pertinent solutions that have bearing on the challenge at hand Ready: we supply complete solutions that equip the Operating Forces It is our job to make the most modern and technologically advanced equipment available to the Operating Forces as quickly, and cost-effectively, as we possibly can.

Marine Corps Systems Command is the acquisition command of the Marine Corps, serving as head of contracting authority and exercising technical authority for all Marine Corps ground weapon and information technology programs.

PMM-112 Marine Intelligence Organization

IAS FoS Intelligence Analysis System Family of Systems is the all-source analysis and production capability for the Marine Corps Intelligence, Surveillance, and Reconnaissance Enterprise. This acquisition program is the Marine Corps' primary intelligence analytical toolset at all levels of the Marine Air-Ground Task Force.

IAS FoS Composition: 3 Tiers Tier I: The MEF IAS supports the MEF Command Element in garrison and deployed.

Tier II: Intelligence Servers are cased into transportable server suites. The Intelligence Server Unix is UNIX-based and supports the Marine Divisions, Marine Aircraft Wings, Marine Logistics Groups, and Intelligence Battalions. The Intelligence Server Windows is Windows-based and supports Marine Expeditionary Units, infantry and artillery regiments, and air groups.

Tier III: Intelligence Workstations are man-portable, Windows-based systems that support battalions, squadrons, companies, and select higher echelon headquarters.

Key Capabilities Meta tagging of structured and unstructured data

Generate link analysis charts and views

Federated searches across disparate data sources

Operate in bandwidth limited/restricted environments

Synchronize and/or replicate analytical data

Provide mission-oriented data-sets or sub-sets of the master data set for disconnected or distributed operations

Expose data and finished intelligence products

AATS Technical Requirements Overview Statement A: Approved for public release (2 Dec 2016)

Overview Section C (PWS) documents supply and services requirements Supply – software and technical deliverables Services – support for integrating the software onto the IAS software baseline, training the end-users, and product improvements in response to end-user feedback Attachment 6 (IAS Hardware and Software Information) Provides additional detail about the operating environment of the AATS software

Note: this presentation does not cover all of the PWS requirements

Scope - Software Commercial Item (CI) or Non-developmental Item (NDI)

FAR 2.101

Supports USMC all-source analyst (MOS 0231) executing the intelligence cycle Shifts cognitive effort from processing of raw data to analysis of information Open API with support for 3rd party plugins, integration to AATS database, and an advanced analytic framework Functions in connected and disconnected modes Fully sustainable w/o FSR support

CI and NDI - Intent Projected effort soon after contract award Install, secure, and test software on the IAS baseline Integrate AATS database to external data sources Develop training material to support new equipment training (NET)

Mitigate schedule and technical risks Existing software already integrated together as a whole solution Previous sales and installations to support similar requirements

Software

Data Sources Analytics API Processing and Exploitation

(information)

Production (intelligence)

(raw data) 3rd-Party Plugin Data

API

Ontology (PWS 3.2.5.1) Gov’t will specify AATS ontology

OWL2 RDF/XML

AATS will validate all data against Gov’t ontology (3.2.5.1.10)

Gov’t ontology will be the “vocabulary” of the system For example, faceted searches will name things by their ontology labels (3.2.5.5.4)

Ontology management support Migration of data to align with ontology changes (3.2.5.1.6) Deployment of ontology updates to other nodes (3.2.5.1.8)

Data Entry (PWS 3.2.5.2) Manual Standard forms-based (3.2.5.2.1)

Tagging User-driven, software-facilitated identification of objects and relationships in documents (3.2.5.2.2)

Automated Pull from external data sources via user-defined data mapping (3.2.5.2.3.2) Object and Relationship identification (3.2.5.2.3.7) User review before commit (3.2.5.2.3.16)

Search (PWS 3.2.5.5) Standard search capabilities with contextual, geospatial, and temporal parameters (3.2.5.5.1-3.2.5.5.3)

Saved vs Standing Queries (3.2.5.5) Saved – can be recalled and executed by user Standing – runs on a periodic schedule, alerts user when new results match query parameters

Improving relevance of results (3.2.5.5)

Analysis (PWS 3.2.5.6) Geospatial (3.2.5.6.1) Relationship (3.2.5.6.2) Graphs/Charts (3.2.5.6.3) Temporal (3.2.5.6.4) Time slider integration – addition of temporal dimension to existing visualization Map Display (3.2.5.6.4.3) – e.g. to answer the question, “Is there a temporal factor associated with a particular cluster of events?”

Relationship Analysis (3.2.5.6.4.4) Heat Maps (3.2.5.6.5) Recommendations (3.2.5.6) Facilitate discovery of non-obvious relationships

Production (PWS 3.2.5.9) Intent Reduce manual effort required to turn intelligence into products ready for review and dissemination Report Templating (3.2.5.9.3) Generating target lists (3.2.5.9.5)

Integration with standard document generation software on the IAS software baseline (3.2.5.9.3.5) See also software build list tab of Attachment 6 (IAS Hardware and Software Information)

Connected/Disconnected (PWS 3.2.5.10) Disconnected, Intermittent, Limited (DIL) Two common scenarios Client (IW) connected to server (IS), local network connectivity only Client disconnected from server Must support intel cycle on the client while disconnected Load subset of AATS server data onto client (3.2.5.10.3) Create new data/modify subset of data on client while disconnected (3.2.5.10.4) Perform analysis and production (3.2.5.10.9 – 3.2.5.10.15) Synchronize with server upon reconnect (3.2.5.10.5)

API (PWS 3.2.5.12)

System Data (3.2.5.12.1) Supports Government development of integration between AATS database and external data sources Analytical Framework (3.2.5.12.2) Supports Government development of analytical algorithms for prediction, classification, etc.

UI Plugins (3.2.5.12.3) Supports Government development of visualizations, analysis tools, etc.

Must operate seamlessly with core software Receive selected objects/relationships, e.g. from map display or search results Send selected objects/relationships, e.g. to Reports

IAS Hardware and Software Information Attachment 6 Intelligence Workstation (IW) Physical laptop with specs shown on “IW Specs” tab Software baseline shown on “Intelligence Workstation Base” tab Components and versions subject to change Intelligence Server (IS) AATS components will be hosted on virtual machines managed by ESXi hosts Available resources shown on “IS Specs tab”

Reflects best information and estimates today Subject to change

Scope - Services Support existing IAS staff Installation, cybersecurity, testing, and training Data integration Product improvements

Require direct experience supporting the proposed AATS in each of the services functional areas

IAS Development Process Overview Software Integration Security Scans Testing Vulnerabilities Trouble Reports

Installation (PWS 3.4.2) Support for resolution of issues Discovered in integration peer testing (3.4.2.1) Discovered in formal engineering drop testing (trouble reports, 3.4.2.2) Discovered in security scanning (3.4.3.3)

Must document all problems, root cause, and resolution Intent: AATS software fully sustainable by IAS staff

Ontology Installation (PWS 3.4.4) Troubleshoot and resolve installation (import) issues

Document all problems, root cause, and resolution Intent: AATS software fully sustainable by IAS staff

Gov’t AATS Ontology Contractor Requirements (3.2.5.1.2)

OWL2

RDF/XML

AATS

Import

Cybersecurity (PWS 3.4.6) Government will perform security scans and identify cybersecurity requirements (DISA, Navy, USMC) Contractor responsible for resolving scan findings Contractor responsible for developing response to requirements Must provide software updates or patches if requirements cannot be met through configuration Must document all responses to cybersecurity requirements

Source Code Analysis (PWS 3.4.6.3.3) Applicable to:

Components for which source code is available to the Government (e.g. open-source software, GOTS) Source code developed on this contract

Government will perform scanning of source code Contractor supports instrumentation of source code scanning tools (e.g. compilation, linking, etc) Contractor reviews findings, and implements response

Test (PWS 3.4.7) Support IAS staff Formulation of test cases and procedures to verify proper functioning of AATS software on the IAS baseline (3.4.7.1 – 3.4.7.2) Troubleshooting/resolution of test incidents (3.4.7.2.2)

Development and execution of performance tests (3.4.7.5)

Integration into automated testing program (3.4.7.4) Current automated test platform: ATRT Test Manager (vendor – IDTUS)

Data Integration (PWS 3.4.5) Integrate AATS database with external data sources E.g. MIDB, M3

Design considerations Data management strategy Data mapping to Government AATS ontology

Provide all technical data for IAS program to maintain the data integration

Software Development (PWS 3.4.3) In response to emerging user requirements Feedback from fielding, training, operational use

NOT for development of initial software delivery See requirements for CI/NDI software

Training (PWS 3.5) IAS Training Team responsible for NET

NET covers all aspects of the IAS baseline

Contractor supports training team for the AATS component of the IAS baseline Trains part or all of the AATS software to a system administrator and end-user audience Provides SME support during NET to train advanced usage of the AATS software

Solicitation Overview Statement A: Approved for public release (2 Dec 2016)

Solicitation Overview

Contract Type: Indefinite Delivery/Indefinite Quantity (IDIQ) All supplies/services authorized and funded by placement of delivery/task orders

Single Award Contract (SAC) Pricing Arrangement: Delivery/task orders issued under the contract will be either Firm Fixed Price (FFP) or Cost Plus Fixed Fee (CPFF).

Period of Performance: Five Year Performance Period

Solicitation Overview

Timing of Delivery Order 0001: Government intends to award delivery order (DO) 0001 concurrently with contract award. At a minimum, DO 0001 shall require delivery of contract line item number (CLIN) 0001 - AATS Software.

Estimated Solicitation/ Award Dates: Solicitation Issued - February 2017 Proposals Received - March 2017 Contract Award - April 2018 Competitive Environment: Full and Open Competition

Section B Overview

Solicitation Focus Areas Section C, PWS Section 8.1.1 – Security Classification Classified work shall be performed under this contract and subsequent task orders, as required Contractor shall have at the time of contract award a SECRET facility security clearance (FCL)

Section L, Non-government personnel employed by The MITRE Corporation may serve as advisors in the source selection process Each offeror and each of its subcontractors/teaming partners are required to enter into their own non-disclosure agreements with the non-government company and copies of these non-disclosure agreements must be submitted as part of this proposal. Point of contact identified in solicitation

Source Selection Phased Evaluation Approach The Government will implement a phased evaluation.

Phase I will include an evaluation of the following factors:

Factor A (AATS Software Product) Factor B (Technical Capability) Factor C (Past Performance) (acceptable/unacceptable only) Factor D (Software Development Plan) (acceptable/unacceptable only) Factor E (Small Business Participation) (acceptable/unacceptable only) Factor F (Cost/Price)

Phase II will include the evaluation of Factor G (AATS Software Product Demonstration)

A proposal that receives a rating of "Unacceptable" in any evaluation factor or subfactor will render the entire proposal ineligible for award

Government will invite those offerors with the most highly rated proposals to participate in Phase II: evaluation of Factor G (AATS Software Product Demonstration) The most highly rated proposals will be the following:

Rated "Acceptable" in Factor C (Past Performance), D (Software Development Plan), and E (Small Business Participation)

Represent the best value to the Government following a trade off of Factors A (AATS Software Product), B (Technical Capability), and F (Cost/Price)

Phase II: Offerors rated "Acceptable" or better under Factor G will be included in the best value trade off analysis of the following factors:

A (AATS Software Product) B (Technical Capability) G (AATS Software Product Demonstration) F (Cost/Price)

Solicitation Sections L and M Evaluation Criteria Factor A - AATS Software Product

Factor A relates to contract line item number (CLIN) 0001 - Delivery of AATS Software

Subfactor A1 – Support for Intelligence Cycle Subfactor A2 – Operation in a DIL Network Environment Subfactor A3 – Ontology and Data Management Subfactor A4 – Application Programming Interface (API) Subfactor A5 – Technical Approach (related to Software Capabilities Matrix)

Factor B - Technical Capability

Factor B relates to CLIN 0004 - Original Equipment Manufacturer (OEM)/Subject Matter Expert (SME) Support for AATS Integration, Configuration, System Administration, Test, and Information Assurance

Subfactor B1 – Systems Engineering Support Subfactor B2 – Cybersecurity/Info Assurance Support Subfactor B3 – Data Integration Support

Factor C - Past Performance

Demonstrated record of performance in supplying products and services that meet contract requirements

Past Performance references associated with Factor A (AATS Software Product) and Factor B (Technical Capability)

Factor A - provide contract references where products/modules have been previously delivered to Government or non-Government customers

Factor B - provide contract references for efforts similar in scope to the requirements of the solicitation

Factor D - Software Development Plan

Subfactor D1 – Software Development Plan Subfactor D2 – Software Development Plan Rationale Subfactor D3 – Model Based Maturity Assessment

Factor E - Small Business Participation

Extent of participation with small businesses in terms of the total acquisition value (TAV) of the contract

Minimum acceptable small business participation average goal, based on the total acquisition value for this solicitation is 5.0%

Factor F - Cost / Price Proposal

Prices and any information required by Section B

Cost Proposal Narrative

Pricing Model for primes and all subcontractors in accordance with solicitation Attachments 4A and 4B

Evaluated for price reasonableness, cost realism (CPFF portion), price realism (FFP portion), uncompensated overtime, HubZone preference, professional employee compensation, and small business subcontracting plan

Factor G - AATS Software Product Demonstration (Phase II Only)

AATS Software Product demonstrations will be conducted as part of the evaluation of Phase II

Product demonstrations will occur at SPAWARSYSCEN Atlantic facilities in Charleston, SC

A demonstration plan will be provided by the Government that specifies the tasks to be performed for each demonstration

Government will provide all source data and materials required to conduct the demonstration (with the exception of the hardware and software)

Factor G - AATS Software Product Demonstration (Phase II Only)

Subfactor G1 - Demonstration of Ontology and Data Management Subfactor G2 - Demonstration of Support for Intelligence Subfactor G3 - Demonstration of API.

Basis for Award Non-Cost Factors More Important than Cost

Evaluation factors other than cost, when combined, are more important than cost/price, however, cost/price is an important factor and should be considered when preparing proposals

Relative Importance of Non-Cost Factors

For Phase I Evaluation, Factors A and B will be rolled up into an overall technical rating

For purposes of establishing that rating, the order of relative importance for the non-cost evaluation factors is established as follows:

Factor A (AATS Software Product) is significantly more important than Factor B (Technical Capability)

Factor C (Past Performance – Confidence Assessment), Factor D (Software Development Plan) and Factor E (Small Business Participation) will be evaluated on an Acceptable/Unacceptable basis

Relative Importance of Non-Cost Factors

For Phase II Evaluation, Factors A, B, and G will be rolled up into an overall technical rating

For purposes of establishing that rating, the order of relative importance for the non-cost evaluation factors is established as follows:

Factor A (AATS Software Product) is more important than Factor G (AATS Software Product Demonstration), which is significantly more important than Factor B (Technical Capability)

Factor C (Past Performance – Confidence Assessment), Factor D (Software Development Plan) and Factor E (Small Business Participation) will be evaluated on an Acceptable/Unacceptable basis

Wrap-Up After the break, we will begin responding to questions received during the break. Time permitting, we will respond to questions submitted today

Questions are encouraged…please submit all solicitation related questions in writing to ensure a non-attributional record and to provide accurate minutes of the conference

Questions will be addressed during the allotted question and answer period. This is not a forum for open discussions

All questions and answers (along with presentation material) will be posted on the SPAWAR e-Commerce website (https://e-commerce.sscno.nmci.navy.mil)

Information in the presentations may change. Updates will be reflected in the final solicitation image3.jpeg image4.jpeg image5.jpeg image1.jpeg image2.jpeg image11.jpeg image12.png image13.png image14.jpeg image15.png image16.png image17.jpeg image18.jpeg image19.jpeg image20.jpeg image21.jpeg image22.jpeg image23.jpeg image24.png image25.png image26.jpg image27.jpeg image36.png image37.png image38.png image39.gif image40.png image41.jpeg image42.png image28.png image29.png image30.png image31.png image32.png image33.wmf image34.jpeg image35.png image43.emf

Microsoft_Word_Document1.docx

NOTIONAL ESTIMATED SUPPLIES AND SERVICES

Year 1

Year 2

Year 3

Year 4

Year 5

(Five-Year Ordering Period, No Option Years)

Task Order 0002--------------------------- Delivery Order 0001 ---------------------------

AATS SOFTWARE

INITIAL DELIVERY

CLIN 0001 (FFP)

SYSTEM DOCUMENTATION

CLIN 0002 (FFP)

TRAINING MATERIALS

CLIN 0003 (FFP)

OEM/SME SUPPORT

CLIN 0004 (CPFF)

ANNUAL LICENSE RENEWALS/UPDATES

CLIN 0005 (FFP)

CLIN 0006 (FFP)

PRODUCT IMPROVEMENTS BASED ON USER FEEDBACK

CLIN 0007 (CPFF)

CLIN 0008 (FFP)

CLIN 0009 (FFP)

PRODUCT IMPROVEMENTS BASED ON USER FEEDBACK

CLIN 0010 (CPFF)