A07_Attachment_6_-_Task_Order_1_PWS_FORCES.pdf

PERFORMANCE WORK STATEMENT

Army Force Organization Cost Estimating System (FORCES) Task Order No. 1

Rev: 23 June 2016 for Deputy Assistant Secretary of the Army for Cost & Economics

Part 1

GENERAL INFORMATION

1.0 GENERAL: This is a non-personnel services contract to provide support to the

Army’s FORCES Suite. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

The Deputy Assistant Secretary for Cost and Economics (DASA-CE) requires the maintenance and update of the Army Force Organization Cost Estimating System (FORCES), a suite of models and database tools used to cost Army organization structure and capabilities. The tools included in the suite are the FORCES Cost Model (FCM), The Army Contingency Operations Cost Model (ACM), the Cost and Factors Handbook (CFH), the ARFORGEN Costing Tool (ACT), and the Tables of Distribution & Allowances (TDA) Cost Model. The ACM and the FCM are available in both SQL Server executables and web-based models. The ACT is available as a SQL Server executable and may be converted to a web based model. The CFH is web-based searchable compendium of data tables. The TDA model is a web-based model.

DASA-CE also requires the annual development of Installation Status Report – Infrastructure (ISR-I) cost factors for new construction, renovation, and sustainment to:

• Estimate the cost of improving installation facilities such that they meet or exceed

Army-defined standards.

• Estimate the cost of keeping facility condition at a constant state by performing sufficient maintenance and repair to prevent facility degradation.

• In addition to the ISR-I costs stated above, DASA-CE also requires annual generation of a Historical Preservation Factor along with ongoing subject matter expertise and support associated with the ISR-I costs.

1.2 Background:

1.2.1 The contract to develop the initial FCM was awarded in 1989 as a DOS-based program and converted to the SQL Server language in 1997. It was converted to a web-based model in 2013.

1.2.2 The FCM estimates Active and Reserve Component costs driven by a unit’s Table of

Organization and Equipment (TOE). The types of costs include Acquisition, Activation, Operations & Sustainment, Movement, and Inactivation of units. All personnel and equipment can be modified at the user’s discretion.

1.2.3 The ACM was added to the FORCES suite in 1997. It estimates costs for planning a

Contingency Force or Training Operation through the pre-deployment, deployment, operations and sustainment, redeployment, reconstitution, and demobilization phases.

1.2.4 The CFH is a searchable, web-based database consisting of data used in the FCM and

ACM, along with other data commonly needed by analysts.

1.2.5 The ACT was added to the FORCES suite in 2013. It is a PC-based cost model used for estimating the cost of units through the ARFORGEN cycles.

1.2.6 The TDA web-based model was added to the FORCES suite in 2015. It estimates the

Operations & Sustainment costs of TDA units.

1.2.7 The ISR-I costs are used by a wide-reaching array of stakeholders throughout the

Army to help quantify the resources required to attain and perpetuate installation infrastructure readiness. The ISR-I costs satisfy macro resource planning requirements for Major Army Command (MACOM) and Headquarters, Department of the Army (HQDA) management levels.

1.2.8 The ISR-I Historic Preservation Factor is used to estimate resources required for upkeep of historic preservation facilities

1.2.9 The Contractor must be proficient and be able to perform all of the following:

a) Army force structure data bases to include Tables of Organization and Equipment (TOE), Structure & Manpower Allocation System (SAMAS), Consolidated TOE Updates (CTU), and Tables of Distribution & Allowances (TDA)

b) Developing standard composite modified TOEs (MTOEs) for individual Standard Requirements Codes (SRCs)

c) Experience generating Army force cost estimates for Base TOEs, Modified TOEs, and Objective TOEs encompassing unit acquisition costs, operating and support costs, and movement costs

d) Developing standardized Army unit cost estimates for Contingency Operations

e) Developing, maintaining, updating, and modifying force costing models in the

SQL Server PC programming language and in the ASP.NET web-based programming language.

f) Developing Army-specific costs for new construction, renovation, and sustainment at the Facility Category Group (FCG) and Facilities Category Code (FCC) levels of detail.

g) Generating an Army-specific Historic Preservation factor.

h) Utilizing Army, DoD, and private sector data sources to generate cost factors.

1.3 Objectives:

a) Maintain the FORCES suite of models.

b) Update the data bases supporting the FORCES suite of models.

c) Modify the program code in the FORCES suite of models.

d) Perform special cost analysis research.

e) Provide customer/technical assistance with the FORCES suite of models, to include training and briefings.

f) Maintain and develop new methodologies, data tables, and cost factors required to meet changing Army policies.

g) Develop ISR-I new construction, sustainment, and renovation cost factors.

h) Provide ongoing subject matter expertise and support related to the ISR-I cost factors

i) Generate Historic Preservation cost factor.

1.4 Scope: The contractor shall provide non-personal technical support services to DASA in the areas of cost of operations of TOE units and cost of contingency operations.

1.5 Period of Performance: Five (5) Year Ordering Period per Section F of the Contract.

1.6 General Information

1.6.1 Quality Control The contractor shall develop and maintain an effective quality control program (QCP) to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which the contractor assures that the work complies with the requirement of the contract. The QCP will be delivered to DASA-CE. (CDRL A022) After acceptance of the QCP contractor shall receive the contracting officer’s acceptance in writing of any proposed change to his quality control system.

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.5 Place of Performance: Contractor Location.

1.6.6 Type of Contract: Indefinite Delivery/ Indefinite Quantity (ID/IQ) with Cost Plus

Fixed Fee (CPFF) Task Orders.

1.6.7 Security Requirements: Contractor personnel performing work under this contract must have a SECRET security clearance at time of the proposal submission, and must maintain the level of security required for the life of the contract. The security requirements are in accordance with the attached DD254.

1.6.7.1 Antiterrorism/Operations Security:

a. Contractor Employees Who Require Access to Government Information Systems.

All contractor employees with access to a government info system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the information systems and then annually thereafter.

b. For Information assurance (IA)/information technology (IT) training. All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of employment.

c. For Contract Requiring Performance or Delivery in a Foreign Country. DFARS

Clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US. The clause shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support. The key AT requirement is for non-local national contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

d. For Contracts That Require Handling or Access to Classified Information.

Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “(Con)fidential,” “(Sec)ret,” or “Top (Sec)ret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating

Manual (DoD 5220.22-M); any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

1.6.8 Key Personnel:

Project Manager—

Minimum/General Experience: Fifteen years of DoD/Federal program management experience and contract oversight. The name of this person and an alternate who shall act for the contractor when the Project Manager is absent shall be designated in writing to the COR.

Functional Responsibility: The Project Manager and alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

Education: Bachelor's degree business field or technology discipline.

Senior Consultant—

Minimum/General Experience: Ten years of relevant progressive experience in quantitative analysis, computer modeling, forecasting, management consulting, and the ability to effectively use applicable tools and techniques.

Functional Responsibility: Provide consulting to Division Chiefs and Senior Analysts for cost models, data bases, cost factors and analyses. Designs, organizes, leads, and conducts maintenance and improvements of cost estimating models, tools and data development. Provides cost estimates. Manage a team of consultants and analysts.

Education: Bachelor's degree in Information Systems, Engineering, Business, or a Quantitative discipline such as statistics or economics or other related discipline.

Senior Management Consultant—

Minimum/General Experience: Twenty years relevant professional experience, five years management of relevant study types.

Functional Responsibility: Provides expert guidance on study-related policy and procedural issues. Acts as Team Lead reporting to a Principal and is responsible for a specific study area on large, complex projects. Directs and performs data collection, analysis, and report preparation.

Education: Master's degree in Operations Research, business or technology discipline

Senior Systems Programmer—

Minimum/General Experience: Four years' experience in transfer, sustainment, modernization, and continuous improvement of automated data processing activities.

Functional Responsibility: Performs complex assignments on operating systems and application programs; Performs work on moderately complex applications programs; Codes, tests, and debugs applications; Analyzes a variety of systems, programs, and develops documentation, and design specifications; Analyzes system specifications and develops methods for problem solution; May perform system test and integration and select computer systems, languages and equipment; Defines nature of data contained in the database.

Education: Bachelor's in engineering, information technology, computer science, or programming or similar technology field

1.6.8.1 Non-Key Personnel:

Principal Information Engineer—

Minimum/General Experience: Eight years' experience in information engineering with knowledge of functional and data requirements analysis, activity-based costing, modeling, functional economic analysis, process improvement, and performance measurement; Knowledge of information engineering methodologies, tools, and techniques for application across project, functional area, and organizational boundaries.

Functional Responsibility: Develops and refines new engineering techniques to enhance quality and productivity; Develops and recommends standards for information systems procedures;

Develops and recommends cost effective information engineering methodologies and tools for application across functional and project boundaries; Develops and applies organization-wide information models for use in designing and building integrated, shared software and database measurement systems; Develops and assists in development of activity and data models in both the "as-is" and "to-be" environments, identifies targets of opportunity for improvement;

Develops and leads development of simulation models for "what-if" analyses of identified core and business processes targeted for re-engineering and improvement.

Education: Bachelor of Science degree in Computer Science, Information Systems, Business, Engineering, or related technical discipline.

Senior Program Analyst—

Minimum/General Experience: Three years' experience may include design, installation, maintenance, and requirements development; Knowledge of systems applications, equipment processes, capabilities and limitations.

Functional Responsibility: Assists or directs the analysis and design of management systems;

Identifies key users, their needs, and determines disconnects between data and information;

Identifies data storage or handling of information and provides solutions; Devises improved methods of data descriptions, data outputs, and data feeds to support a variety of users;

Responsibilities may include analysis of technical, financial, and program data.

Education: Bachelor of Science degree in Computer Science, Information Systems, Business, Engineering, or related technical discipline.

Senior Database Administrator—

Minimum/General Experience: Seven years of experience with complex databases is required;

Possess knowledge of standards and procedures, able to maintain database dictionaries, and competent in the database management.

Functional Responsibility: Works at the highest level of database management; May be responsible for design, implementation, and maintenance of complex databases with respect to JCL, access methods, access time, device allocation, validation, organization, and statistical methods; Duties may include protection and security of physical information; Provides advice to database administrators on design and development of large scale or complex database applications; May monitor the performance of subordinates and provide guidance and instruction to project/task team members.

Education: Bachelor of Science degree in Computer Science, Information Systems, Business, Engineering, or related technical discipline.

Principal—

Minimum/General Experience: Twenty years federal consulting experience, 10 years management of relevant studies

Functional Responsibility: Provides corporate-level project oversight, and project management of large, complex projects. Provides high-level technical expertise and executive briefings and training.

Education: Master's degree in business or technology discipline.

Consultant—

Minimum/General Experience: Eight years of progressive experience in quantitative analysis, computer modeling, forecasting, management consulting.

Functional Responsibility: Provides technical consulting support to Division Chiefs and Senior Analysts for cost models, data bases, cost factors and analyses. Designs, organizes, leads, and conducts maintenance and improvements of cost estimating models, tools and/or data development. Provides cost estimates.

Education: Bachelor's degree in Information Systems, Engineering, Business, or a Quantitative discipline such as statistics or economics or other related discipline.

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart

42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract;

issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.11 Contractor Travel: Contractor will be required to travel OCONUS and CONUS within the performance of this contract to attend meetings, conferences, and training.

The contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR.

1.6.12 Other Direct Costs: This category includes travel, reproduction, and shipping expenses associated with training activities as well as visits to contractor facilities. It could also entail the renting of suitable training venues.

1.6.13 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.)

or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.14 Transition In/Out: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the 30 day phase in/phase out periods. During the phase in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

1.6.15 ACCOUNTING FOR CONTRACT SERVICES REQUIREMENT – ENTERPRISE-

WIDE CONTRACTOR MANPOWER REPORTING APPLICATION

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the FORCES contract via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/, and then click on “Department of the Army CMRA” or the icon of the DoD organization that is receiving or benefitting from the contracted services.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk by clicking on “Send an email” which is located under the Help Resources ribbon on the right side of the login page of the applicable Service/Component’s Contractor Manpower Reporting website.

PART 2 / Reserved

PART 3

3.0 GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: The Government will provide reasonable access to its facilities, key people, data, and documents in support of the project as required

3.2 Facilities: Not Applicable

3.3 Utilities: Not Applicable

3.4 Equipment: Not Applicable

3.5 Materials: Not Applicable

PART 4

4.0 CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES

4.1 General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this

PWS.

4.2 Secret Facility Clearance The contractor shall possess and maintain a SECRET facility clearance from the Defense Security Service. The Contractor’s employees, performing work in support of this contract shall have been granted a SECRET security clearance from the Defense Industrial Security Clearance Office.

4.3. Materials: Visual SQL Server and web-based programming languages

4.4. Equipment: Not Applicable

5. SPECIFIC TASKS

5.1. Basic Services

5.1.1 The Contractor shall provide services for updating and maintaining the FORCES

Suite of models as well as special studies based on these models.

5.1.2 The Contractor shall provide services for updating and maintaining the Installation

Status Report - Infrastructure (ISR-I) Cost Factors.

5.2. Tasks

5.2.1 The Contractor shall maintain and make the FORCES models available to users.

5.2.1.1 The Contractor shall maintain the FORCES web-based models (FORCES on the

Web, FCM, ACM, TDA model, CFH) on the Army domain (NIPRnet) and make available to users as directed by the COTR.

5.2.1.2 The Contractor shall maintain and develop designated statistics of user and technical activity for each of the FORCES models and maintain them on the FORCES website.

(CDRL A001)

5.2.1.3 The Contractor shall research, identify, and implement a redesign of FORCES on the web to more fully integrate the individual models.

5.2.1.3.1 The Contractor shall facilitate multiple modernization requirements research, design, and development workshops to determine the best way forward to combine costing elements of the current web-based ACM, FCM, and TDA cost models into one integrated cost model.

5.2.1.3.2 The Contractor shall design, develop, and test software code to research, to identify data sources, establish recurring data feeds from those sources, design layout and structure of the data, and develop improvements to existing ACM, FCM and TDA cost models and correspondence equations and mathematic equations/formulas that will allow users to analyze resource requirements for manpower and equipment requirements and authorizations for the Army.

5.2.1.4 The Contractor shall reengineer PC-based SQL Server applications to Web-based applications, to include forms, data, table structures, programs, and processes.

5.2.1.5 The Contractor shall design, implement, and maintain automated web services and integrate with JIAT as directed by the COTR.

5.2.1.6 The Contractor shall maintain the FORCES PC-based models (FCM, ACM, ACT) and make available to the COTR as directed.

5.2.2 The Contractor shall collect, analyze, validate, and process the latest data from official sources (OSMIS, AMCOS, SAMAS, CTU, TAMIS, etc.) and update the data/factors tables in the FORCES models. (CDRL A002)

5.2.2.1 The Contractor shall provide a list of the tables in each of the FORCES models and update the list when tables are deleted or added as a result of new requirements / methodologies. (CDRL A003)

5.2.2.2 The Contractor shall provide a list of the sources for the data in each of the FORCES models and update the sources when tables are deleted or added. (CDRL A004)

5.2.2.3 The Contractor shall conduct a continuous review of all data sources to ascertain that they meet user requirements and incorporate emerging technologies and policy/methodology changes.

5.2.2.4 The Contractor shall report the receipt of incomplete, corrupted, or incorrectly formatted data from DoD or DoD-owned databases to the COTR for resolution.

5.2.2.5 The Contractor shall identify all Army data update requirements to the COTR and continue to identify data requirements as Army databases change to reflect new costing methodologies.

5.2.3 The Contractor shall design, develop, test, and implement modifications and changes to the FORCES models as identified by the COTR. (CDRL A005)

5.2.3.1 The Contractor shall research, identify, and implement the development of the force structure for the TDA model at the paragraph level. (CDRL A006)

5.2.3.2 The Contractor shall research, identify, and implement an expansion of the Installation Services Cost Element Structure in the TDA model as designated by the

COTR. (CDRL A007)

5.2.3.3 The Contractor shall research, identify, and implement the additional function of enabling a user to create a user SRC from scratch in the ACM, the FCM, and the TDA model. (CDRL A008)

5.2.3.4 The Contractor shall research, identify, and implement the ability to develop cost factors for civilian personnel in schedules other than GS/WG in the TDA model.

(CDRL A009)

5.2.4 The contractor shall develop cost estimates designated by the COTR, using the FORCES suite of models (FCM, ACM, ACT, TDA, and CFH).

5.2.5 The Contractor shall design, develop, test, and implement custom tools to estimate costs on a case by case basis as required by DASA-CE when current tools are not applicable. This may include tools ranging from simple spreadsheet models to complex PC-based or Web-based applications.

5.2.6 The Contractor shall provide customer/technical assistance with FORCES.

5.2.6.1 The Contractor shall research and respond to users’ queries on FORCES and supporting data.

5.2.6.2 The Contractor shall provide technical expertise on the source data used in the

FORCES models, remaining current on changes with the data and their file structures.

5.2.6.3 The Contractor shall assist users with technical difficulties.

5.2.6.4 The Contractor shall provide briefings, training, and customer support in force costing, the FORCES models, and the models’ source data.

5.2.6.5 The Contractor will develop, maintain, and update help files for each of the models.

(CDRL A010)

5.2.7 The Contractor shall develop, update, and maintain FORCES program documents.

(CDRL A011)

5.2.7.1 The Contractor shall prepare and present an Approach Plan that outlines how the contractor intends to accomplish the requirements of this contract. (CDRL A012)

5.2.7.2 The Contractor shall develop and implement a software testing plan for the FORCES suite of models. (CDRL A013)

5.2.7.3 The Contractor shall provide In Process Reviews as needed to describe progress to date and plans for the remainder of the contract. This may include a revised Approach Plan. (CDRL A014)

5.2.7.4 Reserved

5.2.7.5 The Contractor shall provide a weekly list of current actions.

5.2.7.6 Reserved

5.2.7.7 The Contractor shall make recommendations for possible improvements to the

FORCES suite of models.

5.2.8 The Contractor shall develop ISR-I cost factors for new construction. Cost factors may be developed by Facilities Category Group or Facilities Category Code, based on the specific Task Order issued. (CDRL A015) For each new construction factor, the Contractor shall:

i. Utilize a costing methodology, approved by DASA-CE-I, which incorporates appropriate DOD, Army, and/or applicable private sector data sources, to generate accurate new construction costs expressed in dollars per unit of measure (e.g., $/SF).

ii. Clearly indicate the process for generating the new construction costs and note any assumptions, business rules, inflation factors, and adjustments that impact the costs.

iii. Identify year-over-year variances and, for large variances, provide detailed explanations and supporting documentation

5.2.9 The Contractor shall develop component-level “AMBER to GREEN” and “RED to GREEN” ISR-I cost factors for renovation. (CDRL A016) The factors developed may be at the FCG or FCC level, based on the specific task order issued. The Contactor shall:

i. Utilize a costing methodology, approved by DASA-CE-I, which incorporates appropriate DOD, Army, and/or applicable private sector data sources, to generate accurate component level renovation costs expressed in dollars per unit of measure (e.g., $/SF).

ii. For each component of each FCG/FCC, clearly indicate the cost to repair (AMBER to GREEN) and the cost to replace (RED to GREEN).

iii. Clearly define the logic and methodology utilized to generate the factors and indicate any assumptions, business rules, inflation factors, and adjustments that impact the renovation construction costs.

iv. Identify year-over-year variances and, for large variances, provide detailed explanations and supporting documentation.

v. If the Army implements the Builder program, the Contractor shall provide a mapping from the inspection units identified using the Builder program to the developed renovation cost factors.

5.2.10 The Contractor shall develop ISR-I cost factors for sustainment for permanent, as well as semi-permanent or temporary, facilities. (CDRL A017) Cost factors may be required by FCG or FCC, based on the specific Task Order issued. For all sustainment cost factors, the Contractor shall:

i. Utilize a costing methodology, approved by DASA-CE-I, which incorporates appropriate DOD, Army, and/or applicable private sector data sources, to generate accurate sustainment costs expressed in dollars per unit of measure (e.g., $/SF).

ii. Capture all necessary maintenance and repair activities to maintain assets over a 50 year service life.

iii. Identify year-over-year variances and, for large variances, provide detailed explanations and supporting documentation.

5.2.11 The Contractor shall develop a historic preservation cost factor. (CDRL A018) The Contractor shall:

i. Identify those Army assets that are considered to be “historic preservation” properties.

ii. Utilize a costing methodology, approved by DASA-CE-I, to generate a single factor identifying the ratio of costs between historical and non-historical preservation properties. This shall include any necessary extrapolation from applicable DOD, Army, and/or private sector data sources.

5.2.12 The Contractor shall provide ongoing subject matter expertise and customer/technical support to DASA-CE-I regarding the ISR-I cost factors and historic preservation cost factor.

5.2.12.1 The Contractor shall assist DASA-CE-I in identifying the impact of changes in policies, manuals, guidelines, and data sources on the ISR-I cost factors and assist in developing potential solutions.

5.2.12.2 The Contractor shall serve as a subject matter expert in meetings, briefings, and seminars which may be directly or peripherally related to the development, modification, or application of the ISR-I cost factors, as requested by DASA-CE-I.

Contractor shall not officially represent any government entity.

5.2.12.3 The Contractor shall provide training and briefings to DASA-CES-I regarding the life-cycle development of the ISR-I cost factors, as requested by DASA-CES-I.

5.2.12.4 Upon request, the Contractor shall review all proposed data sources, logic, methodologies, and equations used in the creation of ISR-I cost factors with DASA-

CE.

5.2.13 The Contractor shall perform various program management activities related to the ISR-I cost factors as specified herein.

5.2.13.1 Reserved

5.2.13.2 Reserved

5.2.13.3 The Contractor shall submit all documentation, software, data, and other materials used in the development of cost factors to the COR within 30 days of the completion of a given task order. (CDRL A019) All data, models, and formulas used to generate cost factors will be considered deliverables as part of this contract. All methodologies and tools used in the performance of this contract shall be documented. The Contractor agrees that government personnel may reutilize any and all tools, methodologies, and data sources without any limitation or additional compensation to the Contractor. The Army reserves the right to evaluate, re-use, and publish results using the tools, techniques, methods, and data used to satisfy the requirements of this contract, regardless as to whether they were initially considered to be proprietary.

5.2.13.4 The Contractor shall provide a monthly status report by the 15th of the following month. (CDRL A020) This report will include at a minimum the following:

a) Technical Status – Summary of Accomplishments/Major Events/Issues.

b) Management Status – Summary of Accomplishments/Major Events/Issues.

c) Open Action Status – Action Item tracking shall include all open action items, the person/ organization that opened the item, description, status, the assigned responsibility for investigation and closure, the date created, the date resolution needed, a complete history of promised dates for resolution, and other information deemed important by the Government or Contractor.

d) Risk Management Status – The contractor shall include the current risk management Status including identified risk, risk impact, mitigation strategies, probability of occurrence and severity.

e) Deliverable Documentation Status – This is a table of all deliverable documentation including, at a minimum, the title of the document, identification number of the document, revision of the document, the due date, the submitted date, date approval is required, and approval status.

f) 30 day forecast of events, meetings, and deliverables.

g) Current and cumulative monthly cost by task order.

5.2.13.5 The Contractor shall provide a Contract Funds Status Report by the 15th of the following month by task order. (CDRL A021)

PART 6 - Deliverables

CDRL Deliverable References A001 Statistics User & Technical Activity 5.2.1.2 A002 Data/Factors Tables 5.2.2 A003 Update FORCES Table 5.2.2.1 A004 Update Sources Table 5.2.2.2 A005 Changes FORCES Model 5.2.3 A006 FORCES Structure TDA Model 5.2.3.1 A007 Installation Service Cost Element Structure 5.2.3.2 A008 User SRC 5.2.3.3 A009 Civilian Cost Factors 5.2.3.4 A010 Help Files 5.2.6.5 A011 FORCES Program Documents 5.2.7 A012 Approach Plan 5.2.7.1 A013 Software Testing Plan 5.2.7.2 A014 In Process Review 5.2.7.3 A015 New Construction Cost Factors 5.2.8 A016 Cost Factors for Renovation 5.2.9 A017 Cost Factors for Sustainment 5.2.10 A018 Cost Factors for Historic Preservation 5.2.11 A019 Final Task Order Documentation 5.2.13.3 A020 Monthly Status Report 5.2.13.4 A021 Contract Funds Status Report 5.2.13.5 A022 Quality Control Plan 1.6.1