19 Implementation of CVR / IT Methodology on Outsourced Applied Research to Internship Environment , Case , Information Technology Directorate of Bina Nusantara Foundation

ITD consists of three main divisions, as in Fig 1. The Information System Development Division (IS Dev) is responsible in developing and maintaining whole foundation Information System Solution, such as web sites and console applications. The Network, Data, and Operational Division (Oper) are responsible in building and maintaining Network Connections, Data Storage and Servers, and daily operational procedure in foundation. Technology Development Division (Tech Dev) is responsible in maintaining applied research researchers and Internship partner students for helping the whole directorate.


Group Activities
Establish and report project status

Whole design
The whole design shall be explained in 3 parts, stakeholders, methods templates, and procedures, as in Table 2.The CVR / IT Standard were mapped as in Table 3.The mapping is necessary to alleviate several problems.In research world, resources often come from grant that has fixed schedule, so grant must be pursued before researcher procurement.Furthermore, to maintain whole University research map, all research planned must go through committee examination.After the permission granted, researcher must procure student for running the research.

Stake holders
These system stake holders are as follows.

System implementation test
The CVR / IT system adoption rate is calculated using simple equation, how much activities mandated from CVR / IT already implemented on current system.

Result
The CVR / IT system adoption rate is as in Table 2. Furthermore, the system adoption status is in Table 3.To alleviate these problems, writer suggested to start from changing student paradigm, start from early semesters.The class should be shaped to expose student to project development culture, where they learn to address real world problem, came up with solution, and essentially, to work together and to track progress, because most project fail in the last two items.

Activities Adoption Status Assign an initiating
Several alternative solutions can be made.First is to encourage project based activities on class.Although this model can be considered artificial, at least that could train student responsibility on keeping with documentation and schedule.
Second is, to bridge the class to real life industries.The first variant is to get industrial agreement to be the sand box for class project.The second variant is to us real life project as either the complement or substitute of relevant credit.
The third one is, to actually shape the class as a software factory, where student accomplishment measured by task and project based style.The project should come from out school.Another variant of this model is to consider the whole university as a software factory, where the upper classes act as analyst and managers, and lower classes as programmers.
Only when student understand the project environment and the consequences behind it, the CVR / IT adoption rate (or, any project management standard in general) shall rise.

Conclusion
Based on observation, the system adoption rate is 40 % at most.Further activity is needed to raise the value to 100 %, addressing how to reduce fear in student, and how to manage research documentation and monitoring.
Solution made should aim to introduce and raise student awareness to project management environment o early semesters.

Acknowledgement
The author would like to thank Mr. Gintoro FX, this system is based on his idea to expand current associate member system to accommodate IT Directorate needs.This work will not taken place to begin with if without his idea.
The author would like to Thanks Mr. Eddy Santosa Jaya, Head of Information Technology Directorate, and everyone within the directorate to support the program adoption and let the study takes place.

4.16 Researcher Punishment Activities Researcher
Punishment Procedure is as in Fig 17.System shall punish every researcher based on their achievement in research.Fig.17.Researcher Punishment Procedure Standard.Researcher Punishment Activities critical success factor is 1.Every Researcher status is reviewed, 2. Every Researcher Evaluation Report is reviewed, 3. Verify Researcher misconduct to themselves, related Research Specialist, ResearchCoordinator, or other related person / group, 4. Ensure that the Researcher is deserved to be punished, If the misconduct is made not by them, they did not deserve to be punished, Technology Development Manager already approves the Researcher punishment report draft, and 6.Punishment is mandated to the deserved Researcher.
 Head of Information Technology Directorate, Head of Information Technology Department and Board of Management.They are in charge of judging research product and its availability for incubation.Thesis Student.Main source of internship program.www.intechopen.comFig. 16.Researcher Reward Procedure Standard.Researcher Reward Activities activities is 1.Review every Researcher Evaluation Report, 2. Review available budget, 3. Obtain approval of Researcher Reward Report Draft from Technology Development Manager, 4. Pay every Researcher Reward, and 5. Update Budget Balance.Researcher Reward Activities deliverables is Form R15.Researcher Reward Report 2.www.intechopen.com 5.

Table 4 .
CVR / IT adoption current status.Preservation of Research tree is still uncommon in Binus University by the time this paper is written.IT Directorate must establish its own research tree, based on Research Directorate inputs.Different Point of View (POV) between IT Directorate and IT Department does ignite problem, mostly in how the project conducted and roll out of project.Some monitoring and documentation activities and rules cannot be done due conflict with IT Department rules.