CAMS Request for Information Technical Attachments_2025-Jul21_v-1_Rev 1.docx
DOCX document 61 KB Posted
- Solicitation number
- CBPRFI20250725
About this file
This document is a Request for Information (RFI) for the U.S. Customs and Border Protection (CBP) Asset Management System (CAMS), seeking comprehensive information from potential vendors about an enterprise-wide asset lifecycle management solution. The RFI requires detailed responses across six key areas: corporate information, solution description, training approach, support methodology, data analytics capabilities, and pricing/licensing details. Vendors must address critical business requirements spanning acquisition lifecycle, controls and performance, disposal process, maintenance process, and general system functionality, with specific responses detailing how their solution meets 98 distinct system requirements.
The proposed CAMS system aims to replace 13 existing disparate asset management systems, providing CBP with improved asset accountability, data integrity, and analytical capabilities. The system must support complex asset tracking across multiple scenarios including procurement, maintenance, reporting, compliance, financial management, and mission execution. Key technical requirements include integration with existing financial and enterprise systems, support for barcode and mobile technologies, robust reporting capabilities, automated workflows, and comprehensive asset lifecycle management from acquisition through disposal. Vendors are expected to provide detailed descriptions of their solution's functionality, architecture, software assurance, readiness levels, and pricing structure for approximately 8,000-10,000 users.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| APMD_OPS_STAFF_CAMS_RFI_Consolidated_Q and A_.pdf | ||
| APMD_OPS_STAFF_CAMS_RFI_Consolidated_Questions_Responses_.xlsx | XLSX spreadsheet | |
| APMD_ACQPGM_OFAM_CAMS_RFI_250721_v2.docx | DOCX document | |
| APMD_ACQPGM_OFAM_CAMS_RFI_250721_v-1.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CAMS Request for Information Technical Attachments Requested Information Item 1 – Corporate Information and Solution Context: CBP requests information about the provider, their experience, and system related services necessary to support full deployment of an asset management system across CBP.
Item 2 – Critical Business Requirements: CBP requests information about the offered solution’s ability to perform against a non-exhaustive list of high-level asset management requirements across CBP.
Attachment A – CAMS Scenarios: Scenarios that the CAMS system will support are provided. Respondents are encouraged to consider these scenarios when providing responses to Items 1 and 2.
Item 1 – Corporate Information and Solution Context: CBP requests information about the provider, their experience, and system related services necessary to support full deployment of an asset management system across CBP.
1. Corporate Profile - not to exceed one (1) page, including point-of-contact, CCR #, DUNS #, business size status and socio-economic status such as: Competitive 8(a), HUBZone, Emerging Small Business, Partial Small Business, Total Small Business, Veteran-Owned Small Business, and Service-Disabled Veteran-Owned Small Business. Identify the company's management system certifications, such as Capability Maturity Model Integration (CMMI) and International Organization for Standardization (ISO).
2. Previous Performance - not to exceed six (6) pages, describe prior experience providing asset management solutions to CBP, the Department of Homeland Security, other Federal Government organizations, or the private sector within the last five (5) years. Provide contract number, name and point-of-contact information for each customer, period of performance, total dollar value, type of contract, and a summary of the products and services provided. A maximum of five (5) detailed examples, are requested. Identify whether the company participated as the prime contractor or a subcontractor. Additionally, describe the single, largest implementation to date of the offered solution system. In addition to a general overview, please describe:
a. The number of active and concurrent users supported.
b. How the solution addresses users from different geographical areas and time zones.
c. The extent to which the system was implemented across multiple unique divisions or large user groups.
3. Solution Description – not to exceed four (4) pages, provide a description of your product. Include classification in accordance with the FAR (e.g., Commercial Item, COTS Item, NDI, DI, etc.).
a. Functionality – Describe the basic functions the product performs.
b. Architecture – Provide a functional system architecture description. In addition:
i. Based on the high level system requirements, what hardware, including quantity, is required/recommended to implement the solution (servers, cloud computing resources, etc.)?
ii. Does the product use an open systems interface approach?
iii. Identify advantages of design that would limit cost and support drivers for your product.
c. Software Assurance – Describe your software assurance services.
d. What is the Manufacturing Readiness Level (MRL) and Technology Readiness Level (TRL) of the product?
e. Provide Reliability, Availability, and Maintainability data for your product.
f. Identify any limited data rights or constraints on your product.
4. Training – not to exceed one (1) page, describe approach for initial and on-going training on the use and administration of the vendor solution that would enable execution of provided CAMS Operational Scenarios. Detail aspects of training and support, such as train-the-trainer, classroom instruction, and on-line computer based training.
5. Support – not to exceed one (1) page, describe approach for on-going solution technical and operational support, i.e., through a helpdesk, manuals, tutorials, etc.
6. Data Analytics – not to exceed one (1) page, describe approach to providing data analytics capabilities that would enable execution of the types of analysis outlined in the provided CAMS Operational Scenarios.
7. Pricing, licensing, and system requirements – not to exceed one (1) page:
a. Is this product available on the GSA schedule? If so, please provide the GSA schedule number.
b. What Software licenses will be required to implement and sustain the vendor solution and how are they structured?
i. What is the annual license cost per user for approximately 8,000-10,000 users?
ii. Is there an additional one-time, upfront license configuration? If so what is the cost?
iii. Is there an additional annual maintenance costs per license? If so what is the cost?
iv. What costs are associated with renewal of licenses and/or subscriptions?
v. What escalation percent is applied to annual license costs?
c. Is training included in the license costs listed above or is it additional? If additional, what is the approximate cost?
d. Is additional manpower development/solutioning necessary for implementation? If so, what is the additional costs of these teams? Please break down any manpower components by labor category.
e. What is the cost be to integrate (or connect to an API) for approximately 8 existing CBP Asset Management Systems?
f. What is the cost to migrate data from existing CBP Asset Management systems to your product or solution?
g. As applicable, how are costs calculated for additional features/applications (Apps)?
h. What is the cost associated with adding additional features to your production or solution?
Item 2 – Critical Business Requirements: CBP requests information about the offered solution’s ability to perform against a non-exhaustive list of high-level asset management requirements across CBP.
Critical Requirements Categories
| 1. Acquisition Lifecycle |
| Critical business requirements relating to the procurement of assets such as: planning, procurement, purchases, categorization, and receiving. |
| 2. Controls & Performance |
| Critical business requirements relating to data and reporting functionality. |
| 3. Disposal Process |
| Critical business requirements relating to disposal in the asset management lifecycle such as: lost, damaged, destroyed, stolen, reutilized, disposed, and retired. |
| 4. Maintenance Process |
| Critical business requirements relating to sustainment in the asset management lifecycle such as: supply support, inventory management, maintenance planning, utilization and tracking, and ticket/work order reporting. |
| 5. General |
| Critical business requirements relating to general system functionality that does not fall under the other categories. |
For each critical requirement please respond with the following information
| [A] Vendor Description |
| [B] Requirement Met? |
· Meets
· Does Not Meet
| [C] What requirements are included in the vendor product? |
| [D] What requirements are not included in the vendor product? |
| [E] What additional development is required to fully meet? How long do you expect it to take? |
| [F] Additional Narrative |
(1) Acquisition Lifecycle
| Req ID |
| Requirement Description |
| 1.01 |
| The system shall support asset management by tracking key asset details including but not limited to unique identifiers, vendor, lease information, order date, shipping date, receiving date, person who received asset, date in service, expiration date/shelf-life, acquisition cost, location, authorized asset user, end-of-warranty, transfer agency for interagency transfers, service contract period of performance (PoP) end date, transportation requirements, and asset type. The system shall track all data on total and per asset basis. |
| 1.02 |
| The system shall allow for sub-categorization and parent-child relationships for asset data, which includes alignment to guidance such as the Federal Supply Classification codes. |
| 1.03 |
| The system shall allow users to create and track preferred vendor profiles and non-preferred vendor profiles by capturing information including but not limited to name, estimated prices, purchase history, and required certifications (such as airworthiness for aviation parts, and mechanic information for authorizing repair actions). |
| 1.04 |
| The system shall allow users to view planned, pending and completed purchase orders and procurement contracts. |
| 1.05 |
| The system shall include the capability to prepare, save, retrieve, print, and email purchase orders. |
| 1.06 |
| The system shall calculate “optimal” order quantity and reorder point from applicable sources such as total requirement, quantity on hand, quantity already on-order, demand rates, logistics data (repair pipeline data, transportation data, etc.), and purchase history. |
| 1.07 |
| The system shall provide review and approval workflows for all purchase orders and procurement documentation. Government approvers are limited to their own assigned agency/programs. Temporary approvers must be able to be assigned in the absence of the primary approver. |
| 1.08 |
| The system shall recommend procurement strategy based on predetermined calculation methodology (such as lease versus buy or repair verses replace). |
| 1.09 |
| The system shall have the ability to track budget requests, assign purchase orders to budget requests, and receive new assets against budget requests and purchase orders. |
| 1.10 |
| The system shall provide access to key shipping information for assets and parts including but not limited to shipping date, estimated arrival date, shipping carrier, shipping location, receiving location, and shipping status (ordered, awaiting shipment, shipped-in transit, received). |
| 1.11 |
| The system shall support local delivery management by notifying a parts runner to retrieve parts from a local warehouse location when a work order is submitted, issue the parts to the work order (or consume to shop), and deliver the parts to the requestor, authenticate and log delivery of parts and transfer ownership to the requestor. |
| 1.12 |
| The system shall have the ability to track vendor statement of work (SOW) requirements. |
| 1.13 |
| The system shall have the ability to produce and track vouchers that can be used by contractors for government reimbursement on purchases or maintenance. The voucher approval screen shall display asset details related to the request, such as quantity on hand, asset utilization at CBP, etc. |
| 1.14 |
| The system shall allow field locations to be able to perform local purchases. |
(2) Controls & Performance
| Req ID |
| Requirement Description |
| 2.01 |
| The system shall allow users to create, run and save ad hoc and custom reports using any field as criteria including but not limited to trending, daily asset, maintenance, and disposal reports utilizing database reporting tools. |
| 2.02 |
| The system shall have the ability to generate a failure code/trend analysis report that includes a specific family (type), model (item), and failure. |
| 2.03 |
| The system shall be able to export reports in various formats including Microsoft Excel, Project, and Tableau. |
| 2.04 |
| The system shall be capable of integrating with geospatial systems to allow users to view instances of fleet right sizing on a map. |
| 2.05 |
| The system shall provide reporting dashboard features that can calculate and display performance measures. |
| 2.06 |
| The system shall allow users to run all reports by specified reporting periods. |
| 2.07 |
| The system shall have the capability to run all reports at a summary level. |
| 2.08 |
| The system shall provide the cost center group field on all reports. |
| 2.09 |
| The system shall allow users to run reports with the asset status changes/date available as field selection criteria. |
| 2.10 |
| The system shall be capable of integrating with geospatial systems to allow users to view locations by office/cost centers with the number of outstanding asset records for resolution and by certain asset types on a map. |
| 2.11 |
| The system shall provide general reporting capabilities including but not limited to inventory management, performance management, controls, End of Year (DHS/GSA required), CAPSIS, and lost, damaged, destroyed, or stolen (LDDS) property. |
| 2.12 |
| The system shall provide users the ability to create regularly scheduled reports. |
| 2.13 |
| The system shall allow users to create, store, retrieve, update, and track corrective action plans. |
| 2.14 |
| The system shall support audits, including audit planning, testing, account analysis, and substantive procedure reporting of personal property asset management actions. |
(3) Disposal
| Req ID |
| Requirement Description |
| 3.01 |
| The system shall track all data for disposals including but not limited to retirement date, decommission date, disposal type (donation, sale, destruction, exchange/transfer, recovery, and repurpose), value, sale proceeds, and disposal cost. The system shall track all data on total and per asset basis. |
| 3.02 |
| The system shall track assets through the different steps of the disposal process including but not limited to flagged for disposal, disposal prep work in progress, name of vendor handling disposal, etc. and reconcile in-service/retired assets. Disposal may also include donations and transfers. |
(4) Maintenance
| Req ID |
| Requirement Description |
| 4.01 |
| The system shall have the ability to track all maintenance work orders and required parts data including but not limited to stock keeping unit (SKU), parts availability, itemized costs for parts and labor, start and end date of maintenance, estimate and actual time of completion, estimate and actual maintenance expense, warranty and non-warranty expense and labor, and reorder point. The system shall track all data on total and per asset basis. |
| 4.02 |
| The system shall have the ability to track and account for specialty asset details where required including but not limited to safety parameters, software version status, warranty information, and user inputs. |
| 4.03 |
| The system shall support features/solutions to automatically update inventory in real-time to reflect accurate inventory records. |
| 4.04 |
| The system shall have the ability to auto-identify underutilized assets, such as vehicles, based on predetermined calculation methodology and capture/report acquisition/retainment justification as well as highlight potential redistribution options. |
| 4.05 |
| The system shall be able to track and compare assets, such as vehicles, that are in storage or being reassigned to mission requirements. |
| 4.06 |
| The system shall provide fields to record and display performance data for assets including but not limited to meter readings, greenhouse gas emissions, engine hours, generator hours, scan count, odometer, X-ray hours, system hours, cycle counts, home-to-work usage, Mean Time To Repair (MTTR), Mean Time Between Failure (MTBF), Mean Time Before Failures, and Mean Time Before Repair (MTBR). The system shall track all data on total and per asset basis. |
| 4.07 |
| The system shall be able to track cycles including but not limited to preventative maintenance, repair orders, replacement, and overdue maintenance actions. |
| 4.08 |
| The system shall be able to link repair orders/work orders to one repair and track the overall completion progress of that repair. |
| 4.09 |
| The system shall provide, for a select group of repairable assets, an ability to review pre-repair documentation and document the authorization of repairs. |
| 4.10 |
| The system shall be able to identify an existing vehicle's replacement unit and track the replacement unit's information such as estimated delivery date, estimated cost and like items. |
| 4.11 |
| The system shall be able to calculate estimated costs by manual entry, automatically pulling the "last cost" of the item, or other predetermined calculation methodology. |
| 4.12 |
| The system shall allow the capability to re-baseline calibration cycles on the calibration record including but not limited to Precision Measurement Equipment Laboratory (PMEL) assets. |
| 4.13 |
| The system shall provide a current labor display. This display should show all active employees, the specific task they are currently performing, and tasks in the queue to be performed. |
| 4.14 |
| The system shall provide the capability to report a mechanic's performance (such as repair time) against a labor estimate or product standard and analyze for reasonableness. |
| 4.15 |
| The system shall track packaging, handling transportation, facilities, disposal and environmental impact considerations for lifecycle operations and maintenance of assets. |
| 4.16 |
| The system shall track the utilization and location of all accountable, non-accountable, and Heritage assets including but not limited to location, transfer, agency owner, quantity on hand, condition, status, and Authorized Asset User. |
| 4.17 |
| The system shall auto populate fields and link work orders to asset data including but not limited to asset number, point of contact (POC), POC Phone Number, location, status, equipment number, barcode number and serial number fields when a work order is created. |
| 4.18 |
| The system shall provide the capability to create, update, and track asset status indicators with associated time stamps that include, but are not limited to, on-hand, on-order, in-use, in-repair, in-transit, disposed, and current condition. |
| 4.19 |
| The system shall provide the ability to link to asset technical data, operation and user manuals, and drawings (as applicable). |
| 4.20 |
| The system shall provide inventory adjustments to be charged to an indirect account when the actual product amount varies from the amount identified by the system. |
(6) General
| Req ID |
| Requirement Description |
| 5.01 |
| The system shall track all accountable property, non-accountable property (parts and consumables), and Heritage assets in separate but linked modules. |
| 5.02 |
| The system shall satisfy required regulations including but not limited to Federal Financial Management Improvement Act (FFMIA), OMB guidelines, and DHS and CBP Enterprise Architecture and Cybersecurity requirements including FIPS 199 and FIPS 200. |
| 5.03 |
| The system shall interface with the financial system of record (SAP) and other internal CBP and DHS systems including but not limited to Firearms, Armor, and Credential Tracking System (FACTS), TRIRIGA, and Remedy. |
| 5.04 |
| The system shall interface with external systems as required to perform asset management activities (e.g., GSA's screening and reutilization systems and the DHS CAPSIS platform) |
| 5.05 |
| The system shall support automated forms and workflows for asset management processes (acquisitions, work orders, deferred maintenance, LDDS events, asset disposals, etc.) with the ability to attach supporting documentation (PO/PR, buy sheets, CBP Form 52, etc.). |
| 5.06 |
| The system shall generate automated forms including but not limited to work order tickets, hand receipts, maintenance forms, and disposal forms based on predetermined thresholds or metrics. |
| 5.07 |
| The system shall support barcode scanning technology to perform actions including but not limited to count inventory, add/edit quantity, track new items, and track location. |
| 5.08 |
| The system shall allow CBP to add automated inventory technologies (such as QR or RFID tags) as they are fielded by CBP. |
| 5.09 |
| The system shall generate barcode labels to a designated barcode printer. |
| 5.10 |
| The system shall assign unique identifiers to new documents (purchase orders, work order tickets, etc.) that are automated or uploaded into the system. |
| 5.11 |
| The system shall send users automated email alerts with attachments based on workflows including but not limited to when a reorder point is reached, when a new report is ready with the report attached, or when maintenance is overdue. |
| 5.12 |
| The system shall maintain a version history and full record with time/date stamp for all asset and applicable maintenance records including but not limited to nomenclature, class of asset, item identification, relationship with other assets in a class of supply, bill of materials relationship, serial number, lot number, warranty information, specific handling or security information, total assets in the field, asset condition, status, final level of repair, cost, locations, and summary data. |
| 5.13 |
| The system shall be accessible through the internet via all modern web browsers (plus previous 2 versions of each) and use security features such as PIV card access protocols. |
| 5.14 |
| The system shall allow or limit user access and assign roles based on user access groups. |
| 5.15 |
| The system shall run on mobile devices such as tablets and allow for data access, entry, and reporting. |
| 5.16 |
| The system shall display help buttons that provide standard operating procedures (SOP), training manuals, Service Bulletins, and Airworthiness Directives for specific modules, workflows, or functions. |
| 5.17 |
| The system shall allow records to be modified without requiring users to delete and restart record creation process. |
| 5.18 |
| The systems shall allow users to run searches and partial wildcard searches on any field. |
| 5.19 |
| The system shall support a secure stand-alone/offline capability maintaining some key functionality in the event of network outages. |
| 5.20 |
| The system shall provide the ability, for users with appropriate access, to add or edit data fields to asset records. |
| 5.21 |
| The system shall provide the ability to tailor the user experience. |
| 5.22 |
| The system shall be structured to be compliant with Section 508 of the Rehabilitations Act. |
| 5.23 |
| The system shall integrate with existing enterprise productivity suite, such as but not limited to Microsoft Office. |
| 5.24 |
| The system shall provide a vendor portal that is web-enabled, accessible from non- CBP network machines, and having a “zero client footprint” architecture that requires no locally loaded applications, help files, executables, database software, or non-standard web plugins. |
| 5.25 |
| The system shall operate in an environment where multiple other applications/software are in use. |
| 5.26 |
| The system shall allow all added and modified records to be written to a separate transactional database and fully accessible by National Maintenance Contract (NMC) administrators. |
| 5.27 |
| The system shall support mobility planning for both maintenance events and operational deployments; enable the creation and maintenance of tailorable, capability-specific deployment supply/equipment listings. |
| 5.28 |
| The system shall provide "average cost" of items value. The System must account for the money that is not placed in the average cost of a unit because excess money was not divisible by the quantity. |
Attachment A – CAMS Scenarios: Scenarios that the CAMS system will support are provided. Respondents are encouraged to consider these scenarios when providing responses to Items 1 and 2.
CAMS Scenarios A scenario is used to illustrate CBP personnel’s[footnoteRef:1] day-to-day asset management activities, what challenges they face when working in an asset management system, and how a new capability will mitigate these challenges. The six CAMS scenarios below break out six distinct user groups that regularly interact with CBP asset management systems. The scenarios were determined by reviewing CBP asset management activities to identify who was interacting with the CBP asset management systems and why. To gather information on how different users interact with CBP asset management systems, stakeholder interviews on the interaction between CBP personnel and the various CBP asset management systems were conducted across the CBP enterprise. A description of each scenario can be found below: [1: CBP Personnel: CBP mission operators who report asset information and cleanse asset data. ]
· CAMS Operational Scenario – Procurement personnel [footnoteRef:2]who add CBP asset management data into a CBP asset management system. [2: Procurement Personnel: CBP personnel who input asset data into the CAMS system.]
· CAMS Maintenance Scenario – CBP maintainers[footnoteRef:3] who maintain CBP assets and the assets’ maintenance records. [3: CBP Maintainers: CBP personnel managing asset maintenance throughout an asset’s lifecycle. ]
· CAMS Reporting Scenario – CBP stakeholders[footnoteRef:4] who track, review, and report CBP asset data. [4: CBP Stakeholders: Enterprise level asset managers, such as, but not limited to Personal Property Program Management Office (PPPMO) managers, Office of Facilities and Asset Management (OFAM) leadership, field office/regional and DC leadership.]
· CAMS Compliance Scenario – CBP personnel who ensure compliance with CBP, DHS, and government wide asset management policies.
· CAMS Financial Management Scenario – CBP personnel who analyze and track asset data to determine the funding needed to support CBP asset management activities.
· CAMS Mission Execution Scenario: CBP personnel who are involved in field activities where asset information is needed to execute their mission.
CAMS Operational Scenario Execution Procurement Personnel: Procurement Personnel involved in this scenario include but are not limited to, Local Property Officers (LPO) In Service Engineering Activities (ISEA), In Service Maintenance Activities (ISMA), Configuration Managers and Field Service Representatives (FSR) Various CBP personnel are involved in executing activities that allow CBP to input and manage asset data. Below is a list of specific activities carried out as part of this scenario:
· Input asset data for inventory reporting in an asset management system and export various inventory reports to analyze the asset records.
· Review inventory reports to identify which asset records have discrepancies, and which ones are ready to be closed out.
· Liaise between CBP stakeholders and procurement personnel in the field to correct, change, or update asset records.
· Complete inventory reports and submit them to CBP stakeholders across the CBP enterprise for awareness and to aid in decision making.
Current CBP Asset Management System Challenges and Potential CBP Asset Management Capabilities Procurement personnel face multiple challenges when working in current CBP asset management systems. Below is a list of challenges procurement personnel currently face when interacting with CBP asset management systems, and potential capabilities CAMS will provide procurement personnel to solve some of the listed challenges.
Current CBP Asset Management System Challenges
· Procurement personnel must export and save asset data to a secondary location to review inventory reports, resulting in missing asset information due to export issues.
· Large amounts of asset data are manually inputted, particularly through free text, which leads to the incorrect categorization of assets.
· Lack of data integration between current system has led to incomplete data records.
Potential CBP Asset Management Capabilities
· CAMS will have the ability to automate the asset recordation process, where able, and to prompt procurement personnel to choose from a data dictionary and pre-populated asset information labels to ensure data accuracy.
· CAMS will have features that detect or prevent the inclusion of incomplete or inaccurate data.
· CAMS will provide uniform inventory reporting templates which will reduce the time spent on creating and analyzing individual reports.
· CAMS will include automated data cleaning processes and quality assurance checks to reduce the amount of manual re-work and data cleaning per asset record.
CAMS Maintenance Scenario Execution CBP Personnel: CBP Personnel involved in this scenario include but are not limited to, CBP Developers, Product Architects, SCRUM Masters, Business Analysts, Asset Managers, Field Operators, and Maintainers.
CBP maintainers perform asset maintenance and input the asset maintenance data into an asset management system creating Maintenance Work Orders (MWO) and other applicable reports. Below is a list of specific activities carried out as part of this scenario:
· Record and manage maintenance performance data for preventative and ongoing maintenance activities.
· Perform quality checks on asset maintenance data before a report is created for CBP stakeholders.
· Create reports and MWOs to ensure assets are at the proper location and are operationally ready for deployment.
Current CBP Asset Management System Challenges and Potential CBP Asset Management Capabilities CBP maintainers face multiple challenges when working in current CBP asset management systems. Below is a list of challenges CBP maintainers currently face when interacting with CBP asset management systems, and potential capabilities CAMS will provide CBP maintainers to solve some of the listed challenges.
Current CBP Asset Management System Challenges
· CBP stakeholders change asset maintenance recordation processes and do not inform or provide guidance to CBP personnel in the field on the required process changes, leading to the development of incomplete or outdated records.
· Some asset data is not being recorded in each asset management system and the data that is being recorded is not always added in a useable format for example, data is recorded manually and scanned in as a PDF. The data is also not being recorded properly due to a lack of tools or CBP maintainers lack the ability to understand and utilize the data.
· Inability to make accurate procurement, sparing, and disposal decisions due to a lack of holistic and accurate data records.
· Current asset management systems rely on standardized reporting templates and do not have the capability to develop ad-hoc or custom reports.
· Some CBP asset management systems do not track asset details down to a granular level to understand why a part might have failed. Without the ability to track specific asset details, decision makers will not be able to identify where future problems might occur.
· Data is entered into an asset management system after the maintenance activity has occurred leading to asset management data that could be incomplete and an asset record that is not as up to date as possible.
Potential CBP Asset Management Capabilities
· CAMS will ensure that asset maintenance reporting guidelines, SOPs, and training are followed as efficiently as possible by developing processes and automating data recordation activities.
· CAMS will provide information necessary to enable repair and reallocation prioritization
· CAMS will reduce labor hours due to the automation of maintenance reporting and will allow CBP personnel to focus on conducting preventative and corrective maintenance to reduce asset downtime.
· CAMS will track consumables to identify how many and what type of assets are not deployable in various locations. This activity will increase asset availability information across the CBP enterprise.
· CAMS will provide actionable asset management data that is necessary for CBP stakeholders to determine spare rates before making asset acquisition and parts sourcing decisions to reallocate resources within mission requirements and budgetary boundaries.
· CAMS will provide the ability to upload bulk data or larger asset management data uploads to reduce the time it takes CBP maintainers to record asset data.
CAMS Reporting Scenario Execution CBP Stakeholders: Program Analysts and CBP Leadership CBP stakeholders pull asset data from an asset management system to conduct quality assurance checks, create reports, and submit the reports to CBP leadership to aid in decision making. Below is a list of specific activities carried out as part of this scenario:
· Track and analyze asset data by reviewing asset records in an asset management system to ensure accurate asset information is readily available.
· Review asset records to determine where an asset is located, why an asset was added to a stations’ property book. how the asset should be removed, the assets condition, the assets requirements, review upcoming disposition turn in/lateral transfers, and what loss reporting is associated with the asset record.
· Develop reports on an ad hoc, monthly, quarterly, and annual basis for CBP leadership and DHS with information on asset readiness and any missing or lost assets.
Current CBP Asset Management System Challenges and Potential CBP Asset Management Capabilities CBP stakeholders face multiple challenges when working in current CBP asset management systems. Below is a list of challenges CBP stakeholders currently face when interacting with CBP asset management systems, and potential capabilities CAMS will provide CBP stakeholders to solve some of the listed challenges.
Current CBP Asset Management System Challenges
· CBP personnel manually input asset data, with no data dictionary, which creates reporting errors as there is no standard asset data naming and categorization.
· Current systems do not allow for an enterprise view of asset leading to poor utilization of existing assets.
· Many CBP offices use paper to actively track assets, the paper is then scanned into a PDF and uploaded to an asset management system, which is not traceable or easily digestible.
· CBP stakeholders spend a large amount of time completing quality assurance activities, controls check, and inputting updated asset information.
Potential CBP Asset Management Capabilities
· CBP stakeholders will have asset visibility of stock items available throughout the CBP enterprise and increased precision tracking of inventory, parts, tools, and consumables.
· CAMS will enable CBP stakeholders to consolidate and organize all CBP asset data and will automatically notify CBP stakeholders when risks are identified.
· CAMS will provide standard asset naming and categorization to allow CBP stakeholders to easily populate asset records, generate reports with less errors, and decrease the amount of time spent on asset data quality checks.
· CAMS will allow CBP stakeholders to track active assets across the CBP enterprise and provide information such as asset status/condition, location, connection to the end item/equipment, ongoing replenishment action, asset risks, ownership, last inventoried date, any changes made to the asset record, etc. to communicate asset mission readiness and provide asset visibility to CBP leadership.
· CAMS will enable advanced analytics for ad hoc analysis required to respond to senior leadership requests, Cost Wise Readiness (CWR) analytics, and requirements determinations. Advanced analytics will pull information from multiple asset management systems, digest/deconflict the asset information, and produce asset management reports that provide a holistic look at CBPs asset management data enterprise wide.
CAMS Compliance Scenario Execution CBP Personnel: LPOs, Local Property Coordinators (LPCs), Local Asset Office (LAOs), Inventory Takers, CBP Leadership, OFAM AC, DHS, and Congress.
CBP personnel input asset inventory data into an asset management system and run inventory reports to monitor each CBP office’s inventory progress and ensure offices remain compliant by completing inventory on time. Below is a list of specific activities carried out as part of this scenario:
· Develop several reports in each asset management system, consolidate all the asset inventory data in one report, then input the final report information in a reporting template sent to the OFAM AC.
· Coordinate with the CBP offices in need of asset inventory reporting support and assist them to complete the inventory report efficiently and adequately.
· Provide assistance, compliance training, and resources for CBP personnel working with asset management data in the field.
· Liaise between Office of Information Technology (OIT) and system owners to identify improvements and track high risk assets.
· Utilize asset data to develop asset management compliance reports required by DHS and congress to demonstrate asset management compliance.
Current CBP Asset Management System Challenges and Potential CBP Asset Management Capabilities CBP personnel face multiple challenges when working in current CBP asset management systems. Below is a list of challenges CBP personnel currently face when interacting with CBP asset management systems, and potential capabilities CAMS will provide CBP personnel to solve some of the listed challenges.
Current CBP Asset Management System Challenges
· The inventory reporting process takes a copious amount of labor hours to complete and to identify the relevant data that needs to be reported to remain compliant.
· The current inventory reporting process requires CBP personnel to request additional/ad hoc information that is not automatically generated in a CBP asset management system, delaying the submission of the inventory reports.
· Inventory reporting templates have been established making it difficult to create ad hoc reports for CBP leadership on asset management compliance throughout the inventory process.
· Specific asset management systems do not share all data necessary to develop all-encompassing asset management reports. This leads to the same data manually being taken from one system and inputting it into another.
Potential CBP Asset Management Capabilities
· CAMS will automate asset management reporting activities, allowing users to manage asset records and satisfy compliance requirements throughout the asset’s lifecycle, reducing risk and incomplete asset records.
· CAMS will provide more accurate asset information in real time, reducing the need for re-work during inventory reporting.
· When CBP receives and/or acquires an asset such as a firearm or hazardous materials, CAMS will properly categorize assets to include asset class, property code, capitalization requirements, potential risk, etc. and will allow users to ensure prescribed requirements are complied with.
CAMS Financial Management Scenario Execution CBP Stakeholders: Financial Program Analysts, Financial Program Manager, and CBP Leadership CBP stakeholders use asset management data to manage program budgets, track each programs spend plans, and identify the financial support CBP will require to maintain and procure CBP assets. Below is a list of specific activities carried out as part of this scenario:
· Input purchase requisitions (PRs) into an asset management system to track CBP program budgets, burn rates, obligation rates, and invoices paid to vendors.
· Complete the entire PR process in an asset management system when CBP procures an asset.
· Review resources expended on procuring and maintaining individual assets per program throughout the funding lifecycle.
· Develop modules and dashboards to provide funding information on program execution, future budget plans, assets per organization, and budget usage.
Current CBP Asset Management System Challenges and Potential CBP Asset Management Capabilities CBP stakeholders face multiple challenges when working in current CBP asset management systems. Below is a list of challenges CBP stakeholders currently face when interacting with CBP asset management systems, and potential capabilities CAMS will provide CBP stakeholders to solve some of the listed challenges.
Current CBP Asset Management System Challenges
· CBP personnel are unable to pull real time asset records after updating or adding an asset information into a CBP asset management system since updates are reflected every 24 hours.
· CBP is unable to provide roll-up cost information for mission assets consisting of components that cross programs.
· Current asset management systems do not provide detailed cost data for CWR efforts or contractual information, and do not associate cost information to specific programs/offices.
Potential CBP Asset Management Capabilities
· The CAMS system will reduce financial planning inefficiencies through automated cost calculations.
· CAMS will include the ability to export data to other systems/programs to sort and filter asset information into a digestible format to expedite purchasing decisions.
· CAMS will access current agency wide spending information in real time, identified in multiple asset management systems, and allow CBP leadership to determine ways to reduce spending during future budget cycles.
· CAMS advanced analytics capabilities will assess current agency wide spending information in real time, identified in multiple asset management system, and allow CBP leadership to determine ways to reduce spending during future budget cycles.
· Accurate costs, at the program level and below, will be captured and utilized to evaluate current performance and inform options if performance is not at the desired level.
CAMS Mission Execution Scenario Execution CBP Personnel: CBP Personnel involved in this scenario include but are not limited to, Border Patrol Agents, Air and Maritime Agents, and Field Operations Officers.
CBP personnel are involved in field activities that require awareness of the number, location, and status of assets needed to execute their mission. Below is a list of specific activities carried out as part of this scenario:
· Plan future missions based on an awareness of what assets are required and available or could be made available either within their sector or from other sectors/areas to support the mission.
· Identify asset requirements by location as well as assets on hand and status, visibility of assets in maintenance and associated repair times, and status of replenishment actions to adjust asset levels by location to maximize the region’s ability to meet all mission requirements and provide higher headquarters with a real time understanding of the region’s readiness.
· Access asset information regarding asset status and location, as well as costs, to make critical decisions on procurement, sparing, repositioning, and disposal to support all CBP’s missions with limited resources and track CBP mission readiness Current CBP Asset Management System Challenges and Potential CBP Asset Management Capabilities CBP personnel face multiple challenges when working in current CBP asset management systems. Below is a list of challenges CBP personnel currently face when interacting with CBP asset management systems, and potential capabilities CAMS will provide CBP personnel to solve some of the listed challenges.
Current CBP Asset Management System Challenges
· There is no “single system” that provides visibility of asset information at any level.
· Personnel are required to collect asset information through multiple sources (systems and interviews) and then capture and update this information in another system with limited access, if any, by other personnel.
· Leadership, at all levels, is unable to optimize mission and resource planning because of an inability to access/view existing resources and status, planned procurements and disposals, and by an inability to reallocate resources among components, regions, or sectors without additional cumbersome manual research.
Potential CBP Asset Management Capabilities
· CAMS will provide the required asset visibility, at all levels, for leadership to quickly make informed logistics and sustainment decisions that optimize asset availability at best cost and increase the likelihood of mission success.
· CAMS will provide the ability, with leadership approval, to seamlessly relocate assets across the CBP enterprise according to mission need.
· CAMS will provide visibility of assets across the CBP enterprise to assist mission planners and help ensure optimal allocation of resources to match enterprise-wide requirements.
· CAMS will provide operations personnel an enterprise perspective with sufficient drill-down capability to an individual stations’ asset status. This enterprise perspective provides operational decision makers at the station, sector, and Joint/Combined levels the ability to quickly make data-based mission support decisions which are logistically supportable and detail asset capability and costs.
File details come from the government source that posted it. Updated .