RFP_Attachment_3_-_Requirements_List.xlsx
XLSX spreadsheet 345 KB Posted
- Attached to
- Request for Proposal (RFP) Item Master Logistics Capability Initiative (IMLCI) Federal contract opportunity
- Solicitation number
- FA8770-20-R-0004
About this file
This is a Request for Proposal for the Item Master Logistics Capability Initiative. The USAF intends to award an indefinite-delivery, indefinite-quantity contract for the Item Master Program including Delivery Order 01. The Item Master Logistics Capability Initiative will provide the Air Force enterprise with the capability to generate and manage comprehensive, accurate, and reliable item-specific data. It will provide users with the breadth and depth of accurate item data necessary to support dependent processes, initiatives, programs and transformational concepts. The Item Master provides capabilities for item standardization, item configuration management, and serving as a single authoritative source.
View the file
Other files for this federal contract opportunity
Show all 35
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
IMLCI Read Me - April 2019
| There are 5 tabs including the Read Me Tab, summarized below: |
| IM ITFRs: The Item Master (IM) IT Functional Requirements (ITFR) outline the expected behavior of the material solution. When reviewed in terms of the Business Process Re-engineering (BPR) models; these statements describe the kinds of features, functions, actions, and services needed for delivery of Item Master capabilities. They also serve as a basis for test planning and execution. |
IAW DoDI 5000.75: appendix 4D Appendix 4D: Business System Solutions and Documentation 4D.1. Functional Requirements (ITFRs).
a. Functional requirements will be linked to inputs and outputs that define how the functional requirements support the business processes.
b. Functional requirements will be linked to technical (Technical Requirements) and lifecycle support requirements (LSRs) that constrain how the functional requirements support the business process.
| IM Technical Requirements: The IM Technical Requirements identify the constraints, boundaries, and minimally acceptable criteria to which the M-Solution must comply. These statement address topology, infrastructure, distributed computing and compliance. | |
| Lifecycle Support Requirements (LSRs): The IM LSRs capture the underlying technology, business drivers and key concepts the M-Solution must meet, outlining the minimally acceptable core competencies and services as defined by the Functional Community. | |
| Laws, Regulations and Policies (LRPs): The IM pertinent LRPs that will constrain solutions (LRP Links provided) | |
| Information Technology Functional Requirements (ITFR) Name & Definition as referenced at Tab: IM ITFRs | |
| Column Names | Column Description |
| A: ITFR ID # | Traces each ITFR line item back to the specific BPR Models 1-5 & Activity Blocks (The Activity Blocks describe the behavior of each step in the BPR Models from a functional perspective, explaining the business requirements in terms of the processes they serve. |
| B: ITFR Name | See ITFR Names at Column B of IM ITFRs Tab |
| C: ITFR Definition | See ITFR Definitions at Column C of IM ITFRs Tab |
| Information Technology Technical Requirement (ITTR) as referenced at Tab: IM ITTRs | |
| Column Names | Column Description |
| A: ITTR ID # | IMLCI Team assigned |
| B: ITTR Definition | See ITTR Definitions at Column B of IM ITTRs Tab |
| ITTR Category Name | Description |
| Technical - System Architecture | Requirements on the underlying architecture of the solution. |
| Technical - Usability | Requirements on the usability/ease-of-use of the solution. |
| Technical - Identity and Access Management | Requirements which focus on Identify and Access Management (IAM) requirements, a set of information protection controls and services to make operations more efficient. |
| Technical - Integration | Requirements that address technologies and methods to connect Software as a Service (SaaS) solution(s) to other SaaS, Cloud-hosted and on-premises solutions such as through an integrated Platform as a Service (iPaaS) to enable business processes. |
| Technical - Configuration | Requirements associated with managing the solution's configuration, versions, environments and releases. |
| Technical - Technology Management | Requirements to manage the various dimensions of the solution such as execution (users, integrations, entitlements, level of control, data) and operations (billing, contact information, thresholds, alerts, escalations). |
| Technical - Security | Requirements for keeping data and services secure in the SaaS solution(s). |
| Technical - Storage | Requirements for SaaS solution(s) storage and data retention. |
| Technical - Network | Requirements related to connecting/networking the SaaS solution(s) to users and on-premises and other cloud solutions such as through an iPaaS. |
| Solution - Security | Requirements associated with how the Interested Party (not the solution offering) provides security (e.g., physical security at data centers). |
| Solution - Storage | Requirements around how the Interested Party manages the solution from a storage perspective (e.g., how the data is removed from levels of storage once it has been deleted). |
| Solution - Network | Requirements associated with Interested Parties' ability to provide connection options (e.g., ability to offer direct connect, Multiprotocol Label Switching (MPLS), dark fiber). |
| Lifecycle Support Requirements (LSR) Name & Statement as referenced at Tab: IM LSRs | |
| Column Names | Column Description |
| A: LSR ID # | IMLCI Team assigned |
| B: LSR Name | See LSR Names below; each LSR is cross referenced to one or more LSR Names. |
| C: LSR Definition | See LSR Definitions at the LSR tab |
| D: LSR Category Name | See LSR Category Names and LSR Category Definitions below |
| LSR Name | LSR Name Definition |
| Data Management Flexibility | Data Management Flexibility measures the solution's ability to integrate into a complex environment like the USAF, while extending its architecture and data model to support emergent needs and new business requirements. |
| Usability | Usability assesses the degree to which the solution can be deployed without large investments (in time or money) in end user product training. Usability includes Early User Experiences which identify desirable, forward leaning, end user interface behaviors and navigational concepts that incorporate the use of features such as drop/drag, chat, type ahead, picklists, and visualization tools to sustain the product. |
| Re-Configurability/Adaptability (Post Implementation) | Re-Configurability/Adaptability Post implementation assesses the degree to which new capability can be deployed using the features and functions of the technology stack; the assessment focuses on ease of use and simplicity in the management and configuration of data transfers, workflows, business rules, and user interface revisions (i.e., the 4 configuration options), product extensions and enhancements. |
| Scalability | Scalability evaluates the ability to add more business volume (more data, more users) into the processes as specified in the requirements model. |
| Maintainability | Maintainability assesses the degree to which the solution, its components, patches and planned product upgrades, which are maintained by the original product offeror, remain compatible with the product applications, extensions and configurations created and managed by the USAF. |
| LSR CATEGORY CONSTRUCTS: | |
| LSR Category Name | LSR Category Definition |
| Data Exchange Framework | Describes the characteristics of system-to-system information exchanges |
| Solution Architecture | Describes the technical characteristics expected of the M-solution in terms of support to the functional user |
| User Interface | Identifies required end user interface features and functions, including behavioral characteristics controlled by end users |
| Access Control and Security | Identifies the rules and configuration requirements of role-based system access, attribute management, and segregation of duty |
| Business Rule Engine | Describes the end user controlled features and functions governing data edits and data exchanges |
| Data Management | Describes the parameters required to support data integrity by representing the process models in terms of enterprise logistics data relationships |
| Laws, Regulations and Policies (LRPs) | |
| Pertinent laws, regulations and policies that will constrain solutions (LRP Links provided) as referenced at Tabs LRPs |
&F
&A &P of &N
IM ITFRs
| ITFR ID # | ITFR Name | ITFR Definition |
| IM.ITFR.1.01.34 | Provide system to system data exchange | Solution shall provide the capability for system to system exchange of information with trading partners |
| IM.ITFR.1.02.21 | Provide customizable desktop | Solution shall have the capability to manage individual workload by configuring desktop features |
| IM.ITFR.1.01.32 | Provide business rules functionality | Solution shall provide the capability to assign business rules |
| IM.ITFR.1.01.33 | Update standard workflows | Solution shall provide the capability to change configurations that govern standard workflows |
| IM.ITFR.1.01.01 | Provide standardized Item Master template user interface | Solution shall have the capability for a standardized template user interface |
| IM.ITFR.1.01.02 | Provide systemically generated Assistance Request templates | Solution shall provide the capability to systematically present AR templates to end users |
| IM.ITFR.1.01.03 | Update IM AR with common access card profile data | Solution shall have the capability to update AR templates with requestor's user profile details |
| IM.ITFR.1.01.04 | Search AF Item Master Catalog on Items | Solution shall provide the capability to search the AF Item Master Catalog for Items |
| IM.ITFR.1.01.05 | Search Federal Catalog Item Master on Stocklisted Items | Solution shall provide the capability to search the Federal Catalog for Stocklisted Items |
| IM.ITFR.1.01.06 | Search AF Item Master Catalog on Item attributes | Solution shall provide the capability to search the AF Item Master Catalog for attributes |
| IM.ITFR.1.01.07 | Search Federal Catalog on Item Master Stocklisted Item attributes | Solution shall provide the capability to search the Federal Catalog for attributes |
| IM.ITFR.1.01.08 | Update Assistance Request on Item Master search results | Solution shall provide the capability to copy the search results into an AR template |
| IM.ITFR.1.01.09 | Update AR organization on end item search results | Solution shall provide the capability to copy the end item assigned to an organization into an AR template |
| IM.ITFR.1.01.10 | Save draft Assistance Request | Solution shall provide the capability for requestor to save AR in draft form |
| IM.ITFR.1.01.11 | Provide Assistance Request collaboration workspace | Solution shall provide the requestor with a collaborative workspace to manage ARs |
| IM.ITFR.G.1.01.12 | Provide attachment capability | Solution shall have the capability to add attachments |
| IM.ITFR.1.01.13 | Provide standard AR import templates | Solution shall have the capability for requestor to import information from attachments directly into the AR by mapping source content to target fields in the AR |
| IM.ITFR.1.01.14 | Search current Assistance Requests | Solution shall have the capability for requestor to search current ARs |
| IM.ITFR.1.01.15 | Assign Federal Supply Class to IM AR Line Item | Solution shall have the capability to assign a Federal Supply Class for each part item request prior to submission of the IM AR |
| IM.ITFR.1.01.16 | Obtain Federal Supply Class for new part item | Solution shall have the capability to obtain the Federal Supply Class from the Federal Catalog for a part item creation request |
| IM.ITFR.1.01.17 | Obtain Federal Supply Class of existing part item | Solution shall have the capability to obtain the Federal Supply Class from the AF IM Catalog for a part item change request |
| IM.ITFR.1.01.18 | Route initial Assistance Request by attributes | Solution shall have the capability to route based on the AR attributes |
| IM.ITFR.1.01.19 | Update Assistance Request status to draft | Solution shall have the capability to set the AR status to draft when the user saves but does not submit the AR information |
| IM.ITFR.1.01.20 | Update Assistance Request status to submitted | Solution shall have the capability to set the AR status to submitted when the user submits the AR information |
| IM.ITFR.1.01.21 | Create Item Types | Solution shall have the capability to create multiple Item Types |
| IM.ITFR.1.01.22 | Create Item Type attributes | Solution shall have the capability to create attributes for each Item Type |
| IM.ITFR.1.01.23 | Provide product comparison | Solution shall have the capability to provide side by side comparison of product data |
| IM.ITFR.1.01.24 | Save individual searches | Solution shall have the capability to save individual searches |
| IM.ITFR.1.01.25 | Search for Exact Item | Solution shall have the capability to search for Exact Item match using part number/CAGE Code |
| IM.ITFR.1.01.26 | Assign unique Assistance Request identification | Solution shall have the capability to systematically identify each AR created |
| IM.ITFR.1.01.27 | Search AF Item Master Catalog | Solution shall provide the capability to search the AF Item Master Catalog for Items results |
| IM.ITFR.1.01.28 | Create new Assistance Request templates | Solution shall have the capability to create new AR Templates based on Item Type |
| IM.ITFR.1.01.29 | Create new Item templates | Solution shall have the capability to create new Item templates |
| IM.ITFR.1.01.30 | Create draft Items | Solution shall have the capability to create draft Items |
| IM.ITFR.1.01.31 | Create historical records | Solutions shall have the capability to create historical records |
| IM.ITFR.1.01.35 | Create Bills of Material | Solution shall have the capability to create multiple bills of material based on product structure |
| IM.ITFR.1.01.36 | Update product structure relationships | Solution shall have the capability to update product structures with engineering approved primary and alternate Items |
| IM.ITFR.1.01.37 | Manage Item views | Solutions shall have the capability to provide different views based on user role |
| IM.ITFR.1.01.38 | Provide access control | Solution shall provide the capability for role based access control |
| IM.ITFR.1.01.39 | Associate Item types | Solution shall have the capability to associate Items to one another at any level of product structure indenture |
| IM.ITFR.1.01.40 | Associate contract | Solution shall have the capability to associate lot/serial number information to contract |
| IM.ITFR.1.01.41 | Identify Item aliases | Solution shall have the capability to identify Items by aliases |
| IM.ITFR.1.01.42 | Search AF Item Master Catalog using batch upload | Solution shall provide the capability to search the AF Item Master Catalog using an uploaded batch capability |
| IM.ITFR.1.01.43 | Route draft Item for collaboration | Solution shall have the capability to route AF Item Record drafts for collaboration |
| IM.ITFR.1.01.44 | Search historical data | Solution shall provide the capability to search historical data |
| IM.ITFR.1.01.45 | Provide hyper link capability | Solution shall provide the capability to populate data attributes with hyperlinks |
| IM.ITFR.1.01.46 | Update AR organization on associated product structure search results | Solution shall provide the capability to copy the associated product structures assigned to an Organization into an AR template |
| IM.ITFR.1.01.47 | Search historical Assistance Requests | Solution shall have the capability for requestor to search historical ARs |
| IM.ITFR.1.01.48 | Update Item Types | Solution shall have the capability to update multiple Item Types |
| IM.ITFR.1.01.49 | Update Item Type attributes | Solution shall have the capability to manage attributes for each Item Type |
| IM.ITFR.1.01.50 | Save enterprise searches | Solution shall have the capability to save enterprise searches |
| IM.ITFR.1.01.51 | Modify business rules | Solution shall provide the capability to customize business rules |
| IM.ITFR.1.01.52 | Associate warranty information | Solution shall have the capability to associate lot/serial number information to warranty information |
| IM.ITFR.1.01.53 | Identify routing requirements | Solution shall have the capability to identify AR routing requirements |
| IM.ITFR.1.01.54 | Update IM AR Line Item status to accepted | Solution shall have the capability to set the IM AR Line Item status to accepted when the request passes validation |
| IM.ITFR.1.01.55 | Update IM AR Line Item status to rejected | Solution shall have the capability to set the IM AR Line Item status to rejected when the request fails validation |
| IM.ITFR.1.01.56 | Identify Federal Cataloging actions | Solution shall have the capability to identify Federal Cataloging actions based on IM AR attributes |
| IM.ITFR.G.1.01.01 | Create notification for product structure updates | Solution shall notify designated users of product structure updates |
| IM.ITFR.G.1.01.02 | Create notification for Federal Catalog updates | Solution shall notify designated users of Federal Catalog updates |
| IM.ITFR.1.02.01 | Populate IM AR Line Item with estimated response time | Solution shall have the capability to automatically populate an estimated response time for an IM AR Line Item based on AF business rules |
| IM.ITFR.1.02.02 | Update IM AR Line Item with revised response time | Solution shall have the capability for the Item Lifecycle Management Team supervisors to manually override estimated response times |
| IM.ITFR.1.02.05 | Populate IM AR Line Item with estimated response date | Solution shall have the capability to populate the estimated response date based on response time AF business rules |
| IM.ITFR.1.02.06 | Evaluate Assistance Request | Solution shall have the capability to evaluate the Assistance Request Type to identify routing requirements |
| IM.ITFR.1.02.07 | Classify Assistance Request to Performing Activity | Solution shall have the capability to identify the Assistance Request to the performing activity when the request type is other than an access or provisioning request |
| IM.ITFR.1.02.08 | Classify Assistance Request as Access Only | Solution shall have the capability to identify an access only AR based on the user profile of the Originator |
| IM.ITFR.1.02.09 | Assign IM AR Line Item | Solution shall have the capability to assign an Item Lifecycle Management Team to each IM AR Line Item using the Federal Supply Class value |
| IM.ITFR.1.02.10 | Route Assistance Request | Solution shall have the capability to route AR |
| IM.ITFR.G.1.02.03 | Create notification of team assignment | Solution shall notify designated users of team assignment |
| IM.ITFR.1.02.11 | Route Assistance Request to ILM Team by attributes | Solution shall have the capability to route AR based by attributes |
| IM.ITFR.1.02.12 | Route Assistance Request for Item access | Solution shall have the capability to route the AR to the CA when the request type is for access and the organization is not currently assigned to the item listed on the AR |
| IM.ITFR.1.02.13 | Route Assistance Request for access only | Solution shall have the capability to route the AR when the request type is for access and the requestor is the CA for the item on the AR |
| IM.ITFR.1.02.14 | Route AR for emergency organization access | Solution shall have the capability to route the AR for emergency access when the request type is for access and the requestor is the supply supervisor |
| IM.ITFR.1.02.15 | Route Assistance Request for provisioning | Solution shall have the capability to route the AR to the assigned CAs when the request type is for a provisioning event |
| IM.ITFR.1.02.16 | Route Assistance Request for Support Equipment access | Solution shall have the capability to route the AR to the allowance manager when the request type is for access and the Item type is Support Equipment |
| IM.ITFR.1.02.17 | Route AR for AF Nuclear Weapons Related Materiel access | Solution shall have the capability to route the AR to the AF Nuclear Weapon Center when request type is for access and the Item type is AF NWRM |
| IM.ITFR.1.02.18 | Route AR for Department of Energy NWRM access | Solution shall have the capability to route the AR to the munitions accountable systems officer NWRM when the request type is for access and the Item Type is DOE NWRM |
| IM.ITFR.1.02.19 | Route Assistance Request to performing activity | Solution shall have the capability to route the AR to the performing activity when the request type is other than an access request |
| IM.ITFR.1.02.20 | Route IM AR Line Item for CA approval | Solution shall have the capability to route each IM AR Line Item to CAs for approval |
| IM.ITFR.1.02.22 | Update IM AR Line Item status to awaiting CA approval | Solution shall have the capability to set status to awaiting CA approval for any IM AR Line Item requiring CA approval |
| IM.ITFR.1.02.23 | Update organization access | Solution shall have the capability to associate Item to the CA approved organization |
| IM.ITFR.1.02.24 | Assign Cognizant Authority | Solution shall have the capability to auto assign IM AR Line Item attributes to the appropriate CAs |
| IM.ITFR.G.1.02.04 | Create notification for access request | Solution shall notify designated users of Item access requests |
| IM.ITFR.1.02.25 | Obtain Cognizant Authority disposition | Solution shall have the capability to obtain the CA authorization disposition |
| IM.ITFR.1.02.26 | Obtain Cognizant Authority digital signature | Solution shall have the capability to obtain the CA digital signature |
| IM.ITFR.1.02.27 | Update access request with effective date | Solution shall have the capability for the CA to change the effective dates of the access request |
| IM.ITFR.1.02.28 | Obtain CA access response of concur | Solution shall have the capability to set the IM AR Line Item status to concur when a CA approves the request |
| IM.ITFR.1.02.29 | Obtain CA access response of nonconcur | Solution shall have the capability to set the IM AR Line Item status to nonconcur when a CA disapproves the request |
| IM.ITFR.1.02.30 | Obtain CA access response of concur with changes | Solution shall have the capability to set the IM AR Line Item status to concur with changes when a CA modifies and approves the request |
| IM.ITFR.G.1.02.05 | Create notification for late response | Solution shall notify designated users of late AR responses |
| IM.ITFR.G.1.04.06 | Create notification for completed IM AR Line Item | Solution shall notify designated users of completed IM AR Line Items |
| IM.ITFR.1.05.01 | Evaluate IM AR Line Item Status | Solution shall have the capability to determine if all IM AR Line Items have been dispositioned |
| IM.ITFR.1.05.02 | Identify Late Assistance Request | Solution shall have the capability to systematically identify AR that exceed the estimated response time |
| IM.ITFR.G.1.05.07 | Create notification for late Assistance Request | Solution shall notify designated users of late ARs |
| IM.ITFR.1.06.01 | Update IM AR status to closed | Solution shall have the capability to set the IM AR status to closed when all IM AR Line Items have been dispositioned |
| IM.ITFR.G.1.06.08 | Create notification for AR closure | Solution shall notify designated users of AR closures |
| IM.ITFR.2.01.01 | Route Assistance Requests by priority attribute | Solution shall have the capability to route the AR based on the AR attributes |
| IM.ITFR.2.02.01 | Create new AF Item Record for rapid response | Solution shall have the capability to systematically create an unique AF Item Record within 15 minutes of submission of a rapid response IM AR |
| IM.ITFR.2.02.02 | Create legacy item id numbers | Solution shall have the capability to create multiple legacy-based item identification number schemas |
| IM.ITFR.G.2.02.09 | Create stakeholder notification for Item Master updates | Solution shall notify designated users of IM AR updates |
| IM.ITFR.2.02.03 | Update rapid response IM AR Line Item status to AF Item number created | Solution shall have the capability to set the IM AR Line Item status to AF Item number created when the AF Item Record is created |
| IM.ITFR.2.02.04 | Update Assistance Request with AF Item number | Solution shall have the capability to auto populate the AR with an AF Item number |
| IM.ITFR.2.02.05 | Assign IM AR requestors organization access | Solution shall have the capability to establish the IM AR requestor's organization as a user of the Item when the AF Item Record is created |
| IM.ITFR.2.02.06 | Associate Items to organization | Solution shall have the capability to associate Items to approved organization upon CA approval |
| IM.ITFR.G.2.02.10 | Create CA notification for attribute authorization requirement | Solution shall notify CA of attribute authorization requirements |
| IM.ITFR.2.03.01 | Identify Cognizant Authority attributes | Solution shall have the capability to identify attributes from the AR that need to be forwarded to the CA for approval |
| IM.ITFR.2.03.02 | Identify Cognizant Authority | Solution shall have the capability to Identify the required CA approvals based on AR attributes |
| IM.ITFR.2.03.03 | Route IM AR Line Item Cognizant Authority | Solution shall have the capability to route each IM AR Line Item to CAs for approval |
| IM.ITFR.2.03.04 | Update IM AR Line Item status to CA approval pending | Solution shall have the capability to set the IM AR Line Item status to CA approval pending |
| IM.ITFR.2.04.01 | Update Assistance Request with Cognizant Authority suspense | Solution shall have the capability to revise the AR suspense need date |
| IM.ITFR.2.04.02 | Identify late Cognizant Authority approvals | Solution shall have the capability to systematically identify the IM AR Line Items that exceed suspense need date |
| IM.ITFR.G.2.04.11 | Create CA notification for pending workload | Solution shall notify designated users of pending workload to the CA |
| IM.ITFR.G.2.04.12 | Create management notification for late CA approval | Solution shall notify designated management of late CA approvals |
| IM.ITFR.2.04.03 | Obtain CA response of concur | Solution shall have the capability to obtain CA response when a CA approves the request |
| IM.ITFR.2.04.04 | Obtain CA response of nonconcur | Solution shall have the capability to obtain CA response when a CA disapproves the request |
| IM.ITFR.2.04.05 | Obtain CA response of concur with changes | Solution shall have the capability to obtain CA response when a CA modifies and approves the request |
| IM.ITFR.2.05.01 | Obtain CA response to Item attribute | Solution shall have the capability to obtain the CA authorization disposition |
| IM.ITFR.2.06.01 | Route AR Cognizant Authority by responses | Solution shall have the capability to route the AR based on the CA responses |
| IM.ITFR.2.06.02 | Update IM AR Line Item status to CA concur | Solution shall have the capability to set the IM AR Line Item status to concur when a CA approves the request |
| IM.ITFR.2.06.03 | Update IM AR Line Item status to CA nonconcur | Solution shall have the capability to set the IM AR Line Item status to nonconcur when a CA disapproves the request |
| IM.ITFR.2.06.04 | Update IM AR Line Item status to CA concur with changes | Solution shall have the capability to set the IM AR Line Item status to concur with changes when a CA modifies and approves the request |
| IM.ITFR.2.07.01 | Provide collaborate environment | Solution shall have the capability for a collaboration environment |
| IM.ITFR.2.07.02 | Update IM AR Line Item status to dispute resolution | Solution shall have the capability for the Item Lifecycle Management Team to document final resolution status |
| IM.ITFR.2.07.03 | Route Assistance Request post resolution | Solution shall have the capability for the Item Lifecycle Management Team to reroute the AR for CA coordination after resolution has been documented |
| IM.ITFR.02.08.01 | Update AF Item Record | Solution shall provide the capability to update AF Item Record based on approved IM AR Line Item attributes |
| IM.ITFR.G.2.08.13 | Create stakeholder notification for Item Master updates | Solution shall notify designated users of Item Master updates |
| IM.ITFR.2.08.02 | Identify Item stakeholders | Solution shall have the capability to evaluate the updated AF Item Record to obtain a list of Item stakeholders required for the notification action |
| IM.ITFR.2.08.03 | Associate the AF Item number to the IM AR Line Item | Solution shall have the capability to associate the AF Item number to the applicable IM AR Line Item |
| IM.ITFR.2.08.04 | Update IM AR Line Item status | Solution shall have the capability to update status to the applicable IM AR Line Item |
| IM.ITFR.G.2.08.14 | Create stakeholder notification for product structure updates | Solution shall notify designated users of product structure updates |
| IM.ITFR.2.08.05 | Route Assistance Request Stocklist action | Solution shall have the capability to systematically route Federal Catalog ARs |
| IM.ITFR.2.08.06 | Identify Stocklist actions | Solution shall have the capability to identify Federal Cataloging actions based on IM AR attributes |
| IM.ITFR.3.01.01 | Search Federal Catalog for Like Item | Solution shall have the capability to search the Federal Catalog using any combination of over 2000 Master Requirement Code attributes |
| IM.ITFR.3.01.02 | Search AF Item Master for Like Item | Solution shall have the capability to search the AF Item Master by technical attributes |
| IM.ITFR.3.03.01 | Display search results for Like Item | Solution shall have the capability to display Like Item results |
| IM.ITFR.3.03.02 | Identify catalog sources for Like Item | Solution shall have the capability to identify system source of Like Item found |
| IM.ITFR.3.03.04 | Select requestor Like Item | Solution shall have the capability to allow originators to select a Like Item |
| IM.ITFR.3.03.05 | Route IM AR Line Item for Like Item | Solution shall have the capability to route the IM AR Line Item to CA for Like Item authorization |
| IM.ITFR.G.3.03.15 | Create requestor notification for Like Item results | Solution shall provide requestor of Like Item search results |
| IM.ITFR.G.3.03.16 | Create CA notification for authorization required | Solution shall notify CA of authorization requirements |
| IM.ITFR.3.03.06 | Set Cognizant Authority suspense date | Solution shall have the capability to set the CA suspense need date |
| IM.ITFR.3.03.07 | Identify late Cognizant Authority approval suspense | Solution shall have the capability to systematically identify the IM AR Line Items that exceed suspense need date |
| IM.ITFR.G.3.03.17 | Create notification for missed CA suspense date | Solution shall notify the designated users of missed CA suspenses |
| IM.ITFR.3.03.08 | Update AR line item with Like Item search results | Solution shall have the capability to append the Like Item search results to the AR |
| IM.ITFR.3.03.09 | Route IM AR Line Item with Like Item authorization | Solution shall have the capability to route the IM AR Line Item to CA for Like Item authorization |
| IM.ITFR.3.04.01 | Obtain Cognizant Authority Like Item response | Solution shall have the capability to obtain the CA authorization disposition for Like Item suitability |
| IM.ITFR.3.04.02 | Obtain digital signature | Solution shall have the capability to apply digital signatures to ARs |
| IM.ITFR.3.04.03 | Obtain Like Item CA response of concur | Solution shall have the capability to set the IM AR Line Item status to concur when a CA approves the request |
| IM.ITFR.3.04.04 | Obtain Like Item CA response of nonconcur | Solution shall have the capability to set the IM AR Line Item status to nonconcur when a CA disapproves the request |
| IM.ITFR.3.04.05 | Obtain Like Item CA response of concur with changes | Solution shall have the capability to set the IM AR Line Item status to concur with changes when a CA modifies and approves the request |
| IM.ITFR.3.04.06 | Select Cognizant Authority Like Item | Solution shall have the capability to allow CA to select a like item |
| IM.ITFR.3.04.07 | Apply Public Key Infrastructure | Solution shall have the capability to apply PKI data for IM AR Item Record |
| IM.ITFR.3.05.01 | Route Assistance Request by Cognizant Authority response | Solution shall have the capability to route the AR based on the CA responses |
| IM.ITFR.G.3.05.18 | Create requestor notification of AR disposition | Solution shall notify the requestor of the AR disposition update |
| IM.ITFR.3.05.02 | Update IM AR Line Item status to Like Item approved | Solution shall have the capability to set the IM AR Line Item status to Like Item approved when the CA selects a Like Item |
| IM.ITFR.3.05.03 | Update IM AR Line Item status to Like Item disapproved | Solution shall have the capability to set the IM AR Line Item status to Like Item disapproved when the CA disapproves all Like Item |
| IM.ITFR.3.06.01 | Create AF Item Record when no Like Items found | Solution shall have the capability to create AF Item Record for the approved requested Item when no Like Items are found |
| IM.ITFR.3.06.02 | Update AF Item Record attributes | Solution shall provide the capability to update AF Item Record with all approved IM AR Line Item attributes |
| IM.ITFR.3.06.03 | Create new AF Item Record for routine response | Solution shall provide the capability to create a new AF Item Record based on approved IM AR Line Item attributes |
| IM.ITFR.G.3.06.19 | Create stakeholder notification for routine response Item Master updates | Solution shall notify designated users of IM AR routine response updates |
| IM.ITFR.3.06.04 | Update IM AR Line Item to AF Item number created | Solution shall have the capability to set the IM AR Line Item status to AF Item number created when the Item Record is created |
| IM.ITFR.3.06.05 | Update IM AR Line Item with AF Item number | Solution shall have the capability to populate the IM AR Line Item with an AF Item number |
| IM.ITFR.3.06.06 | Assign organization access | Solution shall have the capability to enable the AR requestor's organization as a user of the item once the AF Item Record is created |
| IM.ITFR.3.06.07 | Route IM AR Line Item for Federal Cataloging actions | Solution shall have the capability to route the IM AR Line Item for Federal Cataloging actions |
| IM.ITFR.3.07.01 | Assign organization access for Like Item | Solution shall have the capability to enable the AR requestor's organization as a user of the Like Item |
| IM.ITFR.4.01.01 | Update IM AR Line Item status to coordination required | Solution shall have the capability to set the IM AR Line Item status to coordination required when external agencies need to approve the request |
| IM.ITFR.4.01.02 | Update IM AR Line Item status to coordination not required | Solution shall have the capability to set the IM AR Line Item status to coordination not required when external agencies not required to approve the request |
| IM.ITFR.4.02.01 | Create Coordination Package | Solution shall have the capability to systematically assemble the Coordination Package |
| IM.ITFR.4.04.01 | Route Coordination Package by response | Solution shall have the capability to route the Coordination Package based on the Interservice responses |
| IM.ITFR.4.05.01 | Modify Coordination Package AR source material | Solution shall have the capability for the ILM Team to modify the AR that is used to generate a Coordination Package |
| IM.ITFR.4.05.02 | Modify Coordination Package AF Item Record source material | Solution shall have the capability for the Item Lifecycle Management Team to modify the AF Item Record that is used to generate an Coordination Package |
| IM.ITFR.4.05.03 | Update IM AR Line Item status to Coordination Package rejected | Solution shall have the capability to set the IM AR Line Item status to Coordination Package rejected when the Item Lifecycle Management Team accepts the rejections |
| IM.ITFR.4.05.04 | Update IM AR Line Item status to revision required | Solution shall have the capability to set the IM AR Line Item status to Coordination Package revision required when the Item Lifecycle Management Team chooses to revise the Coordination Package |
| IM.ITFR.4.06.01 | Create Federal Cataloging data | Solution shall have the capability to assemble AF originated Federal Cataloging data |
| IM.ITFR.4.06.02 | Update IM AR Line Item status to Federal Cataloging required | Solution shall have the capability to set the IM AR Line Item status to Federal Cataloging required upon submission of the assembled package to the Federal Cataloging System |
| IM.ITFR.4.06.03 | Identify Federal Cataloging data discrepancies | Solution shall have the capability to identify discrepancies between the Federal Catalog request and Federal Catalog response |
| IM.ITFR.G.4.06.20 | Create notification for Federal Cataloging data discrepancies | Solution shall notify designated users of Federal Cataloging data discrepancies |
| IM.ITFR.4.06.04 | Route Federal Catalog by response | Solution shall have the capability to route the Federal Catalog data based on the Federal Catalog responses |
| IM.ITFR.4.06.05 | Modify Federal Cataloging AR data source material | Solution shall have the capability for the Item Lifecycle Management Team to modify the AR that is used to generate Federal Cataloging data |
| IM.ITFR.4.06.06 | Modify Federal Cataloging AF Item Record data source material | Solution shall have the capability for the Item Lifecycle Management Team to modify the AF Item Record that is used to generate Federal Cataloging data |
| IM.ITFR.4.08.01 | Update AF Item Record with Federal Catalog responses | Solution shall provide the capability to apply Federal Catalog responses to the appropriate Item Record |
| IM.ITFR.4.08.02 | Update IM AR Line Item status to Federal Cataloging action complete | Solution shall have the capability to set the IM AR Line Item status to Federal Cataloging Action Complete upon completion of the Item update |
| IM.ITFR.G.1.01.21 | Manage notification subscriptions | Solution shall allow a user to subscribe to a notification |
| IM.ITFR.G.1.01.22 | Provide notifications | Solution shall provide notifications based on business rules |
| IM.ITFR.G.5.02.01 | Provide Provisioning Assistance Request collaboration workspace | Solution shall provide the requestor with a collaborative workspace to manage Provisioning ARs |
| IM.ITFR.5.03.01 | Create Provisioning Parts List | Solution shall support creation of a Provisioning Parts List (PPL) |
| IM.ITFR.5.04.01 | Send Provisioning Data Set | Solution shall have the ability to send a complete provisioning data set |
| IM.ITFR.5.05.01 | Update IM AR Line Item status to accepted | Solution shall have the capability to set the IM AR Line Item status to accepted when the request passes validation |
| IM.ITFR.5.05.02 | Update IM AR Line Item status to rejected | Solution shall have the capability to set the IM AR Line Item status to rejected when the request fails validation |
| IM.ITFR.5.05.03 | Update IM Provisioning AR Line Item with estimated response time | Solution shall have the capability to update the estimated response time for each IM Provisioning AR Line Item |
| IM.ITFR.5.05.04 | Assign IM Provisioning AR Line Item | Solution shall have the capability to assign an Item Lifecycle Management Team to each IM Provisioning AR Line Item using the Federal Supply Class value |
| IM.ITFR.5.05.05 | Assign Cognizant Authority | Solution shall have the capability to auto assign IM Provisioning AR Line Item attributes to the appropriate Cognizant Authorities |
| IM.ITFR.5.05.06 | Update IM Provisioning AR Line Item status | Solution shall have the capability to update status to the applicable IM AR Line Item |
| IM.ITFR.5.07.01 | Update Provisioning Line Item Sequence Number | Solution shall enable update of Provisioning Line Item Sequence Number (PLISN) |
| IM.ITFR.5.07.02 | Close Out Provisioning Line Item Sequence Number | Solution shall have the capability to set the PLISN IM Provisioning AR line item status to closed |
| IM.ITFR.5.08.01 | Update closed PLISN information | Solution shall allow a designated user to update Air Force actions associated with a closed PLISN |
| IM.ITFR.5.08.02 | Export data in the LSA-036 format | Solution shall support export of data in the LSA-036 format |
| IM.ITFR.5.08.03 | Export data in the Provisioning Parts List format | Solution shall support export of data in the Provisioning Parts List (PPL) format |
| IM.ITFR.5.03.02 | Import Contractor Data | Solution shall support import of contractor data |
| IM.ITFR.5.03.03 | Create Provisioning Control Code | Solution shall support creation of Provisioning Control Codes (PCC) |
| IM.ITFR.5.03.04 | Create Provisioning Contract Control Number | Solution shall support creation of Provisioning Contract Control Number (PCCN) |
| IM.ITFR.5.03.05 | Capture PLISN Comments | Solution shall enable capture of user comments at the PLISN level |
| IM.ITFR.5.05.07 | Identify Catalog Requirements for PLISN | Solution shall have the capability to identify cataloging requirements for each PLISN |
| IM.ITFR.5.01.01 | Assign Provisioning Team | Solution shall enable assignment of team members to create a provisioning package |
&F
&A &P of &N
IM ITTRs
| ITTR ID # | ITTR Definition |
| 1 | Solution shall be hostable in a DoD approved IL-4 facility using AWS or Azure cloud-hosting environment. |
| 2 | Solution shall comply with DISA Application Security and Development Security STIG. |
| 3 | Solution shall integrate with automated test tools for functional, performance and security testing. |
| 4 | Solution shall satisfy all requirements to obtain a Joint Interoperability Test Command (JITC) certificate of interoperability. |
| 5 | Solution shall include a transactional auditing capability to meet the Defense Financial Improvement and Audit Readiness (FIAR) Requirements. |
| 6 | Solution shall limit third-party client-side browser plug-ins to PDF viewer. |
| 7 | The web pages generated by the solution shall be built using Responsive Web Design principles and techniques, making web pages appear correctly and readable on all devices (i.e., desktops, laptops, smartphones, and tablets). |
| 8 | Solution shall ensure the integrity of the data during implementation of updates. |
| 9 | Solution shall be compatible with tools to synchronize environments (migration/change control). Examples of environments that might be required include: sandbox, development, testing, training, production, and disaster recovery (DR). |
| 10 | Solution shall support a variety of commonly used mobile platforms, whether via integrated app support or web portals compatible with standard mobile web browsers. |
| 11 | Solution shall write all software/business components (including user interface) in a cross-platform programming language, using standard APIs and class libraries. |
| 12 | Solution shall provide software to be compatible with user defined printers and plotters, and respond appropriately when printing errors are reported. |
| 13 | Solution shall be able to capture, store, and export metadata. Industry Standard Markup Language should be used to export technical metadata, business metadata, and operational metadata. |
| 14 | Solution shall allow for IMLCI branding on all notifications, electronic and physical. |
| 15 | Solution shall allow for IMLCI to control the IMLCI branding throughout the software, via configuration management. |
| 16 | Solution shall allow for implementing IMLCI branding on all portals and/or entry points whether they be from inside or outside the IMLCI network. |
| 17 | Solution shall provide support for IMLCI branded email content and formatting. |
| 18 | Solution shall have a clear context mechanism (similar to bread crumb trail of menus) that shows the user where they are at all time in context to the overall functionality of the software. |
| 19 | Solution shall support differences in users’ knowledge and abilities, by providing shortcuts and fast paths for experienced users, while also having clear step by step intuitive solutions for novice users. |
| 20 | Solution shall meet the Application and Information Accessibility criteria proscribed by the 508 Standards of the U.S. Rehabilitation Act of 1973, as Revised in January 18, 2018, to also include the Web Content and Accessibility Guidelines (WCAG) version 2.1. |
a) Section 508 of the U. S. Rehabilitation Act of 1973, as amended by the Workforce Investment Act of 1998;
https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines
b) World Wide Web Consortium (W3C) WCAG v 2.1;
http://www.w3.org/TR/WCAG21/
| 21 | Solution shall provide support International Formats by using neutral data structures and encapsulating format/validation in a programming function. |
| 22 | Solution shall provide a JSON over REST based user management API that can be used by disparate systems to enable seamless management of users. |
| 23 | Solution shall support Lightweight Directory Access Protocol (LDAP) or STARTTLS. |
| 24 | Solution shall support two-factor authentication (2FA) in accordance with National Institute of Standards and Technology (NIST) guidelines. |
| 25 | Solution shall support Oauth for accessing external resources and OpenID Connect (OIDC) for federated online identity. |
| 26 | Solution shall support Simple Cloud Identify Management (SCIM) standard for user provisioning. |
| 27 | Solution shall provide SPML (Service Provisioning Markup Language) support. |
| 28 | Solution shall provide a data access API (including support for BI tooling integration/connectivity) that can be accessed and used by commercially available business intelligence tools (e.g., Microsoft Power BI, Tableau Online, Qlik). |
| 29 | Solution shall provide API access to day-to-day administrative features of the platform, such as managing user accounts and permissions, accessing platform usage data, and managing configuration of the platform programmatically. |
| 30 | Solution shall provide APIs that leverage web services interfaces and file exchange and storage integrations (e.g., SSH File Transfer Protocol [SFTP], cloud storage or enterprise file synchronization and sharing [EFSS] solutions) for bulk import and export of data. |
| 31 | Solution shall provide a development center that includes documentation for all APIs based on standard interface technologies, such as REST and SOAP, and also has access to a set of software development kits (SDKs) for the leading programming languages including Java, .NET, Ruby, Perl and Python. |
| 32 | Solution shall utilize Service Oriented Architecture (SOA) principles to abstract the application layers from interfaces with other components to support the concepts of re-usability and ease of maintenance over time. |
| 33 | Solution shall allow for one integrated data architecture (data model). |
| 34 | Solution shall integrate with a user security model (roles and access for users) to be referenced and managed by commonly used tools and utilities. |
| 35 | Solution shall comply with Air Force network security requirements. |
| 36 | Solution shall allow for one unified/integrated configuration management process. |
| 37 | Solution shall have the ability to develop integrations with no code / drag and drop. |
| 38 | Solution shall support native APIs (e.g. RESTful & Web Services). |
| 39 | Solution shall provide mobile device SDKs. |
| 40 | Solution shall provide configuration management and version control for configurable and development objects. |
| 41 | Solution shall provide an automated tool that can perform a “where used” analysis and report on one or more objects (configurable or not), and all data attributes in the entire data model. |
| 42 | Solution shall provide an automated tool that can perform a “where used” analysis and report on the meta-data for all data attributes and all configuration objects, across the entire solution. |
| 43 | Solution shall provide usage and data tracking tools which IMLCI can use to understand the value of the services to IMLCI and to monitor SLA metrics. |
| 44 | Solution shall provide high availability interface and management console such that no single cloud data center issue causes a failure in the manageability of Solution. |
| 45 | Solution shall provide the ability to view and export a list of users by roles and permissions. |
| 46 | If Solution is multitenant based, Solution shall provide controls for separation of users and data within the service. |
| 47 | Solution shall be on a DoD approved products lists (APL), be covered by a DoD program's Authority to Operate (ATO), or provide a plan to obtain APL approval. |
| 48 | Solution shall provide data and application level security approvals, notifications and workflow by role. |
| 49 | Solution shall provide ability to impersonate other users, granted manually and removed manually or automatically after specific timeframes. |
| 50 | Solution shall record all actions taken by a user impersonating another user and be recorded as the "true" user, not the impersonated user. This is for the entire length of time of impersonation. |
| 51 | Solution shall provide dynamic role assignment based upon a combination of configurable factors including role within organization, location, job, position, manager, or other IMLCI defined criteria. |
| 52 | Solution shall provide the ability to encrypt data at rest (on disk/storage) with the ability for IMLCI to own and possess the encryption keys. |
| 53 | Solution shall follow secure code practices such as the Secure SDLC (Secure Software Development Lifecycle) framework or Open Web Application Security Project (OWASP). |
| 54 | Solution shall be capable of securing sensitive data, ability to mark it, and report on where over exposure of sensitive data resides and report on who is accessing it; as well as privilege escalation. |
| 55 | Solution shall provide evidence it has applied or in the process to meet minimum standard benchmarks defined by DISA IASE Applications https://iase.disa.mil/stigs/Pages/index.aspx# as defined by the DoD Application Security and Development Security Technical Implementation Guide based upon NIST 800-53 controls. Solution shall have been reviewed by a 3rd party assessor for cybersecurity or be in the process and provide evidence. |
| 56 | Solution shall provide emergency and routine security patches in accordance with the Vulnerabilities Equities Process (VEP) Charter. |
| 57 | Solution shall support the enterprise logging Security Information and Event Management (SIEM) solution. |
| 58 | Solution shall provide the ability to mask (obfuscation) any data element based upon configurable rules and elements (e.g., Name, Employee ID, National ID, Address). |
| 59 | Solution shall offer a real-time performance network monitoring service that is accessible from a service interface or the management console. |
| 60 | Solution shall abide by privacy protections and data use terms per the Privacy Act of 1974. |
| 61 | The vendor shall publish or share the network and internet connectivity architecture and topology for the solution. |
| 62 | Solution shall comply with SFIS Structure as mandated by DOD FMR 7000.14R, Vol 1, Ch 4. Target Financial Business Feeder Systems, as defined in paragraph 040204, 05, and 0403 mandate the business rules, implementation procedures, compliance checklist, and compliancy requirements which must be met to ensure all SFIS requirements are met. |
| 63 | Solution shall utilize Public Key Infrastructure (PKI) for authenticating users and devices. |
| 64 | Solution shall utilize Public Key Infrastructure (PKI) for providing data encryption. |
| 65 | Solution shall utilize Public Key Infrastructure (PKI) for digital signature services to provide nonrepudiation of data. |
| 66 | Solution shall interface with DoD PKI architecture. |
| 67 | Solution shall reference DoD certificate servers' revocation lists to validate the active status of authentication certificates at the time of authentication. |
| 68 | Solution shall provide command line interfaces (CLI) for their APIs. |
| 69 | Solution shall be compatible with the currently supported releases of the Air Force Standard Desktop Configuration (SDC) and its associated applications. |
| 70 | Solution shall integrate with approved open source CI/CD utilities and tools. |
| 71 | Solution shall support integration with an approved version control system. |
| 72 | Solution shall support use of APIs in the product build, compile, deploy and configuration process. |
| 73 | Solution shall support programmatic manipulation of environmental configurations in an exposed file. |
&F
&A &P of &N
IM LSRs
| LSR ID # | Lifecycle Support Requirements (LSR) Name | LSR Definition | LSR Category Name |
| 1 | Usability | The solution shall provide a configurable exchange framework, designed to minimize inline coding, that leverages point/click and drag/drop user-managed exchange services. | Data Exchange Framework |
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 .