Transitioning the Army`s Theater Construction Management System
Transcription
Transitioning the Army`s Theater Construction Management System
Transitioning the Army's Theater Construction Management System to the Joint Construction Management System LTC Heather Warden HQDA, Office of the Chief of Engineers Agenda • Army Facilities Component System Overview • Why a Joint Construction Management System • The Joint Operational Engineer Board Work Plan • DoD Defense Initiatives that will Impact JCMS Over Time • Ongoing Transition Work Effort for the JCMS v1.0 Release • Post JCMS v1.0 Release Work Efforts • Discussion/Questions 2 The Army Facilities Components System • Army Regulation (AR) 415-16, Army Facilities Components System, governs the policies, management and use of AFCS • The Chief of Engineers has Army Staff level responsibility for managing AFCS • AFCS provides military engineers a tool to facilitate Theater of Operation (TO) base development planning, facility construction, and construction material acquisition • AFCS designs are based on general conditions and requirements anticipated in the TO and are intended for construction by engineering troops with materials furnished through the Army Supply System • AFCS Consists of – – – – – – Planning Guidance (TM 5-301 series) Designs (TM 5-302 series) Bills of Materials (TM 5-303 series) User Guide (TM 5-304 series) Theater Army Construction Automated Planning System (TACAPS) Theater Orientated Guide Specifications (TOGS) • AFCS provides construction data through web services to JEPES Theater Construction Management System (TCMS) • • TCMS is a standalone application which assists Army Engineers in the development of Theater of Operation projects with AFCS standard facilities and components. The current AFCS design data repository currently contains 1,413 facility designs, 213 component designs, and 5,802 drawings. These numbers include: – Navy: 36 facilities with 95 unique Navy drawings – CENTCOM: 11 components, 137 facilities, and 2,803 unique drawings • Includes Construction Support Data – – – – • Design Drawings (2D, 3D, and Animations) A listing of materials needed for construction Theater Oriented Guide Specifications (TOGS) Labor (MOS) and Equipment (LIN) requirement estimates for construction Microsoft Project Interface capability allowing the war fighter to develop detailed construction schedules for construction execution. 5/30/2012 4 Planning Projects in TCMS Data Organization Project Super Components Components Facilities Sequences 5/30/2012 5 Planning Projects in TCMS Projects Planning Projects in TCMS Projects Planning Projects in TCMS Components Planning Projects in TCMS Facility Planning Projects in TCMS Sequences Planning Projects in TCMS NSN Detail Design • Users have access to the AFCS standard drawings in tables, AFCS drawings associated to each project level (Project, Super Component, Component, Facility, and Construction Sequence), and the ability to attach user developed drawings. • Users can export AFCS standard drawings, modify and site adapt, then attach to their project as a User Drawing. • AFCS standard drawing formats: − 2 Dimensional AutoCAD DWG − BIM 3 Dimensional SoftPlan ZIP (multi-files compressed) − Animations in Microsoft WMV Design TM 5-302-1 -AFCS, Designs -CMU TM 5-302-2 -AFCS, Designs -Metal TM 5-302-3 -AFCS, Designs -Wood TM 5-302-4 -AFCS, Designs -Aviation, Hardstands & Roads TM 5-302-5 -AFCS, Designs -Utilities TM 5-302-6 -AFCS, Designs -Force Protection TM 5-302-7 -AFCS, Designs -Tents & Miscellaneous TM 5-302-8 -AFCS, Designs -Components 5/30/2012 13 Management • Send to Project –creates the mpp file, inserts the resource sheet, project level components, facilities, construction sequences as tasks with their resources, links all tasks, levels the projects, and saves the mpp file. • Receive from Project –opens the project mpp file in the background, extracts percent complete and work balances, closes MS Project, and saves the mpp file in the TCMS Project. Allows users to preview, print, and save all reports. This includes project reports and reports of each AFCS table. Management (Exporting to Microsoft Project) Management (Resource Allocation) Reporting • Allows users to preview, print, and save all reports. This includes project reports and reports of each AFCS table. • Save reports in Word, Excel, PDF, HTML and other formats to customize reporting requirements. • Transmit reports and projects through the chain of command to facilitate the decision making process. • Attach and customized Theater Oriented Guide Specifications (TOGS) to standardize methods for contractor requirements. Reports Theater Oriented Guide Specifications (TOGS) • TOGS are guide specifications tailored for contingency construction that describe the processes, procedures, and construction specifications for materials and or construction sequences. • TOGS when combined with AFCS design drawings provide the basic documents used to perform construction tasks. • TOGS provide technical language and specifications that can be used in construction contracts or construction material acquisition. 5/30/2012 19 Current AFCS Website TCMS Support: Toll Free: (800) 215-2079 E-mail: [email protected] Address: http://www.tcms.net Why a Joint Construction Management System • Experiences in Iraq and Afghanistan highlighted the need to standardize contingency basing standards and designs across the Joint Engineer Community. – The use of multiple standards and designs for similar facilities creates inefficiencies in the use of resources and creates challenges for turning facilities over for contracted operations and maintenance. – Inconsistently applied master planning principles also led to reduced efficiency and effectiveness in contingency bases. • Contingency Basing issues have been raised to the highest levels within the Department of Defense – Life, health and safety concerns were documented in multiple studies and investigations – Efforts to reduce the Operational Energy demand and improve facility sustainability are a high priority • Future operations will require each Service’s Engineers to work together to meet all of the Engineer requirements. The JCMS will provide a single system that all Services can use to plan and execute construction in support of the Joint Force Commanders. 5/30/2012 21 Joint Operational Engineer Board 2012 Work Plan Joint Contingency Construction Standards Problem Statement: Team Members: • A lack of clear Joint Contingency Construction Standards creates inefficiencies in the use of resources and time as well as making facility turnover and O&M more difficult. Master planning principles are inconsistently applied, reducing both efficiency and effectiveness. • Lead Agency: Office of the Chief of Engineers • Supporting: Service Engineers and Schools, COCOM Engineers, USACE Progress Summary: Way Ahead: • Continuing the development of an Automated Joint Construction Management System (JCMS) that: – Contains a Library of Joint Standard Designs for Contingency Facilities and Bases that meet Unified Facilities Criteria (UFC) and other established design and construction requirements – Contains Master Planning Tools to support base planning and design – Is Interoperable with Commercial Software used for construction management and facility design – Is Interoperable with Service Logistics Systems to streamline Bill of Material (BOM) acquisition • Execute JCMS Work Plan Milestones – Complete Standard Design Updates to incorporate UFC and validate design BOMs and labor and equipment estimates – Continue JCMS Software development and finalize data base requirements to ensure interoperability – Finalize the Development of a Master Planning Course and integrate the Master Planning Tool into JCMS • Integrate DoD and Service Operational Energy Initiatives into designs and BOMs • Continue to support USD AT&L’s efforts to further establish contingency basing policies and standards Joint Construction Management System JCMS Master Planning Standard Designs Logistical System Supporting Systems ‐ GIS based ‐ Flexible ‐ Compatible w/ other systems ‐ Common database ‐ Joint and Service standard designs ‐ Direct interface w/ Joint and Service systems ‐ Construction Management ‐ Analysis tools ‐ GeoExPT ‐ VFOB ‐ ABFC ‐ AFCS/TCMS ‐ GCSS‐J ‐ ICIS ‐ JEPES ‐ SALE ‐ SPIDERS ‐ SCM ‐ FIRESTORM ‐ VFOB ABFC – Advance Base Functional Component (USN) AFCS – Army Facilities Component System (USA) SCM – SeaBee Construction Management (USN) FIRESTORM ‐ Facilities, Intelligence, Reconnaissance, Engineering Spatial Tool for Operations and Resource Management (ARCENT) GeoExPT – Geospatial Expeditionary Planning Tool (USAF) GCSS‐J – Global Combat Support System – Joint (Joint) ICIS – Integrated Consumable Item Support (DLA) JEPES – Joint Engineer Planning and Execution System (Joint) SALE – Single Automated Logistics Enterprise (USA) SPIDERS – Support Planning Integrated Data Enterprise Readiness System (DLA) TCMS – Theater Construction Management System (USA) VFOB – Virtual Forward Operating Base (USA) DoD Directive on Contingency Basing **It is DoD policy to pursue increased effectiveness and efficiency in contingency basing by: • Promoting scalable interoperable capabilities that support joint, interagency, intergovernmental, multinational partners • Providing common standards for planning, design, and construction in accordance with UFCs; developing common standards for contingency services; and establishing standards for equipment, base operations, and base transition or closure to support scalable contingency basing • Using operational energy more efficiently, minimizing waste, and conserving water and other resources • Integrating comprehensive risk management for force protection, emergency management, environment, safety, explosives safety, and occupational health into planning, design and operations • Minimizing the logistics footprint by optimizing the delivery of material solutions, contracting practices and services • Providing the optimal mix of military, civilian, and contractor personnel competencies in the DoD Total Force planning process • Conducting contingency basing education and training for military and civilian personnel • Minimizing adverse impacts on local populations and cultural resources 5/30/2012 **10 May 2012 Working Draft Language 24 Facility Criteria • Section 807 of Public Law 111-84, Dated 28 October 2009, directed that it would be the policy of the Department of Defense that facilities, infrastructure, and equipment that are intended for use by military or civilian personnel of the Department in current or future military operations should be inspected for safety and habitability prior to such use, and that such facilities should be brought into compliance with generally accepted standards for the safety and health of personnel to the maximum extent practicable and should be consistent with the requirements of military operations and the best interest of the Department of Defense (DoD), to minimize the safety and health risk posed to such personnel. • The DoD uses the Unified Facilities Criteria (UFC) system as prescribed by MIL-STD-3007 to provide planning, design, construction, sustainment, restoration, and modernization criteria for Defense facilities. • The Office of the Secretary of Defense directed the Tri-Service Engineer Board Working Group to develop UFCs to codify the policy directed by law to ensure that acceptable life, health, and safety criteria are met for facilities used and constructed in support of military operations. 5/30/2012 25 Facility Criteria • Over the past year, the Tri-Service Engineer Board has been developing three new UFC documents. – – – • • Each of these documents addresses minimal acceptable facility design criteria for life, safety, and health to protect personnel that use the facilities. These UFCs establish technical criteria for the following building systems – – – – – – – • UFC 1-201-01 – Non-Permanent Facilities in Support of Military Operations UFC 1-201-02 – Assessment of Existing Facilities for Use in Military Operations UFC 2-202-01 – Host Nation Facilities in Support of Military Operations Fire protection Structural integrity Electrical Plumbing and mechanical Water treatment, storage and distribution Waste water collection and treatment Telecommunications networks. The technical criteria originate from previously published UFCs, International Codes, and/or established DoD/Service Policies or Regulations. 5/30/2012 26 AFCS to JCMS Transition HQDA / CSA AR 415-16 CoE AFCS JCMS DJ4 CoE JOEB Work Plan Navy USACE DFFE MDEP MGMT HNC IT MED Design Other Support Agencies – Provides construction and logistics data to • Inform the TAA process (EN & LOG Force Structure) • JEPES for Theater Engineer Planning – Provides standard designs for contingency construction used by all Service Engineers – Executes exercise support and training for the Joint Force – NATO requested use of TCMS to implement construction standardization OCE AFCS Air Force JCMS A system consisting of a software suite of interoperable capabilities that uses and develops common data and enables Joint Engineers the capability to plan, execute and manage construction in support of military operations. AFCS PgM Policy and Doctrine Update AR 415-16 Master Planning − GIS based − Flexible − Compatible w/other systems Update TM-Series Training Training Course Development Course Validation Exercise & Predeployment Training Supporting Systems − Construction Management − Analysis tools Information Technology Software IT Infrastructure Establish GeoExPt VFOB Development Migration to Integration Integration JCMS IT NEC-R Infrastructure Direct Fund Distribution Design Disperse Funds Oversight Service Level Input Develop Metric Designs Metric Material Evaluation WEBFLIS Automated Updates Metric Material Cataloguing Update Electrical Distribution Designs Convert Navy Designs Logistics Service Logistical System Integration Marine Corps Update Validate Design Existing Data and Input Designs Into JCMS IAW C-UFC Database Logistical System − Direct interface w/Joint andService systems Standard Designs − Common database − Joint and Service specific designs − Meet Non-Permanent Facility UFCs Governance Structure Program Management Office (PMO): Responsible for integrating strategic level products within the Functional Areas of AFCS. Control Management Board (CMB): An O6 level board chaired by Director, OCE. Additional participants include USAES, FORSCOM Eng, O6 Sister Service representative, HQDA G4, & theater engineer commands. Determines AFCS priority requirements & associated funding and approves changes to the AFCS. Configuration Control Board (CCB): Comprised of one – two individuals within the Functional Area responsible for reporting and as required, recommend changes to the CMB for the AFCS PgM. Functional Configuration Review Board (CRB): Led by the functional lead for the discipline, responsible for conducting working group sessions to analyze and make recommended changes to the CCB. Project Configuration Review Board (CRB): Comprised of U.S. Government agencies or private contractors developing products for AFCS responsible for developing products and recommending changes through the Functional CRB to the CCB and CMB. JOEB Chief of Engineers JCG AFCS CMB Training CCB Information Technology CCB Training CRB Information Technology CRB Project CRB DoD Partner CRB Project CRB Policy & Doctrine CCB Design CCB Design CRB DoD Partner CRB 30 Project CRB DoD Partner CRB Post JCMS v1.0 Release Work Efforts • Enhance Functionality of Software • Further Integrate GIS Capabilities • Continual Process to Develop / Update Designs − Sustainability − Construction Materials − Construction Methods • Improve Synchronization of Material Acquisition • Validate efforts at the Contingency Basing Integration Technology Evaluation Center at Fort Leonard Wood 31 Questions / Open Discussion 32 AFCS / JCMS Design Database TCMS v3.2 (2010) is the software that provides access to the AFCS database. AFCS designs consist of: Construction Details Structural plans and elevations Infrastructure requirements Site Plans (Airfields, Base Camps, Support Facilities) 1,400 Facility Designs 200 Component Designs 5,800 Drawings 36 Naval Designs & 95 Drawings TOGS Bill of Materials TCMS generates BOM Reports: BOM Gross – Material totals for an entire project BOM Gross with NSN – includes material details (UI, Specifications) BOM by Component by Facility – material types, quantities, and cost by each facility BOM by Component by Facility by Sequence – materials required for a specific sequence or work activity Theatre Oriented Guide Specifications provide description of process, procedure, and construction specification for the associated sequence/material. TOG Report lists all within the project. Points out duplicate TOGs when applicable in multiple locations Can also be used for construction contracting language. Master Planning Mission critical facilities within AFCS drive Joint Staff and Army contingency plans by determining what manpower and equipment is required within the Force to for a contingency operation. Labor Estimates BOM Reports Equipment Estimates Force Modeling Technical Manuals AFCS Provides enhanced master planning tools and capabilities to the user. Technical Manuals consist of four publication series Planning Guidance TOGS Designs Sequences Facilities Components Bills of Materials User Guide JCMS is: GIS Bas Flexible Compatible with other systems GeoExPT (USAF) VFOB (USA) Standard Designs Logistical System JCMS integrates construction designs across all Services to provide one database of designs compliant with Unified Facilities Criteria (UFC). Direct interface with Joint and Service systems to streamline material acquisition. BOM Report exportable into Service specific logistical acquisition systems. JCMS Contains: Joint Standard Designs Service Specific Designs Both Metric and English C‐UFC Compliant Designs Force Structure JCMS Logistically provides access to: GCSS‐J (Joint) JEPES (Joint) ICIS (DLA) SPIDERS (DLA) SALE (USA) Supporting Systems Construction Management and analysis tools provide additional support to the engineer planner. JCMS supporting systems include: SCM (USN) FIRESTORM (ARCENT) GeoExPT (USAF) VFOB (USA) Project Management Labor and Equipment estimates generated from a project can be extracted and imported into Microsoft Project. JEPES – EN Module Problem Statement: • Current GCSS-J fielded version “JEPES Classic” is slow, not user friendly, and has very limited mapping capabilities. • CCMD’s working to create their own EN / LOGCOP • Aspiration to “plan” future operations is holding back ability to “see” current operations. • JEPES development lacks cohesive “vision” Progress Summary: • GCSS-J v. 7.3 fielded in DEC 11 Big improvement: mapping, Graphical user interface, planning based, limited functionality, initial prototype • Senior Leader Feedback – Need EN COP data repository, current operations, execution tracking synchronization Team Members: • • Lead Agency: JS, J4 ED Supporting: Engineers from: Services CCMDs USFOR-A USF-I (Products & Lessons Learned) Way Ahead: • Stay within GCSS-J, develop EN Module • Improve map as basic component of COP • Develop EN COP Vision • Develop EN COP – Basis for LOGCOP A well-designed Engineer COP provides the map foundation for an effective Log COP • Shift focus from Planning to Execution 34 JEPES – EN Module POA&M: Work Plan Milestone Initial Target Current Mitigation / Status Target Field GCSS-J version 7.3 JAN 12 DEC 11 Complete Field GCSS-J version 7.3.1 APR 12 May 12 No input for EN Field GCSS-J version 7.3.2 DEC 12 NOV 12 Develop EN COP vision APR 12 Develop EN COP in 7.3.3 JUN 13 No/Limited EN equity DJ4/CAM recommendation: Approve • Change approach from deliberate/crisis action planning to concentrate exclusively on execution management. • JS J4-ED develops a vision, provides guidance to development team, and tests prototypes. • Drop JEPES terminology and adopt GCSS-J terminology. New term is Engineer Module. • Develop GCSS-J Engineer Module and Joint Engineer Portal to complement one another. EN Module provides terrain visualization and project execution. Joint Engineer Portal provides knowledge management (e.g. links to guidance, standards, environmental baseline surveys, historic briefings) and tools for engineer governance processes (e.g. Joint Facility 35 Utilization Board) Reports Bills of Material • By Component by Facility by Construction Activity – This report is organized and displayed using the same data hierarchy structure as the project is organized. All the materials for a Component and its associated Facilities and their associated Activity are grouped in the same way that they appear in the project hierarchy. This allows the engineer to see the material costs associated with each Activity, Facility, Component, Super Component, and finally at the conclusion, the summary costs for the entire project. • By Component by Facility Gross – This BOM report is similar to the BOM by Component by Facility by Construction Activity except that the materials associated with all the Activities associated with a facility are not separated by Construction Activities. • Gross – This report lists all the National Stock Numbers (NSNs) and their respective data associated with the entire project. The NSNs are listed in numeric order to allow for quick navigation through the material listing. • Gross with NSN Details – This report lists all the NSNs and their respective data with a detailed description of each NSN associated with the entire project. The NSNs are listed in numeric order to allow for quick navigation through the material listing. • Multi‐Project Gross Report – The AFCS application also supports generating a BOM Gross report that can span multiple projects in the project tree. This allows an engineer to develop or import multiple projects into a project tree and, by using the Consolidated Resources / BOM wizard, select one or more projects from the project tree and generate a gross report. • BOM REPORTS. The pricing information for the BOM comes primarily from FEDLOG. AFCS allows locally sourced (Non‐NSN) materials and their associated costs to be defined in the system. When locally sourced Non‐ NSN materials replace defined NSN data in a project, the pricing information provided in the Non‐NSN is included in the BOM. 5/30/2012 36