ePS_RFP_Attach_15_Gate Form_Requirements Self-Certification_20170302.xlsx

XLSX spreadsheet 630 KB Posted

Attached to
Department of the Navy (DON) electronic Procurement System (ePS)
Solicitation number
N00039-17-R-0002
Issued by

View the file

Other files

File Type Posted
ePS_RFP_Attach_09_ePS_Work_Breakdown_Structure_WBS_20170224.xlsx XLSX spreadsheet
ePS_RFP_Attach_17_Gate Form_Past Performance_20170215.docx DOCX document
ePS_RFP_Attach_2_SRS_Attachment_7_Department_of_Navy_(DoN)_Enterprise_IT_Control_Standards.pdf PDF
ePS_RFP_N00039-17-R-0002_Amendment_0001_2017_07_20.pdf PDF
Amendment_0004_CRM_Response_20170929_Industry_Response.xlsx XLSX spreadsheet
ePS_RFP_Final_N00039-17-R-0002_07132017.pdf PDF
ePS_RFP_Attach_2_SRS_Attachment_5_ePS_COTS_CWS_Data_Validations.pdf PDF
ePS_RFP_Attach_21_Cost_Price_Worksheets_03202017.xlsx XLSX spreadsheet
N00039-17-R-0002_Amend_0004_Attachments (1).zip ZIP file
ePS_RFP_Attach_18_Gate Form_Past Performance Questionnaire_20170217.docx DOCX document
ePS_RFP_Final_N00039-17-R-0002_Amendment_0003_2017_09_21.pdf PDF
ePS_Final_N00039-17-R-0002_Amend_0004_10032017_confcopy.docx DOCX document
ePS_RFP_Attach_13_Consolidated_Government_Furnished_Information_Property_List_20170216.pdf PDF
ATT22EOG.pdf PDF
ePS_RFP_Attach_08_EntArch models for RFP.pdf PDF
ePS_Final_N00039-17-R-0002_Amend_0004_10032017.pdf PDF
ePS_N00039-17-R-0002_Comment_Response_Matrix_07132017.xlsx XLSX spreadsheet
ePS_RFP_Final_N00039-17-R-0002_Conformed_to_Amendment_0003_2017_09_21.docx DOCX document
ePS_RFP_Attach_2_SRS_Attachment_6_ePS_Grants_Reporting_Rules.pdf PDF
N00039-17-R-0002_Amend_0003_Attachments (1).zip ZIP file
ePS_RFP_Attach_05_Systems_Engineering_Plan_20170214.pdf PDF
Amendment_0003_CRM_Response_20170921_Industry_Response.xlsx XLSX spreadsheet
ePS_RFP_Attach_22_PWS_CLIN Mapping_06212017.xlsx XLSX spreadsheet
ePS_RFP_Attach_12_DD 254 Signed.pdf PDF
ePS_RFP_Final_N00039-17-R-0002_Conformed_to_Amendment_0001_2017_07_20.pdf PDF
ePS_RFP_Attach_2_SRS_v1_2_s.pdf PDF
N00039-17-R-0002 Amdt 0005.docx DOCX document
ePS_RFP_Attach_07_Test and Evaluation Master Plan (TEMP)_20170214.pdf PDF
ePS_RFP_Attach_03_Capability_Requirements_Document_20170214.pdf PDF
ePS_RFP_Attach_2_SRS_Attachment_2_Operational_Rules_Matrix.pdf PDF
ePS_RFP_Attach_10_CM Plan_20170214.pdf PDF
ePS_RFP_Attach_1_PWS_2017_07_20.pdf PDF
ePS_RFP_Attach_11_Quality_Assurance_Surveillance_Plan_signed.pdf PDF
ePS_RFP_Attach_2_SRS_Attachment_1_RTM.xlsx XLSX spreadsheet
ePS_RFP_Attach_4_ePS_Notional_Schedule_2017_07_20.pdf PDF
ePS_RFP_Attach_14_Gate Form_Small Business Utilization_20170215.docx DOCX document
ePS_RFP_Exhibit_A_B_C_Contract_Data_Requirements_List_20170309_SIGNED.pdf PDF
ePS_RFP_Questions_2017_08_27.pdf PDF
ePS_RFP_Attach_25_Legacy_System_Data_Statisitics.docx DOCX document
ePS_RFP_Attach_2_SRS_Attachment_4_ePS_COTS_CWS_Transactional_Data_Elements.pdf PDF
ePS_RFP_Attach_23_OCI_Declaration_and_Disclosure.pdf PDF
ePS_RFP_N00039-17-R-0002_Amendment_0002_2017_08_17.pdf PDF
ePS_RFP_Attach_27_Managed_Services_and_Commercial_Cloud_Hosting_and_Services_PWS_20170307.docx DOCX document
ePS_RFP_Attach_26_Technical_Direction_Letter.docx DOCX document
ePS_RFP_Attach_2_SRS_Attachment_3_ePS_COTS_CWS_Required_Data_Element.pdf PDF
ePS_RFP_Attach_01_Performance Work Statement (PWS)_20170712.pdf PDF
ePS_RFP_Attach_16_Gate Form_CWS Deployment Compliance_20170215.docx DOCX document
Show all 47

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file
Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Cover Page N00039-17-R-0002

Definitions

ATTACHMENT 15REQUIREMENTS SELF-CERTIFICATION GATE FORM
TermDefinition
Out-of-the-Box (OOTB)The released version of a COTS solution that includes those functions, capabilities, tasks forms, or other operations that are available to any authorized user upon initial hardware setup and software installation.
OOTB - ConfigurationThe configuration of a Commercial-off-the-Shelf (COTS) solution, which includes any change within the defined set of COTS product parameters where a government user with proper permissions can set with no engineering services performed by the contractor, and does not result in customization of the COTS product.

Software configuration typically:

• Enables or disables functionality that is readily available in the COTS product

• Includes the steps/tasks in the initial setup of a large system (e.g., install parameters, data-element names, functional security model, user interface (UI) modification, settings, processes) available to government users with proper permissions

• Includes the use of available menus and/or wizards to set the parameters that determine the workflow

Future Enhancement to COTS Capability that results from changes to the core code of a COTS product in order to improve existing functionality that cannot otherwise occur through configuration. Enhancements shall be included in future releases of the COTS product. Enhancements are anticipated to be system upgrades necessary to ensure continued alignment, improvement, and standardization of E2E contracting processes and maturation of infrastructure to handle the large transaction volume and data demands. This may include:

• Application version upgrades

• Automation of manual business process steps

• Automated access to additional data required for report completeness

• Major updates to meet changes in compliance requirements and infrastructure modernization to address additional users

• System scalability

• Technology refresh

• Prevailing industry standards

• Emerging technologies

Business Process Reengineering (BPR)A logical methodology for assessing process weaknesses, identifying gaps, and implementing opportunities to streamline and improve these processes to create a solid foundation for success in changes to the full spectrum of operations.
ExtensionAn extension is a software component that is installed or integrated with an existing COTS product in order to enhance its functionality. An extension provides additional functionality in the new solution without disturbing the core software code. It may include additional interfaces, automation of additional contract writing/administration processes, and new data fields.
Plug-InA plug-in is a software component that provides capability not provided by the core COTS solution, and which requires a secondary license or separately loaded application to execute the desired operation. This component will be installed or integrated with the existing COTS product(s) and should not require changes to the core code of the existing COTS product(s). It may include additional interfaces, automation of additional contract writing/administration processes, and new data fields. Once installed/integrated, the operations should seamlessly execute and be unnoticeable to the user.
Other CustomizationCustomization of a COTS solution includes software development work to change or extend the functionality of an existing COTS product, without resulting in changes to the core code of the COTS product. Customization is any software change intended to address specific DON requirements that is not configuration as defined above.

Software customization may be used to create reports, interfaces, conversion objects, extensions, forms, or other capability to satisfy requirements specific to the DON that could not otherwise be implemented by the configuration process. Customization of the COTS product requires a detailed understanding of the COTS implementation and data schemas in order to develop new or change existing functionality of the product.

Customization includes corrections/repairs to defects due to customization that do not involve modifications to core code of the COTS product applications.

ePS PRC

TOTAL NUMBER OF PRODUCT CAPABILITY REQUIREMENTS3032
TOTAL NUMBER OF NON-PRODUCT CAPABILITY REQUIREMENTS832
TOTAL NUMBER OF PRODUCT CAPABILITY REQUIREMENTS MET "OOTB" AT TIME OF PROPOSAL SUBMISSION0
TOTAL NUMBER OF PRODUCT CAPABILITY REQUIREMENTS MET "OOTB - CONFIGURATION" AT TIME OF PROPOSAL SUBMISSION0
PERCENTAGE OF PRODUCT CAPABILITY REQUIREMENTS MET OOTB AT TIME OF PROPOSAL SUBMISSION0.000%
***NOTE: A "No" in column D "Product Capability Requirement Designation" denotes a requirement that will NOT be counted against the 80% in the gate criteria as it is considered unrelated to product capability. These requirements are highlighted in yellow. However, they are still requirements that must be included in the system as a whole. Although not counted against the 80% gate criteria, the contractor shall still respond to the non-product capability requirements as identified in this worksheet.
Instructions for Comments (Column K):
If response chosen in Column G is "OOTB" - Provide the Software Version
If response chosen in Column G is "OOTB - Configuration" - Provide the Proposal Volume, Section/Attachment, Page, and Paragraph reference for the configuration description.
If response chosen in Column G is "Future Enhancement to COTS" - Provide expected date of release
If response chosen in Column G is "Business Process Reengineering" - Provide the Proposal Volume, Section/Attachment, Page, and Paragraph reference for the BPR approach description.
If response chosen in Column G is "Extension" - Provide the name and salient characteristics of the Extension
If response chosen in Column G is "Plug-in" - Provide the name and salient characteristics of the Plug-in
If response chosen in Column G is "Other Customization" - Provide the Proposal Volume, Section/Attachment, Page, and Paragraph reference for the Customization approach description.
IDREQ. NBR.SRS V1.01 REQUIREMENT DESCRIPTIONSPRODUCT CAPABILITY REQUIREMENT DESIGNATIONSELECT METHOD BY WHICH FUNCTIONALITY WILL BE PROVIDEDCOMMENTS
Business Process Controls00
0001SMG-01The system shall provide the capability to capture procurement related documents/information/data for storing from internal sources.Yes1000000
0002SMG-01.01The system shall provide the capability to capture procurement related documents/information/data for storing from external sources.Yes1000000
0003SMG-01.02The system shall provide the capability to capture procurement related documents/information/data for categorizing from internal sources.Yes1000000
0004SMG-01.03The system shall provide the capability to capture procurement related documents/information/data for categorizing from external sources.Yes1000000
0005SMG-01.04The system shall provide the capability to capture procurement related documents/information/data for cross referencing from internal sources.Yes1000000
0006SMG-01.05The system shall provide the capability to capture procurement related documents/information/data for cross referencing from external sources.Yes1000000
0007SMG-01.06The system shall provide the capability to capture procurement related documents/information/data for tracking from internal sources.Yes1000000
0008SMG-01.07The system shall provide the capability to capture procurement related documents/information/data for tracking from external sources.Yes1000000
0009SMG-01.08The system shall provide the capability to capture procurement related documents/information/data for linking from internal sources.Yes1000000
0010SMG-01.09The system shall provide the capability to capture procurement related documents/information/data for linking from external sources.Yes1000000
0011SMG-02[The system shall provide capability to enter data from processes performed off-line to maintain data integrity.Yes1000000
0012SMG-03The system shall automatically assign documents, received & generated, with unique control numbers.Yes1000000
0013SMG-04The system shall automatically record the local date & time when a user completes an action.Yes1000000
0014SMG-05The system shall automatically record the local date & time when a user updates an action.Yes1000000
0015SMG-06The system shall automatically record local date & time when documents are transmitted.Yes1000000
0016SMG-07The system shall automatically record local date & time when documents are received.Yes1000000
0017SMG-08The system shall allow the user to add/associate new acquisition action-related materials to an electronic contract file (ECF), including examples cited in FAR 4.803.Yes1000000
0018SMG-08.01The system shall allow the user to remove acquisition action-related materials from an ECF.Yes1000000
0019SMG-09The system shall associate imported files with system maintained acquisition documents.Yes1000000
0020SMG-10The system shall provide the capability to establish internal distribution and communication requirements.Yes1000000
0021SMG-11The system shall provide the capability to establish external distribution and communication requirements.Yes1000000
0022SMG-12The system shall provide capability to establish internal review & approval chains.Yes1000000
0023SMG-13The system shall provide capability to allow multiple users to concurrently view the original document/file including during editing.Yes1000000
0024SMG-14The system shall provide capability to adjust to component/site/user specific procedures or functions.Yes1000000
0025SMG-15The system shall provide the capability to establish a subset of contract data & documentation based on user functional type .Yes1000000
0026SMG-16The system shall provide capability to simultaneously initiate any system process from any starting point.Yes1000000
0027SMG-17The system shall provide capability to resume an interrupted action.Yes1000000
0028SMG-18The system shall provide capability to perform & view multiple processes/applications/documents concurrently.Yes1000000
0029SMG-19The system shall provide the capability to provide access to each document.Yes1000000
0030SMG-20The system shall provide the capability to prohibit access to each document.Yes1000000
0031SMG-21The system shall prohibit deletion of procurement action-related documents after contract award.Yes1000000
0032SMG-22The system shall notify the assigned user when an item is added to the contract file.Yes1000000
Workflow Management0000000
0033SMR-01The system shall provide the capability to reference a system-defined workflow model during workflow creation.Yes1000000
0034SMR-02The system shall provide the capability to generate a new workflow model that may be leveraged during workflow creation.Yes1000000
0035SMR-03The system shall provide the capability for a workflow model to include tasks that may perform in a sequential manner.Yes1000000
0036SMR-04The system shall provide the capability for a workflow model to include tasks that may perform in a parallel manner.Yes1000000
0037SMR-05The system shall provide the capability to include one or more tasks within each workflow model.Yes1000000
0038SMR-06The system shall provide the capability to identify tasks as mandatory.Yes1000000
0039SMR-07The system shall provide the capability to identify tasks as optional.Yes1000000
0040SMR-08The system shall provide the capability to identify tasks as informational.Yes1000000
0041SMR-09The system shall provide the capability for the system administrator to override a mandatory task.Yes1000000
0042SMR-10The system shall provide the capability for the system administrator to redirect a mandatory task.Yes1000000
0043SMR-11The system shall provide the capability to assign a priority for each task.Yes1000000
0044SMR-11.01The system shall allow the task priority to be user-defined.Yes1000000
0045SMR-11.02The system shall allow the task priority to be determined by designated criteria.Yes1000000
0046SMR-12The system shall provide the capability to establish action types for each task.Yes1000000
0047SMR-12.01The system shall allow Execution to be a task action type.Yes1000000
0048SMR-12.02The system shall allow Approval to be a task action type.Yes1000000
0049SMR-12.03The system shall allow Review to be a task action type.Yes1000000
0050SMR-12.04The system shall allow Comment to be a task action type.Yes1000000
0051SMR-13The system shall require each task to include a minimum set of data.Yes1000000
0052SMR-14The system shall provide the capability to automatically delegate a task to the assignee's alternative if the assignee is unavailable.Yes1000000
0053SMR-15The system shall provide the capability to support review tasks by external users outside ePS.Yes1000000
0054SMR-16The system shall provide the capability to support review tasks by preventing a user from marking a task as complete without opening the associated document.Yes1000000
0055SMR-17The system shall provide the capability to assign an execution task as the final step within the workflow.Yes1000000
0056SMR-18The system shall provide the capability for task completion to be triggered by the completion of the components of the task.Yes1000000
0057SMR-19The system shall provide the capability for a task to be re-worked when a subsequent approval has failed.Yes1000000
0058SMR-20The system shall provide the capability to require assignee comments for failed workflow tasks.Yes1000000
0059SMR-21The system shall provide the capability for a user designated as the "workflow manager” to manage the workflow.Yes1000000
0060SMR-22The system shall provide the capability for the Workflow Manager to delegate the role to another user.Yes1000000
0061SMR-23The system shall provide the capability for the Workflow Manager to assign each workflow task to an individual user.Yes1000000
0062SMR-24The system shall provide the capability for the Workflow Manager to assign each workflow task to a group of users.Yes1000000
0063SMR-25The system shall provide the capability to determine if sufficient permissions exist in order to complete a task prior to task assignment.Yes1000000
0064SMR-26The system shall provide the capability for the Workflow Manager to identify tasks that may not be available for delegation and restrict tasks from delegation.Yes1000000
0065SMR-27The system shall provide the capability for the Workflow Manager to create user-defined notifications for designated assignees.Yes1000000
0066SMR-28The system shall provide the capability for the Workflow Manager to identify tasks that shall also send notifications to the assignee's supervisor.Yes1000000
0067SMR-29The system shall provide the capability for the Workflow Manager to provide temporary permissions to each assignee for task completion.Yes1000000
0068SMR-29.01The system shall not allow the Workflow Manger to provide temporary permissions to assignees that exceed those of the Workflow Manager.Yes1000000
0069SMR-29.02The system shall allow the Workflow Manager to automatically revoke an assignees' temporary permissions upon task completion.Yes1000000
0070SMR-30The system shall provide the capability for the Workflow Manager to modify temporary permissions given to a user.Yes1000000
0071SMR-31The system shall provide the capability for the Workflow Manager to modify the workflow pertaining to the document or document group (i.e., folder) at any time prior to completion.Yes1000000
0072SMR-32The system shall provide the capability for a Workflow Manager to cancel an individual task at any time prior to completion.Yes1000000
0073SMR-33The system shall provide the capability for a Workflow Manager to cancel the entire workflow at any time prior to completion.Yes1000000
0074SMR-34The system shall provide the capability to create a workflow for an individual document or folder.Yes1000000
0075SMR-35The system shall provide the capability to complete specified tasks without a workflow process.Yes1000000
0076SMR-36The system shall provide the capability to generate multiple workflows for an individual document or folder.Yes1000000
0077SMR-37The system shall provide the capability to prevent multiple execution tasks for a contractual document.Yes1000000
0078SMR-38The system shall provide the capability to modify a workflow to eliminate the need for re-work.Yes1000000
0079SMR-38.01The system shall provide the capability to incorporate completed tasks when modifying a workflow to eliminate the need for re-work.Yes1000000
0080SMR-38.02The system shall provide the capability to incorporate in-progress tasks when modifying a workflow to eliminate the need for re-work.Yes1000000
0081SMR-39The system shall provide the capability to display the current status for each workflow task.Yes1000000
0082SMR-40The system shall provide the capability for a user to delegate a workflow task to an alternate.Yes1000000
0083SMR-41The system shall provide the capability to capture a "work stoppage" period for a task.Yes1000000
0084SMR-42The system shall provide the capability to capture an "on hold" period for a task in which the document is marked read-only.Yes1000000
0085SMR-43The system shall provide the capability to calculate elapsed time for work stoppages tasks.Yes1000000
0086SMR-44The system shall provide the capability to calculate elapsed time for "on hold" tasks.Yes1000000
0087SMR-45The system shall provide the capability to maintain a record of all actions pertaining to a workflow.Yes1000000
0088SMR-46The system shall provide the capability to capture all errors encountered during the workflow.Yes1000000
0089SMR-47The system shall notify the workflow originator of any errors encountered during the workflow.Yes1000000
0090SMR-48The system shall provide the capability to mark the document or document group with the designated status once a workflow has been completed.Yes1000000
0091SMR-49The system shall provide the capability for the Workflow Manager and all task assignees to view a visual representation of the entire workflow process.Yes1000000
0092SMR-50The system shall provide the capability for designated users (e.g., Managers) to view the visual representation of the workflow.Yes1000000
0093SMR-51The system shall enable supervisors to monitor all pending workflow tasks for their assigned users.Yes1000000
0094SMR-52The system shall enable supervisors to monitor all completed workflow tasks for their assigned users.Yes1000000
0095SMR-53The system shall enable a user to display the following information about the entire workflow:Yes1000000
0096SMR-53.01The system shall enable a user to display each task for an entire workflow.Yes1000000
0097SMR-53.02The system shall enable a user to display the task type for each task in an entire workflow.Yes1000000
0098SMR-53.03The system shall enable a user to display the action type for each task in an entire workflow.Yes1000000
0099SMR-53.04The system shall enable a user to display the action status for each task in an entire workflow.Yes1000000
0100SMR-53.05The system shall enable a user to display the dates for each task in an entire workflow.Yes1000000
0101SMR-53.06The system shall enable a user to display the assignee for each task in an entire workflow.Yes1000000
0102SMR-54The system shall provide the capability to capture comments for each task.Yes1000000
0103SMR-54.01The system shall provide the capability to retract comments prior to saving.Yes1000000
0104SMR-54.02The system shall provide the capability to edit comments prior to saving.Yes1000000
0105SMR-54.03The system shall provide the capability to delete comments prior to saving.Yes1000000
0106SMR-54.04The system shall only allow comments to be modified by the author of the comment.Yes1000000
0107SMR-55The system shall provide the capability to respond to existing comments made by another user.Yes1000000
0108SMR-56The system shall provide the capability for a user assigned to a task to make additional workflow comments once the user has completed the assigned task, if the workflow has not been completed.Yes1000000
0109SMR-57The system shall prohibit a user from making changes to workflow comments once the workflow has been completed.Yes1000000
0110SMR-58The system shall enable users to view their assigned tasks in one location.Yes1000000
0111SMR-59The system shall enable a user assigned a workflow to enter text into a comments field when conducting the task as part of a workflow.Yes1000000
0112SMR-60The system shall enable a user to complete defined workflow tasks electronically within the system.Yes1000000
0113SMR-61The system shall enable an authorized user to authorize reviewers to input changes to the material under review, with attached comments during a workflow.Yes1000000
0114SMR-62The system shall enable the user managing the workflow to accept the changes made when a reviewer has input changes to the material under review.Yes1000000
0115SMR-63The system shall enable the user managing the workflow to reject the changes made when a reviewer has input changes to the material under review.Yes1000000
0116SMR-64The system shall retain a change until the workflow is complete to include acceptance by user when a change has been made to the material under review.Yes1000000
0117SMR-65The system shall retain a change until the workflow is complete to include rejection by user when a change has been made to the material under review.Yes1000000
0118SMR-66The system shall retain the user’s information for audit purposes when a user completes a workflow task.Yes1000000
0119SMR-67The system shall provide the capability to digitally record and time stamp each unique signature when a document requires electronic signatures.Yes1000000
0120SMR-68The system shall update the status of the instrument, document, or ECF throughout the process.Yes1000000
0121SMR-69The system shall require the entry of a comment whenever a user rejects instruments, documents, or ECFs.Yes1000000
0122SMR-69.01The system shall require the entry of a comment whenever a user disapproves instruments, documents, or ECFs.Yes1000000
0123SMR-69.02The system shall require the entry of a comment whenever a user non-concurs with instruments, documents, or ECFs.Yes1000000
0124SMR-70The system shall maintain a history of all workflow tasks.Yes1000000
0125SMR-71The system shall enable an authorized user to display the history of workflow tasks.Yes1000000
0126SMR-72The system shall enable a user acting as a workflow originator to modify any incomplete tasks.Yes1000000
0127SMR-73The system shall incorporate any previously completed tasks when a workflow has been modified after initiation.Yes1000000
0128SMR-74The system shall enable a user acting as a workflow originator to cancel any incomplete task or workflow.Yes1000000
0129SMR-75The system shall enable a user acting as a workflow originator to reinitiate a previously cancelled workflow task.Yes1000000
0130SMR-76The system shall identify a workflow as “in progress” when any mandatory tasks have not been completed.Yes1000000
0131SMR-77The system shall identify a workflow process as “complete” when all mandatory tasks are completed.Yes1000000
0132SMR-78The system shall notify the workflow originator when the workflow has been completed.Yes1000000
0133SMR-79The system shall enable an authorized user to cancel a workflow.Yes1000000
0134SMR-80The system shall notify the workflow group of the cancellation when a workflow has been cancelled.Yes1000000
0135SMR-81The system shall identify a document as "signed", "approved", or "final" upon completion of the final approval task in a workflow.Yes1000000
0136SMR-82The system shall add or update a document attribute value upon completion of the final approval task in a workflow.Yes1000000
0137SMR-83The system shall require a user to access and open the corresponding document, instrument, or ECF prior to allowing the completion of a mandatory workflow task associated with a document, instrument, or file.Yes1000000
0138SMR-84The system shall prevent a task from being assigned to a user when that user does not have sufficient authority to perform a workflow task.Yes1000000
0139SMR-85The system shall enable a user to rework a previous workflow task when an approval task has been rejected.Yes1000000
0140SMR-86The system shall record initial task statistics in the workflow history.Yes1000000
0141SMR-87The system shall record re-worked task statistics in the workflow history.Yes1000000
0142SMR-88The system shall enable an authorized user initiating a workflow to provide workflow recipients privileges for the particular document, instrument, or ECF sent to that user as part of a workflow process.Yes1000000
0143SMR-88.01The system shall enable an authorized user initiating a workflow to provide workflow recipients read-only privileges for the particular document, instrument, or ECF sent to that user as part of a workflow process.Yes1000000
0144SMR-88.02The system shall enable an authorized user initiating a workflow to provide workflow recipients read and edit privileges for the particular document, instrument, or ECF sent to that user as part of a workflow process.Yes1000000
0145SMR-88.03The system shall enable an authorized user initiating a workflow to provide workflow recipients read, edit, and approve privileges for the particular document, instrument, or ECF sent to that user as part of a workflow process.Yes1000000
0146SMR-88.04The system shall enable an authorized user initiating a workflow to provide workflow recipients comment privileges for the particular document, instrument, or ECF sent to that user as part of a workflow process.Yes1000000
0147SMR-89The system shall enable an authorized user initiating a workflow to designate access rights to documents associated with the workflow, independent of the receiving user's individual access rights.Yes1000000
0148SMR-90The system shall enable a user acting as a workflow originator to cancel temporary access to any document/instrument associated with the workflow at any time during the workflow.Yes1000000
0149SMR-91The system shall enable a user acting as a workflow originator to revoke temporary access to any document/instrument associated with the workflow at any time during the workflow.Yes1000000
0150SMR-92The system shall provide the capability to prohibit recipients of temporary access to documents, instruments, or files from extending the access to any other user(s).Yes1000000
0151SMR-93The system shall enable an authorized user to create a table of codes describing reasons for initiating a particular workflow.Yes1000000
0152SMR-94The system shall enable an authorized user to maintain a table of codes describing reasons for initiating a particular workflow.Yes1000000
0153SMR-95The system shall enable an authorized user to delete a table of codes describing reasons for initiating a particular workflow.Yes1000000
0154SMR-96The system shall enable a user who has been designated as the owner of an action, to grant another user or user group read-only access to that instrument, document, or ECF when an instrument, document, or ECF is in a workflow.Yes1000000
0155SMR-97The system shall enable a user to create a manual workflow for an instrument, document or ECF for review by one or more users or security groups.Yes1000000
0156SMR-98The system shall enable a user to create a manual workflow for an instrument, document, or ECF for approval by one or more users or security groups.Yes1000000
0157SMR-99The system shall enable a user to create a manual workflow for an instrument, document, or ECF for review and approval by one or more users or security groups.Yes1000000
0158SMR-100The system shall enable a user to create an automated workflow for an instrument, document, or ECF for review by one or more users or security groups.Yes1000000
0159SMR-101The system shall enable a user to create automated workflows for an instrument, document, or ECF for approval by one or more users or security groups.Yes1000000
0160SMR-102The system shall enable a user to create automated workflows for an instrument, document, or ECF for review and approval by one or more users or security groups.Yes1000000
0161SMR-103The system shall enable a user to initiate multiple workflows per instrument or document.Yes1000000
0162SMR-104The system shall ensure that only one workflow includes the task to sign an instrument or document when a user initiates multiple workflows.Yes1000000
0163SMR-105The system shall enable an authorized user to create standard process models.Yes1000000
0164SMR-106The system shall enable an authorized user to create workflow business rules.Yes1000000
0165SMR-107The system shall enable an authorized user to create system workflow components.Yes1000000
0166SMR-108The system shall enable a user to reference administrator-established workflow models during workflow creation.Yes1000000
0167SMR-109The system shall enable a user to reference administrator-established business rules during workflow creation.Yes1000000
0168SMR-110The system shall enable a user to reference administrator-established components during workflow creation.Yes1000000
0169SMR-111The system shall require a workflow task to include a responsible party.Yes1000000
0170SMR-112The system shall require a workflow task to include the task type.Yes1000000
0171SMR-113The system shall require a workflow task to include the action type.Yes1000000
0172SMR-114The system shall require a workflow task to include the due date.Yes1000000
0173SMR-115The system shall require a workflow task to include the assignee.Yes1000000
0174SMR-116The system shall enable a user to establish one or more escalation rules for a given task.Yes1000000
0175SMR-117The system shall enable a user to establish one or more exception rules for a given task.Yes1000000
0176SMR-118The system shall enable the user to identify one or more events that trigger task completion.Yes1000000
0177SMR-119The system shall flag the requisite task as completed and record the completion date when all the events that trigger task completion have been recorded as occurred.Yes1000000
0178SMR-120The system shall calculate task duration when a task completion date has been recorded.Yes1000000
0179SMR-121The system shall enable a user to assign workflow tasks based upon the Procurement Action and Procurement Method combination.Yes1000000
0180SMR-122The system shall enable an authorized user to place users into a workflow group.Yes1000000
0181SMR-123The system shall enable a user to assign a workflow task to a workflow group.Yes1000000
0182SMR-124The system shall enable a user to assign a priority to each workflow task.Yes1000000
0183SMR-125The system shall enable an authorized user to create a table of workflow priority definitions.Yes1000000
0184SMR-126The system shall enable an authorized user to modify a table of workflow priority definitions.Yes1000000
0185SMR-127The system shall enable an enterprise system administrator to define a set of task types that may apply to a workflow.Yes1000000
0186SMR-128The system shall enable an authorized user to assign one or more task types to a workflow based on a set of valid tasks.Yes1000000
0187SMR-129The system shall enable an authorized user to tailor a workflow based on one or more defined actions.Yes1000000
0188SMR-130The system shall enable an authorized user to identify which user roles are required for a user to execute an approval type workflow task.Yes1000000
0189SMR-131The system shall enable a user to view the status of all workflow tasks.Yes1000000
0190SMR-132The system shall enable a user to set alerts for each workflow task.Yes1000000
0191SMR-133The system shall notify the user who initiated the workflow when a workflow task is past due.Yes1000000
0192SMR-134The system shall enable the user responsible for performing the workflow task to enter comments associated with a workflow task.Yes1000000
0193SMR-135The system shall enable the user who initiated the workflow to enter comments associated with a workflow task.Yes1000000
0194SMR-136The system shall provide the capability for the workflow originator to provide each assignee temporary access to any instruments/associated documents necessary to accomplish the assigned workflow task.Yes1000000
0195SMR-137The system shall enable an authorized user to establish workload limits for users within their associated security group.Yes1000000
0196SMR-138The system shall notify the workflow initiator when pre-established workload limits approach excess.Yes1000000
0197SMR-139The system shall enable an authorized user to designate a user as eligible or ineligible for a particular workflow task assignment.Yes1000000
0198SMR-140The system shall enable the workflow initiator to identify a task or tasks that are transferrable to an assignee's alternate.Yes1000000
0199SMR-141The system shall enable a user identified as an assignee's supervisor to reassign workflow tasks to another individual within their supervisory responsibility.Yes1000000
0200SMR-142The system shall update the workflow progress tracking when a task has been passed to an assignee's alternate.Yes1000000
0201SMR-143The system shall update the workflow progress tracking when a task has been reassigned by the assignee's supervisor.Yes1000000
0202SMR-144The system shall enable an authorized user to override a mandatory workflow task for users.Yes1000000
0203SMR-145The system shall enable the workflow originator to delegate the workflow originator functions to another user.Yes1000000
0204SMR-146The system shall exclude workflow history information when copying an instrument.Yes1000000
0205SMR-147The system shall exclude workflow history information when cloning an ECF.Yes1000000
0206SMR-148The system shall update any workflow history when updating the instrument identifier.Yes1000000
0207SMR-149The system shall update any associated user notifications when updating the instrument identifier.Yes1000000
0208SMR-150The system shall cancel the workflow when an instrument or document referenced in the workflow has been cancelled.Yes1000000
Workload Management0000000
0209SMW-01The system shall enable a user to establish a Procurement Action Record to record activities and data needed prior to receipt of a PR instrument and those expected to ultimately result in an award instrument.Yes1000000
0210SMW-02The system shall enable a Procurement Action Record (PAR) to be subsumed by another PAR to be maintained for auditability.Yes1000000
0211SMW-03The system shall establish a unique Procurement Action Record identifier other than the PR number, solicitation number, award number or similar instrument number.Yes1000000
0212SMW-04The system shall enable the user who created a Procurement Action Record to identify as the owner of that record.Yes1000000
0213SMW-05The system shall enable the user identified as the owner of a Procurement Action Record, to change the owner designation to a different user within their associated security group.Yes1000000
0214SMW-06The system shall enable an authorized user to change the owner designation to a different user within their associated security group.Yes1000000
0215SMW-07The system shall enable a user to associate an incoming PR to an established Procurement Action Record by referencing the PR number or a PR Package number on the Procurement Action Record.Yes1000000
0216SMW-08The system shall enable a user to enter and view general funding information associated with a Procurement Action Record.Yes1000000
0217SMW-09The system shall store and display descriptive data on a Procurement Action Record.Yes1000000
0218SMW-10The system shall store and display the contractor affected by the identified requirement on the Procurement Action Record.Yes1000000
0219SMW-11The system shall store and display the customer Point of Contact (POC) name and organization on a Procurement Action Record.Yes1000000
0220SMW-11.01The system shall use the Department for the customer POC information on the PARYes1000000
0221SMW-11.02The system shall use the Agency for the customer POC information on the PARYes1000000
0222SMW-11.03The system shall use the Command or Program Executive Office (PEO) for the customer POC information on the PARYes1000000
0223SMW-11.04The system shall use the Program Manager (PM) or Directorate for the customer POC information on the PARYes1000000
0224SMW-11.05The system shall use the Project or Program Name for the customer POC information on the PARYes1000000
0225SMW-11.06The system shall use the Project or Program Element Code for the customer POC information on the PARYes1000000
0226SMW-12The system shall store and display the Funding Office Department of Defense Activity Address Code (DoDAAC) and associated organization name on a Procurement Action Record.Yes1000000
0227SMW-13The system shall store and display supporting role POCs on a Procurement Action Record.Yes1000000
0228SMW-14The system shall use the Procurement Action Record data as a master file to auto-populate data throughout the procurement process.Yes1000000
0229SMW-15The system shall use the Procurement Action Record data as a master data file to access data throughout the procurement process.Yes1000000
0230SMW-16The system shall enable the owner to cancel a Procurement Action Record at any time prior to the issuance of an award instrument associated with the Procurement Action Record.Yes1000000
0231SMW-17The system shall enable an authorized user to reinstate a cancelled Procurement Action Record.Yes1000000
0232SMW-18The system shall create actual milestone dates based upon award for the associated document, instrument, or ECF.Yes1000000
0233SMW-18.01The system shall create actual milestone dates based upon signature for the associated document, instrument, or ECF.Yes1000000
0234SMW-18.02The system shall create actual milestone dates based upon approval dates for the associated document, instrument, or ECF.Yes1000000
0235SMW-19The system shall prevent the modification of the actual milestone dates.Yes1000000
0236SMW-19.01The system shall provide the capability to enter revised milestone dates.Yes1000000
0237SMW-19.02The system shall provide the capability to edit revised milestone dates.Yes1000000
0238SMW-20The system shall automatically perform an initial assessment of the completeness of the requirements package based upon pre-defined validation logic.Yes1000000
0239SMW-21The system shall determine if a pre-existing basic award instrument covers the requirements package upon receipt of a new requirements package.Yes1000000
0240SMW-21.01The system shall search within ePS for the pre-existing basic award instrument.Yes1000000
0241SMW-22The system shall determine if the requirements package contains items matching a National Stock Number (NSN) on a line item to an existing draft award instrument upon receipt of a new requirements package via an internal search of the ePS architecture.Yes1000000
0242SMW-23The system shall compare data within a requirements package to a pre-defined list of required sources of supply.Yes1000000
0243SMW-24The system shall store the results of the automated analysis of a newly received requirements package.Yes1000000
0244SMW-25The system shall enable a user to display the results of the automated analysis of a newly received requirements package.Yes1000000
0245SMW-26The system shall enable a user to print the results of the automated analysis of a newly received requirements package.Yes1000000
0246SMW-27The system shall enable a user to continue executing a procurement action for a requirements package when the automated analysis does not complete.Yes1000000
0247SMW-28The system shall enable an authorized user to establish minimally acceptable criteria that will automatically reject a newly received requirements package based upon the results of the automated analysis of that package if the criteria have not been satisfied.Yes1000000
0248SMW-29The system shall enable an authorized user to establish criteria that will automatically hold a newly received requirements package for manual approval or rejection based upon the results of the automated analysis of that package.Yes1000000
0249SMW-30The system shall enable a user to re-execute the automated requirements package analysis on an ad-hoc basis.Yes1000000
0250SMW-31The system shall enable a user to re-execute the automated requirements package analysis upon combination of multiple requirement packages.Yes1000000
0251SMW-32The system shall enable a user to associate any resulting solicitation or award instruments against an existing Procurement Action Record.Yes1000000
0252SMW-33The system shall update data on the Procurement Action Record with data from an associated PR, solicitation or award instrument upon receipt or execution of that instrument.Yes1000000
0253SMW-34The system shall update the Procurement Action Record with actual data contained in the ECF associated with that Procurement Action Record.Yes1000000
0254SMW-35The system shall display the user's current workload assignment queue on command.Yes1000000
0255SMW-36The system shall display the user's completed workload assignment queue on command.Yes1000000
0256SMW-37The system shall enable a user to tailor the workload assignment queue display.Yes1000000
0257SMW-38The system shall enable a user to formally accept an incoming requirements package.Yes1000000
0258SMW-39The system shall enable a user to formally reject an incoming requirements package.Yes1000000
0259SMW-40The system shall automatically calculate the Procurement Action Lead Time (PALT) in number of days for each procurement action.Yes1000000
0260SMW-41The system shall automatically calculate the number of PALT days for an individual milestone based on PALT start date to milestone actual date.Yes1000000
0261SMW-42The system shall update PALT calculations based on the consideration of specified PALT exclusion milestones.Yes1000000
0262SMW-43The system shall update PALT calculations based on the consideration of timeframes in the milestone plan.Yes1000000
0263SMW-44The system shall provide the capability for an authorized user to identify standard PALT times based upon each procurement action and method combination.Yes1000000
0264SMW-45The system shall provide the capability for an enterprise authorized user to establish and integrate PALT standards across the contract phasesYes1000000
0265SMW-46The system shall provide a visual display corresponding to status indicatorsYes1000000
0266SMW-47The system shall update PALT calculations based upon user specified criteria.Yes1000000
0267SMW-48The system shall update the associated milestones when it updates PALT calculations.Yes1000000
0268SMW-49The system shall enable a user to distinguish between the planning phase and the procurement phase when calculating the PALT values for procurement action and method combinations that include the issuance of a solicitation.Yes1000000
0269SMW-50The system shall provide the capability to compare PALT calculations to the average PALT for the same procurement action and method combination.Yes1000000
0270SMW-51The system shall identify procurement actions as early, on-time, or late when the forecasted PALT is compared to a pre-defined PALT standard value.Yes1000000
0271SMW-52The system shall identify procurement actions as early, on-time, or late when the actual PALT has been compared to a pre-defined PALT standard value.Yes1000000
0272SMW-53The system shall enable an authorized user to identify milestones or activities that suspend PALT calculations.Yes1000000
0273SMW-54The system shall enable a user to apply PALT suspension milestones or activities to a procurement action.Yes1000000
0274SMW-55The system shall suspend PALT calculations for a procurement action when the user applies a PALT suspension to that procurement action.Yes1000000
0275SMW-56The system shall enable an authorized user to separate a single requirements package into multiple procurement actions by line item when the applicable business rules permit.Yes1000000
0276SMW-57The system shall enable a user to update the summary data related to a requirements package when that requirements package has been separated into multiple procurement actions or procurement actions have been combined when the applicable business rules permit.Yes1000000
0277SMW-58The system shall enable a user to flag a document, instrument, or official file as being a high interest action.Yes1000000
0278SMW-59The system shall ensure that any document, instrument, and official file "flags" are compliant with Section 508 of the Rehabilitation Act.Yes1000000
0279SMW-60The system shall enable a user to filter summary views for documents, instruments, and official files that have been "flagged".Yes1000000
0280SMW-61The system shall enable a user to sort summary views for documents, instruments, and official files that have been "flagged".Yes1000000
0281SMW-62The system shall enable a user to establish notification settings based on a flag status.Yes1000000
0282SMW-63The system shall automatically notify the designated KO on a PR when the instrument has been received from an external system.Yes1000000
0283SMW-64The system shall automatically notify the KO identified on the PR as the designated recipient and associated with a security group (by email or other means), when the instrument is received from an external system.Yes1000000
0284SMW-65The system shall automatically create a Procurement Action Record for a received PR as part of the PR acceptance and assignment process when a user specifies automatic generation of Procurement Action Report.Yes1000000
0285SMW-66The system shall enable an authorized user to create a workload assignment of one or more requirements to a designated user.Yes1000000
0286SMW-67The system shall enable an authorized user to create a workload assignment of one or more Procurement Action Records to a designated user.Yes1000000
0287SMW-68The system shall enable an authorized user to create a workload assignment of one or more requirements to a designated security group.Yes1000000
0288SMW-69The system shall enable an authorized user to create a workload assignment of one or more Procurement Action Records to a designated security group.Yes1000000
0289SMW-70The system shall hold the PRs and requirements packages received from external systems by an authorized system user for manual assignment when an authorized user within a security group specifies manual workload assignment with one or more pre-defined storage locations.Yes1000000
0290SMW-71The system shall enable supervisors to view pending work assigned to users who report to them.Yes1000000

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.