The file's text, extracted by GovTribe without its formatting.
IT Division 15
Source Management and Under Cover Modernization Performance Work Statement DRAFT – For AWARD in 09/2025
Table of Contents
| Table of Contents | 3 | |
| 1.0 | BACKGROUND | 4 |
| 2.0 | SCOPE | 4 |
| 3.0 | Project Management | 5 |
| 3.1 | Progress Reports | 5 |
| 4.0 | Technical Deliverables | 5 |
| 4.1 | Source Management Functional Requirements | 6 |
| 5.0 | Project Closeout | 6 |
| 6.0 | Production Maintenance | 6 |
| 7.0 | Deliverables | 6 |
| 7.1 | Schedule of Deliverables | 7 |
| 7.2 | Acceptance of Project Deliverables | 7 |
| 7.2.1 | Quality | 7 |
| 7.2.2 | Performance Details | 7 |
| Appendix A – Functional Requirements | 11 | |
BACKGROUND
The Naval Criminal Investigative Service (NCIS) is an organization of approximately 3000 personnel of which 850 serve at Headquarters and the remaining staff serve at offices worldwide. NCIS is the Department of the Navy (DoN) component with primary responsibility for criminal investigation, law enforcement (LE), counter-terrorism (CT), counterintelligence (CI), and physical and personnel security matters. NCIS has the 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, CI, and security matters with Federal, state, local law enforcement, facility security, and intelligence agencies. Reviewing the revised NCIS Charter known as SECNAVINST (Secretary of the Navy Instruction) 5430.107 will provide insight into NCIS roles and responsibilities. Additional information on NCIS can be found at our public website http://www.ncis.navy.mil.
Source Management is an integral capability related to NCIS core mission areas including Criminal Investigations, and Cyber Investigations. Sources are identified and managed by NCIS agents, as well as USMC and USN Criminal Investigators and provide valuable leads and data to forward the NCIS mission to investigate and defeat criminal, terrorists, and foreign intelligence threats while protecting the people, equipment, technology and infrastructure of the United States Navy and Marine Corps.
The vision for the Source Management System is to provide a web-based common solution for NCIS agents worldwide. The solution selected will be installed on the unclassified (NIPR) network.
SCOPE
The scope of this Performance Work Statement (PWS) includes all software licensing, services and written material necessary to install, integrate data and business processes, and configure and sustain both a source management application (CSM), and an Under Cover Management (UC) application (all are COTS solutions known commercially on the GSA schedule). On the NCIS Unclassified network (NIPR), both an installation of CSM and UC will be included. Additionally, on the NCIS Secret network (SIPR), an installation of UC will also be included. Licensing will include the rights to install 3 environments for each application, which are Train, Test, and Production. Written materials in support of the applications, and ongoing production support onsite and/or via remote login, via phone, and email during the period of performance is to be included.
The Government will provide the hardware (servers) and hands-on system administration to work collaboratively with the contractor provided labor necessary to maintain/upgrade/enhance/remediate the software on the networks as Government Furnished Equipment. The primary location of performance is NCIS Headquarters, Russell Knox Building, 27130 Telegraph Road, Quantico, VA 22134. There may be some development and support activities, as well as program management activities that will occur off-site with government concurrence.
The contractor shall provide support for the installation, and tailoring of the application to meet NCIS business requirements. The contractor shall provide documentation for the installation, and operations of the system to include Standard Operating Procedures for the Start/Stop of the application, database, and servers, backup procedures, restore procedures, as well as troubleshooting and escalation procedures for support to be provided by the contractor when required under contract.
Project Management Progress Reports The contractor shall provide no less than bi-weekly progress reports for each task listed under section 4 of this PWS. The progress reports shall detail completed and remaining activities, completion metrics, and areas of concern. Other topics may be included at the government’s discretion or with government consent.
Technical Deliverables Utilizing standard industry methodology and best practices, the contractor shall assist (side by side) government led systems administrators to perform all necessary activities to complete the provisioning of servers, installation, configuration to include both applicable DoD Security Technical Implementation Guides (STIGs), and functional configuration of application related items, such as user interface, data, workflow, and reports.
a. Licensing of Software Products – The contractor shall provide Investigative Tool software license for the installation of 3 environments (Test/Train/Prod) on NIPR for the 3 applications (1 CSM, and 2 UC). The environments will be utilized for testing, training, and production on the network. The government will furnish the license(s) for the server operating system(s), application platform, and database platform.
b. Maintain the application that is written on the Microsoft .Net platform.
c. Deliver software enhancements and defect corrections on a regular schedule as agreed upon with the government throughout the period of performance.
d. Support for DoD Security Technical Implementation Guides (STIGs) – The contractor shall provide support and collaborate with NCIS system administrators in the installation and ongoing maintenance of DoD STIGs.
e. Integration Activities – The contractor shall work closely with NCIS agents and analysts to configure the user interface (UI), workflow(s), approval(s), and reports.
f. Ongoing Maintenance and Support – The contractor shall provide Standard Operating Procedures for communicating with the contractor to report defects, and to request enhancements throughout the period of performance.
Source Management Functional Requirements See Appendix A – Functional Requirements Under Cover Management Functional Requirements See Appendix B – Functional Requirements
Project Closeout The contract shall coordinate and provide a briefing on the project close out activities within thirty (30) days of closeout. Project closeout activities shall include:
a. Final Product Acceptance Checklist
b. Project Artifacts Checklist
c. Lessons Learned
d. Post-Implementation Plan(s)
e. Documented Open Issues Production Maintenance The contractor shall coordinate and provide a knowledge transfer of the following information:
a. The contractor shall document all standard operations procedures to be executed by NCIS IT staff in support of the system.
b. The contractor shall document all service levels to be achieved in the support of the system.
Deliverables All information, records, data, files, documents, and work papers obtained or created in support of this PWS shall become, and remain, the property of the Government and shall be returned or disposed of in accordance with the Contracting Officer’s Representative’s (COR) instructions at the conclusion of this contract.
Deliverables developed under this contract shall be delivered as indicated in Section 4.1, Schedule of Deliverables.
The contractor shall obtain, store, maintain and reproduce the required source code, technical data and applicable documents, plans, regulations, specifications, and other pertinent data as appropriate for fulfilling the tasks described in this PWS. When appropriate procedures exist, the contractor shall acquire the above information directly; however, in instances where the data and/or procedures are to be created, the contractor is expected to follow procedures once they are approved by the Government and made available. The contractor shall obtain these data from both Government and non-Government sources.
The contractor shall provide the Government or other agencies, as approved by the COR, access to any and all program information and data prepared or obtained as part of this contract or in support of any tasking of this PWS.
Section 508 of the Rehabilitation Act requires Federal agencies to make their electronic and IT accessible to people with disabilities. This applies to all Federal agencies when they develop, procure, maintain, or use electronic and IT.
All electronic and information technology (EIT) procured through this effort must meet the applicable accessibility standards specified in 36CFR1194.2, unless an agency exception to this requirement exists.
Government has made the following schedule, however; changes can be made with concurrence with both contractor and Government approval.
Schedule of Deliverables
| No. |
| Item |
| PWS Paragraph |
| Format |
| Due Date |
| 1 |
| Progress Reports |
| 3.1 |
| Contractor Format |
| Bi-Weekly |
| 2 |
| Functional Software Enhancements |
| 4.0 (C) |
| NA |
| Ongoing |
| 3 |
| Provide Certification and Accreditation document support |
| 4.0 (D) |
| Government Provided Format |
| Ongoing |
| 3 |
| Quality Assurance Surveillance Plan |
| 4.3 |
| Contractor Format |
| Ongoing |
Acceptance of Project Deliverables The COR will review contractor deliverables in accordance with specifications and standards identified during the contract kick-off meeting, any directives issued by the COR or ACOR during the life of this contract, and the Quality Assurance Surveillance Plan (QASP). Deliverables will be submitted to the COR. The acceptance of deliverables and satisfactory work performance, required herein, shall be based upon the timeliness and accuracy of the deliverables as described in the QASP. Only the Contracting Officer and/or COR that initiated a specific tasking has the authority to accept or reject associated deliverables.
0. Quality The contractor shall provide internal quality assurance IAW via the Quality Assurance Surveillance Plan.
The Government will provide quality assurance surveillance in accordance with the Government QASP.
0. Performance Details Period of Performance The period of performance for the PWS is for a base year, plus four option years.
Place of Performance Approved Contractor Locations- Telework can be authorized on a case by case for the contractor when deliverables are unclassified. If telework authorization is changed/revoked, then the contractor will be required to work at NCIS facilities.
The primary place of performance for this effort shall be either:
Headquarters Naval Criminal Investigative Service Russell-Knox Building 27130 Telegraph Road Quantico, VA 22134 NCIS New York Resident Unit (NENY) 201 Varick Street, #1009 New York, New York 1001407053
Travel Performance under this contract shall require occasional travel by Contractor personnel. The Government will reimburse the Contractor for allowable travel costs incurred by Contractors in performance of the contract and determined to be in accordance with the FAR subpart 31.2. Travel shall be first approved by the COR, and shall be within the specified travel ceiling.
The Contractor will also be required to perform travel to NCIS Headquarters, Quantico, VA.
Reimbursement of travel expenditures
(a) Travel
| (1) Area of Travel. Performance under this contract may require travel by contractor personnel. If travel, domestic or overseas, is required, the contractor is responsible for making all needed arrangements for the contract personnel. This includes but is not limited to the following: |
| Medical Examinations |
| Immunization |
| Passports, visas, etc. |
| Security Clearances |
All contractor personnel required to perform work on any U.S. Navy vessel will have to obtain boarding authorization from the Commanding Officer of the vessel prior to boarding.
(2) Travel Policy. The Government will reimburse the contractor for allowable travel costs incurred by the contractor in performance of the contract and determined to be in accordance with FAR subpart 31.2, subject to the following provisions:
Travel required for tasks assigned under this contract shall be governed in accordance with rules set forth for temporary duty travel in FAR 31.205-46.
(3) Travel. Travel, subsistence, and associated labor charges for travel time are authorized, whenever a task assignment requires work to be accomplished at a temporary alternate worksite.
Travel performed for personal convenience and daily travel to and from work at contractor's facility will not be reimbursed.
(4) Per Diem. Per diem for travel on work assigned under this contract will be reimbursed to employees consistent with company policy, but not to exceed the amount authorized in the Department of Defense Joint Travel Regulations.
(5) Shipboard Stays. Whenever work assignments require temporary duty aboard a government ship, the contractor will be reimbursed at the per diem rates identified in paragraphs C8101.2C or C81181.3B(6) of the DOD Joint Travel Regulations, Volume 2.
(6) Air/Rail Travel. In rendering the services, the contractor shall be reimbursed for the actual costs of transportation incurred by its personnel not to exceed the cost of tourist class rail, or plane fare, to the extent that such transportation is necessary for the performance of the services hereunder and is authorized by the Ordering Officer. Such authorization by the Ordering Officer shall be indicated in the order or in some other suitable written form.
NOTE: To the maximum extent practicable without the impairment of the effectiveness of the mission, transportation shall be tourist class. In the event that only first class travel is available, it will be allowed, provided justification therefore is fully documented and warranted.
(7) Private Automobile. The use of privately owned conveyance within the continental United States by the traveler will be reimbursed to the contractor at the mileage rate allowed by Joint Travel Regulations. Authorization for the use of privately owned conveyance shall be indicated on the order. Distances traveled between points shall be shown in standard highway mileage guides. Any deviations from distance shown in such standard mileage guides shall be explained by the traveler on his expense sheet.
(8) Car Rental. The contractor shall be entitled to reimbursement for car rental, exclusive of mileage charges, as authorized by each order, when the services are required to be performed outside the normal commuting distance from the contractor's facilities. Car rental for TDY teams will be limited to a rate of one car for every four (4) persons on TDY at one site.
Certifications
Contractor staff members performing work under this PWS and performing functions specified in SECNAV M-5239.2, shall be transitioned from the previous Information Assurance Workforce structure to the Cyber IT/Cybersecurity Workforce (Cyber IT/CSWF) structure. The Cyber IT/CSWF is managed by the Cyber IT/CSWF Program Manager (Cyber IT/CSWF PM). Contractor support personnel assigned to perform cyberspace specialty tasks must meet qualification standards established in the DON Cyber IT/CSWF Program requirements of the Information Assurance (IA) categories in the DoD 8570.01-M are the only standard for determining whether IA work is being accomplished and what commercial certifications are required. As DoD and DON guidance is determined for CSWF for contract personnel the contractors will comply with the latest guidance. The current DON guidance is derived from SECNAV M-5239.2 Appendix 4. Contractor positions are expected to be designated Cyber IT/CSWF and at that time the positions will be assigned a specialty code within one of five categories - Security Provision, Operate and Maintain, Protect and Defend, Investigate, Oversee and Govern. Contractor personnel must have a baseline certification prior to reporting but are allowed six months from reporting to acquire specialty code related training. All training is the sole responsibility of the contractor employee and/or contractor employer. Each Authorized, Enhanced and Core User of DON, including contractors, must maintain the appropriate security clearance, have a current user access agreement, have an appointment letter designating Cyber IT/CSWF and if applicable, a Privileged Access Agreement and have completed approved cybersecurity awareness training prior to accessing DON networks. Any deviation or waivers of qualifications must be reviewed on a case by case basis by the Cyber IT/CSWF PM and approved by the Senior Security Officer.
Security Requirements The Contractor shall be a United States Contractor, licensed, chartered, or incorporated in the United States and personnel shall possess a valid DoD SECRET clearance.
A DD254 will be processed to address other security concerns.
Hours Unless otherwise noted or coordinated, onsite Government facility hours are from 0700-1600 local time.
Federal Holidays The Government observes the following Federal Holidays: New Year’s Day, Martin Luther King’s Birthday, George Washington’s Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, and Christmas Day. If the holiday falls on Sunday, it will be observed on the Monday immediately following the holiday. If the holiday falls on Saturday, it will be observed on the immediately preceding Friday.
Points of Contact Contract Specialist:
COR:
TBD
Source Management and Under Cover Modernization PWS
Source Management and Under Cover Modernization PWS
Appendix A – Source Management Functional Requirements Note regarding requirements: The requirements listed are a representative sample at the time the PWS was written. This is a living document in that the list is managed and updated through the Agile Methodology Systems Development Lifecycle utilized throughout the duration of development activities in the execution of the contract.
| Requirement ID |
| Requirement Description |
| Requirements Category |
| Requirements Mapping |
| BR-1 |
| Deliver and maintain unclassified CRIM source management system. |
| CRIM_SRC |
| FR-1,FR-2, FR-3 |
| FR-1 |
| Must be hosted on NIPR. |
| CRIM_SRC |
| BR-1 |
| FR-2 |
| Must authenticate with CAC |
| CRIM_SRC |
| BR-1 |
| FR-3 |
| Must allow for administrative deactivation of user accounts |
| CRIM_SRC |
| BR-1 |
| BR-2 |
| System must provide user access control (user management). |
| NCIS |
| FR-5, FR-6, FR-7, FR-8, FR-9, FR-10 |
| FR-5 |
| User access must be role based. Roles are: Administrator, Desk Officer (DO) – CRIM, Desk Officer (DO) – National Security Directorate (NSD), Executive Assistant Director, Atlantic (EADLANT), Executive Assistant Director, Pacific (EADPAC), Field Office (FO) Administrator, Read-Only User, Handler, Special Agent-in-Charge (SAC), Assistant Special Agent-in-Charge (ASAC), Special Intelligence Officer (SIO), Supervisory Special Agent (SSA), Supervisor, Analyst, Global (OSP, OSS, Cyber); Code 11; Code 15. |
| NCIS |
| BR-2 |
| FR-6 |
| Need to be able to assign one or more office codes to each user. |
| NCIS |
| BR-2 |
| FR-7 |
| Administrators and FO (Field Office) Administrators must be able to view, add, edit, re-activate, and de-activate users. |
| NCIS |
| BR-2 |
| FR-8 |
| Reassign source handler |
| NCIS |
| BR-2 |
| FR-9 |
| System will automatically deactivate users after 60 days of login inactivity |
| NCIS |
| BR-2 |
| FR-10 |
| Must be able to search the list of users. |
| NCIS |
| BR-2 |
| BR-3 |
| System must have the ability to manage source data. |
| NCIS |
| FR-11 |
| FR-11 |
| System must be all inclusive, to include messaging and notification to users (de- confliction, anomalies, update source, etc.) |
| NCIS |
| BR-3 |
| BR-4 |
| System must have the ability to support up to 2000 active users. |
| NCIS |
| FR-12, FR-13 |
| FR-12 |
| System must support 600 concurrent users. |
| NCIS |
| BR-4 |
| FR-13 |
| System must support 365 days, 24 hours availability. |
BR-4
| BR-5 |
| System must have internal deconfliction. |
| NCIS |
| FR-14 |
| FR-14 |
| Internal – when a source (all) is entered biographic data is checked against existing for possible duplicate. |
| NCIS |
| BR-6 |
| BR-6 |
| System must be secure. (see B-1 and B-2 ) |
| NCIS |
| FR-15 |
| FR-15 |
| Secure URLs, Hashed passwords, data encrypted at rest, PII, System is backed-Up. |
| CRIM_SRC |
| BR-6 |
| BR-7 |
| System must be capable of handling different file types and large volumes of data. |
| NCIS |
| FR-17 |
| FR-17 |
| PDFs, PDFs w/special handling instructions (Controlled Unclassified Information (CUI)), Word Docs, Excel, PNG, BMP, video file support, PPTs, Data entry, jpegs, GIFs. Electronic fingerprint file (EFT). |
| CRIM_SRC |
| BR-8 |
| BR-8 |
| System must be able to create reports on all data (as there should be search options for many data points.) |
| NCIS |
| FR-18, FR-19, FR-20 |
| FR-18 |
| Source Productivity Report, Supervisor Timeliness Report, Missing NFN Report |
| NCIS |
| BR-8 |
| FR-19 |
| System must be able to generate customized reports via VITALS and PowerBI |
| NCIS |
| BR-8 |
| FR-20 |
| System must allow user option for auto- generated emails notifications, alerts and reports |
| NCIS |
| BR-8 |
| BR-9 |
| System must be able to integrate/communicate with other major NCIS systems (i.e. CLEOC, NJIS, VITALS, RIMS/C-RIMS, etc.). |
| NCIS |
| FR-21 |
| FR-21 |
| Closed source files must be transferrable to RIMS. |
| NCIS |
| BR-9 |
| BR-10 |
| System must be interoperable with geospatial capabilities. |
| NCIS |
| FR-22 |
| FR-22 |
| System must use maps to display source employer locations on multiple addresses and placement areas |
| NCIS |
| BR-10 |
| BR-11 |
| System must have robust search capability. |
| NCIS |
| FR-30, FR-31, FR- |
32, FR-33, FR-34, FR-35
| FR-30 |
| Quick search: Available from each screen. Searches source numbers, source last name, office codes. |
| NCIS |
| BR-11 |
| FR-31 |
| System must be configured to search Bio-data minus the name |
| NCIS |
| BR-11 |
| FR-32 |
| Advanced search: search by name, office code, source number, status (opened or closed), handler, date range (open or closed), source level, and Potential One-Time Source (POSO) |
| NCIS |
| BR-11 |
| FR-33 |
| System must be configured to search Utilization Records (UR) |
| NCIS |
| BR-11 |
| FR-34 |
| System must be configured to search contents of attached files. |
| NCIS |
| BR-11 |
| FR-35 |
| System must be configured to export search data. |
| NCIS |
| BR-11 |
| BR-12 |
| System must be able to link sources |
| NCIS |
| FR-36, FR-37 |
| FR-36 |
| System must be able to link multiple IIRs and CCNs to one source. |
| NCIS |
| BR-12 |
| FR-37 |
| System must be configured to add multiple source numbers (FBI, CID, OSI) |
| NCIS |
| BR-12 |
| BR-13 |
| The system must be cloud compatible. |
| NCIS |
| FR-38, FR-39 |
| FR-38 |
| The application architecture must be compatible with the Microsoft Azure IL5 cloud platform provided by the US Navy. |
| NCIS |
| BR-13 |
| FR-39 |
| If cloud capacity is funded, the vendor must provide systems integrator support to fully install and configure the application in the Microsoft Azure IL5 cloud platform provided by the US Navy. |
| NCIS |
| BR-13 |
| BR-14 |
| The system must be mobile device compatible |
| NCIS |
| FR-40, FR-41, FR-42 |
| FR-40 |
| The application must be fully functional on an Apple or Android device that is managed and configured by a DOD approved Mobile Device Manager such as DISA DMUC, or Flank Speed Intune. |
| NCIS |
| BR-14 |
| FR-41 |
| The vendor must provide systems integrator support to create a mobile Application on Apple IOS devices for use by NCIS agents on government authorized mobile devices. |
| NCIS |
| BR-14 |
| FR-42 |
| The vendor must provide systems integrator support to create a mobile Application on Android devices for use by NCIS agents on government authorized mobile devices. |
| NCIS |
| BR-14 |
Appendix B – Under Cover Management Functional Requirements Note regarding requirements: The requirements listed are a representative sample at the time the PWS was written. This is a living document in that the list is managed and updated through the Agile Methodology Systems Development Lifecycle utilized throughout the duration of development activities in the execution of the contract.
| Requirement ID |
| Requirement Description |
| Requirements Category |
| Requirements Mapping |
| BR-1 |
| Deliver and maintain Under Cover management system. |
| CRIM_UC |
| FR-1,FR-2, FR-3 |
| FR-1 |
| Must be hosted on NIPR.and SIPR |
| CRIM_UC |
| BR-1 |
| FR-2 |
| Must authenticate with CAC or SIPR PIV (respective of network) |
| CRIM_UC |
| BR-1 |
| FR-3 |
| Must allow for administrative deactivation of user accounts |
| CRIM_UC |
| BR-1 |
| BR-2 |
| System must provide user access control (user management). |
| NCIS |
| FR-5, FR-6, FR-7, FR-8, FR-9, FR-10 |
| FR-5 |
| User access must be role based. Roles are: Administrator, Desk Officer (DO) – CRIM, Desk Officer (DO) – National Security Directorate (NSD), Executive Assistant Director, Atlantic (EADLANT), Executive Assistant Director, Pacific (EADPAC), Field Office (FO) Administrator, Read-Only User, Handler, Special Agent-in-Charge (SAC), Assistant Special Agent-in-Charge (ASAC), Special Intelligence Officer (SIO), Supervisory Special Agent (SSA), Supervisor, Analyst, Global (OSP, OSS, Cyber); Code 11; Code 15. |
| NCIS |
| BR-2 |
| FR-6 |
| Need to be able to assign one or more office codes to each user. |
| NCIS |
| BR-2 |
| FR-7 |
| Administrators and FO (Field Office) Administrators must be able to view, add, edit, re-activate, and de-activate users. |
| NCIS |
| BR-2 |
| FR-8 |
| Reassign Under Cover resources |
| NCIS |
| BR-2 |
| FR-9 |
| System will automatically deactivate users after 60 days of login inactivity |
| NCIS |
| BR-2 |
| FR-10 |
| Must be able to search the list of users. |
| NCIS |
| BR-2 |
| BR-3 |
| System must have the ability to manage Under Cover data. |
| NCIS |
| FR-11 |
| FR-11 |
| System must be all inclusive, to include messaging and notification to users (de- confliction, anomalies, update, Under Cover, etc.) |
| NCIS |
| BR-3 |
| BR-4 |
| System must have the ability to support up to 2000 active users. |
| NCIS |
| FR-12, FR-13 |
| FR-12 |
| System must support 600 concurrent users. |
| NCIS |
| BR-4 |
| FR-13 |
| System must support 365 days, 24 hours availability. |
BR-4
| BR-5 |
| System must have internal deconfliction. |
| NCIS |
| FR-14 |
| FR-14 |
| Internal – when a Under Cover resource (all) is entered biographic data is checked against existing for possible duplicate. |
| NCIS |
| BR-6 |
| BR-6 |
| System must be secure. (see B-1 and B-2 ) |
| NCIS |
| FR-15 |
| FR-15 |
| Secure URLs, Hashed passwords, data encrypted at rest, PII, System is backed-Up. |
| CRIM_UC |
| BR-6 |
| BR-7 |
| System must be capable of handling different file types and large volumes of data. |
| NCIS |
| FR-17 |
| FR-17 |
| PDFs, PDFs w/special handling instructions (Controlled Unclassified Information (CUI)), Word Docs, Excel, PNG, BMP, video file support, PPTs, Data entry, jpegs, GIFs. Electronic fingerprint file (EFT). |
| CRIM_UC |
| BR-8 |
| BR-8 |
| System must be able to create reports on all data (as there should be search options for many data points.) |
| NCIS |
| FR-18, FR-19, FR-20 |
| FR-18 |
| Source Productivity Report, Supervisor Timeliness Report, Missing NFN Report |
| NCIS |
| BR-8 |
| FR-19 |
| System must be able to generate customized reports via VITALS and PowerBI |
| NCIS |
| BR-8 |
| FR-20 |
| System must allow user option for auto- generated emails notifications, alerts and reports |
| NCIS |
| BR-8 |
| BR-9 |
| System must be able to integrate/communicate with other major NCIS systems (i.e. CLEOC, NJIS, VITALS, RIMS/C-RIMS, etc.). |
| NCIS |
| FR-21 |
| FR-21 |
| Closed source files must be transferrable to RIMS. |
| NCIS |
| BR-9 |
| BR-10 |
| System must be interoperable with geospatial capabilities. |
| NCIS |
| FR-22 |
| FR-22 |
| System must use maps to display source employer locations on multiple addresses and placement areas |
| NCIS |
| BR-10 |
| BR-11 |
| System must have robust search capability. |
| NCIS |
| FR-30, FR-31, FR- |
32, FR-33, FR-34, FR-35
| FR-30 |
| Quick search: Available from each screen. Searches source numbers, source last name, office codes. |
| NCIS |
| BR-11 |
| FR-31 |
| System must be configured to search Bio-data minus the name |
| NCIS |
| BR-11 |
| FR-32 |
| Advanced search: search by name, office code, source number, status (opened or closed), handler, date range (open or closed), source level, and Potential One-Time Source (POSO) |
| NCIS |
| BR-11 |
| FR-33 |
| System must be configured to search Utilization Records (UR) |
| NCIS |
| BR-11 |
| FR-34 |
| System must be configured to search contents of attached files. |
| NCIS |
| BR-11 |
| FR-35 |
| System must be configured to export search data. |
| NCIS |
| BR-11 |
| BR-12 |
| System must be able to link sources |
| NCIS |
| FR-36, FR-37 |
| FR-36 |
| System must be able to link multiple IIRs and CCNs to one source. |
| NCIS |
| BR-12 |
| FR-37 |
| System must be configured to add multiple source numbers (FBI, CID, OSI) |
| NCIS |
| BR-12 |
| BR-13 |
| The system must be cloud compatible. |
| NCIS |
| FR-38, FR-39 |
| FR-38 |
| The application architecture must be compatible with the Microsoft Azure IL5 cloud platform provided by the US Navy. |
| NCIS |
| BR-13 |
| FR-39 |
| If cloud capacity is funded, the vendor must provide systems integrator support to fully install and configure the application in the Microsoft Azure IL5 cloud platform provided by the US Navy. |
| NCIS |
| BR-13 |
| BR-14 |
| The system must be mobile device compatible |
| NCIS |
| FR-40, FR-41, FR-42 |
| FR-40 |
| The application must be fully functional on an Apple or Android device that is managed and configured by a DOD approved Mobile Device Manager such as DISA DMUC, or Flank Speed Intune. |
| NCIS |
| BR-14 |
| FR-41 |
| The vendor must provide systems integrator support to create a mobile Application on Apple IOS devices for use by NCIS agents on government authorized mobile devices. |
| NCIS |
| BR-14 |
| FR-42 |
| The vendor must provide systems integrator support to create a mobile Application on Android devices for use by NCIS agents on government authorized mobile devices. |
| NCIS |
| BR-14 |
Appendix C: Acronyms
| ACOR |
| Alternate Contracting Officer’s Representative |
| C&A |
| Certification & Accreditation |
| cDOT |
| Clustered Data ONTAPP |
| CONUS |
| Continental United States |
| COR |
| Contracting Officer’s Representative |
| COTS |
| Commercial Off-The-Shelf |
| COTR |
| Contracting Officer’s Technical Representative |
| CSP |
| Counterintelligence Security Polygraph |
| DCV |
| Data Center Virtualization |
| DON |
| Department of the Navy |
| EIT |
| Electronic and Information Technology |
| FR |
| Functional Requirement |
| FAR |
| Federal Acquisition Regulation |
IAVA
IAW
Information Assurance Vulnerability Alerts In Accordance With
| IT |
| Information Technology |
| JTR |
| Joint Travel Regulation |
| MTU |
| Maximum Transmission Unit |
| NCIE |
| NetApp Certified Implementation Engineer |
| NCIS |
| Naval Criminal Investigative Service |
| NISPOM |
| National Industrial Security Program Operating Manual |
| OCONUS |
| Outside Contiguous United States |
PWS
QASP
Performance Work Statement Quality Assurance Surveillance Plan
| SRM |
| Site Recovery Manager |
STIG
TB
Security Technical Implementation Guide Terabyte
| UCS |
| Unified Computing System |
| UCSM |
| Unified Computing System Manager |
| VCP |
| VMware Certified Professional |
| VEM |
| Virtual Ethernet Module |
| VI |
| Virtual Infrastructure |
| VSM |
| VMware Service Manager |
Source Management and Under Cover Modernization PWS 12 image1.png