M00264-17-R-0025_amend_0002.pdf
PDF 299 KB Posted
- Solicitation number
- M00264-17-R-0025
- Issued by
-
United States Marine Corps
About this file
Solicitation amendment to provide Government responses to Contractor submitted questions, remove the mobile application development from the PWS, and correct the delivery associated with line item 0001 from NLT 90 days ADC to 140 days ADC.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| M00264-17-R-0025.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
M3000417SUFE004
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83)
Prescribed by GSA
FAR (48 CFR) 53.243
The purpose of this solicitation amendment is to provide Government responses to Contractor submitted questions, remove the mobile application development from the PWS, and correct the delivery associated w ith line item 0001 from NLT 90 days ADC to 140 days ADC.
1. CONTRACT ID CODE PAGE OF PAGES
J 1 20
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 02-Aug-2017
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X M00264-17-R-0025
X 9B. DATED (SEE ITEM 11)
07-Jul-2017
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
02-Aug-2017
CODE
RCO-NCR, MCB QUANTICO
2010 HENDERSON RD.
QUANTICO VA 22134
M00264 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
M00264-17-R-0025
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION SF 1449 - CONTINUATION SHEET
SOLICITATION/CONTRACT FORM
The required response date/time has changed from 31-Jul-2017 12:00 PM to 11-Aug-2017 12:00 PM.
SUPPLIES OR SERVICES AND PRICES
CLIN 0001
The CLIN extended description has changed from:
Development of Sikes Act Permit Sales & Dispersed Recreation Access Management Services (SAPDRAMS) in accordance with the PWS.
To:
Development of Sikes Act Permit Sales & Dispersed Recreation Access Management Services (SAPDRAMS) system in accordance with the PWS.
DELIVERIES AND PERFORMANCE
The following Delivery Schedule item for CLIN 0001 has been changed from:
DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /
CAGE
90 dys. ADC 1 M30004
JOHN H. ROHM
RHUL STREET BLDG 3227
QUANTICO VA 22134
FOB: Destination
M30004
140 dys. ADC 1 M30004
JOHN H. ROHM
RHUL STREET BLDG 3227
QUANTICO VA 22134
The following Delivery Schedule item for CLIN 1001 has been changed from:
POP 01-DEC-2017 TO
30-NOV-2018
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
POP 01-FEB-2018 TO
31-JAN-2019
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
The following Delivery Schedule item for CLIN 2001 has been changed from:
POP 01-DEC-2018 TO
30-NOV-2019
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
POP 01-FEB-2019 TO
31-JAN-2020
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
The following Delivery Schedule item for CLIN 3001 has been changed from:
POP 01-DEC-2019 TO
30-NOV-2020
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
POP 01-FEB-2020 TO
31-JAN-2021
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
The following Delivery Schedule item for CLIN 4001 has been changed from:
POP 01-DEC-2020 TO
30-NOV-2021
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
POP 01-FEB-2021 TO
31-JAN-2022
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
The following Delivery Schedule item for CLIN 5001 has been changed from:
POP 01-DEC-2021 TO
31-MAY-2022
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
POP 01-FEB-2022 TO
31-JUL-2022
N/A M30004
3250 CATLIN AVENUE
BUILDING 3049
QUANTICO VA 22134
JOHN H. ROHM
703-432-0522
The following have been added by full text:
QUESTIONS AND ANSWERS
Question #1: Page 15, Section 4 FORMAT OF QUOTE – What are the page limitations for each Quote Volumes?
Government Response #1: Page count limitations have been established within the FAR 52.212-1 addendum in the solicitation.
Question #2: Page 15, Section 4 FORMAT OF QUOTE – What is the page format required? 12-point font, double-sided, table font, graphics, etc.?
Government Response #2: Format requirements have been established within the FAR 52.212-1 addendum in the
Question #3: Page 20, Page Section 2.1.2.2 - CALL FEATURES OF TELEPHONE SYSTEM - Regarding
“customers or administrative staff can receive calls from outbound calling system as notifications or reminders,” would text suffice in place of outbound calls or does MCBQ prefer automated outbound calling capability specifically?
Government Response #3: Texts messages will suffice for this requirement; the PWS has been updated accordingly
Question #4: Page 20, 2.1.2.3 - CALL-IN RESERVATION SERVICE - Regarding, “reservations can be created for certain days of the week and times of day,” how many days out does MCBQ anticipate allowing users to make reservations?
Government Response #4: Most reservations are the day prior to the activity. However, the Government requires the ability to Skip/ blackout any day (or days) of choosing. For example, there could be several days where the base is closed for an activity Christmas Eve (Friday), Christmas Day (Sat) and Sunday. In this instance, the user would be making a reservation on a Thursday for a Monday activity.
Question #5: Your current permit/licensing process requires the submission of an application and visit to the Game
Checking Station. How much in the way of in-person participation do you see being required with the new system?
If you prefer most of it be done online, how would you handle confirming photo IDs, state licenses, ink signatures, and verification that the required videos have indeed been watched, etc…
Government Response #5: All users will have to come to GCS prior to their account becoming active to verify identity and initiate background check. They should be permitted to create an account prior to coming to check station but will not be able to check in or out or buy licenses until GCS personnel activates their account.
Comprehension of training videos will be verified by a quiz and an acknowledgement by the user stating they watched the video and understand all the material contained in it.
Question #6: What type of system/devices do you have in use currently for check in/out purposes, if any? (Generic mobile apps/GPS tracking tools/SPOT devices/bulletin boards, etc.)
Government Response #6: MCB, Quantico currently utilizes a telephone reservation system for hunters. Under this system, each hunter is furnished with an ID card with a unique bar code after a reservation is made. This ID card is used to allow hunters to access the training area and tracks when hunters return, as well. The card readers are linked to a local non-networked server that records all pertinent data. Hunting is the only activity required currently to check in and out. Under this requirement, many other user groups will be required to check in and out, as well..
Question #7: Are you interested in a fully custom solution that is tailored to your every need and integrated with all systems; or a familiar, existing open source CMS or COTS system that is customized to suit your requirements? Do you have examples of existing systems you have seen that may have framed your expectations? (conversely, any that you know and have a distaste for?)
Government Response #7: The system either existing or newly created must meet the requirements outlined. As long as it meets those requirements either is acceptable.
Question #8: Roughly how many pages of ‘static’ content would you say the public-facing portion of the site will have?
Government Response #8: The Offeror’s proposed technical solution should address the requirements of the PWS;
an acceptable solution may contain as many pages as necessary to fulfil the requirements of the PWS.
Question #9: Will videos be hosted or will you make use of outside services (YouTube, Vimeo etc).
Government Response #9: Videos must be hosted on the site developed for this requirement.
Question #10: How many MCBQ administrators and equivalents from other organizations are there?
Government Response #10: It will depend on what roles an administrator has; 2-3 Government personnel will need full access to create permits and modify content and up to 10 Government personnel will require access to update profiles, enter in open and closed areas, and similar small tasks that the general public will not have access to.
Question #11: Are the MCBQ websites considered to be mutually exclusive in that the conservation law enforcement officers and the range control schedulers will always be separate, for example? How many websites are there?
Government Response #11: The Government requires a page or section of the site exclusively for handling of permits, activity management, and license sales. Further, the Government requires a page or section of the site exclusively for range scheduling (what is open and closed for a day). Also, the Government requires a page or section of the site exclusively for conservation law enforcement. Acceptable solutions to the Government’s requirement may include different sites, pages, or just restricted based on user roles. The developer has the freedom to design the system the way they deem most appropriate based on stated requirements. However, the Government requires for at least 2-3 lead administrators to be granted with the ability to modify all section/areas of the site.
Question #12: Does the MCBQ administrator resolve information conflicts between these separate web sites?
Government Response #12: There must be at least 2-3 Government administrators who have the ability to modify all sections/areas of the site(s).
Question #13: What are examples of “variables” in 2.1.1.2 on page 18 of 24?
Government Response #13: MCBQ will need the ability to modify the content on the sites. The Government will require the ability to build/delete as many different permits as it needs, to add/delete types of activities, and to add/delete areas available for recreation. These and other examples are stated in section 2.1.1.2 with the sentence
“For example,….
Question #14: Is there existing pay.gov interface for any existing MCBQ systems currently or will this system be the first time MCBQ payments are processed in this fashion?
Government Response #14: This will be first time MCBQ payments are processed in this fashion.
Question #14: It is assumed that check-in and check-out are intended to tracking who is supposedly onsite at any time. How does remote (via computer at home) + 1 hour commute to the government property work out? Is the government satisfied with remote/distant check-in? I95 can be slow?
Government Response #14: The Government expects remote/distant access to the check-in/out process and understands that there may be delays in a user’s real time occupation of an area.
Question #15: Is access to the government property by reservation only?
Government Response #15: A reservation is not required but recommended for those activities that have limited space. The day of the activity, regardless if the user has a spot reserved or not, they must check into the system and, once they complete the activity, check out of the system.
Question #16: Is each person listed on a permit required to have their own CMS account?
Government Response #16: All users must have an account (register with system). And each user will need to have a permit for the activities they want to conduct. Some accounts will need restrictions. For example, a minor will definitely need an account. They will also need to get a zero dollar permit for the activity they want to participate in but will not be able to check in or check out without being linked to an adult.
Question #17: Can reservations be made by phone? 2.1.2.1 says “Reservations of daily access passes can be done online or through telephone check-in/out.” This statement indicates reservations can also be made by phone. Prior to reading this statement it was assumed the business rule was check-in/out could only be done to a pre approved reservation?
Government Response #17: Yes, reservations can be made by phone or online the day prior to the activity. The day of the activity, check-in and out of an assigned area can be completed by phone or online.
Question #18: Does pay.gov provide the processes (on that site) to handle refunds or other payment corrections?
Government Response #18: All sales will be final. If there is a system failure that erroneously charges a customer the wrong amount, local staff will resolve the matter. If the user makes a mistake and buys the wrong license, there will be no refund. There should be an acknowledgement statement the user checks prior to submitting payment.
Question #19: 2.1.2.1, Is the MCBQ toll free number going to forward calls to the contractor’s telephone stack or is the toll free number being installed on the contractor’s telephone stack?
Government Response #19: The Contractor will establish the toll free number and be responsible for creating and operating the telephone system.
Question #20: 2.1.1.5, Are permits for only one customer or for groups of customers? If a permit can be for a group of customers, does each member of the group have to have their own account? Also, can one person pay for the group permit or does each person have to pay their own portion or permit? If the permits are separate for each customer, how are group reservations to be handled? As per 2.1.1.8 it is assumed a customer (member of a group) who is put on admin hold does not hold the entire (group) permit, is this true?
Government Response #20: Permits will be on the individual basis. Each person must have their own account.
Question #21: 2.1.1.5 and 2.1.2.16, since there are various mobile devices available, can the “mobile” application be a web application that is accessible via the mobile device or is a specific iTunes and Google Store application required? Are Windows mobile device apps also required?
Government Response #21: The mobile application requirement has been removed from the PWS.
Question #22: 2.1.4, Is it correct to understand the CMS will be required to be installed at .mil?
http://pay.gov/ http://pay.gov/
Government Response #22: No it will not be installed on the .mil domain. It will be hosted by the contractor.
Question #23: 2.2.2, Specifically, what vendors regarding warranty repair are discussed here?
Government Response #23: If something goes wrong with the system provided by the contractor, the contractor will be required to fix the system and resolve the problem at no additional cost to the government.
Question #24: 2.1.1.5, Is a kiosk or other self-service GFE + printer intended at the MCBQ Game Checking Station?
Government Response #24: No kiosk or self-service equipment will be needed.
Question #25: Is there a current database that maintains the background checks and status or persons purchasing records?
Government Response #25: An MS Access database is currently utilized to store and manage historical and current data; however, MCB, Quantico does not currently keep purchasing records by user.
Question #26: Will the current background checks and approvals for permitted persons be provided for integration into the SAPDRAMS database?
Government Response #26: SAPDRAMS database will only maintain the status of the background check and send reminders when one is about to expire. Staff will need to unlock and lock accounts based on the status of the background check.
Question #27: Does historical and current activity data, including harvest data and permit information, currently exist in a SOR?
Government Response #27: An MS Access database is currently utilized to store and manage historical and current data.
Question #28: In 2.1.1.5 wood cutting is mentioned as a sales category SAPDRAMS interface with the pay.gov system. What other activities will the SAPDRAMS permitting system need to handle?
Government Response #28: Fire wood cutting sales will go to forestry account at Defense Finance Accounting
Service (DFAS) The hunting and fishing sales will go to wildlife fee account at DFAS. The Government requires the ability to add other permit sales to the system as the need arises. Other activities that will require permits include bike riding, greenery picking, wildlife viewing; however, these activities are available free of charge.
Question #29: For CLIN 0001, the government lists quantity of 1 with unit of each; are we correct that this is a total price for the base year services (encompassing all development, materials, software, and subscription servicing)?
Government Response #29: Line item 0001 solicits the proposed total firm fixed price for the development and delivery of the SAPDRAMS web based system. As provided within the “Delivery Information” section, the
Government requires the system development, delivery, inspection, and acceptance process to be achieved NLT 140 days after the date of contract award. After the SAPDRAMS system is inspected and accepted under line item 0001, line item 1001 may be exercised and funded by the Government so long as the Contractor fulfills the mandatory criteria at PWS 2.1.4 and 2.2.1.
Question #30: For CLINs 1001, 2001, 3001, 4001, and 5001 the government has a quantity of 12 with a unit of each;
are we correct that this amount is a monthly charge for all support requirements expected or proposed for
SAPDRAMS?
Government Response #30: Yes
Question #31: Under Delivery Information of the RFQ (pg 6 of 24, CLIN 001) the government states the delivery date of 90 dys. ADC; please define what ADC means.
Government Response #31: After Date of Contract award
Question #32: Under Delivery Information of the RFQ (pg. 6 of 24) the government indicates that Option Period 1 will begin on 01 Dec 2017 and end on 30 Nov 2018, with all other option periods following. In the PWS (Section 5) the government states the Base period is a 12-month period of performance. What is the correct base period, and when does the government plan to award this work to meet these dates?
Government Response #32: Please see Government response to question #29
Question #33: Clause 52.217-9 (pg 14 of 24) has the total duration of the contract (including any options as not to exceed 60 months (in red); this is a base year 912 months) with four option periods (12 months each) that equals 60 months. The government adds a possible 6-month extension period; should this clause be modified to say not to exceed 66 months?
Government Response #33: Services for a duration up to 60 months may be exercised under the authority at FAR
52.217-9. An additional 6 months may be exercised under the authority at FAR 52.217-8.
Question #34: Are there ANY databases/sources that are currently utilized to support operations now that will need to be integrated or migrated to the proposed structure? If so, we request the government identify ALL databases, type of data contained, data format/structure, and programming languages that must interface/migrate to the new proposed architecture.
Government Response #34: MCB, Quantico currently retains historical data within an MS Access database. The information is generated from an application built for MCBQ called the Hunter Tracking System (HTS).
Question #35: Do we build the Pay.gov website to support SAPDRAMS or is this built by the Pay.gov (i.e. third party?)
Government Response #35: Contractor will be responsible for making SAPDRAMS system direct online payments to the Pay.Gov service. MCBQ will be responsible for getting the base enrolled in this service but the contractor will need to make sure online payment from their system are using pay.gov.
Question #36: How many users (both administrative and customers) are there annually (historically) that would be expected to access this system in its proposed format?
Government Response #36: The Government requires at least 10 administrative users. MCB, Quantico estimates between 3000 and 5000 users.
Question #37: Are the days described in the deliverable/milestone table calendar or business days?
Government Response #37: Per FAR 2.101, “’Day” means, unless otherwise specified, a calendar day.”
Question #38: Is SAPDRAM CMS to be on a .mil or .com?
Government Response #38: It will NOT be on the .mil or .gov domain.
Question #39: Is the contractor or pay.gov staff responsible for building the requisite financial web pages on pay.gov?
Government Response #39: The contractor must ensure their system can direct payments to the Pay.gov service.
Question #40: Does MCBQ already have permission to develop on pay.gov and add data interfaces to pay.gov? Has any of that work been performed yet?
Government Response #40: MCBQ won’t be developing on pay.gov. MCBQ, will coordinate account set up and the contractor will ensure the site it develops will direct payments to pay.gov.
Question #41: Will pay.gov develop the necessary web pages for CMS on pay.gov for the pay transactions or is that the responsibility of the contractor?
Government Response #41: MCBQ won’t be developing on pay.gov. MCBQ, will coordinate account set up and the
Question #42: Does MCBQ already have permission to develop on pay.gov and to add data interfaces to pay.gov?
Government Response #42: MCBQ won’t be developing on pay.gov. MCBQ, will coordinate account set up and the
Question #43: Does MCBQ already have agreement from pay.gov IA staff to support completion of service development in 120 days considering that an ATO mod will be required of pay.gov to include the interface from
CMS to pay.gov?
Government Response #43: There is no existing agreement.
Question #44: Does CMS have pay.gov provide the customer a receipt or does CMS? If CMS provides the receipt does MCBQ already have agreement from pay.gov to send financial data to CMS?
Government Response #44:
No agreement is in place. CMS should be able to provide customers with of list of permits they purchased.
Question #45: How much history data is required to be maintained? 3 years? 5 years? 10 years? Forever?
Government Response #45: All data must be maintained for the life of the contract. All data should be easily exported into common database programs such as MS Excel or MS Access.
Question #46: Regarding account creation does the business rule for checking government IDs by CMS require the check to be done ONLY by physically presenting the ID to MCBQ personnel or can the government ID number be accepted electronically (entered via the honor system)?
Government Response #46: Accounts can be created without ID/background checks but accounts won’t be active.
MCBQ staff will physically check all ID and unlock accounts once vetting requirements have been fulfilled.
Question #47: Is the help desk intended to serve MCBQ staff, customers, or both?
Government Response #47: The Help Desk telephone support must provide vendor assistance with the system to
Government users; general customer service will be handled by MCBQ.
Question #48: Is there any current legacy data to load into CMS? If so, what form is it in, what software, and what size (volume on drives)?
Government Response #48: MCB, Quantico currently retains historical data within an MS Access database. The information is generated from an application built for MCBQ called the Hunter Tracking System (HTS).
Question #49: Does MCBQ have any feedback on the length of time to make changes to pay.gov and complete documentation required to satisfy banking regulations for IT systems (e.g., PCI DSS, Gramm-Leach-Billey ACT, C-
TPAT, and others)?
Government Response #49: Not currently.
Question #50: Activities listed in the Milestone or Deliverable chart on page 23 of 24 are listed in a serial fashion.
Does this chart say the intended CMS production date is = 45 + (60 to 120) + 125 + 127 + 140 days? If so, can the delivery dates be adjusted due to the approval schedule for FEDRAMP and other regulatory requirements as necessary?
Government Response #50: The development and delivery of the SAPDRAMS system may be performed prior to providing proof of FEDRAMP compliance; however, an active FEDRAMP certification or an ATO must be provided to the Government prior to the exercising and funding of the line items in support of monthly maintenance.
Question #51: Does MCBQ intend for the mobile application to be on iTunes and the Google store? If so, is MCBQ prepared for any delays that affect the Milestone or Deliverable chart due dates due to requirements, delays, funding demands, or any other issue with respect to adding an application to these commercial websites?
Government Response #51: Mobile application requirement has been removed from PWS
Question #52: Should the solution account for the migration of existing customers?
Government Response #52: No
Question #53: Why does Factor 2 reference "performance-based operating parameters" if this acquisition is intended to be firm-fixed price?
Government Response #53: Under performance based acquitions, the Government describes a desired end state and industry provides a proposed technical approach to achieve the desired end state along with a management plan. The management plan should describe the methodology in which the contractor intends to acquire and retain qualified personnel as well as how the contractor personnel will be utilized effectively to achieve the proposed technical approach.
Question #54: Please confirm that the Help Desk telephone support is for Tier 1 information technology support only for the SAPDRAMS system.
Government Response #54: The Help Desk telephone support must provide vendor assistance with the system to
Government users; general customer service will be handled by MCBQ.
Question #55: What time zone shall the Help Desk telephone support for the hours 0800-1500?
Government Response #55: EST
Question #56: What are the page counts for the technical and price volumes?
Government Response #56: Page count limitations have been established within the FAR 52.212-1 addendum.
Question #57: Why is there no Section 3 in the Performance Work Statement?
Government Response #57: This is a typo that has been corrected
Question #58: Will an extension be granted if the answers are not provided in a timely manner in order for bidders to incorporate any changes into the proposal response?
Government Response #58: Yes, the proposal submission suspense has been extended.
Question #59: Is there a standard file format for the maps the government intends to upload to the site?
Government Response #59: Maps the government produces will be a PDF format.
Question #60: Does the government intend for this product to be hosted on MCEITS?
Government Response #60: No, it will be hosted by contractor
Question #61: Is there a preferred map service/display the government desires for the Web Map?
Government Response #61: No preferred map service/display. Web map must perform in accordance with PWS
2.1.2.7.
Question #62: The milestone chart shows initial delivery within 125 days of award. Is this a hard deadline or are vendors able to provide alternative schedules based on understanding of the requirements and associated development timelines?
Government Response #62: Vendors are able to provide alternative schedules based on understanding of the requirements and associated development timelines within the proposed technical approach.
Question #63: Is the AWS GovCloud an acceptable hosting environment for the final product?
Government Response #63: Yes, so long as the requirements of the PWS are met.
Question #64: What OS does the government prefer this to be developed on?
Government Response #64: No preferred OS so long as the requirements of the PWS are met.
Question #65: Does the government have a preferred coding language?
Government Response #65: No preferred coding language so long as the requirements of the PWS are met.
Question #66: Does the government have an existing telephone service in use today for similar functions, and if so what is the brand in use?
Government Response #66: There is no existing telephone service in use today for similar functions.
Question #67: Are there any security concerns for the locations being shared in the mapping features?
Government Response #67: No; all information that will be shared as part of this service is already shared with the public.
Question #68: Can the government share any special IDE or APIs in use for agencies to process background investigations?
Government Response #68: MCBQ will handle the background checks locally. MCBQ staff will physically check all ID and unlock accounts once vetting requirements have been fulfilled.
Question #69: Will the government accept login/password or does the solution need to support SSO access via a
CAC?
Government Response #69: System must be login/password. Not all users have CAC cards
Question #70: Does the Combined Synopsis/Solicitation under solicitation number M0026417R0025 contain requirements similar to a current contract? If possible, please provide the current contract number. Or, is this a new requirement for the government?
Government Response #70: This is a new requirement for MCB, Quantico; no current contracts are in place or have been previously awarded for the required services.
Question #71: Can you elaborate on the below 2.1.4 FedRAMP compliance? For example, does the application have to just be inside a FedRAMP environment or does it have to be not only inside a FedRAMP environment but officially certified too? If it has to be officially certified then this process can take a significant amount of time that will exceed the project schedule you have documented. Will you allow for this certification time? If not, this opportunity would not allow any bidder without a current FedRAMP certification to bid on this solicitation. Is that the government’s intention? Please advise.
Government Response #71: The development and delivery of the SAPDRAMS system may be performed prior to providing proof of FEDRAMP compliance; however, an active FEDRAMP certification or an ATO must be provided to the Government prior to the exercising and funding of the line items in support of monthly maintenance.
TERMS OF USE
TERMS OF USE
1. When a customer registers with the CMS, he/she cannot purchase permits, check-in/out of recreation areas until program staff vet the user and approves his/her account. This can require revalidation at specified time periods; the Contractor must automatically send reminders to the customer when the customer is due for a new background check
2. Staff can put any customer on administrative hold which will prevent them from account access and/or purchasing permits.
3. Conservation law enforcement or other administrative staff can query real-time all users that are currently checked-in using either website or telephone system. Staff can retrieve check-in details and other information, such as vehicles page, where searches can be done on make, model, color, type, plate, year, state and whether the vehicle’s owner is checked-in.
4. The CMS will provide automated check-out text reminders to users who fail to check-out by a certain time. It will allow staff to send texts to those in a specific area or everyone who is currently checked-in if needed due to severe storm warning, change in Base operating code and other messages as required.
5. A mobile application will provide an emergency button feature where an email or text message can be sent to
MCBQ program staff with the current latitude and longitude of the user who pressed this button.
The following have been modified:
FAR 52.212-1 ADDENDUM
1. SUMMARY: This solicitation will result in a Firm Fixed-Price (FFP) contract for SAPDRMS web-based services. The Government intends to award a single contract for a base 12-month period of performance, four
(4) 12-month option periods, and an optional six (6) month extension IAW FAR 52.217-8 as a result of the
2. The Offeror is requested to thoroughly review the requirements of this solicitation and submit any questions in writing to Sgt Tyler Sullivan at tyler.sullivan@usmc.mil and Michael Dennie at Michael.Dennie@usmc.mil
NLT 12:00 p.m., Eastern Standard Time (EST) on Friday, 14 July 2017.
3. SUBMISSION OF QUOTE:
Quotes shall be submitted by electronic mail to Sgt Tyler Sullivan at tyler.sullivan@usmc.mil and Michael
Dennie at Michael.Dennie@usmc.mil NLT 12:00 p.m. EST on Friday, 11 August 2017.
4. FORMAT OF QUOTE:
(a)
1. Representations and certifications: The Quoter must be registered at https://www.sam.gov/index.html/#1 and must state that this has been accomplished when submitting the technical quote.
2. Each Quoter must submit its quote under two (2) separate volumes: Volume One for non-price factors
(Technial Capability and Performance Execution/Management) and Volume Two for Price. Volume One shall not exceed 40 pages and Volume Two shall not exceed 10 pages. The Government reserves the right to include all or part of the technical quote in the award.
3. Quoters shall comply with the following format and content specifications:
Single-spaced typed lines;
1 inch margins on all sides;
11 point Arial or Times New Roman font;
Headers/footers – ensure the company name and RFP number is included on each page;
Graphs and drawings must be clear/legible and may use a smaller font;
No photographs or hyperlinks are permitted; and
Content should utilize .doc, .pdf. xls, and .jpg formats to the degree possible
(b) The Quoter agrees to hold the quote firm for 90 calendar days from the date specified for receipt of quotes.
(c) Quoters must be determined to be responsible to be awarded the contract.
All quotes must include the Quoter’s Cage Code, DUNS #, and TIN
(End of provision)
PERFORMANCE WORK STATEMENT
Performance Work Statement
Information Technology Solution for
Sikes Act Permit Sales & Dispersed Recreation
Access Management Services (SAPDRAMS)
1. OBJECTIVE
mailto:tyler.sullivan@usmc.mil mailto:Michael.Dennie@usmc.mil mailto:tyler.sullivan@usmc.mil mailto:Michael.Dennie@usmc.mil https://www.sam.gov/index.html/#1
The objective of this Performance Work Statement (PWS) is to expand the capabilities and improve efficiency of the Natural Resources and Environmental Affairs Branch (NREAB) Game
Checking Station operations at Marine Corps Base, Quantico (MCBQ), Virginia, by facilitating the issuance and management of Sikes Act (16 U.S.C. 670 et seq.) permits issued to individuals for access to MCBQ for the purpose of hunting, fishing, trapping, firewood, and other authorized dispersed outdoor activities. The Sikes Act requires military installations to allow access for hunting, fishing, trapping and other compatible activities to the maximum extent practicable.
Executive Order 13443 –Facilitation of Hunting Heritage and Wildlife Conservation provides basic direction for access to public land for hunting.
1.1 Scope
Major capabilities that need to be made available for automated Sikes Act Permit Sales &
Dispersed Recreation Access Managment Services (SAPDRAMS) include: customized web based content management service (CMS); online permit sales; online check-in/out; telephone check-in/out; integration of payment acceptance service for permits; an integrated daily access pass reservation service; online help documentation and training videos; training on all services;
and ongoing support for the newly integrated capabilities.
2. TASKS
2.1 TASK 1: DEVELOPMENT OF SAPDRAMS
2.1.1 Core Features
2.1.1.1 Website Development. MCBQ administrators, to include natural resources managers, conservation law enforcement officers, range control schedulers, or other designated staff require the ability to build and maintain their own web site content. Training and assistance to the
MCBQ staff with initial site construction as well as online tutorial videos are required.
Authorized staff must be able to update notices or add weather statements, cancellations, trail closures, etc. Designated MCBQ staff requires the ability to upload directives, maps, reports, photographs, or other text/graphics concerning the recreational activities.
2.1.1.2 Content Management Service (CMS). The Contractor must build a CMS within their web-based service that allows MCBQ staff to control all variables within the SAPDRAMS. This is the online interface where MCBQ staff view and control all services to which they have subscribed. For example, web site builder, staff permissions, view and edit customer accounts, configure permits, create and control areas, manage activities and game, view reports, send notifications, view area check-ins, occupancies, etc. The CMS will allow for staff to create and schedule (date controlled) any number of activities and recreation areas so that approved account holders can easily check-in/out of MCBQ for offered activities using the contractor’s website.
Each area may have a specific quota of daily passes per activity available for check-in. These quotas may be changed by staff when necessary.
2.1.1.3 Hosting. The contractor provides all hosting, security, maintenance, and backups. This will also encompass pro-active maintenance and service, including service packs, hotfixes, and patches to the hosted services to ensure recreationist can access the SAPDRAMS with common browsers.
2.1.1.4 Customer Interface. Customers will access the Contractor’s website via internet service to create a user account. The customer shall have the capability to check-in/out of MCBQ dispersed recreation areas after NREA has completed identification (ID) and/or background checks (vetting) and has activated the user account. The customer shall have access to view training videos, submit harvest data, participate in customer opinion surveys, and view informational notices, photographs, graphics and reports posted by NREA.
2.1.1.5 Permit Creation and Sales. The CMS will allow for permit issuance and sales online through the website and in-person at the MCBQ Game Checking Station. Staff will be able to create any variation of permits, for example, seasonal permits, senior permits, annual, trip, junior, no-cost permits, etc. The CMS will list the permits and the cost. The customer will be able to select one or more permits during a session and will be able to procure them using credit/debit card when a cost is applicable. The CMS will use the free Pay.Gov to process online sale transactions. Revenue will be deposited into the applicable DoD/MCBQ accounts at Defense
Finance and Accounting Service (DFAS). There will be multiple sales categories than must remain distinct. MCBQ will have some permits sales that are deposited directly into Sikes Act fee account (fish and wildlife conservation fund), while other sales (wood cutting) get deposited into a forestry account. The CMS will maintain a register of all sales, orders & transaction reporting (exportable) for reconciliation in real time. The CMS will provide printable permits and receipts for customers. Digital copies will be available to users with mobile devices when out in the field. Customers also have access to their accounts to view old permits and registration information.
2.1.1.6 Vetting Approval. When a customer registers with the CMS, he/she cannot purchase permits, check-in/out of recreation areas until program staff vet the user and approves his/her account. This can require revalidation at specified time periods; the Contractor must automatically send reminders to the customer when the customer is due for a new background check
2.1.1.7 Background Check/Debarment. At the time of application for a customer account, persons must present acceptable government issued Identification (ID) to MCBQ staff or else have a background check. The SAPDRAMS application will include a checklist of authorized
ID for MCBQ staff to certify which form of Identification (ID) card was presented. For personnel who do not have an acceptable government issued ID, MCBQ will conduct a background check. Failure to pass a background check will place a permanent hold (debarment) status on the applicant. Major violations of lawful regulations aboard MCBQ may also result in debarment. The CMS will provide a report of any personnel in debarment status. Debarment status can be removed by MCBQ conservation law enforcement when the reasons for debarment have been adjudicated per MCBQ directive.
2.1.1.8 Apply Administrative Holds. Staff can put any customer on administrative hold which will prevent them from account access and/or purchasing permits. Administative holds will disable customers’ accounts and may be temporary or permanent, depending on severity of the issue or completion of a restrictive period. A recreationist may be prohibited from participating in MCBQ dispersed recreation for a variety of reasons, to include, but not limited to: violation of
Virginia, federal or MCBQ regulations; expiration of Virginia or MCBQ licenses/permits; failure to abide by safety standards; and failure to obtain a passing score on any required safety exams.
2.1.1.9 Accounts. Authorized staff can search and view a user’s contact information, holds, validations, user notes, active permits, reservations, accepted acknowledgements, and lifetime activity history.
2.1.1.10 Email Notification. The CMS will automatically send email account notification concerning permit expiration/renewal notices.
2.1.1.11 Administrative Roles or Groups. The lead administrator for MCBQ can assign roles to staff members to control which staff members have access to which pages in the CMS and what that group of users can do to that page (edit, read only, etc.).
2.1.1.12 Customer Account Access. Customers can log into their account to edit account information, reprint permit, attain new permits, view receipts, and see their own activity and harvest history.
2.1.1.13 Training. Training can be conducted remotely via online video conferencing tool.
2.1.1.14 Documentation and Tutorials. Each page in the CMS will have help documentation specific to the page you are on.
2.1.1.15 Safety Brief. MCBQ will provide one or more (number unlimited) safety brief(s) which contractor will embed into the website for users to watch. After the video, users take a quiz to verify that they understood the requirements. If the user passes the quiz, he/she will be granted access to purchase/issue any permits that require that safety briefing and their account will be unlocked and available for activity check-in. Users will be unable to access the safety brief(s) until they have been properly vetted.
2.1.1.16 Surveys. CMS will include an online survey builder where you can build a survey and have your customers complete the survey and view results at any given time. Results are real-time and can be viewed via the CMS or exported.
2.1.2 Check-in/out Service
2.1.2.1 Daily Access Pass Service. The contractor will build, test and integrate a service for daily access pass issuance. The contractor will supply MCBQ with demonstrations of the interface for testing and validation. The service must provide staggered reservation start times for a minimum of four user groups, e.g., from priority 1 (one) through priority 4 (four). Different user groups can be granted different levels of activity and area access. NREA must be able to designate the user group of each registered permittee and be able to designate the reservation system entry time for each user group. On the day prior to scheduled activities (early reservation period), members of user groups will be able to reserve daily passes at the time designated for their user group. On actual activity days, all users will have equal access to reservation of unissued passes. Reservations of daily access passes can be done online or through telephone check-in/out. The contractor will provide a telephone based service to allow users to check-in/out of a designated recreation areas without the need to utilize the contractor’s website.
MCBQ will be issued a toll free number that allows customers and staff members to call into its service with any touch-tone phone to check-in/out, record harvest, reserve a spot, hear area openings/closings, retrieve user information, look-up vehicles, hear who is currently checked-in/out, etc. This service is seamlessly integrated with all other services and should be able to minimally handle 12 calls simultaneously.
2.1.2.2 Call Features of Telephone System:
Customers can check-in/out, record harvest or hear notification messages
Customers or administrative staff can receive calls and/or text messages from outbound calling system as notifications or reminders. For example, an auto checkout reminder call or text message can be triggered to call or send a text message to all individuals who forgot to check-out by a certain time of day
Customers can call in to hear area open/close statuses and search areas by name, region or zone.
2.1.2.3 Call-in Reservation Service:
Customers can create, review or cancel activity or area reservations
Reservations can be created for certain days of the week and times of day
Limitations can be placed on reservations such as area occupancy, compatible user groups, and conflicting activities
If the user fails to check-in by the designated time, they will lose their reservation and it will automatically become available to others
2.1.2.4 Area and Activity Creation and Management. Staff can create as many hunting, fishing, biking trails, or other dispersed recreation areas as the MCBQ program requires. Staff can establish maximum occupancy quotas on areas by activity and disseminate current occupancy numbers real-time via public website. Staff can open/close areas and schedule activities by day, season date ranges and/or business hour ranges (morning and/or afternoon). Staff can restrict specific areas to a select activity (e.g., archery hunting only), to a specific user group, those with handicap verification, age (youth hunt), etc. If an area gets closed and users are already checked-in to that area, an automatic area closure alert/notification will be sent via email/text/outbound call to those individuals requiring that they immediately depart the area and check-out once cleared from that area.
2.1.2.5 Area Scheduler & Web Display. This feature is used to display area status
(open/closed) and occupancies to users via website. This display will display hunting, fishing, and firewood cutting areas, nature and mountain bike trails, and any other dispersed recreation areas that require check-in/out.
2.1.2.6 Web Reservation Service. Users can reserve an area or activity the day before, and can be limited to certain days of the week and times of day. Limitations can be placed on reservations, which can be based on area occupancy maximum and/or user groups (% of passes).
If the user fails to check-in by the designated time, they will lose their reservation and it will automatically become available to others.
2.1.2.7 Web Map. Display map information staff wants to share with the users. They can select their area(s) through the use of a color-coded, interactive map, which can be used to display open/close status, current/max occupancies, acreage, descriptions, dates, etc. This can be used for general public, check-in only or for administrative staff to schedule area openings or closings.
2.1.2.8 Activity Data. Authorized MCBQ personnel will have access to activity database that contains record of all customer visit transactions.
2.1.2.9 Harvest Data. Hunters, trappers, and anglers must complete custom harvest data collection forms during checkout.
2.1.2.10 Reports. All reports are exportable to MS Excel. Types of reports available in CMS include game harvest, fish creel report, activity & area use, demographics, time spent, etc...All reports can have filters applied such a date, area, customer type or other.
2.1.2.11 Acknowledgements. Acknowledgements are used to display necessary information to the user at designated places during registration and check-in/out, where the user must ‘Agree’ to the terms before he/she can continue.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .