SOURCES SOUGHT
99 -- Program Executive Office Command Control Communications-Tactical (PEO C3T) Project Manager Mission Command (PM MC) Multi-form Collaboration Capabilities
- Notice Date
- 7/7/2023 8:45:54 AM
- Notice Type
- Sources Sought
- Contracting Office
- USA PEO, COMMAND CONTROL AND COMMUN ABERDEEN PROVING GROU MD 21005-1846 USA
- ZIP Code
- 21005-1846
- Solicitation Number
- PEO_C3T_MC_0707JUL-Collaboration
- Response Due
- 7/28/2023 2:00:00 PM
- Archive Date
- 12/20/2023
- Point of Contact
- Virginia Pippen
- E-Mail Address
-
virginia.a.pippen.civ@army.mil
(virginia.a.pippen.civ@army.mil)
- Description
- Requested Information Program Executive Office Command Control Communications-Tactical (PEO C3T) Project Manager Mission Command (PM MC) Purpose This Request for Information (RFI) is issued by Project Manager Mission Command to provide the United States (U.S.) Army industry feedback on multi-form collaboration capabilities that may provide a solution for the next generation Mission Command system. The Government (Project Manager Mission Command) is requesting interested sources to provide information in the form of a white paper, capability briefing, or product description materials which demonstrates the capability to meet the requirements described within this RFI. Information shall be submitted electronically and shall not exceed 20 pages for all items associated with the RFI response. Responses should include a completed Self-Assessment Checklist (Enclosure A) indicating which requirements the proposed solution is capable of fulfilling. This is a RFI only. This RFI shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. There is no obligation on the part of the Government to acquire any products or services described in this RFI or its responses. Responses to this RFI will be treated only as information for the Government to consider. There is no payment for direct or indirect costs that are incurred in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government will not pay for the information submitted in response to this RFI. Generic capability statements will not be considered. Responses must address capabilities specific to this RFI. Request that End User License Agreements be submitted for any commercial software offered in response to this RFI to include those terms and conditions of third parties for which the government must comply in order to ensure proper use of any software. References to hyperlinks either as a method of submission, or within the documentation, is not considered acceptable. If commercial software is offered as part of the RFI response, please indicate which current, active government contracts are available for procurement of licenses or procurement of source code outright. If commercial software is offered but not available under active government contracts, provide the following in table format for each licensable component: Name of Software Date of First Version Date of End Date of Availability End of Extended Support for Security Date for Availability of Sale������� General Support Updates Available? (Y/N) Is software proprietary/commercial or open source software? If open source, how is the life cycle support provided? Available pricing information for each item required to procure and support the software over its life cycle. If pricing is not available for out-years, annotate and estimate based on past pricing. Requirement Project Manager Mission Command is seeking a software solution that enables multi-form collaboration amongst U.S. forces and Unified Action Partners within the tactical, operational, and/or strategic community of interest. Commanders want the ability share and communicate with other commanders in a mixed environment. Multi-form Collaboration will enable the sharing of ideas and communication amongst multiple participants, locally and geographically dispersed, and promote situational understanding between superiors, subordinates, and peers in the form of sketching, highlighting, verbal interaction, and gesturing through voice, text, chat, data, video, white boarding, map boarding, messages, and shared applications throughout the planning and execution processes. Project Manager Mission Command is currently fielding the Command Post Computing Environment (CPCE) system to units across the Army from Battalion, Brigade, Division, Corps, and Army Service Component Command (ASCC).� CPCE provides an integrated fused common operational picture, command and control capabilities and planning tools.� Throughout the operations process, commanders, subordinate commanders, staffs, and unified action partners actively collaborate to share and question information, perceptions, and ideas to better understand situations, synchronize activities and make decisions. Collaborating horizontally and vertically within the Joint Task Force (JTF) enhances shared understanding of the environment, clarifies intent, improves planning and decision-making, and supports detailed coordination. Different operational perspectives and understanding collaboratively combined with operational assessments yield a holistic understanding of the Operational Environment. Operational Capability Statements Collaboration Tools Provide a consistent implementation of software-based tools that enables collaboration between Commanders, Leaders and Soldiers using disparate MC and Intelligence systems across all phases of Joint operations. These tools collectively allow users to share ideas and situational understanding between superiors, subordinates, and peers via sketching, highlighting, talking, listening, and gesturing through voice, text, chat, data, streaming video, white boarding, map boarding, messaging, and shared applications throughout the planning and execution process.� Collaboration tools should allow users to create rich information visualizations to facilitate thinking and communicating about a problem on the fly. Provide a capability to support shift change briefs, Battle Update Briefs (BUB), Command Update Briefs (CUB), After Action Reviews, Rehearsals and the Mission Planning Process (e.g. Running Estimates, Mission Analysis, Course of Action (COA), COA Decision, and Plans/Orders briefings). Provide a white boarding capability to enable multi-form collaboration including free-form sketching, editing, co-editing and enrichment of information within the shared workspace, during briefings, and when sharing applications and displays. Provide a File Viewer application that supports importing, exporting, Create, Read, Update, Delete (CRUD), and two way sharing of office-type Documents (images, textual documents, slides, tables/spreadsheets) across echelons.� This application shall also be integrated into the briefing tool and permit the ability for white boarding and highlighting on top of products shared via the File Viewer. Provide Highlighting capability throughout the shared workspace. Provide web conferencing capability with displays synchronized with talking, listening, & gesturing through voice and bi-directional video capability. Provide Text & Chat capability. Provide Collaborative Data Sharing capability to include video feeds. Provide Map Boarding capability. Shared Workspace A virtual environment in which two or more people can contribute to an effort by sharing ideas, collaborating, and/or editing products together, through the support of computer applications and collaboration tools within a network. Participants are able to see what others are working on, while communicating and collaborating on ideas in near real-time. Enables users to manage data and files located on servers within and between Command Posts and provides the ability for users to simultaneously create, read, update, delete, query, process, synchronize, disseminate and share, log, archive, backup, and recover work products as documents, charts, spreadsheets, overlays, information sources, alerts, briefings, and specialized visualizations of information. Enables users to share their workspace (desktop or applications within) with others while having a shared and simultaneous capability to sketch, highlight, pen on top of the display while simultaneously communicating via voice, video, and chat synchronized with user sketching, highlighting and drawing functions. � On demand, the shared workspace capability and collaboration sessions shall be continuously persisted, recorded and indexed while active and, when completed, are backed up and/or archived and available to restore and query at user demand.� The shared workspace shall permit the sharing of automated tactical alerts and notifications, consisting of both an audible and visual indication, that trigger Command Post Battle Drills that can be collaboratively executed based on unit Standard ��������Operating Procedures (SOP). The Shared Workspace shall support concepts of voice gesturing, collaboration session and briefing owner, transitioning controls and presenters, managing participants, displaying and sharing workspace products including files, products, workspaces, layers, and bookmarks with a capability for participants to white board, highlight and sketch on information shared during a collaboration session and briefing. Provide collaborative sharing and synchronization of applications, application states and displays. View sharing should start in �WYSIWIS� (What You See Is What I See) mode and should allow each user to switch to an individual display where they can change their own view (e.g., map zoom, table scroll, time range); information shown is still shared (and updated if any collaborating user changes, adds or removes items). Collaboration sessions in shared workspaces shall be visible and discoverable.� Scalability Enables collaboration over tactical networks, Satellite Communications (SATCOM) and Tactical Radio, within and between Army Command Posts from Army Service Component Command (ASCC) to Battalion echelons. The solution should offer acceptable performance on a network that is potentially latent, not lossless (packet loss), and subject to jitter. Collaboration at each echelon is required with higher headquarters (HQ), subordinate units, with adjacent nodes and within the Headquarters of each echelon between the MAIN, Tactical, and Rear Command Posts.� This equates to an ASCC and a Corp HQ collaborating with up to 20 external nodes (a node is another HQ or CP equipped with a CPCE server), a Division HQ and Brigade HQ collaborating with up to 15 external nodes, and a Battalion collaborating with up to five external nodes. Multiple collaboration sessions could occur at the same time; initial capability is to be able to support three collaboration sessions at one time.� Each session could require the number of nodes specified above to be involved. Other Enabling Requirements Provide collaborative means to receive, display, share, develop, enrich, review, and approve Operational Graphics. Provide ability to monitor and display the status of collaborative services including application status, performance and application logs. Provided ability to notify users when network conditions impact collaboration between nodes and provide an intuitive means for users to restrict/reduce services/applications, sessions, shared workspace, and connections to external node functions to maintain minimum viable collaboration capability. Provide for permissions management and implementation to support concepts of general purpose user, system administrators, knowledge managers and elevated permissions for collaboration managers. The system applications shall operate over wired and wireless networks. The capability shall show the ability to function in degraded environments. Additional Response Information In addition, in a separate file please provide capability statements that satisfy the requirements defined below: Company Profile: Describe what is your company�s core business? Please include the following: company name, company address, points-of- contact information including name, phone number, e-mail address, number of employees, annual revenue history, office location, CAGE code, DUNS number, NAICS code(s), and current business size status under contracts. Corporate Experience: Prior/current United States Department of Defense (DoD) and/or foreign defense department corporate experience performing efforts of similar size and scope within the last three years, including contract number, organization supported, indication of whether as a prime or subcontractor, contract value, Government point of contact, and a brief description of the specific task areas in the referenced contract as it relates to the services described herein. Please indicate whether you have a Communications Security (COMSEC) Account and specific experience managing COMSEC, Controlled Cryptographic Items, and classified equipment. Capabilities: Describe experience and capabilities in regard to your company's ability to manage DoD tasks of this nature and size. Please provide a narrative to address the following: Post-Production Software Support & System Engineering Expertise.� Must provide post-production software support and deployment software support to include: System engineering software development, software upgrades, testing, integration, training and help desk support for legacy and new software components. Security Requirements.� The contractor will be required to have at a minimum, a Secret Security Clearance for all personnel with exception to administrative support personnel. The contractor shall also be required to have at a minimum, a Secret Facility Clearance, and Secret Safeguarding. Interactive Electronic Technical Manuals and Interactive Multimedia Instruction.� Describe your experience with developing and updating Army technical manuals, quick reference guides, Interface Design Documents, Interface Control Documents, Interface guides, Operator guides, and Web-based/Computer based trainers for software systems in accordance with to the latest Military Standards and Army Regulations. Cybersecurity.� Describe your company�s experience with Risk Management Framework accreditations, Information Assurance Vulnerability Alert updates and Security Technical Implementation Guides. Submission of Responses. ��Responses shall be submitted no later than 1700 hrs. EST on 28 Jul 2023� �All questions and responses shall be submitted via Microsoft Word and emailed to virginia.a.pippen.civ@army.mil. �� Additional Discussions: The Government may choose to reach out to select respondents for additional discussions as a result of this RFI.� Such discussions would only be used to obtain additional information as part of market research effort. Questions: Questions regarding this RFI shall be submitted in writing by email to the contacts listed above.� Questions must be submitted 1700 on 12 Jul 2023.� The Government does not guarantee that questions received after1700 on 12 Jul 2023 will be answered. Disclaimer: This RFI is issued solely for information and planning purposes.� This RFI is not a solicitation and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract.� Responses will not be considered as proposals, nor will any award be made as a result of this request.� Federal Acquisition Regulation (FAR) clause 52.215-3, �Request for Information or Solicitation for Planning Purposes�, is incorporated by reference.� The Government does not intend to reimburse respondents for any costs associated with the submissions of their responses to this RFI; respondents to this RFI are solely responsible for all expenses associated with responding. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in response to this RFI that is marked �Proprietary� will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed.� In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.� Responses from this RFI will be used to formatively shape broad Army guidance for acquiring software solutions.� Response content may be aggregated and anonymously published into summary documentation to facilitate such guidance.� Any publications resulting from this RFI will be non-attributional, and RFI respondents� consent for their responses to be used for such purposes.
- Web Link
-
SAM.gov Permalink
(https://sam.gov/opp/2fdb25ffe4164cbd91b90b2434eb0a60/view)
- Place of Performance
- Address: Aberdeen Proving Ground, MD 21005, USA
- Zip Code: 21005
- Country: USA
- Zip Code: 21005
- Record
- SN06741155-F 20230709/230707230047 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |