Loren Data's SAM Daily™

FBO DAILY ISSUE OF JULY 27, 2011 FBO #3532
DOCUMENT

D -- Request for Information - Construction Battalion Center Micro Supply (CBCMS), Commercial-Off-The-Shelf application - Attachment

Notice Date

7/25/2011
 

Notice Type

Attachment
 

NAICS

541614 — Process, Physical Distribution, and Logistics Consulting Services
 

Contracting Office

N62583 SPECIALTY CENTER ACQUISITIONS NAVFAC 1100 23rd Ave Bldg 1100 Port Hueneme, CA
 

Solicitation Number

N6258311CBCMS
 

Response Due

9/3/2011
 

Archive Date

9/18/2011
 

Point of Contact

Debra Buckley, 805-982-3993
 

E-Mail Address

debra.buckley@navy.mil
(debra.buckley@navy.mil)
 

Small Business Set-Aside

N/A
 

Description

STRATEGY AND INSTRUCTIONS: This Request for Information (RFI) is for informational and planning purposes only and shall not be construed as a Request for Proposal (RFP), Request for Quote (RFQ) or as an obligation on the part of the Government. The Government does not intend to award a contract on the basis of this request or otherwise pay for the requested information. Naval Facilities (NAVFAC) is requesting information to procure a Commercial-Off-The-Shelf (COTS) application, fully hosted by NAVFAC, that supports warehouse operations. Capabilities sought include: total life cycle management and tracking of: Containerization, Component Shipment Packing, Unpack and Physical Inventory as well as support for program management level planning, programming, budgeting and execution (PPBE) through all future year defense plan (FYDP) cycles. This RFI is intended to solicit vendors to conduct a œself-assessment  of their application ™s ability to satisfy the functionalities desired as listed below in the Functionality Desired section, conduct an on-site system demonstration at Naval Facilities Expeditionary Logistics Center (NFELC) in Port Hueneme, CA to validate their capabilities, present an oral presentation and submit a rough cost estimate covering initial planning through on-going sustainment. NAVFAC is requesting all respondents use Attachment (1) to rate their system capabilities to satisfy the requirements. If the respondent ™s system requires software changes in order to satisfy requirements, please submit a rough cost estimate identifying what that cost would be. This RFI is looking for a rough cost estimate (over a 3 year period) for procurement, implementation and operations & maintenance of an enterprise application that has been described in this RFI. NAVFAC is requesting each respondent fill out Attachment (2) with their cost estimates. Please email your responses to this RFI including Attachment (1) and (2) by 3 September 2011 to the following NAVFAC point of contact: Ms. Debra Buckley, Contract Specialist, email: debra.buckley@navy.mil. Please submit all questions regarding this RFI and Attachments (1) and (2) to Ms. Buckley by 12 August 2011. NAVFAC is requesting all respondents conduct a system demonstration during the week of 26 “ 30 September 2011. The system demonstration will be limited to 2 hours. In addition to conducting a system demonstration, respondents are invited to prepare an oral brief presenting the following: Implementation and Sustainability Methodology: Corporate Experience: Past Performance The oral presentation shall be limited to 1 hour followed with a ฝ hour break to setup for the system demonstration which will be limited to 2 hours. Each respondent will be limited to no more than 4 individuals from their company attending and participating in the system demonstration and oral presentation. All participants will be required to provide necessary information and complete necessary documentation in order to request base access. Respondents must contact Ms. Debra Buckley, Contract Specialist, email: debra.buckley@navy.mil no later than 12 September 2011 to schedule their presentation and demonstration. FUNCTIONALITY DESIRED: Functionality is described as generically as possible to aid in the comparison to other systems and / or business processes. The following paragraphs describe the functionality provided by the current system and what is desired in a replacement system. Additional detailed functional requirements are listed in Attachment (1), Functionality and Capability Matrix. 1)Requirements Management A TOA is developed for each Advance Base Functional Component (ABFC). TOAs provide a comprehensive list of National Stock Number (NSN) requirements needed to manage and deploy a component. A hierarchical grouping is required to organize a TOA. One or more NSNs are used to make up an assembly or Equipment Code (EC) requirement. Assemblies and ECs are arranged together to form Facilities or Groups. Sections are used to identify the type of category for all material and equipment; i.e. weapons, communications equipment, civil engineer support equipment. Components, sub-components and stand-alone components are used to identify a major configuration of personnel and material for a specific level of operation or mobilization. a)Documentation of changes (configuration management) is necessary within the TOA system. Significant changes to a TOA will dictate the need to save or copy a specific TOA version for historical purposes. Allowance items, replaced within the TOA, need to be identified for acceptable substitution. Attributes of a TOA and its parts are required to be identified within the system. Size and unit characteristics are identified for purposes of packing / containerization and shipping / mobilization. b)NFELC manages changes to the TOAs centrally for the NECC and other expeditionary forces. Headquarters, deployed units and expeditionary forces require access to the TOA's and their changes. The capability of putting TOA changes in the hands of deployed units and those managing packed or containerized assets will allow TOA Integrated Logistics Overhaul (ILO) at the field level. c)Container Management and Kitting and packing of NSNs into assemblies and the containerization of material accountability also require maintenance during issue, pack and storage. AIT capabilities and bar coding are required to track material accountability during issue, receipt into the pack area, packing into boxes and stowing into containers. Inventory is maintained for the material assets. Issue control by customer, warehouse, priority and project. NAVSUP Management reports capability: Inventory Control Effectiveness (ICE), 1144. d)Physical Inventory reporting is required for all material. Location audits, key item and wall-to-wall inventories are conducted in accordance with the following NAVSUP policies and procedures: NAVSUP Publication 485 “ Volume I, II and III Ashore Supply Procedures NAVSUP Publication 723 “ Navy Inventory Integrity Procedures DOD 4140.27-M “ Shelf Life Management Manual Physical Inventory requirements include: Specific Locations or Location Ranges Specific NIINs or NIIN Ranges Hazardous Materials (HAZMAT) Controlled Item Identification Codes (CIIC) Cognizance Symbol (Cog) Shelf Life Codes (SLC) Shelf Life Action Codes (SLAC) Use of bar code technology is integrated to allow ease of data collection to perform inventory activities. e)Handheld Scanner Hardware is required to gather material asset information and interface with a Navy-Marine Corps Intranet (NMCI) workstation to update the CBCMS database. f)Bar Code Label Printers are required to print out labels such as box IDs and packing aids through CBCMS. 2)Products, Services & Interfaces Products, services and interfaces of CBCMS required to efficiently support the NECC ™s and expeditionary forces ™ business practices include: a)Integrated Logistics Overhaul (ILO) - Provides for the modernizing and replacing of deployed, stored and containerized material assets. Replacing and overhaul of old equipment assets with current TOA requirements. b)Component Shipments Packing - Provides the ability to tailor and extract specified requirements at the component, sub-component, facility, group or assembly level from a master and / or proposed file in one request, specify level of pack, generate and process system requisitions, generate and process free issue requisitions from store rooms, track shorts, produce reports, conduct prescreen against multiple store rooms in one request and feed data to micro systems for packing. Maintain status based on data fed back from micro systems. Including a Multi-Line Item Packing ability i.e. UL / SG / Kitting. c)Containerization - Provides the ability to plan, pack, track and re-pack containerized material. Use of Automated Identification Technology (AIT) during packing for purposes of asset management. d)Other System Interface - Providing the ability to interface with standard Navy, Other Service and DOD system applications for logistics support as well as interfacing with handheld scanner hardware for data collection and bar code label printers for creating tracking information. The interfaces also include but are not limited to the following DOD system: EXMIS. e)Users - DOD IA/IT REQUIREMENTS The NAVFAC Information Assurance (IA) Program is a unified approach to protecting unclassified, sensitive or classified information, and is established to consolidate and focus efforts in securing that information, including its associated systems and resources. IA is required operationally throughout the Department of Navy (DoN). The DoN Chief Information Officer (CIO) is responsible for Information Technology (IT) within the Navy, as mandated by the Clinger-Cohen Act and is the lead for departmental compliance with the Federal Information Security Management Act of 2002 (FISMA). NAVFAC seeks a solution with the following IA aspects: Ability to login using either a user ID/password or DoD Common Access Card (CAC). Documents containing personally identifiable information (PII) or data (per the Privacy Act of 1974) or that are marked with a security classification such as For Official Use Only (FOUO), need to be flagged or otherwise distinguished from other documents. Documentation on how the product can run in a virtualized environment. A security features ™ guide for users and a separate security guide for system administrators. Ability to mark groups of documents which, when combined, might result in unintentional disclosure of classified information (and then restrict access to them).
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVFAC/N47408/N6258311CBCMS/listing.html)
 

Document(s)

Attachment
 

File Name: N6258311CBCMS_CBCMS_RFI_7_18_2011.pdf (https://www.neco.navy.mil/synopsis_file/N6258311CBCMS_CBCMS_RFI_7_18_2011.pdf)

Link: https://www.neco.navy.mil/synopsis_file/N6258311CBCMS_CBCMS_RFI_7_18_2011.pdf

 

File Name: N6258311CBCMS_Attachment_1_-_CBCMS_Functionality_and_Capability_Matrix_-_6-8-2011.docx (https://www.neco.navy.mil/synopsis_file/N6258311CBCMS_Attachment_1_-_CBCMS_Functionality_and_Capability_Matrix_-_6-8-2011.docx)

Link: https://www.neco.navy.mil/synopsis_file/N6258311CBCMS_Attachment_1_-_CBCMS_Functionality_and_Capability_Matrix_-_6-8-2011.docx

 

File Name: N6258311CBCMS_Attachment_2_-_CBCMS_Cost_Template_-_6-8-2011.xls (https://www.neco.navy.mil/synopsis_file/N6258311CBCMS_Attachment_2_-_CBCMS_Cost_Template_-_6-8-2011.xls)

Link: https://www.neco.navy.mil/synopsis_file/N6258311CBCMS_Attachment_2_-_CBCMS_Cost_Template_-_6-8-2011.xls

 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN02508871-W 20110727/110725234245-736aed4e55c23d9752bdd58099a7f659 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |