W91CRB-16-T-0017-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

SOLICITATION AMENDED TO INCORPORATE QUESTIONS AND ANSWERS, REVISE SECTION C (PERFORMANCE WORK STATEMENT), ADD CLAUSE 5152.237-4900 TO SECTION C, REVISE 52.212-5, REVISE FAR 52.217-9, REVISE SECTION L (EVALUATION APPROACH), ADD CLIN 0004 (TRANSITION), INCORPORATE A REVISED COST MODEL, INCORPORATE A REVISED DD 254, AND ADD CLAUSES AND PROVISIONS.

A CONFORMED COPY OF THIS SOLICITATION INCORPORATING ALL CHANGES TO THIS SOLICITATION THROUGH AMENDMENT 0002 IS

AVAILABLE AT WWW.FBO.GOV.

THE RESPONSE DATE/TIME IS EXTENDED TO 11:00 AM EST 26 MAY 2016.

1. CONTRACT ID CODE PAGE OF PAGES

Y 1 42

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 12-May-2016

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W91CRB-16-T-0017

X 9B. DATED (SEE ITEM 11)

21-Apr-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

12-May-2016

CODE

ACC - APG - W91CRB

4310 BOOTHBY HILL AVE

ABERDEEN PROVING GROUND MD 21005-3013

W91CRB 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91CRB-16-T-0017

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

QUESTIONS AND ANSWERS

1. QUESTION: General. Please confirm that this solicitation was sent directly to a subset of SDVOSBs as an outcome of a review of the responses to your Sources Sought issued on 2/11/16. If so, please name these vendors so we can explore teaming arrangements (we are not a SDVOSB).

ANSWER: No, the solicitation was only posted to the Federal Business Opportunities (FedBizOpps) website on 21 April 2016

2. QUESTION: General. In order to afford opportunities for maximum competition, would the government consider allowing offerors to submit offerors under GSA Schedule IT 70? In addition, would the government be open to allow offerors to form a GSA Schedule Contractor Team Agreement (CTA), which allows two or more GSA Schedule contractors work together to meet the government’s needs? Further, would the government allow CTA teams to consist of SDVOSBs, Large Businesses and other SBs or consist of only of SDVOSBs? Using a CTA, the government can procure one total solution instead of issuing separate awards for each part of a requirement. By complementing each other’s capabilities with attention focused on their combined core capabilities, the team offers a total solution to the ordering activity’s requirement. The government would still be able to meet its socio-economic goals using this approach as it would have privity of contract with each CTA member.

ANSWER: No. The determination to set-aside this acquisition as a SDVOSB was based on the results of our Requests for Information published in FedBizOpps on 11 February 2016.

3. QUESTION: General. Please confirm the Lowest Priced Technically Acceptable (LPTA) evaluation criteria for a professional services contract, especially considering the attention in the media, DoD, and industry around the Value Based Defense Procurement Act.

ANSWER: Yes, this acquisition will be evaluated and awarded to the LPTA offeror.

4. QUESTION: Section 2.3 Senior Enterprise Architect (SEA) / Systems Architect I / BPR Specialist. The resumes requirement calls for seven of these personnel. Can you be more specific about the roles that the seven may play? Are all seven equally supporting domains, or are some playing different roles?

ANSWER: See revised Personnel Requirements in Sections 2.3 thru 2.6. Three are designated as key personnel. The priority areas are all Domain/Process-oriented.

5. QUESTION: Section 2.3.3 EA Qualifications. The requirement states “A recognized Enterprise Architecture certification is required.” Does “recognized Enterprise Architecture certification” mean a certification from an industry recognized certification body [e.g., Federal Enterprise Architecture Certification (FEAC), National Defense University (NDU), The Open Group Architecture Framework (TOGAF), Global Enterprise Architecture Organization (GEAO)]? If so, please list which specifically named professional certifications you will consider.

ANSWER: See Section 2.3.3 of the Performance Work Statement (PWS).

6. QUESTION: Section 2.3.3 EA Qualifications. The requirement states “A recognized Enterprise Architecture certification is required.” Does “recognized Enterprise Architecture certification” mean a vendor neutral enterprise architecture certification from an organization recognized by industry, academia, and government?

ANSWER: See Question 5.

7. QUESTION: Section 2.5 Systems Engineer (SE). Is the SE role intended to be half time, or may we propose a Full Time equivalent? Is this role supporting EKR development, another organization like CIO/G6, or something else?

ANSWER: It is anticipated that the SE will be Full-time for a six month duration.

Actual timeframe will be stated on individual task orders. Not supporting EKR, rather interfacing with Army technical organizations like CIO/G-6/PM AESIP/PM-EIS.

8. QUESTION: Section 3.2.1 EKR Implementation Support: Please clarify what is meant by configuring and implementing the EKR? Is the OBT the material developer, or is it the functional requirements developer? Will EKR development occur within the OBT, or will development continue to reside outside the OBT?

ANSWER: OBT is not the material developer. EKR support is aligned to architecture power user type roles.

9. QUESTION: General personnel qualifications. Can minimum education requirements be replaced by years of experience?

ANSWER: Only if it is stated in the qualifications.

10. QUESTION: Transition period. Does the government have an expected transition-in time for the new team? Does the government have an expected transition-out time for the incumbent contract?

ANSWER: See Section 8.2 of the PWS.

11. QUESTION: Transition period/price. Is the offeror expected to price the transition-in and –out period?

ANSWER: The offeror shall price the Transition in CLIN 0004. Transition out will not be separately priced.

12. QUESTION: Transition plan. Does the government have a requirements-based transition plan for the incumbent contract? And if so, will the government share it with offerors?

ANSWER: No

13. QUESTION: Will the government consider an acquisition option other than LPTA?

14. QUESTION: Can the minimum education requirements be replaced by years of experience?

ANSWER: See Question #9.

15. QUESTION: Does the government have a transition plan or is the vendor to recommend a plan as part of the proposal?

ANSWER: See Questions 10, 11 & 12.

16. QUESTION: Does the vendor have to calculate transition costs for this proposal?

ANSWER: See Question #11

17. QUESTION: Is the government requiring certification from an national/international recognized certification body (FEAC, TOGAF,NDU, etc)? Is a vendor certification acceptable?

ANSWER: Yes, see revised Personnel Requirements in Section 2 of the PWS.

18. QUESTION: Is the Systems Engineer billet intended to be only half time? The spreadsheet shows it as half time.

ANSWER: See Question #7.

19. QUESTION: Is the government expecting QA/QC functions to be performed by all personnel? Would the government entertain an additional QA/QC billet to handle this function across all lines of effort?

ANSWER: QA/QC functions will be embedded within the labor categories.

20. QUESTION: Does the EKR development occur within the OBT? Is the government expecting one of the EA billets to be and EKR developer or similar support role?

ANSWER: OBT is not the EKR material developer. Some combination of SEA or EA billets would be EKR “power users”.

21. QUESTION: Section 2.1.3 PM Qualifications: The PM shall possess a Bachelor’s degree in business administration, business management, or human resources.

Question: Would it be correct to assume that any Bachelor’s Degree from an accredited college or university is the minimum requirement, and that a specific Degree in either business administration, business management, or human resources is desirable.”

ANSWER: See revised Personnel Requirements in Section 2.1.3 of the PWS.

22. QUESTION: Section 2.2.1 Consultant / Facilitator is responsible for all the tasks needed to run a productive and impartial meeting. The Consultant / Facilitator shall be able to serve the needs of any group who are meeting with a common purpose, whether it be making a decision, solving a problem, or exchanging ideas and information. This person shall have a minimum of five (5) years’ experience in assisting government personnel in their efforts to lead groups through training, education, or mentoring activities.

Question: Would it be correct to assume the Consultant / Facilitator labor category requires a Secret Clearance?

ANSWER: Yes.

23. QUESTION: Section 2.3.3 EA Qualifications: A bachelor's degree from an accredited college or university with major study in engineering, physical science, mathematics, life sciences, computer science, or other field of science.

23a. Question: Would it be correct to assume that any Bachelor’s Degree from an accredited college or university is the minimum requirement, and that a specific Degree in engineering, physical science, mathematics, life sciences, computer science, or other field of science is desirable.”

ANSWER: See revised Personnel Requirements in Section 2.3 of the PWS.

23b. Question: Does the Senior EA position require experience performing analysis with architecture tool features, databases and business intelligence products?

ANSWER: See revised Personnel Requirements in Section 2.3 of the PWS.

23c. QUESTION: Degrees in engineering technology are not considered to be qualifying for this position.

Question: Would it be correct to assume that this restriction on ‘engineering technology’ degrees is not accurate and needs to be removed?

ANSWER: See revised Personnel Requirements of the PWS.

23d. A recognized Enterprise Architecture certification is required.

Question: Would it be correct to assume that a recognized Enterprise Architecture certification is desired, but not required?

ANSWER: See revised Personnel Requirements in Section 2.3 of the PWS.

24. Section 2.4.2 EA Qualifications: A bachelor's degree from an accredited college or university with major study in engineering, physical science, mathematics, life sciences, computer science, or other field of science.

24a. Question: Would it be correct to assume that any Bachelor’s Degree from an accredited college or university is the minimum requirement, and that a specific Degree in engineering, physical science, mathematics, life sciences, computer science, or other field of science is desirable.”

ANSWER: Degrees in engineering technology are not considered to be qualifying for this position.

24b. Question: Would it be correct to assume that this restriction on ‘engineering technology’ degrees is not accurate and needs to be removed?

ANSWER: See revised Personnel Requirements in Section 2.7 of the PWS.

24c. Question: Would 15 years professional experience be an acceptable substitute for a Bachelors Degree for the EA position?

ANSWER: See revised Personnel Requirements in Section 2.7 of the PWS.

24d. Question: Does the EA position require experience performing analysis with architecture tool features, databases and business intelligence products?

ANSWER: See revised Personnel Requirements in Section 2.7 of the PWS.

25. QUESTION: Section 2.5.3 SE Qualifications: A bachelor's degree from an accredited college or university with major study in engineering, physical science, mathematics, life sciences, computer science, or other field of science. Would it be correct to assume the Systems Engineer labor category requires a Secret Clearance?

ANSWER: Yes, see Section 2.8 of the PWS.

26. QUESTION: Section 3.10 Period of Performance. The base period of performance shall be two years. Are there any option periods?

27. QUESTION: Section 3.6 Summary Requirements. At least one Enterprise Architect personnel supporting para. 3.1.3, 3.1.4, and 3.1.5 shall be designated as key personnel who must be highly knowledgeable of the Business Enterprise Architecture and compliance requirements, as well as portfolio management as practiced by DoD and the Army.

Does this mean a total of ONE Key Person for this entire PWS, or does this mean THREE Key persons for this entire PWS? (I.E. one for 3.1.3, one for 3.1.4, and one for 3.1.5) ??

ANSWER: Four key personnel. See Sections 2.1, 2.4, 2.5, and 2.6 of the PWS.

28. Section 5.1.1 Clearance Requirement

Contractor personnel performing work under this contract shall have a minimum of SECRET clearance. One (1) of the contracted personnel on this effort is required to have a Top Secret Clearance.

28a. QUESTION: Would it be correct to assume the number of contractor personnel needing a Top Secret clearance is two(2) instead of only one(1) ?

ANSWER: Only one Top Secret clearance is needed. See Section 5.1.1 of the PWS.

28b. The Contractor is responsible for obtaining the necessary clearances and ensuring contract personnel have the appropriate clearances at time of contract award. The security requirements are in accordance with the attached DD 254. Interim Secret clearance is unacceptable. Question: Would the Government consider allowing contractor personnel to begin work with an interim clearance?

ANSWER: Yes

29. QUESTION: Section 5.1.4 – Conflicts of Interest The contractor shall not hire any person for this contract whose employment would result in an appearance of a conflict of interest as defined in 5 CFR 2635.502. The contractor shall notify the KO in writing, five

(5) working days prior to employing any active civilian Government or military personnel.

If a company is already under contract to the Army as a materiel developer, or as Program Office Support for an Army Business System, does that present a Conflict of Interest with respect to working at the Army OBT per this solicitation?

ANSWER: Due to the nature of the data regarding business systems and the business system portfolio, all personnel must sign a Non-Disclosure Agreement.

30. Cost Model spreadsheet

30a. Question: In the Labor Cost Detail tab of the Cost Model spreadsheet, there are only 960 hours indicated for the Systems Engineer labor category, as opposed to 1920. Is 960 hours the correct requirement?

ANSWER: Yes.

The wording in paragraph 2.5.2 “long duration missions and experience in leading teams of data systems engineers and scientists” This does not sound like part-time work… Does the gov’t intend for this to be only a part time position? If so, what part of the PWS is the Systems Engineer aimed at? IF only 960 hours – how are these hours allocated? (Full time for 6 months, half time for 12 months? on-call as needed?)

ANSWER: Full time for 6 months

30b. QUESTION: Cost Model spreadsheet: In the Labor Cost Detail tab of the Cost Model spreadsheet, there are 7 “Senior Enterprise Architects”, and 3 “Enterprise Architects”. Would the Government consider adjusting this spreadsheet so there are 5 “Senior Enterprise Architects”, and 5 “Enterprise Architects”? As written, the ratio of 7 Senior to 3 regular architects does not seem to be an optimum mix of personnel to achieve OBT’s transformational objectives.

ANSWER: See Sections 2.3, 2.4, 2.5, and 2.6 of the PWS.

31. Section L - Instructions, Conditions and Notices to Bidders

31a. QUESTION: FACTOR 1: Do each of the resumes required to be submitted represent a Key Personnel for the contract award?

ANSWER: Three SEAs and Program Manager are “KEY PERSONNEL”, however, the remaining submitted resumes are assumed to be personnel actually intended to work on the project (one for each labor category).

31b. QUESTION: FACTOR 1: If the Government changes the Labor Cost Detail tab of the Cost Model spreadsheet to reflect only 5 “Senior Enterprise Architects”, would number of resumes required for “Senior Enterprise Architect” also be 5?

ANSWER: No, four are required

31c. QUESTION: FACTOR 1: If the Government changes the Labor Cost Detail tab of the Cost Model spreadsheet to reflect a need for 5 “Enterprise Architects”, would number of resumes required for “Enterprise Architect” remain at only 1?

ANSWER: Yes.

32. QUESTION: Page 41. Far Clause 52.217-9 OPTION TO EXTEND THE TERM

OF THE CONTRACT (MAR 2000). Does paragraph (c) imply that the Government can extend the contract for an additional 24-month period AFTER the base period….

or…. Is this text saying that because the contract length cannot go past 24 months, which is the same length of the base period, that there can be no extension at all.

ANSWER: The fill-in in Far 52.217-9 is being changed from “24 months” to “30 months”. If FAR 52.217-8 is exercised for 6 months, the total duration of the contract will not exceed 30 months.

33. QUESTION: Was the solicitation sent to the SDVOSB vendors who replied to the RFI?

Or was it solely posted to FBO?

ANSWER: It was solely posted to FBO.

34. QUESTION: If the prime is a SDVOSB and has built a team of subcontractors and one of the subs is a SDVOSBs does that combination of labor account for the 51%. Or must the prime SDVOSB have the 51%?

ANSWER: SDVOSB’s must perform 51% of work

35. QUESTION: Please provide the low price technically acceptable evaluation criteria for a professional services contract. OSD has provided written guidance about the use of LPTA strategies and professional services are generally not a good use of LPTA strategy.

ANSWER: See Section L, Evaluation Approach.

36. QUESTION: Section 2. Personnel Requirements

Please confirm all minimum education requirements that can’t be replaced by years of experience.

ANSWER: See revised Personnel Requirements of the PWS.

37. QUESTION: Does the government have a transition plan for the incumbent contract with requirements that they can share? Does the government have an expected transition plan and timeline for the new team and the incumbent vendor?

ANSWER: No, see Section 8.2 of the PWS.

38. QUESTION: Please confirm transition costs are not part of this proposal.

ANSWER: See CLIN 0004.

39. QUESTION: Section 2.3. Can you be more specific about the roles that the 7 Senior EA may play? Are all 7 equally supporting domains, or are some playing different roles?

ANSWER: See revised Personnel Requirements of the PWS. Three SEAs are designated as key personnel. The priority areas are all Domain/Process-oriented.

40. Section 2.3.3 EA Qualifications.

40a. QUESTION: The requirement states “A recognized Enterprise Architecture certification is required.” Our experience would expect a certification from an industry recognized certification body [e.g., Federal Enterprise Architecture Certification (FEAC), National Defense University (NDU), The Open Group Architecture Framework (TOGAF), Global Enterprise Architecture Organization (GEAO)]. If so, please name which professional certifications you will consider.

ANSWER: See Section 2.3.3 of the PWS.

40b. QUESTION: The requirement also states “A recognized Enterprise Architecture certification is required.” Please confirm this means that a software vendor tool certification is not acceptable.

ANSWER: See revised Personnel Requirements in Section 2.3.3 of the PWS.

41. Cost Model Spreadsheet

41a. QUESTION: Is the Systems Engineer role intended to be half time or may we propose a Full Time role? Is this role supporting CIO/G6, EKR development or other purpose?

ANSWER: Full time for six months. Role is in support of CIO/G-6, PM-AESIP, PM- EIS (and others)

41b. QUESTION: If the vendor believes that additional billets are warranted to support the OBT, can the vendor recommend them in the spreadsheet?

ANSWER: No.

42. Section 3.2.1

QUESTION: Is the OBT the material developer or is it the functional requirements developer? Will EKR development occur within the OBT or will development continue to exist with ARDEC or CECOM?

ANSWER: OBT is not the material developer. No changes to the EKR material developer are currently forecast.

43. DD254

We request that the government make the necessary edits to the DD254, publish an amendment, and provide adequate time for vendors to properly document their security capabilities in their proposals.

a.) QUESTION: Section 1.a. - Facility clearance is labeled as ‘’Secret’’ but doesn’t coincide with section 11.l., stating that at least one Senior Enterprise Architect possess a Top Secret clearance on this contract. The minimum facility clearance in this case must be TS.

ANSWER: The facility clearance is correct as SECRET. The facility clearance is not required to match the clearance level of the employees.

b.) QUESTION: Section 1.b. - Level of Safeguarding Required is labeled as “Secret”.

Few, if any, qualified SDVOSBs would carry this level of Safeguarding capability according to NISP and DSS requirements. The government has stated that the place of performance will be on Government sites. If no classified material is to be stored at the CONTRACTOR site, then the field should state “None”.

ANSWER: Block 1.b. has been changed to "None" c.) QUESTION: Section 8.a. (also referencing Section 11.a.) - Actual locations/addresses must be more specific. If contractor sites are required, then the Level of Safeguarding is necessary (Section 1.b.). Vendors must be informed of the locations on this form (not just elsewhere in the solicitation) in order to properly address the security requirements.

ANSWER: Block 8a. has been updated.

d.) QUESTION: Section 10.e – Either line (1) or (2) must be selected. Both entries cannot be identified under the “No” column.

ANSWER: Block 10e(2) has been changed to "Yes".

e.) QUESTION: Section 10.k. - This entry must have be specified as Yes or No. It cannot remain blank.

ANSWER: Block 10k. has been changed to "No" as there is not other information.

f.) QUESTION: Section 12 – minor typo, where the City should be properly identified as Washington, DC.

ANSWER: Block 12 has been changed from "Washington, D 20310" to "Washington, DC 20310" g.) QUESTION: Section 11.a., 11.b., and 11.c. contradict Section 1.b. If no classified material is to be stored at the CONTRACTOR site, then Keep 11a-c but change 1.b.

If the contractor is expected to store classified material at the contractor site, then Keep 1.b. but change 11a-d accordingly.

ANSWER: Blocks 11.a., 11.b., 11.c, and 11.d are correct and no changes were made.

No safeguarding of materials is required at the contractor site.

h.) QUESTION: Section 16 - The phone number for the security officer, Vickie Hall, does not contain the correct area code. The correct area code is “703”.

ANSWER: Block 16c. has been changed to "703-601-9106".

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 23-May-2016 12:00 AM to 26- May-2016 11:00 AM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0003

The FSC code R425 has been added.

The PROG code S10 has been added.

The WSC Equipment code 000 has been added.

The SIC code 9999 has been added.

The NAICS code 541611 has been added.

The MDAP/MAIS Code 000 has been added.

CLIN 0004 is added as follows:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0004 Lot Transition

FFP

Transition in accordance with PWS Paragraph 8.2.

FOB: Destination

NET AMT

The following have been modified:

MINIMUM/MAXIMUM

MINIMUM/MAXIMUM

This is an Indefinite Delivery/Indefinite Quantity contract with Firm Fixed Price task orders with a minimum award of $5,000.00 and a maximum award of $7,000,000.00.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

PERFORMANCE WORK STATEMENT

1.0 REQUIREMENTS BACKGROUND

1.1. Background

As the threats to the Nation’s security become more diverse and challenging, the demand to support the current operational tempo requires the Army to look for innovative solutions to organize, man, equip, train, and fund the modular force on a rotational and sustained basis.

The Secretary of the Army designated the Under Secretary of the Army as the Army’s Chief Management Officer (CMO) in accordance with Congressional guidance, and the Office of Business Transformation (OBT) to assist the CMO in carrying out business transformation initiatives to guide and improve Army business operations with a new business model. Army business transformation shall be broad in scope and closely aligned with the management priorities outlined in the Department of Defense (DoD) 2012-13 Strategic Management Plan and Congressional guidance on improving business operations.

The CMO is responsible for providing the business architecture, governance, and investment oversight, to include business systems compliance, needed to achieve the Army’s enterprise management goals. The OBT reports directly to the CMO in support of these efforts.

The Army is developing an Army Business Enterprise Architecture (formerly Business Systems Architecture) (ABEA) covering all Army business operations, in order to satisfy statutory requirements from the National Defense Authorization Acts (NDAA) of 2009 and 2010. The ABEA describes the key components of the institutional army across seventeen (17) End-to-End (E2E) processes into an evolving operational blueprint. It also supports portfolio management, business systems investment review, and transition planning. The ABEA provides the Army its own enterprise architecture while ensuring compliance with DoD’s Business Enterprise Architecture (DBEA). The key components of the ABEA are seventeen (17) E2E business processes including associated information flows, as well as the 710 systems in the Army Defense Business System Portfolio. Especially critical are the core Enterprise Resource Planning systems (ERPs) which form the backbone of the to-be environment.

As highlighted in the Army’s Business Strategy (ABS), the Army is moving toward managing its business operations using E2E process mapping. Within this construct, seventeen (17) E2E processes span the Army’s core business missions to synchronize and optimize Army mission area, domain, and command functions. The Army Business Management System (ABMS) also singles out key components for enterprise Information Technology (IT) management, including enterprise governance, enterprise architecture, portfolio management, investment analysis, and solution development.

1.2. Scope

This effort requires technical expertise to support business transformation efforts in the following general areas:

strategic planning business alignment IT requirements and acquisition reform efforts Enterprise Resource Planning (ERP) software implementation and convergence planning business architecture development E2E business process modeling and improvement and business investment governance system and service architecture development technical services to evaluate emerging technologies that could accelerate business transformation liaison support with Office of the Secretary of Defense (OSD) Staff, Military Services and Army

Commands executing transformation initiatives and activities implementing business changes that shall occur

1.3. Intent

The scope of work covered in this Performance Work Statement (PWS) requires specialized enterprise architecture, business process analysis, and facilitation knowledge and expertise necessary to facilitate and perform E2E business process mapping and modeling, system/service architecture development in support of E2E processes, investment analysis in conjunction with business process re-engineering and the requisite skills to enable and provide technical enterprise and support infrastructure services. The E2E business processes include the seventeen (17) published in the DoD BEA.

Required capabilities for this effort include: the capability to work with Subject Matter Experts to gather information about business processes and to incorporate the information into models of the business and business systems; the capability to manipulate and employ architecture tools to capture, manage and use architecture data; and the capability to rationalize a portfolio that contains business systems to reduce cost and risk.

The Office of Business Transformation operates as a collaborative hub for transformation efforts across the Army Business Mission Area. These efforts take many forms including (but not limited to):

1.3.1. Deep Dive Analysis – Targeted effort, usually generated through the Army Business Council (ABC), intended to attack and solve a known business problem at the detail level

1.3.2. Problem Statement Development – Structured process to identify and quantify a business problem following the OSD Requirements Validation process

1.3.3. End to End Process Maturation (streamlining) – Targeted effort to define and refine high level business process interactions crossing multiple domains

1.3.4. Business Process Reengineering – Holistic effort designed to radically change and improve business processes, typically to realize financial or manpower savings

1.3.5. Continuous Process Improvement (CPI) – Effort intended to enhance local or tactical processes through incremental improvements

1.3.6. IT Portfolio Reviews – Annual review of Domain portfolios

1.3.7. IT Portfolio Road mapping – Continuous process to leverage Portfolio Review (PfR) to define ways forward (roadmaps)

1.3.8. Data (Master data) Analysis – Identification and standardization of business data requirements with a heavy focus on cross-domain (Master data) requirements

1.3.9. Technology Insertion – Efforts to identify and quantify opportunities to insert enabling or disruptive technologies into Army solutions and business processes.

OBT’s operating model is to bring groups of subject matter experts from across affected Commands, Domains, and Solutions to work toward consensus-based approaches to solving Army business problems. These efforts may either be in a supporting role (with Commands/Domains) in the lead, or in a leadership role on behalf of the enterprise.

Work products produced throughout all of these efforts impact and are integrated in to the Army Business Enterprise Architecture.

Personnel supporting this effort shall work in tandem with OBT government personnel (military and civilian) as liaisons with Domain architecture and portfolio management support teams. In this role, the effort requires knowledge of the Business Enterprise Architecture, published by the DoD Office of the Deputy Chief Management Officer, the Department of Defense Architecture Framework (DoDAF v2.02), and the expertise to incorporate required changes/upgrades into the Army’s Business Enterprise Architecture. Required capabilities also include the analytical skills and technical knowledge to support investment decisions, perform liaison services, and facilitate collaboration among OBT stakeholders, and support the statutory and regulatory requirements for managing Army business systems.

1.4. Objectives

The objectives are as follows:

1.4.1. Provide highly-specialized expertise and skills in support of business process teams, including facilitating the modeling of the seventeen (17) E2E Business processes plus any new E2E processes that may be required. Facilitate collaboration focused on rationalizing and integrating the Army’s business system portfolio

1.4.2. Provide enterprise architecture expertise in support of the Army Business System portfolio, with emphasis on the evolving ERP ecosystem

1.4.3. Facilitate the development and continuous refinement of the Army Business Enterprise Architecture & Enterprise Roadmap

1.4.4. Contribute to the IT portions of the Army’s Annual Congressional Report.

1.4.5. Collaborate with Headquarters Department of the Army (HQDA) staff agencies and their Direct

Reporting Units, US Forces Command, US Training and Doctrine Command and US Army Materiel Command

1.4.6. Align investments with business architecture. Update and coordinate Army input to the DoD Enterprise Transition Plan

1.4.7. Ensure investments comply with the Business Enterprise Architecture and statutory requirements for Business Process Re-engineering

1.4.8. Support the Government’s performance of strategic planning and technical services necessary to implement the Army Business Management Strategy

1.4.9. Participate in working groups and forums across the Army, DoD, and Federal government on behalf of the Office of Business Transformation

1.4.10. Support development and operations of governance structures for Army business operations to include institutionalizing the BSA as a foundational capability to make informed investment decisions.

2. Personnel Requirements/Qualifications

2.1. Program Manager (PM) – Key Personnel

2.1.1. The PM is considered key personnel and is responsible for the overall administrative management of contractor personnel and ensuring the achievement of all contract performance requirements.

2.1.2. The PM may also be called upon to assist in coordinating the activities of the contractor team and other government POCs.

2.1.3. PM Qualifications: The PM shall possess a Bachelor’s degree in business administration, business management, or human resources. The PM shall have five (5) years supervisory experience in the management of personnel. The PM shall have a background in overseeing problems of similar scope and technical requirements, must be able to interact with senior Army officials, and shall have a Secret clearance.

2.2. Consultant / Facilitator

2.2.1. Consultant / Facilitator is responsible for all the tasks needed to run a productive and impartial meeting. The Consultant / Facilitator shall be able to serve the needs of any group who are meeting with a common purpose, whether it be making a decision, solving a problem, or exchanging ideas and information. This person shall have a minimum of ten (10) years’ experience in assisting government personnel in their efforts to lead groups through training, education, or mentoring activities. Must be a US Citizen and must have a Secret clearance prior to beginning work on the project.

2.3. Senior Enterprise Architect (SEA)/Systems Architect I / BPR Specialist

2.3.1. The SEA is responsible for work that involves developing strategies in support of an organizations IT portfolio; developing technical documents relating to process-centric architectures including business process models. A high degree of understanding of underlying business processes and Information Technology, such as system interface diagrams and data schemas is required. These persons shall be developing an enterprise architecture from a collection of subject matter interviews, research in other government architecture (e.g. Federal Enterprise Architecture, DoD Business Enterprise Architecture), reviewing system architectures; analyzing information system architectural requirements for an enterprise.

2.3.2. These persons shall have an understanding of a recognized DoD Architecture Framework. They shall also have demonstrated a minimum of eight (8) years’ experience in documenting business processes and establishing relationships and linkages to IT systems. They shall demonstrate a minimum of eight

(8) years’ experience in applying architecture data to conduct architecture-based analysis.

2.3.3 SEA Qualifications: A bachelor's degree from an accredited college or university with major study in systems engineering, computer information systems, computer science, or similar discipline.

The SEA shall have a minimum of eight (8) years’ experience in direct support to enterprise architecture projects to include those focused at a business or strategic level. Three (3) additional years demonstrated experience in business architecture development can be substituted for the educational requirements.

The SEA shall have demonstrated knowledge of some segment of business architecture (e.g., Logistics, Human Resources, Acquisition, etc.). Experience with the US Army or other DoD activity is required.

Must be a US Citizen and must have a Secret clearance prior to beginning work on the project.

2.4. Senior Enterprise Architect (SEA) Army Business Enterprise Architecture (BEA) Architecture Management and Cross-Domain Integration (Lead) (Key Personnel)

2.4.1 The SEA is responsible for work that involves developing strategies in support of an organizations IT portfolio; developing technical documents relating to process-centric architectures including business process models. A high degree of understanding of underlying business processes and Information Technology, such as system interface diagrams and data schemas is required. These persons shall be developing an enterprise architecture from a collection of subject matter interviews, research in other government architecture (e.g. Federal Enterprise Architecture, DoD Business Enterprise Architecture), reviewing system architectures; analyzing information system architectural requirements for an enterprise.

2.4.2 These persons shall have an understanding of a recognized DoD Architecture Framework. They shall also have demonstrated a minimum of eight (8) years’ experience in documenting business processes and establishing relationships and linkages to IT systems. They shall demonstrate a minimum of eight (8) years’ experience in applying architecture data to conduct architecture-based analysis.

2.4.3 SEA Qualifications: A bachelor's degree from an accredited college or university with major study in systems engineering, computer information systems, computer science, or similar discipline.

The SEA shall have a minimum of eight (8) years’ experience in direct support to enterprise architecture projects to include those focused at a business or strategic level. Three (3) additional years demonstrated experience in business architecture development can be substituted for the educational requirements.

The SEA shall have demonstrated knowledge of some segment of business architecture (e.g., Logistics, Human Resources, Acquisition, etc.). Experience with the US Army or other DoD activity is required.

Must be a US Citizen and must have a Secret clearance prior to beginning work on the project.

2.4.3 The SEA shall demonstrated experience with:

1) Leading and managing a team of senior architects

2) Managing complex architecture data using COTS-based tools (preferably ARIS)

3) Working with senior government staff

4) Developing guidance and policy across a complex environment (preferably DoD)

5) Developing innovative and impactful ways to leverage architecture data

2.5 Senior Enterprise Architect (SEA) Process / Data Architecture Development (Lead )(Key Personnel)

2.5.1 The SEA is responsible for work that involves developing strategies in support of an organizations IT portfolio; developing technical documents relating to process-centric architectures including business processmodels. A high degree of understanding of underlying business processes and Information Technology, such as system interface diagrams and data schemas is required. These persons shall be developing an enterprise architecture from a collection of subject matter interviews, research in other government architecture (e.g.

Federal Enterprise Architecture, DoD Business Enterprise Architecture), reviewing system architectures;

analyzing information system architectural requirements for an enterprise.

2.5.2 These persons shall have an understanding of a recognized DoD Architecture Framework. They shall also have demonstrated a minimum of eight (8) years’ experience in documenting business processes and establishing relationships and linkages to IT systems. They shall demonstrate a minimum of eight (8) years’ experience in applying architecture data to conduct architecture-based analysis.

2.5.3 SEA Qualifications: A bachelor's degree from an accredited college or university with major study in systems engineering, computer information systems, computer science, or similar discipline.

The SEA shall have a minimum of eight (8) years’ experience in direct support to enterprise architecture projects to include those focused at a business or strategic level. Three (3) additional years demonstrated experience in business architecture development can be substituted for the educational requirements. The SEA shall have demonstrated knowledge of some segment of business architecture (e.g., Logistics, Human Resources, Acquisition, etc.). Experience with the US Army or other DoD activity is required. Must be a US Citizen and must have a Secret clearance prior to beginning work on the project.

2.5.4 In addition the SEA shall have demonstrated experience with:

1) Leading and managing groups of subject matter experts in documenting complex, business processes

2) Deriving information requirements from complex processes

3) Working with senior government staff

4) Linking process architecture to solutions architecture to support architecture based analysis

2.6 Senior Enterprise Architect (SEA) Application/Technology Architecture Development Lead (Key Personnel)

2.6.1. The SEA is responsible for work that involves developing strategies in support of an organizations IT portfolio; developing technical documents relating to process-centric architectures including business process models. A high degree of understanding of underlying business processes and Information Technology, such as system interface diagrams and data schemas is required. These persons shall be developing an enterprise architecture from a collection of subject matter interviews, research in other government architecture (e.g. Federal Enterprise Architecture, DoD Business Enterprise Architecture), reviewing system architectures; analyzing information system architectural requirements for an enterprise.

2.6.2 These persons shall have an understanding of a recognized DoD Architecture Framework. They shall also have demonstrated a minimum of eight (8) years’ experience in documenting business processes and establishing relationships and linkages to IT systems. They shall demonstrate a minimum of eight (8) years’ experience in applying architecture data to conduct architecture-based analysis.

2.6.3 SEA Qualifications: A bachelor's degree from an accredited college or university with major study in systems engineering, computer information systems, computer science, or similar discipline.

The SEA shall have a minimum of eight (8) years’ experience in direct support to enterprise architecture projects to include those focused at a business or strategic level. Three (3) additional years demonstrated experience in business architecture development can be substituted for the educational requirements.

The SEA shall have demonstrated knowledge of some segment of business architecture (e.g., Logistics, Human Resources, Acquisition, etc.). Experience with the US Army or other DoD activity is required.

Must be a US Citizen and must have a Secret clearance prior to beginning work on the project.

2.6.4 In addition the SEA shall have demonstrated experience with:

1) Leading and managing groups of subject matter experts in documenting solution architecture

2) Integrating architecture content from multiple solutions into enterprise views

3) Working with senior technical staff (government and contractor) to develop system roadmaps

4) Linking process architecture to solutions architecture to support architecture based analysis

2.7 Enterprise Architect (EA)/Systems Architect II / BPR Specialist

2.7.1 The EA is responsible for work that involves documenting business processes, information requirements, and solution architecture in support of an organization’s IT portfolio, developing technical documents relating to process-centric architectures including business process models, or similar diagrams, developing an enterprise architecture from research in policy, interviews with subject matter experts by analyzing system architectures; analyzing information system architectural requirements for an enterprise and developing business processes to span an enterprise.

2.7.2 EA Qualifications: A bachelor's degree from an accredited college or university. Shall be a US

Citizen and shall have a Secret clearance at time of contract award. The EA shall have a minimum of two (2) years’ experience in direct support of enterprise architecture projects. A degree in a technical field (computer science, systems engineering, computer information systems, or related area) may be substituted for the experience requirement. Must be a US Citizen and must have a Secret clearance prior to beginning work on the project.

2.8 Systems Engineer (SE)

2.8.1 The Systems Engineer shall be a recognized systems architect, technical authority, and technical adviser/consultant to agency management, other government agencies, and industry. The SE is the primary point of contact on system requirements affecting major projects. Identifies the most promising software and data system technologies for infusion and application to solve center and agency-wide challenges.

2.8.2 The SE shall have specialized experience in systems architecture, design, and data integration to originate requirements and apply emerging functions of a national or international magnitude for onboard autonomy for long duration missions and experience in leading teams of data systems engineers and scientists to produce complex data-driven systems to enable knowledge extraction and information integration for autonomous capabilities in various data domains..

2.8.3 SE Qualifications: A bachelor's degree from an accredited college or university with major study in engineering, mathematics, computer science, or related field. Must be a US Citizen and must have a Secret clearance prior to beginning work on the project.

3 Task Areas

3.1 Army Business Enterprise Architecture Evolution

The following are the major task areas described below:

E2E Business Architecture Development Army BEA Architecture Management and Cross-Domain Integration Process / Data Architecture Development Application/Technology Architecture Development Enterprise Analysis and Liaison Activities Enterprise Knowledge Repository Direct Domain Architecture Support Army E2E Business Architecture Development Support

3.1.1 E2E Business Architecture Development

Provide architecture development services to support the evolution of the Army Business Enterprise Architecture focusing on artifacts aligned to the figure below and defined in the Army Business Strategy and the ABEA 5-Year Implementation Plan.

Figure 1: Army Business Enterprise Architecture (ABEA) Framework

The Government requires enterprise architecture support to map E2E business processes for Human Capital, Acquisition and Logistics, Finance, Training Readiness, and Installations, Environment and Energy, and their integration, in addition to developing Data, System, and others models and performing analyses in support of business process re-engineering, problem statement development, portfolio analysis, master data management or other business transformation activities. The ABEA shall be heavily focused on Process and Data Architecture for the foreseeable future, efforts in System and Technology architecture shall be evolving but on a smaller scale.

3.1.2 Army BEA Architecture Management and Cross-Domain Integration Provide technical services to manage the evolution of the Army Business Enterprise Architecture (ABEA), ensuring horizontal and vertical integration of content:

a. Update and maintain the ABEA Methods and Conventions document, interface with DOD/OSD architecture community, discover and recommend ways to integrate best practices into the ABEA.

b. Develop and execute processes to ensure consistency across the segments (Domains) of the ABEA.

c. Develop and manage the ABEA Overview and Summary (all viewpoint (AV-1)), ensure a consistent…