Suggested Answers to questions with MOCA comments.docx

1. Technical: SOW, Section 1.1 Question:Are there specific minimum system requirements (e.g., operating system, hardware specifications) for the software to run efficiently on MOCA’s infrastructure?

Answer: *The software must be able to integrate into MOCA's existing infrastructure, which includes Elasticsearch clusters. System requirements will depend on the scale of deployment, but the solution must be compatible with the current Elasticsearch architecture and capable of handling the ingestion and analysis of both structured and unstructured data (e.g., CSV, JSON, PDF, HTML). Additionally, the solution should leverage Elasticsearch’s capabilities to support real-time data processing and complex queries. Comment by user8:

*The system will support the Workflow management of all the transactions in the System and be able to allow the MOCA to introduce new workflows without the need for code changes or recompilations.

*The system will preserve data per the Government of Jamaica (GOJ) guidelines and Data Protection Act (DPA) of 2020.

*The system will ensure that personal data shall be processed fairly and lawfully and shall not be processed unless the criteria set out in the first standard of the Data Protection Act 2020 are met.

*The system shall provide an audit trail of all activities performed by all users of the system.

*The system shall have adequate safeguards in place to ensure the confidentiality and integrity of sensitive investigative data.

*The system will be designed for optimal performance, ensuring quick response times for searches, data analysis, and report generation.

*The system will be user-friendly and intuitive, allowing investigators to navigate the system and perform their tasks efficiently.

*The system will be compatible with MOCA's existing IT infrastructure, including operating systems, databases, and network protocols.

*The system will be scalable to accommodate future growth in data volume and user demand.

2. Technical: SOW, Section 1.2 Question:What level of integration is required with existing MOCA systems? Could you specify the platforms or tools with which the software needs to interface?

Answer: The software should integrate seamlessly with the existing Elasticsearch cluster, which serves as the central data repository. Additionally, it must be able to interface with other internal and external data sources, including Cellebrite, Nuix, Esri, Axiom, Intella, Videris, XRY etc or other platforms which produce data that would have to be ingestable by the platform listed in the requirements. The solution should support API or bulk data integration to ingest data from these platforms. Comment by user8: Axiom, Intella, Videris, XRY etc are other platforms which produce data that would have to be ingestable by the platform

3. Technical: SOW, Section 1.3 Question: Is there a preference for on-premise deployment, cloud-based solutions, or hybrid models?

Answer: MOCA prefers an on premises deployment as it would be hosted on a network that would be air-gapped from the internet.

4. Technical: SOW, Section 1.4 Question: Are there any mandated security standards or certifications (e.g., FIPS, ISO 27001) for the software?

Answer: The solution should comply with relevant security standards. Specific security certifications, such as ISO 27001, may be required to ensure the solution meets MOCA’s data security and privacy regulations. The solution must support encryption for data in transit (TLS) and adhere to other security best practices. Comment by user8:

Additionally the Solution shall support the following Elasticsearch security options:

Elasticsearch subscriptions (formerly X-Pack).

Search Guard.

Open Distro Security for Elasticsearch The Solution shall support LDAP and Active Directory authentication and authorization.

The Solution shall establish individual and role-level access control for UI components such as dashboards, visualizations, and saved searches.

The Solution shall implement restrictions on data access.

The Solution shall provide end-to-end encryption from the user interface to inter-cluster communications, including encrypted Elasticsearch.

The Solution shall provide authentication through methods including:

Active Directory/LDAP.

OpenID.

JWT.

The Solution shall enable user authorization through roles provided by the authentication method.

All data utilized by the Solution shall be encrypted, including data in transit between Elasticsearch and client components or between Elasticsearch nodes.

5. Technical: SOW, Section 1.5 Question:What investigative or intelligence-specific features are considered essential (e.g., link analysis, geospatial mapping, case management)?

Answer: The solution must support key investigative features, such as link analysis, geospatial mapping, and case management. The graph visualization tools should provide integrated link analysis, and the platform should allow for querying and displaying relationships across datasets. Geospatial mapping will be important for visualizing data in the context of physical locations. Data ingestion and analysis from various internal and external sources, Enhanced search capabilities, Link analysis and relationship visualization, Advanced reporting and knowledge sharing, Workflow automation and management and security and user access control Comment by user8: Data ingestion and analysis from various internal and external sources Enhanced search capabilities Link analysis and relationship visualization Advanced reporting and knowledge sharing Workflow automation and management Security and user access control

6. Technical: SOW, Section 1.6 Question: Should the software support multilingual capabilities, especially for languages commonly used in the region?

Answer: Yes, the solution must support multilingual capabilities, including natural language processing (NLP) for multiple languages. This includes language identification, tokenization, entity extraction, and the ability to handle non-English documents. The system should also support transliteration. Comment by user8:

The Solution shall support role-based access control on JDBC tables mapped to Elasticsearch indices.

The Solution shall fully integrate with Search Guard add-ons for field-level security, document-level security, and configuration management.

The Solution shall support TLS on the transport layer and REST API.

The Solution shall support pluggable authentication methods (LDAP, Kerberos, JWT, etc.).

The Solution shall support an adaptive user interface with per-role access rules.

The Solution shall support field-level anonymization for compliance with GDPR and Personally Identifiable Information (PII) protection standards.

The Solution shall support the following audit logging:

AUTHENTICATED - Logs successful user authentication GRANTED_PRIVILEGES - Logs successful requests to Elasticsearch.

FAILED_LOGIN - Logs failed login attempts due to incorrect credentials MISSING_PRIVILEGES - Logs access attempts without required permissions.

BAD_HEADERS - Logs attempts to spoof requests using internal headers.

SSL_EXCEPTION - Logs access attempts without a valid SSL/TLS certificate.

SG_INDEX_ATTEMPT - Logs attempts to access internal user and privilege indices without valid admin TLS certificates.

The Solution shall log user-performed actions.

The Solution shall log the following session data:

Actions performed by users, such as opening dashboards.

Access to system configuration objects, such as requesting dashboard configuration Data-related search queries, including fetching data for visualizations.

Queries that obtain document counts, such as fetching counts for dashboard data.

Export actions for data in JSON or CSV format Requests sent from the Dev Tools console.

Internal data-related queries, such as fetching license information

7. Technical: SOW, Section 1.7 Question: What specific reporting and data visualization tools are required for the software?

Answer: The software must include flexible reporting and data visualization capabilities. Key tools include:

· Record tables that can paginate, filter, and export results in formats like CSV or JSON.

· Graph visualizations for link analysis, with integrated relationship mapping.

· Customizable dashboards for different types of users, including executive-level dashboards.

· The ability to script actions in dashboards and automate data interactions.

8. Admin: General Information Question: How many users will require access to the software, and will licenses be named or concurrent?

Answer: Twenty users will require access, concurrent licenses. Comment by user8: Concurrent licenses are preferred

9. Admin: SOW, Section 2.1 Question: Is the contractor expected to provide training sessions for MOCA staff? If so, how many sessions, and should they be conducted on-site in Kingston?

Answer:The contractor is expected to provide training sessions for MOCA staff. One week of training on site in Kingston

10. Admin: SOW, Section 3.1 Question:What is the anticipated timeline for full deployment after contract award?

Answer:The anticipated timeline for full deployment is four months after contract award.

11. Admin: SOW, Section 3.2 Question:Are there specific requirements for local support, such as having a physical presence in Kingston or nearby regions?

Answer: It is likely that local support in Kingston will be necessary to address any issues with the deployment, particularly during the initial setup and training phases. This may require a physical presence or a local partner. The vendor must have a 24/7 capacity to receive and act on issues that the local administrator cannot resolve via immediate action. Performance standards in relation to resolution of issues should be in line with best industry standards and refined by negotiation if necessary. A Service Level Agreement is critical Comment by user8: This is desirable but not essential. The vendor must have a 24/7 capacity to receive and act on issues that the local administrator cannot resolve via immediate action. Performance standards in relation to resolution of issues should be in line with best industry standards and refined by negotiation if necessary. A Service Level Agreement is critical

12. Technical: SOW, Section 3.3 Question:Should ongoing maintenance and updates be included in the proposal, and if so, for what duration (e.g., 1 year, 3 years)?

Answer: Yes, the proposal should include maintenance and updates for at least 1 year, with the option to extend to 2 years. This includes bug fixes, system updates, and any required patches for security or functionality.

13. Admin: Evaluation Criteria Question:Will preference be given to software solutions with prior deployment in similar contexts (e.g., organized crime and anti-corruption agencies)?

Answer: Preference may be given to software solutions that have been successfully deployed in similar investigative or law enforcement contexts, particularly those related to organized crime or anti-corruption agencies. This prior experience would demonstrate the solution’s applicability to MOCA’s needs.

14. Admin: Evaluation Criteria Question: How will cost proposals be evaluated—based solely on price, or will features and functionality also weigh significantly?

Answer: Cost will likely be a significant factor, but features and functionality will also be critical. The perspective vendor’s proposal should strike a balance between cost-effectiveness and meeting the required technical specifications, particularly the investigative features, integration capabilities, and security requirements.

15. Admin: General Information Question: Are there specific export control or licensing requirements contractors should be aware of for deploying software in Jamaica?

Answer: Contractors should be aware of any export control laws or licensing requirements that apply to the export of software to Jamaica. The solution should comply with any applicable international trade regulations or licensing requirements for software deployment.

16. Admin: General Information Question:Can you clarify the invoicing and payment schedule for this contract?

Answer:Yearly subscription payments will be made. Typically, payments would be milestone-based, with invoices submitted upon completion of certain deliverables (e.g., installation, configuration, and training). Payment is made within thirty days after deliverables are received.

17. Cost: SOW, Section 4, Deliverables Question:Can installation and configuration be done remotely or needs to be onsite?

Answer:Installation and configuration can likely be done remotely, but there may be a need for on-site presence for initial setup and troubleshooting, particularly in the case of network or hardware integration with MOCA’s systems – Strongly encouraged on-site presence.

18. Cost: SOW, Section 4, Deliverables Question: Do you have target deadlines for deliverables?

Answer: The target deadlines for deliverables are not specified. The contractor should propose a reasonable timeline for completing major deliverables, including installation, configuration, training, and system deployment.

19. Cost: SOW, Section 4, Deliverables Question:Do they want all the installation and configuration done by the contractors, or is there some of their staff they want involved and in what capacity?

Answer: The solution should be implemented by the contractors, but MOCA staff may need to be involved in certain phases, such as training or assisting with integration into the existing infrastructure.

20. Cost: SOW, Section 4, Deliverables Question: Can the training be done remotely over Zoom or other video teleconferencing, or do they need to be onsite?

Answer: On site training is preferable

21. Technical: Section 3, Page 3 Question:Will this be on-premises / self-managed or in the cloud? If could, which cloud service provider (CSP)?

Answer: On premises deployment is preferred

22. Technical: Section 3, Page 3 Question:Is there existing infrastructure that this is currently running on that we need to integrate / leverage? Can you share specifics?

Answer: The solution will integrate with the existing Elasticsearch infrastructure. Specific details of the current setup can be shared with the contractor upon request.

23. Technical: Section 3, Page 4 Question:Can you share any specifics of how the current Elasticsearch cluster(s) are set up?

Answer: The current Elasticsearch setup serves as the primary data repository and is designed to support real-time data ingestion and analysis. The cluster supports a variety of input plugins, including those for structured data (e.g., CSV, JSON) and unstructured data (e.g., PDF, HTML). It is optimized for distributed joins, real-time processing, and caching of data. The specific configuration of nodes, indices, and existing data models within the cluster, however, has not been detailed in the provided documentation.

24. Technical: Section 3, Page 5 Question: What is the approximate daily ingest/data volume for this project?

Answer: The daily ingest/data volume for this project is not explicitly stated in the provided documentation. However, it is important for the contractor to assess the data streams from MOCA's systems and define data ingestion rates based on historical performance metrics. The contractor should also consider scalability and redundancy to ensure the system can handle any fluctuations in data volume as it scales over time.

25. Admin: Statement of Work, INL-Kingston, 191NLE25Q0013, INL Kingston Intelligence and Investigative Analytical Software for MOCA, SECTION 2.3 NOTICE OF SAM.GOV SYNOPSIS CLOSING DATE AND TIME, Page 3 Question:What is the page limit for the contractor's proposal?

Answer: The page limit for the contractor's proposal is typically stated in Section 2 of the Statement of Work or Proposal Instructions. Since this is not explicitly provided in the information at hand, you will need to refer directly to the "Proposal Instructions" section of the SOW to verify the exact page limit. If no limit is mentioned, the contractor should keep the proposal concise, clearly addressing all technical and administrative requirements.

26. Admin: Statement of Work (SOW), Intelligence and Investigative Analytical Software for MOCA, Place of Performance: Jamaica, Period of Performance: 2 Years. Third Party data provider, Vendor Instructions Question:As the Place of Performance is Jamaica, is the contractor expected to include a budgetary estimate for travel to Jamaica for its consultants to perform on this project?

Answer: Yes, since the Place of Performance is Jamaica, the contractor is expected to include a budgetary estimate for travel to Jamaica for consultants performing on the project. Contractors typically account for these expenses under "Other Direct Costs" (ODCs) or "Travel Costs" in their financial proposal, ensuring the budget covers the necessary travel logistics for the consultants to carry out project activities in Jamaica.