Configuration Management Tool

REQUEST FOR INFORMATION (RFI) United States Marine Corps Configuration Management Tool This notice is a Request for Information (RFI) to obtain market research information from sources capable of satisfying requirements identified herein. Responses from all industry sources are welcome. This market research is for informational purposes only and should not be construed as a commitment of any kind. Responses to this RFI cannot be accepted by the Marine Corps to form a contract. Responders will not be reimbursed for any information received and are encouraged not to provide proprietary data or business sensitive information as any information received may be used by the Government. The Government is primarily focused on seeking a suitable commercial item to meet existing Government requirements. The due date for responses to this RFI is 4:00 pm Virginia local time 12 December 2016. OVERVIEW/BACKGROUND: The Marine Corps Systems Command (MCSC) Global Combat Support System - Marine Corps (GCSS-MC) Logistics Information Systems (LIS) is seeking a Commercial of the Shelf (COTS), Configuration Management (CM) Tool that includes software maintenance, software updates, annual helpdesk support, implementation support and user training. The CM Tool must include capabilities specific to identifying and tracking hardware and software configuration item information, associating change proposals/change requests and files to specific parts and/or software, unique identification tracking, user-generated workflows, to automate the review of documents and/or change proposals/change requests, maintain change history, search/query, ad hoc and canned reporting, document management, program reporting, change proposal and change request form generation to support the five (5) CM functions; Configuration Management Planning and Management, Configuration Identification, Configuration Change Management, Configuration Status Accounting, and Configuration Verification & Audit. The purpose of this RFI is to identify the existence of commercial or non-developmental software with the desired performance characteristics. This RFI is only intended to gather information regarding available performance characteristics and capabilities that currently exist in the commercial market to help define the performance requirement trade space. The desired performance parameters are identified below. In addition, the CM Tool must be Web enabled for general users as well as administrative users utilizing Public Key Infrastructure (PKI) Common Access Card (CAC) verification. The CM Tool must have web interface reporting, the ability to perform bulk import and bulk export to other tools (e.g. Commercial/Government CM Tools, Excel, etc.), and the ability to assign permissions by Program name and to groups, folders, files based on user roles and profiles. In a deployed state, the CM Tool must meet requirements for Assessment and Authorization (A&A) per the DoD Risk Management Framework (RMF) following the SIAT RMF Process Guide. CM Tool vendor must be pro-active in addressing CM Tool security vulnerabilities. Requirements/Performance Parameters: Respondents to this RFI are requested to provide information addressing the following list of desired performance parameters. Respondents are encouraged to report their metrics for each performance parameter even if they do not meet the target metric. For any metric that the respondent does not know, the respondent should state "unknown" and also state if possible, the expected performance (e.g. "Unknown. Expected performance = __________") - 1. Configuration Management Planning and Management. - a. Baseline. Target functionality must: (1) Compare like information, (2) Enter and track the initial approved baselines of Configuration Items (CI) and all proposed/approved changes, associate hardware, software, and associated documents to a specific baseline version, (3) Manage a future baseline (where changes have been approved but not fielded/implemented), and (4) Copy a baseline and re-identify with a new (future) baseline version or name. - b. Software Development. Target functionality must: (1) Track the configuration item during the software development lifecycle (track open problems, fixed problems against specific builds/releases), (2) Produce snapshots of the configured systems at any given point in the Software Development Lifecycle (SDLC), (3) Track a software version to four (4) digits with each digit position having the ability to expand up to three digits. (i.e., 999.999.999.999), (4) distribute software media, (5) licenses and warranties and (6) Associated hardware to software versions. - c. Asset Management of Hardware and Software. Target functionality must (1) Track Operating Systems, Commercial off the Shelf (COTS) and Government off the Shelf (GOTS) Applications, and Hardware level components, (2) Update and record the version number of a CI (parent) if the version number of any component of CI (child) is changed, (3) Provide parts lists information (drawing number, revision, page number, part number, find number, quantity, serial number, manufacturer, cage code, etc.), (4) Provide asset location and the ability to change the location, (5) Provide item unique identifier (IUID) reader input, (6) Provide capability to export required fields into the DoD IUID Registry, (7) Provide the ability to track all DD Form 1423's Contract Data Requirements List (CDRLs) attributes and (8) Track the delivery process from creation to delivery regardless if there are fixed dates or event driven dates. - 2. Configuration Identification. Target functionality must: (1) Provide the ability to uniquely identify each configuration item (Document Number, Revision, Drawing Number, Part Number, Software Version, IUID, etc.) and prevent duplication of any of these unique identifiers, (2) Contain the Configuration Item Description Title and Nomenclature (ex. Assembly, Frame; MK 1 MOD 0; AN/UYK-70), (3) Contain CI parts list information (drawing number, revisions, sheet number, part number, find number, quantity, serial number, manufacturer, cage code, etc.), (4) Contain the CI National Stock Number (NSN), (5) Contain the CI vendor/manufacturer make, model, serial number, part number, cage code, and any additional attributes needed, (6) Contain the CI Vendor/Manufacturer Version/Release, (7) Contain the CI Location/Equipment Reallocation, (8) Contain the CI Where Used, Next Higher Assemblies, and Parts List, (9) Contain the CI Vendor/Manufacturer information (Name, Address, and Contact Information), (10) Contain the CI Warranty Information (Under Warranty "Y/N", Expiration Date), (11) Contain the CI License Information, (12) Contain the CI Cost Information, (13) Contain the CI "Owner" (USMC, Army, Navy, etc.), (14) Contain the CI Notices of Revision (NOR) associated with drawings and documents, (15) Contain the CI Build List, (16) Contain the Bill of Material, (17) Contain the CI Fielded or Site Configuration listing, (18) Contain the CI modification installation/instruction number, and (19) Track the appropriate distribution statements, proprietary marking, and export control for records and reports. - 3. Configuration Change Management. Target functionality must: (1) Provide alerts when CI's change, (2) Provide the ability to enter and track decisions from multiple boards and/or team meetings, (3) Provide the ability to view associated documents/reports to change board and/or team meeting discussions, (4) Provide the ability to view the open and approved changes affecting a particular CI, (5) Provide the ability to assign unique change proposal/request with automated tracking number, (6) Provide the ability to track a change as it progresses through a user-defined workflow using status codes, provide the ability to digitally sign changes, (7) Provide an area for Test/Developer role to generate test incident reports or trouble reports, (8) Promote test problems to software change requests and track status and planned build, (9) Provide the ability to provide conjunctive change relationship (install with, prior, after), (10) Provide the ability to associate software change requests to a specific version, (11) Provide the ability to perform action item tracking on specified workflow states, (12) Provide the ability to produce online agendas and minutes for change boards and team meetings, (13) Provide the ability to identify installation planned and actual dates, (14) Provide the ability to change a document with attached associated documents, (15) Provide the fields associated with an Engineering Change Proposal (ECP) (DD Form 1692) and print, (16) Provide the fields associated with a Request for Variance (RFV) DD Form 1694 and print, (17) Provide a Software Change Request (SCR)/Problem Change Request (PCR) description, priority, probability, solution, and workaround description, date found, change owner, and any additional attributes as needed, (18) Provide the ability to use terms specific to the Program (e.g., SCR vs Software Work Change Request (SWCR), Test Incident Report (TIR) vs Trouble Report (TR), and (19) Provide the ability to track cost associated with an ECP and RFV. - 4. Configuration Status Accounting. Target functionality must: (1) Provide the Status of Change (e.g. approved, in-review, deferred, disapproved, canceled), (2) Provide the ability to relate individual CI's across multiple higher levels CI's, (3) Provide the ability to determine CI relationships through next higher assemblies, parts lists, where used on, and what changes have been approved against the configuration item (change proposal, change request, problem trouble report, variance/deviation/waiver), (4) Provide the ability to associate problems/trouble reports to change requests and change requests to change proposals or variances/deviations/waivers in order to track initial problem to implementation/release, (5) Provide the ability to identify other affected CI, provide the ability to show the hierarchy of relationships between "Parent" Configuration Items and "Child" Configuration Items, and (6) Provide the ability to track the history of a part or software release based on approved changes and RFV/Deviation/Waiver - a. Data Entry and Update. Target functionality must: (1) Provide the ability to add new CI, modify existing CI, and delete CI, (2) Provide the ability to track CI with different model numbers and version numbers, (3) Provide the ability to maintain a history of all CIs; both historical and current version, and (4) Provide the ability to scan CI barcodes. - b. Workflow. Target functionality must: (1) Provide the ability to provide a document review workflow that can be generated without System Administrator assistance, (2) Allow for workflow customization by designated user roles, (3) Provide a workflow that is role based driven allowing for access to view, update, and process items through the workflow. (4) Information shall be displayed only to the user required to view or process the information, (5) Provide the ability to notify users through email of items requiring action (administrative, recurring, user-specified, timeframe), (6) Provide the ability to modify and track status of workflows, (7) Provide the ability to develop workflow templates, (8) Provide the ability to distribute any document, problem report, change request, change proposal or RFV/Deviation/Waiver for community review via an automated workflow, (9) Provide the ability to enter technical assessment/comments in response to a workflow task, (10) Provide the ability to consolidate or display all comments in an readable format in support of a meeting, (11) Provide the ability to track the adjudication of comments in support of meetings, (12) Provide the ability for workflow tasks to be distributed via email to user(s), (12) Provide the ability for the casual users to access a screen/view via a workflow task to review a document, change proposal, change request, problem, trouble report, or similar form, (13) Provide technical assessment/comments with minimal understanding of the tool and (14) Provide the ability to view the workflow process for the system/program they are accessing when requested. - c. Search. Target functionality must: (1) Provide the ability to search for a product, change, or item information, (2) Provide the ability to search by custom fields and tables, (3) Provide the ability to search utilizing at least one wild card character, and (4) Provide the ability to save search criteria for future uses. - d. Repository. Target functionality must: (1) Provide the ability to attach documents to records, (1) Provide the ability to store multiple versions of a document, (2) Provide the ability to associate data with a file(s) (doc title, doc number, revision, date of doc, author, etc.), and (3) Provide the ability to allow for a structured and organized storage of assorted documentation. - e. Custom Fields and Tables. Target functionality must provide the ability to update List of Values (LOVs) by data administrators (or similar role). - f. Record Editing. Target functionality must provide the ability to check-in/check-out editing/changing a document by a single user. - g. Reporting. Target functionality must: (1) Provide the ability to produce agendas/minutes, (2) Provide the ability to produce a parts list breakdown (indentured breakdown), (3) Provide the ability to produce a CI List Report with relationships (Baseline with Hardware and Software) and associated RFV's, (4) Provide the ability to produce a history of configuration items (ECPs, Deviations, Waivers, RFVs, NORs); (5) Provide action and attribute data change history for all stored records, (6) Provide the ability to produce an As Built Listing, (7) Provide the ability to produce an As Delivered Listing, (8) Provide the ability to produce an As Installed Listing, (9) Provide the ability to produce a modification installation status (per serialized CI), (10) Provide the ability to produce future configuration based on approved ECP's, (11) Provide the ability to produce metrics (review cycle, number of open changes, number of board meetings in a given period, etc.), (12) Provide the ability for custom reports with a dashboard view, (13) Provide the ability for ad hoc query reports, (14) Provide the ability for canned queries, (15) Provide the ability to save customizable reports for future use by all users, (16) Provide the ability to export to XLS, CSV, PDF, and TXT, (17) Provide the ability to generate configuration status accounting records, and (18) Provide the ability to capture the periodicity of report generation and to whom they are provided. - 5. Configuration Verification & Audit. - a. Data Validation. Target functionality must: (1) Provide the ability to validate input data, (2) Provide IUID reader input, and (3) Provide a discrepancy/issues report - b. Digital Signatures. Target functionality must provide the ability to digitally sign for approvals for various form types at designated lifecycle states, OTHER INFORMATION: The anticipated North American Industry Classification System (NAICS) code for this effort is 541519. Please include your company's Corporate and Government Entity (CAGE) code and business size. Small business is defined for this purpose as $27.5M or 150 employees for information technology value added resellers. Parties interested in providing information in response to this RFI are invited to provide the following information to assist the Government with its market survey: Introductory Statement that includes at least the following - o Organization Name, Address and Point of Contact information - o DUNS number and CAGE code - o Business size, as determined by the applicable NAICs, and type (i.e., large, foreign, small disadvantaged, veteran owned, minority owned, etc.). Statement of capabilities addressing the Government's potential requirement. Information contained in the capability statement should be pertinent and specific to the Government's requirement, and at a minimum address the following qualifications: (1) Information addressing the above list of desired performance characteristics; (2) Experience: An outline of previous applications sold or licensed to the Government, with an emphasis on applications similar to the above list; (3) Personnel: Amount, availability, experience and qualifications of current employees that will support the application; (4) Facilities: Availability and description of facilities location and availability to support performance; (5) Security: A statement regarding personnel and facility security clearance; (6) Organization structure; (7) Interest level: Include an affirmative statement that they are a [indicate large or small] business and interested in performing as a prime contractor. (This sources RFI is not seeking to identify subcontractors or match subcontractors with prime contractors). Include any other specific and pertinent information as it pertains to the particular supplies to enhance our consideration and evaluation of your company's capability to meet the requirement. Responses should be limited to not more than 10 pages that print as 8 " x 11" for each sheet, and be readable in at least Microsoft Office 2013 and/or Adobe Reader Professional 8. SUBMISSION PROCESS AND DUE DATE: To respond to this RFI, please supply requested information and send via e-mail to: Jessica Baldwin at jessica.baldwin@usmc.mil. The due date for responses to this RFI is 4:00 pm Virginia local time 12 December 2016. NOTE: This RFI is issued for the purpose of determining the capability of sources and does not constitute an Invitation for Bid (IFB), a Request for Proposal (RFP), a Request for Quote (RFQ) or an indication that the Government will contract for any of the items and/or services contained in this notice. No solicitation document exists. Proprietary information should not be provided. Responses may not include classified material. Responses to this notice will not be returned. No reimbursement will be made for any costs to provide information in response to this announcement or any follow-up information requests. Information or statements contained herein are not binding upon the Government.