The file's text, extracted by GovTribe without its formatting.
ATTACHMENT 8
Solicitation SP4703-17-R-CB01 Electronic Point of Sale (EPoS) and Supporting Services Factor 2: Solution Demonstration
The Solution Demonstration will be evaluated in two steps.
STEP 1: MATERIALLY THE SAME
The Government will assess whether an Offeror’s Solution Demonstration is deemed compliant with the instructions and presents a demonstration that is “materially the same” as their proposed Technical Approach.
The Government defines ‘materially the same’ to be the approach and the technologies used to address Solution Demonstration scenarios that are the same as the corresponding areas in the submitted technical approach.
Further, the Government defines approach as the Offeror’s solution architecture and the technologies that consist of demonstrated COTS and developed software.
Offers submitted for consideration will have the mobile and fixed solutions rated individually. This will allow offers to be submitted for either fixed, mobile, or both solutions without penalizing an offer that does not have a solution to one of the devices.
Step 1 Ratings
Color/Adjectival Rating Description
Acceptable Green The Offeror’s Solution Demonstration uses concepts or technologies that are “materially the same” as its proposed Technical Approach.
Move to Step 2 Scenarios
Unacceptable Red The Offeror’s Solution Demonstration introduces concepts or technologies that are not “materially the same” as its proposed Technical Approach. Proposal does not meet requirements and contains one or more deficiencies (fails).
Move to overall rating with Solution Demonstration as Unacceptable (Unawardable).
STEP 2: SCENARIOS
If the Offeror’s Solution Demonstration is “materially the same” as their proposed Technical Approach, then the responses to the scenarios will be rated against the criteria in the table below.
SCENARIO 1 – FIXED FACILITY DEVICES
The Government will rate Scenario 1 for fixed facility device Offerors. The overall scenario weight is 100% of the overall rating for the technical solution for the fixed facility device. Each Key action is assigned a weight in the table below. Each individual step is assigned total points possible. The points will be added and will factor into the overall rating based on that actions weight. Vendors will not be penalized if there solution is not intended to provide fixed facility operations.
SCENARIO 1
FIXED FACILITY OPERATIONS RATING SHEET
Scenario Weight 100%
| Description |
| Possible Task Points |
| Demo |
Task Points
| Action Weight |
| Demo Action Score (%) |
| Action 1 |
| Purchase Media Authentication |
| Variation 1 |
| Communications Protocol |
| Vendor Documentation shows that application will authenticate using XML communication to Simple Object Access Protocol (SOAP) Web Services. Documentation will demonstrate that all external communication used by the application will leverage WS_SECURE. |
| 10 |
| The user inserts purchase media into the device (pedestal), enters odometer reading, and then inserts ID card once |
| 10 |
| The system authenticates the purchase media against the enterprise repository. (*Note: vendor will simulate all authentication.) |
| 10 |
| Transaction is complete |
| 10 |
| Variation 2 |
| Execute variation 1 with a card that is not authorized to purchase product |
| Transaction is denied and user receives a visual notification to contact the card provider, or the facility operator |
| 10 |
| Transaction is complete |
| 10 |
| Variation 3 |
| Execute variation 1 with an authorized purchase media to blacklist (Simulate loss of network communication to Enterprise). |
| The system authenticates the purchase media against the blacklist because communication is lost. (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 10 |
| Variation 4 |
| Execute variation 1 with an unauthorized purchase media to blacklist (Simulate loss of network communication to Enterprise). |
| Transaction is denied and user receives a visual notification to contact the card provider, or the facility operator |
| 10 |
| Total Action 1 Task Points |
| 100 |
| Demo Action 1 Score |
| 40.00% |
| Action 2 |
| Customer Identification |
| Variation 1 |
| Personal Identity Verification (PIV)) |
| Customer will insert PIV/Common Access Card (CAC) |
| 25 |
| Device will store users full name and Electronic Data Interchange Personal Identifier (EPIDI) |
| 25 |
| Variation 2 |
| Driver’s License |
| Customer will insert Driver’s License |
| 25 |
| Device will store customers full name and ID number |
| 25 |
| Total Action 2 Task Points |
| 100 |
| Demo Action 2 Score |
| 10.00% |
| User is prompted to select the desired pump number to activate |
| 11 |
| The pump activates and the product is dispensed |
| 12 |
| Transaction completes and the total quantity is stored in the device with the identification information and billing information from the purchase media |
| 11 |
| The information is transmitted to the enterprise |
| 11 |
| The device prompts for receipt printing |
| 11 |
| Variation 1 |
| Printing Receipt |
| Printing is selected and receipt is printed |
| 11 |
| Transaction is complete |
| 11 |
| Variation 2 |
| No Receipt Printed |
| Printing is not selected and no receipt is printed |
| 11 |
| Transaction is complete |
| 11 |
Total Action 3 Task Points
| Demo Action 3 Score |
| 10.00% |
| Action 4 |
| Transmission of Data to Enterprise |
| Variation 1 |
| Successful Transmission |
| Completed transaction is transmitted to Enterprise. (*Note: vendor will simulate transmission and provide a copy of the transmitted output with documentation.) |
| 20 |
| Variation 2 |
| Fails to Transmit to Enterprise |
| Information is stored and transmitted when communication is restored. |
| 20 |
| Communication is restored and data is successfully transmitted to Enterprise |
| 20 |
| Variation 3 |
| Transmission to Enterprise is not viable |
| Information is manually downloaded and transmitted through external system (Email). |
| 20 |
| Downloaded information must be encrypted and not editable |
| 20 |
| Total Action 4 Task Points |
| 100 |
| Demo Action 4 Score |
| 40.00% |
FIXED DEVICE SUMMARY SCORE AND RATING
| Scenario 1 Summary |
| Possible Score |
| Demo Action Scores |
| Action 1: Purchase Media Authentication |
| 40.00% |
| Action 2: Customer Identification |
| 10.00% |
| Action 3: Fuel Dispensing |
| 10.00% |
| Action 4: Transmission of Data to Enterprise |
| 40.00% |
Rating based on Total Demo Score and table below
Step 2 Ratings:
| Rating |
| Demo Action Score Range |
| Description |
Outstanding Blue
| 100% |
| Demonstration indicates an exceptional approach and understanding of the requirements and contains multiple strengths, and risk of unsuccessful performance is low. |
Good Purple
| 75.00 – 99.99% |
| Demonstration indicates a thorough approach and understanding of the requirements and contains at least one strength, and risk of unsuccessful performance is low to moderate. |
Acceptable Green
| 50.00 – 74.99% |
| Demonstration meets requirements and indicates an adequate approach and understanding of the requirements, and risk of unsuccessful performance is no worse than moderate. |
Marginal Yellow
| 25.00 – 49.99% |
| Demonstration has not demonstrated an adequate approach and understanding of the requirements, and/or risk of unsuccessful performance is high. |
Unacceptable Red
| 0 – 24.99% |
| Demonstration does not meet requirements of the solicitation, and thus, contains one or more deficiencies, and/or risk of unsuccessful performance is unacceptable. Demonstration is unacceptable. |
MOBILE DEVICES – SCENARIOS 2, 3, 4
The Government will rate Scenarios 2, 3 and 4 for mobile device respondents. The overall scenario weight will total 100% of the overall for the mobile device offering. Each scenario identified in the tables below have independent weights that will be used to calculate the overall rating of the offer. Each Key action is assigned a weight in the table below. Each individual step is assigned total points possible. The points will be added and will factor into the rating based on that actions weight. The actions weight will be used to calculate the overall scenario rating. Vendors will not be penalized if there solution is not intended to provide mobile operations.
SCENARIO 2 – MOBILE DEVICES
SCENARIO 2
MOBILE SALE/CREDIT/REISSUE OPERATIONS
Scenario Weight 50%
| Description |
| Possible Task Points |
| Demo |
Task Points
| Action Weight |
| Demo Action Score (%) |
| Action 1 |
| User Authentication |
| User Will Insert CAC card and log in to device |
| 12 |
| Variation 1 |
| Valid CAC/PIV |
| Users CAC/PIV card will be authenticated against CRL. (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 11 |
| User will be authenticated against AD (Vendor will simulate AD authentication). (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 11 |
| Vendor documentation will provide evidence that AD integration is incorporated into device operating system |
| 11 |
| Variation 2 |
| Invalid CAC/PIV |
| User CAC/PIV card will be authenticated against CRL. (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 11 |
| User will not be allowed to log into device |
| 11 |
| Variation 3 |
| Valid CAC/PIV No User Account in AD |
| User CAC/PIV card will be authenticated against CRL. (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 11 |
| User will be authenticated against AD (Vendor will simulate AD authentication). (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 11 |
| User will not be allowed to log into device |
| 11 |
| Total Action 1 Task Points |
| 100 |
| Demo Action 1 Score = Demo Task Points / Possible Task Points |
| 15.00% |
| Action 2 |
| Operator Selects Transaction Type |
| Operator Selects Drop Down for Transaction Type |
| 50 |
| All Transaction Types are listed |
| 50 |
| Demo Action 2 Score |
| 5.00% |
| Action 3 |
| Purchase Medium Authentication |
| The operator has the purchaser present purchase medium and identification |
| 9 |
| Variation 1 |
| Capitalized Source Media With Network Connectivity |
| The mobile device will authenticate the purchase media and authorize the transaction. ( *Note: vendor will simulate authentication and communications to enterprise.) |
| 10 |
| Variation 2 |
| Capitalized Source Media Without Network Connectivity |
| The mobile device will authenticate the purchase media against the self-contained blacklist and authorize the transaction. (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 9 |
| Variation 3 |
| Non-Capitalized Source Media with Network Connectivity |
| Mobile device will scan QR code |
| 9 |
| The mobile device will authenticate the purchase media and authorize the transaction. (*Note: vendor will simulate authentication and communications to enterprise.) |
| 9 |
| Variation 4 |
| Non-Capitalized Source Media without Network Connectivity |
| Mobile device will scan QR code |
| 9 |
| Device will store information from QR code and will not authenticate |
| 9 |
| Variation 5 |
| Customer with No Source Media with Network Connectivity |
| The operator will manually input purchaser information |
| 9 |
| Manually input information will be authenticated at enterprise. (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 9 |
| Variation 6 |
| Customer with No Source Media without Network Connectivity |
| The operator will manually input purchaser information |
| 9 |
| Manually input information will be stored and no authentication will occur |
| 9 |
| Total Action 3 Task Points |
| 100 |
| Demo Action 3 Score |
| 20.00% |
| Action 4 |
| Customer Identification |
| Variation 1 |
| Customer presents CAC/PIV |
| The operator will scan the purchaser’s PIV |
| 25 |
| The device stores the purchaser’s full name from the identification |
| 25 |
| Variation 2 |
| Customer Does not present CAC/PIV |
| The operator manually inputs the purchaser’s full name |
| 25 |
| Devices Stores customers full name |
| 25 |
| Demo Action 4 Score |
| 5.00% |
| The operator selects the desired operation |
| 15 |
| The operator scans the refueling equipment identification QR code |
| 15 |
| Variation 1 |
| Using Default Unit of Measure |
| The operator does not select the option to use an alternate unit of measure |
| 10 |
| The default unit of measure is used for the transaction |
| 15 |
| Variation 2 |
| User Selects Alternate Unit of Measure |
| The operator selects the option to use an alternate unit of measure |
| 15 |
| The operator selects the desired Unit of Measure from the dropdown list |
| 15 |
| The selected unit of measure is used for the transaction |
| 15 |
| Demo Action 5 Score |
| 5.00% |
| The operator selects to input a memo/comment |
| 50 |
| Total Action 6 Task Points |
| 100 |
| Demo Action 6 Score |
| 5.00% |
| Action 7 |
| Quantity Determination |
| Variation 1 |
| If the equipment has a meter that dynamically generates meter information as a QR Code |
| The operator will scan the beginning QR Code |
| 10 |
| The operator will complete the fuel movement |
| 15 |
| The operator will can the ending QR code |
| 15 |
| The mobile software will calculate the total quantity of the fuel movement by calculating the difference between the beginning and ending totalizer value obtained from the dynamic QR codes |
| 15 |
| Variation 2 |
| If the equipment meter does not have a dynamically generated QR code |
| The operator completes the fueling operation |
| 15 |
| The operator scans the meter for OCR recognition, or manually input the total quantity of the transaction |
| 15 |
| The mobile software converts the quantity scanned/manually input to 60 degrees using the specified conversion factor for the product |
| 15 |
| Total Action 7 Task Points |
| 100 |
| Demo Action 7 Score |
| 15.00% |
| Action 8 |
| Completing Transaction |
| The receiver electronically signs for the receipt if a PIV card was not used to identify the receiver |
| 20 |
| The transaction data is transmitted to the enterprise |
| 20 |
| Variation 1 |
| Print is selected |
| Variation 2 |
| Print is not selected |
| Total Action 8 Task Points |
| 100 |
| Demo Action 8 Score |
| 10.00% |
| Action 9 |
| Transmission To Enterprise |
| Variation 1 |
| Successful Transmission |
| Transaction is transmitted to Enterprise Successfully and cleared from device |
| 20 |
| Variation 2 |
| Unsuccessful Transmission |
| Transaction is stored on Device for future transmission |
| 20 |
| Communication is restored and transaction is successfully transmitted |
| 20 |
| Variation 3 |
| Communication is not possible |
| Information is manually downloaded for transmittal by external method |
| 20 |
| Downloaded information is encrypted and cannot be edited or changed |
| 20 |
| Total Action 9 Task Points |
| 100 |
| Demo Action 9 Score |
| 20.00% |
| Scenario 2 Summary |
| Possible Score |
| Demo Action Scores |
| Action 1: User Authentication |
| 15.00% |
| Action 2: Operator Selects Transaction Type |
| 5.00% |
| Action 3: Purchase Medium Authentication |
| 20.00% |
| Action 4: Customer Identification |
| 5.00% |
| Action 5: Fuel Dispensing |
| 5.00% |
| Action 6: Memo Input |
| 5.00% |
| Action 7: Quantity Determination |
| 15.00% |
| Action 8: Completing Transaction |
| 10.00% |
| Action 9: Transmission to Enterprise |
| 20.00% |
SCENARIO 3 – MOBILE DEVICES
SCENARIO 3
MOBILE INFLIGHT/REISSUE OPERATIONS
Scenario Weight 15%
| Description |
| Possible Task Points |
| Demo |
Task Points
| Action Weight |
| Demo Action Score (%) |
| Action 1 |
| Data Radio is Turned Off |
| Operator Turns of Radio |
| 50 |
| Device does emit any Radio Transmissions |
| 50 |
| Total Action 1 Task Points |
| 100 |
| Demo Action 1 Score |
| 5.00% |
| Action 2 |
| User Authentication |
| User Will Insert CAC card and log in to device |
| 25 |
| Variation 1 |
| Valid CAC/PIV |
| Users CAC/PIV card will be authenticated against CRL. (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 25 |
| Variation 2 |
| Invalid CAC/PIV |
| User CAC/PIV card will be authenticated against CRL. (Vendor will demonstrate that the system can output a an xml file to a web service and receive an acknowledgment.) |
| 25 |
| User will not be allowed to log into device |
| 25 |
| Total Action 2 Task Points |
| 100 |
| Demo Action 2 Score |
| 10.00% |
| Action 3 |
| Transaction Type Selection |
| Operator selects transaction type |
| 50 |
| Operator selects INFLIGHT |
| 50 |
| Total Action 3 Task Points |
| 100 |
| Demo Action 3 Score |
| 10.00% |
| Action 4 |
| Inflight Transaction |
| The operator inputs the receiving aircraft tail number |
| 50 |
| The operator inputs a mission number |
| 50 |
| Total Action 4 Task Points |
| 100 |
| Demo Action 4 Score |
| 15.00% |
| The operator selects to input a memo/comment |
| 50 |
| Total Action 5 Task Points |
| 100 |
| Demo Action 5 Score |
| 10.00% |
| Action 6 |
| Completion of Transaction |
| The operator manually inputs the total quantity of the transaction |
| 50 |
| The operator is prompted to input additional transactions |
| 25 |
| Additional transactions are entered |
| 25 |
| Total Action 6 Task Points |
| 100 |
| Demo Action 6 Score |
| 20.00% |
| Action 7 |
| Data is Saved for Later Transmission to Enterprise |
| The information is stored for later transmitted to Enterprise |
| 25 |
| Transactions are transmitted to Enterprise |
| 25 |
| Transaction is Complete |
| 25 |
| Total Action 7 Task Points |
| 100 |
| Demo Action 7 Score |
| 30.00% |
| Scenario 3 Summary |
| Possible Score |
| Demo Action Scores |
| Action 1: Data Radio is Turned Off |
| 5.00% |
| Action 2: User Authentication |
| 10.00% |
| Action 3: Transaction Type Selection |
| 10.00% |
| Action 4: Inflight Transaction |
| 15.00% |
| Action 5: Memo Input |
| 10.00% |
| Action 6: Completion of Transaction |
| 20% |
| Action 7: Data is Saved for Later Transmission to Enterprise |
| 15% |
SCENARIO 4 – MOBILE DEVICES
| SCENARIO 4 FUEL HEADER OPERATIONS |
| Scenario Weight 35% |
| Description |
| Possible Task Points |
| Demo |
Task Points
| Action Weight |
| Demo Action Score (%) |
| Action 1 |
| Shipment Transfer |
| The operator selects the quantity determination method from a list of options* |
| 3 |
| The operator has the option of changing the unit of measure from the default US Gallons from a list of options* |
| 3 |
| The operator will indicate if they are using a meter that dynamically generates meter information in the form of a QR code |
| 3 |
| If yes, the operator will scan the beginning QR code prior to the fuel movement |
| 3 |
| If no, action is not required |
| 3 |
| The operator enters the following information |
| 3 |
| The operator will enter the following required fields dependent on the type of meter |
| 3 |
| If the operator indicated using a meter that dynamically generates QR codes and provides user information |
| 3 |
| The ending QR Code will be scanned |
| 3 |
| Gross Quantity will be calculated by comparing the beginning and ending totalizer |
| 3 |
| Net Quantity will be the same value as gross quantity |
| 3 |
| User will input Standard Density |
| 3 |
| User will input Observed Temperature |
| 3 |
| If the operator indicated they are not using a meter that dynamically generates QR codes the user will manually enter the following information |
| 3 |
| The operator enters the following optional fields for each |
| 3 |
| The operator selects the option of adding comments |
| 3 |
| The operator indicates the operation is complete |
| 3 |
| The operator is prompted to review and confirm all inputs |
| 3 |
| The data is transmitted to enterprise |
| 3 |
| The operator is prompted to enter an additional transaction |
| 3 |
| Total Action 1 Task Points |
| 100 |
| Demo Action 1 Score |
| 33.33% |
| Action 2 |
| Contract Receipt |
| The operator is prompted to confirm that the fuel type being received matches the type of the equipment that was scanned |
| 4 |
| The operator selects the quantity determination method from a list of options* |
| 5 |
| The operator has the option of changing the unit of measure from the default US Gallons from a list of options * |
| 5 |
| The operator updates the date that the movement began |
| 5 |
| The operator inputs the following information |
| 5 |
| Acceptor name is obtained from the users CAC Card |
| 5 |
| Gross weight (required if quantity determination method is weight conversion) |
| 5 |
| Acceptor email is obtained from the users CAC Card |
| 5 |
| Acceptor enters his phone number |
| 5 |
| Acceptor enters his title |
| 5 |
| The operator enters text comments |
| 5 |
| The operator is prompted to scan shipping documents |
| 5 |
| The operator is allowed to scan up to 10 documents |
| 5 |
| The operator is prompted to select the type of document |
| 5 |
| Documents are named as the document type id + a 40-character unique ID |
| 5 |
| The operator indicates the operation is complete |
| 4 |
| The operator is prompted to review and confirm all inputs |
| 4 |
| The data is transmitted to enterprise |
| 4 |
| The operator is prompted to enter an additional transaction |
| 4 |
| Total Action 2 Task Points |
| 100 |
| Demo Action 2 Score |
| 33.33% |
| Action 3 |
| Transfer Receipt |
| The operator is prompted to confirm that the fuel type being received matches the type of the equipment that was scanned |
| 6 |
| The operator selects the quantity determination method from a list of options * |
| 6 |
| The operator has the option of changing the unit of measure from the default US Gallons from a list of options * |
| 6 |
| The operator updates the date that the movement began |
| 6 |
| The operator inputs the following information |
| 6 |
| Batch Cargo Number (Optional) |
| 6 |
| Gross Weight (Required only if quantity determination method is Weight Conversion) |
| 6 |
| The operator enters text comments |
| 6 |
| The operator is prompted to scan shipping documents |
| 8 |
| The operator is prompted to select the type of document |
| 6 |
| The operator indicates the at the operation is complete |
| 6 |
| The operator is prompted to review and confirm all inputs |
| 6 |
| The data is transmitted to enterprise |
| 8 |
| The operator is prompted to enter an additional transaction |
| 6 |
| Total Action 3 Task Points |
| 100 |
| Demo Action 3 Score |
| 33.34% |
* The additional transaction prepopulates screen fields identified with * with the previously entered information
| Scenario 4 Summary |
| Possible Score |
| Demo Action Scores |
| Action 1: Shipment Transfer |
| 33.33% |
| Action 2: Contract Receipt |
| 33.33% |
| Action 3: Transfer Receipt |
| 33.34% |
MOBILE DEVICE SUMMARY SCORE AND RATING
| SCENARIO |
| Weight |
| Demo Score |
| Scenario 2: MOBILE SALE/CREDIT/REISSUE OPERATIONS |
| 50% |
| Scenario 3: MOBILE INFLIGHT/REISSUE OPERATIONS |
| 15% |
| Scenario 4: FUEL HEADER OPERATIONS |
| 35% |
Rating based on Total Demo Score and table below
Step 2 Ratings:
Color/Adjectival Rating
| Demo Action Score Range |
| Description |
Outstanding Blue
| 100% |
| Demonstration indicates an exceptional approach and understanding of the requirements and contains multiple strengths, and risk of unsuccessful performance is low. |
Good Purple
| 75.00 – 99.99% |
| Demonstration indicates a thorough approach and understanding of the requirements and contains at least one strength, and risk of unsuccessful performance is low to moderate. |
Acceptable Green
| 50.00 – 74.99% |
| Demonstration meets requirements and indicates an adequate approach and understanding of the requirements, and risk of unsuccessful performance is no worse than moderate. |
Marginal Yellow
| 25.00 – 49.99% |
| Demonstration has not demonstrated an adequate approach and understanding of the requirements, and/or risk of unsuccessful performance is high. |
Unacceptable Red
| 0 – 24.99% |
| Demonstration does not meet requirements of the solicitation, and thus, contains one or more deficiencies, and/or risk of unsuccessful performance is unacceptable. Demonstration is unacceptable. |
Defense Logistics Agency Aviation