€¦ · web viewpage 42, section 3.11, pm.7 - please clarify if pmbok should be the abbreviation...

QUESTIONS AND RESPONSES #1SOLICITATION: DPSCS IT&CD 2006-17

MAFIS Replacement

March 10, 2006

Vendors:

The List of Questions and Responses #1 is being issued to clarify certain information contained in the above named RFP. The statements and interpretations of contract requirements which are stated in the following questions of potential offerors are not binding on the State, unless the State expressly amends the RFP. Nothing in the State’s responses to these questions is to be construed as agreement or acceptance by the State of any statement or interpretation on the part of the vendor asking the question as to what the contract does or does not require.

1. 1, Section 1.9 - Please confirm that the original versions of the technical and financial proposals should be submitted unbound (i.e., not hole-punched, not in binders).

Response: Section 1 paragraph 1.9 indicates that the original and seven (7) ‘bound’ copies be provided. The original must also be bound. The State prefers that ‘bound’ be interpreted as placed into three ring binders or similar products.

2. Page 13, Section 1.18 - In this section of the RFP, it is indicated that confidential/proprietary information should be placed after the Title Page and before the Table of Contents. Does this mean that the confidential/proprietary information should not be included within the sections that it applies to?

For example, if we need to include a few paragraphs of confidential/proprietary information as part of our response to Tab I, should that information be omitted from our response in Tab I and only be included in the section after the Title page? If this is the case, how should we indicate within Tab I that information has been omitted and can be found in the section behind the Title Page?

Response: Section 1, paragraph 1.18 is a minimal requirement for vendors to follow. This is to protect the proprietary nature of your products or services. At your discretion, you may provide additional verbiage within the specific sections of your proposals to outline confidential/proprietary information. All confidential and proprietary information must be listed as outlined in Section 1.18 so the State can easily identify where the data exists within your proposal without viewing the entire document.

1 of 24 5/20/2023MAFIS Replacement Questions and Responses #1

Department of Public Safety and Correctional Services

Information Technology & Communications DivisionPost Office Box 5743 • Pikesville, Maryland 21282-5743

Main №: 410-585-3100 • Facsimile №: 410-764-4035 • www.dpscs.state.md.usSTATE OF MARYLAND

ROBERT L. EHRLICH, JR.GOVERNOR

MICHAEL S. STEELELT. GOVERNOR

MARY ANN SAARSECRETARY

G. LAWRENCE

FRANKLINDEPUTY SECRETARY

MARY L. LIVERS, Ph.D.DEPUTY SECRETARY

RONALD C. BROTHERSACTING CHIEF

INFORMATION OFFICER

http://www.dpscs.state.md.us/

3. Minimum requirement 2 discusses multi-finger matching and references requirement T.17, regarding a “best of 6” search. Should this section also address latent searching and use of multiple records per subject and searching of both flat and rolled impressions (e.g., searching latent fingers against all 20 fingers)?

Response: The minimum requirement #2 refers to multi-finger matching which is in support of increased accuracies of tenprint searches. Minimum requirement #3 refers to the utilization of both flat and rolled impressions in support of increased latent accuracy.

4. 2, Section 3.2 - The fourth paragraph on the page states; “The State has purchased 10 Cardscans to change this workflow into a single submission….. These Cardscans will be in place prior to the implementation of the new AFIS.”

Can the State identify the vendor of these Cardscan devices and provide information on the hardware and software architecture to include the communication protocols supported?

Response: The 10 cardscans indicated have been purchased from Sagem Morpho, Inc. The relevant issue of hardware and software architecture is; the cardscans will send a NIST package to the Transaction Controller via SMTP. This process operates similarly to any livescan product on the market.

5. Page 27, Section 3.4 - The first paragraph states; “The project shall incorporate several new technologies to include: distributed computing, browser-based interfaces, TCP/IP communications protocol, latent palm matching, image capture, software matching (emphasis added) and relational database software.”

Can the State confirm that fingerprint matching solutions based upon only a software-based matching approach is required, or will Vendors be permitted to propose a solution utilizing hardware-based accelerators to provide improved economy of scale?

Response: It is the States preference to strongly consider a software matching solution. We currently operate with a hardware-based process and, however dated, we feel is not the best method. We are open to hardware solutions but we have experienced problems in the past keeping hardware matchers on currently available hardware and operating systems. As a result, we insist a detailed definition of a vendors’ process to maintain current hardware and operating systems for the matcher computer(s) be provided within the proposal.

6. Page 27, Section 3.5 - Mention is made that “When required, the Contractor shall perform on-site work for all central AFIS concerns at or within 30 miles of the following location:” Also, there is a statement that for the Transaction Controller, “all development will be conducted at the DPSCS office”. Is the intent that the work for any part of the contract be performed within 30 miles of the DPSCS office, or that the contractor will have to have its development personnel actually perform the development at the DPSCS office? If work must be done at the office, what facilities will be available (space, IT, etc.) for the contractor?

Response: The intent of Section 3 paragraph 3.5 is to provide a broad overview of where our primary work area is in support of the design and implementation of the products outlined in this solicitation. Our primary data center is located in close proximity to the DPSCS IT& CD offices. All design, document reviews, testing and


status meetings will be held within this 30 mile radius. The State understands that the products developed and maintained by the vendor will be done at a location outside of this 30 mile radius. However, the Transaction Controller will become property of the State of Maryland upon acceptance. As indicated, the State prefers to have this development work done within close proximity (30 miles) of the DPSCS office. This will allow State involvement in the development of the product, allowing an effective knowledge transition to the State. If a vendor feels this cannot be done, please ensure a detailed approach outlining the knowledge transfer process within your proposal.

7. Page 28, Section 3.5 - Table 3.5-1 identifies 41 workstations located at 10 sites. Section 2.2.2, T.3 requires 22 tenprint workstations, Section 2.2.3, L4 requires 26 latent workstations, for a total of 48 workstations. Please clarify the discrepancy between these numbers.

Response: The intent of Table 3.5-1 was to outline the production components and the locations and quantities of each component. The numbers of workstations required for this procurement are a total of 48 each. The distribution of these workstations is: 26 Remote Latent sites, 15 tenprint operations, 3 Training, 4 Disaster Recovery. Photoshop will be supplied by the vendor for installation on latent, training, and disaster recovery workstations, totaling 33 machines.

8. 5, Section 3.11.2 - What is the required capture resolution for each system that captures original data?

Response: 1000ppi is the required resolution for all capture products within this solicitation.

9. Page 38, Section 3.11.6 - What components and versions of the Websphere suite are available for the Transaction Controller development?

Response: The State has used its Websphere suite to successfully develop and deploy three tiered service oriented applications using JAVA code running on Apache WEB server on Oracle database running in AIX. We have the following Websphere development product available: Websphere Application Server Network Development Suite version 6.0. Our current contract with IBM allows us to upgrade the product when new versions are available. For specific information please see. www-306.ibm.com/software/webservers/appserv/was/network/

10. Page 47 – 49, Section 3.12 - This section discussed conversion of electronic and inked records, but no mention is made of latent fingerprints. Are there requirements for latent conversion? If so, please specify these requirements.

Response: Latent images are generally stored by each vendor in a proprietary manner. This is certainly the case for the State of Maryland. For this reason the State of Maryland plans to reenter all latent images into the new system without vendor involvement. This will also allow us to scan these images at 1000ppi.

11. Page 49, Section 3.12.3 - The solicitation states, “Prior to shipping these cards, the State will be responsible to ensure each card has a barcode label affixed to the card containing the SID and the Event ID. The vendor will be responsible to provide the barcode stickers to be applied to the cards.” Three questions follow:

1. Does the State expect the Vendor to supply blank barcode labels?


2. Who will provide the barcode printers?3. Who will provide the application software to create and print the barcode labels?

Response: As indicated, the State will provide an electronic extract of data which will include the SID# and Event ID. In order to match the proper fingerprint card to the associated criminal history record, the ability to link the data is through these two data elements. It will be a requirement of the vendor to provide barcode labels with the SID and Event ID. The vendor will provide all supplies hardware and application software. The purpose of this approach is to ensure the barcode labels can be read by the vendors’ conversion process without difficulty.

12. Page 56, Section 3.14.5 - The last paragraph on the page states that “All Vendors must comply with the State of Maryland Change Management Process for testing and implementing system related changes into the production environment.” Will the State provide a description of the State of Maryland Change Management Process?

Response: The Change Management Process is controlled by our Quality Management Team. For vendors supporting our environment, all software and hardware that is implemented into production must go through vigorous testing with State personnel. The Quality Management Team will oversee and/or conduct testing to validate quality prior to allowing the software to be moved into production. Emergency implementations will also be passed through the Quality Management Team and approved prior to implementation. Vendors are required to coordinate all production modifications with their State contacts for support in this process. All SDLC documentation, change descriptions and associated release notes for software must be documented and presented to the Quality Management Team to initiate this process.

13 Page 66, Section 4.2 - The second sentence of this section states “An original, so identified, and five (7) copies of each volume are to be submitted.” Please clarify if five or seven copies of each volume are to be submitted.

Response: The requirement is: “An original and seven (7) bound copies of each volume are to be submitted”.

14 Page 66, Section 4.3 - This section states that “all pages of both proposal volumes shall be consecutively numbered from the beginning (Page 1) to the end (Page “X”). Is it acceptable for pages to be numbered consecutively by section? For example, all pages behind Tab A will be numbered Page A-1 to A-X, all pages behind Tab B will be numbered Page B-1 to B-X, etc.

Response: It is acceptable to provide your proposals in either manner. You may number them consecutively throughout the tabs or number them within each tab. Either method must be utilized consistently throughout the entire proposal.

15. Page 67, Section 4.4 - In the instructions for Tab D, Cross Reference Matrix, it states that the “Cross Reference Matrix shall list RFP section number, requirement, and proposal page number and proposal section.” Please clarify what is meant by “RFP section.” Are all parts of the solicitation document, as well as Attachment H to be included in this Cross Reference Matrix?

Response: It is a requirement that each requirement within Attachment H be answered in the vendor proposals, therefore the requirement number be listed. In support of this, we ask that the section number within the Statement of Work, Section 3 of the RFP be referenced as well where applicable.


16. Page 68, Section 4.4 - In the instructions for TAB G, it states that the “Offeror shall provide a minimum of five references;” however, later in the paragraph it states “Offeror shall include references of up to three of its customers...” Please clarify how many references are required.

Response: Three of the five references provided must be in support of the AFIS vendors’ products and services. At least two references must be provided in support of the additional products listed within the RFP, preferably in regard to the Transaction Controller or other component requested. References must cover all products listed within this procurement. In order to cover all products, more than five references may be listed.

17. Page 68, Section 4.4 - In the instructions for Tab I, it states that “Vendors must address each of the requirements outlined in the Requirements Document in Attachment H of this RFP in a written response.” Does this mean vendors should provide a point-by-point response to each requirement in Attachment H?

Response: Each requirement listed in Attachment H must be addressed by the vendor. Simply indicating “Will Comply” will not be acceptable. If you have answered a requirement elsewhere in previous responses, referencing that response will be acceptable.

18. Page 68, Section 4.4 - If a point-by-point response is required, is “Comply” an adequate response? For example, requirement L.25 on page 40 states “The system shall be sized to process 100 latents to unsolved latent searches in an 8-hour period and 300 LT/UL searches in 24 hours”. Can vendors say “comply” if the proposed solution meets that requirement or do vendors have to demonstrate how the proposed solution meets the requirement in the written response?

Response: Responses of “Comply” or “Will Comply” will be considered non-responsive. A brief description of how the requirement will be met is required.

19. Page 68, Section 4.4 - Also, if a detailed point-by-point response is required for each requirement, will the State consider an extension of the proposal due date of 2 weeks to allow vendors adequate time to respond to every requirement in Attachment H?

Response: Based on responses from several vendors, an extension will be considered and published by the State of Maryland.

20. Page 69, Section 4.4 - Also, this section states that “Vendors shall give an overview (not to exceed 1000 words and shall include no marketing), to the following sections:” Is the 1000 word overview to be provided in addition to addressing each requirement in a point-by-point response?

Response: Yes, the 1000 word overview would be in addition to addressing each requirement. The 1000 word overview can be utilized however the vendor feels is necessary in order to give the State of Maryland a summary of your responses to each section. Additional information such as a vendor’s suggestions or options available can also be listed in this overview.

21. Page 69, Section 4.4 - Please clarify if the 1000 word limit applies to each individual section overview, or if one combined overview for all sections is required. To be more specific, are vendors allowed 1,000 words or less for a General AFIS requirements overview, and 1,000 words or less for a Tenprint Processing overview, and1,000 words or less for a Latent Processing overview, etc. Or, are vendors to provide one combined


overview (1,000 words or less) covering General AFIS requirements through Project Management and Development requirements?

Response: The vendors shall provide up to a 1000 word overview for each section beginning at 2.2.1 through 3.11 of Attachment H. Example, Section 2.2.1, General AFIS, the vendor shall provide an overview of up to 1000 words or less. For section 2.2.2, Tenprint AFIS, the vendor shall provide an overview of up to 1000 words or less. If a vendor feels that an overview is not necessary, please simply indicate that the section is clearly answered in the responses to the listed requirements.

22. 9, Section 4.4 - Regarding the 1,000 word overview to be provided for certain sections of Attachment H, please confirm that some sections from Attachment H were purposely omitted from the list on page 69. To be specific, “Audit Trail,” “Data Currency,” “Reliability,” “Fault Tolerance,” “Performance,” and “Data Retention” were omitted from the list of sections on page 69.

Response: Vendors must respond to all sections within 2 and 3 of Attachment H. This will be more clearly addressed in the published Addendum to the RFP.

23. Page 6, Section 2.2.1, A-4 - Paragraph A.4 states “The hardware for the system shall be compatible with the State’s computing environment, including databases and operating systems”. The solicitation identifies the preference for Oracle, DB2, or SQL Server.

Can the State provide preferred specifications on hardware platforms and operating systems as well?

Response: The State currently uses Microsoft Windows for the operating system on PC’s. PC hardware is currently Dell. UNIX currently in use includes AIX on IBM hardware. We are open to vendor proposed solutions on vendor-supported products. The Transaction Controller must have a commercially supported Operating System.

24. Page 6, Section 2.2.1, A-7 - Please provide more information regarding the State’s SAN, including information regarding hardware and software.

Response: The SAN’s are EMC model DMX 1000. Please refer to the EMC WEB site additional technical information. Access to the SAN network uses FIBRE channel. If there are additional technical clarifications required, please ask a specific question. Both Primary and Secondary SAN devices contain Timefinder Clone and SRDFA.

25. Pages 7 and 35, Section 2.2.1, A-13 and 3.1 - Paragraph A.13 states “Each component within the system must be protected with anti-virus and appropriate security related software. (State will provide the software and license to support this requirement).” Whereas, paragraph S.24 through S.28 on page 35 states: “The <components> shall use the State’s enterprise anti-virus software if applicable to the operating system chosen. Otherwise the vendor shall supply an anti-virus and malware management plan appropriate for the AFIS environment.”

Can the State provide additional specifications on the enterprise anti-virus capabilities available, specifically the vendor, version, and operating systems supported?

Response: The State will supply anti-virus software (currently from Symantec) for PC’s running Microsoft Windows operating systems. No anti-virus software is required for UNIX operating systems.


26. , Section 2.2.1, A.14 - Paragraph A.14 states; The system shall guarantee delivery of a response within 3 seconds to any transaction that has been accepted or rejected, unless deleted by the System Administrator.

Can the State provide the definition of “guarantee delivery of a response” in the context of this requirement? Is this intended to be an “ACK-type” of acknowledgment, or the actual response to the transaction, in which case the response time is measured from the time of receipt to the time the response is sent back, but not necessarily received?

Response: The State currently experiences a significant number of orphaned transactions. This occurs when the intended receiving system does not actually receive a record transmission and the sending system has no knowledge concerning when to delete a transaction from its work in progress queue and/its transmission queues. The intent of this requirement is to require the vendor(s) of the new systems to ensure that the Transaction Controller, the Archive, the Mugphoto server and the AFIS never reach a “deadlock” situation where records are orphaned, lost, or unable to continue processing. The system integrity must ensure that every record submitted is traceable. Consequently, the State is expecting the vendors to describe its methodology to ensure continuity of processing and integrity of the workflow for tenprint records.

27. Page 7, Section 2.2.1, A.14 - Mention is made of a “guarantee delivery of a response with 3 seconds to any transaction that has been accepted or rejected …” How does this 3 second requirement relate to the performance requirements in Section 3.9? For example, requirement FI.13 says that Fast Identification searches will be 1,500 per day with peak hour of 500 searches, how does the 3 second requirement in A.14 relate to this requirement (and the others in 3.9?)

Response: The State currently experiences a significant number of orphaned transactions. This occurs when the intended receiving system does not actually receive a record transmission and the sending system has no knowledge concerning when to delete a transaction from its work in progress queue and/its transmission queues. The intent of this requirement is to require the vendor(s) of the new systems to ensure that the Transaction Controller, the Archive, the Mugphoto server and the AFIS never reach a “deadlock” situation where records are orphaned, lost, or unable to continue processing. Consequently, the State is expecting the vendors to describe its methodology to ensure continuity of processing and integrity of the workflow for tenprint records

The three-second requirement does not apply to FAST ID. However, to the extent that the user interface devices can provide feedback to user that his search request has been receive and is being processed, it is desired that the FAST ID central processing system provide feedback to the user to avoid situations where the user becomes impatient with response time and repeatedly re-transmits the same search request.

28. Page 7, Section 2.2.1, A.16 - Mention is made of meeting the Service Level Agreement for processing time. Where is the Service Level Agreement defined and what is the scope of this agreement?

Response: The State currently has a Service Level Agreement with its user agencies that the State will provide a tenprint search and identification response to electronic submissions from livescans and cardscans within 20 minutes of receipt of the search request at the central site (CJIS). The State has sized its tenprint throughput


requirements (270 per hour) to meet and/or exceed this level of service commitment to our user agencies.

29. Page 7, Section 2.2.1, The General AFIS Requirements skip from A.17 to A.19. Please confirm that A.18 was purposely omitted.

Response: Yes, this is correct.

30. Page 7, Section 2.2.1, A21 - Paragraph A.21 states: “Vendor must provide a complete and separate test system that will mirror the production system”.

Can the State provide additional clarification for sizing and functionality purposes? Does the separate environment require the same level of performance (i.e., database size and transaction volume) and availability (i.e., redundant components)? Must the test system be separate from the Disaster Recovery system? Will the test system require a fully synchronized current database?

Response: The purpose of the test system(s) is to provide a platform(s) for software functionality testing prior to the deployment of new software on the production system(s). The test system(s) must be separate from both the primary production and disaster recovery systems. The test system(s) can have greatly reduced throughput and greatly reduced background databases from the operational system. However, all functionality including interfaces to other test systems must be present on the test system(s) to facilitate functionality testing.

31. , Section 2.2.1, A28 - Regarding jams that occur on the printer, will an FBI certified printer suffice to meet this requirement?

Response: No, the State has experienced paper jam problems with some models of FBI IQS certified printers and expects that the vendor based on its experience will avoid supplying such problem printers to the State.

32. Page 9, Section 2.2.1, A.36 - Can the State provide additional information regarding the secondary storage?

Response: The state anticipates using SDLT tape or whatever replaces SDLT in the future.

33. Page 9, Section 2.2.1, A.36 - Will the State provide the secondary storage equipment?

Response: Yes

34. Page 10, Section 2.2.2, T.6 - Please define Validation results; are they the results determined by the AFIS?

Response: Validation for purposes of T6 is the second stage of two-stage fingerprint verification process. Validation in this case will be performed by a human fingerprint examiner.

35. Page 10, Section 2.2.2 - The Tenprint Processing Requirements skip from T.8 to T.10. Please confirm that T.9 was purposely omitted.

Response: Yes, this is true. T.9 was omitted.

36. Page 11, Section 2.2.2, T.17 - Should “the best four of six fingers be searched” actually be “the best four of ten fingers”?

Response: The State is interested in maximum accuracy at an affordable cost. The State anticipated that this would occur using the best quality 4 fingers selected from


finger numbers 1,2,3,5,6,7. However the State is open to any and all other options that will support our accuracy requirements at a competitive cost.


Response: Yes, this is true. T.18 is omitted.



39. Page 12, Section 2.2.2 - The Tenprint Processing Requirements skip from T.30 to T.34. Please confirm that T.31, T.32, and T.33 were purposely omitted from this section, and that T.31 and T.33 are included in 3.9 Performance requirements, but T.32 is not included anywhere in Attachment H.


40. Page 12, Section 2.2.2, T.50 - Please clarify if the database sizing requirement is for “day one forward”?

Response: No, the initial AFIS tenprint database will contain approximately 2.5 million converted tenprint records. Contracted database sizes are listed in the Table located on page 34 of Section 3 of the RFP. Additionally sizing requirements are indicated within Attachment H, Functional and Technical Requirements Document.

41. Page 13, Section 2.2.2, T.50 - Can the state confirm is this is the actual size of the subject records or the total number of fingerprint records to be accommodated if multiple records per subject are stored within the AFIS database?

Response: The new AFIS will be a “composite” AFIS. Consequently there will be only one tenprint record per SID# (subject) in the AFIS. Currently there are approximately 2.5 million SID#’s (subjects) in Maryland. The “4 million” number was provided so that AFIS vendors could size the system to meet the throughput requirements to support a 4 million subject AFIS database to allow for future growth of the system.

42. Page 14, Section 2.2.3, L.16 - Paragraph L.16 states; “The system must support ULW software on all MAFIS latent workstations with the ability to electronically transfer “coded” images and minutiae from MAFIS workstation software into ULW software along with associated Type-2 data.”

If the vendor’s COTS product provides all of the functionality of the ULW, can the vendor’s solution be proposed as an alternative?

Response: Yes, as long as the vendor’s “ULW clone” software provides full and/or superior functionality to the current version of the FBI ULW and the vendor agrees to enhance its own “ULW” software consistent with FBI ULW enhancements in the future.

43. Page 14, Section 2.2.3, L.16 - Please define “coded’ images. Are these images edited by the operator?

Response: “Coded” images are images for which the minutiae have been extracted by automated and/or human processes.


44. Pages 14 and 15, Section 2.2.3 - The Latent Processing Requirements skip from L.22 (page 14) to L.30 (page 15). Please confirm that L.23 through L.29 were purposely omitted from this section, and are included in 3.9 Performance requirements.

Response: Yes this is true. L.23 – L.29 were purposely placed into the Performance requirement section.

45. Page 16, Section 2.2.3, L.50 - Please clarify if the database sizing requirement is for “day one forward”?

Response: Yes, the State will re-enter its unsolved latents by reacquiring them at 1,000 ppi, recoding the minutiae and launching a LT/TP search on the new AFIS.

46. Page 16, Section 2.2.4 - What are the accuracy and reliability requirements for latent palm processing?

Response: The State expects the same or better accuracy and reliability for latent palm prints as stated for latent fingerprints.

47. Page 17, Section 2.2.5, T.2 - Who is responsible for providing the MQSeries Server?

Response: The State will supply MQ Series server software licenses. The state also operates multiple MQ series servers. The vendor may find it useful to deploy a MQ Series server as a function of the Transaction Controller.

48. Page 17, Section 2.2.5, TC.3 - Please provide information about the location of the appendix for Check Digit Standards.

Response: The document has been included at the end of this document.

49. Page 17, Section 2.2.5 - The Transaction Controller Processing Requirements skip from TC.9 to TC.11. Please confirm that TC.10 was purposely omitted.

Response: Yes, TC.10 was omitted.

50. Page 18, Section 2.2.5, TC.26 - Please define the criteria to qualify a record as “defective.”

Response: “Defective” for purposes of the Transaction Controller is any record that cannot pass NIST record format validation or NIST Type 2 data validation (if a tenprint record incoming from livescan or cardscan).

51. Page 19, Section 2.2.5, TC.37 - FIS is not part of the abbreviation list, please provide an abbreviation explanation.

Response: FIS is a Type of Transaction found in Section 3.7 of the FBI EFTS – “Fingerprint Image Submissions” See also Section 3.7.1.1 of the EFTS.

52. Page 20, Section 2.2.6, FA.1 - Please provide information about the software running on the State’s SAN and mirrored disaster recovery SAN.

Response: Both Primary and Secondary SAN devices contain Timefinder Clone and SRDFA.

53. Page 21, Section 2.2.6, FA.17 - Regarding MD CJIS certification watermark, can the state provide more information regarding the type of water marking that will be used?

Response: The State will work with the vendor to design a watermark that can be inserted into the vendor’s printer stream. The State currently anticipates using a JPEG file or a PDF file for this purpose, but is open to suggestions.


54. Page 22, Section 2.2.7, DC.1 - Please provide criteria to qualify “Best Quality Record on file”. Which entity will make the decision on which record should be converted?

Response: The State will make this decision.

55. Page 23, Section 2.2.8, FI.9 - Please define further the “message format” mentioned in this requirement.

Response: NIST refers to NIST Publication SP 500-245. M1 refers to ANSI/INCITS 378-2004. SC37 is ISO 19794-2:2005.

56. Page 24, Section 2.2.8 - The Fast Identification requirements skip from FI.12 to FI.18. Please confirm that FI.13 through FI.17 were purposely omitted from this section, but are included in 3.9 Performance requirements.

Response: Yes, FI.13 through FI.17 are located in the Performance Requirements Section.

57. Page 25, Section 2.2.9, MS.27 - Paragraph MS.27 states; “The vendor shall provide network ready color printers for optional purchase.” Can the State confirm these are the “FBI-certified” printers identified under Table F-9 and that pricing for these printers should be provided under this entry in table F-9?

Response: Yes, pricing for the network ready color printers goes in the “FBI Certified Color Printer” entry in Table F-9. (Note that the FBI does not certify color printers – only grayscale printers”.) Table F-9 will be changed to read “Network Ready Color Printers”.

58. Page 26, Section 2.2.9 - The Mugshot System requirements skip from MS.34 to MS.42. Please confirm that MS.35 through MS.41 were purposely omitted from this section, but are included in 3.9 Performance requirements.

Response: Yes, this is correct. MS.35 – MS.41 are located in the Performance Requirements Section.

59. Page 28, Section 2.2.10, SM.21 - Will the State of Maryland expect the vendor to place all system components of AFIS in Escrow? Can the State provide a timeline?

Response: Yes. Within 60 days of system acceptance by the State. All software updates and patches must also be entered into escrow within 60 days of acceptance / implementation by the State.

60. Page 35, Section 3.1, S.16 - Can vendor assume that the State of Maryland is referring to the same secondary storage mentioned in A.36 on page 9?

Response: Yes

61. Page 36, Section 3.1, S.29 - Paragraph S.29 states “Biometric logon is a desirable option to the State. Vendor shall describe the use of this feature if available with their proposed solution.” Can the State identify if pricing information on the biometric logon feature is required, and if so, under which Pricing table the information should be provided?

Response: Table F-9 of the pricing sheets will be updated to include a location to price biometric logon. If biometric logon is available, it should be priced. If biometric logon is not priced, the State will assume that the vendor cannot supply this function.

62. Page 37, Section 3.5 - Can Vendors assume that VPN is permitted in order to perform remote administration?


Response: Yes

63. Page 37, Section 3.6 - Please provide examples of “vital processing functions”? Are they the “primary work task” defined in the RFP document in 3.15 on page 58?

Response: Vital processing functions are the ability to fully process tenprints, latents, latent palms, insert records into archive, mugphoto, search archive and mugphoto systems, receive and transmit tenprints and latents to/from the FBI, receive latents from livescans and operate the FAST ID system.

64. Page 39, Section 3.8 - Can some of the Disaster Recovery capacity be used in searches?

Response: Yes, the State will consider favorably an operational AFIS that is split over two locations with each “half” of the AFIS able to independently continue operations at reduced capacity in the event of the loss of one of the sites. The bidder must provide the bandwidth requirements for this type of solution. The proposed solution must meet all High Availability and Disaster Recovery requirements.

65. Page 40, Section 3.8, DR.13 - Paragraph DR.13 states “The Transaction Controller (TC) shall be mirrored at the disaster recovery site with the mirrored TC able to immediately continue processing in the event of failure of the primary TC”.

Can the State clarify the fail-over/redundancy requirements for the additional AFIS components, specifically the AFIS, Fingerprint Archive, Fast ID, and Mugphoto components of the system? Do these additional components require immediate fail-over processing capabilities as well?

Response: The Transaction Controller must have immediate failover to full operations. All other components including AFIS, Archive, FAST ID and Mugphoto must be operational at the disaster recovery site within one hour after the decision is made to initiate the disaster plan.

66. Page 40, Section 3.9 - This section provides throughput requirements for tenprint, latent and palm print searches. It also provides response time requirements for Fast Identification searches. Can the State please provide response time requirements for the following searches:

TP/TP (Tenprint to Tenprint)LT/TP (Latent to Tenprint)LT/UL (Tenprint to Unsolved Latent)LP/PP (Latent Palm to Palm Print)TP/UL (Tenprint to Unsolved Latent)LP/ULP (Latent Palm to Unsolved Latent Palm)

Response: Please see the chart in Section 3.10 on page 34 of the proposal.TP/TP = 270 per hourTL/TP = 100 per 8 hours = 12.5 per hourLT/UP = 25 per 8 hours = 3.125 per hourLP/PP = 40 per 8 hours = 5 per hourTP/UP = 1100 per 24 hours = 45.8 per hourLP/ULP = 15 per 8 hours = 1.875 per hourPP/ULP = 120 per 24 hours = 5 per hour

67. Page 42, Section 3.11, PM.7 - Please clarify if PMBOK should be the abbreviation for Project Management Body of knowledge.

Response: Yes


68. Page 43, Section 3.11, PM.28 - Is SEMP referring to a System Engineering Management Plan?

Response: Yes

69. In certain cases, the Solicitation Document contains additional or conflicting information/requirements compared to Attachment H. Please clarify which document takes precedence. Example: Attachment H, 2.2.7, DC.10, page 23 states “All card conversion will be performed at the Maryland State designated location.” Solicitation Section 3.12, page 47, Location and Facilities, “It is preferred that the conversion processes be performed at a location provided by the State of Maryland, however this is not mandatory”.

Response: The State believes given the large volume of cards that must be converted, that a State provided location would be advantageous to the vendors. However, the State will consider card conversion at a vendor location. If a vendor proposes its own location, the vendor will be responsible for all costs related to shipping, QC requirements for State personnel, etc.

70. Where in the proposal do we respond to solicitation requirements that are in addition to or different from the requirements in Attachment H?

Response: To the best of the State’s knowledge, there are no inconsistencies between the Statement of Work and the requirements in Attachment H. Several pointed issues have been asked in previous questions within this document. If you believe that you have discovered an inconsistency that has not been addressed, please respond in writing and indicate the area of the SOW that is inconsistent. The State will respond to questions submitted in a timely manner to clear up any inconsistency issues prior to the RFP response deadline.

71. Who is responsible for providing the mail server?

Response: The email server that is part of the Transaction Controller is considered to be a vendor deliverable.

72. Would it be possible to receive a brief tour of the proposed Card Conversion area and Hard Card storage area sometime Tuesday morning, March 7th prior to the Bidders Conference?

Response: The current repository of inked cards can be toured by scheduling an appointment through the procurement officer, Joselyn Hopkins. The State has not yet identified a space for card conversion and seeks vendor input concerning space requirement suggestions (square feet needed) and electrical requirements for the card scanners and associated equipment.

73. Who is the incumbent?

Response: Sagem Morpho, Inc.

74. What system is currently in use?

Response: Sagem Morpho’s XL model.

75. How long has it been in use?

Response: Initially installed in the early 1990’s, the current AFIS has been upgraded periodically since that time.

76. What is the cost of current contract?


Response: The current AFIS contract has been in place since the early 1990’s and renewed periodically since that time. It has no relevance to the current procurement.

77. Does all experience have to be in the United States or can it be from outside the United States?

Response: AFIS experience can be from outside the United States. However, Maryland must be able to communicate effectively with the referenced customers. So language / communications capability at the reference site must be considered by the vendor before supplying the reference.

78. The Disaster Recovery site has been configured to provide 50% 1, 2, 3 priority performance during a production system catastrophic failure. When the production system is up and running, the DR system is idle." Would the state consider alternative solutions to an idle Disaster Recovery system that still meets the other requirements?

Response: Yes, the State will consider favorably an operational AFIS that is split over two locations with each “half” of the AFIS able to independently continue operations at reduced capacity in the event of the loss of one of the sites.

79. Why is 2 million the minimum requirement for tenprint records in previously installed systems?

Response: As a matter of risk management, the State wants to make sure that the chosen vendor has experience deploying an AFIS similar in magnitude to the AFIS needed by the State.

80. What is the size of the State’s SAN?

Response: The state will expand the EMC SANs (operational and mirrored backup SAN) to meet all permanent storage needs for the AFIS, archive, and mug-photo systems. Vendors must describe how much space your systems will require (one SAN only – we can multiply by 2 for the backup SAN.) so we can size our SAN’s accordingly.

81. Will the AFIS workstations be used for tasks other than running the AFIS system?

Response: Yes, office automation, image enhancement (Photoshop), archive access, and mugshot system interface at minimum are all requirements of this procurement.

82. What is the enterprise anti-virus software that is currently being used?

Response: Symantec Enterprise Anti-virus Version 9 on Windows PCs. No anti-virus software is required on UNIX machines.

83. Will DPSCS allow a tour of the facility where card conversion will be performed and can we see a sample of the cards that will be converted?

Response: The current repository of inked cards can be toured by scheduling through the procurement officer, Joselyn Hopkins. The State has not yet identified a space for card conversion and seeks vendor input concerning space requirement suggestions (square feet needed) and electrical requirements for the card scanners and associated equipment.


84. Page 3, Section 1.1 of states that the Mugshot System is Optional. Please confirm that the Mugshot is an Option. Additionally, will any optional items be included in the price evaluation?

Response: Mugphoto is a mandatory item per the RFP. Based on affordability and the proposed system, the State may chose not to purchase any items proposed.

85. RFP, page 53, the first paragraph of Attachment H Section 3.14.3 User Training, uses the phrase "on-site 24X7 training support," please provide further details defining the meaning of training support.

Response: Training support during system start-up (Go Live) is to provide on-site assistance for operators. The latent operations are generally a five day process, Monday through Friday from 8:00am till 5:00pm. During this eight-hour period we expect at a minimum of one trainer to be available at the Maryland State Police Crime Lab in support of latent operations. The tenprint operations are conducted 24 hours per day, seven days per week. It is requested that an on-site trainer be provided to assist operators during the first 10 days of production use on each shift.

86. RFP, Page 53, 3.14.3 User Training, in lieu of training all the employees listed in table 3.14-2 on page 55 of this RFP; will DPSCS consider a train-the-trainer approach for the training of end users?

Response: Training will be provided for the personnel listed in table 3.14-2. A train-the-trainer approach will be considered for future training needs outside of the training required in this RFP.

87. RFP, Page 56, 3.14.5 System Support and Maintenance references the "State of Maryland Change Management Process," please either provide a copy of this document or a link to access the document.

Response: The Change Management Process is controlled by our Quality Management Team. For vendors supporting our environment, all software and hardware that is implemented into production must go through vigorous testing with State personnel. The Quality Management Team will oversee and/or conduct testing to validate quality prior to allowing the software to be moved into production. Emergency implementations will also be passed through the Quality Management Team and approved prior to implementation. Vendors are required to coordinate all production modifications with their State contacts for support in this process. All SDLC documentation, change descriptions and associated release notes for software must be documented and presented to the Quality Management Team to initiate this process.

88. RFP, page 73, Technical Criteria has Tab F included in both item 1 (highest importance) and item 7. Is item 7 Offeror Experience and Capabilities really referencing Tab E (Company Background and Experience)?

Response: Yes, Item 7 should refer to Tab E (company background and experience) of the technical proposal.

89. RFP, page 119, In table F-9, are the 25 and 50 investigative licenses different than the enterprise mugshot license DPS is asking for? Also, what exactly is expected in the photo/facial recognition package in this same table F-9?


Response: The intent of listed prices for enterprise licensing listed in Table F-9 is for the possible future purchasing to support additional users outside of the tenprint and latent community. The State would be interested in purchasing an enterprise license to support this need.

Facial Recognition is generally an optional package associated with most mugphoto systems. Facial recognition can allow digital sketches and/or digital photos, etc. to be entered into the mugphoto system and searched against the database for identification purposes. We do not anticipate purchasing this until we have our mugphoto system operational. We do however expect the mugphoto system to be able to provide this type of utility.

90. Page 6, A.4 The hardware for the system shall be compatible with the State’s computing environment, including databases and operating systems. State approval of all proposed hardware and system software will be required. Please define the State’s computing environment, databases and operating systems that the AFIS solution must interact with.

Response: The existing legacy system environments are outlined in Section 3.13 of the RFP. Additional information is provided in question #23 above.

91. Page 7, A.8 The system will use the State’s SAN for primary record storage. Please define the preferred manner in which connectivity is to be provided (e.g., fiber)?

Response: Connectivity provided by the State will be Fibre Channel.

92. Page 7, A.13 Each component within the system must be protected with anti-virus and appropriate security related software. (State will provide the software and license to support this requirement.). Please define the anti-virus and related security related software that will be provided. Please provide software name and revision. Please also provide rules for implementation.

Response: At this time, this requirement solely refers to anti-virus software in support of PC’s. The State is currently operating on Version 9 of Symantec and intends to stay as current as possible with this product through our enterprise agreement. We currently deploy anti-virus as a standard installation that scans all files opened on a computer. The State will work with the selected vendor to resolve issues as needed.

93. Page 10, A.53 The system shall be delivered with a minimum of 1 Gigabit internal network backbone to support all system servers provided within this contract. Please confirm that AFIS will not reside on an existing, or to be installed, DPSCS network. Will the AFIS vendor need to provide a separate 1 Gigabit network that will support only AFIS systems? Will the AFIS vendor need to provide physical wiring and ports throughout central site, disaster recovery site and remote sites? If this is so, please define any additional workstations, servers, and subsystems, not listed in this RFP, which will require connection to the AFIS network.

Response: The AFIS provider will provide two networks, one at the primary data center and one at the disaster site. Both networks will be interfaced to the DPSCS network with Gigabit over copper. All remote devices will ride the DPSCS network to communicate with the AFIS internal network. All cabling and hardware to


support the AFIS networks will be provided by the selected vendor. The State’s current network environment uses CISCO products.

94. Page 10, T.2 Each tenprint verification workstation shall be provided with a FBI IQS certified flatbed scanner to support a search and purge tenprint identification process. This process must not allow permanent record storage of tenprints in the database. Are they different than those defined in T.3? If different what is the quality of workstations required?

Response: The tenprint verification workstations discussed in T.2 and T.3 are the same.

95. Page 13, section 2.2.3 The Latent Processing Requirements do not include a requirement to have a latent camera. Page 54 of the RFP states that Latent training will require the use of camera and lighting techniques. Please specify if a high resolution fixed camera with lighting is required on all 26 latent workstations.

Response: The purchase of camera equipment is not part of this procurement. We will addend page 54 for to omit the training requirement for camera and lighting techniques.

96. Page 14, L.17 The system shall allow the use of third party image editing software (e.g. Photoshop CS/2) on all latent workstations with electronic import – export of images between latent workstation and image editing software. Please indicate if the state will provide the license for the third party image editing software (Photoshop).

Response: No, the State will not be providing licenses. We request the vendor provide Photoshop on the workstations listed below. Latent workstations – 26 ea, Disaster Recovery Workstations - 4 ea, and Training Workstations – 3 ea.

97. Page 23, FI.2 Vendor will supply mobile WiFI (802.11g) PDA type capture devices for Dept. of Corrections. Pilot Quantity is 8 units. State will supply wireless network. Please define the general location and operation of 802.11g access points. Vehicle based? MESH based? State Wide?

Response: Fast Identification is for pilot use. The wireless capture devices are planned for Division of Corrections, that are in fixed locations. No 802.11g access points have been implemented at this time. The State is responsible for implementing the 802.11g access points at all pilot locations.

98. Page 23, FI.8 All FAST ID capture messages will be via TCP/IP. Please confirm that the State will provide TCP/IP network

Response: The State will provide the TCP/IP network for all FAST ID capture messages.

99. Page 34, 3.1 Security All systems must follow the Maryland Department of Budget and Management Office of Information Technology Information Technology Security Policy and Standards document Version 1.3 dated December 2005. Please identify the location where the vendor can obtain this document.


Response: this document is available at: http://www.dbm.maryland.gov/dbm_publishing/public_content/dbm_taxonomy/security/prevention/itsecuritypolicies.pdf

100. Page 35, S.22 Test and Training databases must be separate from operational databases. Please confirm that the test and training database will be housed on the State SAN.

Response: Yes, the State SAN will be used to support the test bed and training databases. These databases must be deployed separate from the production databases on the SANs.

101. Page 36, N.1 The system shall be able to accommodate remote latent or tenprint workstations with minimum communication rates of .5 T1-capacities (750 kbs). These workstations shall have acceptable response times for the user, in accordance with the Business Requirements. Please indicate if the AFIS vendor is to provide communication lines between remote sites, central site and disaster recovery site.

Response: The State shall provide communication lines between remote sites, central site and disaster recovery site.

102. Page 40, L.25 states “The system shall be sized to process 100 latent to unsolved latent searches in an 8-hour period and 300 LT/UL searches in 24 hours.” RFP, page 34 table defines the LT/UL searches to be 25 per 8 hours and 75 per 24 hours. Please define the correct LT/UL throughput.

Response: The RFP, page 34 refers to current usage. Page 40 L.25 requires the bidder to size the new system to handle up to a 100 latent to unsolved latent searches in an 8-hour period which is 300 LT/UL searches in 24 hours.

103. How many concurrent clients does DPS anticipate will be using the enterprise mugshot license at peak times (i.e. should the enterprise license be able to cover 50,100,200 users simultaneously)?

Response: 50 concurrent users

104. Will the mugshot system be required to enrol existing images/records from county, city and other mugshot systems upon installation, or will it start with 0 records and only be receiving about 15,000 new records each month upon installation (i.e. existing records will NOT be "uploaded" into the state mugshot system)?

Response: Mugshot will be day one forward for purposes of this procurement.

105. The Disaster Recovery site has been configured to provide 50% 1, 2, 3 priority performance during a production system catastrophic failure. When the production system is up and running, the DR system is idle." Would the state consider alternative solutions to an idle Disaster Recovery system that still meets the other requirements?

Response: Yes, the State will consider favorably an operational AFIS that is split over two locations with each “half” of the AFIS able to independently continue operations at reduced capacity in the event of the loss of one of the sites.


http://www.dbm.maryland.gov/dbm_publishing/public_content/dbm_taxonomy/security/prevention/itsecuritypolicies.pdf

http://www.dbm.maryland.gov/dbm_publishing/public_content/dbm_taxonomy/security/prevention/itsecuritypolicies.pdf

106. Please clarify the deliverables required for the transaction controller. Deliverables are identified in sections 3.9, 3.14, the Price Proposal, and FRD. The lists in these sections are not consistent.

Response: We agree with this statement. As a result of these inconsistencies an addendum will be published with changes to both Table 3.9-1 and the Price Sheets in Attachment F. A summary of our findings are:

i. Phase I, Deliverable 4 of Table F – 4 – Complete System Integration Test Plan. It is the State’s intent that all integration testing be centralized around the Transaction Controller due to the fact it is the centralized controlling device for all other components. Thus this deliverable in Table 3.9-1, (d) Development Phase, Deliverable 10 Integrated Test Plan shall be priced within the Transaction Controller Price Sheet F – 4.

ii. Phase I, Deliverable 4 of Table F – 4 - Transaction Controller Training Plan will be removed from the price sheets. The vendor is responsible to ensure the knowledge transfer requirement is included into the development of the Transaction Controller.

iii. Phase I, Deliverable 5 - Transaction Controller Operations Guide will be modified to state ‘Operators Guide”. The deliverable in Table 3.9-1, (d) Development Phase, Deliverable 19 will be deleted.

iv. Phase III, Deliverable 4 of Table F - 4 – User Training will be modified to state User Training for Supervisors.

107. Who is responsible for the development of the: a.) transaction controller system test cases, and b.) the execution of the system test cases. Where will this testing take place?

Response: Test case scenarios are a joint responsibility of the vendor and the State. It is anticipated that the vendor will develop comprehensive test scenarios for unit and acceptance tests. The State will review and contribute to these tests cases until all possible functional permutations have been tested.

108. The system sizing and throughput table in the SOW, Section 3.10, does not indicate a “Contracted Database Size” for the Fingerprint Archive; what is the intended size? Does the State intend to store all AFIS, Archive, and Mugphoto records on the existing SAN.

Response: Yes, the State will provide EMC DMX 1000 SAN storage for all permanent records in AFIS, Fingerprint Archive, and MugPhoto Servers. The Fingerprint Archive will start with a database size of 6 million converted records and grow at a rate of approximately 1,038 tenprints (and palmprints) per day.

109. In the same table as above, all numbers for the Estimated DB size in 2025 are less than or equal to the “contracted database size” except the unsolved latent component where the “contracted database size is 350,000, but the estimated DB size in 2015 is 367,000. Please confirm the figures for these two entries.

Response: 350,000 is the correct contracted database size for unsolved latent prints. Our current AFIS does not support any useful methodology for deletion of unsolved latents and thus at current rates, the number of unsolved latents would have exceeded the desired contracted size. Unsolved latents will be entered day one forward into the new AFIS and the State expects that the new AFIS will provide a useful methodology for deletion of unsolved latents for cases where the statue of limitations has expired and similar events.


110. Attachment H, paragraph DC 10 states that, “All card conversion will be performed at the Maryland State designated location”, whereas paragraph 3.12.1 of the SOW says that this is preferred, but not mandatory. Which is correct.

Response: The State anticipated due to the large volume of tenprint cards to be converted that the vendor would desire to perform this function in Maryland. However, if the vendor desires to pay for shipping (both ways) of tenprint cards and can provide a methodology whereby the tenprint cards are inaccessible to Maryland for a minimum time period, the State will allow for them to be done off-site.

111. Does the State require a permanent on-site test-bed for AFIS and all subsystems?

Response: Yes

112. In the SOW, paragraph 3.9, are the durations shown in calendar days or in working days?

Response: Calendar Days

113. In the SOW, paragraph 3.9, Table 3.9, can the State confirm that 15 days for the Testing Phase is correct?

Response: Yes, however, note that this fifteen days of testing is followed by 50 more days of acceptance testing and user training which are additional forms of testing.


CRITERIA FOR CREATING, EDITING AND USING PCNS FOR THE NETWORK LIVESCAN

NOTE - This document neither addresses nor, at this time, affects any currently used "600" series Prefix.

PCN STRUCTURE

PCNs to be used in the NLS will consist of a twelve-byte string composed of the following: Three byte device identifier Two byte PCN Year Six byte Sequence Number One byte Check Digit

The specific requirements are as follows:

DEVICE IDENTIFIER

Each Live Scan or Card Scan device will be assigned a unique three character prefix code. The codes will be designated by the CJIS director or the Director's designee. The only requirement is that each new prefix will be different from all previously assigned NLS or IPS prefixes and different from all ABS assigned prefixes.

PCN YEAR

The second part of the PCN will consist of the last two digits of the year the PCN was generated.

SEQUENCE NUMBER

This number will be a six digit number generated incrementally and will represent the "Nth" PCN generated in that year on that device.

CHECK DIGIT

In order to perform a meaningful edit on the NLS PCN the following steps will be taken to allow the standard MOD 7 Check Digit routine to be done.

The first three characters of the PCN will be treated as an alphanumeric that will be converted to a numeric value called the "PREFIX" value.

Each of the three characters will be converted to a decimal value for that character. This includes numbers. The decimal value for each character is in a table at the bottom of this document. The value of the first character will be multiplied by 32051 to produce the first product. The value of the second character will be multiplied by 179 to produce the second product. The first two product values will be added to the value for the third character. This total will be the PREFIX value.

For example, suppose the prefix is "BA1". "B" = 13, "A" = 11 and "1" = 131. So the PREFIX value is -

(13 * 32051) + (11 * 179) + 131 = 418763. The PCN YEAR and the SEQUENCE NUMBER will be concatenated to create a single eight

digit numeric field called the SUFFIX value.


For example, the first PCN generated by a given device in 2005 will be 000001. So the SUFFIX value will be 05000001.

The PREFIX value will be added to the SUFFIX value to create the DIVIDEND value. In the previous examples the DIVIDEND value will be 05000001 + 418763 = 5418764.

The Check Digit must equal the REMAINDER of the DIVIDEND value divided by 7. In the example above the remainder of 5418764 / 7 is one (1). This means that in this example the PCN will be -

BA1050000011

PRACTICAL CONSIDERATIONS

Whenever the PCN is displayed in human readable form it will be display as -

XXX NNN NNN NNN.

In the example in the previous section the PCN would appear as -

BA1 050 000 011

Any three character combinations that may be offensive or vulgar will not be assigned. All of the assigned Device Identifier combinations will be stored in the IPS Code Table. The PREFIX value for each of those assigned combinations will be stored with the identifiers

in the table. When a PCN is to be edited, the appropriate portion of the IPS Codes Table will be searched

for the first three bytes of the PCN. If not found the edit fails. If found the PREFIX value will be retrieved to use in the verification of the Check Digit value.

No accounting or auditing will be required to account for unused PCNs.

DECIMAL VALUES FOR LETTERS AND NUMBERS IN THE PREFIX

"A" = 11 "B" = 13 "C" = 17 "D" = 19 "E" = 23 "F" = 29 "G" = 31 "H" = 37 "I" = 41 "J" = 43 "K" = 47 "L" = 53 "M" = 59 "N" = 61 "O" = 67 "P" = 71 "Q" = 73 "R" = 79 "S" = 83 "T" = 89 "U" = 97 "V" = 101 "W" = 103


"X" = 107 "Y" = 109 "Z" = 113 "0" = 127 "1" = 131 "2" = 137 "3" = 139 "4" = 149 "5" = 151 "6" = 157 "7" = 163 "8" = 167 "9" = 173

CURRENTLY ASSIGNED NLS PREFIXES

TYPE LOCATION COUNTY PREFIX

NLS CRIMINAL Franklin Station Baltimore Co. BC3

Carroll Co. Detention Center Carroll CRD

NLS HAZMAT Salisbury Wicomico WIA

Waldorf Charles CHB

Belair Harford HFC

Glen Burnie Anne Arundel AAD

Frederick Frederick FRE

SAMPLE DATA

The first few PCNs generated at Waldorf in 2004 should be - CHB 040 000 016CHB 040 000 020CHB 040 000 031

The first few PCNs generated at Franklin Station in 2005 should be –BC3 050 000 015BC3 050 000 026BC3 050 000 030


TRACKING NUMBER STANDARD FORMATS

The tracking number is an 8 character alphanumeric space filled to 15 characters or 12-character numeric space filled to 15 characters. In the 8 character alphanumeric number, the first six characters are numeric, the seventh character is alphabetic and the eighth character is a numeric check digit.

For the number NNNNNNXC, N is numeric and X is Alphabetic and C is a Mod-7 check digit computed based on the first six digits - i.e. the remainder of NNNNNN divided by 7 must = C

EXAMPLES –

000000A0000001B1000002C2000003D3000004E4000005F5000006G6000007H0000008X1000009Z2

In the 12 character numeric number, the 12th digit is a Mod-7 check digit.

For the number NNNNNNNNNNNC, C IS THE MOD-7 CHECK DIGIT FOR NNNNNNNNNNN - I.E. THE REMAINDER OF NNNNNNNNNNN DIVIDED BY 7 MUST = C.

EXAMPLES - 949000000001 059000000006 949000000012 059000000010 949000000023 059000000021 949000000034 059000000032 949000000045 059000000043 949000000056 059000000054 949000000060 059000000065 949000000071 059000000076

WHENEVER THE NUMBER IS DISPLAYED IN HUMAN READABLE FORM IT SHOULD BE FORMATTED IN GROUPS OF THREE AS -

NNN NNN NNN NNNOr

NNN NNN XN

EXAMPLES - 949 000 000 071123 456 A4


€¦ · web viewpage 42, section 3.11, pm.7 - please clarify if pmbok should be the abbreviation...

Documents