N0018922RZ004-0001.pdf

N6328520210390

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

See page 2 for amendment details.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 56

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 14-Jan-2022

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0018922RZ004

X 9B. DATED (SEE ITEM 11)

21-Dec-2021

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

14-Jan-2022

CODE

NAVSUP FLC NORFOLK PHILADELPHIA OFFICE

ATTN: JACOB SEGAL 700 ROBBINS AVENUE, BLDG. 2

PHILADELPHIA PA 19111-5083

N00189 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0018922RZ004

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

SUMMARY OF CHANGES

SUMMARY OF CHANGES

PART I – THE FOLLOWING CHANGES ARE HEREBY INCORPORATED INTO THE

SOLICITATION:

AMENDMENT 0001 DETAILS

The purpose of this amendment is detailed below:

1. Provide Small Business subcontracting goals as shown below.

2. Update the Attachment list as shown below.

3. Add an Exhibit list as shown below.

4. Update the PWS as shown on the following page(s).

5. Add a section for Security Administration as shown on the following page(s).

6. CDRL A001 is hereby deleted, as it is a duplicate with errors.

7. Update provision 52.212-1 as shown on the following page(s).

8. Extend the closing date of the solicitation to 4:00 PM EST on 28 January 2022.

9. Provide answers to a list of questions received by vendors as shown in Part II below.

10. All other terms and conditions remain unchanged.

11. Point of contact for this document is Mr. Jacob Segal who can be reached by e-mail at

Jacob.a.segal.civ@us.navy.mil.

12. Any future questions will be answered at the Government’s discretion.

DoD Subcontracting Goals:

DoD Subcontracting Goals:

SDB 5%

WOSB 5%

HZ 3%

VOSB 3%

SDVOSB 3%

Attachments:

ATT I: CONTRACT ADMINISTRATION PLAN (CAP)*

ATT II: QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)*

ATT III: Pricing Worksheet*

ATT IV: DD FORM 254 “CONTRACT SECURITY CLASSIFICATION FORM”*

ATT V: PAST PERFORMANCE FORM*

ATT VI: Guidebook for Acquisition of Naval Software Intensive Systems (attached to amendment posting)

Exhibits:

Exhibit A: Contract Data Requirements List (CDRL) (A002-A031)*

*Included in the original Solicitation package

The following have been modified:

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT

FOR

DEPARTMENT OF THE NAVY (DON)

mailto:Jacob.a.segal.civ@us.navy.mil

NAVAL CRIMINAL INVESTIGATIVE SERVICE (NCIS)

LAW ENFORCEMENT INFORMATION SHARING PROGRAM

1. Introduction

The Naval Criminal Investigative Service (NCIS) is the Department of the Navy (DON) component with primary responsibility for criminal, counterintelligence (CI), and counter terrorism (CT) investigations and operations, and

Navy security and law enforcement policy matters. NCIS has primary investigative and CI jurisdiction within the

DON, and exclusive investigative jurisdiction in non-combat matters involving actual, potential, or suspected criminal, terrorism, sabotage, espionage, and subversive activities. Further, NCIS has primary responsibility for liaison on all criminal investigative and CI matters. Reviewing the revised NCIS Charter known as SECNAVINST

(Secretary of the Navy Instruction) 5430.107A will provide insight into NCIS roles and responsibilities. Additional information on NCIS can be found at our public website http://www.ncis.navy.mil/Pages/publicdefault.aspx.

The NCIS mission is to 1) Prevent terrorism and related hostile acts against DON forces and installations, 2) Protect against compromise of DON information and penetration of critical operational systems that would cause an unacceptable risk to the safety and security of personnel and strategic assets, and 3) Reduce criminal activity and mitigate its impact on Navy and Marine Corps operational readiness through adoption of a more proactive posture.

1.1 Background

The NCIS Department of Defense Law Enforcement Information Exchange (D-DEx) and the Law Enforcement

Information Exchange (LInX) Program (initiated in 2004 by NCIS) is designed to address issues that grew out of the attack against the USS COLE and the September 11th terrorist attack upon the United States. These acts of aggression dramatically accelerated the need for change in all areas of NCIS operations, providing impetus for NCIS to act quickly and prudently to address critical, emergent mission challenges. These programs align with facets of all three aforementioned mission challenges. Subsequent criminal acts involving DON and Department of Defense

(DoD) personnel to include the Fort Hood, Washington Navy Yard and Chattanooga shootings, reinforced the need for collaborative law enforcement efforts and improved information sharing.

The D-DEx/LInX system provides access to law enforcement incident and investigative data collected and contained within a central data warehouse. The system is designed to permit participating users to query and analyze collected law enforcement data that can satisfy the needs of four principal user groups: executive decision makers, analytical staff, law enforcement patrol (tactical) and investigative staff. The system provides scheduled data collection from each participating agency and automatically updates the data warehouse. See Appendix A for a more detailed description of the LInX architecture.

1.2 Scope

The D-DEx/LInX program has reached a state of maturity, which requires contract support for the maintenance and refresh of hardware systems, the installation and updates of software licenses provided by the Government, and some expansion of the regional data in D-DEx/LInX sites. Additionally, the integration of additional data and enhancements from several investigative sources within the DoD, as well as federal partnerships with other information sharing initiatives will continue to be pursued. The NAVY anticipates there will be an emphasis on the continued build out of capabilities for D-DEx.

This scope of effort covers:

Ongoing maintenance of 15 Regional LInX sites, detailed below in section 3.9.Integration of data from additional agencies into LInX sites on a limited basis as tasked by the Government.

Integration of data and enhancements of existing data feeds to and from D-DEx/LInX from additional Law

Enforcement agencies and/or partner systems, like the National Data Exchange (N-DEx).

Maintenance and operation of the 15 Regional LInX sites and D-DEx sites, as shown below in Section 3.9.

Development of software releases, and integration of Commercial Off the Shelf/Government Off the Shelf

(COTS/GOTS) tools; generally 2 or 3 releases per year, as tasked by the Government, to support the NCIS http://www.ncis.navy.mil/Pages/publicdefault.aspx mission and that of other DoD partners, and to support the continued compatibility of LInX and D-DEx with the Department of Justice (DOJ) agencies, the Department of Homeland Security (DHS) and other federal agencies.

Deployment of the updated software releases as required.

Compliance with Information Assurance standards and the DoD Risk Management Framework (DoD

RMF).

Compliance with Criminal Justice Information Services (CJIS) requirements.

Systems engineering to support the identification and procurement of updated hardware (tech refresh of hardware baseline).

Systems administration and operation, and technical assistance for all D-DEx/LInX systems, including the establishment and operation of a 24x7 help desk for Systems Administration support.

Assess the current architecture and provide a plan to re-architect the system with a goal of reducing maintenance costs while maintaining a high level of capabilities for NCIS agents and analysts and the Law

Enforcement User Community. This would include the exploration of Cloud hosting options.

Research and prototype new candidate capabilities in support of D-DEx/LInX. Examples include, but are not limited to; Smartphone technology, Biometric integration, Digital Photography, GIS Integration, Crime

Scene data integration, improved search capability, Big Data Analytics.

Assist in the implementation of a D-DEx/LInX continuity/backup/failover plan

Sustainment of an IV&V environment (Government furnished equipment)

Enhancements to ensure NIEM compliant data feeds based on configurable business rules

Support to the Government PMO with training development and delivery in addition to, governance and strategic planning.

Documentation in support of above listed scope of effort.

1.3 Objectives

The primary objectives of this effort are to continue the operation and maintenance of the existing D-DEx/LInX systems.

1.4 Outcomes

The Government desires the following outcomes:

Through continuous improvement processes employed for the maintenance of the system(s), the desired outcome by the Government is system availability above 99% (unscheduled outages), and system performance and reliability at industry standards or better.

When the Government tasks the Extract, Transformation, and Load of additional agency data, the desired outcome by the Government is data reliability and data quality metrics are maintained and improved throughout the period of performance.

Through occasional software enhancements and the reduction of defects in the system, the Government desires that the D-DEx/LInX application continues to provide the Law Enforcement community the best of breed in easy to use query and analytic capabilities to reduce crime, prevent terrorism, and protect DoD assets.

The desired outcome by the Government is to have Cost Models that demonstrate investment in re-architecting and possibly changing platforms (for example open source for DB and search engine) which will save the Government money without diminishing capabilities as tasked by the Government.

Through more efficient architectural approaches, the desired outcome by the Government is to reduce the overhead cost of the system and the LInX program so that LInX can continue to deliver regional connectivity with fewer costs, and thereby potentially have additional funding for other enhancements and expansion.

The Government desires the presentation of new technologies and platforms for the D-DEx/LInX application. Examples include, but are not limited to; Smartphone technology, Biometric integration, Digital Photography, GIS Integration, Crime Scene data integration, improved search capability, Big Data

Analytics.

The Government desires reach back expertise that bring open source solutions and new capabilities that will meet the mission requirements. The desired outcome by the Government is to reduce the overall cost of the program and that LInX and D-DEx continue to provide excellent capabilities. Examples would include the use of new database capabilities such as big data to solve performance issues related to structured data queries across several entities.

1.5 D-DEx/LInX Standards

The D-DEx/LInX standards include:

Governance: A formal body is established, consisting of the leadership of all participating agencies, to determine local priorities and operating procedures, and to assume responsibility for each agency’s use of the system, as well as the region’s collective use.

Data Availability: Agency participation requires the contribution of all legally sharable data.

System Performance: All LInX systems continue to be characterized by the key technical capabilities that produce timely responses, comprehensive and reliable searches, and analytical tools deemed critical to the operational requirements of the system.

Security: Security must be maintained consistent with DoD and federal standards, so as not to preclude the full participation of DoD, DOJ, DHS and state/local/tribal law enforcement agencies. The D-DEx system must be accredited by the U.S. Navy NetWarCom according to the DoD Risk Management Framework

(RMF) standard (reference (b)) for sensitive but unclassified law enforcement data. The security accreditation will be in place March 2022 and it is anticipated to be valid for two and a half years. The document is a living document and will require updates and addendums as software releases and configuration changes are implemented.

Data Standards:

National Information Exchange Model http://www.niem.gov/

National Crime Information Center (NCIC) http://www.fbi.gov/about-us/cjis/ncic

2. Applicable Documents

a. National Information Exchange Model (NIEM) 3.0, http://www.niem.g4ov

b. Department of Defense Instruction 8510.01, Risk Management Framework (RMF) for DoD Information

Technology (IT), March 12, 2014

c. LINX System Requirement Specification v6.3

d. LINX System Functional Design Description v6.3

e. Office of the Assistant Secretary of the Navy (Research, Development and Acquisition) Guidebook for

Acquisition of Naval Software Intensive Systems, Version 1.0, September 2008.

f. IEEE/IEC Standard 12207-2008 Systems and software engineering – Software life cycle processes, Second edition, 2008.

3. Management, Operational and Technical Requirements

3.1 Project Management Plan

The Contractor shall develop, deliver and maintain a project management plan that details how the Contractor will manage the program. At a minimum, the plan shall address how the Contractor will staff the project, maintain cost and schedule control, resolve problems and issues, exercise corporate reach-back, and identify and mitigate risks.

The draft project management plan will be submitted with the proposal and the final shall be submitted not later than

30 days after contract effective date with quarterly updates.

3.2 Software Development Plan

The Contractor shall develop, deliver and maintain a Software Development Plan (SDP) that describes the

Contractor’s software development approach. The SDP shall be structured in accordance with the software life cycle processes described in IEEE/EIA Standard 12207 and shall address the Contractor’s specific tasks and activities http://www.niem.gov/ http://www.fbi.gov/about-us/cjis/ncic http://www.niem.g4ov/ across the software life cycle for D-DEx/LInX software. The draft SDP will be submitted with the proposal. The final shall be submitted for PMO approval not later than 30 days after contract award. The SDP will be updated as necessary throughout the period of performance to reflect new and/or improved software development processes.

All changes to the SDP will be subject to PMO approval. A sample SDP template is contained in Guidebook for

Acquisition of Naval Software Intensive Systems, reference (e).

3.3 Project Master Schedule

The Contractor shall develop, deliver and maintain a project master schedule in the most current version of

Microsoft Project. The project master schedule shall include all project tasks and activities and accomplishments

(completed tasks). The Contractor shall be prepared to discuss schedule variances at the weekly contract status reviews.

3.4 Risk Management Plan

The Contractor shall prepare and deliver a Risk Management Plan that describes an ongoing, proactive Risk

Management Process. Risk assessment and mitigation will be discussed at status meetings on a regular basis. The

Risk Management Plan will be submitted to the PMO for approval within 30 days of contract award.

3.5 Change Management

The Contractor shall prepare and deliver a Configuration Management Plan (CMP) that describes the items that are being controlled, how configuration items are identified, version numbering, and the change control process. The

CMP will be submitted to the PMO for approval within 30 days of contract award.

3.6 Contract Status Review

The Contractor shall execute a Contract Status Review (CSR) weekly. The CSR must address project activities to include technical accomplishments and challenges, schedule, risk, and cost performance based on past challenges and future tasks. The Government Program Manager or COTR may identify other relevant topics to be discussed.

3.7 Quality Assurance Plan

The Contractor shall develop a Quality Control Plan which identifies quality standards and guidelines for:

Software evaluation

Requirements analysis

Product design

Coding and Unit Testing

Acceptance testing

Product release process

Production Maintenance and Support

Corrective action process

Deviations and waivers process

The QCP shall also address the execution of quality reviews that should cover areas for improved efficiencies, reduction of defects/quality improvements, improved customer satisfaction, and cost savings. Results of the quality reviews shall be provided to the Government with proposed action plans to implement improvements as well as reports and metrics to support and track corrective actions., such as Data Quality Reports, Systems Performance

Metrics, Audit table, System Logs, Problem/Suggestions Log and other metadata that is collected and available from the database and the application servers. The execution of the plans of action shall proceed based on Government approval.

3.8 General Requirements

The D-DEx/LInX program requires project and program management knowledge and expertise that covers deliverables such as detailed schedules, weekly status, bi-weekly contracts meeting agenda and governance presentations as well as law enforcement-specific experience with implementation of a large police department records management system or other local or state law enforcement IT project. Additionally, the program requires experience with involvement in law enforcement investigative processes.

The D-DEx/LInX program requires systems architecture and engineering knowledge and expertise in executing technical releases and change management to systems. Particular emphasis on the expertise required to manage and sustain regional systems in a consolidated environment to reduce costs and realize efficiencies. The Contractor shall lead the development of various deliverables including updates to systems software management, tuning, metadata capture, design and architecture documents.

The D-DEx/LInX program requires information assurance engineering knowledge and expertise to work closely with the Government Program Management Office (PMO) and the Contractor team to maintain the confidentiality, integrity, availability, and the non-repudiation of the D-DEx/LInX systems according to the standards and protocols set forth in the DOD Risk Management Framework (RMF), reference (b). Familiarity with RMF across the DoD services to ensure acceptance and compliance for D-DEx member agencies is required.

The Contractor shall:

Use standard data feeds created and maintained by the Records Management System (RMS) vendors whenever available and retrofit custom data feed solutions with a NIEM-compliant solution where available.

Ensure the design is fully compatible with existing hardware and software infrastructure, is sufficiently flexible to support future enhancements and built on an open architecture platform, uses components that are modular in construction and not tightly coupled, and is able to support reasonable reuse;

Maximize the use of COTS/GOTS technologies and investments;

Develop, document and maintain system architecture information using industry standard processes and formats;

Provide invoicing by agency, engineering, and management resources. Provide invoicing by the

10th of each month. Include in each invoice a breakout by site, engineering and project management. In each of these categories, include: labor by person for each agency as required by FISC, procurement, travel expenses, other direct costs.

3.9 Maintain and Operate D-DEx/LInX Production and Development Site

There are currently 13 regional LInX sites, one (1) D-DEx site, one (1) Federal site and one (1) IVV site that comprise the “D-DEx/LInX sites”. The regional sites, and the number of agencies connected to each are listed below. These locations and number of agencies are subject to change and additional agencies will be priced at the time they are added.

Region Agencies Connections Grant Funded

California 142 129 0

Carolinas 569 338 0

D-DEx 16 35 0

Federal 9 18 0

Florida 160 0 160

Gulf Coast 292 44 0

Hawaii 14 24 0

IV&V 0 7 0

MW 95 98 0

NCR 219 216 0

NE 91 70 0

NW 331 174 0

RG 39 51 0

RM 70 48 0

SE 324 259 0

VA 241 227 0

TOTAL 2612 1738 160

The Contractor shall provide production system monitoring for all D-DEx/LInX production systems to include:

24 hours, seven (7) days per week monitoring and proactive notification of production availability.

Notification of degradation or loss of service shall be communicated through an agreed upon method to include email and phone follow-up. For each notification, response activities include identification of issue, notification through agreed upon method (phone and email contact list), and plan/execution of issue resolution in a timely manner:

o Two (2) hour response to production operations issues during business hours (8am to 6pm Monday through Friday).

o Four hour response to production operations issues after hours and weekends/holidays o Updated hardware & software Asset Inventory whenever inventory changes.

The Contractor shall produce and deliver a quarterly Centralized Management Operations center report summarizing the LInX production availability. The Centralized Management Operations

Center Report shall include:

LInX system downtime, reason for each downtime event with resolution, Total downtime per site (for period)

Operation reports be provided on a quarterly basis. The periodicity of these reports will remain quarterly for the duration of performance.

The Contractor shall produce and deliver a Quarterly Front Porch Data Feed Maintenance / Repair Report summarizing the data reported in the weekly status reports. For each issue, the report will include the date of the issue, Agency(ies) involved, Agency Contact, details of the issue, and whether the issue was resolved or escalated.

The Contractor shall provide the PMO with preemptive email notification of planned production down time.

The Contractor shall assist with the implementation of systems software and security upgrades/patches as follows:

For the regional LInX systems, the Contractor will be primary for systems software and security upgrades/patches.

For the D-DEx system, the Contractor shall be primary for systems software and security upgrade/patches working with the Government to implement strict configuration management.

The Government will assist the Contractor with the management of existing equipment support agreements and dispatch vendors or maintenance contractors to support existing hardware:

The Contractor shall be primary in the management of existing equipment support agreements; the

Contractor shall be primary in the dispatch of vendor maintenance for the regional LInX systems, and shall be primary for the dispatch of vendor maintenance for the D-DEx system.

The Contractor shall assist the Government with LInX/D-DEx system troubleshooting and dispatch of ISP/Telecom

Service Providers as required:

For the regional LInX systems, the Contractor will be primary for troubleshooting and dispatching of

ISP/Telecom Service Providers.

For the D-DEx system, the Government will be primary for troubleshooting and dispatching of

ISP/Telecom Service Providers.

The Contractor shall conduct a site visit to each regional LInX site to perform equipment preventive maintenance as needed.

The Contractor shall provide onsite support, as required, to restore a failed system.

The Contractor shall perform database and system backup for system recovery.

The Contractor shall monitor system logs and server performance and remediate potential issues prior to end user awareness of the issue whenever possible.

The Contractor shall implement automated scripts wherever possible to maintain D-DEx/LInX application and database maintenance to include patches, bug fixes, update statistics, recycle of servers.

For the regional LInX systems, the Contractor shall be primary for application and database maintenance to include patches, bug fixes, update statistics, recycle of servers.

For the D-DEx system, the Contractor shall be primary for application and database maintenance to include patches, bug fixes, update statistics, recycle of servers. The Contractor shall coordinate closely with the Government to maintain strict configuration management of such changes.

The Contractor shall update the system recovery tapes when a software change is performed.

For the regional LInX systems, the Contractor shall be primary for application and database maintenance to include patches, bug fixes, update statistics, recycle of servers.

For the D-DEx system, the Contractor shall be primary for application and database maintenance to include patches, bug fixes, update statistics, recycle of servers. The Contractor shall coordinate closely with the Government to maintain strict configuration management of such changes.

The Contractor shall perform refresh of existing equipment as tasked and provided by the Government.

3.10 Software Integration

The Contractor shall develop and implement D-DEx/LInX software releases as directed by the NCIS LInX PMO.

All software utilized for the deployment and expansion of the LInX system shall be commercial off the shelf

(COTS) software to the fullest extent possible. The Contractor may develop unique software upon approval of the

PMO to include COTS custom interfaces, web services, and integration software.

The Contractor shall document all system and functional requirements in accordance with the documentation requirements listed in the CDRL. The Contractor shall update this documentation with each release or upgrade of the system as a versioned artifact.

3.11 Web Technology

Because of the wide and varied LInX customer base, it is imperative that no client-side software installation be required to use the base LInX application for user access, query, and analysis. The Contractor shall develop all capabilities to run on required web browsers such that users will be able to access and use D-DEx/ LInX with only a standard browser and the JAVA Runtime Environment.

3.12 Data Extraction, Transformation and Load (ETL)

The data from the participating agencies must be replicated in a data warehouse on a near real time basis. The ETL process will transform the data to the extent possible to normalized values using NCIC based lookup tables wherever applicable. Other processes will also be executed during the Update Data Warehouse step to include, but not limited to the extraction of entities from heterogeneous sources, both structured and unstructured data through advanced entity extraction tools, indexing of data for both tactical, and analytic and free text queries, association of mug shots and scars/marks/tattoos with person data, and geocoding of all well-formed addresses.

3.13 Expansion of Existing D-DEx/LInX Sites

Should the Navy determine that additional regional sites are desired, the Government expects to leverage the existing server capacity with new webservers to accommodate this expansion.

The Contractor shall be tasked with the maintenance of all regional systems, to include improving the performance and the availability of all regional systems where feasible as directed by the Government.

Research and Prototyping: The Government PMO is interested in the exploration of information technology advancements, process improvement, strategic partnerships and other areas to enhance the overall functionality of the LInX/D-DEX program. The Government seeks the Contractor’s support in the investigation of these areas of interest. As directed by the Government, the Contractor shall prepare white papers and recommendations based on technical capabilities, cost benefit analysis, strategic direction and risk-based analysis to include but not limited to the following topic areas:

Technical Planning

Technology Assessment

Cloud Hosting

Architectural Assessment

System Design

Systems Implementation

Staging and Configuration Services and Management

Systems Integration

Systems Support

Migration Services

Clustering Services

High Availability (HA) Services

Implementation and Roll-out

Capacity Planning

Systems Analysis and Design

Site Surveys

Implementation, Deployment, Fielding, Testing and Logistics Support

Operations and Maintenance Support

Business Process Modeling

Best Practices for querying records system within the Law Enforcement industry

Best Practices for deploying secure data warehouse-based applications

Strategic Partnerships

Other areas of interest may be identified during the research effort and additional areas of investigation may be added under mutual Government and Contractor agreement.

The Contractor shall provide the following:

1. Within 6-months from the effective date of the award, develop a business analysis that provides the following:

o Comparison of fixed costs and estimate for the shift of the DDEX server farm from the Russell

Knox Building to a DoD IL5 Cloud environment to include at least the following cloud environments:

Amazon AWS

Microsoft Azure

DISA MilCloud 2.0

Oracle IL5 Enclave o Rough estimate on the timeline required to migrate and implement DDEX with a full Risk

Management Framework Authority to Operate.

o The estimate for the shift of DDEX to the CLOUD should include required labor from the contractor to execute the migration during the first option year of this contract.

o Once the DDEX migration has completed, indicate any savings or new expenses to be incurred by the government in the normal operations of DDEX.

3.14 Partner System Integration and Compatibility

The Contractor shall maintain standard interfaces for information sharing such as the National Information

Exchange Model and the Logical Entity Exchange Specification (LEXS). D-DEx/LInX currently includes these interfaces for both transfer and ingestion of data, as well as the sharing of data via web-services. As these standards are modified or enhanced over time, the Contractor shall maintain the deprecated legacy interfaces in addition to the updated interfaces to ensure access for all data exchange partners. The Contractor shall assist the Government in migrating data exchange partners from deprecated interfaces to the new, supported interfaces. When authorized by the Government, this may include providing direct engineering support to partner systems and LInX/D-DEx data exchange participants.

3.15 Test and Evaluation

The Contractor shall be responsible for ensuring that all data integration and software releases are tested and evaluated. Metrics on defects will be collected and utilized to implement a quality program, with the goal of reducing defects, improving efficiencies, and improving quality throughout the systems life cycle. The Government will issue a formal User Acceptance letter upon completion of testing, and determination that all requirements have been successfully delivered and tested for production.

3.16 D-DEx/LInX Training and Online Help Documentation

The Contractor shall maintain the existing training documentation that supports all user training programs.

Maintenance of the material requires updates of the text and graphics with each release to reflect changes to the documentation using Microsoft Word.

The use of innovative products for producing multi-media and eLearning training, is under consideration by the

Program Management Office, and may be in scope of future tasking to document and manage training material enhancements.

3.17 Security and Accreditation

The Contractor shall maintain all LInX/D-DEx Security Accreditation documentation and is responsible for the implementation of the DISA Security Technical Implementation guidelines (STIGs) under the change procedures described in section 3.3, above. The Government will provide access to the DISA STIGS and websites as required.

The Contractor shall work with the NCIS Enterprise Security Directorate to meet all necessary security requirements at the law enforcement sensitive but unclassified level. The NCIS Enterprise Security Directorate will deliver the final system accreditation documentation to the Navy NetWarCom Designated Accreditation Authority - DAA.

This includes the required hardware and software configuration documentation, data and user audits and scan results from the DISA-required scans and audits.

The Contractor shall produce the necessary system security accreditation documentation for the DAA to issue and maintain final accreditation of the D-DEx/LInX data warehouse and network. This documentation shall meet the requirements of the DOD Risk Management Framework (RMF).

The Contractor shall ensure all software, hardware and network integration, and modifications meet all established

RMF standards at the time of implementation. The System Security Accreditation Authorization (SSAA) documentation for all D-DEx/LInX deployments has been published and accepted by the Navy DAA. A representative SSAA document is available to the Contractor for reference, and RMF template documents will be provided by the Government.

3.18 Hardware/Software Procurement

The Contractor shall provide support for the procurement of COTS hardware and software, the support shall include the following: records management, market research, inventory control management, and shipping/receiving of hardware, software, and materials required for the successful accomplishment of the mission. This support includes maintaining an up-to-date inventory of Government-owned software and hardware, to include warranties, licenses and maintenance agreements, as well as providing services for its storage, handling, servicing, and distribution.

During the performance of this contract, if any new/additional hardware, software or licensing is needed, the contractor shall coordinate the purchase with the COR and NCIS shall purchase any hardware, software and licensing required to perform the tasks of the PWS. All hardware, software and licensing is currently in place to continue the support for the LInX/D-DEx system.

3.19 Data Integration and Coding Language

The data integration and coding language needed for this contract is shown below:

Oracle for the Database

Oracle Web Logic, Global Scape and ESRI for Mapping

TOAD and SQL for Data

4. Travel

The Contractor shall be required to travel in order to meet requirements. The Government will reimburse the

Contractor for allowable travel costs incurred in performance of requirements and determined to be in accordance with the FAR subpart 31.2. Travel shall be first approved by the COR (NCIS LInX COR), and shall be within the specified travel ceiling.

The Contractor shall also be required to perform travel to NCIS Headquarters, Quantico, VA and various state and federal agencies to execute portions of the required tasks. Additionally, the Contractor shall be required to travel to or attend virtually, all planning and task review meetings held, at a minimum, on a bi-weekly basis. The location of these meetings will be at the NCIS HQ, Quantico, VA, or at agreed upon locations within the Metro DC area.

5. Contract Deliverables

The Contractor shall provide the following deliverables:

Deliverable Title Format Due Date

Design Documents As tasked At each design review in accordance with the IMS schedule

Architecture Documents DOD Architecture Framework

(DODAF) with tailoring authorized from the LInX Program

Management Office

At each design review in accordance with the IMS schedule

Data Model Output from a DM tool such as

ERWin

At each design review in accordance with the IMS schedule

Interface Documents Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

At each design review in accordance with the IMS schedule

Requirements Document Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

At each requirements review in accordance with the IMS schedule or when directed by the CCB.

Test Plan Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

At each requirements review in accordance with the IMS schedule.

Test Scenarios Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

14 days prior to the Test Readiness

Review

Operations Manual to include server Start/Stop, COTS/GOTS

Configuration settings

Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

Updates as required

Production Readiness Checklist Government Furnished Template Updates as required

Release Notices Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

5 days before release

User Manuals Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

5 days before release

Security Accreditation

Documentation

Government Furnished Templates Delivery during Test Phase as agreed upon by Government and

Contractor

Support Plan Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days after contract award

Hardware and Software Inventory Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

As changes occur

Production Management Reports Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

Quarterly

Online Help Documentation Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

Available 10 days prior to User

Acceptance Testing

Training Manual Updates Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

Available 10 days prior to User

Acceptance Testing

Lesson Plans Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days prior to training

Project Management Plan Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days after Task Order Issuance

Software Development Plan Content tailored from Appendix L of the Navy Guidebook for

Acquisition of Naval Software

Intensive Systems

30 days after Task Order Issuance

Risk Management Plan Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days after contract award

Quality Management Plan Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days after contract award

Quality Assurance Report Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days after contract award and then Semi-Annual updates

Communications Plan Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days after contract award

Weekly Status Meeting Agenda Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

1 day prior to meeting

Weekly Status Meeting Minutes Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

1 day after meeting

Centralized Management Operation

Center Report

Content as described in section 3.3.

Contractor format.

Quarterly after award

Front Porch Data Feed

Maintenance / Repair Report

Content as described in section 3.3.

Contractor format.

Quarterly after award

Hardware and Software Inventory for LINX Program

Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days after contract award and 30 days after changes occur

Hardware and Software

Maintenance

Contractor-Determined Format with tailoring authorized from the

LInX Program Management Office

30 days after changes occur

CLOUD Business Analysis Content as described in Section

3.13. Contractor format.

6-months after effective date of the contract

**NOTE: See attached CDRLs for specific details of each deliverable.

6. Place of Performance

The primary place of performance will be at the Contractor facility, with limited performance at NCIS Headquarters, Quantico, VA and/or Government furnished facilities located in Northern Virginia and Jacksonville, FL.

7. Ordering Period

The ordering period will be for five years starting on the execution date of the contract and expiring 60 months after.

8. Government-Furnished Equipment and Information

8.1 Government-Furnished Equipment

Government furnished property to be provided to the Contractor will include, but not be limited to:

Office facilities

Computer equipment

Software Licenses

When the Contractor is working in a Government facility, the Government will supply workspace, desktop computer dedicated to unclassified information, one or more desktop computers with access to the NCIS Local Area Network

(LAN) and any applicable shared drives or directories; NCIS e-mail accounts; telephones with voice mail, and access to the NIPRNET networks (all for official use only).

The Government will require all necessary security forms, and provide Common Access Cards (CACs) and other

DoD identification cards as needed to access Government facilities. Contract services can commence with

Government escort provided as needed while background checks and clearances are obtained.

9. Security

The data contained and managed by the D-DEx/LInX application is deemed Law Enforcement sensitive, but

Unclassified, however, access to the system requires a Secret clearance. The contractor’s facility will need a

“SECRET” clearance for the safeguarding of data during the performance of this contract.

All contractor personnel working within the system/database will need a “SECRET” clearance to perform under this contract. All other non-technical/administrative personnel does not need any clearance to perform under this contract.

The Contractor shall ensure all Contractor personnel are United States citizens with no criminal record. Personnel assigned must be U.S. citizens, per SECNAVINST 551-0.30A, paragraph 8-3. The Contractor employees shall be subject to facility access determination national agency check (FADNAC). All Contractor personnel must submit an

SF-86 for clearance processing within 30 days of contract award. All Contractor personnel must have a favorable

FADNAC.

All deliverables associated with this effort are “Unclassified” unless otherwise specified on the individual work order.

10. Service Contract Reporting

Services Contract Reporting (SCR) requirements apply to this contract. The contractor shall report required SCR data fields using the SCR section of the System for Award Management (SAM) at following web address: https://sam.gov/SAM/.

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://sam.gov/SAM/.

Qualification Requirements:

Program Manager (Level 3)

Education: BA or BS and 10 years of experience.

Duties: Provides oversight and direction for large or complex efforts. Provides strategic input, oversees budget, project delivery and management. Responsible for formulating and enforcing work standards, assigning contractor schedules, reviewing work discrepancies, and supervising project staff. Directs the development of project goals, work plans, timeliness, development and implementation of project strategies. Serves as the contractor's authorized https://sam.gov/SAM/ https://sam.gov/SAM/ interface with the contract level Contracting Officer's Representative (COR), government management personnel and partner agency representatives. Responsible for the overall contract performance.

Experience must be in support to law enforcement or similar information technology programs. Management and

Supervision experience relating to the design, development, integration, testing and fielding of law enforcement or similar systems and applications. Knowledgeable of DoD acquisition/contract policies and procedures.

Demonstrated ability to work with large and diverse teams and the ability to effectively provide guidance, direction, and supervision in all areas of contracted effort such as program management, systems maintenance, deployment, partner agency engagement, vendor management and financial management.

Project Manager (Level 2)

Education: minimum BA or BS and 10 years of experience.

Duties: Serves as the project manager for a task or set of tasks affecting the use and deployment of the LInX/D-DEx system and shall assist the Program Manager in working with the government management personnel and customer agency representatives. Under the guidance of the Program Manager, this individual is responsible for the overall management of the specific tasks and ensuring that the technical solutions, partner agency engagement and schedules in the task order are implemented in a timely manner. Performs program wide horizontal integration planning and interfaces with internal and external agencies to meet program goals. Experience related to law enforcement or similar communication systems and their operational use.

Project Manager (Technical)

Education: minimum BA or BS and 10 years of experience.

Duties: Responsible for the overall technical direction and management of the Program Operations, Maintenance, and Enhancements. Provides technical guidance over operations and maintenance and project implementation to include life cycle support. Establishes relationship with key stakeholders, partner agency technical teams, and support vendors. Supervises, leads, and directs technical teams and project activities. Responsible for assigning tasks, establishing and maintaining task/project schedules, and maintaining liaison between appropriate project personnel and the customer to ensure effective coordination of all project efforts. Demonstrated leadership skills in planning, organizing, leading, and controlling the technical activities of a project. Work with the ordering activity

Contracting Officer (CO), the contract level Contracting Officer’s Representative (COR), prepares and adheres to project cost, schedule and staffing plans, preparing plans, proposals, briefings and company representation with other government personnel and subcontractors as required. Performs business analysis, requirements gathering, develop testing strategy, test cases, documentation, and support User Acceptance Testing (UAT). Captures and reports project measurements, actions, risks and issues to the appropriate stakeholders. Support the Government

PMO on wide ranging technical matters and interagency engagements.

Network Engineer:

Education: Minimum BS or BA and 10 years of experience.

Duties: Maintain and control LInX/DDEx networks and associated computing environments like software for systems, software applications, equipment, and configurations. Running operations for disaster recovery and backups of data. Ensure data applications, and hardware are protected by organizing, preparing, and enforcing network security measures. Troubleshooting, diagnosing and solving hardware, software, and other issues affecting the network and device. Replacing defective hardware components of the network where possible.

Database Development Engineer:

Education: Minimum BA or BS and 10 years of experience

Duties: Maintaining and enhancing the performance of existing LInX/DDEx database programs. Assisting database development teams in designing new database programs that meet the system’s data storage needs. Monitor the

LInX/DDEx databases and related systems to ensure optimized performance. Writing new support programs and scripts to increase data storage.

Cloud Architect:

Duties: Develop and organize cloud system for the DDEx program. Create a well-informed cloud strategy and manage the adaption…