W911SD-23-R-0051-0004 _Admin MRJ Questions Answers.pdf

Q&A

1. Which pages from W119SD are required when we submit this bid?

A. You need to submit the entire document. Returned can be emailed or mailed to arrive before the closing of the solicitation. The returned document needs to be signed, all required sections filled out, including your quote along with data sheet (of your specifications/capabilities for your MRJ product) to be compared with our PWS.

2. *Pages 28‐30 look to be where we indicate pricing. Can this information be submitted in another format?

A. Pricing is on page 17, for clin 0001. However, if you wish to give a breakdown of your pricing on a separate data sheet with your specifications this will be acceptable.

3. *Starting page 37 there look to be blanks that we need to complete. Would you like only these pages submitted or are we required to also include the pages that do not indicate any response?

A. You are required return the document in it’s entirety to include this Q&A page and signed.

4. I am working with a subcontractor for the Cloud Based job posted on Sam and was trying to inquire about the payout. I could have missed it but I did not see the way this contract would be paid out. I ask because I would like to submit a quote as close to accurate as possible.

A. This is a base plus two option years; the option years will depend on availability of funds. The Payment system used will be WAWF, please refer to clause “252.232-7006 WIDE AREA –

WORKFLOW PAYMENT INSTRUCTIONS”.

5. Is this solicitation part of renewal versus additional purchase?

A. This is a new purchase not part of any renewal contract.

6. When will the start date would be for this contract?

A. The POP will start on the day it is awarded and end the day before the start date the following‐ year. For example: POP 10/23/23 thru 10/22/24.

7. User Types:

Admin ‐ users that prAuthor and reviewer rights might be shared by the same user(s), but they are separated in case there's a difference between peers and editorial reviewers.

ovide administration of the site. Users, reports, etc.

Authors of manuscripts ‐ submit their work to the site for review. Can see status of their submissions and have the ability to modify their submissions with updates Reviewers ‐ review submissions, provided feedback or accept the submissions ‐ not sure what follows from here Other?

A. Other‐ "Traditional academic reviewers, that we can assign reviewers to a manuscript or transfer it to a reviewer and they can transfer it back to admin/editor."

8. Registration:

Will users register themselves?

A. "Yes" Is it invite only?

A, "No" Will admins be solely responsible for registering new users?

A. "No"

9. Workflow:

1. A user submits a new document/article/link/etc. for review.

2. The review process starts (reviewers get notified by email, through the app, etc.)

3. The reviewer provides notes/other feedback to submitter

4. The submitter makes changes/responds to reviewer with perhaps a bit of back and forth until the review is approved or the process is otherwise terminated/progressed

5. The submitter has access to previous submissions (can only see their own)

6. The reviewer can see their history of interaction with reviews and view/access a queue of new submissions awaiting review.

No Response to these questions

10. Reports:

Dashboard(s) for administrative purposes?

A. "Yes"

11. Website Pages:

7. Registration (possibly two if users can register themselves and/or admins)

8. Login

9. Forgot Password/Username

10. Navigation (account, my manuscripts, my reviews, my dashboard, logout)

11. Dashboard (landing page after login)

12. New manuscript page (~10 fields including ability to upload file(s))

13. List of manuscripts (per user, all users, with filter)

14. Edit manuscript (reviewer)

15. Reports?

A. "Yes”, lead time , metrics, number of manuscripts, basic metric to grasp what is in the system"

12. Orchid:

Only here to note as the integration requirements are to be determined.

A. Orchid is a requirement.

13. Payments:

Is there any payment processing required for the website?

A. "No"

14. Do you need a smart phone app?

A. "No"

15. Are there any technologies that are a requirement (Azure/AWS, .Net/PHP, SQL Server/MySQL, etc.)?

A. "No”