NextGen Federal Systems’ Post

Thanks John for posting this- For future vendors-to demonstrate understanding of the project requirements and showcase how your company can meet those requirements effectively. Here are some key steps to outline your capabilities and experience: 1. Introduction: - Provide a brief overview of your company, including its background, expertise, and relevant industry experience. - Highlight your company's commitment to supporting JTIC2S and the Advanced Field Artillery Tactical Data System Artillery Execution Suite. 2. Relevant Experience: - Describe any previous projects or contracts that demonstrate your company's experience in developing and delivering similar command and control systems or mission command systems. - Highlight specific accomplishments, successes, and lessons learned from those projects. - Emphasize any experience working with fire support systems or artillery execution suites. 3. Technical Expertise: - Outline your company's technical capabilities and expertise relevant to the requirements of JTIC2S and the Advanced Field Artillery Tactical Data System Artillery Execution Suite. - Highlight any specialized knowledge, certifications, or technologies that set your company apart. - Provide details on the software development methodologies and technologies your company utilizes. 4. Team Composition: - Introduce key members of your team who will be involved in supporting the project. - Highlight their relevant experience, qualifications, and areas of expertise. - Emphasize any team members' previous experience with similar systems or projects. 5. Approach and Methodology: - Explain your company's approach to supporting JTIC2S and the Advanced Field Artillery Tactical Data System Artillery Execution Suite. - Describe how you will collaborate with the PEO C3T and other vendors to ensure seamless integration and successful delivery. - Highlight any unique methodologies, best practices, or tools that your company will utilize. 6. Innovation and Differentiation: - Showcase any innovative features, technologies, or approaches that your company can bring to the project. - Emphasize how these innovations can enhance the capabilities and performance of JTIC2S and the Advanced Field Artillery Tactical Data System Artillery Execution Suite. - Demonstrate how your company's unique value proposition aligns with the project's objectives. 7. Past Performance and References: - Provide references from previous clients or partners who can vouch for your company's capabilities and performance. - Include testimonials or case studies that highlight successful projects or implementations. Remember to align your capabilities and experience with the specific requirements and objectives of JTIC2S and the Advanced Field Artillery Tactical Data System Artillery Execution Suite. Tailor your proposal to showcase how your company's strengths and expertise can contribute to the success of the project.

U. S. Central Command (USCENTCOM) transitions to digital warfighting tools based on live data feeds, according to Brig. Gen. John Cogbill and Schuyler Moore. Learn more: https://lnkd.in/gU53_uMF #GovernmentTechnology

U. S. Central Command (USCENTCOM) transitions to digital warfighting tools based on live data feeds, according to Brig. Gen. John Cogbill and Schuyler Moore. Learn more: https://lnkd.in/gU53_uMF #GovernmentTechnology

Modernisation Effort: US Army Planning to Move to Multi-Vendor Approach Historically, “a very small number of industry” has been involved in the Advanced Field Artillery Tactical Data System (AFATDS), the Army’s main command and control system, because “it’s very complicated, it’s very niche,” Mark Kitz, program executive officer for command, control, communications-tactical (PEO C3T) said. Read More : https://buff.ly/3PTgpoP #USArmy #ModernisationEffort #MultiVendorApproach #AFATDS #CommandAndControl #defence #DataExchange #SoftwareDevelopment #IndustryVendors #Leidos #RequestForInformation #TechnicalExchangeMeeting #SystemIntegration #SoftwareModernization #DataManagement #MilitaryTechnology #rakshaanirveda

To add to that new way of thinking, this multi-vendor development approach should take advantage of that fact that those specific PEOs fires products as will as other PEO products should be using common SW frameworks and libraries. This is equivalent to MOSA for HW products to support plug and play and drive data and interface stds. For example, one PEO, or Army org, could take responsibility to implement a .dll (Windows) or .so (Linux) library for tactical data links (CoT, USMTF, VMF) and Army acquision programs, M&S, training communities all leverage for their need. Another example, one PEO, or Army org, could take responsibility to implement a common SW framework that provides an underlying data model that can be extended (NATOs MIM), 2D/3D view, map elevation and overlays ingest on a composeable and extendable architecture with dynamic API. This would allow the same communities mentioned above to start development and just focus on their specific need by extending the data model and creating plugins for needed capability features. In today's world these common things are built time and time again leading to interoperability and compatibility issues.

FIRES RFI RELEASE: The Army released a request for information (RFI) today for interested parties to respond with feedback on a multi-vendor approach for the development of modern digital fires products housed in the PEO C3T Product Manager Fire Support Command and Control (FSC2). This new consortium-like approach will allow multiple vendors to have opportunities to potentially participate in the modernization of the Advanced Field Artillery Tactical Data System (AFATDS) and the Joint Targeting Command and Coordination Suite (JTIC2S). #army2040 #armynetwork #army2030 #ArmyTransformation

Whenever I read something from Rémy Fannader, I always feel like I'm "drinking from a fire hose"! I'm currently on page 35 of his book, "Enterprise Architecture Fundamentals". The link below is a passage on his discussions on the Observation-Orientation-Decision-Action (OODA) Loop. The OODA Loop is a decision-making (DM) paradigm developed in the 1960s by Colonel John Boyd, based on his experience as a fighter pilot and military strategist. I like this quote from Remy: "Its [OODA Loop] renewed relevance for today’s operational DM comes from the correspondence between the seamless integration of IT systems with business processes, and fighter jets’ command and control processes." Indeed, the OODA Loop decision-making concept will have great relevance once (if and when) we close the Business-IT gap to achieve "the seamless integration of IT systems with business processes". https://lnkd.in/eHd8vebz

Navigating the Future of Military Aviation and Mission Management: Explore the transformative impact of Digital Moving Maps in defense. Discover the power of advanced situational awareness and how PlanetObserver's 2D and 3D TerrainData are enhancing civil and military operations. #EarthObservation #PlanetSAT #PlanetDEM #SateliteImagery #3DData #MilitaryTech #Defense https://lnkd.in/e9_MwdVy

Navigating the Future of Military Aviation and Mission Management: Explore the transformative impact of Digital Moving Maps in defense. Discover the power of advanced situational awareness and how PlanetObserver's 2D and 3D TerrainData are enhancing civil and military operations. #EarthObservation #PlanetSAT #PlanetDEM #SateliteImagery #3DData #MilitaryTech #Defense https://lnkd.in/eNDwaNiH

Data Governance is the framework that ensures the reliability, security, and integrity of our data assets. It is about establishing rules, processes, and controls that govern how data is collected, stored, managed, and shared across our enterprise. Just as we uphold discipline, order, and accountability in our military operations, data governance instills discipline and order in how we manage and protect our data resources.