DRAFT_GCSS-MC_T-WMS_Requirements_Spec_20161205.xlsx
XLSX spreadsheet 629 KB Posted
- Attached to
- Tactical Warehouse Management System Industry Day Announcement & RFI Federal contract opportunity
- Solicitation number
- M67854-17-I-TWMSRFI
- Issued by
- United States Marine Corps
About this file
Draft Requirement Specifications
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| CRM.xlsx | XLSX spreadsheet | |
| Industry_Day_Attendees.xlsx | XLSX spreadsheet | |
| T-WMS_Industry_Day_Brief_12_Jan_17.pptx | PPTX presentation | |
| TWMS_overview.docx | DOCX document | |
| GCSS-MC_TWMS_Glossary.xlsx | XLSX spreadsheet | |
| TWMS_PWS_Version_2.docx | DOCX document | |
| GCSS-MC_LCM_Increment_1_Architecture.pptx | PPTX presentation |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Cover Page
| GCSS-MC/LCM T-WMS |
| Requirements |
DRAFT
| GLOBAL COMBAT SUPPORT SYSTEM – |
| MARINE CORPS/LOGISTICS CHAIN |
| MANAGEMENT (GCSS-MC/LCM) |
| TACTICAL-WAREHOUSE MANAGEMENT SYSTEM (T-WMS) |
Version 4.0
23-Sep-16
DISTRIBUTION STATEMENT D: Distribution authorized to DOD and DOD contractors only; (Administrative Use, 26 June 2012). Other U.S. requests shall be referred to the GCSS-MC Program Management Office, 2200 Lester Street, Quantico, VA 22134-6050
DESTRUCTION NOTICE
Record copies of FOUO documents shall be disposed of in accordance with the Federal Records Act (Title 44 Chapter 33 United States Code) and Marine Corps records management directives. Non-record FOUO documents may be destroyed
Version
| Change Description | Ver | Date | Updated By |
| Initial Draft of Functional Requirements | 0.1 | 4/4/16 | Dan Ragan, Carol Culp |
| Initial Draft of Non-Functional Requirements | 0.2 | 4/8/16 | Mike Kania, Ray Henderson |
| Reformat, Functional Requirement Acceptance Criteria, Feedback | 1.0 | 5/31/16 | Don Sturdivant, Carol Culp |
| Reformat Non-Functional Requirements, Feedback | 1.1 | 6/9/16 | Mike Kania, Ray Henderson |
| Non-Functional Requirements Feedback/Adjudication | 1.5 | 6/29/16 | Mike Kania, Ray Henderson |
| Functional Requirements Feedback/Adjudication | 2.0 | 7/1/16 | Don Sturdivant, Carol Culp |
| Reformatted - all Functional Requirement in one tab | 2.5 | 7/5/16 | Don Sturdivant, Carol Culp |
| Added Priority for Functional Requirement Admin Rqmts; made editorial changes | 3 | 7/6/16 | Tara Miner |
| Non-Functional Requirements Feedback/Adjudication | 3.1 | 7/22/16 | Mike Kania, Ray Henderson |
| Non-Functional Requirements Reformatted - all requirements in one tab | 3.5 | 7/22/16 | Mike Kania, Ray Henderson |
| Updates to format and some deletions of Non-Functional Requirements | 3.6 | 7/28/16 | Tara Miner |
| Non-Functional Requirements Feedback/Adjudication | 3.7 | 8/9/16 | Mike Kania, Ray Henderson |
| Non-Functional Requirements Feedback/Adjudication with Comments | 3.8 | 8/19/16 | Mike Kania, Ray Henderson |
| Non-Functional Requirements Feedback/Adjudication | 3.9 | 8/19/16 | Mike Kania, Ray Henderson |
| Deleted attachments and glossary | 4.0 | 8/25/16 | Tara Miner |
| Combined Functiona and Non-Functional in one Excel workbook | 4.0 | 9/23/16 | Casey Russell |
Definitions
| Requirement Column Definition | ||
| Req ID (Functional) | 3 Levels of Requirements: |
Level 1 - Capabilities (example: RCV-1 ) Level 2 - User Requirements (High-Level Requirements) (example: RCV-1.1 ) Level 3 - Functional Requirements - describes the requisite functionality for T-WMS (example: RCV-1.1.1 ) Req ID (Non-Functional) 2 Levels of Requirements:
Level 1 - Original Requirements (example: KPP-1) Level 2 - T-WMS Derived Requirements (example: KPP-1.1)
| Process Area | The capabilities are grouped into general process areas that support the execution of task for that process area. There are the general areas such as the process area administration, execution, special processing. Special Processing would have the requirements that pertain to exceptions found while performing tasks, or other diversions from the normal path. There are also specific capability areas listed - such as Cross dock for receiving. |
| Requirement Text | Definition of the Requirement |
| Acceptance | Acceptance Criteria are the conditions that a software product must satisfy to be accepted by a user, customer, or in the case of system level functionality, the consuming system. |
| Comments | Particular notes that expand the understanding of the requirement |
| Type | Business - Capability level |
User - High Level Requirement Function - Functional requirement level. This will be the requirement that will have acceptance criteria
| Category | Process Level such as Receiving, Pick, Inventory |
| Priority | High - a mission critical requirement; required for the T-WMS system, |
Medium - Supports necessary system operations; required eventually but could wait until a later release if necessary, Low - a functional or quality enhancement; would be nice to have someday if resources permit.
Priority ratings were generated and approved at the capability level by the T-WMS SMEs that attended the BPR workshop and the Requirement Workshop. Priority rating for Admin Requirements were generated based on a judgement call of basic functionality required to operate the warehouse, as well as general system knowlege.
Business and some User level requirements do not have a priority assigned since the decomposed requirements may vary in priority.
Status Final - approved by the IPT group. All Business Level and User level requirements (capabilities) were previously approved by the IPT team.
Draft - Still to be approved
| Thresholds | the defined value that must be exceeded for a certain requirement |
| Objectives | the defineD value sought for a certain requirement |
| To-Be Process Mapping | Indicates the To-Be process model area that displays the need for the requirement |
| Mapping to CDD | Shows the CDD entry that the requirement satisfies. |
The CDD document: GCSS-MC LCM Fut Incr - CDD v0.7 (MROC DM 56-2012) - 5 Sep 12. pdf The mapping list is per the Appendix of this document. Note: third level numbering was created for documentation purpose.
Also note: the CDD mapping was done in BPR Workshop 3
| Requirement Origin | Shows the origin for the requirement. See 'Origin' tab for the options. |
| Requirement Source | Shows the governance document or source that the requirement satisfies. |
Similar to "Mapping to CDD" but includes other sources found for Non-Functional Requirments
Functional Req
| Req ID | Process Area | Requirement Text | Acceptance Criteria | Type | Category | Priority | Status | To-Be Process Mapping | Mapping to GCSS-MC/LCM Future Increments CDD | Requirement Origin |
| RCV-1 | Pre-Receipt Processing | T-WMS shall process and evaluate item information received from external sources in support of warehouse receiving. | N/A | Business | Receiving | N/A | Final | N/A | N/A | N/A |
| RCV-1.2 | Pre-Receipt Processing | T-WMS shall receive and evaluate Due-In information from GCSS-MC. | N/A | User | Receiving | High | Final | Receiving: Receive Item | 2.3.1.1; 2.3.7.1 | As-Is |
| RCV-1.2.1 | Pre-Receipt Processing | T-WMS shall match received document numbers to documents identified in the Due-In. | Given that a GCSS-MC generated Due-In is available to T-WMS, and shipment document numbers are available |
When shipment document numbers are reviewed and captured in T-WMS Then T-WMS will match received document number(s) against Due-In document number(s).
| Functional | Receiving | High | Final | Receiving: Receive Item | 2.3.1.1; 2.3.7.1 | To-Be Analysis |
| RCV-1.2.2 | Pre-Receipt Processing | T-WMS shall identify missing (unreceived) items against Due-In. | Given that GCSS-MC Due-In items are available to T-WMS, and the shipment documentation identifies shipment items |
When shipment documents are reviewed, and shipment items, are entered into T-WMS
| Then the system will provide feedback to the Receiving User identifying which items are missing from the expected Due In. | Functional | Receiving | High | Final | Receiving: Receive Item | 2.3.1.1; 2.3.7.1 | To-Be Analysis |
| RCV-1.2.3 | Pre-Receipt Processing | T-WMS shall enable the Receiving User to identify missing (unreceived) item quantities against Due-In. | Given that GCSS-MC Due In item quantities are known by T-WMS |
When shipment documents are reviewed, and shipment item quantities are available, and entered into T-WMS
| Then the system will provide feedback to the Receiving User identifying which items and the quantity of items are missing from the expected Due In. | Functional | Receiving | High | Final | Receiving: Receive Item | 2.3.1.1; 2.3.7.1 | To-Be Analysis |
| RCV-1.2.4 | Pre-Receipt Processing | T-WMS shall, when document number is unavailable on receipt, match receipts to Due-In expected receipts using National Item Identification Number (NIIN) and Quantity. | Given that GCSS-MC Due-In items are identified with document number(s) and available to T-WMS |
When shipment documents do not contain document numbers, but NIIN and Quantity are available, When NIIN and Quantity are entered into T-WMS
| Then the system will use NIIN and Quantity of the received items to match receipt of shipment items provided on the Due In in order to get the Document number. | Functional | Receiving | High | Final | Receiving: Receive Item | 2.3.1.1; 2.3.7.1 | To-Be Analysis |
| RCV-1.2.5 | Pre-Receipt Processing | T-WMS shall evaluate supplementary address to determine the destination DoDAAC for receipt. | Given that GCSS-MC Due-In DoDAAC destination information is available to T-WMS |
When shipment information is reviewed and supplemental address information is entered into T-WMS
| Then the system will evaluate supplementary address information and DoDAAC to determine and provide shipment destination to the Receiving User. | Functional | Receiving | High | Final | Receiving: Receive Item | 2.3.1.1; 2.3.7.1 | To-Be Analysis | ||||
| RCV-2 | Receiving Inspection | T-WMS shall support inspection of items during receipt for condition, quantity, and documentation review. | N/A | Business | Receiving | N/A | Final | N/A | N/A | As-Is | |
| RCV-2.1 | Receiving Inspection | T-WMS shall provide a Receiving User with inspection information based on item type, issuing party, and other factors in order to support a decision of acceptance/rejection of the item. | N/A | User | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | Wish List | |
| RCV-2.1.1 | Receiving Inspection | T-WMS shall enable the Receiving Inspector to capture, view, and validate results of visual inspection during the receipt process, resulting in a condition code assignment. | Given that receivable items are available for visual inspection during the receipt process |
When items are inspected and item condition is determined and entered into T-WMS
| Then T-WMS can assign the appropriate condition code. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.1.2 | Receiving Inspection | T-WMS shall store, interpret and display results of visual inspection during the receipt process, resulting in a condition code assignment. | Given that receivable items are available for visual inspection during the receipt process |
When items are inspected and item condition is determined and entered into T-WMS
| Then T-WMS can assign the appropriate condition code. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.1.3 | Receiving Inspection | T-WMS shall enable a Receiving Administrator to indicate items for which inspection is required. | Given that receivable items are available in T-WMS |
When an Receiving Administrator user reviews receivable items and determines that those items require inspection
| Then the system will provide the Receiving Administrator user the ability to identify items where inspection is required prior to receipt. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.1.4 | Receiving Inspection | T-WMS shall allow for receipt with inspection for items that require inspection. | Given that receivable items require inspection to acknowledge receipt |
When inspection is conducted and entered in T-WMS
| Then T-WMS shall allow for item receipt with inspection. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | As-Is |
| RCV-2.1.5 | Receiving Inspection | T-WMS shall allow for receipt without inspection for items that do not require inspection. | Given that receivable items do not require inspection to acknowledge receipt |
When items are entered in T-WMS
| Then T-WMS shall allow for item receipt without inspection. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.1.6 | Receiving Inspection | T-WMS shall enable a Receiving Inspector to indicate that an item failed an inspection. | Given that receivable items require inspection to acknowledge receipt |
When the Receiving Inspector identifies that an item has failed the inspection
| Then the T-WMS should enable the Receiving Inspector to identify the received item that failed inspection. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.1.7 | Receiving Inspection | T-WMS shall enable a Receiving Inspector to associate inspection results with a receipt. | Given that receivable items require inspection to acknowledge receipt |
When inspection is conducted
| Then the T-WMS should enable the Receiving Inspector to record inspection results and associate those results with the inspected item. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.1.8 | Receiving Inspection | T-WMS shall enable a Receiving Inspector to associate inspection images to a receipt. | Given that receivable items require inspection to acknowledge receipt |
When inspection is conducted
| Then the T-WMS should enable the Receiving Inspector to capture and store image(s) of the item and associate those results with the inspected item. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.1.9 | Receiving Inspection | T-WMS shall enable a Receiving Inspector to capture inspection notes with a receipt. | Given that receivable items require inspection to acknowledge receipt |
When inspection is conducted
| Then the T-WMS should enable the Receiving Inspector to record inspection notes and associate those notes with the inspected item. | Functional | Receiving | High | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis | ||||
| RCV-2.2 | Receiving Inspection | T-WMS shall generate checklist and configuration guidance for the inspection process that can be completed either electronically or physically. | N/A | User | Receiving | Medium | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | Wish List | |
| RCV-2.2.1 | Receiving Inspection | T-WMS shall generate a receiving checklist for a specified item. | Given that T-WMS contains receiving checklists |
When a Receiving Inspector identifies an item for receipt and a checklist is associated with that item type
| Then the system will generate a receiving checklist for that item. | Functional | Receiving | Medium | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | Wish List |
| RCV-2.2.2 | Receiving Inspection | T-WMS shall generate a configuration sheet for a specified item. | Given that T-WMS contains configuration sheets |
When a Receiving Inspector identifies an item for receipt and a configuration sheet is associated with that item type
| Then the system will generate a configuration sheet for that item. | Functional | Receiving | Medium | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | Wish List |
| RCV-2.2.3 | Receiving Inspection | T-WMS shall store completed receiving checklists. | Given that a receiving checklist is generated for the Receiving Inspector for an item |
When the Receiving Inspector performs the checklist upon inspection
| Then T-WMS will record the completed checklist results. | Functional | Receiving | Medium | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.2.4 | Receiving Inspection | T-WMS shall store completed configuration sheets. | Given that a configuration sheet is generated for the Receiving Inspector for an item |
When the Receiving Inspector performs the configuration sheet upon inspection
| Then T-WMS will record the completed configuration sheet results. | Functional | Receiving | Medium | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis | ||||
| RCV-2.3 | Receiving Inspection | T-WMS shall reject receipt of an item back to the customer due to a failed inspection. | N/A | User | Receiving | Medium | Final | Receiving: Reject Item | 2.3.1.4; 2.3.7.1; 3.6 | Wish List | |
| RCV-2.3.1 | Receiving Inspection | T-WMS shall enable a Receiving Inspector to indicate that an item is rejected for failed inspection, prior to systematic completion of receipt. | Given that a Receiving Inspector has inspected a receivable item |
When the Receiving Inspector determines that the item should be rejected for failed inspection
| Then the T-WMS will allow the Receiving Inspector to indicate the item is rejected prior to completion of the receipt inspection. | Functional | Receiving | Medium | Final | Receiving: Reject Item | 2.3.1.4; 2.3.7.1; 3.6 | Wish List |
| RCV-2.3.2 | Receiving Inspection | T-WMS shall limit the rejection for Secondary Reparable Item (SecRep Code F) receiving to either Bad Serial Number or Bad National Item Identification Number (NIIN). | Given that the receivable item is a Secondary Reparable Item (SecRep Code F) |
When the item is inspected and determined to be rejected
| Then the acceptable rejection reasons are either Bad Serial Number or Bad National Item Identification Number (NIIN). | Functional | Receiving | Medium | Final | Receiving: Reject Item | 2.3.1.4; 2.3.7.1; 3.6 | Wish List |
| RCV-2.3.3 | Receiving Inspection | T-WMS shall enable a Receiving Inspector to capture, view and validate a rejection reason from the Receiving Inspector when a receivable SecRep Code F item is rejected for a failed inspection. | Given that a Receiving Inspector has inspected a SecRep Code F receivable item, |
When the Receiving Inspector determines that the SecRep Code F item should be rejected
| Then the T-WMS will require the Receiving Inspector to capture a rejection reason prior to completion of the receipt inspection. | Functional | Receiving | Medium | Final | Receiving: Reject Item | 2.3.1.4; 2.3.7.1; 3.6 | Wish List |
| RCV-2.3.4 | Receiving Inspection | T-WMS shall store, interpret and display a rejection reason captured by the Receiving User when a receivable SecRep Code F item is rejected. | Given that a Receiving User has inspected a SecRep Code F receivable item, |
When the Receiving User determines that the SecRep Code F item should be rejected
| Then the T-WMS will require the Receiving User to capture a rejection reason prior to completion of the receipt inspection. | Functional | Receiving | Medium | Final | Receiving: Reject Item | 2.3.1.4; 2.3.7.1; 3.6 | Wish List |
| RCV-2.3.5 | Receiving Inspection | T-WMS shall provide an indication to GCSS-MC of rejection of a received item due to failed inspection. | Given that a Receiving Inspector has rejected a receivable item |
When the Receiving Inspector captures the rejection of that item in T-WMS
| Then T-WMS will provide an indication to GCSS-MC that the item has been rejected due to failed inspection. | Functional | Receiving | Medium | Final | Receiving: Reject Item | 2.3.1.4; 2.3.7.1; 3.6 | Wish List | ||||
| RCV-2.4 | Receiving Inspection | T-WMS shall display and enable a user to associate an image with received item. | N/A | User | Receiving | Low | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis | |
| RCV-2.4.1 | Receiving Inspection | T-WMS shall display an image of the received item to the Receiving Inspector. | Given that T-WMS has access to images of receivable items, |
When the Receiving Inspector identifies the receivable item to T-WMS
| Then T-WMS will display an image of the received item to the Receiving Inspector. | Functional | Receiving | Low | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.4.2 | Receiving Inspection | T-WMS shall enable the Receiving Inspector to view and validate an image of a received item. | Given that T-WMS has access to images of receivable items, |
When the Receiving Inspector identifies the receivable item to T-WMS
| Then T-WMS will enable the Receiving Inspector to view the image of the received item for validation against the received item. | Functional | Receiving | Low | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis |
| RCV-2.4.3 | Receiving Inspection | T-WMS shall enable the Receiving Inspector to associate a displayed image with a received item. | Given that T-WMS has displayed an image of the received item to the Receiving Inspector, |
When the Receiving Inspector identifies the receivable item and compares the item to the provided image
| Then T-WMS will enable the Receiving Inspector to associate the image of the with the received item. | Functional | Receiving | Low | Final | Receiving: Inspect Item | 2.3.1.4; 2.3.7.1 | To-Be Analysis | ||||
| RCV-3 | Receiving Execution | T-WMS shall perform systematic receipt of items, capturing and evaluating all required item data. | N/A | Business | Receiving | N/A | Final | N/A | N/A | As-Is | |
| RCV-3.1 | Receiving Execution | T-WMS shall process supply transactions related to unexpected items received. | N/A | User | Receiving | High | Final | Receiving: Evaluate Due In | 2.3.1.2; 2.3.7.1 | As-Is | |
| RCV-3.1.1 | Receiving Execution | T-WMS shall identify receipt of items not from Due-In. | Given an item has been received that is not on the associated Due-In |
When the item completes receiving
| Then the receipt will be identified as not matching the GCSS-MC generated Due-In. | Functional | Receiving | High | Final | Receiving: Evaluate Due In | 2.3.1.2; 2.3.7.1 | As-Is |
| RCV-3.1.2 | Receiving Execution | T-WMS shall allow for receipt of items not from Due-In. | Given an item has been received that is not on the associated Due-In |
When the item completes receiving
| Then T-WMS will allow for receipt of an item that was not identified on the GCSS-MC provided Due-In. | Functional | Receiving | High | Final | Receiving: Evaluate Due In | 2.3.1.2; 2.3.7.1 | As-Is |
| RCV-3.1.3 | Receiving Execution | T-WMS shall provide an indication that an item has been received that was not on the GCSS-MC provided Due-In. | Given an item has been received that is not on the associated Due-In |
When the item completes receiving
| Then T-WMS will provide an indication to GCSS-MC that an item was received that was not identified on the GCSS-MC provided Due-In. | Functional | Receiving | High | Final | Receiving: Evaluate Due In | 2.3.1.2; 2.3.7.1 | As-Is | ||||
| RCV-3.2 | Receiving Execution | T-WMS shall enable the Receiving User to receive items through Automatic Identification Technology (AIT) and manual entry. | N/A | User | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | |
| RCV-3.2.1 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate scanned information throughout the receiving process. | |||||||||
| Given that receivable items are documented with information that can be scanned |
When that information is scanned
| Then the T-WMS will enable a Receiving User to capture, view, and validate the scanned information. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.2.2 | Receiving Execution | T-WMS shall store, interpret and display information scanned by the Receiving User throughout the receiving process. | |||||
| Given that receivable items are documented with information that can be scanned |
When that information is scanned
| Then the T-WMS will store, interpret, and display the scanned information. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.2.3 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate manually entered data to enable the receiving process. | Given that receivable items are identifiable by information that cannot be scanned |
When that information is identified
| Then the T-WMS will enable a Receiving User to capture, view, and validate the manually entered information. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | As-Is |
| RCV-3.2.4 | Receiving Execution | T-WMS shall store, interpret and display data entered manually by the Receiving user throughout the receiving process. | Given that receivable items are identifiable by information that cannot be scanned |
When that information is identified
| Then the T-WMS will store, interpret, and display the manually entered information. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | As-Is | ||||
| RCV-3.3 | Receiving Execution | T-WMS shall capture, store, interpret, and display information scanned from barcode format. | N/A | User | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | As-Is | |
| RCV-3.3.1 | Receiving Execution | T-WMS shall enable the Receiving User to capture, view and display barcoded receipt item identification information. | |||||||||
| Given that receivable items are identifiable by bar coded information that can be scanned |
When that information is scanned
| Then the T-WMS will capture, store and interpret the scanned item identification information. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.3.2 | Receiving Execution | T-WMS shall store, interpret and display barcoded receipt item identification information to the Receiving User. | |||||
| Given that receivable items are identifiable by bar coded information that can be scanned |
When that information is scanned
| Then the T-WMS will capture, store and interpret the scanned item identification information. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.3.3 | Receiving Execution | T-WMS shall enable the Receiving User to receipt for item from scanned barcode information provided on the DD Form 1348. | Given that receivable material has an associated DD Form 1348 with barcoded information |
When the DD Form 1348 barcode is scanned upon receipt
| Then the T-WMS will capture, store and interpret the data in the scanned DD 1348 barcode. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | As-Is |
| RCV-3.3.4 | Receiving Execution | T-WMS shall enable the Receiving User to receipt for item from scanned barcode information provided on the Military Shipping Label. | |||||
| Given that receivable material has an associated Military Shipping Label with bar coded information |
When the Military Shipping Label bar code is scanned upon receipt
| Then the T-WMS will capture and interpret the data in the scanned Military Shipping Label bar code. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.3.5 | Receiving Execution | T-WMS shall receipt for item from scanned Standard Document Number (SDN) provided on the DD 1348. | |||||
| Given that receivable material has an associated DD 1348 with a Standard Document Number (SDN) |
When the DD 1348 SDN is scanned upon receipt
| Then the T-WMS will capture and interpret the scanned SDN. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.3.6 | Receiving Execution | T-WMS shall receipt for item from scanned Military Standard Requisitioning and Issue Procedures (MILSTRIP) Document Number provided on the DD 1348. | |||||
| Given that receivable material has an associated MILSTRIP Document Number |
When the DD 1348 MILSTRIP Document Number is scanned upon receipt
| Then the T-WMS will capture, store and interpret the scanned MILSTRIP document number. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | ||||
| RCV-3.4 | Receiving Execution | T-WMS shall capture, store, interpret, update, and display item identifier information. | N/A | User | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | As-Is | |
| RCV-3.4.1 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate identifier information received via interrogation from active Radio Frequency Identification tag (RFID). | Given that a receivable item is identifiable by active Radio Frequency Identification (RFID) tags, and the ability to interrogate RFID exists |
When an item RFID is interrogated
| Then the T-WMS will enable a Receiving User to capture, view and validate the RFID information. | Functional | Receiving | Medium | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | Wish List |
| RCV-3.4.2 | Receiving Execution | T-WMS shall store, interpret, and display item identifier information received via interrogation from active Radio Frequency Identification tag (RFID). | Given that a receivable item is identifiable by Radio Frequency Identification (RFID) tags, and the ability to interrogate RFID exists |
When RFID is interrogated
| Then the T-WMS will store, interpret and display RFID information. | Functional | Receiving | Medium | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | Wish List |
| RCV-3.4.3 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view, and validate item identifier information received via interrogation from passive Radio Frequency Identification tag (pRFID). | Given that a receivable item is identifiable by passive Radio Frequency Identification (pRFID) tags, and the ability to interrogate pRFID exists |
When pRFID is interrogated
| Then the T-WMS will enable a Receiving User to capture, view and validate the pRFID information. | Functional | Receiving | Medium | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | Wish List |
| RCV-3.4.4 | Receiving Execution | T-WMS shall store, interpret and display item identifier information received via interrogation from passive Radio Frequency Identification tag (pRFID). | Given that a receivable item is identifiable by Passive Radio Frequency Identification (pRFID) tags, and the ability to interrogate pRFID exists |
When pRFID is interrogated
| Then the T-WMS will store, interpret and display the pRFID information. | Functional | Receiving | Medium | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | Wish List |
| RCV-3.4.5 | Receiving Execution | T-WMS shall, based on item identifier information, differentiate received items as consumables. | Given that a receivable item is identifiable as a consumable |
When the consumable item is received
| Then the T-WMS will capture, store and differentiate that item as a consumable. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.4.6 | Receiving Execution | T-WMS shall, based on item identifier information, differentiate received items as Primary End Items (PEI). | Given that a receivable item is identifiable as a Primary End Item (PEI) |
When the PEI is received
| Then the T-WMS will capture, store and differentiate that item as a PEI. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.4.7 | Receiving Execution | T-WMS shall, based on item identifier information, differentiate received items as Secondary Reparable (SecRep) items. | Given that a receivable item is identifiable as a Secondary Reparable Item (SecRep) |
When the SecRep item is received
| Then the T-WMS will capture, store and differentiate that item as a SecRep. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.4.8 | Receiving Execution | T-WMS shall enable the Receiving User to enter National Item Identification Number (NIIN) for an item during receipt. | Given that a receivable item is identifiable by an National Item Identification Number (NIIN) |
When the item is received
| Then the T-WMS will allow the Receiving User to capture and store the NIIN. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | As-Is | ||||
| RCV-3.5 | Receiving Execution | T-WMS shall capture, store interpret, and display Unit of Measure information. | N/A | User | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | |
| RCV-3.5.1 | Receiving Execution | T-WMS shall enable the Receiving User to capture, view, and validate unit of measure information during receiving. | Given that receivable items are labeled with unit of measure information |
When unit of measure information is captured by the receiving user
| Then the T-WMS will enable a Receiving User to capture, view and validate unit of measure. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.5.2 | Receiving Execution | T-WMS shall enable the Receiving User to capture, store, interpret, display and validate unit of measure information during receiving. | Given that receivable items are labeled with unit of measure information |
When unit of measure information is captured by the receiving user
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate unit of measure. | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | ||||
| RCV-3.6 | Receiving Execution | T-WMS shall determine if item weight/dimension is already stored in T-WMS and capture new information if required. | N/A | User | Receiving | Medium | Final | Receiving: Enter Wgt./ Dim. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | |
| RCV-3.6.1 | Receiving Execution | T-WMS shall enable the Receiving User to capture, view and validate weight information captured during receiving. | Given that receivable items are labeled with weight information |
When weight information is captured by the receiving user
| Then the T-WMS will enable the Receiving User to capture, view and validate weight information. | Functional | Receiving | Medium | Final | Receiving: Enter Wgt./ Dim. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.6.2 | Receiving Execution | T-WMS shall store, interpret and display weight information captured during receiving. | Given that receivable items are labeled with weight information |
When weight information is captured by the receiving user
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate weight information. | Functional | Receiving | Medium | Final | Receiving: Enter Wgt./ Dim. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.6.3 | Receiving Execution | T-WMS shall enable the Receiving User to capture, view and validate dimension information captured during receiving. | |||||
| Given that receivable items are labeled with dimension information |
When dimension information is captured by the receiving user
| Then the T-WMS will enable the Receiving User to capture, view and validate dimension information. | Functional | Receiving | Medium | Final | Receiving: Enter Wgt./ Dim. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.6.4 | Receiving Execution | T-WMS shall store, interpret and display dimension information captured during receiving. | |||||
| Given that receivable items are labeled with dimension information |
When dimension information is captured by the Receiving User
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate dimension information. | Functional | Receiving | Medium | Final | Receiving: Enter Wgt./ Dim. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.6.5 | Receiving Execution | T-WMS shall inform the Receiving User if weight information is not available from T-WMS. | Given that weight information is not stored in T-WMS for the item received |
When the item is received by the Receiving User
| Then the system will inform the Receiving User that weight information is not available from T-WMS and prompt the Receiving User to capture weight information. | Functional | Receiving | Medium | Final | Receiving: Enter Wgt./ Dim. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.6.6 | Receiving Execution | T-WMS shall inform the Receiving User if dimension information is not available from T-WMS. | |||||
| Given that dimension information is not stored in T-WMS for the item received |
When the item is received by the Receiving User
| Then the system will inform the Receiving User that dimension information is not available from T-WMS and prompt the Receiving User to capture dimension information for the received item. | Functional | Receiving | Medium | Final | Receiving: Enter Wgt./ Dim. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.6.7 | Receiving Execution | T-WMS shall capture, store, interpret and display weight and dimension information from the Cubiscan, when Cubiscan is present. | |||||
| Given that a Cubiscan system is available and operational |
When the received item is placed on the Cubiscan
| Then the T-WMS will capture, store, interpret and display Cubiscan weight and dimension information for the received item | Functional | Receiving | Medium | Final | Receiving: Enter Wgt./ Dim. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | ||||
| RCV-3.7 | Receiving Execution | T-WMS shall capture, store, interpret, and display for validation item quantity received based on both barcode data and manual entry. | N/A | User | Receiving | High | Final | Receiving: Verify Quantity Info | 2.3.1.6; 2.3.7.1 | As-Is | |
| RCV-3.7.1 | Receiving Execution | T-WMS shall enable the Receiving User to capture, view and validate item quantity during receiving. | Given that receivable items are labeled with quantity information |
When quantity information is captured by the receiving user
| Then the T-WMS enable the Receiving User to capture, view and validate item quantity. | Functional | Receiving | High | Final | Receiving: Verify Quantity Info | 2.3.1.6; 2.3.7.1 | As-Is |
| RCV-3.7.2 | Receiving Execution | T-WMS shall store, interpret, and display item quantity during receiving. | Given that receivable items are labeled with quantity information |
When quantity information is captured by the receiving user
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate quantity. | Functional | Receiving | High | Final | Receiving: Verify Quantity Info | 2.3.1.6; 2.3.7.1 | As-Is |
| RCV-3.7.3 | Receiving Execution | T-WMS shall enable a Receiving User to validate manifest quantity based on captured, stored, and displayed quantity information during receiving. | |||||
| Given that receivable items are identified on a manifest with quantity information |
When manifest quantity information is captured by the receiving user
| Then the T-WMS enable a Receiving User to validate manifest quantity based on captured, stored, and displayed quantity information during receiving. | Functional | Receiving | High | Final | Receiving: Verify Quantity Info | 2.3.1.6; 2.3.7.1 | As-Is | ||||
| RCV-3.8 | Receiving Execution | T-WMS shall capture, store, interpret, and display for validation shelf life information including shelf life code, manufacture date and expiration date associated to an item. | N/A | User | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | As-Is | |
| RCV-3.8.1 | Receiving Execution | T-WMS shall require entry of either manufacture date and expiration date for any item based on either shelf life code or NIIN. | Given that T-WMS has identified an expiring item based on either shelf life code or NIIN |
When that expiring item is received
| Then T-WMS shall require the Receiving User to captureitem manufacture date and expiration date for that item. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.8.2 | Receiving Execution | T-WMS shall display shelf life information captured during receiving including item shelf life code, item manufacture date and item expiration date. | Given that a received item is labeled with shelf-life information (inclusive of shelf life code, manufacture data, expiration data) |
When shelf life information is captured during receiving
| Then T-WMS will display captured shelf life information. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | As-Is |
| RCV-3.8.3 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate date of manufacture. | Given that receivable items are identified with quantity date of manufacture |
When date of manufacture information is captured by the receiving user
| Then the T-WMS will enable a Receiving User to capture, view and validate date of manufacture. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.8.4 | Receiving Execution | T-WMS shall store, interpret and display date of manufacture. | Given that receivable items are identified with quantity date of manufacture |
When date of manufacture information is captured by the receiving user
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate date of manufacture. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.8.5 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate item expiration date. | Given that receivable items are identified with expiration date |
When expiration date is captured by the receiving user
| Then the T-WMS will enable a Receiving User to capture, view and validate item expiration date. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.8.6 | Receiving Execution | T-WMS shall store, interpret and display expiration date. | Given that receivable items are identified with expiration date |
When expiration date is captured by the receiving user
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate expiration date. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.8.7 | Receiving Execution | T-WMS shall calculate expiration date from manufacture date if expiration date is not provided. | Given that a received item is labeled with shelf-life information inclusive of manufacture date |
When expiration date is not present
| Then T-WMS will calculate expiration date based on the manufacture date. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | ||||
| RCV-3.9 | Receiving Execution | T-WMS shall capture, store, interpret, and display for validation warranty information including manufacturer and warranty expiration date associated to an item. | N/A | User | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | Problem Analysis Resolution | |
| RCV-3.9.1 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate manufacturer information during receiving. | Given that receivable items are labeled with manufacturer information, |
When manufacturer information is identified
| Then the T-WMS will enable the Receiving User to capture, view and validate manufacturer information. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.9.2 | Receiving Execution | T-WMS shall store, interpret and display manufacturer information during receiving. | Given that receivable items are labeled with manufacturer information, |
When manufacturer information is identified
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate manufacturer information. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.9.3 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate warranty expiration information during receiving. | Given that receivable items are labeled with warranty information |
When warranty information is identified
| Then the T-WMS will enable the Receiving User to capture, view and validate warranty information. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | Problem Analysis Resolution |
| RCV-3.9.4 | Receiving Execution | T-WMS shall store, interpret and display warranty expiration information during receiving. | Given that receivable items are labeled with warranty information |
When warranty information is identified
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate warranty expiration information. | Functional | Receiving | High | Final | Receiving: Enter Supp. Info | 2.3.1.6; 2.3.7.1 | Problem Analysis Resolution | ||||
| RCV-3.10 | Receiving Execution | T-WMS shall capture, store, interpret, and display for validation project code information. | N/A | User | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | |
| RCV-3.10.1 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate project code(s) during receiving. | Given that receivable items are labeled with project information |
When project information is identified
| Then the T-WMS will enable the Receiving User to capture, view and validate project code(s). | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.10.2 | Receiving Execution | T-WMS shall store, interpret and display project code(s) during receiving. | Given that receivable items are labeled with project information |
When project information is identified
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate project code(s). | Functional | Receiving | High | Final | Receiving: Capture Identifier Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | ||||
| RCV-3.11 | Receiving Execution | T-WMS shall capture, store, interpret, and display for validation serial number associated to an item. | N/A | User | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | |
| RCV-3.11.1 | Receiving Execution | T-WMS shall inform the Receiving User when a receivable item is serial controlled. | Given that T-WMS has identified a receivable item as serial controlled |
When that item is received
| Then T-WMS shall inform the Receiving User that the item is serial controlled. | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.11.2 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate serial number(s) during receiving. | Given that receivable items are labeled with serial number(s) |
When serial number(s) are identified
| Then the T-WMS will enable the Receiving User to capture, view and validate serial number(s). | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.11.3 | Receiving Execution | T-WMS shall store, interpret and display serial number(s) during receiving. | Given that receivable items are labeled with serial number(s) |
When serial number(s) are identified
| Then the T-WMS store, interpret, display and enable the Receiving User to validate serial number(s). | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.11.4 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate a range of serial numbers during receiving. | Given that receivable items are labeled with a range of multiple serial number(s) |
When the range of serial number(s) are identified
| Then the T-WMS will enable the Receiving User to capture, view and validate a range of serial number(s). | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.11.5 | Receiving Execution | T-WMS shall store, interpret and display a range of serial numbers during receiving. | Given that receivable items are labeled with a range of multiple serial number(s) |
When the range of serial number(s) are identified
| Then the T-WMS store, interpret, display and enable the Receiving User to validate a range of serial number(s). | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.11.6 | Receiving Execution | T-WMS shall compare the expected count of serial numbers received against the actual count of items with serial numbers received. | Given that a range of multiple serial numbers have been received |
When the Receiving User captures the actual count of serialized numbers received
| Then T-WMS will compare the actual count of serial numbers within the range against the expected count of serial numbers captured by the Receiving User. | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | ||||
| RCV-3.12 | Receiving Execution | T-WMS shall capture, store, interpret, and display for validation lot number and/or batch number associated to an item. | N/A | User | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | |
| RCV-3.12.1 | Receiving Execution | T-WMS shall enable a Receiving User to capture, view and validate lot number during receiving. | Given that receivable items are labeled with lot information |
When lot information is identified
| Then the T-WMS will enable the Receiving User to capture, view and validate lot information. | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.12.2 | Receiving Execution | T-WMS shall store, interpret and display lot number during receiving. | Given that receivable items are labeled with lot information |
When lot information is identified
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate lot information. | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.12.3 | Receiving Execution | T-WMS shall enable the Receiving User to capture, view and validate batch number during receiving. | Given that receivable items are labeled with batch information |
When batch information is identified
| Then the T-WMS will enable the Receiving User to capture, view and validate batch information. | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.12.4 | Receiving Execution | T-WMS shall store, interpret and display batch number during receiving. | Given that receivable items are labeled with batch information |
When batch information is identified
| Then the T-WMS will store, interpret, display and enable the Receiving User to validate batch information. | Functional | Receiving | High | Final | Receiving: Verify Serial Info | 2.3.1.6; 2.3.7.1 | To-Be Analysis | ||||
| RCV-3.13 | Receiving Execution | T-WMS shall evaluate receipt process workflow to determine the appropriate receiving status to indicate to GCSS-MC. | N/A | User | Receiving | High | Final | Receiving: Evaluate Due In | 2.3.1.6; 2.3.7.1 | As-Is | |
| RCV-3.13.1 | Receiving Execution | T-WMS shall provide an indication to GCSS-MC of receipt of an item Due-In is completed. | Given that an item has been received |
When T-WMS reconciles the received item against the corresponding GCSS-MC Due In and identifies a match
| Then T-WMS will inform GCSS-MC that the Due In for that item is complete. | Functional | Receiving | High | Final | Receiving: Evaluate Due In | 2.3.1.6; 2.3.7.1 | As-Is |
| RCV-3.13.2 | Receiving Execution | T-WMS shall provide an indication to GCSS-MC of receipt of an item not from Due-In is completed. | Given that an item has been received |
When T-WMS reconciles the received item against the corresponding GCSS-MC Due In and does not identify a match
| Then T-WMS will inform GCSS-MC that the receipt of that item is complete and not from Due In. | Functional | Receiving | High | Final | Receiving: Evaluate Due In | 2.3.1.6; 2.3.7.1 | To-Be Analysis |
| RCV-3.13.3 | Receiving Execution | T-WMS shall provide an indication to GCSS-MC receipt of an item with a discrepancy and discrepancy type. | Given that an item has been received by T-WMS |
When the received item has been identified with discrepancy type and information (e.g., overage, underage, damaged)
| Then T-WMS will provide GCSS-MC with item discrepancy information. | Functional | Receiving | High | Final | Receiving: Evaluate Due In | 2.3.1.6; 2.3.7.1 | To-Be Analysis | |
| RCV-3.14 | Receiving Execution | T-WMS shall associate a Receiving User with completion of receipt execution. |
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 .